| System and method for preventing multiple charges for a transaction in a payment system -> Monitor Keywords |
|
|
  System and method for preventing multiple charges for a transaction in a payment systemUSPTO Application #: 20070276766Title: System and method for preventing multiple charges for a transaction in a payment system Abstract: A system and method for preventing multiple charges for a transaction in a payment system is presented. A payment system receives a payment operation request from the order system, and determines whether the payment operation is a duplication of a previous payment operation request. If so, the payment system retrieves stored financial transaction results and provides the financial transaction results to the order system. When the payment operation request is not a duplicate, the payment system contacts a payment provider to receive financial transaction results, which is passed to the order system and stored in a persistent data store. (end of abstract) Agent: Ibm Corporation - Rsw (jvl) C/o Van Leeuwen & Van Leeuwen - Austin, TX, US Inventors: Carlos Antonio Lorenzo Hoyos, Marcelo Perazolo, Mark E. Peters, Viswanath Srikanth, Andrea Jean Watkins Moryadas USPTO Applicaton #: 20070276766 - Class: 705 75 (USPTO) The Patent Description & Claims data below is from USPTO Patent Application 20070276766. Brief Patent Description - Full Patent Description - Patent Application Claims
CROSS REFERENCE TO RELATED APPLICATION [0001]This application is a continuation-in-part of commonly assigned, co-pending U.S. Non-Provisional patent application Ser. No. 11/420,040, entitled "System and Method for State-Based Execution and Recovery in a Payment System," filing date May 24, 2006, Attorney Docket No. RSW920050208US1. BACKGROUND OF THE INVENTION [0002]1. Technical Field [0003]The present invention relates to a system and method for preventing multiple charges for a transaction in a payment system. More particularly, the present invention relates to a system and method for providing existing financial transaction results to an order system when the order system invokes a duplicate payment operation request. [0004]2. Description of the Related Art [0005]Software-based payment systems today rely upon common techniques to orchestrate financial transactions between external payment providers (e.g., credit card companies). A challenge found with these techniques, however, is that the software-based payment systems may not check for duplicate financial transaction requests. Even though payment systems may implement transaction-based techniques to minimize the possibility of such situations, problems arise when duplicate requests originate external to the payment system, such as from order systems that are connected to the payment system. [0006]In such cases when a payment operation request is driven from a connected external component, the external component may not provide checks or transactional control for duplicate payment operation requests to the payment system. Hence, the payment system sends duplicate financial transaction requests to the external payment provider. For example, an order system may request a payment system to capture a deposit of $50 twice when the order system's original intent was for the deposit to be captured once. [0007]Furthermore, a challenge found with double charging is that the external payment provider may not allow the payment system to retract an executed financial transaction request. Meaning, the payment provider may not allow executed financial transaction request "rollbacks" or cancellations. Therefore, even if the payment system discovers a double charge, the payment system has to manually send a new financial transaction request to the payment provider to credit the customer's account. [0008]While specific solutions may be proposed for solving duplicate payment operation requests that are initiated by an end user (e.g., web-form double-submission, invoice double submission), a challenge found is that a payment system may also receive duplicate payment operation requests from order systems that are not directly initiated by an end user. [0009]What is needed, therefore, is a system and method that prevents a payment system from performing duplicate financial transaction requests to a payment provider when the payment system receives a duplicate payment operation request from an order system. SUMMARY [0010]It has been discovered that the aforementioned challenges are resolved using a system and method for providing existing financial transaction results to an order system when the order system invokes a duplicate payment operation request. A payment system receives a payment operation request from the order system, and determines whether the payment operation is a duplication of a previous payment operation request. If so, the payment system retrieves stored financial transaction results and provides the financial transaction results to the order system. When the payment operation request is not a duplicate, the payment system contacts a payment provider to receive financial transaction results, which is passed to the order system and stored in a persistent data store. [0011]A customer places an order with an order system by sending order and payment details to the order system. For example, the customer may place an order on a web page for office supplies, in which case the order and payment details may include line item information for the office supplies along with credit card information to pay for the office supplies. [0012]While processing the customer's order, the order system generates an order identifier, which uniquely identifies the customer's order. The order system also generates a release identifier, which uniquely identifies all or part of the customer's order that plans to ship at the same time to the customer (e.g., a "package"). The order system sends the order identifier, the release identifier, and one or more payment operation requests to the payment system. For example, the payment operation requests may be a payment instruction validation request, a payment instruction storage request, a process payment instruction after allocation request, or a process payment instruction after shipment request. [0013]Some payment operation requests involve the payment system sending a "financial transaction request" to a payment provider, which may be an external payment provider (e.g., credit card company). When this occurs, the payment provider sends "financial transaction results" back to the payment system. When received, the payment system sends the financial transaction results to the order system, and also stores the financial transaction results in a persistent data store. [0014]In order to identify duplicate payment operation requests generated by the order system, the payment system uses a detection algorithm. The detection algorithm detects duplicate payment operation requests using the combination of the order identifier, the release identifier (if applicable), and the payment identifier. [0015]When the detection algorithm detects a duplicate payment operation request, the detection algorithm does not send a financial transaction request to the payment provider. Instead, the detection algorithm instructs the payment provider to retrieve the financial transaction results previously stored in the persistent data store, and send the financial transaction results to the order system. By detecting duplicate payment operation requests, the payment system alleviates duplicate requests to the payment provider that, in turn, reduces cost and eliminates rollback situations. [0016]The foregoing is a summary and thus contains, by necessity, simplifications, generalizations, and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the present invention, as defined solely by the claims, will become apparent in the non-limiting detailed description set forth below. BRIEF DESCRIPTION OF THE DRAWINGS [0017]The present invention may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings. [0018]FIG. 1 is a diagram showing a payment system receiving and processing payment operation requests from an order system; [0019]FIG. 2 is a diagram showing a payment system receiving payment parameters from an order system, and using the payment parameters to identify duplicate payment operation requests; [0020]FIG. 3A is a diagram showing interface information for a payment system that permits external components to request payment operations; Continue reading... Full patent description for System and method for preventing multiple charges for a transaction in a payment system Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this System and method for preventing multiple charges for a transaction in a payment system patent application. Patent Applications in related categories: 20080172340 - Method and system for carrying out a transaction between a mobile device and a terminal - A method of conducting a transaction between a user of a mobile electronic device and a vendor includes determining a location of the mobile electronic device. At least one transaction terminal that has a location-based relationship with the mobile electronic device is identified. A transaction code for authenticating the mobile ... 20080172341 - Methods for authentication - A method for managing access to application software contained on a computer system or network. The computer system utilizes an authentication component that is configured to receive a unique user account identifier and to generate an authentication passkey by using an identifying data element, typically called a “password”. The identifying ... ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like System and method for preventing multiple charges for a transaction in a payment system or other areas of interest. ### Previous Patent Application: Point-of-service (pos) and pos application compatability Next Patent Application: Defining and sizing feasible approaches to business needs within an integrated development process Industry Class: Data processing: financial, business practice, management, or cost/price determination ### FreshPatents.com Support Thank you for viewing the System and method for preventing multiple charges for a transaction in a payment system patent info. IP-related news and info Results in 0.84059 seconds Other interesting Feshpatents.com categories: Electronics: Semiconductor , Audio , Illumination , Connectors , Crypto , |
||
