Test data

Use the test data to test your integration for different payment methods.

Use the test data for checking your integration and payment workflows for different payment methods that you want to offer to your customers.

Overview

To make testing the Unzer API easier, you can use the following test data for each of the supported payment methods. You can test each use case before processing live payment information. You also need your test API keys for processing the test transactions.

Customer data

Never use real-time customer data for testing purposes. Use the following test accounts for your use cases.

For a full list of test card, go to the Test cards page.

Customer test data

Additional risk-check authentication

The following payment methods support the Authorize response with additional risk-check authentication flow, in which the customer must complete an extra verification step (SMS code verification) before the authorization can succeed:

• Unzer Invoice
• Unzer Installment
• Unzer Direct Debit

To test this flow, you must first contact Unzer to configure the risk engine to require additional verification. After testing is complete, contact Unzer again to remove this setting so that regular testing can continue.

In the sandbox, you can trigger this flow on demand by setting the customer’s email field to one of the test addresses below. When a matching email is used, the authorize response returns isPending: true together with a redirectUrl that will be used to guide the user through the verification challenge. For details on handling the response, see Authorize response with additional risk-check authentication.

When the flow includes an SMS code step, use the following test values on the additional verification page:

Use any other email to test the standard authorize flow without the additional risk-check step.

Alipay

Apple Pay

Apple Inc. offers a separate page with Apple Pay sandbox data. Note that we only support Mastercard and Visa credit cards for Apple Pay. Currently, cards from Discover and American Express are declined by our payment system. You must only use the credit cards that are available on the Apple Pay sandbox data.

EPS

The best way to test EPS is to create an empty EPS resource (without BIC) and execute a charge. After that, you’ll get a redirect link to the EPS bank selection page.

Please make sure that you select the following bank details:

You can also request test access for your bank by reaching out to your bank and entering an EPS online banking agreement.

You can also use this test data:

Google Pay

• Google provides the test data that you can use before you process transactions in the production environment.
• For a successful test transaction, note that the basket amount must be exactly 200 EUR.
• Go to the list of instructions and other criteria required for testing Google Pay in sandbox.

iDEAL

Klarna

Klarna runs its own risk and identity checks, so you test Klarna with Klarna’s per-market sample customer data rather than with a single Unzer test customer.

Testing prerequisites

• An Unzer test account with Klarna enabled for the market(s) you want to test. Klarna test merchants are provisioned per market, so if only one country works for you, your test account is enabled only for that market. Contact Unzer to have additional markets (for example, DE) enabled.
• Klarna’s sample customer data for the country you are testing: Klarna sample customer data.

Required fields

Klarna validates the request more strictly than most payment methods. Make sure the following are set, otherwise the authorization is rejected:

Country notes

• You can test any market that your Klarna test account is enabled for. Testing is not limited to a single country such as Finland.
• For Nordic markets, enter the national identification number from Klarna’s sample data to reach the intended approved or denied flow.
• Finland (FI) and Switzerland (CH) do not provide a Klarna test user-account login flow. Use the sample national identification number for these markets instead.

Klarna maintains the authoritative list of test customers and national identification numbers per country. Always use the current values from the Klarna sample customer data page.

PayPal

Create your own PayPal test account.

Przelewy24

Przelewy24 test credentials are pre-filled by default. When testing, click Pay.

Sofort

TWINT

You do not need any additional data for testing TWINT.

German test bank

Austrian test bank

PIN

When you are prompted to enter an account number and an online banking PIN, you can use the following options to force certain behaviors.

Enter one of the following keywords in the PIN field, and proceed:

Direct Bank Transfer

Direct Bank Transfer (Unzer Direktüberweisung) payments are completed by the customer on the online banking page of their own bank. In the sandbox environment, you are redirected to a bank selection screen where you choose a test bank, sign in with test credentials, and select the outcome that you want to simulate.

Testing prerequisites

• An Unzer test account with Direct Bank Transfer enabled.
• Your test API keys, for processing the test transaction.

Testing workflow

Follow these steps to test a Direct Bank Transfer payment:

Step 1: Initiate a Direct Bank Transfer payment from your test application using the Unzer sandbox API, then open the returned redirect URL.

Step 2: On the bank selection screen, make sure that Germany is selected as the country, and select Sepa Capability Redirect flow Test Bank. The test banks are listed at the end of the German bank list.

We recommend that you use one of the German Sepa Capability [type] Test Bank entries for your sandbox testing. Choose the entry that matches the flow you want to test: redirect, embedded, or decoupled.

Step 3: On the Connect to your bank screen, sign in to the simulated bank with the following test credentials.

If the test bank prompts you for a field that accepts digits only, enter 111111111111 (the digit 1, twelve times).

Step 4: On the Choose your account screen, select the test account that you want to pay from, then select Pay.

Step 5: On the TestBankConfigurePayment screen, select the outcome that you want to simulate, then select Continue. The outcome that you select determines the result that the bank reports back to Unzer, so you can test both successful and declined payments.

The available outcomes depend on the test bank that you select in Step 2. The outcomes listed above are the ones offered by Sepa Capability Redirect flow Test Bank.

To test a payment that the customer abandons, select the close icon (✕) instead, then select Cancel payment and confirm.

Step 6: You are redirected back to your return URL. Check the status of the payment through the Unzer API.

Testing refunds

To test a refund for a Direct Bank Transfer payment in the sandbox environment, use a payment amount below 100.00 EUR. Refunds for higher amounts are not processed in the sandbox.

SEPA Direct Debit

Invoice

WeChat Pay

Wero

To test Wero payments in the sandbox environment, you need to use the Wero consumer test portal to simulate customer approvals.

Testing prerequisites

• An Unzer test account with Wero enabled
• Access to the Wero consumer test portal: https://example-consumer-psps.werouat.eu

Testing workflow

Follow these steps to test a Wero payment:

Step 1: Initiate a Wero payment from your test application using the Unzer sandbox API.

Step 2: When redirected to the Wero payment page, select “TestBank” as your merchant bank.

Step 3: In the consumer portal, click on “Quick Tools” from the left sidebar.

Step 4: Navigate to “Local Profiles” to manage test consumer accounts.

Step 5: Either add a new consumer by clicking “Add Consumer” or select an existing test consumer profile.

Step 6: Select the consumer and click on “Give Consent”.

Step 7: Enter the consent code displayed in your payment flow to authorize the transaction.

Step 8: The payment will be processed, and you’ll be redirected back to your returnURL.