Payment Gateway Questions & Answers

Create a dedicated high-value FX-retail UPI clearing account so large inbound remittances don’t mix with standard UPI receipts.

Post each tranche (if split) with its own RRN and hold it in the clearing ledger until PSP settlement and FX conversion are confirmed.

Map final credited amounts to FX Remittance Revenue/Receipts with rate/fee adjustments applied at posting time.

Ensure refunds/chargebacks and FX reversals hit the same high-value clearing ledger for clean reconciliation and audits.

Tag each UPI payment with the NPCI-approved purpose code GOLD (or the specific PSP-supported jewellery code) when creating the UPI intent.

Store this code in the transaction record, settlement ledger, and audit trail so all gold/jewellery receipts can be filtered easily.

Ensure PSP callbacks return the same code and validate it before posting to revenue or clearing accounts.

Finance teams should enable:

• Daily UPI volume alerts when ticketing inflows reach 80–90% of the allowed daily cap.
• High-value payment alerts for any UPI transaction above ₹1 lakh (or your PSP’s threshold).
• Failure-rate spike alerts if declines/timeouts exceed ~5% in a 15-minute window.
• Settlement delay alerts when UPI receipts don’t clear within the expected T+1 window.

Tag each club membership UPI payment with the NPCI/PSP-supported purpose code CLUB (or the specific membership code your PSP provides) when generating the UPI intent.

Store this code in the transaction record, ledger entry, and audit trail so finance teams can filter membership receipts easily.

Verify that the PSP callback returns the same code before posting to the membership revenue or clearing ledger.

When UPI caps are hit mid-checkout, the software should recommend debit/credit cards, net banking, and wallets as immediate fallback options.

It should also suggest bank transfer (IMPS/NEFT/RTGS) for high-value hospital bills.

The fallback choices must appear instantly with a clear reason for the UPI failure for user transparency

Create a separate high-value UPI clearing account so gold/jewellery receipts above the per-txn cap don’t mix with regular UPI inflows.

Post each tranche (if auto-split) with its own RRN under one parent order and move amounts to Cash at Bank only after PSP settlement.

Map these payments to a dedicated “Gold & Jewellery Revenue” ledger with purpose code tracking for audits.

Ensure refunds/chargebacks reverse against the same high-value clearing ledger, not standard UPI accounts.

• Maintain a category→limit table for GOLD/JEWELLERY (per-txn + daily caps) with bank/PSP overrides and tag each payment category=GOLD before intent creation.
• Pre-validate: if amount > perTxnLimit or (today_inflow_for_category + amount) > dailyAggregateLimit then block, auto-split, or prompt alternate payment.
• Call PSP/NPCI eligibility APIs for bank-specific higher-limit allowance, record RRNs and update daily counters after settlement, and surface clear UI messages/fallbacks to the payer.

Use idempotency keys + a strict retry cap (e.g., max 3 retries on timeouts/5xx only) so duplicate UPI debits can’t occur.

Apply exponential backoff with jitter and a circuit breaker that opens on high latency/error rates, pushing retries to a delayed queue.

Enforce per-hospital and global concurrency limits, queuing excess requests with a short TTL and linking them to the original txn.

Log every retry decision and expose metrics/alerts (retry count, latency, circuit state) so ops can safely tune thresholds.

• Keep an eye on the UPI API's latency and error rate; if the average delay exceeds a threshold (such as two seconds) or the error rate exceeds X%, Change to the degraded mode.
• In degraded mode, only retry temporary problems (timeouts/network) and employ exponential backoff + jitter for retries (e.g., 5s → 15s → 45s) with a maximum retry count.
• Put in place a circuit breaker to stop fresh UPI attempts following a string of failures (such as more than 20% failures in 5 minutes) and direct users to backup methods; record and notify operations of all throttling occurrences.

Create a separate high-value UPI clearing ledger so EMI payments above the standard cap don’t mix with normal UPI inflows.

Post each tranche (if split) with its own RRN into this clearing account and move funds to Loan EMI Collections – Bank only after PSP settlement is confirmed.

Map category = LOAN/EMI so revenue and reconciliation reports separate high-value EMIs.

Ensure refunds/chargebacks reverse against the same high-value clearing ledger for clean audits