Alchemy Pay: crypto ramp dealing, payment costs and regional terms

The Swiss agreement describes Alchemy Pay AG acting as the customer’s agent to obtain fiat or crypto on the customer’s instructions. This establishes a direct exchange-execution role, although the user-facing transaction is a quote-based conversion rather than a central limit-order-book trade.[1]

The documented buy flow refreshes its displayed rate every 15 seconds and asks for an existing wallet address before payment. The sell guide uses a randomly generated, single-use deposit address. That address is tied to the particular sale and should not be saved as a reusable funding destination. A wallet or exchange embedding the checkout is a separate service provider, so its branding alone does not determine who handles a delayed payment.[9][10]

The accessible help-centre tariff was last updated on 21 October 2024. It remains useful as a dated description of how card and Indonesian payment costs were expressed, but it does not establish the current charge for every entity, partner or country. Its figures are reproduced with that limitation; a customer needs the applicable checkout breakdown before committing a transaction.[11]

The Swiss agreement instead specifies processing and network charges displayed before the order, with fees payable in EUR. The older help page says delayed settlement can change the final crypto quantity. These disclosures should not be combined into a promise that the first displayed amount is locked regardless of payment timing.[1][11]

For comparing two available rails, the useful figure is the net asset amount received for the same fiat outlay, asset and network. A fixed local-currency fee affects a small transaction more than a large one, while a different blockchain can change delivery costs. Save the final screen rather than relying on a marketing percentage or an older screenshot from a different country. The signed-checkout documentation also allows a partner to fix several inputs before the customer arrives.[25]

Buying and selling have different completion clocks. The delivery guide describes a few minutes to a few hours after payment, depending on the order and security checks. The sale guide instead gives approximately three working days for fiat receipt after crypto processing. These are provider estimates for different stages, not a single guaranteed end-to-end deadline. A payment authorisation or a blockchain broadcast alone does not prove that the destination has received usable funds.[17][10]

The Swiss agreement bars customer cancellation after an order is placed. Provider rejection or a failed transaction has a different recovery process. The older failed-sale guide permits corrected bank details and resubmission, or a refund request from order history, and gives a 24-hour processing expectation. Bank and blockchain charges can remain.[1][19]

There is also an unresolved fee distinction: the July 2024 help pages say Alchemy Pay does not charge for failed transactions or refunds, whereas the Swiss agreement permits a processing charge on a rejected order. Consequently, neither the old no-fee wording nor its timing estimate should be presented as an unconditional current refund promise. The reason for failure, applicable entity and refund rail need to accompany the request.[18][19][1]

Alchemy’s wallet guide allows delivery to a mobile, browser, hardware or exchange-hosted wallet. Those destinations do not all give the customer the same private-key control. The important distinction is who controls the receiving wallet after delivery; access to the ramp’s transaction history does not itself make that external wallet recoverable through Alchemy Pay.[21][22]

The company’s fraud guide addresses a practical risk particular to payment ramps: a legitimate crypto purchase can be the payment step in somebody else’s false investment, job or account-unlocking story. Successful delivery by Alchemy Pay does not verify the promised use of the crypto at another service. The guide directs customers unsure about an order to official support and warns against impersonated support using remote-access software.[23]

The January excluded-country list includes, among others, mainland China, Russia, Ukraine, Iran, Cuba and North Korea. Broad marketing references to coverage in more than 170 countries do not replace that list or establish a right to use a particular fiat corridor. The KYC country selector, residency rules and applicable operating entity must agree with the requested transaction.[15][8]

The verification-time guide describes automatic feedback within about a minute in many cases, but says document review can take from several minutes to 24 hours. Those are published estimates from a March 2024 help article. Poor images or documents requiring manual review can extend the process; a payment-time estimate should not be mistaken for a commitment to complete onboarding in the same interval.[16]

When an account reaches its allowance, the limits guide instructs the customer to wait for the displayed reset time or ask support about a review. It does not give one universal daily or monthly reset schedule for every customer. The partner asset-query documentation also returns minimum and maximum values at asset/network level, reinforcing that a general USD2,000 example is not enough to establish the size permitted on a specific route.[13][27]

The Transactions menu groups buy and sell orders, making it the documented starting point for reconciliation. A partner’s order identifier and Alchemy’s own identifier can differ, so retain both where available. The public history instructions establish how to view records, but do not establish a standard customer CSV export or tax statement. This matters when a customer has made purchases through several unrelated wallet integrations.[22][25]

The company contact page states a response target within 24 hours; it is not evidence from a support test or a promise of final resolution. No distinct emergency dealing desk or universal formal-complaint deadline was established in the reviewed support material. FINMA directs reports about SRO-affiliated intermediaries to the responsible SRO, but that supervisory route should not be described as a guaranteed customer compensation process.[24][6]

Alchemy Pay’s Swiss site publishes VQF membership number 101208 and explicitly says Alchemy Pay AG is not authorised under MiCA. The membership number is a company disclosure: a matching current member result was not independently retrieved for this profile. FINMA explains that affiliated intermediaries are supervised by their SRO for the relevant AML obligations, rather than directly by FINMA. This distinction prevents an SRO membership claim from being recast as a bank licence.[4][5]

The Swiss site’s references to customers approaching the service on their own initiative do not establish blanket permission to serve every jurisdiction. Nor do group announcements about another country automatically extend the Swiss entity’s authority there. No current customer-level insurance schedule or compensation entitlement was established for these conversions. A membership number, company registration and insurance policy are separate matters.[4][5]

The transfer notice identifies Alchemy Pay AG by Swiss company number CHE-494.441.537 and says existing account details continue, with possible requests to refresh KYC. It describes transfer of customer data from the Lithuanian operator. Its penalty-free opt-out concerned that transition; the Swiss agreement separately allows expenses on termination. Account continuity therefore should not be interpreted as proof that the legal counterparty or every closure condition stayed the same.[2][1]

Everest Ocean s.r.o. remains named in the retained ramp terms, while Golden Alpha Capital Pty Ltd appears in the regional terms index. The visible documents do not fully reconcile those references with the Swiss transfer notice. The applicable confirmation and contract need to identify the actual entity before a customer relies on any jurisdictional protection; no Czech CASP authority is inferred from a company listing.[2][3]

Alchemy’s anniversary article dated 7 October 2025 reports 4.2 million users and describes a business founded in 2017. That is historical, company-claimed user reach, not a current count of active traders. The broader payment-network and merchant-coverage figures in its company description also measure distribution rather than audited exchange turnover. They support the brand’s relevance in fiat-to-crypto access without establishing an order-book volume rank.[7][8]

Operator

Alchemy Pay AG for the Swiss ramp; additional regional entities remain in the published terms index

Exchange model

Centralised

Service scope

Quoted fiat-to-crypto purchases and crypto-to-fiat sales through direct and partner checkouts; Swiss agreement describes agency execution.

Client types

Retail clients

Pricing publication

Public and quoted pricing

Pricing scope

Current Swiss terms use displayed processing and network charges; available numerical help tariff is dated October 2024 and is not presented as universally current.

Funding scope

Cards and country-specific local payment rails; older public method lists require current checkout confirmation.

Custody and asset handling

Purchase delivery to a customer-specified external wallet; the ramp and the destination wallet have separate control and recovery arrangements.

Client eligibility

Supported residency, KYC, asset/network and payment method required; regional operator allocation and the older upper-age condition are not fully reconciled.

Support

Official support email, help-centre requests, order history and a published response target.

Authorisation and registration scope

Swiss site claims VQF membership 101208 and expressly disclaims MiCA authorisation. SRO supervision is scoped to AML; no worldwide permission or insurance inferred.

Exchange metadata checked 21 Oct 2026Source 1Source 2Source 3Source 4Source 9Source 10Source 11Source 13

The integration guide covers browser pages and embedded mobile web experiences. The payment-troubleshooting guide also identifies an Apple Pay authentication error for which it advises iOS above 16.1; that is a documented troubleshooting condition, not a universal device compatibility guarantee. An account may therefore be accessible while one authentication or payment path fails on a particular device.[30][20]

Request signing authenticates merchant API messages using a shared secret; it is distinct from control of a customer’s wallet private key. The webhook guide recommends querying the order as well as handling callbacks, and limits optional callback retries to on-ramp orders. For customers, the practical result is to use the order record and delivery evidence when an embedded app appears stalled. The public documentation does not establish an autonomous AI trading mandate.[26][29]