Systems and methods for providing notifications to devices

1. A system for providing time-sensitive push notifications to mobile devices of users attempting to complete a transaction, the system comprising:

one or more storage devices storing instructions; and

one or more processors coupled to the one or more storage devices, wherein the instructions cause the one or more processors to perform operations comprising:

receiving a first transaction notification indicating an attempted transaction;

in response to receiving the first transaction notification generating a push notification with a payload, the payload comprising:

a set of instructions to display a first graphical user interface (GUI) comprising an alert and an interactive icon, wherein the alert comprises alert information and a first message indicating that the attempted transaction can be approved, and wherein the interactive icon comprises a response element for confirming proceeding to approve the attempted transaction; and

a uniform resource identifier associated with the interactive icon that is initiated when the interactive icon is selected, wherein the uniform resource identifier comprises an action ID encoding a one-click response API call to communicate with a database and to update a user account, wherein the action ID indicates an action to perform with respect to the user account, and wherein the action ID indicates a transaction approval action;

transmitting the push notification to a mobile device associated with the user account;

receiving an electronic message from the mobile device, the electronic message generated in response to an interaction of a user with the interactive icon confirming proceeding to approve the transaction, wherein the electronic message comprises the uniform resource identifier that comprises the action ID;

determining the user account from the electronic message that is generated in response to the interaction with the interactive icon;

causing a second GUI to be displayed, wherein the second GUI enables the user to perform device level authentication with the mobile device;

updating database records of the user account based on the action ID, wherein updating the database records causes approval of the transaction; and

causing a third graphical user interface to be displayed on the mobile device indicating that the transaction has been approved.

2. The system of claim 1 , wherein updating the database records of the user account comprises processing the electronic message within a single communication channel.

3. The system of claim 1 , wherein the payload further comprises one or more instructions to display a graphical user interface comprising information identifying a merchant.

4. The system of claim 1 , wherein:

the response element is a response button; and

the uniform resource identifier defines a call-to-action of the response button.

5. The system of claim 1 wherein the push notification comprises a one-click response API call.

6. The system of claim 5 , wherein the one-click response API call:

configures directory paths comprising query parameters; and

returns a cookie ID in an HTTP response header.

7. The system of claim 5 , wherein the one-click response API call generates a web URL for a one-click interaction, the web URL encoding a customized interaction-specific web page.

8. The system of claim 5 , wherein the one-click response API call generates at least one of scripts or microdata routines to execute actions encoded in the action ID.

9. The system of claim 1 , wherein updating the database records of the user account comprises recording an incident in the database records of the user account.

10. The system of claim 1 , further comprising:

receiving device-level authentication; and

determining whether the device-level authentication is acceptable to complete the transaction.

11. The system of claim 10 , wherein the operations further comprise:

in response to determining that the device-level authentication is not acceptable, transmitting one or more instructions to the mobile device to launch a mobile application.

12. The system of claim 1 , wherein the operations further comprise:

after transmitting the push notification, determining whether an acknowledgement is received within a threshold time; and

in response to determining the acknowledgement was not received within the threshold time:

generating a website template including the uniform resource identifier; and

dispatching the website template through at least one of an email or an SMS.

13. The system of claim 1 , wherein:

the payload is a first payload;

the push notification is a first push notification;

the interactive icon is a first interactive icon; and

the operations further comprise:

generating a second push notification with a second payload, the second payload comprising:

a second alert specifying a merchant and a transaction amount; and

second interactive icons displaying survey options.

14. The system of claim 13 , wherein the second payload comprises one or more instructions for displaying an approved graphical user interface comprising a confirmation window, a confirmation icon, and a confirmation message.

15. The system of claim 1 , wherein transmitting the push notification comprises invoking a dispatching application program interface.

16. The system of claim 1 , wherein:

generating the push notification comprises receiving a transaction decline notification from a merchant, the transaction decline notification comprising the user account; and

the operations further comprise, after updating the database records, authorizing the transaction associated with the transaction decline notification while the user associated with the user account remains at a point of sale and without requiring launching of a mobile payment application.

17. The system of claim 1 , wherein:

the electronic message is received from an edge server; and

updating the database records comprises:

generating an implementation repository request workflow to access and update the user account; and

invoking a capability API to exchange information with a database.

18. The system of claim 17 , wherein invoking the capability API comprises using at least one of an elastic cache or an FPGA to process the implementation repository request workflow.

19. A non-transitory computer-readable medium storing instructions that, when executed by a processor, perform operations to provide time-sensitive push notifications to mobile devices of users attempting to complete a transaction, the operations comprising:

receiving a first transaction notification indicating an attempted transaction;

in response to receiving the first transaction notification generating a push notification with a payload, the payload comprising:

a set of instructions to display a first graphical user interface (GUI) comprising an alert and an interactive icon, wherein the alert comprises alert information and a first message indicating that the attempted transaction can be approved, and wherein the interactive icon comprises a response element for confirming proceeding to approve the attempted transaction; and

a uniform resource identifier associated with the interactive icon that is initiated when the interactive icon is selected, wherein the uniform resource identifier comprises an action ID encoding a one-click response API call to communicate with a database and to update a user account, wherein the action ID indicates an action to perform with respect to the user account, and wherein the action ID indicates a transaction approval action;

transmitting the push notification to a mobile device associated with the user account;

receiving an electronic message from the mobile device, the electronic message generated in response to an interaction of a user with the interactive icon confirming proceeding to approve the transaction, wherein the electronic message comprises the uniform resource identifier that comprises the action ID;

determining the user account from the electronic message that is generated in response to the interaction with the interactive icon;

causing a second GUI to be displayed, wherein the second GUI enables the user to authenticate with the mobile device;

updating database records of the user account based on the action ID, wherein updating the database records causes approval of the transaction; and

causing a third graphical user interface to be displayed on the mobile device indicating that the transaction has been approved.

20. A computer-implemented method for providing notifications to mobile devices, the computer-implemented method comprising:

receiving a first transaction notification indicating an attempted transaction;

in response to receiving the first transaction notification generating a push notification with a payload, the payload comprising:

a set of instructions to display a first graphical user interface (GUI) comprising an alert and an interactive icon, wherein the alert comprises alert information and a first message indicating that the attempted transaction can be approved, and wherein the interactive icon comprises a response element for confirming proceeding to approve the attempted transaction; and

a uniform resource identifier associated with the interactive icon that is initiated when the interactive icon is selected, wherein the uniform resource identifier comprises an action ID encoding a one-click response API call to communicate with a database and to update a user account, wherein the action ID indicates an action to perform with respect to the user account, and wherein the action ID indicates a transaction approval action;

transmitting the push notification to a mobile device associated with the user account;

receiving an electronic message from the mobile device, the electronic message generated in response to an interaction of a user with the interactive icon confirming proceeding to approve the attempted transaction, wherein the electronic message comprises the uniform resource identifier that comprises the action ID;

determining the user account from the uniform resource identifier within the electronic message;

causing a second GUI to be displayed, wherein the second GUI enables the user to authenticate with the mobile device;

updating database records of the user account based on the action ID, wherein updating the database records causes approval of the attempted transaction; and

causing a third graphical user interface to be displayed on the mobile device indicating that the attempted transaction has been approved.