Abstract: This application describes an autonomous system for utilizing a non-fungible token (“NFT”) to manage dynamic operational conditions applied to bank account. The autonomous system may include a dynamic NFT stored on a distributed ledger. The dynamic NFT may include non-editable fields and editable fields. The autonomous system may include a static NFT stored on the distributed ledger. The dynamic and static NFTs may be linked to an account. The static NFT may define operating conditions for the non-editable account number. The autonomous system may include a smart contract that executes on the distributed ledger. The smart contract may detect a change in a value stored in the editable field of the dynamic NFT. The smart contract may locate operating conditions stored in the static NFT. Based on the operating conditions and the value, the smart contract may take action to manage the corresponding account.

Abstract: Apparatus and methods for utilizing non-fungible tokens (“NFTs”) for payment redemption and remittances are provided. A payor may use a computer program product to create an NFT. The NFT may include a digital envelope and metadata. The digital envelope may include one or more payment terms as a payment statement and the payment funds. The NFT may be transferred to a digital wallet belonging to a payee. The payee may select an option to redeem the payment funds. The payment funds may be transferred to the payee per the selection.

Abstract: A method for harnessing a connected network to securely verify and execute a transaction is provided. The method may include requesting a PIN from a mobile device. The request may be transmitted via a USSD message. The method may also include receiving the PIN from the mobile device. The PIN may be received via a response to the USSD message. The method may also include authenticating the mobile device. The method may also include accessing a third-party network to verify an authentication status of the mobile device. The third-party network may include a plurality of IoT endpoints. Each IoT endpoint may include a stored verification usage process. The stored verification usage process may relate to a user associated with the mobile device. The method may also include executing the transaction upon receipt of an authentication signal from the third-party network.

Abstract: A method for harnessing a connected network to securely verify and execute a transaction is provided. The method may include requesting a PIN from a mobile device. The request may be transmitted via a USSD message. The method may also include receiving the PIN from the mobile device. The PIN may be received via a response to the USSD message. The method may also include authenticating the mobile device. The method may also include accessing a third-party network to verify an authentication status of the mobile device. The third-party network may include a plurality of IoT endpoints. Each IoT endpoint may include a stored verification usage process. The stored verification usage process may relate to a user associated with the mobile device. The method may also include executing the transaction upon receipt of an authentication signal from the third-party network.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a dynamic endpoint engine. A computing platform may receive, from a client computing device, event definition information defining an event. Subsequently, the computing platform may receive, from a recipient computing device associated with the event, a request for a recipient-selection user interface, and may determine that a dynamic endpoint option is available for a user of the recipient computing device. Thereafter, the computing platform may send, to the recipient computing device, a delivery selection user interface that includes a user-selectable option that, when invoked, causes the computing platform to create a new endpoint.

Abstract: Apparatus and methods for utilizing distributed electronic ledger technology to process and record syndicated loan payments are provided. An agent address may receive an interest payment from a borrower address (e.g., interest accrual). The agent address may distribute the interest, pro rata, to members of a lender consortium and records the payments on the distributed electronic ledger. The distributed electronic ledger may provide and maintain a shared source of truth for event details associated with a syndicated loan. Facility agreements and corresponding utilizations (e.g., loans) may be represented on the distributed electronic ledger as smart contracts. As events occur, a corresponding record of each event is anchored to the facility/utilization smart contract, creating a chronological audit trail of all activity associated with the syndicated loan.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a dynamic endpoint engine. A computing platform may receive, from a client computing device, event definition information defining an event. Subsequently, the computing platform may receive, from a recipient computing device associated with the event, a request for a recipient-selection user interface, and may determine that a dynamic endpoint option is available for a user of the recipient computing device. Thereafter, the computing platform may send, to the recipient computing device, a delivery selection user interface that includes a user-selectable option that, when invoked, causes the computing platform to create a new endpoint.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a link discovery engine. A computing platform may receive event definition information defining an event. The computing platform may identify and validate one or more linked first client user accounts, and transmit to a host computing platform a response identifying user account information. The computing platform may transmit notification to a first recipient computing device. The computing platform may generate first event orchestration command(s) directing a first event processor to execute action(s) associated with the first event. The computing platform may transmit to the host computing platform, account reconciliation instructions.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a dynamic endpoint engine. A computing platform may receive, from a client computing device, event definition information defining an event. Subsequently, the computing platform may receive, from a recipient computing device associated with the event, a request for a recipient-selection user interface, and may determine that a dynamic endpoint option is available for a user of the recipient computing device. Thereafter, the computing platform may send, to the recipient computing device, a delivery selection user interface that includes a user-selectable option that, when invoked, causes the computing platform to create a new endpoint.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data with centralized event orchestration. A computing platform may receive, from a client computing device, event definition information defining an event. Subsequently, the computing platform may receive, from a recipient computing device associated with the event, a request for a delivery selection user interface. The computing platform may send the delivery selection user interface to the recipient computing device and may receive, from the recipient computing device, delivery selection information identifying a destination for the event selected by a user of the recipient computing device. Subsequently, the computing platform may generate one or more event orchestration commands directing an external event processor to execute one or more actions associated with the event, and may send the one or more event orchestration commands to the external event processor via an external event processing interface.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a link discovery engine. A computing platform may receive event definition information defining an event. Subsequently, the computing platform may receive a request for a recipient-selection user interface. The computing platform may mine alias data associated with a unique alias linked to a recipient computing device and may generate one or more relational user interface elements having relational content mined from the alias data. Then, the computing platform may send a delivery selection user interface having the one or more relational user interface elements to the recipient computing device. The computing platform may receive delivery selection information from the recipient computing device and may generate and send one or more event orchestration commands directing an event processor to execute one or more actions associated with the event.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator. A computing platform may receive event definition information defining an event as well as stimulus selection information. Subsequently, the computing platform may receive a request for a recipient-selection user interface. The computing platform may identify one or more stimulus options available for a user of a recipient computing device associated with the event and may send a delivery selection user interface that includes a user-selectable component, which, when invoked, causes the computing platform to create a new endpoint associated with a stimulus option. Thereafter, the computing platform may receive delivery selection information and may generate one or more event orchestration commands directing an event processor to execute one or more actions associated with the event.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data with centralized event orchestration. A computing platform may receive, from a client computing device, event definition information defining an event. Subsequently, the computing platform may receive, from a recipient computing device associated with the event, a request for a delivery selection user interface. The computing platform may send the delivery selection user interface to the recipient computing device and may receive, from the recipient computing device, delivery selection information identifying a destination for the event selected by a user of the recipient computing device. Subsequently, the computing platform may generate one or more event orchestration commands directing an external event processor to execute one or more actions associated with the event, and may send the one or more event orchestration commands to the external event processor via an external event processing interface.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a dynamic endpoint engine. A computing platform may receive, from a client computing device, event definition information defining an event. Subsequently, the computing platform may receive, from a recipient computing device associated with the event, a request for a recipient-selection user interface, and may determine that a dynamic endpoint option is available for a user of the recipient computing device. Thereafter, the computing platform may send, to the recipient computing device, a delivery selection user interface that includes a user-selectable option that, when invoked, causes the computing platform to create a new endpoint.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator and a link discovery engine. A computing platform may receive event definition information defining an event. Subsequently, the computing platform may receive a request for a recipient-selection user interface. The computing platform may mine alias data associated with a unique alias linked to a recipient computing device and may generate one or more relational user interface elements having relational content mined from the alias data. Then, the computing platform may send a delivery selection user interface having the one or more relational user interface elements to the recipient computing device. The computing platform may receive delivery selection information from the recipient computing device and may generate and send one or more event orchestration commands directing an event processor to execute one or more actions associated with the event.

Abstract: Aspects of the disclosure relate to multicomputer processing of client device request data using a centralized event orchestrator. A computing platform may receive event definition information defining an event as well as stimulus selection information. Subsequently, the computing platform may receive a request for a recipient-selection user interface. The computing platform may identify one or more stimulus options available for a user of a recipient computing device associated with the event and may send a delivery selection user interface that includes a user-selectable component, which, when invoked, causes the computing platform to create a new endpoint associated with a stimulus option. Thereafter, the computing platform may receive delivery selection information and may generate one or more event orchestration commands directing an event processor to execute one or more actions associated with the event.

Abstract: A system for monitoring one or more transactions includes a memory, which stores first metadata, second metadata, and third metadata, communicatively coupled to one or more processors. The one or more processors receive the first metadata from a first transaction processing system, the second metadata from a second transaction processing system, and the third metadata from a third transaction processing system and determine attributes from each of the first, second, and third metadata. Each of the first, second, and third metadata are associated with a task performed by the first, second, and third transaction processing systems, respectively. The one or more processors associate the first metadata with a first transaction. The one or more processors then determine that none of the attributes from the second metadata are the same as any of the attributes from the first metadata and then associate the second metadata with a second transaction.