What we do
Tools
Industries
Department
How we workLet's talk →
Home/Plaid/Plaid Transfer
Plaid

Plaid Transfer: How a Payment Gets Authorized, Settles Into Your Ledger, and Comes Back

Plaid Transfer moves money in and out of US bank accounts that customers link through Plaid. You can collect a debit or send a credit over ACH, same-day ACH, real-time rails or wire, without a separate payment processor. It's a different job from reading account data, so it has its own application, its own risk check on every payment, and a balance held with Plaid that you'll need to manage.

One payment, start to finish

Link the customer's account with transfer in the products list, and keep the account_id they chose.

Authorize with /transfer/authorization/create: amount, debit or credit, network and the customer's legal name. Plaid's risk check answers approved or declined, with a reason.

Create it with /transfer/create using that authorization. The transfer starts as pending.

Track it through events. Plaid sends a TRANSFER_EVENTS_UPDATE webhook, and /transfer/event/sync returns what changed.

What each step expects from you

  1. 1

    Get approved for Transfer

    Plaid requires a Transfer Application and approval before you can move real money, separate from any approval for its data products. Transfer is sold on Plaid's Custom plan. You can build against Sandbox while the application is reviewed.

  2. 2

    Pick the network per payment

    ach for standard ACH, same-day-ach when it can't wait, rtp or rfp for instant, and wire. Plaid can route instant payments across RTP and FedNow, and fall back to same-day ACH.

    Watch for: the authorization only lasts an hour by default. Authorize when you're ready to create the transfer, and cancel the ones you won't use.

  3. 3

    Send an idempotency key with the authorization

    Plaid strongly recommends one. If the network drops mid-request, the retry returns the same decision instead of authorizing twice.

  4. 4

    Write a description the customer will recognize

    The description field takes 15 characters, and on ACH only the first 10 appear on the customer's statement. An unfamiliar name on a statement is a common reason people dispute a debit.

  5. 5

    Let events, not responses, settle the question

    A transfer moves through pending, posted, settled and funds_available, or ends as failed, returned or cancelled. Plaid's docs say a 500 on create doesn't guarantee it failed, so read the events before you retry or tell anyone.

Where the money sits: the Plaid Ledger

Debits you collect land in a balance held with Plaid, and credits you send are paid from it. It has a pending side and an available side, and payouts can only use what's available.

Example week for a payout platform (figures are illustrative)
Customer debits collected Monday (Pending until settled, then held) + $42,000
Hold before funds become available (Typically 2 to 5 days after settlement) $0 yet
Deposit from your business account (Pulled by /transfer/ledger/deposit, held 3 business days) + $15,000
Payouts sent once those funds are available (Declined with NSF if available balance is short) − $38,500
A returned debit from last month (Clawed back from the Ledger) − $1,200
Available once holds clear $17,300

You can set a minimum and a maximum balance, so Plaid tops the Ledger up from your bank or sweeps the excess out by same-day ACH. On your bank statement, each sweep carries the first 8 characters of its sweep_id, which is how you match it.

Where Transfer builds go wrong after launch

Treating "settled" as the end of the story

How you'll know: A consumer debit is marked settled and the loan or invoice is closed, then it comes back weeks later.

Fix: For consumer debits (web or phone authorized), the customer's bank can return them as unauthorized for up to 60 calendar days after settlement. Keep the record open to returns, and reopen the balance automatically when one arrives.

Payouts failing on a short Ledger

How you'll know: Authorizations for credits come back declined with NSF on a busy day.

Fix: Payouts draw on the available balance, not the pending one. Watch it, set a minimum balance, or schedule a deposit ahead of payout runs.

Retrying a returned payment the wrong way

How you'll know: A debit came back R01 or R09 for insufficient or uncollected funds and you simply send it again.

Fix: Plaid requires those retries to carry the description "Retry 1" or "Retry 2". Build that in, along with a cap on attempts.

An approved decision taken as a guarantee

How you'll know: You see approved and assume the payment won't bounce.

Fix: Plaid can approve by default when it can't predict return risk. Read decision_rationale and decide what your product does in that case.

Your records and the Ledger drifting apart

How you'll know: Finance can't say which bank deposit covered which payouts.

Fix: Sync sweep.* events next to transfer events, and store Plaid's transfer and sweep IDs on your own payment records.

Questions people ask

What's the difference between Plaid Transfer and Plaid Auth?

Auth reads a verified account and routing number. Transfer moves the money, using an account the customer linked through Plaid, with a risk check on each payment. Transfer Items also carry the one-time Auth fee, so the two come together.

Does Plaid Transfer support same-day ACH?

Yes. Set the network to same-day-ach on the authorization. Transfer also supports standard ACH, wire, and instant payments over RTP and request for payment, with FedNow in Plaid's instant routing.

Do I need separate approval to use Plaid Transfer?

Yes. You complete Plaid's Transfer Application and wait for approval before moving real money, even if your data products are already live. Transfer is US only and is sold on Plaid's Custom plan, not Pay-as-you-go or the Trial.

What is Plaid Transfer typically used for?

Collecting loan repayments, rent or invoices by bank debit, and paying out to contractors, sellers or borrowers. It suits businesses that want the payment and the account check in one provider and control their own payment schedule.

Who builds the reconciliation around Plaid Transfer?

n-frames builds it: the event sync that updates your own payment records, return handling that reopens the right balance, Ledger monitoring before payout runs, and the sweep matching finance needs at month end.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.