Skip to main content

Multi API v3.10.0

· 3 min read
Maria Stellini

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 KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. 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, transferTransfer A transaction that moves funds between instruments managed by Weavr. The source and destination instruments of a transfer transaction must be owned by the same identity. Transfers can be scheduled for future execution and can be performed in bulk operations. and sendSend A transaction type that allows sending funds to another identity's instrument or to a beneficiary. Send transactions may require Strong Customer Authentication depending on the destination and whether it's a trusted beneficiary. 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, transferTransfer A transaction that moves funds between instruments managed by Weavr. The source and destination instruments of a transfer transaction must be owned by the same identity. Transfers can be scheduled for future execution and can be performed in bulk operations. or sendSend A transaction type that allows sending funds to another identity's instrument or to a beneficiary. Send transactions may require Strong Customer Authentication depending on the destination and whether it's a trusted beneficiary. 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 accountManaged Account An account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. and managed cardManaged Card A payment card (virtual or physical) that can be created and managed through the Weavr platform. Cards can operate in prepaid mode (with their own balance) or debit mode (linked to a managed account). All cards must be assigned to a card assignee who is an Authorised User. statement​

The following fields are now available in the the managed accountManaged Account An account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. and managed cardManaged Card A payment card (virtual or physical) that can be created and managed through the Weavr platform. Cards can operate in prepaid mode (with their own balance) or debit mode (linked to a managed account). All cards must be assigned to a card assignee who is an Authorised User. 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