Skip to main content

Version 3.59.1

· One min read

Statement Filtering on transactions​

We’ve made it easier for you to get the information you need! You can now filter transactions when calling the statement endpoint, so you’ll only receive the ones you're interested in, rather than all transaction types. This means fewer API calls to get the statement view you're looking for, saving you time and effort when building your statements.

Key points​

When calling the statement endpoints, the desired transaction types can be specified in the new filter parameter transactionType.

Key API details​

  • /multi/managed_cards/{id}/statement
  • /multi/managed_accounts/{id}/statement

Custom fees: error handling​

We've improved the error response for custom fees that are incorrectly configured.

A custom fee is triggered by you, via API POST /multi/corporates/fees/charge, according to a pre-set and approved configuration.

Key points​

Previously, if a custom fee was triggered on an instrument in a currency where a value had not been configured, a 200 response was returned. This has been changed to a 409 “FEE_AMOUNT_NOT_SET” response, which more accurately indicates that the fee was not charged.

API details​

  • /multi/corporates/fees/charge