Revolv API and Apple Pay Token Processing
The Revolv API allows merchants to send an Apple Pay token directly to a Payment Service Provider (PSP) without modification. The decryption of the token is handled by the PSP. To enable this functionality, the merchant must provide a Payment Processing Certificate to the PSP (e.g., Nuvei). The PSP is actively involved in the generation of this certificate. If the merchant has already implemented the Apple Pay button, they should be familiar with the Payment Processing Certificate and its generation process, which Apple documents here.Prerequisites
To enable Apple Pay transactions through Revolv3, ensure the following steps are completed:- Obtain a Certificate Signing Request (CSR): Request a CSR file from your PSP (e.g., Nuvei). The PSP will provide this file to initiate the certificate generation process.
-
Generate a Payment Processing Certificate: Using the CSR file, generate a Payment Processing Certificate (
.cer
) through your Apple Developer account. Detailed instructions are available in Apple’s official documentation. -
Register the Certificate with Your PSP: Submit the generated
.cer
file to your PSP. They will register the certificate on their end, enabling them to decrypt Apple Pay tokens associated with your merchant profile. - Confirmation from PSP: Await confirmation from your PSP that the certificate has been successfully registered and your merchant account is configured to process Apple Pay transactions.
Revolv3 API – Apple Pay Token Parameter Description
Once the merchant obtains the Apple Pay token, it can be passed to the Revolv REST API as a payment method for processing. Example of original apple pay token (before being encoded) to put to Revolv3 Rest API:Using GooglePay