This is valuable, but I want to be able to know for sure that 1. the email is "real" and 2. the person using the email address actually has access to it and can receive emails on it. Thus the process of actually sending an email to the provided address and making them click a link.
I've still not seen anything that provides this functionality.
Agreed that the Callback URL is definitely preferable, if the consuming application has a backend (Lambda or more substantial). Thanks!
I was thinking either pinging or some sort of a "check" button that the user would click/tap (e.g. Cloudflare's button to check the status of NS transfers). Not the smoothest part of the idea. This decision would ultimately be left to the consumer of the API. Also, in thinking this through a little more I think it is also applicable to applications that do have their own backend, in which case they could provide a callback.
I like your idea on 3/4. That could maybe be a configurable option
I have an app in the Windows Store (haha, I know). It uses some 3rd party APIs but does not have a server-side backend of its own (technically it does, but for the purpose of this question let's say it doesn't).In the app, the user enters their email address and payment information. Before processing their payment, I would like to verify that the user actually owns the email address that they...