Search Overlay

API Keys

Please Note: As an ISV / Paysafe Partner, you will need to complete all of the below "merchant" steps on behalf of the Parent Merchant Legal Entity (PMLE) that your merchants will be operating under.

Before you begin, you need two distinct API keys for processing transactions to ensure security and fraud prevention.

  • API key to request single-use tokens: For payment requests, you need to retrieve single-use tokens from the Customer Vault. The single-use tokens are generated using this API key. When you create a test account, you get access to a web link that you can use to create the API key for single-use tokens. On a live system, to get the API key for single-use tokens, contact Customer Support to get enrolled for processing GooglePay transactions. Once your account set up is complete, you need to do this initial configuration in our merchant back office. This key is not the same as the key used for server-to-server API requests.
  • The API key for server-to-server API calls: Once a single-use token is retrieved – it is valid for one-time use only – it is sent to your server. You must then use the API key for server-to-server API calls to send requests from your server to the Card Payments API to process the transaction, which includes the single-use token as a parameter. To directly integrate with Paysafe REST APIs, refer to the section Integrating with Rest APIs.

You must register on our Developer Center to get your Test account and Test server-to-server API keys. The API key consists of two elements:

  • Key username
  • Key password

Combine the key username and key password into a string separated by a colon to create an API Key – i.e., "username:password”.

If you have already registered, you can find these Test credentials when you sign in to the Merchant Back Office, as shown below:

On this Page