w3c / payment-request

Payment Request API
https://www.w3.org/TR/payment-request/
Other
488 stars 135 forks source link

Signaling payment handler details errors #727

Closed marcoscaceres closed 6 years ago

marcoscaceres commented 6 years ago

For example, the card might have expired. There might be insufficient digits, etc...

ianbjacobs commented 6 years ago

To say a bit more: suppose the merchant gets back some payment credentials and those credentials don't work for some reason. The merchant might want to prompt the user again, but "minus the unacceptable credentials". Such information would need to be passed to the payment handler as well.

marcoscaceres commented 6 years ago

The model in the spec is “the following things are erroneous: x, y, z.” But not “minus unacceptable”, which seems different to me.

ianbjacobs commented 6 years ago

I think there is a difference between:

Ian

marcoscaceres commented 6 years ago

You can't use this, so the browser or payment handler should no longer present it as an option

I'm not in favor is this, tbh. Right now, everything maps to input fields.

ianbjacobs commented 6 years ago

We don't have this feature today and that has not been a show-stopper.

marcoscaceres commented 6 years ago

Paying for TPAC today...

screenshot 2018-06-26 14 14 33

We can't do this today :)

marcoscaceres commented 6 years ago

This bug should probably move to the basic card spec.

marcoscaceres commented 6 years ago

Moved https://github.com/w3c/payment-method-basic-card/issues/57

marcoscaceres commented 6 years ago

Reopening, because this still needs infrastructure in this spec.