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.
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.
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:
/managed_cards/\{id\}/physical/activate//managed_cards/\{id\}/physical/pin/unblock/managed_cards/\{id\}/physical/pin/get/managed_cards/\{id\}/physical/pin/setA 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.
You may have already noticed changes in the documentation and in our communication, we are renaming our build environment to sandbox. The re-branded sandbox environment will have the same features and capabilities we already offer in the build environment.
You can only upgrade virtual cards to physical cards if their state is ACTIVE. If the card being upgraded is currently BLOCKED the POST /managed_cards/\{id\}/physical/upgrade API call will return a 409 - Conflict error with error code INSTRUMENT_BLOCKED.
We have introduced 2 new error codes SOURCE_INSTRUMENT_BLOCKED and DESTINATION_INSTRUMENT_BLOCKED that replace the current error code ACCOUNT_BLOCKED. With these new error codes you can provide more informative messages to your customers and give better options on how to perform the transfer transaction.
You can now show and update physical card PINs as soon as a virtual card is upgraded to a physical card. Previously cards had to be activated first.
We have added a new webhook so that you are notified when there are updates on the KYC status of a corporate's director or beneficiary.
We are enhancing our APIs so that we can support a broader set of providers and use-cases. In some use-cases, the Transfer transaction may not be executed instantly so the transfer transaction's status will be shown as PENDING. You can check the status of the transaction by calling the transfers/get or transfers\{id\}\get APIs.
POST /passwords/{credential_id}/expire