Instant-deposit approval engine for sportsbooks that lifts first-deposit conversion without widening fraud losses.

1. Deposit acceptance and risk management are already being described as one of digital finance's most common friction points, creating a named workflow budget instead of a hidden ops tax.
2. AFT is pushing providers from pay-by-bank into the full money-movement lifecycle, so operators need orchestration across funding steps rather than one isolated rail.
3. Account verification, duplicate-card detection, velocity limits, and suspicious-activity monitoring are now embedded directly in funding products, which makes approval logic part of the user-facing deposit flow.
4. Network support from Mastercard and Visa Direct increases the number of real-time funding paths available to operators, which raises the value of an independent control layer above any single processor.
5. A profitable infrastructure vendor that has processed more than $50 billion and still raised a $50 million Series C shows that this category is mature enough to support adjacent workflow software.

Catalyst. Interchecks' AFT launch, its explicit sportsbook buyer narrative, and its built-in controls for duplicate-card and velocity risk show that instant deposits have become a real-time decisioning problem, not just a payments integration project.

The product plugs into AFT processors, pay-by-bank providers, KYC vendors, and internal risk systems to make one decision per funding session. It ingests account-verification results, card fingerprints, player history, velocity, suspicious-activity signals, and rail availability, then decides whether to approve AFT instantly, route to a fallback rail, request another credential, or hold the attempt for review. Teams get a policy console that simulates conversion-versus-loss tradeoffs by state, event window, cohort, or processor. Every decision ships with an audit trail that risk teams and sponsor-bank partners can review without pulling exports from multiple systems. Once embedded on deposits, the same engine can expand into instant payouts and the broader money-movement lifecycle.

What's different. Processors and AFT vendors move money and expose baseline controls, but they are rewarded for rail coverage, not for maximizing funded-account conversion at a regulated operator. This startup wins by becoming the funding decision system that learns which user, card, and session patterns deserve instant funding now, a fallback rail, or a hard block. Its moat comes from cross-rail approval data, operator-specific policy graphs, and loss-outcome feedback that sit above any one network or processor.

Jobs to be done

flowchart LR
  Buyer[VP Payments at sportsbook] --> Pain[Good players fail deposits while risky attempts slip through]
  Pain --> Product[Instant-deposit approval engine]
  Product --> Outcome[More funded accounts with lower fraud loss]

Executive takeaways

• The beachhead is large enough to matter: U.S. legal sports betting reached $149.90B of handle and $13.78B of revenue in 2024, and Q1 2026 alone still processed $43.52B of handle despite softer volumes [1][2].
• Payment friction is economically visible: a PayNearMe/Betting Hero study found 29% of players reported deposit or withdrawal issues, 23% left and never returned, and 60% would switch apps for faster withdrawals [19].
• The category is shifting from “offer another method” to “decide the funding session”: Interchecks’ AFT launch adds duplicate-card detection, velocity limits, suspicious-activity monitoring, and debit funding on the same stack [16][17][18].
• Rails are multiplying faster than operator workflows are simplifying: RTP already reaches 71% of DDAs, FedNow supports instant A2A transfers, and Visa Direct formalizes AFT/OCT flows, which raises the value of a neutral policy layer above any one processor [6][8][9][10].
• Competition is intense but fragmented: pay-by-bank vendors, PSPs, and horizontal fraud platforms all solve parts of the problem, yet none obviously owns cross-rail funded-account conversion for sportsbook buyers by default [20][22][23][24][25][26][27][28].

Market definition

The relevant market is deposit-decision infrastructure: software that sits above card-based AFT, ACH/pay-by-bank, and instant A2A rails to decide whether to approve, route, step up, or block a funding session in regulated online gaming and adjacent instant-funding fintech flows [4][5][6][8][10][13][16][17].

Customer and buyer

The primary buyer is the VP/GM of Payments working with the CRO or fraud lead at a regulated multi-state operator. A good first logo looks like an RSI-style operator juggling multiple states, brands, and betting products while trying to keep cashier UX smooth enough for first-time and event-driven depositors [14][15][19][34].

Buying triggers

• Launching debit AFT or another instant-funding rail creates new routing, duplicate-card, and velocity-policy work immediately. [10][16][17][18]
• Major event windows magnify the cost of failed first deposits, slow reviews, and weak cashier performance because actives, stakes, and first-time deposits spike together. [19][34]
• New state launches and product-level controls such as deposit limits force teams to revisit cashier rules, auditability, and customer communications. [14][29][30]

Willingness to pay

If a tool can recover even a few points of funded-player conversion or cut manual-review and support load, it has budget: payment issues already create support tickets, churn, and lower lifetime value, while adjacent risk tools are billed per request and sit directly inside revenue capture. [19][24][33]

Category dynamics

Growth signal 24.8% YoY U.S. sports-betting revenue growth in 2024; Same Day ACH volume +16.7% in 2025

Validation signals

• Interchecks raised $50M while launching AFT specifically for sportsbooks, fintechs, and financial institutions, validating buyer attention in this workflow.
• A Betting Hero survey found payment friction is common and sticky enough to cause churn, making conversion-oriented tooling budget-worthy.
• Trustly argues it can outperform cards on approval rate and cost while embedding identity checks, proving operators will rework cashier flows for better economics.
• Gamers treat instant good-funds access as a priority, yet PYMNTS/Ingo found only 49% are offered the instant winnings options they want.

Regulatory & technical constraints

• Visa Direct AFT flows require network-specific onboarding and data elements such as acquiring BIN and business application identifiers, so card-rail decisioning is not plug-and-play.
• Nacha does not view WEB-debit fraud controls without account validation as sufficient, so ACH fallback logic must include validation rather than only score-based fraud filtering.
• FinCEN has treated online real-time deposit, settlement, and payment intermediaries as money transmitters in relevant fact patterns, which matters if the product expands beyond pure decisioning.
• State product requirements such as deposit limits or licensing reviews can change cashier behavior and deployment timing market by market.

Competition is dense but fragmented. Interchecks is moving down-stack from pay-by-bank into debit AFT with native controls [16][17][18]; Trustly proves operators will change cashier flows for better approval and lower cost on bank rails [20][21]; Nuvei and Paysafe sell broader PSP/payment-method breadth into gaming [22][23]; and horizontal risk vendors like Plaid, Stripe, SEON, Sardine, and Sift already monetize adjacent scoring, review, and AML workloads [24][25][26][27][28]. The gap is an operator-controlled layer that independently optimizes approve/route/step-up decisions across all of them.

Why incumbents do not win by default

• AFT processors. Processors win the integration and rail-coverage layer, but their economics favor moving volume over their own stack rather than staying neutral across competitor rails and fraud vendors.
• Pay-by-bank providers. Pay-by-bank specialists can improve approval rates and lower cost, but they mainly optimize bank funding rather than universal decisioning across debit AFT, cards, ACH, and manual-review paths.
• Broad PSPs. PSPs bring breadth of methods and merchant tooling, yet sportsbook deposit optimization is one workflow among many, making an external control plane attractive when buyers already mix providers.
• Horizontal fraud vendors. Risk platforms deliver scoring, review, AML, and transaction monitoring, but they do not automatically own sportsbook-specific routing, event-window policy tuning, or cashier conversion KPIs.

Sportsbook Deposit Approval Engine should start as a provider-neutral funding-session control plane for U.S. multi-state sportsbooks that are adding debit AFT on top of existing ACH or pay-by-bank deposits before the 2026 NFL season. The first buyer is a VP or GM of Payments working with the fraud lead because failed first deposits and manual reviews directly depress funded-player conversion during event windows while duplicate-card and suspicious-activity risk still sits with the operator. The initial product should not try to replace processors; it should replay 90 days of deposit attempts in shadow mode, recommend approve, route, step-up, or block decisions, and generate audit-ready evidence by state, cohort, and rail. If shadow mode proves lift, the company can move into limited live control for one AFT processor and one bank-funding fallback rail, which is a lower-friction sequence than selling a full payment-stack replacement. Go-to-market is coherent because the trigger is a new AFT rollout, state launch, or pre-event deposit-failure spike, distribution starts with direct founder-led sales into roughly twenty beachhead operators plus processor referrals, and pricing combines paid implementation with annual software and usage tied to funding sessions under policy coverage. Competition is real across Interchecks, Trustly, Nuvei, Paysafe, and Sardine, but those vendors either own a rail or sell horizontal risk rather than neutral cross-rail conversion optimization. The researched market is not huge—about $32.0M SAM and $8.4M year-3 SOM for the beachhead—so the company only works as a venture case if sportsbook proof expands into adjacent regulated-fintech funding flows. The main evidence gap is public proof that a third-party engine can both influence AFT decisions and lift funded-player conversion without sponsor-bank resistance, so the first 90 days must validate data access, audit requirements, and measurable ROI.

Problem

• High-intent deposit sessions are split across AFT processors, pay-by-bank providers, fraud tools, and manual rules, so good players fail funding at the moment sportsbooks most need them to convert.
• Risk teams cannot tune duplicate-card, velocity, and suspicious-activity policies fast enough by state, event window, or player cohort, which forces a tradeoff between funded-player growth and fraud loss.
• When sponsor banks, compliance teams, or regulators ask why a deposit was approved or blocked, operators must reconstruct the answer from multiple dashboards instead of one auditable decision trail.

Solution

• Start with a shadow-mode engine that ingests AFT, pay-by-bank, KYC, fraud, and internal history signals for one deposit funnel and recommends approve, route, step-up, or block decisions in milliseconds.
• Give payments and risk teams a policy console to simulate funded-player conversion versus loss by state, event window, processor, and cohort before rules go live.
• Convert proven policies into limited live control with case management and immutable audit logs so the same system explains every decision to sponsor-bank and compliance stakeholders.

Why we win

• The wedge sits above processors and rails, so the product can optimize across AFT, ACH or pay-by-bank, and manual-review paths instead of being biased toward one provider's volume.
• Each deployment compounds a cross-rail dataset of approvals, declines, returns, duplicate-card hits, and fraud outcomes that no single processor sees inside one operator.
• The first buying trigger is immediate and measurable—AFT rollout or NFL-season deposit pressure—so proof can be judged on funded-player conversion, false declines, manual-review share, and loss rate rather than vague platform adoption.

Milestones

flowchart LR
  Wedge[Sportsbook deposit wedge] --> MVP[Shadow mode MVP]
  MVP --> Proof[Conversion and loss proof]
  Proof --> Expansion[Cross rail expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least five of the first ten target operators must confirm that deposit approval is a top-three cashier pain with budget attached.
• At least three design partners must provide rail, fraud, and outcome data detailed enough to replay 90 days of funding sessions.
• Shadow-mode pilots must show at least a 2-point funded-player conversion lift or at least a 25% manual-review reduction without higher loss.
• Processors and sponsor banks must permit a third-party layer to recommend or enforce approval and routing logic in production.
• At least half of paid pilots must convert to annual contracts before incumbents bundle equivalent cross-rail decisioning.

Open diligence questions

• Which title owns budget when the KPI is funded-player conversion but the downside is sponsor-bank and fraud risk?
• How many deposit attempts per day and per event window does the target operator process by rail, and how does that change the ROI ceiling?
• What data fields and approval hooks will Interchecks, Trustly, or the incumbent processor expose to a third-party control plane?
• How does the operator currently measure false declines, duplicate-card abuse, and manual-review latency at the funding-session level?
• What minimum lift would justify replacing processor-native rules before the next NFL season?

Model sanity

• Revenue engine. Base-case revenue is driven less by raw logo count than by four early sportsbook logos graduating from $35K land contracts into $75K-$110K multi-rail expansion contracts by Y3.
• Must go right. The first three paid pilots must convert and at least the first two live logos must expand within 12 months, or the model misses both the Y2 milestone and the cash-efficient path shown in the base scenario.
• Model breaks if. A one-quarter sales-cycle slip or one mature-logo churn event removes roughly $500K-$660K of Y3 revenue and can erase $460K-$640K of ending cash, which is why the downside case turns cash-negative.
• Next-round proof. The next financing is justified once five sportsbook production logos, two-rail live approval proof, and one adjacent-fintech account are in hand, because that validates the wedge before the company tries to close the gap to the researched $8.4M SOM.

Scenarios

Sensitivity

flowchart LR
  Leads[Founder outbound and processor referrals] --> Pilots[Paid shadow-mode pilots]
  Pilots --> Production[Production logos]
  Production --> Expansion[Second rail or brand expansion]
  Expansion --> Revenue[Revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash]

Flags: Six logos still make the base case highly concentrated: losing one mature sportsbook account would remove well over 15% of exit ARR. · Base-case exit ARR reaches about $6.6M by M36, still below the researched $8.4M year-3 SOM, so the model requires another expansion step or a seventh logo after this horizon. · Sponsor-bank or processor resistance remains the single gating risk; if live influence slips beyond the first five logos, the downside case shows the current pre-seed ask is not enough. · Y3 profitability depends on expansion inside early logos, not just new bookings; if second-rail or second-brand adoption stalls, the efficiency metrics reverse quickly.

• Processor bundling. AFT processors or PSPs may add lightweight routing and analytics, compressing the perceived need for a separate layer. Mitigation: Stay processor-agnostic, optimize across multiple rails, and win on cross-provider conversion and loss insights that no single processor can see.
• Customer concentration. The initial sportsbook market is finite and seasonal, which could limit early logo count if expansion is slow. Mitigation: Use sportsbooks as the proving ground, then sell the same approval engine to neobanks, wallets, and brokerages with similar funding workflows.
• ROI attribution gaps. Many operators do not have clean baselines for false declines versus fraud loss, making the buying case harder to quantify. Mitigation: Launch in shadow mode with historical replay, holdout tests, and operator-specific benchmarks tied to funded-account conversion and net loss.