> ## Documentation Index
> Fetch the complete documentation index at: https://developer.nomba.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fetch Transaction

> Retrieve the status of an initiated mobile money collection

<Card title="Fetch Transaction" icon="magnifying-glass" href="/nomba-api-reference/global-collections/fetch-mobile-money-transaction" />

# `GET /v1/global-collection/transactions/{transactionId}`

Retrieve the status of any initiated mobile money transaction. Use this endpoint to confirm whether a collection was successful, pending, or failed — keeping your records accurate and your customers informed.

<CodeGroup>
  ```bash Request theme={null}
  curl --request GET \
    --url https://api.nomba.com/v1/global-collection/transactions/a822e327-4bcd-40ec-ac61-ed3622eac000 \
    --header 'Authorization: Bearer <token>' \
    --header 'accountId: <accountId>'
  ```

  ```json Response theme={null}
  {
    "code": "00",
    "description": "Successful",
    "data": {
      "transactionId": "a822e327-4bcd-40ec-ac61-ed3622eac000",
      "coreUserId": "xxxx-xxxx-4402-97c0-6c3824cxxxxx",
      "account": "0980802918",
      "status": "SUCCESS",
      "amount": 10.00,
      "currency": "CDF",
      "vendor": "MPESA",
      "gatewayMessage": "APPROVED",
      "gatewayCode": "Merchant credited"
    }
  }
  ```
</CodeGroup>

#### Path parameters

<ParamField path="transactionId" type="string" required>
  The `transactionReference` returned when the inflow was initiated.
</ParamField>

#### Response body

<ResponseField name="transactionId" type="string" required>
  The unique collection transaction ID.
</ResponseField>

<ResponseField name="coreUserId" type="string">
  The Nomba account ID that received the collection.
</ResponseField>

<ResponseField name="account" type="string">
  The customer's mobile money account (phone number).
</ResponseField>

<ResponseField name="status" type="string" required>
  Current status of the collection.

  | Value              | Description                                                                                                                                   |
  | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
  | `PENDING`          | Payment prompt sent; awaiting the customer's action.                                                                                          |
  | `APPROVED`         | The provider approved the charge.                                                                                                             |
  | `SUCCESS`          | The collection completed.                                                                                                                     |
  | `FAILED`           | The collection did not complete.                                                                                                              |
  | `PENDING_APPROVAL` | The provider returned no outcome within the polling window, so the collection is unresolved. It can still settle on a late provider callback. |
</ResponseField>

<ResponseField name="amount" type="number" required>
  The collected amount.
</ResponseField>

<ResponseField name="currency" type="string" required>
  The currency of the collection.
</ResponseField>

<ResponseField name="vendor" type="string">
  The mobile money network the collection was requested on, echoing the `topupVendor` you sent.
</ResponseField>

<ResponseField name="gatewayMessage" type="string">
  The provider's own response word, passed through unchanged.
</ResponseField>

<ResponseField name="gatewayCode" type="string">
  What that word means, in plain words.

  | `gatewayMessage` | `gatewayCode`              |
  | ---------------- | -------------------------- |
  | `ACCEPTED`       | Awaiting customer approval |
  | `APPROVED`       | Merchant credited          |
  | `DECLINED`       | Payment declined           |

  Those are the three words the providers write. Anything else leaves `gatewayCode` null.
</ResponseField>