APIs · head to head
Basis Theory vs Zeplo

Basis Theory
APIs
Developer tokenisation platform that holds card and sensitive data inside a PCI Level 1 environment you do not operate
- From
- $995/month
- Rated
- -

Zeplo
APIs
Message queue as a URL prefix, adding retries and delays to any HTTP request
- From
- Free
- Rated
- -
The short version
- Only Zeplo has a free tier, so it costs nothing to try first.
- Each has a real cost: Basis Theory the Starter plan is 995 US dollars a month before any volume, which is a real floor for an early stage company and puts the product out of reach of teams tokenising a few thousand records.; Zeplo zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
- They diverge on capability: Basis Theory covers Tokenisation API, Zeplo covers URL prefix interface.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Basis Theory and Zeplo actually diverge.
| Attribute | Basis Theory | Zeplo |
|---|---|---|
| Starting price | $995/month | Free |
| Pricing model | Per month by token volume | Per month by request count |
| Free tier | No | Yes |
| Platforms | Web, iOS, Android, Linux | Web, Cloud |
Identical on both: user rating (Not yet rated), category (APIs).
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 Basis Theory
- Tokenisation API
- Hosted elements
- Outbound proxy
- PCI attestation of compliance
- Processor portability
- Reactors
- Access controls and audit
- PII and PHI options
Only in Zeplo
- URL prefix interface
- Retries with backoff
- Delayed delivery
- Cron scheduling
- Concurrency limits
- Deduplication keys
- Request logs
- Team workspaces
What people use each for
The jobs each tool is most often brought in to do.
Basis Theory
- A payments company that wants card on file without bringing its own infrastructure into PCI scope and paying for the assessment that followsnot Zeplo
- A merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirernot Zeplo
- A fintech collecting bank account and identity data that needs it isolated from its application database before an enterprise security reviewnot Zeplo
- A team that needs to send stored card data to a third party for a one-off integration without that data traversing its own serversnot Zeplo
Zeplo
- A Vercel or Cloudflare Workers application that needs retried background jobs without deploying a separate always-on workernot Basis Theory
- A team that wants a webhook receiver protected by a concurrency limit so a burst does not overwhelm a downstream APInot Basis Theory
- A small product needing cron jobs against HTTP endpoints without adding a scheduler to its infrastructurenot Basis Theory
- A developer adding idempotent retries to an unreliable third-party API call with a one-line URL changenot Basis Theory
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Basis Theory
- The Starter plan is 995 US dollars a month before any volume, which is a real floor for an early stage company and puts the product out of reach of teams tokenising a few thousand records.
- Starter is limited to the US region, so a company with European data residency requirements is pushed into a quoted Scale or Enterprise agreement immediately.
- Log retention on Starter is 24 hours, which is well below what most security teams expect for a system holding cardholder data and forces an upgrade for reasons unrelated to volume.
- Migrating away means moving card data out of the vault, which requires processor and assessor involvement and is slow, so the portability argument that attracts buyers cuts against them at exit.
- An attestation of compliance covers the vendor environment, not your assessment; your assessor still decides what is in scope, and buyers occasionally discover their integration pattern pulled systems back into scope anyway.
Zeplo
- Zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
- The free Developer tier includes only 500 requests a month and one team member, so it is a demonstration allowance rather than a usable free plan for anything real.
- Overage on the Developer tier is 20 US dollars per 100,000 requests, two hundred times the marginal rate on the Company tier, so exceeding the free allowance without upgrading is expensive.
- Team members cost 15 US dollars each beyond the plan allowance, which is an odd charge on an infrastructure product billed by request volume.
- Log retention is 30 days on both published tiers, so anything requiring longer audit trails on job execution has to be logged separately.
Pricing, plan by plan
Basis Theory
$995/month- Starter$995/month
- 20,000 tokens included
- Production PCI Level 1 environment
- US region only
- Scale$undefined/month
- Quoted
- Higher token volumes
- Additional regions
- Enterprise$undefined/month
- Quoted
- Additional compliance options for PII and PHI
- Responses for 95 percent of PCI SAQ D
Zeplo
Free- DeveloperFree
- 500 requests a month included
- $20 per additional 100,000 requests
- 1 team member
- Company$39/month
- 1,000,000 requests a month included
- $10 per additional million requests
- Up to 3 team members
- Enterprise$undefined/month
- Volume discounts
- Custom team size
- Support with SLA
Which should you pick?
Choose Basis Theory if
- You need tokenisation api.
- You work on Web, iOS, Android, Linux.
- You also want hosted elements.
Choose Zeplo if
- You need url prefix interface.
- You want to start without paying.
- You work on Web, Cloud.
- You also want retries with backoff.
Questions people ask
- Is Basis Theory or Zeplo better?
- Neither clearly leads. Basis Theory starts at $995/month and Zeplo at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Basis Theory or Zeplo?
- Zeplo has a free tier; the other does not. Paid plans start at $995/month for Basis Theory and Free for Zeplo.
- Does Basis Theory or Zeplo run on more platforms?
- Basis Theory runs on Web, iOS, Android, Linux. Zeplo runs on Web, Cloud.
- Can I use Zeplo for free?
- Yes. Zeplo has a free tier, so you can try it without paying. Basis Theory starts at $995/month.
- What is Basis Theory best used for?
- Basis Theory is most often used for a payments company that wants card on file without bringing its own infrastructure into pci scope and paying for the assessment that follows, a merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirer, a fintech collecting bank account and identity data that needs it isolated from its application database before an enterprise security review, a team that needs to send stored card data to a third party for a one-off integration without that data traversing its own servers. Of those, a payments company that wants card on file without bringing its own infrastructure into pci scope and paying for the assessment that follows and a merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirer are not what Zeplo is typically brought in for.
- What can Basis Theory do that Zeplo cannot?
- Basis Theory covers Tokenisation API, Hosted elements, Outbound proxy, PCI attestation of compliance. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.
Answered from the vendors’ own pages
Basis Theory: Does this make us PCI compliant?
It removes cardholder data from your systems and gives you an AOC plus documented responses for most of a SAQ D. Your assessor still determines your scope, and a careless integration can pull systems back in.
Zeplo: How does Zeplo work?
You prefix your endpoint URL with zeplo.to and add query parameters for retries, delay, cron or concurrency. No SDK or broker is needed.
Basis Theory: What does it cost to start?
995 US dollars a month on Starter, including 20,000 tokens, a production PCI Level 1 environment and US hosting. Higher tiers are quoted.
Zeplo: What does it cost?
Free for 500 requests a month; 39 US dollars a month for a million requests, then 10 dollars per additional million.
Basis Theory: Can we switch payment processors without re-collecting cards?
Yes, that is the main non-compliance reason to buy it. You hold the tokens and detokenise into whichever processor you route to.
Zeplo: Is it suitable for critical jobs?
It is a small vendor in your execution path with no published SLA below Enterprise, so weigh that against the convenience.
Basis Theory: Is data stored outside the United States?
Not on Starter, which is US only. Other regions require a Scale or Enterprise agreement.
Zeplo: Does it work with serverless platforms?
Yes, that is its main use, covering Vercel, Cloudflare Workers, Netlify and similar environments that lack long-running workers.
Related pages
More on Basis Theory
Other head to heads
- Basis Theory vs Skyflow
- Basis Theory vs Increase
- Basis Theory vs Lithic
- Basis Theory vs Volt
- Basis Theory vs Swan
- Basis Theory vs Moov
- Basis Theory vs Trustly
- Basis Theory vs Vodeno
- Basis Theory vs TrueLayer
- Basis Theory vs Paymentology
- Basis Theory vs Akoya
- Basis Theory vs Sila
- Basis Theory vs Backbase
- Basis Theory vs Enfuce
- Basis Theory vs Griffin
- Basis Theory vs Stoplight
- Basis Theory vs Svix
- Basis Theory vs AWS API Gateway
- Basis Theory vs Tink
- Basis Theory vs Pusher
- Basis Theory vs Yodlee
- Basis Theory vs Tribe Payments
- Basis Theory vs Unit
- Basis Theory vs Convoy
- Basis Theory vs Boomi API Management
- Basis Theory vs Codat
- Basis Theory vs curl
- Basis Theory vs Fintech Farm
- Basis Theory vs Fintecture
- Zeplo vs Skyflow
- Zeplo vs Increase
- Zeplo vs Lithic
- Zeplo vs Volt
- Zeplo vs Swan
- Zeplo vs Moov
- Zeplo vs Trustly
- Zeplo vs Vodeno
- Zeplo vs TrueLayer
- Zeplo vs Paymentology
- Zeplo vs Akoya
- Zeplo vs Sila
- Zeplo vs Backbase
- Zeplo vs Enfuce
- Zeplo vs Griffin
- Zeplo vs Stoplight
- Zeplo vs Svix
- Zeplo vs AWS API Gateway
- Zeplo vs Tink
- Zeplo vs Pusher
- Zeplo vs Yodlee
- Zeplo vs Tribe Payments
- Zeplo vs Unit
- Zeplo vs Convoy
- Zeplo vs Boomi API Management
- Zeplo vs Codat
- Zeplo vs curl
- Zeplo vs Fintech Farm
- Zeplo vs Fintecture
