Give Merchants the Ease + Transparency They Want
with 3DS + SCA + FIDO + W3C Compliance in a Single Solution
that Includes Data Enhancements which
Eliminate Consumer Friction and Approve More Transactions
Europe’s PSD2’s Strong Consumer Authentication (SCA) is requiring 98% of transactions be interrupted with some sort of authentication challenge. mSIGNIA’s merchant solution eliminates these interruptions.
mSIGNIA’s payment products are simple for the merchant to implement, easy for the consumer to use, and enable a safe, frictionless approval of valid transactions which are SCA compliant!
mSIGNIA’s EMV 3DS version 2.2 certified merchant solution – which can be purchased separately and branded by a payment service provider – includes:
- 3DS Server available in a cloud-compliant Java container for on-premise or AWS operation and seamless integration with an overall payment offering
- ‘Universal’ 3DS SDKs for iOS, Android, and Browser
- The Browser SDK is available now though it will not be required until 3DS v2.3’s availability in 2022
- Client API (cAPI) for easy eCommerce server integration
- Payment Simulator for end-to-end testing of the consumer experience and 3DS, SCA, and FIDO protocol compliance
Scroll down to review the design that makes such simplicity possible or click on the icons below to learn more about mSIGNIA product benefits for merchants and consumers…
mSIGNIA’s merchant solution, available as a white-label solution to payment service providers and acquirers, includes the necessary 3DS certified Server and certified SDKs as well as the Client API (cAPI). The solution communicates with any certified 3DS Directory Server and ACS.
mSIGNIA’s cAPI and uSDKs for Browser, iOS, and Android, shown as orange in the diagram, can be purchased separately to augment an existing EMV 3DS certified Server payment offering.
The cAPI and the uSDK architecture provides merchants a simple, easy interface which is protocol and version independent.
The same design is ready for the future EMV 3DS version 2.3 ‘split SDK’ standard coming in 2022.
The same cAPI interface can also send data using other protocols such as FIDO and EMV’s Secure Remote Commerce (SRC). See more about Next Generation Design here.
Only mSIGNIA’s cAPI and uSDK allows merchants and Trusted Third Parties (TTPs including Issuers, Delegated Authenticators, FIDO Reliant Parties, and Risk Engines) to get enhanced device and biometric data from a merchant’s browser and mobile apps so more transactions are approved – including SCA compliance – without interruptions that cause cart abandonment.
Merchants and TTPs can use cAPI data instructions to pre-declare which enhanced data a uSDK should collect. As the diagram shows, the data instructions and resultant data are exchanged within compliant EMV 3DS protocol messages. These instructions
- Collect additional data such as device tags and behavioral biometrics for SCA compliance, and
- Prompt the user for a fingerprint or facial biometric which can initiate a FIDO authentication exchange
Enhanced data exchange improves the consumer experience by eliminating nearly all authentication step-ups, improves the accuracy of risk scoring, complies with SCA requirements… all to increase the number of approved transaction so the entire payment ecosystem works better.
Easy Integration – mSIGNIA provides simple, easy, single API interfaces between the eCommerce server and cAPI and the between the merchant’s client apps and uSDKs. Merchants connect to cAPI via their commerce server and cAPI interfaces with various hardware clients, abstracting the chaos of different clients like browsers, mobile apps, speaker apps, gaming consoles, etc. Learn more about cAPI and uSDKs here.
Frictionless 3DS + SCA Transactions – PSD2 SCA and other transactions using multi-factor authentication cause step-up interruptions in 98% of attempted transactions, leading to significant cart abandonment. mSIGNIA’s cAPI data instructions enable Trusted Third Parties (TTPs including Issuers, Delegated Authenticators, FIDO Reliant Parties, and risk engines) to collect the data they require to approve the transaction with data exchange in the initial EMV 3DS frictionless exchange; learn more here.
Best Consumer Experience including FIDO – When a consumer hits the BUY button, in their mind, they have bought the product. Subsequent identity challenges and OOB exchanges are irritating and cause cart abandonment. Merchants want a frictionless transaction which requires effortless authentication done as part of the purchase, not after. EMV 3DS created Delegated Authentication to improve the CX but it is not well defined, ambiguous to implement, and does not ensure the 3DS liability shift which guarantees payments for merchants.
mSIGNIA’s Client API (cAPI) provides a well-defined, simple interface that works with Mastercard and Visa Delegated Authentication programs to enable Trusted Third Parties (TTPs) to significantly improve the CX; learn more here.
Next Generation Design – mSIGNIA products available today are designed to minimize customer effort and change in the future. mSIGNIA’s products are already compliant with EMV 3DS version 2.2, multi-factor authentication requirements such as Europe’s PSD2 Strong Consumer Authentication (SCA), and (soon) FIDO. In addition, mSIGNIA’s products are designed for compliance with future requirements such as EMV 3DS v2.3, SRC, and beyond… as detailed here.
Make versus Buy – Compliance is a requirement, other factors – including Expertise, Cost, Time-to-Market, Market differentiation, and Brand recognition – ensure that you can trust your payment partner is the right choice.
mSIGNIA has been a leader in EMV 3DS, mobile security, data analytics, and continues to innovate with payment products that allow payment services to offer their customers the absolute best-in-class products. Read more about make vs buy here.