Softwr

APIs · head to head

Marqeta vs Weavr

Marqeta logo

Marqeta

APIs

Card issuing and transaction processing APIs with just-in-time funding

From
On request
Rated
-
Full reviewWebsite
Weavr logo

Weavr

APIs

Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Marqeta you still need a sponsor bank and a BIN, so the timeline and compliance burden of launching are set by a bank you must separately court and satisfy.; 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: Marqeta covers Just-in-time funding, 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 Marqeta and Weavr actually diverge.

Attributes where Marqeta and Weavr differ
AttributeMarqetaWeavr

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web, REST API), 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 Marqeta

  • Just-in-time funding
  • Virtual and physical issuing
  • Spend controls
  • Programme management tools
  • Multi-region issuing
  • Webhooks and ledger data

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.

Marqeta

  • A delivery marketplace funding courier cards only at the moment a courier pays for the ordernot Weavr
  • An expense platform issuing a virtual card per subscription with merchant locksnot Weavr
  • A lender issuing a card that draws on an approved credit line rather than a stored balancenot Weavr
  • A fintech wanting the same issuing stack across US and European programmesnot Weavr

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Marqeta
  • A marketplace paying out sellers from accounts held inside its own productnot Marqeta
  • A procurement platform issuing virtual cards against approved purchase ordersnot Marqeta
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot Marqeta

Where each one falls short

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

Marqeta

  • You still need a sponsor bank and a BIN, so the timeline and compliance burden of launching are set by a bank you must separately court and satisfy.
  • Pricing carries minimum monthly platform commitments, so a programme with modest card volume pays for capacity it never uses.
  • Programme revenue depends heavily on interchange, which means regulated debit interchange caps and European interchange caps materially change the business case by market.
  • Disputes, chargebacks and fraud losses sit with the programme, and teams that assumed the processor absorbed them discover a real operations headcount requirement.
  • Just-in-time funding makes your own authorisation endpoint a hard availability dependency; if it is slow or down, cards decline at the point of sale.

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

Marqeta

On request
  • Marqeta card issuing$undefined/year
    • Minimum monthly platform fee plus per-transaction and per-active-card charges
    • Interchange share negotiated between programme, processor and sponsor bank
    • Sponsor bank required, with its own fees and approval process

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

  • You need just-in-time funding.
  • You work on Web, REST API.
  • You also want virtual and physical issuing.
Marqeta review

Choose Weavr if

  • You need plug-and-play products.
  • You work on Web, REST API.
  • You also want regulated cover.
Weavr review

Questions people ask

Is Marqeta or Weavr better?
Neither clearly leads. Marqeta starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Marqeta or Weavr?
Marqeta starts at On request and Weavr at On request.
Does Marqeta or Weavr run on more platforms?
Both run on Web, REST API, so platform support will not decide this one for you.
What is Marqeta best used for?
Marqeta is most often used for a delivery marketplace funding courier cards only at the moment a courier pays for the order, an expense platform issuing a virtual card per subscription with merchant locks, a lender issuing a card that draws on an approved credit line rather than a stored balance, a fintech wanting the same issuing stack across us and european programmes. Of those, a delivery marketplace funding courier cards only at the moment a courier pays for the order and an expense platform issuing a virtual card per subscription with merchant locks are not what Weavr is typically brought in for.
What can Marqeta do that Weavr cannot?
Marqeta covers Just-in-time funding, Virtual and physical issuing, Spend controls, Programme management tools. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

Answered from the vendors’ own pages

Marqeta: Do I need a sponsor bank?

Yes. Marqeta is an issuer processor, not a bank. Card programmes run on a sponsor bank BIN, and that bank approves and supervises your programme.

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.

Marqeta: How does the pricing really work?

A minimum monthly platform fee plus per-transaction and per-active-card charges, offset by a negotiated share of interchange. The interchange split is the substance of the deal.

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.

Marqeta: What is just-in-time funding?

Marqeta calls your endpoint at authorisation so you decide and fund each transaction, rather than pre-loading balances onto cards.

Weavr: How does Weavr make money?

Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.

Share

Related pages

More on Marqeta

More on Weavr

Keep looking

Other head to heads