Crypto Payment Failed State

Overview

What it means and why it matters

A failed crypto payment is an attempted payment that the system cannot accept because a defined error or rejection condition occurred. It should identify which attempt failed and why, not hide all uncertainty under one label.

How it works in practice

The processor may receive a reverted contract execution, observe an invalid destination or token, detect an amount outside policy, or receive an explicit upstream error. Each condition is recorded with a reason code. The invoice may remain retryable depending on whether the failure relates to one attempt or the whole order.

Technical detail without the jargon

An Ethereum transaction with execution status 0 can consume gas without completing the intended token transfer. A transaction missing from a mempool after a timeout is not automatically failed. Distinguish network execution failure, invoice-policy rejection and API transport failure.

A deeper point to understand

A failed payment attempt should keep its unique attempt identifier even when the merchant order remains open. This makes it possible to distinguish a failed first token transfer from a later successful retry. Otherwise support may mistakenly refund the successful payment when investigating the earlier unsuccessful attempt.

Common mistakes and limitations

Do not issue a second payout or charge just because an HTTP request timed out: the first action may have succeeded. Reconcile chain evidence and request identifiers before retrying or refunding.

What to check in a real payment system

Classify the failure into provider request error, on-chain execution failure or invoice rejection. The first may require reconciliation before retry; the second may require a corrected new transaction; the third may require changing asset, amount or policy conditions.

Related concepts

Crypto Payment Status, Crypto Invoice, Transaction Finality.

Further reading

OxaPay — API Documentation.