Proxy Update Process

Prerequisites

Partners are required to create a Proxy and then initiate the update process. For some proxy updates, it may be necessary to upload supporting documents.

Required Documents

For specific types of Proxy data updates, providing an appropriate document confirming the change is required:

• scopeType (for SIGNATORY proxy type) - registry extract, document type: CURRENT_REGISTRY_EXTRACT

• custodyType (for GUARDIAN proxy type) - proof of single custody, document type: PROOF_OF_SINGLE_CUSTODY

The document identifier (documentId) must be provided in the update request for the above-mentioned fields.

Update Process

The process is asynchronous and involves several steps:

1. Partner calls the update proxy endpoint,

2. The system verifies if everything is present,

3. The Proxy is updated and the process finishes.

Update Restrictions Based on Proxy Type

The proxy update process has specific restrictions based on the proxy type:

1. POWER_OF_ATTORNEY and INFORMATION_PROXY:

   • Can update customerProductIds

   • Can update validityType

2. SIGNATORY:

   • Can update scopeType (requires supporting document)

3. GUARDIAN:

   • Can update custodyType (requires supporting document)

How to Call the Update Endpoint

The update is performed by calling the endpoint:

PATCH /roles/proxies/{proxyId}

The request structure should contain a ProxyUpdate object with the appropriate fields to be updated, and when required, a documentId reference to a previously uploaded document.