Payment Gateway Questions & Answers

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.

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.

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

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

Validate the instalment amount against the ₹5L per-txn and ₹10L daily caps so eligibility is accurate.

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 validation for audit.

Recommend NetBanking (IMPS/RTGS/NEFT) as the primary fallback for high-value vehicle down payments.

Offer debit/credit cards only if the dealership supports large-ticket card processing.

Use split UPI only when both the dealer and PSP allow it and the customer agrees.

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

Check the bill’s healthcare/hospital MCC or purpose code and confirm the hospital is NPCI-verified for high-value UPI.

Validate the payable amount against the applicable per-txn and daily caps before showing eligibility.

Confirm acceptance via the gateway/PSP pre-auth response.

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

• Test refund routing for split settlements (airline + OTA + convenience fee) to ensure each leg stays within the new UPI per-transaction caps and doesn’t trigger cap violations.
• Simulate partial refunds and multi-PNR changes to verify prorated amounts return correctly to the payer VPA without exceeding per-day caps.
• Run chargeback scenarios (wrong fare, no-show, cancellation) to ensure dispute evidence maps back to the original split payments.
• Validate reversal logs + reconciliation so every refund/chargeback matches the original UPI txn ID and respects NPCI’s updated cap rules.

• Create test cases for full, partial, and prorated refunds plus chargeback disputes, ensuring each maps to the original parent/child UPI txn IDs and preserves purpose code.
• Run end-to-end flows: (a) trigger refund via API, (b) simulate PSP/bank responses (success/failure/partial), (c) verify ledger reversals, refund-linked child txn IDs, and invoice status updates.
• Validate idempotency, webhook handling, and reconciliation: confirm duplicate callbacks don’t double-refund, disputes attach evidence to original txn, and nightly reports reconcile refunded amounts vs. UPI settlement.