User Blocks & Restrictions

Users may be blocked from operating on the platform due to compliance rules or operational restrictions. This guide explains block types, how to detect them, and what actions are available.


Checking blocked users

Use GET /v2/blocks to retrieve a paginated list of the blocked legalIds that apply to your company: blocks applied by Manteca and merchants your company blocked itself. Blocks created by other companies are never listed.

curl --request GET \
  --url 'https://sandbox.manteca.dev/crypto/v2/blocks?page=1&pageSize=20' \
  --header 'accept: application/json' \
  --header 'md-api-key: YOUR_MD_API_KEY'
{
  "totalCount": 3,
  "pageCount": 3,
  "pageSize": 20,
  "page": 1,
  "lastPage": 1,
  "data": [
    "20330624087",
    "27300000008",
    "18405226745"
  ]
}

You can also check a user's status via GET /v2/users/:userAnyId. A blocked user will have status: "INACTIVE".


Types of blocks

Compliance blocks

Triggered automatically when a user fails compliance checks or exceeds risk thresholds.

Block typeCauseResolution
Security validation failureUser matched a sanctions list, watchlist, or other regulated sourceContact Manteca support
Identity verification failureRepeated failed identity validationsResubmit documentation or contact support
Suspicious activityAbnormal patterns detected by compliance monitoringContact Manteca support

Operational blocks

Triggered by specific operating patterns.

Block typeCauseResolution
Micro-operationsUser performed many small transactions in rapid succession, which may indicate structuringContact Manteca support
Limit exceededUser exceeded their transactional limitsWait for the limit window to reset or contact Manteca support to review limits

What happens when a user is blocked

When a user is blocked:

  • Their status changes to INACTIVE
  • All operations are rejected — orders, withdrawals, deposits, and synthetic operations will fail
  • Existing balances are preserved but cannot be moved
  • A USER_STATUS_UPDATE or USER_ONBOARDING_UPDATE webhook may fire with status: "INACTIVE"

Blocking merchants

If your fraud or compliance team detects unusual activity on a merchant, you can block it yourself as a preventive measure. While the merchant is blocked, QR payment locks from your company towards it are rejected with MERCHANT_BLOCKED.

The block only applies to your company: other Manteca clients can keep paying that merchant, and blocks applied by Manteca's compliance team are not affected.

Use POST /v2/blocks with the merchant's tax ID (paymentRecipientLegalId in the payment lock) and its country:

curl --request POST   --url 'https://sandbox.manteca.dev/crypto/v2/blocks'   --header 'content-type: application/json'   --header 'md-api-key: YOUR_MD_API_KEY'   --data '{
    "legalId": "30712345678",
    "exchangeCountry": "ARG",
    "reason": "Unusual activity detected by our fraud team"
  }'

To lift it, use DELETE /v2/blocks/:legalId:

curl --request DELETE   --url 'https://sandbox.manteca.dev/crypto/v2/blocks/30712345678'   --header 'md-api-key: YOUR_MD_API_KEY'

Both endpoints return 204 No Content. DELETE returns 404 when your company has no block for that legalId, including when the merchant is only blocked by Manteca.

Merchants you block also show up in GET /v2/blocks, mixed with the blocks applied by Manteca. The list does not say who applied each block, and only the ones your company created can be lifted with DELETE.

The block is checked when a payment lock is created. Locks created before the block are not re-checked.


What you can do vs. what requires Manteca support

ActionSelf-serviceRequires Manteca support
Check if a user is blockedGET /v2/blocks—
Check user statusGET /v2/users/:userAnyId—
Block or unblock a merchant for your companyPOST /v2/blocks, DELETE /v2/blocks/:legalId—
Resubmit rejected KYC docsResubmission flow—
Unblock a user—Contact Manteca support with context
Understand block reason—Contact Manteca support
Request limit increase—Contact Manteca support

Blocks applied for compliance reasons (sanctions, suspicious activity) can only be lifted by Manteca's compliance team after review. There is no API endpoint to unblock users; DELETE /v2/blocks/:legalId only lifts merchant blocks your company created.


Monitoring limits

To proactively avoid limit-related blocks, use the following endpoints:

Limit webhooks

Configure the COMPLIANCE_NOTICE webhook to receive proactive alerts:

TypeMeaning
CLOSE_TO_OPERATION_LIMITUser is approaching their limit — consider pausing operations or notifying the user
OPERATION_LIMIT_UPDATEDUser's limits were recalculated (e.g., after a limit period reset)

Frequently asked questions

Can I unblock a user via API?
No. User blocks can only be removed by Manteca's compliance team. Contact support with the user's legalId and the context of the block. The only blocks you can lift via API are the merchant blocks your company created with POST /v2/blocks.

How quickly are blocks applied?
Compliance blocks are applied in real time. If a security validation fails during onboarding, the user is blocked immediately.

Will I be notified when a user is blocked?
Yes, if you have configured the USER_ONBOARDING_UPDATE or USER_STATUS_UPDATE webhook. The user's status will change to INACTIVE.

Can a blocked user's balance be recovered?
Balances are preserved. Once the block is lifted, the user can resume operations. For permanent blocks (e.g., sanctions matches), Manteca's compliance team will coordinate the resolution.

What is a "micro-operations" block?
This block triggers when a user performs many small transactions in a short period. This pattern is associated with transaction structuring (attempting to avoid reporting thresholds). Contact support to review and resolve.


Related pages


Did this page help you?