Five vendors. Three requests.
Identity, open banking, balance check, fraud scoring, and multi-rail payment. Three API calls replace your entire stack.
customers.create bridge.link charges.create The payments stack, collapsed
Most teams stitch together a KYC provider, an open banking aggregator, a payment processor, and a fraud vendor. Each with its own contract, SDK, and failure modes.
Verify the customer
One call to customers.create runs graph-based KYC, fraud scoring, watchlist screening, and address verification. Sub-second. No selfies. No third-party redirect.
Connect the account
Initialize a Bridge widget session and let your customer connect their bank. The widget handles auth, account selection, and verification. You get back a Paykey: a secure token binding identity to account.
Move the money
charges.create checks balance, selects the optimal rail, initiates the transfer, and monitors for fraud. You set the intent; the system picks the fastest path.
The system picks the fastest path
You set the payment intent. Straddle evaluates amount, urgency, and recipient bank to select the optimal rail. No configuration needed.
The system handles the rest
Signed webhooks for every state change. ML fraud scoring on every transaction. Balance monitoring, sanctions screening, velocity checks. You get notified; you don't have to poll.
Your first charge in three requests
$ straddle customers create --name 'Ron Swanson' $ straddle bridge link --customer cus_8f3a $ straddle charges create --amount 425000 --paykey pk_2b7c Get sandbox access in minutes. No sales calls, no contracts. Build first, talk to us when you're ready.