Skip to main content

56 posts tagged with "Multi-v3"

View All Tags

Version 3.25.0

· One min read
Isaac Tanti

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.


Version 3.24.0

· 2 min read
Isaac Tanti

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

Version 3.23.0

· One min read
Isaac Tanti

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

Version 3.21.0

· 2 min read
Isaac Tanti

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

Version 3.19.0

· 2 min read
Maria Stellini

OWT information in the managed account statement

The activity statement for managed accounts in the innovator portal now contains additional information for Outgoing Wire Transfers:

  • Beneficiary name
  • Beneficiary account
  • Beneficiary bank code
  • Reference/description

Most of the above information, apart from the description, was already available in the GET a managed account statement API; this has now been added as well. When retrieving a managed account statement, for records of transactionId.type = OUTGOING_WIRE_TRANSFER, we now share the payment ‘description’ (that was entered by the user when making the payment), under additionalFields = description

Affected APIs:

  • GET /managed_accounts/\{id\}/statement

Strong Customer Authentication for Sends

As part of our continued compliance with Strong Customer Authentication (SCA) requirements, two-factor authentication will be extended to also include Sends. This can be challenged using OTP via SMS. More authentication methods will be coming soon.

In the meantime we are planning to introduce some exemptions such as the low-value to reduce the number of the challenges required as allowed by the regulation. The exemption will work out of the box.

We will soon be reaching out directly and providing dedicated information to help you upgrade your integration and incorporate SCA processes in your product. In the meantime, you can have a look at our documentation here.