> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

# API changes for August 10, 2026

## Logo fields and per-device metrics on device query records

The device query endpoints now return four new fields on each record:

| Field              | Type    | Description                                                                         |
| ------------------ | ------- | ----------------------------------------------------------------------------------- |
| `paypointLogo`     | string  | URL of the paypoint's logo, or `null` when the paypoint has no logo.                |
| `parentOrgLogo`    | string  | URL of the parent organization's logo, or `null` when the organization has no logo. |
| `transactionCount` | integer | Total number of transactions processed by the device.                               |
| `volumeProcessed`  | number  | Total volume processed by the device, as the sum of net transaction amounts.        |

Payabli calculates `transactionCount` and `volumeProcessed` per device (by `deviceId`), not per paypoint. All four fields are also filterable through the `parameters` query string: use string operators for `paypointLogo` and `parentOrgLogo`, and numeric operators for `transactionCount` and `volumeProcessed`.

### Affected endpoints

* [Get list of devices for a paypoint](/developers/api-reference/get-list-of-devices-for-a-paypoint)
* [Get list of devices for an organization](/developers/api-reference/get-list-of-devices-for-an-organization)

## `referenceId` on payout authorization responses

Payout authorization responses return `referenceId` in the `responseData` object — the ID you pass to the capture endpoint to settle the transaction. A declined authorization returns `null`, because no transaction is created.

See [Authorize payout](/developers/api-reference/moneyout/authorize-a-transaction-for-payout) for the full API reference.

## `allowedActions` on payout query records

We've added an `allowedActions` array to each record returned by the payouts query endpoints. It lists the operations currently permitted for a payout, derived on the server from the payout's status, so you no longer have to hardcode status-to-action logic on the client.

The field is always present. Possible values are `capture`, `cancel`, and `reissue`, matching the corresponding MoneyOut endpoint verbs. It's empty for terminal statuses such as paid or canceled. Read `allowedActions` directly rather than inferring available actions from `PaymentStatus`.

```json
{"allowedActions": ["capture", "cancel"]}
```

### Affected endpoints

* [Get list of payouts for paypoint](/developers/api-reference/query/get-list-of-payouts-for-entrypoint)
* [Get list of payouts for organization](/developers/api-reference/query/get-list-of-payouts-for-organization)