Settings

Configure and Test Kiosk Payment

The Kiosk Payment tab stores three branch-level switches: customer-detail page visibility, Cash on Delivery, and Razorpay. Razorpay remains disabled until the current branch has a payment gateway key.

Menu path: Settings -> Sales Channels -> Kiosk -> Payment
Verified from: Posnic demo and current POS source reviewed on 2026-09-08

Technical source evidence

Live demo Settings -> Sales Channels -> Kiosk -> Payment audited 2026-09-04, frontend/modules/settings_write.html kioskpayment-line, frontend/static/script/js/modules/js/settings.js payment loading gateway eligibility and kiosk form submission, api/src/models/setting.model.js kioskPaymentModel branch-scoped switches, api/src/repositories/item.repository.js kiosk_payment catalog response, api/src/controllers/settings.controller.js kioskPayment plan access, frontend payment gateway settings audited 2026-09-04

Current Posnic Kiosk Payment tab with Customer detail control Cash on Delivery and Razorpay settings — **Kiosk Payment controls**Live Posnic demo rechecked 2026-09-04. Razorpay is disabled when the current branch has no saved gateway key; Customer detail control and Cash on Delivery remain selectable.

Current Posnic sale tender drawer used to verify branch payment controls before enabling kiosk Razorpay — **Test the branch payment path**Kiosk Razorpay depends on branch gateway configuration. Prove the configured payment path with a controlled transaction before offering it to kiosk customers.

Posnic Kiosk Report summary used to reconcile kiosk payment totals — **Reconcile the test payment**After a controlled order, compare kiosk totals with the sale, payment report and gateway or cash evidence.

Understand Each Control

Control	When selected	When cleared
Show/Hide Page	The kiosk payment data tells the customer channel to use its customer-details page.	The customer channel receives the customer-detail switch as off. Test the deployed kiosk because required identity can vary by workflow.
Cash on Delivery	The kiosk offers its cash-on-delivery or pay-at-counter path.	That payment choice is removed for this branch.
Razorpay	The kiosk can offer the configured Razorpay path after gateway eligibility is present.	Razorpay is not offered by this kiosk configuration.
Save	Posts the complete current state of all three switches.	There is no partial save: cleared enabled boxes are deliberately stored as false.

Prepare Razorpay Before Enabling It

Open Settings -> Payment Gateway -> Razorpay for the same active branch.
Enter the correct Key ID and Secret Key and configure the displayed webhook URL in the merchant dashboard when the deployment requires it.
Enable the gateway and save it; do not paste credentials from another outlet.
Return to Kiosk -> Payment and confirm Razorpay is no longer greyed out.
If it remains disabled, reopen the gateway page and verify that a non-empty branch key loads and the gateway save succeeded.

Choose the Customer Flow

Decide whether the shop needs a phone number or customer identity before accepting a kiosk order.
Keep the customer-details page when the operation needs order contact, pickup identification, loyalty, support follow-up or delivery information.
Clear it only after testing the deployed kiosk from item selection through completion; the settings label does not describe every downstream field.
Do not collect customer details merely because the switch exists. Match the shop's real service and privacy requirements.
Document the approved state for each branch because these switches are not global across all outlets.

Configure Kiosk Payment

Confirm the active branch and its Kiosk Store ID.
Open Kiosk -> Payment and note the currently selected controls before changing anything.
Select or clear Show/Hide Page according to the approved customer flow.
Select Cash on Delivery only when staff have a defined collection and order-release procedure.
Select Razorpay only when it is enabled and the branch gateway has already passed a payment test.
Click Save and wait for Payment settings updated successfully.
Leave and reopen Payment to confirm all three controls reload in the intended state.

Test Cash on Delivery

Open the customer-facing kiosk for the exact Store ID in a fresh session.
Create a low-value controlled order and choose Cash on Delivery.
Confirm the order reaches the intended branch with the correct items, taxes and total.
Verify the receipt or kitchen output clearly identifies the order and payment state used by the deployed kiosk.
Follow the shop's cash collection procedure and make sure staff do not treat an uncollected kiosk order as settled cash.
Confirm the order appears in Sales History and Kiosk Reports under the expected payment bucket.

Test Razorpay End to End

Use the gateway's approved test environment or a controlled low-value live transaction according to the merchant's policy.
Start a fresh kiosk order and confirm Razorpay is actually offered to the customer.
Complete payment without closing the kiosk and record the provider payment reference.
Confirm the order is created once, belongs to the correct branch and shows the expected paid state.
Check the provider dashboard or webhook evidence for success and compare the amount with the Posnic sale.
Reconcile Kiosk Reports, Payment Reports and day-close totals; a checkbox or QR display alone is not acceptance evidence.
Run one failure or cancellation test and verify no duplicate paid sale is created.

Troubleshooting

Symptom	Likely cause	Action
Razorpay is greyed out	The current branch has no saved Razorpay gateway key.	Configure and save Razorpay for this branch, then reopen Kiosk Payment.
Razorpay is selectable but absent on kiosk	Kiosk settings are stale, the wrong Store ID is open, or deployed checkout integration failed.	Reload settings and kiosk, verify branch mapping, then inspect the real checkout and gateway response.
Customer detail page appears unexpectedly	Show/Hide Page is saved on or the kiosk session has stale settings.	Clear it, Save, reopen Payment and start a fresh kiosk session.
No customer details are captured	The customer-detail switch is off or the deployed channel does not consume it as expected.	Enable it and test the required fields end to end before customer use.
Cash order looks paid before collection	The operational handling of Cash on Delivery is unclear.	Stop rollout and define payment-state, collection and release responsibilities before resuming.
Payment succeeds but sale is missing	Callback, webhook or order finalization did not complete.	Keep provider evidence, do not retry blindly, search Sales History, and escalate with Store ID and payment reference.
Two sales appear for one payment	The customer retried or completion was processed more than once.	Stop live use, preserve both sale IDs and the provider reference, and reconcile before refunding or voiding.
Changes revert after navigation	Save failed or settings were changed under another branch.	Confirm the active branch, save again, wait for success and reopen the tab.

Payment Acceptance Record

Branch name and Kiosk Store ID.
Customer-detail switch and reason for its state.
Every enabled payment method and responsible collection process.
Test order ID, amount, date and kiosk device or browser.
Provider reference for Razorpay or collection evidence for Cash on Delivery.
Sale, Kiosk Report, Payment Report and day-close reconciliation result.
Failure/cancellation test result and any duplicate-order check.
Operator and manager approval before customer rollout.