InitialAdapter

Matches transactions submitted with a customer-profile payment token by the adapter and payment method of the transaction that originally registered that token. Shown as "Adapter of Initial Transaction" in the condition catalogue.

Use this condition to keep payments made with a stored customer-profile payment token on infrastructure compatible with where the token was originally registered, without pinning them to one specific connector (use InitialConnector for that).

Parameters

Field	Type	Required	Allowed values
adapterIdentifier	string	yes	The identifier of the adapter of the initial transaction
methodIdentifier	string	yes	The identifier of the payment method of the initial transaction

Example

{
  "constraint": "InitialAdapter",
  "params": {
    "adapterIdentifier": "SimulatorPci",
    "methodIdentifier": "Creditcard"
  }
}

Notes

• Availability: might not be included in your platform package — if this condition is missing from the catalogue returned by List routing constraints, contact your Customer Success Manager to have it activated.
• Available for routing meta-connectors only — not in multi-method routing documents.
• Both parameters must match the token's registration transaction for the condition to match.
• All other transactions — including follow-ups referenced in any other way — evaluate to false and continue in the else branch.