feat(billing): optional Stripe Connect Express onboarding for workers
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the Stripe Connect patterns from issue #10 and read docs/payments/stripe-connect-vs-onchain-payouts.md, referenced as the spike for #77. Then locate the worker profile and payout UI entry points; the issue does not name their files. Done means test-mode Express onboarding persists the connected account ID, shows payout readiness or pending status, and leaves on-chain earnings available to workers who skip Connect.
由索引模型根据 Issue 内容生成。
描述
Summary
Optional Stripe Connect Express onboarding so workers can later cash out via bank or Connect stablecoin payouts.
Estimated size: M
Priority: P1 (from spike #77)
Motivation
Spike #77 recommends on-chain default for marketplace settlement and Connect as an optional off-ramp. Workers who want KYC + bank/crypto cash-out need a connected account first.
Proposal
- Express connected-account onboarding (Stripe-hosted or embedded).
- Store
stripeConnectedAccountIdon the worker profile. - Link to Express Dashboard for wallet/bank setup.
- Test mode only; keys via env (no secrets in repo).
Acceptance criteria
- A worker can complete Express onboarding in Stripe test mode.
- Connected account id is persisted and shown as “payout ready” / pending in UI.
- Workers who skip Connect can still receive on-chain earnings (#8).
Out of scope
- Per-fragment settlement via Stripe Transfers (rejected in #77).
- Live-mode keys.
Dependencies
- #77 (decision)
- #10 (Billing / Connect phase patterns)
- Prefer #8 landing first so ledger/earnings exist to cash out later
References
- Spike:
docs/payments/stripe-connect-vs-onchain-payouts.md(PR for #77) - https://docs.stripe.com/connect/express-dashboard
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 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#111 ·
维护者通常 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
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
-
Validate finite output clamping limits in StepPredictor.prepare_clamping_params to prevent silent NaN/Inf propagation可能已有人在做 @muskan-creates352 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
mllam/neural-lam#848 ·
维护者通常 2 天内回复
-
infra
难度 1/5 1 小时以内 新手友好度 88/100
fab-geocommuns/RNB-coeur#1166 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
deepspeedai/DeepSpeed#8951 ·
维护者通常 2 天内回复