💵 Off-Ramp

​

Integration Flow

​

How to do an Off-Ramp Operation

1. ​

   Select the Blockchain and Token:

   1. The following is a list of the Blockchains and Tokens
   2. The list of Blockchains - Tokens symbols supported in Capa are:
      1. POL - USDC, USDT, POL, MATIC
      2. BSC - BNB
      3. BASE - USDC, USDC.e, USDbC, ETH, MXNe, cbBTC, wUSDL
      4. OP - USDC, ETH
      5. ARB - USDC, ETH
      6. SOL - USDC, SOL, USDY, PYSUD
      7. WLD - WLD
      8. STK - USDC, STK
      9. ETH - USDC, ETH, wBTC
         For faster completion time use USDC in Polygon POS

2. ​

   Select the Fiat Currency:

   1. Choose the supported fiat currency for the transaction. Capa currently supports the following fiat currencies:
      1. MXN (Mexican Peso)
      2. DOP (Dominican Peso)
      3. USD (US Dollar)
      4. EUR (Euro)

3. ​

   Quoting:

   1. To show a real-time estimate of how much fiat the user will get with the selected Blockchain Token, Fiat Currency and Amount use the Get Quote Rate endpoint.
   2. To lock a guaranteed exchange rate, use the Create Quote endpoint. This returns a quoteId with an expiration time (expiresAt). Pass the quoteId when creating the transaction to use the locked rate.
   3. You can specify either fiatAmount or cryptoAmount in the quote request.
   4. Forward Settlement (MXN OTC only): For MXN orders above 50,000 MXN (OTC), the locked quote supports a forwardingDays parameter (0-4) that lets you lock the rate now but settle the transaction T+N days later.

4. ​

   User Bank Information:

   1. The user bank information can be provided in multiple ways:
      • Inline bank details: Pass userBankInformation directly in the off-ramp request body.
      • Saved bank account: Use a previously saved bank account ID.
      • Receiver: Pass a receiverId for third-party payouts (see Receivers Guide).
   2. Bank account requirements vary by country:

      Country	Required Fields
      MX	accountIdentifier (18-digit CLABE)
      DO	accountIdentifier, bankName, accountType, documentIdentifier, documentType. List of Dominican Republic Banks
      US	accountIdentifier, bankName, routingNumber (9-digit ABA), accountHolder (type, firstName/lastName or businessName), address (streetLine1, city, postalCode, country)
      SEPA	iban, bic, bankName, accountHolder (type, firstName/lastName or businessName)

   3. For MX accounts, the bank information will go through a penny testing process to ensure that the KYC’d user is the actual owner. If the user is successfully verified the transaction will go through, otherwise it will be CANCELLED and the crypto will be reimbursed.

5. ​

   Obtain User Wallet Address:

   After a successful KYC users get their own Wallet Address which is used as an intermediary to identify the user’s off ramps on chain transaction. In order to show the user where the crypto must be sent to you must obtain the wallet by creating the Off Ramp transaction, the response would have the wallet address.

6. ​

   Execute the Off-Ramp:

   With all required information gathered, you can proceed to execute the off-ramp operation using the Capa API. See the documentation to execute the off ramp Create Off Ramp Key parameters:
   • userId (required): The user’s Capa ID
   • fiatCurrency, blockchainSymbol, tokenSymbol: The selected currency, blockchain, and token (required when quoteId is not provided)
   • fiatAmount or cryptoAmount: The amount to convert
   • userBankInformation (optional): Inline bank account details
   • receiverId (optional): A previously created receiver for third-party payouts
   • quoteId (optional): A locked quote ID from the Create Quote endpoint
   • premiumSpread (optional): A spread percentage to apply to the exchange rate

​

Transaction Status Progression

​

Regular Off-Ramp

​

OTC Off-Ramp (large amounts)

​

Settlement Times

​

Over-Funding

​

SPEI Payout Reference

​

Rounding

​

Execute Off-Ramp (Forwards-Enabled Partners)

{
  "transactionId": "8374f327-38bd-4b0b-b8a7-2524599eb903"
}

​

Available Platforms

​

Notifications

• Webhooks for Partners: Capa posts updates to the configured partner webhooks to notify of transaction status changes.
  Email Notifications for Users (Optional): Users receive email notifications regarding their transaction status and other relevant updates. Webhooks
• Ensure that your webhook settings are correctly configured to receive timely notifications and stay informed about the status of transactions. Webhook Settings

​

Dominican Republic Banks

[
  "ABONAP",
  "Alaver",
  "Asociación Cibao",
  "Asociación Duarte",
  "Asociación La Nacional",
  "Asociación Maguana",
  "Asociación Mocana",
  "Asociación Peravia",
  "Asociación Popular",
  "Asociación Romana",
  "Bancamérica",
  "Banco Activo",
  "Banco Ademi",
  "Banco Adopem",
  "Banco Agrícola",
  "Banco Atlántico",
  "Banco BACC",
  "Banco BDI",
  "Banco BHD",
  "Banco Caribe",
  "Banco Cofaci",
  "Banco Confisa",
  "Banco Fihogar",
  "Banco Gruficorp",
  "Banco Lafise",
  "Banco López de Haro",
  "Banco Popular",
  "Banco Promerica",
  "Banco Santa Cruz",
  "Banco Unión",
  "Banco Vimenca",
  "Banco Óptima",
  "Bancotui",
  "Bandex",
  "Banesco",
  "Banfondesa",
  "Banreservas",
  "Bonanza Banco",
  "Citibank",
  "Corporación de Crédito Monumental",
  "Corporación de Crédito Nordestana",
  "Corporación de Crédito Oficorp",
  "JMMB Bank",
  "Leasing Confisa",
  "Motor Crédito",
  "Qik Banco Digital",
  "Scotiabank"
]

​

What’s Next

• /api/partner/v2/off-ramp