Payment Gateway Questions & Answers

Recommend NetBanking (IMPS/RTGS/NEFT) as the primary fallback for large vehicle down payments that exceed UPI caps.

Offer debit/credit cards only if the dealer supports high-value card acceptance.

Use split UPI only if the dealer and PSP allow it and the customer consents.

Show a clear UPI limit reached, choose another payment method prompt to avoid checkout failure.

Have the app fetch the effective-dated UPI limit table (post–15 Sep 2025) from your backend for the real estate token category at checkout.

Before creating the UPI intent, compare token amount + any prior same-day token UPI payments against that category limit.

If it breaches, block the UPI option, show a clear higher-cap / fallback message, and log the decision with category + date for audit.

• Add a use-case mapper that tags every invoice with the correct UPI purpose code/MCC (e.g., air travel, hotels, tours) based on product type or booking category.
• Auto-embed the purpose code in the UPI collect request / deep link so the gateway receives a clean, audit-ready tag.
• Store the purpose code + UPI txn ID in your ledger for reconciliation and export it in monthly audit reports.
• Block invoice creation if the booking lacks a mapped purpose, forcing consistent tagging across all travel transactions.

Tag each SIP as mutual-fund (MCC/purpose code) and confirm the AMC is NPCI-verified for high-value UPI.

Enforce per-txn ≤ ₹5,00,000 and 24-hour aggregate ≤ ₹10,00,000 checks, using the lower bank/PSP cap when applicable.

Block or auto-split charges that exceed limits and require idempotency keys for retries.

Log validation results with UPI txn ID, purpose code, merchant verification flag, amount, daily aggregate, and audit trail.

Check the SIP invoice’s purpose code/MCC = mutual funds and confirm the AMC is NPCI-verified for high-value UPI.

Validate the instalment amount against the ₹5L per-txn and ₹10L daily caps before showing eligibility.

Use the gateway/PSP pre-auth response to confirm the high-limit category is accepted.

Display a higher-limit eligible banner only after all checks pass and log the result for audit.

Verify the SIP is tagged with the mutual-fund MCC/purpose code and that the AMC/merchant is NPCI-verified for high-value UPI.

Check the instalment against the per-txn cap and the payer/merchant 24-hour aggregate before promising eligibility.

Confirm the gateway/PSP pre-auth response accepts the high-limit category.

Show a non-promissory real-time banner only after all checks pass, timestamp the validation, and log the result for audit.

Recommend NetBanking (e-mandate) as the main fallback when SIP instalments breach UPI per-txn or daily caps.

Offer debit/credit card mandates if supported by the AMC for recurring payments.

Use split UPI only if AMC policy allows; otherwise direct users to a single higher-limit option.

Show a clear UPI limit reached choose another method prompt to prevent SIP setup failure

ecommend NetBanking (e-mandate) as the primary fallback when SIP instalments exceed UPI per-txn or daily caps.

Offer debit/credit card mandates only if supported by the AMC for recurring payments.

Use split UPI only if AMC and PSP policies allow; otherwise direct users to a single higher-limit method.

Show a clear UPI limit reached, choose another payment method prompt to prevent SIP setup failure.

The accounting package should store the revised category-wise UPI limits as effective-dated compliance rules starting September 15, 2025.

Each hospital bill must be validated in real time against its mapped category limit before posting the payment entry.

Any breach should block posting, raise a compliance error, and log the exception for audit review.

• Purpose-code GL mapping: route GeM receipts to government procurement GLs using the embedded purpose code/MCC so high-value payments post to correct accounts.
• Split-settlement rules: allocate amounts across supplier, taxes, fees, and platform commissions with exact child-payment links for each split.
• Cap & merchant verification checks: enforce NPCI per-txn and daily caps and confirm merchant/GeM-verified status before posting; flag or block over-limit receipts.
• UPI traceability & refund handling: store immutable UPI txn ID, purpose code, parent/child links, and ensure refunds/chargebacks reconcile against the original split entries.