Complete card or wallet payment
Card and wallet checkout records the selected tender, but the external device result and POS record must agree. Card or UPI-style wallet processing requires the configured provider and connection; an eligible single Wallet flow may queue only when the screen explicitly permits it. Submit once, then check Orders and Payments before retrying any missing or conflicting result.
Before you start
- An authenticated POS session on the intended branch.
- A reviewed cart with the correct customer, service mode, item prices, tax context, and amount due.
Steps
- Choose Card or Wallet only when it is enabled for the branch.
- Complete the connected terminal or wallet flow and keep its safe reference.
- Wait for POS to show success, failure, cancellation, pending, or an explicit eligible queue state.
- When the external device and POS disagree, stop and reconcile Orders and Payments before retrying.
Expected result
The POS and external terminal or wallet agree on one success, failure, cancellation, or still-pending outcome. Never submit an uncertain tender again until Orders and Payments show whether it succeeded, failed, or queued.
Permissions
- The staff member needs POS checkout access for the active branch; discounts, overrides, Khata, and some tenders may require the specific manager or configured payment permission.
Troubleshooting
Staff cannot choose Card or Wallet only when it is enabled for the branch because the control is missing, disabled, or rejected before they complete the connected terminal or wallet flow and keep its safe reference.
Before reopening the workflow, verify: An authenticated POS session on the intended branch. A reviewed cart with the correct customer, service mode, item prices, tax context, and amount due. Check those conditions on /billing and repeat only the blocked step once. Preserve the screen and ask Support to review the safe order/payment references, tender, amount, branch, status, and time; omit card data, CVV, wallet secrets, and PINs. For escalation, state what happens when staff choose Card or Wallet only when it is enabled for the branch.
The total, tender, receipt, server record, and local queue do not show one payment outcome after the final checkpoint: When the external device and POS disagree, stop and reconcile Orders and Payments before retrying.
Compare the final total, Orders entry, Payments entry, receipt, external-terminal result, and local queue. When the external device and POS disagree, stop and reconcile Orders and Payments before retrying. Retry only when both server records and the local queue prove no payment exists. Give Support the safe order/payment references, tender, amount, branch, status, and time; omit card data, CVV, wallet secrets, and PINs.
Related articles
Cart totals show subtotal, discount lines, VAT or tax, service charge, tip, and final amount using current branch pricing.Apply or remove a promotion code
Promotion validation returns the eligible saving or explains why the code did not change the cart.Use an authorized discount or price override
Discounts and overrides appear only when configured and may require manager approval before checkout can continue.Choose a payment method
The checkout shows only payment methods enabled for the branch, including cash, card, wallet, UPI, or Khata where configured.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback