Plan your GatewayRoot integration
See the intended website payment journey, what a merchant will need, and how the dashboard is organized. Technical API specifications will be published when the platform is ready.
Overview
GatewayRoot is planned to sit between your website and supported Nepali payment options. A customer begins payment on your site, chooses a method, and returns to a result that your site can use after verification. The merchant dashboard is intended to show payment and customer records in one place.
Planned integration steps
- Create a merchant workspace
Set up your business profile and the website that will accept payments.
- Choose payment methods
Enable eligible methods after the required merchant onboarding and gateway approvals.
- Connect your checkout
Send a payment request from your server using the future GatewayRoot integration. Keep credentials on the server, away from public browser code.
- Verify the payment result
Confirm the final status through a trusted server-side verification flow before fulfilling an order.
- Review dashboard records
Check transaction references, amounts, methods, statuses and associated customers.
Planned payment methods
Fonepay
Integration availability and requirements will be announced at launch.
NepalPay
Integration availability and requirements will be announced at launch.
eSewa
Integration availability and requirements will be announced at launch.
Khalti
Integration availability and requirements will be announced at launch.
Information in a payment record
| Field | Purpose |
|---|---|
| Reference | Identifies a payment in your records. |
| Customer | Links the payment to a customer or order. |
| Method | Shows which payment option was selected. |
| Amount | Shows the requested payment in NPR. |
| Status | Indicates the result after verification. |
What is available today?
You can explore the website, sign-up screens and a dashboard with clearly labeled sample data. Account creation, gateway connection, payment collection, transaction verification and password recovery require a backend and are not active yet.
Explore the static demo →