Create Auto-Conversion Rule

Create an Auto-Conversion Rule for fiat<->crypto conversions.

Supported Assets:

• USD, USDC, USDT, PYUSD, RLUSD, USDG, USDP, EURC, MXNB Supported Networks:
• Fiat networks: US_ACH, US_FEDWIRE, SWIFT
• Crypto networks: ETHEREUM, POLYGON, BASE, ARBITRUM, AVALANCHE, BNBCHAIN, SOLANA

Validation Rules:

• Must be fiat<->crypto conversion (fiat->fiat and crypto->crypto are NOT supported)
• Idempotency-Key header is required and must be a valid UUID v4
• Source network must match asset type (fiat asset requires fiat network, crypto asset requires crypto network)
• For crypto destination: network is required
• For fiat destination: network will be omitted

Withdrawal Configuration:

• Fiat->Crypto with withdrawal: provide wallet_address (external crypto wallet address)
• Crypto->Fiat with withdrawal: provide external_account_id (bank account ID from external-accounts API)
• Conversion-only (no withdrawal): omit both fields, converted funds remain in customer's account

Idempotency & Webhook Behavior:

• This endpoint creates resources asynchronously. The webhook notification may arrive before the HTTP response returns.
• Use the Idempotency-Key to query the resource status via webhook response, enabling proper idempotency control.
• Recommended flow: Instead of waiting for the HTTP response and then the webhook, clients can use the webhook arrival as the completion signal and query by Idempotency-Key to verify the result.
• This approach prevents "dangling wait" scenarios where clients unnecessarily wait for the HTTP response when the webhook has already confirmed the outcome.

Response & Status:

• The response will have status=PENDING and source_deposit_info=null because deposit info is being prepared asynchronously.
• Once deposit info is ready, the status will transition to ACTIVE and source_deposit_info will contain bank deposit details or crypto wallet address.
• Use the retrieve endpoint or webhook to get the full details when the rule becomes ACTIVE.