Payment Instruction

Overview

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. In the operational context of Payment Instruction, the payment record should preserve pricing, authorization, transaction evidence, confirmations, fees, settlement, and any exception or refund as separate states.

Important risks include invoice fraud, address substitution, stale instructions, wrong account or network, missing tags, unauthorized changes, and duplicate execution.

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.

For Payment Instruction, risk controls should be proportional to payment value and reversibility. 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.

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. In the relationship between Payment Instruction and Payment Memo, the commercial order should advance through idempotent state transitions tied to durable external identifiers.