# Retrieve associated payment instruments

Retrieves the payment gateway and a list of payment instruments that are associated with a payout request with a specified ID.

Endpoint: GET /payout-requests-v2/{id}/payment-instruments
Version: latest
Security: SecretApiKey, JWT

## Path parameters:

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

## Response 200 fields (application/json):

  - `paymentInstrumentId` (string)
    ID of the payment instrument to offer for the payout.
    Example: "inst_0YVB8KPKNXCBR9EDX7JHSED75N"

  - `gatewayName` (string,null)
    Name of the payment gateway and payment instrument to use for the payout.
This field is empty if the requested payment instrument has not been used yet.

  - `gatewayAccountId` (string)
    ID of the gateway account to use for processing this allocation.
    Example: "gateway_0YVB8KPKNXCBR9EDX7JHSED75N"

  - `gatewayPayoutInstruction` (string,null)
    Payout configuration for the gateway account.
    Enum: "all", "covered-payout", "approved-payment", "none"

  - `exposureAmount` (number)
    Total amount of sales minus credit for the specified gateway and instrument.

  - `previousAllocatedAmount` (number)
    Total amount of allocated credit for the payout request for the specified gateway and instrument.

  - `lastPaymentTime` (string,null)
    Date and time when the last payment is created for the gateway and the payment instrument.
Payments are the result of sale or capture transactions.

  - `lastPayoutTime` (string,null)
    Date and time when the last payout is created for the gateway and the payment instrument.

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