Test Data

Ratepay recommends to use the following test data.

The advantage of using the test environment is that…

  • Test orders are immediately recognized as tests
  • No Ratepay fees are incurred and charged
  • No dunning processes are triggered
  • Alleged test buyers do not receive unwanted orders or even deliveries
  • The right contact person can be identified quickly and easily

attention

This test data can only be used on the test environment!

Data for testing Acceptance and Rejecting

Payment API 1.8

To provoke certain test cases, please always specify the <city> of Testhausen.

First name Last name Street contains Reason Code
* ABLEHNUNG * 703
* HAENDLERLIMIT * 701
* TECHERROR * 1000
* DOB * 2003
* RECHNUNGSADRESSE * 2100
* LIEFERADRESSE * 2101
* IBAN * 2111
* BANKDATEN * 2110
* * NICHT VERSENDEN 700
BUYER ABLEHNUNG * 730
PAYMENT ABLEHNUNG * 720
RISK ABLEHNUNG * 721

*: You can freely select a technically valid first name, last name or street.

Payment API 2.0

To provoke certain test cases, please specify the following email-address in the Authorization request.

Email Test case
buyer_identity@ratepay.com Decline: 422 - Buyer Identity
payment_attribute@ratepay.com Decline: 422 - Payment Attribute
risk_decision@ratepay.com Decline: 422 - Risk Decision
transaction_risk@ratepay.com Decline: 422 - Transaction Risk
otp_required@ratepay.com OTP flow: Documentation

Data for testing Direct Debit and Instalment via Direct Debit

Germany

Parameter Value
Bank Berliner Sparkasse
BIC BELADEBEXXX
BLZ 10050000
IBAN DE44100500001654698497
Account No. 1654698497

Austria

Parameter Value
Bank Commerzbank
BIC COBAATWXXXX
BLZ 19675
IBAN AT811967500100915806
Account No. 100915806

Netherlands

Parameter Value
Bank ABN AMRO Bank N.V.
BIC ABNANL2A
BLZ ABNA
IBAN NL18ABNA0484869868
Account No. 484869868

One Time Password

To invoke one time password (OTP) test cases, specify the email address otp_required@ratepay.com in the Authorization request. There are two testing approaches available:

  1. Use the fixed code "99999" to mock OTPs and bypass actual code delivery for quick testing.
  2. Test with real mobile phone numbers for end-to-end verification.

Include the special header X-2FA-Live with the value true for all API endpoints involved in the OTP flow (authorization endpoint, OTP verify, and OTP resend endpoints).