Transactions

The Transactions API allows you to initiate transfers, query transaction history, retrieve specific transactions, look up bank details by IBAN, and download account statements.

circle-exclamation

Get transactions by Account

get
/api/v1/transactions

Retrieves a paginated list of transactions for a specified account within a date range.

Authorizations
AuthorizationstringRequired

Authentication using a Bearer token.

Query parameters
account_uuidstring · uuidRequired

Universally Unique Identifier (UUID) as defined by RFC 4122.

Example: e1f8a3b1-7d6c-4e9a-9b2e-3f8d1a9c5f2gPattern: ^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$
date_fromstring · date-timeRequired

Start date for the filter period (YYYY-MM-DD).

Example: 2025-04-01
date_tostring · date-timeRequired

End date for the filter period (YYYY-MM-DD).

Example: 2025-04-27
per_pageinteger · min: 1 · max: 100Optional

Number of items to return per page in a paginated response.

Default: 15
pageinteger · min: 1Optional

The current page number for paginated results.

Default: 1
directionstring · enumOptional

Sort direction for the transaction list.

Default: descPossible values:
sortstring · enumOptional

Field to sort the transaction list by.

Default: created_atPossible values:
Responses
chevron-right
200

A paginated list of transactions matching the criteria.

application/json
get
/api/v1/transactions

Create a new transaction

post
/api/v1/transactions

Create a new transaction

Authorizations
AuthorizationstringRequired

Authentication using a Bearer token.

Query parameters
account_uuidstring · uuidRequired

Universally Unique Identifier (UUID) as defined by RFC 4122.

Example: e1f8a3b1-7d6c-4e9a-9b2e-3f8d1a9c5f2gPattern: ^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$
Header parameters
X-Request-IDstring · uuidOptional

A unique identifier for the request. This header can be used for tracking and idempotency control, ensuring the same request is not processed multiple times.

Body

Data required to initiate a new transaction.

account_uuidstring · uuidRequired

The UUID of the source account for the transaction.

Example: d8f7b4a0-6e3c-4b5a-8d1e-2f7c9a8b4e1f
amountnumber · floatRequired

The monetary amount of the transaction. Must be greater than 0 and have a maximum of two decimal places.

Example: 199.99
payment_detailsstring · max: 140 · nullableOptional

Unstructured payment details or remittance information. Mandatory via validation rules if 'payment_code' is not provided.

Example: Payment for invoice #ABC-123
payment_codestring · max: 35 · nullableOptional

Structured payment code (e.g., Purpose Code). Mandatory via validation rules if 'payment_details' is not provided.

Example: RENT
end_to_end_identstring · max: 35 · nullableOptional

Optional End-to-End payment identifier for tracking.

Example: E2E-REF-001
payment_typestring · enum · nullableOptional

Indicates the type of payment. If not specified, SEPA will be selected by default. Accepted values: swift, sepa.

Example: SEPAPossible values:
Responses
post
/api/v1/transactions
circle-info

Important: API error responses during transaction creation reflect only the technical outcome of a request and do not represent the final business state of a payment. The authoritative and final payment status is delivered through the webhook events and should be treated as the source of truth.

More information about webhook event statuses can be found here: Transaction Event | Documentationarrow-up-right

More information about error handling can be found here: Error Handling | Documentation

Get specific transaction by UUID

get
/api/v1/transactions/{uuid}

Retrieves the details of a specific transaction by its UUID, scoped to an account.

Authorizations
AuthorizationstringRequired

Authentication using a Bearer token.

Path parameters
uuidstring · uuidRequired

Universally Unique Identifier (UUID) as defined by RFC 4122.

Example: e1f8a3b1-7d6c-4e9a-9b2e-3f8d1a9c5f2gPattern: ^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$
Query parameters
account_uuidstring · uuidRequired

Universally Unique Identifier (UUID) as defined by RFC 4122.

Example: e1f8a3b1-7d6c-4e9a-9b2e-3f8d1a9c5f2gPattern: ^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{12}$
Responses
chevron-right
200

Successful retrieval of the transaction details.

application/json

Detailed information about a financial transaction.

uuidstring · uuidOptional

Unique identifier for the transaction.

Example: a1b2c3d4-e5f6-7890-1234-567890abcdef
parent_transaction_uuidstring · uuid · nullableOptional

UUID of the parent transaction.

Example: a1b2c3d4-e5f6-7890-1234-567890abcdef
statusstring · enumOptional

Current processing status of the transaction.

Example: pendingPossible values:
aml_statusstring · enumOptionalDeprecated

DEPRECATED: This field is scheduled for removal on August 4th, 2025. It is already deprecated in the Sandbox environment. Anti-Money Laundering (AML) check status of the transaction.

Example: approvedPossible values:
operation_datestring · dateOptional

Date of the transaction operation (YYYY-MM-DD).

Example: 2025-04-27
operation_date_timestring · date-timeOptional

Date and time of the transaction operation (ISO 8601 format).

Example: 2025-04-27T10:30:00Z
operation_date_unixinteger · int64Optional

Date and time of the transaction operation as a Unix timestamp (seconds since epoch).

Example: 1745821800
amountnumber · floatOptional

Transaction amount.

Example: 1234.56
currencystring · ISO 4217Optional

Currency code (ISO 4217).

Example: EUR
payment_typestring · enumOptional

Type of payment rails used.

Example: SEPAPossible values:
transaction_typestring · enumOptional

Type of financial transaction, such as payment, return, adjustment, or fee.

Example: paymentPossible values:
payment_urgencystring · enum · nullableOptional

Urgency level of the payment.

Example: NORMALPossible values:
payment_detailsstring · nullableOptional

Remittance information or payment details provided by the payer.

Example: Invoice #INV-123 Payment
payment_codestring · nullableOptional

Optional payment code associated with the transaction.

Example: SALARY
end_to_end_identstring · nullableOptional

End-to-end identifier for tracking the payment across systems.

Example: E2E-XYZ789
directionstring · enumOptional

Direction of the transaction relative to the account holder.

Example: CREDITPossible values:
document_numberstring · nullableOptional

Reference number of an associated document, if any.

Example: DOC-456
created_atinteger · int64Optional

Timestamp when the transaction record was created in the system (Unix timestamp).

Example: 1745820000
verification_of_payeestring · enumOptional

Verification of the payee match status.

Possible values:
get
/api/v1/transactions/{uuid}

Get bank details by IBAN

get
/api/v1/transactions/iban-details

Retrieves bank details (like BIC, bank name) based on a provided IBAN.

Authorizations
AuthorizationstringRequired

Authentication using a Bearer token.

Query parameters
ibanstringRequired

The International Bank Account Number (IBAN) to look up.

Example: LT89370400440532014200
Responses
chevron-right
200

Successfully retrieved IBAN details.

application/json

Resource representing bank details derived from an IBAN.

ibanstringOptional

The IBAN that was looked up.

Example: LT347044060007958239
is_validbooleanOptional

Indicates if the provided IBAN format is considered valid.

Example: true
bank_bicstring · nullableOptional

The Bank Identifier Code (BIC/SWIFT) associated with the IBAN.

Example: CBVILT2XXXX
bank_namestring · nullableOptional

The name of the bank associated with the IBAN.

Example: AB SEB
get
/api/v1/transactions/iban-details
triangle-exclamation

Last updated

Was this helpful?