Postback Attempts

Postback Attempts

Use Postbacks to review outbound postback delivery history and troubleshoot failed deliveries.

Open:

https://factoring.ltvx.dev/factoring/postbacks

Available filters

FilterPurpose
WebsiteFilter postbacks by the website that generated the event.
HTTP statusFilter by the HTTP status returned by your endpoint.
ShowChoose how many records to display per page.
Attempt resultFilter by the latest attempt result: Processing, Success, or Failed.
Postback statusFilter by the overall postback status: Pending, Processing, Success, or Failed.
Postback typeFilter by Transaction completed or Transaction refunded.
FromShow attempts started on or after this date.
ToShow attempts started on or before this date.

Results table

ColumnDescription
WebsiteWebsite URL, website ID, and the target postback URL used for delivery.
PostbackOverall postback status, mode (Live or Sandbox), and postback type.
OrderOrder ID, transaction ID, and clickID when available.
AttemptLatest attempt number, attempt result, HTTP status, and response latency.
CreatedPostback creation date and latest attempt date.
ActionsOpens the attempt details and retry history.

Attempt details

Click Attempts on a row to inspect:

SectionDescription
Request payloadJSON payload sent to your endpoint. Sensitive values are redacted.
Event IDUnique postback event ID. Use this for idempotency.
AmountAmount and currency sent in the postback payload.
TypePostback type and mode.
CreatedPostback creation time and latest attempt time.
Attempt chainFull retry history for the same postback.
Error messageDelivery error for the selected attempt, when available.
Response bodyResponse body returned by your endpoint for the selected attempt.

Troubleshooting failed attempts

If an attempt failed, check that your endpoint:

  1. Accepts POST requests.
  2. Accepts JSON request bodies.
  3. Uses HTTPS.
  4. Responds with HTTP 200.
  5. Responds within 30 seconds.
  6. Does not block requests by firewall, IP allowlist, WAF, or bot protection rules.
  7. Handles duplicate events idempotently by event_id.


Did this page help you?