Coverage at a glance
Your account covers cards, local methods, and everything that connects them: one integration, one commercial relationship.
Your integration reaches local payment rails and card processing at equal depth. One connection, one commercial relationship, one settlement chain, across every method and market in your account.
Account coverage
Operational- Local markets
- 1 live · Indonesia
- Local rails
- 3 pay-in · 3 pay-out
- Card acceptance
- Visa, Mastercard, Apple Pay, Google Pay
- Settlement
- One chain · USD, EUR, or USDT
- Card-data standard
- PCI DSS Level 1
Coverage by market
Local Payment Methods
Every local payment method listed in your account is integrated and tested before it goes live. When a method is available, it is operational. Not pending, not accessed through an unverified chain.
Coverage is built market by market, method by method. What is listed is what works.
Current live market
Indonesia
Transaction currency: IDRPay-In
3 methods- QRIS
- Virtual Accounts
- BCA
Pay-Out
3 channels- BI-Fast
- Non BI-Fast
- E-Wallet
Virtual accounts issued by
.svg){kind=logo}
_prototype_logo.svg){kind=logo}
Local payment methods in development.
Coverage is built and verified market by market before it goes live.
Card acceptance
Card Processing
Visa and Mastercard accepted across active markets, with Apple Pay and Google Pay included. Processing runs on Vianta's own acquiring network.
Accepted
Smart routing
The Engine selects the acquirer at the transaction level in real time — across approval rates, latency, and cost — calibrated to your account by our team.
Fallback on decline
Where a route returns a soft decline, the Engine activates the next available acquirer within the same session, automatically, within the configured fallback sequence.
Network tokenisation
Card PANs are replaced with a network-issued token, reducing decline rates on stored credentials and recurring transactions.
3D Secure
3DS is applied where the issuer or market requires it. Where frictionless authentication is supported, the challenge step is bypassed without merchant action.
Disbursement
Payouts
Pay-out capability is available across all live markets, in the native currency of each. One instruction set covers multiple recipients, confirmed per item in your dashboard and via webhook.
Mass payouts
Multiple recipients paid in a single instruction set. Status confirmed per recipient in the dashboard and via webhook.
Batch API submission
Payout batches submitted through the API or dashboard. One request covers a full disbursement run; webhook confirmation delivered on each item.
Local currency disbursement
Recipients receive funds in the currency of their market.
OCTs — push to card
Funds pushed directly to a Visa or Mastercard number via Original Credit Transaction. No prior charge required on the recipient card. Applicable to player withdrawals, winnings, and partner payments.
FAQ
Yes. Both are available within one merchant account, accessed through one integration.
It means the method has been integrated and tested before it appears in your account. What is listed is operational, not pending activation or subject to further setup on your end.
Local currency proceeds are converted and settled in your agreed currency (USD, EUR, or USDT) at the FX spread set out in your Merchant Service Agreement.
Yes. Payout channels are available in each live market, including bank transfers, instant rails, and e-wallets where applicable.
Settlement frequency varies by market and method. For most, daily settlement is available on agreed terms.
Yes. Every transaction passes through an in-house antifraud module before it reaches settlement. No separate tool to procure or configure. Fraud controls are part of the account from day one.
Bring your markets onto one account
Cards, local methods, and payouts under one integration and one commercial relationship, across every market in your account.
Onboarding
- Apply
- A few minutes
- Review
- Individual · all categories
- Live
- ~1 week to processing