Not explicitly but it does come up regularly. The challenge with standards is that they are very slow to solidify so we have to keep ensuring we are tackling a manageable (small) scope.
In my personal opinion recurring payments are quite specific to the payment method. For example, how would one do a recurring Bitcoin payment?
At Coil we are trying to come up with some open standards to address this problem space that we hope will complement the W3C browser APIs. We base our standard around the concept of a "mandate" which the user authorizes a payee to create in against their account and which allows that payee to "push" funds from the account to themselves at specific intervals and for predefined amounts. We prefer mandates to the card-based model because the user is in control and can cancel the mandate at any time.
In my personal opinion recurring payments are quite specific to the payment method. For example, how would one do a recurring Bitcoin payment?
At Coil we are trying to come up with some open standards to address this problem space that we hope will complement the W3C browser APIs. We base our standard around the concept of a "mandate" which the user authorizes a payee to create in against their account and which allows that payee to "push" funds from the account to themselves at specific intervals and for predefined amounts. We prefer mandates to the card-based model because the user is in control and can cancel the mandate at any time.
You can read a bit more about that work here: https://openpayments.dev
Excuse the state of the website it's under a small redesign but the content is mostly there, albeit a little rough right now.