Push payments vs pull payments: What's the difference?

Payments are a lot like hockey games. One player passes the puck to another: he pushes it towards his team mate. If the puck represents $5, then the hockey player is a morning commuter paying for an espresso by credit card. That’s your push payment.

Now, an opponent makes a deft swipe and pulls the puck away from his competitor. The parallel to this would be paying off your car in monthly installments; the money leaves your account each month in a series of pull payments.

If you’re unsure whether a transaction counts as push or pull, consider who is passing the hockey puck (that is, the payment) – or taking it. 

In the rest of this article, we’ll look in more detail at pull vs push payments, the differences between them, their pros and cons, plus use cases for each.

Quick summary: Difference between push and pull payments

To put it simply: push payments happen when somebody actively transfers funds from one source to another. By contrast, pull payments collect funds from someone who has authorized it. 

What differentiates the two is the entity who sets off the transaction; If it’s the payer, it’s a push payment. If it’s the payee, it’s a pull payment.

Here are some examples of purchases commonly made with each method:

Below, we will explain each type in more detail.

What is a push payment?

A push payment is any monetary transaction initiated by the payer, rather than the payee. Common examples include a customer swiping a credit card at the cash register or choosing to pay by digital wallet at an online checkout.

If you receive $60,000 in an insurance payout, that’s a push payment because the insurance company sent the funds directly to your account. Similarly, if you make a withdrawal from an ATM, this is also a push payment (because you triggered the transaction request).

Push payment process

These days, you may be more likely to come across push payments in the context of digital payments such as via payment gateway or electronic funds transfer (EFT). A quick example of a push payment is sending your partner $400 over Venmo (a peer-to-peer electronic payment).

Now let’s look at a more secure form of transaction: a C2B credit card payment on receipt of goods. Here are the stages of that push payment.

1. The point-of-sale device or payment gateway captures the cardholder’s account information. The cardholder authenticates the transaction.
2. The payment processor passes the transaction request to the merchant acquirer.
3. The acquirer contacts the card scheme of the cardholder’s credit card (such as Visa, Mastercard or Diners Club) to request authorization.
4. The card scheme contacts the cardholder’s bank (the issuer) for confirmation.
5. The issuer authorizes the payment. The processor relays the message back to the merchant (at the point of sale/payment gateway).

Pros of push payments

Reduced risk of refund requests and chargebacks because a customer is actively involved in payment at the point of sale. The need for authentication at the point of payment leaves less room for the payer to claim a wrongful charge.

Convenience and familiarity to the customer, who feels confident to submit payment using their chosen method (be it credit card, Apple Pay or direct deposit).

Increased security for merchants because digital payment processing often comes with fraud detection systems. Cashiers typically have a few methods of testing bank notes for authenticity upon receipt, too. 

Instant payment ensures merchants can confidently dispatch goods or provide services knowing they have been paid for. 

Cons of push payments

Transaction fees apply if you are using almost any form of digital payment system. 

Risk of losing repeat business if your payment gateway does not retain cardholder details. Research found a concerning 30% of US online shoppers will abandon their carts if they have to re-enter their credit card details. By contrast, pull payment methods rely on stored payment details to automatically collect funds at regular intervals. 

What is a pull payment?

A pull payment happens when a payee triggers a transaction, instead of the payer. That means the organization expecting payment sends a request, and automatically collects the amount specified. These are also known as merchant-initiated transactions.

The clearest example is an ACH payment that covers your phone bill. Rather than logging into your bank account every month and sending $60 to T-Mobile, you agree to ongoing payments that don’t need any action on your part.

Pull payment process

The exact structure of a pull payment will depend on the specific method chosen. For the sake of simplicity, we will describe the steps of a Direct Debit mandate via ACH in the US. Using the centralized clearing facility in this way is standard practice for taking regular (or one-off) payments from a client. 

1. The business presents a contract (known as a mandate) to the buyer, which sets out the payment terms.
2. The buyer signs the contract, and provides their account information.
3. The merchant submits the Direct Debit mandate to their payment service provider (PSP), with details of transaction amount(s) and frequency.
4. PSP submits the mandate to the Originating Depository Financial Institution (ODFI) if they are separate entities.
5. The ODFI contacts the ACH network to initiate the transaction.
6. The ACH makes the payment request from the Receiving Depository Financial Institution (RDFI), that is, the payer’s bank. 
7. The RDFI authorizes the payment, and credits the merchant’s account.

Benefits of pull payments 

Reduces effort and burden on customers to actively engage in recurring payments. This is a significant convenience which works well for ongoing services, prepaid subscriptions, repeat deliveries, memberships, and other types of recurring trade.

Reduce cart abandonment by allowing customers to spread payments over time (which is how BNPL works).

Predictable revenue flow for your business because mandated payments are more concrete than estimates for pay-on-demand. 

‍ACH transactions are cheaper for merchants compared with credit card processing. However, this may not be the case if your business faces a high rate of ACH declines.

One-off authentication is convenient for merchants, saving time and costs usually involved in customer payment permissions. Merchant-initiated transactions are out of the scope of SCA, and European paperless Direct Debit mandates may not need authenticating at all.

Drawbacks of pull payments

Risk of failed payments if the payer has insufficient funds or cancels the mandate via their bank. Merchants can end up chasing debt because service provision is already underway. Thankfully, modern tech such as Checkout.com's Real-Time Account Updater means customer card details update automatically.

Refund requests can be harder to combat. For instance, when a subscription renews and buyer’s remorse kicks in.

Funds may take several working days to land in the merchant’s account (because ACH Direct Debit is a delayed notification transaction type). You may be able to access same-day ACH payment processing, depending on your bank. However, this comes with additional fees and is not available for international transactions.

Deciding between push or pull payments for your business

Most businesses settle on either push or pull payment methods to conduct the bulk of their revenue operations. Which side you come down on should be led by your product (or service) offering, the nature of your clientele, and the markets you operate in. 

Here are the main considerations for choosing between push vs pull:

‍

Pull payments ask the payer to place a huge amount of trust in your business. Not only will you need a secure method of storing and processing bank account data, but you’ll need to invest in a studied customer retention method. Consider that it’s relatively resource-intensive to sign up a new client for direct-to-account transfer methods such as ACH Direct Debit, but cheaper to collect ongoing revenue thereafter. On the other hand, any interruption of service can readily trigger canceled payments.

Different priorities apply to the merchant favoring push payments. Such transactions take place in near real-time, compared with the delayed notification system of ACH payments. Your customers may be in more of a hurry than those willing to pay by pull methods. After all, nobody wants to fill out a bank mandate every time they buy a cappuccino. 

The advantage of guaranteed payments that push payments like credit card processing provides is the confirmation of the transaction in real-time. You wouldn’t let a customer walk out the door with a diamond necklace just because they signed a piece of paper, right? On-the-spot payment authorization poses significant benefits to both parties in many business deals.

By contrast, there are certainly a range of services, subscriptions, memberships, and repeat deliveries where continual authorization requests would irritate and exhaust the consumer. 

To clarify the differences, here are some examples of businesses better suited to push or pull payments (in the context of taking payment from customers):

‍

It can make sense for businesses to utilize more than one payment method for different sides of their business. A simple example is an insurance broker, which receives premiums via pull payments and dispenses payouts using push payments. 

For others, it wouldn’t make sense to set up a payment infrastructure for taking one-off payments if the business only offers services via subscription, for instance.

Explore payment processing with Checkout.com

When considering long-term investment in your payments infrastructure, you should weigh up which provider is best equipped for the transactions you need. As an integrated provider of payment gateways, acquiring, processing, issuing, and authentication, Checkout.com is reliable for a multitude of business payments.

Secure and flexible push payments

Our dependable platform facilitates secure push payments, empowering businesses to send and receive money across multiple channels and international borders.

Streamlined integration for pull payments

Checkout.com offers robust APIs and pre-built integrations that make it easier for businesses to set up and manage pull payments, such as recurring billing and subscription-based models.