CoinCorner

• Name: CoinCorner
• URL: https://www.coincorner.com/
• Category: bitcoin payments and remittance operator / wallet-and-exchange company / Lightning API and card-payment middleware
• Tags: bitcoin-ecosystem
• Summary: CoinCorner belongs in companies/ because the practical control surface is a named company that onboards users and businesses, issues API credentials, holds or intermediates balances, schedules recurring Lightning payouts, routes Send Globally transfers through partner payout rails, and decides how Bolt Card, Lightning send/receive, and merchant workflows are packaged. The useful analytical question is not just does this app support Lightning? but which company controls custody posture, API access, remittance routing, recurring-payment behavior, and the wallet/card surfaces users treat as payment truth?
• What it does:
  • Operates consumer Bitcoin account, custody, buy/sell, send, and receive flows alongside a business-facing Bitcoin and Lightning API
  • Exposes authenticated API access so external businesses can add Bitcoin and Lightning support without running their own wallet infrastructure
  • Supports Lightning payments through invoices, Lightning addresses, and LNURL flows, including recurring Lightning payouts on daily, weekly, monthly, or yearly schedules
  • Runs Send Globally, which converts user balances into BTC, routes over Lightning, and settles out through third-party local-currency bank-account or mobile-money payout rails in supported countries
  • Packages the Bolt Card as an NFC Lightning payment surface tied to CoinCorner balances and LNURL-based withdrawal flows
  • Combines exchange, wallet, remittance, recurring-payout, and card-payment functions inside one company-run operating shell rather than a neutral protocol layer
• Key claims:
  • CoinCorner’s API homepage says businesses can support Bitcoin and Lightning without needing any wallet infrastructure, which is strong evidence that the company note matters more than a narrow app note
  • The API docs use production-style HMAC-SHA256 request signing with API key, signature, nonce, SSL-only transport, and rate limits, showing CoinCorner operates a real external integration surface
  • The Lightning support docs say users can send with Lightning invoices, Lightning addresses, and LNURL, and receive through LNURL, account Lightning addresses, or generated invoices
  • The recurring-payments docs say CoinCorner supports scheduled Lightning payments daily, weekly, monthly, or yearly to a Lightning Address or LNURL pay endpoint, which makes payout-policy and account-control decisions part of the real operator boundary
  • The Send Globally docs say GBP/EUR or BTC balances are converted into BTC, moved across Lightning, and converted by partners into local-currency bank-account or mobile-money payouts, which is exactly the kind of offchain routing and dependency stack that belongs in companies/
  • The Bolt Card docs show CoinCorner also controls an NFC payment experience tied to CoinCorner balances, giving the company influence over the signer/payment surface users actually touch
• Whitepaper: No classic standalone company whitepaper is the important artifact here. The clearest primary materials are CoinCorner’s API docs and first-party support corpus for Lightning, recurring payments, Send Globally, and the Bolt Card, collected in ../whitepapers/coincorner-primary-sources-2026-05-02.md.
• Sources:
  • https://www.coincorner.com/
  • https://api.coincorner.com/
  • https://support.coincorner.com/api/v2/help_center/en-us/articles/360020667299.json
  • https://support.coincorner.com/api/v2/help_center/en-us/articles/5785088860956.json
  • https://support.coincorner.com/api/v2/help_center/en-us/articles/7032542268700.json
  • https://support.coincorner.com/api/v2/help_center/en-us/articles/7032882154908.json
  • https://support.coincorner.com/api/v2/help_center/en-us/articles/5600580995346.json

Internal linkages

• Legacy project alias: coincorner.
• Best self-hosted merchant-stack contrast: btcpay-server.
• Useful adjacent company reads: opennode, strike, and lightspark.

Protocol / company boundary

• CoinCorner does not become analytically cleaner when treated as a standalone protocol note.
• The important surface is the company-run operating shell: custody and account policy, business API issuance, Lightning payout scheduling, partner remittance routing, and the Bolt Card / wallet interfaces that package those capabilities for end users and integrators.
• That is why CoinCorner belongs in companies/: the meaningful questions are about who controls payment workflow, payout reach, account permissions, and the hosted state users and merchants depend on.

Control surface

• Practical leverage sits in account onboarding, custody and balance policy, API-key issuance, rate limits, Lightning send/receive feature exposure, recurring-payment scheduling, remittance partner routing, payout-country coverage, and the wallet/card interfaces CoinCorner chooses to expose.

• The sticky dependency is operational: once a business or user relies on CoinCorner-managed balances, recurring Lightning flows, Send Globally corridors, and Bolt Card payments, the real trust surface is the company-run workflow graph rather than Lightning in the abstract.

• Read CoinCorner as a Bitcoin payments and remittance operator first, with exchange features attached.

• Last reviewed: 2026-08-07 UTC