Use it with your agent
Talk to your agent normally. The skill loads when you mention a provider, NPR or Nepali payments, or when you’re debugging a Nepali payment signature, callback or status check. You don’t need to say “skill”.
Prompts that work well
Section titled “Prompts that work well”Add eSewa and Khalti payments to my Hono API on Cloudflare Workers with D1.
Integrate Fonepay dynamic QR for our restaurant POS.
Our eSewa callback says ES104 invalid signature. Fix it.
Add Khalti checkout to the Flutter app; the backend is FastAPI.
Set up connectIPS with our .pfx and a reconciliation job.
Name the providers and your stack when you know them. If you don’t name a provider, the skill recommends eSewa and Khalti first, then NPS or Fonepay to cover banks, connectIPS for direct bank debit and CyberSource only for card acquiring through a bank.
What the agent does
Section titled “What the agent does”The skill gives the agent this workflow:
-
Pick providers from the provider table, or recommend a set.
-
Detect the stack from
package.json,pyproject.toml,composer.json,pubspec.yaml,go.modand similar, and find where server routes and database models live. -
Install the adapters by copying the folder for your language and keeping only the providers you need. See Use the adapters directly.
-
Add persistence and routes: a
payment_attemptstable and the return handler from Production architecture, wired into your framework with Web frameworks or Mobile apps. -
Add reconciliation, so customers who pay and close the tab still get their order.
-
Test with the bundled suites, then the integration checks in Testing and go-live.
Debugging with the skill
Section titled “Debugging with the skill”The provider references list the failure modes I hit while building and testing the adapters, such as eSewa’s ES104 invalid signature, Fonepay’s date format and Khalti’s integer-paisa amounts. Paste the error and the agent checks it against the matching reference.