Softwr

APIs · head to head

Lithic vs Merge

Lithic logo

Lithic

APIs

API-first card issuing platform with direct Visa, Mastercard and Amex network connections

From
On request
Rated
-
Full reviewWebsite
Merge logo

Merge

Automation Integration

One API for all your integrations

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Merge has a free tier, so it costs nothing to try first.
  • Each has a real cost: Lithic pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation.; Merge cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • They diverge on capability: Lithic covers Direct network connections, Merge covers Unified API.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Lithic and Merge actually diverge.

Attributes where Lithic and Merge differ
AttributeLithicMerge
Starting priceOn requestFree
Pricing modelquoteusage-based
Free tierNoYes
PlatformsWeb, APIApi
CategoryAPIsAutomation Integration
FoundedUnknown2020

Identical on both: user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Lithic

  • Direct network connections
  • Processor Client mode
  • Lithic Program Management
  • Card lifecycle APIs
  • Sandbox environment
  • Real-time authorization controls

Only in Merge

  • Unified API
  • HRIS integrations
  • Accounting integrations
  • CRM integrations
  • ATS integrations
  • Ticketing integrations
  • File storage integrations
  • Workday

What people use each for

The jobs each tool is most often brought in to do.

Lithic

  • A fintech wanting direct Visa or Mastercard network access rather than routing through a third-party processornot Merge
  • A company that already holds its own issuing licence and wants API access without full programme managementnot Merge
  • A neobank or expense platform wanting Lithic to manage bank and network relationships end to endnot Merge
  • A product team prototyping a card programme in sandbox before committing to a launchnot Merge

Merge

  • Workflow Automationnot Lithic
  • Data Integrationnot Lithic
  • Process Automationnot Lithic
  • App Integrationnot Lithic
  • API Connectivitynot Lithic

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Lithic

  • Pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation.
  • Choosing Processor Client mode still leaves the company responsible for holding its own issuing licence and managing the regulatory relationship, which is a substantial undertaking many teams underestimate.
  • As with any card infrastructure provider, an outage or network issue at Lithic becomes a direct outage for every card programme built on it, and a customer has limited visibility into root cause during an incident.
  • Building a card programme on API infrastructure requires real engineering investment; it is not a plug-and-play product for a non-technical team.
  • Switching card infrastructure providers after launch is a major undertaking involving card reissuance and programme migration, so the initial choice carries lasting lock-in.

Merge

  • Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
  • No support for legacy systems without APIs; limited to modern SaaS applications
  • Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs

Pricing, plan by plan

Lithic

On request
  • Lithic$undefined/year
    • Volume and interchange-based pricing, not published
    • Separate Processor Client and Program Management pricing tracks
    • Custom quote required via sales

Merge

Free
  • FreeFree
    • 1 linked account
    • All integrations
    • Standard support
  • Launch$650/month
    • 50 linked accounts
    • All categories
    • Email support
  • Scale$2500/month
    • Unlimited accounts
    • Priority support
    • SLA
  • Enterprise$undefined/month
    • Dedicated support
    • Custom contracts
    • Advanced security

Which should you pick?

Choose Lithic if

  • You need direct network connections.
  • You work on Web, API.
  • You also want processor client mode.
Lithic review

Choose Merge if

  • You need unified api.
  • You want to start without paying.
  • You work on Api.
  • You also want hris integrations.
Merge review

Questions people ask

Is Lithic or Merge better?
Neither clearly leads. Lithic starts at On request and Merge at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lithic or Merge?
Merge has a free tier; the other does not. Paid plans start at On request for Lithic and Free for Merge.
Does Lithic or Merge run on more platforms?
Lithic runs on Web, API. Merge runs on Api.
Can I use Merge for free?
Yes. Merge has a free tier, so you can try it without paying. Lithic starts at On request.
What is Lithic best used for?
Lithic is most often used for a fintech wanting direct visa or mastercard network access rather than routing through a third-party processor, a company that already holds its own issuing licence and wants api access without full programme management, a neobank or expense platform wanting lithic to manage bank and network relationships end to end, a product team prototyping a card programme in sandbox before committing to a launch. Of those, a fintech wanting direct visa or mastercard network access rather than routing through a third-party processor and a company that already holds its own issuing licence and wants api access without full programme management are not what Merge is typically brought in for.
What can Lithic do that Merge cannot?
Lithic covers Direct network connections, Processor Client mode, Lithic Program Management, Card lifecycle APIs. Merge covers Unified API, HRIS integrations, Accounting integrations, CRM integrations.

Answered from the vendors’ own pages

Lithic: Does Lithic publish pricing?

No, pricing is volume-based and requires a sales conversation.

Merge: What is a Linked Account in Merge?

A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.

Source
Lithic: What is the difference between Processor Client and Program Management?

Processor Client suits companies with their own issuing licence and bank relationships; Program Management is for companies wanting Lithic to coordinate those relationships on their behalf.

Merge: Can I access custom data not in Merge's universal schema?

No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.

Source
Lithic: Which networks does it connect to?

Visa, Mastercard and American Express directly.

Merge: What happens if I switch away from Merge?

Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.

Merge: Does Merge work with legacy systems?

No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.

Share

Related pages

More on Lithic

More on Merge

Keep looking

Other head to heads