KEMBAR78
Should we validate nonsense payer error properties? · Issue #793 · w3c/payment-request · GitHub
Skip to content

Should we validate nonsense payer error properties? #793

@marcoscaceres

Description

@marcoscaceres

If we have a payment request that has option: {requestPayerEmail: false}, then what should we do if the merchant asks to correct something that was not requested, like

response.retry({payer: {email: "Lol, I never asked for your email."} })

Right now, the spec just says to ignore that. Should we maybe throw or just continue to ignore. The above also applies to some cases of .updateWith() (e.g., flagging shipping address errors when no shipping address was requested).

cc @aestes, @rsolomakhin, @romandev.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions