Corporate webhook events

Corporate webhook events inform you of activity on the corporatesCorporates (Corporate Identity). Business entities that can be onboarded as customers on Weavr. Corporate customers represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. you have onboarded.

Set up webhooks first

To receive these events, you need to set up a webhook receiver in your app. See the webhooks guide for the full setup.

KYB status updates

We submit KYBKYB (Know Your Business). Know Your Business - the identity verification process for corporate customers. This process allows you to securely verify your business customer's identity. Weavr asks users to submit the information and documentation they need for approval by financial providers. details to a third party service provider using the KYB UI component. The third party performs verification asynchronously. This webhook gives you the corporate's acceptance status and its latest KYBKYB (Know Your Business). Know Your Business - the identity verification process for corporate customers. This process allows you to securely verify your business customer's identity. Weavr asks users to submit the information and documentation they need for approval by financial providers. run for each regulatory financial institution.

Embedding the KYB flow

For more information on the KYBKYB (Know Your Business). Know Your Business - the identity verification process for corporate customers. This process allows you to securely verify your business customer's identity. Weavr asks users to submit the information and documentation they need for approval by financial providers. process, see Corporate due diligence and KYB.

The information is sent to you using the <<WEBHOOK_URL>>/corporates/kyb/watch webhook URL.

Configuring your webhook URL

The <<WEBHOOK_URL>> is the URL configured in your application settings.

The webhook includes the following information:

• The corporateId, which is the unique identifier of the corporate.
• The corporateKybStatus, which is the corporate's lifecycle status: NEW, PENDING, APPROVED, REJECTED, or CLOSED. Only APPROVED means the corporate may use financial services.
• kybRuns[], containing the latest run for each regulatory financial institution. See KYB runs for the fields and exact status values.

The legacy status, ongoingStatus, and details fields are deprecated but remain populated. They are derived from the same data as the new fields, so they cannot conflict.

corporateKybStatus and kybRuns[] are also included for corporatesCorporates (Corporate Identity). Business entities that can be onboarded as customers on Weavr. Corporate customers represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. in these events:

• Identity activated (IdentityActivatedEvent)
• Identity deactivated (IdentityDeactivatedEvent)

Stakeholder due diligence updates

We submit each stakeholder's details (directors, UBOs, and other authorised representatives) to a third party service provider using the Stakeholder due diligence UI component. The details are verified asynchronously from other processes. This webhook is triggered whenever there is an update on the status of one of the corporate's stakeholders.

Stakeholder terminology

The API represents these stakeholders (directors, UBOs, authorised representatives) as beneficiaries of the corporate KYBKYB (Know Your Business). Know Your Business - the identity verification process for corporate customers. This process allows you to securely verify your business customer's identity. Weavr asks users to submit the information and documentation they need for approval by financial providers. process. For this webhook, treat beneficiary, director, and stakeholder as equivalent.

The information is sent to you using the <<WEBHOOK_URL>>/corporates/kyb/beneficiaries/watch webhook URL.

The webhook includes the following information:

• The event, which indicates the changes made to the beneficiaryBeneficiaryA trusted recipient for payments that includes both information about the business or individual as well as their bank account or instrument details. When using trusted beneficiaries, customers may be allowed to skip Strong Customer Authentication (SCA) when executing Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Now referred to as a Trusted Payee. details.
• The eventDetails, provided only if the beneficiaryBeneficiaryA trusted recipient for payments that includes both information about the business or individual as well as their bank account or instrument details. When using trusted beneficiaries, customers may be allowed to skip Strong Customer Authentication (SCA) when executing Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Now referred to as a Trusted Payee. details were not approved. In most cases, you can use this information to fix issues with provided documents and/or details.
• The additionalInformation, which includes information on the corporate and the beneficiaryBeneficiaryA trusted recipient for payments that includes both information about the business or individual as well as their bank account or instrument details. When using trusted beneficiaries, customers may be allowed to skip Strong Customer Authentication (SCA) when executing Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Now referred to as a Trusted Payee. that triggered the webhook.