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 pathsBuilt 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.
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.
Payment links
Create a trackable payment request for invoices, social selling and remote orders without rebuilding a storefront.
Open the link workflowRecurring billing
Design consent, schedules, retries and customer notifications around repeat revenue.
Plan recurring paymentsSettlement control
Reconcile transaction status, refunds and payout references with a clear operational record.
Understand commercial termsSee the transaction. Not just the result.
Every payment moves through a sequence your finance, support and engineering teams can understand.
- 01InitiateCustomer selects a method
- 02AuthenticateRequired checks are presented
- 03AuthorizeThe payment is approved or declined
- 04SettleFunds follow the agreed schedule
- 05ReconcileRecords connect back to the order
Which LKR routes are active, the amount limits behind them and the settlement arrangement are defined in the signed merchant schedule.
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 how a settlement is requested
- Exceptions
- Refund, dispute and cross-border conditions
- Implementation
- Hosted, API or connector scope
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?
For Sri Lanka the working set is LKR: iPay, PayGo, local bank transfer and QR payments. Availability is confirmed after the merchant profile and target markets are reviewed, and the signed schedule records the approved routes, settlement currency and payout account.
Can the approved method list change later?
It can. Each route carries its own minimum and maximum amount and can be switched off temporarily. The platform exposes current availability and limits programmatically, so the checkout should read that list on a schedule instead of showing a method that cannot take the payment.
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 merchant keeps customer payment details out of its own systems, requests are signed with a private key over encrypted transport, credentials stay server-side, and the final payment state is confirmed from a verified notification rather than the browser. Certification status is never implied without written evidence.
Is there a sandbox before production?
Integration work starts on a separate test project with its own key and project identifier. Those credentials are swapped for production values once success, failure, pending and duplicate-notification handling have all been exercised.
Are payouts part of the same integration?
No. Collecting money and sending it out are two different flows. A hosted checkout covers incoming payments; withdrawals to customers run through the server API with their own notifications and their own limits.
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.