Hosted checkout
Send the customer to a controlled payment experience while your server keeps the order reference and verifies the final status.
Accept LKR payments, settle locally, and connect checkout with one merchant integration.
LKR firstCheckout and merchant records built around local currency.
Local routesCards, wallets, QR, and bank methods reviewed per merchant.
Local settlementClear payment states before funds reach the merchant operation.
Designed around local operations
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.
Open a hosted checkout, payment link, platform order, or server API session with a merchant reference.
Use server side verification before an order, booking, or account is marked as paid.
Keep refunds, support cases, and settlement records tied to the original transaction.
Use the smallest integration that still gives your business a verified payment state.
Send the customer to a controlled payment experience while your server keeps the order reference and verifies the final status.
Collect against an invoice, remote order, service, or sales conversation without building a full cart.
Review WooCommerce and Shopify needs, order state mapping, return paths, and go live testing.
Build custom payment creation, signed event handling, status verification, refunds, and reconciliation.
Explore integrationLocal payment choice
Different Sri Lankan businesses need different routes. The merchant review confirms what is available before the checkout is designed around it.
Start accepting paymentsApproved debit and credit card routes for local and eligible international customer payments.
Local wallet and LankaQR requirements reviewed against the merchant journey.
A direct route for invoices, remote orders, and businesses without a complete online store.
Repeat payment requirements scoped around authorization, retries, cancellation, and account state.
Commercial model
Pricing is prepared from the merchant category, payment methods, expected volume, average order value, refunds, integration work, and settlement schedule.
Review pricing inputsKeep sensitive credentials and payment decisions off the customer browser.
Hosted payment fields, controlled credentials, encrypted transport, server verification, validated events, and traceable references reduce avoidable ambiguity.
Merchant questions
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.
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.
Card, local wallet, QR, and bank based routes may be reviewed for an eligible merchant. The approved mix depends on the business category, transaction model, customer flow, and applicable service arrangement.
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.
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.
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.
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.
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.
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.
No matching questions. Try a different word.