Instant card funding

Instant card funding lets you process transactions for a shopper moving money from a card to another card, digital wallet or bank account. Adyen supports instant card funding transactions for Visa and Mastercard. Possible use cases include:

Top-up

A shopper loading or topping up their prepaid cards.
A shopper moving funds into another of their financial accounts such as a savings deposit account or retirement account.
A shopper loading their third-party digital wallet.

Person to person money transfer

A funding source for person to person money transfers.

Enable instant card funding

Step 1: Compliance

To enable instant card funding, you must submit compliance documents to Adyen. You must also specify your use case and fulfill compliance requirements for the card scheme. Contact your Account Manager to discuss the requirements.

Step 2: Configuration

When you have completed the compliance processes, contact our Support Team to enable instant card funding.

Process an instant card funding transaction

To process transactions for instant card funding, you must send additional data fields. The fields indicate who is sending the funds and, if applicable, who is receiving them. Send the fields in your /payments or /sessions request, depending on your server-side implementation. The fundOrigin and fundRecipient objects work the same way in both requests. The data you submit must meet our requirements to pass our data validation checks.

Data validation

We perform additional validations when facilitating money transfers between different entities, and decline transactions where the data provided does not meet our requirements.

Only ASCII characters are supported.
The shopperName, and billingAddress fields values can not:
- Consist only of spaces, symbols, numbers.
- Include emojis.
- Be N/A, or null.
The shopperName, and billingAddress fields can only contain the following special characters: ,, ., ;, :, -, —, /, \, +, &, !, ?, @, (, ), ", '.
The shopperName can not be a common placeholder name, like John Doe.
The combined number of characters for the firstName and lastName fields in the shopperName can not be less than 3.
The billingAddress.street field can not consist of less than 3 characters.
The different fields in the billingAddress can not have the same value.

Partial authorization

Partial authorizations enable you to request an authorization for shopper's available balance when the requested amount is higher than the shopper's balance. We recommend to enable partial authorizations for online payouts to avoid failures when a shopper has insufficient funds, and increase authorization rates.