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 pathsA 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.
Choose the route that matches how customers buy. Method, currency and settlement availability are confirmed during merchant onboarding.
Use a hosted experience to reduce implementation scope or connect through an API when the checkout needs deeper control.
See integration pathsCreate a trackable payment request for invoices, social selling and remote orders without rebuilding a storefront.
Open the link workflowDesign consent, schedules, retries and customer notifications around repeat revenue.
Plan recurring paymentsReconcile transaction status, refunds and payout references with a clear operational record.
Understand commercial termsEvery payment moves through a sequence your finance, support and engineering teams can understand.
Payment methods, acquiring partners, currencies and settlement timing are defined in the signed merchant schedule.
Hosted checkout, APIs, webhooks, payment links and connector-supported commerce paths let the payment experience fit the operating model instead of replacing it.
Explore integrationsA payment gateway quote should make the total operating model visible, not hide behind a single percentage.
Answers for the first evaluation
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.
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.
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.
Yes. The normal paths are hosted checkout, direct API integration, webhooks, payment links or a supported commerce connector. Compatibility is confirmed in technical discovery.
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.
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.
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.