Browse wiki · Payment confirmation

Payment confirmation

When is a payment complete?

Time estimates are approximate, not deadlines or guarantees. Base commonly needs about 20–30 minutes; Arbitrum can take minutes to tens of minutes as Ethereum batches finalize. Arc, Polygon and Avalanche generally need seconds, with verification sometimes taking up to a minute. Congestion, delayed batches, RPC outages and testnets can take longer.

These estimates include an operational allowance for verification. Base finality, Arbitrum chain information, Arc finality, Polygon finality, and Avalanche integration explain the network behavior.

Transfer executed, awaiting finality means the matching transfer was observed in a canonical block, but the payment remains pending. We never switch to soft confirmations to speed up fulfillment. A shared finalized-head cache only defers checks; payment still requires fresh canonical receipt and finalized-block verification, including the independent RPC witness where configured.

Normal finality waits are checked roughly every 15–25 seconds. RPC failures retain backoff. Progress retains signature-verification, scan-anchor and broadcast timestamps and durations even when old timeline entries are pruned. It records submittedAt, includedAt (first verified observation, not block timestamp), finalizedAt (server confirmation), waitReason, and block/head numbers. Timeline confirmation checks show duration, scheduled time and queue delay, distinguishing network waits from worker delay. Missing timestamps on older payments are not backfilled; the timeline keeps the latest 100 entries.

Deliver your product only after your server reads status: "paid" for the expected invoice. Match the invoice and order, amount and recipient. A wallet popup, submitted transaction hash, browser redirect or screenshot is not a confirmed payment.

While awaiting payment, poll from your server at a modest interval, such as every 5–10 seconds, with backoff on errors. Stop on a terminal result and apply an overall deadline. Keep fulfillment idempotent so repeated status checks cannot deliver an order twice.

Confirmation time depends on the network and verification. If a result is pending or uncertain, keep checking the existing invoice instead of asking the customer to pay again. Receipts are available after successful settlement; export the receipts you need for your records.

Configure signed payment webhooks in the API tab. See Payment webhooks for verification and retry behavior. Automatic subscription billing is not available.

← All topics