A postback is an event and parameter agreement; field names should not be copied from another program.
Agree the data contract first
01
The public T&C do not define a universal postback API.
02
Availability should be confirmed with the manager or technical support.
03
A useful event set often includes registration, FTD and qualified action.
Investigating a mismatch
Without deduplication, retries can double conversions.
Logs, signing and retries
- Provide an endpoint template.
- Confirm signing and retry behaviour.
- Run a test event.
- Deduplicate by event ID.
The event test chain
The brief lists registration, FTD and approved CPA, event ID, signing, retries and accepted response codes.
The developer handover
A postback is ready only after a repeatable test, duplicate protection and retention of the raw response.
Technical agreement
Before development, obtain the event list, parameter names, request example, signing method, retry policy and expected response codes. Send a unique event ID and use it for deduplication. The test should prove delivery of registration and FTD, safe handling of a retry and storage of the raw request. Do not copy another program’s format as an assumption.
A minimum postback acceptance test
Before sending real volume, create one test for every agreed event type. Both sides should be able to find the same event ID together with click or SUB_ID, timestamp, amount, currency and final status. Then resend the same event ID: the receiver must not create a second conversion. This single test validates routing, deduplication and the evidence needed for later reconciliation.
Sources and review date
For “How to request and validate a RioAff postback”, the editorial team reviewed the official RioAff website, current T&C and available dashboard evidence. Last reviewed: 2026-08-06.
Minimum postback evidence
Keep the URL, method, event, click ID, response status and timestamp. Never expose secrets in screenshots or public logs.
Duplicate delivery should be handled idempotently so statistics are not inflated.
Frequently asked questions
Is there one public RioAff postback format?
The public T&C do not define a universal postback API. This reflects public terms; account-specific rates and restrictions still require confirmation.
Which event fields and security rules need agreement?
Provide an endpoint template. This reflects public terms; account-specific rates and restrictions still require confirmation.
How should retry duplicates be prevented?
Without deduplication, retries can double conversions. This reflects public terms; account-specific rates and restrictions still require confirmation.