Systems, methods, and computer program products for generating digital receipts
By using account identifiers and transaction identifiers to process transaction data in the payment processing network and generating and transmitting digital receipt objects, the problem of transaction dispute processing resources and information sharing privacy in the payment processing network is solved, and efficiency and privacy protection are improved.
Patent Information
- Application Number
- CN202211029931.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-08-25
- Filing Date
- 2022-08-25
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-08-25
AI Technical Summary
The existing payment processing network is resource-intensive when handling transaction disputes and refunds, and lacks effective information communication, which makes it difficult to generate receipts for transaction records, especially because users do not want to share personal information with merchants.
By using an account identifier to receive a transaction request message from the merchant system, assign a transaction identifier, and store the relevant transaction data and identifiers in the data storage device, receive digital receipt data, match the transaction identifier, generate and transmit digital receipt objects, Reduce communication times and computing resource consumption.
It realizes the efficiency of generating digital receipts in the payment processing network, reduces resource consumption and communication times for transaction dispute processing, and protects user privacy.
Smart Images

Figure CN115731039B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to digital receipts and, in some non-limiting embodiments or aspects, to systems, methods, and computer program products for generating digital receipts. Background Art
[0002] In existing payment processing networks, disputes and chargebacks regarding transactions are resource intensive for all systems involved due to the lack of available information and the lack of communication between the parties. In addition, the existing infrastructure for communicating with all parties to a transaction (including the issuer institution, the merchant system, and the account holder) is limited in terms of issuing receipts showing a record of the transaction. Users who do not wish to share personal information (e.g., email address, phone number, account identifier, etc.) with merchants are particularly limited. Summary of the invention
[0003] According to a non-limiting embodiment or aspect, a computer-implemented method is provided, comprising: receiving a transaction request message for a transaction between a consumer and a merchant system using an account identifier from a merchant system via a first communication channel, the transaction request message comprising first transaction data associated with the transaction; assigning a transaction identifier to the transaction using at least one processor; storing the first transaction data in association with the transaction identifier in at least one data storage device; receiving digital receipt data via a second communication channel independent of the first communication channel, the digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data; processing the transaction using the account identifier using at least one processor; determining the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data storage device using the at least one processor; storing the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receiving a query including the transaction identifier from at least one external system; and transmitting the digital receipt object to the at least one external system in response to the query.
[0004] In a non-limiting embodiment or aspect, the first transaction data and the second transaction data each include a checkout identifier generated by the merchant system, wherein matching the second transaction data with the first transaction data in the at least one data storage device includes matching the checkout identifier from the first transaction data with the checkout identifier from the second transaction data. In a non-limiting embodiment or aspect, the digital receipt object includes an electronic image file. In a non-limiting embodiment or aspect, the digital receipt object includes a structured data file. In a non-limiting embodiment or aspect, the method further includes automatically transmitting the digital receipt object and the transaction identifier to an issuer system, the at least one external system including the issuer system or at least one other system. In a non-limiting embodiment or aspect, the first communication channel includes an electronic payment processing system, and the second communication channel includes an Internet-based communication channel. In a non-limiting embodiment or aspect, the at least one external system includes an issuer banking application displayed on a user computing device.
[0005] According to a non-limiting embodiment or aspect, a system is provided, comprising: at least one data storage device, the at least one data storage device comprising transaction data stored in association with a transaction identifier; and at least one processor in communication with the data storage device, the at least one processor being programmed or configured to: receive a transaction request message for a transaction between a consumer and a merchant system from a merchant system using an account identifier via a first communication channel, the transaction request message comprising first transaction data associated with the transaction; assign a transaction identifier to the transaction; store the first transaction data in association with the transaction identifier in the at least one data storage device; and transmit the transaction request message to the merchant system via a second communication channel independent of the first communication channel. receiving digital receipt data, the digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data; processing the transaction using the account identifier; determining the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data storage device; storing the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receiving a query including the transaction identifier from at least one external system; and transmitting the digital receipt object to the at least one external system in response to the query.
[0006] In a non-limiting embodiment or aspect, the first transaction data and the second transaction data each include a checkout identifier generated by the merchant system, wherein matching the second transaction data with the first transaction data in the at least one data storage device includes matching the checkout identifier from the first transaction data with the checkout identifier from the second transaction data. In a non-limiting embodiment or aspect, the digital receipt object includes an electronic image file. In a non-limiting embodiment or aspect, the digital receipt object includes a structured data file. In a non-limiting embodiment or aspect, the at least one processor is further programmed or configured to automatically transmit the digital receipt object and the transaction identifier to an issuer system, the at least one external system including the issuer system or at least one other system. In a non-limiting embodiment or aspect, the first communication channel includes an electronic payment processing system, and the second communication channel includes an Internet-based communication channel. In a non-limiting embodiment or aspect, the at least one external system includes an issuer bank application displayed on a user computing device.
[0007] According to a non-limiting embodiment or aspect, a computer program product is provided that includes at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to: receive, from a merchant system via a first communication channel, a transaction request message for a transaction between a consumer and a merchant system using an account identifier, the transaction request message including first transaction data associated with the transaction; assign a transaction identifier to the transaction; store the first transaction data in at least one data storage device in association with the transaction identifier; receive, via a second communication channel independent of the first communication channel, digital receipt data including a digital receipt object and second transaction data associated with the transaction, the second transaction data including at least a subset of transaction parameters of the first transaction data; process the transaction using the account identifier; determine the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data storage device; store the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receive a query including the transaction identifier from at least one external system; and transmit the digital receipt object to the at least one external system in response to the query.
[0008] Other non-limiting embodiments or aspects are set forth in the following numbered clauses:
[0009] Clause 1: A computer-implemented method comprising: receiving, via a first communication channel, a transaction request message for a transaction between a consumer and a merchant system using an account identifier, the transaction request message comprising first transaction data associated with the transaction; assigning, using at least one processor, a transaction identifier to the transaction; storing, in association with the transaction identifier, the first transaction data in at least one data storage device; receiving, via a second communication channel independent of the first communication channel, digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data; processing, using at least one processor, the transaction using the account identifier; determining, using at least one processor, the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data storage device; storing, in association with the transaction identifier, the digital receipt object in the at least one data storage device or at least one other storage device; receiving a query including the transaction identifier from at least one external system; and transmitting, in response to the query, the digital receipt object to the at least one external system.
[0010] Clause 2: A computer-implemented method according to clause 1, wherein the first transaction data and the second transaction data each include a checkout identifier generated by the merchant system, and wherein matching the second transaction data with the first transaction data in the at least one data storage device includes: matching the checkout identifier from the first transaction data with the checkout identifier from the second transaction data.
[0011] Clause 3: The computer-implemented method of clause 1 or 2, wherein the digital receipt object comprises an electronic image file.
[0012] Clause 4: The computer-implemented method of any of clauses 1-3, wherein the digital receipt object comprises a structured data file.
[0013] Clause 5: The computer-implemented method of any of clauses 1-4, further comprising automatically transmitting the digital receipt object and the transaction identifier to an issuer system, wherein the at least one external system comprises the issuer system or at least one other system.
[0014] Clause 6: The computer-implemented method of any of clauses 1-5, wherein the first communication channel comprises an electronic payment processing system, and wherein the second communication channel comprises an Internet-based communication channel.
[0015] Clause 7: The computer-implemented method of any of clauses 1-6, wherein the at least one external system comprises an issuer bank application displayed on a user computing device.
[0016] Clause 8: A system comprising: at least one data storage device, the at least one data storage device including transaction data stored in association with a transaction identifier; and at least one processor in communication with the data storage device, the at least one processor being programmed or configured to: receive a transaction request message for a transaction between a consumer and a merchant system from a merchant system using an account identifier over a first communication channel, the transaction request message including first transaction data associated with the transaction; assign a transaction identifier to the transaction; store the first transaction data in association with the transaction identifier in the at least one data storage device; receive digital receipt data over a second communication channel independent of the first communication channel, the digital receipt data including a digital receipt object and second transaction data associated with the transaction, the second transaction data including at least a subset of transaction parameters of the first transaction data; process the transaction using the account identifier; determine the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data storage device; store the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receive a query including the transaction identifier from at least one external system; and transmit the digital receipt object to the at least one external system in response to the query.
[0017] Clause 9: A system according to clause 8, wherein the first transaction data and the second transaction data each include a checkout identifier generated by the merchant system, and wherein matching the second transaction data with the first transaction data in the at least one data storage device includes: matching the checkout identifier from the first transaction data with the checkout identifier from the second transaction data.
[0018] Clause 10: The system of clause 8 or 9, wherein the digital receipt object comprises an electronic image file.
[0019] Clause 11: The system of any of clauses 8-10, wherein the digital receipt object comprises a structured data file.
[0020] Clause 12: A system according to any of clauses 8-11, wherein the at least one processor is further programmed or configured to automatically transmit the digital receipt object and the transaction identifier to an issuer system, wherein the at least one external system includes the issuer system or at least one other system.
[0021] Clause 13: The system of any of clauses 8-12, wherein the first communication channel comprises an electronic payment processing system, and wherein the second communication channel comprises an Internet-based communication channel.
[0022] Clause 14: The system of any of clauses 8-13, wherein the at least one external system comprises an issuer bank application displayed on a user computing device.
[0023] 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, from a merchant system via a first communication channel, a transaction request message for a transaction between a consumer and a merchant system using an account identifier, the transaction request message comprising first transaction data associated with the transaction; assign a transaction identifier to the transaction; store the first transaction data in association with the transaction identifier in at least one data storage device; receive, via a second communication channel independent of the first communication channel, digital receipt data, the digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data; process the transaction using the account identifier; determine the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data storage device; store the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receive a query including the transaction identifier from at least one external system; and transmit the digital receipt object to the at least one external system in response to the query.
[0024] Clause 16: A computer program product according to clause 15, wherein the first transaction data and the second transaction data each include a checkout identifier generated by the merchant system, and wherein matching the second transaction data with the first transaction data in the at least one data storage device includes: matching the checkout identifier from the first transaction data with the checkout identifier from the second transaction data.
[0025] Clause 17: The computer program product of clause 15 or 16, wherein the digital receipt object comprises an electronic image file.
[0026] Clause 18: A computer program product as recited in any of Clauses 15-17, wherein the digital receipt object comprises a structured data file.
[0027] Clause 19: A computer program product according to any of clauses 15-18, wherein the at least one processor is further caused to automatically transmit the digital receipt object and the transaction identifier to an issuer system, wherein the at least one external system comprises the issuer system or at least one other system.
[0028] Clause 20: The computer program product of any of clauses 15-19, wherein the first communication channel comprises an electronic payment processing system, and wherein the second communication channel comprises an Internet-based communication channel.
[0029] 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 after 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 illustration and description purposes only and are not intended as a definition of the limits of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Additional advantages and details are explained in more detail below with reference to non-limiting, exemplary embodiments shown in the schematic drawings, in which:
[0031] Figure 1 is a schematic diagram of a system for generating a digital receipt according to a non-limiting embodiment or aspect;
[0032] Figure 2 is a schematic diagram of a system for generating a digital receipt according to a non-limiting embodiment or aspect;
[0033] Figure 3 is a sequence diagram for generating a digital receipt according to a non-limiting embodiment or aspect;
[0034] Figure 4 is a sequence diagram for generating a digital receipt according to a non-limiting embodiment or aspect; and
[0035] Figure 5 Example components of an apparatus for use in conjunction with non-limiting embodiments or aspects are shown. DETAILED DESCRIPTION
[0036] 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 description are merely exemplary embodiments or aspects of the present disclosure. Accordingly, specific dimensions and other physical characteristics relating to the embodiments or aspects disclosed herein shall not be considered limiting.
[0037] 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. Also, 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. Also, as used herein, the term "having" etc. is intended to be an open term. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on".
[0038] 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.
[0039] 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 any combination of alphanumeric 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 instances, an original account identifier such as a PAN may be associated with multiple tokens for different individuals or purposes.
[0040] As used herein, the term "communication" may refer to the reception, acceptance, transmission, transfer, 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 send information to the other unit. This may refer to a direct or indirect connection (e.g., a direct communication connection, an indirect communication connection, and / or the like) that is wired and / or wireless in nature. In addition, although the information sent 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 send 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.
[0041] As used herein, the term "computing device" may refer to one or more electronic devices configured to process data. In some instances, 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, and the like. A 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.
[0042] 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 an electronic wallet for a customer, such as And / or other similar electronic payment systems. In some non-limiting examples, the issuing bank may be an electronic wallet provider.
[0043] As used herein, the term "issuer institution" may refer to one or more entities, such as a bank, that provide customers with accounts for conducting transactions (e.g., payment transactions), such as initiating credit and / or debit payments. For example, an issuer institution may provide a customer with an account identifier, such as a PAN, that uniquely identifies one or more accounts associated with the customer. The account identifier may be implemented on a portable financial device, such as a physical financial instrument (e.g., 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 that executes one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing transactions.
[0044] 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. As used herein, a "point of sale (POS) system" may refer to one or more computers and / or peripheral devices used by a merchant to engage in payment transactions with customers, including one or more card readers, near field communication (NFC) receivers, RFID receivers and / or other contactless transceivers or receivers, contact-based receivers, payment terminals, computers, servers, input devices, and / or other similar devices that can be used to initiate payment transactions.
[0045] 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 pendant, an RFID transponder, a retailer discount or membership card, a cellular phone, an electronic wallet mobile application, a 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.).
[0046] 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, which provides payment services (e.g., transaction service provider payment services, payment processing services, etc.) to one or more merchants (e.g., transaction service provider payment services, payment processing services, etc.). The payment service may be associated with the use of a portable financial 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.
[0047] As used herein, the term "server" may refer to or include one or more computing devices operated by or facilitating 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, 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 implement previous steps or functions. For example, as used in the specification and claims, a first server and / or first processor stated to implement a first step or function may refer to the same or different servers and / or processors stated to implement a second step or function.
[0048] 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, for example , or any other entity that processes transactions. 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 that executes 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.
[0049] In a non-limiting embodiment or aspect, a digital receipt is generated for a customer purchase and provided to an entity through a query to reduce the burden of investigating a specific transaction, including unnecessary network communications and the use of computing resources. By utilizing two separate communication channels for transaction requests from merchants and digital receipts from merchants, merchants can still use existing electronic payment processing network architectures. In addition, customers who request more information about a transaction or dispute a transaction with an issuer usually have to make several separate queries, and even so, may not be able to find detailed item information for the disputed transaction. Therefore, customers who want to dispute a transaction must carefully organize their receipts and use bandwidth to upload the receipts to the issuer. In turn, the issuer must then expend computing resources and other resources to send the same information to merchants, transaction service providers, etc. to resolve the dispute. The non-limiting embodiment reduces the number of communications and the amount of computing resources consumed when a transaction is disputed or any other action using information from a receipt related to a transaction between a consumer and a merchant system is taken.
[0050] Figure 1 A system 1000 for generating a digital receipt is depicted according to a non-limiting embodiment or aspect. The system 1000 includes a transaction processing system 102 that includes a digital receipt system 100. The digital receipt system 100 is shown as part of the transaction processing system 102, but it should be understood that in non-limiting embodiments, the digital receipt system 100 can be separate and / or external to the transaction processing system 102. The digital receipt system 100 includes a computing device and / or one or more software applications executed by the computing device to store and provide digital receipts. The transaction processing system 102 and / or the digital receipt system 100 also communicate with an acquirer system 104, a merchant system 106, and an issuer system 108. The digital receipt system 100 communicates with a transaction database 114, which may include one or more data storage devices on which transaction data is stored.
[0051] Continue to refer Figure 1In operation, a user 101 may initiate a transaction with a merchant system 106, such as a merchant website or POS system. The user 101 may use a payment device, such as, but not limited to, a client computing device 110 displaying a user interface 112. After receiving payment device information from the user 101, the merchant system 106 may generate a transaction request message and transmit it to the acquirer system 104. Additionally or alternatively, the merchant system 106 may transmit the transaction request message to a payment gateway (or a payment gateway) separate from the acquirer system 104. Figure 1 108) and / or directly to the transaction processing system 102. The acquirer system 104 (or payment gateway) can then forward the transaction request message to the transaction processing system 102 for processing. The transaction processing system 102 can process the transaction request message by generating an authorization request message and transmitting the authorization request message to the issuer system 108.
[0052] Still refer to Figure 1 , the merchant system 106 may also generate a digital receipt object and transmit it to the client computing device 110 and the digital receipt system 100. The client computing device 110 may display the digital receipt object on the user interface 112. As used herein, the term "digital receipt object" refers to structured or unstructured data representing a transaction between the user 101 and the merchant system 106, such as an image of a receipt (e.g., a photo or digitally rendered receipt) and / or a structured data file (e.g., HTML, JavaScript Object Notation (JSON), Extensible Markup Language (XML), etc.). In some non-limiting examples, the digital receipt may include an email receipt containing text, images, and / or markup / layout data, such as an email receipt sent to a customer after a purchase. In non-limiting embodiments or aspects, the digital receipt object is an image without text information (e.g., without optical character recognition (OCR)). In other non-limiting embodiments or aspects, the digital receipt object is machine-readable. It should be appreciated that other forms of data may be used to construct the digital receipt object.
[0053] Continue to refer Figure 1 , merchant system 106 can transmit the digital receipt to digital receipt system 100 via a second communication channel that is different from the first communication channel used to transmit the transaction request message (e.g., via an electronic payment processing network). In some examples, the second communication channel can be a communication channel external or internal to the electronic payment processing network. For example, merchant system 106 can send the digital receipt object to digital receipt system 100 via an Internet-based communication channel, such as email, one or more Internet communication protocols (e.g., HTTP), one or more application programming interfaces (APIs), one or more links identifying a network location of a digital receipt object, etc.
[0054] Still refer to Figure 1 Once the digital receipt object is received by the digital receipt system 100, the digital receipt object is stored in the transaction database 114. In a non-limiting embodiment or aspect, in addition to the digital receipt object 116, transaction data is transmitted by the merchant system 106 with or associated with the digital receipt object 116 so that the digital receipt system 100 can match the transaction data received from the merchant system 106 with the transaction data in the transaction database 114. For example, the merchant system 106 can generate a checkout identifier (e.g., a shopping basket identifier) that is unique to the transaction and include this identifier in the transaction data sent to the acquirer system 104 (or payment gateway) (e.g., within a transaction request message) and transmit the identifier to the digital receipt system 100 along with the digital receipt object 116. The checkout identifier can be randomly generated and / or can be generated using the transaction data as input.
[0055] Figure 2 A system 2000 for generating a digital receipt is depicted in accordance with a non-limiting embodiment or aspect. Figure 2 , the digital receipt system 202 is shown to be external to the transaction processing system 102. The digital receipt system 202 may be similar to Figure 1 The digital receipt system 100 operates in. Figure 2 Also shown is a dispute resolution system 200, which may include hardware and / or software (e.g., a computing device executing one or more software applications) for handling transaction disputes. Figure 2 2 is also shown as being external to the transaction processing system 102. However, it should be appreciated that in non-limiting embodiments, the digital receipt system 202 and / or the dispute resolution system may be part of and / or controlled by the transaction processing system 102.
[0056] Continue to refer Figure 2, an additional entity 204 (e.g., a customer service agent of an issuer organization associated with the issuer system 108) operating an additional computing device 206 is also shown. In some non-limiting embodiments or aspects, the computing device 206 can be part of the issuer system 108. For example, the computing device 206 can be a customer service system operated by the issuer organization, and the issuer system 108 can be an electronic wallet system operated by the same issuer organization. Various other arrangements are possible. In the depicted example, the computing device 206 accesses the dispute resolution system 200 and displays a user interface 208 that allows the customer service agent 204 to query the dispute resolution system 200 for a particular transaction. The dispute resolution system 200 can expose one or more APIs to allow the customer service agent 204 (via the computing device 206) and / or the user 101 (via the client computing device 110) to make such queries. The dispute resolution system 200 can be queried using the transaction data, checkout identifier, and / or digital receipt object to identify corresponding data in the transaction database 114 or any other data storage device.
[0057] Still refer to Figure 2 , the digital receipt system 202 can communicate with a receipt database 210, which can include one or more data storage devices having digital receipt data stored thereon (e.g., digital receipt objects from various transactions). It should be appreciated that the digital receipt data can additionally or alternatively be stored in one or more transaction databases 114 or elsewhere. In operation, the merchant system 106 can transmit the digital receipt object and the checkout identifier to the digital receipt system 202 before, after, or simultaneously with transmitting the transaction request message to the acquirer system 104 (or payment gateway). In this manner, the customer service agent 204 can view the digital receipt object for the disputed transaction through the user interface 208. This viewing can occur while the customer service agent 204 is interacting with the user 101 (e.g., on the phone, chatting, etc.).
[0058] Reference now Figure 3 , shows a sequence diagram for generating a digital receipt according to a non-limiting embodiment or aspect. It should be understood that additional, fewer and / or different step orders may be used in non-limiting embodiments or aspects, and Figure 3The steps shown in are for example purposes only. At step s1, a customer initiates a payment transaction with a merchant system 106 using a client computing device 110. This may include a face-to-face transaction at a POS device or a remote transaction conducted through a website or mobile application. In response to the transaction request, at step s2, the merchant system 106 transmits a transaction request message to the acquirer system 104 (or a payment gateway) via a first communication channel, such as an electronic payment processing network. In addition to transaction data related to the detail transaction, the transaction request message may also include a checkout identifier that uniquely identifies this transaction among multiple transactions. The checkout identifier may be generated by the merchant system 106, or generated by any other system, and provided to the merchant system 106.
[0059] At steps s3 and s4, merchant system 106 transmits the digital receipt object to digital receipt system 100 and client computing device 110, respectively. Transmission of the digital receipt object to digital receipt system 100 may be via a second communication channel different from the first communication channel used to transmit the transaction request message in step s2, such as email, one or more Internet communication protocols (e.g., HTTP), one or more APIs, one or more links identifying the network location of the digital receipt object, etc. Transmission of the digital receipt to the client device may also be via a second communication, or may be a third communication channel different from both the first communication channel and the second communication channel.
[0060] In response to receiving the transaction request message at step s2, at step s5, the acquirer system 104 then transmits the transaction request message to the transaction processing system 102. The transaction processing system 102 then completes the transaction process ( Figure 3 ), the transaction flow involves transmitting an authorization request message to the issuer system 108, receiving an authorization response message from the issuer system 108, transmitting the result to the merchant system 106, and settling the payment transaction.
[0061] Continue to refer Figure 3 At step s6, the digital receipt system 100 may request (e.g., via a query) a transaction identifier associated with one or more digital receipt objects and / or other data received from the merchant system at step s3. For example, the request may include sending the checkout identifier and / or any other transaction data provided by the merchant system at step s2. At step s7, the transaction processing system 102 responds by transmitting the transaction identifier associated with the checkout identifier to the digital receipt system 100. The digital receipt system 100 may then store the transaction identifier in a digital receipt database in association with the checkout identifier and the corresponding digital receipt object. It should be appreciated that in addition to or in lieu of sending the transaction identifier at step s7, the transaction processing system 102 may provide any transaction data that enables identification of the transaction.
[0062] Still refer to Figure 3 At some point, a customer operating a client computing device 110 may wish to query a transaction, view additional information about a transaction, and / or dispute a transaction. At step s8, the client computing device 110 may transmit a request for more information about a transaction in response to, for example, the customer selecting the transaction from a transaction history on a mobile application or website (e.g., an issuer mobile application) presented on the client computing device 110. The client computing device 110 may also transmit a request for more information through a customer service system, such as by chatting with a customer service representative, etc. At step s9, the issuer system 108 requests a digital receipt object by transmitting a transaction identifier to the digital receipt system 100. At step s10, the digital receipt system 100 responds by transmitting digital receipt information, such as a digital receipt object, to the issuer system 108. At step s11, the issuer system 108 may transmit the digital receipt object or information derived from the digital receipt object to the client computing device 110.
[0063] although Figure 3 No dispute resolution system is shown (e.g. Figure 2 ), but it should be understood that such a system can be included in the message sequence. The dispute resolution system can be part of the transaction processing system. In other examples, the dispute resolution system can include the digital receipt system 100.
[0064] Figure 4 A sequence diagram for generating a digital receipt including a dispute resolution system 200 according to a non-limiting embodiment or aspect is shown. Steps s1 to s5 may be combined as described above. Figure 3 At step s5a, the transaction processing system 102 may transmit transaction data associated with the authorized and / or processed payment transaction to the dispute resolution system 200. At step s6, the digital receipt system 100 may request from the dispute resolution system 200 (e.g., via a query) a transaction identifier associated with one or more digital receipt objects and / or other data received from the merchant system at step s3. At step s7, the dispute resolution system 200 responds by transmitting a transaction identifier associated with the checkout identifier to the digital receipt system 100 based on the transaction data previously received at step s5a. The digital receipt system 100 may then store the transaction identifier in a digital receipt database in association with the checkout identifier and the corresponding digital receipt object. It should be appreciated that in addition to or in lieu of sending the transaction identifier at step s7, the dispute resolution system may provide any transaction data that enables identification of the transaction. Step s8 may be as described above in conjunction with Figure 3At step s9, issuer system 108 requests a digital receipt object and / or initiates a transaction dispute by transmitting a transaction identifier to dispute resolution system 200. At step s9a, dispute resolution system 200 queries digital receipt information 100 to obtain a digital receipt object. At step s10, digital receipt system 100 responds by transmitting the digital receipt information, such as a digital receipt object, to issuer system 108 to initiate a dispute.
[0065] Reference now Figure 5 , a diagram showing example components of an apparatus 900 according to a non-limiting embodiment. As an example, the apparatus 900 may correspond to Figure 1 The client computing device 110, transaction processing system 102, digital receipt system 100, acquirer system 104, merchant system 106, and / or issuer system 108 in some non-limiting embodiments or aspects, such systems or devices may include at least one device 900 and / or at least one component of device 900. The number and arrangement of components shown are provided as examples. In some non-limiting embodiments or aspects, Figure 1 Compared to those shown in , device 900 may include additional components, fewer components, different components, or components arranged in a different manner. Additionally or alternatively, a set of components (e.g., one or more components) of device 900 may perform one or more functions described as being performed by another set of components of device 900.
[0066] like Figure 5 As shown, the device 900 may include a bus 902, a processor 904, a memory 906, a storage component 908, an input component 910, an output component 912, and a communication interface 914. The bus 902 may include components that allow communication between components of the device 900. In some non-limiting embodiments or aspects, the processor 904 may be implemented in hardware, firmware, or a combination of hardware and software. For example, the processor 904 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 906 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 904.
[0067] Continue to refer Figure 5, the storage component 908 may store information and / or software related to the operation and use of the device 900. For example, the storage component 908 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 910 may include a component that allows the device 900 to receive information, for example, through 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 910 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 912 may include a component that provides output information from the device 900 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.). The communication interface 914 may include a transceiver-like component (e.g., a transceiver, a separate receiver and a transmitter, etc.) that enables the device 900 to communicate with other devices, for example, through a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 914 may allow the device 900 to receive information from another device and / or provide information to another device. For example, the communication interface 914 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, and / or the like.
[0068] The device 900 can perform one or more processes described herein. The device 900 can perform these processes based on the processor 904 executing software instructions stored by computer-readable media such as memory 906 and / or storage component 908. The computer-readable medium may include any non-transient memory device. The memory device includes a memory space located inside a single physical storage device or a memory space spread over multiple physical storage devices. The software instructions can be read from another computer-readable medium or from another device to the memory 906 and / or storage component 908 through the communication interface 914. When executed, the software instructions stored in the memory 906 and / or storage component 908 can cause the processor 904 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.
[0069] Although the embodiments have been described in detail for the purpose of illustration, it should be understood that such details are used for that purpose only, and 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 can be combined with one or more features of any other embodiment.
Claims
1. A computer-implemented method comprising: receiving, by a transaction processing system including at least one processor, from a merchant system via a first communication channel using an account identifier, a transaction request message for a transaction between a consumer and the merchant system, the transaction request message including first transaction data associated with the transaction, the first communication channel including a payment processing network, the first transaction data including a checkout identifier generated by the merchant system, the first transaction data not including personal information of the consumer, wherein the transaction processing system is independent of the merchant system and the issuer system; assigning, by the at least one processor, a transaction identifier to the transaction; storing, by the at least one processor, the first transaction data in association with the transaction identifier in at least one data storage device; receiving, by the at least one processor, digital receipt data from the merchant system via a second communication channel that is independent and different from the first communication channel, the digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data, the second transaction data comprising a checkout identifier generated by the merchant system; processing, by the at least one processor, the transaction using the account identifier; determining, by the at least one processor, the transaction identifier based on the second transaction data by matching the second transaction data with first transaction data in the at least one data store, wherein matching the second transaction data with the first transaction data in the at least one data store comprises matching a checkout identifier; storing the digital receipt object and the transaction identifier in association with each other by the at least one processor in the at least one data storage device or at least one other storage device; receiving, by the at least one processor, a query including the transaction identifier from at least one external system, wherein the at least one external system includes the issuer system; as well as The digital receipt object and the transaction identifier are automatically transmitted, by the at least one processor, to the issuer system in response to the query.
2. The computer-implemented method of claim 1, wherein the digital receipt object comprises an electronic image file.
3. The computer-implemented method of claim 1, wherein the digital receipt object comprises a structured data file.
4. The computer-implemented method of claim 1, wherein the first communication channel comprises an electronic payment processing system, and wherein the second communication channel comprises an Internet-based communication channel.
5. A system comprising: at least one data storage device, the at least one data storage device comprising transaction data stored in association with a transaction identifier; as well as A transaction processing system comprising at least one processor in communication with the data storage device, the at least one processor being programmed or configured to: receiving, from a merchant system via a first communication channel using an account identifier, a transaction request message for a transaction between a consumer and the merchant system, the transaction request message including first transaction data associated with the transaction, the first communication channel including a payment processing network, the first transaction data including a checkout identifier generated by the merchant system, the first transaction data not including personal information of the consumer, wherein the transaction processing system is independent of the merchant system and the issuer system; assigning a transaction identifier to the transaction; storing the first transaction data in association with the transaction identifier in at least one data storage device; receiving digital receipt data from the merchant system via a second communication channel that is independent and different from the first communication channel, the digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data, the second transaction data comprising a checkout identifier generated by the merchant system; processing the transaction using the account identifier; determining the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data store, wherein matching the second transaction data with the first transaction data in the at least one data store comprises matching a checkout identifier; storing the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receiving a query including the transaction identifier from at least one external system, wherein the at least one external system includes the issuer system; and In response to the query, the digital receipt object and the transaction identifier are automatically transmitted to the issuer system.
6. The system of claim 5, wherein the digital receipt object comprises an electronic image file.
7. The system of claim 5, wherein the digital receipt object comprises a structured data file.
8. The system of claim 5, wherein the first communication channel comprises an electronic payment processing system, and wherein the second communication channel comprises an Internet-based communication channel.
9. 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 of a transaction processing system, cause the at least one processor to: receiving, from a merchant system via a first communication channel using an account identifier, a transaction request message for a transaction between a consumer and the merchant system, the transaction request message including first transaction data associated with the transaction, the first communication channel including a payment processing network, the first transaction data including a checkout identifier generated by the merchant system, the first transaction data not including personal information of the consumer, wherein the transaction processing system is independent of the merchant system and the issuer system; assigning a transaction identifier to the transaction; storing the first transaction data in association with the transaction identifier in at least one data storage device; receiving digital receipt data from the merchant system via a second communication channel that is independent and different from the first communication channel, the digital receipt data comprising a digital receipt object and second transaction data associated with the transaction, the second transaction data comprising at least a subset of transaction parameters of the first transaction data, the second transaction data comprising a checkout identifier generated by the merchant system; processing the transaction using the account identifier; determining the transaction identifier based on the second transaction data by matching the second transaction data with the first transaction data in the at least one data store, wherein matching the second transaction data with the first transaction data in the at least one data store comprises matching a checkout identifier; storing the digital receipt object in association with the transaction identifier in the at least one data storage device or at least one other storage device; receiving a query including the transaction identifier from at least one external system, wherein the at least one external system includes the issuer system; and In response to the query, the digital receipt object and the transaction identifier are automatically transmitted to the issuer system.
10. The computer program product of claim 9, wherein the digital receipt object comprises an electronic image file.
11. The computer program product of claim 9, wherein the digital receipt object comprises a structured data file.
12. The computer program product of claim 9, wherein the first communication channel comprises an electronic payment processing system, and wherein the second communication channel comprises an Internet-based communication channel.
