CoinGate

• Name: CoinGate
• URL: https://coingate.com/
• Category: regulated crypto-payments operator / merchant settlement and payout company / white-label payment-operations infrastructure
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: CoinGate belongs in companies/ because the useful control question is not only what crypto checkout flow exists? but which named operator onboards merchants, issues API credentials, hosts invoice and payout workflow, decides settlement and FX behavior, and becomes the source of webhook, dashboard, and audit truth for payment state? That authority sits with CoinGate as a company boundary more clearly than with a neutral payment-rail label.
• What it does:
  • Operates hosted crypto checkout, merchant invoicing, payment links, ecommerce plugins, and API-based order creation for businesses accepting crypto
  • Packages settlement choices including EUR, stablecoin, and crypto balances, with instant conversion and merchant-side payout routing under one operator shell
  • Runs payout workflows through dashboard, CSV batch uploads, and API integrations, including FX conversion during remittances and lifecycle visibility for operators
  • Offers white-label payment infrastructure with custom-branded payment flow, virtual-ledger or sub-account style accounting, AML checks, and more advanced payment-routing behavior
  • Exposes company-run webhook, refund, team-permission, balance-management, and reporting surfaces that downstream businesses may start treating as operational truth
  • Sells one-company integration across checkout, conversion, payouts, billing, and reconciliation rather than a neutral lower-layer protocol primitive
• Key claims:
  • The homepage says CoinGate is a regulated crypto payment gateway, one of the first MiCA-licensed providers in the EU, and a platform for payments, payouts, billing, and balance management rather than only a checkout button
  • The homepage also says CoinGate has processed more than 7 million payments since 2014 and supports settlement into EUR, stablecoins, or crypto with instant conversion, which is a strong sign that the company boundary matters more than the underlying rail alone
  • The crypto-payouts page describes dashboard, CSV, and API payout modes plus role-based access, activity logs, MFA, four-eye approval, AML compliance, and exportable transaction records, making the operator boundary explicit
  • The create-order API docs require API-token-authenticated order creation and return a CoinGate payment_url, while settlement and Travel Rule prefilling sit inside CoinGate-managed workflow fields rather than a neutral protocol surface
  • The same create-order docs say receive_currency controls settlement currency and can trigger exchange-based conversion at invoice creation time, which makes CoinGate a live routing and settlement policy layer rather than only a passive invoice host
  • CoinGate’s product materials repeatedly frame the service as infrastructure for businesses that want crypto payments, payouts, billing, balances, and white-label operations under one regulated shell
• Whitepaper: No classic standalone company whitepaper is the key artifact here. The strongest primary materials are CoinGate’s homepage, payouts page, business-solution pages, and developer docs, which together show a company-run merchant-processing, payout, and reconciliation stack rather than a neutral payments protocol. The broader source bundle remains ../whitepapers/coingate-primary-sources-2026-05-02.md.
• Sources:
  • https://coingate.com/
  • https://coingate.com/solutions/business
  • https://coingate.com/crypto-payouts
  • https://developer.coingate.com/reference/cryptocurrency-payment-api
  • https://developer.coingate.com/reference/api-overview
  • https://developer.coingate.com/reference/create-order

Internal linkages

• Product-layer note: coingate.
• Best self-hosted merchant-stack contrast: btcpay-server.
• Useful adjacent company reads: opennode, bvnk, and moonpay.

Protocol / company boundary

• coingate still does useful work as the product-layer note for hosted invoice creation, callback delivery, refund handling, payout objects, and merchant-facing integration surface.
• This company note is the broader operator boundary: merchant admission, API-token issuance, settlement and FX policy, payout approval workflow, compliance posture, team permissions, white-label packaging, and dashboard or webhook truth all sit with CoinGate as a named company.
• That split matters because the sticky dependency businesses inherit is not simply accept crypto; it is a company-run operating shell for invoicing, settlement, payouts, and auditability.

Control surface

• Practical leverage sits in merchant onboarding, production credential issuance, invoice lifecycle, accepted settlement currencies, conversion timing, payout-mode exposure, refund workflow, webhook and dashboard truth, permissions and four-eye approval policy, and the white-label behavior partners inherit.

• The deeper lock-in is operational: once a merchant hardens around CoinGate-hosted invoices, conversion logic, payout records, sub-account accounting, and compliance workflow, the dependency is on the company-run payment-operations graph more than on any one API endpoint.

• Read CoinGate as a regulated merchant-payments and payout operator first. The crypto rails are inputs; the real authority sits in the company-managed workflow shell around them.

• Last reviewed: 2026-08-07 UTC