Payment Links are a no-code tool for collecting payments from your customers. Create a link in the Command Center or through the Payment Links API, share it with your customer, and they complete payment through Sonic checkout. Every payment mode Nimbbl supports is available to your customers -- UPI, cards, Netbanking, wallets, Pay Later, and more.
What Are Payment Links?
A Payment Link is a unique URL tied to a payment request. When your customer opens the link, they see the payment details you configured and can complete the transaction through Sonic checkout. Each link has its own lifecycle -- from creation through payment completion or expiration.
You can create Payment Links one at a time through the Command Center UI, in bulk via file upload, or programmatically through the API for automated workflows.
For a side-by-side comparison with Payment Pages, see the Plug and Play overview. Payment Links are one-to-one (one link per customer), while Payment Pages are reusable (one page, many customers).
Amount-Based and Product-Based Links
Every Payment Link falls into one of two categories based on what you are collecting payment for.
Amount-based links represent a fixed monetary value. You specify the amount when you create the link, and the customer pays exactly that amount. Use amount-based links for invoices, service fees, subscription renewals, or any scenario where the total is predetermined.
Product-based links let you attach one or more products to the link. Each product includes a title, description, price, quantity, tax, and optional image. The customer sees an itemized breakdown when they open the link. Use product-based links when you need to bill for specific items -- product orders, detailed service breakdowns, or multi-line invoices.
Both link types behave the same way once created: they can be shared, tracked, and managed identically. The difference is in how the payment amount is determined and what the customer sees.
Both types support expiration dates, customer notifications via SMS, email, and WhatsApp, callback URLs for custom post-payment flows, Third Party Verification (TPV), and custom metadata tags.
Expiration and Customer Notifications
Payment Links are time-bound. You set an expiration date and time when you create the link. After that point, the link automatically moves to expired status and customers can no longer make payments through it. Expired links cannot be reactivated.
When you create a link, you choose whether to notify the customer:
- Notify ON -- Nimbbl sends the link to your customer via SMS, email, WhatsApp, or any combination. You can schedule notifications for immediate or future delivery, and enable automatic reminders.
- Notify OFF -- the link is generated but no notification is sent. You share the link manually through your own channels.
Use Cases
Payment Links work well for:
- Invoicing -- send a payment link alongside or instead of a traditional invoice
- Service payments -- collect fees for services rendered
- Product orders -- share an itemized link for specific products
- Follow-up payments -- send a link to customers who abandoned checkout or have outstanding balances
- Remote payments -- collect payment from customers who are not on your website
For reusable payment collection from multiple customers, consider Payment Pages instead.
Detailed Guides
Customer Experience
Understand the end-to-end journey your customers go through when they receive and open a Payment Link -- from notification delivery through Sonic checkout to payment confirmation. See Customer Experience for the full walkthrough.
Creating Payment Links
Step-by-step instructions for creating Payment Links through the Command Center UI and the Payment Links API. Covers both amount-based and product-based links, customer notifications, expiration settings, and advanced options. See Creating Payment Links for the complete guide.
Managing Payment Links
Learn how to edit, share, and track your Payment Links after creation. Covers status transitions (created, sent, partially paid, paid, expired, cancelled), editing restrictions based on link status, and sharing options. See Managing Payment Links for all management actions.
Webhooks
Configure webhooks to receive real-time notifications when Payment Link statuses change. Eight webhook events cover the full Payment Link lifecycle, enabling you to automate downstream workflows in your systems. See Webhooks for Payment Links for event details and setup.
Field Reference
A complete reference for all Payment Link fields, organized by tab (Details, Customer, Advanced). Includes field types, required/optional status, and descriptions for every configurable option. See Payment Link Field Reference for the full table.