Skip to content

Payment integration #4803

Description

@JSONbored

Problem: No mechanism exists to actually collect payment from a customer and tie it to their compute-time allocation.

Area: Product / Billing

Proposal: Integrate a payment mechanism (fiat and/or on-network, per #4781's economics decision) that feeds directly into #4790's pricing conversion.

Deliverables:

  • A working payment flow resulting in a correctly allocated compute-time balance.

Acceptance criteria:

Boundaries:

  • Blocked on Stake/payment → compute-time pricing #4790. No real payment credentials or customer financial data referenced in code comments, commit messages, or issue/PR text — handle exclusively through the payment provider's own secret-storage mechanism.

Part of #4778.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

Status
Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions