Pay & Get Paid

Pay & Get Paid gives Amy users two straightforward ways to send supported assets or request payment.

• Pay lets you send a supported asset from your connected wallet.
• Get Paid lets you create a one-time payment-request link for another person to pay.

Amy provides the interface, request tools, history and status display. Wallet, card, on-ramp and settlement services are handled through thirdweb and its connected providers where relevant.

1. Pay and Get Paid

The live page has two main tabs, each with its own history.

Pay sends supported assets from your connected wallet.

Get Paid creates and manages one-time payment requests.

To use either, log in to Amy and connect your wallet.

2. What Pay does

Pay lets you send a supported asset directly from your connected wallet to another wallet address. The transfer happens on the selected asset's current network.

Pay does not:

• bridge the asset
• change the asset
• move it to another chain
• convert it automatically
• hold it in Amy custody

For example, KAITO selected on Base is sent on Base. BERA selected on Berachain is sent on Berachain.

The asset selector shows supported wallet-held assets that Amy can currently send. Supported assets and available networks can vary. The live asset selector is the source of truth.

3. How to send an asset

1. Select a supported asset.
2. Enter the recipient wallet address.
3. Enter the amount as a token quantity or estimated USD value.
4. Use Max where appropriate.
5. Select Review.
6. Check the asset, amount, recipient and network.
7. Go back if anything needs changing.
8. Select Confirm.
9. Approve the transaction through your connected wallet.
10. Wait for network confirmation.
11. View the result and relevant chain explorer link.

Final approval happens through your wallet, not through Amy.

4. Amounts, Max and gas

You can switch between entering the amount as a token amount or an estimated USD amount. The corresponding value is approximate. Pricing may change. The actual onchain transfer is made in the selected token amount.

Max uses the available balance shown for the selected asset. Every onchain transfer also needs the relevant network gas asset. If you are sending the network's native gas asset, leave enough to cover the transaction fee. For other tokens, you need a separate balance of the network gas asset.

5. Checking the recipient and network

Make sure the recipient expects the selected asset on the displayed network. Amy sends the asset on that network and does not bridge it elsewhere.

Before confirming:

• double-check the full address
• confirm the asset and network
• confirmed onchain transfers are normally irreversible
• Amy cannot recover assets sent to the wrong address or network

Before confirmation, Amy shows the main payment details including the asset, amount, recipient and network. The connected wallet provides the final transaction approval.

6. Pay history

Recent Pay transactions appear in your Pay history. Each entry may show:

• asset
• amount
• shortened recipient address
• status
• chain explorer link

Transfer states include Pending, Success and Failed. Recent transactions may take time to appear.

7. What Get Paid does

Get Paid lets you create a one-time payment-request link. You enter the payment details, choose Simple or Pro and generate a shareable link. The payer then opens the link and uses one of the payment routes available to them.

You do not need to know the payer's wallet address. The payer does not need an Amy account to open and pay the link.

8. Why payment requests use stablecoins

Get Paid uses supported stablecoins rather than volatile assets. This means the requested amount remains easier to understand between the time the request is created and when it is paid.

9. Simple mode

Simple mode is currently fixed to USDT on BSC. This is the default because it offers broad practical compatibility across supported wallet and provider routes.

In Simple mode:

• you enter the request details and a USD amount
• the receiving asset and network are fixed
• supported wallet, card, Apple Pay or Google Pay methods may be shown to the payer where available
• actual payment-method availability depends on the payer's location, device and provider support

Simple rule

Simple uses the default USDT on BSC route. The payer sees the payment methods currently made available by the provider for their country, device and payment route.

10. Pro mode

Pro mode lets you choose a supported stablecoin and network, enable or disable supported payment methods and choose whether alternate settlement is allowed.

The live selector shows the current supported combinations, which may include options across BSC, Base, Ethereum and Berachain. The live selector is the source of truth.

Pro is useful when receiving the payment in a particular stablecoin on a particular network matters.

11. How the payer can pay

Wallet payment is normally the most direct route when you need a particular stablecoin on a particular network. The payer connects a supported wallet and completes the onchain payment.

Card, Apple Pay and Google Pay depend on the payer's country, device, payment provider, selected stablecoin and network. Provider checks or limits may apply. These methods may not be available in every country.

Creating a request and paying it are separate steps. The payment methods available to the payer depend on the payer's location, device and provider support.

12. Alternate settlement

Alternate settlement is a Pro-mode choice. If a card or on-ramp route cannot support the exact stablecoin or network selected by the requester, the provider may settle the payment in another supported stablecoin.

Key points:

• alternate settlement must be enabled by the requester
• it is not automatic for every Pro request
• the received asset may differ from the originally selected asset
• where the provider returns the information, Amy displays the final settlement asset and receiver amount
• if receiving the exact asset and network matters, use a wallet-only request and leave alternate settlement disabled

13. Creating and sharing a request

1. Open Get Paid.
2. Choose Simple or Pro.
3. Enter the request details, including who the request is from, what the payment is for and any useful short description.
4. Enter the requested USD amount.
5. In Pro, choose the supported stablecoin and network.
6. In Pro, select the payment methods to offer and whether alternate settlement is allowed.
7. Generate the payment link.
8. Copy, share or display the QR code.
9. Track the request in Get Paid history.

Sharing options include a copied link, QR code or your device's standard share options.

Anyone with the link can open the public payment page and may see the display or business name, payment title, description, requested amount, selected stablecoin and network, and receiving wallet address. Do not include confidential, sensitive or unnecessary personal information in the payment title or description. Share the link only with the intended payer.

14. Request history and statuses

Created Get Paid requests appear in your Get Paid history. Each entry may show:

• payment title
• requested amount and asset
• expected receiver amount after fees
• network
• status
• Copy link, QR, Edit and Delete options

Get Paid uses four states.

• Pending. The request has been created and is still available for payment. A failed or abandoned payment attempt does not close it. The payer can try again.
• Paid. The payment has completed and been confirmed. The link cannot be used again.
• Cancelled. The requester cancelled the request before payment. The public link becomes unusable.
• Unavailable. The selected asset, network or provider route is no longer available.

15. Editing or cancelling a request

After a request is created, you can edit descriptive information such as the display or business identity, payment title and short description.

The following cannot be changed after creation:

• requested amount
• asset
• network

To change the amount, asset or network, cancel the unpaid request and create a new one. Cancelling makes the public link unusable. A Paid request cannot be reused.

16. Fees

Pay. Amy does not charge a separate send fee. The sender pays the relevant network gas fee. Gas goes to the network, not to Amy.

Get Paid. The payer pays the face value shown in the request. Provider and Amy fees are deducted from the amount received by the requester. The request history shows the expected receiver amount after the currently calculated fees where available.

Fees can vary by provider, payment route, asset, network and payment method. The payer should be shown the applicable payment total and provider costs before confirmation. The requester can see the expected receiver amount in Amy.

17. Settlement and custody

Amy does not custody the funds. Pay moves assets directly from the sender's wallet to the recipient address. Get Paid routes the payment through the selected wallet or available provider flow for settlement to the receiving wallet.

Timing depends on network and provider confirmation. Amy cannot guarantee instant settlement. Status may take time to update.

18. Who handles what

Amy provides:

• the Pay and Get Paid interface
• the supported asset, network and payment-route choices shown in the interface
• request creation
• links and QR codes
• histories and statuses
• routing into supported thirdweb payment flows

thirdweb and connected providers may handle:

• wallet connection
• card or on-ramp payment
• payment processing
• conversion
• provider checks and transaction limits
• geographic availability
• settlement
• provider fees

Provider terms and privacy information may apply where a payer uses a provider service.

Amy does not custody user funds, process card payments itself, reverse confirmed onchain transfers or control provider availability and checks.

19. Checking a payment and getting help

Before confirming any payment:

• verify the recipient wallet address
• verify the asset
• verify the network
• verify the amount
• review any fees

Confirmed onchain transfers are normally irreversible. Once confirmed on the network, they cannot be reversed.

If a transaction, request status, receiver amount or available payment route appears missing or incorrect, contact the Amy team with the relevant wallet, network, asset, request or transaction details. Amy can review the interface, request record, displayed status and transaction information available to Amy. When contacting support, share only the wallet address, request reference, transaction hash or other non-sensitive details needed to investigate the issue.

Underlying payment or settlement information may also need to be checked with thirdweb, the connected provider or the relevant blockchain network. Provider or network confirmations can be delayed, so you may occasionally need to reload the page or check the receiving wallet and chain explorer.

Never send Amy support your seed phrases, private keys, full card details, passwords or one-time security codes. Amy support will never need your seed phrase or private key.

20. Worked examples

A user wants to send 2 BERA to another wallet on Berachain. They select BERA, enter the recipient address and amount, review the details and confirm through their connected wallet. After confirmation, the transfer appears in Pay history with the relevant explorer link.

A user wants to request $50 through Simple. Amy creates a one-time request for the current default route, USDT on BSC. The payer sees the wallet or card-based methods currently available for their country, device and provider route.

A project creates a Pro request for USDC on Base and enables wallet payment because it wants settlement on that network.

A Berachain user or partner requests HONEY on Berachain. Wallet payment is the clearest route where the exact asset and network matter. Card-based routes may be unavailable for that exact asset and network. Where alternate settlement is enabled, the provider may instead settle in another supported stablecoin.

A failed card attempt leaves the request Pending so the payer can retry. If the requester cancels it, the state becomes Cancelled and the link stops working.

21. Changes and current information

Supported assets, stablecoins, networks, payment methods, provider routes, fees, limits and geographic availability may all change over time.

The live Pay page shows what is currently available for your connected wallet. The payer's public checkout page shows the payment methods currently available for their location, device and selected request.

Simple rule

Use the guide to understand how Pay & Get Paid works. Use the live page to see what is currently available.