Skip to main content

​
What is Bringin?

Bringin is a crypto-to-fiat payment platform. Partners integrate the Bringin API to give their users:
  • Top-up Debit Card — Users deposit crypto (BTC, USDC, ETH), Bringin converts to EUR and loads their debit card
  • On-ramp — Buy crypto by sending EUR to a deposit IBAN
  • Connections — Set up recurring standing orders that auto-convert crypto ↔ fiat
Bringin handles KYC, compliance, custody (via Striga), and settlement. Partners provide the user-facing experience.

​
Choose Your Integration

Top-up Debit Card API

Let users top up their EUR debit card with crypto. Deposit USDC/BTC, spend EUR anywhere.

Connection API

Automatic EUR ↔ BTC conversions. Pass a Bitcoin address, get back an IBAN. Funds convert automatically.

​
Partner Types

​
Top-up Debit Card Partners

Your backend calls the Bringin API to let users top up a EUR debit card with crypto. Each user gets a per-user API key after onboarding. Typical flow:
  1. Onboard user (Bringin handles KYC + card issuance)
  2. Get deposit address for the crypto the user wants to convert
  3. User sends crypto to the deposit address
  4. Bringin converts to EUR and loads the debit card balance
  5. You receive an order-status webhook when complete
  6. User spends EUR anywhere with their card
Example: Lendasat — users deposit USDC on Polygon, spend EUR with their Bringin debit card.

​
Connection Partners

Your app helps users create a connection (standing order) between a crypto address and an IBAN. You make a single API call with the user’s email and connection details — Bringin handles onboarding, KYC, confirmation, and SMS OTP. You receive webhooks when everything is ready. Once active, conversions happen automatically every time funds arrive — no further API calls needed. Example: Cake Wallet — user links a BTC address to their bank account. Every BTC deposit auto-converts to EUR and arrives via SEPA.

​
Key Concepts

​
Two API Keys

KeyPurposeHow to get it
Master API keyIdentifies your application. Used for onboarding new users.Provided by Bringin during partner setup
Per-user API keyIdentifies a specific user within your application. Used for connections, balance, transactions.Returned after user onboarding

​
Onboarding

Before a user can use Bringin through your app, they must be onboarded: registered with Bringin and KYC-verified. You trigger this with POST /application/connect using your master API key. Bringin handles the signup, KYC, and email verification.

​
Connections

A connection is a permanent standing order that links a Bitcoin address to a bank account. Once created, conversions happen automatically — any amount, any time.
  • Buy Connection — You provide a BTC address → Bringin returns a deposit IBAN. User sends EUR to the IBAN → BTC arrives at their address.
  • Sell Connection — You provide an IBAN → Bringin returns a BTC deposit address. User sends BTC to the address → EUR arrives in their bank.
No further API calls needed after setup. Bringin handles the KYC, SMS confirmation, and all conversions.

​
Webhooks

If you provide a callback URL during onboarding, Bringin sends webhook notifications for:
  • /verification-status — User completed KYC, per-user API key delivered
  • /order-status — Transaction completed or failed
  • /connection-status — Connection became active
Webhooks are optional. Client-only partners can poll instead.

​
Base URLs

EnvironmentURL
Sandboxhttps://dev.bringin.xyz
Productionhttps://api.bringin.xyz
All endpoints use the prefix /api/v0/.