Payment Methods & Proof Review

Share manual payment instructions, review proof, and confirm payment only after it is actually accepted.

Payment Methods & Proof Review#

Many businesses take payment manually — a GCash transfer, a Maya transfer, a bank deposit, or a QR scan — and then review the receipt. This setup lets the agent share the account details you saved, collect proof, and keep the payment unconfirmed until your review rule accepts it.

Open Agent Studio → Tools → Cart & Checkout → Payment setup. The page is Payment Methods & Proof Review. Orders and Procedures decide when the agent is allowed to use it.

A customer saying "I already paid" is not confirmation. A screenshot sitting in the chat is not confirmation either.

What You Configure#

Setting	Description
Payment methods	At least one GCash, Maya, bank, GrabPay, or other account, including a QR image tied to that method
Share instructions	Lets the agent mention those saved methods when a customer asks how to pay
Screenshot verification	Reviews a receipt. Add a method before turning this on
Verification mode	Owner confirmation, AI waits, or Auto-accept clear receipts
Replies	What the customer hears while a receipt is pending, after it is confirmed, and when the image is unreadable
Proof goes to	Staff channel, AlonChat Assistant, email, or webhook. Owner-confirmation mode uses this before payment is treated as confirmed
Google Sheets log	Optional copy of payment proof. The sheet is not what marks a payment verified

Checkout links are separate. A connected Maya or PayMongo link is created and checked as a payment link, not as a manual receipt. See Integrations.

How Proof Is Judged#

What the customer did	What the payment status is
Says they paid, with no receipt or reference	Stays pending. Ask for a screenshot, receipt, or reference number
Paid cash or offline	Stays pending until the team checks the amount, time, place, and any receipt they can send
Sends a receipt, owner confirmation is on	Stays unconfirmed until a reviewer marks it received
Sends a clear receipt, auto-accept is on	Can continue. Unclear or blocked receipts still go to review
Sends an unreadable image	Ask for a clearer shot that shows the amount and reference. Do not confirm it
Uses a payment link	Not paid until the payment-status check says it is paid

The confirmed-payment reply is sent after owner approval, or after auto-accept handles a clear receipt. It is not sent because the customer uploaded a file.

Auto-accept does not mean every image is accepted. Low-confidence and blocked receipts still wait for a person.

When a Payment Step Fails#

What happened	What to tell the customer
The payment step fails	No payment was confirmed
The result is unclear	Check the payment status before trying again
Instructions were shared	That only tells them where to pay. It does not mean they paid
A link was created	They still have to complete checkout. Creating the link is not payment

Because the status stays pending until review or a successful status check, the agent should not mark an order or booking paid on the customer's word alone.

Where It's Used#

Payment review is most useful inside a Procedure — for example, a deposit before a booking is confirmed, or full payment before delivery is booked. The procedure should wait for the verified result, not for the customer to say they paid.