Countries & Providers

Amy provides the software interface. Some features depend on third-party providers for wallet connection, authentication, payment processing and on-ramp services. This page explains how provider availability and country support affect what you can do within Amy.

1. Amy and third-party providers

Amy provides the software interface and routes eligible transactions through provider-powered flows. thirdweb provides the underlying wallet connection, authentication and supported payment or on-ramp infrastructure. Amy is designed to show the available route, fees and requirements before you confirm a transaction, where that information is supplied through the provider flow.

Amy does not operate the provider's KYC, card checks or settlement systems. The provider decides whether it can support a specific user, payment method, country and transaction.

Simple rule

Amy provides the interface. The provider decides whether the transaction is supported.

2. Browsing Amy

You may browse public parts of Amy regardless of whether a provider transaction is available in your country. Browsing the software is separate from being eligible to use a provider-powered payment or on-ramp flow. You may be able to create or view an Amy account but still be unable to complete a particular provider transaction.

3. Provider-dependent features

Some Amy features depend on third-party infrastructure. Current provider-dependent features include wallet connection and in-app wallet access through thirdweb, card or supported wallet payment flows, Apple Pay where supported, on-ramp flows, payment-request checkout, settlement to a supported destination and provider-powered transaction processing.

Available methods are shown in the live provider flow.

4. Country availability

Provider support varies by country and sometimes by region. Amy does not maintain its own independent country blocklist. A country may be supported for one provider flow but not another. A supported country does not guarantee every card, bank, currency or asset is supported. Availability may depend on where the payer is located and on the recipient or settlement destination. Provider rules may change.

The live provider flow shows whether the requested route is currently available.

5. Why a transaction may be unavailable

Possible reasons include:

• the payer's country is not supported
• the recipient or settlement destination is not supported
• the payment method is unavailable
• the card issuer declines the payment
• the requested asset, currency or network is not supported
• the transaction is outside provider limits
• provider KYC is incomplete or verification fails
• the provider cannot support the transaction under its legal, compliance or risk rules
• the provider temporarily disables a route or identifies a security concern

6. Provider KYC and verification

Provider-powered payment and on-ramp flows may require you to complete KYC or other checks with the provider. Possible requirements may include full legal name, date of birth, residential address, government-issued identification, selfie or liveness check and payment-method ownership checks.

These checks are completed with the provider. Amy does not conduct the provider's KYC and does not decide whether the provider approves or rejects you.

7. Amy verification versus provider KYC

An Amy account may require a connected wallet, a verified Amy email address and the 18+ and policy declaration. A provider transaction may separately require KYC, payment verification, card checks, country eligibility and transaction review.

Simple rule

Completing an Amy account does not mean you have completed provider KYC.

8. Payment methods

Available payment methods depend on provider support. Current examples may include payment cards, Apple Pay where supported and other methods shown in the live thirdweb-powered flow. Method availability may vary by device, country and provider route. Card acceptance depends on the issuer and provider. The live checkout is the source of truth.

9. Payer and recipient eligibility

A transaction can involve two different eligibility sides.

A route may be available to the payer but unavailable for the selected settlement destination, or the reverse.

10. Assets, currencies and networks

Supported fiat currencies, digital assets and networks are determined by the provider. Not every asset is available in every country and not every network is supported for every payment method. Check the selected route before confirming the transaction. Confirm the destination wallet and network carefully.

11. Fees, rates and limits

Provider transactions may involve provider fees, Amy fees where applicable, exchange-rate conversion, network fees, minimum or maximum transaction amounts and card or payment-method limits.

The live flow should show the available provider and Amy fee information before confirmation. Review the amount paid and the estimated amount received. Final settlement may differ slightly where rates or network costs change.

12. Declined or failed transactions

A provider may decline or fail a transaction. A decline does not necessarily mean your Amy account has a problem. Amy may only receive limited information about the provider's decision. You may need to follow the provider's instructions.

Confirm whether a card was charged before attempting another payment. Report duplicate payments immediately. Possible statuses may include unavailable, verification required, pending, declined, failed, completed or refunded where supported by the provider.

13. Refunds and disputes

Refunds, reversals and payment disputes are handled according to the provider and payment-method rules. Follow the support route shown in the transaction flow. Amy may help identify the provider, transaction reference and visible status, but cannot guarantee a refund or chargeback outcome.

Disputes about the underlying goods, services or agreement remain between the payer and the requester unless a separate Amy feature expressly states otherwise.

14. Legal and provider restrictions

Providers may restrict transactions because of applicable laws, sanctions, fraud controls, security rules or internal risk policies. Providers may block countries or individuals due to sanctions and regulatory obligations. Amy does not override the provider's legal, compliance or sanctions-screening decisions.

The absence of an Amy country block does not mean every provider route is legally or commercially available. You must provide accurate information to the provider. Attempts to bypass country, identity or payment restrictions may result in rejection or account restrictions.

15. Current information and changing availability

Provider support can change. Countries, methods, assets, limits and KYC requirements may be updated. Amy does not maintain a permanent static country list. A previously available route may later become unavailable, and vice versa. The live provider flow is the source of truth for the specific transaction.

Simple rule

Check the live provider flow before relying on a payment or on-ramp route.

16. Getting help

Contact Amy if you need help with:

• identifying which provider powers the flow
• where the transaction status is shown
• which transaction reference to provide
• whether the issue appears to be within Amy's interface
• how to locate the provider support route
• whether a visible fee or status looks incorrect

Provide non-sensitive details such as:

• wallet address
• transaction reference
• provider reference
• date and approximate time
• amount and currency
• selected payment method and settlement details
• visible error message
• a screenshot after removing private credentials, identity documents, card details, verification codes and recovery information

Contact Amy by emailing theteam@amyonbera.com or opening a support ticket in the Amy Discord.

Amy support will never need your seed phrase, private key, full card details or identity-document images. Provider-specific KYC or card issues may need to be handled directly with the provider.

17. Amy's role

Amy provides:

• the software interface and access to integrated provider-powered flows
• provider and transaction information shown within Amy
• fee and status visibility where available
• account and transaction references
• support for Amy interface issues
• records and reporting available through the product

Amy does not:

• operate thirdweb's KYC process or decide which countries it supports
• approve or reject provider users or guarantee card or Apple Pay acceptance
• guarantee every asset, currency or network is available
• override provider limits, legal restrictions or sanctions screening
• guarantee that a transaction will complete
• custody provider funds or act as the card processor, bank or on-ramp provider
• guarantee refunds or chargeback outcomes

18. Worked examples

A user can open and browse Amy, but the live provider flow says the on-ramp route is unavailable in their location. They can continue browsing but cannot complete that transaction.

A user starts a card-funded transaction. The provider asks for identity information. The user completes the checks directly with the provider. Amy does not review the KYC decision.

A user expects Apple Pay but it does not appear. The method may be unavailable because of the country, browser, device, card or provider route.

A payer is in a supported country, but the selected settlement destination is not supported. The route cannot be completed.

A user completes the Amy account and passes provider KYC, but the card issuer declines the payment. The Amy account remains valid. The decline must be resolved with the issuer or provider.

A route worked previously but later becomes unavailable because the provider changed its country, payment-method, asset or compliance support. The live flow shows the current position.

19. Current information

The live provider flow and checkout screen show the options currently available for the specific transaction. Review them before confirming a provider-powered payment or on-ramp transaction.

Simple rule

Use this guide for the general model. Use the live provider flow for the current transaction.