Re-branding our build environment​

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.

Update to the physical card upgrade process​

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.

More descriptive error codes for the transfer transaction​

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.

API ChangeLog​

More flexible physical card PINs​

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.

New Webhook notifications​

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.

Updates to the Transfer transaction​

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.

API ChangeLog​

What's New​

• Passwords: A new API endpoint is being introduced to trigger the password expiry for a user. When this API is called, the latest version of the user's password will be expired.
  • POST /passwords/{credential_id}/expire

What's Changed​

• Physical cards can be assigned a custom delivery name and surname which when provided will replace the identity's business name on the postage address when delivering the physical card. This is particularly useful when you want to deliver a physical to a corporate user rather than the business.
  • POST /managed_cards/{id}/physical/upgrade
  • POST /managed_cards/get
  • POST /managed_cards/{id}/unfreeze
  • POST /managed_cards/{id}/physical/report_stolen
  • POST /managed_cards/{id}/physical/replace_damaged
  • POST /managed_cards/{id}/physical/report_lost
  • POST /managed_cards/{id}/physical/replace_lost_stolen
  • POST /managed_cards/{id}/physical/activate
  • POST /managedcards//assign
  • POST /managed_cards/{id}/remove
  • POST /managed_cards/{id}/get
  • POST /managed_cards/{id}/update
  • POST /managedcards//create
  • POST /managed_cards/{id}/freeze

What's Changed​

• The hasPending request parameter has been removed for both the managed_account and managed_card resources.
  • POST /managed_accounts/get
  • POST /managed_cards/get