Xpend B2B
Businesses want to accept digital assets without becoming crypto companies. Xpend B2B is the infrastructure that turns that wish into a reliable payment relationship.
- Technical leadership across payment flows and B2B product surfaces.
- Active alongside the consumer Xpend product.
What it is
Xpend B2B helps businesses accept digital assets and settle into something they can operate on, without forcing them to understand wallets, chains, and confirmation mechanics as a day job.
Merchants create a payment. Payers complete it through a checkout experience. The business gets a clear signal when money is actually there.
The problem
Accepting crypto can look simple in a pitch. In practice it asks merchants to think about deposit addresses, network delays, confirmations, asset mismatches, and what “paid” really means.
Most businesses do not want that complexity. They want collection, confirmation, and settlement that behave like payments.
How we approached it
The centre of the design is a payment intent: a clear record of what should be paid, how it can be paid, and what state it is in.
A payment is not treated as complete because an API call looked successful. There has to be a reliable relationship between the intent, the actual payment, enough confirmation, the merchant’s available balance, and the notice the merchant receives.
Intent
Merchant asks to collect a payment
Checkout
Payer is given a clear way to pay
Payment
Value arrives through the supported rails
Confirmation
The system waits until the payment is trustworthy
Balance
Available funds update for the merchant
Notice
The merchant is told what happened
The parts that matter
Seeing activity on a network is not the same as having money you can safely treat as settled. Credit has to wait for trust.
Merchants should not reconcile half a dozen partial signals. Available balance has to come from a disciplined settlement path.
Signing money-moving operations is separated from the systems that hold merchant state. That boundary is a security decision as much as an engineering one.
Networks fail and clients retry. Partner APIs and internal processing have to tolerate that without creating duplicate credits or payouts.
What I work on
My work here is the infrastructure thinking: how payment intents behave, when money becomes available, how merchants are notified, and how the system stays exact while the merchant experience stays small.
The goal is easy to say and expensive to build: digital assets in, settlement merchants can trust, without turning every integration into a crypto education project.
Where it is now
Xpend B2B continues beside the consumer product. The unfinished work is still the important work: staying correct under messy provider and network conditions, while keeping the merchant mental model simple.