Mark Brown

We're unlikely to expose running balances outside of statements. This feature would be exposing the spendable balance on an account at the time of request only.

This can be surprising but query params do need to be correctly URL Encoded. We've tried to call this out in the docs at the end of the Query Parameters...

Transactions will soon expose a "note" field with this value. e.g. `"note": { "text": "my note" }` I'm looking into exposing "attachments" as well separate to this.

Transactions return an optional "attachment" relationship. They can be queried separately as a new resource. ``` GET /attachments GET /attachments/{id} ``` Docs will update shortly.

> would you ever consider POST / PATCH for Notes? Yes, absolutely.

Transactions will soon expose a "performingCustomer" with this e.g. `"performingCustomer": { "displayName": "$mark" }` It'll return either the Upname or preferred name.

Closing as a duplicate of https://github.com/up-banking/api/issues/16

Separating Payment and Transfer requests.

Not at this stage, these tokens are still intended for personal use only. We do support Open Banking though which does what you describe.

Thanks for the question Lewis, has sparked a bit of discussion internally. There is a desire to see the API progress. I'll get on top of the unanswered issues so...