mas-perf.worldpaypp.com Open in urlscan Pro
2a02:26f0:480:24::1726:6274  Public Scan

Form analysis
1 forms found in the DOM

Name: form1 — POST Auth/Login.aspx

<form name="form1" method="post" action="Auth/Login.aspx" id="form1">
  <div>
    <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE"
      value="Kj554KNEdcTxQxzRnTGIjCmYE/IZ+1ZW12bEXsXFk8BTY6iEf/3bR6de8IOyTde39EgcxJ4zBTxkMOZnQF9gUyglxda5pEjfIBKUZLJH3hwhK9lSRkSBr9Lxp+ipOseH6+R9J6sUaAJiG8qp4T3vFjuGlC66Dj1B7AHMJlPRTavmtzpUW7AEEb+bdGCqGOEPqrz14yCfNg5p28KWgC+1UMfUNE8fgqC6irJvZbTecfDZw+tt">
  </div>
  <script type="text/javascript">
    //<![CDATA[
    var theForm = document.forms['form1'];
    if (!theForm) {
      theForm = document.form1;
    }

    function __doPostBack(eventTarget, eventArgument) {
      if (!theForm.onsubmit || (theForm.onsubmit() != false)) {
        theForm.__EVENTTARGET.value = eventTarget;
        theForm.__EVENTARGUMENT.value = eventArgument;
        theForm.submit();
      }
    }
    //]]>
  </script>
  <script src="/WebResource.axd?d=pynGkmcFUV13He1Qd6_TZDYg3MA6x2OGDdJkOyeVxDcXDluDaoMQWe_aC8FIGTbh3f3Tvg2&amp;t=638344089340000000" type="text/javascript"></script>
  <script src="/WebResource.axd?d=JoBkLzP19aTuxbWOhHobYn_i5ZqHix4wn1nbjTU9bU_V01JbRQ6_MTwksrgX7uxo7ebOPw2&amp;t=638344089340000000" type="text/javascript"></script>
  <div>
    <input type="hidden" name="__VIEWSTATEGENERATOR" id="__VIEWSTATEGENERATOR" value="442DF5CE">
    <input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="">
    <input type="hidden" name="__EVENTARGUMENT" id="__EVENTARGUMENT" value="">
  </div>
  <div class="loginFormWrap">
    <div id="notification" class="notifier notifier-info">
      <span>
        <img width="5%" height="5%" src="../Images/info_i_icon.png" alt="Important notice!">
      </span>
      <span class="bolded">The way you log in to MAS is changing.</span>
      <span> Customers will be required to authenticate themselves using a secondary method in order to benefit from two-factor authentication and comply with Strong Customer Authentication (SCA) requirements.
        <a href="#" onclick="popupService.show('loginPopup')">Click here for more details</a>
      </span>
    </div>
    <span id="Label2">Welcome to the Merchant Administration System.</span>
    <br>
    <span id="lblLoginMsg">Please enter your user details below.</span>
  </div>
  <div class="loginFormWrap">
    <div class="formFieldClass">
      <input name="txtUserName" type="text" id="txtUserName" tabindex="1" placeholder="Email address" style="border-width:1px;border-style:solid;">
    </div>
    <div class="formErrorClass">
    </div>
    <div class="formButtonClass">
      <input type="submit" name="Button1" value="Continue" id="Button1" tabindex="3" class="formSubmitClass">
    </div>
  </div>
  <script type="text/javascript">
    //<![CDATA[
    WebForm_AutoFocus('txtUserName'); //]]>
  </script>
</form>

Text Content

Merchant Administration System (TEST)

- Introducing Strong Customer Authentication -

In September 2019, new requirements were introduced in Europe as part of the
Second Payment Services Directive (PSD2). These requirements affect the level of
authentication required for users who instruct Bankouts and are designed to
reduce fraud. This means the Merchant Administration System (MAS) must enforce
Strong Customer Authentication (SCA) by the end of 2020.


WHAT IS STRONG CUSTOMER AUTHENTICATION?

Strong Customer Authentication (SCA) is a regulation to reduce the likelihood of
fraud by requiring additional ways to prove the customer is who they say they
are. A single-factor authentication (e.g. username & password) is not deemed
sufficient to prevent fraud under the regulation. SCA requires the user to at
least have two of the following three elements:

 * Something the customer knows: e.g password
 * Something the customer has: e.g a token or one time pin from a phone
 * Something the customer is: e.g fingerprint


HOW DOES THIS AFFECT YOUR MAS LOGIN?

In order for customers to continue making Bankouts using MAS the customer must
satisfy two of the elements outlined in SCA. To help facilitate the customer,
MAS will be changing its login method to support two-factor authentication.


WHAT DOES THE CUSTOMER HAVE TO DO?

When prompted in the near future, after the user enters their email, the user
will be redirected to Infinity IDP (provided by FIS). The customer will be
required to register with Infinity IDP and then download the FIS Authenticator
Mobile App. After registration the customer will be required to use their email
and password and the FIS Authenticator Mobile App to login MAS for all
subsequent logins.

Please see our communications for more details.

Log in
The way you log in to MAS is changing. Customers will be required to
authenticate themselves using a secondary method in order to benefit from
two-factor authentication and comply with Strong Customer Authentication (SCA)
requirements. Click here for more details
Welcome to the Merchant Administration System.
Please enter your user details below.