Charge without a booking
Not everything you sell goes through your storefront's search. A package you put together by hand, a balance on an invoice, a deposit, a service arranged over the phone — a payment link collects money for any of those.
You create the link in the panel, send the address to your customer, and the payment arrives under Incoming Payments.
Choose the right kind of link
Payment Links → New Payment Link asks which kind you want. The choice cannot be changed later, so pick deliberately.
| Kind | The payer | Use it for |
|---|---|---|
| Fixed amount | Pays exactly what you set | An invoice, a specific package, a known balance |
| Payer-defined | Types their own amount, optionally within a range you set | Deposits, top-ups, open donations |
| Custom plans | Pays your base amount, plus the price of any plans they pick from the services you build, at most one per service | Tiered extras on top of a base price: insurance levels, package upgrades |
Fixed and payer-defined links are a single short form. A custom-plans link opens a four-step builder.
The custom-plans builder
Four steps, in order:
| Step | You define |
|---|---|
| Basics | Title, service type, currency, and the base amount, which every payer pays and percentage plans are calculated from |
| Services & plans | The services the payer can choose from, their feature lists, and the plans under each |
| Payment page | What the payer sees — a detail card built from a template, plus optional rich content |
| Checkout settings | What to collect from the payer, when the link expires, whether it is single use |
Services and plans
A service is a thing you are offering. It carries a title, a feature list, and optional header and background images. A service can have at most 50 features, a link at most 20 services, and a service at most 20 plans.
A plan is a purchasable option within that service. Each plan has a title, a description, a price, and up to 30 features ticked from the service's own list. A plan's price is a whole number, at least 1, and either:
- Fixed price: a flat amount, or
- Percent of base amount: a percentage, up to 100, of the base amount from step 1.
The payer picks at most one plan per service, and picking is optional. Each plan they pick is added to the base amount.
The feature list is the reference: a plan can only include features the service defines, so the comparison between plans always lines up.
Every service needs at least one plan.
The payment page
The service type you picked in step 1 — flight, hotel, activity, visa, tour, car rental, transfer, package or custom — decides what the detail card looks like. Choose one and you get a structured form for exactly that kind of service:
| Service type | What you fill in |
|---|---|
| Flight | Trip shape and airline, route, schedule, cabin and baggage, conditions |
| Hotel | Property and location, stay dates, room and board, inclusions |
| Activity | The experience and where it takes place, participants, inclusions |
| Visa | Application details, timings, required documents |
| Tour | Title and length, logistics, itinerary highlights |
| Car rental | Vehicle, pick-up and return, rental terms |
| Transfer | Vehicle, route, pick-up time, waiting policy |
| Package | Several of the above, combined into one card |
A live preview shows the card as you type. Choosing Custom as the service type skips the structured card.
Custom page content is a separate optional rich-text area for anything the structured card does not cover.
Checkout settings, on every kind of link
These decide the payer's experience, and two of them interact.
Payer information to collect
Tick what the payer must fill in before paying: first name, last name, email, phone, passport number, national code, birth date, gender, citizenship, address.
Ask for what you genuinely need. Every extra field is friction.
Payment method
| Option | Behaviour |
|---|---|
| Standard (wallet) | The payer settles from their wallet balance and tops it up only for the shortfall |
| Gateway only | The payer always pays the full amount at a payment gateway. Refused unless your platform has a gateway in the link's settlement currency: rial for IRR, dollar for anything else |
Access
| Option | Behaviour |
|---|---|
| Sign-in required | Only signed-in customers can open and pay the link |
| No sign-in | Anyone with the address pays as a guest |
A guest link must use Gateway only, and must collect an email or a phone number. Without a sign-in and without a contact field, you would have no way to reach the payer afterwards. The form refuses to save otherwise.
Expiry and single use
- Expiration date — optional, and must be in the future. Leave empty for no expiry.
- Single use — the link is consumed after the first successful payment.
Use single use for anything addressed to one customer. A fixed-amount link with no expiry and no single-use flag can be forwarded and paid repeatedly.
After you create it
The panel shows the link address immediately, with a Copy button. Send it however you like.
The list shows every link with its status:
| Status | Meaning |
|---|---|
| Active | Payable |
| Disabled | You switched it off; still visible to you, not payable |
| Consumed | A single-use link that has been paid |
| Expired | Past its expiration date |
Filter by status, and sort by newest, oldest, amount low to high or amount high to low.
Per link you can view, edit, disable (active links only) and delete. Neither can be undone: a disabled link stays in your list but cannot be switched back on, and a deleted one is gone.
Tracking the money
Payments against your links arrive in Incoming Payments, with the payer's details, the amount, the tracking code and when it was verified. Filter by status (Pending, Success, Canceled), and sort by newest, oldest or amount high to low.
The money itself goes to your platform wallet, unless the payer paid through one of your dedicated gateways, in which case it is already in your own merchant account. A link in IRR settles to your platform's rial balance.
A payer who was not signed in shows as Guest.
Scenarios
Invoice a corporate client for a trip you arranged
Fixed amount, no sign-in, gateway only, collect first name, last name and email, single use, expires in 7 days. Send the link with your invoice.
Take a deposit and the balance later
Two payer-defined links, or a fixed-amount link for the deposit and a second for the balance. Mark each single use.
Offer travel insurance at three levels
Custom plans, with the trip price as the base amount. One service called Travel insurance, a feature list covering everything any level includes, then Basic, Standard and Premium plans each ticking the features they cover. The payer pays the trip, plus the level they pick, if any.
Offer an optional extra priced off the trip
Custom plans, with the trip value as the base amount and a plan priced as a percent of base amount. The payer always pays the base amount; the plan adds its percentage on top only if they pick it.
Someone paid twice
Check Incoming Payments for both. To stop it happening again, mark customer-specific links single use.
Important notes
- The link kind is fixed at creation. To change from fixed to payer-defined, create a new link.
- Disabling and deleting are both final. A disabled link stays in your list; to take payments again, create a new one.
- A link with no expiry and no single-use flag lives forever and can be forwarded to anyone.
- Guest links need gateway-only plus a contact field — enforced when you save.
- Payment link payments are not bookings. They produce no ticket or voucher, and Order Notifications sends only the order-placed email for them.
Related
- Payment Links · Incoming Payments
- Get paid — gateways, which payment links also use