JPM MSDK - VIDEO 2 - Install Core API

This tutorial covers basic MSDK Core API installation and configuration. Use MSDK Director and kit documentation for deeper guidance. To start, download the MSDK from the Developer Center and save it to a local directory. To begin the install, extract the package using the jar -xvf command or a utility like WinZip, set system environment variables, then run quickcheck to validate the installation.

The MSDK contains important directories like bin that includes the MSDK proxy server, scripts to run programming samples, and generate security keys. Quickcheck-- installation validation utilities Logs-- log4j2 generates files that record processing events. The MSDK can be set up for one of three development models with each model supporting a variety of payment systems, processing types, and connectivity configurations.

Configurations are created by editing the appropriate XML file in the config directory. Files are named with associated payment system, processing type, and connectivity identifiers, and have configuration instructions embedded. Using Stratus Online HTTPS with the simulator as an example, the basic steps for implementing a simulator-based development model are configure connectivity, start the HTTPS simulator, build and send a transaction. Test in production security credentials will be provided during the boarding process. 

JPM MSDK - VIDEO 3 - Install & Configure  Universal Interface

This is the MSDK Universal API Installation and Configuration Tutorial. It builds on the Core Interface Installation Tutorial. Use MSDK Director and kit documentation for deeper guidance.

The Universal Interface is an optional MSDK JAVA kit component that works with the core API to provide REST-like services. It runs in a Java servlet container and accepts HTTPS payment transactions formatted in JSON, XML, URL, or CSV.

Transactions flow from a payments-enabled application or device to the universal interface for core interface and payment system processing. The universal interface can be implemented using the open source Jetty server included in the kit or using the standard application server WAR file downloaded from Developer center. The umpire directory contains utilities, processing samples, and service components for the universal interface.

Quickcheck has the utilities needed to validate the Universal API installation with programming examples in various languages and data formats in the Samples directory and service containing Windows utilities and MSDK login mechanisms. The Universal interface uses log4j2 to record events to common MSDK log files. To use the built-in Jetty option, start the interface by double clicking on or typing the umpire command. Use the quickcheck utility to validate the installation. To implement the WAR file option, extract umpire.war to the application server's Web Apps directory. Restart the application server and run quickcheck.

[MUSIC PLAYING] 

JPM MSDK - VIDEO 4 - Core API Programming [MUSIC PLAYING]

This tutorial covers basic MSDK Core API Programming. Use MSDK Director and its quick code feature for customized guidance. The MSDK Core API supports Orbital, Stratus, and Tandem online processing, where transactions are processed immediately using a request-response handshake.

It also handles Stratus batch processing, where transactions are collected in a file then submitted to Stratus for processing, and Tandem upload processing, where transactions are held by a point of sale system, then uploaded to Tandem to complete the payment cycle. Programming samples for these and other processing types are in directory MSDK_HOME/samples.

Technical specifications convey payment system-specific processing logic not included in the MSDK and are used in conjunction with MSDK coding tools to build solutions. CodeAssist can accelerate the coding process with MSDK transaction format class files for Eclipse, Visual Studio, and other compatible IDEs. And the HTML format reference guide provides quick access to MSDK transaction formatting details.

The Stratus online programming sample, SLMOnlineAuth.java, is used as a guide for this tutorial. Step one, construct a dispatcher. Step two, create a request object with processing type New Transaction and connectivity type TCPConnect, private network. Step three, add transaction-level configuration values such as security credentials provided by merchant services using request.getConfig().setField().

Step four, build the Stratus-based payment transaction by setting format record field values as needed. Step five, continue to build the transaction with optional format records, fields, and values. Step six, send the transaction to Stratus using process request. This action also creates a resp object and blocks subsequent code execution until the Stratus response is received.

Step seven, process the response message using getInField. Then handle success or processing errors. The same coding framework is used for .NET and all supported development models, payment systems, and connectivity types. 

JPM MSDK - VIDEO 5 - Universal API Programming

This tutorial covers basic MSDK Universal API programming, use MSDK Director, and its quick code feature for customized guidance. The Universal API, UMPIRE, supports Orbital, Stratus, and Tandem online processing, where transactions are executed immediately using a request-response handshake.

[MUSIC PLAYING]

It handles Stratus Batch, where transactions are collected in a file, then submitted to Stratus, and Tandem Upload, where transactions are held by a Point Of Sale, POS system, then uploaded to Tandem to complete the payment cycle.

[MUSIC PLAYING]

Data-driven programming examples are in the UMPIRE samples data directory. Technical specifications convey payment system-specific processing logic, not included in the MSDK. Specifications are used with MSDK APIs and coding tools to build solutions.

With data-driven programming, payment transactions are coded as name value pairs, using a programming language that supports HTTP. All values must be ASCII strings.

[MUSIC PLAYING]

The payments-enabled application or device uses HTTP to connect to the interface. Use the Format Reference Guide in the doc directory for quick access to MSDK transaction formatting details.

[MUSIC PLAYING]

The Stratus Online Authorization, JSON sample is used as a guide for this tutorial.

[MUSIC PLAYING]

Begin by coding the header section, specify JSON-RPC version 2.0. For ID, use a unique integer value entered as a string. And for method, enter, "Process" that is used for all JSON transactions.

Build the control section of the transaction, specify the action to take, configuration file to use, and security credentials provided. Code the required process transaction format record fields, followed by any additional format records and fields needed to complete the transaction.

[MUSIC PLAYING]

Using content type "mime applcation/json-rpc," send the transaction to the Universal Interface URL. Process the HTTP response, handling success or error conditions.

[MUSIC PLAYING]

The same coding approach is used for all development models, payment systems, and connectivity types.

[MUSIC PLAYING] 

This tutorial covers updating the MSDK. Use MSDK director and kit documentation for additional guidance. With technology advancing rapidly, keeping payment components current is critical. MSDK updates are made available at a regular cadence providing developers access to the latest scan code and regression tested technology.

Updates are identified by a unique numeric value with modification details described in release notes. Major and minor releases are binary updates that can include, MSDK framework, tool, and template advancements. Micro releases are non-binary format template replacements that provide developers access to the latest payment products and services. To install a binary release, review the release notes, download the new MSDK kit extract and validate kit content, replace the old MSDK with the new version, and copy over important configuration attributes, test the new kit deployment.

One for one binary updates do not require JPMC integration testing unless changes are made to the client's application. To install a micro release after download, replace the old template library and test the deployment, and replace the HTML format reference guide and if needed, build updated IDE class files. Micro releases do not require JPMC integration testing until new payment products or services are implemented. For dot war file micro release installation, open the umpire.war, replace the old template library with the new one, restart the app server and test the deployment. 

This tutorial covers MSDK software development tools. A key MSDK principle is to position payment know-how at the point of development where it has real value. With documentation, IDE classes, interactive utilities, payment simulators, and more, the MSDK has tools built for productivity. Payment engine interface specifications are used to identify format elements and processing logic needed to build custom applications. MSDK specific documentation provides detailed development guidance that includes, release notes, providing technical details associated with each release.

MSDK quick references with a design and set-up guide that covers basic architectural concepts, installation, and configuration details and a programming guide-- the details, the use of the core, and universal APIs. The HTML format reference guide delivers an MSDK coding syntax view of payment transaction formats with MSDK classes, providing in-line IDE payment code references with rapid code insertion capabilities, programming samples and build scripts a developers by highlighting payment coding techniques. Payment engine simulators provide a standalone sandbox environment echoing back responses to requests received from the MSDK. Simulator responses can be customized to mimic specific payment processing operations. MSDK director provides interactive guidance for a range of set-up integration and coding activities accelerating the payments enabled process. 

This tutorial covers MSDK SFTP batch processing, where the MSDK is used for end to end automation. JPMC assigns clients to SFTP server pairs. One pair for integration testing and the other for live transaction processing. Each pair has a primary and secondary server complete with failover capabilities.

For security, Public Key Authentication, PKA is implemented and encryption protects files in transit. For convenience, JPMC server fingerprints are preset in the MSDK SFTP configuration file along with other important attributes that can be modified.

A utility is included in the kit to generate key pairs for file encryption and authentication. Client public keys must be shared with JPMC to complete the setup process. Files at rest are also automatically encrypted for additional protection.

When coding, the submission descriptor class is used to create close, encrypt and transmit batch files for processing. And the response descriptor class retrieves JPMC batch processing result files that are mirrored on primary and secondary servers.

Mirrored files are available for 30 days unless removed by the client. An SFTP simulator is in the kit for offline sandbox development and testing. For increased flexibility, the MSDK supports batch processing using several integration methods. Use MSDK Director and kit tools for additional guidance.

[MUSIC PLAYING] 

This tutorial covers the MSDK proxy server, a standalone kit executable designed for high-volume online transaction processing, where persistent TCP/IP socket connectivity, load balancing, heartbeat messaging, retrieves, and other critical communication functions are required. Primary and failover proxy instances can run on the same computer as the MSDK core interface or in a distributed model using other computing resources on the network. In all instances, payment transactions flow from the MSDK core interface to the MSDK proxy server to the JPMC payments engine then back.

MSDK core interface attributes, like proxy server, IP address, and port number, are entered in the MSDK engine connectivity configuration file with MSDK proxy server origination listening port as well as JPMC payment engine destination IP and port entered in the proxy configuration file. Multiple engine ports can also be configured by defining additional destination elements. The proxy has its own event log-in function as defined in the log-in configuration file. Once all attributes have been properly established, the proxy server can be started.

The .NET proxy server starts as a Windows service. This mode can be disabled by using the no service switch. To secure data in transit, transport layer security is available for either or both the MSDK-to-proxy and proxy-to-payment engine communication channels. For sandbox testing, MSDK engine simulators can be used to validate the implementation. Be sure to update configuration files with simulator attributes. Use MSDK Director and kit documentation for additional guidance. 

[MUSIC PLAYING]

This tutorial covers the MSDK SFTP security framework used with NetConnect batch where RSA public key authentication, PKA, and PGP file in transit encryption are used. Files at rest are automatically encrypted by the MSDK with no additional setup required.

To get started, obtain a presenter ID and username from a JPMC technical implementations professional. Use the MSDK RSA key generation script to create RSA public and private key pairs. If needed, open the script file for additional command line options.

Once RSA keys are generated, send a copy of the public key along with the MSDK host IP address to JPMC. Update the MSDK SFTP configuration file with the PID, username, and RSA private key name. The MSDK validates JPMC server IDs automatically using JPMC primary and secondary SSH fingerprints that are preset in the configuration file.

To set up file and transit encryption, download JPMC VAR and PROD public PGP keys from developer center and save them to the MSDK directory that contains the RSA keys. The MSDK uses JPMC PGP public keys to encrypt batch files it sends to JPMC.

Create MSDK PGP public and private key pairs using the PGP key generation script. Ensure PGP keys are in the same directory as the other keys. Send a copy of the MSDK PGP public key to JPMC so that MSDK batch file submissions can be decrypted.

Complete the setup process by adding MSDK PGP private key name, JPMC PGP public key name for either VAR or prod, and another important attributes to the SFTP config file. For dynamic configuration management, attributes can also be set in application code. Reference SFTP programming samples for more information.

The MSDK includes an SFTP batch simulator for sandbox development and testing. When implementing the simulator, be sure to use these attributes and keys in place of those used for JPMC prod or VAR net connect batch systems. Use MSDK director and kit documentation for additional guidance.

[MUSIC PLAYING]