Push and pull payments describe two opposite directions money can travel. The difference comes down to who initiates the transaction. In a push payment, the payer selects how to send funds (e.g., wire transfer, instant payout). In a pull payment, a business debits an account using authorization the payer already granted (e.g., card payments, direct debits). In 2025, the US Automated Clearing House (ACH) Network processed 15.6 billion push transactions and nearly 19.6 billion pull transactions.

The distinction between push and pull payments is in how fast the funds move, whether a transaction can be reversed, and what risk each type of transaction carries. Below, we cover how push versus pull payments work, where they differ on authorization and reversibility, and which one fits specific business needs such as payroll, subscriptions, or marketplace payouts.

Key takeaways

• Push payments are initiated by the payer, while pull payments are initiated by a business that has been granted authorization in advance.

• Push payments are generally final, whereas pull payments can be disputed and reversed; this shifts the risk associated with each payment model.

• Businesses often use both models: to pull recurring payments from customers and push payouts to vendors or contractors.

What are push payments?

A push payment moves because the payer decides to send it; no one needs to request it. The person or business holding the funds controls the timing and amount, and once the money clears, the recipient usually can’t pull more or reverse the payment. Common examples include wire transfers, ACH or Single Euro Payments Area (SEPA) credit transfers, and real-time payments.

What are pull payments?

A pull payment works the other way around. The business collecting the money has previously obtained permission, through a card number entered at checkout or a signed authorization, to debit the payer’s account. Common examples include card payments and ACH or SEPA direct debits.

Push vs. pull payments: What are the main differences?

Push and pull payments diverge in nearly every aspect. The direction of initiation determines who carries the risk, how fast funds settle, and how easily a transaction can be reversed.

Here’s what to know:

• Initiator: Payers start push payments, while businesses start pull payments with authorization already granted by the payer.

• Authorization timing: Push payments need no advance authorization; the payer simply decides to send money. Pull payments require consent before the first debit, whether that’s a card number or a signed direct debit authorization.

• Reversibility: Push payments are generally final once they clear the network, but pull payments carry built-in reversal paths. For example, cardholders can dispute a charge through their issuer, and ACH debits can be returned by the receiving bank within specific time frames, typically two business days for unauthorized debits and up to 60 days for consumer accounts.

• Speed: Wire transfers and real-time push payments can settle as quickly as in a few seconds to the same day, while standard direct debit pulls usually take one to three business days, though same-day options exist.

• Risk exposure: Because businesses have the power to debit an account, pull payments carry exposure to insufficient funds, disputes over unauthorized use, and chargebacks. With push payments, the risk falls on the sender if they enter the wrong account details, since money sent to the wrong destination is difficult to recover.

• Best-fit models: Push payments tend to suit one-time disbursements such as payroll, vendor payments, and marketplace payouts, while pull payments typically suit anything recurring, such as subscriptions, memberships, and installment plans.

When should a business use push vs. pull payments?

The decision usually comes down to who needs control over the timing of the payment and how much recurring collection a business actually handles.

Here are the main considerations:

• Payroll: Push payments generally work here because companies need certainty that wages will land on a specific day.

• Vendor and contractor payments: Businesses that pay vendors, contractors, and earned wage access (EWA) programs—where employees draw against wages already earned before payday—often rely on push payments for the same reason.

• Marketplace and platform payouts: Platforms that pay out sellers, drivers, or freelancers on demand typically use push payments, especially instant payouts, because recipients often want funds immediately.

• Subscriptions and recurring billing: Subscription businesses usually depend on pull payments to collect payments automatically each billing cycle.

• Utilities, insurance, and loan servicing: These businesses often use direct debit (i.e., pull payments) because the amount is known in advance, the schedule is fixed, and manual collection isn’t realistic for the volume they process.

• Card-present (CP) retail: Even though it settles in seconds, a CP transaction is a pull payment since the customer authorizes the charge at the terminal and the business’s payment provider handles the pull from there.

How does authorization work for push vs. pull payments?

When a business initiates a push payment such as a wire transfer, a real-time transfer, or an instant payout, it’s already authorized to move funds out of its own account. That means authorization is built into the act of sending, and there’s no separate step involving the recipient’s consent.

Pull payments need explicit, documented authorization before the first debit, and the specifics shift depending on the payment network. Card networks treat the card number itself—plus the card verification value (CVV), address verification, and sometimes 3D Secure (3DS)—as evidence of authorization at the point of sale (POS). The cardholder agreement also covers recurring use once a card is on file.

Direct debit is stricter. Nacha rules require a written or “similarly authenticated” authorization for every recurring ACH debit, and businesses must keep that authorization record on file for two years after it’s revoked. That’s why an ACH checkout page usually includes explicit consent language and a checkbox. A direct debit sent without valid authorization can come back as an unauthorized return, and return rates above the network’s thresholds can cause a business’s entire setup to come under scrutiny. This can sometimes lead to added monitoring or processing restrictions.

Card issuers work similarly: a pattern of disputes tied to weak authorization evidence, such as a missing CVV or an expired card-on-file agreement, makes it harder for a business to win future chargebacks.

What are the risks and constraints of push and pull payments?

Push and pull payments can each run into trouble at volume. Failure modes don’t show up until a business is processing real transactions.

Push payments

Instant settlement means instant exposure with push payments. Once a real-time payment settles, it’s done. There’s no float period to catch a mistake before it’s final, and errors are hard to reverse. Getting the money back from a wire or an instant payout that was sent to the wrong account number, for example, depends on the receiving bank’s cooperation, not on any automatic dispute mechanism. Push payments also don’t handle uncertain amounts well. They’re best for fixed, known amounts sent at a chosen moment.

Pull payments

Pull payments carry dispute and chargeback exposure. They require up-to-date authorizations that can be proven. If a customer disputes ever having authorized a subscription charge, the business needs the original consent record to prove it; a billing history showing past charges won’t suffice. Also, any business pulling direct debits at scale will see a percentage of returns for non-sufficient funds. This is routine for pull payments at volume, and repeated attempts against the same account carry their own return-rate risk.

How Stripe Payments can help

Stripe Payments provides a unified, global payments solution that helps any business—from scaling startups to global enterprises—accept payments online, in person, and around the world.

Stripe Payments can help you:

• Optimize your checkout experience: Create a frictionless customer experience and save engineering time with prebuilt payment user interfaces (UIs), access to 125+ payment methods, and Link, Stripe’s consumer network.
  
• Expand to new markets faster: Reach customers worldwide and reduce the complexity and cost of multicurrency management with cross-border payment options, available in 195 countries across 135+ currencies.
  
• Unify payments in person and online: Build a unified commerce experience across online and in-person channels to personalize interactions, reward loyalty, and grow revenue.
  
• Improve payments performance: Increase revenue with a range of customizable, easy-to-configure payment tools, including no-code fraud protection and advanced capabilities to improve authorization rates.
  
• Move faster with a flexible, reliable platform for growth: Build on a platform designed to scale with you, with 99.999% historical uptime and industry-leading reliability.
  

Learn more about how Stripe Payments can power your online and in-person payments, or get started today.

FAQs about push and pull payments