Update Merchant Debit Routing

July 28, 2026 · View on GitHub

Use case

Enables or disables runtime debit/network routing for a merchant.

Authentication

Protected. Send either Authorization: Bearer <jwt_token> or x-api-key: <api_key>. In sandbox, also send x-feature: decision-engine.

For local development, start with:

export BASE_URL=http://localhost:8080
export AUTH_HEADER="Authorization: Bearer <jwt_token>"
# Sandbox only:
# export BASE_URL=https://sandbox.hyperswitch.io
# export FEATURE_HEADER="x-feature: decision-engine"

Request

Method and path: POST /merchant-account/{merchantId}/debit-routing
Parameters:
- merchantId (path, required, string)
Body: Path parameter merchantId; JSON body with enabled boolean.

Example

Enable debit routing

curl --location "$BASE_URL/merchant-account/merchant_demo/debit-routing" \
  --header "$AUTH_HEADER" \
  --header "Content-Type: application/json" \
  --data '{
  "enabled": true
}'

Disable debit routing

curl --location "$BASE_URL/merchant-account/merchant_demo/debit-routing" \
  --header "$AUTH_HEADER" \
  --header "Content-Type: application/json" \
  --data '{
  "enabled": false
}'

Response

{
  "merchant_id": "merchant_demo",
  "debit_routing_enabled": true
}

Notes

If disabled, NTW_BASED_ROUTING and NTW_SR_HYBRID_ROUTING calls should fail with a clear debit-routing-not-enabled error.
This endpoint toggles the feature flag only; detailed fee/config editing is not exposed by the dashboard yet.