Payments

How to Accept Payments for Local Business Orders

Learn how KyoskGo handles local payments with business currency, UPI instructions, customer payment proof, vendor approval, and manual payment records tied to orders and invoices.

KyoskGo · 2026-05-28

accept payments local businessaccept payments online small businesslocal business payment methodsUPI payment for orderspayment proof uploadmanual payment approval

Local businesses rarely have one payment story. A home baker may take UPI. A salon may take cash at the chair. A boutique may mix bank transfer and partial advance. A restaurant may use counter POS plus online prepayment for catering.

KyoskGo is honest about that reality. The platform records what was ordered, what is owed, what was paid, and what a customer claims they paid—with vendor review when proof is involved. It is not a promise that every business automatically processes cards inside KyoskGo without configuration.

The payment principles KyoskGo follows

Three rules protect both sides:

  1. **Business currency is authoritative.** If the shop sells in INR, order and invoice amounts stay in INR unless there is an explicit, traceable conversion flow. The customer’s browser locale does not silently change displayed currency.
  1. **Totals live on the server.** Order totals, amount paid, and amount due come from backend services and payment status logic—not from a customer-edited screenshot.
  1. **Payment status is explicit.** Statuses such as unpaid, partial, and paid are derived from recorded payments and approvals, not from hope.

Step 1: Configure how customers should pay you

In business settings, vendors can add payment instructions customers see during checkout and on order tracking or payment pages. Typical fields include:

  • UPI ID and optional UPI QR image URL.
  • Payee name shown on UPI apps.
  • Bank transfer details.
  • Short note (for example “Add order number in UPI note”).
  • Accepted methods: UPI, cash, bank transfer, other.

Customers use these instructions to pay outside or alongside any integrated flow your business actually uses.

Step 2: Understand what happens at checkout

Checkout creates the order with a total and initial payment status—often unpaid for local businesses that collect after confirmation.

The customer may:

  • Pay later using instructions on the tracking or payment page.
  • Pay cash on pickup.
  • Send UPI and upload proof.
  • Ask the vendor to record payment manually in the dashboard.

None of that replaces the order record. The order is still the anchor for what was sold and for how much.

Step 3: Let customers upload payment proof when needed

When manual confirmation is part of your workflow, customers can submit:

  • Screenshot or image of the transfer.
  • Claimed amount.
  • Optional note (for example last four digits of reference).

The upload is stored as a payment confirmation request. Vendors review it in the dashboard, approve or reject, and on approval the system can record a manual payment against the order or linked invoice.

Rejections should include a vendor note so the customer knows what to fix.

This flow exists because many local businesses already trust bank alerts and screenshots more than a generic “paid” button with no verification.

Step 4: Approve or record payments as a vendor

Vendors can:

  • Approve customer proof and record the approved amount.
  • Enter payments manually (for cash at counter, verified bank transfer, or card terminal not wired into KyoskGo).
  • Link payments to invoices when invoicing is part of the workflow.

Approval updates total paid and amount due using precise decimal handling on the server. Overpayment rules and invoice settlement still apply when an invoice is involved.

Step 5: Keep orders and invoices aligned

If you issue invoices, payments should settle invoice balances and reflect back on related orders where configured. Do not mark an invoice paid in one place while the order still shows unpaid without a reason.

KyoskGo uses shared payment status services so invoice and order states stay consistent when payments are recorded through the proper APIs.

What about card payments and gateways?

Subscription billing for KyoskGo vendor plans may use payment providers such as Stripe or Razorpay for the vendor’s own SaaS subscription. That is separate from how each local business collects money from its customers.

For customer order payments, assume offline-first unless your deployment explicitly enables and configures an integrated gateway for that business. Do not tell customers “card checkout always works” without checking your live setup.

Common mistakes to avoid

  • Changing prices only in chat while the catalog still shows an old price.
  • Treating a WhatsApp screenshot as paid without approving or recording payment in the system.
  • Displaying USD to a customer when the business currency is INR.
  • Letting staff mentally calculate totals that differ from the checkout total.
  • Promising instant payment confirmation when your workflow is manual review.

Customer checklist

  • Pay to the UPI or account shown on the official order payment page, not a random number from an old chat.
  • Include the order number in the payment note when possible.
  • Upload proof with the correct amount if the business uses confirmation.
  • Recheck order tracking for `amount due` after the vendor approves.

Vendor checklist

  • Keep payment instructions current.
  • Review proof requests daily during busy hours.
  • Record cash payments at pickup so reporting is accurate.
  • Train staff to use the same order record for phone orders and walk-ins.

Related guides

FAQ

Does KyoskGo process UPI automatically?

UPI instructions and QR help customers pay their UPI app. Settlement still depends on the customer completing transfer and the vendor confirming or recording it unless an integrated automatic flow is configured for your account.

Can customers pay in a different currency than the business?

Customer-facing amounts should follow the business currency configured for that shop. Do not rely on browser locale to pick currency for money display.

What if a customer underpays?

Amount due stays positive until a payment or approved proof covers the balance. Vendors can reject incorrect proof with a note.

Is payment proof stored forever?

Payment proof assets follow retention policies. Sensitive screenshots are managed by the platform and are not meant for arbitrary manual deletion by vendors in ways that break audit trails.

Can I accept only cash?

Yes. Configure accepted methods and record cash payments when orders are fulfilled so status matches reality.