Payment pages · no website needed
One page, shared once, paid by many
A payment page is a small hosted page for one purpose: a workshop, a fee, a donation drive. You set it up once, share it everywhere, and every payment arrives with the details you asked for.
Weekend pottery workshop
Sat–Sun, 10am–4pm · materials included · Illustrative
Pay ₹1,500
UPI · cards · net banking
Payments, by the page's fields
- Ritika S.₹1,5001 seat · apron M · receipt sent
- Omar K.₹2,8002 seats · apron L, S · receipt sent
- Neha P.₹1,5001 seat · apron S · receipt sent
Page, link or checkout?
All three take payments on a hosted or built-in screen. The difference is who they're for and how often they're used.
| Payment page | Payment link | Checkout | |
|---|---|---|---|
| Made for | Many payers, one purpose | One payer, one amount | Your own website or app |
| Created | Once, reused | Per payment | Built into your flow |
| Amounts | Fixed, choices or payer-entered | Fixed | From your cart |
| Collects extra details | Yes, your own fields | Usually not | Your own forms |
| Needs a website | No | No | Yes |
| Typical use | Events, fees, donations | Invoices, dues | E-commerce |
One payer, one amount: payment links. Your own checkout: collection API.
What makes a page people finish
- 1
What it's for
A clear title and two lines: what, when, what's included. Payers who can't tell what they're paying for leave.
- 2
The amount
Say exactly what each option buys. If there's a fee on top, show it before the pay button, not after.
- 3
Only the fields you'll use
Each field should answer a question you'll act on: a name for the list, a size for the order.
- 4
Familiar methods
UPI first on phones, with cards and net banking available; payers expect choice.
- 5
What happens next
A confirmation screen and a receipt that say what they paid for and when it happens.
Fixed, a choice, or up to the payer
The amount setting decides how much checking you'll do afterwards. A fixed amount is simplest to reconcile. A choice between amounts works for tiers or quantities. A payer-entered amount suits donations and contributions, but needs a sensible minimum and a clear label, or you'll get ₹1 test payments and typos with an extra zero.
Which amount options are available on your Peneu setup is confirmed during onboarding.
Fixed
One price: a course fee, a ticket.
Reconciling: Every payment should match; anything else is a question.
Choice
Tiers or quantities: 1 seat, 2 seats, a family pass.
Reconciling: Match by option; count seats from the options chosen.
Payer enters
Donations, contributions, part-payments.
Reconciling: Set a minimum; watch for mistyped amounts.
Your own fields: ask only for what you'll use
Worth asking
- The attendee's or student's name, if different from the payer
- A phone number or email for the confirmation
- An option you'll act on: a size, a batch, a session
- A reference the payer already has, such as a roll number or member ID
Leave out
- Card details: the payment step handles them, never your fields
- Passwords, PINs or OTPs, ever
- Full identity numbers, unless a law requires you to collect them; see Aadhaar verification for why this is sensitive
- Anything you'd collect “just in case”
Every extra field loses some payers and adds personal data that you then have to protect and keep only as long as you need it.
Sharing one page everywhere
As a link
In messages, emails and social posts. The same link for everyone.
As a QR code
On a poster, a desk or a flyer, so people can pay from their phone on the spot.
As a button
On a website or blog you already have, pointing to the page.
In a bio or profile
For businesses that sell mainly through social media.
Which sharing options (QR, embeddable button) Peneu provides for pages is confirmed during onboarding.
After someone pays
Three things should happen within seconds: the payer sees a confirmation that repeats what they paid for, they receive a receipt, and you're told, with their field answers attached. If any of the three is missing, payers pay twice to be safe, or write in to ask.
When the event is full or the fee deadline passes, close the page. A deactivated page with a clear message is better than refunding people who paid for something that no longer exists.
Refunds for cancellations follow your published policy; the mechanics are in the refunds guide.
Reconciling by field
Because every payment carries the payer's answers, the page doubles as your list. Export the payments and group them by field to see who's coming, which sizes to order, or which batch each student joined, and match the total against what's been settled to you.
| Apron size | Seats | Collected |
|---|---|---|
| S | 7 | ₹10,500 |
| M | 11 | ₹16,300 |
| L | 5 | ₹7,300 |
Illustrative. See reconciliation for matching against settlements.
Setting up a page in an afternoon
- 01
Write the two lines
What it's for, when it happens, what's included, and who to contact with questions.
- 02
Set the amounts
Fixed, options or payer-entered, with a minimum if payers choose.
- 03
Add only the fields you'll use
Mark which are required. Test the form on a phone.
- 04
Write the confirmation and receipt
What they paid for, what happens next, and your refund policy in a sentence.
- 05
Pay it yourself
Make a real small payment and refund it, so you see exactly what payers see.
- 06
Share, then watch the first day
Early payments show quickly whether a field is confusing or an option is missing.
A receipt that answers the next question
The receipt is the only thing most payers keep. A good one means they never need to write to you to ask whether their payment went through, what it was for, or how to get a refund.
If you issue tax invoices for what you sell, the receipt isn't a substitute for one. What you're required to issue is a question for your tax adviser.
- Your business name and a contact for questions
- What they paid for, including the option they chose
- The amount, date and time
- A payment reference they can quote
- The answers they gave in your fields
- What happens next, and your refund policy in one line
Most payers are on a phone
A page shared on social media or by message is opened on a phone almost every time, often on a slow connection, sometimes by someone who's never paid you before. Write and test for that person.
- Keep the description short enough to read without scrolling past the amount.
- Use the right keyboard for each field: numbers for phone numbers, email for email.
- Label every field clearly, not just with placeholder text that disappears when they start typing.
- Make the pay button say the amount, so there's no doubt what happens when they tap it.
Public pages attract misuse
A page anyone can open is also a page anyone can abuse. The most common problem is card testing: someone with a list of stolen card numbers uses a payer-entered amount to try them one after another with tiny payments. The payments are small; the chargebacks and the attention from your provider are not.
- Set a sensible minimum for payer-entered amounts.
- Watch for bursts of small payments, especially failed ones, and deactivate the page if you see them.
- Close pages you no longer use instead of leaving them live.
What people build with a page
| Use | Amounts | Fields worth adding |
|---|---|---|
| Workshops and events | Fixed or by ticket type | Attendee name, session, dietary needs |
| School and coaching fees | Fixed per term, or by class | Student name, class, roll number |
| Donations and fundraisers | Payer-entered, with suggestions | Name for the receipt, whether to stay anonymous |
| Consultations | Fixed per session | Preferred slot, what it's about |
| Freelancers and creators | Fixed per product or package | Delivery email, requirements |
Payment page questions
Can I use one page for several events or batches?
You can, with a field or amount option that says which one. For events with different dates, prices or capacities, separate pages are usually clearer for payers and easier to close when each fills up.
Can a payer pay again on the same page?
Yes. A page is reusable by design, so the same person can pay more than once: for a second ticket, say. If a repeat payment would be a mistake for your use, say so on the page and watch for duplicates.
What is a payment page?
A payment page is a hosted web page that anyone with the link can use to pay you. It describes what the payment is for, offers one or more amounts, collects any details you need, and takes the payment. Unlike a payment link, one page is shared with many payers.
Do I need a website to use a payment page?
No. The page is hosted for you, so you can share its link on social media, in messages, on a poster as a QR code, or add it as a button to a site you already have.
What's the difference between a payment page and a payment link?
A payment link is usually created for one payer and one amount, such as one invoice. A payment page is created once and reused by many payers, often with amount choices and fields to fill in, such as registrations or donations.
Can payers choose their own amount?
Pages commonly support a fixed amount, a choice between amounts, or an amount the payer enters, which suits donations and contributions. Which options your Peneu setup offers is confirmed during onboarding.
What should I avoid asking for on a payment page?
Anything you don't need, and anything sensitive: card details (the payment step handles those), passwords, full identity numbers or health information. Every extra field loses some payers and adds data you then have to protect.
How do I close a page when an event is full?
Deactivate it or set an end date, so late payers see a clear message instead of paying for a seat that doesn't exist. Whether pages can close automatically by date or number of payments is confirmed during onboarding.
Start collecting with a page
Tell us what you're collecting for. We'll walk through the page, fields and reports that fit.
Last reviewed . Examples, amounts and screens marked illustrative are not Peneu figures.