Pull payment
What is pull payment?
Pull payment is a transaction where the merchant initiates the withdrawal of funds from a customer's account based on prior authorization. The customer provides payment credentials once, then the merchant "pulls" the authorized amount when needed.
Most of the payments people make every day work this way. Card payments, collections, and are all pull payments: the customer grants permission at checkout or signup, and the merchant triggers every debit after that through its and the relevant or bank rails. Because the merchant controls the timing, pull payments support stored credentials, , and automatic billing without the customer returning to approve anything.
Key facts
- Also known as: merchant-initiated transaction (MIT), the label card networks use to separate merchant-triggered charges from ones where the customer is present at checkout. The distinction affects which authentication rules apply to the charge.
- Initiated by: the merchant, using credentials the customer authorized earlier
- Common rails: payments, direct debit, direct debit
- Typical use cases: subscriptions, usage-based billing, one-click checkout, free-trial conversions
- Opposite model: , where the customer initiates each individual transfer
How it works
- Authorization – The customer enters card details or signs a direct debit mandate and agrees to be charged in future.
- Credential storage – The credentials are stored, usually through rather than as a raw card number, so later charges don't require the customer to enter anything again.
- Merchant trigger – When a charge is due, whether that's a renewal date, a metered invoice, or a one-click purchase, the merchant submits the request for the agreed amount.
- Routing and approval – The request reaches the acquirer, then the card network, then the , which approves or declines it against the customer's balance or credit line.
- Settlement – Approved funds move to the merchant, and the customer sees the debit on the account after it has happened rather than before.
Pull payment vs push payment
The two models differ in who starts the transaction, and that single difference drives the fraud profile, the flow, and what happens when a customer wants their money back.
| Who triggers each payment | When the customer approves | Common rails | Reversal route | |
| Pull payment | Merchant | Once, upfront | Cards, direct debit | through the issuer |
| Customer | Every transaction | Bank transfer, , | Refund from the merchant; limited buyer protection |
Benefits and risks
- Higher fraud risk – Stolen credentials can be misused, because possession of the card data is enough to trigger a charge without the customer being involved.
- Chargeback exposure – Customers can dispute transactions with their issuer months after the debit, and the merchant carries both the reversed amount and the cost of contesting it.
- Greater convenience for repeat purchases and subscriptions – Renewals run without any customer action, so no checkout step stands between the billing date and the payment.
- Predictable collection timing – The merchant chooses the debit date, which makes subscription revenue easier to forecast than customer-initiated transfers that arrive late or never.
