> For the complete documentation index, see [llms.txt](https://tembo.gitbook.io/tembo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tembo.gitbook.io/tembo/momo-collection-and-payout-api/api-reference/payout/get-payout-status.md).

# Get Payout Status

### Endpoint

```
POST /payment/status
```

### Request

#### **Headers**

* **`Content-Type`**<mark style="color:red;">**\***</mark> — Must be `application/json`&#x20;
* **`x-account-id`**<mark style="color:red;">**\***</mark> — Your unique TemboPlus account identifier
* **`x-secret-key`**<mark style="color:red;">**\***</mark> — Your TemboPlus API secret key
* **`x-request-id`**<mark style="color:red;">**\***</mark> — Unique UUID per request for tracing

#### **Body Parameters**

* **`transactionId`**<mark style="color:red;">**\***</mark> *(string)* — Transaction ID returned from the Initiate Payout request.
* **`transactionRef`**<mark style="color:red;">**\***</mark> *(string)* — Your original transaction reference used in the Initiate Payout request payload.

#### Example Request Payload

```json
{
  "transactionId": "ZK8pL3vN9qRx",
  "transactionRef": "payment-ref-abc123-2025"
}
```

### Responses

<details>

<summary><code>200</code> OK</summary>

Returns the current status of the payout transaction, including the original partner transaction reference and the TemboPlus transaction ID generated at initiation.

#### Response Format

```json
{
  "statusCode": "PAYMENT_ACCEPTED",
  "transactionId": "gm56e6CmzwyD",
  "transactionRef": "txn-2025-09-22-mobile-001",
  "meta": {} // Additional metadata (may contain extra transaction details)
}
```

</details>

<details>

<summary><code>400</code> BAD REQUEST</summary>

Returned when the request payload is missing one or more required fields, or when any field contains invalid data.

#### Response Format

```json
{
    "statusCode": 400,
    "reason": "VALIDATION_ERROR",
    "details": {
        "transactionId": "\"transactionId\" is required"
    },
    "message": "{\"transactionId\":\"\\\"transactionId\\\" is required\"}"
}
```

*Fields inside `details` and `message` are optional and vary depending on the specific validation failure.*

***

**Common Validation Errors to Avoid**

* Ensure all **required fields** are included in the request body in the right format.
* **`x-request-id`** must be included in the request headers.

</details>

<details>

<summary><code>401</code> UNAUTHORIZED</summary>

Returned when authentication headers are missing or invalid.

#### Response Format:

```json
{
    "statusCode": 401,
    "reason": "INVALID_CREDENTIALS",
    "details": {}
}
```

</details>

<details>

<summary><code>404</code> NOT FOUND</summary>

Returned if no matching collection transaction is found for the given `transactionId` and `transactionRef`.

#### Response Format

```json
{
    "statusCode": 404,
    "reason": "NOT_FOUND",
    "details": {}
}
```

</details>

<details>

<summary><code>500</code> INTERNAL SERVER ERROR</summary>

Indicates a temporary issue within TemboPlus. Retry later or contact TemboPlus Support with your `x-request-id`.

#### Response Format:

```json
{
    "statusCode": 500,
    "reason": "SERVER_ERROR"
}
```

</details>