Apple and Vantiv for Enterprise

Document created by gjsissons on Jul 12, 2016Last modified by gjsissons on Aug 9, 2016
Version 21Show Document
  • View in full screen mode

Solutions for Large Merchants

supermarket-grocery-store.jpg

 

Large merchants and Enterprise retailers often prefer direct integrations to Vantiv's core payment processing platforms. Integrations may be done by the merchant themselves, or by point of sale solution providers working with Vantiv and the merchant.

 

Integrations to Vantiv's core platforms involve working directly with our payments integration team to connect to our high-throughput ISO 8583 compliant payment interface or our 610 platform.

 

Merchant's integrated to Vantiv's IBM RAFT front-end can accept both in-App or in-Store payments via Apple Pay.  The in-App experience differs from the in-Store experience due to how the data is packaged. Apple Pay will first package both the EMVCo token and transaction cryptogram into a single 3D Secure (3DS) encrypted data element and return only the 3DS package (versus the individual data elements). This means that the 3DS package needs to be decrypted and parsed by the merchant before the transaction can be processed. Unlike the in-Store transaction, the in-App transaction always includes the full untruncated cryptogram. Apple Pay is facilitated by an extension to the ISO 8583 Authorization Request Message, subfield 126. Details are available in the manual Vantiv ISO 8583 specification - Network Tokenization (Apple Pay).

 

If you are already integrated to our core payment platforms, or are interested in adding support for Apple Pay mobile payments via direct integration with Vantiv, please contact us and we will connect you with an expert who is able to help. Depending on how you wish to support Apple Pay against Vantiv's core platforms, select one of the links below.

 

 

High-level Overview of the Integration Process

 

Merchant apps that support in-app Apple Pay with Vantiv's core platform will submit a PkPaymentRequest to Apple Pay’s PassKit interface and receive back a PkPaymentToken. Inside of the PkPaymentToken bundle is Payment Data as defined by Apple’s documentation – located at: https://developer.apple.com/library/prerelease/iOS/documentation/PassKit/Reference/PaymentTokenJ SON/PaymentTokenJSON.html

 

Having received the PkPaymentToken from Apple, the developer or merchant will need to initiate an In-App Authorization Request to the RAFT front-end following these steps:

 

  • Decrypt and parse the PkPaymentToken
  • Map the Payment Data elements to specific ISO8583 fields
  • Populate other ISO8583 fields with specific values that enable Vantiv to interpret the transaction as being an Apple Pay / e-commerce transaction

 

These steps are detailed in the Vantiv ISO 8583 Specification - Network Tokenization (ApplePay) documentation.

 


 

Additional information about Vantiv core platforms available in the Vantiv O.N.E. Enterprise space. Vantiv O.N.E. members can  access our Technical Guides and Resources for Enterprise Integrations

Attachments

    Outcomes