Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#76 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
backend, payments

Research direction

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.

Written by the indexing model from the issue text.

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

Dominant language
Python
Stars
2
Forks
4
Avg merge
5h 19m
Merged PRs (30d)
11

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QMeshPy/distributed-quantum

All issues in QMeshPy/distributed-quantum

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.