Payment Gateway Questions & Answers

Show a real-time eligibility banner by checking the booking’s purpose code/MCC and confirming the merchant is marked NPCI-verified for high-value UPI.

Validate the amount against the new ₹5L per-txn cap before displaying the message.

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

Surface the message only after these checks pass to avoid false assurances.

Use purpose-code/MCC-driven GL mapping so high-value travel UPI receipts post to the correct air/hotel/ancillary ledgers.

Apply split-settlement rules that allocate the receipt across supplier, fees, and taxes exactly as per the booking engine.

Validate NPCI’s ₹5L per-txn / ₹10L per-day caps before posting and flag any over-limit receipts.

Record the UPI txn ID + purpose code with each ledger entry to support reconciliation and audits.

Use purpose-code/MCC-driven GL mapping so high-value travel UPI receipts post to the correct air/hotel/ancillary ledgers.

Apply split-settlement rules that allocate the receipt across supplier, fees, and taxes exactly as per the booking engine.

Validate NPCI’s ₹5L per-txn / ₹10L per-day caps before posting and flag any over-limit receipts.

Record the UPI txn ID + purpose code with each ledger entry to support reconciliation and audits.

Your accounting package should verify that each UPI receipt tagged under the travel category (MCC-based) stays within the new ₹5 lakh per-transaction and ₹10 lakh per-day NPCI limits.

Check that the merchant is NPCI-verified for high-value UPI before applying these caps.

Block or flag any posting that exceeds limits or has missing/incorrect purpose codes.

Store the UPI txn ID, purpose code, and validation result for audits.

Your accounting package should verify that each UPI receipt tagged under the travel category (MCC-based) stays within the new ₹5 lakh per-transaction and ₹10 lakh per-day NPCI limits.

Check that the merchant is NPCI-verified for high-value UPI before applying these caps.

Block or flag any posting that exceeds limits or has missing/incorrect purpose codes.

Store the UPI txn ID, purpose code, and validation result for audits.

• Simulate UPI donations (below/above ₹1L) in a sandbox to verify the correct UPI corridor is used.
• Test partial/full refunds using original RRNs and confirm PSP processing under new capped rules.
• Trigger mock chargebacks via PSP dispute APIs to validate temporary holds and ledger reversals.
• Reconcile results against PSP confirmation files to ensure refund/chargeback entries match and audit trails stay accurate.

Create a high-value UPI clearing ledger so large donations don’t mix with regular UPI inflows.

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

Tag postings with category DONATION for audit filters.

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

Capture the UPI RRN from the PSP callback and store it on the membership invoice record.

Insert it into the GST e-invoice JSON under PayDtls.PayRefNo before IRP submission.

Render the same RRN in the PDF’s Payment Details section (e.g., UPI Reference ID: XXXXX).

If payments are split, list all RRNs under the same membership invoice for audit clarity.

Create a high-value UPI clearing ledger so large B2B procurement payments don’t mix with standard UPI transactions.

Post each tranche (if split) with its own RRN into this clearing account and move it to the Supplier Payables – Bank ledger only after PSP settlement.

Tag all postings with category B2B_PROCUREMENT for audit filters.

Ensure refunds/adjustments reverse against the same high-value clearing ledger

• Maintain a category→limit table for B2B_PROCUREMENT (per-txn and daily caps) and tag each supplier payment with this category.
• Pre-validate block or auto-split if amount > perTxnLimit or (today_inflow + amount) > dailyLimit.
• Call PSP/NPCI limit-eligibility APIs for bank-specific higher limits.
• On success, store RRNs and update daily counters for audit and reconciliation."