- From: Petr Dvořák via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Mar 2024 10:44:21 +0000
- To: public-webauthn@w3.org
OK, it makes sense. One solution could be just to ask the RP to provide a meaningful message, as you suggest. If a structured data is required, I can contribute my experience in this by suggesting formats to look into, then. If this is primarily about payments and PSD2 (as many people above suggest), you can look into: - [SPAYD](https://en.wikipedia.org/wiki/Short_Payment_Descriptor) (short payment description) which I "invented" and is used on every invoice in the Czech Republic. - [EPC Code](https://en.wikipedia.org/wiki/EPC_QR_code) the same thing, proposed on European level In our systems, we wanted to have more generic data encoded, so we took the experience from above to design a generic [data payload format for operation data](https://developers.wultra.com/components/powerauth-webflow/develop/documentation/Operation-Data.html#section-documentation). As a result, it allows you to encode data such as payments, or configuration changes into the short fixed format payload, i.e.: ### Example 1 ``` A1*A100CZK*ICZ2730300000001165254011*D20180425 ``` > Payment of 100 CZK to IBAN CZ2730300000001165254011 with associated date 2018-04-25. Displayed as: ``` AMOUNT: 100 CZK IBAN: CZ2730300000001165254011 DATE: 2018-04-25 ``` ### Example 2 ``` A0*TClosing Ticket*R32784237923 ``` > Confirmation of closing ticket with reference ID 32784237923. Displayed as: ``` MESSAGE: Closing Ticket REFERENCE: 32784237923 ``` -- GitHub Notification of comment by petrdvorak Please view or discuss this issue at https://github.com/w3c/webauthn/pull/2020#issuecomment-1988140471 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 March 2024 10:44:21 UTC