CoinGate

• Name: CoinGate
• URL: https://coingate.com/
• Category: crypto payment gateway / merchant-and-payout control plane / white-label payment operations infrastructure
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: CoinGate at the project layer is the hosted invoice, checkout, and payout-workflow surface inside a broader CoinGate company shell. The useful product cut is the merchant-facing API and white-label payment-integration surface; the broader operator boundary now lives in coingate, which is the cleaner place to reason about merchant onboarding, API-token issuance, settlement and FX policy, payout approval workflow, compliance posture, and dashboard or webhook truth.
• What it does:
  • Lets businesses accept crypto payments through hosted invoices, APIs, ecommerce plugins, email/direct-link billing, and browser-based point-of-sale flows
  • Converts customer payments into a merchant’s preferred settlement currency and supports withdrawals to bank accounts or crypto wallets
  • Supports crypto payouts through dashboard, CSV batch uploads, and API workflows, including FX conversion during payout execution and payout-lifecycle visibility
  • Offers team permissions, reporting, notifications, balance management, refunds, and mass-payout tooling for payment operations
  • Provides white-label infrastructure with custom-branded payment flows, virtual ledgers/sub-account style accounting, AML checks, and advanced API behavior such as hidden payment flows and crypto refunds
  • Exposes a public API for order creation, callbacks, redirect handling, and Travel Rule form prefilling during checkout
• 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 just a merchant checkout form
  • The same page says CoinGate has processed more than 7 million payments since 2014 and supports settlement into EUR, stablecoins, or crypto with instant conversion, which reinforces the operator-infrastructure framing
  • The business and ecommerce solution pages describe an invoice → payment → conversion → settlement flow, plus flexible withdrawals, refunds in crypto, currency conversion, mass payouts, API integrations, plugins, and browser-based POS
  • Those solution pages also say CoinGate’s white-label product keeps payment flow on the brand’s own domain/frontend, adds AML and realtime wallet checks, exposes virtual ledgers for sub-account style accounting, and supports hidden payment flows, crypto refunds, discrepancy tracking, and mass payouts
  • The crypto payouts page says CoinGate supports one-off dashboard payouts, CSV upload batch payouts, and API-based remittances, with FX conversion during payout execution, webhooks, role-based access, activity logs, MFA, and optional four-eye approval for batch payouts
  • The payouts FAQ says recipients only need a compatible wallet address and that supported assets and networks span major crypto and stablecoin rails, which makes the product look broader than a store plugin
  • The Create Order API docs say POST /api/v2/orders returns a payment_url and supports status callbacks, cancel/success redirect URLs, merchant validation tokens, and optional shopper information to prefill Travel Rule forms
• Whitepaper: No canonical standalone CoinGate whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official product pages plus the developer docs for payment orders and payout operations; see ../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

• Company boundary for the broader operator shell: coingate.
• Best self-hosted merchant-stack contrast: btcpay-server.
• Closest hosted-processor peer once the question is merchant operations rather than broader payment-company workflow: opennode.

Product / company boundary

• Keep this note on the merchant-facing product surface: hosted invoice creation, payment_url handoff, callbacks and redirects, payout objects, white-label checkout behavior, and the receive-currency / refund choices integrators wire into their own systems.
• Use coingate when the sharper question is who approves merchants, issues API tokens, sets settlement and FX policy, controls payout approval workflow, runs permissions and audit controls, and publishes dashboard or webhook truth around those flows.
• That split matters because CoinGate is not only crypto payments in the abstract. It is a product layer sitting inside a regulated company-run operating shell for checkout, conversion, payouts, and merchant-state publication.

Control surface

• At the product layer, practical authority sits in order creation, payment_url checkout handoff, callback delivery, receive-currency and refund behavior, payout objects, and the merchant-facing white-label flow the integration exposes.

• For the wider operator shell around merchant admission, API-token issuance, settlement and FX policy, permissions, payout approvals, and compliance workflow, read coingate.

• Read it as a managed processor product surface, not as a neutral payment rail.

• Last reviewed: 2026-08-07 UTC