Payment Verification
Collect payment instructions, accept proof-of-payment screenshots, and approve payments before fulfilling.
Payment Verification#
Many businesses take payment manually — a GCash transfer, a bank deposit, a QR code scan — and confirm it from a screenshot. Payment Verification lets your agent share the right payment instructions, collect the customer's proof of payment, and route it to you for approval before anything is marked paid.
Find it under Automations > Payment Verification.
What You Configure#
| Setting | Description |
|---|---|
| Payment instructions | The details customers need to pay you (e.g., GCash, bank transfer, QR code) |
| Require proof | Ask the customer to upload a screenshot of their payment |
| Approval | Require a human to approve the payment before it's marked verified |
| Where it's logged | Send verified payments to a sheet, a webhook, or an activity record |
How It Works#
Code
Customer ready to pay
|
Agent shares your payment instructions
|
Customer pays and uploads a screenshot
|
Proof is collected and (optionally) sent for your approval
|
You approve -> payment marked verified -> order/booking continues
Because approval is in your hands, the agent never marks something paid on a customer's word alone.
Manual Proof vs. Payment Links#
- Payment Verification (this page) is for manual payments you confirm from a screenshot.
- For automatic checkout links, AlonChat can also create payment links through a connected payment provider as part of a Business Process. Both fulfill the same job — getting paid — and you can use whichever fits each flow.
Where It's Used#
Payment Verification is most powerful inside a Business Process — for example, requiring a deposit before confirming a booking, or collecting full payment before arranging delivery.