Softwr

APIs · head to head

Codat vs Increase

Codat logo

Codat

APIs

One API for small business accounting, banking and commerce data

From
On request
Rated
-
Full reviewWebsite
Increase logo

Increase

APIs

Direct banking API for ACH, wires, real-time payments, accounts and cards

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Codat the accounting platforms are metering developer access themselves, with Xero introducing tiered connection based developer pricing from 2 March 2026, so a cost you do not control has been inserted between you and the data and it scales with the number of customers you connect.; Increase the published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.
  • They diverge on capability: Codat covers Normalised accounting API, Increase covers ACH origination and receipt.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Codat and Increase actually diverge.

Attributes where Codat and Increase differ
AttributeCodatIncrease

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

  • Normalised accounting API
  • Banking and commerce data
  • Lending products
  • Write-back
  • Business verification
  • Supplier onboarding
  • Connection management
  • Data quality handling

Only in Increase

  • ACH origination and receipt
  • Domestic wires
  • Real-time payments
  • Bank accounts
  • Cards
  • Cheques
  • Sandbox and simulations
  • Audit and reconciliation data

What people use each for

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

Codat

  • A business lender that wants live ledger data for underwriting rather than a borrower emailing exported PDF accountsnot Increase
  • A commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterlynot Increase
  • A payment company verifying a merchant trading history before extending working capitalnot Increase
  • A B2B platform writing bills and payments back into a customer accounting system so reconciliation happens automaticallynot Increase

Increase

  • A payroll or treasury product that needs to originate same-day ACH and wires under its own control rather than through a payment processornot Codat
  • A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Codat
  • A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Codat
  • An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Codat

Where each one falls short

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

Codat

  • The accounting platforms are metering developer access themselves, with Xero introducing tiered connection based developer pricing from 2 March 2026, so a cost you do not control has been inserted between you and the data and it scales with the number of customers you connect.
  • Pricing is opaque and enterprise shaped for a product developers expect to evaluate technically first, so build decisions get made before anyone knows the unit economics.
  • Normalisation hides but does not remove the underlying differences between accounting systems, and edge cases in multi-currency, journals and tax handling surface as data quality problems that your team must reason about in each source system anyway.
  • Data quality depends on the small business keeping its books properly, so a lender using ledger data for underwriting inherits the bookkeeping standard of its worst borrower and needs its own validation layer regardless.
  • Connection breakage from expired tokens and platform API changes is an ongoing operational load, and a borrower whose connection lapses stops being monitored silently, which is the failure mode that matters most in a lending portfolio.

Increase

  • The published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.
  • Free allowances are deliberately small at ten account numbers and five physical cards, so any programme issuing accounts or cards at volume moves to quoted pricing almost immediately.
  • Banking is provided through partner banks, so programme approval, compliance obligations and the ability to launch at all depend on a bank relationship you do not control, and post-Synapse bank risk appetite has tightened considerably.
  • The API deliberately exposes payment rail mechanics rather than smoothing them, which is correct engineering but means a team without payments expertise will build reconciliation and return handling wrongly and only discover it when funds go astray.
  • Coverage is United States only, so a company with international payout needs runs a second provider and reconciles two ledgers, and the single API argument disappears at the first cross border customer.

Pricing, plan by plan

Codat

On request
  • Codat Platform$undefined/year
    • Priced by connected companies, data types and products
    • Lending and verification products priced above core data access
    • Annual enterprise agreements

Increase

On request
  • Increase Platform$undefined/month
    • Monthly fee quoted by use case and not published
    • Next-day ACH origination listed at 0.50 US dollars per transaction
    • Same-day ACH origination listed at 2.00 per transaction

Which should you pick?

Choose Codat if

  • You need normalised accounting api.
  • You work on API, Web.
  • You also want banking and commerce data.
Codat review

Choose Increase if

  • You need ach origination and receipt.
  • You work on API, Web.
  • You also want domestic wires.
Increase review

Questions people ask

Is Codat or Increase better?
Neither clearly leads. Codat starts at On request and Increase at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Codat or Increase?
Codat starts at On request and Increase at On request.
Does Codat or Increase run on more platforms?
Both run on API, Web, so platform support will not decide this one for you.
What is Codat best used for?
Codat is most often used for a business lender that wants live ledger data for underwriting rather than a borrower emailing exported pdf accounts, a commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterly, a payment company verifying a merchant trading history before extending working capital, a b2b platform writing bills and payments back into a customer accounting system so reconciliation happens automatically. Of those, a business lender that wants live ledger data for underwriting rather than a borrower emailing exported pdf accounts and a commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterly are not what Increase is typically brought in for.
What can Codat do that Increase cannot?
Codat covers Normalised accounting API, Banking and commerce data, Lending products, Write-back. Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts.

Answered from the vendors’ own pages

Codat: What is changing with Xero in 2026?

Xero is introducing a tiered, usage based developer pricing model effective 2 March 2026, with tiers based on the number of customer connections an app holds. That is a new cost in the chain for anyone reading Xero data at scale, whether directly or through Codat.

Increase: Does Increase publish its pricing?

Partly. Per transaction fees for ACH, wires, RTP, FedNow and cards are listed publicly. The monthly platform fee is not, and it is described only as varying by use case.

Codat: Can Codat write data back?

Yes. It supports pushing bills, payments and journal entries into accounting systems, not only reading from them.

Increase: Who holds the deposits?

Partner banks, not Increase itself. That relationship determines your programme approval, your compliance obligations and your risk if the bank changes appetite.

Codat: Is pricing published?

No. It is quoted by connected companies, data types and products, and users consistently describe it as opaque.

Increase: Is it international?

No. Increase covers United States rails only, so cross border payouts require a second provider.

Codat: Does it replace bank data aggregation?

Not entirely. It covers banking alongside accounting and commerce, but lenders commonly run it beside a bank aggregator for transaction level cash flow.

Increase: How is it different from a middleware BaaS platform?

It exposes the rails rather than abstracting them, showing real return codes and settlement timing. That suits teams who understand payments and punishes teams who do not.

Share

Related pages

More on Codat

More on Increase

Keep looking

Other head to heads