Update a wallet by walletId

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 : When we enable the property checkRatificationOnWalletStatusUpdateToActive and attempt to update the wallet status from Barred to Active, then we check the KYC rule.

Path Params
int64
required
int64
required
Body Params
string

A bank account number for deposits if supported by the underlying bank

configuration
array of objects

Updated AVPs. If not passed then all AVP's will be deleted

configuration
int64

The customer who owns this wallet. If not provided then the wallet must be owned by an organisation and hence organisationId should be provided

string
length between 0 and 200

Wallet Description

string

A globally unique identifier set by the tenant for this wallet. Useful for correlating between the tenants systems and Eclipse

string

A unique reference for a wallet used for deposits and other transactions

string
length between 3 and 50

Name of the Wallet

int64

The organisation who owns this wallet. If not provided then the wallet must be owned by a customer and hence customerId should be provided

string
enum
Allowed:
string
enum

The status of the wallet. Impacts if it can currently be used

int64

A unique system generated numeric identifier for the wallet

int32
Responses

400

Bad Request

Language
Credentials
Bearer
JWT
URL
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json