dev.3dsecure2.com Open in urlscan Pro
52.85.151.11  Public Scan

Form analysis
1 forms found in the DOM

Name: 3ds2-form — POST https://backend.gpayments.com/subscribe

<form action="https://backend.gpayments.com/subscribe" method="post" id="3ds2-form" name="3ds2-form" class="validate" novalidate="" data-hs-cf-bound="true">
  <div id="mc_embed_signup_scroll">
    <div class="mc-field-group"><label for="mce-EMAIL">Email Address</label> <input type="email" value="" name="email" class="required email" id="mce-EMAIL"></div>
    <div id="mce-responses" class="clear">
      <div class="response" id="mce-error-response"></div>
      <div class="response" id="mce-success-response"></div>
    </div><!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
    <div id="mc-hidden-input" aria-hidden="true"><input type="text" name="b_41b30c482c9d07570b96415ce_dd26b03e25" tabindex="-1" value=""></div>
    <div class="clear"><input type="hidden" name="interests[17213c13f6]" value="true"> <input type="hidden" name="interests[883c54c608]" value="true"> <input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button">
    </div>
  </div>
</form>

Text Content

We use cookies to give you the best online experience. By using our website you
agree to our use of cookies in accordance with our privacy statement. Click here
to learn more.

Accept
 * What's new in 3D Secure 2.0
   Frictionless Flow Non-Payment Authentication Native Mobile Integration
   
 * FAQ & Glossary
   Frequently Asked Questions Glossary
 * Timeline
 * Card Schemes
 * Blog
 * English
   ENGLISH 日本語


EARLY DAYS AUTHENTICATION DID NOT HAVE MOBILE PAYMENTS IN MIND

Apart from meeting the Strong Customer Authentication (SCA) compliance under
PSD2, there are numerous benefits to the new 3DS 2.0 protocol, especially from a
mobile payments standpoint. The improved design dramatically increases the user
experience on mobile devices by being fully compatible with mobile wallet
applications and in-app transactions.


3D SECURE 1 WAS 
RIDICULOUSLY NON-USER-FRIENDLY

 * Some users were unable to view the 3DS
   authentication page on their device
 * Actually see it as a security threat
 * Compatibility issues when the authentication process
   is conducted on mobile browsers
 * Users felt the extra step was unnecessary, and often
   got irritated by it to the point where they would quit the purchase
 * Authorization page loading speeds cause issues
   and frustration
 * Users are not always able to identify the authenticity of the popup window,
   which would often cause suspicion and result in transaction abandonment.


WE ARE AT THE DAWN OF A NEW ERA

 * With the addition of an SDK component, comprehensive integration with mobile
   apps is
   now possible, allowing merchants to natively integrate 3D Secure into their
   mobile apps.
 * Merchants can ensure that the authentication process looks
   and feels consistent with the rest of the app
 * Dramatically increases the user experience on mobile devices, including
   non-browser based platforms and mobile integration
 * Biometric authentication whilst still in the merchant’s app it will
   likely just feel like a valid security measure
 * The merchant’s platform will only require additional authentication if the
   risk is high –
   that will happen in only a small percentage of the transactions
 * Authentication activity will be invisible to the cardholder




DID YOU KNOW THAT...

140m

70% of American users say security is
their biggest worry when making
mobile payments while

2020

Mobile wallets expected to
become more popular than
debit and credit cards by 2020

50%

50% of cybersecurity professionals are
sceptical about the safety of mobile
payments.

70-85%

According to Visa, the enhanced 3DS
protocol (3D Secure 2) will reduce
card abandonment by 70% and
checkout times by 85%.


3D SECURE 2.0 IS ON THE WAY WITH:


FRICTIONLESS FLOW LEARN MORE

Frictionless Flow is perhaps the biggest improvement made to this 16 years old
protocol. By performing risk-based authentication in the access control server
(ACS), issuers are now able to approve a transaction without the need for input
from the cardholder. That means no more annoying pop-up windows, and having to
remember static passwords, removing friction from the checkout process; hence
"frictionless flow".


NON-PAYMENT AUTHENTICATION LEARN MORE

3D Secure 2.0 can be used for more than just online transactions. With the
addition of "Non-payment authentication", the cardholder can be authenticated
even without them making a purchase. This is extremely useful for adding credit
cards to e-wallets (gone is the $1 charge just to validate your credit card!)




NATIVE MOBILE INTEGRATION LEARN MORE

Mobile devices have become an integral part of our lives, and consumers are
increasingly shopping on their mobile devices. 3D Secure 2 has added a mobile
SDK component, allowing merchants to natively integrate the 3D Secure process
into their mobile apps, making the mobile checkout experience fast and seamless.


STAY ON TOP OF WHAT'S HAPPENING WITH 3DS2

Email Address




and join group to learn more and discuss


THANKS! YOU ARE
SUBSCRIBED TO 3DS2 NEWSLETTER!



one last thing to be done here - join group to learn more and discuss

 * What's New in 3D Secure 2
   Frictionless Flow Non-Payment Authentication Native Mobile Integration
 * FAQ & Glossary
   Frequently Asked Questions Glossary
 * Timeline
 * Card Schemes
 * Blog
 * English
   ENGLISH 日本語