Making a place for this question in the explainer so we can link to it
The Web Payments WG has designed two APIs that follow a similar pattern to Web Monetization but for a different use case.
The Payment Request API is an imperative API that websites can use to request a single discrete payment: the Payment Request API is designed to always prompt the user for authorization as part of the flow as it is designed for payment sizes where this is necessary. However, nothing prevents this API also supporting a non-interactive flow that supports Web Monetization use cases.
Further, the Payment Handler API aligns well with the model anticipated for Web Monetization senders: A sender might manifest as a specialized Payment Handler capable of returning not just a PaymentResponse but also a handle to a stream of micropayments.
Making a place for this question in the explainer so we can link to it