---
title: "Coverage"
description: "What the Partner API supports today, and how the work is split between your integration and Stablegate. Routes, assets and rules change over time: the API is the source of truth at runtime, and the Changelog records every change."
canonical_url: "https://docs.stablegate.com/docs/guide/getting-started/coverage"
---
# Coverage

> What the Partner API supports today, and how the work is split between your integration and Stablegate. Routes, assets and rules change over time: the API is the source of truth at runtime, and the Changelog records every change.

What the Partner API supports today, and how the work is split between your integration and Stablegate. Routes, assets and rules change over time: the API is the source of truth at runtime, and the [Changelog](https://docs.stablegate.com/docs/changelog) records every change.

## Exchange Routes

The fiat side is `EUR` over `sepa`. The crypto side is a stablecoin on one of its supported networks:

<table>
<thead>
  <tr>
    <th>
      Asset
    </th>
    
    <th>
      Networks
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        USDT
      </code>
    </td>
    
    <td>
      <code>
        ethereum
      </code>
      
      , <code>
        tron
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        USDC
      </code>
    </td>
    
    <td>
      <code>
        ethereum
      </code>
      
      , <code>
        stellar
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        EURC
      </code>
    </td>
    
    <td>
      <code>
        ethereum
      </code>
    </td>
  </tr>
</tbody>
</table>

Every pair works in both directions: on-ramp (`EUR` to the stablecoin) and off-ramp (the stablecoin to `EUR`). Each order is one exchange between one source and one destination. Query [`GET /v1/exchange-routes/`](https://docs.stablegate.com/docs/guide/exchange-routes) for the current list and `fraction_digits` of each asset, and [`POST /v1/exchange-routes/check/`](https://docs.stablegate.com/docs/guide/exchange-routes#check-route-availability) before creating an order: a route can exist and still be temporarily unavailable.

## Customers

<table>
<thead>
  <tr>
    <th>
      
    </th>
    
    <th>
      Individual
    </th>
    
    <th>
      Corporate
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Create via API
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Yes (<code>
        company_name
      </code>
      
       required)
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://docs.stablegate.com/docs/guide/customers#start-instant-verification">
        Instant Verification
      </a>
    </td>
    
    <td>
      Yes, when enabled for your account
    </td>
    
    <td>
      No
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://docs.stablegate.com/docs/guide/customers#create-a-verification-link">
        Standard verification
      </a>
      
       via hosted link
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      Yes
    </td>
  </tr>
  
  <tr>
    <td>
      Trading after approval
    </td>
    
    <td>
      Instant: at once. Standard: after activation
    </td>
    
    <td>
      After activation
    </td>
  </tr>
</tbody>
</table>

Instant Verification runs sanctions and PEP screening and approves automatically when the screening is clear, usually within minutes; a match goes to manual review. Standard verification adds document checks and account activation (a test deposit or a video interview). Higher levels and personal limits are assigned by Stablegate compliance after a Source-of-Funds review.

A customer record is created once and is not edited afterwards; closing a customer that has not started verification arrives with the next release (see [Close a Customer](https://docs.stablegate.com/docs/guide/customers#close-a-customer)). Customer states (`active`, `limited`, `blocked`, `closed`) are managed by Stablegate and read from [`GET /v1/customers/{customer_uuid}/`](https://docs.stablegate.com/docs/guide/customers#get-customer-details).

Customers from the [non-serviced countries](https://docs.stablegate.com/docs/verification/common/countries) and US persons cannot be onboarded.

## Accounts

<table>
<thead>
  <tr>
    <th>
      Account
    </th>
    
    <th>
      Networks and rails
    </th>
    
    <th>
      Ownership proof
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Bank account
    </td>
    
    <td>
      IBAN, SEPA payouts
    </td>
    
    <td>
      Holder name on the account
    </td>
  </tr>
  
  <tr>
    <td>
      Wallet
    </td>
    
    <td>
      <code>
        ethereum
      </code>
      
      , <code>
        tron
      </code>
      
      , <code>
        stellar
      </code>
      
       for the routes above; see <a href="https://docs.stablegate.com/docs/guide/external-accounts#create-a-wallet">
        External Accounts
      </a>
      
       for every accepted rail
    </td>
    
    <td>
      Signed message for Ethereum, or a <a href="https://docs.stablegate.com/docs/guide/external-accounts#satoshi-test">
        Satoshi Test
      </a>
    </td>
  </tr>
</tbody>
</table>

Every order pays out to an account registered for the customer. The number of accounts per customer is set by your account configuration. See [External Accounts](https://docs.stablegate.com/docs/guide/external-accounts).

## Limits and Fees

Limits are per customer, counted in EUR, and depend on the verification level and risk category. The fee is calculated in the deposit currency, deducted from the deposit, and has a minimum per transaction. Defaults are on [Limits](https://docs.stablegate.com/docs/guide/fees-and-limits/limits) and [Fees](https://docs.stablegate.com/docs/guide/fees-and-limits/fees); the values that apply to a given customer come from [`GET /v1/customers/{customer_uuid}/limits/`](https://docs.stablegate.com/docs/guide/fees-and-limits/limits#get-customer-limits) and [`POST /v1/customers/{customer_uuid}/check-fees/`](https://docs.stablegate.com/docs/guide/fees-and-limits/fees#check-fees-api).

## Events

[Webhooks](https://docs.stablegate.com/docs/guide/webhooks) deliver `order.status_changed` for orders created through the API, signed with HMAC-SHA512. Verification outcome, customer state and deposit progress are read by polling the customer and order detail endpoints.

## Who Does What

<table>
<thead>
  <tr>
    <th>
      Through the API
    </th>
    
    <th>
      By Stablegate, on request
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Create customers, start verification, close unused customers
    </td>
    
    <td>
      Enable Partner API access and review clients' verification
    </td>
  </tr>
  
  <tr>
    <td>
      Register and remove bank accounts and wallets
    </td>
    
    <td>
      Block, limit, reactivate or close a verified customer
    </td>
  </tr>
  
  <tr>
    <td>
      Check routes, fees and limits; create and cancel orders while <code>
        new
      </code>
    </td>
    
    <td>
      Set verification levels, custom limits, minimum amounts and fee schedules
    </td>
  </tr>
  
  <tr>
    <td>
      Read order and deposit status; receive webhooks
    </td>
    
    <td>
      Retry, hold, stop or roll back an order; refund a rejected deposit; recover a transfer sent on the wrong network
    </td>
  </tr>
  
  <tr>
    <td>
      Manage API keys and webhooks in the Developers section
    </td>
    
    <td>
      Set the deposit deadline (<code>
        valid_until
      </code>
      
      ) and the number of accounts per customer
    </td>
  </tr>
</tbody>
</table>

To request anything from the right column, contact your account manager or support with the customer or order UUID.


## Sitemap

See the full [sitemap](https://docs.stablegate.com/sitemap.md) for all pages.