Skip to main content
Payment links are shareable URLs that let customers pay without any code on your side. Each link points to a hosted PayBridgeNP checkout page - you configure the amount, description, and expiry in the dashboard, then share the URL anywhere.

Use cases

  • Invoicing - send a payment link in an email or SMS
  • Donations - embed a payment link on a website or social media
  • Event tickets - sell a fixed number of seats by setting a max use limit
  • Subscriptions alternative - recurring manual billing for small businesses
  1. Go to Payment Links in the dashboard
  2. Click New Payment Link
  3. Configure the link:
  1. Click Create - PayBridgeNP generates a URL like:
On a link’s page in the dashboard, Send delivers the link to one customer: The message wording is fixed: you choose who gets it and the language (English or Nepali), not the text. Some rules keep it safe for your customers:
  • Only the owner and admins can send, and only once your account email is confirmed.
  • Only an active link that customers can pay can be sent: in live mode the project needs a connected payment provider. A link made for one customer (with a customer phone or email set) can only go to that customer.
  • Each link can be sent 5 times a day, each recipient can get 3 sends a day, and an account can send 200 a day.
  • An email address that bounced or reported spam before is not sent to again.
  • Messages carry your project name (or business name). A name that looks like PayBridgeNP or a payment app (eSewa, Khalti, Fonepay and similar) is not used for sending.
  • A link whose title or project name contains a web address (https://, www., or a domain such as example.com) cannot be sent; the only address in the message is the payment link.
  • Test mode never delivers. A send from a sandbox link is logged so you can check it, but no real phone or inbox receives it.
Before you send, the dialog shows the SMS text (or the email’s subject and sender) and what it uses from your plan. It also lists the link’s recent sends and what happened to each, with phone numbers and emails masked.

Tracking payments

Payments made through a link fire webhooks (payment_link.paid and payment.succeeded), which are the reliable way to know a link has been paid. See Confirming a payment for the webhooks-first pattern and how to verify a payment server-side.

Webhooks

Payment link payments fire a payment_link.paid event (and also payment.succeeded). The webhook payload includes the metadata attached to the payment link, a payment_link_id field, and - when address collection is enabled - a customer_address object. Set up a webhook endpoint in the dashboard to receive these events. You can disable or re-enable a link at any time from the dashboard. Payment links have a full API - see Create a payment link. Beyond a fixed amount, a link can accept an open amount within a range (minAmount/maxAmount) so the customer enters what they pay, and it can send the customer to your own page after payment with redirectUrl. You can also create and manage links from the dashboard.

After payment

By default the customer stays on a PayBridgeNP confirmation page that shows the amount and offers a receipt to download. Set a redirectUrl (or choose Redirect to your website in the dashboard) to send them to your own page instead: after a short confirmation, they arrive with session_id, status and payment_id added to the URL. Treat those as a hint and confirm the payment through the API or a webhook before fulfilling the order.

Limitations

  • A link’s provider set and currency (NPR) are fixed once created