Regional Starter Pack
Koywe logo

Koywe

Koywe is a Latin American crypto-finance infrastructure provider offering fiat on/off ramps between local currencies and stablecoins. It ramps Argentine pesos (ARS), Mexican pesos (MXN), and Colombian pesos (COP) to USDC on Stellar via local rails — CVU/QR in Argentina, SPEI in Mexico, and PSE in Colombia.

Regions

🇦🇷 Argentina🇲🇽 Mexico🇨🇴 Colombia
Currency

MXN

Rail

spei

Token

USDC

KYC

Required

On-Ramp (MXN → USDC) Off-Ramp (USDC → MXN)

How this anchor scores

Commercial

  • failed: Locally denominated asset (stablecoin or stablebond) on Stellar USDC only
  • met: Support for local payment rails connected to Stellar WIREAR/QRI (AR) + SPEI (MX) + PSE (CO)
  • partial: Competitive rates (wholesale <25 bps conversion)
  • unverified: Deep liquidity for low slippage (local ↔ global assets)

Developer

  • partial: Open self-service access (credentials + sandbox, no human in the loop) Credentials by email request (lightweight human step)
  • met: Accurate, well-documented API (docs match the wire) Authoritative OpenAPI spec
  • met: High-fidelity sandbox (a completed test ramp lands real on-chain testnet tokens) On-ramp settles canonical USDC on Stellar testnet, verified end-to-end
  • partial: Agent-buildable (machine-readable docs/spec, diagnosable failures) OpenAPI good; opaque/silent sandbox failures
  • met: Fee/rate discoverability (costs findable via pricing docs or a quote/fee API) Quote API returns fee per transaction

Integration Flow

On-Ramp

  1. Authenticate — Exchange the integration clientId/secret for a JWT scoped to the user email.
  2. Select Payment Method — Fetch ARS payment providers (WIREAR / QRI / Khipu) and let the user pick a rail.
  3. Get Quote — Request an executable ARS → USDC quote for the chosen payment method.
  4. Create On-Ramp Order — Submit the order with the user’s Stellar address; receive CVU instructions or a hosted redirect.
  5. Pay via Local Rail — The user transfers ARS via CVU, or completes the hosted QR/Khipu redirect.
  6. Receive USDC — Koywe delivers USDC to the user’s Stellar wallet once funds settle.

Off-Ramp

  1. Authenticate — Exchange the integration credentials for a user-scoped JWT.
  2. Get Quote — Request an executable USDC → ARS quote.
  3. Create Off-Ramp Order — Submit the order against a registered bank account; receive a Koywe deposit address.
  4. Send USDC — Sign and submit the USDC payment to the Koywe deposit address with Freighter.
  5. Submit Tx Hash — Attach the Stellar transaction hash so Koywe can reconcile the transfer.
  6. Receive ARS — Koywe pays out ARS to the user’s bank account.

Known Issues

  • Regional coverage wired here: Argentina (CVU/QR), Mexico (SPEI), Colombia (PSE) — all to USDC on Stellar. Chile (CLP) and Peru (PEN) are also supported by Koywe but not yet wired into this app. Brazil (BRL) on-ramps via PIX, but its off-ramp is not in Koywe's bank-account currency enum, so Brazil is intentionally excluded for now.
  • Off-ramp payout-account registration is only sandbox-verifiable for Argentina (which has documented whitelisted test pairs, and is itself currently Koywe-side broken). Mexico and Colombia off-ramps are wired to spec but have no published sandbox test identities, so they cannot be verified end-to-end in the sandbox.
  • Koywe does not return a Stellar issuer for USDC (it is network-dependent), so the integration injects PUBLIC_USDC_ISSUER for the active network.
  • The hosted KYC widget URL endpoint is unconfirmed in the sandbox — the client surfaces a clear "not implemented" state until it is wired up. Complete KYC for the test user via the Koywe dashboard.
  • On-ramp is verified end-to-end in the sandbox: a Khipu order (pay 1234/123456 on the hosted test page) advances WAITING → EXECUTING → IN_PROGRESS → DELIVERED and lands canonical USDC on Stellar testnet at the destination address, matching the quoted amount. WIREAR and QRI orders stay in WAITING (only Khipu has a sandbox pay page).
  • The off-ramp order field name and the submit-tx-hash REST path follow the documented OpenAPI spec but have not been verified end-to-end against the live sandbox.
  • Off-ramp is blocked at bank-account registration: POST /rest/bank-accounts returns a 400 ownership-validation error even for Koywe's own documented DNI↔CVU test pairs. Appears to be a non-functional sandbox validation backend on Koywe's side.
  • KYC document numbers are single-use: re-using a whitelisted test DNI on a new account returns "account already exists with that document number", so the small pool of sandbox test identities is quickly exhausted. Account verification status is read live via GET /rest/accounts/{email}/check.

Links