Payments - Introduction / Learning brief
Push versus pull payments
Your notes
In simple terms / 01
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.
Complete lesson / 02
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
- CUSTOMER
Months ago, Riya signed a mandate authorising the gym to collect her membership fee from her Bank Alfa account.
- INSTRUCTION
Ahead of the due date, the gym submits a collection request for INR 1,499.00 through its own bank.
The collection travels through the scheme toward Bank Alfa — an instruction to debit, never the money itself.
- VALIDATION
Bank Alfa checks the collection against the mandate and against Riya's account: is this collector authorised, and can the debit be made?
- 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.
- NOTIFICATION
Riya sees the debit on her statement; the gym is credited and can reconcile the payment against her membership.
| Push (credit transfer) | Pull (direct debit) | |
|---|---|---|
| Who initiates | The payer instructs their own bank | The payee collects under a mandate |
| Who sets the amount | The payer, on each instruction | The collector, within the mandate's terms |
| Typical uses | Rent, salaries, one-off invoices | Utilities, subscriptions, insurance premiums |
| If it goes wrong | Payer asks for the money back — a recall the receiver must agree to, or a return | Payer 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?
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 GOINGKey takeaways / 03
Three things to remember
- 01
In a push payment the payer starts the transfer; in a pull payment the payee collects using authority granted in advance.
- 02
A credit transfer is the canonical push; a direct debit is the canonical pull.
- 03
The direction of the instruction decides who controls the timing and how a payment can be reversed.
Practical use cases / 04
Where you would use this
A person paying a one-off invoice uses a push credit transfer, choosing the exact amount and the moment it leaves their account.
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.
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.
Worked example / 05
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 / 07
Evidence & review
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
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council · Credit transfer as the payer-initiated (push) instrument
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.
- 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
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
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.