Integrating Paysafe REST API
As an ISV or Paysafe partner, you must complete all merchant-related steps on behalf of the Parent Merchant Legal Entity (PMLE) under which your merchants will operate.
After you have successfully integrated with any of the following:
You can proceed to integrate with Paysafe’s Customer Vault and Card REST APIs to process Apple Pay transactions.
You will need both of your API keys: API key for single‑use tokens and API key for the Card API.
There are two main scenarios when working with Paysafe’s APIs for Apple Pay:
-
You pass the encrypted Apple Pay payment token to Paysafe. Paysafe decrypts the payload and extracts the DPAN for transaction processing. This article demonstrates how to integrate under this scenario.
-
If you have a special agreement with Apple that allows you to decrypt the payload. You decrypt the Apple Pay token and provide Paysafe with the raw clear‑text card data for processing. This article demonstrates how to integrate in the context of this scenario.
Regardless of the scenario, Paysafe returns the following card and authentication data:
Field | Description |
|---|---|
card.tokenType | Indicates the token type of the card. Possible values:
|
card.applePay.expiry{} | The expiry date of the tokenized card stored on the user’s Apple device. Do not show this expiry date in your user interface or you may get the user confused. |
card.applePay.lastDigits | The last four digits of the tokenized card stored on the user’s Apple device. Do not display this to avoid confusing users. |
card.applePay.subtype | The subtype of the tokenized card. Possible values:
|
card.type | The card brand (e.g., Visa, Mastercard). |
card.lastDigits | The last four digits of the real card number. This can be shown to the user. |
card.cardExpiry | Clarify that this is the token expiry, and should not be shown to users to avoid confusion. |
card.issuingCountry | The issuing country of the card. |
authentication.eci | Indicates whether the transaction may qualify for liability shift. |