APIs · head to head
Marqeta vs Unit
Marqeta
APIs
Card issuing and transaction processing APIs with just-in-time funding
- From
- On request
- Rated
- -
Unit
APIs
Banking as a service platform for embedding deposit accounts, cards and payments, with a sponsor bank behind it
- From
- On request
- Rated
- -
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.; Unit your product depends on a sponsor bank you do not contract with directly, and 2024 showed what that means: Thread Bank received an FDIC enforcement action naming its banking as a service programmes and Blue Ridge Bank went under an OCC consent order and offboarded fintech partners.
- They diverge on capability: Marqeta covers Just-in-time funding, Unit covers Deposit accounts.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Marqeta and Unit actually diverge.
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 Unit
- Deposit accounts
- Card issuing
- Payments
- White label components
- Compliance operations
- Lending
- Programme reporting
- Sandbox
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 Unit
- An expense platform issuing a virtual card per subscription with merchant locksnot Unit
- A lender issuing a card that draws on an approved credit line rather than a stored balancenot Unit
- A fintech wanting the same issuing stack across US and European programmesnot Unit
Unit
- A vertical SaaS platform for contractors that wants to hold customer funds and issue expense cards without pursuing a charternot Marqeta
- A payroll or benefits platform embedding accounts so employees can be paid ahead of schedulenot Marqeta
- A marketplace that wants seller balances to sit in real accounts under its own brand rather than as ledger entries at a processornot Marqeta
- A company that needs interchange revenue from a card programme to make the unit economics of its core product worknot 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.
Unit
- Your product depends on a sponsor bank you do not contract with directly, and 2024 showed what that means: Thread Bank received an FDIC enforcement action naming its banking as a service programmes and Blue Ridge Bank went under an OCC consent order and offboarded fintech partners.
- Programme approval by the bank is a separate gate from signing with Unit, and it can add months and impose product restrictions that were not visible during the commercial conversation.
- Compliance obligations are shared but the operational load lands on you, and platforms consistently underestimate the staffing needed for disputes, escalations and the bank ongoing oversight requests.
- Pricing is unpublished and blends platform fees, per-account and per-transaction charges and interchange sharing, which makes it hard to model unit economics before you have volume and easy to be surprised by the minimum.
- Migrating a live deposit programme to a different provider or bank is extremely disruptive because it involves moving customer accounts and card credentials, so switching costs are far higher than for ordinary software.
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
Unit
On request- Unit Banking as a Service$undefined/year
- Platform fee plus per-account and per-transaction charges, quoted
- Interchange sharing arrangements negotiated per programme
- Minimum commitment typical
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.
Choose Unit if
- You need deposit accounts.
- You work on Web, iOS, Android.
- You also want card issuing.
Questions people ask
- Is Marqeta or Unit better?
- Neither clearly leads. Marqeta starts at On request and Unit at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Marqeta or Unit?
- Marqeta starts at On request and Unit at On request.
- Does Marqeta or Unit run on more platforms?
- Marqeta runs on Web, REST API. Unit runs on Web, iOS, Android.
- 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 Unit is typically brought in for.
- What can Marqeta do that Unit cannot?
- Marqeta covers Just-in-time funding, Virtual and physical issuing, Spend controls, Programme management tools. Unit covers Deposit accounts, Card issuing, Payments, White label components.
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.
Unit: Who actually holds the money?
A chartered partner bank, not Unit. Deposits sit at the sponsor bank and FDIC insurance flows from that bank, so its condition is your condition.
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.
Unit: What happened with Unit sponsor banks in 2024?
Thread Bank received an FDIC enforcement action that explicitly named its banking as a service and lending as a service programmes, and Blue Ridge Bank was under an OCC consent order from January 2024 and offboarded fintech partners. Blue Ridge exited the order in late 2025.
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.
Unit: What does Unit cost?
Not published. Expect a platform fee, per-account and per-transaction charges, an interchange share and a minimum commitment.
Unit: Do we need our own compliance team?
Yes. Unit supplies tooling and the bank sets the rules, but disputes, escalations and evidence for bank oversight require named people on your side.
Related pages
Other head to heads
- Marqeta vs i2c
- Marqeta vs Enfuce
- Marqeta vs Paymentology
- Marqeta vs Highnote
- Marqeta vs Tribe Payments
- Marqeta vs Lithic
- Marqeta vs Thredd
- Marqeta vs Episode Six
- Marqeta vs Yapily
- Marqeta vs Synctera
- Marqeta vs Treasury Prime
- Marqeta vs REST Client VSCode
- Marqeta vs Rutter
- Marqeta vs Sensedia
- Marqeta vs Sila
- Marqeta vs Spring Cloud Gateway
- Marqeta vs Swagger
- Marqeta vs Solaris
- Marqeta vs Increase
- Marqeta vs Column
- Marqeta vs Toqio
- Marqeta vs Weavr
- Marqeta vs Swan
- Marqeta vs Vodeno
- Marqeta vs Griffin
- Marqeta vs Akana
- Marqeta vs Akoya
- Marqeta vs Apidog
- Marqeta vs Astra
- Marqeta vs Asyncapi
- Marqeta vs AWS API Gateway
- Unit vs i2c
- Unit vs Enfuce
- Unit vs Paymentology
- Unit vs Highnote
- Unit vs Tribe Payments
- Unit vs Lithic
- Unit vs Thredd
- Unit vs Episode Six
- Unit vs Yapily
- Unit vs Synctera
- Unit vs Treasury Prime
- Unit vs REST Client VSCode
- Unit vs Rutter
- Unit vs Sensedia
- Unit vs Sila
- Unit vs Spring Cloud Gateway
- Unit vs Swagger
- Unit vs Solaris
- Unit vs Increase
- Unit vs Column
- Unit vs Toqio
- Unit vs Weavr
- Unit vs Swan
- Unit vs Vodeno
- Unit vs Griffin
- Unit vs Akana
- Unit vs Akoya
- Unit vs Apidog
- Unit vs Astra
- Unit vs Asyncapi
- Unit vs AWS API Gateway