Most payment processors work the same way underneath, regardless of what the dashboard tells you. Money comes in, it lands in an account the processor controls, and it sits there until a payout runs on their schedule, not yours. That pooled account is a balance sheet risk for you and a liability for them, and it is the default nearly every platform reaches for because it is the easiest thing to build.
ChainPal does not work that way, and it was never going to. We are never a custodian. It is the first of the two rules we built the entire product around, and it shows up in the plumbing of every checkout session, invoice, payment link and terminal charge that runs through the platform.
A destination, not a balance
Before a payment is ever collected, your business names a destination: a bank account or an external wallet you control. ChainPal generates a single-use address for that specific payment, and when funds land on it, they route straight through to your destination. There is no intermediate pool, no internal ledger balance that represents "your money sitting with us," and no batch payout schedule standing between a payment clearing and it reaching you.
The single-use part matters as much as the routing does. A dynamic address per transaction, rather than one shared collection address, means every incoming payment is unambiguous from the moment it lands, and there is nothing for a custodial balance to accumulate into even transiently.
What this rules out
Being a non-custodian is not a marketing position, it is a constraint that removes certain features from the table entirely. ChainPal cannot offer you a "wallet balance" you top up and spend down, because there is no balance to hold. We cannot hold your funds overnight to earn yield on them, because they are never ours to invest. And if ChainPal disappeared tomorrow, there would be no pool of customer funds sitting on our books to sort out, because there never was one.
That last point is the one that matters most to a treasury team evaluating a new payments vendor. The question is not "how solvent is ChainPal," it is "does ChainPal ever get the chance to be insolvent with my money." The answer is no, and the architecture is why.
The same rule shows up on the other side
The same discipline applies to withdrawals out of a business’s own destinations. Treasury moves are executed as Safe transactions, signed by keys the business controls, not by ChainPal on the business’s behalf. ChainPal’s relayer sponsors the network gas so a business is not forced to hold native currency just to move its own stablecoin, but sponsoring gas is not the same as holding funds, and the two are kept deliberately separate in how the system is built and how it is accounted for.
Why it was the first decision
We are early, and we say so elsewhere on this site rather than let a polished demo imply otherwise. But the non-custodial architecture is not something we are building toward. It was the starting constraint everything else had to fit inside, because it is the one thing a business moving real volume across borders cannot get comfortable discovering later.