Step 1
Verified starting point
Open Settings → Payment Acceptance. Enable the SkipCash external integration, then choose Manage SkipCash. Select Sandbox or Production and enter the restaurant-issued Client ID, Key ID, Key secret, and Webhook key.
- SkipCash starts disabled for new restaurants; existing configured restaurants retain their enabled state
- Saving creates an encrypted immutable credential version
- Branch settings separately control online payment and the optional Pay at Table switch
Step 2
Enter the restaurant's SkipCash credentials
Go to Settings → Payments and choose Production only when the restaurant has an approved live merchant account. Enter the Client ID, Key ID, Key secret, and Webhook key issued to the restaurant by SkipCash. Save the encrypted credentials and complete reauthentication if requested.
- Never paste payment secrets into support chat or a guide
- Sandbox is for approved test tenants, not real customer payments
Step 3
Activate and test the connection
Activate the saved gateway configuration. Use Test connection with an existing provider-approved SkipCash payment ID where the screen requests it. Confirm the merchant, amount, currency, and callback setup belong to the same restaurant environment.
- Use a controlled low-value live smoke only with explicit merchant approval
- A successful settings save is not proof of end-to-end settlement
Step 4
Enable online payment by order type
Open the branch payment-method settings. Enable Pay securely online only for the ordering modes the branch already supports; Cash at handoff and Card at handoff remain separate choices. Place a controlled order and reconcile the DashDine order ID, SkipCash transaction, QAR amount, refund state, and bank settlement.
- Fulfillment status never proves that payment was collected
- Investigate unmatched or duplicate provider events immediately
Step 5
Enable Pay at Table safely
Pay at Table is a separate branch opt-in and starts off. After SkipCash is enabled with valid live credentials, open Branches → Edit Branch → Payment methods, enable online payment, then enable Pay at Table. Eligible dine-in order details and receipts can show an order-specific QR for the full remaining balance.
- Partial or split Pay at Table payments are not supported; the guest pays the full remaining order balance
- An active provider payment locks staff cash/card collection and manager payment correction for that order
- Confirmed payment updates the audited money ledger but never advances kitchen or fulfillment status