Confirm a payment · Reviewed 24 October 2026
Bank proof review and issued receipts
Read uploaded proofs with OCR, check actual bank receipt, and give customers a receipt for each confirmed payment.
Review a submitted proof
- Open Invoices and filter Awaiting confirmation, or use the pending-proof indicator. Open the relevant invoice and proof review.
- Inspect the uploaded proof. Where extraction is available, review the suggested amount, reference, date, bank and destination account. Correct inaccurate fields.
- Check the actual bank statement and match the payment to the right customer and invoice. OCR reads the document; it cannot establish that money arrived.
- Confirm the amount actually received, or reject with the appropriate reason. Inspect the updated payment history and remaining balance.
An unreadable proof or failed extraction must be resolved visibly. Do not treat missing fields as confirmation or fill them with assumed values.
Record an already received bank payment
Use the invoice’s bank-payment controls to record a payment you can verify. Enter amount, payment date, reference and note, and attach evidence when available. Confirm the amount and invoice before saving. For partial payments, record the actual amount rather than the full invoice total.
Find and share an issued receipt
After payment confirmation, the buyer’s permanent invoice page shows confirmed payments, their receipts and the updated balance. Each receipt records the payment amount and balance after that payment; later payments do not rewrite the earlier receipt. Open the hosted receipt or download its PDF.
A bank-uploaded proof and a YeboPay-issued receipt serve different purposes. A receipt is issued from a confirmed payment record. Receipt delivery may fail independently of payment confirmation; review the delivery outcome before resending.
Inspect payment history and reporting
Open Payments for transaction history and detail. Use Overview for the selected reporting range, payment totals and overdue follow-up. Keep currencies separate when comparing totals, and check whether the dashboard is showing Live or Test data.
In an integration, the public receipt routes are GET /receipts/{id} and GET /receipts/{id}/pdf. Confirm the server-side payment result before fulfilling an order.
Refund an eligible charge
Open Payments, inspect the charge and use its Refund controls when available. Enter a positive amount for a partial refund, or leave it blank to refund the remaining refundable balance. Check the amount and customer before submitting; inspect the result and refreshed refunded total.
The merchant API is POST /v1/refunds with refunds.write, charge_id, optional amount and optional reason. Only eligible succeeded or partly refunded charges can be refunded, and the amount cannot exceed the remainder. Some saved-instrument charge paths return 501 because refunds are not implemented for that path. Surface that failure and contact support; do not mark the refund complete.
A charge refund follows its supported payment processor. An escrow refund instead returns held funds to the buyer’s wallet.
Explore the other features
Browse all guides
- Escrow holds, releases and disputes
- Invoices, partial payments and layby
- Customers, CSV imports and bulk billing
- Collection channels and bank accounts
- Payouts, withdrawals and partial settlements
- AI assistant, voice and follow-ups
- Recurring billing, installments and subscriptions
- API keys, hosted checkout and webhooks
- Business setup, verification and security