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
This test data can only be used on the test environment!
Use any valid, syntactically correct buyer-, address- & transaction data in the Authorization request to get an acceptance on the test environment.
To provoke certain rejection & use cases, please specify the following email-address in the Authorization request.
| 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 |
| Parameter | Value |
|---|---|
| Bank | Berliner Sparkasse |
| BIC | BELADEBEXXX |
| BLZ | 10050000 |
| IBAN | DE44100500001654698497 |
| Account No. | 1654698497 |
| Parameter | Value |
|---|---|
| Bank | Commerzbank |
| BIC | COBAATWXXXX |
| BLZ | 19675 |
| IBAN | AT811967500100915806 |
| Account No. | 100915806 |
| Parameter | Value |
|---|---|
| Bank | ABN AMRO Bank N.V. |
| BIC | ABNANL2A |
| BLZ | ABNA |
| IBAN | NL18ABNA0484869868 |
| Account No. | 484869868 |
To invoke One Time Passcode (OTP) test cases, specify the email address otp_required@ratepay.com in the Authorization request. There are two testing approaches available:
Use the fixed code "99999" to mock OTPs and bypass actual code delivery for quick testing.
Test with real German mobile phone numbers for end-to-end verification.
- Include the special headerX-2FA-Livewith the valuetruefor all API endpoints involved in the OTP flow (authorizationendpoint, OTPverify, and OTPregenerateendpoints).