#Remitter & Account Info

#1. NPCI Requirements for Remitter Details and Account Info for all Bill Payments

Bill payments require remitter details and payment instrument information, and you will need to format them correctly for different payment methods. This guide provides the exact formatting specifications NPCI requires for each payment mode, plus validation rules to ensure your requests are accepted.

The key principle: each payment method has its own format requirements, from simple UPI addresses to complex card authorization codes, and getting these wrong will cause payment failures.

#2. Fields Reference

#2.1 Remitter Object Properties

#3. Usage Across Flows

• Fetch/Validation requests: remitter is optional.
• Payment requests (Flow 1–3): remitter.name and paymentDetails.accountInfo are required.

#3.1 Sample Payment Request

{
  "refId": "{{REF_ID_FROM_FETCH_OR_VALIDATION}}",
  "paymentDetails": {
    "amount": 50000,
    "mode": "UPI",
    "custConvFee": 120,              // Optional; Total to debit = amount + custConvFee
    "paymentRefId": "{{UNIQUE_DEBIT_ID}}",
    "timestamp": "{{ISO_8601}}",
    "accountInfo": "user@ybl"
  },
  "remitter": {
    "name": "{{PAYER_NAME}}"
  }
}

#4. NPCI Specifications

#4.1 Account Information Format by Payment Mode

#4.2 Code Format Examples

The following table provides detailed formatting specifications for different NPCI codes:

#4.3 Field Handling Rules

#4.3.1 Mandatory Behavior

• In payment requests across Flow 1–3, remitter.name and paymentDetails.accountInfo are required
• The paymentDetails.accountInfo field must contain NPCI-compatible values corresponding to the selected payment mode