Entered-cost scenario
Every illustrative rate, share, minimum, and cost remains editable and visible.
Embedded Payments Unit Economics Calculator
Embedded Payments Unit Economics
Enter your values, then calculate to see a verified result.
Reference range
How this result is calculated
A clear calculation path based on your inputs.
Inputs usedReview the information used for this result.
Full calculation and sourcesOpen Full calculation for the assumptions, cost bridge, comparison table, and interpretation.
Versioned calculationFormula v1.0.0
Piecewise break-even
The solver preserves provider minimum commitments and reports unreachable cases explicitly.
Payments scope
This models acquiring economics, not all embedded-finance products.
Build adopted volumeConvert eligible distribution into active customers, payments, and GPV.
Adoption × usageReconcile the cost stackSeparate revenue share, partner bill, loss, support, and overhead.
No hidden benchmarksSolve scale and paybackFind break-even numerically and project contribution.
Minimums preservedInterpretation
Replace illustrative inputs with dated contract terms or reconciled actuals.
Keep economic value and regulatory responsibility aligned across every participant.
Separate direct payment contribution from indirect retention or SaaS value.
Use this result
Continue with your result
Compare, save, or take the next step
Did we solve your problem?Your feedback helps us improve this calculator.
Thanks. Your feedback has been recorded.
Keep exploring
Check out 1 similar fintech calculators & resources
Public verification recordFormula v1.0.0
- Review scope
- Financial-calculation-and-content-review
- Review team
- CalculatorGeek Algorithmic Team
- Verified
- 2026-09-25
- Next source review
- 2027-03-25
- Automated fixtures
- 10 cases
Review method
Independent formula derivation, boundary vectors, JavaScript/PHP parity, visible assumption review, primary-source review, content-intent separation, internal-link checks, desktop/mobile rendering, and browser interaction checks.
Known limitations
- The model represents merchant-payment economics, not every embedded-finance product.
- Entered weighted rates should come from a contract, invoice, or reconciled actuals.
- Fraud and dispute loss must follow the real responsibility allocation.
- Accounting gross-versus-net presentation, licensing, reserves, and capital require professional review.
Primary sources
Published calculation checks
| Case | Inputs | Expected result |
|---|---|---|
| Positive PFaaS base scenario | See versioned calculator fixture | {"active_customers":100,"monthly_transactions":20000,"monthly_gpv":2000000,"monthly_net_revenue":16500,"monthly_partner_cost":10400,"monthly_loss_cost":2000,"monthly_support_cost":200,"monthly_operating_contribution":1900,"break_even_active_customers":52,"break_even_eligible_customers":520,"payback_months":5.2631578947} |
| Provider minimum controls current bill | See versioned calculator fixture | {"monthly_partner_cost":15000,"monthly_operating_contribution":-2700,"economics_code":4,"payback_possible":0} |
| Referral label preserves entered economics | See versioned calculator fixture | {"monthly_net_revenue":4000,"monthly_operating_contribution":3500,"net_take_rate_bps":19.5} |
On this page
What the Embedded Payments Unit Economics Calculator calculates
The Embedded Payments Unit Economics Calculator converts eligible customers, adoption, transaction volume, contracted revenue, partner costs, entered losses, support, fixed overhead, and implementation cost into retained revenue, loss-adjusted contribution under those assumptions, break-even scale, payback, and a multi-year scenario.
The prefilled values are an illustrative example for exploring the model, not industry benchmarks. Replace them with dated contract terms or reconciled actuals. Selecting referral, PFaaS, or registered PayFac labels the operating model and does not insert different economics.
How to use this calculator
- Select the operating model described by the actual contract and funds flow.
- Enter eligible customers, adoption, transactions per active customer, and average ticket.
- Translate contracted revenue and variable costs into basis points and per-transaction amounts.
- Enter provider minimums, assigned fraud/dispute loss, variable support cost, and monthly fixed overhead.
- Review contribution before fixed costs, operating contribution, scale break-even, payback, and the annual forecast.
Method and formula
Monthly GPV equals active customers × transactions per active customer × average ticket. Gross payment revenue applies the entered take rate; retained payment revenue then applies the contractual share. Partner cost is the larger of variable contract cost and the monthly minimum. Fraud, dispute, support, platform, and compliance costs remain visible before operating contribution is calculated.
Use the payment cost-stack guide to avoid treating merchant price or interchange as platform margin.
Worked example
Suppose 1,000 eligible customers have 10% adoption, each active customer produces 200 monthly payments at a $100 average ticket, and gross payment revenue is 100 bps. With 80% retained revenue, $5 of other revenue per active customer, 50 bps plus $0.02 per transaction in partner cost, 10 bps of loss, $2 support cost per active customer, and $2,000 of fixed monthly overhead, modeled monthly operating contribution is $1,900. The numeric break-even is 52 active customers under these assumptions.
How to interpret the result
Positive gross payment revenue does not establish a profitable program. Read retained net revenue, contribution before fixed costs, and operating contribution as separate levels. A minimum commitment creates a piecewise cost curve, so the calculator solves each valid cost branch directly rather than dividing fixed cost by a misleading headline margin or stopping at an arbitrary scale ceiling.
Compare operating responsibility in Referral vs PFaaS vs PayFac.
Assumptions and limitations
The loaded values are illustrative scenario inputs, not benchmarks or a provider quote. Replace them before relying on the output. This is a planning model for embedded merchant-payment economics, not lending, deposits, insurance, treasury, or investing. Contract allocation, card mix, interchange qualification, network rules, jurisdiction, fraud liability, reserves, prefunding, capital, accounting presentation, tax, and licensing can materially change the result. An unavailable scale break-even or payback is shown as not reachable rather than as zero. When revenue and cost are both zero at every scale, the result is shown as no unique scale because every scale is mathematically break-even.
Inputs, outputs and result meaning
Models an entered-cost embedded-payment contribution scenario with provider minimums, loss allocation, variable support, fixed program cost, piecewise scale break-even, straight-line payback, and an annual forecast.
Inputs
- Operating model
- Labels the contract and responsibility model being evaluated; it does not insert benchmark economics. Choices: Referral or agent, PayFac-as-a-Service, Registered PayFac.
- Eligible customers or merchants
- Customers or merchants that could adopt the embedded payment product. Supported range: 1 to 100,000,000.
- Payment-product adoption rate
- Share of eligible customers expected to become payment-active. Supported range: 0 to 100.
- Monthly transactions per active customer
- Settled transactions per payment-active customer each month. Supported range: 0 to 10,000,000.
- Average settled transaction value
- Average settled payment amount used to calculate gross payment volume. Supported range: 0.01 to 1,000,000,000.
- Gross payment take rate
- Illustrative value loaded for exploration. Replace it with contracted gross payment revenue in basis points of processed volume. Supported range: 0 to 10,000.
- Retained payment revenue share
- Illustrative value loaded for exploration. Replace it with the contractual share of gross payment revenue retained by the modeled platform. Supported range: 0 to 100.
- Other monthly revenue per active customer
- Contracted account, subscription, or service revenue attributable to each payment-active customer. Supported range: 0 to 1,000,000.
- Processor, network, and partner variable cost
- Illustrative value loaded for exploration. Replace it with the weighted variable cost in basis points of GPV from contract or actuals. Supported range: 0 to 10,000.
- Per-transaction variable cost
- Authorization, gateway, settlement, or other variable cost per settled transaction. Supported range: 0 to 1,000,000.
- Monthly provider minimum commitment
- Minimum monthly provider bill applied when it exceeds the modeled variable contract cost. Supported range: 0 to 1,000,000,000.
- Fraud, dispute, and negative-balance loss rate
- Illustrative value loaded for exploration. Replace it with net loss assigned to the modeled platform in basis points of GPV. Supported range: 0 to 10,000.
- Monthly support and operations cost per active customer
- Variable customer support, reconciliation, monitoring, and operations cost per active account. Supported range: 0 to 1,000,000.
- Monthly platform and sponsor fixed fees
- Fixed provider, sponsor, gateway, or platform charges. Supported range: 0 to 1,000,000,000.
- Monthly compliance and program overhead
- Internal risk, compliance, finance, legal, audit, insurance, and engineering overhead assigned to the program. Supported range: 0 to 1,000,000,000.
- Upfront implementation cost
- One-time integration, certification, launch, legal, and implementation cash cost. Supported range: 0 to 1,000,000,000.
- Annual active-customer growth
- Scenario growth rate applied once per forecast year. It is an assumption, not a traffic or sales forecast. Supported range: -99 to 1,000.
- Forecast period
- Number of annual contribution rows to calculate. Choices: 1 year, 2 years, 3 years, 4 years, 5 years.
Outputs
- Monthly operating contribution
- Primary result. Calculated from the visible scenario without intermediate display rounding.
- Payment-active customers
- Calculated from the visible scenario without intermediate display rounding.
- Monthly settled transactions
- Calculated from the visible scenario without intermediate display rounding.
- Monthly gross payment volume
- Calculated from the visible scenario without intermediate display rounding.
- Monthly gross payment revenue
- Calculated from the visible scenario without intermediate display rounding.
- Monthly retained net revenue
- Calculated from the visible scenario without intermediate display rounding.
- Monthly processor and partner cost
- Calculated from the visible scenario without intermediate display rounding.
- Monthly fraud and dispute loss
- Calculated from the visible scenario without intermediate display rounding.
- Monthly support and variable operations cost
- Calculated from the visible scenario without intermediate display rounding.
- Monthly contribution before fixed costs
- Calculated from the visible scenario without intermediate display rounding.
- Annual operating contribution
- Calculated from the visible scenario without intermediate display rounding.
- Contribution margin before fixed costs
- Calculated from the visible scenario without intermediate display rounding.
- Risk-adjusted net yield before fixed costs
- Calculated from the visible scenario without intermediate display rounding.
- Break-even active customers
- Calculated from the visible scenario without intermediate display rounding.
- Break-even eligible customers
- Calculated from the visible scenario without intermediate display rounding.
- Implementation payback period
- Calculated from the visible scenario without intermediate display rounding.
- Forecast cumulative contribution after implementation
- Calculated from the visible scenario without intermediate display rounding.
Formula contract: Active customers = eligible × adoption; GPV = active × transactions × ticket; operating contribution = retained payment and account revenue - max(variable partner cost, minimum) - losses - support - fixed platform and compliance cost.
Frequently asked questions
Is GPV revenue?
No. Gross payment volume is the value processed. Only the contractually earned portion is revenue, and accounting presentation may be gross or net.
What is the difference between take rate and net yield?
Take rate describes revenue relative to GPV. Net yield subtracts modeled variable partner, loss, and support costs before fixed overhead.
Why can more volume fail to improve profit?
Price compression, minimums, variable costs, loss rates, support needs, and unfavorable liability terms can absorb the added revenue.
Does selecting PayFac insert an industry benchmark?
No. The label changes the scenario description only; all economics come from entered terms.
Primary sources
- Visa - Payment Facilitator and Marketplace Risk Guide
- Visa - Payment Facilitator Model
- OCC - Interagency guidance on third-party relationships
- PCI Security Standards Council - PCI DSS
- Visa - Merchant regulations and fees
- Mastercard - Merchant interchange rates
Sources and methodology reviewed 2026-09-25. Results are planning estimates, not a lender quote, tax opinion, investment recommendation, legal opinion, or provider proposal.