Updated the company registration number to optional
You can now onboard sole traders who do not have a company registration number. The company.registrationNumber
parameter can now be left empty.
Note, that for other company types, the registration number is still required to complete the KYB process.
Affected APIs:
GET /corporates
POST /corporates
PATCH /corporates
New sender name information in the deposit webhook
The account deposit webhook now includes new senderName
field as part of the deposit information.
Affected webhooks:
POST /managed_accounts/deposits/watch
New cancelled type for card authorisations
Card authorisations are cancelled if an approve or reject decision is not received by the provider in the agreed time. This ensures that no authorisations are wrongly approved.
If a card authorisation is cancelled by the provider, you will receive a card authorisation webhook notification having the authorisationType
field set as CANCELLED
. Cancelled card authorisations are now included in the card statement API endpoint with their entry.transactionId.type
being AUTHORISATION_CANCELLATION
.
Affected webhooks:
POST /managed_cards/authorisations/watch
Affected APIs:
GET /managed_cards/\{id\}/statement
New Pending state for deposit, transfer and send transactions
In most cases, transactions are executed instantly, however there are cases where a transaction needs to be temporarily paused. This may be due to different reasons, ranging from asynchronous processes to transaction monitoring.
If a deposit, transfer or send transaction is in a pending state, its transaction state
will be marked as PENDING
and will resume automatically as soon as all requirements are met.
Affected APIs:
GET /transfers
GET /transfers/\{id\}
POST /transfers
GET /sends
GET /sends/\{id\}
POST /sends
Additional transaction information in the managed account and managed card statement
The following fields are now available in the the managed account and managed card statement:
actualBalanceAfter
actualBalanceAdjustment
availableBalanceAfter
availableBalanceAdjustment
entryState
Instrument balances are represented using both an actual and an available balance. The actual balance shows how much funds actually reside on the instrument, while the available balance shows how much funds are available to be used. If there are no pending transactions on the instrument, the available and actual balance should be equal. Transaction entries returned in the statement APIs are reporting a balance change in one or both balances.
Note that the balanceAfter
field is now deprecated in favour of the availableBalanceAfter
.
The new transaction entryState
field indicates whether a transaction has moved into a PENDING
or COMPLETED
state. When a transaction is in a PENDING
state, this means that some fund movements have completed however additional fund movements are still pending. Once a transaction is moved to a COMPLETED
state, this means that all expected fund movements are now complete.
Affected APIs:
GET /managed_cards/\{id\}/statement
GET /managed_accounts/\{id\}/statement