Availability of certain integration methods depend on merchant’s domicile. Click here for details.
 

Payeezy.js

User Action: Buyer does a checkout on the merchant hosted site by clicking on buy/submit button
 
  1. Payeezy.js which is included on the page using a <script> tag intercepts the form upon submit, and then asynchronously posts the credit card details directly to Payeezy bypassing the merchant server. This call uses JSONP over https, passing in API key and an identifier.
  2. Payeezy returns a token associated with the credit card.
  3. Payeezy.js submits the form with the hidden credit card token along with other form details to the merchant’s server.
  4. Merchant’s server makes an API call and submits the token to Payeezy to complete the transaction using the server side library (Direct API) of your choice. This API call uses HMAC authentication over https. Refer to API docs section for more information on this.
  5. Payeezy completes the transaction (such as authorize, purchase) with the provided token and sends back a new token to be used for any related secondary transaction (such as capture, void, refund). Success/failure message is handled accordingly by the merchants server.

Direct API

User Action: Buyer does a checkout on the merchant hosted site by clicking on buy/submit button. This needs to be a secure page.

  1. Upon Submit the form gets posted to the Merchant server.
  2. Merchant’s backend server invokes the Payeezy API over a SSL connection and submits the order information securely. The call requires providing an authorization header with a HMAC hash. Refer to API docs section for more information on this.
  3. Payeezy process the transactions (such as authorize, purchase) with the provided transaction details and sends back the response.
  4. Success/failure message needs to be handled accordingly by the merchants server.

NOTE: The merchant/third party is responsible for PCI compliance and may be required to provide First Data with additional documentation and/or their attestation of compliance

Apple Image Logo

Apple Pay®

User Action: Buyer taps the Pay button in the App and selects the payment card and uses the Touch-ID to complete the transaction.

  1. The Merchant App communicates with merchant server and creates a transaction ID
  2. The Merchant App obtains the encrypted transaction payload (The tokenized card data "DPAN", Cryptogram, and transaction details) from Apple's Pass Kit Framework
  3. The Merchant App sends the encrypted transaction payload to Payeezy usig the Payeezy SDK
  4. Payeezy decrypts the encrypted transaction payload and processes the transaction
  5. Payeezy responds back to the Merchant App (Through the SDK) with either an approval or declination
  6. If provided, Payeezy sends out a transaction receipt to the merchant URL (Via a Webhook)
Google Pay Image Logo

User Action: Buyer taps "Google Pay" button, and then selects payment method and shipping address.

If the purchase originates from a third-party site

  1. The merchant/client server issues a credential request with the Merchant ID and Processor Name as First Data to Google.
  2. Google returns response with encrypted payment credentials signed with the First Data key to the merchant server.
  3. The Merchant sends the encrypted payload to First Data.
  4. First Data decrypts and validates the payload, and then processes the transaction and responds back to merchant with either an approval or decline response.

If the purchase originates from a Google site:

  1. Google initiates a purchase request to the merchant after the consumer confirms order.
  2. The merchant/client server issues a request with the Merchant ID and Processor Name as First Data to Google.
  3. Google returns response with encrypted payment credentials signed with the First Data key to merchant server.
  4. The merchant sends the encrypted payload to First Data.
  5. First Data decrypts and validates the payload and process the transaction and respond back to merchant with either an approval or decline response.

iOS

Build Apps and accept credit cards in the App. The iOS mobile SDK requires iOS SDK 6 and XCode 5.1+ It supports our Direct API.

Batch Processing

User Action:Merchant sends Recurring transactions to First Data File Gateway in batch format.

  1. The merchant creates a batch file of recurring transactions. See the Recurring Batch Solution Implementation Guide for formats and requirements.
  2. The merchant uploads the batch file to First Data File Gateway.
  3. The Batch server retrieves the file from the First Data File Gateway, processes the transactions from the batch file, and receives a response for each transaction in the batch file.
  4. First Data compiles the responses into the appropriate response batch file format and places it on the First Data File Gateway for the merchant.
  5. The merchant retrieves the response batch file from First Data File Gateway.

Android

Build Apps and accept credit cards in the App. The Android SDK requires Android 4.0 and above with JDK 6+. It supports our Direct API.

ACH Web

Build Apps, tokenize ACH, and accept token-based ACH payments using Payeezy Java SDK.
Web Example shows how to do that using Java 8, Spring Boot 1.4.1, and XmlHttpRequest.
Modern browser supporting XmlHttpRequest (IE 10+, Firefox 41+, Chrome 44+) is required.

To get field-level data definitions and descriptions of the business logic, please register on the First Data Spec Portal. To register: Complete the registration process at https://specs.firstdata.com/kb/register/
Next, login into the portal: https://specs.firstdata.com/kb/login/
Click on the following links. First Data Merchant Services -> TeleCheck
Download the ConnectPay Specification and ConnectPay Product Guide. Scroll down and accept the NDA terms.

Hosted Payment Page

Hosted Payment Page is a securely hosted web payment form designed to accept Internet-based E-commerce transactions. With Hosted Payment Page in place, you are no longer exposed to the sensitive cardholder details required to process a payment. Additionally, you have access to an expanding toolkit of payment options and fraud prevention tools without the need for additional development.

User Action: Buyer clicks the Buy button from your online store which then redirects the buyer to a secure payment form which is customized by you and hosted by First Data. Buyer enters payment information and completes the transaction. Buyer is redirected to the merchant website where the order confirmation is displayed.