# Accepting stablecoin payments: what a merchant receives A merchant can receive stablecoins directly into a wallet or use a processor that handles token acceptance and credits another settlement currency. The customer’s payment asset therefore may differ from the merchant’s final balance. Before fulfillment, verify the accepted token, network, amount and completed payment status in the chosen system. Evidence: [Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments); [Stablecoin payments infrastructure](https://www.circle.com/use-case/payments) Canonical: https://degreesofsatoshi.com/encyclopedia/stablecoin-merchant-payments/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:26:58.461Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Direct receipt:** A direct wallet payment leaves the merchant holding the token until it is spent or converted. ([USDC Terms](https://www.circle.com/legal/usdc-terms)) - **Processor example:** Stripe documents stablecoin acceptance with completed payments settling in its merchant balance. ([Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments)) - **Refund:** A supported refund workflow is distinct from a card-style dispute process. ([Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments)) ## Know what lands in the merchant’s account With direct receipt, the merchant needs wallet operations, asset checking and a policy for handling token exposure. With a processor, the contract specifies accepted tokens and the currency credited to the merchant balance. Stripe’s documentation, checked on 2 October 2026, describes customers choosing a supported token and network while the completed payment settles in the merchant’s local-currency Stripe balance. This is one provider’s workflow, not a rule for all stablecoin payments. Evidence: [Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments); [USDC Terms](https://www.circle.com/legal/usdc-terms) ## A screenshot is not an order status A customer can show a transaction hash before the relevant payment is complete. In a direct transfer, inspect the actual token contract, destination, amount and execution result. With a processor, use its authenticated payment status and order association. Suppose an invoice requests 75 units on an accepted chain but the customer sends a similarly named token from another issuer. The displayed number does not satisfy the request. Token identity belongs in the acceptance rule. Evidence: [Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) ## Decide how exceptions are handled A useful payment record ties the invoice to the payment attempt, completed receipt and any refund. Duplicate notifications must not cause duplicate fulfillment; asynchronous events require a durable record of what was already processed. Partial payments, expired invoices and refunds need explicit policies. Stablecoin support does not make those ordinary commerce questions disappear. Keep customer personal information out of public transaction memos. Evidence: [Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments); [Webhook delivery and duplicate events](https://docs.stripe.com/webhooks); [Why digital privacy matters](https://ethereum.org/en/privacy/) ## Questions ### Does accepting stablecoins require the merchant to keep them? Not necessarily. Some processors accept a token from the customer and settle a different currency to the merchant. Direct wallet receipt usually leaves conversion to the merchant or its chosen provider. Evidence: [Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments); [USDC Terms](https://www.circle.com/legal/usdc-terms) ## Claims and scope ### stablecoin-merchant-payments-quick-answer A merchant can receive stablecoins directly into a wallet or use a processor that handles token acceptance and credits another settlement currency. The customer’s payment asset therefore may differ from the merchant’s final balance. Before fulfillment, verify the accepted token, network, amount and completed payment status in the chosen system. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-merchant-payments-fact-direct-receipt Direct receipt: A direct wallet payment leaves the merchant holding the token until it is spent or converted. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-merchant-payments-fact-processor-example Processor example: Stripe documents stablecoin acceptance with completed payments settling in its merchant balance. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-merchant-payments-fact-refund Refund: A supported refund workflow is distinct from a card-style dispute process. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Stablecoin payments](https://docs.stripe.com/payments/stablecoin-payments) — Stripe. Processor-specific stablecoin acceptance, refund and merchant balance behavior. Locator: Payment flow; refunds; disputes; settlement. Retrieved: 2026-10-02T18:51:05.825Z. - [Stablecoin payments infrastructure](https://www.circle.com/use-case/payments) — Circle. Issuer-described payment use cases, not independent proof of advertised costs or delivery times. Locator: B2B payments; remittances; payroll; merchant payments. Retrieved: 2026-10-02T18:51:04.998Z. - [USDC Terms](https://www.circle.com/legal/usdc-terms) — Circle. Issuer redemption eligibility, dollar denomination, third-party market value and supported-chain limitations. Locator: USDC; redemption; third-party services and risk disclosures. Retrieved: 2026-10-02T18:51:05.108Z. - [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) — Ethereum Improvement Proposals. Names/symbols, balances and Transfer events do not independently authenticate the issuer. Locator: Token methods and events. Retrieved: 2026-10-02T18:51:07.936Z. - [Webhook delivery and duplicate events](https://docs.stripe.com/webhooks) — Stripe. Payment event processing and idempotent reconciliation; this does not establish chain settlement. Locator: Event delivery; duplicate events; ordering. Retrieved: 2026-10-02T18:52:46.705Z. - [Why digital privacy matters](https://ethereum.org/en/privacy/) — ethereum.org contributors. Supports the public-ledger privacy limitation; does not establish a private transaction or universal privacy guarantee. Locator: Privacy can be the default: public and transparent ledger. Retrieved: 2026-10-02T19:25:01.807Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Accepting stablecoin payments: what a merchant receives.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/stablecoin-merchant-payments/