Problems › Should We Raise Our Prices? › Fintech
The question is never whether to raise the take rate in general. It is which merchant segments, on which flows, by how much, and what volume and charge-off rate you expect to lose. What makes this harder for fintech companies is structural: lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple. Any credible answer therefore has to hold blended take rate and charge-off rate in the same view, which is exactly where most internal analysis stops because the two live in different systems.
The question is never whether to raise the take rate in general. It is which merchant segments, on which flows, by how much, and what volume and charge-off rate you expect to lose. What makes this harder for fintech companies is structural: lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple. Any credible answer therefore has to hold blended take rate and charge-off rate in the same view, which is exactly where most internal analysis stops because the two live in different systems.
The take rate is the fastest lever on contribution margin in a fintech business. It requires no new TPV, no additional merchants, and no change to the warehouse facility, and the effect appears in the next billing cycle. Operators still avoid touching it, which is why blended take rates sit below what the contribution margin after charge-offs would support.
A useful take-rate review does not produce one number. It produces a segmentation by merchant: which cohorts generate TPV whose contribution margin exceeds the cost of their CAC by channel, which cohorts already sit at the point where further rate increases would trigger substitution or higher charge-off rates, and where manual overrides show pricing being set deal-by-deal rather than by policy.
Any effective change in take rate will cause some merchants to leave or reduce TPV. If a rate adjustment produces no loss of volume or change in charge-off rate, the adjustment was too small relative to the contribution margin available.
These three together are the signature. One on its own usually points somewhere else.
✓ Almost every merchant signs at the first quoted blended take rate with no negotiation on terms.
✓ Take-rate exceptions appear frequently and vary by sales rep rather than by merchant economics or charge-off history.
✓ The published take rate schedule has stayed fixed while CAC by channel and charge-off rates have moved.
The move that usually makes it worse. Applying the same take-rate increase to every merchant and every flow, which reduces volume from merchants who were already marginal on contribution margin while leaving higher-margin merchants underpriced.
It is for you if you run or finance a fintech and almost every deal closes, and closes quickly. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on a fintech. It is a sample profile rather than a customer, and it is unedited engine output — this is the format you get, on your own numbers.
The subject is Verrano Pay, a sample company profile used for testing rather than a customer — $84M net revenue, 28,000 merchants, $9.4B of payment volume.
Excerpt from a real Percision run · Pricing Strategy · sample company profile
The move. Scale lending book from $110M to $260M advances using existing distribution and data assets while maintaining charge-off rate below 9.0% covenant.
The leak it closes. Reduces 26% partner rev-share leakage by increasing merchant stickiness through lending relationship
The assumption it rests on. Platform partners maintain 180-day termination clauses without exercising exit — the engine put the probability at 0.7.
| Investment required | $0 incremental equity |
| Expected return | 4.5x |
| Revenue, year 1 | $24.1M lending revenue (30% growth) |
| Revenue, year 2 | $31.3M lending revenue (30% growth) |
| Revenue, year 3 | $40.7M lending revenue (30% growth) |
| Exit criteria | Terminate if charge-off rate exceeds 8.7% for two consecutive quarters OR if any platform partner terminates contract |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Pricing & Revenue Optimization, one of 29 engagements the platform runs. For fintech companies it works through blended take rate, charge-off rate, contribution margin and CAC by channel, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. Read a complete report here if you would rather see the depth first.
There is no general answer, and the useful analysis is per segment. What can be said is that the loss you fear is usually concentrated in a group whose economics you would improve by losing them.
New first is safer and slower; existing is where the money is. A defensible sequence is to move new-customer pricing, watch win rate for a quarter, then bring existing customers up at renewal with notice.
Then you are selling against them on something other than price, or you are not — and that is the real question. Competing on price without the cost structure to support it is the most reliable way to lose money at increasing volume.
Materially, yes. Lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are blended take rate, charge-off rate, contribution margin, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on blended take rate and charge-off rate. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית