Crypto Payment Initiation

Overview

What it means and why it matters

Crypto payment initiation is the moment a customer or application starts a payment attempt, before the blockchain has necessarily received any funds. It begins a business workflow, not an irreversible transfer.

How it works in practice

A checkout asks the payment service to create a payment request. The service records an order reference, supported asset and network, amount, expiry and destination instructions. The customer may open a wallet or scan a QR code. Only after signing and broadcasting does an on-chain transaction exist; initiation alone does not create one.

Technical detail without the jargon

An invoice ID should remain separate from a transaction hash: one invoice can have zero, one or several transactions. Store a stable idempotency key for creation requests so a retry does not accidentally create several orders. The exchange-rate quote may also have its own expiration independent of the invoice.

A deeper point to understand

Initiation has two separate clocks: the request creation time and the moment a payer actually signs. For recurring checkout, a customer may request several invoices for the same shopping cart; the merchant must decide which payment request remains payable and whether earlier ones are canceled. Cancellation cannot recall a transaction the customer already broadcast.

Common mistakes and limitations

A customer can open a wallet and then abandon it, switch network, or submit too little. Therefore initiation is not proof of payment. Do not decrement inventory permanently or deliver digital goods merely because a session was opened.

What to check in a real payment system

To troubleshoot an abandoned checkout, compare invoice-created time with any broadcast transaction found on the correct chain. Review the invoice ID and session ID separately. If no transfer exists, contact the customer rather than trying to reverse an initiation event.

Related concepts

Crypto Payment Status, Crypto Invoice, Transaction Finality.

Further reading

OxaPay — API Documentation.