Confirm the business and supported UPI journey
Describe your company, registration jurisdiction, product, customer locations and expected INR volume. Ask which route and customer journey can be approved for that business. An API discussion does not itself establish merchant approval.
NPCI describes UPI and merchant QR integration in its UPI frequently asked questions. Scheme-level functionality is not a promise that every integration offers every flow. PAYJN is not NPCI or an Indian bank.
Separate QR checkout from other app experiences
| Question | Why it matters |
|---|---|
| Which journey is approved? | QR, app handoff and other flows have different customer steps. |
| How does mobile checkout work? | A same-device payment needs a supported completion and return path. |
| What expires? | The displayed instruction and merchant order must have clear rules. |
| What confirms the order? | Your backend needs the documented final status, not just a return URL. |
Test the exact environment customers use, including mobile browser and in-app contexts where relevant. Do not advertise an app experience until it has been confirmed and tested on the approved route.
Design INR order status and callback handling
Store your merchant order reference and the provider transaction identifier. Follow the approved amount format, verification process and notification acknowledgement rules. Define when the order remains pending and which final status permits fulfilment.
Plan for repeated updates and an interrupted create request. Your system should not credit the same purchase twice or create a replacement payable order without checking the existing transaction as documented.
Explain any multi-merchant platform model
If your product serves other merchants, identify the underlying businesses and their transaction flows during review. Confirm how their orders are separated and how new merchants are approved. Never treat platform API access as permission to process unknown businesses.
Request the applicable fee, settlement and limit schedule for the approved structure. Do not assume a payout product, refund feature or particular UPI experience is included simply because a collection API is available.
Complete an operational launch check
- Merchant eligibility and actual UPI flow confirmed.
- Customer instructions tested on intended devices.
- Pending, expired and successful orders tested.
- Notification authentication and repeated delivery handled.
- Reconciliation references and exception support agreed.
Review PAYJN’s India payment API scope, then send the website, business model, average order amount and monthly volume for a merchant discussion.
Get a merchant-specific integration review
Share your website, target market, required methods and expected volume. Our team will review merchant fit and the proposed payment flow. Do not send API secrets or customer banking data in a first enquiry.
Discuss India integrationMethod availability, transaction limits, fees and production access depend on the approved merchant setup. Operator references describe the payment ecosystem and do not imply a direct partnership.