Skip to main content
POST
cURL

Create Remitter

Creating a remitter is idempotent: submitting the same id_type + id_number for your organization again returns the stored remitter unchanged, even if other fields (name, date of birth, phone, email, address) differ.
customer_id is not part of this request. A remitter is a standalone record, not a Customer: customer endpoints reject a remitter ID.

Field notes

  • source_of_funds: one of salary, savings, gifts, gift_from_family_and_friends, business_income, investment_proceeds, funds_from_dividend_payouts, pension_retirement, inheritance, sale_of_assets_real_estate, loan_from_bank, final_settlement, funds_from_schemes_and_raffles, gambling_proceeds, other_sources. Other codes (for example esops, credit_card, crypto_currencies) are rejected.
  • The response includes status, which is VERIFIED on create: the remitter’s identity is checked when the payout is fulfilled.
  • id_type: use PASSPORT or DRIVING_LICENCE. BENEFICIARY_ID, PAN_CARD, AADHAAR_CARD, AIRLINE_STAFF_CARD, BUSINESS_REGISTRATION_NO_BR, CENTRAL_BANK_LICENCE and ACRA are accepted but stored as a generic government ID. Other values are rejected.
  • id_number: 6–20 characters, letters, digits and -.
  • nationality and residence_country must be valid ISO 3166-1 alpha-3 codes. residence_country cannot be IND: a remitter must live outside India.
  • dob must be in the past. phone must be E.164 (+ and country code) with a known dial code.
  • The remitter is recorded as the sender of each payout, which is why full identity is required.

Error Codes and Messages

Authorizations

X-API-KEY
string
header
required

API Key for authentication

X-TIMESTAMP
string
header
required

Current timestamp in seconds since epoch

X-SIGNATURE
string
header
required

HMAC SHA256 signature of the request encoded in Base64

Body

application/json
first_name
string
required

Letters, spaces, apostrophes, and hyphens only. 1-100 characters.

Example:

"Siva"

last_name
string
required

Letters, spaces, apostrophes, and hyphens only. 1-100 characters.

Example:

"Raj"

nationality
string
required

ISO 3166-1 alpha-3 country code (validated, uppercased).

Example:

"IND"

city
string
required

Letters, spaces, apostrophes, and hyphens only. 2-50 characters.

Example:

"Sydney"

source_of_funds
enum<string>
required

Source of funds. One of the listed codes; others are rejected.

Available options:
business_income,
final_settlement,
funds_from_dividend_payouts,
funds_from_schemes_and_raffles,
gambling_proceeds,
gift_from_family_and_friends,
gifts,
inheritance,
investment_proceeds,
loan_from_bank,
other_sources,
pension_retirement,
salary,
sale_of_assets_real_estate,
savings
Example:

"gifts"

id_type
enum<string>
required

Identity document type. Use PASSPORT or DRIVING_LICENCE; the other values are accepted but stored as a generic government ID.

Available options:
PASSPORT,
DRIVING_LICENCE,
BENEFICIARY_ID,
PAN_CARD,
AADHAAR_CARD,
AIRLINE_STAFF_CARD,
BUSINESS_REGISTRATION_NO_BR,
CENTRAL_BANK_LICENCE,
ACRA
Example:

"PASSPORT"

id_number
string
required

6–20 characters: letters, digits and hyphens.

Example:

"P1234567"

dob
string<date>
required

Date of birth (YYYY-MM-DD). Must be in the past.

Example:

"1990-01-15"

phone
string
required

Phone in E.164 format with the leading +. The dial code must be a known country.

Example:

"+61412345678"

address_line
string
required

Residential address, max 500 characters

Example:

"1 George Street"

residence_country
string
required

Country of residence, ISO 3166-1 alpha-3. Must not be IND: a remitter must live outside India.

Example:

"ARE"

client_reference_id
string

Optional client-supplied reference for tracking. Max 255 characters.

Example:

"remitter-ref-001"

email
string<email>

Email address. Optional.

Example:

"siva.raj@example.com"

Response

Remitter created (or existing matching remitter returned)

status
boolean
Example:

true

message
string
Example:

"Remitter created"

data
object