MerchantValidationEvent
Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see thecompatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
Secure context: This feature is available only insecure contexts (HTTPS), in some or allsupporting browsers.
TheMerchantValidationEvent
interface of thePayment Request API enables a merchant to verify themselves as allowed to use a particular payment handler.
Learn more aboutmerchant validation.
In this article
Constructor
MerchantValidationEvent()
DeprecatedCreates a new
MerchantValidationEvent
object describing amerchantvalidation
event that will be sent to the payment handler to request that it validate the merchant.
Instance properties
MerchantValidationEvent.methodName
DeprecatedA string providing a unique payment method identifier for the payment handler that's requiring validation. This may be either one of the standard payment method identifier strings or a URL that both identifies and handles requests for the payment handler, such as
https://apple.com/apple-pay
.MerchantValidationEvent.validationURL
DeprecatedA string specifying a URL from which the site or app can fetch payment handler specific validation information. Once this data is retrieved, the data (or a promise resolving to the validation data) should be passed into
complete()
to validate that the payment request is coming from an authorized merchant.
Instance methods
MerchantValidationEvent.complete()
DeprecatedPass the data retrieved from the URL specified by
validationURL
intocomplete()
to complete the validation process for thePaymentRequest
.
Browser compatibility
Loading…