Softwr

APIs · head to head

Marqeta vs Swan

Marqeta logo

Marqeta

APIs

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

From
On request
Rated
-
Full reviewWebsite
Swan logo

Swan

APIs

European banking-as-a-service platform for embedding accounts, cards and payments into other products

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.; Swan its regulatory base and strongest local account coverage are French and European, so companies needing US, UK-post-Brexit-specific, or broader global banking-as-a-service need an additional provider.
  • They diverge on capability: Marqeta covers Just-in-time funding, Swan covers Embedded business accounts.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Marqeta and Swan actually diverge.

Attributes where Marqeta and Swan differ
AttributeMarqetaSwan
PlatformsWeb, REST APIWeb, API

Identical on both: starting price (On request), pricing model (quote), 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 Marqeta

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

Only in Swan

  • Embedded business accounts
  • Card issuing
  • SEPA payments
  • Local account localisation
  • ACPR regulation
  • Usage-based pricing

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 Swan
  • An expense platform issuing a virtual card per subscription with merchant locksnot Swan
  • A lender issuing a card that draws on an approved credit line rather than a stored balancenot Swan
  • A fintech wanting the same issuing stack across US and European programmesnot Swan

Swan

  • A vertical SaaS platform wanting to embed business bank accounts under its own brandnot Marqeta
  • A marketplace wanting to issue cards to sellers or partners without becoming a licensed banknot Marqeta
  • A company wanting SEPA payment initiation embedded directly into its own productnot Marqeta
  • A European fintech wanting to avoid a six-figure setup fee and long lock-in typical of legacy banking-as-a-service dealsnot 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.

Swan

  • Its regulatory base and strongest local account coverage are French and European, so companies needing US, UK-post-Brexit-specific, or broader global banking-as-a-service need an additional provider.
  • Pricing is described only philosophically (usage-based, no big setup fee) rather than published as an actual rate card, so a company still needs a sales conversation to get real numbers.
  • Embedding banking features into a product is a substantial compliance and design undertaking regardless of the vendor, and Swan handling the licence does not remove a platform's own KYC, AML and customer support obligations for the accounts it offers.
  • As a comparatively young, single-country-licensed e-money institution, its balance sheet and regulatory standing carry more concentration risk than a banking-as-a-service offering backed by an established, multi-jurisdiction bank.
  • Local account depth is explicitly limited to France, Germany and Spain, so a platform needing native local accounts in other European countries may find coverage thinner than expected.

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

Swan

On request
  • Swan$undefined/month
    • Usage-based pricing, no published rate card
    • No long-term contract or large setup fee required
    • Custom quote based on current, not forecast, usage

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

  • You need embedded business accounts.
  • You work on Web, API.
  • You also want card issuing.
Swan review

Questions people ask

Is Marqeta or Swan better?
Neither clearly leads. Marqeta starts at On request and Swan at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Marqeta or Swan?
Marqeta starts at On request and Swan at On request.
Does Marqeta or Swan run on more platforms?
Marqeta runs on Web, REST API. Swan runs on Web, API.
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 Swan is typically brought in for.
What can Marqeta do that Swan cannot?
Marqeta covers Just-in-time funding, Virtual and physical issuing, Spend controls, Programme management tools. Swan covers Embedded business accounts, Card issuing, SEPA payments, Local account localisation.

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.

Swan: Which countries does Swan offer local accounts in?

France, Germany and Spain specifically, alongside broader SEPA payment coverage.

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.

Swan: Is pricing published?

No, Swan describes a usage-based, no-large-setup-fee philosophy but requires a quote for actual numbers.

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.

Swan: Who regulates Swan?

France's ACPR (Autorite de Controle Prudentiel et de Resolution), as a licensed e-money institution.

Share

Related pages

More on Marqeta

More on Swan

Keep looking

Other head to heads