Digital Garage announced the commercial rollout of DG Stablecoin Payment Service on 10 August, positioning the software layer between existing payment infrastructure and stablecoins. The service is scheduled to be deployed first to JCB and DG Financial Technology, with USDC on Base as the first supported payment rail.

The announcement is concrete about the architecture and cautious about deployment. The 1.3 million payment locations highlighted in some headlines are the footprint already served by DGFT. They are not 1.3 million merchants already accepting stablecoins.

What actually launched

In its 10 August announcement, Digital Garage said it had started the commercial rollout of DG Stablecoin Payment Service, or DG SPS. The product is aimed first at payment providers. They are meant to connect it to existing infrastructure through an API, then offer merchants a stablecoin option without requiring extra hardware or separate operations for every blockchain.

Digital Garage describes JCB and DGFT, its own subsidiary, as the first scheduled recipients. That distinction matters: the release does not say that every merchant in either network has activated the service. Payment Navi and NADA News preserve the future-tense wording in their Japanese coverage.

The first announced rail is USDC on Base. Digital Garage plans to add the yen-linked JPYC stablecoin, as well as Ethereum and Polygon. DG SPS is also designed to support x402, a payment protocol that software agents can use, but the company still frames that capability as a development goal.

A 1.3 million-location network is not 1.3 million acceptors

The release says DGFT processes ¥9.1 trillion a year and supports more than 1.3 million payment locations. It also says JCB has a network of 72 million acceptance locations worldwide and handles ¥53.4 trillion in annual transaction volume.

Those figures describe the reach of networks to which DG SPS could connect. They do not measure activated merchants or stablecoin payment volume. A TechTimes headline says the middleware is “reaching” 1.3 million merchants, while the primary source describes DGFT’s existing footprint and an initial deployment that is still scheduled.

The distinction separates three stages: having a distribution network, integrating a new payment option and generating real usage. Digital Garage has the first and is commercialising the layer needed for the second. The release provides no data on the third.

Why the middleware layer matters

A merchant accepting cards does not normally connect directly to every bank, currency and network. A payment provider absorbs that complexity. DG SPS applies the same model to stablecoins: support assets and chains upstream, then expose a standard connection downstream.

That approach could prove more important than another isolated pilot. In February, Digital Garage, JCB and Resona ran an in-store trial using USDC on Base and JPYC on Polygon. It relied on dedicated applications at one venue and envisaged the merchant receiving yen. DG SPS turns the experiment into a product for payment operators instead of a separate integration for each shop.

GatherHub’s inference is that, if the API genuinely reduces integration and operating work, the main advance will not be a blockchain visible at checkout. It will be the ability to add a programmable rail to infrastructure that merchants already use while keeping their workflow familiar.

The GatherHub Stablecoins course explains the distinction between a stablecoin, its issuer and the distribution intermediaries that make it spendable.

What the announcement leaves unanswered

“Commercial” describes the product’s status, not its adoption. Digital Garage gives no production date for JCB or DGFT, no activated-merchant count, no payment volume and no list of participating brands.

The release also leaves the final conversion into yen, fees, settlement time, custody of funds and keys, refund handling and error liability unspecified. The February pilot envisaged yen settlement for the merchant, but that design cannot be assumed for every future commercial deployment.

Centralising the integration creates an operational dependency, too. If several providers use the same layer, an outage, routing error or control weakness could affect many merchants at once. The supported assets and networks add their own dependencies: chain availability, issuer policy, freezing powers and conversion liquidity.

Agent payments remain a scenario. Announced x402 support does not show that an agent has paid a merchant through DG SPS, or that questions around authorisation, disputes and liability have been settled.

Why it matters now

Japan already has extensive payment networks and pilots involving USDC and JPYC. The bottleneck is moving from “can a stablecoin payment work?” to integration with the systems that providers and merchants use every day.

DG SPS is noteworthy precisely because it does not ask shops to become blockchain operators. If it works as announced, it could lower the marginal cost of adding another asset or network. Success will nevertheless depend less on the theoretical size of the footprint than on activation, customer demand and the quality of local-currency settlement.

Payment providers, tourism and cross-border merchants, treasury teams and compliance officers are the first groups affected. For them, the issue is broader than onchain transaction speed: conversion, fraud, refunds, accounting and support all remain part of the payment.

What to watch next

The next verifiable signals will be announcements from JCB and DGFT themselves, a production date, activated-merchant numbers and initial volume. It will also be worth checking whether JPYC, Ethereum and Polygon move from the roadmap into production.

Details on fees, yen settlement, regulated partners, custody, security audits and service availability would make the middleware itself easier to assess. Finally, activation and usage rates will show whether a distribution footprint becomes an acceptance network — the central question that the 1.3 million figure cannot yet answer.

Sources consulted

Editorial illustration generated by Édito GatherHub under the “Portail Matière” identity. This article is not financial advice.