Skip to main content

Multi API v3.6.0

· 2 min read
Maria Stellini

Introducing SEPA transfersTransfer 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.​

We are excited to announce the launch of SEPA transfersTransfer 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. - for both ConsumersConsumers Individual persons who can be onboarded as identities on Weavr. Consumer identities represent individual customers and require Know Your Customer (KYC) verification. For consumers, the card owner and card assignee are typically the same person. and CorporatesCorporates Business entities that can be onboarded as identities on Weavr. Corporate identities represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees.. You can now extend your product capabilities to enable your customers to both receive funds from 3rd parties, as well as 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. funds to 3rd party bank accounts in the SEPA region.

The “Outgoing Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP).” API endpoints have been updated to include Strong Customer Authentication (SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics).) regulatory requirements. If an outgoing wire transferWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP). needs to be verified via SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics)., the transaction’s state will be updated to PENDING_CHALLENGE.

When this occurs, you will need to initiate an SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics). challenge with the logged in user using the multi/outgoing_wire_transfers/\{id\}/challenges/otp/\{channel\} API endpoint.

Note that before users can verify outgoing wire transfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP)., they must have enrolled their mobile device for strong customer authentication.

Affected APIs:

  • POST /multi/outgoing_wire_transfers
  • POST /multi/outgoing_wire_transfers/\{id\}/challenges/otp/\{channel\}
  • POST /multi/outgoing_wire_transfers/\{id\}/challenges/otp/\{channel\}/verify
  • POST /multi/authentication_factors
  • POST /multi/authentication_factors/otp/\{channel\}
  • POST /multi/authentication_factors/otp/\{channel\}/verify

Deprecated APIs:

  • POST /multi/corporates/verification/mobile/send
  • POST /multi/corporates/verification/mobile/verify
  • POST /multi/consumers/verification/mobile/send
  • POST /multi/consumers/verification/mobile/verify

New optional mobile number field for authorised usersAuthorised Users Individuals that have been invited by the root user to manage an identity's instruments and transactions. They are not the legal owners of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorised Users.​

You can now store the mobile number associated with a user. The mobile number is required if you are onboarding your users for strong customer authentication using one time passwords sent over SMS text messages.

Affected APIs:

  • GET /multi/users
  • POST /multi/users
  • GET /multi/users/\{user_id\}
  • PATCH /multi/users/\{user_id\}

Added support for more Corporate company types​

Different company types require different 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. processes to get approved. 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. flows have been added for PUBLIC_LIMITED_COMPANY, LIMITED_LIABILITY_PARTNERSHIP and NON_PROFIT_ORGANISATION. Now you can onboard these types of companies via the API.

Affected APIs:

  • POST /multi/corporates
  • GET /multi/corporates
  • PATCH /multi/corporates