You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per suggestion here for consistency with fail fast design: #536 (comment)
The payment identifiers provided in a request should be valid (per the PMI spec) and can either be checked as part of the show() algorithm at step 11 here or earlier at step 4.2 of the Payment Request constructor here although this is likely more processing than desired inside a constructor.
Assuming this check is implemented in the show() algorithm it should result in the promise being rejected. The error to use is up for debate...
URL parsing error seems best for a URL identifier unless the issue is specific to payment method identifiers (not using https etc)
The text was updated successfully, but these errors were encountered:
Per suggestion here for consistency with fail fast design: #536 (comment)
The payment identifiers provided in a request should be valid (per the PMI spec) and can either be checked as part of the
show()
algorithm at step 11 here or earlier at step 4.2 of the Payment Request constructor here although this is likely more processing than desired inside a constructor.Assuming this check is implemented in the
show()
algorithm it should result in the promise being rejected. The error to use is up for debate...URL parsing error seems best for a URL identifier unless the issue is specific to payment method identifiers (not using
https
etc)The text was updated successfully, but these errors were encountered: