Two-part pricing. A flat monthly hosting fee plus a 0.1%–0.4% transaction share. The model exists for one reason: we earn more when your channel processes more, which means the partnership stays invested in the channel performing well over years rather than performing well long enough to close a contract.
Generic processors price for transaction volume only. The result is an incentive structure where the processor wins by signing operators whether or not the channel performs after go-live, and where any cost the processor wants to recover lives inside the per-transaction rate. That model is fine for retail e-commerce and broken for iGaming.
The two-part model splits cost cleanly. The monthly hosting fee covers the operating cost of running your tenant — infrastructure, security, ongoing development, the operations team — and is fixed because those costs are fixed. The transaction share covers the variable rail and partner cost and is aligned with the channel's actual processing volume. We earn more only when you process more. There is no part of the model that pays us to find an operator and walk away.
We do not publish a public rate card because the share rate that makes sense for a high-volume UPI deployment in India is not the share rate that makes sense for a mid-volume bKash deployment in Bangladesh, and neither is the share rate that makes sense for a Vietnamese sportsbook running peak-event traffic. Quotes are tailored to the situation; the situation is the question we ask in the discovery conversation.
The monthly fee is what runs your tenant. It is sized to the package and the deployment shape — not to a generic SaaS rate card.
Server infrastructure for your isolated tenant, with capacity sized for your expected volume and headroom for known peak windows. CDN, DNS, and the underlying compute and storage to keep the cashier running.
On-call coverage matched to your event calendar, incident response, monitoring and alerting on the cashier surface, and the operations team that responds to a Telegram message at 2 AM during a cricket peak rather than a ticket queue Monday morning.
PCI DSS-relevant handling on our side of the surface, security monitoring, vulnerability management, and the audit-ready reporting the platform produces. Your compliance team gets data in the format it actually needs.
The rails included in your package — typically UPI, MFS wallets, e-wallets, and bank rails appropriate to your markets. New rails added during the relationship are scoped commercially when they require additional partner cost.
Continuous improvements to the platform — new partner integrations, fraud-rule refinements, performance tuning, reporting layer additions — flow to your tenant as part of the operating cost rather than as billable upgrades.
Working communication via Telegram for routine questions and incidents; email is available for formal correspondence. No tiered support plans, no support hours, no upsell to "premium support."
The 0.1%–0.4% range exists because the underlying acquiring economics differ across markets, methods, and volume tiers. Your specific rate inside that range is a function of four variables.
UPI in India runs on near-zero rail cost; e-wallet acquiring in Vietnam or the Philippines runs higher; bank rail acquiring in Pakistan or Bangladesh has its own profile. The market your traffic flows through is the largest single driver of where your rate lands inside the band.
Higher monthly processing volume scales partner-side costs in the operator's favor. The transaction share rate reflects that — operators in higher tiers see lower share rates because the partner stack underneath is priced that way at scale.
A deployment dominated by UPI prices differently from one dominated by MFS wallets or one balanced across multiple rails. The mix matters because partner-side acquiring economics vary by rail. A heavy UPI mix tends to land at the lower end of the band; a card-heavy mix sits closer to the upper end.
Standard deployments use the platform's existing capabilities. Operators who need custom routing logic, bespoke reporting, or non-standard rail integrations beyond the package have those scoped separately rather than absorbed into the share rate.
Honest separation of cost. There are three categories of payment-related cost that are not part of the monthly fee or the transaction share.
You bring your own merchant accounts. The fees those accounts charge — setup, monthly minimums, per-transaction acquirer fees — are between you and the acquiring bank. Our platform does not custody your float and does not extract margin from those fees.
Settlement-side bank fees, FX spreads imposed by your settlement currency, and any acquirer-side rate the partner charges for gaming-classified flows are paid by you to those parties directly. Our share rate is on top, not within.
We register the cashier domain on your behalf at registration time and you reimburse the registration cost. Any premium domain or trademark-related cost is yours; standard registration is a small line item passed through at cost.
One Telegram message. Tell us your monthly processing volume, your target markets, your iGaming platform, and your licensing posture. We respond within hours during Asian business hours, often faster.
Quotes are tailored to the specific situation rather than pulled from a public rate card. Operators who would prefer a public rate card and a self-serve checkout are not the operators this platform is built for, and we are honest about that up front.
The discovery conversation typically takes an hour. The proposal that follows arrives within days. Neither step costs anything; both steps are useful even if you ultimately do not move forward — at minimum, you walk away with a clearer read on what your current setup is costing and what alternative architectures look like.
Tell us the situation; we tell you the quote. No demo to schedule, no "evaluation phase" before the answer.