GoMining releases GoBTC Pay SDK and APIs to push BTC-native merchant payments
The company says the rail settles on Bitcoin in about 12 hours on average and charges merchants a 0.2% fee split with wallets and miners.
GoMining has opened developer access to its GoBTC Pay protocol with a new SDK and APIs, positioning it as a bitcoin-native merchant payment rail. The pitch is explicit: merchants receive BTC by default, contrasting with Square’s Lightning-based flow that converts to USD unless a merchant opts into BTC.
Key Takeaways
- GoMining unveiled an SDK and APIs for GoBTC Pay on June 19, 2026, targeting merchant integrations for everyday BTC purchases.
- The protocol is positioned to keep the full transaction in bitcoin, with merchants receiving BTC by default and handling any fiat conversion themselves.
- GoMining describes GoBTC Pay as settling directly on the Bitcoin network using its Stratum V2 mining protocol, with around 12 hours as the average settlement time.
- Merchant fees are stated at 0.2%, split evenly between wallet providers and miners, with an initial rollout goal of 10 merchants.
GoMining Opens GoBTC Pay to Builders With New SDK and APIs
GoMining rolled out a software development kit and application programming interfaces for GoBTC Pay on June 19, giving merchants and payment builders programmable access to its bitcoin payment protocol. In practice, the tooling is meant to shorten integration work for teams that want to accept BTC for routine commerce rather than treat bitcoin payments as a one-off checkout option.
The company framed the release as a move from concept to integration surface area. An SDK typically packages prebuilt components for developers, while APIs let external systems trigger and reconcile payments. The immediate market question is not whether merchants can “accept BTC” in theory, but whether GoMining can get enough wallet and merchant endpoints live to make the rail usable without custom plumbing.
BTC-to-Merchant by Default: The Direct Contrast With Square’s Fiat-Default Flow
GoMining’s differentiation is not subtle. It is optimizing for merchants that want to receive bitcoin, not merchants that want USD-denominated cash flow with a bitcoin-branded front end.
GoMining says GoBTC Pay completes the entire transaction in BTC and pays merchants in BTC by default. If a merchant wants fiat, the conversion sits on the merchant’s side of the stack. That is a structural contrast with Square’s bitcoin payments service, which uses the Lightning network and converts the bitcoin amount into U.S. dollars by default, with merchants receiving BTC only if they opt in.
That positioning matters because it effectively splits the merchant market into two cohorts: those treating BTC as a treasury asset they want to retain, and those treating BTC as a payment method they want to neutralize into fiat. GoMining is explicitly chasing the first cohort.
How GoBTC Pay Says It Settles: On-Chain, Stratum V2, and the ~12-Hour Average
GoMining describes GoBTC Pay as settling directly on the Bitcoin network, using the company’s Stratum V2 mining protocol as part of the settlement design. Stratum V2 is a mining protocol standard for communication between miners and pools. In this context, GoMining is presenting it as infrastructure that supports an on-chain settlement path.
The tradeoff is clear in the numbers provided. GoMining put average settlement time at around 12 hours. That is a very different user experience than Lightning’s “instant” narrative, and it pushes GoBTC Pay toward merchant categories that can tolerate confirmation latency in exchange for on-chain finality.
On fees, GoMining stated merchants will pay 0.2% per transaction, with the fee split 50/50 between wallet providers and miners. Hard-coding a low fee and sharing it across the stack reads like an incentive design choice aimed at pulling in integrations and miner participation, not just a pricing decision.
Merchant Rollout: 10-Partner Target and the Missing Implementation Details
GoMining said it plans to recruit an initial 10 merchants. No merchant names, verticals, or launch geographies were provided, which limits near-term read-through on adoption beyond the announcement itself.
The next signals that matter are operational, not promotional: whether the first cohort expands beyond 10, which wallet providers integrate (they are explicitly part of the fee split), and whether real-world settlement times match the stated ~12-hour average once transactions hit production volume. The packet also leaves open key implementation details that typically decide merchant viability, including compliance and AML posture, custody versus non-custody deployment patterns, and onboarding timelines.
What This Launch Signals for the BTC Payments Narrative
GoMining is making a clean bet that the next leg of BTC payments adoption comes from merchants who want to keep bitcoin, not merchants who want to hide it behind automatic USD settlement. That is a narrower target market, but it is also the only one that creates sustained BTC-denominated merchant receipts without relying on a separate conversion layer.
The threshold that matters is whether GoBTC Pay can turn its stated 0.2% fee and wallet-miner split into real integrations while proving that on-chain settlement with a ~12-hour average is acceptable for specific merchant categories. If that holds, the setup starts to look structural rather than narrative-driven, because it would demonstrate a BTC-to-merchant rail that does not default back into fiat at the last mile.
