SPC spec

[Karlheinz Seybold, REINER SCT]

Hello,

 

just a short question regarding the SPC interface:

 

Are there any limitations for the values/fields passed to a PaymentRequest?

 

 

Especially, are there any limitations regarding the displayName field?

Can I pass a multiline String?

 

Maybe you can point me to the spec where it is defined.

 

Thanks a lot for your help!

 

Regards

 

kalle

[Rouslan Solomakhin]

Hi kalle,

The spec does not place a lot of restrictions on the displayName field, but it probably should. Could you please post this question on https://github.com/w3c/secure-payment-confirmation/issues/new for the wider community to discuss? This mailing list is for Chromium specifically, but SPC is being developed in collaboration with many other organizations.

Thank you!

Cheers,

Rouslan

--
You received this message because you are subscribed to the Google Groups "payments-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to payments-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/payments-dev/002001da89c1%24cea98300%246bfc8900%24%40reiner-sct.com.

[Karlheinz Seybold, REINER SCT]

Hello Rouslan,

 

thanks for the fast reply! I will post it on the mailing list.

 

I got a meeting tomorrow where I need to know about the restrictions in the current Implementation of Chromium.

 

Maybe you can help me with the most important question directly:

 

Can I pass a multiline string to the displayName field?

 

Background:

 

We are consulting a german bank. They are looking for a new way to secure online transactions for home banking.

SPC seems to be a good possibility, but only if there is a way to securely display all the transaction data. And they don’t fit in one line…

Therefore we need more than one line.

 

Thanks for your help!

[Rouslan Solomakhin]

Hi kalle,

I don't think that displaying a lot of data is not the intended use case for the displayName field. When you post the discussion to https://github.com/w3c/secure-payment-confirmation/issues/new, please provide some examples of your use case, so that the community can discuss whether/how this use case should be supported.

We would be happy to hear more about this use case and whether other payment APIs can be of use, e.g., see the "displayItems" field in the https://w3c.github.io/payment-request/ API.

Cheers,

Rouslan

[Rouslan Solomakhin]

> I don't think that displaying a lot of data is not the intended use case for the displayName field.

Meant to write: I don't think that displaying a lot of data is the intended use case for the displayName field.

[Stephen Mcgruer]

> Meant to write: I don't think that displaying a lot of data is the intended use case for the displayName field.

I'll follow up on the GitHub issue, but just wanted to confirm this. The PaymentInstrument.displayName field is expected to be used as a short identifier for a given PaymentInstrument, such as "Stephen's Bank Account", "Account ****1234", or "My ScotiaBank Visa". It is not intended for folks to add additional transaction information into.

If there is a need for additional transaction details, the Web Payments Working Group would be happy to hear them on the SPC issue you file!

Thanks,
Stephen

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/payments-dev/CAMMzaWFeS3i3GYEcnL%3Dz%2BZE_KQcfbAK2yrYZ-BOzs%2B7JEHnwBw%40mail.gmail.com.

[kalle s]

Thats exactly what we are evaluating.
We want to show the transaction data e.g. for a money transfer from one account to an other, like

John Smith  

IBAN: XXXXXXXXXXX

invoice YYYY

Having multiple lines (lets say up to 3 or 4) would open SPC for a lot of new use cases.

And as a bonus for  hight security it would be nice if there is a optional possibility to show the transaction data on the hardware device's display before confirming (signing) the transaction.

Thanks 

Kalle