Article
From AFT to payout: what happens behind a money transfer
Every time money moves, a carefully orchestrated sequence kicks off invisibly. This is what it actually looks like.
Money transfer sounds simple: someone sends funds, someone receives them. But behind that two-second notification lies a layered chain of authorisations, verifications, network rails, and settlement cycles - each of which can silently succeed or fail. Understanding this chain isn't just an academic exercise. For product teams and finance leads building payout flows, every link in that chain is a lever: for speed, cost, reliability, and compliance.
Let's walk through the full journey - from the moment a payer initiates an Account Funding Transaction (AFT) all the way to the moment funds land in a recipient's account.
What is an Account Funding Transaction?
An Account Funding Transaction (AFT) is a specific card transaction type used to pull funds from a payer's card account - not to pay a merchant, but to fund a separate account or initiate a transfer. Think of it as the "pull" at the start of the payment journey.
AFTs are governed by card network rules (Visa and Mastercard each have their own specifications) and are distinct from standard card purchases. They carry a unique Merchant Category Code (MCC) which signals to the issuing bank that this is a funding event rather than a retail transaction.
Key distinction:
An AFT funds a transfer. The corresponding outbound leg - pushing money to the recipient - is called an Original Credit Transaction (OCT), often referred to simply as a "push-to-card" payout. Together, AFT + OCT form the backbone of card-based money transfer.
The full journey: step by step
The full journey: step by step
Here's what actually happens when a money transfer is triggered:
Step 1
Payer Initiates: Card details & amount submitted via AFT
Step 2
Authorisation: Issuing bank approves or declines the pull
Step 3
Funds Held: Balance reserved; not yet moved
Step 4
OCT Dispatch: Push-to-card or bank rail triggered
Step 5
Settlement: Funds clear into recipient account
Step 1: The funding pull (AFT)
The payer enters their card details on the platform - either a debit or credit card. The platform (or its payment provider) submits an AFT to the card network. This request includes the transaction amount, the payer's card PAN, and the specific MCC marking it as a funding transaction.
At this stage, 3D Secure (3DS) authentication may be required depending on the geography and risk profile. Under PSD2 in Europe, for example, strong customer authentication (SCA) applies to most cardholder-initiated funding transactions.
Step 2: Authorisation at the issuing bank
The card network routes the AFT request to the payer's issuing bank. The issuer runs its own checks: Is the card active? Is there sufficient credit or balance? Does the transaction pattern look suspicious? The issuer returns an authorisation response - approved, declined, or a referral.
Decline rates on AFTs tend to be higher than on standard purchases because many issuers treat funding transactions with more scrutiny. Platforms should build in smart retry logic and user-facing messaging for declines to reduce abandonment.
CTA: Contact us today to know how you can lower the risk of failed payment attempts
Step 3: Funds hold and settlement lag
Once authorised, the funds aren't immediately moved, they're held. The payer's available balance is reduced, but the actual transfer of funds between banks happens during the settlement cycle, which typically runs once or several times per business day depending on the network and region.
Step 4: Dispatching the payout (OCT or bank transfer)
Once the inbound funds are confirmed (or using pre-funded liquidity), the platform dispatches the outbound payout.
Step 5: Final settlement and confirmation
Settlement is the point at which funds actually move between financial institutions - not just as an authorisation, but as an irrevocable transfer. Once settled, the recipient's bank credits their account and the payout is complete.