Guides

UPI App Development Guide: Intent Flow, QR Payments, Collect Requests & Merchant Workflows

10 min read Published 2026-06-04By Vayqube Payments Engineering Team

Key Takeaway Summary

A reliable UPI app needs more than a payment button. It should include intent flow, QR flow, collect requests, payment callbacks, status polling, transaction state management, merchant settlement views, refunds, audit logs, and secure backend APIs.

The Common Challenge

UPI products often fail when teams treat the payment screen as the full system and ignore callbacks, pending states, reconciliation, fraud checks, merchant operations, and support visibility.

Critical Areas to Evaluate First

Area	What to Check	Why It Matters
UPI Intent Flow	App redirect, payment initiation, response parsing, timeout handling, and fallback status checks	Intent payments depend on external PSP apps, so the product must handle user exits, pending states, and failed redirects.
QR Flow	Static QR, dynamic QR, order mapping, amount validation, merchant IDs, and reconciliation	QR payments are common for merchants, but they need accurate mapping between payment events and business orders.
Collect Request	Request creation, expiry rules, customer approval, callback processing, and status polling	Collect requests are asynchronous and require strong state management for pending, approved, declined, or expired payments.
Merchant Operations	Settlements, refunds, payment history, dispute views, reports, and role-based admin access	UPI app development must support operations teams, not only end-user payment completion.

What Is a UPI Application?

A UPI application is software that lets users or merchants initiate and receive payments through India’s Unified Payments Interface. It may support UPI intent, QR payments, collect requests, merchant payment links, status callbacks, refunds, reports, and payment history depending on the business model.

Consumer UPI apps focus on fast payment initiation, history, notifications, and user trust.
Merchant UPI apps need QR mapping, settlement reports, refunds, staff roles, and dashboards.
Business UPI systems need audit logs, reconciliation, webhook processing, and admin controls.

UPI Intent Flow Architecture

UPI intent flow usually starts when your app creates a payment request and redirects the user to a PSP or banking app. The user approves payment externally, then your app receives a response or checks payment status through backend APIs. The backend should not trust the client response alone; it should verify status through trusted provider callbacks or status APIs.

Create a server-side payment/order record before opening the UPI intent.
Handle success, failure, pending, timeout, cancelled, and duplicate callback states.
Use polling or provider status APIs when app redirects do not return reliable final state.

QR Payments and Collect Requests

QR flow works well for merchants because customers scan and pay without manually entering details. Collect requests work when the merchant or business sends a payment request for customer approval. Both flows need order mapping, expiry handling, payment status checks, settlement reports, and support visibility.

Use dynamic QR codes when payment amount, order ID, or merchant context changes per transaction.
Track collect request expiry and notify users before payment requests become invalid.
Create reconciliation exports that match provider payments to orders, invoices, or merchant accounts.

Business & Operational Impact

Payment Reliability

Clear transaction states reduce confusion around pending, duplicate, failed, or delayed UPI payments.

Merchant Adoption

QR payments, settlement views, and reports help merchants trust the platform faster.

Support Efficiency

Audit logs and payment history reduce manual investigation for failed or disputed payments.

Step-by-Step Implementation

1
Define whether the product needs consumer UPI, merchant UPI, QR payments, collect requests, payment links, or all flows.
2
Design order, transaction, merchant, settlement, refund, callback, and audit-log data models.
3
Build backend APIs for UPI initiation, callback verification, status polling, refunds, reports, and admin actions.
4
Create customer, merchant, and admin interfaces for payment history, QR codes, collect requests, and settlement visibility.
5
Test success, failure, pending, timeout, duplicate callback, refund, and reconciliation scenarios before production launch.

Frequently Asked Questions

What is a UPI application?

A UPI application is software that enables payments through India’s Unified Payments Interface. It can support intent payments, QR payments, collect requests, payment links, merchant dashboards, refunds, transaction history, settlement reports, and secure backend status verification.

How does UPI intent flow work?

UPI intent flow redirects the user from your app to a UPI-enabled payment app for approval. After payment, your backend should verify the transaction through trusted callbacks or provider status APIs before marking the order as paid.

What is a UPI collect request?

A UPI collect request is a payment request sent to a user for approval. The user can approve, decline, ignore, or let it expire, so the system must track pending, successful, failed, and expired states accurately.

How much does UPI app development cost?

UPI app development cost depends on user flows, provider integrations, merchant dashboards, refunds, reconciliation, compliance needs, mobile platforms, admin tools, and QA depth. A QR-only MVP costs less than a full merchant payment platform.

upi app development guide

UPI app development

UPI payment app development

UPI intent flow

UPI collect request

QR payment app development