Payment Attempt

Overview

Meaning and boundaries

Payment Attempt is a distinct payer action or transaction candidate intended to satisfy all or part of a payment obligation. One order may produce several distinct attempts: a wallet transaction that fails, an expired quote, a retried invoice, and finally a valid transfer. Assign a unique attempt ID, relate it to the parent obligation, and record which network transaction or provider response belongs to that attempt.

How it works in practice

The payment system creates an attempt when the payer begins an actionable route, then records wallet initiation, requested amount, transaction submission, and eventual result as separate events. A pending attempt may be reconciled again after an API timeout; a new attempt should reference its predecessor and the same parent order so accounting cannot mistake retries for new revenue.

Checks and failure points

Distinguish an attempt from a completed payment. Retries after timeouts must be idempotent so a customer’s second click does not create an accidental second payable order. Preserve previous attempts for troubleshooting rather than overwriting the first result.

Operational evidence and decisions

Attempts should have stable timestamps for initiation, submission, observation, and terminal outcome. This makes it possible to distinguish a wallet signature rejected by the user from a submitted transaction that is merely pending. A retry policy should check both the internal attempt state and the external network result before continuing. Payment analytics should distinguish retry counts, unique payer sessions, and successful orders. This prevents checkout dashboards from confusing repeated attempts with additional sales or new customers.

How it differs from related terms

An attempt is an individual action or candidate, whereas the payment obligation is what must be satisfied and may span multiple attempts. Related entries: Payment Match Candidate; Crypto Payment Initiation; Crypto Payment Exception.