Push Payment
A payment initiated and authorized by the sender, giving them full control over when and how much to send.
Key Takeaways
- A push payment is a transaction initiated by the sender, who controls the amount, timing, and destination of the transfer. This contrasts with pull payments, where the recipient withdraws funds from the sender's account.
- Push payments eliminate the risk of unauthorized debits because only the account holder can authorize outgoing transfers. Bitcoin and the Lightning Network are inherently push-based payment systems.
- The primary fraud risk with push payments is Authorized Push Payment (APP) fraud, where senders are socially engineered into voluntarily transferring funds to a fraudster's account, making recovery difficult.
What Is a Push Payment?
A push payment is a payment transaction where the sender (payer) initiates and authorizes the transfer of funds to a recipient (payee). The sender decides when to pay, how much to send, and where the money goes. No third party can debit the sender's account without their explicit action.
The term "push" describes the direction of control: the sender pushes money outward. This stands in contrast to pull payments, where the recipient pulls money from the sender's account using pre-authorized credentials. Common pull payment examples include direct debits, credit card charges, and subscription billing.
Push payments are one of the oldest payment models. Physical cash is the original push payment: you hand money to someone, and only you can decide to do so. Digital push payments extend this model to electronic transfers, preserving the sender's control over the transaction.
How It Works
The mechanics of a push payment follow a consistent pattern regardless of the underlying payment rail:
- The sender identifies the recipient (by account number, address, or payment request)
- The sender specifies the amount to transfer
- The sender authorizes the transaction through their bank, wallet, or payment app
- The payment system validates the transaction and moves funds from the sender to the recipient
- The recipient receives the funds according to the settlement timeline of the payment rail
The critical distinction is step 3: authorization always comes from the sender. The recipient cannot initiate the transfer, regardless of whether they have the sender's account details.
Push Payments Across Different Rails
The settlement speed and mechanics vary significantly depending on the payment rail used:
| Payment Rail | Type | Settlement Speed | Reversibility |
|---|---|---|---|
| Wire transfer | Push | Same day to next day | Difficult to reverse |
| Fedwire | Push | Real-time (during hours) | Final and irrevocable |
| FedNow | Push | Seconds (24/7) | Final and irrevocable |
| RTP Network | Push | Seconds (24/7) | Final and irrevocable |
| SEPA Instant | Push | Seconds | Limited reversal window |
| Zelle | Push | Minutes | Generally irrevocable |
| Bitcoin (on-chain) | Push | 10-60 minutes | Irreversible after confirmations |
| Lightning Network | Push | Milliseconds to seconds | Instant finality |
Bitcoin as a Push Payment System
Bitcoin is fundamentally a push payment system. Every Bitcoin transaction requires the sender to sign it with their private key. No one can move funds from a Bitcoin UTXO without the corresponding private key. There is no mechanism for a recipient to "pull" bitcoin from someone else's wallet.
This push-only architecture is a core security property of Bitcoin. It means there is no equivalent of a chargeback, no recurring billing that can overdraft an account, and no way for a compromised merchant to drain customer funds. The sender must explicitly construct, sign, and broadcast each transaction.
The Lightning Network inherits this push model. When a sender pays a Lightning invoice, they actively route the payment through HTLCs across payment channels. The recipient cannot extract funds from the sender's channel balance without the sender initiating the payment. Even keysend payments, which don't require an invoice, are still sender-initiated pushes.
# Bitcoin: sender must sign to push funds
bitcoin-cli createrawtransaction '[{"txid":"...","vout":0}]' '{"recipient_address":0.01}'
bitcoin-cli signrawtransactionwithwallet "raw_tx_hex"
bitcoin-cli sendrawtransaction "signed_tx_hex"
# Lightning: sender pushes payment to an invoice
lncli payinvoice lnbc10u1p...Push vs. Pull: A Comparison
Understanding the difference between push and pull payments is essential for evaluating payment system security and user experience:
| Characteristic | Push Payment | Pull Payment |
|---|---|---|
| Who initiates | Sender | Recipient |
| Authorization | Per transaction | Pre-authorized (ongoing) |
| Unauthorized debit risk | None | Possible (if credentials are compromised) |
| Chargebacks | Generally not applicable | Common (credit cards) |
| Recurring payments | Requires sender action each time | Automatic |
| Merchant risk | Lower (no chargebacks) | Higher (chargeback fraud) |
| Consumer protection | Limited after sending | Stronger (dispute mechanisms) |
| Examples | Wire, Zelle, Bitcoin, Lightning | Credit cards, direct debit, ACH pull |
For merchants, push payments reduce chargeback risk significantly. For consumers, push payments offer protection against unauthorized debits but reduce the ability to dispute transactions after the fact. This tradeoff shapes how different payment systems are designed and regulated.
Use Cases
Peer-to-Peer Transfers
Sending money to friends and family is the most intuitive push payment use case. Apps like Zelle, Venmo, and Cash App all operate on a push model where the sender initiates each transfer. Bitcoin and Lightning payments work the same way: the sender chooses to pay and pushes funds to the recipient.
Cross-Border Remittances
International wire transfers are push payments routed through the SWIFT network and correspondent banks. Bitcoin and Lightning offer an alternative push payment rail for cross-border payments with lower fees and faster settlement, particularly for corridors underserved by traditional banking.
Real-Time Payments
Modern push payment rails like FedNow, RTP, Faster Payments (UK), and UPI (India) enable instant push transfers that settle in seconds. These systems are push-only by design: recipients cannot pull funds through them.
Payroll and Disbursements
Payroll processing is an automated push payment. Employers push wages to employee accounts on a scheduled basis. Insurance payouts, government benefits, and merchant settlements also follow the push model: the entity with the obligation initiates the outbound transfer.
Bitcoin and Layer 2 Payments
Every Bitcoin transaction is a push payment, from on-chain transfers to Lightning payments to Spark transfers. This push-only model is what makes self-custody meaningful: holding your own keys means no one can pull funds from your wallet. Layer 2 solutions like Lightning and Spark preserve this property while adding speed and scalability.
Why It Matters
The push payment model is becoming increasingly important as real-time payment systems expand globally. FedNow in the United States, Faster Payments in the UK, and UPI in India are all push-based systems that settle in seconds. This shift toward instant push payments is closing the gap between traditional finance and cryptocurrency payment rails.
For developers building on Bitcoin infrastructure, understanding the push payment model is essential. The merchant payments landscape is evolving as push-based crypto rails offer lower fees and instant settlement compared to legacy pull-based card networks. Platforms like Spark enable developers to integrate push-based Bitcoin and stablecoin payments into applications with minimal complexity.
Risks and Considerations
Authorized Push Payment (APP) Fraud
The primary fraud risk unique to push payments is APP fraud: scams where victims are manipulated into voluntarily sending money to a fraudster. Because the sender authorizes the transaction, traditional fraud detection systems may not flag it as suspicious.
APP fraud takes several forms:
- Impersonation scams: fraudsters pose as banks, government agencies, or trusted companies to convince victims to transfer funds
- Invoice fraud: attackers intercept legitimate invoices and substitute their own bank details
- Romance scams: fraudsters build fake relationships to extract payments over time
- Business email compromise: attackers impersonate executives to authorize fraudulent wire transfers
Losses from APP fraud are projected to reach $6.8 billion globally by 2027 according to ACI Worldwide. In the UK, the Payment Systems Regulator introduced mandatory reimbursement rules in 2024, splitting liability between sending and receiving institutions.
Irrevocability
Most push payments are difficult or impossible to reverse once sent. This is by design: the sender authorized the transaction, so the system treats it as final. For wire transfers, Bitcoin transactions, and Lightning payments, there is no chargeback mechanism. If you send funds to the wrong address or fall victim to a scam, recovery depends entirely on the cooperation of the recipient.
No Built-In Recurring Payments
Push payments require the sender to initiate each transaction individually. This makes them less convenient for subscriptions and recurring bills compared to pull payments and direct debits, where the recipient automatically collects on a schedule. Some push-based systems address this with scheduled or automated push functionality, but the sender must still pre-authorize the automation.
Recipient Verification
Because push payments rely on the sender to input recipient details correctly, mistyped account numbers or wallet addresses can result in lost funds. Traditional banking systems have introduced Confirmation of Payee services to verify recipient names before sending. Bitcoin and Lightning lack equivalent safeguards: sending to the wrong address is generally unrecoverable.
This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.