GET /payments (and /assets/:contract/payments) returns per-item fields
txHash, ledger, closedAt, buyer, seller, sponsor, amount, assetContract,
assetSymbol, feeBumped, scheme, facilitator — confirmed against the live
Render deployment. There is no resource field anywhere in PaymentRow /
PaymentResponse (src/db.ts, src/api-types.ts).
This makes it impossible to tell which HTTP endpoint a given on-chain
settlement was paying for when a seller has more than one priced endpoint
behind the same payTo address — seller alone can't disambiguate.
The facilitator already has this information at settle time (the
resource URL is part of the x402 payment requirements the buyer paid
against). Recording it alongside the payment write, and adding a
resource field to PaymentRow / PaymentResponse, would let downstream
consumers (the vellar-vscode sidebar's Recent Settlements section, for
one) show which endpoint each settlement belongs to without guessing
or cross-referencing by amount, which is ambiguous when two endpoints
share a price.
Filed while building vellar-vscode's Recent Settlements section, which
currently omits the endpoint column entirely rather than guess at it.
GET /payments (and /assets/:contract/payments) returns per-item fields
txHash, ledger, closedAt, buyer, seller, sponsor, amount, assetContract,
assetSymbol, feeBumped, scheme, facilitator — confirmed against the live
Render deployment. There is no
resourcefield anywhere in PaymentRow /PaymentResponse (src/db.ts, src/api-types.ts).
This makes it impossible to tell which HTTP endpoint a given on-chain
settlement was paying for when a seller has more than one priced endpoint
behind the same payTo address — seller alone can't disambiguate.
The facilitator already has this information at settle time (the
resource URL is part of the x402 payment requirements the buyer paid
against). Recording it alongside the payment write, and adding a
resourcefield to PaymentRow / PaymentResponse, would let downstreamconsumers (the vellar-vscode sidebar's Recent Settlements section, for
one) show which endpoint each settlement belongs to without guessing
or cross-referencing by amount, which is ambiguous when two endpoints
share a price.
Filed while building vellar-vscode's Recent Settlements section, which
currently omits the endpoint column entirely rather than guess at it.