# Real Cards
source: https://developer.mastercard.com/commercial-connect-api/documentation/use-cases/rc/index.md

The real card use cases illustrate the process of a partner registering, searching, managing, updating, replacing, and deleting real cards.
Note: In the following diagrams, optional steps are denoted with dashed arrows instead of solid arrows.

## Register a real card {#register-a-real-card}

Partners use these endpoints to register a real card with authorization controls and contacts. Authorization controls and contacts are not required to register the real card.

Optionally, you can add the authorization controls and contacts after the initial registration of the real card. The authorization controls apply to the real card only.
Alert: You must register a real card in order to create a virtual card. Diagram rcreg-withcc
API Reference: `POST /accounts/real-cards`


API Reference: `POST /accounts/real-cards/{account_id}/card-controls`


API Reference: `POST /accounts/real-cards/{account_id}/card-contacts`

## Search real card details {#search-real-card-details}

Partners use this endpoint to search for a registered real card within defined search parameters.

Search parameters:

* Search by real `cardNumber`

The search returns a list of real card numbers and the associated `accountId`.

The `accountId` can be used to retrieve additional real card details using the Retrieve real card details endpoint.
Diagram rcsearch
API Reference: `POST /accounts/real-cards/searches`

## Manage real cards {#manage-real-cards}

### Retrieve real card details for existing real card {#retrieve-real-card-details-for-existing-real-card}

Partners use this endpoint to retrieve real card details and existing authorization controls and contacts.
Diagram rcretrievedet
API Reference: `GET /accounts/real-cards/{account_id}`

### Update real card details {#update-real-card-details}

Partners use this endpoint to update real card details of an existing real card such as the name and expiration date associated with the real card.
Diagram rcupdatedet
API Reference: `PUT /accounts/real-cards/{account_id}/card-details`

### Manage real card contacts {#manage-real-card-contacts}

Partners use these endpoints to update or remove a contact for a real card.
Diagram rccontacts
API Reference: `PUT /accounts/real-cards/{account_id}/card-contacts`


API Reference: `DELETE /accounts/real-cards/{account_id}/card-contacts`

## Update real card status {#update-real-card-status}

Partners use this endpoint to update the status of a real card.

The `ACTIVE` or `BLOCKED` statuses allows users to block or unblock a real card. This can be used before deciding on further action if a card is reported as lost or stolen.
Diagram rcstatus
API Reference: `PUT /accounts/real-cards/{account_id}/card-status`

## Replace a real card {#replace-a-real-card}

Partners use this endpoint to replace an existing real card with a different real card. This can be used if a card is reported as lost or stolen.

Replacing a real card will not affect the functionality of virtual cards created using the originally linked real card. All existing virtual cards will continue to be associated with the replaced card. The `accountId` for the real card will remain the same.
Diagram rcreplace
API Reference: `PUT /accounts/real-cards/{account_id}/card-replacement`

## Delete a real card {#delete-a-real-card}

Partners use this endpoint to delete a real card for a specific real card `accountID`. Deleting a real card renders the real card inactive. Deleting a real card removes it from the system and makes it unusable for both payments and virtual card creation.
Alert: A real card associated with any virtual cards cannot be deleted. Diagram rcdelete
API Reference: `DELETE /accounts/real-cards/{account_id}`