Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#76 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Domaine
backend, payments

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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).

Langage dominant
Python
Étoiles
2
Forks
4
Merge moyen
6 h 54 min
PR mergées (30 j)
7

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de QMeshPy/distributed-quantum

Toutes les issues de QMeshPy/distributed-quantum

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.