---
title: "Get multi-leg payment status"
method: GET
path: "/corporate/v3/payments/multileg/{multilegId}"
tags: ["Payments"]
---

# Get multi-leg payment status

`GET /corporate/v3/payments/multileg/{multilegId}`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/corporate/v3/payments/multileg/{multilegId}`
- Auth: HTTP bearer

Enables users to query the processing status of a multi-leg payment.

## Path parameters

- `multilegId` string, required

## Response `200`

Successful response

- MultiLegV3Status
  - `multileg_id` string, required: A unique multileg payment identifier provided by the client. If an existing `multileg_id` already exists in the system, the API returns a `409` error. This field is: - Unique within the Organization. - Immutable — It can't be updated. - Not recyclable — You can't reuse a `multileg_id`.
  - `status` 'CREATING' | 'EXECUTING' | 'DEBITS_EXECUTED' | 'CREDITS_FAILED' | 'FINISHED' | 'ROLLING_BACK' | 'ROLLED_BACK' | 'ROLLBACK_FAILED' | 'TIMED_OUT', required: Status of the multi-leg processing.<br> * `CREATING`: The multileg payment request has been received and queued for execution. * `EXECUTING`: Asynchronous processing of the multileg payment has started. * `DEBITS_EXECUTED`: All debit legs have been successfully executed; credit leg processing is still in progress. * `CREDITS_FAILED`: Used in v2 when one or more credit legs failed. This status is no longer used in v3, but remains in the API for queries on payments created via the V2 endpoint. * `FINISHED`: All payment legs were processed successfully. * `ROLLING_BACK`: One or more payment legs failed, and the rollback process has begun. * `ROLLED_BACK`: One or more payment legs failed, and all successful legs were rolled back. * `ROLLBACK_FAILED`: One or more payment legs failed, rollback was attempted, but the rollback of some legs was unsuccessful. * `TIMED_OUT`: Processing did not complete because the multileg execution timed out.
  - `debits` MultiLegItemV3Status[]
    - `tracking_id` string, required: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
    - `external_account_id` string, required: External ID of the account to which the transaction is posted.
    - `status` 'PENDING' | 'EXECUTED' | 'FAILED' | 'ROLLED_BACK' | 'ROLLBACK_FAILED', required: Status of the leg processing.<br> * `PENDING`: The payment leg is awaiting execution. * `EXECUTED`: The payment leg was executed successfully. * `FAILED`: The payment leg execution failed. * `ROLLED_BACK`: The payment leg was executed successfully but was rolled back due to a failure in another leg. * `ROLLBACK_FAILED`: The payment leg was executed successfully; another leg failed, triggering a rollback, but the rollback for this leg was unsuccessful.
    - `event_datetime` string, date-time: Event date and time displayed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.<br> `minLength: 1` `maxLength: 30`
    - `error` MultilegLegError
      - `status` integer: HTTP Status code of the error
      - `code` string: Error code `minLength: 1` `maxLength: 12`
      - `message` string: Error message `minLength: 1` `maxLength: 1000`
    - `rollback` object
      - `tracking_id` string, required: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
      - `event_datetime` string, date-time: Event date and time displayed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.<br> `minLength: 1` `maxLength: 30`
      - `error` MultilegLegError
        - `status` integer: HTTP Status code of the error
        - `code` string: Error code `minLength: 1` `maxLength: 12`
        - `message` string: Error message `minLength: 1` `maxLength: 1000`
  - `credits` MultiLegItemV3Status[]
    - `tracking_id` string, required: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
    - `external_account_id` string, required: External ID of the account to which the transaction is posted.
    - `status` 'PENDING' | 'EXECUTED' | 'FAILED' | 'ROLLED_BACK' | 'ROLLBACK_FAILED', required: Status of the leg processing.<br> * `PENDING`: The payment leg is awaiting execution. * `EXECUTED`: The payment leg was executed successfully. * `FAILED`: The payment leg execution failed. * `ROLLED_BACK`: The payment leg was executed successfully but was rolled back due to a failure in another leg. * `ROLLBACK_FAILED`: The payment leg was executed successfully; another leg failed, triggering a rollback, but the rollback for this leg was unsuccessful.
    - `event_datetime` string, date-time: Event date and time displayed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.<br> `minLength: 1` `maxLength: 30`
    - `error` MultilegLegError
      - `status` integer: HTTP Status code of the error
      - `code` string: Error code `minLength: 1` `maxLength: 12`
      - `message` string: Error message `minLength: 1` `maxLength: 1000`
    - `rollback` object
      - `tracking_id` string, required: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
      - `event_datetime` string, date-time: Event date and time displayed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.<br> `minLength: 1` `maxLength: 30`
      - `error` MultilegLegError
        - `status` integer: HTTP Status code of the error
        - `code` string: Error code `minLength: 1` `maxLength: 12`
        - `message` string: Error message `minLength: 1` `maxLength: 1000`

## Other responses

- `404`: Not Found

---

[API](https://skmtc.dev/pismo/apis/banking-transaction-banking.md) - [All operations](https://skmtc.dev/pismo/apis/banking-transaction-banking/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/banking-transaction-banking/revisions/1334306c9303?raw)