The mobile number used by authorised users within the same corporate or consumer identity must be unique. If a mobile number is already being used by another user, the API will return an HTTP 409 - Conflict error with error code MOBILE_NOT_UNIQUE.
You can now download the due diligence screening report of a consumer from the Multi Portal. In the report, you will find detailed information on the status of the due diligence process and any reasons for which the identity hasn't been approved yet.
This report will only be available if the identity has not completed due diligence.
In the deposit transaction details screen in the Multi portal, you can now see the sender of deposit transactions received on your customers' managed accounts.
Send transactions can transfer funds between cards and managed accounts. You can now charge a different fee, based on the source and destination instrument types involved in the transaction.
End-customer fees can be configured in the Multi portal.
When configuring your end-customer forex fees in the Multi portal, you can now choose from increments of 0.25%.
Please note that forex fees are attached to a card when it is being created, so if you change the fee afterwards, the new rate will only apply for newly created cards.
A new rejectionComment field has been added in the consumer and corporate due diligence webhooks to include a detailed description as to why due diligence has been temporarily rejected. This information should be used together with the failureReason field to provide more information to the user.
Affected webhooks:
We have updated our webhook API documentation design style so that it is in line with the Multi API design style. Don't worry, nothing has changed with the webhooks themselves.
You can find the new webhook documentation here.
Corporate root users who are opening an account on behalf of a company must either be a director or an authorised representative of the company. This is already being checked as part of the corporate KYB process, however the rootUser.companyPosition will now start accepting only DIRECTOR or AUTHORISED_REPRESENTATIVE as valid values.
Affected APIs:
Different company types require different KYB processes and therefore the companyType field cannot be updated once a corporate identity is created. The companyType field will be removed from the update corporate API endpoint.
Affected APIs:
When activating an already activated user, the API will start returning an http 204 - No Content response instead of returning an http 409 - Conflict with error code USER_ALREADY_ACTIVATED.
Similarly, when deactivating an already deactivated user, the API will start returning an http 204 - No Content response instead of returning an http 409 - Conflict with error code USER_ALREADY_DEACTIVATED.
Affected APIs:
POST multi/users/\{user_id\}/activatePOST multi/users/\{user_id\}/deactivateAdditional occupation options have been added to consumer identities. Now you can enable your customers to choose STUDENT, UNEMPLOYED, RETIRED or OTHER as their occupation.
Affected APIs:
GET multi/consumersPOST multi/consumersPATCH multi/consumersWe 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_transfersPOST /multi/outgoing_wire_transfers/\{id\}/challenges/otp/\{channel\}POST /multi/outgoing_wire_transfers/\{id\}/challenges/otp/\{channel\}/verifyPOST /multi/authentication_factorsPOST /multi/authentication_factors/otp/\{channel\}POST /multi/authentication_factors/otp/\{channel\}/verifyDeprecated APIs:
POST /multi/corporates/verification/mobile/sendPOST /multi/corporates/verification/mobile/verifyPOST /multi/consumers/verification/mobile/sendPOST /multi/consumers/verification/mobile/verifyYou 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/usersPOST /multi/usersGET /multi/users/\{user_id\}PATCH /multi/users/\{user_id\}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/corporatesGET /multi/corporatesPATCH /multi/corporates