> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://ixopay.ferndocs.com/developer-hub/documentation/reference/features/provisioning/connector-routing/rule-conditions/amount-currency/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# AmountCurrency

Matches transactions whose amount (in a chosen currency) satisfies a numeric comparison against a threshold. Shown as "Amount & Currency" in the condition catalogue.

## Parameters

| Field        | Type   | Required | Allowed values                                                      |
| ------------ | ------ | -------- | ------------------------------------------------------------------- |
| `amount`     | number | yes      | A non-negative number, e.g. `100`, `1500.50`                        |
| `currency`   | string | yes      | Any ISO 4217 code (`EUR`, `USD`, …), or the literal `"Base Amount"` |
| `comparator` | string | yes      | `"="`, `">"`, `">="`, `"<"`, `"<="`                     |

## Example

```json
{
  "constraint": "AmountCurrency",
  "params": {
    "amount": 1000,
    "currency": "EUR",
    "comparator": ">="
  }
}
```

## 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.
* When `currency` is set to `"Base Amount"` (note the space, exact case), the comparison uses the transaction's amount already normalised to the tenant's base currency — no conversion at evaluation time.
* When `currency` is a regular ISO code different from the transaction's currency, the platform converts the transaction amount to the configured currency before comparing. Rules that depend on cross-currency comparison only work when an exchange rate is available.
* `amount` accepts whole and decimal values, e.g. `100` or `1500.50` — send it as a number, not as a string.
* Also available in multi-method routing documents.