# Retrieve a cashier

Retrieves a cashier with a specified ID.

Endpoint: GET /storefront/cashiers/{id}
Version: latest
Security: CustomerJWT

## Path parameters:

  - `id` (string, required)
    ID of the resource.

## Response 200 fields (application/json):

  - `id` (string, required)
    Unique identifier of the cashier.
    Example: "cashier_0YV7DE4Z26DQSA1AC92FBJ7SEG"

  - `websiteId` (string, required)
    ID of the website.
A website is where an organization obtains a customer.
For more information, see [Obtain an organization ID and website ID](https://www.rebilly.com/docs/settings/organizations-and-websites/#obtain-your-organization-id-and-website-id).
    Example: "web_0YV7DE4Z26DQSA1AC92FBJ7SEG"

  - `currency` (string, required)
    Currency code in ISO 4217 format.
    Example: "USD"

  - `redirectUrl` (string,null, required)
    URL to redirect the customer to when a deposit or withdrawal is completed.
The default value is the website URL.

  - `balance` (number, required)
    Customer's current balance.
    Example: 1500

  - `bonusBalance` (number, required)
    Bonus balance available to the customer.
    Example: 1500

  - `pendingPayoutTotal` (number, required)
    Sum of all payout requests that are currently in a pending state.
This value is also the maximum possible "reverse withdrawal" amount.
    Example: 100

  - `depositMethods` (array, required)

  - `depositMethods.amounts` (array, required)
    Example: [10,20,50]

  - `payoutMethods` (array, required)

  - `payoutMethods.method` (string, required)
    Example: "payment-card"

  - `payoutMethods.brands` (array)
    Example: ["Visa","MasterCard","American Express","Discover"]

  - `depositAmounts` (array, required)
    List of predefined deposit amounts that the customer can choose from.
    Example: [10,20]

  - `depositCustomAmount` (object, required)
    Custom amount restrictions.
If this value is not specified, custom amounts are prohibited.

  - `depositCustomAmount.minimum` (number, required)
    Example: 10

  - `depositCustomAmount.maximum` (number, required)
    Example: 1000

  - `depositCustomAmount.multipleOf` (number, required)
    Example: 0.5

  - `lastDepositRequestId` (string)
    ID of the last deposit request that is made for this cashier.
    Example: "dep_req_01K2HMPNTBDS92TA6W4EX3VJPM"

  - `createdTime` (string)
    Date and time which is set automatically when the resource is created.

  - `updatedTime` (string)
    Date and time which updates automatically when the resource is updated.

  - `_links` (array)
    Related links.

  - `_links.href` (string)
    Link URL.

  - `_links.rel` (string)
    Type of link.
    Enum: "self"

## Response 401 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.

## Response 403 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.

## Response 404 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.