Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#76 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
backend, payments

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
6h 54min
PRs com merge (30d)
7

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QMeshPy/distributed-quantum

Todas as issues de QMeshPy/distributed-quantum

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.