Welcome to requestUSD1.com

requestUSD1.com is an educational page about how to request USD1 stablecoins in a way that is clear, safe, and easy for other people to pay.

When this page says USD1 stablecoins, it is using that phrase in a generic, descriptive sense: digital tokens (digital units recorded on a blockchain) designed to keep a stable value relative to U.S. dollars and intended to be redeemable (able to be exchanged) one-to-one for U.S. dollars. Different organizations may issue stablecoins, and each system can work differently, so this page focuses on concepts that apply broadly rather than promoting any single product or provider.

Requesting a payment is more than posting an address. A good request helps the payer understand exactly what to send, on which network, by when, and how you will recognize the payment after it arrives. That clarity helps you avoid failed transfers, delayed settlement, and common kinds of confusion and fraud.

What it means to request USD1 stablecoins

To request USD1 stablecoins is to ask someone else to send you a specified amount of USD1 stablecoins, usually with enough information for them to complete the transfer correctly.

Most USD1 stablecoins live on a blockchain (a shared ledger maintained by a network of computers that records transfers). A transfer is recorded as a transaction (an entry on the ledger showing that tokens moved from one address to another). The payer normally sends the tokens from a wallet (software or a device that holds cryptographic keys (secret values that prove control) used to control digital tokens) to a destination called a public address (a public string of characters that tells the network where tokens should be delivered).

Requesting is therefore a communication problem as much as a technical one. If you leave out details, the payer may:

send USD1 stablecoins on the wrong network,
send the wrong amount,
send without a needed reference field,
or send to an address that looks similar but is not yours.

A request can be as simple as a message that includes an amount and an address, or as structured as an invoice generated by a payment provider. In every case, the goal is the same: give the payer enough information to make the transfer successfully and give you enough information to match the transfer to the right bill, order, or person.

Why people request USD1 stablecoins

People request USD1 stablecoins for many practical reasons:

Remote work and freelancing: A contractor can invoice a client in U.S. dollar terms while receiving a digital token that aims to stay close to that value.
Cross-border payments: A payer and recipient in different countries can settle a bill without waiting for bank processing windows, though local rules still apply.
Online commerce: A merchant can accept payment in USD1 stablecoins for digital goods or services, then decide whether to keep the tokens or sell USD1 stablecoins for U.S. dollars through a provider.
Donations and community funding: A project can publish a request that supporters can pay without sharing bank details.
Internal business transfers: A company with multiple teams or entities can move funds in a traceable way, sometimes with automated bookkeeping.

Stability is relative, not absolute. Even when a token aims to maintain a stable value, the real-world experience depends on redemption mechanisms, liquidity (how easily a token can be exchanged at the desired price), and operational reliability. Understanding that nuance is part of making good requests and setting appropriate expectations for payers.

Common ways to create a request

There are several common patterns for requesting USD1 stablecoins. The best choice depends on who is paying, how often you get paid, and how much structure you need.

1) A simple message with amount, network, and address

This is the most direct approach. You share:

the amount to send (denominated in U.S. dollars),
the network to use (for example, a specific blockchain or a layer 2 network (a system built on top of a base blockchain that can make transfers faster or cheaper)),
and the destination public address.

This can work well for one-off peer payments, but it puts the burden on you to provide clean instructions and on the payer to follow them precisely.

2) A payment request link

Some wallets and payment services generate a link that encodes the address, amount, and network. This can reduce manual typing and copy-and-paste errors. It can also make it easier to include a note, an invoice reference, or a due date.

A useful link is not automatically a safe link. The receiver still needs to protect the link from tampering and ensure it is shared through channels where the payer can verify it came from the right person.

3) A QR code

A QR code (a square, machine-readable pattern that can encode text such as a payment request) helps mobile users scan and pay quickly. It is especially helpful for in-person transactions and printed invoices.

QR codes raise their own operational issues: a printed QR code can be replaced, a screenshot can be edited, and a code copied from a random chat may not be authentic. The same verification ideas that apply to addresses also apply to QR codes.

4) A structured invoice

If you run a business, an invoice format can help you keep consistent records and reduce disputes. A strong invoice often includes:

a description of what is being paid for,
the amount and currency basis (U.S. dollars),
the network and destination address,
a reference identifier you can match to your records,
and your refund or adjustment policy.

Some invoicing systems also support status tracking (sent, paid, overdue) and reconciliation (matching incoming payments to invoices).

5) A checkout flow

For online sales, a checkout flow can present a pay screen, a countdown for price validity, and automated confirmation once the transfer is observed. If you use this approach, it is worth understanding where the provider sits in the flow and what they can see or control, particularly if they are custodial.

Choosing where you will receive USD1 stablecoins

Before you request USD1 stablecoins, you need a destination that can receive them. The biggest decision is whether you will use a custodial or non-custodial setup.

Custodial setup

A custodial wallet (an account where a service provider holds the cryptographic keys on your behalf) often feels like online banking: you sign in, you see a balance, and you can receive funds by sharing a deposit address or payment link.

Pros:

easier recovery if you lose access credentials (depending on the provider),
customer support and fraud monitoring may be available,
sometimes smoother conversion to U.S. dollars.

Cons:

you rely on the provider for access and availability,
your account may be limited or frozen under certain terms or legal obligations,
you may have fewer privacy controls because the provider can connect your identity to on-chain activity.

Custodial services are also typically subject to compliance programs, such as KYC (know your customer, identity checks that some laws call for) and AML (anti-money laundering, rules aimed at preventing financial crime). Those programs can shape how you request and receive payments.^[2]

Non-custodial setup

A non-custodial wallet (a wallet where you control the cryptographic keys directly) gives you direct control. Access is commonly backed up by a recovery phrase (a set of words that can recreate the wallet keys if you lose the device).

Pros:

you control access without relying on a provider to approve transactions,
you can often generate a fresh address for each request, which can improve privacy,
you can choose tools and settings that fit your needs.

Cons:

if you lose the recovery phrase, you may lose access permanently,
security is your responsibility, including device hygiene (basic practices that keep a computer or phone safer) and phishing (messages that impersonate a trusted party to steal secrets or money) resistance,
mistakes are harder to fix because transfers are often irreversible once confirmed.

Non-custodial does not mean law-free. Businesses that accept payments in USD1 stablecoins may still have legal, tax, and consumer obligations, regardless of wallet choice.

Token format and smart contracts

Many USD1 stablecoins are implemented as tokens managed by a smart contract (software code on a blockchain that can hold and move tokens according to written rules). This can affect how you request payment because a payer might need to choose the correct token within their wallet, not just the correct network.

If you request USD1 stablecoins, it helps to specify how the payer should identify the token (for example, by the token name shown in common wallets or by a contract address (the on-chain identifier of a smart contract) supplied by a trusted source). Confusion between similarly named tokens is a known source of mistakes and scams.

Building a clear payment request

A clear request is friendly to both humans and software. If someone can read it, they can check it. If software can parse it, it can reduce errors.

Here are the most helpful components to include.

Amount and currency basis

State the amount of USD1 stablecoins to send and make the currency basis clear. Most people interpret USD1 stablecoins as representing U.S. dollars, but you should still write the amount in a way that is unambiguous:

use standard decimal formatting,
avoid shorthand like "10k" unless you also write the full number,
clarify whether the amount includes any added fees or whether the payer should add fees on top.

Network fees (fees paid to the network to process a transaction) are typically paid separately from the token amount. If a payer is not familiar with this, they may send less than intended by subtracting fees from the amount. A clear request can prevent that misunderstanding.

Network selection

State the network explicitly. This matters because sending USD1 stablecoins on the wrong network can result in funds being stuck or lost, especially if the receiving wallet does not support that network.

If you accept payments on more than one network, specify which networks you accept and whether you treat them as equivalent for settlement. Some merchants accept a specific network for operational reasons such as faster confirmation times or lower fees.

Destination address and references

Include the destination public address and, when relevant, a reference field such as:

a memo (an additional text field some networks or custodial providers use to route deposits to the correct account),
an order number,
an invoice identifier,
or a customer name or alias.

If your request depends on a memo, treat it as essential. Without it, a custodial provider may receive the tokens but not know which user account to credit.

Timing and confirmation expectations

Transfers on a blockchain are not always instantaneous. A payer submits a transaction, then the network confirms it. A confirmation (an additional block added after the transaction that increases confidence it will not be reversed) can take seconds or minutes depending on the network and network load.

If timing matters, explain what you consider "paid." For example:

"paid when the transaction is visible on the network,"
or "paid after X confirmations,"
or "paid when our provider marks the invoice as completed."

The right standard depends on your risk tolerance and the size of the payment.

Clear identity and contact path

Because phishing is common, it helps to include a way for the payer to verify they are paying the right person. This can be as simple as:

a consistent business name,
a known email address,
or a signed invoice sent from a channel the payer already trusts.

If a payer is unsure, they should have a way to ask before they send funds.

Requesting USD1 stablecoins often involves sending a public address, and that is where many scams try to intervene. The goal is to reduce the chance that a payer sees a modified address or a fake request.

Use channels that support verification

A request shared in a secure business email thread is easier to verify than a request sent from a newly created account in a random chat app. If your relationship with the payer already has a standard channel, sticking to it reduces confusion.

If you must use a new channel, it can help to provide verification through a second channel (for example, sending the address in one place and confirming the first and last several characters in another).

Watch for address substitution and look-alike tricks

A common attack is to replace the destination address with an attacker address. Because addresses are hard to read, people often do not notice.

Ways to reduce this risk include:

sharing the address in a format the payer can copy exactly (to avoid manual typing),
asking the payer to compare multiple parts of the address, not just the first few characters,
and avoiding screenshots when plain text is possible.

Another trick is the look-alike account name or domain. Someone may register a domain that resembles yours or create a social media account with a similar handle. If you use requestUSD1.com as part of your public presence, consistency helps a payer recognize when something is off.

QR code tampering

If you print QR codes on paper, someone can physically replace them. If you share QR codes as images, someone can edit the image. If the payer can also see the underlying address in text, they can cross-check the QR code output before they pay.

Limit how much you reuse a single address

Many wallets allow you to receive funds to the same address repeatedly. That can be convenient, but it can also make your transaction history easier for strangers to follow because blockchains are typically public.

If your tooling supports it, using a fresh address per invoice can improve privacy and can simplify reconciliation, especially when combined with an invoice identifier. Some wallets call this a "receive address rotation" feature.

Avoid oversharing sensitive details

A payer does not need your recovery phrase, private keys (secret values that authorize spending), or device access to send you USD1 stablecoins. If anyone asks for those, treat it as a warning sign.

Confirming receipt and keeping records

After you send a request, the next step is verifying payment. The process varies based on whether you use a wallet you control directly or a service provider.

Verifying on-chain activity (recorded directly on a blockchain)

Many networks can be viewed through a block explorer (a website that displays transactions recorded on a blockchain). By searching the destination address, you can see incoming transfers and their confirmation status.

What you are typically looking for:

the correct token (USD1 stablecoins) and amount,
the correct destination address,
the transaction status (pending or confirmed),
the timestamp and confirmation count.

Some networks offer fast finality (a strong guarantee that a confirmed transaction will not be reversed) while others are probabilistic (based on probability, where confidence increases with more confirmations). The difference can matter for large payments.

Reconciliation and bookkeeping

For personal use, a simple note can be enough. For a business, payment reconciliation is often a routine process. Reconciliation (matching incoming payments to invoices, orders, or customer accounts) is easier when your request includes an invoice identifier and when your receiving tooling makes it easy to tag or label transactions.

Good records can also matter for tax reporting. In many places, digital token activity can have tax implications, and rules can differ by jurisdiction.^[7] Even if a token aims to track U.S. dollars, you still may need to record the time, value, and purpose of each receipt.

Receipts and customer communication

If you are requesting USD1 stablecoins for goods or services, it can help to provide a receipt after confirmation. A receipt can include:

what was purchased,
the amount paid,
the date and time,
and a transaction reference that the payer can keep.

Clear receipts reduce the chance of disputes later and make refunds easier if something goes wrong.

Mistakes, refunds, and dispute handling

No matter how clear you are, mistakes happen. Planning for them ahead of time makes you more resilient.

Common mistakes

Wrong network: The payer sends USD1 stablecoins using a network you do not support. Recovery depends on the wallet setup and may not be possible without special tooling.

Wrong token: The payer sends a different token that looks similar, or sends a token with a confusing name. If your wallet does not support it, you may not see it.

Missing memo: A payer sends to a custodial deposit address but forgets the memo. The provider might still be able to credit the account, but it can take time and may involve support processes.

Overpayment or underpayment: The payer sends too much or too little. Your response depends on policy and context.

Refunds

Transfers of USD1 stablecoins often do not support chargebacks (forced reversals by a payment network). If you issue a refund, it is usually a new transfer you initiate back to the payer.

That creates two practical questions:

How will you confirm the payer refund address safely?
How will you document the refund and connect it to the original transaction?

In many business settings, it helps to treat refunds as part of a written policy and to handle them through the same identity checks you use for receiving.

Disputes

When a payer claims they paid, the public nature of many blockchains can help resolve disputes. You can compare the destination address, the token, and the transaction reference. Clear requests with clear receipts reduce disputes in the first place.

Policy and compliance basics

Stablecoin payments intersect with financial rules in many jurisdictions, especially when businesses are involved. The practical message for requesting USD1 stablecoins is simple: the more you operate like a payment business, the more likely you are to face formal obligations.

Financial crime controls

Regulators and international bodies have published guidance on virtual assets and service providers, including expectations around AML controls and customer due diligence (checking and documenting customer information to assess risk).^[2] Service providers that custody funds may be expected to screen for sanctions exposure (legal restrictions on transacting with certain parties) and monitor for suspicious activity.

If you are a business requesting USD1 stablecoins, you may need to think about:

whether you need to collect customer information,
whether you need to monitor for high-risk activity,
and how you will respond if a payment is flagged.

The right approach depends on your jurisdiction, your business model, and whether you use a regulated service provider. The Financial Stability Board has also discussed regulatory approaches and oversight expectations for stablecoin arrangements, emphasizing governance, risk management, and operational resilience.^[1]

Travel Rule considerations

In some contexts, the "Travel Rule" (a rule that can call for certain originator and beneficiary information to accompany transfers between service providers) may apply to virtual asset transfers handled by providers.^[2] Even if you are not a provider, the providers you use may ask for information that affects how you request and receive payments.

Consumer protection and disclosure

If you are requesting USD1 stablecoins from retail customers, you may have consumer protection obligations related to disclosures, refunds, and dispute resolution. In the European Union, the Markets in Crypto-Assets Regulation (MiCA) sets a framework that includes rules for certain crypto-asset issuers and service providers, with provisions relevant to stable-value tokens and consumer safeguards.^[3]

Data security and identity

Account security is part of compliance and part of basic risk control. Frameworks such as the NIST Digital Identity Guidelines discuss authentication practices like multi-factor authentication (MFA, using two or more proof factors such as a password plus a one-time code).^[6] Even if you are not operating under a formal framework, the ideas are useful when you choose how to receive payments and how to protect your accounts.

Fees, speed, and reliability

Requesting USD1 stablecoins also involves user experience tradeoffs.

Network fees and timing

Most blockchains need a network fee to process transactions. Fees can rise when a network is congested (busy) and fall when it is quiet. If a payer is sensitive to fees, they may prefer a network with lower fees, but you need to support the same network on the receiving side.

Finality and risk tolerance

Payment acceptance policies often depend on finality. Some merchants treat a payment as accepted when it is visible on-chain, while others wait for multiple confirmations. Higher-value payments often justify waiting longer.

Operational reliability

Reliability is not only about the network. It is also about:

whether the payer wallet is functioning,
whether your receiving wallet or provider is available,
and whether your own systems can track incoming transfers accurately.

The BIS has discussed how stablecoins can create new efficiencies while also introducing new risks, including operational and governance risks that can show up during stress periods.^[5]

Privacy, accessibility, and international notes

Requesting USD1 stablecoins can expose more information than people expect.

Public ledger privacy basics

Many blockchains are public. Addresses are often pseudonymous (not directly linked to a real name on the ledger), but activity can still be analyzed. If you reuse one address frequently, others may be able to estimate your income patterns or link payments across customers.

Privacy-friendly practices often include:

using fresh receiving addresses when possible,
sharing only what the payer needs to complete the payment,
and avoiding posting a single receiving address publicly if it will attract unwanted attention.

Accessibility

A good request is usable by people with different devices and needs. Helpful patterns include:

providing both a QR code option and a plain-text option,
avoiding tiny fonts or hard-to-read screenshots,
and including a human-readable amount and a human-readable contact method.

International and currency notes

Even if USD1 stablecoins aim to be redeemable one-to-one for U.S. dollars, people outside the United States may face conversion steps, local reporting needs, and differing legal treatment. Central banks and regulators have discussed how digital money and stablecoin arrangements can affect payments and financial stability, and those discussions often inform local policy choices over time.^[4]

Glossary

USD1 stablecoins: Digital tokens designed to keep a stable value relative to U.S. dollars and intended to be redeemable one-to-one for U.S. dollars.
Blockchain: A shared ledger maintained by a network of computers that records transfers.
Wallet: Software or a device that holds cryptographic keys used to control digital tokens.
Public address: A public string of characters that tells the network where tokens should be delivered.
Network fee: A fee paid to the network to process a transaction.
Confirmation: An additional block added after a transaction that increases confidence it will not be reversed.
Custodial wallet: An account where a service provider holds cryptographic keys on your behalf.
Non-custodial wallet: A wallet where you control cryptographic keys directly.
Recovery phrase: A set of words that can recreate wallet keys if you lose a device.
Smart contract: Software code on a blockchain that can hold and move tokens according to written rules.
Block explorer: A website that displays transactions recorded on a blockchain.
KYC: Know your customer, identity checks that some laws call for.
AML: Anti-money laundering, rules aimed at preventing financial crime.