Search

Are you looking for test card numbers?

Would you like to contact support?

Default icon

Adyen Issuing

Learn how to build a card issuing platform using Adyen's Balance Platform.

Adyen Issuing is in the Early Adopter stage. All APIs, documentation, and processes are subject to change. If you want to learn more about Adyen Issuing, reach out to our Issuing team.

Adyen Issuing is a white-label, customizable issuing solution using our Balance Platform API.

With Adyen Issuing, you can:

  • Create fully customizable physical, virtual, and one-time use cards.
  • Provide your users with Visa and Mastercard debit cards.
  • Create transaction rules for advanced authorization logic.
  • Proxy authorization requests to your own servers so you can approve or refuse any authorization.
  • Use a single pool of funds for all card payments or maintain balances per card.

Adyen always operates in the background, allowing you to manage account creation, customize your own cards, and handle your funds. You will always be the point of contact for your users.

Core concepts and resources

The Balance Platform REST API contains a set of resources to handle accounting and payment processing for your users.

For each user and card you want to issue, you need to create:

  • An accountHolder: Your user's entity within the balance platofrm. All KYC information is stored here and KYC is performed against the account holder.
  • A balanceAccount: Account where funds are held for an account holder. All financial activity happens through balance accounts.
  • A paymentInstrument: The card itself, an externally-facing payment instrument for interacting with funds on the associated balance account. Creating a payment instrument issues a card.

You can additionally create:

  • transactionRules: Rules that are applied to automatically approve or deny authorization when a user attempts to pay with a payment instrument.

Dynamic balance account funding is specifying your liable balance account for other balance accounts to deduct from, allowing you to maintain a single balance for all your users.

You will also have a balanceAccount for your company called a liable balanceAccount. Your funds to load cards and perform balance transfers are within your liable balance account.

Each accountHolder can have one or more balanceAccounts for accounting flexibility but in most use cases, a single balance account is sufficient.

Each balanceAccount can have one or more paymentInstruments that can deduct from it.

Example account structures

Here are example account structures:

graph TD A[accountHolder] --> B[balanceAccount] B --> C[paymentInstrument] D[accountHolder] --> E[balanceAccount] D --> F[balanceAccount] E --> G[paymentInstrument] F --> H[paymentInstrument] F --> I[paymentInstrument]
  • On the left is a 1-1-1 relationship for an accountHolder, a balanceAccount, and a paymentInstrument.
  • On the right, the 1-N relationship are represented by the multiples of balanceAccounts and paymentInstruments for a single accountHolder.

Notifications

Many of the actions and events within the Balance Platform API are asynchronous. Some of these events include processing payments and performing KYC checks on an account holder. You need to rely on notification webhooks to receive these events.

An Issuing integration is incomplete without accepting and handling notifications.

Security and PCI Compliance

Some of our Balance Platform APIs can return raw card data. You need to be PCI level 1 or 2 compliant in order to use Adyen Issuing.

Future Balance Platform versions will return tokenized data, keeping you out of PCI scope. Let your Adyen contact know you are interested in this feature.

Next steps