A request for payment can look like a bill inside a banking application, but the request itself does not move money. It carries structured information that lets the payer review the request and, if they choose, authorize a separate payment from their own account.
The payee creates a structured request
A business or other eligible payee prepares a message identifying the amount, purpose, parties, requested payment date and reference information supported by the service. Its bank or provider validates the message and sends it through an instant-payment system to the payer's participating institution.
Identifiers and remittance details help the payer understand the obligation and later help both sides reconcile the result. The request should be traceable to its sender and should not rely on an unverified link or free-form message alone.
The payer receives information, not a debit
The payer's bank presents the request through an authenticated channel with enough context to make a decision. Receipt of the request does not authorize the payee to pull funds and does not by itself reduce the payer's balance.
The payer can review the sender, amount, due date and reason, then approve, decline or allow the request to expire according to the service. A bank can add warnings or verification steps when the request is unusual or the customer may be at risk of deception.
Approval creates a separate credit transfer
If the payer approves, the bank authenticates the instruction and performs the controls that apply to an outgoing instant payment. The resulting payment is a credit push authorized from the payer's account; it is not the request message turning into an automatic debit.
The bank checks available funds, limits, account status and applicable fraud or compliance controls before submitting the transfer. Approval screens need to make the destination and amount clear because instant payments may settle finally within seconds.
The instant-payment rail settles and reports status
The system validates the credit-transfer message and, when accepted, settles between the participating institutions. The receiving institution then makes funds available under the service rules and posts the payment to the recipient's account.
Status messages tell the participating banks whether the request and payment were accepted, rejected or otherwise completed. The payee's records use the original reference information to match the incoming funds with the correct invoice or obligation.
Controls address fraud, duplicates and exceptions
A legitimate-looking request can still be fraudulent, misdirected, duplicated or already paid through another channel. Customers should verify unexpected requests through a trusted method, and banks monitor sender patterns, repeated requests, unusual amounts and other risk signals.
Expiration, decline and payment status are recorded separately so a request is not mistaken for completed settlement. Clear support and dispute procedures remain important even though the payer, rather than the payee, initiates the actual transfer.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.