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 virtual and physical cards from Mastercard and Visa.
- 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 the following resources:
An accountHolder: A user's entity within the Balance Platform. All KYC information is stored here, and KYC is performed against the account holder. Depending on your account structure, the account holder can either be your company, or your customers.
A balanceAccount: Account where funds are held for an account holder. All financial activity happens through balance accounts. Each account holder can have one or more balance accounts for accounting flexibility, but in most use cases, a single balance account is sufficient.
- 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. Each balance account can have one or more payment instruments that can deduct funds from it.
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.
You will also have a balance account for your company called a liable balance account. This balance account will contain your funds for loading cards and performing balance transfers.
If you want to maintain a single balance for all your users, you can also configure your users' balance accounts to deduct funds directly from your liable balance account. This is called dynamic balance account funding.
Example account structures
- Example 1: 1-1-1 relationship for an accountHolder, a balanceAccount, and a paymentInstrument.
- Example 2: the 1-N relationship are represented by the multiples of balanceAccounts and paymentInstruments for a single accountHolder.
Many of the actions and events within the Balance Platform API are asynchronous. These events include payments, captures, and refunds. You need to rely on notification webhooks to receive these events.
An Issuing integration is incomplete without accepting and handling notifications.
The scope for PCI compliance depends on your use case—the type of cards you'll issue and how the cards will be used. To know more if PCI compliance requirements apply to your use case, reach out to your Adyen contact.