Back to blog
Industry News8 min read

The GENIUS Act Regulates Stablecoin Issuers, Not Merchants. What It Changes for an Acquirer or ISO Whose Merchants Want to Accept Them.

The federal stablecoin law takes effect on 18 January 2027, and Treasury's offer-and-sale proposal is open for comment until 19 October. What the Act covers, where a payments business might fall under it, and what changes when a merchant takes stablecoins instead of cards.

Kyle Hall

Kyle Hall

Founder

The GENIUS Act Regulates Stablecoin Issuers, Not Merchants. What It Changes for an Acquirer or ISO Whose Merchants Want to Accept Them.

Sooner or later a merchant asks whether it can take stablecoins, or a processor offers to add them as a payment method. The question now comes with a federal law attached. The GENIUS Act, signed on 18 July 2025, is the first US statute written specifically for payment stablecoins. It takes effect on 18 January 2027, and Treasury's proposed rule on who may offer and sell stablecoins to people in the United States is open for comment until 19 October 2026.

Most of the Act is about issuers: who may create a dollar-backed token, what has to sit behind it, and who supervises them. It says nothing directly about merchants accepting them, and nothing about acquirers or ISOs by name. This piece works from the enrolled text of the Act, Treasury's August 2026 proposal, and what the networks and processors have published, to set out what the law covers, what it leaves open, and what a merchant-services team should check before boarding a merchant that wants to accept stablecoins.

What the Act Actually Regulates

The Act defines a payment stablecoin as a digital asset designed to be used for payment or settlement, whose issuer is obliged to redeem it for a fixed amount of money and represents that it will hold a stable value. Deposits, national currencies and securities are carved out.

From the effective date, only a permitted payment stablecoin issuer may issue one in the United States. The rest of the statute hangs off that status:

  • Issuers are treated as financial institutions under the Bank Secrecy Act, with an anti-money-laundering program, customer identification, suspicious-activity reporting and sanctions compliance.
  • An issuer may issue only if it has the technical ability to comply, and will comply, with a lawful order to seize, freeze, burn or block the transfer of its stablecoins.
  • An issuer may not pay holders interest or yield solely for holding, using or keeping the stablecoin.
  • A payment stablecoin is not federally insured, and the Act makes it unlawful to represent that one is backed by the full faith and credit of the United States, guaranteed by the government, or covered by FDIC or NCUA insurance.
  • The Act amends the securities and commodities laws so that a payment stablecoin issued by a permitted issuer is neither a security nor a commodity.
  • A public company not predominantly engaged in financial activities, such as a large retailer, may not issue a payment stablecoin without a unanimous vote of the Stablecoin Certification Review Committee.

Two Dates, and Rules That Are Still Coming

The Act takes effect on the earlier of 18 months after enactment or 120 days after the primary federal regulators issue final implementing rules. No final rule from those regulators came early enough to bring the date forward, so the operative date is 18 January 2027. From then, issuing a payment stablecoin without being a permitted issuer is unlawful.

A second prohibition starts three years after enactment, on 18 July 2028. From that date a digital asset service provider may not offer or sell a payment stablecoin to a person in the United States unless a permitted issuer issued it. A separate provision bars service providers from offering, selling or otherwise making available a foreign issuer's stablecoin unless that issuer can, and will, comply with US lawful orders and any reciprocal arrangement with its home country.

The rules that fill this in are not final. The Act set a one-year deadline for implementing regulations, and it passed in July 2026 without them. The OCC published its proposal for issuers under its supervision on 2 March 2026, and its comment period closed on 1 May. Comptroller Jonathan Gould said in August that the agency aimed to finalize by November. Treasury's proposal on issuance, offer and sale was published on 18 August 2026, with comments due on 19 October.

Where a Payments Business Might Fit

The 2028 prohibition falls on digital asset service providers, so the definition matters. The Act defines one as a person that, for compensation or profit, is in the business in the United States of:

  • exchanging digital assets for monetary value;
  • exchanging digital assets for other digital assets;
  • transferring digital assets to a third party;
  • acting as a digital asset custodian; or
  • participating in financial services relating to digital asset issuance.

The exclusions cover distributed ledger protocols, developers of self-custodial software, validators and liquidity pools. There is no exclusion for payment processing or merchant acceptance. The Act's three exempt transactions are for individuals: a direct transfer between two people acting for themselves with no intermediary, a transfer between one person's own US and foreign accounts at the same parent company, and transactions through a self-custody wallet. On the plain words of the definition, a business that takes a customer's stablecoin and pays the merchant in dollars is exchanging a digital asset for monetary value. A merchant that simply receives stablecoins for its own goods is a harder fit, because it is not obviously in the business of exchanging or transferring digital assets for others.

Treasury's proposal does not settle this for merchant acceptance. It defines "offer" by the statute's words, to make available for purchase, sale or exchange, and lists five examples of a service provider offering or selling to a person in the United States: directly soliciting a purchase, advertising the stablecoin as available to US buyers, answering an unsolicited inquiry with willingness to sell, advising buyers how to evade location checks, and contracting to sell one whatever the form of payment. Treasury says the list is not exhaustive. Merchant acceptance comes up only in Treasury's discussion of an alternative, offshore framework for foreign issuers, where it asks whether facilitating US merchant acceptance should be treated as evidence of directed selling efforts into the United States.

For an acquirer or ISO, that leaves an open question rather than an answer. Whether a particular acceptance product makes its provider a digital asset service provider, and whether that provider offers or sells stablecoins when it settles them, is a question for the provider's counsel and for the final rule. What a merchant-services team can do is make sure it knows who in the chain is taking that position.

What Acceptance Looks Like Today

Two different things tend to get called stablecoin payments, and they have different consequences.

The first is network settlement. In December 2025 Visa said US issuer and acquirer partners could settle their obligations to Visa in Circle's USDC, with Cross River Bank and Lead Bank the first to do so, over the Solana blockchain. Visa said the change makes no difference to the consumer card experience, and that broader US availability was planned through 2026. This is settlement between Visa and the banks on either side of the transaction. Nothing in the announcement changes the card sale itself for the merchant.

The second is a customer paying the merchant in stablecoins. Stripe's documentation is a clear example. As of October 2026 it lists USDC on several networks, plus USDP and USDG marked as US-only, presentment in US dollars, and settlement into the merchant's Stripe balance in local currency. Stripe's US price is 1.5% of the transaction, against 2.9% plus 30 cents for a domestic online card payment. The same page says:

  • There is no dispute support. Stripe says the merchant will not have disputes that turn into chargebacks.
  • Refunds go back as stablecoins to the customer's original wallet.
  • Customers are limited to $10,000 per transaction.
  • Connect platforms can enable it for connected accounts.

The second model is the one that changes a merchant's risk profile, and it is the one to understand before boarding.

What Changes for Merchant-Services Teams

  • Chargebacks. A stablecoin payment is not a card transaction, so card-network dispute rights do not apply, and Stripe's product offers no dispute process of its own. That moves the risk of a bad sale from the merchant to the customer. It reads well in a risk review, and it is also a reason to ask why a merchant with a high card dispute ratio wants to add it.
  • Refunds. On Stripe, refunds go back as stablecoins to the wallet that paid, not to a card or bank account. Support teams should know that before a merchant's first refund request.
  • Sanctions. OFAC may add digital currency addresses to SDN entries and says its listings are not likely to be exhaustive. A US person who identifies a wallet it believes belongs to a blocked person must block the digital currency and report it. Ask the acceptance provider how it screens paying wallets.
  • Frozen funds. Permitted issuers must be able to freeze stablecoins under a lawful order. A merchant that holds a stablecoin balance, rather than settling to dollars, carries that risk on the balance.
  • Marketing. The Act makes it unlawful for anyone to represent that payment stablecoins are backed by the full faith and credit of the United States, government-guaranteed or federally insured, and unlawful to market a product in the United States as a payment stablecoin unless it is issued under the Act. Merchant-facing sales material is not exempt.
  • Which coins. From 18 July 2028, a stablecoin that no permitted issuer issued cannot be offered or sold to US persons by a service provider. A merchant integration built around a particular token should be checked for whether its issuer has, or is seeking, permitted status.

What to Do Now

  1. Ask any processor or partner that offers stablecoin acceptance whether it considers itself a digital asset service provider under the Act, what licences it holds, and how it intends to meet the July 2028 prohibition.
  2. Confirm whether the merchant will settle in dollars or hold stablecoins. Holding a balance brings the freeze and redemption questions onto the merchant's books.
  3. Add stablecoin acceptance to the underwriting questions for merchants with elevated chargeback ratios, and record why the merchant wants it.
  4. Give support staff the refund flow in writing before the first merchant goes live.
  5. Review any sales or merchant-facing material that describes stablecoins as insured or government-backed.
  6. Watch for the final OCC and Treasury rules. The definitions that decide who is covered are still proposals, and the comment period on Treasury's closes on 19 October 2026.

Nothing in the Act requires an acquirer or ISO to offer stablecoins, and nothing in it changes how a card transaction is processed. What it does is set two dates: from 18 January 2027 only licensed issuers may issue a payment stablecoin in the United States, and from 18 July 2028 service providers may sell only those issuers' coins to US persons. Who counts as a service provider is the part still being written, and it is close enough to plan around now.

Tags

About the author

Kyle Hall

Kyle Hall

Founder

Kyle Hall is a fintech entrepreneur, software engineer, and marketing strategist with over a decade of experience in high-risk payment processing and SaaS development. He is the CEO of PayKings, a leader in high-risk merchant services, and the founder of PulseCRM, a purpose-built CRM platform for the payments industry. Kyle specializes in building custom payment processing systems and growth strategies that empower merchant services providers to scale and succeed in the digital marketplace.

Now onboarding software partners

Turn your software into a payments business.

We sell it, board it, underwrite it, and run it. You add a revenue line to your platform without adding headcount.

Built for vertical SaaS platforms ready to monetize payments.

PCI DSS compliantSOC 2 Type II99.9% uptimeMulti-processor