Softwr

APIs · head to head

Column vs TrueLayer

Column logo

Column

APIs

A nationally chartered US bank that ships its own API, with no middleware in between

From
On request
Rated
-
TrueLayer logo

TrueLayer

APIs

Open banking payments and data across the UK and Europe, with the largest share of UK variable recurring payments

From
On request
Rated
-

The short version

  • Each has a real cost: Column column publishes no pricing whatsoever, so there is no way to model cost before a sales process, and terms are negotiated per programme which favours larger, more sophisticated buyers.; TrueLayer variable recurring payments, the strongest reason to choose TrueLayer, is a UK construct, and European businesses expecting the same capability in their market will not get it on the same timetable.
  • They diverge on capability: Column covers National bank charter, TrueLayer covers Pay by bank.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Column and TrueLayer actually diverge.

Attributes where Column and TrueLayer differ
AttributeColumnTrueLayer
PlatformsWeb, APIWeb, iOS, Android

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 Column

  • National bank charter
  • Direct Federal Reserve access
  • Ledger and accounts
  • International wires
  • Real-time payments
  • Lending
  • Cheque handling
  • Correspondent banking

Only in TrueLayer

  • Pay by bank
  • Variable recurring payments
  • Payouts and refunds
  • Account information
  • Account name verification
  • Signup and KYC support
  • Multi-country coverage
  • Hosted payment page

What people use each for

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

Column

  • A fintech that has been burned by a middleware provider failing and wants its deposits held by the same entity that provides the APInot TrueLayer
  • A payments company needing direct Fedwire and Swift access rather than routing through a correspondent it cannot seenot TrueLayer
  • A lender that wants origination, funding and deposit accounts from one chartered institution instead of three counterpartiesnot TrueLayer
  • A payroll or treasury platform where same-day settlement certainty matters more than fast onboardingnot TrueLayer

TrueLayer

  • A UK subscription or top-up business that wants card-like recurring collection over bank rails using variable recurring paymentsnot Column
  • A trading or crypto platform funding accounts instantly by bank transfer where card deposits carry chargeback risknot Column
  • A marketplace paying sellers out to verified bank accounts with name checking to reduce misdirected paymentsnot Column
  • A lender verifying income and affordability from bank transaction data rather than uploaded statementsnot Column

Where each one falls short

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

Column

  • Column publishes no pricing whatsoever, so there is no way to model cost before a sales process, and terms are negotiated per programme which favours larger, more sophisticated buyers.
  • Onboarding is bank diligence rather than vendor sign-up, and programmes routinely spend several months on compliance review, flow of funds documentation and volume forecasting before the first live transaction.
  • Column selects its customers and declines many, so the charter advantage is only available to programmes it considers acceptable risk, which excludes most early-stage teams.
  • It is United States only, so any programme with international account or local payment needs must add a second banking relationship and reconcile across both.
  • Being the bank means Column also carries the bank's regulatory constraints, so product changes that affect risk, such as new customer segments or higher-risk flows, need approval rather than a configuration change.

TrueLayer

  • Variable recurring payments, the strongest reason to choose TrueLayer, is a UK construct, and European businesses expecting the same capability in their market will not get it on the same timetable.
  • Payment conversion varies substantially by bank, and a bank with a slow or broken authentication journey drags results down regardless of vendor, so aggregate coverage numbers say little about your actual mix.
  • Pay by bank has no chargeback mechanism, which merchants like until a customer disputes a purchase and finds no scheme protection, making it a poor fit for categories where buyers expect card style recourse.
  • Pricing is unpublished and varies by market and product, so multi-country merchants cannot model cost without a full sales engagement and often find rates differ significantly between countries.
  • Open banking authentication requires the customer to leave the checkout and authorise in their banking app, and that redirect remains the largest source of drop-off compared with a stored card.

Pricing, plan by plan

Column

On request
  • Column Bank Platform$undefined/year
    • Deposit accounts and ledger
    • ACH, wire, RTP and cheque rails
    • International wires over Swift

TrueLayer

On request
  • TrueLayer Payments and Data$undefined/year
    • Per-payment fees quoted by volume, market and product
    • Separate commercial terms for payment initiation, VRP and account information
    • Platform and minimum commitment terms negotiated per contract

Which should you pick?

Choose Column if

  • You need national bank charter.
  • You work on Web, API.
  • You also want direct federal reserve access.

Choose TrueLayer if

  • You need pay by bank.
  • You work on Web, iOS, Android.
  • You also want variable recurring payments.

Questions people ask

Is Column or TrueLayer better?
Neither clearly leads. Column starts at On request and TrueLayer at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Column or TrueLayer?
Column starts at On request and TrueLayer at On request.
Does Column or TrueLayer run on more platforms?
Column runs on Web, API. TrueLayer runs on Web, iOS, Android.
What is Column best used for?
Column is most often used for a fintech that has been burned by a middleware provider failing and wants its deposits held by the same entity that provides the api, a payments company needing direct fedwire and swift access rather than routing through a correspondent it cannot see, a lender that wants origination, funding and deposit accounts from one chartered institution instead of three counterparties, a payroll or treasury platform where same-day settlement certainty matters more than fast onboarding. Of those, a fintech that has been burned by a middleware provider failing and wants its deposits held by the same entity that provides the api and a payments company needing direct fedwire and swift access rather than routing through a correspondent it cannot see are not what TrueLayer is typically brought in for.
What can Column do that TrueLayer cannot?
Column covers National bank charter, Direct Federal Reserve access, Ledger and accounts, International wires. TrueLayer covers Pay by bank, Variable recurring payments, Payouts and refunds, Account information.

Answered from the vendors’ own pages

Column: Is Column actually a bank?

Yes. It is a nationally chartered, FDIC-insured bank, which is why there is no sponsor bank behind it.

TrueLayer: Is VRP available outside the UK?

No. Variable recurring payments are a UK capability. EU adoption is on a slower path, with UK commercial VRP expanding into ecommerce during 2026.

Column: How is that different from Synctera or Unit?

Those are technology providers that connect you to a separate sponsor bank. With Column the API provider and the depository institution are the same company.

TrueLayer: What does TrueLayer cost?

Not published. Per-payment fees are quoted by volume, market and product, usually with a platform component and a minimum commitment.

Column: What does Column cost?

Nothing is published. Pricing is negotiated per programme.

TrueLayer: Are there chargebacks on pay by bank?

No. Bank transfers have no card scheme chargeback mechanism, which removes that cost but also removes buyer recourse, so it suits some categories and not others.

Column: How long does onboarding take?

Expect months. This is bank-grade diligence on your compliance programme, not a vendor sign-up.

TrueLayer: Which countries are covered?

The UK plus a substantial set of European markets under PSD2, though bank-level coverage and conversion vary by country and should be checked for your specific mix.

Share

Related pages

Other head to heads