Systems and methods for integrated third-party callbacks

1. A method comprising:

configuring, by a mobile device, a third-party callback to be performed after a triggering event is detected by a remote device associated with the mobile device;

determining, by the mobile device, that the mobile device is within a pre-determined proximity of the remote device;

receiving, by the mobile device and from the remote device, a message indicating that the triggering event has been detected;

sending, by the mobile device, an authentication request to authenticate the message;

receiving, by the mobile device, a response indicating the message is authenticated;

performing, by the mobile device and based on the message and the response, the third-party callback; and

sending, by the mobile device and to the remote device, a confirmation that the third-party callback has been performed.

2. The method of claim 1 , wherein the triggering event comprises authentication of biometric information on the remote device.

3. The method of claim 1 , wherein the triggering event comprises a determination that the remote device has entered a geographical location.

4. The method of claim 1 , wherein the message indicates an input command associated with the mobile device has been made on the remote device.

5. The method of claim 1 , wherein the receiving, by the mobile device and from the remote device, a message indicating that the triggering event has been detected comprises:

establishing a connection between the mobile device and the remote device; and

receiving the message through the connection.

6. The method of claim 5 , wherein the establishing a connection between the mobile device and the remote device further comprises:

receiving, by the mobile device and from the remote device, a ping packet; and

sending, by the mobile device and to the remote device, a reply.

7. The method of claim 1 , wherein the determining that the mobile device is within a pre-determined proximity to the remote device comprises:

broadcasting, by the mobile device and with a low transmission power, a connection request; and

receiving, by the mobile device and from the remote device, a reply.

8. The method of claim 1 , wherein the message further comprises a token, wherein the sending, by the mobile device, an authentication request further comprises:

sending the token to a remote platform to authenticate the message.

9. The method of claim 1 , wherein the determining that the mobile device is within a predetermined proximity to the remote device comprises:

receiving, by the mobile device and from the remote device, an indication that indicates a local network that the remote device is currently connected; and

determining, by the mobile device and based on the indication, that the mobile device is connected to the same local network.

10. The method of claim 1 , wherein the performing the third-party callback comprises:

opening an application on the mobile device; and

sending, through the application and to a third party, a service request.

11. A mobile device comprising:

one or more processors; and

memory configured to store computer instructions that, when executed by the one or more processors, cause the mobile device to perform actions comprising:

configuring, a third-party callback to be performed after a triggering event is detected by a remote device associated with the mobile device;

determining, that the mobile device is within a pre-determined proximity of the remote device;

receiving, from the remote device, a ping packet;

sending to the remote device, a reply to establish a connection between the mobile device and the remote device;

receiving, through the connection, a message indicating that the triggering event has been detected;

sending an authentication request to authenticate the message;

receiving a response indicating the message is authenticated;

performing, based on the message and the response, the third-party callback; and

sending, to the remote device, a confirmation that the third-party callback has been performed.

12. The mobile device of claim 11 , wherein the computer instructions are configured to cause the mobile device to determine that the mobile device is within a pre-determined proximity to the remote device by performing actions comprising:

broadcasting, by the mobile device and with a low transmission power, a connection request; and

receiving, by the mobile device and from the remote device, a reply.

13. The mobile device of claim 11 , wherein the message comprises a token, wherein the computer instructions are configured to cause the mobile device to send the authentication request by performing actions comprising:

receiving, from the remote device, a token; and

sending, to a remote platform, the token to authenticate the message.

14. The mobile device of claim 11 , wherein the computer instructions are configured to cause the mobile device to determine that the mobile device is within a predetermined proximity to the remote device by performing actions comprising:

receiving, from the remote device, an indication that indicates a local network that the remote device is currently connected; and

determining, based on the indication, that the mobile device is connected to the same local network.

15. The mobile device of claim 11 , wherein the computer instructions are further configured to cause the mobile device to perform the third-party callback by performing actions comprising:

opening an application on the mobile device; and

sending, through the application and to a third party, a service request.

16. A non-transitory computer-readable medium storing computer instruction that, when executed by one or more processors, cause performance of actions comprising:

configuring a third-party callback to be performed after a triggering event is detected by a remote device associated with a mobile device;

receiving, from the remote device, an indication that indicates a local network that the remote device is currently connected to;

determining, based on the indication, that the mobile device is connected to the same local network;

determining, based on the determination that the mobile device is connected to the same local network, that the mobile device is within a pre-determined proximity of the remote device;

receiving, from the remote device, a message indicating that the triggering event has been detected;

sending an authentication request to authenticate the message;

receiving a response indicating the message is authenticated;

performing, based on the message and the response, the third-party callback; and

sending, to the remote device, a confirmation that the third-party callback has been performed.

17. The non-transitory computer-readable medium of claim 16 , wherein the computer instructions are configured to receive the message indicating that the triggering event has been detected by causing performance of actions comprising:

establishing a connection between a mobile device and the remote device; and

receiving the message through the connection.

18. The non-transitory computer-readable medium of claim 17 , wherein the computer instructions are configured to establish the connection between the mobile device and the remote device by causing performance of actions comprising:

receiving, from the remote device, a ping packet; and

sending, to the remote device, a reply.

19. The non-transitory computer-readable medium of claim 16 , wherein the message comprises a token, and wherein the computer instructions are configured to send an authentication request by causing performance of actions comprising:

sending the token to a remote platform to authenticate the message.

20. The non-transitory computer-readable medium of claim 16 , wherein the computer instructions are configured to perform the third-party callback by cause performance of actions comprising:

opening an application on the mobile device; and

sending, through the application and to a third party, a service request.