UPI
The payment system that moves money between participating accounts.
Unified Payments Interface (UPI) is a payment system in India that lets customers pay in real time from linked bank accounts.
The payment system that moves money between participating accounts.
Where your customer reviews and authorises the payment.
Connects UPI to your checkout and sends payment status updates to your backend so your site can show the result.
Confirm how UPI should appear at checkout, what steps your customers will follow and whether your project needs to support a specific UPI app.
A‑Pay lists PhonePe and PhonePe by Number separately from UPI. See all payment methods in India.
If your website already has a checkout, start with the screen where customers choose how to pay. Look at how that screen shows the order total, names each payment option and tells customers what happens next. Those details help you decide where to introduce UPI and what customers should see when they select it.
Both options require backend integration. Before development, identify the checkout screens you want to keep, the screens your team will need to update and the point at which the customer enters the agreed UPI payment flow.
To confirm a UPI payment flow, tell A‑Pay what customers are paying for, where they start the payment and which devices they use. These details help the team review the setup against your checkout requirements.
What customers pay for
Describe the purchase or account funding activity and where UPI fits in that journey.
Availability for your business
Confirm whether UPI can be enabled for the payment activity you’ve described.
Where payments start
Tell us whether customers begin on desktop web, mobile web or in an app. If one channel accounts for most of your payments, mention it.
The flow on each device
Ask what customers will see, where they will complete the payment and what instructions they’ll need.
Any app your checkout depends on
Name the UPI app if support for it is a requirement.
App compatibility
Confirm whether the agreed setup supports that app before using its name or logo in your checkout.
Your typical payment amount and monthly transaction count give A‑Pay a starting point for discussing commercial terms. Share both figures, along with the smallest and largest payments you expect to accept.
If customers make many low-value purchases, ask how processing fees would apply to a typical transaction and what that would mean across a month of payments. Share your expected monthly count as well as the periods when payment activity tends to peak. If a large share of purchases falls near the bottom of your price range, use that amount when discussing fees and minimum transaction limits.
If customers make larger purchases less often, start with your typical payment and the highest amount you expect to accept. Ask whether both fit within the transaction limits that would apply to your project. If your checkout combines several items into one order, use the combined total when estimating your upper range.
Ask when A‑Pay would send merchant settlements and when you should expect the funds to become available under the agreed terms. Use that schedule to plan around expenses such as supplier payments or other bills that fall due during the month.
Agree on the payment flow for your project and get the configuration details your developers need.
Use the agreed integration to start UPI payments. Configure your backend to receive payment status updates and use them to update the matching order.
Verify what customers see when a payment is confirmed, when the result is still pending and when the payment fails. Check that the order status reflects the result recorded in your backend.
Use your first live payments to see where customers need clearer instructions or help from your team.
Count payment attempts and confirmed payments over the same period. Track retries separately so you can see where customers are starting over.
Gather the order reference, amount, approximate time and transaction ID if available. Check the recorded result before marking the order paid or asking the customer to try again.
If customers often retry on mobile or ask about the same message, review what checkout tells them while a payment is being checked.
Customer report
My bank account was debited.
Order status
Awaiting payment
First check
Look up the original UPI transaction in your backend.
Share the transaction ID and a description of the issue with A‑Pay support. Use what you learn to update your checkout instructions and give your team a consistent way to handle similar cases.
Availability depends on where your business is registered and what you collect payments for. Share your country of registration, the products or services your customers in India pay for, and the legal entity that would receive the funds. A‑Pay can then assess your proposed setup.
UPI can be added to an existing A‑Pay project if the method is available for that setup. Share your project reference and where you want to introduce UPI. A‑Pay can confirm whether your developers need to update the checkout or backend before you enable the method.
A‑Pay reviews customer payouts separately from payment acceptance. If your platform needs to send money to customers in India, describe who receives the funds and what triggers each payment. The team can confirm which payout methods are available for your project.
Confirm the refund process for your UPI setup before publishing your refund instructions. Tell A‑Pay whether you need full refunds, partial refunds or both. Once the process is agreed, explain how customers can request a refund and what your support team needs to identify the original payment.
Automatic subscription renewals require separate confirmation. When discussing your checkout, tell A‑Pay whether customers can approve each renewal themselves or whether your billing model requires automatic collection. That distinction helps the team assess what your UPI setup can support.
If you run multiple storefronts, tell A‑Pay which one you want to launch first. Share its URL and how it shares checkout or order management with your other sites. The team can review how to scope the initial setup and what would need to be confirmed before expanding it.
Language options depend on who hosts the payment screen. If you manage your own checkout, your team can prepare its wording in the languages your customers use. For A‑Pay’s Hosted Payment Page, confirm which languages are available for your setup before planning a launch in a particular language.