Key topics
Related public pages
If you need the product, API or operations page rather than only the article, start with these VPOS.am sections.
QR page should be a payment entity
Tips, donations and invoice targets have different business meaning, but all should point to a controlled payment flow.
A QR code for tips or donations is often treated as a simple picture. In production, it is a public payment point: target type, recipient, available amounts, currency, public page, payment session and result display rules.
Separate employee, team, company, donation, invoice and custom targets early. Then one payment infrastructure can serve different scenarios, while operators understand why the payment was created and where it belongs in reporting.
- do not make QR code the only source of data;
- store target type, recipient id and branch id;
- create payment session only after server-side validation;
- show clear pending, success and failed states.
Statuses should separate payment, feedback and payout
Successful payment, feedback, payout request and payout completed are different events and should not be merged into one status.
After QR payment, the system may collect feedback, create report entries, open a payout request and send a webhook. These events are connected but have different lifecycles. Payment can be verified while payout is still requested or processing.
Do not promise automatic split settlement unless it is supported by bank or provider contract. In early stages, payout records are better treated as operational records for reporting, reconciliation and manual period closing.
- payment status is not payout status;
- feedback should not change financial status;
- payout request needs period, amount and owner;
- manual payout completion should log reference.
How to close shift and month without spreadsheets
Operators need a short list of verified payments, payout batches and exceptions, not manual search through bank statements.
For a restaurant, hotel, service business or charity, payment itself is only part of the job. The team needs to know which QR payments were verified during the shift, which recipient they belong to, which amounts are included in payout request and which operations need review.
A practical process closes exact matches automatically: verified payments are grouped by period, target, branch and currency. Exceptions include amount mismatch, cancellation, refund, missing payout reference or manual correction without comment.
- group payments by period, target and currency;
- reconcile gross, fee and net amounts separately;
- create payout batches only from verified payments;
- send payout status webhook without exposing secrets.
FAQ
Can QR tips promise automatic payouts immediately?
No, not unless split settlement or card payout is confirmed by bank or provider contract. At launch, payout should usually be an operational record for reporting and manual closing.
How are QR tips different from a payment link?
QR tips are usually linked to recipient, shift, feedback and payout report. A payment link is more often linked to an invoice, order or fixed amount.
Is payout status webhook needed?
Yes, if external CRM/ERP or reporting system needs to know when payout is requested, processing, completed or cancelled. The webhook should be signed and idempotent.
