Welcome to chargeUSD1.com

Charging is a simple word, but in digital payments it can describe two related ideas:

Charging a customer (requesting payment for goods or services).
Charges (fees applied by a network, a service provider, or your own business policy).

This page explains both ideas as they relate to USD1 stablecoins (digital tokens designed to be redeemable one-for-one for U.S. dollars). The term USD1 stablecoins is used here only as a descriptive category, not a brand name, and not a promise that any particular token is risk-free.

chargeUSD1.com is one page in the USD1 stablecoins network, a collection of educational resources that discuss USD1 stablecoins in a generic, descriptive way.

Stablecoins (digital tokens designed to keep a steady price, often by being backed with reserves) can be useful when you want digital payments that behave more like U.S. dollar transfers than like volatile cryptocurrencies. Many stablecoins live on a blockchain (a shared transaction ledger run by a network of computers), which can allow payments to settle without a card network or a bank wire. That said, stablecoins come with real tradeoffs: legal rules vary by country, transactions can be hard to reverse, and the quality of a stablecoin depends on how it is issued, managed, and redeemed.^[2]^[3]

What follows is an educational, hype-free guide to charging customers using USD1 stablecoins. It is not legal, tax, or investment advice. If your business has specific compliance obligations, consult qualified professionals in your region.

What it means to charge using USD1 stablecoins

When you charge a customer using USD1 stablecoins, you are asking them to send a specific amount of USD1 stablecoins to a destination you control. In most cases, that destination is a blockchain address (a public identifier used to receive tokens), or an account at a custodian (a service provider that holds assets on behalf of users).

A helpful mental model is to compare three common payment styles:

Card payments: a card charge is usually authorized first, then later settled. Chargebacks (a card-network dispute process) can reverse a payment after the fact.
Bank transfers: funds move account to account, often with strong identity checks, but settlement speed varies.
Blockchain transfers: value moves address to address. Once sufficiently confirmed (included in blocks with enough additional blocks after it), reversal is often impractical without the recipient sending a refund.

USD1 stablecoins can be used in the third style. That can be attractive for some businesses, but it changes how you handle customer support, fraud, and refunds. It also changes what "paid" means in your internal processes, because you may need to decide how many confirmations you wait for before delivering a digital good or shipping a physical product.

Two more terms are worth defining early:

On-chain (recorded directly on a blockchain) versus off-chain (recorded in a service provider's internal ledger, like a custodial exchange account).
Custody (who controls the private keys, meaning the secret credentials required to move assets).

In short: charging with USD1 stablecoins is less like tapping a card and more like receiving a bank transfer that can arrive at any time of day, including weekends. It can also be more final than a card payment, which is why clear refund policies and careful checkout design matter.

A plain-English primer on USD1 stablecoins

USD1 stablecoins are a type of stablecoin intended to track the value of U.S. dollars. In a typical arrangement, a user can acquire USD1 stablecoins by paying U.S. dollars to an issuer (an organization that creates and redeems the token) or by obtaining USD1 stablecoins from another holder. The issuer may promise redemption at one U.S. dollar per unit, often subject to terms, eligibility requirements, and fees.

Not all USD1 stablecoins are the same. When you evaluate whether to accept them, you are really evaluating an arrangement that may include:

Issuer risk (whether the issuer can honor redemptions and manage reserves responsibly).
Reserve quality (what backs the stablecoin, such as cash, short-term government debt, or other assets).^[2]
Operational risk (whether systems, banking partners, and redemption processes work reliably).
Legal and regulatory status (how your jurisdiction treats stablecoins, custody, and money transmission).^[1]^[3]

A second dimension is where the token exists. USD1 stablecoins may be issued on one or more blockchains. Each blockchain has its own fee model, transaction speed, and tooling. That affects the customer experience when you request a payment.

Key blockchain terms you will see:

Gas fee (a network fee paid to validators or miners to process a transaction).
Validator (a network participant that helps confirm transactions and add blocks).
Smart contract (software deployed on a blockchain that can hold and move tokens according to rules).
Network congestion (a period when many users are competing for limited block space, often raising fees).

If you are new to these ideas, focus on one practical point: a USD1 stablecoins payment is not a single technology. It is a stack. Your business experience will depend on the stablecoin arrangement, the blockchain network, the wallet software your customers use, and the operational choices you make.

Common ways to request and collect payment

There is no single best way to charge customers using USD1 stablecoins. The right approach depends on your business size, technical resources, risk tolerance, and the type of sale you are making. Below are several common patterns, along with their practical tradeoffs.

1) A simple address and amount

The most basic flow is:

You provide a receiving address.
You specify the amount of USD1 stablecoins to send.
The customer sends the payment from their wallet.

This can work for low-volume invoicing, donations, or business-to-business settlement. It becomes harder at scale because you also need a way to reconcile (match) payments to customers. If you reuse a single address for all customers, you may need the customer to include an order reference in the payment note, but many blockchains do not support notes in a standard way. Some networks do support a memo field (an extra identifier attached to a transfer), and in those cases the memo can be important, because missing it can cause delays or loss depending on the receiving system.

Operational considerations:

Address format: some blockchains have similar-looking addresses, so you must clearly state the network you expect.
Amount formatting: stablecoins often support fractional units. You should specify how many decimal places you accept to avoid rounding disputes.
Timing: you must decide what counts as paid. Many businesses use a threshold like "payment detected" and "payment confirmed."

2) Unique deposit addresses per customer or per invoice

A more scalable pattern is to generate a unique address for each customer or each invoice. That makes reconciliation easier because incoming transfers to that address can be linked to a single order.

This usually requires a wallet system capable of generating many addresses and tracking them safely. If you control your own wallet infrastructure, you are responsible for key management (how you store and protect private keys). If you use a service provider, you are trusting them with custody and availability.

3) Hosted checkout or payment processor

A third pattern is to use a payment service provider that offers a hosted checkout page, invoices, and automatic reconciliation. In this model, you may receive:

A payment page that shows the amount and network options.
Real-time detection of incoming transfers.
Webhooks (automated notifications) to mark an invoice as paid.
Optional conversion services, such as exchanging USD1 stablecoins for U.S. dollars.

The tradeoff is counterparty exposure: you depend on the provider for uptime, fee transparency, and payout reliability. You may also have additional compliance steps, such as business verification and transaction monitoring.

4) Custodial account transfer

Some businesses and customers keep USD1 stablecoins inside custodial platforms. In that case, the payment might occur as an internal transfer within that platform. These transfers can be fast and cheap because they may be off-chain, but they come with a different risk profile:

You rely on the custodian's internal records and policies.
Withdrawals to a blockchain address may be delayed or restricted.
Dispute handling is governed by the custodian, not by a card network or a bank.

From an accounting viewpoint, you should still record the customer payment, but your proof of payment may be a platform receipt rather than a blockchain transaction.

5) Subscription billing and recurring charges

Recurring billing with USD1 stablecoins is possible, but it is fundamentally different from card subscriptions. Cards can be charged again using stored payment credentials and card network rules. Blockchain transfers require the customer to authorize each payment, unless they use a smart contract or a wallet feature that permits recurring transfers under controlled rules.

If you offer subscriptions, be clear about:

How the customer initiates each renewal payment.
Whether you support a grace period if they pay late.
How cancellations and partial-period refunds work.

For many businesses, subscriptions are feasible if you pair stablecoin billing with proactive reminders and an easy one-click payment experience.

Understanding fees and who pays them

In card payments, the merchant pays a well-known set of processing fees, and the customer rarely sees a separate network fee. In blockchain payments, fees work differently, and customers may see them directly in their wallet.

When charging customers using USD1 stablecoins, you may encounter several types of fees:

Network fees

Most blockchain networks require the sender to pay a fee to include a transaction in the ledger. This is often called a gas fee. The fee is not typically paid in USD1 stablecoins. It is often paid in the network's own asset (the base asset used for fees on that blockchain). That matters for user experience: a customer may have USD1 stablecoins but still be unable to pay if they do not have enough of the base asset to cover the network fee.

For merchants, network fees create two practical choices:

Customer-paid fees: the customer pays the network fee on top of the invoice amount. This is the most common model in self-custody wallet transfers.
Merchant-paid fees: you can choose to reimburse fees indirectly, but the network fee is still paid by the sender at the time of transfer. You can also adjust pricing to account for typical fee levels.

Service provider fees

If you use a payment processor, custodian, or exchange, you may pay:

Processing fees for payment detection and settlement.
Payout fees for withdrawing to your bank or to your own wallet.
Conversion fees if you exchange USD1 stablecoins for U.S. dollars.
Spread (the difference between a quoted buy price and sell price) when converting between assets.

The most important operational practice here is transparency. If you display an invoice amount in U.S. dollars and you accept USD1 stablecoins, customers will expect the stablecoin amount to match closely. If you add a buffer to cover fees or price movement, disclose that clearly and explain why.

Your own charges and policies

You may decide to add a convenience fee (an extra amount added to cover operational costs) or to offer a discount for paying with USD1 stablecoins. Both can be reasonable, but both require careful communication. The less familiar the customer is with stablecoin payments, the more they benefit from plain language:

"This invoice is for 100 U.S. dollars. Pay 100 units of USD1 stablecoins. Your wallet will also charge a small network fee."
"If you pay with USD1 stablecoins, we reduce the price by 2 U.S. dollars because the payment settles without card processing fees."

Be cautious with percentage-based surcharges. In some regions and card contexts, surcharging is regulated. Even if you are not using a card network, consumer protection rules can still apply.

Fee volatility and customer support

Network fees can change quickly during congestion. If your checkout expires after a set time, you need a policy for late payments or underpayments. A common approach is to:

Show a payment timer.
Provide a "refresh amount" button that recalculates the required amount of USD1 stablecoins.
Accept small underpayments within a tolerance when feasible, or request a top-up.

These design choices can reduce support tickets and improve conversion rates, especially for first-time stablecoin payers.

Confirmations, settlement, and timing

A key difference between charging with USD1 stablecoins and charging a card is the meaning of "final."

Card transactions can be disputed after settlement. Banks can recall wires in limited cases. Blockchain transfers are different: once a transaction is confirmed and final enough for your risk tolerance, it usually stays that way unless you issue a refund.

Here are the concepts that matter in practice:

Detection versus confirmation

Detected payment: your system sees a pending transaction or a transaction included in a recent block.
Confirmed payment: the transaction has enough confirmations that the chance of reversal is very low for your purposes.

Different blockchains have different finality models (how they decide a transaction is irreversible). Some use probabilistic finality (finality increases as more blocks are added). Some use faster finality where a block becomes final after a protocol step. In either case, you must choose a confirmation target that matches your risk tolerance and the value of the goods being delivered.

Settlement speed and business operations

If you sell digital goods, you might deliver after a smaller confirmation count because the downside is limited. If you ship physical goods or deliver high-value services, you might wait longer. This is not about trusting customers; it is about managing the small but real risk of blockchain reorganizations (rare events where a chain temporarily changes which transactions are included).

You should also plan for operational timing issues:

Payment windows: customers may start a payment and get interrupted. Decide how long an invoice stays valid.
Partial payments: customers may send the wrong amount. Decide whether you accept it, refund it, or request a top-up.
Duplicate payments: customers sometimes pay twice. Your system should detect this and have a clear refund path.

Pricing and exchange timing

If your prices are denominated in U.S. dollars, the cleanest approach is to request the same numeric amount in USD1 stablecoins, because the goal is a one-for-one relationship. In the real world, there can be small deviations due to fees, liquidity (how easily an asset can be bought or sold without moving price) conditions, or issuer terms. Be clear about what you accept:

Do you accept only one specific USD1 stablecoins token on one specific blockchain?
Do you accept multiple versions, and if so, how do you prevent customer confusion?

A practical rule is to simplify options. Too many networks and token choices can cause customer mistakes. If you do offer multiple options, your checkout should make the network choice explicit, with clear labels and help text.

Refunds, disputes, and customer support

Refund handling is where many businesses feel the biggest difference between stablecoin payments and card payments. With cards, refunds and disputes are built into the network. With blockchain transfers, you must build your own policy and process.

Refunds are outbound payments

A refund in USD1 stablecoins is typically a new transfer from you to the customer. That implies:

You need a safe way to send USD1 stablecoins.
You may need the customer to provide a refund address.
You should verify that the refund address matches the same blockchain network used for the original payment.

If you refund to the wrong network or wrong address, the refund may be unrecoverable. A good support workflow includes a confirmation step where the customer repeats the address and network in plain language, and you confirm it back to them before sending.

Disputes are policy-driven

Because blockchain transfers do not have a universal chargeback system, disputes are resolved by your customer support policy. This can be an advantage for merchants who face high chargeback rates, but it also increases your responsibility to be fair and transparent.

Your policy should cover:

Non-delivery claims: what proof you accept for delivery, and how you handle shipment issues.
Digital goods: whether refunds are available after access is granted.
Mistaken payments: what happens if a customer sends funds to the wrong address or sends the wrong amount.
Overpayments and duplicates: how you handle accidental extra payments.

For some businesses, offering a clear refund promise can increase trust and adoption, especially for first-time stablecoin users.

Fraud and social engineering

Stablecoin payments reduce some types of card fraud, but they introduce new ones. Common risks include:

Phishing (tricking a customer into sending funds to the wrong address).
Invoice manipulation (a criminal changing a payment address on an invoice).
Impersonation (a criminal posing as your support team and requesting a refund to their address).

Practical mitigations include:

Always presenting payment details inside authenticated pages, not in editable documents alone.
Using consistent invoice identifiers and asking customers to confirm them.
Training support staff to treat address changes as high risk.

These are not exotic threats. They are normal payment fraud patterns translated into a blockchain setting.

Compliance basics in many regions

Compliance obligations vary widely by jurisdiction, business model, and transaction flow. This section is a general orientation, not a checklist.

Know your customer and transaction monitoring

KYC (know your customer, meaning verifying customer identity) and AML (anti-money laundering, meaning controls to prevent illicit financial activity) are central topics in stablecoin payments. In many countries, businesses that transmit money, exchange assets, or provide custody services can have licensing and compliance duties. International standards bodies have also issued guidance that influences national rules for virtual assets and service providers.^[1]

If you are simply accepting USD1 stablecoins as payment for your own goods and services, your obligations may differ from those of an exchange or a custodian. Still, many businesses choose to implement risk-based controls, such as:

Screening customers or transactions against sanctions lists (government lists of restricted parties).^[4]
Monitoring for unusual patterns, such as many small payments from many unrelated wallets.
Keeping records of invoices, payment proofs, and customer communications.

If you use a payment processor or custodian, they may perform some of these checks. You should understand which responsibilities are yours versus theirs.

Sanctions risk

Sanctions compliance can apply even when transactions happen on a blockchain. Authorities have published guidance specifically for virtual currency activity, emphasizing that organizations should apply risk-based compliance programs and should block or report prohibited activity where required.^[4]

Even if you are not required to screen every customer, having a plan matters. For example, you should know how to respond if a payment arrives from a wallet that a service provider flags as high risk, or if a bank asks questions about the source of funds when you cash out.

Reporting and recordkeeping

Some jurisdictions require businesses to keep records of transactions over certain thresholds, report suspicious activity, or provide information about counterparties. In the United States, for instance, FinCEN has published guidance on how certain virtual currency activities can fall under money services business (a regulated category of non-bank financial service provider) rules, depending on the role you play in a transaction flow.^[5]

For global businesses, the safest stance is to assume that stablecoin acceptance touches financial rules and to get tailored advice before scaling.

Consumer disclosures

Even if USD1 stablecoins aim to track U.S. dollars, you should not imply that they are bank deposits or that they carry government insurance. Stablecoin arrangements can fail, redemption can be delayed, and legal rights can differ from traditional bank accounts. Regulators and policy groups have highlighted risks related to reserve quality, redemption, governance, and operational resilience.^[2]^[3]

A clear disclosure statement at checkout can set expectations. Plain language is best:

"Payments are made using USD1 stablecoins on a blockchain network."
"Blockchain payments are typically irreversible. Refunds follow our refund policy."
"Network fees may apply and are paid through your wallet."

These disclosures are also helpful for support, because they reduce confusion when a customer expects a card-like reversal mechanism.

Security and operational controls

If you accept USD1 stablecoins directly into your own wallets, security becomes a core business function. A lost private key or a successful theft can be irreversible.

Below are security concepts worth understanding early.

Wallet types and custody

A wallet (software or hardware that stores the secret credentials used to authorize transactions) can be:

Self-custody: you control the private keys.
Custodial: a provider controls the private keys and gives you account access.

Self-custody can reduce dependence on intermediaries, but it increases your operational burden. Custodial services can simplify payments, but they introduce counterparty risk.

Some businesses use a hybrid model:

A hot wallet (a wallet connected to the internet) for day-to-day receipts and refunds.
A cold wallet (a wallet kept offline) for larger balances.
A multi-signature wallet (a wallet that requires multiple approvals to move funds) for internal controls.

These tools can reduce the risk of a single compromised credential causing a total loss.

Operational practices that reduce risk

Security is not just technology. It is also process:

Separation of duties: the person who approves a refund is not the same person who executes it.
Verification steps: require a second person to confirm a refund address for high-value refunds.
Device hygiene: keep payment devices updated, use strong authentication, and limit administrative access.
Backups: store recovery phrases securely, and test recovery procedures.

Identity assurance guidance from standards bodies can be useful when you design administrative access controls, especially for teams that operate shared wallets or custodial dashboards.^[6]

Monitoring and incident response

You should assume that mistakes and attacks happen. A mature setup includes:

Monitoring for inbound payments and outbound transfers.
Alerts for unusual activity, such as large transfers or new withdrawal addresses.
An incident response plan (a documented plan for how to respond to a security event).

Even a simple plan helps: who you notify, how you freeze operations, and how you communicate with customers.

Accounting, records, and reporting

Accounting for USD1 stablecoins payments can be straightforward in concept but tricky in practice. You are receiving a digital asset that aims to track U.S. dollars, but accounting and tax rules may treat it differently from bank deposits.

This section is general education. Your accountant should advise based on your jurisdiction and reporting standards.

What to record

At minimum, keep a record that links each sale to:

The invoice amount and currency unit (U.S. dollars or USD1 stablecoins).
The payment proof (a transaction hash or a custodial receipt).
The date and time of payment recognition in your system.
Any refunds and their outbound transaction proof.
Any conversion activity if you exchange USD1 stablecoins for U.S. dollars.

Good records help with audits, customer disputes, and compliance reviews.

Tax treatment may differ from intuition

In some jurisdictions, tax authorities treat virtual currency as an asset for tax purposes. In the United States, IRS guidance has historically treated virtual currency as an asset rather than as foreign currency for many tax rules, which can affect how gains and losses are calculated when you dispose of it.^[7]

For a merchant who promptly converts USD1 stablecoins to U.S. dollars, gains and losses may be small, but they can still exist due to fees and small price deviations. The most important operational step is consistency: decide your accounting method and apply it the same way each period.

Reconciling and cash management

A practical business question is: when do you convert?

Immediate conversion can reduce exposure to stablecoin risks and simplify cash planning.
Holding USD1 stablecoins can be useful if you pay suppliers or contractors in stablecoins, or if you operate across borders, but it may increase exposure to issuer, custody, and regulatory risks.

If you choose to hold balances, define limits and review them. Many risk frameworks for stablecoin arrangements emphasize governance, risk management, and transparency as key controls for resilience.^[2]

Common scenarios for charging with USD1 stablecoins

Charging customers using USD1 stablecoins can be a good fit when your business values fast settlement, clear payment finality, and the ability to serve customers across borders without relying on card rails. It can also be a poor fit when your customers expect card-like reversals, when you need very strong consumer protections baked into the rail, or when your team is not ready to manage the operational and compliance details.

Below are a few scenarios where businesses often explore USD1 stablecoins payments.

Business-to-business invoicing

For business-to-business sales, invoices are already common, payment terms are negotiated, and customers may be comfortable with bank-transfer-like workflows. USD1 stablecoins can be used for:

Cross-border supplier payments where bank wires are slow or costly.
Time-sensitive settlements, such as shipping releases that depend on confirmed payment.
Situations where both sides already hold stablecoins for treasury operations.

Even here, you will want clear terms on who pays network fees, how late payments are handled, and what proof of payment is accepted.

Digital services and online commerce

Online businesses may use USD1 stablecoins to offer an additional payment method alongside cards and bank transfers. This is most straightforward when:

The product is delivered digitally after a confirmation threshold is met.
The customer base already uses wallet-based payments.
The business can provide clear instructions at checkout, including the exact network and the exact amount.

If you ship physical goods, you can still accept USD1 stablecoins, but you may want to delay shipment until you have the confirmation level that matches your fraud and logistics risk.

International customers and currency conversion

If you serve customers in many countries, you may encounter card declines, high foreign exchange (currency conversion) fees, and slow bank transfers. USD1 stablecoins can simplify the customer side by letting them pay in a U.S. dollar equivalent, while you choose how and when to convert to local currency. Your business still needs banking access for cash-out, and you should plan for the compliance questions that banks may ask about the source of funds.^[2]^[5]

Marketplaces and payouts

Some marketplaces explore stablecoins for faster payouts to sellers or contractors. This can reduce payout friction, but it introduces additional questions about identity checks, sanctions screening, and recordkeeping. If you are moving funds between third parties, your role can start to resemble a payment service provider, which may change your regulatory duties.^[1]^[5]

Donations and community funding

For donations, the ability to receive funds at any time can be useful, and stable value can reduce the volatility that donors and recipients worry about. The main operational needs are transparency (where the funds go), security (who controls the keys), and clear refund and mistake-handling policies.

No matter the scenario, it helps to start small. Treat your first stablecoin payment flow as a pilot, measure support burden, and refine your checkout instructions and internal controls before scaling.

Risks and limitations to understand

USD1 stablecoins can reduce some friction in digital payments, but they do not remove risk. Understanding risk is part of responsible adoption.

Stable value is a goal, not a guarantee

Even when a stablecoin aims to be redeemable one-for-one for U.S. dollars, that outcome depends on reserves, governance, liquidity, and market confidence. Stablecoin arrangements have faced stress events in the past, and policy bodies have repeatedly highlighted risks of runs (rapid redemptions), operational failures, and unclear legal claims.^[2]^[3]

As a merchant, you can reduce exposure by:

Limiting the amount you hold in USD1 stablecoins.
Converting to U.S. dollars on a schedule.
Diversifying payment methods so your business is not dependent on one rail.

Blockchain risks are real

Blockchains can have outages, congestion, software bugs, and governance disputes. A payment rail that works well today can experience delays tomorrow. Design your checkout with failure in mind:

Provide status messaging if a network is congested.
Offer alternative payment methods when possible.
Avoid shipping goods until you have the confirmation level you require.

Compliance and banking access can change

Even if stablecoin acceptance is legal, banking partners may have their own risk policies. Your ability to cash out can depend on your bank, your region, and your transaction patterns. Policy and regulatory approaches to stablecoins and related service providers have evolved, and they continue to evolve.^[3]^[5]

Customer support burden

Because stablecoin payments are unfamiliar to many customers, you should budget for extra support, especially early on. Common support topics include:

"I sent the payment but it is not marked as paid yet."
"My wallet shows a fee and I do not understand it."
"I used the wrong network. Can you still see my payment?"
"I paid twice. Can I get a refund?"

A well-designed checkout and a clear FAQ can cut these tickets dramatically.

Frequently asked questions

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

No. USD1 stablecoins aim to track U.S. dollars, but they are not the same as a bank deposit. Legal protections, redemption rights, and risk profiles differ. Your safest communication to customers is to describe USD1 stablecoins as a blockchain-based payment method that targets a one-for-one value with U.S. dollars, without implying deposit insurance or guaranteed redemption.^[2]^[3]

Can I reverse a payment if a customer made a mistake?

In most blockchain systems, the payment itself cannot be reversed unilaterally. You can issue a refund as a new payment, but that requires you to control the funds and to know the correct refund address. This is why clear refund policies and careful address verification are important.

Who pays the network fee?

Typically the sender pays the network fee using the base asset of the chosen blockchain. This fee is separate from the USD1 stablecoins amount. Some businesses adjust pricing or offer discounts to account for fee differences, but the fee is still paid through the sender's wallet at the time of transfer.

What happens if a customer sends USD1 stablecoins on the wrong network?

This depends on your setup. If you use a custodian or processor that supports only one network, a wrong-network transfer may be difficult or impossible to recover. If you control the private keys for the receiving address on both networks, recovery may be possible, but it can still be complex. The best mitigation is prevention: make the network choice obvious and provide a copy button and QR code in your checkout.

Do I need KYC to accept USD1 stablecoins?

It depends on your role and jurisdiction. A merchant selling its own goods may have different duties than a financial service provider, but AML and sanctions rules can still be relevant. Many businesses implement risk-based controls even when not strictly required, and processors may require business verification.^[1]^[4]^[5]

How do I prove a payment was made?

On-chain payments can be proven with a transaction hash (a unique identifier for a blockchain transaction) and the receiving address. Custodial transfers can be proven with platform receipts and account records. For customer support, it helps to provide a simple receipt page that shows the invoice identifier, amount, time, and proof reference.