# Test Data (Payment API 2.0)

div
div
⏱ 3 min
div
👤 Merchant Onboarding Team (Marcel K.)
###### 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


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

## Data for testing Acceptance and Rejection

### Acceptance

Use any valid, syntactically correct buyer-, address- & transaction data in the [Authorization request](/apis/payment/openapi/payment_api/transaction-management/createtransaction) to get an acceptance on the test environment.

### Rejection

To provoke certain rejection & use cases, please specify the following email-address in the [Authorization request](/apis/payment/openapi/payment_api/transaction-management/createtransaction).

| Email | Test case |
|  --- | --- |
| buyer_identity@ratepay.com | Decline: [422 - Buyer Identity](/docs/developer/api_integration/payment_2.0/declines/422_buyer_identity/) |
| payment_attribute@ratepay.com | Decline: [422 - Payment Attribute](/docs/developer/api_integration/payment_2.0/declines/422_payment_attribute/) |
| risk_decision@ratepay.com | Decline: [422 - Risk Decision](/docs/developer/api_integration/payment_2.0/declines/422_risk_decision/) |
| transaction_risk@ratepay.com | Decline: [422 - Transaction Risk](/docs/developer/api_integration/payment_2.0/declines/422_transaction_risk/) |
| otp_required@ratepay.com | OTP flow: [Documentation](/docs/developer/otp/introduction/) |


## 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 Passcode

To invoke [One Time Passcode (OTP)](/docs/developer/otp/introduction/) test cases, specify the email address **otp_required@ratepay.com** in the [Authorization request](/apis/payment/openapi/payment_api/transaction-management/createtransaction).
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 German 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 `regenerate` endpoints).