Should your business accept stablecoins?

This is the whole rubric. There is no form in front of it, no score at the end of it, and no email address anywhere on this site.

Ten questions. Work through them in order against your own business. Where a payment processor's published terms answer part of a question, this page quotes the terms and gives the date they were read. Where the honest answer is no, the criterion says so. Where the question stops being a business question and becomes a licensed professional's question, the criterion stops and says who to ask.

As of 2026-08-24, every small-business guide to accepting stablecoins that this team could find was published by a company that sells the rail ². That is the reason this page exists. It is not a reason to distrust those guides, which are often accurate about their own product. That survey of guides was not run again for edition 2 ¹⁵. This page carried fourteen sources in edition 1, and nine of them were opened again on 2026-09-07 ¹⁵. Four were not re-opened and keep their 2026-08-24 reading dates: the rail-published merchant guide ², the FinCEN and OFAC notice ⁵, the IC3 annual report ⁷ and the Malwarebytes post ⁸. One, a news report, refused this site on the day of the check and also keeps its earlier date ¹³. The seven sources numbered from ¹⁵ down this list are new to this edition and were read for the first time on 2026-09-07.

Edition 2, checked 2026-09-07 ¹⁵. Three criteria changed and the rest came back unchanged. Criterion 1 carries corrected figures, because three of the four numbers the earlier edition quoted for one processor were not on the page it cited ¹¹⁶¹⁷. Criterion 3 no longer says this page has read no processor's dispute terms, because one processor's terms have now been read and the answer in them is blunter than expected ¹⁶. Criterion 8 carries the statute check the earlier edition promised, two comment deadlines, 2026-10-19 and 2026-10-20, both ahead of the 2026-09-23 edition date, and a finding that on 2026-09-07 no final rule existed ^18121920; its paragraph on the EU guidelines is also corrected, because re-reading them showed they do set a training cadence after all ¹⁰.

Edition 3, checked 2026-09-23 ¹⁵. One fact changed: criterion 8's CLARITY Act sentence now states the cloture vote's outcome — failed, 49 Yea to 50 Nay — in place of the earlier "nothing about the outcome is known" ²². No other criterion was re-checked this edition.

1. What you would actually be paid in, and where it lands

The question: if a customer pays in a stablecoin, what arrives in your bank account, and when?

What to look at in your setup. Which processor you already use. Whether you want dollars in the account you have now, or the stablecoin itself. Which country you are in, and which countries your customers are in.

What the published terms say, read 2026-09-07. These figures come from Stripe's own product documentation this edition, because the earlier edition took them from a newsroom post that did not carry most of them ¹¹⁶. Stripe lists customer locations as Global, excluding sanctioned countries; accepts USDC on the Tempo, Ethereum, Solana, Polygon and Base networks, with USDP and USDG in narrower US-only forms; presents prices in USD, with other currencies in private preview; and settles completed payments into your Stripe balance in your local currency ¹⁶. A single customer transaction is capped at 10,000 USD ¹⁶. On Stripe's published pricing page the same day, stablecoins are priced at 1.5% of the transaction amount in USD in the Payments block, and at 0.8% per successful transaction in the Link block, where that 0.8% is marked a promotional rate through January 1, 2027 with 0.2% added after that ¹⁷. Two prices on one page on one day is what the page says; which one applies to you is a question to put to the processor in writing. The earlier edition of this page said merchants could be paid in the stablecoin itself — that option is in the June 2025 announcement and is not in the current product documentation, so this edition does not claim it ¹¹⁶. Shopify, Coinbase and Stripe brought USDC checkout to merchants across 34 countries, announced June 2025 ¹. PayPal has its own stablecoin, PYUSD; this edition has not read PayPal's merchant terms and quotes no figures for it.

When the answer is no. Your customers are in a country the processor excludes, or your ordinary order is larger than the per-transaction ceiling, or you want dollars at the end of it and the published rate is worse than the blended rate you actually pay on cards today — compare it against your real statement, not against the headline rate on anyone's pricing page ¹⁷.

2. Whether any of your customers would use it

The question: do you have evidence that your own customers want to pay this way, or only evidence that some businesses accept it?

What to look at in your setup. Ask your staff whether anyone has requested it in the last year. Search your own inbox and your point-of-sale notes. Count.

What the published numbers say. One survey — JD Power's merchant-services satisfaction survey — put 19% of US small businesses accepting crypto, up four points year on year ³. That is a single source and this edition has not read its method. A second, run by The Harris Poll for PayPal and the National Cryptocurrency Association, put small businesses at 34%; it was fielded 2025-10-21 to 2025-10-27 and published 2026-01-27, and its 619 respondents were payment-strategy decision makers in four consumer-facing industries rather than a general sample of small businesses ⁴. The four-in-ten figure quoted from it is all US merchants, not small ones, and PayPal sells the rail. Acceptance figures describe other businesses. None of them is evidence about your customers. Both were checked again on 2026-09-07 and both came back unchanged: the PayPal and Harris release still carries its figures, the same field window, the same 619 respondents and a stated precision of plus or minus 3.9 percentage points at 95% confidence ⁴; the JD Power release still carries the 19% sentence word for word, read through a reader proxy because jdpower.com refuses this site directly ³.

When the answer is no. Nobody has asked, and you cannot name a customer or a segment who would use it. Acceptance costs you setup, reconciliation and a new failure mode. Demand you cannot name will not pay for that.

3. What happens when a payment goes wrong

The question: after a payment is disputed, who can reverse it, on what grounds, within what window, and who ends up out of pocket?

What to look at in your setup. Your dispute rate on cards over the last twelve months. Whether you ship or deliver before a payment is confirmable. Whether you have ever had to reverse a payment yourself as a goodwill gesture.

What one processor's published terms say, read 2026-09-07. Stripe's product documentation for stablecoin payments lists dispute support: no ¹⁶. Its own explanation is that the customer authenticates the payment with their bank, so — in its words — you won't have disputes that turn into chargebacks with funds withdrawn from your Stripe account ¹⁶. Refunds are supported, in full and in part, but a refund is always returned as stablecoins to the customer's original wallet, not as dollars to a card ¹⁶. On the same processor's published pricing, a dispute received on a card payment carries a $15.00 fee, and that is the comparison worth holding in your head: the card product has a dispute process with a price on it, and the stablecoin product has neither ¹⁷.

What that means, and what it does not. It does not mean nothing can go wrong. It means the reversal mechanism you are used to is absent, so whatever recourse exists comes from your contract with the processor and from your own refund procedure rather than from a network's dispute rules. One processor's terms have now been read. No other processor's have. If you use a different one, find the dispute section of its terms and read it end to end; the asymmetry to confirm in writing is the same one.

When the answer is no. Your dispute rate is high, or you release goods before delivery is confirmable, or your processor's terms carry no dispute process at all and you have nothing of your own to put in its place. Any of those makes the recourse gap the whole decision.

4. Bookkeeping and tax treatment

The question: how does this appear in your books, and what does it change at year end?

What to look at in your setup. Who does your bookkeeping, what software they use, and whether that software already has a place to put a payment that arrives in something other than dollars. Whether your accountant has handled this for another client.

Where this stops. Here. Tax treatment and accounting treatment are a licensed accountant's work, and this site holds no accounting licence and gives no tax advice. Take these questions to your CPA before you turn anything on: how is each payment recorded at the moment it is received, what happens between receipt and settlement to dollars, what has to be tracked per transaction, what changes on the return, and what does the accountant need from the processor's reports to do the work without re-keying it.

When the answer is no. Your accountant has not done this before and does not want to learn it on your books. That is a real no, and it is cheaper than the alternative.

5. Whether to hold any of it

The question: settle everything to dollars, or keep a balance?

This rubric takes a position and it is a narrow one. It will not tell you whether to hold a stablecoin balance. What a business keeps on its balance sheet is investment-adviser territory, this site holds no licence, and a web page cannot know your cash position.

What to look at in your setup. Whether you need every dollar of receipts for payroll and stock in the same month. Whether anyone in the business is authorised to make a treasury decision at all.

Where this stops. Take the holding question to a licensed adviser, together with your accountant. The processors named in criterion 1 publish an option to settle to a bank account in dollars, which is a fact about their product, not a suggestion about your business ¹.

The one position this page takes. A treasury decision made alone off a web page is the part of this that goes wrong. Including off this web page.

6. Counterparty and processor risk

The question: between your customer's payment and the money reaching your bank, who is holding it, and what happens if they stop?

What to look at in your setup. Get it in writing from the processor: who holds the funds at each step, under what agreement, and what the published procedure is if a payment is held or an account is paused. Ask what happens to funds in flight.

What the record shows. A stablecoin's issuer can act at the token layer. Circle operates a freeze and blocklist capability on its own token, which this edition has from a secondary source rather than from Circle's own documentation. In April 2026 FinCEN and OFAC published a joint proposal on real-time sanctions screening in the Federal Register; by its terms it binds permitted payment stablecoin issuers, not the merchants who accept the tokens ⁵.

When the answer is no. You cannot get the custody chain in writing. A verbal answer from a sales representative is not the answer to this question.

7. Fraud, from the merchant's side of the counter

The question: which of the ways this goes wrong are aimed at you rather than at the customer?

The procedure that matters most. Confirm receipt in your processor's dashboard, or on a block explorer, before you release goods. Never on the strength of a screenshot, an email, a text message or a phone call from the buyer. Make that a written rule for whoever is on the counter, because it is the one that will be tested.

What the record shows. The FBI's IC3 reported 181,565 complaints and about $11.366 billion in crypto-linked fraud losses for 2025, with complaints from people aged 60 and over accounting for more than $7.7 billion, up 37% year on year ⁷. Crypto kiosk complaints came to 13,460 and about $389 million, up 58% ⁷. Address poisoning — a fraudulent address planted where a real one is expected — is a named pattern in public advisories. In August 2026 Malwarebytes reported that fake crypto checking tools are themselves being used to drain wallets, the same template rebranded under several names ⁸. That last one is the reason this site asks you to paste nothing anywhere: pasting an address into an unfamiliar tool is the attack.

When the answer is no. Nobody in the business will own the confirm-before-release rule. Then this is a fraud loss waiting for a busy Saturday.

8. What the rules require now, and the dates that change it

The question: is the rule you would be relying on actually in force?

What the record shows, read on 2026-09-07. The GENIUS Act was signed on 2025-07-18 and had not taken effect as of 2026-09-07 ¹⁸. Section 20 of the statute — read this edition, not summarised from a tracker — says the Act takes effect on the earlier of 18 months after enactment, which is 2027-01-18, or 120 days after the primary Federal payment stablecoin regulators issue any final regulations implementing it ¹⁸. A Federal Register search over rule documents, run the same day, returns proposed rules and notices and no final rule from those regulators, so on that date the outer date was the operative one ²⁰. Rulemaking was live at that reading, and a comment window is the part of it you can act on while it stands open: the FDIC board approved a proposed rule on 2026-04-07, it published on 2026-04-10 and its comment period closed on 2026-06-09 ¹¹⁶; Treasury's proposal implementing section 3 published on 2026-08-18, with comments due by 2026-10-19 ¹². A separate SEC proposal, Regulation Crypto Assets, published on 2026-08-21 with comments due 2026-10-20; it governs offering and selling crypto assets as investments and does not govern a shop that accepts a dollar-denominated stablecoin in payment for goods ¹⁹. The CLARITY Act's cloture vote on the motion to proceed took place on 2026-09-15, the date the Senate's own tentative schedule pointed to once its state work period ran to 2026-09-11 ²¹, and it failed: the Senate's own roll call record, Vote No. 234, gives the result as 49 Yea to 50 Nay against the 60 votes needed to invoke cloture ²². The bill stayed on the Senate's calendar, and this page found no primary-source record of a rescheduled vote as of 2026-09-23 ²². For readers in the EU: ESMA's knowledge-and-competence guidelines under MiCA Articles 68(5) and 81(7) ask crypto-asset service providers to review their staff's knowledge and competence at least once a year and to keep it current through continuous professional development or training ¹⁰. No external certification is mandated — the competence assessment may be run by the provider itself or by an external body — but a cadence is set: the guidelines tell providers to determine an adequate minimum number of hours of continuous professional development or training per year for the staff concerned, and the guidelines' own worked example for the least complex range of information is 10 hours, with 20 for staff giving advice ¹⁰. The earlier edition of this page said no cadence was set; re-reading the guidelines on 2026-09-07 showed that was wrong, and the Register carries the correction as its own dated entry ¹⁰. The obligation binds those providers rather than merchants. The guidelines are dated 2026-01-28 and apply six months after their publication on ESMA's website in all official EU languages, so the 2026-07-28 date is derived rather than printed in them, and it depends on when that all-languages publication actually happened ¹⁰.

A limitation this edition closed, and one it still carries. The earlier edition read the effective-date rule from policy trackers rather than from the statute and said so on its face; the statute has now been read, and the trackers were right ¹⁸⁹. Still carried, and stated rather than hidden: nobody here had read the Treasury or the SEC proposal in full — only their published dates, their dockets and their own abstracts of themselves ¹²¹⁹.

Where this stops. Anything about how a rule applies to your specific business in your specific state is an attorney's question.

When the answer is no. You are in a regulated line of business where a rule change would force you to unwind the decision. Waiting until an effective date costs you nothing; rebuilding does.

9. What you tell the customer, before and after

The question: what does your published refund policy say the day after you turn this on?

What to look at in your setup. Your current refund policy, your receipt template, and your order-confirmation email. Read them as though a payment had arrived in something other than dollars, and mark every sentence that stops being true.

One published term to write into the policy. On the one processor whose terms this edition has read, a refund on a stablecoin payment is always returned as stablecoins to the customer's original wallet ¹⁶. A customer who paid in a stablecoin and expects dollars back is a complaint your current policy does not answer.

What to write. How a refund is issued and in what, how long it takes, what a customer should do if a payment does not appear, and who they reach. Publish it before the first payment, not after the first complaint.

The mistake this page expects. Turning this on with the refund policy you have today, unchanged. It was written for cards.

When the answer is no. Nobody has time to rewrite the policy this month. Then nobody has time to accept stablecoins this month either.

10. Staff and process readiness

The question: who does the work on an ordinary Tuesday?

What to look at in your setup. Name the person who reconciles the payments, the person who answers the question at six in the evening, and the person who covers both when the first one is on holiday. Write down the steps they follow. If the steps live only in one person's head, that is the finding.

When the answer is no. One person, no written procedure, no cover. Accepting a new payment method adds a reconciliation path and a support path. Both need an owner with a name.

How to read this rubric

It reports two things and nothing else: facts about your own setup, and what the payment processors' and regulators' published documents say on the date each was read. It does not predict a saving, quote a testimonial, or rank any processor. Where a question belongs to a licensed accountant, adviser or attorney, it says so and stops.

Every page on this site carries a valid_as_of date. This one was written on 2026-08-24, checked again on 2026-09-07, in the middle of live rulemaking, and checked a third time on 2026-09-23 for the CLARITY Act outcome only ¹⁵²²; parts of criterion 8 carry dates that fall after that last check: the Treasury comment deadline of 2026-10-19, the SEC's of 2026-10-20, and the statute's outer effective date of 2027-01-18 ^15121918. Nothing on this page was re-read after 2026-09-23, and nothing on it is updated after that date unless a later edition says so; the Register holds the dated record up to the same date ¹⁵.