MerchantValidationEvent: MerchantValidationEvent() constructor

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 the compatibility 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 in secure contexts (HTTPS), in some or all supporting browsers.

The MerchantValidationEvent() constructor creates a new MerchantValidationEvent object. You should not have to create these events yourself; instead, just handle the merchantvalidation event.


new MerchantValidationEvent(type)
new MerchantValidationEvent(type, options)



A string with the name of the event. It is case-sensitive and browsers always set it to merchantvalidation.

options Optional

An object that, in addition of the properties defined in Event(), can have the following properties:

methodName Optional

A string containing the payment method identifier for the payment handler being used. This is an empty string by default.

validationURL Optional

The URL from which to retrieve payment handler specific verification information used to validate the merchant. This is an empty string by default.

Return value

A new MerchantValidationEvent object providing the information that needs to be delivered to the client-side code to present to the user agent by calling complete().



Thrown if the string specified as validationURL could not be parsed as a URL.


Thrown if the specified methodName does not correspond to a known and supported merchant or is not a well-formed standard payment method identifier.


This feature is deprecated and is not part of any specification.

Browser compatibility

BCD tables only load in the browser

See also