Company
People hold assets. They should be able to spend them.
Trillions of dollars sit in brokerage and wallet balances that cannot buy anything without first being sold, settled, and moved. StockPay is the payment layer that closes that gap.
How we build
Payments software earns trust by being boring in the right places. These are the rules we hold to.
Integers, never floats
Fiat in minor units, asset quantities as arbitrary-precision integers crossing the wire as strings. A float anywhere in a settlement path eventually mis-pays someone.
Observe, do not trust
Confirming a payment opens a channel; it never marks money received. Settlement requires an independently observed transfer at the required depth.
One state machine
Every status change goes through a single guarded transition. A late webhook cannot resurrect a canceled payment, and a redelivered callback is a no-op rather than an error.
Say what does not work
Our own docs open with the limits of the Robinhood integration rather than burying them. An integrator who discovers a constraint in week three has been failed twice.
Where the product actually stands
Written plainly, because a payments company that oversells its own readiness is not one you should route money through.
Live
The API surface, ledger, quoting, state machine, payment links, hosted checkout, idempotency and signed webhooks. ETH and USDC settlement verified against a real chain, tested on Sepolia.
Adapter-backed
Equity custody. Pricing, quoting and the ledger are real; the custody handoff runs through a simulator until a brokerage partner is connected.
Not built yet
Rate limiting enforcement, KYC and AML, tax reporting, payout execution, and multi-process coordination. Each is table stakes before real money at scale.
Get in touch
Brokerage and custody partnerships, platform accounts, or an integration question that the docs did not answer.