Integration readiness

Payment processor

Provzo’s payment processor is Razorpay, operated by Razorpay Software Private Limited. Merchant onboarding is complete. The methods the gateway is configured to present are UPI, credit and debit cards, net banking, wallets, EMI and pay-later options.

Provzo is not a bank, a wallet issuer or a payment system operator. It is a merchant using a licensed processor, and accepting these policies does not create any relationship between you and that processor beyond the payment you choose to make.

What is live and what is not

Cash on completion is live. The in-app digital payment step is not yet in a released build, so no online payment can currently be collected, authorised, captured or refunded through the app.

This section is the honest statement of that gap. It will be updated in the same revision that ships the payment flow, rather than in advance of it.

What ships with the payment flow

Server-side transaction states rather than client-trusted ones; signed webhook handling for capture, failure and refund; reconciliation against gateway settlement reports; idempotency so a retried request cannot charge twice; and a refund path support can actually operate.

Published policy text stating fees, receipts, failure handling, duplicate payments, refunds, chargebacks, settlement and retention is part of that same change, together with a new policy revision.

No active government API

No government API or automatic government-record verification is currently active. Provider approval means approved for marketplace listing only. It is not a government identity, licence, background or trade-credential verification.

Requirements before government data access

Before any activation, Provzo must identify the exact API and owning authority, purpose, requested fields and scopes, legal basis, recipients, whether use is optional, retention and deletion, effect on approval, failure path and manual alternative. The affected person must receive a just-in-time disclosure and give separate purpose-scoped consent. A new API, purpose or scope requires new consent.

Launch blockers remain visible

Registered legal entity details, office address, monitored support and grievance channels, registration or tax disclosures, website and stable policy URLs remain required before commercial launch or third-party onboarding where applicable. Unknown facts are not replaced with sample details.