The payment gateway
End-to-end payment technology solutions tailored to your business needs
If you are running payments under your own licence rather than accepting through ours, the operator-side software is described under payment systems. Sector-specific flows are covered under tourism and hospitality.
Payment Orchestration (Core)
The building blocks of your payment infrastructure — routing, security, installments, and reporting
Smart Routing (Smart Switch)
Every transaction is evaluated before it leaves your system. The routing engine reads the card's BIN, brand, type and currency, then matches it against your rules to pick the acquirer most likely to approve it. When a provider degrades, a circuit breaker opens and traffic moves to the next eligible route without a failed payment reaching your customer.
Fraud Prevention
Risk is scored before authorization, not after settlement. Velocity limits track attempts by card, IP and customer; device signals flag automation and timezone mismatches; BIN analysis weighs issuer country and card type. Every decision is written to an immutable audit row, so a declined transaction can always be explained.
Installment Engine
Installment options are resolved per issuer, not hardcoded per merchant. You define which plans apply to which card ranges and amount bands, and the checkout shows only the plans the customer's card actually supports. Campaign periods and merchant-funded extra instalments are configured separately from the base plan, so a promotion never rewrites your standing terms.
Reconciliation & Reporting
Settlement files are matched against your own transaction records line by line, and anything that does not reconcile is surfaced as an exception rather than silently absorbed. Reports read from the same ledger the payment flow writes to, so the number on a dashboard and the number in an export are never two different truths.
Payment Acceptance Solutions
Offer the best payment experience to your customers
Checkout (Ready-Made Payment Page)
A hosted payment page you can point customers to or embed in your own flow. Fields, language and branding follow your configuration; card data is tokenized at the edge and never reaches your application layer. The same page handles the 3DS challenge, so you do not maintain a separate redirect path for authenticated payments.
Pay by Link
Create a payment request and send it over any channel — SMS, email, messaging app or a printed QR. The link carries a fixed amount or lets the payer enter one, expires on a schedule you set, and can be reused or locked to a single use. Each link reports its own status, so you know whether it was opened, abandoned or paid.
Recurring Payments
Subscriptions run on stored credentials with the issuer flags a recurring charge requires, not on a re-run of the original checkout. Plans carry their own interval, retry policy and grace period; a failed renewal moves into a dunning sequence instead of silently cancelling. Customers can be notified before each charge, which is what keeps disputes down.
QR Code Payment
Generate a QR that resolves to a payment request — at a table, a kiosk, a counter or on an invoice. The code can be static and tied to a location, or generated per order with the amount already filled in. The payer scans, pays on their own device, and the result reaches your system over the same webhook as any other transaction.
Platform & Ecosystem
Platform solutions that fit your business model
Marketplace Solution
Onboard sub-merchants under your own account and keep their transactions, balances and reporting separate. Commission is calculated per sub-merchant and per transaction type, then split at the point of settlement rather than reconciled afterwards. Each party sees only its own data, while you retain a consolidated view across the platform.
Bulk Payments
Submit many payments in one operation — by file upload or API batch — and track them as a single job with per-row status. Rows that fail validation are rejected before any money moves, so a malformed file does not produce a half-executed batch. Completed jobs keep their full row-level history for audit.
Developer Tools
Powerful tools for your technical team
Mobile SDK
Native SDKs for iOS and Android that keep the payment flow inside your app instead of bouncing the user to a browser. Card entry is tokenized on the device, so your app never handles raw card data and stays outside PCI scope. 3DS challenges render in-app, and the result comes back through the same callback as every other outcome.
Chargeback Management
Disputes arrive in one queue with their deadline, reason code and current stage visible at a glance. Evidence requirements are listed per reason code, and the documents you have already collected for that transaction are attached automatically. Nothing depends on someone remembering a date — every stage carries its own due date.