Ramps Operational Limits
Ramps Operational Limits
Operational limits control how much value an identity can move within a configured compliance window. Limits apply per person (legal identity), not per user record: a person with multiple user accounts shares the same limit pool.
How Limits Work
- Denominated in a base currency: limit values are stored in a base currency that depends on the user's country (e.g. ARS for Argentina, USDT for most other countries). You can request limits converted to any supported asset using the
assetquery parameter. - Two limit types:
EXCHANGEcovers buy/sell operations and is tracked monthly and yearly.REMITTANCEcovers outbound transfers declaring a third-partyrecipient, and adds a daily window on top. An operation is blocked if it would exceed any applicable window. Declaring asenderdoes not by itself make an operation a remittance: it only selects whose limit is consumed. - Per identity, not per account: limits are tied to the legal ID (
numberId) of the person, not to individual platform user records.
| Situation | Behavior |
|---|---|
| Within every applicable limit window | Operation proceeds |
| Near threshold (10% remaining) | COMPLIANCE_NOTICE webhook fires with CLOSE_TO_OPERATION_LIMIT |
| Limit updated by compliance team | COMPLIANCE_NOTICE webhook fires with OPERATION_LIMIT_UPDATED |
| Limit exceeded | Operation blocked; returns BLOCKED_UIF (400) |
Querying Limits
GET /crypto/v2/limits/:numberId
GET /crypto/v2/limits/:numberId?asset=USDT
GET /crypto/v2/limits?legalIdNationality=ARG&legalId=20300000003
GET /crypto/v2/limits?legalIdNationality=ARG&legalId=20300000003&asset=USDT
Returns the current limit state for an identity. Two lookup variants are supported and return the same response shape:
- By Manteca
numberId: path parameter. Use under the End-user model, where the partner holds a Manteca user record per end-user. - By legal identity:
legalIdNationality+legalIdas query parameters. Use under the Principal Accounts model, where the partner only holds the end-user's legal identity (the value declared insender.legalId).
Query Parameters
| Parameter | Required | Description |
|---|---|---|
legalIdNationality | Conditional | ISO country code of the legal identity (e.g. ARG, BRA, MEX). Required when querying by legal identity instead of numberId. Must be sent together with legalId. |
legalId | Conditional | National ID or tax number of the end-user (matches the value used in sender.legalId). Required when querying by legal identity instead of numberId. Must be sent together with legalIdNationality. |
asset | No | Convert limit amounts to this asset (e.g. USDT, BTC, ETH). If omitted, amounts are returned in the user's native limit currency. Uses live market prices for conversion. |
Response
The endpoint returns an array with one entry per limit type held by the identity.
[
{
"exchangeCountry": "ARG",
"type": "EXCHANGE",
"asset": "ARS",
"yearlyLimit": "35000000",
"availableYearlyLimit": "34500000",
"monthlyLimit": "25000000",
"availableMonthlyLimit": "24800000"
},
{
"exchangeCountry": "ARG",
"type": "REMITTANCE",
"asset": "USDT",
"yearlyLimit": "40000",
"availableYearlyLimit": "38800",
"monthlyLimit": "10000",
"availableMonthlyLimit": "9350",
"dailyLimit": "2500",
"availableDailyLimit": "1850"
}
]| Field | Description |
|---|---|
exchangeCountry | ISO country code for the limit jurisdiction |
type | Limit type (EXCHANGE or REMITTANCE) |
asset | Denomination asset: matches the asset query parameter if provided, otherwise the user's native limit currency |
yearlyLimit | Total allowed per year |
availableYearlyLimit | Remaining yearly allowance |
monthlyLimit | Total allowed per month |
availableMonthlyLimit | Remaining monthly allowance |
dailyLimit | Total allowed per day in a rolling 24h window. REMITTANCE only: not returned for EXCHANGE. |
availableDailyLimit | Remaining daily allowance in the current rolling window. REMITTANCE only: not returned for EXCHANGE. |
Note: When using
asset, amounts are converted using live market prices at the time of the request. The same limit queried at different times may return slightly different values as prices fluctuate.
Compliance Webhooks
The platform emits COMPLIANCE_NOTICE events for limit-related state changes.
| Event | Trigger |
|---|---|
CLOSE_TO_OPERATION_LIMIT | Identity has 10% or less of a limit remaining |
OPERATION_LIMIT_UPDATED | Compliance team adjusted the identity's limit |
Subscribe to COMPLIANCE_NOTICE to proactively surface limit proximity to users before operations are blocked.
When an Operation Is Blocked
An operation that exceeds a limit returns HTTP 400 with this body:
{
"internalStatus": "BLOCKED_UIF",
"message": "Needs fund origin."
}Do not retry on BLOCKED_UIF: the block persists until the limit window resets (rolling 24h for daily, calendar cycle for monthly and yearly), the user uploads fund-origin documentation, or the compliance team raises the limit. See Raise Limits.
BLOCKED_UIFis not the same asOPERATION_BLOCKED.OPERATION_BLOCKED(409) means the asset pair or the operation itself is disabled by platform policy, and is unrelated to the identity's limits.
Implementation Requirements
- Parse and persist
internalStatusfrom every non-2xx response. - Show clear user-facing messaging for blocked operations: do not surface raw error codes.
- Avoid blind retries when a limit is exceeded.
- Route blocked cases to your review or escalation path.
Default Limit Ranges
Limits are assigned automatically during onboarding and depend on the user's country, compliance level, and risk profile. The following table shows approximate ranges across all supported jurisdictions.
Exchange Limits
| Region | Currency | Monthly | Yearly |
|---|---|---|---|
| Argentina | ARS | 8,000,000 to 25,000,000 | 20,000,000 to 35,000,000 |
| LATAM (non-Argentina) | USD | 1,000 to 5,000 | 10,000 to 30,000 |
Note: Limits for non-Argentina countries are expressed in USD equivalent. Argentina limits are in ARS. Users with higher compliance levels or additional documentation may receive limits at the upper end of these ranges. Conversely, high-risk profiles or users without identity documentation may receive lower limits.
Outbound Limits
Outbound limits are the REMITTANCE limits. They apply to payouts and ramp-offs that declare a third-party recipient, and they are consumed from the sender's identity. They are denominated in USDT.
They are the same for every country:
| Daily | Monthly | Yearly |
|---|---|---|
| 2,500 | 10,000 | 40,000 |
Note: Outbound limits are enforced on a rolling-window basis for daily limits and calendar-based for monthly and yearly limits.
Raising Limits
Use Raise Limits for the escalation and reprocessing sequence when a user needs a higher operational threshold.
Related pages
- Virtual Accounts Operational Limits: the
VIRTUAL_ACCOUNTSlimit applied to deposits and transfers through Virtual Accounts. It is a separate pool: it does not consume theEXCHANGEorREMITTANCElimits described here, and vice versa.
Updated 1 day ago