Skip to main content
Every user operates under a compliance tier. A tier defines how much the user can move: per transaction, per day, per month, and so on. Tiers are configured for your company by Kravata; you read them with the API. A user has one tier assignment per currency. For example, a user can be in tier 1 for COP and in tier 2 for USD.

1. Get the tiers and their limits

Call Get Tier Limits (GET /api/v1/tier/compliance/limits). It returns your active tiers, ordered by level, each one with its limits.
Query parameters, all optional: Each entry in limits groups the limits of one operation type in one currency: A null value means that tier has no limit of that kind. A tier with an empty limits list has no limits configured for the requested currency.

2. Find a user’s tier

Call Get Tier User Assignments (GET /api/v1/tier/user-assignments) with the user_id filter:
tier_compliance_id is the id of a tier from step 1. Match them to get the tier’s name, level and limits. Filters, all optional and combinable: Without filters, the endpoint lists the assignments of all your users.
A user gets their first assignment for a currency when Kravata first evaluates them in that currency, usually at their first operation. Until then the list can be empty for that user. They start in the base tier: the active tier with the lowest level that has deposit limits in that currency.

Assignment statuses