UPI integration: questions to take to a provider

Agree the journey you are reviewing

Draw your customer's intended checkout journey before comparing integration proposals. Include the point where an order is created, how the customer receives a payment instruction and how your system learns the result. Describe the journey as a requirement; let the prospective provider confirm what its service can support.

Use NPCI's official UPI information as a starting point for terminology, then obtain the provider's current documentation and onboarding requirements. A general description of UPI does not establish that a particular integration or merchant use case is eligible.

Ask about state changes and exceptions

Request examples for a completed payment, a pending result, a failure and a later status change. Ask how an order is associated with a payment reference and how your application should behave if a customer returns before confirmation arrives. Your team needs one consistent interpretation of each state.

• Which system confirms the final payment status?
• How should duplicate or delayed notifications be handled?
• What is the process for investigating an unmatched record?
• How are refund requests and their outcomes represented?

Set a useful acceptance checklist

Build a test sheet with expected outcomes and named owners. Include logging, access controls, support contacts and a sample reconciliation review. Do not put live credentials or personal customer data in a shared comparison document. Ask the provider to review the final checklist so that a completed pilot means something specific. Keep test results, commercial terms and formal onboarding approval as separate records rather than combining them into a single ‘ready’ label.