The developer.datatrans.com Developer Hub

Welcome to the developer.datatrans.com developer hub. You'll find comprehensive guides and documentation to help you start working with developer.datatrans.com as quickly as possible, as well as support if you get stuck. Let's jump right in!

Testing Credentials

Use this page to find testing credentials for specific payment methods. The testing credentials below are only supported in our sandbox environment. For tests in production, you will require to proceed with real payments if you wish to test it.

Missing testing credentials? Contact us!

Get in touch with us today and we'll make sure to advise you accordingly. Send us a message anytime by using this link.

Credit & Debit Cards

To test payments with a credit or debit card, you may use one of the test cards listed below. Make sure to use a card stating a limit and an amount within the ranges described below to test decline scenarios. For any card listed below, you may use the expiry date 06/25. If you own test credentials with an older expiry date, you may simply update the month and year to the new expiry date.

Depending on the amount and if a limit is set on a specific card, the following 4 rules are applied:

  • amount=0 to amount=9000: Transaction is authorized.
  • amount=9000 to amount=10000: Transaction is declined. This simulates a case where the card has reached its limit or the expiry date is wrong.
  • amount=10000 to amount=11000: Transaction is in a referral state.
  • amount=11000 or higher: Transaction is declined. The card was reported lost or stolen.

For 3D Secure 2 tests, you may use the dedicated cards with 3D v2 listed below. You can test 4 scenarios depending on which card you use:

  • ¹ Challenge authenticated
  • ² Challenge declined
  • ³ Frictionless authenticated
  • ⁴ Frictionless declined

Use the OTP 4000 to successfully authenticate a challenge flow and 4009 to simulate an unsuccessful authentication within the challenge flow.

Name
Card number
CVV
Limit
3D Secure

Mastercard

5200 0000 0000 0007
5100 0000 0000 0016
5404 0000 0000 0001
5100 0010 0000 0022
5100 0010 0000 0014
5100 0010 0000 0030

123
123
123
123
123
123

No
No
Yes
No
No
No

No
3D v1
3D v1
3D v2 ¹ ²
3D v2 ³
3D v2

Mastercard Debit

5500 0000 0000 0004

123

No

No

Visa

4900 0000 0000 0094
4242 4242 4242 4242
4900 0000 0000 0003
4000 0010 0000 0042
4000 0010 0000 0018
4000 0010 0000 0034

123
123
123
123
123
123

No
Yes
No
No
No
No

No
No
3D v1
3D v2 ¹ ²
3D v2 ³
3D v2

Visa Debit

4444 0901 0101 0103

123

No

No

American Express

3758 111111 11123
3758 111111 11115
3750 000000 00007
3400 00100 000024
3400 00100 000016
3400 00100 000032

1234
1234
1234
1234
1234
1234

No
Yes
No
No
No
No

No
No
3D v1
3D v2 ¹ ²
3D v2 ³
3D v2

Unionpay

6223 1649 9123 0014
8100 0000 0000 0002

None
None

No
No

No
3D v1

Diners

3616 800258 6009
3616 771911 0012
3600 001000 0014
3600 001000 0006
3600 001000 0030

123
123
123
123
123

Yes
No
No
No
No

No
3D v1
3D v2 ¹ ²
3D v2 ³
3D v2

Discover

6011 4200 0000 0004

123

No

No

JCB

3569 9900 1003 0400
3569 9900 1003 0442

123
123

No
Yes

No
No

Maestro

6759 0000 0000 0018
6759 0000 0000 0026

123
123

No
Yes

3D v1
3D v1

Dankort

5019 9940 0012 4034

747

No

No

Loyalty & Gift Cards

The rules from card payments apply to loyalty & gift cards. Please refer to the section credit & debit cards for more details.

Name
Card number
CVV
Limit

UATP

1920 72420 096379

None

No

Boncard

6299 1200 0003 4200

038

Yes - 250 CHF daily

Lunch-Check

6375 9400 1000 1072

123

Yes - 250 CHF daily

Amazon Pay

Please log in to your Amazon Pay account to simulate a transaction.

Apple Pay

Add a real card to your Apple Pay wallet. Confirm the transaction using your newly registered card. Instead of using your real card, we will replace the card number to 4242 4242 4242 4242 and the expiry date to 12/21.

Availabill

Please contact Availabill for test information.

Byjuno

Please contact Byjuno for test information.

CRIF

Please contact CRIF for test information.

Cryptocurrencies

Coinify provides a sandbox platform to test crypto payments. Please bear in mind that you will have to send additional account credentials to us in order to let you process test payments via Coinify. You can sign up for your sandbox merchant account here.

To proceed with a test payment, you can use the following setup:

  • Install a testnet wallet on your smartphone. You ca use the test wallet Testnet Wallet if you need one.
  • Add funds to your wallet by using a Testnet faucet.

Easypay

Please contact Swisscom for test information.

EPS

Select Stuzza Bank (STZZATWWXXX) as your bank. On the login screen use the following credentials:

  • Username: 1004399
  • Password: Ve7yQ8EDBb56moAL

Google Pay

Register for Google Pay on your device and add a real card supporting Google Pay. Confirm the transaction using your newly registered card. Authorizations with real cards will be declined in our test environment. If a valid Google Pay token is identified, we send the following replacements:

  • cardno=4242 4242 4242 4242
  • expirydate=12/21

Giropay

For Giropay, you can simply click yourself through the payment forms without entering anything. Simply click the login button and you should be able to proceed.

iDeal

iDeal does currently not offer any way to test their platform.

Klarna

Please contact Klarna for test information.

Migros Bank E-Pay

For Migros Bank E-Pay, please use the following credentials:

  • E-Pay ID: epaysuccess1

PayPal

Register for a developer's account at PayPal. Once you have registered, you should receive details to your test buyer account. The buyer account can be used to test PayPal payments in our sandbox environment.

Paysafecard

For Paysafecard, please use the following credentials:

  • PIN: 7740228278243675

Please note that this PIN is only valid for EUR or CHF transactions.

PostFinance

For PostFinance Card and PostFinance E-Finance through our Redirect or Lightbox integration, you can simply click yourself through the payment forms without entering anything. Simply click the next button until you reach your success page. If you are using our Mobile SDK integration, depending on the SDK version installed, you will only have the option to test PostFinance with productive transactions.

Powerpay

Please contact MF Group for test information.

Reka

Please contact Reka for test information.

Samsung Pay

Register for Samsung Pay on your Samsung device and add a real card supporting Samsung Pay. Confirm the transaction using your newly registered card. Authorizations with real cards will be declined in our test environment. If a valid Samsung Pay token is identified, we send the following replacements:

  • cardno=4242 4242 4242 4242
  • expirydate=12/21

SEPA (ELV)

For SEPA (ELV), please use the following credentials:

  • IBAN: DE85123456781234512345

Sofort

For Sofort, you can simply click yourself through the payment forms by entering dummy information with the required minimum length for each field (usually 4 or 5 digits).

Swissbilling

Please contact Swissbilling for test information.

SwissPass

For SwissPass, please use the following credentials:

  • SwissPass card number: S48681516807
  • ZIP-Code 3000
  • Phone number +41781234567
  • E-mail: any e-mail address
  • Code: 1111

Twint

To test Twint payments, you will need to download a test app and go through the registration process again using a Swiss mobile phone number. Productive Twint apps will not allow you to test Twint payments. You can open the following links to download the so-called 'TWINT Configurator' and finally the test application:

Please select the PAT environment for your Twint tests via Datatrans. To top up your test account you will require voucher codes. You may contact us to receive your test vouchers for Twint. For some payment flows to work, you may have to complete an account verification at Twint and contact their support to fully activate your Twint account.

Updated 8 days ago

Testing Credentials


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.