Built for payments that cannot wait.

A Sri Lanka payment gateway for businesses that want one clear route from checkout to settlement. Launch the payment flow you need, connect your operation, and know what happens after every transaction.

sri lanka payment gateway routing visual from checkout to settlement
CheckoutApprovalSettlementOne operational route

One platform. Four money moments.

Choose the route that matches how customers buy. Method, currency and settlement availability are confirmed during merchant onboarding.

Put a focused payment step at the end of every cart.

Use a hosted experience to reduce implementation scope or connect through an API when the checkout needs deeper control.

See integration paths

See the transaction. Not just the result.

Every payment moves through a sequence your finance, support and engineering teams can understand.

  1. 01InitiateCustomer selects a method
  2. 02AuthenticateRequired checks are presented
  3. 03AuthorizeThe payment is approved or declined
  4. 04SettleFunds follow the agreed schedule
  5. 05ReconcileRecords connect back to the order

Payment methods, acquiring partners, currencies and settlement timing are defined in the signed merchant schedule.

For finance, engineering and customer operations

The operational details belong in the product.

Online payments do not end at an approval screen. Your team still needs reliable references, refund handling, payout visibility and a defined route when something needs attention.

Method readiness

Activate the routes that fit the merchant profile.

Cards, bank transfers, wallets, QR and international options depend on onboarding, acquiring setup and market availability.

Risk and onboarding

Know the checks before development becomes urgent.

Business registration, ownership information, KYC/AML review and website readiness are mapped before production access.

Post-payment control

Keep order and money states connected.

Use transaction references and event updates to align fulfilment, support, refunds and finance reconciliation.

Start with the surface you already run.

Hosted checkout, APIs, webhooks, payment links and connector-supported commerce paths let the payment experience fit the operating model instead of replacing it.

Explore integrations
Hosted checkoutREST APIWebhooksCommerce connectorsPayment links

Commercial facts, before the go-live date.

A payment gateway quote should make the total operating model visible, not hide behind a single percentage.

One merchant scheduleMethods · currencies · fees · payout timing · refund rules · support route
Processing
Rate by approved method and transaction profile
Settlement
Currency, payout account and agreed cadence
Exceptions
Refund, dispute and cross-border conditions
Implementation
Hosted, API or connector scope
Review the pricing model

Answers for the first evaluation

Common questions, sorted by the work ahead.

What does merchant onboarding require?

Requirements vary by business type, ownership and payment flow. Expect business registration details, ownership and identity information, a clear product or service description, website policies and the settlement account requested by the acquiring setup.

Which payment methods and currencies are available?

Method and currency availability is confirmed after the merchant profile and target markets are reviewed. The signed schedule records the approved methods, settlement currency, payout account and any cross-border conditions.

How long does it take to go live?

Timing depends on document readiness, underwriting, the selected integration and testing. We map these dependencies at the start rather than promise a universal launch date.

Can this connect to an existing website or app?

Yes. The normal paths are hosted checkout, direct API integration, webhooks, payment links or a supported commerce connector. Compatibility is confirmed in technical discovery.

Can I collect payment without a full checkout build?

Payment links are designed for that case. Create a request, share the secure link and connect the resulting status to the relevant order or invoice workflow.

How is payment security handled?

The implementation is designed to reduce unnecessary card-data exposure, apply transport security, protect credentials and support authentication or risk checks required by the approved payment route. Certification status is never implied without written evidence.

How are refunds and disputes managed?

Refund eligibility, timing, fees and dispute responsibilities are documented in the merchant schedule. Operational references keep the customer request, original transaction and resulting money movement connected.