Skip to main content

Set multi-method routing

POST 
/setConnectorMultiMethodRouting/:connectorGuid

Sets the per-payment-method routing configuration of a multi-method meta-connector.

For each payment method you can configure an availability rule tree (deciding whether the method is offered to the customer, with enable / disable action leaves) and a routing rule tree (deciding which connector processes the transaction, with route leaves — the same shape as in the routing document of a routing meta-connector).

The document is explicit-only: methods omitted from the methods array are preserved untouched. To turn a method off, send its block with disabled: true. Each method must already be linked to the meta-connector — link methods via Connector – Create or Connector – Update before configuring their routing here. Method identifiers are matched case-insensitively; responses return the canonical identifier (for example Creditcard, DirectDebit).

For a method block that is present, the trees you send fully replace that method's existing trees. The response echoes the stored configuration with all server-assigned rule ids populated, and the endpoint is idempotent.

Condition subset

Multi-method routing accepts a fixed subset of the condition catalogue: CustomerCountry, CustomerIpCountry, Currency, AmountCurrency, RiskScore and ExtraData. Other conditions are rejected with error code 1011 — including conditions that a rule tree authored in the admin interface may contain; adjust such documents fetched via Get multi-method routing before resubmitting them.

What the API validates

The document is checked for structural correctness, known conditions with well-formed parameters, tenant-level condition availability, and valid connector references. The API does not assess whether the resulting routing strategy behaves as you intend — see Validation and its limits. Test routing changes against your sandbox environment before applying them to production.

Request​

Responses​

The stored multi-method routing configuration, echoing the submitted document with all server-assigned rule ids populated. Methods not included in the request are returned with their unchanged configuration.