Question 1

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 2

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 3

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 (coming soon) lets you launch without separate provider paperwork.

Question 4

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 5

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.

Integrate wallets, Connect IPS, Fonepay & bank with one tool