The Rails Are Open. The On-Ramp Runs Through the Banks You Wanted to Skip.
BSP's open-finance push promises cheaper cross-border payments for Filipino founders. The sandbox slots and API keys route through the incumbents who already own the queue.
A Manila founder building a remittance app or a payroll tool for OFWs hears the pitch and it sounds like a fair shot: open finance, standardized APIs, a regulatory sandbox at the BSP, cheaper cross-border rails that cut the fees eating into every transaction. The digital-peso pilots and the open-finance framework read like a door swinging open for anyone with working code.
Then you try to plug in. The API access you need routes through incumbent banks and one or two large fintechs who sit between your product and the payment rail. They decide when your integration gets reviewed, what data you can pull, and how long you wait in a queue they control.
Access You Have to Ask For
The BSP's open-finance rules are opt-in and phased, which sounds cautious until you notice who gets to be first. Banks and the biggest e-money issuers move earliest because they already have the compliance staff, the sandbox relationships, and the volume that makes a partnership worth the incumbent's time. A three-person startup does not.
So the smaller player ends up building on top of a gatekeeper rather than beside one. Your cross-border transfer clears through a partner's license and infrastructure, and every improvement to your product depends on their roadmap, their fee schedule, and their appetite for a competitor that might one day route around them.
This is the quiet cost of rails that are technically open but practically permissioned. The regulator writes the standard, but the incumbents own the on-ramp, and access becomes something you negotiate rather than something you claim.
The Sandbox Is Not the Market
A sandbox slot is a chance to test, not a license to ship. Founders who clear the pilot still face the same partner banks when it comes time to move real money at real volume, and the terms rarely favor the newcomer. The fee you save the customer gets clawed back in the cut your infrastructure partner takes.
Regulators across ASEAN are running the same experiment, and the pattern repeats: Singapore's frameworks reward the well-capitalized, Indonesia's rails favor the established issuers, and the smaller founder waits in the same line everywhere. Open finance lowers the cost of building an app. It does not lower the cost of reaching the payment layer, because that layer is still owned.
If the BSP wants the digital peso to widen who gets to build, the fix is not another sandbox cohort. It is direct API access that does not require a founder to rent an incumbent's license, and a queue where the review time is published and enforced instead of set by whoever holds the integration.
Until then, the cheaper cross-border payment clears for the customer, and the founder pays the toll to the same bank the whole thing was supposed to route around.
