---
title: "List transaction flows"
method: GET
path: "/v1/transaction-flow"
tags: ["Transaction flows"]
---

# List transaction flows

`GET /v1/transaction-flow`

List transaction flow configurations that link transaction types and processing codes.

See [Processing codes and transaction types](https://developers.pismo.io/pismo-docs/docs/processing-codes-and-transaction-types) and [Payments configurations](https://developers.pismo.io/pismo-docs/docs/payments-configurations) for information on processing codes and transaction types, how to create them, and map them to each other.

## Query parameters

- `processingCode` string
- `transactionTypeId` integer
- `pageOffset` integer

## Response `200`

OK

- object
  - `has_next` boolean — Indicates whether there are more pages after the current page
  - `items` TransactionFlow[]
    - object[]
      - `transaction_type_id` integer — Transaction type ID. Certain IDs are reserved by the platform and cannot be used.
      - `processing_code` string — Processing code that issues the transaction type
      - `key` 'PRINCIPAL' | 'INSTALLMENT' | 'CONTRACT' | 'OTHER' — Sets the relation key that links transaction type and processing code. * `PRINCIPAL` uses principal amount. * `INSTALLMENT` uses installment amount. * `CONTRACT` uses contract amount. * `OTHER` uses any custom amount, such as fees, taxes, or other charges. When the key is OTHER, you must define the `custom_key` value.
      - `custom_key` string — Sets a customized relation between transaction type and processing code, usually to configure fees, taxes, or other charges. REQUIRED if the key is OTHER.

## Other responses

- `400` — Bad request
- `500` — Internal error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)