Skip to main content

Version 3.51.0

· 4 min read
Kristina Gauci

New Bulk processing capabilities in the Multi API​

This new feature is available to try out, on request (via support ticket or your account manager).

End-customer businesses (i.e. Corporates) often have to perform certain actions in bulk or batches. For example when an employer enrols their employees into their benefits programme. In such cases, the Embedder’s application can call a Multi endpoint for each individual end user action, as many times as necessary. We are now providing built-in bulk processing capabilities to make this type of repetitive/batch action easier to run and monitor.

Bulk operations refers to the capability of grouping multiple individual API-based actions into a batch. Over time we will make available an increasing range of common actions as bulk operations.

Running a bulk operation creates a Bulk Process, which is a parent task representing the workload, with a lifecycle (statuses) and management method. We aim to make this manageable in a consistent way regardless of the type of operation being performed in different or concurrent processes.

The first bulk operations we’re making available are:

  • POST bulks/users Bulk create Corporate Authorised Users

  • POST bulks/user/_user_id_/invite Bulk invite Corporate Authorised Users

  • POST bulks/managed_cards/_id_/spend_rules Bulk update spend rules across Managed Cards

See our documentation for full details of the underlying Multi API calls.

Owner details added to the manual transaction Webhook event​

Previously for Embedder programme developers or technical administrators that enabled Weavr Webhook API, the manual transaction webhook event provided information relating to the transaction and the financial Instrument, but the Instrument owner's details were not included.

We’re now including the Instrument owner's details in the manual transaction event webhook. The owner details will include the type (whether corporate or consumer) and the owner ID.

WEB

This means that the additional data (the owner ID) can be used to reconcile all manual transactions impacting a single customer. This update will be made available automatically upon release and visible once a manual transaction webhook event is received.

Additional measure to avoid shared mobile device for biometrics​

Currently, for a device that has been enrolled for biometrics, it is possible to fully log-out, and then a different user use the same device to log-in. It is already not possible to enrol the same device for two users, and so a secondary user in that scenario would be able to log in, but then not be permitted to access functions requiring a Stepped-Up token.

We are closing this edge case to strengthen the security of our biometrics SDK: once the device is enrolled, it can only be used for logins by the unique end user who set up biometrics. For anyone else to use that device for their own logins to the Embedder's application, it would need to be unenrolled by the first end user (thus freeing it up to be enrolled into biometrics by a different user).

Updated word separator in Embedder Portal URLs​

In the process of standardising URL structure in the Embedder Portal we have replaced underscores (_) with hyphens (-) in paths of: /programmes/:programmeId/console/

Example:

  • managed_accounts -> managed-accounts
  • managed_cards -> managed-cards

All navigation paths should work as usual, and old URLs the Embedder's team have bookmarked should redirect to the new URLs. Please contact us if you spot anything that's not working as expected in the Embedder Portal interfaces.

FATCA reporting for US citizens and residents​

Please note that we are required to report details of any USA citizen/resident account holders under Foreign Account Tax Compliance Act (FATCA) regulations. This applies to Directors or Beneficial Owners of Corporates as well as to Consumers. We will contact you if this affects your live programme.

If you are planning to expand the addressable market of end customers onboarding to your application, whether for US-based customers or other geographic expansion, please discuss with your Weavr account manager (or open a support ticket) to confirm possibilities and any additional processes required.