The piece frames the disappearance of legacy crypto on-ramps and external bridges as payments become invisible, quoting Alex Fine: “The age of on-ramps will be completely dead and the age of external bridging sites will be dead.”
Fun powers 100% of deposits and withdrawals on Polymarket, processes more than $3 billion in monthly transaction volume, and has raised more than $75 million to date.
Fun processes deposit flows into Aave’s largest vaults and provides APIs that allow fintechs and crypto applications to embed deposits, withdrawals, settlement, and checkout directly into their products. The article names prediction markets Polymarket and Kalshi as platforms using Fun’s infrastructure. In the case of Polymarket, Fun powers 100% of deposits and withdrawals on the platform. These technical elements are presented as part of Fun’s payments infrastructure.
These points are presented within the article’s coverage of evolving crypto payments infrastructure. The statements identify the technical routing and API integration capabilities attributed to Fun. They appear alongside the article’s discussion of on-ramps and external bridges.
The crypto payments ecosystem remains fragmented, with developers stitching together card processors, banking partners, crypto assets, blockchains and bridges to create funding experiences. This fragmentation requires engineering teams to integrate disparate payment rails and asset types across multiple partners and protocols. As a result, teams repeatedly rebuild similar funding infrastructure rather than reuse common components. The article identifies this repeated rebuilding as a characteristic challenge in Web3 payments.
Alex Fine’s quoted remarks address this fragmentation and its consequences: “The age of on-ramps will be completely dead and the age of external bridging sites will be dead,” Fine said. He also contrasted payments in Web2 and Web3, stating: “In Web2, payments are highly fungible,” Fine said. “In Web3, they’re much more complex because every payment method behaves differently. Teams keep rebuilding the same infrastructure over and over again instead of building unified optimized funding flows.”
The article frames these observations as an argument for unified payment flows embedded into applications. It presents the fragmentation and Fine’s comments as part of the case for simplifying crypto funding experiences.
The article closes by describing a shift toward unified crypto payments infrastructure in which funding and settlement are embedded directly into applications, reducing reliance on separate on-ramps and external bridges as payments become effectively invisible to users. It frames this evolution as a move away from fragmented, developer-assembled stacks toward integrated APIs and routing that consolidate deposits, withdrawals, settlement and checkout within product flows, presenting unified payments as the expected architecture for mainstream crypto experiences.
