Accept retries safely
Stable idempotency keys and transaction identities keep duplicate deliveries from becoming duplicate commercial outcomes.
Affiliate tracking
Connect referral codes and links to conversions with explicit identity, idempotency and environment boundaries that survive duplicate delivery.
Built for operating reality
Stable idempotency keys and transaction identities keep duplicate deliveries from becoming duplicate commercial outcomes.
A conversion retains the code, affiliate and rule evidence used when the decision was made.
Publishable and secret test keys stay bound to sandbox environments and separate test activity from live activity.
One path to money
Use browser-safe code validation where a customer enters a referral, then record the paid outcome from trusted server code. AffiliateRails resolves the authoritative attribution before commission calculation.
Failure semantics
Retry the same semantic body and key. The platform returns the original committed result or a bounded conflict when another request is still in progress.
Questions, answered
A stable external transaction identity and idempotency key bind retries to one canonical conversion result.
Record confirmed outcomes from trusted server code. Secret credentials must not be shipped in a browser or mobile bundle.
An existing live attribution remains authoritative; a later supplied code cannot silently replace it.
Build the reliable path