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.