paybridgenp.com valid
PayBridgeNP
Developer documentation for accepting eSewa, Khalti, and Fonepay payments in Nepal with PayBridgeNP.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.paybridgenp.com/llms.txt
- llms-full.txt
- https://docs.paybridgenp.com/llms-full.txt
- Sections
- 1
- Links
- 145
- Size
- 29937 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-26T09:26:25.020Z
- Last checked
- 2026-10-26T09:26:27.264Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T09:26:25.024Z. Cached copy · Source on paybridgenp.com
# PayBridgeNP
> Developer documentation for accepting eSewa, Khalti, and Fonepay payments in Nepal with PayBridgeNP.
> ## Agent Instructions
> Use hosted checkout for a new payment integration unless the user explicitly needs an SDK or Direct QR flow.
> Keep secret API keys on the server. Never place an sk_test_ or sk_live_ key in browser or mobile code.
> Never treat a browser return URL as proof of payment. Verify a signed webhook and confirm status, amount, and currency on the server before fulfillment.
> Fonepay has no sandbox. A Fonepay payment made from a sandbox project uses the merchant's real Fonepay account and moves real money within the documented caps.
> Do not recommend direct integration with Mobile SDK device endpoints. Use the PayBridgeNP Mobile SDK and the merchant-facing session creation API.
- [Accept eSewa, Khalti, and Fonepay with one API](https://docs.paybridgenp.com/home.md): PayBridgeNP developer documentation. Accept eSewa, Khalti, and Fonepay payments in Nepal through one API, with sandbox testing, signed webhooks, SDKs, and store plugins.
- [How PayBridgeNP works](https://docs.paybridgenp.com/introduction.md): Learn how checkout sessions, provider settlement, API keys, sandbox testing, and payment confirmation fit together.
- [Quickstart](https://docs.paybridgenp.com/quickstart.md): Accept your first payment in under 5 minutes.
- [Sandbox testing](https://docs.paybridgenp.com/guides/sandbox-testing.md): Test eSewa and Khalti safely, and understand Fonepay's real-money exception.
- [Plans and limits](https://docs.paybridgenp.com/guides/plans-and-limits.md): What Free, Growth, Pro, and Enterprise include - volume, projects, team seats, SMS receipts, retention, and feature gates.
- [Confirming a payment](https://docs.paybridgenp.com/guides/confirming-payments.md): Know for certain when a payment succeeded. Use webhooks as your source of truth, and verify server-side before you release value.
- [Webhook Verification](https://docs.paybridgenp.com/guides/webhook-verification.md): Verify webhook signatures to ensure events are genuinely from PayBridgeNP.
- [Idempotency](https://docs.paybridgenp.com/guides/idempotency.md): Make retries safe - avoid duplicate payments when network failures occur.
- [Sync with provider](https://docs.paybridgenp.com/guides/payments-sync.md): Check a payment's current status with Khalti, eSewa or Fonepay, and catch refunds issued from the provider's own merchant panel.
- [Payment Links](https://docs.paybridgenp.com/guides/payment-links.md): Create no-code hosted payment pages and share them with customers.
- [Payment Buttons](https://docs.paybridgenp.com/guides/payment-buttons.md): Add a checkout button to any website with a single script tag - no backend required.
- [Embedded Checkout](https://docs.paybridgenp.com/guides/embedded-checkout.md): Open the checkout in an overlay on your own page instead of redirecting the customer to a payment page.
- [Customer details at checkout](https://docs.pa
…Machine-readable: GET /v1/resolve?q=paybridgenp.com · GET /v1/domain/paybridgenp.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage paybridgenp.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for paybridgenp.com:
1. POST https://agentwebmap.com/v1/sites/paybridgenp.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://paybridgenp.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/paybridgenp.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/paybridgenp.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.