Skip to main content

Version 3.49.1

· 2 min read

Email to End User for new device biometrics enrolment​

Embedders have the option of enabling mobile device biometrics (facial recognition or fingerprints depending on hardware and Android vs iOS) as a multifactor authentication method, provided their application offers End Users a mobile app.

When an End User successfully enrols their first device or a new device for biometrics, Weavr will now send an email directly to them. As well as confirming a successful enrolment, this is also a security feature to alert them in case the device enrolment was not done by them. (In addition to this email, Weavr continues to send a webhook to the Embedder on the status change of the biometrics enrolment flow.)

The following is the default template for this email, where the example text “PasscodeApp” would change to the Embedder’s application name:

WEB

As with other transactional emails sent by Weavr directly to End Users, as the Embedder you have the option to apply your own brand design and potentially wording changes to this email template, subject to approval.

To create or change customised email templates, please open a support ticket.

Additional endpoints now supporting idempotency​

As mentioned in previous Release Notes, we are extending the list of endpoints in the Multi API which can be called idempotently. This can be achieved by including the idempotency-ref header in the requests.

WEB

In this release, the following Multi API endpoints can (optionally) be called idempotently:

  • PATCH /managed_accounts/{id} to update a Managed Account details

  • POST /managed_cards/{id}/physical/activate to activate a physical card

  • POST /managed_cards/{id}/physical/replace_damaged to replace a damaged physical card

  • POST /managed_cards/{id}/physical/replace_lost_stolen to replace a lost or stolen physical card

  • POST /managed_cards/{id}/physical/contactless_limit/reset to reset the contactless limit for a physical card

Further information on idempotency is provided in our API Docs here.

Card Settlement Reversal indicated in Embedder Portal​

We have made changes to the way a payment card Settlement Reversal is presented on the Embedder Portal in the Managed Cards transaction activity view. Previously, only the transaction type was shown, without a merchant name.

In order to help Embedder support staff to reconcile a reversal with the relevant settlement, this view now displays the merchant name.

WEB

The changes made to the Embedder Portal statement user interface will not affect the endpoints provided in the Multi API or Multi Back-office API for the generation of Managed Cards statements.