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!

Tokenization

Save your loyal customers’ payment information securely and PCI-compliant in the background as a token to make repeat purchases or one-click checkouts easily. Check the section saving payment information in our docs to see how this process works.

Activation required

By default, the tokenization service is not active in your merchant configuration. Please contact us to activate the tokenization option for your account.

Except for credit & debit cards and loyalty & gift cards, you will be required to contact your acquirer or payment method provider to activate an additional option for your account. If the required option is not active on the acquiring level, an error will be returned if you try to create a token.

Token Format

All our tokens created after a payment or a dedicated registration are unique. All payment methods share a common token format:

AAABcH0Bq92s3kgAESIAAbGj5NIsAHWC
  • Possible characters: A-Z, a-z, 0-9, -, _
  • Length: 32 characters

Payment Methods Support

The following table shows the payment methods supporting tokenization. It also shows you if a payment method supports registration only or payment and registration at the same time.

Payment method
Registration Only
Payment + Registration

Credit and Debit Cards

:heavy-check-mark+:

:heavy-check-mark+:

Loyalty & Gift Cards

:heavy-check-mark+:

:heavy-check-mark+:

Apple Pay ¹

:heavy-check-mark+:

:heavy-check-mark+:

Byjuno ²

:heavy-check-mark+:

:x+:

EasyPay

:heavy-check-mark+:

:heavy-check-mark+:

Google Pay ¹

:heavy-check-mark+:

:heavy-check-mark+:

Klarna

:heavy-check-mark+:

:heavy-check-mark+:

Migros Bank E-Pay

:x+:

:heavy-check-mark+:

PayPal

:heavy-check-mark+:

:heavy-check-mark+:

PostFinance Card

:heavy-check-mark+:

:heavy-check-mark+:

PowerPay

:heavy-check-mark+:

:heavy-check-mark+:

Reka

:heavy-check-mark+:

:heavy-check-mark+:

Samsung Pay ¹

:heavy-check-mark+:

:heavy-check-mark+:

SEPA (ELV)

:heavy-check-mark+:

:heavy-check-mark+:

SwissPass

:heavy-check-mark+:

:heavy-check-mark+:

TWINT

:heavy-check-mark+:

:x+:

¹ Apple Pay, Google Pay, and Samsung Pay transactions are processed as card transactions. In other words: The saved cards in your customer's Apple Pay, Google Pay, or Samsung Pay wallets are processed by your configured debit or credit card acquirers.
² For Byjuno registrations you will need to provide additional parameters within your init requests in the objects customer and INT. The required parameters may vary from merchant to merchant. Please double-check with Byjuno which information will be required for your contract. No additional parameters are required in your requests to debit Byjuno tokens. For payments with Byjuno tokens you may send optional parameters within customData located in the object INT.

Updated 2 months ago

Tokenization


Suggested Edits are limited on API Reference Pages

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