More descriptive purchase decline reasons​

We have updated the authorisations webhook /managed_cards/authorisations/watch to include a comprehensive list of decline reasons.

New KYB temporary failure reasons​

The KYB webhook /corporates/kyb/watch now includes a new details parameter. The new optional parameter contains the reasons why the corporate identity has temporarily failed it’s KYB. Such information can help the corporate solve any problems with the documents or information they provided.

Resend expired end-user invites from the Portal​

We added the ability for you to resend end-user invites from the Portal in case their original invite expired before they completed their registration. The resend invite capability can be found in the end-user details screen.

Re-introducing mandatory corporate details​

When creating a corporate you will be required to specify the following fields:

• companyName
• companyRegistrationNumber
• registrationCountry

API ChangeLog​

## Removing due diligence deprecated fields possibly breaking In previous releases, a number of fields where made deprecated as they where being replaced with other fields which provide additional information on the due diligence of your corporate and consumer customers.

For Corporate KYB the following fields have now been removed: verifications, kyb.allowedLimit and kyb.remainingLimit. The affected APIs are:

• POST /corporates/{id}/get
• POST /corporates/{id}/update
• POST /corporates/_/create
• POST /corporates/{id}/kyb/get

For Consumers KYC the following fields have now been removed kyc.pep, kyc.sanctioned, kyc.enhancedDueDiligence, kyc.allowedLimit, kyc.remainingLimit.The affected APIs are:

• POST /consumers/{id}/get
• POST /consumers/{id}/update
• POST /consumers/_/create
• POST /consumers/{id}/kyc/get

## Deprecating due diligence fields non-breaking We are simplifying further the due diligence information returned to you via the API. This helps you in understanding the status of the KYC or KYB for consumers or corporates respectively.

For Corporates the kyb.enhancedCompanyChecksVerified field has been deprecated. We recommend that you use the kyb.fullCompanyChecksVerified field to get the due diligence status of your corporate.

For Consumers the kyc.fullDueDiligenceAddressMatched field has been deprecated. We recommend that you use the kyc.fullDueDiligence field to get the due diligence status of your consumer.

API ChangeLog​

Additional validation for the call-ref parameter​

When calling any of the APIs offered by Weavr, you can optionally specify a value for the call-ref parameter. If we receive 2 API requests with the same call-ref value, the request will only be executed once. This avoids executing requests multiple times by mistake.

The call-ref parameter has been restricted to a maximum of 255 characters. If a longer call-ref is provided an error 400 - Bad Request will be returned.

API ChangeLog​

Updating the delivery address of a physical card​

We introduced the ability to update the delivery address of a managed card. This feature is particularly useful if the user using a physical card has moved to a different address and you want to make sure that they receive their card at the right address.

You can only update the delivery address for physical cards. If the delivery address is specified when updating a virtual card, the API will return a 409 - Conflict error with error code INSTRUMENT_NOT_PHYSICAL.

New error codes when managing physical cards​

You cannot activate, retrieve or update the pin of a blocked or destroyed physical card. When executing the following APIs on a blocked or destroyed card, the API will return a 409 - Conflict error with error code INSTRUMENT_BLOCKED or INSTRUMENT_DESTROYED:

• POST /managed_cards/\{id\}/physical/activate/
• POST /managed_cards/\{id\}/physical/pin/unblock
• POST /managed_cards/\{id\}/physical/pin/get
• POST /managed_cards/\{id\}/physical/pin/set

New error code when updating the details of a consumer​

A new error code EMAIL_NOT_UNIQUE has been added to the POST /consumers/\{id\}/update API. This error code will be returned if the new email address being specified is already being used by another consumer in your community.

API ChangeLog​