Product
Two ways to run a sweepstakes brand — integrate the API or run on our platform — and where every part of the product is documented.
Two routes
There are two ways to run a sweepstakes brand on our product, and which one you want is usually decided by something you already have rather than by anything on this page: whether you hold a player ledger, and whether it can represent two currencies.
API integration You run the platform
We supply the game catalogue, the launch layer and virtual-currency support. Everything else — the wallet, the ledger, redemption, packages, payments, verification, state controls — is yours.
Managed platform We run the platform
We operate the ledger and wallet of record, the redemption engine and the state-rule enforcement. You set the policy that drives them, and you keep your own acquiring — the payment rails are not ours on either route. Turnkey and white label sit here too — same platform underneath, with the front end and launch delivered as well.
Turnkey and white label are not a third route. They are the managed platform with the front end and the launch delivered as well — the same platform underneath, the same split of responsibilities, a different amount of work done for you at the start.
What each route includes
| API integration — you run the platform | Managed platform — we run the platform | |
|---|---|---|
| Game catalogue and launch layer | casinoapi.tech | casinoapi.techThe one thing that is ours on both routes. 25,000+ titles from 160+ studios, launched through the same call. |
| Virtual-currency support in play | casinoapi.tech | casinoapi.techA callback registered per currency, so every round carries the currency it was played in rather than having it inferred afterwards. |
| The player wallet and both balances | You | casinoapi.techOn the API route you are wallet of record and the balances live in your system. On the managed route we hold them. |
| Keeping Gold Coins and Sweeps Coins apart in the ledger | You | casinoapi.techWhoever holds the balances owns the separation. This is the part of the build that has to be right first, on either route. |
| Coin package price and contents | You | You set it, we run itThe price point, the Gold Coins, and the Sweeps Coins that accompany a package are an operator decision on both routes. |
| Taking the payment | You | YouYours on both routes. The merchant account is in your name and we do not resell acquiring, so a coin purchase is never acquired through us. The one exception is the crypto rail, which is ours on the managed platform because it needs no merchant account at all. |
| Handling a redemption request | You | casinoapi.techThe mechanism that takes a Sweeps Coin balance and turns it into a prize under stated conditions. |
| Redemption thresholds and holds | You set it, we run it | You set it, we run itThe minimum balance before a redemption can be requested, and any hold before it pays out. Your policy on both routes, and the values live in our back office on both. What acts on them differs: on the managed platform the engine enforces them; on an API integration you read the settings and enforce them yourself, because you hold the balances. |
| Identity verification before a first redemption | You | YouThe check itself is arranged by the operator on both routes, with the operator's own provider. On the managed route the platform enforces the gate — redemption stays blocked until verification is marked complete — but it does not perform the check. |
| Per-state registration, play and redemption rules | You | You set it, we run itWhich jurisdictions are open, to what, and when. Set independently of one another — a state can be closed to redemption and open to play. |
| Promotional offers and grants | You | You set it, we run itFirst-purchase and win-back offers are confirmed. Anything beyond those is an operator decision on both routes. |
| The audit record behind a redemption | You | casinoapi.techOn the managed route the record is kept for 60 days. On the API route we never see the redemption, so the record is yours to keep and yours to size. |
Two rows deserve reading twice. The wallet row is the one prospects most often get wrong, because it decides who is wallet of record and therefore where the money legally sits. And on both routes the identity check itself is yours — on the managed platform we enforce the gate, but we do not perform the check.
The product, page by page
Everything that exists, grouped. There is no page here that describes something we have not built.
The two routes
- API integrationYou run the platform; we supply the catalogue and virtual-currency support.
- Managed platformWe run the platform, including the ledger and the redemption engine. Turnkey and white label sit here.
Virtual currency
- Virtual currencyHow the two-currency model works, and who owns which part of it.
- Dual-currency walletWhy the ledger holds both balances and what keeping them apart requires.
- Gold Coins and Sweeps CoinsWhat each currency is for and what may never be done with either.
- Coin packagesPackage structure, pricing and offers — an operator decision on both routes.
- Redemption engineThresholds, holds, the verification gate and the audit record.
Games
- Game contentThe catalogue, currency-aware from the first round.
- Game aggregationWhat aggregation gets you and what it costs, including when it is us.
- Game providersThe four kinds of content supplier, and how to tell one from a reseller.
- RTP parityWhether one model should serve both currencies.
Money in and out
- PaymentsHow coin purchases are acquired and how payouts leave — and who runs which part.
- High-risk acquiringUnderwriting, classification, and the costs that are not on the rate card.
- Payout railsWhat each rail trades off, and where payouts fail.
- Declines and chargebacksTwo different failures, and what each one costs.
Free entry
- AMOEThe no-purchase route, what it has to be, and what it is not.
- No purchase necessaryWhat the phrase carries and what it does not.
- Postal entryRunning a mail-in route that works.
- Sweepstakes rulesWhat official rules have to say and who writes them.
Compliance
- ComplianceWhat we enforce, what you decide, and what neither of us can outsource.
- State referenceEvery US jurisdiction, with the instrument behind each position.
Documentation
- DocumentationThe integration, in public.
- Getting startedThe first integration, in order.
- Wallet APIThe callback the platform calls, and what it must return.
- Seamless walletHow a round settles against a ledger you hold.
- SandboxStage credentials, the currency list and what to test first.
Where to start
- Read the documentationPublic, and the fastest way to decide whether the integration fits what you already have.
- Get sandbox credentialsA stage environment with a currency list, so the two-currency question can be answered by testing rather than by discussion.
- Book a walkthroughBring your wallet situation and a rough state list; both shape the answer more than anything else.
Two routes, one product. If you are weighing them against each other, tell us what you already run — the answer usually turns on whether you hold a player ledger already.