Stablecoin Payments is a Payment Method that lets a business accept stablecoin payments, but the settlement is handled through a Settlement Services Provider rather than the platform itself. That single structural fact reshapes what a founder needs to check before going live. The risks and obligations described below come from the published terms; the verification steps are recommendations, not terms of the agreement.
Who you are actually contracting with
The terms are explicit that a Settlement Services Provider is a Financial Provider. By using Stablecoin Payments, you agree to the applicable Settlement Services Terms, and those terms form an agreement between you and that provider. Appendix A lists the providers and their respective Settlement Services Terms.
Beyond your platform agreement, the settlement services terms form a separate agreement between you and the provider. That means the entity you rely on for settlement is a counterparty in its own right, not just a hidden back end.
Terms that can change without notice
The platform may add or remove Settlement Services Providers, and the Settlement Services Terms may be updated by a provider, at any time without notice to you. Continued use of Stablecoin Payments, and payment of related fees after the relevant changes, is deemed acceptance of updated terms.
This is the operational reason to assign an owner for periodic review. A silent provider swap is permitted by the terms, so nobody should assume the provider named at launch is the provider settling next year.
Instructions go to the provider, not the platform
Where you provide instructions relating to Stablecoin Payments through the dashboard, such as the instruction of a refund in stablecoins, you are providing those instructions directly to the Settlement Services Provider. The practical consequence: your refund workflow depends on provider-side address handling, and errors there are contemplated by the liability section.
What is allowed, and what you cannot promise
- You may only use Stablecoin Payments to sell your goods and services to Customers.
- You must not make representations to your Customers that contradict, or are inconsistent with, the terms.
- Transactions involving stablecoins may be subject to Taxes, and tax forms may be sent to Customers using information they provided.
The representation limit matters for marketing. A founder-facing pitch that promises certainty about settlement outcomes, or that describes the product in ways the terms do not support, sits awkwardly against this clause. Sales copy and support scripts should be reviewed alongside the terms.
Depeg events and exchange-rate risk
If a Depeg Event occurs, the platform and the provider may immediately either suspend Stablecoin Payments for the affected stablecoin, including suspending new exchanges of fiat currency for it, or continue providing Stablecoin Payments at the affected stablecoin's prevailing stablecoin-to-fiat market exchange rate.
Either outcome is permitted, so a launch plan should specify who monitors, who decides, and how customers are told. The platform is also not liable for losses, damages or costs arising from a Depeg Event or actions taken in connection with one. That includes any difference between the exchange rate applicable at the time you accept payment and the rate at which the provider executes the exchange, if it chooses to do so.
If the provider executes the exchange at a different rate, as that liability carve-out contemplates, the amount that settles may differ from what you would expect at acceptance. Founders should treat this as a scenario to plan for rather than a certainty, and should not present any particular conversion outcome to customers.
Wallet and data errors are your exposure
Use of the Settlement Services is at your own risk, and, to the maximum extent permitted by law, the platform disclaims all liability with respect to that use. It is similarly not liable for losses, damages or costs if you or any of your Customers provide incorrect transaction information, including an inaccurate or incomplete Deposit Address, or an incorrect wallet address to receive refunds.
The terms do not describe what controls, if any, a merchant must operate. That gap is where wallet-hygiene controls belong: a documented deposit-address confirmation step, a refund-address capture process, and a named reviewer before any address is entered.
A pre-launch checklist
- Name the Settlement Services Provider in Appendix A and store a copy of its Settlement Services Terms with the launch file.
- Assign an owner and a review cadence for provider changes and updated terms, since changes may arrive without notice.
- Write down the depeg decision: suspend or continue, who decides, and how support responds.
- Document deposit-address and refund-address confirmation steps, with a second reviewer.
- Audit customer-facing copy and support scripts against the representation limit.
- Coordinate with finance on tax treatment of stablecoin transactions before the first sale is accepted.
What the source does not say
The terms do not state which Settlement Services Providers appear in Appendix A, what fees apply, or settlement timing. They do not specify whether you can choose a provider or object to a change. They do not define the conditions that trigger a Depeg Event, nor any notice period for suspension. They do not describe required merchant controls for wallet addresses, refunds, or recordkeeping, and they do not address what happens to in-flight transactions during a suspension. Treat every one of those as an open question to resolve with the provider and your own advisers before launch.
Capitalized terms used in the Payment Method Terms that are not defined there take the meaning given in the platform's Services Agreement. Regional Terms apply based on your account country, so confirm the section that governs your entity rather than assuming a single global standard.