Methods and systems of using sub-domains to federate device credentials scoped to a common domain

1. A computer-implemented method of authenticating a user device via a device credential scoped to a common domain shared among a plurality of payment networks, each payment network having a respective domain name different than the common domain and each payment network being assigned with a respective sub-domain of the common domain, the method comprising:

receiving, by a server of a payment network of the plurality of payment networks, a first request redirected from a sub-domain assigned to the payment network to a domain name associated with the payment network;

responsive to the first request, transmitting, by the server to the user device, an authentication request comprising a challenge, a user identifier that identifies a user, and the common domain to which the device credential is scoped;

receiving, by the server from the user device, a response;

accessing, by the server, the device credential, the device credential having been stored by the payment network, the payment network being assigned with the sub-domain of the common domain to share the scope with other ones of the plurality of payment networks;

validating, by the server, the response based on the device credential; and

causing, by the server, the user identifier and the device credential to be federated to the other ones of the plurality of payment networks based on the validating.

2. The method of claim 1 , wherein receiving the first request comprises:

receiving the first request via an authentication interface of the payment network, the sub-domain resolving to the authentication interface based on the redirection from the sub-domain to the domain name.

3. The method of claim 1 , wherein the response comprises digitally signed data signed based on the challenge and a private key created with the device credential as a key pair, and wherein validating the response further comprises:

decrypting the digitally signed data based on the device credential; and

verifying that the user device has possession of the private key based on the decrypting.

4. The method of claim 1 , wherein the response encodes an origin of the authentication request, and wherein validating the response further comprises:

determining that the origin encoded in the response matches the common domain even though the common domain is different from the domain name associated with the payment network.

5. The method of claim 1 , wherein transmitting the authentication request comprises:

transmitting an application programming interface (API) call to an authenticator API of the user device; and

controlling, based on the API call, an authenticator of the user device to digitally sign data comprising the challenge.

6. The method of claim 5 , wherein determining that the digitally signed data was digitally signed by the user device comprises:

decrypting the digitally signed data based on the device credential and an encryption technique used by the authenticator; and

determining that the decrypted digitally signed data includes the challenge.

7. The method of claim 1 , wherein the payment network implements a secure remote commerce (SRC) specification that facilitates SRC payments through the plurality of payment networks, wherein accessing the request to authenticate the user device comprises:

receiving the first request to authenticate the user device from an SRC initiator (SRCI) that initiates a payment transaction as an SRC payment to a merchant and transmits the first request to the sub-domain assigned to the payment network.

8. The method of claim 7 , further comprising:

redirecting back to the SRCI after validating the response;

identifying, by the SRCI, a payment credential for the SRC payment after validating the response;

federating, by the server or the SRCI, the user identifier and the device credential prior to processing the SRC payment;

receiving, at a digital card facilitator (DCF) associated with the payment network, a redirection from the SRCI to confirm the SRC payment; and

forwarding, by the SRCI to the merchant, the identified payment credential.

9. The method of claim 8 , further comprising:

processing the SRC payment based on the payment credential.

10. The method of claim 1 , further comprising:

accessing a registration request to register the user device, the registration request being redirected from the sub-domain assigned to the payment network to the domain name associated with the payment network.

11. A system of authenticating a user device via a device credential scoped to a common domain shared among a plurality of payment networks, each payment network having a respective domain name different than the common domain and each payment network being assigned with a respective sub-domain of the common domain, the system comprising:

a server of a payment network among the plurality of payment networks, the server to:

receive a first request redirected from a sub-domain assigned to the payment network to a domain name associated with the payment network;

responsive to the first request, transmit, to the user device, an authentication request comprising a challenge, a user identifier that identifies the user, and the common domain to which the device credential is scoped;

receive, from the user device, a response;

access the device credential, the device credential having been stored by the payment network, the payment network being assigned with the sub-domain of the common domain to share the scope with other ones of the plurality of payment networks;

validate the response based on the device credential; and

cause the user identifier and the device credential to be federated to the other ones of the plurality of payment networks based on the validating.

12. The system of claim 11 , to receive the first request, the server is further to:

receive the first request via an authentication interface of the payment network, the sub-domain resolving to the authentication interface based on the redirection from the sub-domain to the domain name.

13. The system of claim 11 , wherein to transmit the authentication request, the server is further to:

transmit an application programming interface (API) call to an authenticator API of the user device; and

control, based on the API call, an authenticator of the user device to digitally sign data comprising the challenge.

14. The system of claim 11 , wherein the payment network implements a secure remote commerce (SRC) specification that facilitates SRC payments through the plurality of payment networks, wherein to access the request to authenticate the user device, the server is further to:

receive the first request to authenticate the user device from an SRC initiator (SRCI) that initiates a payment transaction as an SRC payment to a merchant and transmits the first request to the sub-domain assigned to the payment network.

15. The system of claim 14 , wherein server is further to:

redirect back to the SRCI after validating the response;

identify, by the SRCI, a payment credential for the SRC payment after validating the response;

federate, by the server or the SRCI, the user identifier and the device credential prior to processing the SRC payment;

receive, at a digital card facilitator (DCF) associated with the payment network, a redirection from the SRCI to confirm the SRC payment; and

forward, by the SRCI to the merchant, the identified payment credential.