> ## Documentation Index > Fetch the complete documentation index at: https://docs.fexco.com/llms.txt > Use this file to discover all available pages before exploring further. # Deactivate a merchant > Remove a merchant from active DCC participation using the Boarding API or XML Boarding File Upload. When a merchant no longer needs DCC, you can deactivate them. After deactivation, the rate service stops returning offers for that merchant. The merchant record is not deleted. It stays in the system for historical reporting and can be reactivated later. ## Before you start You need the following before you can deactivate a merchant. * At least one [boarded merchant](https://docs.fexco.com/dcc/guides/merchant-boarding/board-api.md) that you want to deactivate. * For Boarding API deactivation: [OAuth authentication](https://docs.fexco.com/dcc/api-reference/authentication/oauth.md) configured. * For Boarding File Upload (XML) deactivation: [secure connectivity setup](https://docs.fexco.com/dcc/guides/getting-started/security-setup.md) completed, including Secure File Transfer Protocol (SFTP) credentials. ## What deactivation does Deactivation is a soft delete. The merchant record remains in the system but is flagged as inactive. Once deactivated: * The rate service rejects DCC offer requests for the merchant. * The merchant no longer appears as active in reporting. * Historical transaction data is preserved. * The merchant can be reactivated without re-boarding. ## Deactivate via Boarding API The Boarding API supports deactivation through the [Create a batch of boarding requests](https://docs.fexco.com/dcc/api-reference/boarding-rest/create-boarding-batch.md) endpoint. Set the `operation` field to control what is deactivated. | Operation | Effect | | :- | :- | | `DEACTIVATE_LOCATION` | Deactivates the merchant and all of its card acceptors. | The full steps to deactivate a merchant via the Boarding API are below. **Step 1** ### Submit a deactivation request Send a `POST` request to [Create a batch of boarding requests](https://docs.fexco.com/dcc/api-reference/boarding-rest/create-boarding-batch.md) with the `operation` set to `DEACTIVATE_LOCATION`. The following example deactivates a merchant. > [tab] Request > > ```bash theme={null} > curl -X POST https://BOARDING_API_BASE_URL/v1/boarding \ > -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ > -H "Content-Type: application/json" \ > -H "x-acquirer-id: YOUR_ACQUIRER_ID" \ > -d '[ > { > "operation": "DEACTIVATE_LOCATION", > "location": { > "locationId": "LOC001", > "name": "Main Street Store", > "mcc": 5411, > "cardAcceptors": [ > { > "cardAcceptorId": "CA001", > "templateId": 1, > "baseCurrency": 978 > } > ] > } > } > ]' > ``` > [tab] Response > > ```json theme={null} > { > "boardingId": "f47ac10b-58cc-4372-a567-0e02b2c3d479", > "status": "PENDING", > "submittedAt": "2026-09-20T10:30:00.000Z" > } > ``` **Step 2** ### Poll for status Send a `GET` request to [Get boarding status](https://docs.fexco.com/dcc/api-reference/boarding-rest/get-boarding-status.md) to check the deactivation status. > [tab] Request > > ```bash theme={null} > curl https://BOARDING_API_BASE_URL/v1/boarding/f47ac10b-58cc-4372-a567-0e02b2c3d479 \ > -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ > -H "x-acquirer-id: YOUR_ACQUIRER_ID" > ``` > [tab] Response > > ```json theme={null} > { > "boardingId": "f47ac10b-58cc-4372-a567-0e02b2c3d479", > "status": "COMPLETED", > "submittedAt": "2026-09-20T10:30:00.000Z", > "completedAt": "2026-09-20T10:30:12.000Z", > "batchSummary": { > "total": 1, > "completed": 1, > "errors": 0, > "warnings": 0 > } > } > ``` > [!TIP] > > A successful deactivation returns a `status` of `COMPLETED` > with `0` in the `errors` field of the `batchSummary`. If the > deactivation failed, call > [Get boarding summary status](https://docs.fexco.com/dcc/api-reference/boarding-rest/get-boarding-summary.md) > to see the error details for each merchant. ## Deactivate via Boarding File Upload (XML) The Boarding File Upload `deleteMerchant` element deactivates a merchant by merchant ID. Add one `deleteMerchant` element per merchant you want to deactivate. **Step 1** ### Build the deactivation XML Add `deleteMerchant` elements to your Boarding File Upload XML file. Each element needs only the merchant `id` attribute. ```xml theme={null} ``` Follow the [file naming convention](https://docs.fexco.com/dcc/guides/merchant-boarding/board-xml.md#file-naming-convention) described in the XML boarding guide. > [!WARNING] > > Do not include `createMerchant` and `deleteMerchant` elements > for the same merchant in the same file. Submit creation > requests in a separate file first. **Step 2** ### Validate and submit Validate the file against the Boarding File Upload XSD, then upload it to your Fexco SFTP folder. See [Validate an XML file before submission](https://docs.fexco.com/dcc/guides/merchant-boarding/validate-xml.md) for validation instructions. **Step 3** ### Check the response file After processing, Fexco places a response file in your SFTP folder. Each deactivated merchant appears as a row with a `DEACTIVATE` action. > [!TIP] > > Each `DEACTIVATE` row has a `200` status code and no errors. > If any merchants failed, correct the data and resubmit only > the failed merchants in a new Boarding File Upload file. ## Related content * [Reactivate a merchant](https://docs.fexco.com/dcc/guides/merchant-boarding/reactivate-merchant.md): restore a deactivated merchant to active DCC participation. * [Update a boarded merchant](https://docs.fexco.com/dcc/guides/merchant-boarding/update-merchant.md): change a merchant's details without deactivating them. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.