Skip to main content

Version 3.55.0

· 3 min read

Linked Accounts - further details for End Customer support​

Embedder staff can find a list of all of a (Corporate) End Customer’s Linked Accounts in the Embedder Portal. In this interface we have added to the information panel to include the sort code and account number of the external account, to be used by Embedder staff for supporting End Customers with any queries.

WEB

We have also added a new data dashboard in the Embedder Portal to support the review and analysis of Linked Accounts. This shows Embedder staff key metrics to help with proactive troubleshooting of End Customer Linked Account setup processes:

WEB

The Linked Accounts data dashboard also features a funnel chart that visualises the Linked Account setup journey, showing the various steps which have to be completed.

Additionally, we have updated the SCA Events dashboard to include Linked Account IDs within the Details table for more comprehensive tracking.

You can find out more about Linked Accounts in our documentation here.

Data insights on Micro-enterprises​

Programmes onboarding and servicing UK Corporates are required to track whether the End Customer business is a Micro-enterprise. We have added a new filter and charts to the Corporates data insights dashboard in the Embedder Portal to help Embedder staff manage Micro-enterprises in their programme, if applicable.

Filter Managed Cards by renewal type​

Weavr offers two options in regards to renewal when a card reaches expiry: RENEW and NO_RENEW. For more information see the Card Renewals section in our documentation.

We have added renewalType as an option on the GET Managed Cards endpoint to allow you to filter the results by cards that are set to either RENEW or NO_RENEW.

Effected endpoint: GET /managed_cards

Webhooks for more granular KYC/KYB status changes​

We have enhanced existing webhook functionality for tracking KYC and KYB process states to include webhooks when additional information is required at a certain step, so that the application cannot proceed until something is added or revised.

Weavr will now send webhooks at all of these stages: initiation, pending review, temporary rejection (indicated by an ‘Initiated’ status), and approval or rejection.

In the details passed with the webhook, we may supply a rejection reason (e.g. CorporateKybFailureReason - see API documentation) and there may be a customer-specific message from the support agent.

Affected webhooks:

Prevention of duplicate Consumer Identity creation​

We are strengthening controls to ensure that an individual can only be added once per programme, when creating a Consumer Identity.

If an attempt is made by the Embedder to create a new Consumer, and Weavr considers it’s a probable duplicate within that programme, we will reject with a new error code 409 CONSUMER_ALREADY_EXISTS