Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#76 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
backend, payments

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Python
Estrellas
2
Forks
4
Merge medio
5 h 19 min
PR fusionados (30 d)
11

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QMeshPy/distributed-quantum

Todos los issues de QMeshPy/distributed-quantum

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.