Frequently asked questions, clearly answered.

UniWeb is a merchant payment-operations technology platform. It combines onboarding, Test Mode, payment links, QR journeys, transaction reporting, refunds, settlements and support workflows. Live financial services depend on merchant approval and activated banking or payment partners.

We match payment links and QR as the reliability bar. Live cards and UPI use those partners when keys are on. We do not copy Route, Easy Split, POS or a consumer wallet. See the Compare page for the honest table.

Yes. Test Mode and the platform tour are designed for demos and integration checks. Test transactions do not move real money and must not be treated as real payment confirmation.

Sole proprietorships, partnerships, LLPs, companies and other supported entities may apply. The required documents and final eligibility depend on the entity type, use case, business category and payment-partner policy.

No. Registration creates an account. Live Mode requires complete KYC, business and website review, bank verification, risk acceptance, commercial setup and partner activation.

KYC helps identify the merchant, authorized signatory, beneficial owners, business activity and settlement bank. It supports fraud prevention and applicable legal and payment-partner obligations.

A sole proprietor and a private company have different ownership and registration evidence. UniWeb shows entity-relevant documents so merchants are not asked to upload every possible document.

The KYC page shows the status and available reason. Upload a clear, current replacement that matches the registered name and details. A rejected document does not automatically close the account.

A reference copy may be available for review. The binding acceptance is shown to the signed-in merchant and records the agreement version, merchant identity, timestamp and audit details.

Depending on activation, merchants can use payment links, all-method QR, dynamic UPI QR, fixed-amount QR, checkout and APIs. A method shown in Test Mode may still require separate Live Mode activation.

Yes. Merchants can create separate QR codes for a counter, branch, campaign, product or fixed amount and open transaction history filtered to a specific QR.

Pending means a final success or failure confirmation has not yet been received. Do not deliver solely on a screenshot or pending state; wait for confirmed status and reconcile the transaction.

Test and Live keys are separate. Keep secrets on the server, rotate exposed keys, validate webhook signatures and never place a secret key in browser code, screenshots or public repositories.

The applicable schedule appears in the merchant commercial setup or dashboard. Timing can be affected by bank holidays, partner processing, reconciliation, disputes, risk review and settlement-bank availability.

Common reasons include incomplete KYC, changed bank details, unmatched transactions, refunds, chargebacks, negative balance, suspicious activity, partner instructions or a legal review. The portal should display the available reason.

The merchant first approves and initiates an eligible refund. It is sent to the original payment method through the relevant partner. Final credit timing is controlled by the customer’s bank or payment network.

The merchant submits evidence through the available workflow, but the issuer, bank, card network or payment partner may make the final decision under its rules and deadlines.

UniWeb Admin (and scoped staff) own every merchant account. Bank and PG partners are tech rails — keys and methods in Partner Registry. Partners do not get a UniWeb merchant-management portal and do not “own” your merchants.

Merchants: login.php. Customers: customer_login.php. Super Admin: admin_login.php. Staff/ops: staff_login.php. There is no separate partner login for banks or gateways.

The Portal displays an IST clock and session countdown. Idle and maximum session limits are enforced by portal type. Save work before expiry and sign out on shared devices.

Yes. Merchants can enable optional authenticator-app verification from Settings. Admin and staff accounts use their configured security controls and role permissions.

Change the password, revoke other sessions if available, rotate API and webhook secrets, review staff access and contact support with the incident time. Never send the exposed secret itself.

Staff access is role- and scope-based. Sensitive actions and merchant-management events may be recorded for audit and review.

Yes. UniWeb Test Pay, sandbox API keys, payment links and QR in Test Mode do not move real money and do not attract Live MDR.

Partner MDR + UniWeb platform fee + GST on applicable fees. Settlement follows the written T+N schedule in your Portal. We do not publish a fake 0% live UPI or instant-settlement public rate card.

Your Merchant Portal commercial schedule is the source of truth. Website numbers appear only when a public MDR table is approved for publication.

Include merchant code, transaction or settlement ID, date, amount, payment status and a concise description. Do not send OTPs, UPI PINs, card PINs, CVV, passwords or complete card numbers.

We save a ticket even if email is delayed. Acknowledgement target is 1 business day. Payment or bank issues may take longer because partners must confirm. Keep the CTI reference if you follow up.

Check whether the debit is final and keep the bank reference. Failed debits are often reversed by the bank after reconciliation. Contact the merchant and issuing bank if the normal reversal period has passed.

Terms, Privacy, Refund, Compliance, Trust and Grievance pages are in the website footer. Signed-in merchants accept the Merchant Agreement from Merchant Settings.

No. UniWeb does not issue a consumer PPI wallet and does not sell an NBFC lending product.