GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX

Payments - Introduction / Learning brief

Push versus pull payments

Your notes

What this means in plain language

Push and pull payments differ by which party starts the transfer. A push is initiated by the payer, a pull is collected by the payee under prior authority, with credit transfers and direct debits as the standard examples.

A payment moves money in one direction — from the payer to the payee — but the instruction that starts it can come from either end, and that starting point is what separates a push from a pull. In a push payment, the payer tells their own bank to send money out; the bank debits the payer's account and pushes the funds toward the payee. A credit transfer is the everyday example. In a pull payment, the payee collects the money using authority the payer granted in advance; the payee's instruction reaches into the payer's account and pulls the funds out. A direct debit is the everyday example. The money ends up in the same place either way, but who initiates, who holds the timing, and how the payment can be reversed all change with the direction of the instruction.

Understand the full idea, step by step

Two payments will leave Riya's account this week, and she will only press Send for one of them. The rent goes because she tells her bank to send it. The gym membership goes because the gym asks for it — and her bank agrees. Same account, same direction of money, two completely different starting points.

Ask who gave the instruction, not who gets the money

In almost every payment, value travels one way: out of the payer's account and into the payee's. So you cannot classify a payment by where the money ends up. Instead, ask who started it. In a push payment the payer instructs their own bank — Riya's rent is a credit transfer, the canonical push. In a pull payment the payee collects, using authority the payer granted beforehand — the gym's collection is a direct debit, the canonical pull. This one question predicts almost everything else: the party that starts a payment tends to control its amount and timing, and the party that did not start it is the one the scheme's protections are built around.

You may be wondering: how can the gym reach into Riya's account at all?

Only because Riya let it. When she joined, she signed a mandate — a standing authority that names the gym as a collector and states the terms on which it may take money. The mandate is what makes the pull legitimate: without one, no party may collect from another's account, and Bank Alfa checks each incoming collection against the mandate before it debits her.

Direct debit

A direct debit is a pull payment: the payee collects from the payer's account under a mandate the payer granted in advance. On each due date the collector submits a collection request through the scheme; the payer's bank verifies it and debits the account. Utilities, insurers, and subscription services favour it because, once the mandate exists, they can collect recurring — and varying — amounts without the payer acting again.

The pull, step by step

  1. CUSTOMER

    Months ago, Riya signed a mandate authorising the gym to collect her membership fee from her Bank Alfa account.

  2. INSTRUCTION

    Ahead of the due date, the gym submits a collection request for INR 1,499.00 through its own bank.

  3. MESSAGE

    The collection travels through the scheme toward Bank Alfa — an instruction to debit, never the money itself.

  4. VALIDATION

    Bank Alfa checks the collection against the mandate and against Riya's account: is this collector authorised, and can the debit be made?

  5. LEDGER

    Bank Alfa debits Riya INR 1,499.00. Interbank clearing and settlement then square the banks up, exactly as they would for a push.

  6. NOTIFICATION

    Riya sees the debit on her statement; the gym is credited and can reconcile the payment against her membership.

Push vs pull at a glance
Push (credit transfer)Pull (direct debit)
Who initiatesThe payer instructs their own bankThe payee collects under a mandate
Who sets the amountThe payer, on each instructionThe collector, within the mandate's terms
Typical usesRent, salaries, one-off invoicesUtilities, subscriptions, insurance premiums
If it goes wrongPayer asks for the money back — a recall the receiver must agree to, or a returnPayer holds a scheme-defined right to have a collection refunded

COMMON CONFUSION

A mandate lets the payee take any amount, at any time, forever.

A mandate names one collector and the terms of collection, and it stays under the payer's control. Riya can cancel it through her bank at any time, her bank checks every collection against it, and the scheme gives her a right to have a collection returned. The pull is authorised, bounded, and reversible — not a blank cheque.

WHAT IF — Riya spots a collection on her statement that she does not recognise

What happens: She does not have to prove fraud or negotiate with the collector first. Consumer direct-debit schemes give the payer a right to a refund: a defined window for a collection made under a valid mandate, and a longer one where no valid mandate exists at all.

How it is handled: Riya asks Bank Alfa to return the collection, and the bank processes it as a routine scheme event — this is the system working, not breaking. The exact windows and conditions are set by each scheme's rulebook, so a practitioner checks the rulebook in force rather than quoting a number from memory.

STRICTLY SPEAKING

Strictly speaking, push and pull describe the instruction, not the rail it rides. An instant credit transfer is still a push — just a fast one. A card payment is, underneath, another pull, though its authority takes a different form from a direct debit mandate. And mandate formats, refund rights, and timings all vary by scheme and jurisdiction; the direction of the instruction is the part that holds everywhere.

FOR NOW, REMEMBER

  • Money always flows payer to payee; push vs pull is about which end issued the instruction.
  • A credit transfer is the canonical push — the payer starts it and sets the amount each time.
  • A direct debit is the canonical pull — the payee collects under a mandate the payer granted once.
  • Whoever initiates holds the timing; whoever did not is protected: recalls for a mistaken push, scheme refund rights for a disputed pull.

TRY IT YOURSELF

Asha Traders wants its customers to pay monthly invoices that vary in amount, without the customers having to act every month. Which instrument fits best?

A direct debit, collected under a mandate each customer signs once.

Correct — Right. A varying, recurring obligation is exactly what a pull is for: the collector adjusts each request to the real invoice, the customer's bank checks it against the mandate, and the customer keeps a scheme-defined refund right as the counterweight.

A standing order from each customer for a fixed monthly amount.

Not this one — A standing order is a push on a timer — the amount is fixed until the customer edits it. Varying invoices would leave it constantly wrong, underpaying or overpaying until someone intervenes.

A one-off credit transfer that each customer sends by hand every month.

Not this one — That works, but it fails the requirement: the customer must act every month, and a missed month means a missed payment. The question asked for collection without the payer acting again.

Riya's rent is the same amount every month — can her bank simply send it for her? A push on a timer is its own instrument, with its own controls, and it is easy to confuse with the pull you just met.

KEEP GOING

Three things to remember

  1. 01

    In a push payment the payer starts the transfer; in a pull payment the payee collects using authority granted in advance.

  2. 02

    A credit transfer is the canonical push; a direct debit is the canonical pull.

  3. 03

    The direction of the instruction decides who controls the timing and how a payment can be reversed.

Where you would use this

USE CASE 01

A person paying a one-off invoice uses a push credit transfer, choosing the exact amount and the moment it leaves their account.

USE CASE 02

A utility company collecting monthly bills uses a pull direct debit under a mandate each customer signed, so it can request varying amounts on schedule.

USE CASE 03

A payments operations team routes returns differently for the two directions, because a mistaken push must be recalled while a disputed pull can often be refunded under scheme rules.

Put the idea into a real situation

Illustrative example: a fictional customer, Priya Nandal, owes EUR 240.00 to a fictional electricity supplier, Northwind Energy. As a push, Priya opens her banking app and sends a credit transfer of EUR 240.00; her bank debits her account and the funds reach Northwind the same day, and only Priya could have started that movement. As a pull, Priya instead signs a direct debit mandate once, and every month Northwind submits a collection — EUR 240.00 in March, EUR 205.50 in April as usage falls — and Priya's bank pays each on the due date without her acting again. If April's amount were wrong, Priya could ask her bank to refund the direct debit within the scheme's eight-week window; a mistaken push, by contrast, would need Priya to request a recall and Northwind to agree to return the money.

Evidence & review

REVIEWED 2026-07-13

General instrument taxonomy across schemes; SEPA rulebooks cited as concrete examples. Mandate formats, refund rights, and timings vary by scheme and jurisdiction.

What this brief simplifies: Treats push vs pull as a clean binary; card collections and request-to-pay hybrids are only gestured at. Refund windows are described qualitatively rather than as numbers, which the rulebooks set and revise.

Sources for this brief3
  1. Scheme-specific rule2025 version 1.1 (EPC125-05)

    2025 SEPA Credit Transfer rulebookEuropean Payments Council · Credit transfer as the payer-initiated (push) instrument

    Governs the SEPA Credit Transfer scheme: participant obligations, datasets, time cycles, and r-transaction rules for euro credit transfers. · Effective 2025-10-05 · Checked 2026-07-12

    Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.

  2. Scheme-specific rule2025 v1.1 (EPC016-06)

    2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06)European Payments Council · Mandate, collection, and refund mechanics for direct debits

    Rules of the SEPA Direct Debit Core scheme: mandates, collection lifecycle, timelines, R-transactions, and refund rights. · Effective 2025-10-05 · Checked 2026-07-13

  3. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

Learn this properly

Related briefs

View Payments - Introduction archive

Domestic versus cross-border payments

Compares a same-country payment with one that crosses a border, showing how differing currencies, correspondent banks, longer timelines, higher cost, and additional compliance checks turn a single hop into a multi-party chain.

READ BRIEF

Reconciliation in payments

Explains how banks match internal ledgers against nostro statements and clearing reports to prove recorded money equals actual money, and how unmatched items, called breaks, are found, investigated, and cleared.

READ BRIEF