> ## 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.

# 2. Activated vs Enabled

> Understand the status and enabled fields of an instrument and the four paths an instrument takes to go live.

Available in
🇮🇳 India

An instrument answers two separate questions.

* `status` says whether Razorpay and the bank or provider have finished setting the instrument up for the account. Razorpay does this once, and it can take days.
* `enabled` says whether customers can pay with it at checkout right now. It is an instant on and off switch that you control.

| | `enabled: true` | `enabled: false` |
| - | - | - |
| `status: activated` | Customers can pay with it. | Switched off. Switching it on is instant. |
| Any other status | Not possible. | Switching it on starts the onboarding. |

An instrument that is not activated is never enabled.

## 2.1 Instrument Statuses

| Status | Meaning | `enabled` can be true | Next |
| - | - | - | - |
| `eligible` | Can be enabled. `requirements` lists anything Razorpay will need. | No | Enable it. It moves to `activated`, `in_progress` or `under_review`. |
| `ineligible` | Cannot be enabled now. `status_reason` says why. | No | It becomes `eligible` once the reason clears, for example when KYC is verified. |
| `in_progress` | Enabled, and something is still due. `requirements` lists it. | No | It moves to `under_review` once nothing is due. |
| `under_review` | Enabled and nothing is due. Razorpay and the bank or provider are reviewing it. | No | It moves to `activated`, `rejected` or `needs_clarification`. |
| `needs_clarification` | A reviewer or the bank asked for more. `requirements` lists it. | No | It moves to `under_review` once answered. |
| `activated` | Onboarded. `enabled` shows whether it is switched on. | Yes | It stays activated. Enabling and disabling change `enabled` only. |
| `rejected` | Refused for this account. `status_reason` says why. | No | Final for this API. The sub-merchant can ask Razorpay support to review it. |
| `suspended` | Switched off by Razorpay after activation. `status_reason` says why. | No | Razorpay decides. You cannot enable it through this API. |

Disabling an instrument that is `in_progress`, `under_review` or `needs_clarification` returns it to `eligible`.

## 2.2 Reason Codes

`status_reason` appears for an `ineligible`, `rejected` or `suspended` instrument. It is `null` otherwise. Build logic on `status_reason.code`, not on the text.

| Code | Status | English text |
| - | - | - |
| `kyc_pending` | `ineligible` | This is only available after your KYC is verified. |
| `category_not_allowed` | `ineligible` | This is not permitted for your business category. |
| `blocked_for_account` | `ineligible` | This method is not permitted for your category or business type. |
| `card_payments_required` | `ineligible` | Accept a card payment first to unlock this option. |
| `eligibility_no_history` | `ineligible` | Eligibility will be calculated after your first transactions. |
| `eligibility_calculating` | `ineligible` | Calculating eligibility. Please refresh shortly. |
| `eligibility_below_threshold` | `ineligible` | This payment method will unlock once your business achieves the credit card transaction count or average transaction size set for the account. |
| `not_allowed_for_business` | `rejected` | This instrument is not allowed for your business. |
| `rejected_on_review` | `rejected` | The reason Razorpay or the bank gave, as written. |

## 2.3 How Each Instrument Goes Live

What happens when you enable an instrument depends on which of four paths it is on.

| Path | When you enable it | Time to activation |
| - | - | - |
| Live by default | Nothing to onboard. The instrument is already `activated`, so enabling or disabling it only flips `enabled`. | Already live |
| Activated immediately on demand | The sub-merchant has to opt in explicitly. The instrument is then `activated` and enabled in the same call. | Immediate |
| Bank or provider onboarding | Razorpay raises the onboarding with the bank or provider. The status is `under_review` when nothing is missing, or `in_progress` with requirements when something is. If the bank asks for more later, it becomes `needs_clarification`. | Days. `estimated_activation_days` gives the estimate. |
| Eligibility-gated | Unavailable until the account meets the credit-card transaction rule. Enabling it earlier is refused with `instrument_ineligible`. | As for bank or provider onboarding, once eligible |

The path depends on the instrument:

| Payment method | Live by default | Activated immediately on demand | Bank or provider onboarding | Eligibility-gated |
| - | - | - | - | - |
| Cards | Visa, Mastercard, RuPay, recurring cards, Apple Pay, Google Pay and CRED | None | American Express, and international cards, which Razorpay reviews | Diners Club |
| Netbanking | A set of banks that depends on the account | None | The remaining banks | None |
| UPI | All five UPI instruments | None | None | None |
| Wallets | None | PhonePe | Every other wallet | None |
| EMI | Credit-card EMI `credit_card`, after the account's first card payment | None | HDFC Bank, SBI and American Express credit-card EMI, HDFC Bank and IndusInd Bank debit-card EMI, and the five cardless EMI providers | HDFC Bank credit-card EMI |
| COD | None | Full and partial COD | None | None |

> [!NOTE]
>
> **Handy Tips**
>
> * Fetch the payment method for the instrument's actual path and `estimated_activation_days`. The estimate adjusts to the account's business category. It is `null` when there is no estimate, or when the instrument needs no onboarding.
> * Onboarding asks for items such as business details, website policy links or documents, depending on the bank or provider and the business sub-category. Each item appears in `requirements`.

## Next Step

[Supply Requirements](https://razorpay.com/docs/partners/aggregators/onboarding-api/payment-methods/supply-requirements.md)
