# US 2015/0106246 A1 · Systems and methods for secure financial transactions

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

- Number: US 2015/0106246 A1
- Document ID: US20150106246A1
- Status: Published application
- Kind: A1
- Application number: 14/279,532
- Filed: 2014-05-16
- Published: 2015-04-16
- Earliest claimed: 2011-11-16
- Applicants: Mineraltree, Inc.
- Inventors: Bagepalli C. Krishna
- Web page: https://patentgrep.com/patent/US20150106246A1

## CPC

- G06Q 40/12: Accounting
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

According to another example, a payment directory system is provided. The payment directory system includes a payment directory executed by at least one computer system. The payment directory is configured to receive information descriptive of a first payment subdirectory administered by a financial institution. This information includes associations between a subdirectory identifier of the first payment subdirectory and a plurality of identifiers of payees. The payment directory is also configured to store the information and transmit, via the at least one network interface, data descriptive of at least a portion of the information. This data is transmitted to a second payment subdirectory different from the first payment subdirectory. The data includes at least one association between the subdirectory identifier and an identifier from the plurality of identifiers of payees.

## Claims

### Claim 1

A payment directory system comprising:
a payment directory executed by at least one computer system including memory, at least one network interface, and at least one processor coupled to the memory and the at least one network interface, the payment directory being configured to:
receive information descriptive of a first payment subdirectory administered by a financial institution, the information including associations between a subdirectory identifier of the first payment subdirectory and a plurality of identifiers of payees, the plurality of identifiers of payees being representative of a plurality of holders of accounts with the financial institution;
store the information; and
transmit, to a second payment subdirectory different from the first payment subdirectory via the at least one network interface, data descriptive of at least a portion of the information, the data including at least one association between the subdirectory identifier and an identifier from the plurality of identifiers of payees.

### Claim 2 (depends on 1)

The payment directory system according to claim 1, wherein the payment directory is further configured to:
provide an interface configured to receive the information descriptive of the first payment subdirectory; and
receive the information descriptive of the first payment subdirectory via the interface.

### Claim 3 (depends on 2)

The payment directory system according to claim 2, wherein the interface includes at least one of a user interface and a subdirectory interface.

### Claim 4 (depends on 3)

The payment directory system according to claim 3, wherein the subdirectory interface is configured to receive the information descriptive of the first payment subdirectory from at least one of the first payment subdirectory and a third payment subdirectory.

### Claim 5 (depends on 4)

The payment directory system according to claim 4, wherein the plurality of identifiers of payees include public identifiers.

### Claim 6 (depends on 5)

The payment directory system according to claim 5, further comprising a plurality of payment subdirectories including the first, second, and third payment subdirectories, each payment subdirectory of the plurality of payment subdirectories being executed by one or more computer systems and being configured to:
receive payee information descriptive of a payee, the payee information including a private identifier of the payee and a public identifier of the payee;
store the payee information; and
transmit data descriptive of an association between the payment subdirectory and the public identifier.

### Claim 7 (depends on 6)

The payment directory system according to claim 6, wherein each payment subdirectory of the plurality of payment subdirectories is further configured to:
receive a request for information descriptive of a payee; and
transmit, responsive to the request, payee information regarding the payee.

### Claim 8

A method for providing a payment directory using at least one computer system including memory and at least one processor coupled to the memory, the method comprising:
receiving, by the at least one computer system, information describing a first payment subdirectory administered by a financial institution, the information associating a subdirectory with a plurality of payees, the plurality of payees including a plurality of holders of accounts with the financial institution;
storing the information; and
transmitting data descriptive of at least a portion of the information to a second payment subdirectory different from the first payment subdirectory, the data associating the subdirectory with at least one payee of the plurality of payees.

### Claim 9 (depends on 8)

The method according to claim 8, further comprising receiving the information describing the first payment subdirectory via an interface.

### Claim 10 (depends on 9)

The method according to claim 9, wherein receiving the information includes receiving the information via at least one of a user interface and a subdirectory interface.

### Claim 11 (depends on 10)

The method according to claim 10, wherein receiving the information via the subdirectory interface includes receiving the information from at least one of the first payment subdirectory and a third payment subdirectory.

### Claim 12 (depends on 11)

The method according to claim 11, wherein receiving the information includes receiving a plurality of public identifiers of payees.

### Claim 13 (depends on 12)

The method according to claim 12, further comprising:
receiving payee information describing a payee, the payee information including a private identifier of the payee and a public identifier of the payee;
storing the payee information; and
transmitting data associating the payment subdirectory with the public identifier.

### Claim 14 (depends on 13)

The method according to claim 13, further comprising:
receiving a request for information describing a payee; and
transmitting, responsive to the request, payee information describing the payee.

### Claim 15

A payment subdirectory system comprising:
a memory;
at least one network interface;
at least one processor coupled to the memory and the at least one network interface; and
a payment subdirectory executed by the processor and configured to:
receive payee information descriptive of at least one payee, the payee information including a private identifier of the at least one payee and a public identifier of the at least one payee;
store the payee information; and
transmit, to a payment directory via the at least one network interface, data descriptive of an association between the payment subdirectory and the public identifier.

### Claim 16 (depends on 15)

The payment subdirectory system according to claim 15, wherein the payment subdirectory is further configured to:
provide an interface configured to receive the payee information descriptive of the at least one payee; and
receive the payee information descriptive of the at least one payee via the interface.

### Claim 17 (depends on 16)

The payment subdirectory system according to claim 16, wherein the interface includes at least one of a user interface, a directory interface, and a subdirectory interface.

### Claim 18 (depends on 17)

The payment subdirectory system according to claim 17, wherein the subdirectory interface is configured to receive the payee information descriptive of the at least one payee from another payment subdirectory.

### Claim 19 (depends on 18)

The payment subdirectory system according to claim 18, wherein payment subdirectory is further configured to:
receive a request for information descriptive of a payee; and
transmit, responsive to the request, payee information descriptive of the payee.

### Claim 20 (depends on 19)

The payment subdirectory system according to claim 19, wherein the request includes an identifier of a requestor and the payment subdirectory is further configured to:
validate that the requestor is trusted; and
transmit payee information including the private identifier to the requestor.
