Plaid for Transfer API: ACH, RTP and FedNow
- Nishant Shah
- Sep 25, 2024
- 11 min read
Introduction
A customer wants to fund their wallet, receive a loan payout, pay a bill, or cash out their earnings. They expect it to be fast and painless. But behind that one tap, your application needs to verify the bank account, pick the right payment rail, run risk checks, kick off the transfer, and track it until the money actually lands.
That's exactly the problem the Plaid Transfer API solves. It's Plaid's end-to-end bank-payment solution built for US companies that need to move money using Standard ACH, Same Day ACH, RTP, and FedNow—all through a single integration, rather than stitching together separate processors for each rail.
In this guide, we'll walk through what the Plaid Transfer API actually does, how ACH, RTP, and FedNow differ, how Plaid decides which real-time rail to use, and what a solid integration flow looks like from authorization to reconciliation. If your team is scoping this build, it's also worth talking to engineers who've shipped it before—our team at FintegrationFS has hands-on Plaid integration experience across wallets, lending platforms, and payout products.
What Is the Plaid Transfer API?
The Plaid Transfer API is Plaid's payment infrastructure that connects a financial application directly to the US banking system, letting businesses move money in and out of customer accounts without managing a separate payment processor relationship.
In plain terms, it can help your app:
Connect a customer's bank account
Confirm a transfer is actually allowed before it happens
Move money into or out of that account
Automatically choose the right payment rail
Track the payment from start to finish
Manage the risk of ACH returns
Reconcile completed transfers against your ledger
How Does the Plaid Transfer API Work?
The Plaid Transfer API works by connecting a user’s bank account through Plaid Link, checking account eligibility, authorizing the payment, and initiating the transfer through an appropriate payment rail. Businesses can use ACH for standard collections and payouts or request real-time payments, which Plaid routes through RTP or FedNow based on availability.
Plaid Auth vs. Plaid Transfer: The Difference That Trips People Up
This is one of the most common points of confusion for developers new to Plaid:
Plaid Auth retrieves verified account and routing numbers, but you still need a separate processor to actually move the money.
Plaid Transfer handles the entire payment workflow itself—verification through settlement—without a third-party processor in between.
Transfer does have narrower supported use cases than Auth, though. It's not built for peer-to-peer transfers or general marketplace payment flows in its standard form.
Who Can Actually Use Plaid Transfer?
Access isn't automatic. It's built for US-based businesses that complete Plaid's Transfer application and fall into an approved use case. The good news: you can start building in Sandbox while your production approval is still in progress, so development doesn't have to wait on paperwork.
What Payment Rails Does Plaid Transfer Support?
Three rails power most Transfer use cases:
Standard and Same Day ACH
RTP (The Clearing House's real-time network)
FedNow (the Federal Reserve's real-time service)
To the customer, it might all look like the same "Send Money" button. Under the hood, these rails behave very differently in speed, cost, and reversibility.
ACH Payments Through the Plaid Transfer API
What Is ACH?
ACH is the workhorse of US bank payments—reliable, broadly supported, and well-suited to transactions that don't need to land instantly. Think wallet funding, loan repayments, insurance premiums, subscriptions, bill pay, and recurring transfers.
ACH Debit vs. ACH Credit
ACH debit: Your platform pulls money from the customer's account.
ACH credit: Your platform pushes money to the customer's account.
For example: when a customer adds $200 to their investment account, that's typically an ACH debit. When they withdraw $200, that's an ACH credit.
Standard ACH vs. Same Day ACH
Standard ACH is generally the cheaper option and usually settles within one to three business days. Same Day ACH costs a bit more but can settle the same business day, as long as it's submitted before the relevant processing cutoff.
Why Businesses Still Rely on ACH
Works with nearly every US bank
Handles both incoming and outgoing payments
Great fit for recurring, non-urgent transfers
Generally cheaper than real-time rails
Familiar to both businesses and consumers
Where ACH Falls Short
Settlement isn't instant, and payments can still be returned after they're initiated—insufficient funds, closed accounts, and unauthorized debits are all real risks your platform needs to plan for. That's part of why a wallet might show funds as "pending" rather than immediately spendable: the ACH transfer hasn't fully cleared yet.
RTP Payments Through the Plaid Money Transfer API
What Is RTP?
RTP stands for Real-Time Payments, a network run by The Clearing House. RTP transfers settle around the clock—including weekends and holidays—with funds typically available to the recipient within seconds.
Common RTP Use Cases
Instant wallet withdrawals
Gig-worker payouts
Insurance claim disbursements
Fast loan disbursements
Earned-wage access
Emergency payments
Time-sensitive refunds
Important: RTP Is Credit-Only
RTP is built to push money out, not pull it in. A delivery platform, for instance, can instantly send a driver's earnings to their bank account—but it can't use a standard RTP credit transfer to pull money back from that same account.
RTP's Trade-Offs
Immediate availability and 24/7 operation are huge wins, but not every bank account is eligible for RTP, the receiving bank can still reject a payment, and once sent, these transfers generally can't be reversed the way a card payment can.
FedNow Payments Through Plaid Bank Payment Integration
What Is FedNow?
FedNow is the Federal Reserve's own real-time payment service. Like RTP, it enables instant, always-on bank-to-bank transfers, but it's operated by the Fed rather than The Clearing House.
FedNow vs. RTP: The Practical Difference
Both move money in real time and both are credit-only. The real difference comes down to which banks participate in each network—a receiving account might support RTP, FedNow, both, or neither.
How Developers Actually Access FedNow
Here's the part that surprises a lot of teams: you don't pick FedNow as a separate option. For an instant payout, your integration simply specifies:
network = rtpPlaid then routes the payment through whichever network—RTP or FedNow—the receiving account actually supports. There's no separate FedNow integration to build.
FedNow Limitations to Plan Around
Credit-only, irreversible once sent, and dependent on the receiving institution's participation. Treat authorization as a green light to proceed, not a guarantee the payment will land.
ACH vs. RTP vs. FedNow: Quick Comparison
Factor | ACH | RTP | FedNow |
Speed | Same day or 1-3 business days | Seconds | Seconds |
Availability | Processing windows | 24/7/365 | 24/7/365 |
Debit support | Yes | No (credit only) | No (credit only) |
Credit support | Yes | Yes | Yes |
Reversibility | Can be returned | Generally irreversible | Generally irreversible |
Bank coverage | Broad | Participating banks | Participating banks |
Best for | Funding & collections | Instant payouts | Instant payouts |
Plaid network value | ach or same-day-ach | rtp | rtp (auto-routed) |
choose ACH when cost matters more than speed, choose real-time rails when your customer needs the money now, and always build a fallback for accounts that aren't RTP/FedNow eligible. |
How the Plaid Transfer API Works, Step by Step
Step 1: Create the Customer Record
Your app first establishes the internal user, along with identity information, consent, transfer purpose, and a risk profile.
Step 2: Connect the Bank Account With Plaid Link
The customer selects their bank, authenticates through Plaid Link, and picks an eligible account. Your app gets a temporary public_token, which your backend exchanges for a permanent access_token—one that should never leave your server.
Step 3: Check Real-Time Payment Eligibility
Before promising an instant payout, call /transfer/capabilities/get to check whether the linked account actually supports real-time payments. This way, you're only showing payment speeds the customer can realistically use—not a button that fails later.
Step 4: Create a Plaid Transfer Authorization
This is the decision-making step: /transfer/authorization/create. The request typically includes the amount, direction, network, account ID, ACH class, and an idempotency key, and Plaid evaluates whether the transfer should proceed based on its risk rules.
Step 5: Create the Transfer
Once authorized, call /transfer/create. Keep authorization and creation as separate steps in your logic—approval alone doesn't move money. Plaid uses the authorization ID to prevent duplicate transfers if this call needs to be retried.
Step 6: Track Transfer Events
Use /transfer/event/sync rather than relying only on the initial response. Payments move through several states—pending, posted, settled, failed, returned—and your system needs to catch every transition.
Step 7: Translate Status Into Plain Language
Customers shouldn't have to decode banking jargon. Convert raw statuses into messages like "Transfer submitted," "Your bank is processing this," or "Funds delivered."
Step 8: Reconcile Every Transfer
Tie the Plaid transfer ID to your internal payment ID, ledger entry, fees, settlement status, and bank trace info so nothing falls through the cracks at month-end.
How Plaid Chooses Between RTP and FedNow
Your platform requests a real-time credit transfer with network=rtp.
Plaid checks the receiving account's eligibility.
Plaid selects RTP or FedNow, whichever is available.
If configured, a slower ACH fallback can kick in when neither rail is supported.
Your app receives events reflecting the final outcome.
A freelancer requests a $500 instant payout. Their bank supports FedNow but not RTP. Your app still sends network=rtp, and Plaid automatically routes the payout through FedNow—no extra integration work required on your end. |
Plaid Transfer Authorization and Risk Management
Why ACH Returns Matter
Insufficient funds, closed accounts, invalid account details, and unauthorized transactions are the usual culprits behind ACH returns—and each one can cost you money and customer trust.
Using Plaid's Risk Tools
Plaid Balance checks come included with Transfer, and Signal Transaction Scores can help assess the likelihood of an ACH return before you commit to a transfer. Use these to approve, flag for review, or reject higher-risk transfers automatically.
Plaid Transfer Webhooks and Event Handling
Why Payment Status Needs to Be Asynchronous
Bank payments rarely complete within a single request-response cycle. Your system should return an immediate processing response, store the transfer ID, and then listen for webhook notifications as the real status unfolds.
Risk Controls for Real-Time Payments
Because RTP and FedNow are hard to reverse, lean on stronger safeguards: identity verification, account-ownership checks, velocity limits, per-user daily caps, manual review for unusual activity, and a confirmation screen before final submission.
Important: authorization is not the same as final settlement. An RTP or FedNow transfer can still fail after approval if the receiving bank rejects it.
Recommended Event-Handling Flow
Receive a webhook.
Call /transfer/event/sync.
Process events in order.
Save the new cursor.
Update each transfer idempotently.
Retry temporary failures.
Log the raw event for auditing.
Treat transfer events as your source of truth—a transfer can technically be created even if your API client received a server error, so never assume failure just because a response timed out.
Webhook Security Basics
Always use HTTPS, verify webhook authenticity, never trust a status the client claims on its own, and process duplicate events safely using stored event IDs.
Error Handling and Idempotency
Preventing Duplicate Transfers
Double-taps, dropped connections, timeouts, and retried backend jobs can all trigger duplicate payment attempts if you're not careful. Generate a unique idempotency key per payment intent, store it before calling Plaid, and reuse it only for retries of that same transaction.
Handling Server Errors Gracefully
A 500 error doesn't necessarily mean the transfer wasn't created. Retry authorization with the same idempotency key, retry creation with the same authorization ID, then check transfer details or run event sync before assuming failure.
When an Account Isn't Instant-Payment Eligible
Don't keep retrying the same real-time network. Offer Same Day or Standard ACH instead, or prompt the customer to link a different account—and be upfront about the new arrival time.
Testing the Plaid Transfer API in Sandbox
Before going live, test these scenarios:
Successful ACH debit and credit
Returned ACH payment
Insufficient-funds failure
Closed-account failure
Successful instant payout
Ineligible RTP/FedNow account
Duplicate API request
API timeout
Delayed and duplicate webhooks
Out-of-order events
Refund flow
Reconciliation mismatch
Sandbox transfers can be simulated through Plaid's Dashboard or API using test amounts that trigger specific state transitions. Keep in mind: Sandbox doesn't move real money, and access to a capability there doesn't guarantee production approval.
Compliance Considerations
Connecting the API is only half the job. You'll also need to handle customer identification, KYC/AML monitoring, OFAC and sanctions screening, ACH authorization records, Nacha requirements, consumer disclosures, and dispute handling. Licensing and compliance obligations vary by business model, so loop in legal and compliance specialists early—not after launch.
Common Plaid Transfer API Use Cases
Digital wallet funding: ACH debit pulls funds into a wallet balance
Instant wallet withdrawal: Real-time credit for eligible accounts, ACH as backup
Lending: ACH for scheduled repayments, RTP/FedNow for fast disbursements
Earned-wage and contractor payouts: Let workers choose standard vs. instant
Insurance: ACH debit for premiums, real-time credit for urgent claims
Bill payments: ACH collection with asynchronous settlement tracking
Brokerage funding: ACH debit for deposits, credit for withdrawals
When Plaid Transfer Might Not Be the Right Fit
Consider Plaid Auth with a separate processor, or a different payments setup entirely, if you're building peer-to-peer transfers, marketplace payments between buyers and sellers, international transactions, or complex sub-merchant fund flows. Auth gives you more processor flexibility; Transfer is built specifically as an end-to-end US payment solution with a narrower use-case scope.
Plaid Transfer Integration Best Practices
Confirm your use case is approved before finalizing architecture
Keep credentials and access tokens on the backend only
Separate payment intent, authorization, and transfer creation
Use idempotency keys for every payment attempt
Check account capabilities before offering instant payouts
Treat transfer events as your source of truth
Build ACH returns into your ledger and customer messaging
Require stronger verification for irreversible payouts
Maintain an ACH fallback for ineligible accounts
Reconcile daily against your internal ledger
Test failures and returns, not just successful payments
Give your ops team real tools to investigate transfers
Conclusion
The Plaid Transfer API gives fintech companies one unified way to handle both everyday ACH payments and near-instant payouts through RTP and FedNow. But the strongest implementations go beyond the API calls—they account for account eligibility, fraud controls, event tracking, reconciliation, and how a pending or returned payment actually feels to the customer on the other end.
If you're scoping a Transfer integration, our team at FintegrationFS has built these flows for wallets, lenders, and payout platforms, and as an official Plaid partner, we can help you get from Sandbox to production faster—without the trial-and-error most teams hit along the way.
Frequently Asked Questions
1. Does the Plaid Transfer API process ACH payments directly?
Yes—unlike Plaid Auth, which only hands you verified account details for use with a separate processor, Transfer handles the entire ACH payment lifecycle itself, from authorization through settlement.
2. Does Plaid support FedNow payments?
Yes. When you request a real-time transfer using network=rtp, Plaid automatically routes it through either RTP or FedNow depending on which one the receiving bank supports.
3. Do I need separate integrations for RTP and FedNow?
No. Plaid abstracts both networks behind the same real-time payment flow, so your integration work stays the same regardless of which rail actually processes the payment.
4. Can RTP or FedNow pull money from a customer's account?
No—both are credit-only, meaning they can only push money out. If you need to collect funds from a customer, ACH debit is the option to use.
5. Can a real-time payment be reversed once it's sent?
Generally, no. RTP and FedNow transfers are built to be irreversible after they've gone through, which is exactly why stronger identity and fraud checks matter before you initiate one.
6. How does my app know if a bank supports instant payouts?
Call /transfer/capabilities/get before offering an instant option—this tells you whether the linked account is actually eligible for real-time payments.
7. What is a Plaid Transfer authorization, and why is it a separate step?
Authorization is Plaid's risk-evaluation step that happens before the transfer itself is created. Keeping it separate means an approval doesn't automatically mean money has moved, which protects you from duplicate charges during retries.
8. What happens if an instant payout isn't available for an account?
Your app should fall back gracefully—offer Same Day or Standard ACH, or prompt the customer to link a different account, rather than repeatedly retrying an unsupported real-time network.
9. Can Plaid Transfer support recurring ACH payments?
Yes, recurring ACH is a common and well-supported use case for subscriptions, loan repayments, and other scheduled collections, provided you have proper authorization on file for each charge.
10. Is the Plaid Transfer API available outside the United States?
No, Plaid currently documents Transfer as a US-only product, so international money movement would require a different setup entirely.
