Give account holders cashback at thousands of merchants without signing a single merchant deal yourself.
Neobanks, challenger banks and card issuers with an existing account base.
Your customers already spend with merchants you could be earning commission on. Reaching those merchants means signing up to a dozen affiliate networks, each with its own contract, its own API, its own payout schedule and its own idea of what a conversion is.
Worse, the shopper is anonymous by the time money moves. A click leaves your app, a purchase happens somewhere else, and nothing reliably ties the two together — so you cannot tell a customer what they earned, and you cannot reconcile what you are owed.
You send a hashed identifier, never raw personal data. Email and phone are hashed with your own salt before they leave your systems, so what we store cannot be reversed back to a person.
POST /v1/end-users
A tokenised card reference, not a card number — we never receive or store a PAN. This is the rail that lets a later purchase be tied back to the right account holder.
POST /v1/end-users · card_tokens[]
One call returns a link carrying a click token. The link is resolved at the edge, so the redirect is fast wherever the customer is, and the click is written to the ledger before the shopper reaches the merchant.
POST /v1/links
When the network confirms the purchase, the postback lands on the ledger already joined to the end-user who earned it. You get the commission, the merchant, the amount and the raw payload behind it.
GET /v1/conversions · webhooks
Fourteen networks sit behind one set of endpoints. Adding a network is a change on our side, not an integration project on yours.
Each cashback payment traces to a click, a conversion and the network postback that confirmed it — so a customer query has an answer and finance has a reconciliation.
Identifiers are hashed before transmission. The graph holds digests only, and revoking one is recorded in the audit log.
Card tokens are accepted and stored today, so the rail exists and a card can be tied to an end-user. What is not built is card-network spend detection — attribution still needs the customer to pass through a tracking link. Detecting a qualifying purchase from card activity alone is subsystem #8 and is not shipped.
POST /v1/end-usersPOST /v1/linksGET /v1/conversionsPOST /v1/webhooks