Reseller Program

Resell Aggregator products and services to your own customers. Pay a one-time USD 400 signup fee and choose a provider-access plan lasting six calendar months. You set your customer pricing and provide first-line support to your customers.

Review a package and continue to checkout#

Start with the live reseller packages. Each available package opens a review page that separates the one-time signup fee, six-month package fee, initial invoice total and renewal cost. Prices and eligibility come from the current public reseller API response.

1. Review the selected package and its current provider scope.
2. Sign in or create a workspace. Your selected package is retained through registration and sign-in.
3. Choose the required providers. Search by provider name or filter to the providers you have selected. Enterprise includes the full eligible catalogue.
4. Review the fee breakdown and request the reseller invoice. This step does not make a payment.
5. Use the payment instructions confirmed by finance, submit the actual reference once and wait for verification.

The public review shows initial enrollment costs. If your organization has already paid the signup fee, the workspace applies package-only renewal pricing and checks the existing term before issuing an invoice. An outstanding invoice or pending payment must be resolved before requesting another invoice.

Plans and payment#

The USD 400 signup fee is charged once, separately from the recurring plan fee. Subsequent six-month renewals cost USD 500, USD 1,000 or USD 2,000 for the selected plan. Fees are in USD and do not credit your GGR wallet or your customers' player wallets.

The catalogue contains regional feeds grouped into provider brands. A feed count is not a count of distinct brands, slot providers or unique games. Read the current feed count and eligibility in the live reseller packages, provider directory and the access assigned to your workspace.

Submitting a payment request, entering a transaction reference or returning from a payment page does not activate access. Finance must verify received payment before approval. Retain the invoice and payment reference for reconciliation; do not submit duplicate payments while a request is pending.

Unlimited customer accounts#

There is no per-customer reseller charge and no limit on the number of customer accounts you can onboard under an active reseller plan. Customer access remains bounded by your paid plan, enabled providers, approved currencies and production-access requirements.

Give each customer its own workspace and credentials. Do not share a reseller master key between customers or expose backend API keys in a browser. Keep customer credentials and wallet callbacks separate so identities, balances and settlements cannot cross customer boundaries.

Six-month terms and renewals#

Provider access lasts six calendar months, not a fixed 180-day period. Renew before expiry to avoid an access interruption. Renewal requires another verified plan payment; the one-time signup fee is not charged again.

Early renewal extends the current plan's expiry by six calendar months. A different plan can be selected only after the current term expires; this prevents a six-month upgrade payment from granting the remaining old term as additional upgraded access. Check your approved start and end dates in the workspace.

An expired or suspended reseller subscription does not authorize new customer launches. Settlements, reconciliation and support for already accepted activity still need to be completed. Do not delete financial records or retry a timed-out launch with a new idempotency key to bypass an access restriction.

GGR funding and player wallets#

Reseller plan fees purchase provider access; they do not include gameplay usage. Separately funded prepaid GGR is required. Usage charges follow the agreed workspace/provider billing configuration, not a percentage inferred from the plan price.

The implemented downstream contract uses the native Complete rate: 10% of positive net GGR, calculated independently for each customer, provider, play currency and UTC calendar month, rounded up to cents. Negative GGR can reverse that same period's assessment but cannot offset another provider or carry into another month. Downstream accounting currently supports USD only; no unverified exchange-rate conversion is applied.

Your customer's backend remains responsible for player funds, wallet accounting and signed settlement processing. Player funds are not the reseller subscription payment and are not interchangeable with prepaid GGR. Follow the workspace balance guide and settlement contract.

Insufficient prepaid funding records usage debt rather than rejecting a legitimate accepted settlement. Outstanding debt blocks new launches and is collected from subsequent verified GGR funding. A settlement with an unresolved provider identity also blocks new launches and requires audited platform attribution; it is never assigned to a guessed provider to calculate a fee.

Before accepting real-money traffic, confirm the relevant GGR funding, production authorization, provider and currency enablement, callback delivery and reconciliation. A catalogue listing alone is not a guarantee that every game, territory or protocol is enabled.

Customer integration and support#

Customers integrate their backend with POST https://aggregatornetwork.com/v1/commands, discover their entitled games and use their own workspace API credentials. Complete the integration checklist before production traffic.

You provide customer onboarding, integration assistance, first-line support and player-facing support. Escalate platform issues with the customer workspace, request or correlation ID, game identifier and timestamps. Never send API keys, callback secrets or unnecessary player personal data in a support message.

You and your customers remain responsible for applicable licenses, territory restrictions, responsible-gaming obligations and lawful operation. Subscription payment does not supply a gambling license or waive provider approval.

Reseller control API#

The reseller control API uses the existing authenticated control session, workspace ownership checks and mutation protections. It is separate from the customer game-command API. Package prices and invoice totals are calculated by the server; clients cannot supply their own fee.

Enrollment and renewal bodies contain plan, the selected real provider IDs in providers, and idempotencyKey. Customer creation contains name, a unique lowercase URL-safe slug, providers and idempotencyKey. A payment-evidence body contains method: "manual_review", reference, optional note and idempotencyKey.

Reuse the same idempotency key and unchanged body after an uncertain response. Reusing a key for different request contents returns a conflict. Check the existing invoice before retrying a payment; evidence submission does not mean finance has approved it.

If you selected the wrong package before submitting payment evidence, cancel the unpaid invoice and request a new one. An invoice under pending or confirmed payment review cannot be canceled through this action; contact support instead. Cancellation does not issue a refund or credit a wallet.

Customer listing uses limit and an opaque cursor; follow nextCursor to load subsequent pages. Pagination limits the response size, not the number of customers you may create.

Owned customer administration reuses native control handlers beneath /control/v1/reseller/customers/{customerId} for organization settings, API keys, team members, funding, game access and support. The server verifies the parent-child relationship before applying the customer scope. A supplied customer UUID alone never grants authority.

Check availability before requesting an invoice. An unapproved or incomplete provider package cannot be purchased merely because its marketing price is published. The API's current fundingPolicy states the supported accounting currency and usage rules.

Launch and recovery checklist#

1. Choose a reseller plan and request the initial invoice.
2. Complete the separate signup and plan payment and wait for verified approval.
3. Confirm the assigned provider feeds and production/currency enablement.
4. Create a separate workspace for each customer and provision its own backend credentials.
5. Configure the customer's wallet callbacks and fund the required GGR balance separately.
6. Exercise launch idempotency, signed settlements, delivery retries and reconciliation before going live.
7. Track the subscription expiry and arrange the next six-month renewal.

For the commercial overview, see the reseller plans. For game discovery and integration, continue with the game catalogue and launch guide.

Open your program in the reseller workspace.