> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://ixopay.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# InitialConnector

Matches transactions whose initial-transaction connector equals the configured GUID — used for follow-up transactions (e.g. captures, refunds, recurring) that should re-route through the same connector that processed the original transaction. Shown as "Connector of Initial Transaction" in the condition catalogue.

## Parameters

| Field           | Type   | Required | Allowed values                                               |
| --------------- | ------ | -------- | ------------------------------------------------------------ |
| `connectorGuid` | string | yes      | GUID of one of your merchant's regular (non-meta) connectors |

## Example

```json
{
  "constraint": "InitialConnector",
  "params": { "connectorGuid": "CO-1234-5678-9012-3456-7890-1234" }
}
```

## Notes

* **Availability:** might not be included in your platform package — if this condition is missing from the catalogue returned by [List routing constraints](https://documentation.ixopay.com/api/provisioning/list-routing-constraints), contact your Customer Success Manager to have it activated.
* Applies only to transactions that have a recorded initial-transaction connector. New (root) transactions evaluate to false and evaluation continues in the `else` branch.
* Available for routing meta-connectors only — not in multi-method routing documents.