Here you will find the test data both for the so-called giropay OLD (the previous giropay way via your online banking), as well as giropay NEW (the formerly used way of Paydirekt requiring a user name and a password).
Which of the two ways (OLD and/or NEW) will be available to you when testing, depends on your contract. Please contact your sales representative should you not be presented with the expected variant. Please also bear in mind that you may be presented with either of the two variants iniaitally, depending on what might be stored in your browser from previous selections. So you may return to the selection of the NEW or OLD variant by using the left arrows available in the giropay user interface (please don't confuse with the browser back button!).
Please use the login data provided below (please do not change the password within the interface as it is shared with other testers, and also remember that your test transactions will be visible to other people using the same account):
| Form field | Input value |
|---|---|
| Username | Giropay_test |
| Password | 8x5hHDs+98Q2W |
| TAN (should one be requested at some point) | 123456 |
Please make sure to only use the following giropay test bank for your tests!
| Form field | Input value |
|---|---|
| Bank | giropay Testbank |
| IBAN | DE48499999601234567890 |
| VR-NetKey / Alias | (any value) |
| PIN | 1234 |
| TAN‑Verfahren auswählen (only for amounts >= 20,00, see below) | “Smart-TAN plus optisch / USB” or “Smart-TAN photo” |
| TAN | 123456 |
Special amounts
The behaviour of the transaction may be controlled through the checkout sum (magic numbers), see the table below. For the integration of giropay in a shop o an authority office, the main takeaway of this list is that the amounts specified in the table below trigger a special behaviour of the simulation and therefore might produce unexpected results when not taken into account.
| Amount | Reaction |
|---|---|
| 2,00 EUR | For PSD2 payments, the payment is immediately rejected by the PSD2 Bank with the status REJECTED. |
| 20,00 EUR | Up to this amount, no TAN authentication is expected; for exactly 20 euros, the selection of TAN procedures is also displayed (without having to enter a TAN) |
| 20,02 EUR | For PSD2 payments with TAN authentication, the photo TAN procedure as well as two unsupported TAN procedures are used. For the user, this Magic Number should behave in the same way as €21.00. When selecting the TAN procedure, it is then specified that no TAN entry is necessary (EXEMPTED) |
| 21,00 EUR | For PSD2 payments with TAN authentication, only Photo-TAN procedures are used |
| 21,01 EUR | For PSD2 payments with TAN authentication, the photo TAN procedure as well as two unsupported TAN procedures are used. For the user, this Magic Number should behave in the same way as €21.00. |
| 22,00 EUR | For PSD2 payments with TAN authentication, only push TAN procedures are used |
| 22,01 EUR | For PSD2 payments with TAN authentication, the push TAN procedure and two unsupported TAN procedures are used. For the user, this Magic Number should behave in the same way as €22.00. |
| 23,00 EUR | For PSD2 payments with TAN authentication, only Flicker TAN procedures are used |
| 23,01 EUR | For PSD2 payments with TAN authentication, the Flicker TAN procedure and two unsupported TAN procedures are used. For the user, this Magic Number should behave in the same way as €23.00. |
| 23,45 EUR | With PSD2 payment with TAN authentication, there will be no automatic status change for push, photo and flicker TAN. The SCA status and the transaction status must be set manually in the test portal via paymentId. |
| 403,01 EUR | When starting a PSD2 TAN authentication at a Volksbank, simulates a 403 (forbidden) with the reason SERVICE_BLOCKED as the answer. |
| 403,03 EUR | Simulates a 403 (forbidden) with the reason EXPIRED as the answer to a PSD2 status query at a Volksbank. |
| 403,04 EUR | When sending a PSD2 TAN to a Volksbank, simulates a 403 (forbidden) with the reason SERVICE_BLOCKED as the answer. |
| 403,05 EUR | When selecting a PSD2-TAN authentication method at a Volksbank, simulates a 403 (forbidden) with the reason SERVICE_BLOCKED as the answer. |
| 403,13 EUR | Simulates a 403 (forbidden) with the reason BLOCKED as the answer to a PSD2 status query at a Volksbank. |
| 405,02 EUR | Simulates a 405 (method not allowed) as a response when deleting PSD2. |
| 408,04 EUR | Simulates a long response time (for a timeout) with PSD2 TAN authentication. |
| 422,00 EUR | Simulates a 422 (not processable) as a response to a PSD2 payment. |
| 422,01 EUR | Simulates a 422 (not processable) as a response for PSD2 authentication. |
| 503,00 EUR | Simulates a 503 (not available) as a response for a PSD2 payment. |
| 503,01 EUR | Simulates a 503 (not available) as a response for PSD2 authentication. |
| field | value |
|---|---|
| BIC | HYPTAT22XXX |
| Verfügernummer/-name und PIN | no input needed, click Login |
| mobile TAN | any or empty |
transaction result
| result code | answer | description |
|---|---|---|
| 4000 | successful transaction | After submission of the form by using the data above you create a successful transaction. |
| 4900 | unsuccessful transaction | After clicking the button Zahlung abbrechen you create an unsuccessful transaction. |
3-D Secure 2.0
Since 3-D Secure 2.0, please use the following 3DS2 enabled cards.
| Case | Card number |
|---|---|
| Without card holder authorisation | 4012001037167778 |
| With card holder authorisation | 4012001037664444 |
| With 3DS Method | 4005559876540 |
| With 3DS Method and card holder authorisation | 4012001036853337 |
Card holder: Any
Card verification code (CVC2/CVV): any 3-digit number (is not validated)
Expiration date: any future date
When asked for address data in the credit card form, any data may be entered into all fields. This data is not validated in test mode.
Transaction results
| Result code | Answer | Description |
|---|---|---|
| 4000 | Successful transaction | After entering the above data and considering the following information, the transaction is successful: Integer amount between 1,00 and 99,00 |
| 4502 | Aborted transaction | After clicking the button cancel you create an aborted transaction. |
| Bank account | Bank code | Response code | Result type | Description |
|---|---|---|---|---|
| 1234567890 | 12345678 | 4000 | successful transaction | A successful payment will be created. |
| 1212121211 | 12345679 | 4051 | unsuccessful transaction | An unsuccessful payment will be created. |
| IBAN | Response code | Result type | Description |
|---|---|---|---|
| DE87123456781234567890 | 4000 | Successful transaction | A successful payment will be created. |
| DE23690516200012345600 | 5027 | Unsuccessful transaction | An unsuccessful transaction will be created. |
| Form field | Input value |
|---|---|
| Card number | 6799990100000000019 |
| Expiration date | any valid future date |
| Card verification code (CVC2/CVV) | any number of 3 or 4 digits (is not validated) |
Please note that Maestro transactions in test mode can only be successful for full amounts without cents. Amounts with cents (such as 19,80 EUR) will always be declined.
| form | value |
|---|---|
| issuer | RABOBANK |
transaction result
| result code | answer | description |
|---|---|---|
| 4000 | successful transaction | After submission of the form by using the data above there can be created a successful transaction. |
| unsuccessful transaction | not supported |
| Form field | Input value |
|---|---|
| BLZ | 88888888 |
| BIC | SFRTDE20XXX |
| Login | (any) |
| Passwort | (any) |
| Konto | (select from list) |
| TAN | (any) |
For testing purpose there runs a PayPal simulation page. After initialisation of a PayPal payment the buyer is redirected to a simulation page. There can be chosen if the transaction should be finished successfully or unsuccessfully.
Transaktionsausgang
| result code | answer type | description |
|---|---|---|
| 4000 | successful transaction | The payment result can be chosen in the simulation page. |
| 4900 | unsuccessful transaction | The payment result can be chosen in the simulation page. |
In order to test Bluecode e-commerce payments, you require a smart phone with an installed and activate Bluecode app.
We recommend that you call the following URLs directly on your smart phone:
iOS: https://install.appcenter.ms/orgs/bluecode-organization/apps/at.secure-shopping.bluecode.sandbox-ios/distribution_groups/public
Android: https://install.appcenter.ms/orgs/bluecode-organization/apps/com.spt.bluecode.sandbox-android/distribution_groups/public
Important:
Special note on iOS:
When first installing the sandbox app on iOS devices, it is necessary to establish trust for the business app “bluesource”. Do this by going to “Settings > General > Profiles & Devices” and confirming that you trust this app. Only then the Bluecode app may be used on iOS.
No “real” payments are processed in the Bluecode sandbox app, they are only simulated!