API Overview

Recent Revisions to This Document

About This Guide

Introduction to Apple Pay
- Requirements for Using Apple Pay
- Supported Card Types and Optional Features
- Apple Pay Integrations and Payload Decryption Methods
  - Flow of Apple Pay In-App Transactions Processed Using Cybersource Decryption
  - Flow of Apple Pay In-App Transactions Processed Using Merchant Decryption
  - Flow of Apple Pay Web Transactions Using Cybersource Decryption
  - Flow of Apple Pay Web Transactions Using Merchant Decryption

Configuring Apple Pay Processing
- Generating and Loading a New Certificate Signing Request
- Configuring Apple Pay Response Handling

Processing Apple Pay Transactions
- Authorization Service
- Authorizations Using Cybersource Decryption for Mastercard
  - Required Fields for Authorizing a Payment Using Cybersource Decryption for Mastercard
  - Example: Cybersource Decryption and Mastercard
- Authorizations Using Cybersource Decryption for Visa
  - Required Fields for Authorizing a Payment Using Cybersource Decryption for Visa
  - REST Example: Cybersource Decryption for Visa
- Authorizations Using Merchant Decryption for Mastercard
  - Required Fields for Authorizing a Payment Using Merchant Decryption for Mastercard
  - REST Example: Merchant Decryption and Mastercard
- Authorizations Using Merchant Decryption for Visa
  - Required Fields for Authorizing a Payment Using Merchant Decryption for Visa
  - REST Example: Merchant Decryption and Visa
- Authorization Reversals
  - Required Fields for Processing an Authorization Reversal
  - REST Example: Processing an Authorization Reversal
- Captures
  - Required Fields for Capturing an Authorization
  - REST Example: Capturing an Authorization
- Sale
  - Required Fields for Processing a Sale
  - REST Example: Processing a Sale

Searching for Apple Pay Transactions

On This Page

Authorization Service

This section provides the information that you need for requesting the authorization service using these methods which determine the request fields that are required to request the authorization service. In addition, different request fields are required in order to request the authorization service. The type of card used to process the transaction determines which request fields are used.

After you send the request, verify the response messages to make sure that the request was successful.

A 200-level HTTP response code indicates success.

For information about response codes, see

Transaction Response Codes

.

IMPORTANT

Worldpay VAP supports 3-D Secure 2.0 with Mastercard transactions. Worldpay VAP also supports network tokens and digital payments with Mastercard transactions. However, Worldpay VAP does not support the 3-D Secure 2.0 protocol if used with network tokens or digital payment. Cybersource declines any transaction processed by Worldpay VAP that uses both 3-D Secure 2.0 and either network tokens or digital payments.

Endpoint

Production:

POST https://api.cybersource.com/pts/v2/payments

Test:

POST https://apitest.cybersource.com/pts/v2/payments

Back to top