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
| Filter | Purpose |
|---|---|
| Website | Filter postbacks by the website that generated the event. |
| HTTP status | Filter by the HTTP status returned by your endpoint. |
| Show | Choose how many records to display per page. |
| Attempt result | Filter by the latest attempt result: Processing, Success, or Failed. |
| Postback status | Filter by the overall postback status: Pending, Processing, Success, or Failed. |
| Postback type | Filter by Transaction completed or Transaction refunded. |
| From | Show attempts started on or after this date. |
| To | Show attempts started on or before this date. |
Results table
| Column | Description |
|---|---|
| Website | Website URL, website ID, and the target postback URL used for delivery. |
| Postback | Overall postback status, mode (Live or Sandbox), and postback type. |
| Order | Order ID, transaction ID, and clickID when available. |
| Attempt | Latest attempt number, attempt result, HTTP status, and response latency. |
| Created | Postback creation date and latest attempt date. |
| Actions | Opens the attempt details and retry history. |
Attempt details
Click Attempts on a row to inspect:
| Section | Description |
|---|---|
| Request payload | JSON payload sent to your endpoint. Sensitive values are redacted. |
| Event ID | Unique postback event ID. Use this for idempotency. |
| Amount | Amount and currency sent in the postback payload. |
| Type | Postback type and mode. |
| Created | Postback creation time and latest attempt time. |
| Attempt chain | Full retry history for the same postback. |
| Error message | Delivery error for the selected attempt, when available. |
| Response body | Response body returned by your endpoint for the selected attempt. |
Troubleshooting failed attempts
If an attempt failed, check that your endpoint:
- Accepts
POSTrequests. - Accepts JSON request bodies.
- Uses HTTPS.
- Responds with HTTP
200. - Responds within 30 seconds.
- Does not block requests by firewall, IP allowlist, WAF, or bot protection rules.
- Handles duplicate events idempotently by
event_id.
Updated 28 days ago
Did this page help you?