Marqeta Straddles Bond and i2c

Marqeta matters because it collapsed two layers of the card stack into one better product. Legacy processors like i2c sit close to the payment rails and run the hard real time work of authorization, ledgering, clearing, and settlement, while Bond wraps that core with bank relationships, compliance, card manufacturing, and smoother implementation. Marqeta does the processor job, but with cleaner APIs and more operational packaging, so it feels more like a modern infrastructure platform than a bare processor.

• i2c is the bedrock layer. It is battle tested, but it is described as rough to integrate, not self serve, and closer to managed services than software. Marqeta sits in that same core processor position, but replaces older integrations with modern APIs and a more developer friendly workflow.
  1 sacra 3 sacra
• Bond is the smoothing layer on top. It helps a company avoid stitching together the issuing bank, processor, card manufacturer, compliance work, and contracts on its own. Bond makes money from implementation, subscriptions, transaction fees, and interchange share because it is managing the program, not just processing transactions.
  1 sacra 4 sacra
• Marqeta straddles both because it won enterprise customers by offering processor level control with enough onboarding, bank abstraction, and program support to remove much of the old friction. That is why it scaled with customers like Square and Ramp, while pure BaaS platforms still leaned on issuer processors underneath.
  1 sacra 2 sacra 3 sacra

The direction of travel is toward more unbundling at the top and more power at the processor layer underneath. As more fintechs and software platforms want flexibility over banks, networks, and product design, the winners will look like modern processors with modular services around them. That is the path Marqeta opened, and the path newer issuers are still chasing.