Saferpay Test Accounts

Saferpay offers the possibility to test all interfaces in a specially for you created test account.

The Saferpay test account allows you to implement Saferpay into your system and make test transactions over several payment simulators before going live.

Please click here for your individual test account

On individual test accounts the https Interface is NOT available! We strictly recommend the usage of the Saferpay JSON API. If this should not be feasible, use the general test account for the https Interface!

Your are looking for the entry to the Saferpay test Backoffice?

Link to Saferpay test Backoffice

IMPORTANT: The Saferpay test account is separated from your Saferpay live account. Access details, log-in data etc. for the test account CANNOT be used on the live account and vice versa.

Please therefore ensure that you use the correct access data upon changing over from the test account to the live account.

By default, all Saferpay functions are activated on the test accounts, including Saferpay Business functions. Please note that the Business functions will no longer be available on your account later if you have not concluded a Saferpay Business contract.

Please consult the license matrix in the JSON API documentation in order to evaluate which functions are available with which license.

Usage of Saferpay JSON API with the Test Account

To ensure that the requests are sent to the test account, you are required to adjust the base URL for requests.

Base URL:

All other URL are derived from this base URL. For example:

Credentials for HTTP Basic Authentication can be created in the test Backoffice under "Settings > JSON API Basic Authentication"

JSON API Online Help

Do you require help during the integration?

You can now also view the Saferpay specification online. This includes a number of examples which you can use as well as a full parameter description for all interfaces from and to Saferpay.


Older API

If desired, older Saferpay interfaces can be tested either with the Saferpay Client Libraries for JAVA and .NET or the https Interface.

The general test account features all necessary functions.

Please note that older Saferpay interfaces will not be developed further. Thus it is STRONGLY recommended to choose the JSON API for a new implementation.

You can derive the ACCOUNTID from the above-specified data as follows:
CUSTOMERID-TERMINALID, i.e. 401860-17795278

Saferpay Client Libraries