Account identifier digitization abstraction
Described herein are various technologies pertaining to integrating account identifier (e.g., card provider(s)) into a digitization system, for example, without requiring changes to a client application on a user device (e.g., smart phone). An extensible account identifier abstraction system is provided that stores data according to a unified data model and is accessible to the user device via unified interface(s). The extensible abstraction system includes one or more plugin modules/provider relay plugin(s) that convert call(s) to the unified interface(s) and data stored according to the unified data model into provider-specific call(s) with data formatted according to a provider-specific schema.
1. An extensible account identifier digitization abstraction system, comprising:
a computer comprising a processor and a memory, the memory comprising:
a management coordinator component configured to receive a request from a user device, identify a provider associated with the request, provide the request to a provider plugin module associated with the identified provider, wherein the request is associated with an integrated chip card, the management coordinator component further configured to emulate the integrated chip card based on a card profile stored in a data store;
the provider plugin module configured to convert the received request based on a provider-specific contract, provide the converted request to the identified provider using a provider relay plugin; and
the provider relay plugin configured to securely communicate with the identified provider.
2. The system of claim 1 , further comprising an authentication component configured to authenticate the user device to the extensible account identifier digitization abstraction system.
3. The system of claim 2 , wherein authentication of the user device is based on a token stored on the user device.
4. The system of claim 1 , wherein the request is received via a unified interface.
5. The system of claim 4 , wherein the unified interface comprises an application programming interface.
6. The system of claim 1 , the provider plugin module further configured to convert data stored in a unified data model into a data schema utilized by the identified provider.
7. The system of claim 1 , further comprising a secure data store storing limited use transaction credentials issued by the identified provider for generating a cryptogram during a transaction time, the limited use credentials utilized by the provider relay plugin during secure communication with the identified provider.
8. The system of claim 1 , wherein the request comprises a management operation.
9. The system of claim 8 , wherein the management operation comprises at least one of enrolling a digitized card, resuming digitized card enrollment, canceling a digitized card enrollment, processing a provider notification, handling an unknown state or querying digitized card metadata.
10. The system of claim 1 , wherein the request comprises a transaction-related operation.
11. The system of claim 10 , wherein the transaction-related operation comprises at least one of provision of a card profile or provision transaction credentials.
12. A method of utilizing an extensible account identifier abstraction system to facilitate an operation, comprising:
receiving a request using a unified interface;
identifying a provider associated with the request;
providing the request to a plugin module associated with the identified provider;
identifying stored data associated with the request by the plugin module, converting the stored data into data formatted according to a provider-specific schema;
providing the converted stored data to the identified provider;
by the plugin module, converting the request based on a provider-specific contract; and
providing the converted request to the identified provider.
13. The method of claim 12 , further comprising:
receiving a response to the converted request from the provider; and
providing the response to the user device.
14. The method of claim 12 , further comprising:
authenticating the user device using a token that uniquely identifies a user device that sent the request.
15. A computer storage media storing computer-readable instructions that when executed cause a computing device to:
receive a request using a unified interface;
identify a provider associated with the request;
provide the request to a plugin module associated with the identified provider;
identify stored data associated with the request;
by the plugin module, convert the stored data into data formatted according to a provider-specific schema;
provide the converted stored data to the identified provider;
by the plugin module, convert the request based on a provider-specific contract; and
provide the converted request to the identified provider.
16. The computer storage media of claim 15 , storing further computer-readable instructions that when executed case the computing device to:
receive a response to the converted request from the provider; and
provide the response to the user device.
17. The computer storage media of claim 15 , storing further computer-readable instructions that when executed case the computing device to:
authenticate the user device using a token that uniquely identifies a user device that sent the request.