Now live Pakistan is up. JazzCash, EasyPaisa and Raast are ready to accept. See the methods
Home Solutions Pay in Pay out Integration Support Support FAQs Blog Talk to sales →
FAQs

Questions merchants actually ask.

Not the questions we wish they'd ask. Answers based on 90-day merchant onboarding calls, ops incidents, and the compliance grillings our legal team gets from prospects' risk teams.

Onboarding & approval

Getting from "hello" to live traffic.

How long does approval actually take?

For a straightforward business, we're at sandbox keys in 4 hours and full go-live inside a working week. iGaming, betting or forex merchants add a compliance review that usually runs 5-10 working days on top. If you're ready with docs, that number shrinks. If your KYB is a mess, it grows.

What documents do you need for KYB?

Certificate of incorporation, tax registration, bank statement (last 3 months), UBO details for anyone owning >25%, director IDs, and. For regulated verticals. Your gaming or forex licence. We ask for what our acquiring partners in each country require, no more. Compliance sends a signed checklist on day one.

Do you accept merchants without a local entity in India / Bangladesh / Pakistan?

Yes, through our acquiring partners in each country. You don't need a local entity to accept local rails. You can be a Curacao, Malta, BVI or Estonia-registered company and still accept UPI / bKash / JazzCash. We handle the local KYB with our partner banks on your behalf.

Will you sign us if we've been rejected by Razorpay / Stripe / a bigger PSP?

Being rejected by mainstream PSPs is not a disqualifier. We serve high-risk verticals as a first-class use case. That said, we still underwrite: if the reason for rejection was fraud, reversal abuse or actual regulatory issues, we'll flag it. If it was "we don't do your vertical", that's usually a fit.

What if my go-live gets stuck?

Escalation is a message, not a ticket. Your account manager, their team lead, and our COO are all on your shared Telegram group. If a compliance question is holding things up, we tell you which document unblocks it. Not "under review".

Pricing & fees

What it actually costs.

What's the pricing structure?

Percentage-based per successful transaction, tiered by method and volume. Rates depend on your vertical, expected volume and payout mix. There's no monthly minimum, no per-transaction floor for micro-payments, and no separate integration fee. Your account manager sends a written rate card once we understand your traffic.

Is there a setup fee?

No. Sandbox access, SDKs, dashboards and integration engineering support are included. The only thing you pay for is successful transactions after go-live.

What about reversal or dispute costs?

Reversals on card transactions carry a per-dispute fee that matches network cost ( set this, not us). UPI and wallet transactions don't have reversals in the card sense. They have reversal windows we handle for you. Your dashboard shows all fees line-by-line, matched to your bank statement.

Do you charge for failed transactions?

No. You only pay on approved, settled transactions. Retries, declines and abandoned checkout attempts are all free.

Technical & integration

Questions your engineering team will ask.

How long does integration take?

Sandbox key to first test transaction: about 90 minutes for a competent backend engineer. Full production integration with webhooks, retries and reconciliation: a working week. Complex custom flows or high-throughput setups: 2-3 weeks with our integration engineer embedded in your team's Slack / Telegram.

Do you have SDKs for [my language]?

Official SDKs for Node.js, PHP and Python cover most stacks. For Go, Java, Ruby, .NET or anything else, the REST API is the same. Any HTTP client works. We publish a Postman collection and OpenAPI spec, and our engineers help you build a lightweight wrapper if you want one. See the integration page.

What happens if my webhook endpoint goes down?

We retry with exponential backoff: 30s, 2m, 10m, 30m, 2h, 6h, 24h. If you're still down after 24 hours, the event drops to the dead-letter queue and we alert your ops team via Telegram. You can also replay any event from the dashboard once your endpoint is back up.

Do you support idempotency for retries on our end?

Yes. Every write request accepts an Idempotency-Key header. Same key + same body inside 24 hours returns the original response instead of creating a duplicate. Different body with the same key returns a 409.

What are the rate limits?

Sandbox: unlimited, effectively. Designed for testing. Production: no per-second limits for well-behaved integrations. If we see abnormal traffic patterns (usually a bug or an attack), we alert you first and only rate-limit if it threatens shared infrastructure. Your AM is on the call before we throttle.

Payouts & settlement

When money moves out.

How fast are payouts actually?

IMPS in India: median 2.4 seconds. bKash and JazzCash: 3-5 seconds. Raast: under 2 seconds. NEFT and RTGS: within their respective bank windows. Full table with 30-day medians on the pay-out page. Weekends, holidays and 3am: same speed.

When do I get settled to my own bank account?

Default is T+1. Everything collected on Monday hits your bank on Tuesday morning. Daily cycles available for merchants above a volume threshold. Weekly or monthly available on request. Your dashboard shows an exact settlement calendar for the next 30 days.

Can I settle in USD or EUR instead of local currency?

Yes. Collect in INR / BDT / PKR from your customers, settle in USD or EUR to a corporate account (yours or your parent entity's). FX rate is your bank's mid-market rate + a small conversion margin disclosed on your rate card. No hidden markup.

What if a payout fails? Do I get charged?

No. Failed payouts (invalid VPA, closed account, blocked recipient) reverse to your escrow within minutes. You're not charged. Your webhook fires a reversal event so your ops team can retry with corrected details in one click.

Compliance & KYC

The legal team's questions.

Are you licensed to accept payments in India / Bangladesh / Pakistan?

Yes, through licensed acquiring partners in each country. The full list of licensed entities and the specific licences we operate under is available under NDA to any merchant in advanced conversation. Your compliance team can review before signing.

Where is merchant and customer data stored?

India transaction data lives in AWS ap-south-1 (Mumbai). No cross-border replication to US / EU. Bangladesh and Pakistan data in the same region under compliance carve-outs. RBI payment data localisation requirements are met.

Do you handle KYC for my end customers?

For payment methods that require it (like Raast in Pakistan, or high-ticket UPI in India), yes. We handle the KYC step in the checkout flow. For low-ticket transactions where KYC is optional, we surface the option and pass the verified data to your system if you want to store it.

Will you sign a DPA / SCC / country-specific data agreement?

Yes. We have templates for standard DPA (GDPR-aligned), India DPDP-compliant addenda, and a country-specific data processing agreement covering IN / BD / PK. Your legal team can redline. Most sign within a week.

High-risk verticals

iGaming, betting, forex, prediction.

Do you actually accept betting / iGaming merchants?

Yes. Regulated iGaming, sports betting, forex and prediction markets are core to our merchant base. We're not doing you a favour. This is the vertical we built for. If you have a valid licence in a jurisdiction (Curacao, Malta, MGA, etc.) and you're not targeting prohibited markets, you're a normal customer for us.

What if my players are in India but I'm not RBI-regulated?

This is nuanced and depends on your product, your licence and the specific PROGA (Promotion and Regulation of Online Gaming Act) status of your vertical at time of signing. We won't sign you if your product violates local law. Your account manager and our compliance team walk through the specific facts with your legal team before onboarding.

How do you handle reversal risk in betting?

Realistic reversal tolerances baked into our underwriting. We don't panic-freeze your account at the first dispute. wallet and bank acquiring usesby default to shift liability. Fraud engine tuned per merchant so you can set your own risk appetite. Weekly reversal review with your AM in the first quarter.

Question we haven't answered?

Message our team directly. If it's a common question, it goes on this page next week.