Systems and methods of verifying origin of request for payment

A non-transitory computer readable storage medium, including instructions stored thereon, which instructions, when read and executed by one or more computer processors, cause the one or more computer processors to perform steps comprising:

• maintaining, by a financial institution, a payment domain and a certificate of domain for the payment domain;
• providing, by the financial institution, a trusted application, wherein the trusted application includes an embedded certificate of domain, and wherein the embedded certificate of domain corresponds to the certificate of domain for the payment domain;
• receiving, by a financial institution computer program executed by a financial institution backend of the financial institution, a request, wherein:
• the request is for a payment URL;
• and
• the request is received directly from a merchant computing device;
• generating, by the financial institution computer program, the payment URL, wherein:
• the payment URL comprises a pointer to a network location for the financial institution and the pointer is based on a session identifier;
• the payment URL is associated with a transaction made by a customer of the financial institution using a customer electronic device;
• the payment URL maps to the payment domain maintained by the financial institution;
• and
• the payment URL includes a deep-link association with the trusted application;
• sending, by the financial institution computer program and via short messaging service (SMS), the payment URL directly to the customer electronic device;
• activating, by the customer electronic device in response to user input, the payment URL;
• providing, by the customer electronic device, a prompt to download the trusted application after the user activation of the payment URL;
• executing, by the customer electronic device and in response to the user activation of the payment URL, the trusted application via the deep-link association with the trusted application included in the payment URL;
• sending, by the trusted application, the embedded certificate of domain to the financial institution computer program;
• receiving, by the financial institution computer program and from the trusted application executed by the customer electronic device, the embedded certificate of domain;
• comparing, by the financial institution computer program, the embedded certificate of domain to the certificate of domain for the payment domain;
• in response to the comparison, determining a match between the embedded certificate of domain and the certificate of domain for the payment domain;
• in response to the determination of the match, presenting, by the financial institution computer program to the customer electronic device, a payment web page;
• receiving, at the payment web page, payment details from the customer electronic device;
• and
• executing, by the financial institution computer program, the transaction using the payment details.