# Shows out payment details

Endpoint: GET /out_payment/{id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    Resource Identification

## Response 200 fields (application/json):

  - `id` (string)
    A unique identifier for the resource. While typically formatted as a UUID (Universally Unique Identifier), it can also be in other formats as defined by the user. This field ensures the resource can be distinctly recognized and referenced.

  - `status` (string)
    Status of the out payment.
    Enum: "success", "pending", "deleted", "delayed"

  - `type` (string)
    Type of out payment.
    Enum: "normal", "instant"

  - `method` (string)
    Method used for the out payment.
    Enum: "transfer", "mb"

  - `customer` (object)
    Customer associated with the out payment.

  - `customer.id` (string)
    Unique identifier for the customer.

  - `account` (object)
    Easypay account from which the funds are transferred.

  - `account.id` (string)
    Unique identifier for the Easypay account.

  - `out_account` (object)
    Destination SEPA bank account for the out payment.

  - `out_account.id` (string)
    Unique identifier for the destination account.

  - `key` (string)
    Merchant reference key for the out payment.

  - `value` (number)
    Amount to be transferred.

  - `schedule_at` (string)
    Scheduled date and time for the out payment (YYYY-MM-DD HH:MM:SS).

  - `transactions` (object)
    Transaction related to the out payment.

  - `transactions.id` (string)
    A unique identifier for the entry, represented as a UUID. This ID is used to uniquely track and reference individual entries within the ledger system.
    Example: "4fb3ac57-c7fe-4157-aeb7-4362ae24deec"

  - `transactions.key` (string)
    A customizable text field for users to input their own identifier for the resource. This can be any string that helps the user uniquely identify or reference the resource in their own system.
    Example: "01J1PKR2RPHJNJQGFWGDYXY0KM"

  - `transactions.created_at` (string)
    The timestamp indicating when the resource was created. It is formatted as ISO 8601.
    Example: "2025-05-30T17:21:47Z"

  - `transactions.date` (string)
    The timestamp indicating when the resource was updated. It is formatted as ISO 8601.
    Example: "2025-05-30T17:21:46Z"

  - `transactions.values` (object)

  - `transactions.values.requested` (number)
    The amount requested, rounded by two decimapl plates.
    Example: 12.55

  - `transactions.values.paid` (number)
    The amount paid, rounded by two decimal plates.
    Example: 12.55

  - `transactions.values.fixed_fee` (number)
    The fixed fee amount applied to this transaction.
    Example: 0.07

  - `transactions.values.variable_fee` (number)
    The variable fee amount applied to this transaction.
    Example: 0.09

  - `transactions.values.tax` (number)
    The vat amount applied to this transaction.
    Example: 0.04

  - `transactions.values.transfer` (number)
    The net value to be transferred.
    Example: 12.35

  - `transactions.transfer_date` (string)
    The estimation when the funds will be transfered. It is formatted as ISO 8601.
    Example: "2025-06-02T00:00:00Z"

  - `transactions.transfer_batch` (string)
    A unique identifier for the transfer batch, typically represented as a string. This value is used to track and reference a specific batch of transfers within the system.
    Example: "584"

  - `transactions.method` (string)
    Method used for the transaction.
    Example: "transfer"

  - `transactions.document_number` (string)
    Unique document number used for Easypay Invoice.
    Example: "MARCEL0208220628294020250530172147"

  - `transactions.descriptive` (string)
    This is used to provide additional context or notes that describe the nature of the transaction in plain language.
    Example: "blue t-shirts"

  - `created_at` (string)
    Date and time when the out payment was created.
    Example: "2022-09-15 20:28:58"

  - `timestamp` (string)
    Timestamp of the last update or event for this out payment.
    Example: "1749054192"

## Response 401 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 403 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 404 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 429 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 500 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.