Buyer Personas & Readiness
Bank Readiness looks at the supply side: whether institutions are prepared to issue, hold, and move digital money. This page looks at the other side of the same transaction — the buyers who have to say yes.
Buy-Side Summary
| Persona | Primary Use Cases | Key Stablecoin Value | Readiness Level |
|---|---|---|---|
| 1. Corporate Treasury Teams | Cross-border B2B settlement; intercompany transfers; trapped-cash management; FX optimization | Replaces SWIFT for select corridors; frees pre-funded capital; programmable, 24/7 settlement | Medium |
| 2. Bank Technology & Business Teams | Tokenized deposits; correspondent-bank alternatives; intraday liquidity; trade finance and DvP | Defends transaction-banking franchise; enables atomic settlement and programmable trade flows | Medium–High |
| 3. Trading Firms & Crypto-Native Institutions | Trading collateral; cross-exchange liquidity routing; tokenized Treasury yield on idle cash | 24/7 base currency for digital-asset markets; yield-bearing collateral efficiency | High |
| 4. Entrepreneurial International Consumers | Dollar savings in weak-currency markets; cross-border remittance; nomad spending; freelance payroll | Access to USD without a U.S. bank account; near-zero remittance cost; same-day payouts | High |
| 5. Fintech Platforms | Embedded stablecoin rails for cross-border payouts, card programs, and yield products | Lower settlement cost; broader payout coverage; eliminates pre-funding; faster product launches | High |
The ordering is worth noting. Readiness is highest in the personas that already operate in digital dollars and lowest in the one that most institutional product roadmaps name first. That inversion is the chasm as a product problem: the buyer with the largest addressable flows is the buyer least familiar with the instrument.
Why Readiness Is the Product Manager’s Question
The Digital Money Adoption score places each of the 15 use cases in a stage of the Technology Adoption Life Cycle from Geoffrey A. Moore’s Crossing the Chasm. That placement is deliberate, and it carries a warning that is easy to miss.
The warning is in what a high score actually measures. A score of 7.0 reflects supply-side institutional readiness, not population penetration. It says that the rails exist, the regulatory path is visible, and reference deployments are running. It does not say that the buyer is ready to move.
That gap is the chasm, and it is where digital money products will be won or lost. Moore’s argument is that early adopters and the early majority buy for different reasons: early adopters buy a technology advantage and will tolerate incompleteness to get it, while the early majority buys a whole product to solve a business problem they already recognize and will not go first. A product built on evidence drawn entirely from early-adopter deployments — the pilot announcements, the consortium press releases, the issuance charters — is a product calibrated to the wrong buyer.
For a product manager, the operational conclusion is narrow and demanding. Demand-side readiness cannot be inferred from supply-side activity. It has to be ascertained through customer and market research, for the specific persona the product targets, before the product is built. The questions are the unglamorous ones: does this buyer recognize the problem in the terms the product solves it, who inside the organization owns the decision, what has to be true in their systems and their controls for a yes, and what would they have to stop doing. None of that is visible in a vendor announcement or an on-chain volume chart.
The Treasury Case
Corporate treasury is where the gap is widest, and it is also where the most institutional stablecoin product effort is currently aimed.
In the most recent Association of Financial Professionals digital payments survey, only 13% of respondents said they were “very familiar” or “familiar” with stablecoins [AFP]. Familiarity rose to 34% for tokenized purchases — money market funds, deposits, repo — which suggests that tokenization of traditional assets is further ahead in treasury mindshare than stablecoin payments.
Read that as a product signal rather than a verdict. A stablecoin product targeted at treasury managers is being taken to a population in which roughly seven in eight practitioners do not yet claim familiarity with the category. That is a market-development problem before it is a feature problem, and it does not respond to a better API, a lower fee, or another pilot with another bank. It responds to education, to a use case the treasurer already has a line item for, and to the arrival of the whole product — ERP and treasury-management system integration, accounting treatment, audit trail, counterparty and reserve transparency, and a named person at the bank who will answer for it.
It also suggests where a treasury-facing product should start. The 34% familiarity with tokenized instruments points at money-market and collateral workflows as the shorter path into the treasury function, with payments following once the instrument is familiar. That is a hypothesis to test with treasurers, not a conclusion to design around.
How to Read the Readiness Levels
The five personas below are the buyer markets the Field Guide tracks. Each carries a readiness level — Medium, Medium–High, or High — that is an editorial judgment based on observed deployments, published survey data, and the pain points the persona already recognizes.
These levels are a starting hypothesis, not a research finding. They are pitched at the level of the persona, and no persona buys anything; a specific treasury team at a specific company with a specific ERP and a specific set of controls does. Treat a readiness level as a prior to be tested against primary customer research for the segment a product actually targets, and expect the variance inside a persona to be wider than the difference between two personas.
Buy-Side Markets
1. Corporate Treasury Teams
Treasury teams at multinationals and mid-market companies manage liquidity, FX risk, intercompany settlement, and working capital across multiple jurisdictions and entities. Multinationals run shared treasury centers (Dublin, Singapore, Amsterdam) serving dozens of subsidiaries; mid-market firms face the same challenges with fewer dedicated tools and staff.
Primary pain points stablecoins address:
- Trapped cash and emerging-market repatriation friction (e.g., Nigeria, Argentina, Pakistan)
- Intercompany settlement latency on SWIFT (1–5 days, pre-funded accounts)
- Correspondent-bank FX spreads of 0.5–2% on cross-border transfers
- Working capital tied up in pre-funded subsidiary accounts
Key vendor evaluation criteria:
- Regulatory compliance across operating jurisdictions (GENIUS Act, MiCA, MAS)
- Integration with ERP/TMS systems (SAP, Oracle, Kyriba, FIS)
- Counterparty and custodial risk; reserve framework transparency
- Audit-ready reporting and FASB ASC 350 accounting treatment
Representative firms: Siemens (JPM Kinexys); PayPal (USDC merchant settlement); Airbnb; Stripe (post-Bridge); LatAm corporates using Conduit, BVNK, or Bitso Business.
2. Bank Technology & Business Teams
Internal teams at commercial and investment banks — digital asset desks, blockchain innovation labs, transaction-banking divisions, and payments product groups — that evaluate and deploy stablecoin infrastructure for both internal operations and corporate client services. They sit at the intersection of technology, compliance, and business development inside heavily regulated institutions.
Primary pain points stablecoins address:
- Correspondent-banking inefficiency on shrinking SWIFT corridors
- Intraday and 24/7 liquidity demands legacy batch systems cannot meet
- T+2 securities settlement and intraday credit exposure (vs. atomic DvP)
- Competitive pressure from non-bank fintechs capturing cross-border volume
Key vendor evaluation criteria:
- Regulatory status of provider (OCC, state-licensed, MiCA-regulated)
- Permissioned vs. public chain architecture (often institutional-grade preferred)
- Legal framework distinction: tokenized deposits vs. payment stablecoins
- Integration with core banking platforms (Temenos, FIS, Finacle); BSA/AML/Travel Rule support
Representative firms: JPMorgan Chase (Kinexys/JPMD, $3B+ daily); Standard Chartered (Ripple investor); Citi (Token Services); Deutsche Bank; HSBC.
3. Trading Firms & Crypto-Native Institutional Buyers
Hedge funds, proprietary trading firms, market makers, and crypto-native institutions that use stablecoins as trading collateral, settlement currency, and yield-bearing instruments. These are sophisticated users evaluating products through a lens of liquidity, yield, counterparty risk, and operational efficiency rather than “adoption” concerns.
Primary pain points stablecoins address:
- T+0 settlement requirement for digital asset trading
- Margin and collateral efficiency; yield-bearing stablecoins as collateral
- 24/7 liquidity routing across exchanges (cannot use wires)
- Yield on idle cash via tokenized Treasuries (USDY, OUSG)
Key vendor evaluation criteria:
- Reserve quality, transparency, and attestation cadence
- Liquidity depth and same-day redemption capacity ($100M+)
- Smart-contract audit history and security track record
- Cross-chain availability, DeFi composability, and regulator status (NYDFS, OCC, MiCA)
Representative firms: Jump Trading / Jump Crypto; Cumberland DRW; Citadel Securities; Grayscale; Galaxy Digital.
4. Entrepreneurial International Consumers
A broad and growing category of individuals whose financial lives don’t fit inside a single country’s banking system: remote workers in weak-currency markets, frequent international travelers and digital nomads, and crypto-native early adopters who prefer digital dollars to bank accounts. Common threads: currency volatility, expensive remittances, slow international transfers, and limited USD savings access.
Primary pain points stablecoins address:
- Local-currency devaluation risk (Argentina, Turkey, Nigeria)
- Remittance cost (6–10% via traditional networks vs. cents on stablecoins)
- Banking access for unbanked/underbanked populations
- Cross-border spending without per-transaction FX fees (Rain, Kast Visa cards)
Key vendor evaluation criteria:
- Onboarding ease (no bank account required; light KYC)
- Local-fiat off-ramp quality (MXN, NGN, BRL, ARS)
- Visa/Mastercard card acceptance
- USD yield on balances (4–7% APY) and mobile-app quality
Representative firms: Remote workers using Bitso, Kast, or Revolut; freelancers on Rise or Bitwage; digital nomads on Wirex or Kast Visa cards; LatAm/Africa retail savers on Nubank and regional wallets.
5. Fintech Platforms
Neobanks, payment apps, and remittance companies that embed stablecoin rails into existing products as back-end infrastructure rather than as a primary crypto offering. They are typically already operating regulated payment businesses and are evaluating stablecoins as an upgrade to fiat rails. The stablecoin may be entirely invisible to the end user.
Primary pain points stablecoins address:
- Settlement-cost reduction vs. card networks and correspondent banking
- Payout-coverage expansion to 150+ countries via stablecoin infra (Rain, BVNK, Zero Hash)
- Pre-funding requirements that lock up working capital
- Need for real-time speed as a table-stakes feature
Key vendor evaluation criteria:
- API quality and developer experience (time-to-launch)
- Regulatory licensing coverage (does provider hold the license?)
- On/off-ramp quality and stablecoin-asset breadth (USDC, USDT, EURC)
- Card issuance, white-label flexibility, and embedded compliance (KYC, AML, Travel Rule)
Representative firms: Western Union / Convera (Ripple/RLUSD); MoneyGram (Fireblocks); Zepz / WorldRemit; Nuvei (Rain partner); Brex / Ramp.
What This Section Still Needs
This page carries forward the buy-side personas from the v0.6 Buyer’s Guide. The following gaps are identified transparently for reviewers and potential contributors:
- Primary research behind the readiness levels. The levels are editorial judgments from observed deployments and published surveys. Structured interviews with practitioners in each persona — treasury, bank product, trading operations, platform engineering — would replace judgment with evidence and expose the variance inside each persona.
- Full AFP survey data. The 13% and 34% familiarity figures come from reported summary language. The complete AFP digital payments survey dataset, including breakdowns by company size, industry, and treasury structure, would show whether the familiarity gap is uniform or concentrated in segments a product could avoid or target.
- A buying-committee map for each persona. Familiarity is measured at the respondent level, but digital money purchases clear a committee: treasury, controller, tax, internal audit, IT, and often the relationship bank. Documenting who has to sign, and what each signer needs, would make the readiness levels actionable.
- Decision criteria weights. The evaluation criteria listed under each persona are unordered. Knowing which criterion is the binding constraint — regulatory status, ERP integration, accounting treatment, redemption depth — would tell product managers what to build first.
- Evidence from buyers who evaluated and declined. The deployments and surveys in the Field Guide skew toward institutions already exploring digital money. A source covering buyers who ran an evaluation and chose not to proceed, with their stated reasons, is the most direct available read on where the chasm actually sits.
Sources
- [AFP] Association of Financial Professionals — 2025 AFP Digital Payments Survey. 13% of respondents “very familiar” or “familiar” with stablecoins; 34% for tokenized purchases. Discussed in Stablecoin v. ACH.
- [MOORE] Geoffrey A. Moore — Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers. Technology Adoption Life Cycle stages used in the Digital Money Adoption score.
- [BG] U.S. Stablecoin Field Guide — Buyer’s Guide, POC v0.6, May 12, 2026. Original source of the five buy-side personas and the summary table. Retired in v0.9; the sell-side taxonomy it defined is superseded by the Company Directory.
Page History
4 reader-facing changes since 2026-09-16; last change 2026-10-14 (v1.0.1).
Show all changes
| Date | Release | Change |
|---|---|---|
| 2026-10-14 | v1.0.1 | remove remaining v0.9 score references (Moore and CD pop-ups, buyer personas, overview, roadmap) |
| 2026-10-12 | v1.0 | Maturity matrix numbering matches Use Case sections, adds Global Business Payouts and Related DMA Use Case column; Buyer Personas readiness sentence corrected |
| 2026-10-12 | v1.0 | Buy-Side Summary moved to top of Buyer Personas in matrix style; signup form line covers weekly brief, research and DMA score |
| 2026-09-16 | v0.9 directory | Directory v0.9: split into Companies, Institutions & Regulators, Networks & Protocols |
Infrastructure and formatting commits are omitted. Release-level detail is in the Release Notes.