Payment Instruction
Pronunciation: PAY-ment ihn-STRUHK-shun
Definition
A payment instruction is the structured information telling a payer or payment system how to initiate a payment. It can include payee, account or address, amount, currency, network, memo, due or expiry time, payment method, and reference. An instruction is not evidence that payment occurred and can become invalid after cancellation, replacement, account change, or quote expiry.
Overview
Meaning and scope
A payment instruction is the structured information telling a payer or payment system how to initiate a payment. It can include payee, account or address, amount, currency, network, memo, due or expiry time, payment method, and reference. An instruction is not evidence that payment occurred and can become invalid after cancellation, replacement, account change, or quote expiry.
Mechanism and operation
Systems should authenticate the source, version instructions, preserve approval and effective time, display exact details, revoke superseded instructions, and reconcile execution. The workflow for Payment Instruction commonly touches Payment Method and Payment Memo. Documenting those handoffs keeps duplicate events, delayed updates, and manual corrections for Payment Instruction traceable to the correct object. When Payment Instruction interacts with Payment Method, useful controls include allowlisted assets and networks, server-generated instructions, authenticated callbacks, independent transaction monitoring, confirmation or finality thresholds, duplicate detection, rate expiry, exception queues, and reviewed manual decisions. In the relationship between Payment Instruction and Payment Memo, merchant fulfillment policy should specify exactly which verified state permits delivery or account credit.
Practical payment example
A corporate treasury prepares a payout instruction with asset, amount, chain, beneficiary and approval policy. A signer checks the complete instruction before authorization; a saved request does not itself move funds.
Operational checks
A reliable implementation of Payment Instruction separates intent, authorization, network or provider processing, confirmation, settlement, and accounting. When Payment Instruction interacts with Payment Method, a submitted transaction or customer-facing success message is only an intermediate signal until the expected asset, network, amount, recipient, execution result, and finality policy have been verified.
Distinctions and limits
Important risks include invoice fraud, address substitution, stale instructions, wrong account or network, missing tags, unauthorized changes, and duplicate execution. For Payment Instruction, risk controls should be proportional to payment value and reversibility.
Related reading
Related definitions: Payment Memo.
Example
A corporate treasury prepares a payout instruction with asset, amount, chain, beneficiary and approval policy. A signer checks the complete instruction before authorization; a saved request does not itself move funds.
Comparison
An instruction is not evidence that payment occurred and can become invalid after cancellation, replacement, account change, or quote expiry. Important risks include invoice fraud, address substitution, stale instructions, wrong account or network, missing tags, unauthorized changes, and duplicate execution.
Key Takeaway
Payment instructions must be authenticated, versioned, precise, time-aware, and linked to the resulting transaction and commercial obligation.
Sources
- OxaPay API Reference: Payment — OxaPay (2026-08-01)
- Bitcoin Developer Guide: Payment Processing — Bitcoin.org (2026-08-01)
- FATF Guidance on Virtual Assets — FATF (2026-08-01)