Alchemy Pay

Service Overview

Alchemy Pay was founded in 2017 and positions itself as a payment gateway connecting fiat and the crypto economy. The key word is gateway: what it sells is not a single acquiring capability but the passage between the fiat side and the crypto side — letting users without crypto buy coins with cards or local payment methods, and letting merchants accept coins and move value where they need it.

The official site cites payment coverage in 173 countries across four product lines. On and Off Ramps is the core, handling fiat purchases and sales of crypto assets. Token Listing serves projects by making tokens purchasable and visible inside its rails. Card is a white-label crypto card in virtual and physical form for partners who want to turn crypto balances into swipeable spending. Crypto Payment is the collection line for merchants.

Among the four, On/Off Ramps is the main battlefield, and that shapes the capability profile. The hard part of on-ramp is not technology but local payment method coverage and licensing: every country has different card networks, wallets and transfer rails, and different KYC requirements. Covering 173 countries means substantial investment in that problem, but it also means quality varies widely — smooth in some markets, only one or two methods in others.

On compliance, the site cites a PCI DSS service provider AOC and money transmitter licenses in 20 US states as of an October 2026 update, including Mississippi. Twenty states is not fifty, and that difference matters in cross-border deployment: uncovered states cannot be served under those licenses. The ACH network token is deployed on Ethereum and BNB Chain for ecosystem incentives and network settlement, but it has no direct link to the technical capability of the payment rails.

Ecosystem partners underpin the product, with publicly listed names including Binance, Coinbase, OKX, Crypto.com, Bitfinex, Kraken, Uniswap and PancakeSwap. Those on-ramp integrations show the rails have been validated in exchange settings, which matters more to wallets and trading platforms embedding a buy entry point than to pure e-commerce.

Where the need lands decides the fit. If it is "let users without crypto pay by card or local method and land on crypto rails", the capability combination is right. If it is only "let customers pay in coins", acquiring depth is thinner than with dedicated acquirers, and the local payment method list plus settlement path in each target market must be confirmed rather than inferred from the 173 headline.

Key Strengths

• On-ramp coverage is the core asset: 173 countries means most markets have an available path, and for wallets and trading platforms needing a global buy entry point that coverage decides whether a market can launch at all.
• Four product lines compose: buying, listing, card issuance and collection live in one ecosystem, so a partner can take one line or combine several instead of sourcing each capability separately.
• Rails validated by major platforms: integrations with Binance, Coinbase, OKX, Crypto.com and others show the on-ramp has run under high concurrency and compliance scrutiny, which is meaningful backing for buyers.
• The card line covers spending: white-label crypto cards turn balances into swipeable spending, solving the "coins sit in an account but cannot be spent daily" problem and helping retention.
• PCI DSS service provider AOC: card data handling has been assessed under PCI DSS, which is required material when proving card-data security posture to partner banks or auditors.
• US coverage already spans 20 states: short of 50, but 20 state money transmitter licenses show a genuine US compliance track rather than reliance on an offshore entity alone.

Product Ecosystem

On and Off Ramps

The core passage between fiat and crypto: users buy crypto with fiat or sell crypto back to fiat. Real-world quality depends on card network, local wallet and transfer coverage in the target country plus the smoothness of KYC, and must be validated market by market.

Token Listing

Serves projects by making tokens purchasable and visible within the rails. For early-stage projects, entering a mainstream on-ramp buy list directly affects user acquisition and often lands faster than an exchange listing, though admission standards and compliance requirements move with regulation.

Card (White-Label Crypto Card)

Virtual and physical forms that partners can issue under their own brand to spend crypto balances. Issuance involves card networks, issuing banks and multi-country regulation, so timeline and available regions depend on the partnership structure rather than integration alone.

Crypto Payment

Collection for merchants where customers pay in crypto and the merchant settles as agreed. This is the line closest to acquiring, but versus dedicated acquirers its depth — multi-chain support, settlement policy, reconciliation tooling — must be confirmed per project.

Network Token and Ecosystem (ACH)

ACH runs on Ethereum and BNB Chain for ecosystem incentives and in-network settlement. It is an ecosystem-layer design with no direct link to payment rail capability, so procurement decisions should rest on rail coverage, licensing and fee structure rather than token performance.

API and Integration

Interfaces let wallets, trading platforms and merchant systems connect ramps and collection, with capabilities, limits and supported payment methods governed by official documentation and commercial confirmation. Validate one target country end to end before replicating elsewhere.

Limitations

• Acquiring is not the main battlefield: Crypto Payment is 1 of 4 lines, and multi-chain coverage, settlement policy and reconciliation depth trail dedicated acquirers. For pure collection needs it can be the more expensive and more circuitous choice.
• US licenses fall short of 50 states: 20 states means uncovered states cannot be served under those licenses and multi-state business must be checked state by state. That is a hard constraint in US expansion, not something negotiation removes.
• Unavailable to mainland China entities: virtual-currency business activity is prohibited there, on-ramp has no compliant path domestically, and overseas entities serving mainland users still face regulatory risk.
• Local payment methods differ sharply by country: 173 countries is a coverage figure, and a given market may offer only one or two methods with materially different success rates. Test the actual method list and success rate before integrating.
• Do not conflate token with capability: ACH price and incentive cadence are unrelated to rail performance. Including token performance in vendor selection is the most common misjudgement around projects of this type.
• Inconsistent pricing basis: ramps, card issuance and collection have entirely different fee structures with no unified public list, so comparison requires confirming each product line separately.

Use Cases

• Wallets and trading platforms embedding a buy entry point (★★★★★): when users must buy crypto with fiat inside the app, on-ramp coverage and rails validated by major platforms are precisely the core capability.
• Fiat funding for emerging markets (★★★★☆): where local payment methods are diverse, breadth beats single-rail depth, though success rates must be tested per country rather than inferred from totals.
• Platforms needing a white-label crypto card (★★★★☆): turning user balances into swipeable spending is covered by the card line, with timeline set by the partnership structure.
• Mixed businesses needing both ramps and collection (★★★☆☆): the four lines compose with relatively consistent interfaces and reconciliation, but acquiring depth needs project-level assessment and complex scenarios may still need a dedicated acquirer.
• Mainland China operations (☆☆☆☆☆): virtual-currency business is prohibited domestically and on-ramp has no compliant path. Not worth evaluating.
• A store that just wants a crypto button (★☆☆☆☆): the worst fit, since a dedicated hosted acquirer integrates faster, costs less and reconciles more simply.

Pricing

No percentages are listed because each Alchemy Pay product line has a different pricing structure with no unified public schedule. Actual fees, available payment methods and settlement paths follow the commercial quote, official documentation and your contract.

FAQ

• Is Alchemy Pay an acquirer or an on-ramp provider?
  More accurately an on-ramp provider, with acquiring as 1 of 4 product lines. Its core strength is on the fiat side: local payment coverage, KYC flows and licensing. If the need is collection, confirm whether the acquiring line is deep enough.

• Does 173 countries mean every country works?
  No. It is a coverage figure; a given market may offer only one or two payment methods with differing success rates and limits. Test each target market before launch, focusing on the method list, success rate and failure handling.

• Can US business use these licenses directly?
  Only in the 20 covered states. Uncovered states require a separate licensed entity or local partner. Multi-state operations must be reviewed state by state, and if the US is a primary market this constraint directly limits scope.

• How does the ACH token relate to the payment business?
  ACH is an ecosystem and incentive layer on Ethereum and BNB Chain, unrelated to rail capability or settlement stability. Selection should rest on coverage, licensing and fee structure, not token price.

• Can a mainland China company onboard?
  No. Virtual-currency business activity is prohibited there and on-ramp has no compliant path domestically. Overseas entities whose users are mainly in mainland China still need an independent regulatory assessment.

Source: original 16IDC content. Product capabilities, supported countries and fee definitions follow the official documentation and your contract.