Dynamic generation of digital messages with unique links for direct-to-merchant payments

A transaction management system for managing direct payer to payee payment transactions without need for any intermediate payment systems, the transaction management system comprising:

• a server having an electronic communications interface capable of receiving data from a payer computing device and a payee computing device via a digital communications network, wherein the server is associated with and is in electronic communication with a single trusted consumer banking service computing device associated with a consumer banking service where a user associated with the payer computing device holds a first financial account;
• wherein a dedicated application is installed on the payer computing device and the payee computing device and the dedicated application is configured to generate one or more user interfaces on each of the payer computing device and the payee computing device which allows for input of payment and account information;
• wherein the payer computing device interacts electronically with the server and the single trusted consumer banking service computing device, and wherein the payee computing device interacts electronically with the server but need not be associated with the single trusted consumer banking service computing device, wherein the payee computing device is associated with a gayer third party account associated with a third party payment processing system for processing payments received by the payee computing device;
• the server, comprising a memory configured to store instructions;
• and
• at least one processor configured to execute the stored instructions to perform steps comprising:
• receiving, by the server and from the payer computing device, an electronic payment transaction comprising a monetary value for the electronic payment transaction;
• identifying, by the server and based on receiving the electronic payment transaction, the first financial account from which to debit the monetary value for the electronic payment transaction;
• determining, by the server, whether the first financial account has sufficient funds from which to debit the monetary value for the electronic payment transaction;
• based on determining that the first financial account has sufficient funds from which to debit the monetary value for the electronic payment transaction, debiting the first financial account of the monetary value;
• crediting, by the server, a holding account established at the server separate from the first financial account with the monetary value for the electronic payment transaction;
• associating, within the memory, the electronic payment transaction with information associated with the first financial account, the monetary value, the holding account, and at least one state value, wherein the at least one state value is representative of a state of the electronic payment transaction;
• generating, by the server, a unique hyperlink associated with the electronic payment transaction, wherein the unique hyperlink is associated solely with the electronic payment transaction;
• storing, in the memory, in association with the electronic payment transaction, a hyperlink value representative of the unique hyperlink;
• transmitting, by the server, the unique hyperlink to the payer computing device;
• transmitting, by the payer computing device, the unique hyperlink to the payee computing device, by copying and pasting the unique hyperlink into a communications interface on the payer computing device, wherein following the unique hyperlink on the payee computing device will cause an application executing on the payee computing device to generate the one or more user interfaces associated with the electronic payment transaction;
• receiving, from a web server and in response to the payee computing device accessing the unique hyperlink, a request to deliver the one or more user interfaces associated with the electronic payment transaction to the payee computing device;
• determining, by the server, whether to deliver the one or more user interfaces associated with the electronic payment transaction to the payee computing device based on the at least one state value stored in the memory, wherein the at least one state value determines whether the unique hyperlink is valid or expired;
• based on determining to deliver the one or more user interfaces associated with the electronic payment transaction to the payee computing device, delivering, by the server, the one or more user interfaces associated with the electronic payment transaction to the payee computing device;
• receiving, from the one or more user interfaces on the payee computing device, debit card information associated with a second financial account associated with the payee computing device, wherein the debit card information is received directly from the one or more user interfaces and without a requirement to create an account;
• based on receiving the debit card information, performing a risk analysis that calculates a level of risk associated with the electronic payment transaction;
• transmitting, by the server and based on determining that the level of risk associated with the electronic payment transaction meets a threshold level, a debit instruction to the holding account, and a credit instruction to a second financial institution associated with the payee computing device to post a credit to the second financial account;
• and
• transmitting, by the server, to a plurality of third party payment processing systems associated with a plurality of payees, via a webhook URL/API electronic communication, payment transaction data between a plurality of payers and a plurality of payees, wherein the payer third party account with the third party payment processing system is automatically updated.