Systems and methods for transaction processing based upon an overdraft scenario

• US 8,190,514 B2
• Filed: 06/05/2009
• Issued: 05/29/2012
• Est. Priority Date: 11/05/1999
• Status: Expired due to Fees

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Lead Core Fund LLC (Intellectual Ventures LLC)
• Inventors: Bishop, Fred, Seth, Hitesh, Morgan, Robert E.
• Primary Examiner(s): Patel, Jagdish
• Application Number:
  US12/479,650
• Publication Number:
  US 20090271277A1
• Time in Patent Office: 1,089 Days
• Field of Search: 705/35, 705/38, 705/39
• US Class Current: 705/38
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof

Abstract

Facilitating commercial transactions using a payment system directory are disclosed. A payment directory and/or wireless point of sale (POS) device may be configured to use predetermined rules, a multitude of data items and/or conditions to locate a payment system, and transmit a payment authorization request from a remote location to at least one payment system, either directly, or via a payment system directory and/or a SSL Gateway.

Claims

1. A method, comprising:

receiving, at a payment directory computer, a payment request for a transaction;

determining, by the payment directory computer, a first payment system for processing at least a portion of the transaction based on parameters in the payment request;

transmitting, by the payment directory computer and to the first payment system, a first authorization request related to at least a portion of the transaction;

receiving, at the payment directory computer and from the first payment system, a first authorization response associated with the first authorization request;

in response to the first authorization response indicating at least one of a decline or a partial authorization, determining, by the payment directory computer, a second payment system for processing at least a portion of the transaction based on the parameters in the payment request;

transmitting, from the payment directory computer and to the second payment system, a second authorization request related to at least a portion of the transaction;

receiving, by the payment directory computer and from the second payment system, a second authorization response associated with the second authorization request; and

transmitting, by the payment directory computer, a payment response based upon the payment request and at least one of the first authorization response or the second authorization response.

2. The method of claim 1, wherein at least one of the determining the first payment system or the determining the second payment system comprises querying a payment system directory, wherein the payment system directory comprises a plurality of candidate payment systems.

3. The method of claim 2,

wherein the querying the payment system directory comprises transmitting a payment directory request to the payment system directory with at least one selection parameter;

wherein the selection parameter is associated with at least one of an account owner associated with the payment request or a merchant associated with the transaction; and

wherein the payment system directory parses the payment directory request, creates a query based upon the parsed payment directory request and executes the query against a payment system database.

4. The method of claim 3, wherein the payment system directory transmits a plurality of candidate payment systems in response to the payment directory request, and wherein the payment system directory applies a predetermined rule to select the first payment system from the plurality of candidate payment systems.

5. The method of claim 1, wherein the determining the second payment system comprises determining the second payment system based upon a predetermined rule.

6. The method of claim 5, wherein the predetermined rule is at least partially based upon at least one of the payment request, a merchant system, a requesting device, a merchant who submitted a payment request, a point of service device attribute, a purchaser transaction device attribute, a transaction amount, an account holder, a transaction account, a proxy account identifier, a transaction account issuer, an alternate account associated with a transaction account, an overdraft rule, an overdraft account, an acquiring financial institution, a point of sale device, a point of service device associated with the transaction, a merchant associated with a point of service device, a geographic location, a geographic location associated with the transaction, a code, a product associated with the transaction, a merchant associated with the transaction, a date a user data input, a first budget associated with a first account and with budget information, budget information associated with the payment request, an expiration date associated with a rewards program, a points balance associated with a second rewards program, an expiration date associated with a rewards program, a points balance associated with a rewards account, or an allowance.

7. The method of claim 1, wherein at least a portion of the payment request is received from at least one of a merchant system, a point of sale device, a wireless point of service device, a transaction card, a wireless transaction device, a website, an electronic commerce system, a wallet system associated with a purchaser, or a purchaser transaction device.

8. The method of claim 1, wherein at least a portion of the payment request is received from a merchant system via at least one of an Internet, a gateway, or an SSL Gateway.

9. The method of claim 1, wherein the payment directory computer is part of an SSL gateway.

10. The method of claim 1, wherein at least a portion of the payment response is transmitted to at least one of a merchant system, a point of sale device, a wireless point of sale device, a transaction card, a wireless transaction device, a website, an electronic commerce system, a wallet system associated with a purchaser, or a purchaser transaction device.

11. The method of claim 1, wherein in response to the first authorization response indicating a partial authorization, the second payment system is at least partially determined based upon the partial authorization.

12. The method of claim 1, wherein in response to the first authorization response indicating a partial authorization, an amount of the second authorization request is based upon a transaction amount associated with the payment request minus an amount substantially equal to a partial payment amount associated with the partial authorization.

13. The method of claim 1, further comprising:

calculating the percentage of the partial payment relative to a transaction amount associated with the payment request; and

in response to the percentage of the partial payment being less than a predetermined threshold, setting an amount of the second authorization request equal to the transaction amount associated with the payment request.

14. The method of claim 1, wherein in response to the first authorization response indicating a partial authorization, determining the second authorization request based upon a transaction amount associated with the payment request and determining the payment response based upon the second authorization response.

15. A tangible machine-readable medium having stored thereon computer-executable instructions that, if executed by a payment directory computing device, cause the computing device to perform operations comprising:

receiving, by the computing device, a payment request for a transaction;

determining, by the computing device, a first payment system for processing at least a portion of the transaction based on parameters in a payment request;

transmitting, by the computing device and to the first payment system, a first authorization request related to at least a portion of the transaction;

receiving, by the computing device and from the first payment system, a first authorization response associated with the first authorization request;

in response to the first authorization response indicating at least one of a decline or a partial authorization, determining, by the computing device, a second payment system for processing at least a portion of the transaction based on parameters in the payment request;

transmitting, by the computing device and to the second payment system, a second authorization request related to at least a portion of the transaction;

receiving, by the computing device and from the second payment system, a second authorization response associated with the second authorization request; and

,

transmitting, by the computing device, a payment response based upon the payment request and at least one of the first authorization response or the second authorization response.