> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 4. Follow Onboarding

> Track a payment method instrument to activation using the account.payment_methods.updated webhook or by polling.

Available in
🇮🇳 India

Banks, providers and Razorpay move an instrument through onboarding over days. The usual path is `in_progress` while something is due, then `under_review`, then `activated`. A reviewer or the bank can send it to `needs_clarification` on the way. `rejected` is final for this API.

Fetching its payment method is always the source of truth. Use a webhook to know when to fetch.

## 4.1 Subscribe to the Webhook

Subscribe on the Partner Dashboard, once per mode, with an https URL, a secret and the events to receive. Razorpay delivers these events the same way as the [Onboarding APIs webhooks](https://razorpay.com/docs/webhooks/partners/onboarding-apis.md), to the same URL.

| Event | When it fires |
| - | - |
| `account.payment_methods.updated` | An instrument's status changed, for example to `activated`, `needs_clarification` or `rejected`. It fires on every status change, including one your own call caused. |
| `account.payment_methods.requirements.updated` | Requirements changed without a call from your platform, for example after a check that runs later. It is a new event, delivered the same way as the Onboarding APIs events. |

Switching an activated instrument on or off changes only `enabled`, not its status, so no event fires. A group such as `debit_card` has no event of its own. The event is sent for the member whose status changed.

```json account.payment_methods.updated theme={null}
{
  "id": "evt_Qm4Xr8Lt2Vb6Ns",
  "entity": "event",
  "event": "account.payment_methods.updated",
  "mode": "live",
  "account_id": "acc_TcdGEzmfKQzEl1",
  "product": "payment_gateway",
  "payload": {
    "account": {
      "id": "acc_TcdGEzmfKQzEl1",
      "updated_at": 1796116800
    },
    "payment_method": {
      "method": "emi",
      "name": "EMI",
      "emi": {
        "credit_card": {
          "banks": [
            {
              "bank": "sbin",
              "name": "SBI credit-card EMI",
              "logo_url": "https://cdn.razorpay.com/app/sbin.svg",
              "status": "activated",
              "status_reason": null,
              "enabled": true,
              "requirements": [],
              "estimated_activation_days": 17,
              "updated_at": 1796116800
            }
          ]
        }
      }
    }
  },
  "created_at": 1796116801
}
```

The payload carries the account's id and `updated_at`, and the payment method with only the instrument that changed.

## 4.2 Handle the Webhook

1. **Verify the signature.** `X-Razorpay-Signature` is the HMAC-SHA256 of the raw body, keyed with your webhook secret, as hex. Read the secret from your environment or secrets manager. Reject an event that does not match.
2. **Acknowledge fast.** Answer with any `2xx` within 5 seconds, then do the work. Razorpay retries anything else with exponential backoff for up to 24 hours. After that, it does not send the event again, so fetch its payment method to catch up.
3. **Expect repeats and any order.** Process each `X-Razorpay-Event-Id` once. Order events by `created_at`, then by `payload.account.updated_at`. Fetch its payment method when the order matters.

## 4.3 Poll Instead

Without webhooks, [fetch](https://razorpay.com/docs/partners/aggregators/onboarding-api/payment-methods/fetch-and-enable.md) the instrument's payment method while it is `in_progress`, `under_review` or `needs_clarification`. A few times a day is enough. Stop once it is `activated` or `rejected`.

Razorpay may also email or WhatsApp the sub-merchant about the outcome.

## Next Step

[Cash on Delivery](https://razorpay.com/docs/partners/aggregators/onboarding-api/payment-methods/cash-on-delivery.md)
