EP957: Reprogramming Transaction Banking with Programmable Finance

We're not just automating payments.

We're teaching money to listen, act, and adapt.

It's quite a bold claim, isn't it?

Because usually money just sort of sits there

until you push it somewhere.

The idea that it could listen feels a bit, I don't know,

almost like sci-fi territory.

Completely, but that's exactly the hook for today's deep dive.

We are tearing into this really fascinating interview

from the IBS Fintech Journal.

It's with Vybhoff Tumbay.

To CEO of Transblink.

Right, exactly.

And the headline topic here is programmable finance.

Which is a term that I think gets misused a lot these days.

Usually when people say programmable money,

you know, they're talking about crypto.

Yes, smart contracts, Ethereum.

Exactly, all that stuff.

But what cut my eye here is that Kenbe isn't talking about crypto at all.

He's talking about the actual fiat money

that's running through the traditional banking system right now.

And that's the distinction that really matters for us today.

We're talking about transaction banking.

And honestly, this is an area that, uh,

well, it usually puts people to sleep.

It's not the sexiest topic.

No, it's not.

Because you look at the consumer side things,

like UPI, if you're in India or Venmo in the US.

And it's a party.

You scan a QR code.

The money zips across instantly.

Everyone is happy.

It's seamless.

Right.

But the B2B side, the corporate side.

It's still living in the 90s.

It really is the facts machine in the corner of the office.

That is a painfully accurate description.

While retail payments became instant and totally invisible,

corporate transaction banking stayed, um, incredibly clunky.

Batch process.

Yeah.

Batch process.

Highly manual full of friction.

And Transbricks' mission, effectively,

is to drag that entire infrastructure into the modern era.

So they basically want to do for corporate banking

what UPI did for buying a cup of coffee.

That's a great way to put it, yes.

So let's dig right into this core concept.

Teaching money to listen.

What does that actually mean in a practical day-to-day business sense?

Because right now, you know, if I schedule a payment for next Tuesday,

isn't that programming it?

Well, not really.

That's just a timer.

You're just telling the bank do exit time why.

Programmable finance, at least how Tammy defines it in the piece,

is about logic.

Okay, logic.

Yeah, it's about conditional execution.

It's taking if-then statements and attaching them directly to the capital itself.

So instead of just pay on Tuesday,

it's more like, pay on Tuesday if the goods have been delivered.

And the quality check is verified.

Spot on.

The money basically becomes aware of its real-world context.

That's wild.

It is.

Tammy gives this really great example of a construction company.

In the old world,

managing cash flow for a massive project is a total nightmare.

Oh, I can imagine.

You've got vendors, subcontractors, all these milestones.

Right, and you're cutting checks,

essentially just hoping the work actually got done properly.

And usually the money moves before the verification happens

or the verification happens.

And then the poor vendors sitting there waiting 60 days for the cash.

Exactly.

But with programmable rails,

you encode the condition into the payment.

The capital is there.

It's sitting in the account,

but it's locked.

It's listening for a digital signal.

Like a thumbs up from a site inspector's app or something?

Yes, exactly that.

And the moment that data hits the system,

the money just releases itself.

No accounts payable clerk needs to sit there

and review a massive spreadsheet.

Wow, so that's the acting part of the quote,

the money acts on its own.

And it scales up to things like sweeping,

which I actually think is one of the most underrated tools

in treasury management.

Okay, stick a pin in that,

because sweeping sounds like janitorial work.

Break that down for us.

I mean, in a way it is janitorial.

It's cleaning up lazy capital.

Yeah.

So imagine you're a business with 10 different accounts.

At the end of the day, you might have $50,000

sitting idle in one account,

$20,000 in another.

Just doing nothing.

Doing absolutely nothing.

It's actually losing value

against inflation just sitting there.

So you want to move it to an interest-bearing account?

Right.

But doing that manually every single day

at 4.55 pm is basically impossible.

You'd need a whole team just for that.

Exactly.

So programmable finance turns that into a script.

It's like having a smart thermostat,

but for your cash.

The system just senses,

oh, this operational account

has excess liquidity today.

And it automatically sweeps it into a master account

to earn interest overnight.

And then just pushes it back

before the market's open the next morning.

Yes.

It optimizes the cash

without a human ever having to make a decision

or click a button.

So it's a massive shift.

I think Tammy talks about moving from bending processes

to legacy systems

to making the rails adapt to business logic.

That framing is crucial.

Because traditionally, as a business,

you essentially work for the bank.

You have to submit your file by their cutoff time.

You have to format your CSV exactly the way they want it.

Right. If your business runs 24-7,

but the bank closes at 5-DM, well, too bad.

Exactly.

Friends think it's completely flipping that dynamic.

They're saying the banking infrastructure

should be flexible enough

to wrap around your specific business model.

So if you're a logistics company, say,

and your trucks arrive at 3 AM,

and you need to settle payments instantly

right then to keep the drivers moving.

The banking layers should just handle that.

No questions asked.

This really brings us to the democratization aspect

of the interview.

Tammy compares their ambition to UPI, like we mentioned.

And UPI didn't just make retail payments faster,

it made them accessible to literally everyone.

From a massive mall retailer down to a street vendor.

Right.

So what does democratization mean in this B2B context?

It means taking these incredibly high-end,

sophisticated treasury tools,

which used to be the exclusive playground

of Fortune 500 companies who had armies of engineers

and making them available to everyone.

MSMEs, startups, gig economy platforms.

Exactly.

So a small Fintech lender could essentially have

the same smart money capabilities

as a massive global bank.

That is the goal.

But to actually pull that off,

you have to completely fix the underlying plumbing.

And this leads us to what I think is probably

the most transformative part of the entire interview,

even if it sounds incredibly boring on the surface.

Oh, I know where you're going with this.

You're talking about reconciliation.

The dreaded R word.

Yes.

Listen, I have friends who work in corporate finance,

and I know for a fact that month-end close

is basically a recurring trauma for them.

It's a monthly fire drill.

It means late nights,

ordering pizza to the office,

and just staring at spreadsheets

until your eyes bleed,

trying to figure out why the numbers don't match.

And it happens every single month.

But if you stop and ask yourself why it happens,

it's because money movement and data movement

are usually two entirely separate streams.

Right.

You send the cash over here,

and separately you email an invoice over there.

Exactly.

So at the end of the month,

humans have to step in and try to stitch

those two realities back together.

It's like trying to match socks

after the laundry is done,

but you're doing it with millions of dollars.

That is a perfect analogy.

And Tanby talks about this concept

of the death of end of day.

He argues that in an instant world,

the whole concept of closing the books

at the end of a day is already obsolete.

Because if the payment is instant,

the reconciliation should be instant too.

Precisely.

So to solve your mismatched sock problem,

transbrank uses what they call a recon first architecture.

Recon first.

How does that work in practice?

They utilize microservices.

Think of them as little independent software agents

that ingest events in real time.

Every single time a transaction hits the rail,

it's immediately mapped to an internal identifier.

So the payment itself is the record?

Effectively yes.

They are reconciling as they transact.

The ledgers always live.

There is no end of day

because the day never really ends in this system.

It's just a continuous, perfectly matched flow.

The implication of that for a business

is just huge.

If you're a CFO listening to this,

you get to stop being a historian.

Right, you're no longer just reporting

on what happened three weeks ago.

You actually start acting like a pilot

navigating the business in real time.

And for the business owner,

the key word here is scalability.

This is a really major point in the source material.

This technology allows teams

to scale their transaction volume

without scaling their head count.

Because usually, if your sales triple,

you have to hire more back office staff

just to process the paperwork

and fix all the new errors.

Exactly.

Growth literally breaks the back office.

But if reconciliation becomes this invisible,

dependable utility,

literally just code running in the background,

you can go from a thousand transactions

to a hundred thousand transactions.

And your back office team stays the exact same size.

That's the pure definition of leverage.

It automates all the drudgery,

which paradoxically, I guess,

allows the humans to focus

on the actual relationships.

Yes, the high value work.

Speaking of relationships,

let's pivot and talk about trust.

Because another really major pillar

they discussed in the journal

was Espero as a service.

Oh, this is a favorite topic of mine.

Because it perfectly illustrates

how technology fundamentally changes unit economics.

Now, most of you listening,

probably know what an escrow is conceptually.

You're buying a house,

you put the money in a neutral third party

account, so neither the buyer

nor the seller gets scammed.

Right. It's a trust mechanism.

Yeah.

But historically,

that has been a very heavy,

very expensive process.

Oh, extremely heavy paperwork,

lawyers, banking fees,

massive time delays.

Exactly. So you only ever used it

for high value transactions.

Real estate, corporate mergers,

massive procurement deals.

You would never go through the hassle

of opening a formal bank escrow

for, say, a $500 freelance design job.

The transaction costs would just be way too high.

Right.

But the need for trusts

still exists at that $500 level.

Oh, the trust gap is everywhere.

If you run a digital marketplace

that connects freelancers to clients,

you have this constant standoff.

The freelancer won't deliver the work

until they know the money is actually there.

And the client refuses to pay

until the work is delivered and checked.

Exactly. So what trans bank is doing

is turning escrow into an API call.

Just a line of code.

Yes, they've digitized the entire process.

escrow is a service.

It means a platform can spin up a dedicated

virtual escrow account for one specific transaction

in milliseconds using code.

That changes the game completely.

It basically slashes the marginal cost

of trust to near zero.

It really does.

It means a brand new startup platform

can offer its users the exact same level

of financial security as an eBay

or an Amazon right from day one.

It's safeguards those milestone-based payments

we were talking about earlier.

And it's huge for the lending sector too.

Think about co-lending,

where you might have multiple banks

and maybe an NBSE

all pulling money into a single loan.

You need a highly secure,

neutral place for all that capital to mix

before it goes out to the borrower.

Right.

It effectively unmundles the trust function

from the big banks

and just offers it to the market as a utility.

Which naturally segues into the broader theme

of the interview inclusion.

Because when you strip away all that friction

and those high legacy costs,

who actually benefits the most?

It's the little guy.

The MSMEs.

The businesses that traditional banks

usually just ignore.

Precisely.

We talk a lot in this industry about the credit gap.

You know, why don't big banks lend to small businesses?

It's not because they hate small businesses.

No, it's because they just can't see them.

The financial data is too opaque.

You've got cash businesses,

messy handwritten ledgers.

For a bank,

the underwriting cost is too high

and it's simply too risky.

But look at what happens

when you layer this programmable

funny dance we've been talking about

on top of open finance.

Transbrink talks about using consent-based aggregation.

Right.

If a business runs its cash flows

through these smart programmable rails,

suddenly everything becomes visible.

The behavior itself basically becomes the collateral.

Observable behavior.

That's the exact phrase to be used.

If I'm a lender,

and I can verify your real-time cash flow

because I am literally watching

the transaction settle instantly on my rails,

I don't need to ask for your property deep.

Right.

I can underwrite you

based purely on the fact

that you are a healthy,

operating cash flowing business.

Efficiency is inclusion.

I honestly think that's the most powerful takeaway

from this whole deep dive.

It's not about charity.

It's about making the financial system granular enough

to finally see value

where it was previously just invisible.

And doing it at a cost structure

that actually makes economic sense.

A small rural lender

can't afford a massive due diligence team

in a skyscraper.

But they can afford an API call

that scores a borrower

based on real-time verified flows.

Now, I want to play devil's advocate

for just a second here.

Because we're painting this really

rosy picture of frictionless flowing money,

but transferring operates globally, right?

They do.

They have clients in India,

the Middle East,

Southeast Asia,

and the world is definitely not flat

when it comes to banking regulations.

Oh, far from it.

It is an absolute minefield.

You've got strict data localization laws in Europe.

You've got highly specific reporting formats

required in the Philippines.

You've got KYC rules

that change entirely every time you cross a border.

Right.

So how on earth do you build a single operating system

for treasury

when the rules of the game

are different in every single country?

This is where Vidhov Tambay's

engineering background

really shines through in the interview.

He describes what they call a layer cake approach.

Okay, visualize that layer cake for us.

So the base of the cake is the core engine.

This is the heavy-duty tech

that actually moves the money,

handles the logic,

manages that real-time ledger we talked about.

That core code is universal.

It doesn't care if it's processing rupees

or durums or dollars.

That's the intel inside.

Right, exactly.

Right.

But then, on top of that base,

they build specific compliance layers

for each individual geography.

Oh, I see.

So one layer handles the local KYC checks.

Another layer formats the transaction

reports exactly how the local central bank demands them.

Another layer ensures that the data stays on servers,

physically located within that country,

if the local law requires it.

So they don't just copy-paste the whole platform

when they enter a new market.

They adapt the surface layers

while keeping the core engine completely consistent.

Exactly.

What's really interesting is that

Tambay doesn't view this massive compliance burden

as a negative thing.

Really?

Because a lot of tech companies,

especially in Silicon Valley,

try to actively skirt regulation,

you know, move fast and break things.

Exactly, but Transbrink takes the exact opposite view.

They see compliance as a major trust builder.

How so?

Because if you are hyper-compliant,

if you are seen as boring and incredibly safe,

the regulators and the partner banks

will actually open doors for you faster.

That makes sense.

Banks are terrified of compliance risks.

They are terrified of it.

So if you can walk into a bank and prove to them,

hey, our code literally prevents us from breaking the rules,

you instantly become their best friend.

And that totally explains the stats they mentioned.

They have over 40 bank integrations now

and over 220 clients.

And banks are notoriously hard to integrate with.

They are very protective of their core systems.

And that is Transbrink's moat.

They've done the hard yards.

They position themselves not as disruptors

trying to kill the banks,

but as the backbone,

they provide the orchestration layer.

Orchestration is such a good word for it.

The bank provides the vault in the regulatory license

and Transbrink basically provides the conductors wand.

And the reliability.

They ensure the music doesn't stop

just because a file format changed in one country

or a legacy server hiccups somewhere else.

So as we zoom out here,

we've covered the death of end-of-day reconciliation,

the rise of escrow as a service,

and this global layer cake of compliance.

What is the big picture takeaway from all of this?

I think the big picture is a fundamental shift

from relationship-based finance

to protocol-based finance.

Protocol-based finance?

That sounds a little bit cold, honestly, doesn't it?

It does sound cold initially,

but think about the implications for trust.

Historically, business trust was highly personal.

I trust you because we played golf together

or because our grandfathers did business in the same town.

Right.

And that's nice, but it's not scalable.

And where is it's highly exclusionary?

If I don't know you or if you're not in my network,

I can't trust you so we can't do business.

And programmable finance essentially replaces

that human handshake with code.

Exactly.

It allows us to outsource the trust to the protocol itself.

If the money is literally programmed

to only move when the mutually agreed condition is met,

I don't need to trust you personally.

I just need to trust the logic.

Which brings us right back to that opening

provocation from the article,

teaching money to listen.

If the money listens to the data and acts purely on the data,

the friction of human doubt just disappears.

And that theoretically allows commerce to flow faster

and reach further than ever before.

It allows the smallest player in the most remote market

to trade with a global giant with zero trust deficit.

It is a truly fascinating future.

It's hyper-efficient, yes.

But it also feels like by automating all the paranoia

and the ledger checking,

it frees us up to focus on the parts of the...

...actual product you're building.

You focus on that while the money just handles itself.

That is the ultimate promise here.

Let the machines handle the flow

and let the humans handle the value.

Well said.

A massive thank you to ViPav,

Tom Bay, and the IBSI FinTech Journal

for the source material on this one.

It's really given us a lot to think about

regarding the invisible plumbing

that runs our entire world.

It was an absolute pleasure unpacking it with you.

And thank you for listening.

Keep thinking about those if-then statements

in your own business operations.

You might be surprised where you find them.

We'll see you on the next deep dive.