Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat(billing): Stripe subscriptions, job credits and Connect payouts

Chiusa
  • Qualcosa non va?
#10 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #84 di @harshaldulera — integrata

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, payments

Direzione di ricerca

Start by reading frontend/src/features/auth/server/auth.ts and frontend/src/proxy.ts, then review dependency issue #3 for the credit ledger. The proposal calls for subscription Checkout, signed and idempotent webhooks, a customer portal, credit purchases, and optional Connect payouts. Done means the listed acceptance criteria pass, with webhook replay tests and a Stripe CLI manual test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

chain-integration enhancement payments tier-2

Summary

Add web2 payment support with Stripe: subscriptions that unlock accounts, card-purchased job credits, and optional bank payouts to workers.

Motivation

Not every user holds stablecoins. Cards give a normal on-ramp, and the auth layer already carries trial and subscription state that nothing sets yet.

Current state in this repo

  • frontend/src/features/auth/server/auth.ts (Better Auth) defines user fields trialEndsAt and hasSubscription; trial UI exists under features/auth.
  • No billing code exists.

Proposal

  • Stripe Billing: Checkout session for a subscription; a signed webhook handler that sets hasSubscription; a customer-portal link.
  • Credits: Checkout for one-off credit packs that write confirmed events to the credit ledger (#3); jobs spend credits.
  • Connect (optional second phase): onboard workers and pay out earnings to bank accounts.
  • Use test mode keys only; all configuration via env.

Acceptance criteria

  • Webhooks verify Stripe signatures and are idempotent on event id.
  • Subscription state changes update hasSubscription and the trial banner behaviour.
  • A credit purchase appears in the ledger exactly once, even if the webhook is delivered twice.
  • No card data touches our servers or logs.

Out of scope

  • Tax, invoicing and refunds policy (document as follow-ups).
  • Live-mode keys.

Technical notes and risks

  • Webhook endpoints must be public in frontend/src/proxy.ts but protected by signature verification.

Dependencies

  • #3

Testing plan

  • Webhook replay tests; Stripe CLI-driven manual test script.

References

Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).

Lingua principale
Python
Stelle
2
Fork
4
Merge medio
6h 14m
PR unite (30g)
18

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QMeshPy/distributed-quantum

Tutte le issue di QMeshPy/distributed-quantum

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.