New additions to the Transactions API

What’s changed?

We've enhanced our Transactions API to allow for more detailed financial reporting.

We’ve added two new fields:

• The effective-at field represents the time a transaction takes effect on the account balance.

• The processed-at field represents the time when a transaction was processed by the Griffin system. This will eventually replace our previous post-datetime field.

Our API now supports reverse sorting of transactions:

• The sort=processed-at query gives you the earliest transactions first.

• The sort=-processed-at query gives you the most recent transactions first.

How will this affect existing integrations?

This change won’t immediately break existing integrations. However, we will be deprecating post-datetime. So, you will have to update your integration to look for processed-at instead of post-datetime.

Why have we done it?

The addition of the effective-at field allows for clearer distinction between when a transaction was posted and when it became effective.

This change is particularly important for our bare trust savings accounts. It allows customers to reproduce our interest accrual calculations, which include all transactions with an effective-at time prior to 5pm UK time.

Thanks for reading!

Ready to explore? Sign up for our sandbox to start testing.

Need help? Chat with us in-app or email product@griffin.com.

Stay connected:

 Read our docs

 Join our Slack community

Try our Postman collection

 Follow us on LinkedIn