Skip to main content
Due to Yes Bank moratorium, Customer Identifiers via YesBank were temporarily disabled between March 6, 2020 and March 18, 2020. During this time period, Razorpay onboarded a new partner bank and issued the same Customer Identifiers numbers with an updated IFSC as RATN0VAAPIS. Customers had to use the same account number, but switch the IFSC. Now that the moratorium has been lifted, if your virtual account was created before March 6, 2020, it would now appear as shown below: Your customers can make payments using the account number and either of the IFSCs:
  • RATN0VAAPIS
  • YESB0CMSNOC
New Customer IdentifiersPost March 6, 2020, IFSC for all newly issued Customer Identifiers will be RATN0VAAPIS.

Smart Collect Integration

Your Virtual Account integration will likely work in one of the following ways:
  • By mapping your customers/orders to Razorpay virtual account IDs.
  • By mapping your customers/orders to Razorpay customer IDs.
  • By mapping your customers/orders to Customer Identifiers.
  • By mapping your customers/orders to your own reference identifiers, which you passed in the notes array of your virtual account creation request.
In each of these cases, the Razorpay virtual_account.credited webhook is responsible for informing your server about which order to fulfill.
Existing Virtual Account Credited Webhook

Reconciliation ID | Example | Location in credit webhook

Razorpay virtual account ID | va_EPeK1ykH2PRtnD | payload.virtual_account.entity.id

Razorpay customer ID | cust_EPeLtyhSwk5tub | payload.virtual_account.entity.customer_id

Customer Identifier | 2223330012341234 | payload.virtual_account.entity.receivers.0.account_number

Virtual Account Notes ID | internal_order_id: 12345 | payload.virtual_account.entity.notes.internal_order_id The webhook payload for the migrated virtual accounts will look like this.
Virtual Account Credited Webhook for Migrated Account
As you can see, while a new bank account receiver block has been added to the receivers array of the virtual account, all considered reconciliation IDs are still present in the Razorpay webhook, in the same location. Notably, since the old receiver is still a part of the webhook, your server will still be correctly notified of the virtual account that received the payment, and of the order on your end that needs to be fulfilled. This means as long as your integration uses one of the 4 considered identifiers for payment reconciliation, it does not require any changes.