Request a payment, receive the receipt, confirm

The assistant starts the payment

When a customer says they want to buy, the assistant opens the same payment step for that offering, so nobody has to hunt for a button.

Send a payment request from the panel

From the payments page the team picks a customer and an offering; the same payment message with methods and receipt step goes to their chat.

Five kinds of payment request

Ask for a full payment, a deposit, the balance, an instalment or a custom amount; the amount and the kind are shown in the message and on the pay page.

• Kinds: full, deposit, balance, instalment, custom amount
• Example line: “Deposit 30 %”, “Instalment 2 of 3 — due …”

Advanced payments

Request any amount with your own title

Without any offering set up, type an amount and a title; the request reaches the customer with “open the pay page” and “pay in the chat” buttons.

Advanced payments

Pay for bookings, orders and services

Requests are not only for offerings: a booking's deposit or an order's amount is paid the same way, and each customer only sees their own.

• Can be paid: an offering, a booking deposit, a shop order, a custom request

Advanced payments

Only the methods that fit are shown

Methods are filtered by currency, the business country, the amount and buy-now-pay-later rules; a gateway that does not take the currency never appears.

• Based on: currency, business country, minimum and maximum amount, buy-now-pay-later rules, cash-on-delivery limit

Advanced payments

A pay page for every request

Each request has a mobile page in three languages: amount and kind, the methods that fit, card or IBAN with a copy button, receipt upload and the online gateway.

• Persian, Arabic and English, right-to-left and left-to-right
• Dark mode
• Hidden from search engines

Advanced payments

A safe online payment link

A private link opens a “pay now” page and then the gateway; a link preview never starts a payment, and after paying there is a button back to the chat.

• Result pages: paid, failed, cancelled, being checked
• Shown in the payer's language
• The failure page tells the payer that any amount taken comes back within 72 hours

Payment steps in the flow builder

Flows can send a payment request, wait until it is paid, send the invoice and record a refund request; conditions read the balance due, payment status and overdue instalments.

• Steps: payment request (kind, percent, amount, number of instalments and gap between them), wait for payment (paid / timed out), send invoice or pro-forma, record a refund request
• Conditions: balance due, payment status (open / paid / overdue / none), overdue instalments, total paid
• A basic payment request step and the payment status condition work without Payments+
• If you leave the offering empty, the customer chooses

Advanced payments

No method? The team is told

If no payment method fits the amount and currency, the customer is told politely and the team gets a ticket; no half-filled payment details are sent.

• With no method set up at all, the panel warns you: customers see no pay button and payment requests reach you as tickets

Payment confirmation message

Once confirmed, the customer gets a message in their language with the offering, the gateway reference and, for subscriptions, start and end dates; Payments+ adds the invoice button and what is left or the next instalment.

Rejections come with a reason

When a receipt is rejected, the reason goes to the customer in their language and the app waits for a new receipt.

• A reason is required to reject

Open requests at a glance

Every unpaid payment request in one list; from there open its pay page, send it again, make a pro-forma or cancel it.

• Cancelling also closes the waiting payment so it cannot be paid by mistake

Advanced payments

Payers become customers automatically

Confirming a payment moves the person to the customer stage, tags them with the offering and closes the payment review ticket.

Pay page link to share yourself

If the 24-hour chat window is closed and the message cannot go out, the request is still created and the panel says so, so you can share the pay page link yourself.

Advanced payments

Changing method or offering closes the old one

If the customer switches payment method or offering midway, the earlier unfinished payment is closed by itself with the reason in their language, so no one is left with two open payments.

• Reasons: payment method changed, offering changed

Buy now, pay later with Tabby and Tamara

Gulf customers can pay with Tabby (4 payments) or Tamara (3, 4 or 6); it only shows when the amount is within limits, and a declined customer is offered another method.

• Tabby: UAE, Saudi Arabia, Kuwait (AED, SAR, KWD)
• Tamara: Saudi Arabia, UAE, Bahrain, Kuwait, Oman
• Owner-set minimum and maximum per method and for all buy-now-pay-later
• Tamara eligibility is checked before it is shown

Advanced payments

International gateways

Stripe for international cards, Apple Pay and Google Pay in every currency except toman and rial, and PayPal for ten major currencies; both confirm automatically.

• PayPal currencies: USD, EUR, GBP, CAD, AUD, SEK, NOK, DKK, CHF, MYR
• Test and live modes for both

Online payments confirm themselves

When the customer returns from the gateway, the app asks the gateway itself and confirms only if amount, currency and order reference match; no receipt needed.

A closed tab doesn't lose the payment

If the customer closes the page after paying, the app re-checks every 5 minutes for 24 hours, and gateways that send signed notifications confirm at once.

• With signed notifications: Stripe, PayPal, Tap, PayTabs, Checkout.com, Tabby, Tamara
• Re-check only: Zarinpal, Zibal, NextPay, IDPay, MyFatoorah, Telr, N-Genius
• Every “pay” tap is tracked on its own, so a payment made from an earlier page still confirms

Connect a gateway with a safe test

Enter the gateway keys; the app checks their format, sends a test request that charges nothing and shows “ready” or a clear error.

• Test and live modes
• A table shows what each gateway supports: creating payments, checking them, instant notices, refunds, test mode
• Link to each gateway's own guide
• The Stripe test also checks that the account may take payments
• Zarinpal error codes are shown as plain messages

Amount and country limits per method

For each gateway, set its countries, currencies, minimum and maximum amount, display order and button title in three languages.

Advanced payments

Every world currency

Each offering has its own currency and amounts are written with the currency name and digits of each language, e.g. “1,500,000 Toman” or “AED 499”.

• All official world currencies (the ISO 4217 list)
• Currency names in Persian, Arabic and English
• Gateways are offered only for the currencies they accept

Prices in toman, gateways in rials

Write prices in toman; the app converts them to rials (×10) for Iranian gateways itself; the rial is also supported as its own currency.

National schemes only where they work

Tap can show all methods or only KNET, mada, BENEFIT or OmanNet; a national scheme is only offered in its own country.

• KNET: Kuwait · mada: Saudi Arabia · BENEFIT: Bahrain · OmanNet: Oman

Advanced payments

Methods grouped by region

The methods page groups gateways into Iran, Gulf, International and manual; your own region comes first and gateways that don't fit are dimmed.

• Shows your business country, currency and VAT status
• Warns when the app's public address is not secure (HTTPS)
• Shows the notification address to paste into each gateway's settings

Advanced payments

Three-decimal currencies done right

Kuwaiti dinar, Bahraini dinar and Omani rial keep their three decimals when sent to gateways and on invoices.

• KWD, BHD, OMR: 3 decimals

Card-to-card with a copy button

Your Iranian card number is validated and the bank is detected from it; the customer sees number, holder and bank and gets the number alone with one tap to copy.

• 16 digits with a check-digit test
• Bank detected from the first 6 digits
• Optional note to customers

Bank transfer by IBAN

IBANs of every IBAN country are checked for length and check digits; Iranian banks are detected automatically, and a SWIFT code is optional.

• Account holder, bank name, SWIFT code and a note
• Copy button for the IBAN

Your own payment link

Add any payment link you already have with your own button title; the app checks it opens, and each offering can have its own link.

• Secure links only (https)
• The customer sends a receipt afterwards for review

Upload the receipt on the pay page

Customers can upload the receipt as an image or PDF on the pay page and see straight away that it arrived.

• Images or PDF, up to 8 MB
• At most 12 uploads per request in 10 minutes

Advanced payments

Duplicate receipts are caught

If the same receipt file was already sent for another payment, even by someone else, it is marked “duplicate receipt” and an urgent ticket opens.

• The exact file is compared with every earlier receipt

Advanced payments

Typed amount checked against the request

Amounts, times and reference numbers the customer typed around the receipt are compared with the request, showing “amount matches” or “amount differs”. The receipt image itself is not read; you confirm.

• Looks at the customer's messages from the last 30 minutes
• Understands amounts in toman and rial

Advanced payments

Confirm or reject in one click

See the receipt next to the amount, correct the amount if needed, then confirm or reject with a reason, from the payments page or right in the inbox conversation.

• The owner confirms the receipt; the app does not read receipts by itself
• If the receipt picture is still downloading, the card says so

Deposits at the percent you choose

Deposits default to 30 % and can be changed per request; after a deposit, the next request asks for the balance by itself.

• Deposit percent from 1 to 100

Partial payments add up

Deposit, balance and instalments of one purchase add up; the confirmation tells the customer what is left, and nothing is asked again once it is all paid.

Instalment reminders and overdue follow-up

A reminder with a “pay now” button goes out days before the due date; if it is still unpaid after the grace period, it turns overdue, the customer is messaged and the team gets an urgent ticket.

• Reminder 0–14 days before the due date (default 2)
• Grace period 0–60 days (default 3)
• The overdue ticket can be switched off
• Messages go out only while the chat window is open

An instalment page for the customer

The customer sees the schedule, what is paid and what is left, and pays the next instalment from the same page.

Manage plans from the panel

For each plan you can send the next reminder by hand, waive the next instalment or cancel the plan; the overdue count shows next to the menu.

Reminder for unpaid requests

If a customer started paying but didn't finish, they get one reminder after some hours with the pay page button, worded by your trade pack.

• One reminder, by default after 20 hours (0–72, 0 = off)
• Stops as soon as the request is paid
• Your trade pack's follow-ups for that request are sent as this one message

Automatic chase of pending payments

A payment still waiting for money or a receipt is nudged after 3 and 20 hours, then becomes a team task at 24 hours; on WhatsApp, once the 24-hour window has closed, it uses your prepared message template.

• Stops when the customer replies or says stop
• On WhatsApp outside the 24-hour window it uses your approved reminder template, if you have set one
• Stops as soon as the payment is confirmed or closed

Subscription periods and renewal reminders

For monthly offerings, a payment creates a 1–24 month period and a renewal starts where the current one ends; expiring subscriptions are listed and a renewal reminder goes out in one click.

• Same day next month in the business's Persian, Gregorian or Hijri calendar
• Expiring list: ends within 10 days with no later payment
• Reminder only inside the chat window
• When confirming, the owner can set 1–24 months or mark it as a one-time payment

Automatic invoice after every payment

Every confirmed payment gets an invoice whose link is sent in the confirmation; the invoice page is in three languages and printable.

• Can be switched off
• Donations get no tax invoice
• Print or save as PDF from the invoice page

Six kinds of documents

Depending on country and buyer, the app issues an invoice, tax invoice, simplified tax invoice, pro-forma, credit note or payment receipt.

ZATCA QR for Saudi invoices

Simplified tax invoices in Saudi Arabia carry the ZATCA phase-1 QR: seller name, VAT number, time, total and VAT amount.

• Phase 1 only (phase-2 e-invoicing not included)

Pro-forma invoices

Make a pro-forma from any open request, or by hand with several lines, the buyer's company and tax number, and send the link.

• Up to 50 lines, with quantity and unit price
• Valid 14 days by default
• Your own number prefix (default PF)
• Once accepted, it goes on account within the credit limit, otherwise a payment request is sent

Wholesale and business accounts

Searchable invoice list

Every document with number, type, customer, total and VAT in one list; search by number or name, filter by type, and void any document.

• Seller legal name, address and invoice footer are set once
• A voided document keeps its number and its page says “void”

Gap-free invoice numbers

Each document type has its own gap-free yearly sequence, and you choose each series' prefix.

• Default prefixes: INV, PRO, CN, RCPT
• Number format: INV-2026-00001

Tax number format check

Your tax registration number is checked against your country's format when saved, so typos never reach an invoice.

• UAE: 15 digits
• Saudi Arabia: 15 digits starting and ending with 3
• Bahrain: 15 digits
• Oman: OM + 10 digits

The right invoice type by law

Saudi Arabia: full tax invoice for a VAT-registered buyer, simplified otherwise; UAE: full tax invoice above AED 10,000 or for a registered buyer.

Bilingual invoices for the Gulf

In Gulf countries, invoice labels are also written in Arabic next to the other language.

Itemised invoice lines

When a payment is for a reservation or an order, the invoice lists its lines separately, e.g. nights and extras, or a refundable deposit without VAT.

• A deposit or balance payment shows as one line

Stays, tables and rentals

Full or partial refunds

Enter the amount and reason; where the gateway allows it, the money goes back through the gateway, otherwise the refund is recorded and the team gets a ticket. A credit note is issued and the customer is told.

• Refund through the gateway: Stripe, PayPal, Tap, MyFatoorah, PayTabs, Checkout.com, Tabby, Tamara (full or partial)
• Recorded by hand: card-to-card, IBAN, links, Zarinpal, Zibal, NextPay, IDPay, Telr, N-Genius
• A reason is required

Track every refund

All refunds with status, gateway reference and errors on one page, marked “refunded” or “failed” by you; a customer's refund request is only recorded for the team.

• Statuses: requested, manual, processing, refunded, failed

A credit note for every refund

When money is refunded, a credit note for that amount, with its own running number, is linked to the original invoice so your books and VAT stay right.

• Default prefix: CN
• Not issued for a refund that failed

The payments page

Payments with receipt image, amount, method, reference and subscription period, filtered by to review, awaiting receipt, expiring, confirmed, rejected and a date range.

• Test conversations are hidden unless you choose to show them

Takings today, this week, this month

Confirmed takings for today, the last 7 days and this month, per currency with the number of payments, in your business's local time.

• Test customers are never counted
• only payments you confirmed are counted
• test customers left out

CSV export that opens in Excel

Export payments for a date range and status as a CSV file that opens in Excel; column headings are in the panel language.

• Columns: date, customer, case, offering, amount, currency, method, status
• Test conversations are left out
• columns: date, customer, case, package, amount, currency, method, status

One inbox for every payment

Every payment, any method, in one inbox: receipt checks with duplicate or amount flags, confirm and reject, refunds, invoice links, and open requests you can resend, turn into a pro-forma or cancel.

• Filters: to review, awaiting, confirmed, rejected, all; and by method
• Search by name, username, offering, gateway reference, payment number or invoice number

Advanced payments

Payment figures on the dashboard

Collected in 30 days, receipts to review, open requests, overdue instalments, cash on delivery and open refunds show on the dashboard and above the inbox, with counters next to the menu.

Advanced payments

Each customer's payment file

On each customer's page: balance due, overdue instalments, requests, payments, plans, invoices and refunds together, with new requests and refunds from there.

Advanced payments

Find invoices and requests fast

Invoices, payment requests and refunds show up in the panel's global search.

Advanced payments

Every step in the customer timeline

Method sent, receipt received, confirmed, rejected, invoice, instalment, reminder and refund are all logged in each customer's timeline.

A wrong amount is never confirmed

If a gateway reports a payment whose amount or currency doesn't match the request, it is not confirmed, the customer is asked not to pay again and the team gets an urgent ticket.

Double charges are flagged

If a customer pays twice from two tabs, the team gets an urgent ticket to refund the extra; with Stripe, other open checkout pages are closed after payment.

No card details in the chat

The app never asks for card details in the chat; online payments happen on the gateway's own page and no card is saved.

Payment messages are service messages

Payment requests, confirmations and payment reminders count as service messages, not marketing, so they don't depend on marketing consent.

• Follow-ups tied to a payment request or confirmation count as service messages
• Flows started by a payment event count as service messages unless the owner marks them as marketing

Unsigned gateway notices are refused

Notifications from gateways are accepted only with a valid signature, and even then the payment is checked again with the gateway.

• Stripe signatures older than 5 minutes are rejected
• Floods of unsigned notices claiming to be PayPal are slowed down

Unverified gateways stay off

A gateway not fully checked against public documentation is off by default and turns on only after a successful test and your explicit agreement.

• Applies to IDPay
• Direct KNET and BENEFIT connections cannot be switched on

Advanced payments

Respects the messaging window

Payment messages go out only while the chat window is open; a refund notice is held when it is closed and sent with the customer's next message.

Erase data, keep tax records

Erasing a customer removes their requests, plans, receipts, refunds and cash-on-delivery rows; invoices keep their number and amounts with the buyer's details removed.

Advanced payments