The connectivity layer powering local payments globally

Most merchants move from sandbox access to live production in three to four weeks, depending on the complexity of your reconciliation logic and how many methods you’re activating. Boku supports a wave-based rollout approach – activating countries in stages rather than all at once, which reduces integration risk and allows for validation before scaling. A dedicated Integration Manager supports two-party and merchant-side testing, smoke tests, and certification checks at each stage. Boku monitors closely for approximately two weeks post-launch before transitioning to standard ongoing monitoring.

Boku creates and stores billing tokens on the merchant’s behalf – secure references that enable future charges without re-authentication. Token lifecycle is managed directly with each provider, including refresh, re-authentication, and re-issuance. The same token model supports both merchant-initiated recurring transactions (MIT) and customer-initiated saved-payment flows (CIT).

*Not every LPM supports tokenization – coverage is confirmed during onboarding.

All provider-specific flows – OTPs, app redirects, bank confirmations – run inside Boku’s platform and are surfaced through a consistent gateway response: success, failed, or pending. Pending states are handled with structured polling and webhook callbacks, so merchants never need to manage method-specific timing rules.

Boku provides a full sandbox environment with provider-specific test accounts for realistic end-to-end simulations. Onboarding includes two-party and merchant-side validation, smoke tests, and integration review at each stage, supported by a dedicated Integration Manager throughout.

Boku collects in local currencies and settles into the merchant’s preferred currency (USD, EUR, GBP, or one of 32 supported settlement currencies). The settlement flow runs from payment provider to Boku to merchant, with competitive FX rates, multi-currency collection, and a unified settlement record for finance reconciliation.

Boku provides standardized refund APIs supporting full refunds, partial refunds, and multiple-partial refunds where the underlying method allows. Reversal capability is available for in-progress transactions. Webhook callbacks keep merchant systems in sync for all refund events. Where a method does not support partial refunds, supported behaviour is confirmed per country during onboarding.

Boku actively manages token lifecycle at the provider level – refreshing tokens directly with each provider to prevent expiration before it causes a failed renewal. Smart retry logic handles pending and failed states with method-appropriate behaviour. Where customer action is needed – such as a wallet top-up after insufficient funds – Boku surfaces user-action notifications to prompt re-engagement before the subscription lapses.

Boku’s 24/7 NOC and SOC monitors success rate, error rate, and volume continuously, with anomaly-based and trend-based proactive alerting – not just outage detection. The Risk and Fraud team reviews traffic daily and escalates anomalies. Post-launch, Boku runs approximately two weeks of intensive monitoring before transitioning to standard ongoing oversight.

Boku operates active-active architecture across two AWS regions – either region can carry 100% of traffic independently. Failover exercises run throughout the year. The platform holds a 99.99% monthly uptime SLA and is ISO 27001 certified, with 24/7 NOC and SOC monitoring in place.

Merchants access a portal for transaction search, refunds, and report downloads. Daily and monthly reporting packs cover transactions, refunds, chargebacks, and adjustments. Finance system integration is supported via secure SFTP file delivery with PGP encryption.