#Remitter Details Integration Guide

#Overview

NPCI has introduced comprehensive remittance information handling across two distinct integration flows to accommodate acceptance of remittance data from Agent Institutions for Credit Card Bill Payments. These enhancements ensure compliance with NPCI specifications while providing flexibility for different integration approaches.

#Remitter Details Specification

#Remitter Object Properties

#Key Notes

• NPCI Compatibility: The accountInfo field must be formatted according to NPCI specifications and to be passed with all Bill Payments and the remitter object to be passed with all Credit Card Bill Payments.
• Credit Card Fallback: When remitter name is not provided for credit card payments, the system automatically sends "Not Available" to NPCI
• Remitter vs Cardholder: The person making the payment (remitter) may be different from the credit card holder

#Remitter Details in WL + Custom Payment Flow

#Payment Event Webhook Enhancement

The webhook API for payment events will now support remitter details under the remitter object and account information within the accountInfo property in the incoming payload (See Webhook API Reference).

{
  "orderId": "COUWLje9V7wWs9N3w",
  "transactionId": "UNIQUE_PAYMENT_TRANSACTION_ID",
  "paymentDateTime": "YYYY-MM-DD HH:MM:SS in UTC",
  "amount": "100.00",
  "paymentMode": "CASH|UPI|IMPS|NEFT|AEPS|ACCOUNT TRANSFER|INTERNET BANKING|WALLET|DEBIT CARD|CREDIT CARD|PREPAID CARD|Bharat QR|USSD",
  "paymentStatus": "SUCCESS|FAILURE",
+ "remitter": {
+   "name": "XX",
+   "pan": "xxxx",
+   "email": "XXXX",
+   "aadhaar": "XXX"
+ },
+ "accountInfo": "ICIC0000152|1234567890"
}

#Payment Status API Enhancement

The payment status API must now include remitter details under the remitter object and account information within the accountInfo property in the response payload (See Payment Status API Reference).

{
  "status": "success/invalid-order-id",
  "message": "",
  "data": {
    "orderId": "COUWLje9V7wWs9N3w",
    "transactionId": "UNIQUE_PAYMENT_TRANSACTION_ID",
    "paymentDateTime": "YYYY-MM-DD HH:MM:SS in UTC",
    "amount": "100.00",
    "paymentMode": "CASH|UPI|IMPS|NEFT|AEPS|ACCOUNT TRANSFER|INTERNET BANKING|WALLET|DEBIT CARD|CREDIT CARD|PREPAID CARD|Bharat QR|USSD",
    "paymentStatus": "SUCCESS|FAILURE",
+   "remitter": {
+     "name": "XX",
+     "pan": "xxxx",
+     "email": "XXXX",
+     "aadhaar": "XXX"
+   },
+    "accountInfo": "ICIC0000152|1234567890"
  }
}

#NPCI Specifications

#Account Information Format by Payment Mode

#Code Format Examples

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

#Field Handling Rules

#Mandatory Behavior

• The accountInfo field must contain NPCI-compatible values corresponding to the selected payment mode
• For credit card bill payments, both the accountInfo and remitter objects must be provided.

#Optional Field Handling

• If remitter details or account information are not available, the fields should be omitted entirely
• System automatically handles fallback scenarios