feat(billing): Connect off-ramp from ledger balance (bank and/or stablecoin)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Spike:
docs/payments/stripe-connect-vs-onchain-payouts.md - https://docs.stripe.com/connect/stablecoin-payouts
Part of #1.
- 主要语言
- Python
- 星标
- 2
- 派生
- 4
- 平均合并
- 8 小时 37 分钟
- 30 天内合并 PR
- 29
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
QMeshPy/distributed-quantum#112 ·
维护者通常 1 天内回复
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
QMeshPy/distributed-quantum#110 ·
维护者通常 1 天内回复
-
Integrate persistent collaborative EtherCalc workbooks with experiment results and IPFS versions可能已有人在做 @Winter-Soren 于 1 天前认领。 未关闭
QMeshPy/distributed-quantum#103 · 已指派 1 人 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
priority middle
难度 1/5 1 小时以内 新手友好度 62/100
KATO-Hiro/AtCoderClans#12940 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 76/100
huggingface/huggingface_hub#5283 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement
难度 1/5 1 小时以内 新手友好度 86/100
维护者通常 1 天内回复
-
bug example
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复