# US 2025/0094991 A1 · Systems and methods of verifying origin of request for payment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094991 A1
- Document ID: US20250094991A1
- Status: Published application
- Kind: A1
- Application number: 18/959,155
- Filed: 2024-11-25
- Published: 2025-03-20
- Earliest claimed: 2021-08-31
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: Jpmorgan Chase Bank, N.A.
- Inventors: Jasbir BANGA; Reetu RAJ BOK; Howard SPECTOR
- Web page: https://patentgrep.com/patent/US20250094991A1

## CPC

- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/3255: {using mobile network messaging services for payment, e.g. SMS}
- G06Q 20/3267: {In-app payments}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A method for verifying origin of request for payments may include a financial institution computer program: receiving a request for a payment URL from a merchant, the payment URL provided for a transaction with a customer; generating the payment URL, wherein the payment URL comprises a pointer to a network location for the financial institution; providing the payment URL to a customer electronic device; receiving, from the customer electronic device and at a browsed URL, a stored or pinned certificate of domain for the payment URL; (5) comparing the stored or pinned certificate of domain for the payment URL to a certificate of domain for the browsed URL; presenting a payment page in response to a match; and returning an error in response to a mismatch.

## Claims

### Claim at position 1

1-19. (canceled)

### Claim 20

A method, comprising:
maintaining, by a financial institution, a payment domain and a certificate of domain for a 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;
generating, by a financial institution computer program executed by a financial institution backend of the financial institution, a machine-readable code comprising a payment uniform resource locator (URL) embedded therein, wherein:
the payment URL comprises a pointer to a network location for the financial institution;
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;
communicating, by the financial institution computer program, the machine-readable code to a merchant point of sale device for a merchant;
scanning, by a customer electronic device, the machine-readable code that is displayed by the merchant point of sale device;
executing, by the customer electronic device and in response to a user scanning the machine-readable code as part of a transaction, the trusted application via the deep-link association with the trusted application included in the payment URL;
receiving, by the financial institution computer program and at the payment uniform resource locator and from the trusted application, 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, by the financial institution computer program, 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, by the financial institution computer program 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.

### Claim 21 (depends on 20)

The method of claim 20, wherein the trusted application executed by the customer electronic device comprises a computer program or a browser application.

### Claim 22 (depends on 20)

The method of claim 20, wherein the certificate of domain for the payment domain is an X.509 certificate.

### Claim 23 (depends on 20)

The method of claim 20, wherein the customer electronic device is a smartphone.

### Claim 24 (depends on 20)

The method of claim 20, wherein the customer electronic device is a laptop computer.

### Claim 25 (depends on 20)

The method of claim 20, further comprising:
crediting, by the financial institution computer program, a merchant account for payment.

### Claim 26

A system, comprising:
a financial institution backend for a financial institution, the financial institution backend executing a financial institution computer program;
a merchant point of sale device; and
a customer electronic device;
wherein:
the financial institution maintains a payment domain and a certificate of domain for a payment domain;
the financial institution provides 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;
the financial institution computer program generates a machine-readable code comprising a payment uniform resource locator (URL) embedded therein, wherein:
the payment URL comprises a pointer to a network location for the financial institution;
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;
the financial institution computer program communicates the machine-readable code to a merchant point of sale device for a merchant;
the customer electronic device scans the machine-readable code that is displayed by the merchant point of sale device;
the customer electronic device executes, in response to a user scanning the machine-readable code as part of a transaction, the trusted application via the deep-link association with the trusted application included in the payment URL;
the financial institution computer program receives, at the payment uniform resource locator and from the trusted application, the embedded certificate of domain;
the financial institution computer program compares the embedded certificate of domain to the certificate of domain for the payment domain;
in response to the comparison, the financial institution computer program determines 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, the financial institution computer program presents, to the customer electronic device, a payment web page;
the financial institution computer program receives, at the payment web page, payment details from the customer electronic device; and
the financial institution computer program executes the transaction using the payment details.

### Claim 27 (depends on 26)

The system of claim 26, wherein the trusted application executed by the customer electronic device comprises a computer program or a browser application.

### Claim 28 (depends on 26)

The system of claim 26, wherein the financial institution computer program credits a merchant account for payment.

### Claim 29 (depends on 26)

The system of claim 26, wherein the certificate of domain for the payment domain is an X.509 certificate.

### Claim 30 (depends on 26)

The system of claim 26, wherein the customer electronic device is a smartphone.

### Claim 31 (depends on 26)

The system of claim 26, wherein the customer electronic device is a laptop computer.
