PayQuicker API v2: What a Real-Time Payouts API Changes for Platforms

PayQuicker's API v2 shows what a real-time payouts API does and doesn't change. Compare rails, fees, prefunding math and the fraud controls to set up first.

Adrian ReyesSenior Payments & Fintech Editor

October 23, 2026 · Updated October 29, 2026 · 9 min read

Laptop showing lines of code on screen beside a spiral notebook and blue pen on a wooden desk

Photo: Pixabay

On this page 6 sections

What PayQuicker's API v2 Adds
Payout Speed Depends on the Rail Behind the Real-Time Payouts API
Where Instant Payouts Earn Their Cost
Run the Numbers: Fees and Prefunding for 400 Weekly Payouts
Final Settlement Means Fraud Controls Come First
What to Get in Writing Before You Switch Payout Providers

Key takeaways

A payouts API controls and tracks payments. How fast the money arrives depends on the rail behind it: ACH, Same Day ACH, RTP, FedNow or push-to-card.
Network limits ($1 million for Same Day ACH, $10 million for RTP and FedNow) are maximums. Your bank's limit and your provider's per-payee caps can be lower.
Prefunding can tie up more cash than the fees cost. In our illustrative example, $120,000 in weekly payouts ties up about $48,000 before the card revenue behind it settles.
RTP and FedNow payments are final once sent. Put holds on account changes and require two-person approval for batches before you turn on instant cash-out.

A real-time payouts API lets your platform's software pay sellers, contractors or promoters and see each payment's status the moment it changes. Nobody has to upload a bank file. PayQuicker's API v2, announced Oct. 14, 2026, shows what that layer now handles: signed webhooks, batches of up to 5,000 payments, retractions of mistaken payments and live funding balances. It does not make money move faster. Speed comes from the payment rail underneath, and the rail you choose sets both your cost and how much a mistake will hurt.

What PayQuicker's API v2 Adds

PayQuicker describes itself as a global payouts orchestration platform. Its Oct. 14 press release and the announcement on its own site list four capabilities:

Real-time webhooks. Signed notifications go out when a payee registers, when a payment's status changes, when an account receives funds and as a batch job progresses. Your system no longer has to keep asking the API for updates.
Batch processing. Each job takes up to 5,000 payments or invitations, and you can schedule payments up to 30 days ahead. If a row fails, it's reported on its own and the rest of the batch still goes through.
Retractions. You can recover the remaining balance of a payment sent in error directly through the API, with no support ticket.
Funds visibility. The Paypers reports that funding balances and transaction activity are now available through the API for reconciliation.

All four features give you more control and more information. The fast rails were already in place: PayQuicker's Aug. 26, 2025 Same-Day ACH announcement said its real-time payout network already included instant payments to cards and digital wallets.

For an operator, the webhooks matter most day to day. Finovate's coverage puts it simply: clients can respond to events as they happen and stop checking repeatedly for updates. When a seller emails to ask where a payment is, a webhook-driven dashboard shows the provider's current status. Without it, you're guessing from your last batch file. Read the retraction feature closely, too. It recovers only the remaining balance. Once a payee has withdrawn the money, all you can do is ask for it back.

Payout Speed Depends on the Rail Behind the Real-Time Payouts API

A payouts API sits between your platform and one or more rails. Your software says who gets paid and how much. The provider moves the money and reports back. Here's how the U.S. options compare for payouts.

Rail	Speed	Can You Recall It?	Per-Payment Ceiling	Main Catch
Standard ACH	Batched, a business day or more	Returns allowed under Nacha rules	Set by your bank	Business days only
Same Day ACH	Same business day if you meet the cutoff	Returns allowed under Nacha rules	$1 million (Nacha rule)	Cutoff times; business days only
RTP Network	Seconds, 24/7	No; settlement is final, though a return can be requested	$10 million network limit	Payee's bank must be on RTP
FedNow	Seconds, 24/7	No; settlement is final	$10 million network limit	Payee's bank must be on FedNow
Push-to-card	Near real time	Hard to recover	Set by the card program and issuer	Payee's debit card must be eligible

Those ceilings come from different rulebooks, so it helps to know which is which. Same Day ACH's $1 million per-payment cap is a Nacha operating rule, in effect since March 18, 2022, per Nacha's guidance. The RTP network limit went from $1 million to $10 million in February 2025, according to Stripe's FedNow vs. RTP overview. FedNow got there in two steps in 2025. Its limit rose from $500,000 to $1 million on June 24, as stated in the Federal Reserve's June announcement, and then from $1 million to $10 million effective November 2025, according to Federal Reserve Financial Services' September release.

Both $10 million figures are network maximums, and participating banks can set lower limits. Now that the two caps are equal, Stripe notes that the real differences are who runs each network, which banks participate and how each bank configures the service. So the limit you actually get depends on your bank and your provider. A payout provider's fees and per-payee caps are its own pricing, never a network rule.

Volume differs more than limits do. Stripe reports that RTP processed 142 million transactions in the second quarter of 2026, while FedNow processed nearly 5 million. Both networks only push money from sender to recipient, which suits payouts. Our comparison of RTP, FedNow and ACH for instant payments goes deeper. For push-to-card, see our look at Visa Direct's stablecoin funding for seller payouts.

Don't Split Payments to Get Under the Same Day ACH Cap

Say a general contractor owes a sub $1.4 million on a draw and wants it to land today. Sending two $700,000 Same Day ACH entries to slip under the $1 million cap is the wrong move. Nacha tells originators to avoid structuring entries to get around the per-transaction limit, and it reviews possible evasion case by case. Its guidance draws the line at real invoices. A business paying several separate invoices of $1 million or less to the same supplier can send each one as its own Same Day ACH payment. For a single payment over $1 million, use RTP or FedNow if both banks allow that size, or send a wire.

Where Instant Payouts Earn Their Cost

Speed pays off when payees can see the delay and have somewhere else to go.

Marketplaces

Sellers watch their balance grow in a dashboard while the next scheduled payout is still days away. Instant payouts for marketplaces mean letting sellers withdraw their available balance on demand, and the hard part is defining "available." Subtract open return windows, pending refunds and open disputes, or you'll end up covering chargebacks from your own account. Payout design also affects tax reporting. See 1099-K rules for marketplace operators and confirm the details with a tax professional.

Contractors and Construction

General contractors who pay subs out of draw releases have a specific reason to want speed. Subs commonly won't sign an unconditional lien waiver until the money has actually arrived, and a payment that settles in seconds shortens that exchange. You still need the paperwork. Our guide to conditional vs. unconditional lien waivers explains when to sign each.

Staffing and Professional Services

Paying interpreters, per-diem staff or freelance creatives the day a timesheet is approved helps you fill short-notice work. Approval is the control that matters. No payout should go out before the timesheet or deliverable is signed off.

Events and Ticketing

Promoters, artists and night-of staff expect to be paid right after the show. But ticket revenue carries risk until the event happens. If a show is canceled, refunds and chargebacks arrive after you've already paid everyone. Read our guide to refund rules for canceled or postponed events before you promise same-night payouts.

Run the Numbers: Fees and Prefunding for 400 Weekly Payouts

This example is illustrative. A platform makes 400 payouts a week averaging $300 each, or $120,000 a week. Fees are hypothetical: $0.25 per standard ACH payout and $1.00 per instant payout, over a 52-week year. These aren't any provider's prices, so get written quotes for each payout method.

Scenario (Illustrative)	Weekly Payout Fees	Annual Payout Fees
All standard ACH	400 × $0.25 = $100	$5,200
Instant is optional, 30% choose it, platform pays the fee	(120 × $1.00) + (280 × $0.25) = $190	$9,880
All instant	400 × $1.00 = $400	$20,800

All-instant costs $15,600 a year more than all-ACH. The cash you have to set aside in advance is often the larger figure, though it's a balance you carry and not an expense. Instant payouts come out of an account you've already funded, before the customer card payments behind them reach your bank.

Suppose payouts go out evenly across five business days, $24,000 a day, and the card money for those sales arrives two business days later. You'd carry about $48,000 in the payout account before the matching revenue lands. The gap gets wider if sellers can cash out on weekends and holidays. RTP and FedNow keep running then, but card deposits that reach you by ACH wait for the next business day.

Reserves and holds on your merchant account reduce what you have available to fund payouts, so compare why a processor holds funds with what your own statement shows. Then add a cushion like that $48,000 to a 13-week cash flow forecast. If the number makes you uncomfortable, offer instant cash-out as an option for established payees only and keep scheduled ACH as the default. Then decide whether you'll pay the instant fee yourself or charge a disclosed fee to payees who choose it.

Final Settlement Means Fraud Controls Come First

The Clearing House's RTP FAQ says sending banks can't revoke or recall a payment once it's submitted to the RTP network, and settlement is final and irrevocable. The network does give banks a message to request a return of funds, but the receiving side decides whether the money comes back. Stripe's overview describes FedNow payments as final and irrevocable too. The common failures are predictable. A fraudster takes over a seller's account, swaps in new bank details and requests an instant payout. A fake payee builds up a balance and cashes out before refunds or chargebacks show up. Or one bad batch file sends thousands of wrong payments at once.

Set these controls before the first instant payout goes out:

Hold payouts for a set period after any change to bank or card details. Confirm the change through a separate channel, such as a call to the phone number already on file.
Limit or delay first payouts to new payees until they have a sales or work history with you.
Cap the amount and frequency of payouts per payee, with manual review above the caps.
Require two people to release a batch. A 5,000-row job with a bad file is 5,000 bad payments.
Verify every webhook signature and reconcile daily against your funding balance. PayQuicker signs its notifications, but your code still has to check them.

Platforms that hold or move money for others can also take on legal obligations, including state money transmitter licensing, identity verification, sanctions screening and tax reporting. This is general information, not legal advice. Confirm your obligations with qualified counsel and your bank.

What to Get in Writing Before You Switch Payout Providers

Ask which rails reach U.S. payees and which one the provider falls back to when a payee's bank or card can't take an instant payment. Get per-payout fees for each method in writing, and confirm whether you can charge a disclosed fee to payees who choose speed. Ask what per-payment and daily limits the provider and its partner bank apply, since they can sit well below the network ceilings. Pin down when funding has to be in the account.

Then ask about the failure cases. Find out how retractions and misdirected payments work after a payee has already withdrawn the money. Ask which fraud and compliance controls come built in, such as identity checks, sanctions screening and tax forms, and which you'd have to build yourself. Test in a sandbox, and move a small group of payees off batch ACH before you switch everyone.

Payouts stay predictable only if the money coming in arrives on a predictable schedule. Before you promise sellers or subs same-day money, find out exactly when your card and online sales reach your bank. MannyPay's online payment processing and payment gateway integrations handle incoming payments for eCommerce businesses and event ticketing and promotions companies. Request a free quote and include your current statement. A MannyPay specialist will respond within one business day.

Sources

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.