DEVELOPERS
Payment integration guide
Hosted payment links are available from your merchant account. Public payment APIs, secret keys and automatic external webhook delivery are not provisioned.
Recipient confirmation is required
A customer reference is not a bank-verified payment. Keep the order pending until the recipient confirms the exact transfer. SuzoPay does not provide escrow or custody.
Payment-link workflow
UPI & Cropty checkout
Each generated link opens its own checkout page. Customers can scan the UPI QR, open a UPI app, or visit the configured Cropty receiving profile. Check the recipient and amount before transferring. The same 15-minute payment window applies across both methods and does not restart when the page reloads.
Transfer references
After transferring, submit the reference from your payment app. UPI requires a 12-digit UTR; Cropty requires the transfer reference. A submitted reference remains pending until reviewed. When the checkout timer expires, new transfers are disabled, but a customer who already transferred can still submit their reference.
Recipient confirmation
The merchant checks the receiving account against the order amount and reference. Only the merchant who owns the link can confirm or reject a submitted receipt. A reference or screenshot alone is not proof that funds arrived. Confirmation closes the payment link; rejection does not mark it paid.
Reconciliation & payouts
Review confirmed receipts in the merchant dashboard and retain the receiving account’s transfer records alongside your order information. Reports contain historical transaction records and are not a bank statement. Withdrawal requests are records only: SuzoPay does not automatically settle transfers, move money or execute external payouts.
Webhooks
Historical event signatures can be inspected on the Webhooks page. Submitted receipts are reviewed separately; they do not automatically trigger a provider-verified payment event.
{
"status": "pending",
"method": "UPI",
"confirmation": "merchant_review_required"
}