Search Overlay

Testing Instructions

Overview

The Paysafe Test environment can be used to test websites or applications without running transactions through the Production (live) processing platform. Payment transactions (e.g., credit card or Direct Debit) processed in the Test environment are not sent to the banking network, but through a simulator. Depending on the information provided with the transaction request, the simulator returns either a successful (approved) or failed (declined) response.

With the Paysafe API you can test the following:

  • Verify support for all the operation types that you require.
  • Review all common errors as well as errors that may occur for each operation, and ensure your application can handle them.
  • Verify the lengths and format for all attributes you send.

The Card Payments API also enables you to simulate specific responses by using special values for the amountcvv and street request parameters.

Applying for a Test Account

You can apply for a Test account by clicking the SIGN UP button.

Your Test account will provide you with access to a Test version of the Paysafe Merchant Back Office, where you can view the status of your Test transactions. Once logged in to the Back Office you should also retrieve your Account Number (choose Accounts and copy it from the Account column) and your API Key Username and Password (choose Settings > API Key); the password is also available Base64 encoded.

The default Test account can be used for processing Visa and Mastercard card payments (using the Card Payments, Customer Vault, Hosted Payments, and 3D Secure APIs). Special card numbers are available for testing these APIs and for use with Paysafe.js.

Do not use real card numbers or other payment instrument details in the Merchant Test environment. It is not compliant with Payment Card Industry Data Security Standards (PCI-DSS), and does not protect cardholder/payee information. Any upload of real cardholder data is strictly prohibited, as described in the Terms of Use.

You will need to open separate accounts for Direct Debit payments (one account for each Direct Debit method you want to support: SEPA, EFT, BACS, and ACH) and one account for each of the Alternate Payment methods supported by Paysafe that you want to use (e.g., SOFORT and BOKU). Also, if you want to test payments in a different supported currency then you will need additional accounts for each payment method/currency combination; for example, SEPA Direct Debit EUR, BACS Direct Debit GBP, Card Payments EUR, and Card Payments GBP. Contact Integration Support with your requirements and they will create the accounts for you.

Multiple accounts are summarized in the figure below.

All your accounts can be set up to use the same API key. Please contact Customer Support for more information.

Test API Endpoint

The API endpoint to use for Test transactions is:

https://api.test.paysafe.com

For example:

https://api.test.paysafe.com/customervault/v1/profiles

Test and Production Accounts

Test accounts enable you to process API transactions that mirror the functionality on the Production environment. Once you are satisfied with your integration to the Test environment, you will need to repeat any configuration changes made to your Test account on the Production account. Keep a record of any changes requested and carried out.

You will need to use different API endpoints and authentication credentials to connect to the Paysafe Production environment.

For details see Going Live.