Update MIT cascade control settings for an account.
Controls how MIT retries cascade across processors:
- cascading_enabled: Enable cascading to fallback processors when last successful is unavailable
- fallback_processor_1_id: ID of the first fallback processor
- fallback_processor_2_id: ID of the second fallback processor
Request
This endpoint expects an object.
cascading_enabledboolean or nullOptional
Enable cascading to fallback processors when last successful is unavailable
fallback_processor_1_idstring or nullOptional
ID of first fallback processor
fallback_processor_2_idstring or nullOptional
ID of second fallback processor
update_default_pm_on_fallbackboolean or nullOptional
Whether a successful fallback re-pins the default payment method.
max_fallback_payment_methodsinteger or nullOptional0-10
Maximum fallback cards to try after the primary. Must be 0-10.
Response
Successful Response
cascading_enabledboolean or nullOptionalDefaults to false
Enable cascading to fallback processors when last successful is unavailable
fallback_processor_1_idstring or nullOptional
ID of first fallback processor
fallback_processor_2_idstring or nullOptional
ID of second fallback processor
update_default_pm_on_fallbackbooleanOptionalDefaults to false
When True, a successful fallback card re-pins both the subscription and invoice default payment method to that card. Default False (the merchant’s chosen default is preserved across fallback renewals).
max_fallback_payment_methodsintegerOptional0-10Defaults to 1
Maximum number of fallback cards to try after the primary default card. 0 = no cascade (primary only). Default 1. Capped at 10 to bound the number of cards a single collection attempt walks through — this includes currency-routing pre-flights (which reach no processor) as well as actual processor charge attempts.