Test Data

Swedbank Pay Checkout Test Data

During a Swedbank Pay Checkout implementation, you can use the test data related to the different payment instruments listed below. To see Swedbank Pay Checkout in action, please visit the Playground.

To test a checked-in user in the Playground, please use the following test data:

Checkout test data for Norway

Checkout test data for Sweden

Checkout test data for Denmark

Credit Card Test Data

With regards to card payments, our external integration test environment is connected to our POS system instead of a fake service. It is set up with an internal acquirer. This gives us a production-like test environment, while also giving us sandbox testing opportunities, such as 3-D Secure card enrollment and error scenarios. No payment information will be sent to other acquiring institutions.

3-D Secure Cards

3-D Secure 2

For merchants using 3DS2, OTP (One-Time Password) is the ACS (Access Control Server) you will encounter. Use the Visa or MasterCard listed under 3-D Secure Cards above when doing a card payment. Click approved or cancel to select authentication status.

Network Tokenization

When testing Network Tokenization you can use one of the cards listed below, depending on if you want to use MasterCard or Visa, and if you want a frictionless flow or a challenge flow. These cards are test FPANs (Funding PAN, an actual card number). Make sure that your merchant contract is configured towards our internal acquirer (loopback), since they won’t work as intended if you are configured towards other acquirers.

Each FPAN is connected to a DPAN (Network Token). The DPAN will not appear in the initial transaction response. It will only be displayed when you run the next transaction with the stored token.

Once your card has been enrolled, you will enter into a rotation where the DPAN is updated with a new FPAN every 24h. This way you can notice the changes easily. The rotation consists of 10 cards and will run indefinitely, but the initial FPAN won’t appear again, as it is not a part of the DPANs set of cards. The four FPANs can be used again every day to store a card and initiate a fresh rotation.

Note that in the response, the 6 first digits of the PAN will be shown in the BIN field. The maskedPan will only contain the last 4 digits.

Error testing can be performed using the four bottom cards. They will all be rejected during tokenization.

If you want to test Network Tokenization without card updates, simply use one of our other MasterCard or Visa test cards. You still need to be configured against our internal acquirer (loopback).

Visa

MasterCard

American Express

JCB

Diners

Maestro

Dankort

Visa/DanKort

Forbrugsforeningen

Failure Testing Cards

There are two different ways of testing Card Payments error scenarios. You can test 3-D Secure errors using our 3-D Secure emulator, or you can use specific amounts set to trigger errors in our test environment.

Magic Amounts (Error Testing Using Amounts)

We have some preset amounts that will trigger error codes. While creating a payment (operation purchase), enter one of the amounts from the list below in the prices object ("amount": <number>) before submitting a payment. The error message displayed behind the amounts will be sent with your payment in the test environment.

The amounts that can be used to trigger error codes (transactionThirdPartyError):

The DAILYLIMITEXCEEDED must be performed 10 times to be triggered, and the MONTHLYLIMITEXCEEDED has to be performed 15 times to be triggered. The SuspensionWarning response message appears when the two limit exceeds have 5 attempts left (i.e. after 5 daily or 10 monthly attempts).

Invoice Test Data

Invoice test data for Norway

Invoice test data for Sweden

Invoice test data for Finland

Invoice Service Test Data

Use any name, address etc.

Swish Test Data

Testing a successful Swish purchase (in our external integration test environment) can be done by using any valid Swedish mobile number. E.g: +46 739000001. As with Vipps, the external integration test environment uses a fake service with no app involved. To trigger an error message, set the description value in POST Create Payment or Create Payment Order to one of the following values: