Sri Lanka LKR merchant settlement infrastructure

Built for the way Sri Lanka pays

Accept LKR payments, settle locally, and connect checkout with one merchant integration.

Start accepting payments Explore integration
Relief map showing payment gateway sri lanka routes for local merchant settlement

LKR firstCheckout and merchant records built around local currency.

Local routesiPay, PayGo, bank transfer, and QR reviewed per merchant.

Local settlementClear payment states before funds reach the merchant operation.

Designed around local operations

One payment layer from checkout to reconciliation

A local gateway should understand the whole merchant route, not only the payment button.

Payment methods, customer currency, verification, refunds, settlement files, and support all shape whether a checkout works in practice. This service keeps those steps connected for eligible businesses operating in Sri Lanka.

  1. 1

    Create the payment

    Open a hosted checkout, payment link, platform order, or server API session with a merchant reference.

  2. 2

    Confirm the result

    Use server side verification before an order, booking, or account is marked as paid.

  3. 3

    Operate after payment

    Keep refunds, support cases, and settlement records tied to the original transaction.

Choose how customers reach the gateway

Use the smallest integration that still gives your business a verified payment state.

Hosted checkout

Send the customer to a controlled payment experience while your server keeps the order reference and verifies the final status.

Best for websites and apps

Payment links

Collect against an invoice, remote order, service, or sales conversation without building a full cart.

Ecommerce

Review WooCommerce and Shopify needs, order state mapping, return paths, and go live testing.

Server API

Build custom payment creation, signed event handling, status verification, refunds, and reconciliation.

Explore integration

Local payment choice

Offer the methods that fit the merchant

Different Sri Lankan businesses need different routes. The merchant review confirms what is available before the checkout is designed around it.

Start accepting payments
iPay

A Sri Lankan digital payment app route for LKR deposits, enabled per approved project.

PayGo

A local digital payment service reviewed against the merchant journey and current limits.

Bank transfer and QR

LKR bank routes and QR scan payments where the project configuration returns them as active.

Payment links

A hosted payment page created from the server for invoices, remote orders, and businesses without a complete online store.

Commercial model

A written offer, not a guessed public rate

Pricing is prepared from the merchant category, payment methods, expected volume, average order value, refunds, integration work, and settlement schedule.

Review pricing inputs

Keep sensitive credentials and payment decisions off the customer browser.

Security starts with a clear source of truth

Hosted payment fields, controlled credentials, encrypted transport, server verification, validated events, and traceable references reduce avoidable ambiguity.

  • Verify approved payment states before fulfilment.
  • Keep payment and refund references tied to the order.
  • Test pending, declined, retry, timeout, and reversal paths.
Review the security approach

Merchant questions

What to know before onboarding

Is this a commercial payment gateway service?

Yes. The site presents a payment gateway service for qualified merchants in Sri Lanka. It covers checkout, payment links, verified payment status, refunds, and settlement operations. It is not a consulting practice.

Can settlements be made in LKR?

The service is designed around LKR merchant operations and settlement to eligible Sri Lankan bank accounts. The exact schedule, limits, banking route, and reconciliation format are confirmed in the merchant offer.

Which Sri Lankan payment methods are available?

LKR routes that can be reviewed for an eligible merchant include iPay, PayGo, local bank transfer, and QR payments. The approved mix depends on the business category, transaction model, customer flow, and applicable service arrangement.

Do I need a registered business?

Merchant onboarding normally requires verified business and owner information, a clear product or service, a working customer journey, and supporting documents. The exact eligibility checklist is provided after the initial review.

Can I connect WooCommerce or Shopify?

WooCommerce and Shopify requirements can be reviewed during onboarding. Plugin availability, checkout behavior, order status mapping, and production approval are confirmed for the merchant before launch.

Is there an API for a custom website or app?

A custom integration can use a server API, hosted checkout, signed event handling, and status verification. Credentials and production endpoints are supplied only after technical and merchant approval.

How is pricing calculated?

Pricing depends on payment methods, monthly volume, business category, average order value, refunds, integration scope, and settlement requirements. The merchant receives written commercial terms before onboarding proceeds.

How quickly can the gateway go live?

Timing depends on complete documents, business review, integration choice, testing, and production approval. The site does not promise a fixed launch date before those steps are complete.

Can the available method list change after launch?

Yes. Route availability and the minimum and maximum amounts per method are returned by the platform and can change. The merchant should query the availability endpoint on a schedule and hide a route that is not currently active instead of hardcoding the checkout.

Is there a test environment before production?

A separate test project with its own credentials is used to validate the flow before live customers are onboarded. Test keys are replaced with production keys at go-live.

Can customer payouts run through the hosted checkout?

No. The hosted payment page covers incoming payments only. Payouts and withdrawals are a separate server-side integration with their own status notifications.

Are funds held back as a rolling reserve?

The operating model does not apply holds or rolling reserves. Settlement is requested from the merchant account, and the applicable timing is set in the commercial terms rather than published here.

What security controls should the integration use?

The intended model uses encrypted transport, controlled credentials, hosted payment fields where appropriate, server side verification, validated events, and traceable payment references. Formal certifications are confirmed separately and are not implied here.