top of page
Financial Services
FinTech
Payment Processing
Flywire
Won high-value cross-border receivables by embedding payment, reconciliation, and refund workflows into universities’, hospitals’, travel companies’, and B2B firms’ core systems, despite PayPal, Wise, Western Union, and bank rails controlling much of global payment infrastructure.
1
MODEL
BUSINESS MODEL
Transaction-Based Platform
- Flywire was founded as peerTransfer in 2009 to simplify international tuition payments after Marcaide experienced costly, slow cross-border wires at MIT. [723][726][725] - It built a global payment network that matched cross-border flows, negotiated bank rates, and tracked payment status for institutions and payers. [726][725][727] - It embedded payments into client operating systems through certified integrations with SIS, ERP, CRM, and EHR platforms. [728][729][730] - It expanded from education into healthcare, travel, and B2B receivables, reaching more than 5,300 clients across 240 countries and territories and more than 140 currencies. [731][732][733] - It earns transaction fees on payment value plus platform and other revenues, with revenue recurring because workflows are mission-critical and deeply integrated. [734][735]
1. Identify a high-value, recurring payment or reconciliation workflow where existing banks, cards, or manual processes create cost, delay, or error. 2. Start with one vertical where the payer, payee, and payment event are predictable. 3. Build the integration layer before broadening payment coverage; workflow ownership creates retention. 4. Use banking, card, and local payment partners for rails while owning the software, reconciliation, and customer experience. 5. Expand into adjacent verticals only when the payment workflow, compliance capability, and integration pattern transfer. 6. Monetize the transaction event, then add platform fees for workflow software and services. The common mis-build is competing on FX rate alone rather than owning the receivables workflow.
Flywire began as peerTransfer in 2009 after founder Iker Marcaide struggled to pay MIT tuition from Spain. It proved repeatable demand in international education payments, then expanded into healthcare, travel, and B2B; by 2020 it had processed more than $12 billion in payment volume for over 2,000 clients. [723][724][725]
HOW THEY BUILT IT
HOW TO ARCHITECT IT
DISTRIBUTION MODEL
Direct Sales, Enterprise Sales, Product Integrations, Partnerships
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Flywire used direct institutional sales to universities, beginning with international tuition payment workflows. [723][724][725] - It built more than 100 certified integrations with ERP, SIS, CRM, and EHR systems, including NetSuite, Salesforce, Workday, SAP, and Oracle. [728][729][736] - It used a network of more than 20,000 education recruitment agents to reach international students and education institutions. [730] - It expanded through travel and hospitality integrations with Amadeus Delphi, Oracle OPERA Cloud, Mews, and Blastness Booking. [728] - Customer stories from Hult, Mediterranean Hospitality, Endeavor Health, and Basis Technologies demonstrated reconciliation, self-service, and cost-reduction outcomes. [728]
What worked: Sell into the institution that owns the receivable, then embed the payment workflow into its system of record; integration turns a one-time payment provider into recurring infrastructure. Trap if copied blindly: Integrations without payment-network depth or compliance capability create implementation burden but not transaction volume; it fails when the buyer cannot trust settlement, refunds, or reconciliation.
| PATTERNS OF THIS MODEL
PATTERNS IN VERTICAL PAYMENTS PLATFORMS: 1. WORKFLOW EMBEDDING CREATES PAYMENT VOLUME. When payments are triggered inside ERP, SIS, EHR, or booking systems, transaction frequency follows the customer’s operating rhythm. 2. RECONCILIATION IS THE RETENTION LAYER. Matching payments to invoices, student accounts, or patient records reduces manual work and makes replacement costly. 3. VERTICAL COMPLIANCE CREATES PRICING POWER. Regulated industries pay for refund handling, audit trails, and localized payment methods beyond generic checkout. THE WEAKNESS: Payment platforms remain exposed to card-network fees, banking partners, FX spreads, and regulatory change.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — AI RECEIVABLES OPERATIONS. The opportunity is an agent that predicts late payments, selects the local payment method, resolves failed transactions, and automates reconciliation—not merely a checkout page. GOLDMINE 2 — EMBEDDED CROSS-BORDER B2B PAYMENTS. Mid-market firms need invoice presentment, tax handling, FX, approvals, and ERP reconciliation in one flow; generic payment processors do not own this workflow. GOLDMINE 3 — PAYMENT-INTELLIGENCE LAYER. Transaction data can identify churn risk, collection friction, refund abuse, and currency preference; most processors stop at settlement. THE PIT — REGULATORY AND BANKING DEPENDENCE. Payment licenses, KYC, AML, sanctions, and bank partnerships constrain speed and margin. THE SECOND PIT — FX-RATE COMMODITIZATION. If the product competes only on exchange rates, Wise, banks, and payment aggregators can compress pricing. MOVE WITH CAUTION — Do not build another cross-border payments app; enter only with a vertical receivables workflow, compliance advantage, or embedded distribution advantage. [727][732][734][728][729]
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Universities, hospitals, travel companies, and B2B firms relied on wires, checks, manual reconciliation, and fragmented payment methods. Flywire digitized cross-border receivables by integrating payment, refunds, and reconciliation into SIS, ERP, EHR, and booking systems. [723][728][729][737]
MARKET TYPE
Fragmented Market
ENTRY STRATEGY
Greenfield Entry
WHY THEY WON
Cross-border receivables were fragmented across banks, card processors, FX providers, and manual back-office workflows. No dominant vendor unified high-value international payments with institution-specific reconciliation and refund workflows. Flywire exploited the gap between generic payment processors and vertical operating systems, especially in education where tuition, visas, refunds, and student records were interconnected. Its advantage was vertical integration into mission-critical workflows rather than competing solely on payment rails. The transferable lesson is that under-digitized payment workflows reward vendors that own reconciliation and compliance, not merely transaction execution. [723][732][728][729][737]
EXECUTION
Flywire entered by creating a dedicated cross-border tuition-payment workflow rather than competing as a general remittance provider. It built a payment network, payer experience, and institutional reconciliation layer for universities. The critical bet was that institutions would adopt a third-party payment platform if it reduced failed payments, manual reconciliation, and student support burden. This required banking partners, currency coverage, compliance, and SIS integration. The approach would fail if institutions did not view international payments as a strategic receivables problem or if the platform could not guarantee settlement and refunds. [723][726][725][737]
FOOTHOLD STRATEGY
Beachhead Strategy
Flywire’s beachhead was universities receiving tuition from international students. The pain was high-value wires, payment failures, manual reconciliation, and student support burden; these institutions were reachable through education networks, recruitment agents, and direct sales. From there, Flywire expanded into healthcare, travel, and B2B receivables. [723][725][728][730]
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Flywire’s strongest commercial asset was integration into the institution’s system of record, making payment volume recurring rather than transactional. KEY LEARNING: In payments, the buyer adopts the vendor that removes downstream operational work, not merely the one offering a payment button. HOW TO USE: If your product touches money movement, integrate with the customer’s reconciliation and compliance workflow before competing on payment features.
KEY LEARNING
THE STANDARD: In a fragmented payments market, entrants win by owning a vertical receivables workflow and embedding it into the customer’s operating system. RULE 1 — BUYERS ARE INSTITUTIONS WITH HIGH-VALUE RECEIVABLES. They care about settlement certainty, reconciliation, refunds, and compliance. RULE 2 — PRICING FOLLOWS TRANSACTION VALUE AND WORKFLOW DEPTH. Payment fees scale with volume; platform fees scale with software value. RULE 3 — SUCCESSFUL ENTRANTS OWN RECONCILIATION. Payment execution without invoice matching and refund handling remains a commodity. RULE 4 — FAILURE IS RAILS WITHOUT WORKFLOW. A payments app that does not embed into ERP, SIS, EHR, or booking systems is easily replaced. MARKET TYPE: Fragmented Market (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN INTEGRATION-LED ENTERPRISE DISTRIBUTION: 1. SYSTEM-OF-RECORD INTEGRATIONS CREATE DISTRIBUTION LEVERAGE. ERP, SIS, EHR, and CRM integrations place payments inside existing enterprise workflows. 2. AGENT NETWORKS REACH DISPERSED PAYERS. Education agents, travel partners, and channel intermediaries can drive payer adoption where institutions cannot market directly. 3. CASE STUDIES SELL OPERATIONAL OUTCOMES. Reconciliation savings, self-service rates, and payment success resonate more than FX pricing. 4. THE WEAKNESS: Integration-led distribution can create implementation dependency without transaction volume if the buyer does not route payments through the platform.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Greenfield entry is appropriate when a vertical payment workflow is manual, high-value, and poorly served by generic processors. RULE 1 — Validate that the buyer loses money or time to failed payments, reconciliation, or refunds. RULE 2 — Build the vertical workflow before expanding payment coverage. RULE 3 — Use banking and card partners for rails while owning software and reconciliation. RULE 4 — Reject greenfield entry when the buyer’s existing processor already owns the workflow and switching cost is high. [723][727][728][729]
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A beachhead strategy targets the vertical with the highest payment value, clearest reconciliation pain, and strongest reference effect. RULE 1 — Choose institutions with recurring high-value payments from dispersed payers. RULE 2 — Make the first workflow produce measurable reconciliation and support savings. RULE 3 — Expand into adjacent verticals only when the payment and compliance pattern transfers. RULE 4 — In payments, the beachhead must create recurring transaction flow; otherwise it remains a one-off remittance service.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Flywire earns transaction fees generally applied to payment value, plus fixed per-transaction fees and platform or other revenues. Its revenue is recurring because payment workflows are embedded in client systems and each tuition bill, patient visit, travel journey, or invoice creates a new fee opportunity. [734][735]
REVENUE MODEL
Transaction Fee, Subscription, Service Fee
PRICING MODEL
Transaction Fee, Usage-Based Pricing, Custom Enterprise Pricing
WHY THEY WON
Clients and payers pay transaction fees based on payment value, payment method, currency pair, and geography; Flywire also earns platform and other revenues for software and services. Revenue expands through more transactions, clients, currencies, and integrated workflows, while reconciliation and compliance deepen retention. [734][735]
Flywire charges transaction fees generally as a rate applied to total payment value, with variation by payment method, currency pair, and region; it also earns fixed per-transaction fees and platform or other revenues. [735]
TARGET AUDIENCE
Universities and education institutions (enterprise; want international tuition collection and reconciliation); hospitals and health systems (enterprise; want international patient payments and payment plans); travel and hospitality companies (enterprise; want global booking payments and lower cross-border cost); B2B firms (enterprise; want cross-border invoice collection and ERP reconciliation). [723][731][728][729]
CUSTOMER BUYING BEHAVIOUR
High payment failure rates, manual reconciliation, or cross-border collection friction triggers evaluation. Finance, IT, and operational leaders assess currency coverage, compliance, integrations, and reconciliation; they deploy through ERP, SIS, EHR, or booking-system integration, then expand across departments, geographies, and payment types. [734][728][729][737]
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Institutions pay to convert uncertain cross-border receivables into reconciled, compliant revenue. RULE 1 — PRICE THE TRANSACTION EVENT. Each tuition bill, patient visit, travel booking, or invoice is a fee opportunity. RULE 2 — SELL RECONCILIATION, NOT PAYMENT BUTTONS. The platform must match payments to invoices, student accounts, or patient records. RULE 3 — MONETIZE COMPLIANCE AND REFUNDS. Refund handling, audit trails, and localized payment methods reduce institutional risk. RULE 4 — WATCH PAYMENT-NETWORK COSTS. Card fees, bank spreads, FX margins, and compliance costs can erode take rate. The buyer is really buying receivables certainty, proven by the finance or bursar budget. [734][728][729][737][735]
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Banking and card-network dependence: Payment rails, interchange, FX spreads, and bank partnerships constrain margin and product control. Regulatory risk: KYC, AML, sanctions, data privacy, and cross-border rules increase compliance cost and can restrict corridors. FX commoditization: Wise, banks, and payment aggregators can compete on exchange rates and fees. Vertical concentration: Education, healthcare, travel, and B2B each carry distinct demand cycles and regulatory exposure. Integration switching risk: Deep ERP and SIS integration creates stickiness but also implementation complexity. Flywire went public in 2021, raising $250 million at an initial valuation around $3.4–3.5 billion; current ARR is not disclosed because it reports transaction and platform revenue rather than ARR. [726][738][739][732][734][735]
Where the model can break
4
MOTION
motion ge cs
Flywire sold high-value, compliance-sensitive payment infrastructure to universities, hospitals, travel companies, and B2B enterprises. It built a structured motion around institutional sales, certified integrations, banking partners, and customer success; by 2020 it served more than 2,000 clients and later more than 5,300 globally. [723][731][728][729]
GROWTH EXPANSION MODEL
Market Development, Platform Expansion
HOW THEY EXPAND
Flywire expanded from international tuition payments into healthcare, travel, and B2B receivables. It expanded its platform through more than 100 certified ERP, SIS, CRM, and EHR integrations, while extending currency and country coverage to more than 140 currencies and 240 countries and territories. [731][732][728][729]
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Against PayPal, Wise, Western Union, and bank rails, Flywire differentiates through vertical receivables workflows, reconciliation, refunds, and deep system integration. Its advantage is serving institutions with high-value, compliance-sensitive payment needs rather than competing solely on consumer remittance pricing. [726][727][728][729]
GROWTH ENGINE
GTM
Content Flywheel
Institutional sales wins a university, hospital, travel company, or B2B client. Integration embeds Flywire into the client’s SIS, ERP, EHR, CRM, or booking system, making each new bill, visit, booking, or invoice a transaction event. Reconciliation and refund automation increase retention, while education agents and travel partners extend payer reach. The engine depends on payment reliability, compliance, and integration depth; failed settlement or weak reconciliation breaks the loop. [734][728][729][737][730]
Flywire’s GTM is enterprise-led and partner-led. Institutional sales targets finance, IT, and operational leaders at universities, hospitals, travel companies, and B2B firms; certified integrations and banking partners enable deployment. Customer success drives expansion across departments, geographies, and payment types. The primary motion is enterprise sales; product integrations and partner networks create distribution leverage. This requires compliance, payment-network access, and implementation capacity; it is unlikely to work for low-value consumer remittances. [723][731][728][729][730]
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is high customer lock-in created by embedded payment workflows, reconciliation logic, refund rules, compliance configuration, and integration depth across SIS, ERP, EHR, CRM, and booking systems. Once Flywire becomes part of the client’s receivables operation, replacement disrupts finance and IT workflows.
| MOAT INTELLIGENCE
THE STANDARD: Payment lock-in strengthens when the platform owns reconciliation, compliance, and workflow context. RULE 1 — INTEGRATION DEPTH CREATES SWITCHING FRICTION. More than 100 certified ERP, SIS, CRM, and EHR integrations embed Flywire into client systems. RULE 2 — RECONCILIATION DATA COMPOUNDS. Payment matching, refund history, and audit trails become part of the client’s financial record. RULE 3 — COMPLIANCE CONFIGURATION CREATES DEPENDENCE. KYC, AML, sanctions, and refund rules are costly to rebuild. THE SIGNAL: Flywire’s 2025 10-K states that its solutions are deeply integrated within clients’ existing operating workflows and IT infrastructure, making revenue highly recurring. The moat does not protect against banking-partner failure, regulatory restriction, or a client migrating to a broader ERP-native payments suite. [734][728][729][737][735]
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — VALIDATE THE TUITION WEDGE. Flywire began as peerTransfer in 2009 to simplify international tuition payments after its founder’s MIT payment experience. WATCH: The product must prove settlement reliability and reconciliation value. $1–5M ARR — SCALE EDUCATION DISTRIBUTION. Flywire scaled through university clients and education recruitment agents, adding roughly 50–60 clients per quarter in an earlier growth phase. WATCH: Education demand is seasonal and enrollment-dependent. $5–10M ARR — EXPAND INTO ADJACENT VERTICALS. Under CEO Mike Massaro from 2013, Flywire expanded into healthcare, travel, and B2B, adding clients such as Expedia, Hilton, and Volvo. WATCH: Each vertical requires distinct compliance and integration capability. $10–50M ARR — BUILD THE GLOBAL PAYMENT NETWORK. By 2018, Flywire raised $100 million from Temasek and projected at least $100 million in annual revenue; it expanded currency and country coverage. WATCH: Banking partners, FX spreads, and compliance costs constrain margin. $50–100M ARR — INTEGRATE AND GO PUBLIC. In 2020, Flywire raised $120 million, acquired a California SaaS company, and reported more than $12 billion in cumulative payment volume; it IPO’d in 2021. WATCH: Public-market scrutiny increases the need for predictable revenue and margin discipline. $100M+ ARR — SCALE PLATFORM REVENUE. Flywire now serves approximately 5,100 clients across more than 240 countries and territories and more than 140 currencies, with transaction and platform revenue. Rule: In vertical payments, own the receivables workflow, embed into the customer’s system of record, and expand only when compliance and integration capability transfer. [723][725][740][731][733][734]
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Identify a high-value, recurring payment workflow, embed it into the customer’s system of record, and expand only when compliance and integration capability transfer. SEQUENCE: 1. Choose a vertical with dispersed payers, high transaction value, and manual reconciliation. 2. Build the payment, refund, and reconciliation workflow before expanding payment coverage. 3. Use banking and card partners for rails while owning software, compliance, and customer experience. WORKED: Flywire’s education beachhead, recruitment-agent network, and ERP/SIS integrations created recurring transaction volume and enterprise retention. CAUTION: Do not build a payments product without compliance and reconciliation depth; do not compete solely on FX pricing, where Wise, banks, and payment aggregators can compress margins. [723][726][734][728][729]
bottom of page