Lightspark Built Six Working Apps Inside Its Payment Docs

Zagging on design

Griffin Camper says that on every other payments infrastructure and financial services site, "you see the same story," with many companies using the same graphics and the same identity. His answer for Lightspark was to ask "when everyone's zigging, how do we zag" and to go deep into its roots as a design forward company. He describes his own role as the connective tissue across departments, turning technical jargon into something easy and digestible.

The company also dropped its internal product names. Griffin Camper says it was easier to talk about payments, accounts, cards, and DeFi and trading as categories.

Apps inside the docs

In the Lightspark Global Accounts Playground, Pat Capulong says the team rebuilt iOS for the web "super one to one," because imperfect demos break the immersion. All the flows are complete across the six apps. Griffin Camper says the team at a16z sent a note calling them the best docs they had ever seen.

A second tool, Build Your Flow, lets users pick a source and destination currency, such as USD to BRL, see how money moves through Lightspark, and get the code needed to run it.

Money from A to B

Griffin Camper calls Bitcoin "the invisible engine" but says the method matters less than moving money with no friction, the highest deliverability and the lowest cost. Whether the customer is an enterprise or a developer who wants to go live in three to five days, he says the docs should let them serve end users right away.

Care over AI output

Pat Capulong argues that people can tell when a human cared about every pixel and animation transition, and that this builds trust. Griffin Camper adds that Lightspark gives customers launching payments its playbook, design elements and UX best practices.