We’re excited to welcome David Ruderman as our newest Senior Account Executive. Dave brings over a decade of experience driving growth at the intersection of fintech, regulated markets, and emerging technologies. He’s built GTM functions from the ground up, closed enterprise deals in high-trust industries, and worked across the payments stack to scale quickly, all while keeping customer needs front and center. As we grow Beam’s footprint globally, we need people who can operate with urgency, navigate complexity, and build systems that last. With Dave’s experience across nascent industries, we’ll be able to support more teams solving complex payment challenges with the clarity and tools they need. Welcome to the team, Dave 🫡

most people talk about replacing SWIFT. but on the ground, payment teams are still asking for SWIFT support every day while stablecoin rails can be faster, cheaper, and offer real-time transparency, they don’t address the institutional dependencies that define how international payments actually work today. treasury workflows, ERP integrations, audit protocols, and regulatory reporting requirements are still deeply anchored to the infrastructure SWIFT has standardized, especially its messaging formats. over $150 trillion flows through SWIFT annually. and while stablecoins settled ~$2.4 trillion in payment volume over the last three months, most enterprise finance teams still rely on structured payment messages to reconcile funds, meet internal control requirements, and satisfy auditors. take MT103 and MT202 messages. they’re the structured language that banks, auditors, and financial systems use to define and verify a payment. MT103 provides line-item detail for single customer credit transfers: who sent the money, to whom, when, why, and how much. MT202, by contrast, facilitates transfers between financial institutions. they show up in SOC audits, ERP logs, and vendor compliance checks across global operations. global payments are built on messages, not “rails” per say. moving money from point A to B isn’t enough. enterprises also need to produce documentation that satisfies finance, compliance, and counterparties. and for most institutions, that still means SWIFT. that’s why @beam_cash was built to interoperate. we support both first- and third-party SWIFT flows, while also offering options like stablecoins, RTP, push-to-card, and ACH. global payments used to be defined by access. for decades, the primary challenge was gaining connectivity to the right rails. wiring up to SWIFT, negotiating bank relationships, and integrating with regional payment networks. speed was a differentiator. if you could move money into more markets, faster than your competitors, you had an edge. but that dynamic has changed. access is now commoditized. stablecoins offer permissionless global reach. APIs abstract away once-complex integrations. dozens of providers now offer real-time, cross-border connectivity. simply being "on the rail" no longer sets you apart. what matters is how you use the rails: which ones you choose, how you sequence them, and how you manage exceptions and compliance along the way. as stablecoins and traditional finance converge, teams are moving from asking “which rail should we use?” to “which rail is right for this transaction?” right now, it’s still SWIFT for the most part in xb transactions, but that’s changing quickly

most people talk about replacing SWIFT. but on the ground, payment teams are still asking for SWIFT support every day while stablecoin rails can be faster, cheaper, and offer real-time transparency, they don’t address the institutional dependencies that define how international payments actually work today. treasury workflows, ERP integrations, audit protocols, and regulatory reporting requirements are still deeply anchored to the infrastructure SWIFT has standardized, especially its messaging formats. over $150 trillion flows through SWIFT annually. and while stablecoins settled ~$2.4 trillion in payment volume over the last three months, most enterprise finance teams still rely on structured payment messages to reconcile funds, meet internal control requirements, and satisfy auditors. take MT103 and MT202 messages. they’re the structured language that banks, auditors, and financial systems use to define and verify a payment. MT103 provides line-item detail for single customer credit transfers: who sent the money, to whom, when, why, and how much. MT202, by contrast, facilitates transfers between financial institutions. they show up in SOC audits, ERP logs, and vendor compliance checks across global operations. global payments are built on messages, not “rails” per say. moving money from point A to B isn’t enough. enterprises also need to produce documentation that satisfies finance, compliance, and counterparties. and for most institutions, that still means SWIFT. that’s why @beam_cash was built to interoperate. we support both first- and third-party SWIFT flows, while also offering options like stablecoins, RTP, push-to-card, and ACH. global payments used to be defined by access. for decades, the primary challenge was gaining connectivity to the right rails. wiring up to SWIFT, negotiating bank relationships, and integrating with regional payment networks. speed was a differentiator. if you could move money into more markets, faster than your competitors, you had an edge. but that dynamic has changed. access is now commoditized. stablecoins offer permissionless global reach. APIs abstract away once-complex integrations. dozens of providers now offer real-time, cross-border connectivity. simply being "on the rail" no longer sets you apart. what matters is how you use the rails: which ones you choose, how you sequence them, and how you manage exceptions and compliance along the way. as stablecoins and traditional finance converge, teams are moving from asking “which rail should we use?” to “which rail is right for this transaction?” right now, it’s still SWIFT for the most part in xb transactions, but that’s changing quickly

Over $150T moves through SWIFT each year. It’s still the backbone of global finance, but most platforms struggle to access it with any flexibility Beam now supports first and third-party SWIFT payments to let platforms move money in their name or their users’, all with full compliance Paired with stablecoins, it’s how we’re helping teams move money faster from point A to point B

Stablecoin payment volumes are climbing. After Q1, volumes rose 11% quarter-over-quarter, with an average of $747 billion across April, May, and June. June reached $803 billion in volume, the highest monthly total ever recorded by Visa Onchain Analytics. This was the third consecutive month of growth and signals accelerating demand for stablecoins as an instant settlement layer. Since January, total volume has grown nearly 16%, with over $100 billion in additional payment flow. The annualized run rate is now approaching $9 trillion and reflects the increasing role of real-time, always-on, and programmable rails in global money movement.

founders talk incessantly about building the future. what we talk about less is what to do when the future takes longer to arrive than we planned. execution AND market timing are the name of the game - turns out the “why now” in a VC pitch actually makes sense ;) @beam_cash started out selling into consumer crypto platforms, with instant offramping as a starting point. we then added instant funding capabilities, enabling crypto wallets to be funded like Venmo, Cashapp or Robinhood. the tech worked tremendously. but we were too early - the market wasn’t mature enough yet. the few consumer crypto apps that existed had limited traction. most of the market was NFT-centric. there weren’t enough stablecoin-first platforms. primitives like @privy_io were just coming to market. there were no breakout examples like @slingmoney. and the banks, regulators & administration’s leadership weren’t helping. we had the right product, but not the right timing. so we made a hard pivot. we shifted to business-centric payment flows infra and focused on what was needed: giving crypto platforms like @felixpago the tools to make treasury flows compliant, fast, and programmable across both fiat and crypto rails. we went deep into stablecoin orchestration, compliance-as-a-service, and extending our domestic banking capabilities to non-US companies. instead of focusing on the application layer, we went a layer deeper. that pivot worked. since then, we’ve become the backend for several B2B fintechs, neobanks, and cross-border payment platforms. we scaled volume, expanded coverage, and matured the stack. over the past 6-8 months, B2C stablecoin platforms have picked up major momentum. from wallets and investment apps to remittance tools, more teams are building consumer-facing experiences that require simple crypto access under the hood. they’re coming to us in hordes asking for the exact product we started with - instant funding and payouts for consumer crypto, i mean, stablecoin applications - via one API. most platforms in our space avoid this, or push the fiat processing burden onto traditional gateways… but we leaned in. because the mess is where the moat is. the hardest problems in infra are usually the ones most shy away from because they’re messy. ACH debits, fraud monitoring, liquidity management, identity, etc. all hard. yet therein we provide value. so we've brought back our first service… what’s old is new again… we’ve reintroduced the same instant pay-in and payout flows for consumer platforms that we built in the early innings. plug-and-play APIs. fully embedded compliance. with more to come. the market is finally ready for it. sometimes the most valuable product is the one you had to shelve. then refine. then reintroduce when the timing is right.

founders talk incessantly about building the future. what we talk about less is what to do when the future takes longer to arrive than we planned. execution AND market timing are the name of the game - turns out the “why now” in a VC pitch actually makes sense ;) @beam_cash started out selling into consumer crypto platforms, with instant offramping as a starting point. we then added instant funding capabilities, enabling crypto wallets to be funded like Venmo, Cashapp or Robinhood. the tech worked tremendously. but we were too early - the market wasn’t mature enough yet. the few consumer crypto apps that existed had limited traction. most of the market was NFT-centric. there weren’t enough stablecoin-first platforms. primitives like @privy_io were just coming to market. there were no breakout examples like @slingmoney. and the banks, regulators & administration’s leadership weren’t helping. we had the right product, but not the right timing. so we made a hard pivot. we shifted to business-centric payment flows infra and focused on what was needed: giving crypto platforms like @felixpago the tools to make treasury flows compliant, fast, and programmable across both fiat and crypto rails. we went deep into stablecoin orchestration, compliance-as-a-service, and extending our domestic banking capabilities to non-US companies. instead of focusing on the application layer, we went a layer deeper. that pivot worked. since then, we’ve become the backend for several B2B fintechs, neobanks, and cross-border payment platforms. we scaled volume, expanded coverage, and matured the stack. over the past 6-8 months, B2C stablecoin platforms have picked up major momentum. from wallets and investment apps to remittance tools, more teams are building consumer-facing experiences that require simple crypto access under the hood. they’re coming to us in hordes asking for the exact product we started with - instant funding and payouts for consumer crypto, i mean, stablecoin applications - via one API. most platforms in our space avoid this, or push the fiat processing burden onto traditional gateways… but we leaned in. because the mess is where the moat is. the hardest problems in infra are usually the ones most shy away from because they’re messy. ACH debits, fraud monitoring, liquidity management, identity, etc. all hard. yet therein we provide value. so we've brought back our first service… what’s old is new again… we’ve reintroduced the same instant pay-in and payout flows for consumer platforms that we built in the early innings. plug-and-play APIs. fully embedded compliance. with more to come. the market is finally ready for it. sometimes the most valuable product is the one you had to shelve. then refine. then reintroduce when the timing is right.

founders talk incessantly about building the future. what we talk about less is what to do when the future takes longer to arrive than we planned. execution AND market timing are the name of the game - turns out the “why now” in a VC pitch actually makes sense ;) @beam_cash started out selling into consumer crypto platforms, with instant offramping as a starting point. we then added instant funding capabilities, enabling crypto wallets to be funded like Venmo, Cashapp or Robinhood. the tech worked tremendously. but we were too early - the market wasn’t mature enough yet. the few consumer crypto apps that existed had limited traction. most of the market was NFT-centric. there weren’t enough stablecoin-first platforms. primitives like @privy_io were just coming to market. there were no breakout examples like @slingmoney. and the banks, regulators & administration’s leadership weren’t helping. we had the right product, but not the right timing. so we made a hard pivot. we shifted to business-centric payment flows infra and focused on what was needed: giving crypto platforms like @felixpago the tools to make treasury flows compliant, fast, and programmable across both fiat and crypto rails. we went deep into stablecoin orchestration, compliance-as-a-service, and extending our domestic banking capabilities to non-US companies. instead of focusing on the application layer, we went a layer deeper. that pivot worked. since then, we’ve become the backend for several B2B fintechs, neobanks, and cross-border payment platforms. we scaled volume, expanded coverage, and matured the stack. over the past 6-8 months, B2C stablecoin platforms have picked up major momentum. from wallets and investment apps to remittance tools, more teams are building consumer-facing experiences that require simple crypto access under the hood. they’re coming to us in hordes asking for the exact product we started with - instant funding and payouts for consumer crypto, i mean, stablecoin applications - via one API. most platforms in our space avoid this, or push the fiat processing burden onto traditional gateways… but we leaned in. because the mess is where the moat is. the hardest problems in infra are usually the ones most shy away from because they’re messy. ACH debits, fraud monitoring, liquidity management, identity, etc. all hard. yet therein we provide value. so we've brought back our first service… what’s old is new again… we’ve reintroduced the same instant pay-in and payout flows for consumer platforms that we built in the early innings. plug-and-play APIs. fully embedded compliance. with more to come. the market is finally ready for it. sometimes the most valuable product is the one you had to shelve. then refine. then reintroduce when the timing is right.

founders talk incessantly about building the future. what we talk about less is what to do when the future takes longer to arrive than we planned. execution AND market timing are the name of the game - turns out the “why now” in a VC pitch actually makes sense ;) @beam_cash started out selling into consumer crypto platforms, with instant offramping as a starting point. we then added instant funding capabilities, enabling crypto wallets to be funded like Venmo, Cashapp or Robinhood. the tech worked tremendously. but we were too early - the market wasn’t mature enough yet. the few consumer crypto apps that existed had limited traction. most of the market was NFT-centric. there weren’t enough stablecoin-first platforms. primitives like @privy_io were just coming to market. there were no breakout examples like @slingmoney. and the banks, regulators & administration’s leadership weren’t helping. we had the right product, but not the right timing. so we made a hard pivot. we shifted to business-centric payment flows infra and focused on what was needed: giving crypto platforms like @felixpago the tools to make treasury flows compliant, fast, and programmable across both fiat and crypto rails. we went deep into stablecoin orchestration, compliance-as-a-service, and extending our domestic banking capabilities to non-US companies. instead of focusing on the application layer, we went a layer deeper. that pivot worked. since then, we’ve become the backend for several B2B fintechs, neobanks, and cross-border payment platforms. we scaled volume, expanded coverage, and matured the stack. over the past 6-8 months, B2C stablecoin platforms have picked up major momentum. from wallets and investment apps to remittance tools, more teams are building consumer-facing experiences that require simple crypto access under the hood. they’re coming to us in hordes asking for the exact product we started with - instant funding and payouts for consumer crypto, i mean, stablecoin applications - via one API. most platforms in our space avoid this, or push the fiat processing burden onto traditional gateways… but we leaned in. because the mess is where the moat is. the hardest problems in infra are usually the ones most shy away from because they’re messy. ACH debits, fraud monitoring, liquidity management, identity, etc. all hard. yet therein we provide value. so we've brought back our first service… what’s old is new again… we’ve reintroduced the same instant pay-in and payout flows for consumer platforms that we built in the early innings. plug-and-play APIs. fully embedded compliance. with more to come. the market is finally ready for it. sometimes the most valuable product is the one you had to shelve. then refine. then reintroduce when the timing is right.

Why do Uber want to use stablecoins? @daniel_mottice, CEO of @beam_cash, explains - Global scale - Efficiency - Yield - Increased velocity of money 🎙️ Listen to the latest episode of Tokenized: 📷 Watch on YouTube: