Why No Treasury

This question comes up constantly so it deserves a direct answer.

Many cross-border payment companies maintain a treasury. They pre-fund accounts in destination currencies, float the exchange risk, and pay out from their own balance before the inbound funds clear. This is how traditional MTOs work. It is capital intensive, it creates counterparty risk, and it means the company is sitting on customer funds.

Papillae does not do this. Here is why it is not necessary and why not doing it is actually the stronger architecture.

For Web3 to Web3 transfers - when both the sender and recipient are transacting in stablecoins on-chain - there is no treasury question. Funds move atomically through smart contracts. The contract pulls, routes, and delivers in a single execution. There is no intermediate state where a treasury is needed. The blockchain is the clearing mechanism.

For Web3 to fiat transfers - when the recipient wants local currency in a bank account - the off-ramp partner holds the treasury, not Papillae. Yellow Card maintains naira pools in Nigerian bank accounts. Coins.ph maintains peso pools in Philippine accounts. Bitso maintains peso pools in Mexico. These are licensed financial institutions whose entire business is exactly this. When Papillae routes USDC to Yellow Card, Yellow Card pays naira from their own pool and holds the USDC as their reimbursement. The float risk and the treasury obligation belong to the regulated entity that is built to carry it.

This architecture means Papillae needs zero working capital to process payments. It means Papillae is never a counterparty holding customer funds. It means there is no Papillae treasury that can be hacked, mismanaged, or run dry. It means every dollar of investment goes into building the routing intelligence, not sitting in a bank account waiting to be deployed as float.

It is cleaner. It is more secure. And it is the correct structural answer for a pre-licensed infrastructure company.