# US 2010/0138324 A1 · Method of providing secure payment and transaction reconciliation

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

- Number: US 2010/0138324 A1
- Document ID: US20100138324A1
- Status: Published application
- Kind: A1
- Application number: 12/622,976
- Filed: 2009-11-20
- Published: 2010-06-03
- Earliest claimed: 2003-07-25
- Assignees: StoneEagle Services, Inc.
- Inventors: Robert M. Allen
- Web page: https://patentgrep.com/patent/US20100138324A1

## CPC

- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/0425: {the cheque being electronic only}
- G06Q 20/14: specially adapted for billing systems
- G06Q 20/385: {using an alias or single-use codes}
- 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/403: {Solvency checks}
- G06Q 30/04: Billing or invoicing
- G06Q 40/12: Accounting
- 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 of paying a merchant for a transaction associated with a program. The method including the steps of receiving a request from a merchant for a payment associated with a purchase, generating a payment identifier, generating a payment number having a predetermined limit amount and a predetermined expiration date, associating the payment identifier with the payment number and transmitting the payment number to the merchant for payment of the request.

## Claims

### Claim 1

A system for payment variance notification on program contracts, wherein the payment variance notification system communicates with program administrators and financial institutions via a network, and wherein the system comprises:
a memory storing an instruction set and data related to a plurality of authorized program payments; and
a processor for running the instruction set, the processor being in communication with the memory and the network, wherein the processor is operative to facilitate reconciliation and payment deviation notifications to program administrators by the operations of:
receiving data for the payment authorization from the program administrator computer, the data comprising one or more payment identification elements and a load amount, wherein the combination of payment identification elements uniquely identifies a transaction and forms a first transaction identifier;
receiving data for the payment transaction from the financial institution computer, the data comprising a second transaction identifier and a payment transaction amount, wherein the second transaction identifier is selected from the group consisting of the first transaction identifier and payment identification number;
comparing data for the load amount from the program administrator computer and the payment transaction amount from the financial institution computer to check for deviations;
transmitting notification to the program administrator of deviations between the payment transaction amount and the load amount substantially contemporaneously to the detection of said deviations in the comparing step, the notification comprising the first transaction identifier and the payment transaction amount; and
storing the received data from the bank computer for later dissemination to the program administrator.

### Claim 2 (depends on 1)

A payment variance notification system as recited in claim 1, wherein the processor is further operative to transmit payment authorizations to one or more merchants, the payment authorization comprising the second transaction identifier and a load amount.

### Claim 3 (depends on 1)

A payment variance notification system as recited in claim 1, wherein the processor is further operative to transmit payment by fax to one or more merchants, the payment by fax comprising a transaction identifier and a load amount.

### Claim 4 (depends on 3)

A payment variance notification system as recited in claim 3, wherein the processor is further operative to transmit notification to the program administrator of a failed payment by fax transmission, the notification comprising the first transaction identifier.

### Claim 5 (depends on 4)

A payment variance notification system as recited in claim 4, wherein the notification further comprises the time and description of the failed transmission.

### Claim 6 (depends on 4)

A payment variance notification system as recited in claim 4, wherein the notification further comprises a fax number associated with the failed transmission.

### Claim 7 (depends on 1)

A payment variance notification system as recited in claim 1, wherein the processor is further operative to transmit an authorization to a merchant, the authorization comprising a payment card number and an authorization amount, wherein the payment card number is operable in a card processor system and the authorization amount corresponds to the load amount.

### Claim 8 (depends on 7)

A payment variance notification system as recited in claim 7, wherein the authorization further comprises the second transaction identifier.

### Claim 9 (depends on 7)

A payment variance notification system as recited in claim 7, wherein the processor is further operative to detect declined transactions against a payment card number, wherein the detection of the declined transaction triggers a transmission of notification to a program administrator, the notification comprising a transaction identifier and the payment card number associated with the declined transaction.

### Claim 10 (depends on 9)

A payment variance notification system as recited in claim 9, wherein the notification further comprises the amount of the declined transaction.

### Claim 11 (depends on 1)

A payment variance notification system as recited in claim 1, wherein the processor is further operative to detect multiple payment transactions against a load amount, wherein the detection of a second or subsequent payment transaction triggers a transmission of notification to a program administrator, the notification comprising the first transaction identifier and the payment transaction amount.

### Claim 12 (depends on 11)

A payment variance notification system as recited in claim 11, wherein the notification further comprises the payment transaction amounts of prior payment transactions against the authorized load amount.

### Claim 13 (depends on 1)

A payment variance notification system as recited in claim 1, wherein the processor is further operative to detect refunds against settled payment transactions corresponding to a load amount, wherein the detection of the refund triggers a transmission of notification to a program administrator, the notification comprising the first transaction identifier and the refund amount.

### Claim 14 (depends on 13)

A payment variance notification system as recited in claim 13, wherein the notification further comprises the amount of the settled payment transaction.

### Claim 15 (depends on 1)

A payment variance notification system as recited in claim 1, wherein the processor is further operative to detect mismatched category codes for a transaction from a merchant, wherein the detection of a mismatch triggers a transmission of notification to a program administrator, the notification comprising the first transaction identifier and a category code received from the merchant.

### Claim 16 (depends on 15)

A payment variance notification system as recited in claim 15, wherein the category code is selected from the group consisting of a SIC code and an MCC code.

### Claim 17

A system for exception handling of failed payment-by-fax transmissions, the system comprising:
a first computer associated with a repository defining a repository computer, the repository computer being associated with an electronic communications network, being positioned to receive payment authorizations from a second computer associated with a program administrator defining an program administrator computer, and being positioned to provide payment by fax to a plurality of third computers associated with merchant accounts, the payment authorizations responsive to payment requests by a merchant, and wherein the first computer comprises:
a memory storing an instruction set and data related to a plurality of authorized program payments; and
a processor for running the instruction set, the processor being in communication with the memory and the network, wherein the processor is operative to receive payment authorizations from a program administrator and to transmit payment by fax to a plurality of merchants and further where the computer is operative to perform exception handling of failed payment-by-fax transmissions by the operations of:
receiving data indicative of a failed payment by fax transmission, the received data including a fax number and a transaction identifier;
transmitting notification of the failed payment by fax transmission to the program administrator, wherein the notification includes the transaction identifier;
receiving data from the program administrator, the received data including a revised fax number and the transaction identifier;
retransmitting the payment by fax using the revised fax number.

### Claim 18 (depends on 17)

A system for exception handling of failed payment-by-fax transmissions as recited in claim 17, wherein the notification further comprises the time and description of the failure.
