Atomicrails Trace
Detect unusual activity, verify handovers and support compliance across your distribution network. Without exposing sensitive partner information.
Daisy chaining
Gift cards pass through multiple partners before reaching customers. Trace daisy-chains a verifiable record of each recorded handover to the one before it, without exposing downstream customer relationships.
Brand issues, then Processor activates, Distributor distributes, Reseller sells, and the code is redeemed. Each of the four handovers adds a signed receipt linked to the one before it.
Identify unusual resale patterns, unexpected distribution behaviour and suspicious redemption activity.
Each participating partner signs a receipt for its handover, daisy-chained to the one before, to support investigations and reporting.
Share only what verification needs. Commercially sensitive customer relationships stay with the partner.
Why it matters
Gift cards move through multiple independent businesses before reaching the customer. Each party knows its own transactions, but independently verifying the handovers between them remains difficult.
More control shouldn't mean exposing commercial relationships.
We believe every participating business should be able to prove its handovers without revealing its customers.
Read our perspectiveInteractive preview · sample data
Pick a scenario. The records have the same shape every time. What changes is where the chain and the brand's rules disagree.
Cases / 1155
| Hop | Who | What happened | Market | Check |
|---|---|---|---|---|
| 1 | P-1 | Issued | - | |
| 2 | aggregator | Allocated | TR | |
| 3 | reseller | Fulfilled | TR | |
| 4 | Customer | Sold | TR | |
| 5 | P-1 | Redeemed | US |
Every entry verifies. The exception comes from the brand's market rule, not from the records.
Priced for Turkey, redeemed from the US. The other two were redeemed in Turkey.
Illustrative product preview with sample data. Not customer data and not a live deployment. The registry reports and verifies records; it does not void a code or refuse a redemption.
How it works
A random identifier is created at issuance. The gift card code itself is not shared.
Each participating party writes a signed receipt for the handover it already knows about.
Brands review distribution patterns and exceptions by hop number and role, not downstream identities.
Security and compliance
Signed records, controlled access and privacy-preserving verification help support investigations, auditability and compliance workflows.
Security and compliance detailsSee how verifiable distribution records can support fraud investigations and compliance workflows.
We'd like to use Google Analytics to see which pages are useful. It sets cookies on your device and sends data to Google. Nothing is loaded unless you accept, and the site works the same either way. Privacy notice