Well it’s super clear because this is something I’ve spent a bunch of time thinking about and basically had the same system design.
Honestly depending on your audience I’d probably lean into the how it works flow on the landing page. For now (at-least) most people who are using this are technical enough to understand from that alone.
Then breaking it into the “I want to accept payments” and “I want to build a payment processor” categories would be my focus.
It would help to have built a “tip jar service” before you push this out broadly since it gives a default setup and example to copy from.
I saw the call out to the private data at the end - obviously that’s in a bit of an uncertain state but I think it’s worth being clear up-front what must be private and what must be public for this to work. In particular can I hide both the amount and the recipient of a payment?
For now I appreciate that we’ve already deeply involved both the processor and the provider but it would also be good to have something for the buyer, maybe some way for them to securely store payment methods, although that is a can of worms.
Also check for consistency in terminology - it’s mostly ok but there was a few times I had to read close to understand who was doing what. It would help to establish that up front and then stick with the terms throughout.