Ramps Raise limits

Ramps Raise limits

Raise limits is the operational path used when a transaction is blocked by current limit policy.

Limits are per-person (per numberId). Each user has their own monthly and yearly limits independent of other users on your platform.


Check current limits

Before initiating a raise, retrieve the user's current limit state:

GET /v2/limits/:numberId

Response includes available limits by type and asset:

{
  "type": "REMITTANCE",
  "asset": "USDT",
  "monthlyLimit": "1000",
  "availableMonthlyLimit": "650",
  "yearlyLimit": "1000",
  "availableYearlyLimit": "850"
}

Monitor availableMonthlyLimit and availableYearlyLimit. When either approaches zero, prompt the user to initiate a raise before the next operation is blocked.


COMPLIANCE_NOTICE webhook

Manteca fires a COMPLIANCE_NOTICE webhook when a user's available limit drops to 10% or less of the period limit. Use this signal to proactively surface the raise flow in your UX, before the user hits a hard block.


Practical sequence

  1. Detect the limit block from the operation response.
  2. Collect the proof of fund origin, see what counts below.
  3. Upload it with POST /crypto/v2/documentations/uploadUrl, see below.
  4. Track the review, see Track the review below, and wait for the updated limit.
  5. Retry the operation with the same traceability identifiers.

Additional fund origin documentation may be required during the review process depending on the amount and jurisdiction.


What counts as proof of fund origin

The document has to show where the user's money comes from, carry their name, and state an amount and the period it covers. Any of these works:

  • The user's last three payslips.
  • Their most recent income tax return.
  • A statement of income issued and signed by a certified accountant.
  • Evidence of a specific inflow: the sale of a property or of securities, or a loan received.

These are not accepted on their own, because they identify the user or their tax status without evidencing income:

  • An identity document.
  • A bank statement.
  • A certificate of tax registration.

Send one file per upload. If the evidence spans several documents (three payslips, for instance), merge them into a single file first: a partial upload is reviewed as what it is and rejected.

The list is deliberately generic. Local equivalents of these documents are accepted, and if you are unsure whether a specific one qualifies in your market, ask your integration contact before the user uploads it.


Submit fund-origin documentation

Upload the document so the compliance team can review it and raise the user's EXCHANGE limit. The raise applies to the yearly window. Each document is uploaded in two steps: request a short-lived pre-signed URL, then PUT the file straight to it.

Step 1: Get the upload URL

Call POST /crypto/v2/documentations/uploadUrl with docType: "FUNDS". The response returns a pre-signed url.

curl -X POST https://sandbox.manteca.dev/crypto/v2/documentations/uploadUrl \
  -H "md-api-key: $MD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
      "associatedSubId": "100037043",
      "docType": "FUNDS",
      "fileName": "proof-of-funds.pdf",
      "extension": "pdf"
  }'
{ "url": "https://manteca-documentation.s3.amazonaws.com/upload-target" }

Step 2: Upload the file to the signed URL

PUT the raw file binary directly to the url from Step 1. Do not include the md-api-key header: this request goes straight to the storage URL. Set Content-Type to match the file format.

curl -X PUT 'SIGNED_URL_FROM_STEP_1' \
  -H "Content-Type: application/pdf" \
  --data-binary '@/path/to/proof-of-funds.pdf'
🚧

The signed URL expires in 90 seconds, so upload immediately after requesting it.

After the upload, the file content is checked against the extension declared in Step 1 (for example, a .pdf must actually be a PDF). If it doesn't match, the file is deleted and no document is created, even though the PUT returned 200. Request a new signed URL and upload a file whose content matches its extension.

The document is reviewed asynchronously. When the compliance team raises the limit, a COMPLIANCE_NOTICE webhook fires with OPERATION_LIMIT_UPDATED.


Track the review

The compliance team reviews each document and decides the new limit based on what it evidences: the user does not request a specific amount.

To follow the review, list the user's fund-origin documents with GET /crypto/v2/documentations, or fetch one by its id with GET /crypto/v2/documentations/{documentationAnyId}:

curl -G https://sandbox.manteca.dev/crypto/v2/documentations \
  -H "md-api-key: $MD_API_KEY" \
  --data-urlencode "associatedSubId=100037043" \
  --data-urlencode "docType=FUNDS"
{
  "totalCount": 1,
  "pageCount": 1,
  "pageSize": 20,
  "page": 1,
  "lastPage": true,
  "data": [
    {
      "id": "665f1a2b3c4d5e6f7a8b9c0d",
      "associatedSubId": "100037043",
      "docType": "FUNDS",
      "status": "REJECTED",
      "details": { "amount": 0 },
      "seen": true,
      "valid": false,
      "comment": "The document does not show the user's name.",
      "history": [
        { "newStatus": "PENDING", "date": "2026-11-04T13:02:11.000Z" },
        { "newStatus": "REJECTED", "date": "2026-11-05T15:20:00.000Z" }
      ],
      "platform": "CRIPTO",
      "creationTime": "2026-11-04T13:02:11.000Z",
      "updatedAt": "2026-11-05T15:20:00.000Z"
    }
  ]
}
statusMeaning
PENDINGUploaded, waiting for review.
VALIDATEDApproved. details.amount is the approved amount, in the user's limit currency, and the limit is raised accordingly.
REJECTEDNot accepted, and details.amount stays at 0. comment explains why: collect a new document and upload it.

Documents are returned newest first, so the first FUNDS entry is the latest submission.


Good practices

  • Persist original payload and rejection context.
  • Keep client UX explicit while review is pending.
  • Do not retry automatically until updated state is confirmed.
  • Use GET /v2/limits/:numberId to poll for limit state changes, and GET /crypto/v2/documentations to know whether a document was rejected.

Related pages


Did this page help you?