Multi API v3.14.1

Corporate 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. - UBO Additional Information Requirements

As part of our ongoing improvements to compliance and due diligence processes, we have extended the information captured as part of UBO applications; where UBO business ownership is 25% or greater.

For each qualifying UBO, the following information will need to be provided:

• Place of Birth
• Official ID
• Email Address
• Address, including country of permanent residence

Capturing of this additional information will be required, per qualifying UBO application, as of 12th April 2022.

Annual Corporate 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. Refresh.

As part of our ongoing improvements to compliance and due diligence processes, we have extended verification procedures; in connection with pre-existing corporate 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. information.

On an annual basis 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. information supplied will undergo additional verification. Information will be refreshed as part of this process, which will include corporate root usersRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. re-validating through 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, and if necessary, for directors to provide updated KYCKYC Know Your Customer - the identity verification process for consumer identities. This process allows you to seamlessly and securely verify your user's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. information.

Once a refresh has been initiated there are three indications:

• The corporate due diligence status will show a purple bar, stating 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. refreshing, on the Weavr portal.
• The corporate root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user., and individual directors (if necessary), will receive an email advising the need to update due diligence information.
• A webhook event will be triggered that includes an additional “OngoingStatus” parameter, indicating the refresh progress.

Two additional email templates have been incorporated as part of the notification to root usersRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user. and directors. Default branding is used for such templates, but these can be branded according to your corporate design. If you have not already provided input for branding in connection with these emails, and wish to update this, contact us via our support portal https://support.weavr.io and our team will be able to provide assistance with your specific requirements.

Corporate & Consumer Charge Fee - Additional Transaction Details

When using the charge fee API, additional transaction details will be included within the response payload, including the state and transaction ID, allowing the correlation of transaction and associating fee.

Affected APIs:

• POST /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./fees/charge
• POST /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./fees/charge

Password & Passcode UI Components - New Submit Events

Password and Passcode UI components will support the use of enter key interactions for triggering events. Such events can be used instead of requiring users to click a button, allowing for smoother interactions and automatic form submissions.

For more information refer to our Password UI component and Passcode UI component guides.

Prepaid Cards - Fund 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. on Destroyed & Expired Cards

When using the 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. API, unloading of funds will be supported for prepaid cards in a destroyed or expired status. Such 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. must be to another 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. or 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. belonging to the same corporate or consumer identity.

Affected APIs:

• POST /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.