Skip to main content
Available in🇮🇳 India
Once you capture a payment, Razorpay returns a razorpay_payment_id that can be used to fetch the token_id. This is a manual process and can be done using either APIs or Webhooks. This token_id is used to create and charge subsequent payments.
Handy TipsYou can also search for the Token on your Dashboard.

Token States

As the authorisation transaction moves through its states, the token generated for the mandate also changes state. Emandate registrations are confirmed in real time for all authentication types (Aadhaar, netbanking and debit card). Only tokens in the confirmed state can be used to create subsequent payments.

2.1. Fetch Token by Payment ID

The following endpoint retrieves the token_id using a payment_id. GET /payments/:id
Handy TipsYou can also retrieve the token_id via the payment.authorized webhook.

Path Parameter

id mandatory : string The unique identifier of the payment to be retrieved. For example, pay_1Aa00000000002.

2.2. Fetch Tokens by Customer ID

A customer can have multiple tokens and these tokens can be used to create subsequent payments for multiple products or services. The following endpoint retrieves tokens linked to a customer.
Watch Out!This endpoint will not fetch the details of expired and unused tokens.
GET /customers/:id/tokens

Path Parameter

id mandatory : string The unique identifier of the customer for whom tokens are to be retrieved. For example, cust_1Aa00000000002.

2.3. Delete Tokens

The following endpoint deletes a token. DELETE /customers/:customer_id/tokens/:token_id

Path Parameter

customer_id mandatory : string The unique identifier of the customer with whom the token is linked. For example, cust_1Aa00000000002. token_id mandatory : string The unique identifier of the token that is to be deleted. For example, token_1Aa00000000001.
Last modified on October 30, 2026