Welcome to USD1makers.com

USD1makers.com is part of a set of educational pages about USD1 stablecoins. On this page, the focus is the word "makers": the people and teams who design, build, run, and improve products that use USD1 stablecoins. The goal is clarity rather than hype.

You will see a few recurring organizations cited throughout this page:

BIS (Bank for International Settlements, a global forum for central banks) for research and policy discussion on money and payment systems.^[1]
FSB (Financial Stability Board, a global body that coordinates financial stability work) for high-level recommendations on stablecoin arrangements.^[2]
FATF (Financial Action Task Force, an intergovernmental body that sets standards on illicit finance) for guidance on anti-money laundering controls in virtual asset activity.^[4]
IOSCO (International Organization of Securities Commissions, a global forum for securities regulators) for market integrity and investor protection considerations in crypto and digital asset markets.^[6]
IMF (International Monetary Fund, an international financial institution) for economic analysis of stablecoins and related risks.^[5]

This page is for general education only. It is not legal advice, tax advice, or investment advice. Rules vary by place and can change quickly. If you are building with USD1 stablecoins at scale, it is normal to consult qualified counsel and experienced security reviewers.

What USD1 stablecoins are

A stablecoin (a digital token designed to keep a steady price) is a type of digital asset (a transferable unit recorded in software) that aims to hold a stable value in terms of another asset, most often a national currency such as the U.S. dollar. USD1 stablecoins, as used on USD1makers.com, is a descriptive phrase for any digital token that is intended to be redeemable one for one for U.S. dollars.

That definition is intentionally generic. Many different projects can issue stablecoins, and different stablecoins can use different designs to try to stay stable. For makers, the key point is that the word "stablecoin" is not a promise. Official reports warn that "stablecoin" is a market term, not a guarantee of stable value.^[2]

To understand USD1 stablecoins, it helps to separate three ideas:

Unit: a unit of USD1 stablecoins is a digital claim or instrument that is meant to track one U.S. dollar.
System: the rules that govern creating, transferring, storing, and redeeming USD1 stablecoins.
Participants: issuers (entities that create and redeem tokens), wallet services, exchanges, payment firms, and app teams that make the system work in practice.

When makers say they are "building with stablecoins," they usually mean they are building user experiences that move stable value across a network, while minimizing volatility (price swings), friction (unnecessary steps), and risk (ways things can go wrong). International work on stablecoins has highlighted that stablecoin arrangements can introduce run risk (a rush to redeem) and payment-chain risk (failures in the systems that move value).^[3]

Who makers are in the USD1 stablecoins world

"Makers" is a broad label. In the USD1 stablecoins context, it can include:

Product builders: founders, product managers, designers, and engineers who create apps that let users hold and move USD1 stablecoins.
Payments builders: teams building checkout, invoicing, merchant tools, and payout systems that use USD1 stablecoins as a payment option.
Wallet builders: teams building wallets (apps or devices that help users control digital assets) and custody services (holding assets on behalf of users).
Liquidity builders: market makers (traders or firms that provide buy and sell quotes to keep markets active) and treasury teams that support conversion between USD1 stablecoins and other assets.
Compliance builders: teams implementing KYC (Know Your Customer identity checks), AML (anti-money laundering controls), and sanctions screening (checking people or firms against restricted lists) so services can operate responsibly.^[4]
Infrastructure builders: teams operating nodes (computers that validate and relay network data), building APIs (interfaces that let software talk to other software), and maintaining reliability for high-traffic systems.

A useful mental model is that makers sit between two worlds:

The user world, where people care about speed, cost, privacy, and ease of use.
The system world, where blockchains, custody setups, banking access, and policy rules shape what is possible.

If you are new to this, do not worry about mastering every technical detail at once. The maker job is often to make complex systems feel simple, without hiding the tradeoffs.

Why makers use USD1 stablecoins

USD1 stablecoins are attractive to makers when they solve specific problems better than older rails (legacy payment networks). The most common reasons include:

Stable unit for pricing and settlement. If a user pays for a service priced in U.S. dollars, USD1 stablecoins can help keep the payment amount steady in dollar terms, even if the user is also interacting with other digital assets that move a lot.

Programmable transfers. Smart contracts (software that runs on a blockchain and can move assets based on rules) can automate escrow (holding funds until conditions are met), split payments (sharing a payment across parties), and time-based releases (scheduled payouts). These patterns are often discussed in work on tokenization (turning claims into digital tokens) and new payment system designs.^[1]

Speed and reach. On some networks, transfers can settle quickly across borders. For certain use cases, a user can send USD1 stablecoins at any time of day, without waiting for local banking hours. CPMI-IOSCO (Committee on Payments and Market Infrastructures and IOSCO, two standard-setting bodies) discuss how stablecoin arrangements could be used in cross-border payment flows, while stressing the need for sound oversight and risk controls.^[7]

Reduced operational friction for global teams. A business that pays contractors in many countries can reduce the number of local bank transfers by paying in USD1 stablecoins, assuming the contractor can safely receive and convert the funds.

New product shapes. Some apps are built around onchain (recorded on a blockchain ledger) behaviors like composability (the ability for software pieces to connect) and atomic settlement (all parts of a transaction succeed together or none do). USD1 stablecoins can serve as a stable unit inside those designs.

Those benefits come with tradeoffs. Official sector writing focuses heavily on risks such as redemption uncertainty, reserve quality, and operational failure.^[2]^[8]

How USD1 stablecoins work in practice

A maker does not have to become a protocol engineer, but it helps to understand the lifecycle of USD1 stablecoins.

1) Creation: getting USD1 stablecoins into circulation

In many fiat-backed models (stablecoins backed mainly by traditional financial assets), USD1 stablecoins are created when an issuer accepts U.S. dollars (or sometimes equivalent value) and issues new units of USD1 stablecoins.

Creation can happen directly with an issuer or through intermediaries such as exchanges or payment firms. The U.S. Treasury interagency report emphasizes that different arrangements provide different rights and processes for creation and redemption, and that these differences matter for risk.^[8]

2) Transfers: moving USD1 stablecoins

After issuance, USD1 stablecoins can move between users via a blockchain (a shared database that many computers keep in sync). Transfers are typically authorized with a private key (a secret number that authorizes spending).

A transfer may feel instant in an app, but the network still needs confirmations (the process of the network agreeing that a transfer is included). Finality (the point when a transfer is effectively irreversible) depends on the network and the surrounding services.

3) Storage: holding USD1 stablecoins safely

Holding can look like:

A self-custody wallet (user holds keys).
A custodial wallet (a firm holds keys for the user).
A business treasury setup (operational accounts and controls for an organization).

Storage is a major risk point because mistakes, malware (software designed to harm), or fraud can lead to permanent loss.

4) Redemption: getting back to U.S. dollars

Redemption is the promise at the heart of many stablecoins. USD1 stablecoins are removed from circulation when a holder redeems units of USD1 stablecoins for U.S. dollars and the issuer burns (destroys) the units redeemed.

Key maker questions include:

Who is eligible to redeem?
Are there minimums or delays?
What fees apply?
What happens during stress?

Both the U.S. Treasury report and the IMF highlight that redemption terms and reserve liquidity can influence run dynamics and user confidence.^[5]^[8]

Core building blocks makers rely on

A good maker guide does not start with buzzwords. It starts with the small parts you assemble.

1) The ledger layer

A blockchain (a shared database that many computers keep in sync) is the ledger that records who owns what and which transfers happened. Networks vary widely:

Some are designed for very high throughput (many transactions per second).
Some prioritize decentralization (no single operator controls the system).
Some emphasize compatibility (how well they work with common tools and wallets).

For makers, what matters is user experience, reliability, and risk. For example, if a network becomes congested (too many transfers competing for space), a user may see higher fees or slower confirmations.

2) Wallets, keys, and custody

A wallet (software or a device that helps a user control digital assets) is the main interface most people touch. Under the hood, control usually comes down to keys:

A private key (a secret number that authorizes spending) gives control over funds.
A public address (a public identifier that can receive funds) is what other people use to send funds.

Two broad custody patterns show up:

Self-custody (user holds their own keys). The user controls the private key. This can improve user control and reduce reliance on a single firm, but it can increase the risk of loss from mistakes, phishing (tricking someone into revealing secrets), or device compromise.

Custodial setups (a service holds keys for the user). A firm holds keys and manages transfers. This can feel easier for new users, but it adds counterparty risk (risk that the firm fails or misbehaves) and creates obligations around safeguarding and compliance. IOSCO policy work highlights custody and client asset protection themes in crypto and digital asset markets.^[6]

Many makers use a hybrid: self-custody for advanced users, custodial options for beginners, and clear explanations about what each option means.

3) Onramps, offramps, and conversion

An onramp (a way to convert bank money into digital assets) and an offramp (a way to convert digital assets back into bank money) sit at the edge of many USD1 stablecoins experiences.

Onramps and offramps can be banks, money transmitters, payment firms, exchanges, or other regulated entities, depending on the place and the structure. They bring practical constraints:

Identity checks may be necessary.
Fees can vary.
Transfer times can vary.
Availability differs by country and by bank.

Makers often underestimate how much the user experience depends on these conversion points.

4) Smart contracts and application logic

A smart contract (software that runs on a blockchain and can move assets based on rules) can help makers build:

Escrow and milestone releases.
Subscriptions (recurring payments).
Conditional payouts (payments that happen only if certain conditions are met).
Revenue shares.

Smart contracts also introduce new failure modes. Bugs can lock funds or route funds incorrectly. A maker should treat smart contract design as safety-critical.

5) Monitoring, support, and audit trails

If you run a product that moves value, you need monitoring.

That includes:

Transaction monitoring (detecting unusual flows).
Support workflows (handling mistakes, wrong addresses, or refund requests).
Routing logic (choosing a path that balances cost and reliability).
Audit trails (records that help explain what happened).

FSB recommendations emphasize governance, risk management, and clear responsibilities for stablecoin arrangements, which should translate into how makers run operations day to day.^[2]

Product design choices that matter

There is no single correct way to build with USD1 stablecoins. But the same design questions keep showing up across products.

Custody choice shapes everything

If you choose self-custody, you are making a product for users who can handle key management. You will need clear guidance on backup phrases (recovery words that restore a wallet) and strong warnings about phishing and fake support.

If you choose custodial setups, you are taking on operational duties. You will need safeguards such as:

Segregation of funds (keeping user funds separate in records and operations).
Access controls (limits on who can move funds).
Incident response (a plan for theft, outages, or mistakes).
Clear terms that explain who controls the funds and what protections exist.

Fees are not just math

Network fees (often called gas fees, meaning the fee paid to process a blockchain transaction) are confusing for many users. Makers can improve trust by showing estimates before a user sends USD1 stablecoins, explaining who pays the fee, and setting clear expectations about delays during congestion.

Finality changes how refunds work

Finality (the point when a transfer is effectively irreversible) is a key difference between blockchain transfers and some card payments. If a user sends USD1 stablecoins to the wrong address, there is usually no universal reversal button.

That does not mean refunds are impossible. It means refunds must be implemented as a new payment, not as a reversal. Good maker experiences make copy-and-paste less risky by using address books and warnings, and by confirming destination details for larger transfers.

Interoperability and network choice

Interoperability (the ability for systems to work with one another) matters when users move between wallets, exchanges, and apps. For makers, network choice affects:

Fee levels and fee volatility.
Reliability and downtime risk.
Tooling and developer support.
User familiarity.

A common maker mistake is to treat network choice as purely technical. It is also a user trust decision.

Transparency must be usable

Users and partners often ask: "What backs USD1 stablecoins?" "Can I redeem quickly?" "Who is responsible if something breaks?"

Makers can provide clarity by presenting:

Plain explanations of reserve assets (assets held to support redemption).
A summary of redemption terms.
Links to public reports and disclosures.

The point is not marketing. The point is helping users make informed choices.

Global reality: place-by-place differences

Makers often build for an internet-scale audience, but money still has local rules. Even if USD1 stablecoins move across a global ledger, the user experience usually touches local systems at the edges: bank transfers, card purchases, cash-out options, identity checks, and tax reporting.

Instead of trying to memorize every rule, makers can think in three layers:

Layer 1: Local access to U.S. dollars

Many users interact with USD1 stablecoins by buying USD1 stablecoins with U.S. dollars or selling USD1 stablecoins for U.S. dollars. Some users do this through a bank transfer. Some do it through card rails. Some do it through local payment apps.

The availability and cost of these paths differ by place. That means the same product can feel smooth in one country and frustrating in another.

Layer 2: Local access to local currency

Cross-border use usually ends with someone wanting local currency. A recipient may need to sell USD1 stablecoins for local currency to pay rent, buy groceries, or run a business.

This is where local market liquidity (how easily an asset can be bought or sold without big price moves) and local policy constraints both show up. A maker planning global payouts should expect these differences.

Layer 3: Local compliance expectations

KYC and AML expectations vary. Some services may be expected to verify identity at signup, while others may verify at cash-out. FATF guidance explains how a risk-based approach (controls scaled to risk) is commonly used in virtual asset activity.^[4]

A maker takeaway is simple: do not assume "one product experience fits everywhere." Plan for localization (adapting to local payment and policy realities) and for clear user communication.

Compliance and risk, explained plainly

Makers do not need to become lawyers to understand the basic risk map. But makers do need to know where risk concentrates.

Stable does not mean risk-free

Official reports emphasize that stablecoins can fail to keep stable value and can face runs if confidence breaks.^[2]^[5]^[8] From a maker view, common risk sources include:

Reserve risk: reserve assets may be risky, illiquid (hard to sell quickly without loss), or unclear.
Redemption frictions: redemption may be limited to certain parties or slowed during stress.
Market liquidity risk: if a user needs to sell USD1 stablecoins quickly, the price they get may depend on active markets and willing buyers.
Operational risk: outages, bugs, and human mistakes can block transfers.
Smart contract risk: contract bugs can lock or misdirect funds.
Legal and policy risk: rules can change or differ by jurisdiction.

Illicit finance risk is a real design constraint

AML and CFT (countering the financing of terrorism controls) are not add-ons for many businesses. If your product provides transfer services, you may be expected to implement controls that reduce misuse. FATF guidance explains how standards apply to virtual assets and related service firms, including the need to assess and reduce money laundering and terrorist financing risk.^[4]

Makers commonly translate this into product decisions such as:

Which users can create accounts.
When identity checks happen.
How suspicious activity is detected and handled.
What data is collected and how it is protected.

Market integrity and user protection

Stablecoin use often overlaps with trading venues and custody firms. IOSCO policy work highlights investor protection and market integrity concerns in crypto and digital asset markets, including custody, conflicts, and operational controls.^[6] Even if your product is "just payments," the surrounding market structure can affect your users.

Governance and accountability

Many failures in digital asset markets are not only technical. They are governance failures (bad incentives, weak controls, unclear accountability). FSB recommendations focus heavily on governance, risk management, and the need for oversight that matches the risks a stablecoin arrangement can create.^[2]

A maker takeaway: build with the assumption that you will need clear roles, controls, and documentation as you grow.

Security and operational discipline

Security is not a feature you add at the end. It is an operating habit.

Treat keys like critical infrastructure

If your product holds USD1 stablecoins in custody, keys are the core.

Common safeguards include:

Separation of duties (no single person can move funds alone).
Hardware security modules (specialized devices that protect keys).
Multisignature wallets (wallets that use more than one key to authorize spending).
Cold storage (keys kept offline) for reserves and treasury.
Spending limits and allowlists (pre-approved destinations).

These are not just technical ideas. They are operational controls.

Plan for user error

Users make predictable mistakes:

Sending USD1 stablecoins to the wrong address.
Falling for phishing.
Confusing networks and sending to an incompatible address format.
Assuming a transfer can be reversed.

A maker who plans for these errors can prevent many incidents. Good patterns include clear warnings, address validation, and review screens that slow users down for large transfers.

Monitor, rehearse, and learn

If you move money, you need:

Alerting for unusual flows.
Runbooks (step-by-step response plans) for outages and incidents.
Post-incident reviews (documented lessons after something breaks).

In policy language, this is operational resilience (the ability to keep working during stress). In maker language, it is the discipline that keeps users safe.

Smart contract diligence

If your product uses smart contracts, you need a review process. Many teams use:

Independent audits (external reviews).
Formal verification (math-based checks of certain properties).
Limited upgrade powers, with transparent controls.
Small initial limits, increasing over time after real-world use.

Even with strong reviews, bugs happen. Makers should build blast-radius limits (ways to prevent a single bug from harming everything).

How to evaluate USD1 stablecoins and partners

This section stays high-level on purpose. The right answer depends on your product, users, and jurisdiction.

Questions to ask about USD1 stablecoins

Who issues and redeems? Identify the issuer and the redemption route. If redemption is limited to certain customers, that affects your design.

What backs the token? Look for disclosures about reserve assets and the frequency of reporting. The U.S. Treasury interagency report stresses the value of reserve transparency and redemption confidence.^[8]

How does redemption work during stress? Ask what happens if many holders redeem at the same time.

Which ledger networks are supported? Network choice affects fees, speed, and tooling.

How deep are markets? Liquidity (how easily an asset can be bought or sold without big price moves) matters for users who need to convert.

What controls exist for safeguarding? If USD1 stablecoins are held by intermediaries in your flow, custody controls matter. IOSCO highlights custody and client asset protection themes in its policy work.^[6]

Questions to ask about service firms

If you use an exchange, wallet service, or payment firm, makers often ask:

What licenses or registrations apply where the firm operates?
What is the firm's incident history and response process?
How are user funds separated in practice?
What monitoring exists for fraud and sanctions risk?
What support channels exist for mistakes?

You do not need perfection. You need a realistic view of risk.

Avoiding common maker misunderstandings

Some misunderstandings show up repeatedly:

"Stable means guaranteed." It does not. The term is widely used, but official bodies stress that stable value is not assured.^[2]
"Onchain equals anonymous." Public ledgers can be transparent. Privacy depends on how a system is used and what data is linked.
"If it is fast, it is final." Fast settlement can still involve operational delays, compliance holds, or service downtime.
"A token is the same as a bank deposit." Bank deposits often have a legal and supervisory structure that stablecoins may not share. The U.S. Treasury report explains differences in claims and protections in plain terms.^[8]

Frequently asked questions

Are USD1 stablecoins the same as U.S. dollars in a bank?

USD1 stablecoins aim to track the value of U.S. dollars, but they are not automatically the same as a bank deposit. A bank deposit is a claim on a bank, usually within a banking supervisory system. A stablecoin is typically a claim on an issuer or an arrangement, and user protections can vary. The U.S. Treasury interagency report explains how redemption rights and protections can differ from bank deposits.^[8]

Can USD1 stablecoins lose value?

Yes. Stablecoins can trade below or above one U.S. dollar, especially during market stress or if redemption is uncertain. The FSB and the IMF discuss run dynamics and confidence shocks as key risks for stablecoins.^[2]^[5]

What should a maker explain to users in simple language?

Makers often earn trust by explaining:

Who controls the wallet keys.
How to back up access.
What fees apply.
Whether transfers are reversible.
How users can redeem or convert.

Are USD1 stablecoins useful for cross-border payments?

They can be, especially for certain business flows. But cross-border use brings local rules, conversion constraints, and extra risks. CPMI-IOSCO and the G7 (Group of Seven economies, a policy forum) highlight both potential use cases and the need for strong standards and oversight.^[3]^[7]

How do policy bodies think about stablecoins?

Different bodies focus on different risks:

The FSB focuses on financial stability risks, governance, and oversight for global stablecoin arrangements.^[2]
FATF focuses on money laundering and terrorist financing risk controls for virtual asset activity and service firms.^[4]
IOSCO focuses on market integrity, investor protection, custody, and conflicts in crypto and digital asset markets.^[6]
The IMF discusses economic implications, design features, and risk channels, including reserve quality and liquidity dynamics.^[5]

For makers, these documents are useful because they explain what supervisors and regulators worry about and why.