Skip to main content

Version 3.6.0

· 2 min read

Introducing SEPA transfers

We are excited to announce the launch of SEPA transfers - for both Consumers and Corporates. You can now extend your product capabilities to enable your customers to both receive funds from 3rd parties, as well as send funds to 3rd party bank accounts in the SEPA region.

The “Outgoing Wire Transfers” API endpoints have been updated to include Strong Customer Authentication (SCA) regulatory requirements. If an outgoing wire transfer needs to be verified via SCA, the transaction’s state will be updated to PENDING_CHALLENGE.

When this occurs, you will need to initiate an SCA challenge with the logged in user using the multi/outgoing_wire_transfers/\{id\}/challenges/otp/\{channel\} API endpoint.

Please note that before users can verify outgoing wire transfers, 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 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 KYB processes to get approved. KYB 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