---
title: "Get multi-leg payment status (deprecated)"
method: GET
path: "/corporate/v2/payments/multileg/{trackingId}"
tags: ["Payments"]
deprecated: true
---

# Get multi-leg payment status (deprecated)

`GET /corporate/v2/payments/multileg/{trackingId}`

## Request

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

> **Deprecated.**

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

## Path parameters

- `trackingId` string, required

## Response `200`

Get multi-leg payment status

- MultiLegStatus
  - `tracking_id` string: 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`
  - `status` 'CREATING' | 'EXECUTING' | 'DEBITS_EXECUTED' | 'CREDITS_FAILED' | 'FINISHED' | 'ROLLING_BACK' | 'ROLLED_BACK' | 'ROLLBACK_FAILED' | 'TIMED_OUT': Status of the multi-leg processing.
  - `debits` MultiLegItemStatus[]
    - `tracking_id` string: 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: External ID of the account to which the transaction is posted.
    - `status` 'PENDING' | 'EXECUTED' | 'FAILED' | 'ROLLED_BACK' | 'ROLLBACK_FAILED': 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.
  - `credits` MultiLegItemStatus[]
    - `tracking_id` string: 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: External ID of the account to which the transaction is posted.
    - `status` 'PENDING' | 'EXECUTED' | 'FAILED' | 'ROLLED_BACK' | 'ROLLBACK_FAILED': 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.

## Other responses

- `400`: Bad request
- `401`: Access token is missing or invalid
- `403`: The request has been lost
- `500`: Internal Server Error

---

[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)