Payment pages
Collect one-time payments from a branded page that JPSL builds and hosts for you. You need no website, app or integration.
A payment page is a web page in your branding that ends in Jio Payment Solutions Limited (JPSL) checkout. You share one link — over WhatsApp, SMS, email or social media, or printed as a QR code — and anyone who opens it can pay you.
JPSL builds, hosts and maintains the page. You need no website, no app and no developer work.
Behind the page is the standard JPSL payment gateway. Payment methods, refunds, settlements, reconciliation and the dashboard work exactly as they do for your other payments — nothing changes on the payment side.
See a demo
Open the demo payment page to see what your customers see. It runs in the UAT test environment, so no real money moves.
When to use a payment page
| You want to | Use |
|---|---|
| Collect from anyone, through one link that stays the same | Payment pages |
| Request a set amount from a specific customer | Payment links |
| Take payments on your own website or app | Hosted checkout |
| Collect recurring payments | Subscription Hub |
A payment page suits:
- Businesses with no website or app, such as clinics, coaching classes, salons and consultants
- Event registrations — one event, one page, one link
- Donations to trusts, NGOs and alumni bodies
- One-time fees and dues for schools, societies and associations
- Payments you take today by cash, cheque or bank transfer
- Taking payments while your full integration is still being built
What your customer sees
- They open your link or scan your QR code.
- Your page opens, with your branding, details and instructions.
- They enter the amount, if you let them choose it, and any details you ask for.
- They pay through the standard JPSL checkout, using the payment methods enabled on your merchant account.
Your customer has nothing to download and no account to create.
What you can set
| Item | Options |
|---|---|
| Branding | Your logo and brand colours |
| Images | Banners and images, placed where you choose |
| Text | Page heading, description and instructions |
| Policies | Terms, refund policy and disclaimers shown to the payer |
| Support | The contact details shown to the payer |
| Amount | A fixed amount, or an amount the customer enters |
| Customer details | The fields the customer fills in before paying |
Limits
| Limit | What it means for you |
|---|---|
| One page per merchant ID | For separate products, branches or events, keep the page general and ask the customer for the amount and a reference |
| JPSL domain only | The page runs on a JPSL domain. It cannot run on your own domain |
| Link as issued | JPSL does not shorten the link. Use your own link shortener if you want a shorter one |
| Changes go through JPSL | You cannot edit the page yourself. JPSL makes every change |
| Changes take a release cycle | Each change is built, tested in UAT and signed off by you before it goes live. Plan changes ahead |
| One-time payments only | For recurring payments, use Subscription Hub |
If you need several pages, your own domain or self-service editing, use payment links or hosted checkout instead.
Get a payment page
- Request it. Contact your JPSL relationship manager.
- Send your requirements. Use the checklist below. A complete set up front is the fastest route to going live.
- Review the test page. JPSL builds your page and shares a UAT link. Check it and make test payments.
- Sign off. Confirm in writing that the UAT page is correct. JPSL does not release a page without your sign-off.
- Go live. JPSL releases the page to production and shares the live link.
- Share the link. Send it to your customers, or print it as a QR code on a standee, invoice or poster.
What to send
| Area | Send |
|---|---|
| Account | Your business name, merchant ID, business category and what the page is for |
| Branding | A high-resolution logo, with a transparent background if you have one. Your brand colours and any brand guidelines |
| Images | Banners and images, with where each one goes |
| Content | The final, proofread heading and body text. Terms, refund policy and disclaimers. The support contact to show payers |
| Payment | A fixed amount or a customer-entered amount. The customer details to capture. The payment methods to offer |
| Contact | The person who will test the UAT page and sign it off |
Requirements that arrive late or change after the build are the most common cause of delay.
Change a live page
Send the change to your JPSL relationship manager. It goes through the same build, UAT and sign-off steps as the first release, so the live page stays as it is until you approve the new version.
Next steps
- Payment links — request a specific amount from a specific customer
- Hosted checkout — take payments on your own website or app
Updated about 6 hours ago