Lexicon Garden

fund.at.funding.channel

A payment channel — a specific place where contributions can be received (e.g. a GitHub Sponsors page, an Open Collective profile, a bank account). Each channel is an independent record, individually addressable by its AT URI.

Repository @at.fund did:plc:e5sldj7avn3rinxwqtuddwpu namespace authority
Details · record, key any
Kindrecord
Record keyany
Authorityfunding.at.fund
Indexed
Compare Edit in builder → Fork →

Record

record · key any

Properties

channelType

requiredstring

Channel category. Maps to funding.json channel.type.

  • maxLength: 32
  • knownValues: payment-provider | bank | cheque | cash | other

createdAt

string · datetime

When this record was created or last updated.

description

string

Human-readable description of this channel.

  • maxLength: 500

uri

string · uri

The payment URL for this channel (e.g. https://github.com/sponsors/you). Optional for channels without a public URL (e.g. bank transfers). Maps to funding.json channel.address.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • fund.at.funding.contribute

    record

    A single funding URL published by a steward. Points to the steward's external funding page — the human-friendly entry point. The ATProto equivalent of rel="payment" (IANA link relation).

  • fund.at.funding.plan

    record

    A funding plan or tier with a suggested amount. Each plan is an individual record keyed by its slug ID. Plans reference channels by AT URI, allowing cross-account references (e.g. multiple maintainers pointing plans at a shared org channel).

  • org.hypercerts.funding.receipt

    record

    Records a payment from a sender to a recipient. Any party may record it, and the sender may stay anonymous. When the sender chose the recipient, record one receipt to the final recipient even if platforms or hosts passed the funds on. When an intermediary chose (regranting), record the payment into it and each onward payment as separate receipts. A receipt may be updated in place under the same record key: its URI does not change, so references by URI keep resolving, but a strongRef (as likes an