Get your questions answered before you start.

Stablecoins such as USDC and USDT are crypto assets built to hold the value of a currency, usually the US dollar. A stablecoin payment service helps merchants link a customer's stablecoin payment to the order for the goods or service, and handles payment confirmation, record lookups and the related funds flow. A setup may include different options for receiving, managing or settling funds.

Whether you need a wallet or to hold stablecoins depends on how you receive funds. If you want fiat currency, check whether conversion or settlement is offered in your region. Confirm the account, wallet and sign-up requirements before you start.

That depends on how they pay. Whether a customer's existing wallet or payment tool works has to be checked against the asset, network and connection route. You can't tell from the wallet's name alone.

That depends on the payment flow. A tap may open the payment page or start a connection, and the customer may still need to check the amount and confirm in their own payment app. The exact steps depend on the setup that's live.

USDC on Base is live now. 9x payments focus on USDT and USDC, and the coverage page shows each live combination with its update date. Support has to be pinned down to a combination of asset version, network, region and payment method. One asset name doesn't mean every network is available.

Not necessarily. “Sent” can mean the transaction was submitted but hasn't yet met the merchant service's confirmation rules. Staff should go by the valid payment result on the merchant side.

Tell us your region, type of business, where you take payments and how you want to receive funds. We'll use that to confirm what's covered, what you need to set up and what you'd be quoted for.

Payment confirmation is about whether the customer's payment meets the order and payment rules. Settlement is about how the funds are then booked, converted or delivered. The two can finish at different times.

Keep the order and the actual payment record, check the amount and the transaction status, then follow the right steps for a top-up, the excess or a refund. Don't treat a payment with the wrong amount as a normal full payment.

Look up the result through the order and transaction records. A closed page doesn't tell you whether the payment succeeded or failed, and the customer shouldn't pay again before the result is checked.

First check the original order and the actual payment, then confirm the refund amount, asset, how it's received and any fees under the service rules. Whether you can start a refund in the merchant tools, and who approves or carries it out, depends on your setup.

That depends on your funds setup. Before you start, confirm the asset you receive, the settlement currency, the service region and the conditions. The asset your customer pays with isn't automatically the currency that lands in your bank.

Creating orders, looking them up and confirming transactions all need a network connection. If a device goes offline, follow the recovery and checking steps. A customer's screenshot alone doesn't prove an order is complete.

The app is built around transaction records, takings, the assets you received, and payment and funds status. Exact breakdowns, permissions and actions depend on the version you have.

It helps you create, issue and manage coupons around your business activities. You set the offer and the rules, customers use the coupon when they qualify, and staff redeem it following the matching steps.

Check which offer types and settings are currently supported. Options such as amount or percentage off, validity period, minimum spend, eligible stores and usage limits depend on the features actually provided. Don't assume they're all available.

Whether a payment can trigger a coupon has to be confirmed against the current product flow. Other issuing channels and automations should be checked separately as well.

That depends on how the coupon is recognized, how eligibility is checked and how it connects to your checkout. Some flows may need staff to act. The specifics should be set out in your in-store demo and setup guide.

That depends on which wallet pass integrations are actually available. Saving a coupon pass is a different feature from how the customer pays. Having coupons doesn't mean every wallet or payment method supports them.

It follows your campaign and the service rules. Whether the coupon becomes usable again or void, and how the refund is calculated, should be decided in advance and match the order record.