# US 2013/0275296 A1 · Proximal Customer Transaction Incented By Donation of Auto-Boarded Merchant

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

- Number: US 2013/0275296 A1
- Document ID: US20130275296A1
- Status: Published application
- Kind: A1
- Application number: 13/834,984
- Filed: 2013-03-15
- Published: 2013-10-17
- Earliest claimed: 2012-03-16
- Assignees: esdatanetworks INC
- Inventors: Terrance Patrick Tietzen; Matthew Arnold Macpherson Bates; William Gordon Robertson
- Web page: https://patentgrep.com/patent/US20130275296A1

## CPC

- G06Q 30/0279: Fundraising management
- G06Q 30/02: Marketing; Price estimation or determination; Fundraising
- G06Q 30/0207: Discounts or incentives, e.g. coupons or rebates
- G06Q 30/06: Buying, selling or leasing transactions
- G06Q 50/26: Government or public services (business processes related to the transportation industry G06Q50/40)
- 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

Address, time, and rules obligating donee donations are auto-populated for merchants whose authorization responses for transactions conducted on accounts are used to obtain account holders' travel time to the merchants'. When travel time is proximal to the auto-populated time, the rule and the transaction currency amount are used to calculate the merchant's donee donation, which donation can be messaged for auditing of donations paid and payable. A predetermined time after each such transaction, the merchant is sent a notice as to the difference between obligatory donee donations and the donee donations received. Auto-populated addresses, times, and rules are amendable by the merchant, and the donee amendable by the account holder, whereby the merchant selects the donation, and the account holder selects the donee. Answers to account holder surveys, upon receipt, increments currencies for account holder or donee with greater increment for fast answers.

## Claims

### Claim 1

A method comprising a plurality of steps each being performed by hardware executing software, wherein the steps include:
obtaining from one or more databases, using information derived from a Globally Unique Identifier (GUID) for a merchant, merchant data for the merchant that includes:
a geographic address for the merchant;
a default affinity entity;
a default maximum travel time to the geographic address for the merchant; and
a default business rule obligating the merchant to donate to the affinity entity;
storing the merchant data for the merchant in one or more databases; and
processing information derived from an authorization response for a transaction conducted by the merchant on an account issued to an account holder, wherein the information includes identifiers for the merchant and for the account holder and a currency amount of the transaction, by:
retrieving, using the identifier for the merchant, at least a portion of the stored merchant data for the merchant;
accessing from one or more databases, using information derived from the identifier for the account holder, account holder data for the account holder that includes a geographic address for the account holder;
inquiring, using the geographic addresses for the account holder and the merchant, the travel time from the geographic address of the account holder to the geographic address of the merchant; and
if the inquired travel time is within a predetermined tolerance of the default maximum travel time, deriving, using the default business rule and the currency amount of the transaction, a donation to be made by the merchant to the default affinity entity.

### Claim 2 (depends on 1)

The method as defined in claim 1, wherein the steps further comprise repeating:
the obtaining and storing steps for each of a plurality of said merchants; and
the processing step for each of a plurality of said transactions.

### Claim 3 (depends on 2)

The method as defined in claim 2, wherein the processing step further comprises transmitting a message to a logical address of the merchant containing the donation to be made by the merchant to the default affinity entity.

### Claim 4 (depends on 3)

The method as defined in claim 3, wherein the logical address to which the message and the determined difference are transmitted is selected from the group consisting of:
a logical address for the merchant;
a logical address for the account holder;
a logical address of the affinity entity;
a logical address of an agent for at least one of the merchant, the account holder and the affinity entity; and
a combination thereof.

### Claim 5 (depends on 2)

The method as defined in claim 2, wherein the steps further comprise, a predetermined time period after said plurality of said transactions:
receiving a plurality of donation receipts, wherein:
each said donation receipt includes:
identifiers for the merchant and the default affinity entity; and
a currency amount donated by the merchant to the default affinity entity;
and
for each said default affinity entity and each said merchant:
determining a difference between the sum of:
the donations to be made by the merchant to the default affinity entity in the messages to the logical address of the merchant; and
the currency amount donated by the merchant to the default affinity entity in the donation receipts;
and
transmitting the determined difference to a logical address.

### Claim 6 (depends on 5)

The method as defined in claim 5, wherein the logical address to which the determined difference is transmitted is selected from the group consisting of:
a logical address for the merchant;
a logical address for the account holder;
a logical address of the affinity entity;
a logical address of an agent for at least one of the merchant, the account holder and the affinity entity; and
a combination thereof.

### Claim 7 (depends on 2)

The method as defined in claim 2, wherein:
each said transaction occurs in a payment processing system that includes a plurality of said merchants each conducting each said transaction on a respective said account issued to a respective said account holder by a respective issuer;
each said transaction on each said account is acquired for clearing and settlement by an acquirer for each said merchant through a transaction handler in communication with both the issuer of the account and the acquirer for the merchant; and
the issuer sends a corresponding said authorization response for the transaction to the merchant through the transaction handler and the acquirer in response to an authorization request sent to the issuer from the merchant through the transaction handler and the acquirer.

### Claim 8 (depends on 2)

The method as defined in claim 2, wherein prior to repeating the processing step for each of a plurality of said transaction, receiving and making replacement changes for at least one:
said merchant to at least one of:
the default affinity entity corresponding to the geographic address for the merchant;
the default maximum travel time to the geographic address for the merchant; and
the default business rule obligating the merchant to donate to the affinity entity;
and
said account holder to the default affinity entity for a donation that is to be made by the merchant for each said transaction with said account holder.

### Claim 9 (depends on 1)

The method as defined in claim 1, wherein the default affinity entity corresponds to the geographic address for the merchant.

### Claim 10 (depends on 2)

The method as defined in claim 2, wherein the processing step further comprises transmitting a message to a logical address of the merchant containing the donation to be made by the merchant to the default affinity entity.

### Claim 11 (depends on 2)

The method as defined in claim 2, wherein the processing step further comprises, for each transaction:
transmitting a message containing a question to a logical address of the account holder; and
after receiving, in response to the question, an answer:
incrementing a loyalty currency attributed to at least one of the account holder and the default affinity entity; and
transmitting a message to the logical address of the account holder containing acknowledgement of the increment to the loyalty currency.

### Claim 12 (depends on 11)

The method as defined in claim 11, wherein when the time lapse between the question transmitted and the answer received is within a predetermined tolerance, the increment to the loyalty currency is greater than the increment if the time lapse is not within the predetermined tolerance.

### Claim 13 (depends on 11)

The method as defined in claim 11, wherein the steps further comprise transmitting a message containing the answer to a logical address for at least one of the merchant and an agent of the merchant.

### Claim 14 (depends on 1)

A non-transient computer readable medium comprising software executed by hardware to perform the steps of the method as defined in claim 1.

### Claim 15

A method comprising a plurality of steps each being performed by hardware executing software, wherein the steps include:
auto-populating, for a merchant, an address, duration, and a rule obligating a donation to a donee;
using information from an authorization response for a transaction conducted by the merchant on an account of an account holder to obtain a travel time of the account holder from its address to the auto-populated address; and
when travel time is within a predetermined threshold of the auto-populated duration, deriving a donation, using the auto-populated rule and a currency amount of the transaction, that the merchant is obligated to make to the auto-populated donee.

### Claim 16 (depends on 15)

The method as defined in claim 15, wherein the steps further comprise repeating:
the auto-populating step for each of a plurality of said merchants; and
the obtain step and the deriving step for each of a plurality of said transactions.

### Claim 17 (depends on 16)

The method as defined in claim 16, wherein the deriving step further comprises, for each transaction:
transmitting a message containing a question to a logical address of the account holder; and
after receiving, in response to the question, an answer:
incrementing a loyalty currency attributed to at least one of the account holder and the auto-populated donee; and
transmitting a message to the logical address of the account holder containing acknowledgement of the increment to the loyalty currency.

### Claim 18 (depends on 17)

The method as defined in claim 17, wherein when the time lapse between the question transmitted and the answer received is within a predetermined tolerance, the increment to the loyalty currency is greater than the increment if the time lapse is not within the predetermined tolerance.

### Claim 19 (depends on 15)

A non-transient computer readable medium comprising software executed by hardware to perform the steps of the method as defined in claim 15.

### Claim 20

A method comprising a plurality of steps each being performed by hardware executing software, wherein the steps include:
auto-populating, for each of a plurality of merchants, an address, duration, and a rule obligating a donation to a donee;
for each of a plurality of transactions between respective said merchants and respective account holders on an account issued to the account holder:
using information from an authorization response for the transaction to obtain a travel time from an address retrieved for the account holder to the auto-populated address for the merchant; and
when the obtained travel time is within a predetermined threshold of the auto-populated duration for the merchant, deriving a donation, using the auto-populated rule for the merchant and a currency amount of the transaction, that the merchant is obligated to make to the auto-populated donee.

### Claim 21 (depends on 20)

The method as defined in claim 20, wherein the steps further comprise repeating:
the auto-populating step for each of a plurality of said merchants; and
the obtain step and the deriving step for each of a plurality of said transactions.

### Claim 22 (depends on 21)

The method as defined in claim 21, wherein the deriving step further comprises, for each transaction:
transmitting a message containing a question to a logical address of the account holder; and
after receiving, in response to the question, an answer:
incrementing a loyalty currency attributed to at least one of the account holder and the auto-populated donee; and
transmitting a message to the logical address of the account holder containing acknowledgement of the increment to the loyalty currency.

### Claim 23 (depends on 21)

The method as defined in claim 21, wherein:
each said transaction occurs in a payment processing system that includes a plurality of said merchants each conducting each said transaction on a respective said account issued to a respective said account holder by a respective issuer;
each said transaction on each said account is acquired for clearing and settlement by an acquirer for each said merchant through a transaction handler in communication with both the issuer of the account and the acquirer for the merchant; and
the issuer sends a corresponding said authorization response for the transaction to the merchant through the transaction handler and the acquirer in response to an authorization request sent to the issuer from the merchant through the transaction handler and the acquirer.

### Claim 24 (depends on 20)

A non-transient computer readable medium comprising software executed by hardware to perform the steps of the method as defined in claim 20.
