Methods and systems for enabling interoperability between different Fast Identity Online (FIDO) service providers

A computer-implemented, Fast Identity Online (FIDO) authentication mismatch resolution method comprising:

• receiving, by a server system and from a payment gateway, a mismatch resolution request comprising authentication information for the FIDO authentication of a user, the mismatch resolution request indicating a FIDO protocol mismatch between a first FIDO service provider operating using a first FIDO protocol and a second FIDO service provider operating using a second, mutually incompatible FIDO protocol, wherein the first FIDO service provider is associated with an aggregator application installed on a user device associated with the user and the second FIDO service provider is associated with the payment gateway of a merchant associated with the aggregator application;
• extracting, by the server system, a template associated with the second FIDO service provider from a plurality of templates from a database associated with the server system;
• mapping, by a rule-based model associated with the server system, the authentication information on the template, wherein the mapping by the rule-based model comprises:
• extracting one or more authentication parameters from the authentication information;
• assigning at least one authentication parameter to at least one corresponding field on the template based on predefined mapping rules;
• and
• responsive to a mandatory field on the template lacking an assignable authentication parameter, performing a fallback operation comprising determining whether a historically successful authentication has occurred within a predefined time interval and assigning an authentication parameter obtained during the historically successful authentication when the historically successful authentication is determined to have occurred;
• transmitting, by the server system, a FIDO authentication request message comprising the template to the second FIDO service provider;
• and
• upon receiving a FIDO authentication response message comprising an authentication successful flag from the second FIDO service provider, transmitting, by the server system, an authentication successful message to an acquirer server associated with the merchant using the payment gateway.

A computer-implemented, Fast Identity Online (FIDO) authentication mismatch resolution method comprising:

• receiving, by a server system and from a payment gateway, a mismatch resolution request comprising authentication information the FIDO authentication of a user, the mismatch resolution request indicating a FIDO protocol mismatch between a first FIDO service provider operating using a first FIDO protocol and a second FIDO service provider operating using a second, mutually incompatible FIDO protocol, wherein the first FIDO service provider is associated with at least one application installed on a user device associated with the user and the second FIDO service provider is associated with a new user device;
• extracting, by the server system, a new user device-specific template associated with the second FIDO service provider from a database associated with the server system;
• mapping, by a rule-based model associated with the server system, the authentication information on the new user device-specific template, wherein the mapping by the rule-based model comprises:
• extracting one or more authentication parameters from the authentication information;
• assigning at least one authentication parameter to at least one corresponding field on the new user device-specific template based on predefined mapping rules;
• and
• responsive to a mandatory field on the new user device-specific template lacking an assignable authentication parameter, performing a fallback operation comprising determining whether a historically successful authentication has occurred within a predefined time interval and assigning an authentication parameter obtained during the historically successful authentication when the historically successful authentication is determined to have occurred;
• transmitting, by the server system, a FIDO authentication request message comprising the new user device-specific template to the second FIDO service provider;
• and
• updating, by the server system, a user-device-specific template with the new user device-specific template on the new user device.

A Fast Identity Online (FIDO) authentication mismatch resolution server system, comprising:

• a memory configured with instructions stored therein;
• a communication interface;
• and
• a processor in communication with the memory and the communication interface, the processor configured to execute the instructions stored in the memory and thereby cause the FIDO authentication mismatch resolution server system to perform, at least:
• receiving, from a payment gateway, a mismatch resolution request comprising authentication information for the FIDO authentication of a user, the mismatch resolution request indicating a FIDO protocol mismatch between a first FIDO service provider operating using a first FIDO protocol and a second FIDO service provider operating using a second, mutually incompatible FIDO protocol, wherein the first FIDO service provider is associated with at least one application installed on a user device associated with the user and the second FIDO service provider is associated with the payment gateway;
• extracting a template associated with the second FIDO service provider from a plurality of templates from a database associated with the FIDO authentication mismatch resolution server system;
• mapping, by a rule-based model associated with the FIDO authentication mismatch resolution server system, the authentication information on the template, wherein the mapping by the rule-based model comprises:
• extracting one or more authentication parameters from the authentication information;
• assigning at least one authentication parameter to at least one corresponding field on the template based on predefined mapping rules;
• and
• responsive to a mandatory field on the template lacking an assignable authentication parameter, performing a fallback operation comprising determining whether a historically successful authentication has occurred within a predefined time interval and assigning an authentication parameter obtained during the historically successful authentication when the historically successful authentication is determined to have occurred;
• transmitting, by the FIDO authentication mismatch resolution server system, a FIDO authentication request message comprising the template to the second FIDO service provider;
• and
• upon receiving a FIDO authentication response message comprising an authentication successful flag from the second FIDO service provider, transmitting an authentication successful message to the payment gateway.

A non-transitory computer-readable storage medium comprising computer-executable instructions that, when executed by at least a processor of a server system, cause the server system to perform a Fast Identity Online (FIDO) authentication mismatch resolution method comprising:

• receiving a mismatch resolution request comprising authentication information from a payment gateway for a FIDO authentication of a user, the mismatch resolution request indicating a FIDO protocol mismatch between a first FIDO service provider and a second FIDO service provider, wherein the first FIDO service provider is associated with at least one application installed on a user device associated with the user and the second FIDO service provider is associated with the payment gateway;
• extracting a template associated with the second FIDO service provider from a plurality of templates from a database associated with the server system;
• mapping, by a rule-based model associated with the server system, the authentication information on the template, wherein the mapping by the rule-based model comprises:
• extracting one or more authentication parameters from the authentication information;
• assigning at least one authentication parameter to at least one corresponding field on the template based on predefined mapping rules;
• and
• responsive to a mandatory field on the template lacking an assignable authentication parameter, performing a fallback operation comprising determining whether a historically successful authentication has occurred within a predefined time interval and assigning an authentication parameter obtained during the historically successful authentication when the historically successful authentication is determined to have occurred;
• transmitting a FIDO authentication request message comprising the template to the second FIDO service provider;
• and
• upon receiving a FIDO authentication response message comprising an authentication successful flag from the second FIDO service provider, transmitting an authentication successful message to the payment gateway.