Processing Apple Pay Transactions
This section provides information about the different kinds of Apple Pay transactions
that you can submit:
- Authorizing a Payment UsingCybersourceDecryption or Merchant Decryption
- You can request the authorization service using these decryption methods:
- Cybersourcedecryption: Within this integration,Cybersourcefacilitates all of the encryption key generation and decryption processes associated with implementing Apple Pay. This method reduces the exposure of the sensitive payment data to your system.
- Merchant decryption: Within this integration, you manage all aspects of the Apple Pay integration, from generation of the payment encryption keys to decryption of the Apple Pay payload response. As a merchant, you submit the Apple Pay payment token and other payment information toCybersourcefor processing.
- Reversing an Authorization
- This service uses the request ID returned from the previous authorization. An authorization reversal releases the hold that the authorization placed on the customer’s credit card funds. Use this service to reverse an unnecessary or undesired authorization.
- Capturing a Payment
- This service uses the request ID returned from the previous authorization. The request ID links the capture to the authorization. Use this service to transfer funds from the customer’s account to your bank. The transaction typically completes in two to four days.
- Authorizing and Capturing a Payment
- A bundled authorization and capture is called asale. Request the authorization and capture services at the same time.Cybersourceprocesses the capture immediately.
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
.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Authorizations Using
Cybersource
Decryption for JCB
Cybersource
Decryption for JCB
This section provides the information you need in order to process an authorization using
Cybersource
decryption for JCB.
Authorizations Using
Cybersource
Decryption for mada
Cybersource
Decryption for mada
This section provides the information that you need in order to process an authorization using
Cybersource
decryption for mada debit cards and mada prepaid cards issued in the Kingdom of Saudi Arabia. Apple Pay transactions on these cards are supported on the mada Pay mobile app and for
Visa Platform Connect
only.
Authorizations Using
Cybersource
Decryption for Mastercard
Cybersource
Decryption for Mastercard
This section provides the information you need in order to process an authorization using
Cybersource
decryption for Mastercard.
Authorizations Using
Cybersource
Decryption for Visa
Cybersource
Decryption for Visa
This section provides the information you need in order to process an authorization using
Cybersource
decryption for Visa.
Authorizations Using Merchant Decryption for JCB
This section provides the information you need in order to process an authorization using merchant decryption for JCB.
Authorizations Using Merchant Decryption for mada
This section provides the information you need in order to process an authorization using merchant decryption for mada debit cards and mada prepaid cards issued in the Kingdom of Saudi Arabia. Apple Pay transactions on these cards are supported on the mada Pay mobile app and for
Visa Platform Connect
only.
Authorizations Using Merchant Decryption for Mastercard
This section provides the information you need in order to process an authorization using merchant decryption for Mastercard.
Authorizations Using Merchant Decryption for Visa
This section provides the information you need in order to process an authorization using merchant decryption for Visa.
Authorization Reversals
This section provides the information you need in order to process an authorization reversal.
Reversing an authorization releases the hold on the customer’s payment card funds that the issuing bank placed when processing the authorization.
Supported Card Types
All supported card types can process reversals. For a list of all supported card types, see Payment Processors.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/
{id}
/reversals
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments/
{id}
/reversals
The
is the transaction ID returned in the authorization response.
{id}
Captures
This section provides the information you need in order to capture an authorized transaction.
Supported Card Types
All supported card types can process captures. For a list of all supported card types, see Payment Processors.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}/captures
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}/captures
The
{id}
is the transaction ID returned in the authorization response.
Sales
This section provides the information you need in order to process a sale transactions.
A sale combines an authorization and a capture into a single transaction.
Supported Card Types
All supported card types can process sales. For a list of all supported card types, see Payment Processors.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments