I put a version of this in Brett’s thread back in Sept and showed the running demo on Bluesky a week later, so here’s the general form.
Context: I’ve been building payments for atproto apps out of Europe since the summer - it’s called atmopay. I didn’t build it on this spec, and I’d rather say that than have someone notice. Different records, kept in different places, different way of asking whether someone’s paid.
But it would be very good to have a shared standard, so here are some suggestions up for discussion:
1. The servicer list shouldn’t sit in the DID document
The docs are already of two minds as far as I can tell. Recipients says publish an ordered list of broker DIDs in your DID document. App Developers says “it is up to the recipient to contextually hint or broadcast which payment servicers they use.” So it’s half-settled already, and I’d suggest to settle it as a record.
The reason: that list is the creator’s off switch. Take a broker off it and every app on the network stops believing their attestations, and you don’t need the broker’s cooperation to do it. Best property in the design as far as I can tell. And right now it lives behind the most nerve-wracking write in atproto (DID op) ![]()
With more than one broker around it matters even more. In atmopay’s specauthorizedIssuers lets an app find out which ones a creator uses.
2. payment.lookup needs a lock on it
Required payer and recipient, no auth declared, and the broker guide leaves authentication to each broker. For sure, some will take the easy path. Then it’s a who-paid-whom endpoint for the whole network, which undoes most of what the permissioned-space mode is there for.
Not a free change, I know. Every scenario verifies through lookup. But App Developers already documents local verification straight from the payer’s repo, and that path never touches it. So a lock doesn’t stop you verifying a payment you’ve been pointed at but rather stops you discovering the ones nobody told you about.
In atmopay the endpoint answers two callers: the subject, or a service the creator has named. Everyone else gets the same refusal whether or not the account exists, so the error doesn’t leak either.
The record I’d like to add
Scope says catalogues, pricing and tiers are out. That’s fair, but it’s the first wall an app hits: no checkout screen without knowing what’s for sale. That’s the piece I’d most like to see land somewhere shared. I don’t much mind where.
Paying the app that delivered it. In atmopay the delivering app as well as the selling one get a share of the transaction fees. Delivery is attested by the reader’s own PDS, because the space access check names the client, and the selling app signs with its own PDS. What’s missing is that service auth names the user and never the app. I have a short write-up on that.
Spec, lexicons, a verifier, a mock issuer and the pilot (pnpm start, nothing external) for what atmopay uses can be found here: https://github.com/eurosky-social/atproto-payments
Namespace is a placeholder. I’d rather it didn’t sit under anyone’s company name, mine included. Eurosky can host it if that’s useful, but I’m not attached to that.
Disclosure: I make Skeets and Flashes, I’m involved in Eurosky, and the payments thing is a business. Which is more or less why I shouldn’t be the one holding the lexicons.