Manual Replay

There is no self-service replay endpoint for merchants. If automatic attempts were exhausted, or your endpoint rejected an event with a terminal 4xx (all 4xx except 408/429), first correct the receiver and confirm it can durably accept events. Then find the stored, failed event in the delivery log.

Contact TradeOn support with:

• Your merchant ID, visible in the cabinet under Settings.
• The event ID or list of IDs (X-Event-Id, or id in the delivery log).
• The failure reason and what you changed before requesting replay.

Replay applies to an existing stored event. It cannot reconstruct a missing event that was never queued; use REST reconciliation when state is uncertain.

What manual replay does on our side

Support can queue a failed event for one additional delivery attempt. If that attempt succeeds, the event becomes delivered. If it fails for any reason, including a transient error, it becomes failed again. A manual replay does not restart the automatic retry chain.

What you’ll see

• The same X-Event-Id and raw body as the original event.
• Fresh X-Timestamp and X-Signature, generated when the replay is sent.
• An increased delivery_attempts counter and an updated last_response_code in the delivery log.

Verify the signature and freshness as usual. If your durable inbox already accepted that event, return 2xx without repeating the business effect. If it did not, accept it and process it through the same delivery and business deduplication rules. A stored inbox entry with unfinished work must resume through your local worker; replay does not bypass your deduplication keys.

Already-delivered events

Support cannot replay a delivered event through the replay tooling. If your endpoint returned 2xx but processing is incomplete, recover from your durable inbox. If that record is unavailable, reconstruct current purchase state from REST and reconcile balance.