Card engine integration with backend systems

A network element, comprising:

• one or more processors;
• and
• memory storing computer-executable instructions associated with a card engine that is not compatible with an application programming interface (API) of a backend system associated with a service provider, wherein the computer-executable instructions, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
• receiving, by the card engine from an API Response as Card (ARC) engine, action data indicating a result of an account action, associated with a user account with the service provider, that was at least attempted by the backend system, wherein:
• the ARC engine intercepts an action request sent over a network to the card engine from a client application that:
• is not compatible with the API of the backend system,
• executes on a user equipment (UE) remotely from the card engine and the ARC engine, and
• is configured to visually display account information associated with the user account via user interface (UI) cards based on card data provided by the card engine,
• the ARC engine transmits an ARC action request to the backend system,
• wherein the ARC action request:
• corresponds to the action request and is based on the API of the backend system that the card engine and the client application are not compatible with, and
• causes the backend system to at least attempt to perform the account action associated with the user account,
• the ARC engine receives an action response, from the backend system based on the API of the backend system, indicating the result of the account action that was at least attempted by the backend system in response to the ARC action request, and
• the ARC engine transmits the action data to the card engine, the action data indicating the result, of the account action that was at least attempted by the backend system, in a fact data format interpretable by the card engine, instead of based on the API of the backend system that the card engine is not compatible with;
• selecting, by the card engine, a card format from among a plurality of visual card formats for UI cards to be presented via the client application, wherein the card format is selected based on the result, of the account action that was at least attempted by the backend system, indicated by the action data received by the card engine from the ARC engine;
• generating, by the card engine, a card data instance based on the card format and the action data, wherein the card data instance includes card content indicative of the result, of the account action that was at least attempted by the backend system, indicated by the action data received by the card engine from the ARC engine;
• and
• sending, by the card engine, the card data instance to the client application over the network,
• wherein the card data instance causes the client application to render and display, in a UI of the client application, a corresponding UI card that visually presents the card content, indicative of the result of the account action that was at least attempted by the backend system, based on the card format selected by the card engine.

One or more non-transitory computer-readable media storing computer-executable instructions associated with a card engine that is not compatible with an application programming interface (API) of a backend system associated with a service provider, wherein the computer-executable instructions, when executed by one or more processors of a network element, cause the one or more processors to perform operations comprising:

• receiving, by the card engine from an API Response as Card (ARC) engine, action data indicating a result of an account action, associated with a user account with the service provider, that was at least attempted by the backend system, wherein:
• the ARC engine intercepts an action request sent over a network to the card engine from a client application that:
• is not compatible with the API of the backend system,
• executes on a user equipment (UE) remotely from the card engine and the ARC engine, and
• is configured to visually display account information associated with the user account via user interface (UI) cards based on card data provided by the card engine,
• the ARC engine transmits an ARC action request to the backend system,
• wherein the ARC action request:
• corresponds to the action request and is based on the API of the backend system that the card engine and the client application are not compatible with, and
• causes the backend system to at least attempt to perform the account action associated with the user account,
• the ARC engine receives an action response, from the backend system based on the API of the backend system, indicating the result of the account action that was at least attempted by the backend system in response to the ARC action request, and
• the ARC engine transmits the action data to the card engine, the action data indicating the result, of the account action that was at least attempted by the backend system, in a fact data format interpretable by the card engine, instead of based on the API of the backend system that the card engine is not compatible with;
• selecting, by the card engine, a card format from among a plurality of visual card formats for UI cards to be presented via the client application, wherein the card format is selected based on the result, of the account action that was at least attempted by the backend system, indicated by the action data received by the card engine from the ARC engine;
• generating, by the card engine, a card data instance based on the card format and the action data, wherein the card data instance includes card content indicative of the result, of the account action that was at least attempted by the backend system, indicated by the action data received by the card engine from the ARC engine;
• and
• sending, by the card engine, the card data instance to the client application over the network,
• wherein the card data instance causes the client application to render and display, in a UI of the client application, a corresponding UI card that visually presents the card content, indicative of the result of the account action that was at least attempted by the backend system, based on the card format selected by the card engine.