Issuer Processors Do Not Equal Embedded Finance
Roy Ng, EVP, Chief Business Officer at FIS, on the future of BaaS
Embedded finance is won in the messy middle, not at the processing layer. An issuer processor handles card authorization and ledger adjacent workflows, but a company still needs bank sponsorship, KYC and AML onboarding, compliance controls, account setup, support operations, and product logic that fits the parent software. That is why platforms like Bond, Unit, and Synapse sell a bundled path to launch, while processors like Marqeta or Galileo often serve as one core component inside a broader stack.
-
The practical difference is who stitches the stack together. Going direct to a processor can still leave a company sourcing its own bank partner, KYC vendor, ledger, and operations team. All in one BaaS platforms package those pieces so a non financial software company can test a card or account product faster.
-
This is why issuer processors skew toward card centric use cases, while embedded finance platforms sell outcomes. A processor helps create and route a card. Embedded finance means putting that card, account, or payout flow inside another product, like payroll, expense software, or a marketplace seller workflow, with onboarding and compliance already wired in.
-
The economic split also explains the stack. The fintech or software platform usually keeps the biggest share because it owns the customer relationship and product experience, while the bank, network, processor, and BaaS layer each take smaller cuts. The more pieces a company can bundle, the more margin and control it can keep.
The market is moving toward fewer vendors that combine processing with compliance, bank connectivity, and workflow software. Large enterprises may still unbundle and build more themselves over time, but the growth path in embedded finance is to start with a platform that makes launch simple, then pull pieces in house only after volume justifies the complexity.