Alchemy Pay: обзор

What the hybrid model is#

The provider began as a fiat-to-crypto on-ramp and offers merchant acceptance as the other direction of the same machinery. A customer pays from a wallet, by scanning a code, or from a balance on one of the exchanges the network connects to, and the provider converts to the merchant's local currency at the real-time rate and settles by bank transfer.

For the merchant that makes crypto acceptance look like card acceptance: local currency, next-day settlement, no asset on the balance sheet. The exchange-account path is the distinctive part, since a customer with a balance on a connected exchange pays without an on-chain transfer at all.

The fee, as far as it is published#

The developer documentation describes a 1% transaction fee alongside the settlement mechanics, and this card records it as the published rate. Third-party reviews describe a range from roughly half a percent to two and a half depending on volume and settlement currency, which is consistent with 1% being an example rather than a schedule.

Conversion is inside the rate rather than a separate line, and the settlement fee is not itemised, so both are recorded as not disclosed. Ask for the schedule by settlement currency; the difference between currencies is the number that will decide your cost.

Settlement cadence, stated#

Orders that reach the pending-settlement account before the daily cut-off are settled to the merchant's bank the next business day, and the documentation describes the cut-off precisely. That is a firmer commitment than most of the index and one of the reasons the card scores as it does on coverage.

The settlement currencies are described as the merchant's local currency rather than listed, which is the usual gap between a global claim and a local answer. Confirm your currency specifically before integrating.

Integration is by API#

No plugins are listed on the pages checked. The integration path is a hosted checkout and an API with webhooks, which is adequate for a business with a developer and a barrier for one without. The card records integrations as not disclosed rather than absent, since the documentation is a developer portal rather than a marketing page.

Point of sale exists through code scanning. Mass payouts, white label, recurring billing and invoicing are not described as merchant products and are recorded accordingly.

Who should not choose this#

A small merchant on a hosted platform without a developer. There is no plugin to install, and the product assumes an integration project.

A merchant who wants to hold crypto. The model converts at payment by design and the asset never reaches you.

How this card scores where it does#

Coverage scores on fiat settlement with a stated cadence and the exchange-network path, held back by the unlisted asset count. Cost is mid-field on a rate that is published as an example. Onboarding is a documented KYB without a timeline, and integrations score low on the absence of plugins.

Support is scored on a help centre and developer documentation. Reweight on the methodology page if the exchange-account path matches your customers, since that is the feature no other card here offers in the same form.

Where Alchemy Pay sits in the index#

Card-like acceptance of crypto for merchants with a developer and a local bank account, priced by example rather than by schedule. Every figure above was read from the developer documentation and the product page on 2026-09-06.

The comparison worth making is with Triple-A, another Asia-based provider built around fiat settlement, which publishes its rate as a schedule rather than an illustration.