Smart Collect
Fetch All Customer Identifiers
Fetch all Customer Identifiers using the Razorpay Smart Collect APIs.
GET
Available in🇮🇳 India🇸🇬 Singapore🇺🇸 United States
Use this endpoint to retrieve details of all Customer Identifiers.
Query Parameters
integer
Timestamp, in seconds, from when Customer Identifiers are to be fetched.
integer
Timestamp, in seconds, till when Customer Identifiers are to be fetched.
integer
Number of Customer Identifiers to be fetched. The default value is 10 and the maximum value is 100. This can be used for pagination, in combination with
skip.integer
Number of records to be skipped while fetching the Customer Identifiers. This can be used for pagination, in combination with
count.Response Parameters
string
The unique identifier of the Customer Identifier.
string
The
merchant billing label as it appears on the Dashboard.string
Indicates the type of entity. Here, it is
virtual account.string
Indicates whether the Customer Identifier is in
active or closed state.string
A brief description about the Customer Identifier.
integer
The amount expected by the merchant.
integer
The amount paid by the customer into the Customer Identifier.
json object
Any custom notes you might want to add to the Customer Identifier can be entered here. Know more about notes.
string
Unique identifier of the customer the Customer Identifier is linked with. Know more about Customer API.
json object
Configuration of desired receivers for the Customer Identifier.
string
The unique identifier of the virtual bank account. Sample IDs for:
- Virtual bank account:
ba_Di5gbQsGn0QSz3 - Virtual UPI ID:
vpa_CkTmLXqVYPkbxx
string
Name of the entity. Possible values:
bank_accountvpa
string
The IFSC for the virtual bank account created. For example,
RAZR0000001. This parameter appears in the response only when bank_account is passed as the receiver type.string
The bank associated with the virtual bank account. For example,
RBL Bank. This parameter appears in the response only when bank_account is passed as the receiver type.string
The unique account number provided by the bank. For example,
1112220061746877. This parameter appears in the response only when bank_account is passed as the receiver type.string
The
merchant billing label as it appears on the Dashboard. This parameter appears in the response only when bank_account is passed as the receiver type.json object
Any custom notes you might want to add to the virtual bank account can be entered here. Know more about notes. This parameter appears in the response only when
bank_account is passed as the receiver type.: json object Any custom notes you might want to add to the virtual bank account or virtual UPI ID can be entered here. Know more about notes. This parameter appears in the response only when bank_account is passed as the receiver type.string
The UPI ID consists of the username and the bank handle. The
username consists of the namespace (assigned by the bank to Razorpay), the merchant prefix (which can be customised by you) and the descriptor (which you provide to identify the customer). The unique identifier which forms the first half of the virtual UPI ID. For example, rpy.payto00000gaurikumari. This parameter appears in the response only when vpa is passed as the receiver type. The descriptor can be 10 characters only.string
The bank name that forms the second half of the virtual UPI ID. For example,
icici. This parameter appears in the response only when vpa is passed as the receiver type.string
The UPI ID that combines the
username and the handle with the @ symbol. For example, rpy.payto00000gaurikumari@icici. This parameter appears in the response only when vpa is passed as the receiver type.integer
UNIX timestamp at which the Customer Identifier is scheduled to be automatically closed. The time must be at least 15 minutes after current time. The date range can be set till
2147483647 in UNIX timestamp format (equivalent to Tuesday, January 19, 2038 8:44:07 AM GMT+05:30).integer
UNIX timestamp at which the Customer Identifier is automatically closed.
integer
UNIX timestamp at which the Customer Identifier was created.
Errors
The API `<key/secret>
` provided is invalid.
The API `<key/secret> ` provided is invalid.
Code:
4xxOccurs when there is a mismatch between the API credentials passed in the API call and the API credentials generated on the dashboard.Solution: Make sure that the API keys are active and entered correctly. Also, make sure there are no whitespaces before or after the keys.