Make "payment-authorization" a separate super project

[cyberphone]

Mixing identity-related applications and payment authorization will make specifications unnecessary complex. These topics also have quite different champions.

A separate payment-authorization project would act as a placeholder for all OpenID related standards when used for payment authorizations. Associated documents would presumably be highly profiled. Extensive amounts of examples would also be needed. Putting such in OpenID core documents would only contribute to "pollution".

If we consider implementations, it seems very unrealistic to have a single wallet application that handles everything from selective disclosures to payment authorizations. It would be a "frankenwallet".

Major, not yet addressed features, such as e-receipts (https://cyberphone.github.io/doc/defensive-publications/e-receipts.pdf) would take too much bandwidth from the identity core. It would preferably be a sub-project under payment-authorization.

An account balance lookup option would affect credential provisioning, etc. Apple Pay already have this.

In https://cyberphone.github.io/doc/saturn/saturn-v3-presentation.pdf you can find yet another set of features worth consideration, including:

• discovery services
• stacked messages
• non-direct payments
• in-line confidential issuer-to-payer messaging
• risk-based user authentication

For my current prototype which predates OpenID payment solutions, I have decided to scrap JSON in favor of Deterministically Encoded CBOR: https://github.com/cyberphone/cbor-everywhere

[cyberphone]

Non-direct payments introduce UX concerns as well: