Softwr

APIs · head to head

Highnote vs Swan

Highnote logo

Highnote

APIs

Card issuing, acquiring and ledger on one platform for embedded payments

From
On request
Rated
-
Swan logo

Swan

APIs

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

From
On request
Rated
-

The short version

  • Each has a real cost: Highnote card issuing requires a sponsor bank, and that bank sets programme approval, compliance obligations and often minimum volumes, so a small programme can be rejected regardless of technical fit.; 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: Highnote covers Merchant acquiring, Swan covers Embedded business accounts.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Highnote and Swan actually diverge.

Attributes where Highnote and Swan differ
AttributeHighnoteSwan

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

  • Merchant acquiring
  • Unified ledger
  • Spend controls
  • GraphQL API
  • Programme management
  • Dispute handling
  • Real time authorisation webhooks

Only in Swan

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

Both cover

  • Card issuing

What people use each for

The jobs each tool is most often brought in to do.

Highnote

  • A marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledgernot Swan
  • A vertical software company embedding card acceptance and card issuing for the same customer basenot Swan
  • A fintech launching a commercial charge card programme with custom authorisation logicnot Swan
  • A platform replacing separate issuing and acquiring vendors to remove cross system reconciliationnot Swan

Swan

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

Where each one falls short

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

Highnote

  • Card issuing requires a sponsor bank, and that bank sets programme approval, compliance obligations and often minimum volumes, so a small programme can be rejected regardless of technical fit.
  • Pricing is entirely quoted, including platform fees, per active card charges and monthly minimums that do not appear on the website, so the true cost per card is only visible late in a sales process.
  • Interchange sharing is the real revenue model for most customers, and the split is negotiated, capped for regulated debit under the Durbin amendment and sensitive to your spend mix, so revenue projections built on headline interchange rates overstate income.
  • Running issuing and acquiring with one provider concentrates risk: an outage or a compliance action affects both money in and money out at the same time.
  • Highnote is a younger company than the established issuer processors, so long term programme continuity, network certifications in new geographies and international coverage are thinner than the incumbent alternatives.

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

Highnote

On request
  • Highnote platform$undefined/year
    • Quoted per programme with no public rate card
    • Requires a sponsor bank relationship for card issuing
    • Interchange sharing terms negotiated per programme

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

  • You need merchant acquiring.
  • You work on Web, API.
  • You also want unified ledger.

Choose Swan if

  • You need embedded business accounts.
  • You work on Web, API.
  • You also want sepa payments.

Questions people ask

Is Highnote or Swan better?
Neither clearly leads. Highnote 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, Highnote or Swan?
Highnote starts at On request and Swan at On request.
Does Highnote or Swan run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Highnote best used for?
Highnote is most often used for a marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledger, a vertical software company embedding card acceptance and card issuing for the same customer base, a fintech launching a commercial charge card programme with custom authorisation logic, a platform replacing separate issuing and acquiring vendors to remove cross system reconciliation. Of those, a marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledger and a vertical software company embedding card acceptance and card issuing for the same customer base are not what Swan is typically brought in for.
What can Highnote do that Swan cannot?
Highnote covers Merchant acquiring, Unified ledger, Spend controls, GraphQL API. Swan covers Embedded business accounts, SEPA payments, Local account localisation, ACPR regulation. Both handle Card issuing.

Answered from the vendors’ own pages

Highnote: Do I need a sponsor bank?

Yes for card issuing in the United States. Highnote is a processor and programme platform, not a bank, and the sponsor bank sets approval and compliance terms.

Swan: Which countries does Swan offer local accounts in?

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

Highnote: How do customers make money on a card programme?

Mostly interchange sharing. Negotiate the split explicitly and model it against your actual spend mix, since regulated debit interchange is capped.

Swan: Is pricing published?

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

Highnote: Can Highnote handle both accepting and issuing payments?

Yes since its 2025 acquiring launch, on the same ledger, which is its main structural differentiator.

Swan: Who regulates Swan?

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

Share

Related pages

Other head to heads