The first payment check is not the logo or method name. It is the exact recipient, currency and amount shown inside the current account route.
Public material can describe a payment category, but it cannot establish that a method is currently available to a particular account. This page therefore follows the fields that can be compared without publishing a permanent support list.
Recipient
Open a route you already know and read the recipient exactly as displayed. Stop if a message substitutes a personal bank account, wallet address or QR image, or if the recipient changes after contact moves to chat. A copied logo does not establish ownership.
Method and Currency
Confirm the method and currency together. A bank transfer, card, wallet or other category can carry different account and regional conditions. Do not infer support from an old article, a search result or another user’s screen.
Limits and Fees
Read any minimum, maximum, fee and conversion notice in the current account view before approving a request. This guide does not publish fixed amounts because the applicable figures and eligibility may change.
Reference and Status
Keep the transaction reference, time, amount, recipient and status message. A pending status is not the same as failed or completed. If records conflict, preserve both views before contacting the financial provider through its own known route.
| Field | What to compare | Warning sign |
|---|---|---|
| Recipient | Exact name or account destination | Personal account substituted in chat |
| Currency and amount | Values shown before approval | Last-minute change or conversion pressure |
| Fee and limit | Current account notice | Copied or undated figure |
| Reference | Provider record and time | No traceable identifier |
OTP and PIN
An OTP, UPI PIN, card PIN, CVV, password or recovery phrase is not a support credential. Do not read it to a caller, paste it into chat or type it into a page opened from an unsolicited message.
Stop the request if it adds secrecy, urgency, remote-control access or payment to a personal account. Secure the relevant email and financial accounts before continuing the conversation.
Keep a Dispute Record
Preserve the provider status, recipient, amount, currency, reference, time and relevant message. Record the evidence before a screen expires, but do not reopen a suspicious link merely to improve the record. A bank or payment provider may ask for its own reference format.
Separate Access from the Transaction
A locked account, password reset or device compromise needs its own response. Do not try to solve it by repeating a payment. Secure the account channels first, then compare the transaction record through the financial provider and known service route.
If money has already moved, contact the bank or payment provider through its own application, website or known number. Give the reference and factual timeline, not a password, PIN or one-time code. Preserve later status changes as part of the same record.
Do not repeat a transfer simply because the first status is unclear. Confirm the provider record and reference first; a second payment can make the original problem harder to trace.
If Something Looks Wrong
Use the security response sequence for suspicious contacts or device access. Use account help for access and verification problems. India availability and publication limits are explained on the India source page.
Open the MegaPari India overview to see the wider product map, or consult the source history for dated public observations.