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.
The MerchantValidationEvent
method complete()
takes merchant-specific information previously received from the validationURL
and uses it to validate the merchant.
All you have to do is call complete()
from your handler for the merchantvalidation
event, passing in the data fetched from the validationURL
.
complete(validationData)
complete(merchantSessionPromise)
This exception may be passed into the rejection handler for the promise:
-
InvalidStateError
DOMException
-
Returned if the event did not come directly from the user agent, but was instead dispatched by other code. Another payment request is currently being processed, the current payment request is not currently being displayed to the user, or payment information is currently being updated.
In this example, we see the client-side code needed to support merchant validation for a payment request called payRequest
:
payRequest.onmerchantvalidation = (event) => {
const validationDataPromise = getValidationData(event.validationURL);
event.complete(validationDataPromise);
};
function getValidationData(url) {
}
This code sets up a handler for the merchantvalidation
event. The event handler calls a function, getValidationData()
, which retrieves the data from the validation URL, then passes that data (or a promise to deliver the data) into complete()
.