Set up Account Funding Transactions
Process Visa and Mastercard Account Funding Transactions (AFT) through Silverflow: configure the funding charge per scheme in the silverflow-v2 contract.
For acquirers on Silverflow. An Account Funding Transaction (AFT) pulls funds from a cardholder's Visa or Mastercard card to fund another account, such as a wallet, a prepaid card or a brokerage account. The card schemes require AFTs for specific merchant category codes (MCC), with extra data about the sender and the receiver of the funds.
You decide per project and per scheme whether payments are sent to Silverflow as AFTs. The merchant creates the order as described in Account funding in the payment acceptance docs.
Supported schemes and features
| Visa | Mastercard | |
|---|---|---|
| AFT | Yes | Yes, since February 2025 |
| Refunds of AFTs | Yes | Yes |
| One-click (CIT) and recurring (MIT) AFTs | Yes | Ask your Ginger contact |
| Manual and delayed capture | Yes | Yes |
| Payment links | Yes | Yes |
Payment links support AFTs since 30 October 2026, with card, Apple Pay and Google Pay. Since June 2026, Ginger forwards
the state of the sender and receiver for recipients in the US, Canada and Australia, and since November 2025 the
customer's birthdate. See the changelog.
Configure the contract
In the silverflow-v2 contract of the project, set charge_ to funding-charge for each scheme that sends AFTs,
and pick a funding_. Schemes with charge_ set to charge keep sending regular purchases.
Set sender_ to true when the cardholder funds their own account. Otherwise, give the receiver of the
funds in the receiver_ fields of the scheme. Visa also requires a purpose_ for AFTs to some countries.
See the silverflow-v2 scheme fields of Update a project contract in the API reference for
the funding types per scheme and the other values.
Send AFTs for Visa to a wallet held by the merchant. Mastercard works the same, with a Mastercard funding_:
curl https://api.example.com/v1/admin/merchants/$MERCHANT_ID/projects/$PROJECT_ID/contracts/silverflow-v2/ \
--user "$API_KEY:" \
--header "Content-Type: application/json" \
--request PUT \
--data '{
"boarding_mode": "disabled",
"schemes": {
"visa": {
"acceptor_key": "mac-EXAMPLEACCEPTOR001",
"charge_type": "funding-charge",
"funding_type": "wallet-transfer",
"receiver_first_name": "Acme",
"receiver_last_name": "Wallet",
"receiver_account_number": "NL91ABNA0417164300",
"receiver_account_number_type": "iban-bank-account"
}
}
}'In the Admin portal, open the project, go to Payment Method Contracts, open Silverflow and set Charge type to Funding charge for the scheme.
Where the sender and receiver come from
| Party | Taken from |
|---|---|
| Sender (the cardholder) | The order's customer: first and last name and a complete billing address. With account-to-account, also sender_ in the transaction's payment_ |
Receiver, when sender_ is false | The receiver_ fields of the contract, and the country of the merchant's billing address |
Receiver, when sender_ is true | The order's customer |
When the contract has no receiver_, Ginger falls back to receiver_ in the transaction's
payment_, as the merchant docs show. Ginger checks the data before it sends the AFT: a missing field
puts the transaction in error with a reason such as Missing receiver_ or
Missing postal_.
The transaction
When every scheme in the contract is a funding charge, transactions get transaction_ set to aft. Captures, voids
and refunds of AFTs use the standard endpoints.
Contracts created before silverflow-v2
The legacy silverflow contract switched AFT on for the whole project with is_. Ginger shows such a contract as
silverflow-v2, with Visa as wallet-transfer and Mastercard as account-to-account funding charges. Configure new
projects with silverflow-v2.
Next steps
- Account funding: how merchants create AFTs.
- Silverflow: test cards and amounts.