Skip to main content
Transaction limits cap how much a customer can move per transaction, per day, and per month. The level of KYC/B verification a customer goes through determines which limits apply.

​
Limits per transaction type

Each transaction type has its own set of limits: onramp, offramp, and transfer. A transaction only counts against the limits of its own type, so an on-ramp never uses up off-ramp or transfer headroom. Each type has a single (per-transaction), daily, and monthly limit.

​
Default limits

*Once a customer finishes Enhanced KYC/KYB, Lumx sets a limit that fits the financial capacity shown in the documents they submitted. Every limit is calculated in the USD equivalent of the transaction, including Pix transactions in BRL.

​
Tracking usage

To track a customer’s limit consumption in real time, pass includeTransactionLimits=true when reading the customer. transactionLimits returns one entry per transaction type. Each entry has the max per-transaction limit and the max, used, and remaining amounts for its daily and monthly limits. Amounts are strings in USD with 2 decimal places.
Request
Response (excerpt)
Before you create a transaction, check the entry that matches its type.

​
Minimum amount

Every off-ramp has to be worth at least the equivalent of USD 40, on every rail. A smaller payout is rejected with 422 and the MINIMUM_AMOUNT_NOT_MET code. The minimum may change.

​
When a transaction exceeds a limit

A transaction that would pass its type’s single, daily, or monthly limit is rejected with 422 and the TRANSACTION_LIMIT_EXCEEDED code. The message names the transaction type and the limit that was hit:
Response
Match on code, not on message. To create the transaction, wait until the daily or monthly window has room, lower the amount, or request higher limits for that transaction type. See Errors for the full error format.

​
Requesting higher limits

To unlock higher transaction limits, the customer needs to go through Enhanced KYC/B verification. That runs directly with the Compliance team.

​
How to request

Limit increase requests are submitted from the Lumx Dashboard, in the customer’s overview page.
  1. Open the customer and click Limit Increase Request.
  2. Choose the transaction type and enter the new per-transaction, daily, and monthly limits being requested.
  3. Upload a supporting document that justifies the new limits. PDF, JPG, JPEG, or PNG, up to 10 MB.
  4. Submit the request.
Partners integrating directly can submit the same request through the API. Follow the Limit Increase Requests guide. Each request targets one transaction type (ONRAMP, OFFRAMP, or TRANSFER), and a customer can have one pending request per type. An approval changes only the limits of that type.

​
Accepted supporting documents

The document has to help Lumx compliance validate the requested limits. Accepted types depend on the customer profile:

​
Review outcomes

Lumx compliance reviews the document and decides the outcome. The request page shows the current status and a timeline of events. Possible outcomes:
  • Approved: the new limits are granted in full and become active immediately.
  • Partially approved: compliance grants limits below what was requested (e.g. 70,000 USD on a 100,000 USD request) based on what the supporting document justifies. The approved limits become active immediately.
  • Rejected: the new limits aren’t granted. The customer stays on its current limits.
  • RFI: compliance needs additional or corrected documentation before deciding. Resubmit through the same flow.

​
Review timeline

More complex cases (large step-ups, unusual document types, or requests that touch enhanced due diligence) can take longer. Target, not a contractual guarantee.