Update an existing wallet. This will update any wallet in the tenant irrespective of it being tenant-level, customer or organisation. Null fields are ignored so it acts like a PATCH. Wallet type can be changed so long as: (1) The currency attribute is the same on both types (2) The wallet mode is the same on both types (3) The customer or organisation owning the wallet passes the KYC ruleset of the new wallet type.
(4) supported wallet mapping is RPP_PROXYNote : (1) When we enable the property checkRatificationOnWalletStatusUpdateToActive and attempt to update the wallet status from Barred to Active, then we check the KYC rule. (2) Updating the wallet status will not affect the status of the cards associated with the wallet. Cards can be updated independently. (3) organisationId is the one exception to the null-ignore/PATCH behaviour above: omitting it keeps the wallet's existing organisation link untouched, but explicitly sending "organisationId": null clears it.