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

feat(billing): Connect off-ramp from ledger balance (bank and/or stablecoin)

Aberta
  • Algo errado?
#111 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
Stack de tecnologia
python
Domínio
backend, payments

Direção de pesquisa

Start with docs/payments/stripe-connect-vs-onchain-payouts.md and the referenced issues #77 and #8 to understand the existing settlement and Connect onboarding work. Then locate the ledger balance and payout entry points in the project. Done means withdrawals are idempotent, failed transfers preserve earnings, on-chain fragment payouts stay the default, and Connect country and entity limits are surfaced.

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

Descrição

Summary

Let workers withdraw accrued earnings via Stripe Connect Transfers (bank and/or stablecoin payout), without replacing on-chain pay-per-fragment settlement.

Estimated size: M
Priority: P2 (from spike #77)

Motivation

After on-chain settlement (#8) and Connect onboarding, some workers want a fiat or Stripe-managed USDC cash-out. Spike #77 recommends this as optional off-ramp, not the primary fragment rail.

Proposal

  • Worker requests withdrawal of available ledger balance.
  • Create a Stripe Transfer to their connected account (bank payout and/or Connect stablecoin USDC per https://docs.stripe.com/connect/stablecoin-payouts).
  • Idempotent withdrawal intents; never double-pay.
  • Gate stablecoin path on private-preview access + documented fees.

Acceptance criteria

  • Withdrawal reduces ledger balance exactly once per intent.
  • Failed Transfers do not silently clear earnings.
  • On-chain fragment payouts (#8) remain the default settlement path.
  • Country / entity limits from Connect docs are surfaced in UI or docs.

Out of scope

  • Connect-only marketplace settlement.
  • Replacing AgentKit USDC fragment transfers.

Dependencies

  • #77
  • #8
  • Connect Express onboarding follow-up from #77
  • Stripe Connect stablecoin preview access (if enabling crypto cash-out)

References

Part of #1.

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
8h 37min
PRs com merge (30d)
29

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.