India (INR) Data Requirements

This page lists every data requirement for INR payments to India: the beneficiary and originator identities, the beneficiary financial instrument, and the transaction itself.

Fields shown are those required for this corridor

The identity and financial instrument tables on this page list only the fields IN_NEFT requires, taken from the PII v3 schema. Identities and financial instruments accept further optional fields. For the complete set, see Payment identities and Financial instruments, or use the Payload Schema Utility.

Beneficiary identity

Create the beneficiary identity before the financial instrument, then reference it when you create the payment. See Create and manage identities for the API workflow.

The required fields depend on whether the beneficiary is a business or an individual.

Business beneficiary

Applies to the B2B, B2B2B, C2B2B use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	Business Legal Name. 1–140 characters. Must match `^(?![ .,'&\/()-])(?!.*([ .,'&\/()-])\1)[\p{L}\p{N} .,'&\/()-]+(?<![ .,'&\/-])?$`.
`address.streetAddress`	Required	ARRAY of STRING	Allows the street address of the business to be held.
`address.country`	Required	STRING	Exactly 2 characters. Must match `^[A-Z]+$`.
`address.city`	Required	STRING	City. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L} .'-]+(?<![ .'-])$`.
`address.stateOrProvince`	Required	STRING	State, province, or county of the business address, as defined by postal services. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L}\p{N} .'-]+(?<![ .'-])$`.
`address.postalCode`	Required	STRING	Postal code for the business. 3–15 characters. Must match `^[\p{L}\p{N}][\p{L}\p{N} -]{1,15}[\p{L}\p{N}]$`.
`phone`	Required	STRING	Phone Number. 8–16 characters. Must match `^\+[1-9]\d+$`.
`registration[].number`	Required	STRING	The unique identifier of the organization. 3–35 characters. Must match `^(?![ .'-\/])(?!.*[ .'-\/]{2})([A-Za-z0-9 .'-\/]+)(?<![ .'-\/])\/?$`.
`registration[].type`	Required	STRING	One of `INCORPORATION_CERTIFICATE`, `TAX_ID`.
`incorporationCountry`	Required	STRING	Exactly 2 characters. Must match `^[A-Z]+$`.

Individual beneficiary

Applies to the B2B2C, B2C, C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	First name of the individual. 1–140 characters. Must match `^(?![ .'-])(?!.*([ .'-])\1)[\p{L} .'-]+(?<![ .'-])$`.
`lastName`	Required	STRING	Last name of the individual. 1–140 characters. Must match `^(?![ .'-])(?!.*([ .'-])\1)[\p{L} .'-]+(?<![ .'-])$`.
`address.streetAddress`	Required	ARRAY of STRING	Allows the street address of the individual to be held.
`address.country`	Required	STRING	Exactly 2 characters. Must match `^[A-Z]+$`.
`address.city`	Required	STRING	City. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L} .'-]+(?<![ .'-])$`.
`address.stateOrProvince`	Required	STRING	State, province, or county of the individual's address, as defined by postal services. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L}\p{N} .'-]+(?<![ .'-])$`.
`address.postalCode`	Required	STRING	Postal code for the individual's address. 3–15 characters. Must match `^[\p{L}\p{N}][\p{L}\p{N} -]{1,15}[\p{L}\p{N}]$`.
`phone`	Required	STRING	Phone Number. 8–16 characters. Must match `^\+[1-9]\d+$`.
`identityDocuments[].idNumber`	Required	STRING	Identification Number. 3–35 characters. Must match `^(?![ .'-\/])(?!.*[ .'-\/]{2})([A-Za-z0-9 .'-\/]+)(?<![ .'-\/])\/?$`.
`identityDocuments[].idType`	Required	STRING	One of `ALIEN_REGISTRATION`, `CUSTOMER_ID`, `DRIVERS_LICENSE`, `EMPLOYEE_ID`, `NATIONAL_ID_NUMBER`, `PASSPORT`, `SSN`, `TAX_ID`.
`citizenship`	Required	STRING	Alpha-2 country code for the nationality of the individual in ISO 3166-1 format. Exactly 2 characters. Must match `^[A-Z]+$`.

Beneficiary financial instrument

Set financialInstrumentType: IN_NEFT and currency: INR. Provide the following fields in the inNeft payment rail object. See Create and manage financial instruments for the API workflow.

Field	Required	Type	Constraints
`bankName`	Required	STRING	The name of the identity's bank. 2–140 characters. Must match `^(?![ .,'&\/()-])(?!.*([ .,'&\/()-])\1)[\p{L}\p{N} .,'&\/()-]+(?<![ .,'&\/-])?$`.
`ifscCode`	Required	STRING	The 11-character IFSC code of the identity's bank branch. Exactly 11 characters. Must match `^[A-Z]{4}0[A-Z0-9]{6}$`.
`accountNumber`	Required	STRING	The identity's bank account number. 4–45 characters. Must match `^[A-Za-z0-9]+$`.

Originator identity

Create the originator identity once and reuse it across payments.

The required fields depend on whether the originator is a business or an individual.

Business originator

Applies to the B2B, B2B2B, B2B2C, B2C use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	Business Legal Name. 1–140 characters. Must match `^(?![ .,'&\/()-])(?!.*([ .,'&\/()-])\1)[\p{L}\p{N} .,'&\/()-]+(?<![ .,'&\/-])?$`.
`address.streetAddress`	Required	ARRAY of STRING	Allows the street address of the business to be held.
`address.country`	Required	STRING	Exactly 2 characters. Must match `^[A-Z]+$`.
`address.city`	Required	STRING	City. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L} .'-]+(?<![ .'-])$`.
`address.stateOrProvince`	Required	STRING	State, province, or county of the business address, as defined by postal services. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L}\p{N} .'-]+(?<![ .'-])$`.
`address.postalCode`	Required	STRING	Postal code for the business. 3–15 characters. Must match `^[\p{L}\p{N}][\p{L}\p{N} -]{1,15}[\p{L}\p{N}]$`.
`phone`	Required	STRING	Phone Number. 8–16 characters. Must match `^\+[1-9]\d+$`.
`registration[].number`	Required	STRING	The unique identifier of the organization. 3–35 characters. Must match `^(?![ .'-\/])(?!.*[ .'-\/]{2})([A-Za-z0-9 .'-\/]+)(?<![ .'-\/])\/?$`.
`registration[].type`	Required	STRING	One of `INCORPORATION_CERTIFICATE`, `TAX_ID`.
`incorporationCountry`	Required	STRING	Exactly 2 characters. Must match `^[A-Z]+$`.
`incorporationDate`	Required	STRING	The date when the business was incorporated. Format `date`.

Individual originator

Applies to the C2B2B, C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	First name of the individual. 1–140 characters. Must match `^(?![ .'-])(?!.*([ .'-])\1)[\p{L} .'-]+(?<![ .'-])$`.
`lastName`	Required	STRING	Last name of the individual. 1–140 characters. Must match `^(?![ .'-])(?!.*([ .'-])\1)[\p{L} .'-]+(?<![ .'-])$`.
`address.streetAddress`	Required	ARRAY of STRING	Allows the street address of the individual to be held.
`address.country`	Required	STRING	Exactly 2 characters. Must match `^[A-Z]+$`.
`address.city`	Required	STRING	City. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L} .'-]+(?<![ .'-])$`.
`address.stateOrProvince`	Required	STRING	State, province, or county of the individual's address, as defined by postal services. 1–140 characters. Must match `^(?![ .'-])(?!.*[ .'-]{2})[\p{L}\p{N} .'-]+(?<![ .'-])$`.
`address.postalCode`	Required	STRING	Postal code for the individual's address. 3–15 characters. Must match `^[\p{L}\p{N}][\p{L}\p{N} -]{1,15}[\p{L}\p{N}]$`.
`phone`	Required	STRING	Phone Number. 8–16 characters. Must match `^\+[1-9]\d+$`.
`identityDocuments[].idNumber`	Required	STRING	Identification Number. 3–35 characters. Must match `^(?![ .'-\/])(?!.*[ .'-\/]{2})([A-Za-z0-9 .'-\/]+)(?<![ .'-\/])\/?$`.
`identityDocuments[].idType`	Required	STRING	Must be `PASSPORT`.
`identityDocuments[].expiryDate`	Required	STRING	Expiration date of the identification document. Format `date`.
`dateOfBirth`	Required	STRING	Date of Birth. Format `date`.
`citizenship`	Required	STRING	Alpha-2 country code for the nationality of the individual in ISO 3166-1 format. Exactly 2 characters. Must match `^[A-Z]+$`.

Transaction data requirements

The following transaction-level fields apply to all INR payments to India via NEFT (National Electronic Funds Transfer).

Field	Description	Required	Type	Constraints
`purposeCode`	Purpose of payment	Required	ENUM	See valid values below
`sourceOfCash`	Source of funds	Required	ENUM	See valid values below
`paymentMemo`	Payment memo	Optional	STRING	Max 50 chars. Required (containing the invoice number) for trade purpose codes; see Transaction limits below
`receiverRelationship`	Relationship to the debtor	Required	ENUM	See valid values below; valid values depend on whether the beneficiary is a business or an individual

Purpose of payment codes

Valid purposeCode values depend on the transaction category: Trade, Non-Trade, or C2C (customer-to-customer).

Trade transactions

Trade transactions include B2B, B2C, and C2B trade use cases.

Code	Description
`ACSC`	Accounting services
`AMSC`	Advertising, market research, and public opinion polling services
`CISC`	Construction and installation services
`ENGS`	Architectural, engineering, and other technical services
`GDDS`	Purchase or sale of goods
`GSPM`	Goods for processing and manufacturing services
`GSST`	Goods and services by short-term workers
`IVPT`	Invoice payment
`LESC`	Legal services
`MACH`	Payment for machinery and transport equipment
`MFGD`	Payment for manufactured goods
`MMFA`	Payment for miscellaneous manufactured articles
`MRSC`	Maintenance and repair services
`SCSD`	Software development services
`SCVE`	Purchase or sale of services
`SCWD`	Web design or development services
`TRAD`	Trade services

Invoice number required

An invoice number is mandatory for trade purpose codes. Include it in the paymentMemo field (numeric or alphanumeric, max 50 characters). The invoice amount must not be split into multiple payments.

Non-Trade transactions

Non-Trade transactions apply to B2B, B2C, and C2B use cases that are not trade-related.

Code	Description
`ALLW`	Allowance
`BONU`	Bonus payment
`COMM`	Commission
`DEPT`	Deposit
`DOFI`	Deposits with or from offshore financial institutions
`EDUC`	Education
`EDSC`	Education services
`FAMI`	Family maintenance
`FEES`	Payment of fees
`GDSV`	Purchase or sale of goods and services
`GIFT`	Allowance (gift)
`GSTR`	Goods and services by travellers
`HLTC`	Home health care
`INTE`	Interest
`INTC`	Intra-company payment
`INVS`	Investment and securities
`MDCS`	Medical services
`MP2P`	Mobile P2P payment
`OTHR`	Others
`PAYR`	Payroll
`PSFR`	Passenger fare
`REAB`	Real estate abroad
`RELG`	Rental lease, general
`SALA`	Salary payment
`STDY`	Study
`SUPP`	Supplier payment
`VIAC`	Visa application charges

C2C payments

C2C payments use the same purpose codes as Non-Trade transactions above.

Source of cash codes

Code	Description
`ALMY`	Alimony
`CASH`	Cash proceeds
`COMP`	Compensation
`EMIN`	Employee income
`GIFT`	Gift
`INHE`	Inheritance
`INLQ`	Insurance premium liquidation
`PACA`	Paid-up capital
`REDM`	Redemption
`REPY`	Retirement policy
`REST`	Real estate sale
`RETA`	Retained earnings
`SALE`	Sale of goods
`SEAQ`	Sale or acquisition of a corporation
`SELF`	Self-employment income
`SVGS`	Savings
`WINS`	Winnings

Beneficiary relationship codes

Valid receiverRelationship values depend on whether the beneficiary is a business or an individual.

Business beneficiaries

Code	Description
`BRAN`	Branch/Representative office
`CUST`	Customer
`FRAN`	Franchisee/Franchisor
`HOLD`	Holding company
`PART`	Business partner
`SUBS`	Subsidiary company
`SUPP`	Supplier

Individual beneficiaries

Code	Description
`CHIL`	Child
`CUST`	Customer
`EMPL`	Employee
`EXSP`	Ex-spouse
`FREN`	Friend
`OTHR`	Other
`PARE`	Parent
`PART`	Business partner
`RELA`	Relation
`SELF`	Self
`SIBL`	Sibling/brother/sister
`SPOU`	Covering spouse/partner
`VEND`	Vendor

Transaction limits

Category	Maximum amount	Notes
Trade	INR 1,500,000 per invoice	Must not be split into multiple payments
Non-Trade	INR 1,500,000 per payment
C2C	INR 500,000,000 per transaction

All categories are subject to a daily compliance limit of INR 4,000,000 per beneficiary. Transactions that would cause the sender or receiver to exceed this limit are held for review, and an RFI may be raised.

Trade transaction processing

The INR 1,500,000 trade limit reflects the Rupee Drawing Arrangement (RDA), which caps trade-related remittances at INR 1,500,000 per transaction. Payments exceeding this limit must move outside automated channels into formal bank-to-bank wire transfers with full documentation.
Trade transactions to HDFC Bank up to INR 1,500,000 are not processed automatically. The bank contacts the beneficiary directly for remittance details and supporting trade documents. If the required documents aren't submitted within 21 days, the transaction is rejected without a refund.
A Foreign Inward Remittance Certificate (FIRC) may be required if requested by the beneficiary bank.

Accepted identity document types

Payments over IN_NEFT accept only the following identity document types. Requests that use a document type not listed for the relevant payment role are rejected with a 400 error. Where a role or identity type is not listed below, all values in the field's enum are accepted.

Identity type	Payment role	Accepted document types
Individual (`idType`)	Originator	PASSPORT