Question 1

What is SkyPay?

Accepted Answer

SkyPay is a Nepal payment platform. You accept Khalti, eSewa, Connect IPS, Fonepay, and bank payments through one checkout experience, manage them in a merchant dashboard, and stay updated through the SkyPay business app — without building separate integrations for every wallet and bank.

Question 2

Why do I need SkyPay instead of integrating Khalti or eSewa myself?

Accepted Answer

Each provider has its own APIs, callbacks, and edge cases. SkyPay gives you one checkout link, one payment status format, a dashboard, and phone notifications. You save weeks of engineering and still offer the rails customers already use.

Question 3

Do I need to build my own business app for payment alerts?

Accepted Answer

No. SkyPay’s business app is built for merchants — you get payment notifications on your phone when customers pay. That means you don’t have to invent a custom ops app just to know who paid and when.

Question 4

Can I accept multiple Nepal payment rails with a single integration?

Accepted Answer

Yes. SkyPay routes customers to Khalti, eSewa, Connect IPS, Fonepay, or bank transfer from one checkout URL. You integrate once — redirect, verify, fulfill — regardless of which rail the customer chooses.

Question 5

How long does SkyPay integration take for developers?

Accepted Answer

Most teams ship a working flow in under 10 minutes: generate a checkout link with your API key, redirect the customer, then call the verify endpoint from your backend before fulfilling the order.

Question 6

Do I still need provider merchant accounts?

Accepted Answer

In API Mode, you connect your own provider credentials (for example Khalti and eSewa) in the SkyPay dashboard. In Manual Mode you can start without provider merchant APIs. Assisted Mode lets you launch with SkyPay-managed provider credentials where available.

Question 7

Why not integrate each provider directly?

Accepted Answer

Direct integrations mean separate SDKs, callback formats, and verify logic per provider. SkyPay normalizes checkout and verification so your backend handles one response shape — less code to maintain when you add or change rails.

Question 8

Is server-side payment verification required?

Accepted Answer

Yes — always verify on your server after redirect and before fulfillment. SkyPay exposes a single GET /payments-verify/{code} endpoint that returns a consistent status across wallets, Connect IPS, Fonepay, bank, and manual payments.

Question 9

Does SkyPay support webhooks?

Accepted Answer

Yes. Configure webhook endpoints in your merchant dashboard to receive real-time payment.completed, payment.failed, payment.waiting, and other events. For Manual Mode, webhooks are how you fulfill when the customer has already left checkout — see skypay.dev/guides/manual-mode.

Question 10

How does SkyPay protect my provider credentials?

Accepted Answer

Merchant provider secrets, SkyPay credentials, and webhook signing secrets are encrypted at rest — never stored as plain text. API keys are hashed, and the dashboard masks secrets in the UI. Always verify payments on your server before fulfilling an order.

Accept Khalti, eSewa & bank payments — without building it all yourself