mobi

mobi Payment Gateway Overview For Merchants

mobi is a payments platform focused on helping merchants and payment businesses accept and send payments across Asia using local payment rails. The product positioning centers on cross-border payins and payouts, with support for multiple payment methods and localized flows in markets including Malaysia, Indonesia, and India. mobi also describes coverage at the network level, including bank-account and e-wallet reach, and highlights performance targets such as uptime, success rates, and support responsiveness.

mobi Payment Gateway Overview

mobi’s core proposition is to simplify payins and payouts across Asian markets while handling the complexity of local payment methods and cross-border settlement. The platform is positioned to support a range of users, including merchants, banks, digital wallets, money transfer operators, and financial institutions.

Key scale indicators include:

• 11+ years experience

• 3000+ business users

• 21M+ transactions

• Greater than 81% success rate

Coverage And Local Payment Methods In Asia

mobi describes “payins and payouts to 50+ payment methods in Asia” and presents country-specific coverage for Malaysia, Indonesia, and India.

Malaysia

• Payins: FPX, e-wallets, DNQR, and cards

• Payouts: local bank transfer and e-wallets

Indonesia

• Payins: QRIS, VA, and e-wallets

• Payouts: local bank account and e-wallets

India

• Payins: UPI, Net Banking, one-time recurring payments, and cards

• Payouts: local bank account and UPI

Payment Instrument Categories

mobi groups its payment solutions into three broad categories:

• Bank account payments

• e-wallet payments

• Credit and debit cards

The platform also publishes reach-style metrics:

• 1.2B+ bank accounts

• 401M+ e-wallets

Card network brands explicitly referenced in its terms include Visa and MasterCard.

Payment Acceptance Channels And Merchant Flows

mobi positions its platform for both online and in-store acceptance, and also supports card-not-present operational use cases.

Online And In-Store Acceptance

mobi describes providing businesses with tools to accept payments online and in-store. Its terms reference physical acceptance devices under EZYWIRE plans, including:

• EZYWIRE mPOS reader

• EZYWIRE Plus card terminal

API Integration And Checkout Experience

mobi emphasizes API-based integration and also references plugins that can connect to leading e-commerce platforms. For checkout experience, mobi describes:

• Customizable checkout pages, including tailoring by market while aligning with brand presentation

• Customer-friendly flows intended to simplify payment method registration and completion

A demo flow under its payment experience includes options such as saving a card and selecting payment methods like credit or debit card and FPX, indicating support for saved-card style flows in applicable contexts.

MOTO And Pre-Authorization Capabilities

mobi’s terms describe two capabilities that matter for specific verticals:

• EZYMOTO and EZYMOTO VCC authorization requirements for charging card-not-present transactions, including maintaining written cardholder authorization

• EZYAUTH pre-authorization, described as placing a temporary hold on a card until completion of sale, with typical validity periods described as 31 days for hotel and lodging and car rental, and 7 days for other businesses (subject to card issuer policy)

These features are especially relevant for travel, hospitality, and rental-like business models where deposits and delayed capture are common.

Payouts, Cross-Border Settlement, And Currency Handling

mobi presents itself as supporting cross-border settlements across regions, currencies, and borders, including “worldwide cross-border settlements” in major currencies. In retail and e-commerce positioning, mobi also describes local currency payouts, including enabling e-wallet users to receive payouts in local currencies.

Commercially, settlement periods are not presented as a single standard timetable. Instead, mobi’s terms state that fees, charges, and settlement periods are specified in the quotation and are binding.

Pricing Approach And Commercial Terms

mobi promotes “customized pricing plan” positioning and references transparent fees with no hidden charges. However, the detailed commercial structure is primarily quotation-driven rather than being published as a public fee table.

Key fee and policy elements include:

• Zero setup fee up-front option: certain subscription plans may allow setup fee billing at go-live, deducted from settlement proceeds, subject to conditions.

• Refund policy: mobi states a no-refund policy for its services, with an exception described for rejected applications, where a refund is provided minus a RM200 processing fee.

• EZYAUTH fee: RM1.00 per transaction or 1.00% of the transaction amount (whichever is higher). This is described as not being a merchant discount rate (MDR). The terms also describe invoicing behavior for voided, canceled, invalid, or expired pre-authorizations.

• MDR refund limitation: mobi states it does not refund MDR when a reversal or refund is processed.

• Support and device-related fees: the terms describe location-based onsite technical support fees and responsibility for device loss under EZYWIRE plans (with replacement costs referenced as specified in the plan context).

Risk Management, KYC, And Security

Transaction Risk Controls

mobi’s terms describe operational controls that impact merchants’ settlement outcomes, including the ability to:

• Withhold payments

• Establish a reserve account

• Take other actions where transactions are deemed invalid, fraudulent, counterfeit, suspicious, used for illegal or wrongful purposes, or constitute prohibited payment transactions

The terms also describe inactivity-related suspension behavior for card payment services and conditions that may require reapplication.

Additionally, mobi references a daily transaction limit (DTL) that applies to card payment transactions, with increases subject to approval. It also notes that availability of certain services (such as e-wallets and FPX) is subject to approval and separate policies, and that transaction limits can be determined by PayNet and relevant banks or e-wallet operators.

Security Posture In Customer-Facing Channels

mobi describes using HTTPS with Transport Layer Security (TLS) for encrypted communication across its app, website, and payment processing services, and describes access controls and training measures for staff handling data.

Merchant Portal, Documentation, And Integration Operations

mobi provides an account portal login and a separate portal login endpoint under a portal subdomain. For development, mobi presents developer guides and API references via its documentation area and notes that merchants may need to integrate and upgrade systems to comply with the latest API specifications.

Operationally, mobi also references technical support and an “integration manager” style support route in its documentation section.

Service Levels And Support

Performance and support indicators include:

• 99.9% uptime

• 80%+ success rate (with a separate published figure of greater than 81% success rate on its company page)

• Support resolution time described as resolving most queries in under 15 minutes

• 24/7 customer support

Who mobi Fits Best

mobi is most relevant for:

• Merchants expanding into Malaysia, Indonesia, and India that need local payment rails for both collections and payouts

• Businesses that want both card acceptance and local bank transfer, QR, and wallet options in supported markets

• Verticals that benefit from pre-authorization and card-not-present workflows, such as hospitality and car rental

• Merchants that prefer a quotation-driven commercial model with settlement timing, pricing, and specific method enablement defined per program

Conclusion

mobi is positioned as an Asia-focused payment acceptance and payout platform with localized coverage in Malaysia, Indonesia, and India, combining cards with local bank transfer, QR, and wallet methods. It supports multiple acceptance channels, including online, in-store device-based acceptance, and card-not-present workflows like MOTO and pre-authorization.