Five steps. No platform demos to schedule. No quarterly business reviews. No "evaluation phase" that costs you a quarter before anything ships. The path from "we should look at this" to a live branded payment channel is short because the model is built around speed of decision rather than around enterprise sales theater.
Each step has an estimated timeline. The tight ones are tight because we control them. The longer ones are honest about what sits with you, with acquiring partners, or with regulatory review.
An hour-long Telegram exchange covering the basics: what your operation looks like, target markets, expected processing volume, current payment pain points, your iGaming platform, and your licensing posture. We are looking to understand whether this is a fit on both sides — not to perform a sales pitch. If we are not the right answer, we tell you in the same conversation.
A written proposal that includes the recommended deployment plan (markets, rails, partner mix), the payment-method-by-payment-method picture for each market, an honest read on what is currently routable versus contingent, and the two-part pricing tailored to your volume profile. Specific enough to plan from. We do not produce 60-page proposals because nobody reads them and nobody reads them for a reason.
We register the cashier domain on your behalf (you reimburse the registration cost), provision your isolated tenant, and configure the branded cashier — colors, logo, copy, supported payment methods, language. Your platform team gets the integration documentation; if you want, we run the integration ourselves and hand back the working webhook surface. The branded cashier is at cashier.yourbrand.com from this step forward.
You provide the merchant account credentials for the rails and acquirers in scope; we connect them inside the tenant and run end-to-end test transactions. This step has the widest timeline range because partner-side onboarding sits with the acquirer, not with us. Where we hold pre-existing partner relationships, this collapses to days. Where the operator's profile requires a new partner, it follows the partner's underwriting calendar.
The cashier flips on. Real player traffic starts hitting the rails. From this point, the relationship is operational rather than project-based: we monitor 24/7, handle incidents as they arise, propagate partner-side changes to your deployment, add or adjust rails as your needs evolve, and stay on the same Telegram channel. The "go-live moment" is not the end of the project — it is the start of the working relationship that 0.1%–0.4% transaction-share pricing keeps aligned for the lifetime of the channel.
Clean separation. The boundaries are deliberate — what sits with us is what would otherwise force you to staff and run; what sits with you is what only you can run.
The boundary is intentional. We are not the regulator, the bank, or the iGaming platform. We are the payment infrastructure those three things plug into. Each side keeping to what it does best is how the relationship survives years rather than quarters.
Most operators expect the relationship to slow down after launch. The actual shape is the opposite — go-live is when the platform starts being a piece of the operator's product rather than a project being delivered.
The first month after go-live is dominated by tuning. Routing rules adjust as we see how your specific traffic mix behaves on the rails. Fraud thresholds are calibrated as the deployment accumulates legitimate-vs-anomalous baselines. Capacity planning catches the first peak window and adjusts headroom for the next one. Your team and ours stay in the same Telegram channel through this period because the iteration loop is short and conversational rather than ticketed.
The second through sixth month is dominated by additions. Operators discover rails they did not know they wanted, markets they did not know would benefit from a separate tenant, and reporting they did not know to ask for during the proposal. Adding any of these is operationally cheap because the platform was built to absorb them; commercially they are scoped against the existing pricing model rather than as separate engagements.
From month six onward the relationship settles into a steady cadence. Partner-side compliance changes, API updates, and rail behavior shifts get propagated to your tenant on our timeline rather than yours. You do not have to track NPCI, Bangladesh Bank, SBV, BSP, SBP, or the Central Bank of Myanmar; we track them on your behalf, and the changes that matter to your specific deployment land as Telegram messages summarizing what happened and what we already adjusted. This is the part of the value proposition operators tend not to appreciate during the discovery conversation and tend to appreciate most by the end of year one.
Tell us your operation, your markets, your monthly volume, and your current pain. We will tell you within an hour whether the rest of these five steps make sense for you.