Collections — KYC / KYB

Field requirements when creating a customer for the UPI collections flow. Collections is designed for high-volume, low-friction inbound UPI payments — KYC is light by default and can be opted into per-customer by supplying PAN at creation time.

Use the create-customer flow with type: 'individual', party: 'sender', and purpose: 'collections'. The minimum viable customer is name + mobile_number (with isd_code); email is optional, and identity-document fields are optional and unlock asynchronous PAN verification when supplied.

Only the individual + sender combination is accepted. Individual receivers, business senders, and business receivers all reject up-front with INVALID_CUSTOMER_COMBINATION.

Sender-only flow

Collections is individual-and-sender-only. UPI inbound payments always treat the customer as the payer; the merchant project itself is the implicit receiver.

Individual — sender

Apply when type = 'individual' and party = 'sender'. The sender is the natural person paying the merchant via UPI. Collections runs light KYC by default — only name and a contact channel are required, with PAN-based verification opt-in.

Field	Type	Required	Description
first_name	string	Yes	Customer's legal first name.
middle_name	string	No	Customer's middle name if present.
last_name	string	Yes	Customer's legal last name.
email	string	No	Customer's email address.
mobile_number	string	Yes	Customer's mobile number.
isd_code	string	Yes	International Subscriber Dialing code (e.g. +91). Required alongside mobile_number.
residence_country	IN \| US \| SG	No	Two-letter ISO country code. UPI customers are typically 'IN'.
identity_document_type	pan	No	Identity document type. Send 'pan' (with identity_document_number) to opt the customer into PAN-based KYC verification.
identity_document_number	string	No	PAN number. Required when identity_document_type is provided.

Individual — receiver

Not supported

Individual receivers are not permitted on the collections flow. The createCustomer API rejects type = 'individual' + purpose = 'collections' + party = 'receiver' with INVALID_CUSTOMER_COMBINATION. UPI collection customers are always modelled as senders of funds.

Business — sender

Not supported

Businesses are not permitted on the collections flow. The createCustomer API rejects type = 'business' + purpose = 'collections' with INVALID_CUSTOMER_COMBINATION. Use crypto-offramp or trade-finance flows for business customers.

Business — receiver

Not supported