Change of SMS Sender ID from "Weavr" to "AUTHMSG"​

We have made improvements to the Sender ID of the SMS that is sent during 3DS verification. “Weavr” will no longer be shown in the SMS and the SenderID shown in several countries will be “AUTHMSG” which is a more generalised Sender ID.

Data Insights Dashboard Enhancements​

We are continuously working on improving the functionality within Data Insights to allow you to analyse and understand your data better. As part of this release, we have worked on enhancing our dashboards by introducing the following functionality:

1. A new filter has been added across all dashboards (where applicable), which gives you the option to filter activity within the platform at ‘Programme Name’ level. This is especially beneficial in cases where a number of sub-programmes/applications are set up within your profile.

2. The detailed table within the Physical Cards Overview table has been updated to also include the 'Physical Delivery Tracking Number'.

Mobile Friendly Data Insights​

We’ve improved the data insights tab in the Innovator portal. You can now view and interact with the dashboards from your mobile device.

Resend invites to Directors and Representatives directly from the Innovator Portal​

You can now resend invites to Directors and Representatives to complete their KYC from the Innovator Portal. This is particularly useful if they missed the email or the link that was originally sent to them, has expired.

Note that you can only resend the invite if the director’s / representative’s KYC status is marked as Initiated.

Weavr Back-Office APIs​

The Weavr Back-Office API is a RESTful API that enables you to automate operations for your end-customers. The API includes a subset of the operations already offered in the Weavr Multi API that do not require your end-customer to be logged in.

In this release we will be adding the following operations to the API:

• Charge fee to a corporate
• Charge fee to a consumer
• Get a managed account's details
• Get a managed account statement
• Get a managed card statement
• Create/get a transfer transaction
• Un/block cards

Read the Back Office API guide to learn more on how to integrate and make use of the API.

New error code for KYC Level 1 nationality restrictions​

An additional conflict error code has been added when initiating KYC for a consumer for which the indicated KYC level is not sufficient.

KYC Level 1 is not allowed for individuals with a nationality outside of the EEA or UK. In this case the individual would need to be onboarded at a higher KYC level - a 409 error code KYC_LEVEL_NOT_ALLOWED will be returned in order to indicate this.

Affected API

• POST /consumers/kyc
• POST /consumers/kyc_mobile_sumsub

Physical Cards - Tracking Information​

We are enhancing the information provided in connection with physical cards. When upgrading a virtual managed card to be a physical card the deliveryTrackingMethod and deliveryTrackingCode information will now be visible within the Multi Portal; as part of the card additional information section. Additionally this information will also be available within the Multi and Back office GET APIs.

Please note: the deliveryTrackingCode information will be include for delivery methods that support this (for example Registered Mail & First Class Mail). The tracking code will be included within 24 hours following card dispatch.

Affected APIs:

• GET multi/backoffice/managed_cards/\{CARD_ID\}
• GET multi/managed_cards/\{CARD_ID\}
• GET multi/managed_cards

Card Purchase - Decline Reasons Additional Detail​

Transaction data available within the Multi Portal and the Managed Card Statement (GET) have been expanded. Card purchase transactions will now include decline reasons and spend rule failure reasons.

This update provides data consistency across all three sources: Portal, Multi API & webhooks. ( spendRuleFailedReason is displayed as authRuleFailedReason within webhooks)

Affected APIs:

• GET managed_cards/\{id\}/statement

NameOnCard - Regex Alignment​

We have consolidated the supported characters for use within the NameOnCard field of Managed Cards.

Full regex list can be found HERE

SMS - Additional Validation Response​

An additional validation response will be introduced in connection with mobile SMS verification.

409 (conflict) - “MOBILE_COUNTRY_NOT_SUPPORTED” will be returned if the country is not supported for delivery of an SMS code.

Affected APIs:

• POST /consumer
• POST /corporate
• PATCH /consumer
• PATCH /corporate

SMS - Mobile Number - Update Limit​

A limit will be introduced on the number of times a consumer user can update their mobile number within a calendar year.

It will be possible to update a consumer users mobile number up to three times per calendar year. Requests beyond this will receive the below validation response:

409 (conflict) - “MOBILE_NO_CHANGE_LIMIT_EXCEEDED”

Affected APIs:

• PATCH /consumer