Check the allowed transaction range for a currency and country before you generate a quote or execute a transaction.

⏱️
Time to integrate: Most teams can validate this endpoint in under 5 minutes once they know the currency, country, and payout corridor they intend to use.

What this endpoint does

Use this endpoint to retrieve the transaction limits for a specific currency and country combination.

This endpoint helps you understand the allowed minimum and maximum transaction amounts for the payout corridor you plan to use.

When to call this endpoint

Call this endpoint when you need to:

validate that a requested amount is in range before quoting
prevent avoidable transaction failures caused by corridor limits
enforce amount validation in your UI or backend workflow
confirm operating constraints for a new market, country, or currency flow

For most teams, this endpoint should be used before quote generation whenever the transaction amount may vary by corridor.

Why transaction limits matter

Transaction limits are a simple but important pre-validation control.

Checking limits before quote generation helps your team:

reject invalid amounts earlier in the flow
avoid unnecessary quote requests
give operators or end users immediate feedback
reduce support tickets caused by amount-related failures

For enterprise teams, this endpoint is also useful when defining approval thresholds, payout policies, and corridor-level controls.

Authentication

Send your API key in the x-api-key header on every request.

Item	Value
Authentication method	API key
Required header	`x-api-key`
Rate limit scope	Per API key

Recommended workflow

Use this endpoint in the transaction preparation sequence:

Fetch organization accounts.
Check verification status.
Create a beneficiary.
Add a beneficiary account.
Resolve bank account details if required.
Check transaction limits for the intended currency and country.
Check source currency balance.
Generate a quote.
Execute the transaction.

What data to prepare before checking limits

Before sending the request, confirm the corridor context your transaction requires.

At minimum, your team should confirm:

the transaction currency
the destination country or corridor
the amount you intend to send or price
the payout method or routing context if your internal flow depends on it

⚠️
Needs confirmation: Exact request parameters, whether amount is part of the request, how country must be formatted, and whether provider or network also affect limits should be confirmed in the API definition.

How to use the response

Use the returned limits to decide whether your flow can continue.

If the amount is within the allowed range

You can proceed to:

generate a quote
continue internal approval checks
execute the transaction after final validation

If the amount is below the minimum or above the maximum

You should:

stop the current transaction request
present the allowed range to the operator or end user if appropriate
adjust the amount or choose another allowed flow
retry only after the transaction fits the corridor constraints

Common use cases

Pre-quote validation

Check limits before quote generation so your application can reject unsupported amounts immediately.

Product and UI validation

Use the result to validate user-entered amounts in operational tools or partner-facing workflows.

Corridor rollout planning

Use this endpoint when launching a new currency or country flow so engineering and operations teams understand the expected operating range.

Production notes

Before using this endpoint in production:

Define whether your application checks limits dynamically or relies on cached values.
Revalidate limits if your transaction details change before execution.
Log limit checks that influence transaction approval decisions.
Make sure product, operations, and support teams understand how amount validation is enforced.

For high-volume systems, validate limits early in the request lifecycle so you avoid wasted quote and execution attempts.

Common failure cases

Authentication fails

Check these items first:

the x-api-key header is present
the API key belongs to the intended environment
the base URL is correct

The returned range does not match expectations

If the response looks unexpected:

confirm the currency is correct
confirm the destination country is correct
verify you are checking the intended environment
review whether the payout rail or route differs from your assumption

Quote generation fails even though limits looked valid

If a later quote request still fails:

verify the final amount still matches what you checked
verify the route, provider, or destination details did not change
verify the source account and payout destination are valid
review any corridor-specific validation beyond simple amount limits

Frequent limit checks cause unnecessary load

Because rate limits are enforced per API key:

avoid repeated checks for identical read-only scenarios when caching is acceptable
refresh limits when the amount, country, or currency changes materially
separate batch pre-validation from user-triggered requests when possible

⚠️
Needs confirmation: Exact response fields, whether limits are static or may change dynamically, error codes, and any corridor-specific limit semantics should be confirmed from the API schema and backend behavior.

Enterprise implementation notes

Access control

Allow product, backend, and operations systems to read limits where needed, but keep production API key usage inside trusted backend services.

Auditability

Record:

currency checked
country checked
returned limit range used in a decision
request timestamp
related quote or transaction reference when applicable

Operational controls

Use transaction limits as one input in broader policy controls such as maker-checker review, high-value approval, and market-specific payout restrictions.

Troubleshooting checklist

Use this checklist if amount validation is blocking your flow:

Confirm authentication with x-api-key.
Confirm the currency is correct.
Confirm the country is correct.
Compare the requested amount with the returned range.
Recheck limits if the route or transaction details change.
Continue to quote generation only after the amount is valid.

Recommended next endpoints

After you check transaction limits, continue with:

Related pages

Generate Quote

Generate the quote only after the requested amount fits the allowed corridor range.

Get Currency Balance

Confirm the source account is funded after you know the amount is allowed.

Execute Transaction

Finalize the transaction after limit, balance, destination, and quote checks are complete.