# Register a Creditor
source: https://developer.mastercard.com/payment-acceptance-api/documentation/use-cases/register-creditor/index.md

This use case covers the end‑to‑end lifecycle of Creditor management in Commercial Direct Payments (CDP), including registering a new Creditor, updating or deleting an existing Creditor registration, and optionally retrieving Creditor details.

## How Creditor registration works {#how-creditor-registration-works}

The diagram displays the main steps for the Creditor registration process.
Diagram newregistrationflow

1. The Creditor Agent submits the registration request by calling the Creditor registration API.
2. CDP validates the registration.
3. CDP completes the request.
4. CDP notifies the Creditor Agent of the completed registration request.

Tip: You must include the ICA number and registration ID for the Creditor in the request URI. Note: The Mastercard CDP assigned ICA number is used for agent identification in all service requests for core operations. A customer service provider can use their API credentials to transact on behalf of a customer by providing their customer's ICA number in the request. Direct payment agents can still transact by entering their own ICA when sending a transaction to Mastercard CDP.

## Register a Creditor in CDP {#register-a-creditor-in-cdp}

A Creditor Agent can register Creditors through the CDP registration endpoint.
Diagram submitnewregistration

1. The Creditor Agent submits a Creditor registration request to CDP.
   API Reference: `POST /creditor-agents/{ica}/creditors`

2. CDP returns a 201 Created response to the Creditor Agent.

Tip: You will need the registration ID to perform other registration activities for the Creditor.

## Update a Creditor registration {#update-a-creditor-registration}

A Creditor Agent can update a Creditor's registration after the Creditor is successfully registered in CDP. For example, when a Creditor changes its business location, this endpoint updates the registration details.
Diagram updatenewregistration

1. The Creditor Agent submits an Update Creditor registration request to CDP.
   API Reference: `PUT /creditor-agents/{ica}/creditors/{creditor_id}`

2. CDP returns a 204 No Content response to the Creditor Agent.

## Delete a Creditor registration {#delete-a-creditor-registration}

A Creditor Agent can delete a Creditor registration in CDP.
Note: If there is any transaction activity, the Creditor Agent must deactivate the Creditor registration and its associated Creditor payment profile instead of deleting. Contact your Mastercard representative to deactivate. Diagram deletenewregistration

1. The Creditor Agent submits a Delete Creditor registration request to CDP.
   API Reference: `DELETE /creditor-agents/{ica}/creditors/{creditor_id}`

2. CDP returns a 204 No Content response to the Creditor Agent.

Note: The Creditor is marked in "INACTIVE" state once this endpoint is triggered. The Creditor data is deleted after 90 days.

## Retrieve a Creditor registration {#retrieve-a-creditor-registration}

A Creditor Agent can leverage these endpoints to either lookup a single Creditor or all Creditors associated with the agent in CDP.

### Retrieve a single Creditor registration {#retrieve-a-single-creditor-registration}

Diagram retrievenewregistration

1. The Creditor Agent submits a Retrieve Creditor registration request to CDP.
   API Reference: `GET /creditor-agents/{ica}/creditors/{creditor_id}`

2. CDP returns a 200 OK response with the Creditor registration.

### Retrieve all Creditor registrations {#retrieve-all-creditor-registrations}

Diagram retrieve-new-reg

1. The Creditor Agent submits a Retrieve all Creditor registrations request to CDP.
   API Reference: `GET /creditor-agents/{ica}/creditors`

2. CDP returns a 200 OK response with the list of all Creditor registrations.