Counterparty & financial intelligence · 26 October 2026

Fin.com counterparty intelligence

A vertically integrated global money-movement thesis: stablecoin settlement, regulated local payment networks, acquired operators, enterprise distribution and, ultimately, an owned banking balance sheet. These pages hold what the deck claims, what the analyst report interprets, and what has been checked against the primary document — kept apart on purpose.

26 October 2026Primary: Fin.com investor deck, 21 pagesWorking analysis

Initial institutional stance

Strategically compelling; financially and operationally unverified. The gating issues are audited revenue, customer-level economics, verified partnerships, regulated-entity ownership and realistic forecast conversion.

Where every figure comes from

Deck assertionAnalyst interpretationChecked against the deckFetched 26 Oct 2026Infiniti analysis

Every figure on these pages traces to one of these five. Nothing is estimated.

At a glance

Four figures that frame everything

July 2026 ARR run rate

$2.1M

Management historical — the last reported month

December 2026 projected

$48.17M

Fin.com's projection; the basis for its $1B target

Countries claimed live

40+

Deck and website counts differ

Target valuation

$1B

Fin.com's target; not independently established

01 · Revenue

Seven months reported, five months projected

Checked against the deck Deck p16. The (P) break after July is the single most important fact on this page.

Source: Fin.com investor deck, p16. Solid bars are management historical figures; dashed outlines are the deck’s own (P) projections.

January–July are management historical figures. August–December are Fin.com’s own projections, drawn as dashed outlines so the picture cannot be read as twelve months of reported revenue.

Fin.com MRR and ARR run rate by month, 2026
Month	MRR	ARR run rate	Basis
Jan	$13.7K	$164K	Historical
Feb	$20.1K	$241K	Historical
Mar	$25.9K	$311K	Historical
Apr	$28.4K	$341K	Historical
May	$69.5K	$834K	Historical
Jun	$70.0K	$843K	Historical
Jul	$175K	$2.1M	Historical
Aug	$375K	$4.5M	Projected
Sep	$1.08M	$13.0M	Projected
Oct	$1.83M	$21.9M	Projected
Nov	$2.77M	$33.2M	Projected
Dec	$4.01M	$48.17M	Projected

What the forecast requires

Monthly revenue has to grow about 22.9× in five months — roughly 87% compounded every month — to reach the December figure Fin.com’s $1B target is anchored on.

Coverage counts disagree

The deck claims 40+ countries (p8, p15) and 70+ currencies (p11). Fin’s own funding announcement, two months later, is reported as 40+ currencies and 30+ countries — the two figures swapped and the country count a third lower. Fetched 26 Oct 2026

Reading the table

July’s $175K monthly implies the $2.1M run rate; December’s $4.01M monthly implies $48.17M. Annualised payment revenue is not contracted recurring revenue: gross versus net recognition, pass-through flows, fees and transaction concentration all have to be resolved before either number means what it appears to mean.

02 · Valuation

What $1 billion implies, on three bases

Analyst interpretation Multiples computed from the deck’s own revenue figures. The $1B is Fin.com’s target, not an established value.

Implied multiples on three revenue bases
Revenue basis	Annualised	Implied valuation / revenue
July reported	$2.1M	476×
September projected	$13.0M	77×
December projected	$48.17M	20.8×

Arithmetic flag

The deck prints “23× for $1B” against its December run rate (p17). $1,000M ÷ $48.17M is 20.8×. The two do not reconcile — a small gap, but it sits on the slide the raise is anchored to. Checked against the deck

03 / 04 · Counterparties

Thirty counterparties, one evidence standard

Analyst interpretation Grouping is ours A logo does not prove a direct paying contract. The matrix and all thirty dossiers have their own pages.

Composition of the counterparty list
Group	Count
Customer or endpoint	13
Acquired operator	3
Infrastructure reference	3
Investor or adviser	7
Banking partner	3
Vendor	1

What the matrix is made of

13 of the 30 rows are customers or endpoints. Seven are investors or advisers, three are banking partners named in a “40+” list, three are acquired operators, three are infrastructure references whose contractual scope the report itself calls unclear, and one is a compliance vendor. A reader who counts thirty partnerships is counting the cap table and the vendor list alongside the customers.

Open the full matrix and all 30 dossiers →

05 · Strategic concentration

Where the value is said to sit

Analyst interpretation Qualitative scores from the research report. Not financial ratings, and not confirmed revenue contribution.

Mesh

5/5

Banking network

5/5

Acquired regional PSPs

5/5

PayPal

4/5

Kalshi

4/5

Polymarket

4/5

Western Union

4/5

Crypto exchanges

3/5

Specialized gaming merchants

2/5

06 · Licences

Permissions by jurisdiction

Checked against the deck Re-extracted from deck p12 with the table layout preserved; p11 cross-checked.

Licences by jurisdiction
Jurisdiction	Licence	Typical time	Status
United States	Bank sponsorship	6–12 mo	Live
Canada	MSB	3–6 mo	Live
UAE	PSP Category 3	12–18 mo	Live
Pakistan	PSP	12–24 mo	Live
India	FIU-IND VASP	6–9 mo	Live
India	PA-CB Inward	12–18 mo	Live
India	PA-CB Outward	12–18 mo	In process
Lithuania	VASP	—	Shown on p11, absent from the p12 status table

Count does not reconcile either way

The masterplan slide (p18) claims “Seven licenses live across five jurisdictions, an eighth in process.” The p12 table lists six live across exactly five jurisdictions — United States, Canada, UAE, Pakistan and India — plus India PA-CB Outward in process. Counting the Lithuania VASP from p11 reaches seven live, but takes the jurisdiction count to six. The table supports six live across five, or seven live across six — never seven across five. Lithuania moves the discrepancy rather than resolving it. Checked against the deck

Same licence, two names

UAE is “PSP Category 3” on p12 and “Payment Services Provider (Category 3D)” on p11. A registration, a licence, a sponsorship and a charter are not interchangeable, and neither are categories — verify the exact permission against the exact legal entity.

07 · Risk

Two registers, kept apart

The research report's ranking, and separately our own. Neither is an audit, and neither is investment advice.

Principal underwriting risks

Analyst interpretationFour Critical, four High

The research report's risk register
#	Risk	Assessment	Priority
01	Forecast execution	Extraordinary projected growth with limited validated conversion	Critical
02	Contract validation	Logos may represent indirect or noncommercial relationships	Critical
03	Regulatory control	License ownership and authorized activities require entity-level verification	Critical
04	Gross/net revenue	Pass-through processing flows may distort reported revenue	Critical
05	Bank dependencies	Partner termination can disrupt corridors	High
06	M&A integration	Minority rights and local control complicate consolidation	High
07	Liquidity/FX	Prefunding and spread volatility may erode margins	High
08	Bank acquisition	Regulatory and capital uncertainty	High

What we would underwrite against

Infiniti analysisFrom our own 20 October partnership brief

Infiniti's own risk register
Risk	Severity	Why
Revenue is mostly forecast	Critical	Five of the twelve months that make the headline figure are the deck’s own projections, and the valuation is anchored on the last of them.
Licence count does not reconcile	Critical	The masterplan slide and the licence table disagree on how many permissions are live and in how many jurisdictions.
Operating entities are 51% owned	High	Recourse, data handling and continuity sit with local companies whose founders keep 49% and run them.
Licences and banking are rented	High	Fin’s own words for today. The owned balance sheet is a phase funded by a raise that has not closed.
Named relationships are unverified	High	A logo on a platform page is not a direct paying contract. Every named counterparty needs its contracting entity and live scope confirmed.
Concentration if we route through them	Medium–high	A single young PSP group holding our international collections is a revenue outage waiting to happen without a named fallback acquirer.

08 · Diligence

Investment committee requirements

Analyst interpretation The research report’s own list, in its order.

0 / 8 complete — kept in this browser only

Signed customer contracts; identify direct customers, intermediaries and merely supported endpoints.
Monthly revenue reconciled to general ledger and cash settlement, with gross/net revenue accounting memo.
TPV, net take rate, gross profit, refunds, losses and customer concentration by corridor and product.
Legal entity chart, ownership records, acquisition agreements, regulatory change-of-control consents.
Regulator-verifiable license register, bank sponsorship and permitted-activity legal opinions.
Liquidity, counterparty exposure, reconciliation exceptions and failed payment data.
Forecast bridge from contracted customers to transaction volumes, margin and cash needs.
Bank target identification, capital plan, supervisory pathway and stress testing.

09 · Infiniti’s read

What the research report scores but does not separate

Infiniti analysis From our own 20 October partnership brief.

Kalshi · eligibility, not plumbing

Fin’s problem statement opens with a prediction market: “A prediction market in New York cannot take a deposit from a customer in Lagos.” For Kalshi that sentence describes an eligibility constraint at a CFTC-regulated exchange, not a payments one. Whatever rail delivers the dollars, the account must still be one the exchange will open and the depositor must still be the member.

The research report scores Kalshi 4/5 strategic without drawing that distinction. A better rail shortens the queue; it does not change the door policy. Any funding-leg design has to be read off the exchange’s own deposit and eligibility terms first.

Polymarket · where the sentence is literally true

Polymarket is USDC-native, so a stablecoin partner genuinely changes what is possible there in a way it does not for a US-regulated exchange. The dossier’s named function — named USD SWIFT payouts — is the off-ramp leg, not the funding leg, and the two should not be scored as one relationship.

Polymarket’s own eligibility and KYC rules still apply and are not addressed in either source document.

Method

Sources, and what the tags mean

Primary: Fin.com’s 21-page investor deck. Revenue (p16), valuation (p17), licences (p11–12) and the masterplan (p18) were re-extracted from that PDF with the table layout preserved, which is what “checked against the deck” means: the figure matches the primary document, not that the underlying business fact is independently confirmed.

Secondary: an independent institutional research report dated 26 October 2026, prepared in a Goldman Sachs-style format — not affiliated with Goldman Sachs, not commissioned by us and not an audit. The partnership matrix, the thirty dossiers, the strategic scores, the risk register and the diligence checklist are its work, reproduced as interpretation.

Infiniti analysis is our own, and is labelled as ours wherever it appears. Where a secondary figure disagrees with the deck, we have kept the deck and flagged the disagreement rather than averaging them.

No partner contract, bank licence or financial statement has been independently inspected. Nothing on these pages is investment advice, a fairness opinion or an audit. Figures that are not in the two source documents are not on these pages.

Two dossier fields are template text

The research report repeats two of its five dossier fields verbatim on every one of the thirty counterparties. Neither distinguishes one row from another, so they are stated once here rather than thirty times:

Potential value to Fin — “Supports one or more of enterprise distribution, regulated access, treasury/liquidity, settlement connectivity or ecosystem credibility; contribution to revenue has not been established.”

Evidence status — “Presented by management or public-facing material; direct contracting, production status, financial contribution and legal responsibility require confirmation.”