Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

feat(billing): accept USDC stablecoin payments for credit packs via Stripe

Offen
  • Stimmt etwas nicht?
#76 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
backend, payments

Rechercherichtung

Start by reading frontend/src/features/billing/server/webhook.ts and the linked credit-pack work in #3 and #10; credit packs and the ledger are not implemented yet. Then verify Stripe’s current stablecoin availability, supported networks, and fees for the account and region. Done means a test-mode USDC credit pack is gated by an off-by-default flag and credits the ledger exactly once on webhook replay, with the unsupported cases documented.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

chain-integration enhancement payments tier-2

Summary

Add Stripe's stablecoin payment method to Checkout for one-off credit packs, next to the card flow already merged for subscriptions.

Estimated size: M

Motivation

Crypto-native users can pay without a card, and Stripe settles to our balance in USD, so no wallet custody or on-chain code is needed on our side.

Current state in this repo

  • Stripe subscriptions are merged (#42, part of #10): Better Auth Stripe plugin, signature-verified idempotent webhook in frontend/src/features/billing/server/webhook.ts.
  • No stablecoin or crypto payment code exists. Credit packs and the credit ledger (#3) are not implemented yet.

Proposal

  • Enable the crypto/stablecoin payment method in the Stripe account (Stripe documents this as public preview; confirm availability for our account and region first).
  • Checkout session for one-off credit packs with the stablecoin payment method; reuse the existing webhook claim/release idempotency and write a confirmed event to the ledger exactly once.
  • Gated by an env flag and off by default; test mode only.
  • Per Stripe's docs, disputes and manual capture are not supported and refunds are; design the credit flow around that (no authorize-then-capture reservations). Verify the supported networks and fees on the current docs page before building.

Acceptance criteria

  • A test-mode stablecoin purchase credits the ledger exactly once, even if the webhook is delivered twice.
  • The option is hidden when the flag is off.
  • We hold no wallet keys and store no payment details.
  • Unsupported cases (disputes, manual capture) are documented in the PR.

Out of scope

  • Stablecoin subscriptions (confirm support separately).
  • Tempo and the Machine Payments Protocol (#11).
  • Live-mode keys.

Technical notes and risks

Dependencies

  • #3
  • #10 (credit-pack phase)

Testing plan

  • Webhook replay test; Stripe CLI manual script.

Part of #1 (see also #10). 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).

Vorherrschende Sprache
Python
Sterne
2
Forks
4
Ø Merge
6 Std. 54 Min.
Gemergte PRs (30 T.)
7

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus QMeshPy/distributed-quantum

Alle Issues in QMeshPy/distributed-quantum

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.