saascode
web3 & on-chain infrastructure·run 112 · May 2026

Stipendport

A sandbox payment-orchestration dossier for agencies that separates invoice authority, agent payment intent, provider quotes, screening, settlement and bank reconciliation.

Genesis score6.60/10
Make Stipendport real.0/500
500 more votes and Stipendport is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Small agencies may receive requests from software agents to pay for professional services using stablecoins while the agency invoices and accounts in local currency. Stipendport proposes an orchestration layer around regulated providers. The supplied research confirms an enterprise agent-payments suite and one fiat-orchestration API, while reporting no equivalent small-business package. It also states that three of five referenced capabilities remain unverified. The apparent market gap cannot establish licensing, any-chain acceptance, merchant-of-record status or remittance timing.

A merchant of record is a contractual, tax, consumer, dispute and payment role, not a checkout label. Stablecoin receipt, swap quote, chain inclusion, finality, provider acceptance, fiat settlement and bank receipt are different states. Know-your-customer, transaction screening, sanctions, custody, money transmission, invoice validity, foreign exchange, fees, refunds, chargebacks, accounting and tax vary by entity and jurisdiction. A screening receipt is bounded evidence, not legality or clean funds.

Service agreement, merchant identity, customer or agent authority, invoice, payment intent, route quote, asset, chain, wallet, screening result, exact approval, transfer, chain inclusion, finality, provider receipt, swap, fiat settlement, payout instruction, bank receipt, reconciliation, refund, dispute, tax record and business outcome remain separate. Stipendport should first prove a compliant provider-mediated state model in sandbox without touching funds.

Who pays — and why

An owner or finance lead at a small professional-services agency evaluating stablecoin payments initiated by software agents.

What it unlocks
A jurisdiction and role dossier identifying merchant, customer, agent principal, regulated providers, custody boundaries, invoice authority, screening and tax responsibilities
A sandbox route model preserving asset, chain, quote, fees, expiry, limits, screening, approval, provider states, finality and failure paths
A reconciliation trail separating invoice, payment intent, transfer, provider receipt, swap, fiat settlement, payout, bank receipt, ledger entry, refund and dispute
How Genesis scored it
6.60across seven criteria
tension 7temporal 7blindspot 7buyer 8leverage 6convergence 5why-not 5
8
Buyer persona

Small-agency owners and finance leads are actionable, though transaction volume, jurisdictions, currencies and willingness to pay need validation.

7
Productive tension

Agent-initiated checkout can reduce payment friction, but automation obscures principal authority and regulated money movement.

5
Why nobody did it

The product gap is clearer than the regulatory, provider and unit-economic barrier that kept it unbuilt.

Why it scored well

The input identifies a specific agency buyer, a confirmed enterprise timing signal, one verified fiat-orchestration provider and a concrete invoice-to-bank state problem.

What's holding it back

Three of five capabilities are unverified, merchant-of-record and licensing authority are absent, managed compliance weakens leverage and any-chain plus next-day claims are unsupported.

Signals detected4 sources crossed
SignalSupplied competitor research

SignalSupplied capability research

SignalSupplied competitor research

SignalCanonical red flag

Direction briefstipendport.md
stipendport.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.