Skip to main content

Version 2.14.3

· 2 min read

New occupation types for consumer identities

When creating an identity, you need to specify the occupation of the root user who owns the consumer identity. We added 2 new occupations to the list, PR_MARKETING and MANUFACTURING. API endpoints affected:

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

New error code when verifying an already verified mobile number

As part of the due diligence process, root users are required to verify their mobile number.

The API endpoint POST /corporates/\{id\}/users/mobile/send_verification_code will return a 409 - Conflict error with code ALREADY_VERIFIED if you trigger the send verification code on an already verified mobile number.

New error code when initiating a send or transfer transaction

The destinationAmount.amount should always be a positive number. If a negative number is provided, a 409 - Conflict error with code INVALID_AMOUNT. API endpoints affected:

  • POST /transfers/_/execute
  • POST /send/_/execute

Due Diligence limits are now deprecated

This is part of a larger initiative in which we are upgrading our risk management systems to cater for the growing number of transactions flowing through Weavr. The allowedLimits and remainingLimits have been deprecated and will be removed in future releases. API endpoints affected:

  • POST /consumers/\{id\}/kyc/get
  • POST /corporates/\{id\}/kyb/get

Instead of monitoring your customers’ restrictions via limits, you will be able to access this information in the transaction details whenever a transaction or an identity is flagged for investigation. More details on how this will work will be provided later on.