Skip to main content
POST
/
api
/
v1
/
transactions
/
{winam_tx_id}
/
replay-callback
Replay provider callback for a transaction
curl --request POST \
  --url https://payments.winam.cm/api/v1/transactions/{winam_tx_id}/replay-callback \
  --header 'X-API-Key: <api-key>'
{
  "winam_tx_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "direction": "<string>",
  "provider": "<string>",
  "callback_found": true,
  "callback_id": 123,
  "provider_tx_id": "<string>",
  "raw_payload": {},
  "received_at": "2023-11-07T05:31:56Z",
  "was_already_processed": true,
  "replayed": true,
  "new_state": "<string>",
  "message": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.winampay.de/llms.txt

Use this file to discover all available pages before exploring further.

Use replay only for recovery — when your endpoint was down and missed the original delivery. In normal operation, winam-payments fires webhooks automatically on state changes. Replay is a no-op for transactions not yet in a terminal state (succeeded or failed).

​
When to use

Your callback_url returned a non-2XX response or timed out, and winam-payments exhausted its retry policy (3 attempts with exponential backoff). The transaction is already settled — you just didn’t receive the notification. Call this endpoint to re-deliver the webhook to your callback_url. Your handler should be idempotent — it may receive the same winam_tx_id more than once.

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
winam_tx_id
string<uuid>
required

Response

Successful Response

​
winam_tx_id
string<uuid>
required
​
direction
string
required
​
provider
string
required
​
callback_found
boolean
required
​
callback_id
integer | null
required
​
provider_tx_id
string | null
required
​
raw_payload
Raw Payload · object
required
​
received_at
string<date-time> | null
required
​
was_already_processed
boolean
required
​
replayed
boolean
required
​
new_state
string | null
required
​
message
string
required