Systems, methods, and computer program products for network message enhancement

Abstract

Systems, methods, and computer program products are provided for processing payment transactions over an electronic network. The method includes receiving an authorization request message including first transaction data associated with an electronic payment transaction, and generating a unique identifier associated with the electronic payment transaction. The method also includes receiving an authorization response message, the authorization response message including second transaction data associated with the electronic payment transaction, the authorization response message indicating that the electronic payment transaction is authorized. The method also includes storing a portion of the first transaction data and the second transaction data in association with the unique identifier of the electronic payment transaction. The method further includes transmitting a response message including the unique identifier and the authorization decision, and receiving a clearing request message including the unique identifier. The method also includes retrieving the stored transaction data and initiating a clearing of the electronic payment transaction.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 352,349, filed on June 15, 2022, the disclosure of which is incorporated herein by reference in its entirety. Background Art 1. Technical Field

[0003] The present disclosure relates generally to processing payment transactions through an electronic payment processing network and, in some non-limiting embodiments or aspects, to systems, methods, and computer program products for network message enhancement for processing payment transactions through an electronic payment processing network.

[0004] 2. Technical considerations

[0005] In an electronic payment processing network, an acquirer system of an acquirer (e.g., a bank) may process payment transactions by communicating with a transaction processing system of a transaction service provider. Processing of payment transactions may involve authorizing, clearing, and settling payment transactions. In existing systems, the clearing step requires the acquirer system to store, match, and transmit transaction data to the transaction processing system via a clearing request to clear each transaction. This involves the storage, matching, and communication of large amounts of transaction data (e.g., potentially hundreds of data elements) for each transaction.

[0006] Due to the complexity involved in generating clearing requests, existing acquirer systems process transactions for clearing using batch processing (e.g., large groups of transactions), which is processed at the end of each day. Batch processing does not allow the acquirer system to process transactions in real time or near real time (e.g., relative to transmitting a response message from the transaction processing system). It also requires the acquirer system to expend significant computing resources in order to generate and transmit the clearing requests. Summary of the invention

[0007] It is therefore an object of the present disclosure to provide systems, methods, and computer program products for processing payment transactions through an electronic payment processing network that overcome some or all of the deficiencies identified above.

[0008] According to non-limiting embodiments or aspects, a computer-implemented method for processing a payment transaction through an electronic payment processing network is provided. In some non-limiting embodiments or aspects, the method may include receiving, by a transaction processing system, an authorization request message associated with an electronic payment transaction from an acquirer system, the authorization request message may include first transaction data associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the method may also include generating, by the transaction processing system, a unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the method may also include receiving, by the transaction processing system, an authorization response message associated with the electronic payment transaction from an issuer system, the authorization response message may include second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized. In some non-limiting embodiments or aspects, the method may also include storing, by the transaction processing system, at least a portion of the first transaction data and the second transaction data in association with the unique identifier of the electronic payment transaction. In some non-limiting embodiments or aspects, the method may also include transmitting, by the transaction processing system, a response message including the unique identifier and the authorization decision to the acquirer system. In some non-limiting embodiments or aspects, the method may further include receiving, by the transaction processing system, a clearing request message from the acquirer system, the clearing request message including a unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the method may further include: in response to receiving the clearing request message, retrieving, by the transaction processing system, at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message. In some non-limiting embodiments or aspects, the method may further include initiating, by the transaction processing system, clearing of the electronic payment transaction based on at least a portion of the retrieved first transaction data and the second transaction data associated with the unique identifier.

[0009] In some non-limiting embodiments or aspects, the method may further include transmitting, by the transaction processing system, the authorization request message to an issuer system, wherein the issuer system generates the authorization decision.

[0010] In some non-limiting embodiments or aspects, the clearing request message may include only a unique identifier associated with the electronic payment transaction.

[0011] In some non-limiting embodiments or aspects, the clearing request message may include only a unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data.

[0012] In some non-limiting embodiments or aspects, the clearing request message may not include transaction data associated with transactions other than electronic payment transactions.

[0013] In some non-limiting embodiments or aspects, the transaction processing system may receive the clearing request message in real time or near real time relative to the transmission of the response message.

[0014] In some non-limiting embodiments or aspects, at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier for the electronic payment transaction may include all transaction data required to clear the electronic payment transaction.

[0015] According to non-limiting embodiments or aspects, a system is provided, comprising: at least one processor; and at least one non-transitory computer-readable medium storing instructions, wherein the instructions, when executed by the at least one processor, cause the at least one processor to receive an authorization request message associated with an electronic payment transaction from an acquirer system, wherein the authorization request message includes first transaction data associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the instructions may also cause the at least one processor to generate a unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the instructions may also cause the at least one processor to receive an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized. In some non-limiting embodiments or aspects, the instructions may also cause the at least one processor to store at least a portion of the first transaction data and the second transaction data in association with the unique identifier of the electronic payment transaction. In some non-limiting embodiments or aspects, the instructions may also cause the at least one processor to transmit a response message including the unique identifier and the authorization decision to the acquirer system. In some non-limiting embodiments or aspects, the instructions may further cause the at least one processor to receive a clearing request message from the acquirer system that includes a unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the instructions may further cause the at least one processor to retrieve at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message in response to receiving the clearing request message. In some non-limiting embodiments or aspects, the instructions may further cause the at least one processor to initiate clearing of the electronic payment transaction based on the retrieved at least a portion of the first transaction data and the second transaction data associated with the unique identifier.

[0016] In some non-limiting embodiments or aspects, the instructions may further cause the at least one processor to transmit the authorization request message to an issuer system, wherein the issuer system generates the authorization decision.

[0017] In some non-limiting embodiments or aspects, the clearing request message may include only a unique identifier associated with the electronic payment transaction.

[0018] In some non-limiting embodiments or aspects, the clearing request message may include only a unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data.

[0019] In some non-limiting embodiments or aspects, the clearing request message may not include transaction data associated with transactions other than electronic payment transactions.

[0020] In some non-limiting embodiments or aspects, the transaction processing system may receive the clearing request message in real time or near real time relative to the transmission of the response message.

[0021] In some non-limiting embodiments or aspects, at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier for the electronic payment transaction may include all transaction data required to clear the electronic payment transaction.

[0022] According to non-limiting embodiments or aspects, a computer program product is provided, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising program instructions, the program instructions, when executed by at least one processor, causing the at least one processor to receive an authorization request message associated with an electronic payment transaction from an acquirer system, wherein the authorization request message includes first transaction data associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the program instructions may also cause the at least one processor to generate a unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the program instructions may also cause the at least one processor to receive an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized. In some non-limiting embodiments or aspects, the program instructions may also cause the at least one processor to store at least a portion of the first transaction data and the second transaction data in association with the unique identifier of the electronic payment transaction. In some non-limiting embodiments or aspects, the program instructions may further cause the at least one processor to transmit a response message including the unique identifier and the authorization decision to the acquirer system. In some non-limiting embodiments or aspects, the program instructions may further cause the at least one processor to receive a clearing request message including a unique identifier associated with the electronic payment transaction from the acquirer system. In some non-limiting embodiments or aspects, the program instructions may further cause the at least one processor to retrieve at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message in response to receiving the clearing request message. In some non-limiting embodiments or aspects, the program instructions may further cause the at least one processor to initiate clearing of the electronic payment transaction based on the retrieved at least a portion of the first transaction data and the second transaction data associated with the unique identifier.

[0023] In some non-limiting embodiments or aspects, the program instructions may further cause the at least one processor to transmit the authorization request message to an issuer system, wherein the issuer system generates the authorization decision.

[0024] In some non-limiting embodiments or aspects, the clearing request message may include only a unique identifier associated with the electronic payment transaction.

[0025] In some non-limiting embodiments or aspects, the clearing request message may include only a unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data.

[0026] In some non-limiting embodiments or aspects, the clearing request message may not include transaction data associated with transactions other than electronic payment transactions.

[0027] In some non-limiting embodiments or aspects, the transaction processing system may receive the clearing request message in real time or near real time relative to the transmission of the response message.

[0028] In some non-limiting embodiments or aspects, at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier for the electronic payment transaction may include all transaction data required to clear the electronic payment transaction.

[0029] Other non-limiting embodiments or aspects are set forth in the following numbered clauses:

[0030] Clause 1: A method, comprising: receiving, by a transaction processing system, an authorization request message associated with an electronic payment transaction from an acquirer system, wherein the authorization request message includes first transaction data associated with the electronic payment transaction; generating, by the transaction processing system, a unique identifier associated with the electronic payment transaction; receiving, by the transaction processing system, an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized; storing, by the transaction processing system, the first transaction data in association with the unique identifier of the electronic payment transaction The invention relates to a method for preparing an electronic payment transaction according to the present invention; wherein the transaction processing system comprises a first transaction data and at least a portion of the second transaction data stored in association with the unique identifier from the clearing request message; the transaction processing system transmits a response message including the unique identifier and the authorization decision to the acquirer system; the transaction processing system receives a clearing request message including the unique identifier associated with the electronic payment transaction from the acquirer system; in response to receiving the clearing request message, the transaction processing system retrieves at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message; and the transaction processing system initiates clearing of the electronic payment transaction based on the retrieved at least a portion of the first transaction data and the second transaction data associated with the unique identifier.

[0031] Clause 2: The method of clause 1, further comprising: transmitting, by the transaction processing system, the authorization request message to an issuer system, wherein the issuer system generates the authorization decision.

[0032] Clause 3: A method as described in clause 1 or 2, wherein the clearing request message includes only a unique identifier associated with the electronic payment transaction.

[0033] Clause 4: A method according to any one of clauses 1-3, wherein the clearing request message comprises only a unique identifier associated with the electronic payment transaction and updated first transaction data and / or second transaction data.

[0034] Clause 5: A method as described in any of clauses 1-4, wherein the clearing request message does not include transaction data associated with transactions other than the electronic payment transaction.

[0035] Clause 6: A method according to any one of clauses 1-5, wherein the transaction processing system receives the clearing request message in real time or near real time relative to the transmission of the response message.

[0036] Clause 7: A method according to any one of clauses 1-6, wherein at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier of the electronic payment transaction includes all transaction data required to clear the electronic payment transaction.

[0037] Clause 8: A system comprising: at least one processor; and at least one non-transitory computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to: receive an authorization request message associated with an electronic payment transaction from an acquirer system, wherein the authorization request message includes first transaction data associated with the electronic payment transaction; generate a unique identifier associated with the electronic payment transaction; receive an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized ; storing at least a portion of the first transaction data and the second transaction data in association with a unique identifier of the electronic payment transaction; transmitting a response message including the unique identifier and the authorization decision to the acquirer system; receiving a clearing request message including the unique identifier associated with the electronic payment transaction from the acquirer system; in response to receiving the clearing request message, retrieving at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message; and initiating clearing of the electronic payment transaction based on the retrieved at least a portion of the first transaction data and the second transaction data associated with the unique identifier.

[0038] Clause 9: The system of clause 8, wherein the instructions further cause the at least one processor to: transmit the authorization request message to an issuer system, wherein the issuer system generates the authorization decision.

[0039] Clause 10: The system of clause 8 or 9, wherein the clearing request message includes only a unique identifier associated with the electronic payment transaction.

[0040] Clause 11: A system according to any of clauses 8-10, wherein the clearing request message includes only a unique identifier associated with the electronic payment transaction and updated first transaction data and / or second transaction data.

[0041] Clause 12: A system as described in any of clauses 8-11, wherein the clearing request message does not include transaction data associated with transactions other than the electronic payment transaction.

[0042] Clause 13: The system of any of clauses 8-12, wherein the transaction processing system receives the clearing request message in real time or near real time relative to transmission of the response message.

[0043] Reason 14: A system as described in any of clauses 8-13, wherein at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier of the electronic payment transaction includes all transaction data required to clear the electronic payment transaction.

[0044] Clause 15: A computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising program instructions that, when executed by at least one processor, cause the at least one processor to: receive an authorization request message associated with an electronic payment transaction from an acquirer system, wherein the authorization request message includes first transaction data associated with the electronic payment transaction; generate a unique identifier associated with the electronic payment transaction; receive an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an indication that the electronic payment transaction is storing at least a portion of the first transaction data and the second transaction data in association with a unique identifier of the electronic payment transaction; transmitting a response message including the unique identifier and the authorization decision to the acquirer system; receiving a clearing request message including the unique identifier associated with the electronic payment transaction from the acquirer system; in response to receiving the clearing request message, retrieving at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message; and initiating clearing of the electronic payment transaction based on the retrieved at least a portion of the first transaction data and the second transaction data associated with the unique identifier.

[0045] Clause 16: The computer program product of clause 15, wherein the program instructions further cause the at least one processor to: transmit the authorization request message to an issuer system, wherein the issuer system generates the authorization decision.

[0046] Clause 17: A computer program product according to clause 15 or 16, wherein the clearing request message includes only a unique identifier associated with the electronic payment transaction.

[0047] Clause 18: A computer program product according to any of clauses 15-17, wherein the clearing request message comprises only a unique identifier associated with the electronic payment transaction and updated first transaction data and / or second transaction data.

[0048] Clause 19: A computer program product as recited in any of Clauses 15-18, wherein the clearing request message does not include transaction data associated with transactions other than the electronic payment transaction.

[0049] Clause 20: A computer program product as described in any of clauses 15-19, wherein the transaction processing system receives the clearing request message in real time or near real time relative to the transmission of the response message.

[0050] Clause 21: A computer program product according to any of clauses 15-20, wherein at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier of the electronic payment transaction includes all transaction data required to clear the electronic payment transaction.

[0051] These and other features and characteristics of the present disclosure, as well as methods of operation and functions of related structural elements and combinations of parts and economies of manufacture, will become more apparent when considering the following description and appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as a definition of the limits of the disclosed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Additional advantages and details are explained in more detail below with reference to non-limiting exemplary embodiments shown in the schematic drawings, in which:

[0053] Figure 1 is a diagram of an exemplary environment in which methods, systems, and / or computer program products described herein may be implemented according to some non-limiting embodiments or aspects;

[0054] Figure 2 is a flow chart of a method of processing a payment transaction through an electronic payment processing network according to some non-limiting embodiments or aspects;

[0055] Figure 3 According to some non-limiting embodiments or aspects Figure 1 or Figure 4 schematic diagrams of exemplary components of one or more devices; and

[0056] Figure 4 is a flow chart of a method of network message enhancement for processing payment transactions through an electronic payment processing network according to some non-limiting embodiments or aspects. DETAILED DESCRIPTION

[0057] For the purposes of the following description, the terms "end," "upper," "lower," "right," "left," "vertical," "horizontal," "top," "bottom," "lateral," "longitudinal," and their derivatives shall relate to the orientation of the embodiments in the accompanying drawings. However, it shall be understood that the embodiments may employ various alternative variations and step orders, except where expressly specified to the contrary. It shall also be understood that the specific devices and processes illustrated in the accompanying drawings and described in the following specification are merely exemplary embodiments or aspects of the disclosed subject matter. Accordingly, specific dimensions and other physical characteristics relating to the embodiments or aspects disclosed herein shall not be considered limiting.

[0058] The aspects, parts, elements, structures, actions, steps, functions, instructions, etc. used herein should not be understood as critical or necessary unless explicitly described as such. Moreover, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more" and "at least one". In addition, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related items and unrelated items, etc.), and can be used interchangeably with "one or more" or "at least one". In the case of wishing only one item, the term "one" or similar language is used. Moreover, as used herein, the term "having" and / or its analogs are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on".

[0059] As used herein, the term "acquirer" may refer to an entity that is licensed and / or approved by a transaction service provider to initiate transactions (e.g., payment transactions) using a payment device associated with the transaction service provider. Transactions that may be initiated by an acquirer may include payment transactions (e.g., purchases, original letter of credit transactions (OCTs), account funding transactions (AFTs), etc.). In some non-limiting embodiments or aspects, the acquirer may be a financial institution, such as a bank. As used herein, the term "acquirer system" may refer to one or more computing devices operated by or on behalf of an acquirer, such as a server computer executing one or more software applications.

[0060] As used herein, the term "account identifier" may include one or more primary account numbers (PANs), tokens, or other identifiers associated with a customer account. The term "token" may refer to an identifier used as a replacement or substitute identifier for an original account identifier such as a PAN. An account identifier may be alphanumeric or any combination of characters and / or symbols. A token may be associated with a PAN or other original account identifier in one or more data structures (e.g., one or more databases, etc.) such that the token can be used to conduct transactions without directly using the original account identifier. In some examples, an original account identifier such as a PAN may be associated with multiple tokens for different individuals or purposes.

[0061] As used herein, the term "communication" may refer to the reception, acceptance, transmission, delivery, provision, etc. of data (e.g., information, signals, messages, instructions, commands, etc.). A unit (e.g., a device, a system, a component of a device or system, a combination thereof, etc.) communicating with another unit means that the unit is able to directly or indirectly receive information from the other unit and / or transmit information to the other unit. This may refer to a direct or indirect connection (e.g., a direct communication connection, an indirect communication connection, etc.) that is wired and / or wireless in nature. In addition, although the transmitted information may be modified, processed, relayed, and / or routed between the first unit and the second unit, the two units may also communicate with each other. For example, even if the first unit passively receives information and does not actively transmit the information to the second unit, the first unit may communicate with the second unit. As another example, if at least one intermediate unit processes the information received from the first unit and transmits the processed information to the second unit, the first unit may communicate with the second unit.

[0062] As used herein, the term "computing device" may refer to one or more electronic devices configured to process data. In some examples, a computing device may include the necessary components to receive, process, and output data, such as a processor, a display, a memory, an input device, a network interface, etc. The computing device may be a mobile device. As an example, a mobile device may include a cellular phone (e.g., a smartphone or a standard cellular phone), a portable computer, a wearable device (e.g., a watch, glasses, lenses, clothing, etc.), a personal digital assistant (PDA), and / or other similar devices. A computing device may also be a desktop computer or other form of non-mobile computer.

[0063] As used herein, the terms "electronic wallet" and "electronic wallet application" refer to one or more electronic devices and / or software applications configured to initiate and / or conduct payment transactions. For example, an electronic wallet may include a mobile device executing an electronic wallet application, and may also include server-side software and / or databases for maintaining and providing transaction data to the mobile device. An "electronic wallet provider" may include an entity that provides and / or maintains electronic wallets for customers, such as Google Android Apple Samsung And / or other similar electronic payment systems. In some non-limiting examples, the issuing bank may be an electronic wallet provider.

[0064] As used herein, the term "issuer institution" may refer to one or more entities, such as a bank, that provide accounts to customers for conducting transactions (e.g., payment transactions), such as initiating credit and / or debit payments. For example, an issuer institution may provide customers with account identifiers, such as PANs, that uniquely identify one or more accounts associated with the customer. The account identifier may be implemented on a payment device, such as a physical financial instrument, such as a payment card, and / or may be electronic and used for electronic payments. The term "issuer system" refers to one or more computer devices operated by or on behalf of an issuer institution, such as a server computer executing one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing transactions.

[0065] As used herein, the term "merchant" may refer to a person or entity that provides goods and / or services, or access to goods and / or services, to a customer based on a transaction, such as a payment transaction. The term "merchant" or "merchant system" may also refer to one or more computer systems operated by or on behalf of a merchant, such as a server computer that executes one or more software applications.

[0066] As used herein, a "point of sale (POS) device" may refer to one or more devices that can be used by a merchant to conduct a transaction (e.g., a payment transaction) and / or process a transaction. For example, a POS device may include one or more client devices. Additionally or alternatively, a POS device may include a peripheral device, a card reader, a scanning device (e.g., a code scanner), Communication receiver, near field communication (NFC) receiver, radio frequency identification (RFID) receiver and / or other contactless transceiver or receiver, contact-based receiver, payment terminal, etc. As used herein, a "point of sale (POS) system" may refer to one or more client devices and / or peripheral devices used by merchants to conduct transactions. For example, a POS system may include one or more POS devices, and / or other similar devices that can be used to conduct payment transactions. In some non-limiting embodiments or aspects, a POS system (e.g., a merchant POS system) may include one or more server computers that are programmed or configured to process online payment transactions through web pages, mobile applications, etc.

[0067] As used herein, the terms "client" and "client device" may refer to one or more client-side devices or systems (e.g., remote from a transaction service provider) used to initiate or facilitate a transaction (e.g., a payment transaction). As an example, a "client device" may refer to one or more POS devices used by a merchant, one or more acquirer host computers used by an acquirer, one or more mobile devices used by a user, and the like. In some non-limiting embodiments or aspects, a client device may be an electronic device configured to communicate with one or more networks and initiate or facilitate a transaction. For example, a client device may include one or more computers, portable computers, laptop computers, tablet computers, mobile devices, cellular phones, wearable devices (e.g., watches, glasses, lenses, clothing, etc.), PDAs, and the like. In addition, a "client" may also refer to an entity (e.g., a merchant, an acquirer, etc.) that owns, utilizes, and / or operates a client device to initiate a transaction (e.g., initiate a transaction with a transaction service provider).

[0068] As used herein, the term "payment device" may refer to a payment card (e.g., a credit or debit card), a gift card, a smart card, smart media, a payroll card, a healthcare card, a wristband, a machine-readable medium containing account information, a key chain device or fob, an RFID transponder, a retailer discount or membership card, a cellular phone, an electronic wallet mobile application, a personal digital assistant (PDA), a pager, a security card, a computing device, an access card, a wireless terminal, a transponder, etc. In some non-limiting embodiments or aspects, a payment device may include volatile or non-volatile memory to store information (e.g., an account identifier, an account holder's name, etc.).

[0069] As used herein, the term "payment gateway" may refer to an entity and / or a payment processing system operated by or on behalf of such an entity that provides payment services (e.g., transaction service provider payment services, payment processing services, etc.) to one or more merchants (e.g., merchant service provider, payment service provider, payment facilitator, payment facilitator with a contract with an acquirer, payment aggregator, etc.). The payment service may be associated with the use of a payment device managed by a transaction service provider. As used herein, the term "payment gateway system" may refer to one or more computer systems, computer devices, servers, server groups, etc. operated by or on behalf of a payment gateway.

[0070] As used herein, the term "server" may refer to or include one or more computing devices that are operated by or facilitate communications and processing by multiple parties in a network environment such as the Internet, but it should be understood that communications may be facilitated through one or more public or private network environments, and that there may be various other arrangements. In addition, multiple computing devices (e.g., servers, point of sale (POS) devices, mobile devices, etc.) that communicate directly or indirectly in a network environment may constitute a "system." As used herein, references to "servers" or "processors" may refer to previously described servers and / or processors, different servers and / or processors, and / or combinations of servers and / or processors that are stated to perform previous steps or functions. For example, as used in the specification and claims, a first server and / or first processor stated to perform a first step or function may refer to the same or different servers and / or processors stated to perform a second step or function.

[0071] As used herein, the term "transaction service provider" may refer to an entity that receives transaction authorization requests from merchants or other entities and, in some cases, provides payment assurance through an agreement between the transaction service provider and the issuer organization. For example, a transaction service provider may include, e.g. The term "transaction processing system" may refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction processing server executing one or more software applications. A transaction processing server may include one or more processors and, in some non-limiting embodiments or aspects, may be operated by or on behalf of a transaction service provider.

[0072] Non-limiting embodiments or aspects of the disclosed subject matter relate to systems, methods, and computer program products for processing payment transactions through an electronic payment processing network. The electronic payment processing network may include a transaction processing system that communicates with one or more acquirer systems and one or more issuer systems to process electronic payment transactions initiated between a user (e.g., a consumer) and a merchant system. For example, non-limiting embodiments or aspects of the disclosed subject matter enable an acquirer to initiate clearing processing of an electronic payment transaction by providing a single key matching identifier in a clearing request message for each electronic payment transaction. The present disclosure reduces the burden on computing resources consumed by the acquirer system by reducing the number of data elements received and / or stored by the acquirer system for each transaction. The present disclosure also reduces or eliminates the need for the acquirer system to execute, match, and return logic in order to generate a clearing request. By reducing the burden on the acquirer system, the present disclosure also speeds up the clearing of transactions and reduces exposure to losses caused by delays in clearing transactions. According to some non-limiting embodiments or aspects, the clearing of transactions may alternatively be processed in real time or near real time relative to the transmission of response messages (e.g., after the authorization process is completed). Compared to existing systems, the present disclosure also reduces or eliminates redundant processing of data elements involved in clearing transactions. As opposed to the acquirer system first processing a complete set of clearing data elements to generate a clearing request, and then the transaction processing system reprocessing much of the same data to initiate clearing processing, the present disclosure significantly reduces processing on the part of the acquirer system (and therefore the entire payment network) to generate a clearing request. In addition, the present disclosure reduces the likelihood that a single transaction will be processed more than once, thereby simplifying the clearing process.

[0073] Reference now Figure 1 , Figure 1 1 is a diagram of a non-limiting embodiment or aspect of an exemplary environment 100 in which systems, methods, and / or products as described herein may be implemented. Figure 1 As shown, environment 100 may include a transaction processing system 102 , an issuer system 104 , a client device 106 , a merchant system 108 , an acquirer system 110 , and / or a communication network 112 .

[0074] The transaction service provider system 102 may include one or more devices capable of receiving information from and / or transmitting information to the issuer system 104, the client device 106, the merchant system 108, and / or the acquirer system 110 via the communication network 112. For example, the transaction processing system 102 may include a computing device, such as a server (e.g., a transaction processing server), a server group, and / or other similar devices. In some non-limiting embodiments or aspects, the transaction processing system 102 may be associated with a transaction service provider described herein. In some non-limiting embodiments or aspects, the transaction processing system 102 may communicate with a data storage device, which may be local or remote to the transaction processing system 102. In some non-limiting embodiments or aspects, the transaction processing system 102 may be capable of receiving information from the data storage device, storing information in the data storage device, transmitting information to the data storage device, or searching for information stored in the data storage device.

[0075] The issuer system 104 may include one or more devices capable of receiving information from and / or transmitting information to the transaction processing system 102, the client device 106, the merchant system 108, and / or the acquirer system 110 via the communication network 112. For example, the issuer system 104 may include a computing device, such as a server, a server group, and / or other similar devices. In some non-limiting embodiments or aspects, the issuer system 104 may be associated with an issuer organization described herein. For example, the issuer system 104 may be associated with an issuer organization that issues credit accounts, debit accounts, credit cards, debit cards, and / or the like to users associated with the client device 106.

[0076] The client devices 106 may include one or more devices capable of receiving information from and / or transmitting information to the transaction processing system 102, the issuer system 104, the merchant system 108, and / or the acquirer system 110 via the communication network 112. Additionally or alternatively, each client device 106 may include a device capable of receiving information from and / or transmitting information to other client devices 106 via the communication network 112, another network (e.g., a temporary network, a local network, a private network, a virtual private network, etc.), and / or any other suitable communication technology. For example, the client devices 106 may include client devices, etc. In some non-limiting embodiments or aspects, the client devices 106 may or may not be capable of communicating via a short-range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, Communication connection, communication connection, etc.) (e.g., from merchant system 108 or from another client device 106), and / or transmit information (e.g., to merchant system 108) via a short-range wireless communication connection.

[0077] The merchant system 108 may include one or more devices capable of receiving information from and / or transmitting information to the transaction processing system 102, the issuer system 104, the client device 106, and / or the acquirer system 110 via the communication network 112. The merchant system 108 may also include a communication connection (e.g., an NFC communication connection, an RFID communication connection, a Communication connection, 102, a communication connection, etc.) and / or a device for transmitting information to the client device 106 via the communication network 112, the communication connection, etc. In some non-limiting embodiments or aspects, the merchant system 108 may include a computing device, such as a server, a server group, a client device, a client device group, and / or other similar devices. In some non-limiting embodiments or aspects, the merchant system 108 may be associated with the merchant described herein. In some non-limiting embodiments or aspects, the merchant system 108 may include one or more client devices. For example, the merchant system 108 may include a client device that allows the merchant to transmit information to the transaction processing system 102. In some non-limiting embodiments or aspects, the merchant system 108 may include one or more devices that can be used by merchants to conduct payment transactions with users, such as computers, computer systems, and / or peripheral devices. For example, the merchant system 108 may include a POS device and / or a POS system.

[0078] The acquirer system 110 may include one or more devices capable of receiving information from and / or transmitting information to the transaction processing system 102, the issuer system 104, the client device 106, and / or the merchant system 108 via the communication network 112. For example, the acquirer system 110 may include a computing device, a server, a server group, etc. In some non-limiting embodiments or aspects, the acquirer system 110 may be associated with an acquirer as described herein.

[0079] The communication network 112 may include one or more wired and / or wireless networks. For example, the communication network 112 may include a cellular network (e.g., Long Term Evolution). networks, third generation (3G) networks, fourth generation (4G) networks, fifth generation (5G) networks, code division multiple access (CDMA) networks, etc.), public land mobile networks (PLMNs), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), telephone networks (e.g., public switched telephone networks (PSTNs)), private networks (e.g., private networks associated with transaction service providers), ad hoc networks, intranets, the Internet, fiber-optic-based networks, cloud computing networks, etc., and / or combinations of these or other types of networks.

[0080] supply Figure 1 The number and arrangement of systems, devices, and / or networks shown are examples. Figure 1 There may be additional systems, devices, and / or networks, fewer systems, devices, and / or networks, different systems, devices, and / or networks, and / or systems, devices, and / or networks arranged in a different manner than those shown in FIG. Moreover, the present invention may be implemented within a single system or device. Figure 1 two or more systems or devices shown in, or Figure 1 A single system or device shown in the environment 100 may be implemented as multiple distributed systems or devices. Additionally or alternatively, a set of systems (e.g., one or more systems) and / or a set of devices (e.g., one or more devices) of the environment 100 may perform one or more functions described as being performed by another set of systems or another set of devices of the environment 100.

[0081] Reference now Figure 2 , Figure 2 is an example of a process 200 for processing a payment transaction through an electronic payment processing network in accordance with some non-limiting embodiments or aspects. Figure 2 The steps shown in are for exemplary purposes only. It should be understood that in non-limiting embodiments or aspects, additional, fewer, different and / or different order of steps may be used. In some non-limiting embodiments or aspects, one or more steps of process 200 may be performed by transaction processing system 102 (e.g., one or more devices of transaction processing system 102) (e.g., completely, partially, etc.). In some non-limiting embodiments or aspects, one or more steps of process 200 may be performed by another system, another device, another group of systems or another group of devices (e.g., issuer system 104, customer device 106, merchant system 108 and / or acquirer system 110, etc.) that is separate from or includes transaction processing system 102 (e.g., completely, partially, etc.). It should be understood that a subsequent step may be automatically performed in response to the completion of at least one previous step.

[0082] like Figure 2As shown, at step 202, process 200 may include receiving an authorization request message. For example, transaction processing system 102 may receive the authorization request message from acquirer system 110. In some non-limiting embodiments or aspects, the authorization request message may be associated with an electronic payment transaction. In some non-limiting embodiments or aspects, the authorization request message may include first transaction data associated with the electronic payment transaction (e.g., transaction amount, transaction date, transaction time, other data elements specified in ISO8583, etc.).

[0083] like Figure 2 As shown, at step 204, process 200 may include generating a unique identifier. For example, in response to receiving the authorization request message, transaction processing system 102 may generate a unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the unique identifier may be able to uniquely identify the electronic payment transaction relative to any other electronic payment transaction.

[0084] In some non-limiting embodiments or aspects, the unique identifier may be a code (e.g., a transaction identification number). For example, the unique identifier may be a unique numeric, alphabetic, and / or alphanumeric identifier. In some non-limiting embodiments or aspects, the transaction processing system 102 may automatically generate and / or assign a transaction identification number to an electronic payment transaction when the transaction is initiated.

[0085] In some non-limiting embodiments or aspects, the transaction processing system 102 may transmit the authorization request message to the issuer system 104 to cause the issuer system 104 to generate an authorization decision.

[0086] like Figure 2 As shown, at step 206, process 200 may include receiving an authorization response message. For example, transaction processing system 102 may receive an authorization response message from issuer system 104. In some non-limiting embodiments or aspects, the authorization response message may be associated with an electronic payment transaction. In some non-limiting embodiments or aspects, the authorization message may include second transaction data associated with the electronic payment transaction that is different from the first transaction data. In some non-limiting embodiments or aspects, the second transaction data may include an authorization decision. The authorization decision may indicate whether the electronic payment transaction is authorized, rejected, and / or at least partially authorized. The second transaction data may also include data generated by issuer system 104 in the process of generating an authorization decision associated with the electronic payment transaction.

[0087] In some non-limiting embodiments or aspects, in response to receiving the authorization request message, the issuer system 104 may generate an authorization decision. In some non-limiting embodiments or aspects, when generating the authorization decision, the issuer system 104 may determine whether the electronic payment transaction is authorized, denied, and / or partially authorized.

[0088] In some non-limiting embodiments or aspects, the issuer system 104 may generate an authorization response message. For example, the issuer system 104 may generate an authorization response message associated with the electronic payment transaction based on and / or automatically in response to receiving at least one of the authorization request message, the transaction identification number, and / or the second transaction data. In some non-limiting embodiments or aspects, the issuer system 104 may generate an authorization response message in response to receiving the authorization request message and / or in response to generating an authorization decision.

[0089] like Figure 2 As shown, at step 208, process 200 may include storing transaction data. For example, transaction processing system 102 may store transaction data. In some non-limiting embodiments or aspects, transaction processing system 102 may store at least a portion of the first transaction data and / or the second transaction data in association with a unique identifier of the electronic payment transaction.

[0090] In some non-limiting embodiments or aspects, the transaction processing system 102 may store at least a portion of the first transaction data and / or the second transaction data in a memory of at least one device of the transaction processing system 102 in association with a unique identifier of the electronic payment transaction.

[0091] like Figure 2 As shown, at step 210, process 200 may include transmitting a response message. For example, transaction processing system 102 may transmit the response message to acquirer system 110. In some non-limiting embodiments or aspects, transaction processing system 102 may generate a response message. In some non-limiting embodiments or aspects, the response message may include a unique identifier and / or an authorization decision. Acquirer system 110 may store at least a portion of the data elements included in the response message in a data storage device, for example, by storing the unique identifier in the data storage device. Acquirer system 110 may not store at least a portion of the first transaction data and the second transaction data stored by the transaction processing system, thereby reducing the computational load on the acquirer system to process (e.g., including clearing) the electronic payment transaction.

[0092] like Figure 2As shown, at step 212, process 200 may include receiving a clearing request message. For example, transaction processing system 102 may receive a clearing request message from acquirer system 110. In some non-limiting embodiments or aspects, the clearing request may include a unique identifier associated with the electronic payment transaction.

[0093] In some non-limiting embodiments or aspects, the acquirer system 110 can generate a clearing request. In some non-limiting embodiments or aspects, the acquirer system 110 can send the clearing request to the transaction processing system 102.

[0094] In some non-limiting embodiments or aspects, the clearing request message may include only the unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the clearing request message may include only the unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data. For example, if the transaction data, such as the value of the transaction amount, changes before the transaction is cleared, the acquirer system 110 may include the changed value of the transaction amount and the unique identifier. In some non-limiting embodiments or aspects, the clearing request message may be received by the transaction processing system 102 in real time or near real time relative to the transmission of the response message. The clearing request message may be received by the transaction processing system 102 in less than 1 hour, less than 30 minutes, less than 5 minutes, less than 1 minute, less than 10 seconds, or less than 1 second relative to the transmission of the response message. For example, the clearing request message may not be submitted in association with a clearing batch of multiple electronic payment transactions at the end of the day, but may be submitted in real time or near real time relative to the transmission of the response message.

[0095] In some non-limiting embodiments or aspects, the clearing request message may not include transaction data associated with transactions other than electronic payment transactions. For example, the clearing request message may not be submitted in association with a clearing batch of multiple electronic payment transactions.

[0096] like Figure 2 As shown, at step 214, process 200 may include retrieving stored transaction data. For example, in response to receiving a clearing request, transaction processing system 102 may retrieve at least a portion of first transaction data and second transaction data stored in association with a unique identifier from the clearing request message from a memory of at least one device of transaction processing system 102. Transaction processing system 102 may query a database in which transaction data is stored based on the unique identifier included in the clearing request.

[0097] In some non-limiting embodiments or aspects, at least a portion of the first data and the second transaction data stored by the transaction processing system 102 in association with the unique identifier of the electronic payment transaction may include all transaction data required to clear the electronic payment transaction.

[0098] like Figure 2 As shown, at step 216, process 200 may include initiating clearing of the electronic payment transaction. For example, transaction processing system 102 may initiate clearing of the electronic payment transaction based on at least a portion of the retrieved first transaction data and second transaction data associated with the unique identifier. For example, clearing may include settlement, which may include automatically transferring at least a portion of the transaction amount of the electronic payment transaction from an account of a user (a user who initiates the electronic payment transaction using a payment device) to an account of a merchant.

[0099] Reference now Figure 4 , shows a flow chart of a method 400 of network message enhancement for processing payment transactions through an electronic payment processing network according to some non-limiting embodiments or aspects. Figure 4 The steps shown in are for exemplary purposes only. It should be understood that in non-limiting embodiments or aspects, additional, fewer, different and / or different order of steps may be used. In some non-limiting embodiments or aspects, one or more steps of method 400 may be performed by transaction processing system 402 (e.g., one or more devices of transaction processing system 102) (e.g., completely, partially, etc.). In some non-limiting embodiments or aspects, one or more steps of process 400 may be performed by another system, another device, another group of systems or another group of devices (e.g., issuer system 404, transaction processing database 406 and / or acquirer system 410, etc.) that is separate from or includes transaction processing system 402 (e.g., completely, partially, etc.). In some non-limiting embodiments or aspects, transaction processing system 402 may be the same, similar and / or a part of transaction processing system 102. In some non-limiting embodiments or aspects, issuer system 404 may be the same, similar and / or a part of issuer system 104. In some non-limiting embodiments or aspects, acquirer system 410 can be the same as, similar to, and / or a portion of acquirer system 110 .

[0100] In some non-limiting embodiments or aspects, the transaction processing system 402 may include a transaction processing database 406 (e.g., a data storage device), as described herein. In some non-limiting embodiments or aspects, the transaction processing database 406 may be in communication with the transaction processing system 402. In some non-limiting embodiments or aspects, the transaction processing database 406 may be part of the transaction processing system 402. In some non-limiting embodiments or aspects, the transaction processing database 406 may include at least one memory.

[0101] As shown in step 1, the acquirer system 410 can communicate with the transaction processing system 402. For example, the acquirer system 410 can generate and / or send an authorization request message associated with the electronic payment transaction to the transaction processing system 402. The authorization request message can include first transaction data associated with the electronic payment transaction (e.g., transaction amount, transaction date, transaction time, other data elements specified in ISO 8583, etc.).

[0102] In some non-limiting embodiments or aspects, in response to receiving the authorization request message, the transaction processing system 402 may automatically generate a unique identifier associated with the first transaction data. The unique identifier may be associated with the electronic payment transaction and / or may be able to uniquely identify the electronic payment transaction relative to other electronic payment transactions. For example, the unique identifier may be a transaction identification number. In some non-limiting embodiments or aspects, in response to initiating a transaction and / or generating a unique identifier, the transaction processing system 402 may automatically assign a transaction identification number to the electronic payment transaction.

[0103] As shown in step 2, transaction processing system 402 may communicate with issuer system 404. For example, in response to generating a transaction identification number and / or assigning a transaction identification number to an electronic payment transaction, transaction processing system 402 may send an authorization request message and / or the transaction identification number to issuer system 404. In some non-limiting embodiments or aspects, the authorization request message may be modified to include the transaction identification number. Issuer system 404 may store the transaction identification number in association with the electronic payment transaction in a data storage device associated therewith.

[0104] As shown in step 3, the issuer system 404 may determine whether the electronic payment transaction is authorized (e.g., approved) or denied (e.g., rejected), or some combination thereof (e.g., partially approved). For example, in response to receiving the authorization request message and / or the transaction identification number, the issuer system 404 may generate an authorization decision. In some non-limiting embodiments or aspects, in response to determining whether the electronic payment transaction is authorized or denied, the issuer system 404 may generate an authorization decision (e.g., an indication of whether the electronic payment is authorized or denied). In some non-limiting embodiments or aspects, in response to determining whether the electronic payment transaction is authorized or denied, the issuer system 404 may generate an authorization response message associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the authorization response message may include the authorization decision.

[0105] As shown in step 4, the issuer system 404 may transmit an authorization response message to the transaction processing system 402. For example, the issuer system 404 may automatically send the authorization response message including the authorization decision to the transaction processing system 402.

[0106] In some non-limiting embodiments or aspects, in response to receiving the authorization response message, the transaction processing system 402 may store data associated with the authorization response message. For example, the transaction processing system 402 may store at least a portion of the first transaction data and / or the second transaction data (e.g., the authorization decision) in association with a unique identifier of the electronic payment transaction in a memory of at least one device of the transaction processing system 102 (e.g., the transaction processing database 406).

[0107] In some non-limiting embodiments or aspects, in response to receiving an authorization response message, the transaction processing system 402 may store at least a portion of the first transaction data and / or the second transaction data in the transaction processing database 406 (e.g., in a memory of the transaction processing database 406) in association with the unique identifier.

[0108] In some non-limiting embodiments or aspects, storing data associated with the authorization response message can reduce (eg, minimize) the need for transaction processing system 402 and / or acquirer system 410 retention, matching, and / or return logic.

[0109] In some non-limiting embodiments or aspects, in response to receiving an authorization response message including an authorization decision, the transaction processing system 402 can generate a response message. The response message can include a unique identifier and / or an authorization decision.

[0110] As shown in step 5, transaction processing system 402 may communicate with acquirer system 410. For example, transaction processing system 402 may transmit a response message to acquirer system 410 including a unique identifier and / or an authorization decision.

[0111] In some non-limiting embodiments or aspects, in response to receiving a response message including a unique identifier and / or an authorization decision, the acquirer system 410 may automatically generate a clearing request. The clearing request may include a unique identifier associated with the electronic payment transaction and / or updated first transaction data and / or second transaction data. In some non-limiting embodiments or aspects, the clearing request message may include only the unique identifier associated with the electronic payment transaction. In some non-limiting embodiments or aspects, the clearing request message may include only the unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data. In some non-limiting embodiments or aspects, the clearing request message may not include transaction data associated with transactions other than the electronic payment transaction. For example, the clearing request message may not be submitted in association with a clearing batch of multiple electronic payment transactions.

[0112] As shown in step 6, the acquirer system 410 can communicate with the transaction processing system 402. For example, the acquirer system 410 can automatically send a clearing request to the transaction processing system 402 to initiate a clearing transaction. In some non-limiting embodiments or aspects, the clearing request can be sent to and / or received by the transaction processing system 402 in real time (e.g., in less than 1 hour, less than 30 minutes, less than 5 minutes, less than 1 minute, less than 10 seconds, or less than 1 second) relative to the transmission of the response message.

[0113] In some non-limiting embodiments or aspects, in response to receiving the clearing request, the transaction processing system 402 may retrieve stored transaction data associated with the electronic payment transaction from the transaction processing database 406. For example, in response to receiving the clearing request, the transaction processing system 402 may retrieve at least a portion of the first transaction data and the second transaction data stored in association with the unique identifier from the clearing request message from a memory of at least one device of the transaction processing system 402. In some non-limiting embodiments or aspects, the transaction processing system 402 may retrieve the stored transaction data from the transaction processing database 406 (e.g., a memory of the transaction processing database 406).

[0114] In some non-limiting embodiments or aspects, the stored transaction data may include all transactions required to clear the electronic payment transaction. For example, at least a portion of the first transaction data and the second transaction data stored by the transaction processing system 402 in association with the unique identifier of the electronic payment transaction may include all transaction data required to clear the electronic payment transaction.

[0115] As shown in step 7, the transaction processing system 402 may modify the clearing request. For example, in response to retrieving the stored transaction data, the transaction processing system 402 may automatically modify the clearing request by populating one or more details of the clearing request with the transaction data. In some non-limiting embodiments or aspects, the transaction processing system 402 may modify the clearing request to include at least a unique identifier of the electronic payment transaction in association with at least a portion of the stored transaction data (e.g., transaction data required to clear the electronic payment transaction).

[0116] In some non-limiting embodiments or aspects, the electronic payment transaction may be cleared based on the modified clearing request. Clearing may include settlement, which may include automatically transferring at least a portion of the transaction amount of the electronic payment transaction from an account of a user (a user who initiated the electronic payment transaction using a payment device) to an account of a merchant.

[0117] Reference now Figure 3 , a diagram showing exemplary components of an apparatus 300 according to a non-limiting embodiment or aspect. For example, the apparatus 300 may correspond to Figure 1The transaction processing system 102, the issuer system 104, the customer device 106, the merchant system 108 and / or the acquirer system 110 and / or Figure 4 At least one of the transaction processing system 402, the issuer system 404, the transaction processing database 406 and / or the acquirer system 410 in the embodiment of the present invention. In some non-limiting embodiments or aspects, Figure 1 and Figure 4 Such a system or device in may include at least one device 300 and / or at least one component of a device 300. Figure 3 The number and arrangement of the components shown in are provided as examples. In some non-limiting embodiments or aspects, Figure 3 The device 300 may include additional components, fewer components, different components, or components arranged in a different manner than those shown in . Additionally or alternatively, a set of components (e.g., one or more components) of the device 300 may perform one or more functions described as being performed by another set of components of the device 300.

[0118] like Figure 3 As shown, the device 300 may include a bus 302, a processor 304, a memory 306, a storage component 308, an input component 310, an output component 312, and a communication interface 314. The bus 302 may include components that permit communication between components of the device 300. In some non-limiting embodiments or aspects, the processor 304 may be implemented in hardware, firmware, or a combination of hardware and software. For example, the processor 304 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.). The memory 306 may include a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the processor 304.

[0119] Continue to refer Figure 3, the storage component 308 may store information and / or software related to the operation and use of the device 300. For example, the storage component 308 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, a solid-state disk, etc.) and / or another type of computer-readable medium. The input component 310 may include a component that permits the device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). In addition or alternatively, the input component 310 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). The output component 312 may include a component that provides output information from the device 300 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.). The communication interface 314 may include a transceiver-type component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables the device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. The communication interface 314 may permit the device 300 to receive information from another device and / or provide information to another device. For example, the communication interface 314 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, Interface, cellular network interface, etc.

[0120] The device 300 can perform one or more processes described herein. The device 300 can perform these processes based on the processor 304 executing software instructions stored by a computer-readable medium such as a memory 306 and / or a storage component 308. The computer-readable medium may include any non-transitory memory device. The memory device includes a memory space located inside a single physical storage device or a memory space distributed across multiple physical storage devices. The software instructions can be read from another computer-readable medium or from another device to the memory 306 and / or the storage component 308 via the communication interface 314. When executed, the software instructions stored in the memory 306 and / or the storage component 308 can cause the processor 304 to perform one or more processes described herein. In addition or alternatively, the hard-wired circuit system can replace the software instructions or be used in combination with the software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any specific combination of hardware circuit systems and software. The term "programmed or configured" used herein refers to the arrangement of software, hardware circuit systems, or any combination thereof on one or more devices.

[0121] Although the embodiments have been described in detail for the purpose of illustration, it should be understood that such details are used only for that purpose and that the present disclosure is not limited to the disclosed embodiments or aspects, but on the contrary is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment or aspect may be combined with one or more features of any other embodiment or aspect.

Claims

1. A method for processing a payment transaction via an electronic payment processing network, the method comprising: receiving, by a transaction processing system, an authorization request message associated with an electronic payment transaction from an acquirer system, wherein the authorization request message includes first transaction data associated with the electronic payment transaction; generating, by the transaction processing system, a unique identifier associated with the electronic payment transaction; receiving, by the transaction processing system from an issuer system, an authorization response message associated with the electronic payment transaction, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized; storing, by the transaction processing system, at least a portion of the first transaction data and the second transaction data in association with a unique identifier of the electronic payment transaction; transmitting, by the transaction processing system to the acquirer system, a response message including the unique identifier and the authorization decision; receiving, by the transaction processing system from the acquirer system, a clearing request message including a unique identifier associated with the electronic payment transaction; in response to receiving the clearing request message, retrieving, by the transaction processing system, at least a portion of the first transaction data and the second transaction data stored in association with a unique identifier from the clearing request message; and Clearing of the electronic payment transaction is initiated by the transaction processing system based on at least a portion of the retrieved first transaction data and the second transaction data associated with the unique identifier.

2. The method according to claim 1, further comprising: The authorization request message is transmitted by the transaction processing system to an issuer system, wherein the issuer system generates the authorization decision.

3. The method according to claim 1, wherein: The clearing request message includes only a unique identifier associated with the electronic payment transaction.

4. The method according to claim 1, wherein: The clearing request message includes only the unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data.

5. The method according to claim 1, wherein: The clearing request message does not include transaction data associated with transactions other than the electronic payment transaction.

6. The method according to claim 1, wherein: The transaction processing system receives the clearing request message in real time or near real time relative to the transmission of the response message.

7. The method according to claim 1, wherein: At least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier for the electronic payment transaction includes all transaction data required to clear the electronic payment transaction.

8. A system comprising: at least one processor; as well as at least one non-transitory computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to: receiving, from an acquirer system, an authorization request message associated with an electronic payment transaction, wherein the authorization request message includes first transaction data associated with the electronic payment transaction; generating a unique identifier associated with the electronic payment transaction; receiving an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized; storing at least a portion of the first transaction data and the second transaction data in association with a unique identifier of the electronic payment transaction; transmitting a response message including the unique identifier and the authorization decision to the acquirer system; receiving, from the acquirer system, a clearing request message including a unique identifier associated with the electronic payment transaction; in response to receiving the clearing request message, retrieving at least a portion of the first transaction data and the second transaction data stored in association with a unique identifier from the clearing request message; and Clearing of the electronic payment transaction is initiated based on at least a portion of the retrieved first transaction data and the second transaction data associated with the unique identifier.

9. The system according to claim 8, wherein: The instructions further cause the at least one processor to: The authorization request message is transmitted to an issuer system, wherein the issuer system generates the authorization decision.

10. The system according to claim 8, wherein: The clearing request message includes only a unique identifier associated with the electronic payment transaction.

11. The system according to claim 8, wherein: The clearing request message includes only the unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data.

12. The system according to claim 8, wherein: The clearing request message does not include transaction data associated with transactions other than the electronic payment transaction.

13. The system according to claim 8, wherein: The transaction processing system receives the clearing request message in real time or near real time relative to the transmission of the response message.

14. The system according to claim 8, wherein: At least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with a unique identifier for the electronic payment transaction includes all transaction data required to clear the electronic payment transaction.

15. A computer program product comprising at least one non-transitory computer readable medium, the at least one non-transitory computer readable medium comprising program instructions that, when executed by at least one processor, cause the at least one processor to: receiving an authorization request message associated with an electronic payment transaction from an acquirer system, wherein: The authorization request message includes first transaction data associated with the electronic payment transaction; generating a unique identifier associated with the electronic payment transaction; receiving an authorization response message associated with the electronic payment transaction from an issuer system, wherein the authorization response message includes second transaction data associated with the electronic payment transaction, the second transaction data including an authorization decision indicating that the electronic payment transaction is authorized; storing at least a portion of the first transaction data and the second transaction data in association with a unique identifier of the electronic payment transaction; transmitting a response message including the unique identifier and the authorization decision to the acquirer system; receiving, from the acquirer system, a clearing request message including a unique identifier associated with the electronic payment transaction; in response to receiving the clearing request message, retrieving at least a portion of the first transaction data and the second transaction data stored in association with a unique identifier from the clearing request message; and Clearing of the electronic payment transaction is initiated based on at least a portion of the retrieved first transaction data and the second transaction data associated with the unique identifier.

16. The computer program product of claim 15, wherein: The program instructions further cause the at least one processor to: The authorization request message is transmitted to an issuer system, wherein the issuer system generates the authorization decision.

17. The computer program product of claim 15, wherein: The clearing request message includes only a unique identifier associated with the electronic payment transaction.

18. The computer program product of claim 15, wherein: The clearing request message includes only the unique identifier associated with the electronic payment transaction and the updated first transaction data and / or second transaction data.

19. The computer program product of claim 15, wherein: The clearing request message does not include transaction data associated with transactions other than the electronic payment transaction.

20. The computer program product of claim 15, wherein: The clearing request message is received by the transaction processing system in real time or near real time relative to the transmission of the response message, and wherein at least a portion of the first transaction data and the second transaction data stored by the transaction processing system in association with the unique identifier of the electronic payment transaction includes all transaction data required to clear the electronic payment transaction.

Images