APIs · head to head
Basis Theory vs Weavr

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
- -

Weavr
APIs
Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence
- From
- On request
- Rated
- -
The short version
- 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.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
- They diverge on capability: Basis Theory covers Tokenisation API, Weavr covers Plug-and-play products.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Basis Theory and Weavr actually diverge.
| Attribute | Basis Theory | Weavr |
|---|---|---|
| Starting price | $995/month | On request |
| Pricing model | Per month by token volume | quote |
| Platforms | Web, iOS, Android, Linux | Web, REST API |
Identical on both: free tier (No), 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 Weavr
- Plug-and-play products
- Regulated cover
- Card issuing
- Multi-currency accounts
- Identity and onboarding
- Data insights
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 Weavr
- A merchant locked into a processor by that processor vault that wants to hold its own tokens and route to more than one acquirernot Weavr
- A fintech collecting bank account and identity data that needs it isolated from its application database before an enterprise security reviewnot Weavr
- 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 Weavr
Weavr
- A project management SaaS adding expense cards without hiring a compliance officernot Basis Theory
- A marketplace paying out sellers from accounts held inside its own productnot Basis Theory
- A procurement platform issuing virtual cards against approved purchase ordersnot Basis Theory
- A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot 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.
Weavr
- Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
- Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
- It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
- Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
- European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.
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
Weavr
On request- Weavr embedded finance$undefined/year
- Platform subscription plus per-account and per-card fees
- Interchange share negotiated as part of the commercial terms
- Monthly minimums apply to card programmes
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 Weavr if
- You need plug-and-play products.
- You work on Web, REST API.
- You also want regulated cover.
Questions people ask
- Is Basis Theory or Weavr better?
- Neither clearly leads. Basis Theory starts at $995/month and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Basis Theory or Weavr?
- Basis Theory starts at $995/month and Weavr at On request.
- Does Basis Theory or Weavr run on more platforms?
- Basis Theory runs on Web, iOS, Android, Linux. Weavr runs on Web, REST API.
- 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 Weavr is typically brought in for.
- What can Basis Theory do that Weavr cannot?
- Basis Theory covers Tokenisation API, Hosted elements, Outbound proxy, PCI attestation of compliance. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.
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.
Weavr: Do I need my own financial licence?
No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.
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.
Weavr: How is it different from a banking-as-a-service API?
It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.
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.
Weavr: How does Weavr make money?
Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.
Basis Theory: Is data stored outside the United States?
Not on Starter, which is US only. Other regions require a Scale or Enterprise agreement.
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 Unit
- Basis Theory vs Synctera
- Basis Theory vs Solaris
- Basis Theory vs Thredd
- Basis Theory vs Treasury Prime
- Basis Theory vs Fintech Farm
- Basis Theory vs Highnote
- Basis Theory vs Fintecture
- Basis Theory vs Formance
- Basis Theory vs GraphQL Apollo
- Basis Theory vs GraphQL Playground
- Basis Theory vs Gravitee
- Basis Theory vs Hoppscotch
- Weavr vs Skyflow
- Weavr vs Increase
- Weavr vs Lithic
- Weavr vs Volt
- Weavr vs Swan
- Weavr vs Moov
- Weavr vs Trustly
- Weavr vs Vodeno
- Weavr vs TrueLayer
- Weavr vs Paymentology
- Weavr vs Akoya
- Weavr vs Sila
- Weavr vs Backbase
- Weavr vs Enfuce
- Weavr vs Griffin
- Weavr vs Stoplight
- Weavr vs Unit
- Weavr vs Synctera
- Weavr vs Solaris
- Weavr vs Thredd
- Weavr vs Treasury Prime
- Weavr vs Fintech Farm
- Weavr vs Highnote
- Weavr vs Fintecture
- Weavr vs Formance
- Weavr vs GraphQL Apollo
- Weavr vs GraphQL Playground
- Weavr vs Gravitee
- Weavr vs Hoppscotch
