Skip to main content

Version 3.50.0

· 3 min read
Dragos Tigoianu

Streamlined API call for incrementing a card spend limit​

In embedded finance use cases delivering employee-spendable benefits / rewards / allowances, a common approach is for employers to set an allowance per employee (/card) on a periodic basis (e.g. monthly, weekly). In some cases, the employer may want to allow the employee to carry over any ‘unused’ budget from the previous period into a new period.

This can be achieved via the Weavr APIs by establishing an “ALWAYS interval” and a “limit”, and then setting a new, higher limit when reaching the end of the period. Until now this required two calls, GET all spend rules for a Managed Card (to determine the current limit), then after calculating the new limit, a second call to PATCH update the spend rules on that Managed Card.

Weavr now offers a streamlined way of doing this, as follows:

We have introduced a new parameter in the spendLimit array - updateMethod with the following enums:

  • OVERWRITE : (default option if left null). Overwrites the previous values for the spendLimit object i.e. sets new limits

  • INCREMENT : This will increase the existing value of the spend limit by the amount input the value field.

If INCREMENT is used in conjunction with an ALWAYS interval (as in the example given), it can negate the need for the first GET (of the limit) and the calculation of the new limit. Simply call the PATCH with updateMethod set to INCREMENT, interval to ALWAYS and the value you want the limit to increase by.

INCREMENT can be used on all intervals, not just ALWAYS. You cannot decrease a limit using INCREMENT.

APIs affected:

PATCH /managed_cards/{id}/spend_rules

Data Insights - new SCA Events dashboard​

PSD2 defines that Strong Customer Authentication (SCA) via multifactor authentication needs to be used when End Customers access their sensitive payment account information and make payments.

To help Embedder programme operations and support teams track and troubleshoot SCA actions of End Customers through their programme, we are introducing a new Data Insights dashboard in the Embedder Portal: SCA Events. WEB

Embedder staff can now gain an overview of SCA-type auth events, including the ability to filter by country and authentication channel.

WEB

SCA events covered include:

  • Device enrolment

  • Session Step-Up

  • Transaction confirmation

  • 3DS initiation

  • Beneficiary management

Embedder Portal users can deep-dive into each segment by using the drill-down functionality available across various charts.

Within this dashboard, you can also access a dedicated SMS Analysis tab which you can use to track the journey of SMSs and understand how long SMSs take in each state. This can be helpful for troubleshooting any SMS deliverability issues that are emerging in support cases for particular customers or regions, often due to local telecoms reasons.

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:

  • POST /managed_accounts to create a Managed Account

  • POST /managed_cards to create a Managed Card

  • PATCH /managed_cards/{id} to update a Managed Card

  • DELETE /managed_cards/{id}/spend_rules to delete all spend rules for a Managed Card

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