## Retrieve current plan

Retrieves the current billing plan for the merchant account.
This endpoint returns the plan details including the plan ID, name, tier, and any associated metadata.
It is used to check the current subscription status and plan features available to the merchant.

The response includes information about the plan's tier, which indicates the level of service provided.

## Endpoint signature

```http
POST https://api.reservepay.com/merchants/retrieve-current-plan HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>

{}
```

Returns: object

## Response attributes

### `id` (string)

_Nullable_. The unique identifier of the plan.

### `tier_code` (string)

**Always present**. The code representing the tier this plan belongs to.

Possible values:

- `pay_as_you_go`
- `startup`
- `professional`
- `enterprise`

### `tier_name` (string)

**Always present**. The name of the tier (e.g., 'Basic', 'Pro').

### `features` (array)

**Always present**. List of features included in this plan.

### `revision_time` (number)

**Always present**. The date and time when the plan was last revised.

### `selectable` (boolean)

**Always present**. Indicates whether the plan can be selected by the merchant via self-service.

## Errors specific to this endpoint

### `NO_PLAN_SELECTED`

The merchant is not currently subscribed to any plan. A plan must be subscribed to via the `select-plan` endpoint first.

## Errors common to all endpoints

### `UNHANDLED_ERROR`

This error occurs when the server encounters an unexpected internal error that
it cannot handle gracefully. This typically happens due to bugs, infrastructure
issues, or edge cases that weren't anticipated during development.

### `INVALID_ARGUMENTS`

This error occurs when the request contains invalid or missing parameters.
Common cases include missing required fields, or values that don't match the
expected format or type.

### `BAD_VERSION`

This error occurs when making requests to an API version that does not exist.
This commonly happens when using an outdated SDK or when the API version
specified in the request URL is incorrect.