# Authorized converters

Source: https://docs.settlemint.com/docs/operators/asset-servicing/authorized-converters
Add or remove converter addresses for conversion-minter assets before running governed conversion workflows.



Authorized converters are conversion feature addresses that a conversion-minter asset is allowed to use. Add a converter when a programme needs a governed route from a source asset into its target asset. Remove it when the route is retired, replaced, or no longer approved.

Use this guide when the asset already has conversion behaviour configured. It covers the converter list only, not trigger setup or holder conversion. For the wider feature model, read [Conversion](/docs/architects/components/token-features/conversion). For mandatory holder conversion, use [Forced conversion](/docs/operators/asset-servicing/forced-conversion).

<Callout type="note" title="Converter management is an asset-servicing control">
  Adding a converter does not create a trigger, move holder balances, or approve the business event. It only updates
  which conversion feature address the asset can use for its configured workflow.
</Callout>

## Before you start [#before-you-start]

Confirm these points before changing the converter list:

* The target asset has the conversion-minter feature attached.
* The converter address belongs to a contract that exposes the conversion feature interface.
* The operator has the governance authority required to update the asset.
* The approval record names the asset, converter address, reason for the change, and expected route.
* Wallet verification is available for the submitting operator.

## How the check works [#how-the-check-works]

The Asset Console checks a converter address before it submits the add workflow. If the address is not a conversion feature contract, the console stops the submission.

API integrations should call the probe endpoint before sending an add request. A direct add request queues the update and relies on the contract to reject an invalid converter.

<Mermaid
  chart="`flowchart TB
Start[&#x22;Operator chooses converter&#x22;] --> Probe[&#x22;Check converter interface&#x22;]
Probe --> Valid{Valid conversion feature?}
Valid -->|No| Stop[&#x22;Stop and choose another address&#x22;]
Valid -->|Yes| Verify[&#x22;Wallet verification&#x22;]
Verify --> Submit[&#x22;Submit add authorized converter&#x22;]
Submit --> Record[&#x22;Record result and approval evidence&#x22;]

style Start fill:#5fc9bf,stroke:#3a9d96,stroke-width:2px,color:#fff
style Probe fill:#6ba4d4,stroke:#4a7ba8,stroke-width:2px,color:#fff
style Valid fill:#6ba4d4,stroke:#4a7ba8,stroke-width:2px,color:#fff
style Submit fill:#8571d9,stroke:#654bad,stroke-width:2px,color:#fff
style Record fill:#b661d9,stroke:#8a3fb3,stroke-width:2px,color:#fff
`"
/>

## Add an authorized converter [#add-an-authorized-converter]

<Steps>
  <Step>
    ### Open the conversion feature page [#open-the-conversion-feature-page]

    Open the asset detail page, then open the Conversion feature page. Confirm that the conversion-minter details are visible for the target asset.
  </Step>

  <Step>
    ### Start the add workflow [#start-the-add-workflow]

    Choose Add Converter. Enter the converter address that should be allowed for the asset.
  </Step>

  <Step>
    ### Review the converter check [#review-the-converter-check]

    DALP checks whether the address exposes the expected conversion feature interface. If the check fails, stop and verify that you selected the conversion feature address for the intended route.
  </Step>

  <Step>
    ### Submit with wallet verification [#submit-with-wallet-verification]

    Review the confirmation screen, complete wallet verification, and submit the update. Keep the transaction result with the approval record for the converter change.
  </Step>
</Steps>

## Remove an authorized converter [#remove-an-authorized-converter]

Remove a converter when the conversion route is no longer approved, the converter has been replaced, or the operating policy requires the asset to stop using that route.

<Steps>
  <Step>
    ### Open the conversion feature page [#open-the-conversion-feature-page-1]

    Open the asset detail page and review the current authorized converter list on the Conversion feature page.
  </Step>

  <Step>
    ### Start the remove workflow [#start-the-remove-workflow]

    Choose Remove Converter, then enter the converter address to remove.
  </Step>

  <Step>
    ### Verify the operating impact [#verify-the-operating-impact]

    Before submission, confirm that no open conversion process depends on the converter address you are removing. Removing a converter can stop future conversion requests that rely on that route.
  </Step>

  <Step>
    ### Submit and record the result [#submit-and-record-the-result]

    Complete wallet verification, submit the update, and retain the transaction result with the reason for removal.
  </Step>
</Steps>

## API integration [#api-integration]

Use the API path when an operator system manages converters instead of the Asset Console:

```http
GET /api/v2/tokens/{tokenAddress}/conversion-feature-probe?converterAddress={converterAddress}
POST /api/v2/tokens/{tokenAddress}/features/conversion-minter/authorized-converters
DELETE /api/v2/tokens/{tokenAddress}/features/conversion-minter/authorized-converters
```

Use the probe response before submitting an add request. Add and remove requests use the target token address in the path and the converter address in the request body.

## Troubleshooting [#troubleshooting]

| Issue                            | Check                                                                                                  |
| -------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Add workflow rejects the address | Confirm the address is a conversion feature contract, not a token address or unrelated contract.       |
| Workflow is not visible          | Confirm the asset has conversion-minter behaviour attached and that your operator has governance role. |
| Wallet verification fails        | Complete the required verification method before retrying the update.                                  |
| Conversion later fails           | Confirm the relevant trigger, conversion window, holder balance, and converter list are still valid.   |

## Related guides [#related-guides]

* [Conversion](/docs/architects/components/token-features/conversion) for roles, triggers, conversion windows, and events
* [Forced conversion](/docs/operators/asset-servicing/forced-conversion) for mandatory conversion workflows
* [Token lifecycle API integration](/docs/developers/api-integration/tokens/token-lifecycle) for conversion endpoints
* [Per-asset RBAC](/docs/architects/components/asset-contracts/rbac) for governance role context