Skip to main content

Balance transactions

Balance transactions are the itemized record of money added to or returned from your Inttegro balance. Each entry connects an amount to its order and payment or refund, giving finance and support teams a clear trail for reconciliation.

Use Balances to see current totals. Use balance transactions to explain those totals, trace money back to a sale or refund, and build exports for your accounting system.

Operations

The balance transaction object

Every balance transaction belongs to an order. A payment transaction includes its payment_id; a refund transaction includes its refund_id instead.

amount.value is always a non-negative value in the currency's smallest unit. Check type to determine whether the entry records a payment or a refund. Payout and lifecycle timestamps appear only after the corresponding event has happened.

Properties

  • amountobjectAmount of the payment or refund in the currency's smallest unit.Click or tap to expand
    • Name
      currency
      Type
      string
      Description
      Currency code for the transaction.
    • Name
      value
      Type
      integer
      Description
      Non-negative amount in the currency’s smallest unit, such as pesewas for GHS.
  • Name
    available_at
    Type
    timestamp
    Description

    When payment funds are scheduled to become eligible for payout. This can be a future timestamp. Omitted when the entry does not follow the payment availability lifecycle.

  • Name
    claimed_at
    Type
    timestamp
    Description

    When a payout claimed this transaction. Omitted until the claim occurs.

  • Name
    created_at
    Type
    timestamp
    Description

    When the balance transaction was recorded. Transaction pages are ordered by this timestamp from newest to oldest.

  • Name
    id
    Type
    string
    Description

    Unique balance transaction identifier with the bt_ prefix. Use it for lookup and as the reconciliation key in your own records.

  • Name
    order_id
    Type
    string
    Description

    Order associated with the source payment or refund.

  • Name
    paid_at
    Type
    timestamp
    Description

    When this entry completed its money lifecycle. For a transaction included in a payout, this is set when that payout completes. Omitted until completion.

  • Name
    payment_id
    Type
    string
    Description

    Payment that created the balance transaction. Present when type is payment.

  • Name
    payout_id
    Type
    string
    Description

    Payout assigned to this transaction. Omitted until one is assigned.

  • Name
    refund_id
    Type
    string
    Description

    Refund that created the balance transaction. Present when type is refund.

  • Name
    type
    Type
    enum
    Required
    required
    Description

    Why the transaction exists: payment or refund.

POST/balance_transactions/lookup

Look up a balance transaction

Retrieve one balance transaction by its ID. Use this when you already have a bt_... identifier from an order, payout, dashboard, or previous list response and need the complete record.

Request attributes

  • Name
    transaction_id
    Type
    string
    Required
    required
    Description

    Balance transaction ID returned by Inttegro, beginning with bt_.

Request

POST/balance_transactions/lookup
curl https://api.inttegro.com/balance_transactions/lookup \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"transaction_id": "bt_0123456789abcdefghijklmnopqrstuvwxyzABCD"
}'

Response

SDK versionv8.2.0
TransactionResponse {
transaction: {},
}
POST/balance_transactions/page

Page through balance transactions

Browse balance activity from newest to oldest. Start with page 1, then request later pages until the response contains no transactions.

Available through MCP

AI clients can use list_balance_transactions for this operation. MCP read tools return minimized business data and do not change Inttegro state.

Request attributes

  • Name
    page_number
    Type
    integer
    Required
    required
    Description

    1-based page number to retrieve. Supported pages are 1 through 10.

  • Name
    page_size
    Type
    integer
    Required
    required
    Description

    Maximum number of transactions to return. Minimum 1, maximum 256. The final page may contain fewer transactions.

Request

POST/balance_transactions/page
curl https://api.inttegro.com/balance_transactions/page \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"page_number": 1,
"page_size": 2
}'

Response

SDK versionv8.2.0
PageResponse {
page: {},
}