This is what smart contracts do.
A smart contract with a stablecoin (or a wrapped stabblecoin) would probably solve for this use case.
You want to avoid leaving a bank password in clear text for the process running in cron; so it would really be best for the bank to support Read-Only and Read-Write access tokens
Good point on smart contracts: that's one approach I'm exploring.
Trying to figure out if this should be:
- Crypto-native from day 1 (smart contracts + stablecoins)
- Fiat-first with crypto as backend (abstract the blockchain)
- Pure fiat (traditional banking APIs)
What would you actually use?
This should be available in your bank or other treasury management provider automation. Does your bank not support this? If you're not getting this from your current biz bank, I would shop around. I recommend Mercury (no affiliation, just a happy customer), but others provide some level of this too.
(workflow automation providers do not want this liability, as you note in Zapier's ToS, which is totally fair)
Does Mercury actually support this? Or are you describing scheduled payments
(which still require manual setup each time)?
I'm looking for:
- Dynamic rules based on revenue amount
- Multiple variable destinations
- Percentage-based splits
- One-time setup, runs forever
Maybe I'm missing a Mercury feature? What's the workflow you use?
Im a Brex user and interested by this