> ## 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. # Update a boarded merchant > Change a merchant's name, address, terminals, or currency configuration using the Boarding File Upload XML file. After you board a merchant, you may need to change their details, such as updating a name, adding a terminal, or modifying the currency configuration. Merchant updates are only available through the XML Boarding File Upload method. The Boarding API methods do not support updates. > [!NOTE] > > The Boarding API does not support merchant > updates. To update a boarded merchant, contact your Fexco Key > Account Manager (KAM) to request changes on your behalf, or use > the XML method described on this page. If you do not have SFTP > set up, you must complete the > [SFTP security setup](https://docs.fexco.com/dcc/guides/getting-started/security-setup.md#secure-file-transfer-sftp) > before you can submit update files via XML. This guide covers how to build an `updateMerchant` XML element, submit it via SFTP, and verify the update was applied. ## Before you start You need the following before you can update a boarded merchant. * SFTP credentials and IP whitelisting configured through [security setup](https://docs.fexco.com/dcc/guides/getting-started/security-setup.md#secure-file-transfer-sftp). * A merchant that has already been boarded. You need the merchant's ID (`id` attribute) from the original boarding request. See [Board merchants via XML](https://docs.fexco.com/dcc/guides/merchant-boarding/board-xml.md) or [Board merchants via the Boarding API](https://docs.fexco.com/dcc/guides/merchant-boarding/board-api.md). > [!WARNING] > > Submit files that create merchants before files that update the > same merchants. The Boarding File Upload utility does not check file order. ## Merchant fields you can update Not all merchant fields can be updated through Boarding File Upload. The following table lists the fields that the `updateMerchant` element supports. | Element | Description | | :- | :- | | `newName` | Updates the merchant name. | | `newAddress` | Updates the merchant address. | | `newMCC` | Updates the Merchant Category Code. | | `newDistributionType` | Updates the point-of-sale type. One of: `Terminal`, `Integrated`, `eCommerce`, `Other`. | | `newCommissionSplit` | Changes commission percentages between acquirer and merchant. | | `addTerminal` | Adds a new terminal or ATM. | | `deleteTerminal` | Removes an existing terminal by its ID. | | `deleteMerchantOriginator` | Deactivates an existing merchant originator. Pass the originator tag (MID) as the element text. You can include multiple elements to delete more than one originator in a single update. See [Delete an originator](#delete-an-originator) for details. | > [!NOTE] > > The merchant ID (`id` attribute) cannot be changed. It is used > only to identify which merchant to update. For the full list of elements, attributes, and validation rules, see [XML Boarding File Upload format](https://docs.fexco.com/dcc/developer-resources/file-formats/xml-boarding-file-upload.md). ## Build and submit the update file Follow the steps below to build your update file, submit it, and verify the results. **Step 1** ### Build the update XML Add one or more `updateMerchant` elements inside the `acquirer` element of your Boarding File Upload XML file. Each `updateMerchant` element targets a single merchant by its `id` attribute and contains only the fields you want to change. The following example updates a merchant's name and address, swaps a terminal, and adds a new currency configuration. > [!NOTE] > > The `baseCurrency` element uses an ISO 4217 numeric currency > code instead of a three-letter code. For example, `978` is > EUR and `826` is GBP. ```xml theme={null} Merchant One Updated 34 Oak Park Tralee Kerry IE 1325 Integrated Reception desk AB123456 0123456780003 ``` You only need to include the fields you want to change. For example, to update just the merchant name: ```xml theme={null} Merchant One Updated ``` To change the commission split, include a `newCommissionSplit` element with both `acquirerPercent` and `merchantPercent`. Both fields are required and their values must add up to the total configured for the template. If the values do not add up, the update is rejected with error code `22`. ```xml theme={null} 2.845 0.155 ``` **Step 2** ### Validate the file Validate your XML file against the Boarding File Upload XSD before submitting. Structural or syntax errors cause the entire file to be rejected. See [Validate an XML file before submission](https://docs.fexco.com/dcc/guides/merchant-boarding/validate-xml.md) for instructions. **Step 3** ### Name and submit the file Name the file using the Boarding File Upload naming convention and upload it to your designated SFTP directory: ``` MBUXXXYYYYMMDD.hhmmss.XML ``` Replace `XXX` with your three-letter merchant identifier (assigned by Fexco), and set the timestamp to the file creation time. Fexco picks up the file automatically at a scheduled time. **Step 4** ### Check the response file After processing, Fexco places a response file in your SFTP directory. The response file lists each merchant operation with a status code, warnings, and errors. Look for rows where the `Action` column is `UPDATE`. A `Status Code` of `200` means the update was accepted. Review any warnings or errors. For a full list of error and warning codes, see [Troubleshoot boarding errors](https://docs.fexco.com/dcc/guides/merchant-boarding/troubleshoot.md). > [!TIP] > > Every `UPDATE` row in the response file has a `Status Code` > of `200` and no entries in the error list. If any updates > failed, correct the data and resubmit only the failed > merchants in a new Boarding File Upload file. ## Delete an originator A merchant originator represents a specific base currency and card scheme configuration linked to the merchant. To delete an originator, include a `deleteMerchantOriginator` element inside `updateMerchant` with the originator tag (MID) as the text content: ```xml theme={null} 0123456780003 ``` Deletion is a soft delete — the originator is deactivated rather than removed from the system. If you attempt to delete an originator that does not exist on the merchant, the response file returns error code `10`. If the originator was already deleted, the response returns warning code `105`. > [!NOTE] > > You can delete multiple originators in a single update by > including multiple `deleteMerchantOriginator` elements. To add a > new originator or replace an existing one, contact your Fexco Key > Account Manager (KAM). ## Fields that require Fexco support to change Some merchant fields cannot be changed through the Boarding File Upload utility. For these, contact the Fexco operations team. For the full list of which fields can and cannot be updated, see [XML Boarding File Upload format](https://docs.fexco.com/dcc/developer-resources/file-formats/xml-boarding-file-upload.md). ## Next steps * [Deactivate a merchant](https://docs.fexco.com/dcc/guides/merchant-boarding/deactivate-merchant.md): remove a merchant from active DCC participation. * [Reactivate a merchant](https://docs.fexco.com/dcc/guides/merchant-boarding/reactivate-merchant.md): restore a deactivated merchant. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.