# Set up Authorization Controls on Real Cards
source: https://developer.mastercard.com/business-payment-controls/documentation/use-cases/01-real-cards/index.md

This API supports the following use cases for real cards:

## Set up authorization controls on real cards {#set-up-authorization-controls-on-real-cards}

* [Register](https://developer.mastercard.com/business-payment-controls/documentation/use-cases/01-real-cards/index.md#register-a-real-card-with-controls) a real card with controls
* [Manage](https://developer.mastercard.com/business-payment-controls/documentation/use-cases/01-real-cards/index.md#manage-real-card-controls) real cards with controls
* [Replace](https://developer.mastercard.com/business-payment-controls/documentation/use-cases/01-real-cards/index.md#replace-a-real-card) a real card
* [Block or unblock](https://developer.mastercard.com/business-payment-controls/documentation/use-cases/01-real-cards/index.md#block-or-unblock-a-funding-source) a funding source

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

A company issues corporate credit cards to its employees for business and travel expenses. There are company policies governing the usage and spend limits for their corporate cards, but the company finance team would like to reduce the risk of misuse by applying spend controls and limits.
Using Business Payment Controls, a company can register its corporate credit cards and apply controls limiting how and when the cards can be used, in line with the company's travel and expenses policies.

### Register a real card with controls to manage company spending {#register-a-real-card-with-controls-to-manage-company-spending}

The sequence of the calls to register a real card and add controls to manage company spend:
Diagram 01-register-a-real-card


API Reference: `POST /real-card-accounts`


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


API Reference: `POST /funding-sources`


API Reference: `POST /funding-sources/{funding_source_guid}/controls`

<br />

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

Diagram 01-get-rcn

A company's finance team has registered their employees' corporate credit cards. The finance team wants to confirm the controls that are currently applied.


API Reference: `POST /funding-sources/{funding_source_guid}/controls`


API Reference: `PUT /funding-sources/{funding_source_guid}/controls`

<br />

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


API Reference: `GET /real-card-accounts/{account_guid}`


API Reference: `POST /real-card-accounts/searches`


API Reference: `PUT /real-card-accounts/{account_guid}`


API Reference: `GET /real-card-accounts/{account_guid}/contacts/{contact_guid}`


API Reference: `PUT /real-card-accounts/{account_guid}/contacts/{contact_guid}`


API Reference: `GET /funding-sources/{funding_source_guid}`


API Reference: `PUT /funding-sources/{funding_source_guid}`

<br />

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

Diagram 01-replace-a-real-card

A company-issued credit card is reported lost or stolen by the cardholder. To replace a real card, there are two potential workflows. Users can choose either a basic or a multi-step flow.

* For the basic workflow, the fields `replacedAccountGuid` (real card) and `replacedAccountReason` must be populated.
* The multi-step workflow does not require multiple fields to replace a real card, and deletes the missing card as part of the flow.

The sequence of the calls to replace a lost or stolen real card:

### Single-step flow {#single-step-flow}

1. Register a new real card. Ensure the `replacedAccountGuid` and `replacedAccountReason` fields are populated.
   API Reference: `POST /real-card-accounts`

2. The application checks that the previous real card UUID is active.
3. The application checks the previous real card UUID has an active funding source linked.
4. The application updates the funding source to the new real card UUID. The new real card replaces the missing real card.

### Multi-step workflow {#multi-step-workflow}

1. Register a new real card.
   API Reference: `POST /real-card-accounts`

2. Associate the new real card with the existing funding source.
   API Reference: `PUT /funding-sources/{funding_source_guid}`

3. Delete the missing card account.
   API Reference: `DELETE /real-card-accounts/{account_guid}`

Note: A real card associated with an active funding source cannot be deleted. Any virtual cards linked to the previous real card are now linked to the new real card.

## Block or unblock a funding source {#block-or-unblock-a-funding-source}

The `ACTIVE` or `BLOCKED` status allows users to block or unblock a funding source. This can be used before deciding on further action if a funding source is reported as lost or stolen.
Diagram 01-block-and-unblock-a-real-card

* Change the `{funding_source_guid}` status from `ACTIVE` to `BLOCKED` to block a funding source.
* Change the `{funding_source_guid}` status from `BLOCKED` to `ACTIVE` to unblock a funding source.


API Reference: `PUT /funding-sources/{funding_source_guid}/status`