#stripe
5
2026-08-24
frogermcs/stripe-ksef
A
Synchronize Stripe EU B2B invoices with the Polish National e-Invoicing System (KSeF) using Node.js and TypeScript
2026-10-07
Show HN: Open-source Implementaiton of Stripe's 3D Waves
未评级
I've always been a fan of Stripe's designs. A while ago I saw a video of on a YC pod where they briefly showed an internal tool used to generate the 3D waves on their landing page. Thought it was a shame there wasn't an open-source equivalent, so I built one (and got carried away and probably ended up with a lot more knobs).
2026-09-19
Show HN: Open-source revenue recognition and analytics for Stripe and Metronome
未评级
Hi HN, I’m Tanin. For about four years, I worked on the Revenue Recognition and Analytics teams at Stripe. Today, I'm open-sourcing Book of Revenue, a self-hosted revenue engine and drop-in alternative to Stripe Revenue Recognition (with optional support for Metronome). ### The Problem: Most founders track MRR or cash collected in Stripe and assume that reflects revenue. But cash collected isn't revenue, and MRR isn't an accounting metric. Once you hit scale, raise institutional capital, or prep for an audit, ASC 606 / IFRS 15 rules kick in: - Annual upfront subscriptions must be amortized monthly as deferred revenue. - Mid-cycle upgrades, prorations, usage overages, refunds, and disputes quickly turn into messy manual spreadsheets. - Finance and engineering end up arguing because Stripe dashboard numbers never match QuickBooks or NetSuite during month-end close. ### What Book of Revenue Does: - Automated Revenue Recognition: Computes GAAP/IFRS-compliant revenue schedules from your Stripe billing and payment events out of the box. - Unified Financial Truth: Aligns founder analytics with your accountant’s ledger so both sides look at the exact same numbers. - Full Data Ownership: Self-hosted with no vendor lock-in. You retain complete custody of your customer financial records and intermediate data models. ### Looking for Early Users: I’m looking for early design partners—particularly companies processing over $100k in annual volume who dread month-end reconciliations. I'm offering free hands-on deployment and a complimentary audit of your current Stripe/Metronome billing architecture. If you’d like to test it out, drop a comment below or email me directly at [email protected]. Website: https://bookofrevenue.com GitHub: https://github.com/tanin47/book-of-revenue
2026-09-18
Show HN: Nexus-Arc – pay-per-call and job escrow for AI agents on Arc
未评级
Hi HN — I built Nexus-Arc. AI agents can call APIs and run multi-step work, but they still cannot open a Stripe account or hold a corporate card. Prepaid credits lock capital; L1 fees make $0.001 calls uneconomic; L2 batch latency breaks tight loops. Nexus-Arc is a dual-rail gateway live on Arc mainnet (chain 5042), where USDC is native gas: 1. Synchronous rail — HTTP 402 / x402. Agent hits an endpoint unsigned, gets a 402 + challenge, signs a Permit2 / EIP-712 voucher, retries with PAYMENT-SIGNATURE. Settlement is in-process, sub-second, pay-per-call. No API keys. 2. Asynchronous rail — ERC-8183 escrow (NexusJobs). Client locks a USDC budget, provider submits a deliverable hash (IPFS/Arweave), evaluator releases payout. State machine: Open → Funded → Submitted → Terminal. Expiry refunds the client. Live screener (expect HTTP 402 on an unpaid GET): https://nexus-arc.pryx.dev/v1/screener Explorer: https://explorer.arc.io Stack is Bun + Effect TS on Arc. Fees are small (x402 ~0.1% + $0.0005; escrow 75 bps on completion). Happy to answer questions on the 402 self-facilitation path, Permit2 vouchers, or the escrow evaluator. What should I wire next — MCP tools, more paid APIs, or agent identity (ERC-8004)?