Transaction ID system and process

Abstract

A system and process for creating, maintaining, and using transaction identifiers, i.e. a transaction DNA, is provided. The DNA, along with other transactional information, is sent through a set of intermediary entities as found in a standard transaction processing system. The DNA is based on information that may include source ID, merchant ID, and order ID. The order ID is a unique number that can be generated by the merchant. The DNA is maintained throughout the lifecycle of the transaction, including authorization requests, settlement requests, and exception item processing. The DNA allows the bank to provide precise transactional matching to the original transaction for the merchant, making reconciliation always possible, fast, and automatic, and ensuring information is presented in a manner that the merchant chooses.

Description

BACKGROUND OF THE INVENTION

1. Technical Field

The invention relates to electronic transactions. More particularly, the invention relates to a system and process for establishing and maintaining a transaction ID that enables a merchant to track a transaction over all systems and tie back any activity against such transaction over time.

2. Description of the Prior Art

In order for a credit card transaction to be processed, it must go through a set of intermediary entities until a resolution is established. For example, an e-commerce transaction can include: a merchant server makes a request for funds; the transactional data is sent to the acquirer server, which sends the transactional data to the card association server for verifying compliance with the credit card association; the transaction is then forwarded to an associated issuing bank server for funds availability and settlement determination. Upon such determination, the transaction is then re-routed backwards through the process. Each component in each step of the process requires certain information in a specified manner. Because of this constraint, each step of the process requires from the next step of the process not only that step's requirements, but also the previous step's requirements. The end result is that the burden is on the merchant to offer different information in different electronic formats to satisfy the data needs of each intermediary entity at each step of the transaction process. Each intermediary entity takes the informational data it needs and passes the transactional data onto the next intermediary for the next step.

Because the merchant server is the last step in this chain, the merchant server presently does not have its own unique format or information attached with any particular transaction. Furthermore, a merchant does not necessarily have the capability of creating such a transaction ID. Barriers to a merchant having capability of creating merchant transaction IDs include that the cost for development can be prohibitive and overwhelming for a single merchant and also that coordination among merchants may not be achieved because the intermediary entities may not allow for each merchant to create its own proprietary system.

The effects of such a disjointed system and process fall entirely on the merchant. Further problems a merchant can encounter include the following:

• • Often, there is no certain transactional match throughout the life cycle of the transaction because the many different systems involved use different and unrelated identifiers in their messages and logs;
  • Reconciliation of a transaction, if at all possible, takes a lot of time because a merchant can't use its own identifier to search the database hosted by the acquirer;
  • Reconciliation of a transaction, if at all possible, takes a lot of manual labor because of the prior condition. The merchant has to use non-specific search criteria, such as card number and dollar amount of a transaction, which produces multiple matches that must be sorted through manually; and
  • Exception items which are often presented months after the original transaction are difficult to research and reconcile because the lack of a transaction identifier (transaction ID) makes it difficult or impossible to retrieve the original transaction.

It would be advantageous to provide a computer implemented system and process to facilitate a merchant identifying and tracking a particular transaction at any stage during the lifecycle of the transaction; to improve time for reconciliation of transactions; to automate reconciliation of transactions; and to organize transactional data in a meaningful way for improving transactional processes during the lifecycle of a transaction.

SUMMARY OF THE INVENTION

A system and process for creating and maintaining transaction identifiers is provided. The transaction identifiers become a kind of transaction DNA. The DNA or portions thereof is passed along with other transactional information through the same set of intermediaries as found in a standard transaction processing system. The DNA can be based on a source ID, merchant ID, and order ID. The order ID is a unique number that can be generated by the merchant or can be generated by a gateway system when the merchant does not provide an order ID. The DNA is maintained throughout the lifecycle of the transaction and any subsequent activity associated with such transaction, including authorization of payment, settlement, chargebacks, chargeback reversals, and other dispute resolution. Hence, a merchant can track a transaction over all systems and can tie back any activity against it over time. This process can be used for credit card transactions and electronic check transactions. It is also available for multi-currency transactions. The DNA for transactions allows a bank to provide precise transactional matching back to the original transaction for the merchant, such that for the merchant reconciliation is always possible, reconciliation is fast, reconciliation is automatic, and information is presented in the manner that the merchant chooses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an authorization flow diagram using transaction ID according to the invention;

FIG. 2 is a settlement flow diagram using transaction ID according to the invention; and

FIG. 3 is an exception item flow diagram using transaction ID according to the invention.

DETAILED DESCRIPTION OF THE INVENTION

A system and process for creating and maintaining transaction identifiers is provided. The transaction identifiers become a kind of transaction DNA. The DNA or portions thereof is passed along with other transactional information through the same set of intermediaries as found in a standard transaction processing system. The DNA can be based on a source ID, merchant ID, and order ID. The order ID is a unique number that can be generated by the merchant or can be generated by a gateway system when the merchant does not provide an order ID. The DNA is maintained throughout the lifecycle of the transaction and any subsequent activity associated with such transaction, including authorization of payment, settlement, chargebacks, chargeback reversals, and other dispute resolution. Hence, a merchant can track a transaction over all systems and can tie back any activity against it over time. This process can be used for credit card transactions and electronic check transactions. It is also available for multi-currency transactions. The DNA for transactions allows a bank to provide precise transactional matching back to the original transaction for the merchant, such that for the merchant reconciliation is always possible, reconciliation is fast, reconciliation is automatic, and information is presented in the manner that the merchant chooses.

It should be appreciated that the terms transaction ID, transaction DNA, and DNA are used interchangeably herein.

In one embodiment of the invention, the transaction DNA is based on or includes the following information:

• • Source ID;
  • Client ID; and
  • Merchant Order ID (or Order ID), a unique number that can be generated by the merchant or by the system for the merchant.

It should be appreciated that the DNA is maintained throughout the entire life of the given transaction and any subsequent activity associated with such transaction, such as for example:

• • Authorization of payment;
  • Settlement;
  • Chargebacks;
  • Chargeback Reversals; and
  • Other dispute resolution.

This invention can be used for credit cards, electronic checks such as MasterCard, Visa, Amex, and Discover, and for multi-currency transactions. It should be appreciated that Amex and Discover capability adds a great value because such transactions are usually processed with the minimal tracking and reporting capabilities.

It should further be appreciated that the transaction DNA provides precise transactional matching to the original transaction for the merchant whereby the following is true:

• • Reconciliation is always possible;
  • Reconciliation is fast;
  • Reconciliation is automatic; and
  • Information can be presented in a manner chosen by the merchant.An Exemplary Transaction Authorization Flow

One embodiment of the invention can be described with reference to FIG. 1, a detailed transaction authorization flow diagram showing the creation and passing of component IDs of the more generalized transaction ID according to the invention.

On each authorization request the merchant 102 passes a previously assigned Source ID (202) to a global payment gateway 104. The Source ID (202) is a value assigned by the Global Payments Gateway (GPG) to each major entity that generates transactions into the GPG. In one embodiment of the invention, the Source ID (202) is the highest level identifier in a GPG hierarchy of identifiers. The merchant passes a merchant self-assigned Merchant Reference ID. In one embodiment of the invention, the merchant generates and passes a unique Order ID to the GPG. The global payment gateway checks the Order ID to verify that it is unique within the Source ID.

In one embodiment of the invention, if the merchant does not send an Order ID, then the global payment gateway generates a unique Order ID on the merchant's behalf (204).

It should be appreciated that in one embodiment of the invention, the Source ID has under it one or more Merchant Ref IDs which has under it one or more Order IDs, thus defining a type of hierarchy of identifiers.

The global payment gateway generates 104 a unique Authorization Reference ID, using both the Order ID and the Merchant Reference ID (if available), and passes the Authorization Reference ID to the acquirer 106 as part of the authorization request (206). The acquirer 106 then passes the authorization request (206) through the card association 108 to the card issuer 110.

After receiving an authorization response from the credit card issuer 110, the acquirer 106 returns the authorization response with the original Authorization Reference ID back to the global payment gateway (208).

The global payment gateway 104 uses the Authorization Reference ID to retrieve both the original Order ID and Merchant Reference ID (if present.) Hence, the global payment gateway 104 returns the authorization response to the merchant 102 with the unique Order ID and the Merchant Reference ID (if present), both obtained from the returned Authorization Reference ID (210).

It should be appreciated that according to invention, the Order ID is fully retrieved for the merchant, as opposed to being lost.

An Exemplary Transaction Settlement Flow

One embodiment of the invention can be described with reference to FIG. 2, a detailed transaction settlement flow diagram showing the creation and passing of component IDs of the more generalized transaction ID according to the invention.

In one embodiment of the invention, on each settlement request (302), such as after shipment of the purchased item, the merchant 102 passes the previously assigned Source ID, the unique Order ID and a unique Client Settlement ID to the global payment gateway 104. The unique Client Settlement ID is used by the global payment gateway 104 to avoid duplicate settlements.

Once the global payment gateway 104 determines the settlement request is not a duplicate request, the gateway 104 generates a unique Cross Reference ID and passes it (304) along with the settlement date to the acquirer 106 as part of the settlement request. In one embodiment of the invention, the acquirer imbeds this unique Cross Ref ID into a unique Transaction Reference ID that is created by the acquirer and maintained by the issuer and acquirer for the life of the settled transaction. The acquirer 106 sends the settlement request along with the Transaction Reference ID (306) to the card issuer 110 for processing.

The acquirer 106 receives an acknowledgement to the settlement request (308) from the issuer 110 and then passes it (310) to the global payment gateway 104. The global payment gateway 104 uses the Transaction Ref ID and the embedded Cross-Ref ID from the settlement acknowledgment to retrieve the Order ID and the Client Settlement ID.

The global payment gateway returns (312) the settlement acknowledgement to the merchant 104 along with the Order ID and the Client Settlement ID so that the merchant can reconcile the settlement.

It should be appreciated that the invention provides a cross reference lookup table to identify and retrieve any of the following: Transaction Reference ID, Cross Reference ID, Client Settlement ID, Order ID, and Authorization Reference ID. In one embodiment of the invention, the global payment gateway creates the cross-reference table. An example table can be found in Table A herein below.

TABLE A
Transaction	Cross	Client		Authorization
Ref ID	Reference ID	Settlement ID	Order ID	Reference ID
Abc	Xyz	123	Uvw	456

An Exemplary Transaction Exception Item Flow

Suppose thirty to sixty days after a transaction a consumer is not happy with the purchased and received shipped item. The process of negotiating the consequent consumer's dispute is referred to herein as a transaction exception item. One embodiment of the invention can be described with reference to FIG. 3, wherein a detailed exception item flow diagram shows the creation and passing of component IDs of the more generalized transaction ID according to the invention.

The card issuing bank 110 receives and processes a transaction dispute request from a cardholder. Based on the type of dispute the card issuer creates and issues either a chargeback or retrieval request (402), i.e. an exception item request, to the acquirer 106. The Transaction Reference ID with the embedded Cross Reference ID from the original settlement request is included in the exception item request.

The acquirer 106 passes the exception item and the Transaction Reference ID (404) with the embedded Cross Reference ID to the global payment gateway 104.

The global payment gateway 104 extracts (406) the Cross Reference ID from the Transaction Reference ID and, using the cross reference table, retrieves the original transaction information from its database by using the Cross Reference ID and the original settlement date.

The global payment gateway 104 sends the merchant 102 the exception item with the original Order ID, Client Settlement ID and Transaction Reference ID (408) so that the merchant can electronically retrieve the original transaction details from its database in order to research and reconcile the exception item.

Hence, it should be appreciated that with Beginning of Day (BOD) Exception and End of Day (EOD) Reconciliation file transfer to the merchant, the invention provides the merchant daily reconciliation and comprehensive reporting capability. This combined functionality allows the customer to have one seamless picture of all his or her transactions at any given point of the transaction's path and on any date.

It should be appreciated that the configuration of servers and certain processes for the merchant, global payment gateway, acquirer, card association, and issuer are meant by way of example only. The software and hardware implementations can be distributed among one or more servers and one or more computer applications or modules without departing from the scope and spirit of the invention.

Accordingly, although the invention has been described in detail with reference to particular preferred embodiments, persons possessing ordinary skill in the art to which this invention pertains will appreciate that various modifications and enhancements may be made without departing from the spirit and scope of the claims that follow.

Claims

1. A computer implemented method for a merchant to track an original transaction throughout a lifecycle of the original transaction, the method comprising the steps of: sending, by a global payment gateway server, an authorization response along with a merchant reference identifier and an order identifier to the merchant, a merchant authorization request including the merchant reference identifier and the order identifier, said original transaction associated with the merchant authorization request and the authorization response, the order identifier being a unique number received from the merchant, the merchant reference identifier being an identifier for said original transaction received from said merchant;sending, by the global payment gateway server, a settlement acknowledgment along with the order identifier and a client settlement identifier to the merchant, a merchant settlement request including said order identifier and said client settlement identifier, said original transaction associated with the merchant settlement request and the settlement acknowledgment, the client settlement identifier being a unique identifier used by the global payment gateway server to avoid duplicate settlements; andsending, by the global payment gateway server, an exception item request along with said order identifier, a transaction reference identifier, and said client settlement identifier to the merchant, said original transaction associated with said exception item request, the transaction reference identifier received from an acquirer of the original transaction.

2. The computer implemented method of claim 1, wherein the method further comprises the steps of: generating, by the global payment gateway server, a source identifier, the source identifier being a value assigned by the global payment gateway server to said merchant;sending, by the global payment gateway server, the source identifier to the merchant, wherein said source identifier is unique to said merchant;receiving, at the global payment gateway server, said merchant authorization request from said merchant, wherein said merchant authorization request comprises said source identifier, said order identifier, and said merchant reference identifier;generating, by said global payment gateway server, an authorization reference identifier using said order identifier;sending, by said global payment gateway server, said authorization reference identifier to said acquirer for processing;receiving, by said global payment gateway server, said authorization response from the acquirer, wherein said authorization response comprises said authorization reference identifier; andresponsive to receiving said authorization response, using, by said global payment gateway server, said authorization reference identifier to retrieve said order identifier and said merchant reference identifier.

3. The computer implemented method of claim 2 further comprising the step of: determining that said order identifier was not received by said global payment gateway server; and in response to determining that the order identifier was not received by the global payment gateway server, generating, by said global payment gateway server, the order identifier, the order identifier associated with said original transaction.

4. The computer implemented method of claim 2, wherein the method further comprises the steps of: receiving, at said global payment gateway server, said merchant settlement request from said merchant, said merchant settlement request comprising said source identifier, said order identifier, and said client settlement identifier;generating, by said global payment gateway server, a cross reference identifier;sending said merchant settlement request to said acquirer along with a settlement date and said cross reference identifier, the cross reference identifier embedded in said transaction reference identifier;receiving, at said global payment gateway server, said settlement acknowledgment from said acquirer, said settlement acknowledgment responsive to said merchant settlement request; andusing, by said global payment gateway server, said cross reference identifier to retrieve said order identifier and said client settlement identifier.

5. The computer implemented method of claim 4, wherein the method further comprises the steps of: receiving, at the global payment gateway server, said exception item request from said acquirer prior to sending the exception item request to the merchant, said exception item request comprising said transaction reference identifier in which is embedded said cross reference identifier; andresponsive to receiving said exception item request, extracting, by said global payment gateway server, said cross reference identifier from the transaction reference identifier.

6. The computer implemented method of claim 4, further comprising the step of: providing, by said global payment gateway server, a cross reference table to associate said transaction reference identifier, said cross reference identifier, said client settlement identifier, and said order identifier.

7. A global payment gateway server on a computer network for a merchant to track an original transaction throughout a lifecycle of the original transaction, the global payment gateway server comprising: means for sending an authorization response for the original transaction to said merchant, the authorization response including a merchant reference identifier and an order identifier, a merchant authorization request including the merchant reference identifier and the order identifier, said original transaction associated with the merchant authorization request and the authorization response, said order identifier being a unique number, the merchant reference identifier being an identifier received from said merchant;means for sending a settlement acknowledgment to said merchant, the settlement acknowledgment including the order identifier and a client settlement identifier, a merchant settlement request including said order identifier and said client settlement identifier, said original transaction associated with the merchant settlement request and the settlement acknowledgment, said client settlement identifier being a unique identifier used by the global payment gateway server to avoid duplicate settlements; andmeans for sending an exception item request to said merchant, the exception item request including said order identifier, a transaction reference identifier, and said client settlement identifier, said original transaction associated with said exception item request, the transaction reference identifier received from an acquirer of the original transaction.

8. The global payment gateway server of claim 7, further comprising: means for generating a source identifier, said source identifier being unique to said merchant, the source identifier being a value assigned by the global payment gateway server to said merchant;means for sending said source identifier to said merchant;means for receiving the merchant authorization request from said merchant, said merchant authorization request comprising said source identifier, said order identifier, and the merchant reference identifier;means for generating an authorization reference identifier using said order identifier;means for sending said authorization reference identifier to said acquirer;means for receiving said authorization response from said acquirer, wherein said authorization response comprises said authorization reference identifier; andmeans for using, responsive to receiving said authorization response, said authorization reference identifier to retrieve said order identifier and said merchant reference identifier.

9. The global payment gateway server of claim 7 further comprising: means for generating the order identifier, said order identifier was not available and not sent to said global payment gateway server.

10. The global payment gateway server of claim 8, further comprising: means for receiving said merchant settlement request, said merchant settlement request comprising said source identifier, said order identifier, and said client settlement identifier, said merchant settlement request received from said merchant, said client settlement identifier received from said merchant;means for generating a cross reference identifier;means for sending said merchant settlement request to said acquirer, said merchant settlement request further comprising a settlement date and said cross reference identifier, said merchant settlement request further comprising said transaction reference identifier, said transaction reference identifier including said cross reference identifier;means for receiving said settlement acknowledgment from the acquirer, the settlement acknowledgment responsive to said merchant settlement request; andmeans for using said cross reference identifier to retrieve said order identifier and said client settlement identifier.

11. The global payment gateway server of claim 10, further comprising: means receiving the exception item request from said acquirer, said exception item request comprising said transaction reference identifier, said cross reference identifier being embedded in said transaction reference identifier; andmeans for extracting, responsive to receiving said exception item request, said cross reference identifier.

12. The global payment gateway server of claim 10, further comprising: a cross reference table to associate said transaction reference identifier, said cross reference identifier, said client settlement identifier, and said order identifier.