CTO & Co-Founder Zynk | CTO @AmazonPay | President Technology @Lendingkart | Thinker
Joined August 2012
- Tweets 863
- Following 156
- Followers 384
- Likes 1,000
72 Photos and videos
Less than 24 hours left to apply, get $500,000 and prove everyone wrong → alliance.xyz
63
34
327
110,413
If your payment stack can’t respond to events in milliseconds, it’s not API-native.
Money must become event-driven.
1
42
Manish Bhatia retweeted
Apr 22
who are the strongest folks in crypto lending against receivables onchain or building with tokenized receivables?
69
2
132
19,206
Apr 22
Money should behave like compute.
On-demand.
Elastic.
Programmatically triggered.
Instead we still treat it like:
Batch files.
Manual approvals.
Static corridors.
Agent-native systems won’t tolerate that friction.
We’re entering the era of API-native money.
#AIAgents
41
Apr 20
Idle capital is a tax.
Programmable liquidity is the antidote.
30
Apr 13
Prefunding was a workaround for slow rails.
Multi-chain agent velocity exposes its inefficiency.
Every siloed balance sheet:
Dead capital
Canonical cross-chain issuance reduces fragmentation.
Programmable routing eliminates manual rebalancing.
Capital efficiency is strategic.
1
28
Apr 13
The next wave of payment infra will be liquidity-aware by default.
21
The winner won’t be “a bridge”.
It will be a routing engine across:
Chains
Liquidity pools
Bank rails
Agent wallets
Developers shouldn’t care where value sits.
#CrossChainRouting #LiquidityEngine #MetaLiquidity #ChainAgnostic #RoutingEngine #DeFiInfrastructure #CrossChainSwaps
24
Mar 28
Customer empathy is powerful — but it doesn’t scale.
Empathy is often 1:1. Human. Reactive.
Customer obsession, on the other hand, is designed.
It asks a different question:
👉 Why does the customer need to reach out at all?
True customer-obsessed organizations:
1
26
Mar 28
Build systems where customers can help themselves
Identify patterns, not just problems
Treat RCA as a core capability, not an afterthought
Because solving one issue is support. Solving the pattern is scale.
#CustomerExperience #CustomerObsessed #ProductThinking #Scale #Startups
14
Mar 21
Everyone talks about multi-chain.
But the real challenge is multi-domain.
Bank rails.
Stablecoins.
Smart contracts.
AI agents.
Chain-to-chain interoperability is just one layer.
1
35
Mar 21
Whoever abstracts both layers wins. Because the future stack won’t expose complexity.
It will route value seamlessly across domains — invisible to the user, programmable under the hood.
That’s where the next generation of infrastructure is being built.
1
22
Mar 13
Payments won’t just be triggered.
Treasury will be programmable.
If exposure > cap → rebalance
If balance < threshold → bridge liquidity
If settlement delay > SLA → reroute rails
Money movement becomes execution logic, not manual ops.
16
Mar 11
If treasury still lives in spreadsheets, you’re not multi-chain ready.
If treasury requires humans, you’re not future ready.
#AIAgents #MachineToMachine #ProgrammableLiquidity #APINative #FintechInfrastructure #Stablecoins #CrossChain #Web3Infrastructure #FutureOfPayments
1
18
Mar 10
Liquidity fragmentation is a hidden tax.
Multi-chain world manual treasury = idle capital.
Routing automation collapses that tax.
Capital efficiency becomes a competitive advantage.
13
Wrapped models fragment liquidity.
Canonical issuance compresses risk.
But without programmable routing, you still get capital inefficiency.
Automation is the unlock.
1
1
15
Bridging isn’t moving tokens.
It’s:
Where is capital sitting?
Where is demand?
What’s the cheapest finality path?
That’s routing logic — not UX.
13