Intelligent Dynamic Authentication and Event Processing System

1. A computing platform, comprising: at least one processor; a communication interface communicatively coupled to the at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to: receive a request to process an event, the request to process the event including event details; responsive to receiving the request to process the event, executing an instruction to transfer an amount of funds from a first account to a second, temporary account; generate, based on machine learning datasets and based on the received request to process the event, a first profile for a first user who is a first party to the event and a second profile for a second user who is a second party, the first user profile being unique to the first user and including information identifying the first user, account information of the first user, and an amount associated with the event, and the second user profile being unique to the second user and including information identifying the second user, account information of the second user, and the amount associated with the event; anonymize data in the first profile for the first user including generating an identifier representing the data in the first profile for the first user; transmit, to a first user device of the first user, the first profile for the first user including the identifier representing the data in the first profile for the first user; transmit, to a second user device of the second user, the second profile for the second user; receive a first authorization to process the event, the first authorization including the identifier representing the data from the first profile for the first user; execute a look-up function based on the identifier to identify the anonymized data; determine whether a triggering event has occurred; responsive to determining that the triggering event has occurred, analyze the triggering event to determine a type of triggering event; responsive to determining that the triggering event is a first type of triggering event, and based, at least in part, on the identified anonymized data, transferring the amount of funds from the second, temporary account to a third account different from the first account and the second, temporary account, the first type of triggering event including a second authorization, the second authorization including approval to proceed with transferring the amount of funds based on at least receiving, from the first user device of the first user the first user profile and from the second user device of the second user the second user profile, the first user profile and the second user profiles being tokens to authenticate the first party and the second party; and responsive to determining that the triggering event is a second type of triggering event, denying the request to process the event and transferring the amount of funds from the second, temporary account to the first account, wherein the second type of triggering event includes a request to cancel the event.

2. The computing platform of claim 1 , wherein anonymizing data in the first profile of the first user is performed prior to transmitting the first profile for the first user to the first user device of the first user.

3. The computing platform of claim 1 , further including instructions that, when executed, cause the computing platform to: prior to transmitting the second profile for the second user to the second user device of the second user, anonymizing data in the second profile for the second user.

4. The computing platform of claim 1 , further including instructions that, when executed, cause the computing platform to: after one of: transferring the amount of funds from the second, temporary account to the third account and transferring the amount of funds from the second, temporary account to the first account, deleting the generated first profile for the first user and second profile for the second user to prevent them from being used as authenticating data in subsequent requests to process events.

5. The computing platform of claim 1 , wherein the first account is associated with the first user and the third account is associated with the second user.

6. The computing platform of claim 5 , wherein the second, temporary account is associated with an entity.

7. The computing platform of claim 1 , wherein receiving the first authorization to process the event includes receiving an indication that the first profile of the first user was transmitted from the first user device of the first user to the second user device of the second user.

8. A method, comprising: at a computing platform comprising at least one processor, memory, and a communication interface: receiving, by the at least one processor and via the communication interface, a request to process an event, the request to process the event including event details; responsive to receiving the request to process the event, executing, by the at least one processor, an instruction to transfer an amount of funds from a first account to a second, temporary account; generating, by the at least one processor and based on machine learning datasets, and based on the received request to process the event, a first profile for a first user who is a first party to the event and a second profile for a second user who is a second party, the first user profile being unique to the first user and including information identifying the first user, account information of the first user, and an amount associated with the event, and the second user profile being unique to the second user and including information identifying the second user, account information of the second user, and the amount associated with the event; anonymizing, by the at least one processor, data in the first profile for the first user including generating an identifier representing the data in the first profile for the first user transmitting, by the at least one processor and to a first user device of the first user via the communication interface, the first profile for first user including the identifier representing the data in the first profile for the first user; transmitting, by the at least one processor and to a second user device of the second user via the communication interface, the second profile for the second user; receiving, by the at least one processor and via the communication interface, a first authorization to process the event, the first authorization including the identifier representing the data from the first profile for the first user; executing, by the at least one processor, a look-up function based on the identifier to identify the anonymized data; determining, by the at least one processor, whether a triggering event has occurred; responsive to determining that the triggering event has occurred, analyzing, by the at least one processor, the triggering event to determine a type of triggering event; responsive to determining that the triggering event is a first type of triggering event, and based, at least in part, on the identified anonymized data, transferring, by the at least one processor, the amount of funds from the second, temporary account to a third account different from the first account and the second, temporary account, the first type of triggering event including a second authorization, the second authorization including approval to proceed with transferring the amount of funds based on at least receiving, from the first user device of the first user the first user profile and from the second user device of the second user the second user profile, the first user profile and the second user profiles being tokens to authenticate the first party and the second party; and responsive to determining that the triggering event is a second type of triggering event, denying, by the at least one processor, the request to process the event and transferring the amount of funds from the second, temporary account to the first account, wherein the second type of triggering event includes a request to cancel the event.

9. The method of claim 8 , wherein anonymizing data in the first profile of the first user is performed prior to transmitting the first user profile for the first user to the first user device of the first user.

10. The method of claim 8 , further including: prior to transmitting the second profile for the second user to the second user device of the second user, anonymizing data in the second profile for the second user.

11. The method of claim 8 , further including: after one of: transferring the amount of funds from the second, temporary account to the third account and transferring the amount of funds from the second, temporary account to the first account, deleting the generated first profile for the first user and second profile for the second user to prevent them from being used as authenticating data in subsequent requests to process events.

12. The method of claim 8 , wherein the first account is associated with the first user and the third account is associated with the second user.

13. The method of claim 12 , wherein the second, temporary account is associated with an entity.

14. The method of claim 8 , wherein receiving the first authorization to process the event includes receiving an indication that the first profile of the first user was transmitted from the first user device of the first user to the second user device of the second user.

15. One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, memory, and a communication interface, cause the computing platform to: receive a request to process an event, the request to process the event including event details; responsive to receiving the request to process the event, executing an instruction to transfer an amount of funds from a first account to a second, temporary account; generate, based on machine learning datasets, and based on the received request to process the event, a first profile for a first user who is a first party to the event and a second profile for a second user who is a second party, the first user profile being unique to the first user and including information identifying the first user, account information of the first user, and an amount associated with the event, and the second user profile being unique to the second user and including information identifying the second user, account information of the second user, and the amount associated with the event; anonymize data in the first profile for the first user including generating an identifier representing the data in the first profile for the first user; transmit, to a first user device of the first user, the first profile for the first user including the identifier representing the data in the first profile for the first user; transmit, to a second user device of the second user, the second profile for the second user; receive a first authorization to process the event, the first authorization including the identifier representing the data from the first profile for the first user; execute a look-up function based on the identifier to identify the anonymize data; determine whether a triggering event has occurred; responsive to determining that the triggering event has occurred, analyze the triggering event to determine a type of triggering event; responsive to determining that the triggering event is a first type of triggering event, and based, at least in part, on the identified anonymized data, transferring the amount of funds from the second, temporary account to a third account different from the first account and the second, temporary account, the first type of triggering event including a second authorization, the second authorization including approval to proceed with transferring the amount of funds based on at least receiving, from the first user device of the first user the first user profile and from the second user device of the second user the second user profile, the first user profile and the second user profiles being tokens to authenticate the first party and the second party; and responsive to determining that the triggering event is a second type of triggering event, denying the request to process the event and transferring the amount of funds from the second, temporary account to the first account, wherein the second type of triggering event includes a request to cancel the event.

16. The one or more non-transitory computer-readable media of claim 15 , wherein anonymizing data in the first profile of the first user is performed prior to transmitting the first profile for the first user to the first user device of the first user.

17. The one or more non-transitory computer-readable media of claim 15 , further including instructions that, when executed, cause the computing platform to: prior to transmitting the second profile for the second user to the second user device of the second user, anonymizing data in the second profile for the second user.

18. The one or more non-transitory computer-readable media of claim 15 , further including instructions that, when executed, cause the computing platform to: after one of: transferring the amount of funds from the second, temporary account to the third account and transferring the amount of funds from the second, temporary account to the first account, deleting the generated first profile for the first user and second profile for the second user to prevent them from being used as authenticating data in subsequent requests to process events.

19. The one or more non-transitory computer-readable media of claim 15 , wherein the first account is associated with the first user and the third account is associated with the second user.

20. The one or more non-transitory computer-readable media of claim 19 , wherein the second, temporary account is associated with an entity.

21. The one or more non-transitory computer-readable media of claim 15 , wherein receiving the first authorization to process the event includes receiving an indication that the first profile of the first user was transmitted from the first user device of the first user to the second user device of the second user.