PayTabs TAPn'GO: Add a Tip Step to Scan‑to‑Pay

Summary

TAPn'GO lets guests scan a QR (or tap an NFC cube) to view the bill, split, tip, and pay—no card terminal at the table.
To lift your tip attach rate, show a quick tip selector before the Hosted Payment Page (HPP) or PayLink, so the final cart_amount already includes the tip.
Attribute tips to staff by encoding table/server in cart_id/cart_description and linking other data to tran_ref in your database.
Includes signage copy, staff scripts, a 30‑minute rollout checklist, and a developer JSON snippet.

Scan to pay and tip with PayTabs TAPn'GO

Indian, GCC, and global visitors are comfortable with QR payments. TAPn'GO brings that experience to the table: guests scan, review, split, add a gratuity, and pay from their phones. To maximise conversions, insert a tip prompt before redirecting to the PayTabs checkout—so the gratuity is included in the final charge.

How the flow works

Static table QR → your tip page: Place a table/receipt QR that links to /pay/t/:table_id. Your page fetches the open bill total.
Tip prompt: Show buttons (AED 5/10/15, 10%/12.5%/15%, custom). When selected, compute total = bill + tip.
Create a PayTabs payment: Call the HPP/PayLink API with cart_amount = total, include staff/table metadata in cart_id/cart_description.
Redirect or display QR: Redirect the guest to link_url (or show a dynamic QR returned from the API) to pay by card or wallet.
Allocate & reconcile: On callback, record tran_ref and your encoded fields (cart_id, cart_description) for payroll.

TAPn'GO tip prompt flow: scan → tip → pay → reconcile

Start Receiving Cashless Tips Today

Make tipping easier for your customers and seamless for your team. Join our platform and accept contactless gratuities with ease.

Developer snippet (HPP / PayLink request)

{
  "profile_id": "XXXX",
  "tran_type": "sale",
  "tran_class": "ecom",
  "cart_id": "T12-SRV-NAOMI-04-20250903121912",
  "cart_description": "Table T12 · Tip included",
  "cart_currency": "AED",
  "cart_amount": 125.00,        // bill + tip
  "payment_methods": ["all"],
  "customer_details": {
    "name": "Table 12 Guest",
    "email": "guest@example.com"
  },
  "return": "https://qrtips.ae/paytabs/return",
  "callback": "https://qrtips.ae/paytabs/callback",
  "generate_qr": 1              // optional: return Base64 QR to display
}

Notes: Use cart_id / cart_description for staff/table attribution that will echo in the dashboard and callbacks. For any extra metadata, store it in your DB keyed by tran_ref from the callback. If you use Invoices or Own Form, consult PayTabs docs for user_defined support.

Signage pack (print or on‑screen)

Counter / Entrance

“Scan to Pay & Tip” — Cards & wallets accepted.
“Prefer contactless? Scan to review & tip in seconds.”
Place on host stand, menu footer, delivery slip, and receipts.

At table / service point

“Scan the QR to split, tip, and pay.”
Offer preset bubbles (AED 5 / 10 / 15; 10% / 12.5% / 15%).
Add small staff initials or a table code under each QR.

Staff scripts (10‑second guidance)

When presenting the bill

“You can scan to pay on your phone. There’s a quick tip option before checkout.”

If asked about security/fees

“Payments are processed on PayTabs’ secure page with your usual card or wallet.”

If a guest wants to split

“Each person can scan the QR, select a tip, and pay their part.”

A picture is worth a thousand words. Action is worth a thousand pictures. Scan the QR code and see us in action right away.

Owner checklist (30‑minute rollout)

Enable TAPn'GO / QR flows on your PayTabs profile; confirm HPP/PayLinks access.
Create the tip prompt page that computes bill + tip and calls the PayTabs API.
Encode table and staff in cart_id (e.g., T12‑SRV‑NAOMI‑04‑{ts}).
Print table QR with your tip page URL; add QR to receipts and WhatsApp order messages.
Test end‑to‑end: small payment, refund, callback parsing, and dashboard export mapping.
Set the allowed payment_methods for your venue (cards, Apple Pay, Google Pay, etc.).

Reconciliation & payouts

Use the callback payload and tran_ref to finalize orders and tip mapping. For audits, run portal exports and the Query Transaction API when needed. Your ledger should map each payment to table, server, and tip using the values you encoded in cart_id/cart_description.

FAQs

Is the tip prompt built into TAPn'GO?

TAPn'GO enables scan‑to‑pay. To capture tips reliably, add a brief tip step on your page, then initiate the PayTabs payment with the updated amount.

Can we show a scannable QR instead of redirecting?

Yes. Use the generate_qr option to receive a Base64 QR in the API response; render it for the guest to scan and complete payment on the hosted page.

How do we attribute tips to staff?

Encode staff/table in cart_id or cart_description, then join with the tran_ref from your callback in your own database for detailed allocation. If you use Invoices/Own Form, review PayTabs docs for user_defined options.

Sources

PayTabs – TAPn'GO (scan at table; NFC cube; split & tips): paytabs.com/en/tapngo/
PayTabs – TAPn'GO blog (scan QR or tap NFC cube; add tips): paytabs.com
PayTabs Docs – generate_qr parameter (Base64 QR in response): docs.paytabs.com
PayTabs Docs – Hosted Payment Page (request parameters incl. cart_id, cart_description, cart_amount): docs.paytabs.com
PayTabs Docs – cart_amount parameter: docs.paytabs.com
PayTabs Docs – cart_id parameter: docs.paytabs.com
PayTabs Docs – payment_methods parameter: docs.paytabs.com
PayTabs Docs – callback (server‑to‑server transaction details): docs.paytabs.com
PayTabs Support – QR Pay via Merchant Mobile App (generate/sharing one‑time QR): support.paytabs.com
PayTabs – Merchant Dashboard & App (invoices shareable via QR): site.paytabs.com