Payment Gateway Questions & Answers

• 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.

• 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

Use latency-based throttling: slow retry dispatch in the ERP queue if UPI API response times exceed your threshold (e.g., >2s for 10%+ calls).

Retry just timeout or network failures and use exponential backoff (5s → 15s → 45s).

After multiple unsuccessful attempts, activate a circuit breaker to halt new UPI attempts and reveal backup options such as RTGS/NetBanking.

To help operations keep an eye on PSP instability, log throttle events.

When UPI caps are hit mid-checkout for utility payments, the ERP finance module should prompt users with clear fallback methods:

• NetBanking (IMPS/NEFT/RTGS) for instant or high-value bill payments.
• Debit/Credit Cards if the amount is within the user’s card limits.
• Auto-debit mandates / NACH for recurring utilities.
• Display a message like: Your UPI limit is reached, try NetBanking or Card to complete this payment.

Enable a daily aggregate cap alert when hospital-bill UPI receipts approach the category’s ₹10L per-day limit.

Add a high-value transaction alert for bills nearing the ₹5L per-transaction cap.

Use an unmapped-purpose/MCC alert to flag hospital payments missing the correct healthcare code.

Enable a settlement mismatch alert when UPI collections don’t reconcile with hospital invoices or gateway settlements.

• Maintain a category→limit table for 'Real Estate Token Amounts' with updated per-transaction and daily caps.
• Pre-validate each payment: check the token amount against these caps before sending the UPI intent.
• Call the PSP/NPCI limit-eligibility API to confirm bank-specific higher-limit support when available.
• If limits are exceeded, auto-split the payment or prompt users to switch to RTGS/NetBanking.

• Simulate UPI payments (below and above ₹1 lakh) in a sandbox to test both standard and high-value corridors for real estate token amounts.
• Run partial and full refunds using the original RRNs and verify that PSPs process them under the new capped rules.
• Trigger chargeback cases from the PSP’s dispute sandbox and confirm that ledger reversals and holds post correctly.
• Reconcile all test results to ensure refund/chargeback amounts match PSP confirmations and update the token-amount audit trail accurately.

If UPI API response times exceed your criterion (e.g., >2s for 10% of calls), use latency-based throttling to decrease the frequency of retry. Use exponential backoff (5s → 15s → 45s) for payments that don't go through or are delayed. Turn on a circuit breaker to stop new UPI attempts after a string of failures and instruct users to use backup methods. Keep track of every throttling event for audits and monitoring purposes.

The accounting package should query the mapped hospital category and current RBI/NPCI limit table in real time at payment initiation.

If eligible for higher limits, it should display a dynamic in-app and checkout banner message confirming the enhanced cap.

This message must be API-driven and audit-logged to ensure regulatory traceability.