Refund & Reversal Policy

1. Atomic Transaction Loop Failures

An Atomic Failure occurs when an end-user triggers a digital payment payload, funds are successfully verified and debited from the customer's original bank source ledger, but an intermediate telecom or network cluster disconnects before routing the data to the target operator node (Jio, Airtel, State Power Grid, FASTag NHAI, etc.).

• Our payment system initiates an automated reconciliation check inside 180 seconds to capture the dropped data payload.
• If the upstream operator confirms non-receipt of tokens, the network instantly cancels the transaction sequence and flags it for full automated credit reversal.

2. Turnaround Time (TAT) Framework

Once a fund reversal is validated and approved by the PAY2FLOW services Pvt. Ltd ledger core, the data packet is returned directly to your payment gateway router. The actual credit back into your account depends heavily on standard national banking clearing loops:

• UPI Payments: Reversals are usually resolved within 24 to 48 banking hours.
• Debit/Credit Cards & Net Banking: Clearing and credit settlement loops typically require 3 to 7 business days, depending on your issuing bank's internal processing dockets.

3. Non-Refundable Scenarios & Consumer Liability

Because our system routes transaction payloads instantly through external automated digital rails, certain operations are strictly permanent and cannot be modified or refunded under any financial circumstance:

• User Input Error: If a recharge or bill payment settles successfully on a wrong mobile number, wrong Subscriber ID, or wrong CA identifier provided by the consumer, the transaction is legally finalized. Funds cannot be retrieved or refunded.
• Operator Handover Success: Once an external operator node registers the transaction success log and dispatches the data or utility activation token to your device, the transaction is marked complete.

4. Double Debit Rectification

If a network lapse causes a user to click the "Proceed to Secure Gateway" button multiple times, resulting in a duplicate debit for a single utility account reference:

• Our system's automated audit trail catches duplicate transaction hashes within the same clearing cycle.
• One payload is applied to the utility account, while the duplicate debit string is flagged and queued for a standard banking loop reversal automatically.

5. Dispute Resolution & Customer Support Node

If your account ledger shows a debit string that has been unresolved for more than 7 business days, you can escalate the matter directly to our specialized support desk. Please provide the exact transaction metadata (Transaction ID, Date, Value, Debited Account Statement screenshot):