mSIGNIA realizes market compliance certifications are the starting line… not the finish line.  The same mSIGNIA product is certified compliant for EMV 3DS version 2.2, PSD2 Strong Consumer Authentication (SCA), and soon FIDO.  mSIGNIA product is designed and enhanced so future protocols and protocol versions will not change the way merchants and trusted third parties (TTPs) interface with our product.

mSIGNIA was first to provide a complete, certified EMV 3DS v2.2 solution which includes the 3DS Server, iOS SDK, and Android SDK.

mSIGNIA’s sophisticated payment technologies already provide customers several next-generation, adjacent market, and EMV 3DS v2.3 features, even though 3DS v2.3 products are not expected to be in market earliest April 2022.

EMV 3DS browser SDK – mSIGNIA currently provides the 3DS Browser to issuers so they do not need to implement their own iFrame 3DS Method.  When 3DS v2.3 is available, merchants will get a certified EMV 3DS browser SDK, just as they get certified SDKs for iOS and Android.  The 3DS Browser SDK mSIGNIA provides now to issuers is the same 3DS Browser SDK merchants will get.

mSIGNIA’s Browser SDK – whether provided to issuers or merchants – is designed as another universal SDK which is enhanced with cAPI extensions to allow trusted third parties (TTPs such as Issuers, Delegated Authenticators, FIDO Reliant Parties, and Risk Engines) to receive additional data like biometrics.  This ability for TTPs to request and receive additional data enables frictionless compliance with SCA and FIDO.

cAPI instructions enable data transparency so that merchants can understand which data TTPs require to approve transactions.  cAPI and the Browser uSDK eliminate the need for issuers to take-over the iFrame during the merchant’s buy experience.

mSIGNIA’s uSDKs are not ‘virtual SDKs’.  uSDKs provide the well-managed, client footprint required to enable the convenience and security today’s transaction environments require.

Client API (cAPI) – mSIGNIA’s cAPI already functions as future market needs such as

• cAPI will be certified as the 3DS SDK Server when EMV 3DS v2.3 available
• cAPI is already designed for 3DS v2.3’s split SDKs and soon EMVCo’s SRC
• cAPI uses a communication protocol for 3DS Delegated Auth, FIDO reliant parties, and other TTPs
• cAPI allows TTPs to write data (i.e., device IDs, tokens, …) to the device through the merchant’s SDK; data is written and stored as 1^st party data, not 3^rd party writes which are increasingly being blocked by advanced browsers and not supported at all with apps
• cAPI provides single interface for payment orchestration control

All these design enhancements available now translate to little or no upgrade effort by merchants and TTPs as the market matures and adopts future standards including the Client API and Universal SDK protocols.

Migration from 3DS > SRC > SCC – mSIGNIA’s products are already 3DS, SRC, and (soon) FIDO and W3C compliant… but we do not stop there.  As the Innovation Arc shows, mSIGNIA is already designing for EMVCo’s Secure Remote Commerce (SRC) and even beyond to Secure Connected Commerce, the unification between in-person and online payment experiences.

Learn more about mSIGNIA’s next generation products or explore more mSIGNIA differences here.