Brex Embedded offers risk-bearing card infrastructure
Art Levy, Chief Business Officer at Brex, on the strategy of Brex Embedded
The strategic point is that Brex Embedded is selling a finished card business, not just card plumbing. A platform like Navan or Coupa can drop Brex into checkout or procurement flows and get underwriting, credit approval, fraud operations, and access to balance sheet capital in one package. That is a much heavier lift than issuing an API, because someone still has to eat losses, fund receivables, and staff the risk teams when spend scales.
-
Fraud risk means someone has to monitor suspicious swipes, chargebacks, and account takeovers, then absorb losses when bad transactions slip through. Credit risk means deciding who gets a 30 day charge card and how large a limit they get. Capital risk means funding that spend before the customer pays the bill, often with debt warehouses.
-
Program managers like Stripe, Marqeta, Bond, and Synctera mainly reduce operational setup friction. They help connect the fintech to banks, processors, and compliance workflows. But the broader card economics still depend on who takes interchange, who funds receivables, and who is on the hook when fraud or repayment losses hit.
-
This is why Brex sees embedded as a distribution channel for its existing risk stack. It already underwrites customers, manages fraud, and funds card balances for its core business, so embedding the card inside travel and procurement software lets Brex spread that infrastructure across more volume while partners keep focus on software workflows, not bank like risk operations.
The market is moving toward fewer players that can combine software with real risk bearing infrastructure. As embedded card programs grow, the winners will be the companies that can offer both elegant APIs and the balance sheet, underwriting, and fraud machinery behind them. That shifts advantage toward vertically integrated issuers like Brex and away from thinner middleware layers.