Smart Collect APIs

Create, update, close and fetch Customer Identifiers and resend notifications using APIs.


Razorpay Smart Collect enables you to create Customer Identifiers to accept large payments from your customers in the form of bank transfers via NEFT, RTGS and IMPS.

Customer Identifiers are similar to bank accounts wherein customers can transfer payments. You can create, retrieve and close Customer Identifiers using the Smart Collect APIs.

APIDescription
API to create a Customer Identifier with bank account receiver.
API to create a Customer Identifier with VPA receiver.
API to create a Customer Identifier with VPA and bank account receivers.
API to Fetch a Customer Identifier by ID.
API to fetch all Customer Identifiers.
API to fetch payments made against a particular Customer Identifier.
API to retrieve details of a payment using the Payment ID and transfer method.
API to retrieve details of a payment using bank transfer method via UTR.
API to retrieve details of a UPI payment using the Payment id.
APIs to process refunds for a payment made towards a Customer Identifier.
API to add receiver to an existing Customer Identifier.
API to add receiver to an existing Customer Identifier.
API to update a Customer Identifier.
API to close a Customer Identifier.

  • Use if a Customer Identifier/UPI ID will be mapped to a unique customer.
  • You can use the fail_existing (set to 1) API parameter to create a customer. This helps you avoid customer_id being created multiple times for the same customer and will help in your reconciliation process.
  • We request you to create a single customer_id rather than making multiple IDs for the same customer. If their details change, you can use the API. Duplicate validation is done based on the combination of email ID and phone number.

  • UPI Customer Identifiers are supported only in Live mode.
  • The combination of merchant prefix and descriptor must be 20 characters. The length of the merchant prefix can vary between 4-10 characters and the length of the descriptor from 10-16 characters.
  • Payments made to the Customer Identifiers must be within the .
  • We recommend that you use to make a GET call for any downstream dependencies. Webhooks are just a recommended layer on top of this.
  • We recommend you once the payment is received.

Was this page helpful?