Manage Multiple UPI Merchant Accounts: Paytm + PhonePe

Learn how to manage multiple upi merchant accounts with one dashboard, connect Paytm Business and PhonePe Business, verify payments, and reconcile branches.
Two smartphones and QR stands feed verified UPI payment records into one blue business dashboard.

Manage multiple upi merchant accounts in one place when your business accepts payments through both Paytm Business and PhonePe Business. This guide shows how to connect both accounts to PaymentSetu, keep the customer payment going directly to the right merchant account, and give your team one verification and reconciliation view.

Why businesses end up with two merchant apps

Paytm Business and PhonePe Business can both be useful for a shop, service company, or multi-branch operation. You may have started with one QR at your first counter, added another provider for a new branch, or kept both because customers already recognise both payment options.

The payment itself is not the difficult part. A customer scans a QR and pays through UPI. The work starts after that: someone has to check the correct merchant app, identify the payment, match it to an order or invoice, and update the business record.

Checking two apps separately creates a fragmented operating routine:

  • staff look in different places for payment confirmation;
  • accountants receive separate transaction views;
  • branch or counter references are harder to compare; and
  • website or billing software needs a reliable paid-status signal.

PaymentSetu gives you a common verification layer. It does not replace either merchant account and it is not a payment gateway. The customer pays directly to the connected Paytm Business or PhonePe Business merchant account; PaymentSetu checks the payment details, matches them with the order, and sends the result to your dashboard or webhook.

What you need before setup

Prepare these items before connecting the two sources. This makes the setup easier to hand over to an owner, accountant, or developer.

  1. An active Paytm Business merchant account that receives your business payments.
  2. An active PhonePe Business merchant account that receives your business payments.
  3. Access to the registered mobile number for each account so you can complete the connector’s OTP login yourself.
  4. A list of the places where you collect money: for example, main shop, second branch, website, WhatsApp orders, or service invoices.
  5. Your order, invoice, or customer reference format. Use one reference for each payment request so your team can match the payment later.
  6. A PaymentSetu account and a plan with enough credits for the successful payments you want to verify.

Keep the two merchant accounts clearly labelled in your internal process. “Paytm – Main Store” and “PhonePe – Online Orders” are easier for a cashier or accountant to understand than two unnamed connections.

UPI supports payments between a customer and a merchant account. For background on how UPI transactions and merchant receipts work, see the NPCI UPI FAQ.

Step 1: Confirm the two payment destinations

Why: every payment should land in the intended merchant account before you add a common dashboard.

First, sign in to Paytm Business and PhonePe Business separately and confirm which merchant account each one represents. Note the business name, branch or outlet reference, and the account used for settlement in your own records.

Then check your payment flow:

  1. Identify which QR or checkout currently sends a customer to Paytm Business.
  2. Identify which QR or checkout currently sends a customer to PhonePe Business.
  3. Keep the two destinations separate in your order notes or branch mapping.
  4. Do not replace a merchant QR with a personal UPI ID just to make reporting easier.

Success looks like this: a staff member can tell which QR was used, which merchant account should receive the money, and which branch or sales channel owns the order.

The PaymentSetu guide to accepting UPI payments for a small business explains the same direct-to-merchant model if you are documenting the process for new staff.

Step 2: Create your PaymentSetu account

Why: PaymentSetu needs one workspace where it can verify transactions from both connected merchant sources.

Open the PaymentSetu registration page and create your account. After signing in, choose the plan that matches your expected number of successful payments. A credit represents one successful payment verified, so count payment volume rather than the number of merchant accounts.

Before connecting anything, decide who owns these tasks:

  • the business owner controls account access and merchant connections;
  • the developer adds the API key or webhook URL, if you use a custom checkout; and
  • the accountant uses the transaction history and reports for reconciliation.

Do not send an OTP, API key, or webhook signing detail in a public group. Complete OTP login yourself in the relevant connector screen and give your developer only the integration credentials they need.

Success looks like this: you can sign in to PaymentSetu, see your selected plan, and reach the area for adding merchant accounts or creating payment orders.

Step 3: Connect Paytm Business and PhonePe Business

Why: each payment source must be verified against the correct merchant account before both sources appear in one view.

In PaymentSetu, add the Paytm Business connection first. Select the Paytm Business connector, enter the requested merchant-account details, and complete the OTP login using the registered number. Save it with a clear source name such as “Paytm – Main Store”.

Next, add the PhonePe Business connection. Select the PhonePe Business connector, enter its requested details, complete that account’s OTP login, and save it with a different source name such as “PhonePe – Branch 2”.

Use this small mapping as your checklist:

SourcePayment destinationUseful internal labelMatch against
Paytm BusinessYour connected Paytm merchant accountPaytm plus branch or channelOrder reference, amount, UTR
PhonePe BusinessYour connected PhonePe merchant accountPhonePe plus branch or channelOrder reference, amount, UTR

Do not assume that adding two logins merges the merchant accounts themselves. The accounts remain separate payment destinations. PaymentSetu brings their verified transaction records into a unified dashboard so you can work from one operational view.

Success looks like this: both connections are visible, each has a distinct label, and you can tell which merchant source a verified transaction belongs to.

Step 4: Create one payment flow for every order

Why: a shared dashboard is most useful when every payment request has a unique order or invoice reference.

For a website, billing system, or custom application, create a PaymentSetu order for the amount due and attach your own client transaction ID. PaymentSetu’s API includes:

  • POST /api/create_order to create an order and dynamic QR;
  • GET /api/order_status/{client_txn_id} to check the payment status; and
  • GET /api/check_credits to check remaining verification credits.

Use the client transaction ID as the common key in your shop, CRM, invoice system, and accounting export. Include a branch or channel code inside your own reference format, for example MAIN-2026-0042 or WEB-2026-0042. The exact format is yours; the important part is that it is unique and easy to search.

The customer then scans the generated QR and pays by UPI. The money goes directly to the merchant account associated with that payment flow. PaymentSetu matches the incoming transaction using the order details, including the amount and UTR, and updates the payment status.

For WooCommerce, the PaymentSetu WooCommerce plugin can connect the store to the verification service without custom API work. For hosting companies, the PaymentSetu WHMCS module can verify WHMCS invoice payments and pass the paid status back to the billing system.

Success looks like this: a new order creates a payment request, the customer sees the correct QR, and your website or billing system receives a verified status instead of relying on a screenshot.

Step 5: Use one dashboard for branches and counters

Why: staff should be able to answer “was this paid?” without opening two separate merchant apps for every order.

Use the unified dashboard as the first place to review payment status. A practical daily view contains:

  1. the order or invoice reference;
  2. the source name, such as Paytm or PhonePe;
  3. the branch, counter, website, or service channel;
  4. the expected amount and received amount;
  5. the UTR or payment reference; and
  6. the verification status and timestamp.

For a physical business, put the source label into the counter or branch procedure. For online orders, keep the source and client transaction ID with the order record. For WhatsApp or invoice collections, include the reference in the payment request so the person checking the dashboard has a clear search term.

This gives you one workflow while preserving the important distinction between payment destinations. You are not pooling money into PaymentSetu; you are centralising verification and visibility while the funds go to your own connected merchant accounts.

Success looks like this: a cashier, owner, or support agent can search a reference and see the verified result, source, amount, and next action from one workspace.

Step 6: Export records for reconciliation

Why: your accountant needs a repeatable way to compare orders with verified UPI credits and the two merchant statements.

At the end of each day or accounting period, export the PaymentSetu transaction report for the same date range used in your sales system. Keep the following columns in your working sheet:

FieldWhy it matters
Client transaction IDJoins the payment to the order or invoice
SourceSeparates Paytm Business and PhonePe Business
AmountConfirms the expected and received value
UTR or payment referenceHelps match the merchant statement
StatusDistinguishes verified payments from open orders
Date and timeSupports daily and branch-level review

Reconcile in this order:

  1. Start with orders marked paid by your store, WHMCS installation, or internal billing system.
  2. Match each one to a verified PaymentSetu record using the client transaction ID.
  3. Check the amount and UTR against the relevant Paytm Business or PhonePe Business statement.
  4. Group totals by source and branch so the owner can compare collections without mixing destinations.
  5. Review unmatched rows before closing the period.

The benefit is a single operational report with a clear source column, not a pretend single merchant account. Your financial records still show where the money was received.

For context, Paytm’s official support documentation lists transaction, refund, settlement, dispute, and balance reports in its merchant dashboard. PhonePe’s official merchant materials also describe transaction, settlement, and reconciliation access. PaymentSetu adds a common verification record so your internal order and merchant-statement checks have a consistent starting point.

Which PaymentSetu plan fits your volume?

Choose by the number of successful payments you verify in 30 days, including payments from both merchant accounts.

PlanCapacityGood fit
Starter100 creditsA small shop or freelancer testing a two-source workflow
Pro1,000 creditsA growing store, service business, or hosting operation
Business100,000 creditsHigh-volume, SaaS, or multi-branch operations

All plans include dynamic QR, webhooks, a unified dashboard, real-time notifications, API access, and email support. The Business plan is ₹1,499 per 30 days and adds priority support plus a dedicated account manager. It is the natural fit when Paytm Business and PhonePe Business feed a larger multi-branch operation and you want the headroom to verify more payments without changing the workflow.

You can view the current PaymentSetu pricing before selecting a plan. If you are comparing a flat verification plan with percentage-based gateway pricing, see the worked examples in Payment Gateway Fees on ₹1L, ₹5L and ₹10L Sales. PaymentSetu charges a flat plan price rather than a commission on each verified payment, and the customer’s payment remains directed to your own merchant account.

Common mistakes to avoid

Treating a screenshot as payment proof

A screenshot is not the same as a verified transaction. Use the order reference, amount, UTR, and verified status in your dashboard or webhook before marking an order paid.

Mixing the two sources in staff instructions

Write the source name and branch in each procedure. If a cashier is told only to “check the UPI payment”, they may look in the wrong merchant app.

Reusing an order reference

Every payment request should have a unique client transaction ID. Reusing an old reference makes later reconciliation harder, especially when the same amount is collected more than once.

Giving everyone full account access

Keep merchant logins, OTPs, API keys, and webhook signing details with the people who need them. Share reports and order references with staff instead of sharing primary credentials.

Forgetting the source column in exports

A combined report is useful only when it still identifies Paytm Business versus PhonePe Business. Preserve that source field when you download or transform the report.

FAQ

Can I manage Paytm Business and PhonePe Business together?

Yes. Connect the active Paytm Business and PhonePe Business merchant accounts to PaymentSetu and use its unified dashboard for verified transaction records. The merchant accounts remain separate payment destinations, while the verification view is centralised.

Does PaymentSetu receive or hold the customer’s money?

No. PaymentSetu is a payment verification service, not a payment gateway. The customer pays directly to the connected merchant account, and PaymentSetu matches the payment and sends the verified result.

Can I use one dashboard for several branches?

Yes, when the branches use the connected merchant accounts and your order references identify the branch or channel. Add clear source labels and keep the branch code in the client transaction ID so your team can filter and reconcile the records correctly.

How do I verify a payment without trusting a UPI screenshot?

Create a unique order and dynamic QR, then wait for the verified status or signed webhook from PaymentSetu. Match the client transaction ID, amount, and UTR before updating the order as paid.

Which plan is best for two merchant accounts?

Choose based on combined successful-payment volume, not the number of connected accounts. Starter covers 100 credits, Pro covers 1,000 credits, and Business covers 100,000 credits; each credit represents one successful payment verified.

Previous Article

Payment gateway integration in HTML website: UPI guide

Next Article

How to Choose a Payment Gateway: 12-Point Checklist

Write a Comment

Leave a Comment

Your email address will not be published. Required fields are marked *