FX budget autopilot for Nigerian online importers to auto-execute optimal USD conversions for supplier payments at CLOB-sourced rates.

1. Stabyl's $2.7M CLOB infrastructure raise in June 2026 creates the first programmatic, interbank-grade FX rate feed accessible to Nigerian merchant platforms outside the central bank window.
2. Konga's dual role as Stabyl lead investor and first naira settlement partner via KongaPay opens a direct distribution channel to Konga's merchant base for FX execution tools.
3. Stablecoin-backed settlement eliminates the 24–48 hour correspondent banking lag, making auto-execution feasible for time-sensitive supplier payment deadlines.
4. Nigeria's 2023 naira float created permanent FX volatility for importers, making rate monitoring and timing tools a commercial necessity rather than a convenience.

Catalyst. Stabyl's $2.7M raise and KongaPay integration in June 2026 create the first programmatic CLOB rate feed accessible to Nigerian merchant platforms, making auto-execution tools viable for the first time.

An FX budget autopilot that connects to a Nigerian importer's existing Konga merchant account and supplier invoicing workflow, surfaces a live CLOB rate feed versus BDC and parallel market benchmarks, and auto-executes USD conversions when the rate hits a merchant-set target or a supplier payment deadline is approaching. The product tracks open import orders and their USD exposure, alerts merchants to rate windows, and generates tax-ready FX transaction reports. A merchant spends two minutes setting their rate target and payment timeline; the autopilot handles execution at sub-1% spread versus the 5-15% typically paid to BDC operators.

What's different. Unlike generic multi-currency wallets that offer flat FX rates without execution intelligence, this product connects directly to CLOB-sourced liquidity to deliver transparent, real-time rate benchmarking and algorithmic execution timing tailored to import payment workflows. The Konga distribution partnership provides pre-existing merchant trust and a ready-made pipeline of high-volume USD buyers, while the CLOB integration creates a cost advantage that no BDC operator or informal dealer can replicate without equivalent infrastructure access.

Jobs to be done

flowchart LR
  Merchant[Konga Merchant] --> Dashboard[FX Budget Dashboard]
  Dashboard --> RateFeed[CLOB Rate Feed]
  RateFeed --> Stabyl[Stabyl Liquidity Layer]
  Dashboard --> Autopilot[Rate Autopilot Engine]
  Autopilot --> Execute[USD Execution via KongaPay]
  Execute --> Supplier[Chinese / UAE Supplier]
  Dashboard --> Reports[FX Cost Reports]

Executive takeaways

• The pain is commercially real: Nigeria’s FX shortage has limited ordinary international card usage, while importers and small firms increasingly turn to stablecoins and alternative rails to hedge naira risk and pay overseas suppliers faster [1][154][163].
• Infrastructure readiness has improved enough to support an application-layer wedge: PAPSS, Onafriq, Yellow Card, dLocal, Nium/Circle, and Stabyl all show live or launching mechanisms for local-currency settlement, stablecoin-funded payouts, or programmable FX liquidity in Africa [24][31][39][95][104][152].
• The best initial wedge is not “another cross-border wallet” but execution intelligence for recurring importer payables—benchmarking rates, timing purchases, and turning supplier deadlines into automated buy decisions on top of partner rails [49][67][79][100].
• Competition is meaningful but mostly horizontal: Verto, Fincra, Yellow Card, Nium, and dLocal/AZA sell treasury or payment primitives, while Konga/Jumia control merchant attention; few package a Nigeria-first FX autopilot embedded in importer workflows [11][17][53][67][95][99].
• The main risk is regulatory and distribution execution, not whether the pain exists: stablecoins now sit visibly inside Nigeria’s payments-policy conversation, but winning still requires a trusted licensed partner and a merchant-acquisition surface [12][43][159].

Market definition

The relevant market is software for Nigerian SME importers that sits above banks, BDCs, and emerging stablecoin/local-rail providers: it monitors rates, plans USD exposure, and executes supplier-payment conversions through licensed payment or treasury partners. It is narrower than generic cross-border payments and broader than a wallet; the wedge is execution timing and workflow control for recurring payables rather than raw money movement itself [1][2][24][39][49][79].

Customer and buyer

The practical ICP is a Nigeria-based online merchant or distributor importing consumer goods from China or the UAE with recurring USD invoices and weak in-house treasury capacity. The day-to-day user is the founder, CFO, or finance manager; the most efficient channel buyer could also be a merchant-finance or platform lead at KongaPay or a Jumia-like seller ecosystem that already bundles payments, logistics, and visibility tools for merchants [11][12][17][20].

Buying triggers

• A fresh naira slide, BDC spread spike, or continued inability to use standard local debit cards for international payments makes budget misses immediately painful. [1][2][163][164]
• A supplier invoice deadline or inbound inventory shipment forces the merchant to source USD quickly and exposes the cost of manual dealer calls and opaque quote comparison. [79][67][154]
• A merchant platform or PSP introduces a business account, treasury rail, or settlement partner that makes automated execution operationally feasible without building the rails in-house. [12][20][39][104][152]

Willingness to pay

Willingness to pay is credible because the product competes against a recurring cost center, not a discretionary analytics dashboard. World Bank pricing shows Sub-Saharan Africa remains the most expensive remittance-receiving region at 8.78% average cost, Yellow Card documents 2–3% versus 8–12% traditional corridor economics, and incumbent vendors themselves sell on hidden-fee reduction, quote quality, or spread control rather than on seat licenses. [7][49][58][67][100]

Category dynamics

Growth signal 52% y/y growth in Sub-Saharan Africa crypto market value received

Validation signals

• Stabyl’s $2.7M pre-seed and Konga-led first settlement partnership validate that programmable Africa FX sourcing is moving out of theory and into deployment.
• Visa’s partnership with Yellow Card signals that major global payment networks see African stablecoin settlement as strategic, not experimental.
• Nium/Circle and dLocal stablecoin launches show incumbents are productizing stablecoin-to-local payouts and treasury orchestration now.
• Jumia and Konga already expose merchant-facing distribution surfaces that could carry an FX-autopilot workflow without teaching merchants a new operating system.

Regulatory & technical constraints

• Settlement likely needs to route through licensed PSP or treasury partners, with AML/KYC and rule-aware audit trails treated as core product features.
• Execution quality depends on API-accessible rate sources and wallet / payout primitives that can move from indicative pricing to confirmed settlement.
• Any autopilot must reconcile invoices, quote locks, payout states, and local-currency receipt confirmation across multiple rails.

Competition is strategic rather than category-pure. Verto and AZA frame the market as African FX and treasury infrastructure; Fincra and Onafriq emphasize payment collection, payouts, and settlement coverage; Yellow Card, Circle, and Nium push stablecoin-enabled treasury and payout rails; dLocal sells one-API emerging-market orchestration; and Konga/Jumia remain powerful distribution substitutes that can absorb adjacent treasury features. The proposed startup only wins if it stays closer to the importer’s decision moment than these horizontal providers do [31][39][53][67][95][99].

Why incumbents do not win by default

• Marketplace / PSP platforms. KongaPay or Jumia-like platforms control merchant attention and could distribute the product, but they do not yet market a specialized FX autopilot that benchmarks BDC versus programmable liquidity and buys dollars against supplier deadlines.
• Stablecoin infrastructure providers. Yellow Card, Circle, Nium, and dLocal expose the rails, wallets, and compliance stack, but they sell infrastructure breadth and settlement capability rather than a merchant-specific budget discipline layer.
• Africa-first FX / payment vendors. Verto, AZA, and Fincra already address FX movement and collections, yet their public positioning remains broader B2B treasury/payments rather than a verticalized importer autopilot embedded inside a marketplace workflow.
• Global payout platforms. Nium, dLocal, Wise, and Payoneer validate global payout demand, but their default buyer is the enterprise platform or globally distributed business rather than a Nigerian merchant deciding when to buy dollars for stock replenishment.
• In-house spreadsheets and dealer calls. The current substitute is still manual treasury—dealer WhatsApps, bank queues, spreadsheet tracking, and ad hoc stablecoin buys—which remains acceptable for one-off transfers but breaks once merchants have recurring invoices and volatile rates.

Stabyl's June 2026 raise and KongaPay settlement partnership suggest that programmatic FX rails for Nigerian merchants are becoming available, but the researched gap is still execution intelligence at the moment a merchant must fund a supplier invoice. The first customer should be a Konga marketplace importer of electronics or fashion with $100k-$500k in annual USD payables and no dedicated treasury team. The initial product should not try to become a new wallet, bank, or FX inventory provider; it should benchmark executable or partner-sourced rates against BDC pricing, recommend when to buy, and route approved execution through a licensed partner. This beachhead works because pain is recurring, the buying trigger is sharp, and partner distribution is likely necessary to make a low-ACV merchant model viable. The deliberate tradeoff is to start with alert-plus-approval mode and invoice-linked reporting, not autonomous multi-corridor trading, because partner permission, merchant trust, and auditability are the real gating risks. If pilots show more than 2% net savings versus BDC sourcing, repeat monthly usage after the first supplier payment, and reliable partner settlement evidence, the company can expand into distributors, more merchant platforms, and later treasury products such as exposure forecasting and partner-issued forwards. The main reasons to doubt are regulatory ambiguity, dependency on third-party liquidity and settlement rails, and the still-unverified size of the exact merchant cohort with disciplined recurring payables. Because those gaps are material, the first 18 months should buy partner access, compliance-aware workflow software, and merchant cohort proof rather than broad geographic expansion.

Problem

• Nigerian importers with recurring supplier invoices often pay 5–15% above benchmark USD rates because they source FX through BDC operators, bank queues, or informal dealer networks at the last minute.
• FX exposure lives in spreadsheets and chat threads, so a naira move or supplier deadline turns into budget misses, settlement delays, and weak audit trails.

Solution

• Embed an invoice-linked FX dashboard inside a trusted merchant workflow that shows live benchmarked or executable rates versus BDC spreads, tracks open payables, and lets merchants set target rates or deadline rules.
• Route approved USD purchases and supplier payments through licensed partners such as KongaPay plus multi-source liquidity providers, then return reconciliation and tax-ready reports.

Why we win

• The product sits at the merchant's decision moment rather than only at the money-movement layer, so it can turn partner rails into measurable savings and fewer missed supplier payments.
• Partner distribution through Konga-like merchant ecosystems lowers trust and onboarding friction in a segment that would be expensive to win with pure direct sales.
• Benchmark-versus-execution history, invoice-linked behavior data, and compliance-grade audit trails can compound into a routing and recommendation moat that horizontal FX vendors do not naturally collect.

Milestones

flowchart LR
  Wedge[Konga merchant wedge] --> MVP[Approval-mode invoice and FX MVP]
  MVP --> Proof[Net savings, repeat usage, settlement evidence]
  Proof --> Expansion[More merchants, more partners, broader treasury products]

Founding team

Experiment roadmap

Risk assessment

What must be true

• KongaPay or a similar licensed PSP will distribute or embed the workflow instead of forcing the startup into pure cold-start acquisition.
• Net realized savings versus BDC or manual sourcing stay above 2% after partner fees on typical $10k-$100k tickets.
• A meaningful cohort of merchants has recurring USD invoices and enough process discipline to set target-rate or deadline rules.
• Merchants trust approval-mode recommendations quickly enough to repeat the workflow monthly without high-touch human dealing.
• The same product can expand into distributors, more PSPs, and partner-issued treasury products before horizontal incumbents neutralize the wedge.

Open diligence questions

• What commercial and technical rights will KongaPay or another PSP actually grant a third-party orchestration layer?
• What are the true net spreads versus BDC, bank desk, and direct stablecoin routes across common ticket sizes?
• How many reachable Konga or Jumia sellers have more than $50k in recurring annual USD payables?
• What revenue share, settlement liability, and compliance burden do partner rails impose?
• Which merchant behaviors best predict repeat usage after the first successful supplier payment?

Model sanity

• Revenue engine. Base case revenue is driven by 900 merchants executing recurring USD supplier payments at a blended $163/month ARPU (0.5% execution fee on avg $155k annual payables plus $99 subscription), sourced almost entirely through a KongaPay-embedded partner channel that holds steady-state CAC to $1.8k and 16-month payback.
• Must go right. KongaPay or a comparable licensed PSP must grant embedded approval-mode execution orchestration by M3; without partner distribution the CAC and onboarding timeline inflate to levels that exhaust the $3M pre-seed before the 30-merchant repeat-usage proof needed to close the seed round.
• Model breaks if. Steady-state monthly churn exceeds 3.5% or partner execution fees compress gross margin below 55%, as either condition makes LTV/CAC fall below 2.0x and destroys the unit economics argument for a $6M seed round at Q2Y2.
• Next-round proof. A $6M seed round at Q2Y2 is justified by the sensitivity table showing that at 100+ active merchants with greater than 2% median net savings, 70%+ 90-day repeat rate, and M18 monthly burn below $120k, all six base-case assumptions remain intact with at least $1.6M cash cushion before the raise.

Scenarios

Sensitivity

flowchart LR
  Partner[PSP Partner\nKongaPay] -->|refers merchants| Leads[Merchant Leads]
  Leads -->|30% pilot convert| Pilots[Pilot Merchants]
  Pilots -->|60% first payment| Active[Active Merchants]
  Active --> Sub[Subscription\n$99 per month]
  Active --> Fee[Execution Fee\n0.5% of FX volume]
  Sub --> Revenue[Total Revenue]
  Fee --> Revenue
  Revenue -->|30% COGS\npartner and rail fees| COGS[Cost of Revenue]
  Revenue -->|70% gross margin| GrossProfit[Gross Profit]
  GrossProfit --> Cash[Operating Cash]
  Active -->|2% per month churn| Lost[Churned Merchants]

Flags: Single PSP dependency: if KongaPay declines embedded orchestration the entire customer ramp collapses and the $1.8M SOM run-rate is unreachable without 24+ months of additional direct-only CAC spend at 2x cost · $6M seed raise at Q2Y2 is a modeled assumption not a committed term sheet; if seed does not close before pre-seed cash falls below $1.6M the Y2-Y3 headcount plan must be cut by approximately 40% and Y3 revenue drops to the downside scenario · Y3 annual revenue of $1,127k is a ramp-year total; the $1.8M SOM figure from the business plan is the annualised run-rate at 900 merchants achieved at Y3 end, so stated SOM and annual-total revenue will appear to diverge if measured on calendar-year totals · Revenue per FTE of $87k is below SaaS benchmarks; the company is investing ahead of revenue which is appropriate for pre-seed but requires seed investors to accept two additional years of negative EBITDA before reaching a $200k+ per-FTE steady state · 2%/month churn assumption requires merchants to have recurring disciplined invoice workflows; if the SME cohort is more opportunistic or naira volatility eases materially, churn could reach 4-5%/month, halving LTV and eliminating LTV/CAC viability at the $1.8k CAC target

• CBN regulatory friction. The Central Bank of Nigeria may delay or restrict licensing for a CLOB-connected FX execution product targeting retail importers, creating a 12-24 month go-to-market gap. Mitigation: Structure the initial product as an FX rate advisory dashboard with settlement routed through KongaPay's existing CBN license, and apply for an independent PSSP license in parallel.
• Stabyl infrastructure dependency. Building the product on a single pre-seed-stage CLOB provider creates concentration risk if Stabyl fails to scale, pivots, or changes API pricing terms. Mitigation: Design a multi-source rate aggregation layer from day one, integrating alternative African FX liquidity providers such as AZA Finance alongside Stabyl to avoid single-vendor lock-in.
• Incumbent channel resistance. BDC operators and commercial bank FX desks may lobby the CBN to restrict programmatic FX access for non-bank players if CLOB-driven competition accelerates. Mitigation: Build regulator relationships early and frame the product as a transparency and AML compliance tool that gives the CBN real-time visibility into SME FX flows, converting regulation into a structural moat.