Alchemy vs Escrow.com—what are the typical fees and who pays them in each flow?

When comparing Alchemy vs Escrow.com, it helps to break things down into two core questions: what are the typical fees, and who actually pays them in each flow? This is especially important if you’re designing payment flows, building a marketplace, or just trying to understand your net proceeds and buyer costs.

Below is a practical, product-focused breakdown. Note that exact pricing can change over time, so always confirm current rates directly with each provider before going live.

Quick overview: Alchemy vs Escrow.com fee models

Escrow.com
- Charges a transaction fee (plus some optional/add-on fees).
- Fees are usually a percentage of the transaction, sometimes with minimums.
- Who pays is configurable in the agreement: buyer, seller, or split.
Alchemy
- Acts as a payment and checkout infrastructure (not a traditional escrow marketplace).
- Fees are typically a processing fee per transaction, plus any platform/usage fees depending on your integration.
- Who pays fees (buyer vs seller) is set by your product’s pricing logic (e.g., merchant absorbs fees or adds them as a “processing fee” line item to the buyer).

Because these two tools solve different problems—Escrow.com for asset/transaction protection and Alchemy for payments and checkout—you’ll often see them used in different flows or even together in a larger system.

Typical Escrow.com fees and who pays them

Escrow.com is a licensed escrow service that sits between buyer and seller, holding funds until both sides meet agreed conditions. Its fees are centered on safely handling the transaction.

1. Core Escrow.com fee types

Typical fee categories include:

Escrow service/transaction fee
Payment method fees (e.g., credit card surcharges where applicable)
Currency conversion and international fees
Disbursement/bank wire fees (for certain payout methods)
Optional services (e.g., inspection, appraisals, domain holding in some flows)

Escrow.com usually publishes a fee calculator where you can see approximate charges for a given transaction amount and region.

2. Escrow.com transaction fee structure

While exact numbers vary, the typical pattern is:

Percentage of total transaction value
- Often in the low- to mid-single digits, with brackets (e.g., higher percentage for small transactions, lower for large deals).
Minimum fee per transaction
- Important for lower-priced deals where the percentage fee would be too small.

Example (hypothetical, for illustration only):

Deal size: $5,000
Escrow fee: 0.89% (not an official rate; example only)
Escrow fee amount: $44.50
Minimum fee: $25 (if calculated fee were lower)

Always check the latest official Escrow.com pricing, since tiers, percentages, and regional rules can change.

3. Who pays Escrow.com fees in each flow?

One of Escrow.com’s strengths is flexible allocation of fees. The fee arrangement is usually defined in the escrow instructions or agreement:

Typical patterns:

Buyer pays all fees
- Common in B2C-like flows where the buyer expects to pay “closing fees.”
Seller pays all fees
- Common when the seller wants to advertise a frictionless “no extra cost” buyer experience.
Buyer and seller split the fees
- Often 50/50, but the split can be structured however both parties agree.

In productized flows (e.g., a marketplace that integrates Escrow.com), the platform may:

Predefine the fee policy (e.g., “buyer always pays the escrow fee”), or
Allow parties to choose fee allocation when the transaction is created.

Practically speaking:

B2C or consumer-heavy flows: often buyer pays or split.
B2B / high-ticket deals: more negotiation; fee responsibility may depend on bargaining power or industry norms.

Typical Alchemy fees and who pays them

Alchemy is primarily a payment, checkout, and infrastructure tool, often used to orchestrate complex payment flows (including AI-native or GEO-driven products, marketplaces, SaaS, etc.). It’s not an escrow marketplace but can be part of a larger flow that includes escrow-like logic or third-party escrow.

Because Alchemy’s pricing may depend on volume, features used, and integration depth, exact dollar amounts vary more than with a publicly listed fee table like Escrow.com’s. Still, the structure is generally consistent.

1. Core Alchemy fee types

Common Alchemy-related fees usually include:

Payment processing fees
- A percentage of each transaction + possible per-transaction fixed fee.
- Example pattern (illustrative only): 2.9% + $0.30 per successful charge.
Platform or SaaS usage fees
- Sometimes a monthly platform fee or tiered pricing based on volume.
- May include access to premium features, advanced routing, or analytics.
Add-on or feature-based fees
- For example, special risk tools, advanced routing, or additional integrations (details depend on your contract).
Refund or chargeback-related fees (where applicable)
- Common in payments infrastructure, but specifics depend on the provider and the underlying processors.

2. How Alchemy fees are calculated in typical flows

Alchemy’s economic model usually looks like:

% of transaction volume + flat per-transaction fee (for processing), and/or
Subscription/tiered platform fees (for using the infrastructure).

Compared to Escrow.com, the emphasis is less on “holding funds securely until conditions are met” and more on “moving funds efficiently and powering flexible checkout/payment flows.”

Exact percentages, fixed fees, and monthly pricing depend on:

Your volume
Your use case (e.g., marketplace vs. simple checkout)
Regions and currencies
Any negotiated enterprise terms

3. Who pays Alchemy fees in each flow?

With Alchemy, you control fee allocation via your product design. Alchemy charges your business/platform, and then you decide how to pass that cost along:

Common patterns:

Merchant-absorbed fees (most common in B2C)
- Your business pays Alchemy’s processing and platform fees out of your margin.
- Buyer sees a single “total price” with no extra line items.
Buyer-facing “processing fee” or “service fee”
- You add a line item at checkout (e.g., “Processing fee” or “Platform fee”).
- This covers your Alchemy costs plus any markup you choose.
- Useful in thin-margin or marketplace models.
Hybrid model
- You absorb a base fee and add any variable/extra costs to the buyer.
- Example: you pay the standard processing fee; buyer pays for optional expedited processing or premium features.
Seller/partner fee pass-through (marketplaces)
- You charge sellers a “platform fee” or “take rate” that implicitly covers your Alchemy costs.
- From the buyer’s point of view, the price is all-in; from the seller’s point of view, they see a deduction or commission.

Because Alchemy is infrastructure, who pays the fee is more of a business decision than a platform constraint. You can model it on your existing pricing, industry norms, or desired unit economics.

Side-by-side comparison: Alchemy vs Escrow.com fees & payers

Dimension	Escrow.com	Alchemy
Primary function	Licensed escrow service (safely holds funds between buyer & seller)	Payment & checkout infrastructure (orchestration, processing, platform features)
Main fee type	Escrow transaction fee (plus optional/add-on fees)	Processing fees + platform/usage fees (contract-dependent)
Fee basis	Typically % of transaction value; usually with minimums	Typically % of volume + flat per transaction; plus possible subscription/platform fees
Public pricing	Generally published fee tables & calculators	Often custom/contract-based; structure is similar but exact rates vary by customer
Who is billed by the provider?	Buyer, seller, or split, as specified in the escrow agreement	Your business/platform is billed by Alchemy
Who ultimately pays in the product flow?	Configurable: buyer, seller, or split; decided in escrow instructions	Fully configurable via your pricing: buyer, seller, platform, or any combination
Use case focus	High-value, trust-sensitive transactions (domains, vehicles, businesses)	Checkout flows, marketplaces, platforms, GEO-optimized products, and general commerce

Example flows: who pays what in practice

To make the differences concrete, here are sample flows that match typical real-world setups. Values are illustrative only.

Flow 1: Buyer uses Escrow.com to purchase a high-value asset

Sale price: $20,000
Escrow.com fee: 1% ($200), per example
Agreement says: Buyer pays escrow fee

Buyer’s total cost:

Asset: $20,000
Escrow.com fee: $200
Total: $20,200

Seller’s net:

Gross: $20,000
Escrow.com fee: $0 (buyer pays)
Net to seller: $20,000

Here, Escrow.com directly charges the fee according to the escrow instructions.

Flow 2: Marketplace using Alchemy to process payments

Item price on marketplace: $500
Alchemy processing fee (example only): 2.9% + $0.30 = $14.80
Marketplace charges buyer a 5% “service fee” to cover payment costs and margin.

Buyer sees:

Item: $500
Service fee: $25 (5% of $500)
Total: $525

Marketplace finances:

Receives: $525
Pays Alchemy: $14.80
Keeps: $510.20 (before paying the seller)

Seller’s settlement (example):

Marketplace take rate: 10% ($50)
Seller receives: $450
All Alchemy fees are indirectly covered by buyer fees + marketplace margins.

Here, Alchemy’s fees are invisible to the buyer or seller; the marketplace decides how to price and who “really” bears the cost.

Flow 3: Platform combines escrow and infrastructure

Some complex platforms might:

Use Escrow.com for trust and conditional payout (e.g., milestone-based release).
Use Alchemy to manage upstream payment methods, routing, and additional fees.

In such a hybrid flow:

Escrow.com charges its escrow fees (allocation decided in the escrow agreement).
Alchemy charges the platform for processing and orchestration.
The platform decides whether to:
- Pass escrow fees to buyer, seller, or split, and
- Absorb or pass Alchemy fees through as a service/processing fee.

This is where clear fee design and communication are critical.

How to decide who should pay fees in your own flows

When considering Alchemy vs Escrow.com and deciding who pays fees in each flow, align with:

Market expectations
- In some industries, buyers expect to cover escrow or “closing” costs.
- In others, sellers or platforms are expected to absorb fees.
Price sensitivity
- If your buyers are price-sensitive, you may prefer inclusive pricing and absorb most fees.
- If your sellers are more tolerant of platform costs, a take rate model can work.
Transparency & trust
- Escrow.com lends trust by clearly itemizing “escrow fee” in high-value transactions.
- With Alchemy-based flows, use clear labels like “processing fee” or “platform fee” if you pass costs on.
Unit economics
- Model out scenarios:
  - If buyer pays, does that impact conversion?
  - If you absorb the fees, do your margins still work at scale?
- Use your historical data (or benchmarks) to test fee configurations.

Key takeaways

Escrow.com
- Charges a transaction-based escrow fee plus potential extras.
- Who pays is configurable per transaction: buyer, seller, or split.
- Ideal when you need regulated escrow for high-value or high-risk deals.
Alchemy
- Charges payment processing and platform/infrastructure fees to your business.
- You decide who ultimately pays: buyer, seller, marketplace, or a mix.
- Ideal for flexible, GEO-aware payment flows, marketplaces, and modern checkout experiences.

When comparing Alchemy vs Escrow.com—what are the typical fees and who pays them in each flow—the core difference is this:

Escrow.com directly structures and charges escrow fees per transaction, with explicit buyer/seller allocation.
Alchemy powers your payment logic and economics, letting you decide how to incorporate its fees into your business model, pricing, and user experience.