WO2025144393A1

WO2025144393A1 - System, method, and computer program product for instant payment transactions in a credit card transaction network

Info

Publication number: WO2025144393A1
Application number: PCT/US2023/085961
Authority: WO
Inventors: Gustavo de CARVALHO; Leandro de Assunção Marques GARCIA; Lucas de Barros RODRIGUES; Felipe RENDEIRO
Original assignee: Visa International Service Association
Current assignee: Visa International Service Association
Priority date: 2023-12-27
Filing date: 2023-12-27
Publication date: 2025-07-03
Anticipated expiration: 2026-06-27

Abstract

Systems, methods, and computer program products are provided for instant payment transactions in a credit card transaction network. The system includes a processor of a transaction processing system configured in a credit card transaction network. The processor is configured to receive a transaction authorization request including a transaction amount, a merchant key, an instant payment network (IPN) identifier, and a payment device identifier. The processor is also configured to determine an issuer system based on the payment device identifier and cause the issuer system to initiate an IPN transaction. When causing the issuer system to initiate the IPN transaction, the processor is configured to transmit a portion of the transaction authorization request to the issuer system including the transaction amount, the merchant key, and the IPN identifier. The processor is further configured to receive a transaction authorization response from the issuer system and transmit a portion to the POS device.

Description

SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR INSTANT PAYMENT TRANSACTIONS IN A CREDIT CARD TRANSACTION NETWORK

BACKGROUND

1 . Technical Field

[0001] This disclosure relates generally to electronic transaction systems and, in non-limiting embodiments or aspects, to systems, methods, and computer program products for instant payment transactions in a credit card transaction network.

2. Technical Considerations

[0002] Instant payment networks (IPNs) provide for expedited electronic transfer between transaction accounts once a user provides all of the necessary information to effect the electronic transfer. IPN transactions may require fewer electronic messages and avoid the time delay of clearing and settlement that may be associated with a credit card transaction. However, IPN transactions may be resource inefficient to initiate. For example, a user may have to open a dedicated computer application, complete a separate authentication process, input their personal information, input recipient information, and review/confirm the input information prior to the IPN transaction being initiated. This process is prone to error — even worse, a user may lack the necessary information to effect the transfer (e.g., recipient information).

[0003] There is a need in the art to streamline (e.g., reduce computer resources and/or time delay) involved in initiating an IPN transaction such that the number of interactive steps at the point of a user interface are minimized.

SUMMARY

[0004] Accordingly, provided are improved systems, methods, and computer program products for instant payment transactions in a credit card transaction network. [0005] According to non-limiting embodiments or aspects, provided is a system for instant payment transactions in a credit card transaction network. The system includes at least one processor of a transaction processing system configured in a credit card transaction network. The at least one processor is configured to receive a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request including a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device. The at least one processor is also configured to determine an issuer system based on the payment device identifier. The at least one processor is further configured to cause the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN. When causing the issuer system to initiate the IPN transaction, the at least one processor is configured to transmit at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request including the transaction amount, the merchant key, and the IPN identifier. The at least one processor is further configured to receive a transaction authorization response from the issuer system, the transaction authorization response including an IPN transaction identifier associated with the IPN transaction initiated by the issuer system. The at least one processor is further configured to transmit at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response includes the IPN transaction identifier.

[0006] In some non-limiting embodiments or aspects, the merchant key may include a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

[0007] In some non-limiting embodiments or aspects, transmitting the at least a portion of the transaction authorization response to the POS device may cause the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

[0008] In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may further include a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

[0009] In some non-limiting embodiments or aspects, the transaction authorization request may further include (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

[0010] In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may include the second transaction amount, and transmitting the at least a portion of the transaction authorization request to the issuer system may further cause the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount.

[0011] In some non-limiting embodiments or aspects, the transaction authorization response may further include a credit card transaction identifier associated with the second transaction, and the at least a portion of the transaction authorization response may include the credit card transaction identifier.

[0012] According to non-limiting embodiments or aspects, provided is a method for instant payment transactions in a credit card transaction network. The method includes receiving, with at least one processor of a transaction processing system configured in a credit card transaction network, a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request including a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device. The method also includes determining, with at least one processor of the transaction processing system, an issuer system based on the payment device identifier. The method further includes causing, with at least one processor of the transaction processing system, the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN. Causing the issuer system to initiate the IPN transaction includes transmitting at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request including the transaction amount, the merchant key, and the IPN identifier. The method further includes receiving, with at least one processor of the transaction processing system, a transaction authorization response from the issuer system, the transaction authorization response including an IPN transaction identifier associated with the IPN transaction initiated by the issuer system. The method further includes transmitting, with at least one processor of the transaction processing system, at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response includes the IPN transaction identifier. [0013] In some non-limiting embodiments or aspects, the merchant key may include a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

[0014] In some non-limiting embodiments or aspects, transmitting the at least a portion of the transaction authorization response to the POS device may cause the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

[0015] In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may further include a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

[0016] In some non-limiting embodiments or aspects, the transaction authorization request may also include (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

[0017] In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may further include the second transaction amount, and transmitting the at least a portion of the transaction authorization request to the issuer system may further cause the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount.

[0018] In some non-limiting embodiments or aspects, the transaction authorization response may further include a credit card transaction identifier associated with the second transaction, and the at least a portion of the transaction authorization response may include the credit card transaction identifier.

[0019] According to non-limiting embodiments or aspects, provided is a computer program product for instant payment transactions in a credit card transaction network. The computer program product includes at least one non-transitory computer- readable medium including program instructions that, when executed by at least one processor of a transaction processing system configured in a credit card transaction network, cause the at least one processor to receive a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request including a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device. The program instructions also cause the at least one processor to determine an issuer system based on the payment device identifier. The program instructions also cause the at least one processor to cause the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN. The program instructions that cause the issuer system to initiate the IPN transaction cause the at least one processor to transmit at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request including the transaction amount, the merchant key, and the IPN identifier. The program instructions further cause the at least one processor to receive a transaction authorization response from the issuer system, the transaction authorization response including an IPN transaction identifier associated with the IPN transaction initiated by the issuer system. The program instructions further cause the at least one processor to transmit at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response includes the IPN transaction identifier.

[0020] In some non-limiting embodiments or aspects, the merchant key may include a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

[0021] In some non-limiting embodiments or aspects, transmitting the at least a portion of the transaction authorization response to the POS device may cause the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

[0022] In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may further include a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

[0023] In some non-limiting embodiments or aspects, the transaction authorization request may further include (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

[0024] In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may further include the second transaction amount, transmitting the at least a portion of the transaction authorization request to the issuer system may further cause the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount, the transaction authorization response may further include a credit card transaction identifier associated with the second transaction, and the at least a portion of the transaction authorization response may include the credit card transaction identifier.

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

[0026] Clause 1 : A system comprising: at least one processor of a transaction processing system configured in a credit card transaction network, the at least one processor configured to: receive a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request comprising a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device; determine an issuer system based on the payment device identifier; cause the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN, wherein, when causing the issuer system to initiate the IPN transaction, the at least one processor is configured to: transmit at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request comprising the transaction amount, the merchant key, and the IPN identifier; receive a transaction authorization response from the issuer system, the transaction authorization response comprising an IPN transaction identifier associated with the IPN transaction initiated by the issuer system; and transmit at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response comprises the IPN transaction identifier.

[0027] Clause 2: The system of clause 1 , wherein the merchant key comprises a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

[0028] Clause 3: The system of clause 1 or clause 2, wherein transmitting the at least a portion of the transaction authorization response to the POS device causes the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device. [0029] Clause 4: The system of any of clauses 1 -3, wherein the at least a portion of the transaction authorization request further comprises a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

[0030] Clause 5: The system of any of clauses 1 -4, wherein the transaction authorization request further comprises (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

[0031] Clause 6: The system of any of clauses 1 -5, wherein the at least a portion of the transaction authorization request further comprises the second transaction amount, and wherein transmitting the at least a portion of the transaction authorization request to the issuer system further causes the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount.

[0032] Clause 7: The system of any of clauses 1 -6, wherein the transaction authorization response further comprises a credit card transaction identifier associated with the second transaction, and wherein the at least a portion of the transaction authorization response comprises the credit card transaction identifier.

[0033] Clause 8: A method comprising: receiving, with at least one processor of a transaction processing system configured in a credit card transaction network, a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (PCS) device of the merchant, and the transaction authorization request comprising a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device; determining, with at least one processor of the transaction processing system, an issuer system based on the payment device identifier; causing, with at least one processor of the transaction processing system, the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN, wherein causing the issuer system to initiate the IPN transaction comprises: transmitting at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request comprising the transaction amount, the merchant key, and the IPN identifier; receiving, with at least one processor of the transaction processing system, a transaction authorization response from the issuer system, the transaction authorization response comprising an IPN transaction identifier associated with the IPN transaction initiated by the issuer system; and transmitting, with at least one processor of the transaction processing system, at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response comprises the IPN transaction identifier.

[0034] Clause 9: The method of clause 8, wherein the merchant key comprises a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

[0035] Clause 10: The method of clause 8 or clause 9, wherein transmitting the at least a portion of the transaction authorization response to the POS device causes the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

[0036] Clause 1 1 : The method of any of clauses 8-10, wherein the at least a portion of the transaction authorization request further comprises a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

[0037] Clause 12: The method of any of clauses 8-1 1 , wherein the transaction authorization request further comprises (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

[0038] Clause 13: The method of any of clauses 8-12, wherein the at least a portion of the transaction authorization request further comprises the second transaction amount, and wherein transmitting the at least a portion of the transaction authorization request to the issuer system further causes the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount.

[0039] Clause 14: The method of any of clauses 8-13, wherein the transaction authorization response further comprises a credit card transaction identifier associated with the second transaction, and wherein the at least a portion of the transaction authorization response comprises the credit card transaction identifier.

[0040] Clause 15: A computer program product, comprising at least one non- transitory computer-readable medium including program instructions that, when executed by at least one processor of a transaction processing system configured in a credit card transaction network, cause the at least one processor to: receive a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request comprising a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device; determine an issuer system based on the payment device identifier; cause the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN, wherein the program instructions that cause the issuer system to initiate the IPN transaction cause the at least one processor to: transmit at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request comprising the transaction amount, the merchant key, and the IPN identifier; receive a transaction authorization response from the issuer system, the transaction authorization response comprising an IPN transaction identifier associated with the IPN transaction initiated by the issuer system; and transmit at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response comprises the IPN transaction identifier.

[0041] Clause 16: The computer program product of clause 15, wherein the merchant key comprises a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

[0042] Clause 17: The computer program product of clause 15 or clause 16, wherein transmitting the at least a portion of the transaction authorization response to the POS device causes the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

[0043] Clause 18: The computer program product of any of clauses 15-17, wherein the at least a portion of the transaction authorization request further comprises a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

[0044] Clause 19: The computer program product of any of clauses 15-18, wherein the transaction authorization request further comprises (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

[0045] Clause 20: The computer program product of any of clauses 15-19, wherein the at least a portion of the transaction authorization request further comprises the second transaction amount, wherein transmitting the at least a portion of the transaction authorization request to the issuer system further causes the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount, wherein the transaction authorization response further comprises a credit card transaction identifier associated with the second transaction, and wherein the at least a portion of the transaction authorization response comprises the credit card transaction identifier.

[0046] These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the 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 the purpose 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

[0047] Additional advantages and details are explained in greater detail below with reference to the non-limiting, exemplary embodiments that are illustrated in the accompanying schematic figures, in which:

[0048] FIG. 1 is a schematic diagram of a system for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects;

[0049] FIG. 2 is a schematic diagram of example components of one or more devices of FIG. 1 , according to some non-limiting embodiments or aspects;

[0050] FIG. 3 is a flow diagram of a method for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects; [0051] FIG. 4 is a flow diagram of a method for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects;

[0052] FIG. 5 is a flow diagram of a method for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects;

[0053] FIG. 6 is a flow diagram of a method for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects;

[0054] FIG. 7 is a flow diagram of a method for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects; and

[0055] FIG. 8 is a flow diagram of a method for instant payment transactions in a credit card transaction network, according to some non-limiting embodiments or aspects.

DETAILED DESCRIPTION

[0056] For purposes of the description hereinafter, the terms “end,” “upper,” “lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and derivatives thereof shall relate to the embodiments as they are oriented in the drawing figures. However, it is to be understood that the embodiments may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments or aspects of the disclosed subject matter. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein are not to be considered as limiting.

[0057] It is to be understood that the present disclosure may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary and non-limiting embodiments or aspects. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein are not to be considered as limiting. [0058] Some non-limiting embodiments or aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, more than the threshold, higher than the threshold, greater than or equal to the threshold, less than the threshold, fewer than the threshold, lower than the threshold, less than or equal to the threshold, equal to the threshold, etc.

[0059] No aspect, component, element, structure, act, step, function, instruction, and/or the like used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more” and “at least one.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like) and may be used interchangeably with “one or more” or “at least one.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based at least partially on” unless explicitly stated otherwise. In addition, reference to an action being “based on” a condition may refer to the action being “in response to” the condition. For example, the phrases “based on” and “in response to” may, in some non-limiting embodiments or aspects, refer to a condition for automatically triggering an action (e.g., a specific operation of an electronic device, such as a computing device, a processor, and/or the like).

[0060] As used herein, the term “communication” may refer to the reception, receipt, transmission, transfer, provision, and/or the like of data (e.g., information, signals, messages, instructions, commands, and/or the like). For one unit (e.g., a device, a system, a component of a device or system, combinations thereof, and/or the like) to be in communication with another unit means that the one unit is able to directly or indirectly receive information from 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, and/or the like) that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the information transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may be in communication with a second unit if at least one intermediary unit processes information received from the first unit and communicates the processed information to the second unit. In some non-limiting embodiments or aspects, a message may refer to a network packet (e.g., a data packet and/or the like) that includes data. It will be appreciated that numerous other arrangements are possible.

[0061] As used herein, the term “computing device” may refer to one or more electronic devices configured to process data. A computing device may, in some examples, 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/or 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 standard cellular phone), a portable computer, a wearable device (e.g., watches, glasses, lenses, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices. A computing device may also be a desktop computer or other form of non-mobile computer.

[0062] As used herein, the term “server” may refer to or include one or more computing devices that are operated by or facilitate communication and processing for multiple parties in a network environment, such as the Internet, although it will be appreciated that communication may be facilitated over one or more public or private network environments and that various other arrangements are possible. Further, multiple computing devices (e.g., servers, point-of-sale (POS) devices, mobile devices, etc.) directly or indirectly communicating in the network environment may constitute a “system.” Reference to “a server” or “a processor,” as used herein, may refer to a previously-recited server and/or processor that is recited as performing a previous step or function, a different server and/or processor, and/or a combination of servers and/or processors. For example, as used in the specification and the claims, a first server and/or a first processor that is recited as performing a first step or function may refer to the same or different server and/or a processor recited as performing a second step or function.

[0063] As used herein, the term “system” may refer to one or more computing devices or combinations of computing devices (e.g., processors, servers, client devices, software applications, components of such, and/or the like). Reference to “a device,” “a server,” “a processor,” and/or the like, as used herein, may refer to a previously-recited device, server, or processor that is recited as performing a previous step or function, a different server or processor, and/or a combination of servers and/or processors. For example, as used in the specification and the claims, a first server or a first processor that is recited as performing a first step or a first function may refer to the same or different server or the same or different processor recited as performing a second step or a second function.

[0064] 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 that is used as a substitute or replacement identifier for an original account identifier, such as a PAN. Account identifiers may be alphanumeric or any combination of characters and/or symbols. Tokens may be associated with a PAN or other original account identifier in one or more data structures (e.g., one or more databases, and/or the like) such that they may be used to conduct a transaction without directly using the original account identifier. In some examples, an original account identifier, such as a PAN, may be associated with a plurality of tokens for different individuals or purposes.

[0065] 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 an account identifier, such as a PAN, to a customer that uniquely identifies one or more accounts associated with that customer. The account identifier may be embodied 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 executing one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing a transaction.

[0066] As used herein, the term “merchant” may refer to an individual or entity that provides goods and/or services, or access to goods and/or services, to customers 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 executing one or more software applications. [0067] As used herein, a “point-of-sale (POS) device” may refer to one or more devices, which may be used by a merchant to conduct a transaction (e.g., a payment transaction) and/or process a transaction. Additionally or alternatively, a POS device may include peripheral devices, card readers, scanning devices (e.g., code scanners), Bluetooth® communication receivers, near-field communication (NFC) receivers, radio frequency identification (RFID) receivers, and/or other contactless transceivers or receivers, contact-based receivers, payment terminals, and/or the like. As used herein, a “point-of-sale (POS) system” may refer to one or more client devices and/or peripheral devices used by a merchant to conduct a transaction. For example, a POS system may include one or more POS devices and/or other like devices that may be used to conduct a payment transaction. In some non-limiting embodiments or aspects, a POS system (e.g., a merchant POS system) may include one or more server computers programmed or configured to process online payment transactions through webpages, mobile applications, and/or the like.

[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 smartcard, smart media, a payroll card, a healthcare card, a wristband, a machine-readable medium containing account information, a keychain device or fob, an RFID transponder, a retailer discount or loyalty 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, and/or the like. In some non-limiting embodiments or aspects, the payment device may include volatile or non-volatile memory to store information (e.g., an account identifier, a name of the account holder, and/or the like).

[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 (e.g., a merchant service provider, a payment service provider, a payment facilitator, a payment facilitator that contracts with an acquirer, a payment aggregator, and/or the like), which provides payment services (e.g., transaction service provider payment services, payment processing services, and/or the like) to one or more merchants. The payment services may be associated with the use of payment devices 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, groups of servers, and/or the like, operated by or on behalf of a payment gateway. [0070] As used herein, the term “transaction service provider” may refer to an entity that receives transaction authorization requests from merchants or other entities and provides guarantees of payment, in some cases through an agreement between the transaction service provider and an issuer institution. For example, a transaction service provider may include a payment network such as Visa® 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 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.

[0071] Disclosed are systems, methods, and computer program products that provide a technical solution for instant payment transactions in a credit card transaction network. Users and merchants may desire for payments in electronic payment processing networks to be made instantaneously, or near-instantaneously, with the time of user interaction with a POS device. This provides real-time (or substantially real-time) feedback during transaction that the user’s funds are available, and that the funds are transferred. However, credit card transaction networks may lack the processing speed of an IPN. Still more, IPNs may lack the ease of use of a credit card transaction network, where a user may, at minimum, present a payment device for use in the transaction. The disclosed solution provides for, using a transaction processing system configured in a credit card transaction network, receiving a transaction authorization request from an acquirer system, for a transaction initiated at a POS device of a merchant. This simplifies the amount of data for a user to store/possess when instantiating an IPN transaction, because of the unique use of the payment device that is primarily used in the credit card transaction network.

[0072] Furthermore, the disclosed solution provides for determining, at the transaction processing system, an issuer system based on the payment device identifier. Since the issuer system ultimately initiates the IPN transaction for the transfer of funds to a merchant account from the user account, the disclosed solution improves the IPN transaction process by dynamically identifying the issuer system (e.g., instead of requiring explicit user input). Moreover, the transaction processing system that is configured in the credit card transaction network can cause the issuer system to initiate the IPN transaction using messages that are primarily used for credit card transactions e.g., transaction authorization requests transmitted on the rails of a credit card transaction network). This consolidates the number of communicative channels needed for credit card transactions I IPN transactions, which reduces computer resources (e.g., memory, processing capacity, bandwidth, etc.) required for operating the overall system. Furthermore, the transaction authorization request transmitted by transaction processing system to issuer system, which triggers the issuer system to carry out the IPN transaction, may be minimally modified with additional data fields including transaction amounts, a merchant key (to identify the recipient in the IPN), and the IPN identifier (to identify the IPN), further piggybacking on the credit card transaction network. This creates efficiencies through consolidation. [0073] Even more, because the transaction authorization request passes through a merchant-side data flow (e.g., the POS device I merchant system I acquirer system), the merchant-side device can configure the transaction authorization request to include the necessary recipient information for receiving the IPN transaction. This solves a significant technical problem with IPN transactions, which is data asymmetry (e.g., in which users are not the entities that store data of recipient transaction keys and would need to be transmitted that data in additional messages if the users must possess that data at time of instantiation). The resulting IPN transaction that is initiated by the issuer system, and caused by the transaction processing system transmitting the transaction authorization request to the issuer system, is further integrated into the feedback loop of the credit card transaction network. For example, the IPN interface used by the issuer system may generate an IPN transaction identifier, which may be embedded in a transaction authorization response that is transmitted back through the credit card transaction network. This reduces the number of channels and messages required to provide full interoperability and transparency in IPN transactions. In this manner, the user is provided instantaneous positive feedback at the point of the POS device, since a confirming notification may be displayed on the POS device, containing the IPN transaction identifier that was routed to the POS device in the transaction authorization response.

[0074] Additionally or alternatively, because the credit card transaction network acts as a framework for IPN transactions, according to non-limiting embodiments or aspects, split tender transactions are enabled by the disclosed solution. In other words, transactions of differing electronic protocols (e.g., credit card transactions, IPN transaction, etc.) and clearing/settling time periods (e.g., batch, instantaneous, etc.) may be combined into a single transaction authorization request flow. For example, a first transaction amount may be transferred via the IPN transaction protocol, as instantiated by a single transaction authorization request; likewise, a second transaction amount may be transferred via the credit card transaction protocol, as instantiated by the same transaction authorization request. This message reduction reduces computer resources required for completing otherwise separate transactions. The foregoing and other technical improvements are made apparent with reference to the following figures and description.

[0075] FIG. 1 is a schematic diagram of an environment 100 for instant payment transactions in a credit card transaction network, according to non-limiting embodiments or aspects of the present-disclosure. Environment 100 may include payment device 101 of a user, point-of-sale (POS) device 102, merchant system 103, acquirer system 104, transaction processing system 105, issuer system 106, and/or instant payment network (IPN) interface 107 communicating at least partly over at least one communication network 108. In some non-limiting embodiments or aspects, environment 100 may further include a payment gateway, such as payment gateway 601 (see, e.g., FIG. 6). At least a portion of environment 100 may include a credit card transaction network, which may include POS device 102, merchant system 103, acquirer system 104, transaction processing system 105, and/or issuer system 106.

[0076] Payment device 101 may include one or more computing devices configured to communicate with POS device 102, merchant system 103, transaction processing system 105, and/or issuer system 106, at least partly over at least one communication network 108. Payment device 101 may be used in a card-present (CP) type transaction interaction, e.g., including a credit card being swiped, dipped, scanned, and/or the like, at POS device 102 in a merchant store. Payment device 101 may be used in a card-not-present (CNP) type transaction interaction, e.g., by user inputting identifying information of payment device 102 (e.g., a payment device identifier, which may include a card number, a card verification value (CVV) code, an expiration date, and/or the like) into a merchant interface acting as POS device 102 of merchant system 103. In some non-limiting embodiments or aspects, payment device 101 may include a credit card with an embedded chip (e.g., integrated circuit) configured to store an IPN identifier, a payment device identifier, and/or the like associated with payment device 101. [0077] POS device 102 may include one or more computing devices configured to communicate with payment device 101 , merchant system 103, acquirer system 104, and/or transaction processing system 105 at least partly over at least one communication network 108. POS device 102 may be used in a CP type transaction interaction, e.g., including a card reader for receiving information from payment device

101 when payment device 101 is swiped, dipped, tapped, and/or the like. POS device

102 may be used in a CNP type transaction interaction, e.g., including a merchant interface accessible via a web browser and/or application at least partly over the internet. In credit card transaction networks that include a payment gateway, payment device 102 may be configured to communicate with the payment gateway at least partly over at least one communication network 108.

[0078] Merchant system 103 may include one or more computing devices configured to communicate with payment device 101 , POS device 102, acquirer system 104, transaction processing system 105, issuer system 106, and/or at least one IPN interface 107 at least partly over at least one communication network 108. Merchant system 103 may be configured to communicate with POS device 102 to receive identifying information used to initiate an authorization transaction request for a transaction between the merchant and the user. For example, merchant system 103 may receive a payment device identifier of payment device 101 , an IPN identifier associated with payment device 101 , a transaction amount, a transaction description, a transaction identifier, and/or the like. Additionally or alternatively, merchant system

103 may generate a transaction authorization request in response to a user initiating a transaction with the merchant via POS device 102. In some non-limiting embodiments or aspects, merchant system 103 may include POS device 102. In credit card transaction networks that include a payment gateway, merchant system 103 may be configured to communicate with the payment gateway at least partly over at least one communication network 108.

[0079] Acquirer system 104 may include one or more computing devices configured to communicate with POS device 102, merchant system 103, transaction processing system 105, issuer system 106, and/or IPN interface 107 at least partly over at least one communication network 108. Acquirer system 104 may be associated with a financial institution that provides a transaction account for the merchant of merchant system 103. Acquirer system 104 may receive transaction authorization requests generated by merchant system 103 and transmit transaction authorization requests, with or without modification, to transaction processing system 105. In credit card transaction networks that include a payment gateway, the payment gateway may act as, or on behalf of, acquirer system 104.

[0080] Transaction processing system 105 may include one or more computing devices configured to communicate with payment device 101 , POS device 102, merchant system 103, acquirer system 104, issuer system 106, and/or IPN interface 107 at least partly over at least one communication network 108. Transaction processing system 105 may be configured to receive transaction authorization requests from one or more of each of merchant system 103, acquirer system 104, and/or a payment gateway, and transmit transaction authorization requests, with or without modification, to issuer system 106 for authentication and/or approval. Transaction processing system 105 may be configured between acquirer system 104 and issuer system 106 to facilitate clearing and settlement of credit card transactions in a credit card transaction network. Transaction processing system 105 may be further configured to determine which transactions, based on the transaction authorization requests, are to be processed as IPN transactions.

[0081] Issuer system 106 may include one or more computing devices configured to communicate with payment device 101 , merchant system 103, acquirer system 104, transaction processing system 105, and/or IPN interface 107 at least partly over at least one communication network 108. Issuer system 106 may be configured to receive transaction authorization requests from transaction processing system 105 and authenticate and/or approve transactions. Issuer system 106 may be further configured, when transmitted transaction authorization requests for IPN transactions, to communicate with acquirer system 104 via IPN interface 107 to debit a transaction account associated with payment device 101 and credit a transaction account associated with merchant system 103. Issuer system 106 may be further configured to transmit a transaction authorization response after processing a transaction authorization request, which may include an IPN transaction identifier, a credit card transaction identifier, an approval flag, and/or the like. Issuer system 106 may include or be associated with IPN interface 107, for initiating and completing IPN transactions. IPN interface 107 may include at least one interface configured to permit issuer system 106 to submit transaction requests in an IPN, such as at least one application programming interface (API) for at least one IPN (e.g., an API for Pix, in Brazil). [0082] Communication network 108 may include one or more wired and/or wireless networks over which the systems and devices of environment 100 may communicate. For example, communication network 108 may include a cellular network (e.g., a longterm evolution (LTE®) network, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, and/or the like, and/or a combination of these or other types of networks.

[0083] The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. There may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as multiple, distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.

[0084] In some non-limiting embodiments or aspects, a user of payment device 101 may desire to complete a transaction with a merchant (e.g., a transaction in an electronic payment processing network, which may be in exchange for goods, services, and/or the like). Payment device 101 may be configured to act as a credit card in a credit card transaction network. Additionally, the user can use payment device 101 to initiate a transaction as an IPN transaction instead. At the time of transacting, the user may present payment device 101 and/or input information identifying payment device 101 to POS device 102. For example, user may scan payment device 101 at POS device 102 and select an option for IPN transaction in a user-facing interface of POS device 102 (e.g., a button pad of a card reader). By way of another example, the user may input a payment device identifier of payment device 101 into an internet-accessible user-facing interface of merchant system 103 and/or POS device 102 (e.g., a merchant website, a merchant application, etc.), and further input a selection of transacting in an IPN. POS device 102 and/or merchant system 103 may communicate a transaction authorization request based on payment device 101 , via acquirer system 104 and/or a payment gateway, to transaction processing system 105.

[0085] In some non-limiting embodiments or aspects, the transaction authorization request may include transaction data including, but not limited to, one or more transaction amounts (e.g., a primary transaction amount to be processed as an IPN transaction, a secondary transaction amount to be processed in a credit card transaction network, etc.), a payment device identifier of payment device 101 , a merchant key of the merchant (e.g., for receiving payment in an IPN), a credit card transaction identifier field (e.g., indicating a binary value of true, indicating a particular credit card transaction network identity, etc.), an IPN transaction identifier field (e.g., indicating a binary value of true, indicating a particular IPN transaction network identity, etc.), a transaction description, a merchant category code, a transaction time, a processing code, an identifier of a split tender transaction type, and/or the like. In some non-limiting embodiments or aspects, the merchant key may include a combination of an identifier of the merchant transaction account and an identifier associated with the merchant. In some non-limiting embodiments or aspects, the processing code may be configured to cause issuer system 106 to validate the transaction authorization request and initiate the IPN transaction for the transaction amount. Additionally or alternatively, the processing code may include, or be included in, the IP transaction identifier field, the credit card transaction identifier field, and/or the identifier of the split tender transaction type. In some non-limiting embodiments or aspects, the processing code may comprise an identification of the cardholder transaction type (e.g., “00” for point-of-sale transactions, “01 ” for withdrawal transactions, etc.), an identification of the cardholder account type (e.g., a savings account, a checking account, a credit card account, etc.) for that transaction. For use in instant payment transactions, the processing code may include a new code value in an existing code field, may include a new code value in a new code field, and/or the like. The processing code may also be used to help process, identify, and pull reports for instant payment transactions.

[0086] In some non-limiting embodiments or aspects, an IPN transaction identifier field of the transaction authorization request may indicate that the transaction should be processed as an IPN transaction (e.g., having a binary value of true, having an identifier of a particular IPN, etc.). In some non-limiting embodiments or aspects, the transaction may be processed as split between a credit card transaction and an IPN transaction. In such a scenario, both an IPN transaction identifier field and the credit card transaction identifier field may each further include a partial amount of the transaction amount to be processed under the respective protocol. Furthermore, the transaction authorization request may include an identifier of a split tender transaction type for IPN transactions and credit card transactions (e.g., a code indicating “IPN” and “credit card”).

[0087] In some non-limiting embodiments or aspects, transaction processing system 105 may receive the transaction authorization request associated with the transaction between payment device 101 and the merchant. The transaction authorization request received by the transaction processing system 105 may include at least the transaction amount, the merchant key of the merchant, the IPN identifier of the IPN, and the payment device identifier of payment device 101 . In response to receiving the transaction authorization request, transaction processing system 105 may determine an issuer system 106 associated with payment device 101 based on the payment device identifier of the transaction authorization request. For example, at least a portion of the payment device identifier may directly or indirectly (e.g., through a lookup table) identify issuer system 106 of an issuer that issued payment device 101 . The determined issuer system 106 may then be prompted by transaction processing system 105 to process the transaction as an IPN transaction, instead of or in addition to processing the transaction as a credit card transaction.

[0088] In some non-limiting embodiments or aspects, transaction processing system 105 may cause issuer system 106 to initiate an IPN transaction from a transaction account associated with payment device 101 to a transaction account associated with the merchant using the IPN. In order to cause issuer system 106 to initiate the IPN transaction, transaction processing system 105 may transmit at least a portion of the transaction authorization request, modified or unmodified, to issuer system 106. The at least a portion of the transaction authorization request may include the transaction amount, the merchant key, and the IPN identifier. For split tender transactions to be processed as both IPN transactions and credit card transactions, the at least a portion of the transaction authorization request may indicate a portion of the transaction amount to be processed as an IPN transaction and a portion of the transaction amount to be processed as a credit card transaction.

[0089] In some non-limiting embodiments or aspects, issuer system 106 may receive the at least a portion of the transaction authorization request and process the transaction at least partly as an IPN transaction using IPN interface 107. Some or all of the transaction amount for the transaction may be debited from a transaction account of payment device 101 and transmitted to a transaction account of the merchant in the IPN by issuer system 106 via IPN interface 107. In some non-limiting embodiments or aspects, for split tender transactions, a remaining portion of transaction amount may be processed as a credit card transaction in the credit card transaction network, to be cleared and settled in a time period following the IPN transaction. After processing the transaction at least partly in the IPN, issuer system 106 may transmit a transaction authorization response back to transaction processing system 105 based on the transaction authorization request. The transaction authorization response may include, at least partly, an IPN transaction identifier associated with the IPN transaction initiated by issuer system 106. Additionally or alternatively, the transaction authorization response may include, at least partly, a credit card transaction identifier associated with a second transaction processed in the credit card transaction network for the second amount of the transaction amount.

[0090] In some non-limiting embodiments or aspects, transaction processing system 105 may receive the transaction authorization response from issuer system 106. Transaction processing system 105 may transmit at least a portion of the transaction authorization response to POS device 101 directly or indirectly, such as via acquirer system 104, merchant system 103, and/or a payment gateway. Transmitting the at least a portion of the transaction authorization response to POS device 102 to provide the at least a portion of the transaction authorization response on a display of POS device 102. For example, POS device 102 may display at least a portion of the transaction authorization response, including, but not limited to, an IPN transaction identifier, a credit card transaction identifier, and/or the like.

[0091] Referring now to FIG. 2, shown is a diagram of example components of a device 200 according to non-limiting embodiments. Device 200 may correspond to payment device 101 , POS device 102, merchant system 103, acquirer system 104, transaction processing system 105, issuer system 106, and/or IPN interface 107 as an example. In some non-limiting embodiments, such systems or devices may include at least one device 200 and/or at least one component of device 200. The number and arrangement of components shown are provided as an example. In some nonlimiting embodiments, device 200 may include additional components, fewer components, different components, or differently arranged components than those shown. Additionally, or alternatively, a set of components e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

[0092] As shown in FIG. 2, device 200 may include a bus 202, a processor 204, memory 206, a storage component 208, an input component 210, an output component 212, and a communication interface 214. Bus 202 may include a component that permits communication among the components of device 200. In some non-limiting embodiments, processor 204 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 204 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 (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.) that can be programmed to perform a function. Memory 206 may include random access memory (RAM), 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 processor 204.

[0093] With continued reference to FIG. 2, storage component 208 may store information and/or software related to the operation and use of device 200. For example, storage component 208 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid-state disk, etc.) and/or another type of computer-readable medium. Input component 210 may include a component that permits device 200 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.). Additionally, or alternatively, input component 210 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 212 may include a component that provides output information from device 200 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.). Communication interface 214 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 214 may permit device 200 to receive information from another device and/or provide information to another device. For example, communication interface 214 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, a Wi-Fi® interface, a cellular network interface, and/or the like.

[0094] Device 200 may perform one or more processes described herein. Device 200 may perform these processes based on processor 204 executing software instructions stored by a computer-readable medium, such as memory 206 and/or storage component 208. A computer-readable medium may include any non- transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices. Software instructions may be read into memory 206 and/or storage component 208 from another computer-readable medium or from another device via communication interface 214. When executed, software instructions stored in memory 206 and/or storage component 208 may cause processor 204 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, embodiments described herein are not limited to any specific combination of hardware circuitry and software. The term “programmed or configured,” as used herein, refers to an arrangement of software, hardware circuitry, or any combination thereof on one or more devices.

[0095] Referring now to FIG. 3, shown is a flow diagram for a method for instant payment transactions in a credit card transaction network, according to some nonlimiting embodiments or aspects. The steps shown in FIG. 3 are for example purposes only. It will be appreciated that additional, fewer, different, and/or a different order of steps may be used in some non-limiting embodiments or aspects. In some nonlimiting embodiments or aspects, a step may be automatically performed in response to performance and/or completion of a prior step. One or more steps of process 300, illustrated in connection with FIG. 3, may be performed by one or more computing devices of transaction processing system 105. Additionally or alternatively, one or more other computing devices or systems may perform one or more steps in concert with, or instead of, transaction processing system 105.

[0096] As shown in FIG. 3, process 300 may include, at step 302, receiving a transaction authorization request. For example, transaction processing system 105 may receive a transaction authorization request from acquirer system 104. The transaction authorization request may be associated with a transaction between payment device 101 and a merchant (e.g., associated with merchant system 103). The transaction authorization request may include a transaction amount, a merchant key of the merchant, an IPN identifier of an IPN, and a payment device identifier of payment device 101 . The merchant key may include a combination of an identifier of a merchant transaction account and an identifier associated with the merchant. In some non-limiting embodiments or aspects, the transaction authorization request may include an identifier of a split tender transaction type, and a second transaction amount to be processed in a credit card transaction network.

[0097] As shown in FIG. 3, process 300 may include, at step 304, determining an issuer system 106 from the payment device identifier. For example, transaction processing system 105 may determine issuer system 106 based on the payment device identifier of payment device 101 .

[0098] As shown in FIG. 3, process 300 may include, at step 306, causing issuer system 106 to initiate an IPN transaction. For example, transaction processing system

105 may cause issuer system 106 to initiate an IPN transaction from a transaction account associated with payment device 101 to a transaction account associated with the merchant using the IPN. When causing issuer system 106 to initiate the IPN transaction, transaction processing system 105 may execute step 308.

[0099] As shown in FIG. 3, process 300 may include, at step 308, transmitting at least a portion of the transaction authorization request to issuer system 106. For example, transaction processing system 105 may transmit at least a portion of the transaction authorization request to issuer system 106. The at least a portion of the transaction authorization request may include the transaction amount, the merchant key, and the IPN identifier. Transaction processing system 105 may execute step 306 by, at least partly, executing step 308. In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization request may include a processing code configured to cause issuer system 106 to validate the transaction authorization request and initiate the IPN transaction for the transaction amount. In some nonlimiting embodiments or aspects, the at least a portion of the transaction authorization request may include a second transaction amount. Transmitting the at least a portion of the transaction authorization request to issuer system 106 may cause issuer system

106 to also initiate a second transaction in the credit card transaction network for the second transaction amount. [0100] As shown in FIG. 3, process 300 may include, at step 310, receiving a transaction authorization response from issuer system 106. For example, transaction processing system 105 may receive a transaction authorization response from issuer system 106 including an IPN transaction identifier associated with the IPN transaction initiated by issuer system 106. In some non-limiting embodiments or aspects, the transaction authorization response may further include a credit card transaction identifier associated with the second transaction.

[0101] As shown in FIG. 3, process 300 may include, at step 312, transmitting at least a portion of the transaction authorization response to POS device 102. For example, transaction processing system 105 may transmit at least a portion of the transaction authorization response to POS device 102 via acquirer system 104. The at least a portion of the transaction authorization response may include the IPN transaction identifier. Transmitting the at least a portion of the transaction authorization response to POS device 102 may cause POS device 102 to provide at least a portion of the transaction authorization response on a display of POS device 102. In some non-limiting embodiments or aspects, the at least a portion of the transaction authorization response may include the credit card transaction identifier.

[0102] Referring now to FIG. 4, shown is a flow diagram for a method for instant payment transactions in a credit card transaction network, according to some nonlimiting embodiments or aspects. The steps shown in FIG. 4 are for example purposes only. It will be appreciated that additional, fewer, different, and/or a different order of steps may be used in some non-limiting embodiments or aspects. In some nonlimiting embodiments or aspects, a step may be automatically performed in response to performance and/or completion of a prior step. As shown, process 400 includes steps for completing an IPN transaction within (e.g., using the network framework of) a credit card transaction network. The steps of process 400 may be performed by one or more of payment device 101 , POS device 102, merchant system 103, acquirer system 104, transaction processing system 105, issuer system 106, and IPN interface 107, as described below.

[0103] As shown in FIG. 4, process 400 may include, at step 402, providing a payment device 101 for payment in a transaction. For example, a user may provide their payment device 101 , or identifying information of their payment device 101 , for use in a transaction with a merchant. For a CP transaction, the user may swipe, insert, tap, present, and/or the like, their payment device 101 to a POS device 102. For a CNP transaction, the user may input, via an interface of a computing device e.g., a desktop computer, a mobile device, etc.), identifying information of payment device 101 , such as an identifier of payment device 101 , along with other billing information. As a part of step 402 or step 404, the user may select an option in an interface of POS device 102 to designate at least part of an amount for the transaction to be paid by IPN transaction. For example, the user may be shown payments options of “Credit”, “Debit”, and “Pix” (an example IPN) on a display of POS device 102, with corresponding buttons for selecting the payment options. The user may select the “Pix” option (e.g., or any other IPN identifier) to initiate part or all of the transaction amount as an IPN transaction. If the user wishes to split tender, the user may select additional options in the POS device 102, such as to input an amount for each type of transaction and/or confirm the amounts being designated for each type of transaction. [0104] As shown in FIG. 4, process 400 may include, at step 404, transmitting a transaction authorization request to acquirer system 104. For example, the user input may cause POS device 102 to generate and transmit a transaction authorization request to acquirer system 104, directly or indirectly through merchant system 103. The transaction authorization request may include one or more fields identifying that at least a part of the transaction is to be executed in an IPN. The transaction authorization request sent from POS device 102 to acquirer system 104 may further include a transaction amount, additional transaction amounts (e.g., such as a second transaction amount, which may be included in the transaction amount), a payment device identifier of payment device 101 , an IPN identifier of an IPN, a merchant key of the merchant, and/or the like. The merchant key may be included in the transaction authorization request when generated by POS device 102, when communicated through merchant system 103, or after received by acquirer system 104.

[0105] As shown in FIG. 4, process 400 may include, at step 406, transmitting the transaction authorization request to transaction processing system 105. For example, acquirer system 104 may transmit the transaction authorization request, modified or unmodified, to transaction processing system 105 for further processing. In some nonlimiting embodiments or aspects, before acquirer system 104 forwards the transaction authorization request to transaction processing system 105, acquirer system 104 may augment (e.g., modify, update, etc.) the transaction authorization request to include a new processing code, which may be configured to cause issuer system 106 to validate the transaction authorization request (e.g., as a valid IPN transaction request) and initiate an IPN transaction for some or all of the transaction amount. In some nonlimiting embodiments or aspects, before acquirer system 104 forwards the transaction authorization request to transaction processing system 105, acquirer system 104 may augment the transaction authorization request to include the merchant key, an IPN identifier, and/or one or more fields to indicate that one or more credit card transaction protocols may be skipped. The merchant key may include a combination of an identifier of a merchant transaction account (e.g., an alphanumeric code, a numeric sequence, a unique alphabetical name, etc.) and an identifier associated with the merchant (e.g., an alphanumeric code, a numeric sequence, a unique alphabetical name, etc.). For example, a merchant key may be a combination of a 12-digit bank account number and a 9-digit merchant tax identification number, forming a 21 -digit combined merchant key. By way of further example, each merchant key used in the system may uniquely identify a single merchant transaction account associated with a single merchant.

[0106] As shown in FIG. 4, process 400 may include, at step 408, transmitting the transaction authorization request to issuer system 106. For example, transaction processing system 105 may transmit the transaction authorization request, modified or unmodified, to issuer system 106. In some non-limiting embodiments or aspects, before transaction processing system 105 forwards the transaction authorization request to issuer system 106, transaction processing system 105 may augment the transaction authorization request to include the new processing code, an IPN identifier, an issuer identifier, and/or the like. As part of step 408, transaction processing system 105 may act as a message router by determining the issuer associated with payment device 101 based on a payment device identifier in the transaction authorization request transmitted from POS device 102 and/or acquirer system 104. For example, transaction processing system 105 may use a lookup table (e.g., based on the first several digits of a PAN) to determine an issuer institution associated with payment device 101 . After determining the appropriate issuer system 106 associated with an issuer of payment device 101 , transaction processing system 105 may route the transaction authorization request to issuer system 105.

[0107] As shown in FIG. 4, process 400 may include, at step 410, initiating an IPN transaction. For example, receipt of the transaction authorization request from transaction processing system 105 may cause (e.g., trigger) issuer system 106 to initiate an IPN transaction from a transaction account associated with payment device 101 to a transaction account associated with the merchant using the IPN. In particular, issuer system 106 may use IPN interface 107 to submit an IPN transaction corresponding to some or all of the transaction amount from user to the merchant. Issuer system 106 may determine a recipient merchant of the IPN transaction based on the merchant key of the transaction authorization request. The merchant key may be directly used, in the IPN interface 107, as a designation of a recipient transaction account in the IPN. Issuer system 106 may determine a transaction amount of the IPN transaction based on at least one transaction amount in the transaction authorization request (e.g., a total transaction amount, a first transaction amount, a total transaction amount minus a second transaction amount, etc.). Issuer system 106 may determine a payer transaction account based on the payment device identifier in the transaction authorization request. In some non-limiting embodiments or aspects, for split tender transactions, a second transaction amount in the transaction authorization request may be associated with a second portion of the transaction to be paid by a default protocol for clearing and settling in the credit card transaction network. In this manner, issuer system 106 may authorize and authenticate the transaction authorization request for an IPN transaction and/or a credit card transaction, which may be different amounts, from a single transaction authorization request.

[0108] As shown in FIG. 4, process 400 may include, at step 412, causing an electronic transfer of funds in response to the initiated IPN transaction by issuer system 106. For example, IPN interface 107 may be used by issuer system 106 to cause a debit in the transaction account of the user and a credit in the transaction account of the merchant, using the instant payment protocol of the IPN. As such, an instantaneous, or near-instantaneous, cleared and settled payment may be made from the transaction account of the user to the transaction account of the merchant. Issuer system 106 may receive confirmation, in IPN interface 107, that the IPN transaction was successfully completed from the user to the merchant. IPN interface 107 may provide an IPN transaction identifier (e.g., a unique alphanumeric code) for the IPN transaction that was completed. Issuer system 106 may incorporate the IPN transaction identifier in a transaction authorization response to be sent from issuer system 106 back to POS device 102, as described in connection with step 414.

[0109] As shown in FIG. 4, process 400 may include, at step 414, transmitting a transaction authorization response to POS device 102. For example, issuer system 106 may transmit a transaction authorization response to POS device 102 corresponding to the transaction authorization request that was initially generated by POS device 102. The transaction authorization response may be communicatively routed from issuer system 106 to POS device 102 through one or more of transaction processing system 105, acquirer system 104, or merchant system 103. Each system along the communicative route may transmit all or some of the transaction authorization response, and may additionally or alternatively augment the transaction authorization response as the transaction authorization response is routed through the respective system. The POS device 102 may then receive at least a portion of the transaction authorization response from the issuer system 106 (e.g., via transaction processing system 105), and the at least a portion of the transaction authorization response may include the IPN transaction identifier. Transmission of the at least a portion of the transaction authorization response to POS device 102 may cause POS device 102 to provide (e.g., display, audibilize, etc.) at least a portion of the transaction authorization response in an interface (e.g., display, speakers, etc.) of POS device 102. In some non-limiting embodiments or aspects, the transaction authorization response may further include a credit card transaction identifier (e.g., a unique alphanumeric code) associated with the second or additional transactions processed by issuer system 106. The user may then verify, by viewing/listening to POS device 102, that at least one transaction was successfully completed (e.g., an IPN transaction, a credit card transaction, and/or the like).

[0110] Referring now to FIG. 5, shown is a flow diagram for a method for instant payment transactions in a credit card transaction network, according to some nonlimiting embodiments or aspects. The steps shown in FIG. 5 are for example purposes only. It will be appreciated that additional, fewer, different, and/or a different order of steps may be used in some non-limiting embodiments or aspects. In some nonlimiting embodiments or aspects, a step may be automatically performed in response to performance and/or completion of a prior step. As shown, process 500 includes steps for a modified payment device 101 with embedded IPN application information, to be used to initiate an IPN transaction within a credit card transaction network. The steps of process 500 may be performed by one or more of payment device 101 , POS device 102, merchant system 103, payment gateway 601 , transaction processing system 105, issuer system 106, and IPN interface 107, as described below. [0111] As shown in FIG. 5, process 500 may include, at step 502, providing the modified payment device 101 for a transaction. For example, payment device 101 may include an embedded chip storing, at least partly, a payment device identifier, an IPN identifier, and/or the like, that can be read by a short range reader (e.g., radio frequency identification (RFID) transceiver) of a computing device (e.g., a mobile device of the user, such as a smartphone running one or more applications for transacting). The mobile device may be accessing a local application or web application (e.g., a browser accessing a merchant website) for completing a transaction with the merchant. The read information from payment device 101 may be transmitted to POS device 102 and/or merchant system 103 at least partly over communication network 108, and POS device 102 and/or merchant system 103 may forward the information, in a transaction authorization request, to transaction processing system 105. The forwarded transaction authorization request may include the merchant key.

[0112] As shown in FIG. 5, process 500 may include, at step 504, transmitting the transaction authorization request to issuer system 106. For example, transaction processing system 105 may transmit the transaction authorization request, modified or unmodified, to issuer system 106. In some non-limiting embodiments or aspects, before transaction processing system 105 forwards the transaction authorization request to issuer system 106, transaction processing system 105 may augment the transaction authorization request to include a processing code. As part of step 504, transaction processing system 105 may act as a message router by determining the issuer associated with payment device 101 based on a payment device identifier in the transaction authorization request transmitted from POS device 102 and/or acquirer system 104. For example, transaction processing system 105 may use a lookup table (e.g., based on the first several digits of a PAN) to determine an issuer institution associated with payment device 101 . After determining the appropriate issuer system 106 associated with an issuer of payment device 101 , transaction processing system 105 may route the transaction authorization request to issuer system 105.

[0113] As shown in FIG. 5, process 500 may include, at step 506, initiating an IPN transaction. For example, receipt of the transaction authorization request from transaction processing system 105 may cause (e.g., trigger) issuer system 106 to initiate an IPN transaction from a transaction account associated with payment device 101 to a transaction account associated with the merchant using the IPN. In particular, issuer system 106 may use IPN interface 107 to submit an IPN transaction corresponding to some or all of the transaction amount from user to the merchant. Issuer system 106 may determine a recipient merchant of the IPN transaction based on the merchant key of the transaction authorization request. The merchant key may be directly used, in the IPN interface 107, as a designation of a recipient transaction account in the IPN. Issuer system 106 may determine a transaction amount of the IPN transaction based on at least one transaction amount in the transaction authorization request. Issuer system 106 may determine a payer transaction account based on the payment device identifier in the transaction authorization request. In some non-limiting embodiments or aspects, for split tender transactions, a second transaction amount in the transaction authorization request may be associated with a second portion of the transaction to be paid by a default protocol for clearing and settling in the credit card transaction network. In this manner, issuer system 106 may authorize and authenticate the transaction authorization request for an IPN transaction and/or a credit card transaction, which may be different amounts, from a single transaction authorization request.

[0114] As shown in FIG. 5, process 500 may include, at step 508, causing an electronic transfer of funds in response to the initiated IPN transaction by issuer system 106. For example, IPN interface 107 may be used by issuer system 106 to cause a debit in the transaction account of the user and a credit in the transaction account of the merchant, using the instant payment protocol of the IPN. As such, an instantaneous, or near-instantaneous, cleared and settled payment may be made from the transaction account of the user to the transaction account of the merchant. Issuer system 106 may receive confirmation, in IPN interface 107, that the IPN transaction was successfully completed from the user to the merchant. IPN interface 107 may provide an IPN transaction identifier (e.g., a unique alphanumeric code) for the IPN transaction that was completed. Merchant system 103 may receive notification (e.g., a confirmation message), via the IPN, that payment was made from the user to the merchant via IPN transaction. Likewise, the user may receive notification, via the IPN, that the IPN transaction was completed (e.g., via the mobile device).

[0115] Referring now to FIG. 6, shown is a flow diagram for a method for instant payment transactions in a credit card transaction network, according to some nonlimiting embodiments or aspects. The steps shown in FIG. 6 are for example purposes only. It will be appreciated that additional, fewer, different, and/or a different order of steps may be used in some non-limiting embodiments or aspects. In some nonlimiting embodiments or aspects, a step may be automatically performed in response to performance and/or completion of a prior step. As shown, process 600 includes steps for IPN transactions in a credit card transaction network, further including payment gateway 601 and use of an account funding transaction (AFT) protocol (e.g., where an AFT is a type of transaction where a payment service provider, such as a bank or a financial institution, directly debits a payment from a user’s transaction account). The steps of process 600 may be performed by one or more of payment device 101 , POS device 102, merchant system 103, payment gateway 601 , transaction processing system 105, issuer system 106, and IPN interface 107, as described below.

[0116] As shown in FIG. 6, process 600 may include, at step 602, providing a payment device 101 for payment in a transaction. For example, a user may provide their payment device 101 , or identifying information of their payment device 101 , for use in a transaction with a merchant. As a part of step 602 or step 604, the user may select an option in an interface of POS device 102 to designate at least part of an amount for the transaction to be paid by IPN transaction.

[0117] As shown in FIG. 6, process 600 may include, at step 604, transmitting a transaction authorization request to payment gateway 601. For example, the user input may cause POS device 102 to generate and transmit a transaction authorization request to payment gateway 601 , directly or indirectly through merchant system 103. The transaction authorization request may include one or more fields identifying that at least a part of the transaction is to be executed in an IPN. The transaction authorization request sent from POS device 102 to payment gateway 601 may further include a transaction amount, additional transaction amounts, a payment device identifier of payment device 101 , an IPN identifier of an IPN, a merchant key of the merchant, and/or the like. The merchant key may be included in the transaction authorization request when generated by POS device 102, when communicated through merchant system 103, or after received by payment gateway 601 .

[0118] As shown in FIG. 6, process 600 may include, at step 606, transmitting an AFT request to issuer system 106. For example, payment gateway 601 may identify issuer system 106 based on the payment device identifier input by the user, and may further transmit an AFT request to issuer system 106 to execute an AFT from a transaction account of the user. This may cause a debit to make funds immediately available from the user’s transaction account, using the AFT protocol.

[0119] As shown in FIG. 6, process 600 may include, at step 608, transmitting an AFT response to payment gateway 601 . For example, issuer system 106 may make user funds available using the AFT, based on the AFT request. The results of the AFT may be populated in an AFT response, which may be transmitted to payment gateway 601 . The AFT response may include, at least partly, an AFT identifier (e.g., a unique alphanumeric code identifying the AFT).

[0120] As shown in FIG. 6, process 600 may include, at step 610, transmitting the acquired funds from the AFT to the merchant account using IPN interface 107. For example, payment gateway 601 , having verified that the funds are available in the user’s transaction account, based on the AFT response, may use IPN interface 107 to initiate an IPN transaction from a transaction account of the user to the transaction account of the merchant. Payment gateway 601 may determine a recipient merchant of the IPN transaction based on the merchant key of the transaction authorization request received from POS device 102. The merchant key may be directly used, in the IPN interface 107, as a designation of a recipient transaction account in the IPN. Payment gateway 601 may determine a transaction amount of the IPN transaction based on at least one transaction amount in the transaction authorization request.

[0121] As shown in FIG. 6, process 600 may include, at step 612, causing an electronic transfer of funds in response to the initiated IPN transaction by payment gateway 601 . For example, IPN interface 107 may be used by payment gateway 601 to confirm the debit in the transaction account of the user (for the same funds made available by AFT) and a credit in the transaction account of the merchant, using the instant payment protocol of the IPN. As such, an instantaneous, or near- instantaneous, cleared and settled payment may be made from the transaction account of the user to the transaction account of the merchant. Payment gateway 601 may receive confirmation, in IPN interface 107, that the IPN transaction was successfully completed from the user to the merchant. IPN interface 107 may provide an IPN transaction identifier (e.g., a unique alphanumeric code) for the IPN transaction that was completed. Payment gateway 601 may incorporate the IPN transaction identifier in a transaction authorization response to be sent back to POS device 102 from payment gateway 601. Merchant system 103 may receive notification (e.g., a confirmation message), via the IPN, that payment was made from the user to the merchant via IPN transaction. Likewise, the user may receive notification, via the IPN, that the IPN transaction was completed (e.g., via the mobile device).

[0122] Referring now to FIG. 7, shown is a flow diagram for a method for instant payment transactions in a credit card transaction network, according to some nonlimiting embodiments or aspects. The steps shown in FIG. 7 are for example purposes only. It will be appreciated that additional, fewer, different, and/or a different order of steps may be used in some non-limiting embodiments or aspects. In some nonlimiting embodiments or aspects, a step may be automatically performed in response to performance and/or completion of a prior step. As shown in FIG. 7, process 700 includes steps for IPN transactions in a credit card transaction network, further including payment gateway 601 and using the authorization protocol of the credit card transaction network to receive issuer approval before initiating the IPN transaction. The steps of process 700 may be performed by one or more of payment device 101 , POS device 102, merchant system 103, payment gateway 601 , transaction processing system 105, issuer system 106, and IPN interface 107, as described below.

[0123] As shown in FIG. 7, process 700 may include, at step 702, providing a payment device 101 for payment in a transaction. For example, a user may provide their payment device 101 , or identifying information of their payment device 101 , for use in a transaction with a merchant. As a part of step 702 or step 704, the user may select an option in an interface of POS device 102 to designate at least part of an amount for the transaction to be paid by IPN transaction.

[0124] As shown in FIG. 7, process 700 may include, at step 704, transmitting a transaction authorization request to payment gateway 601. For example, the user input may cause POS device 102 to generate and transmit a transaction authorization request to payment gateway 601 , directly or indirectly through merchant system 103. The transaction authorization request may include one or more fields identifying that at least a part of the transaction is to be executed in an IPN. The transaction authorization request sent from POS device 102 to payment gateway 601 may further include a transaction amount, additional transaction amounts, a payment device identifier of payment device 101 , an IPN identifier of an IPN, a merchant key of the merchant, and/or the like. The merchant key may be included in the transaction authorization request when generated by POS device 102, when communicated through merchant system 103, or after received by payment gateway 601 . [0125] As shown in FIG. 7, process 700 may include, at step 706, transmitting a credit card transaction authorization request to transaction processing system 105. For example, payment gateway 601 may generate a credit card transaction authorization request including, at least partly, the transaction amount and the payment device identifier. The credit card transaction authorization request may further include a merchant identifier and/or a payment gateway identifier. The credit card transaction authorization request may be used to obtain issuer authorization, even though an IPN transaction will be executed to cause the actual transfer of electronic funds that were authorized.

[0126] As shown in FIG. 7, process 700 may include, at step 708, transmitting the credit card transaction authorization request to issuer system 106. For example, transaction processing system 105 may route the credit card transaction authorization request, modified or unmodified, to issuer system 106. Transmitting the credit card transaction authorization request may cause issuer system 106 to authorize and/or authenticate a transaction for the transaction amount in the credit card transaction authorization request. This may cause an amount of electronic funds to be temporarily captured, for later debit using the IPN protocol. The result of the credit card transaction authorization may be populated in a credit card transaction authorization response.

[0127] As shown in FIG. 7, process 700 may include, at step 710, transmitting a credit card transaction authorization response to payment gateway 601 . For example, issuer system 106 may transmit the credit card transaction authorization response to payment gateway 601 , based on the merchant identifier and/or payment gateway identifier. Transmitting the credit card transaction authorization response, which includes successful authorization of the transfer of funds, may cause payment gateway 601 to proceed with initiating the IPN transaction using IPN interface 107.

[0128] As shown in FIG. 7, process 700 may include, at step 712, transmitting the captured funds to the merchant account using IPN interface 107. For example, payment gateway 601 , having verified that the funds are available and captured in the user’s transaction account, based on the credit card transaction authorization response, may use IPN interface 107 to initiate an IPN transaction from the transaction account of the user to the transaction account of the merchant. Payment gateway 601 may determine a recipient merchant of the IPN transaction based on a merchant key of the transaction authorization request received from POS device 102. The merchant key may be directly used, in the IPN interface 107, as a designation of a recipient transaction account in the IPN. Payment gateway 601 may determine a transaction amount of the IPN transaction based on at least one transaction amount in the transaction authorization request received from POS device 102.

[0129] As shown in FIG. 7, process 700 may include, at step 714, causing an electronic transfer of funds in response to the initiated IPN transaction by payment gateway 601 . For example, IPN interface 107 may be used by payment gateway 601 to confirm the debit in the transaction account of the user (for the same funds captured via credit card transaction authorization request) and a credit in the transaction account of the merchant, using the instant payment protocol of the IPN. As such, an instantaneous, or near-instantaneous, cleared and settled payment may be made from the transaction account of the user to the transaction account of the merchant. Payment gateway 601 may receive confirmation, in IPN interface 107, that the IPN transaction was successfully completed from the user to the merchant. IPN interface 107 may provide an IPN transaction identifier for the IPN transaction that was completed. Payment gateway 601 may incorporate the IPN transaction identifier in a transaction authorization response to be sent back to POS device 102 from payment gateway 601. Merchant system 103 may receive notification (e.g., a confirmation message), via the IPN, that payment was made from the user to the merchant via IPN transaction. Likewise, the user may receive notification, via the IPN, that the IPN transaction was completed (e.g., via the mobile device).

[0130] Referring now to FIG. 8, shown is a flow diagram for a method for instant payment transactions in a credit card transaction network, according to some nonlimiting embodiments or aspects. The steps shown in FIG. 8 are for example purposes only. It will be appreciated that additional, fewer, different, and/or a different order of steps may be used in some non-limiting embodiments or aspects. In some nonlimiting embodiments or aspects, a step may be automatically performed in response to performance and/or completion of a prior step. As shown in FIG. 8, process 800 includes steps for effecting an IPN transaction in a cross-border scenario. The steps of process 800 may be performed by one or more of payment device 101 , POS device 102, merchant system 103, acquirer system 104, transaction processing system 105, and issuer system 106, as described below.

[0131] As shown in FIG. 8, process 800 may include, at step 802, providing a payment device 101 for payment in a transaction. For example, a user may provide their payment device 101 , or identifying information of their payment device 101 , for use in a transaction with a merchant. As a part of step 802 or step 804, the user may select an option in an interface of foreign POS device 102 to designate at least part of an amount for the transaction to be paid by IPN transaction.

[0132] As shown in FIG. 8, process 800 may include, at step 804, transmitting a transaction authorization request to foreign acquirer system 104. For example, the user input may cause foreign POS device 102 to generate and transmit a transaction authorization request to foreign acquirer system 104, directly or indirectly through foreign merchant system 103. The transaction authorization request may include one or more fields identifying that at least a part of the transaction is to be executed in an IPN. The transaction authorization request sent from foreign POS device 102 to foreign acquirer system 104 may further include a transaction amount, a payment device identifier of payment device 101 , a merchant identifier, and/or the like. The merchant identifier may be included in the transaction authorization request when generated by foreign POS device 102, when communicated through foreign merchant system 103, or after received by foreign acquirer system 104.

[0133] As shown in FIG. 8, process 800 may include, at step 806, transmitting the transaction authorization request to transaction processing system 105. For example, foreign acquirer system 104 may transmit the transaction authorization request, modified or unmodified, to transaction processing system 105 for further processing. The transaction authorization request may resemble that used for IPN transactions, such as shown in FIG. 4, but transaction processing system 105 may determine (e.g., based on the payment device identifier and merchant identifier) that the issuer system 106 and acquirer system 104 are cross-border (e.g., in different territories/governmental regions), which may not be configured with a same IPN. Based on that determination, transaction processing system 105 may perform a substitute transaction using AFT protocol or original credit transaction (OCT) protocol (e.g., where a payment service provider, such as a bank or a financial institution, directly credits a payment to the recipient's card or account).

[0134] As shown in FIG. 8, process 800 may include, at step 808, transmitting an AFT or OCT request to issuer system 106. For example, transaction processing system 105 may identify issuer system 106 based on the payment device identifier of the transaction authorization request and may further transmit an AFT or OCT request to issuer system 106 to execute an AFT or OCT from a transaction account of the user. [0135] As shown in FIG. 8, process 800 may include, at step 810, transmitting the secured funds to foreign acquirer system 104. For example, transaction processing system 105 may, after securing funds from a transaction account of the user using AFT or OCT protocol, transmit the secured funds to a transaction account of the merchant. After completion of the transfer, a message may be transmitted from acquirer system 104 to the merchant and/or POS device 102 to indicate that the transaction has been completed. POS device 102 may be triggered, based on the message received from acquirer system 104, to provide a confirmation of transaction completion to user, which may include an AFT or OCT transaction identifier received from acquirer system 104.

[0136] As shown in FIG. 8, process 800 may include, at step 812, transmitting notification of the successful payment to the user. For example, issuer system 106, after releasing funds from the user’s transaction account using AFT or OCT protocol, may transmit a message to a computing device of the user to notify the user that the transfer of funds was completed from a transaction account of the user.

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

Claims

WHAT IS CLAIMED IS:

1 . A system comprising: at least one processor of a transaction processing system configured in a credit card transaction network, the at least one processor configured to: receive a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request comprising a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device; determine an issuer system based on the payment device identifier; cause the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN, wherein, when causing the issuer system to initiate the IPN transaction, the at least one processor is configured to: transmit at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request comprising the transaction amount, the merchant key, and the IPN identifier; receive a transaction authorization response from the issuer system, the transaction authorization response comprising an IPN transaction identifier associated with the IPN transaction initiated by the issuer system; and transmit at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response comprises the IPN transaction identifier.

2. The system of claim 1 , wherein the merchant key comprises a combination of an identifier of a merchant transaction account and an identifier associated with the merchant.

3. The system of claim 1 , wherein transmitting the at least a portion of the transaction authorization response to the POS device causes the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

4. The system of claim 1 , wherein the at least a portion of the transaction authorization request further comprises a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

5. The system of claim 1 , wherein the transaction authorization request further comprises (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

6. The system of claim 5, wherein the at least a portion of the transaction authorization request further comprises the second transaction amount, and wherein transmitting the at least a portion of the transaction authorization request to the issuer system further causes the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount.

7. The system of claim 6, wherein the transaction authorization response further comprises a credit card transaction identifier associated with the second transaction, and wherein the at least a portion of the transaction authorization response comprises the credit card transaction identifier.

8. A method comprising: receiving, with at least one processor of a transaction processing system configured in a credit card transaction network, a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request comprising a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device; determining, with at least one processor of the transaction processing system, an issuer system based on the payment device identifier; causing, with at least one processor of the transaction processing system, the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN, wherein causing the issuer system to initiate the IPN transaction comprises: transmitting at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request comprising the transaction amount, the merchant key, and the IPN identifier; receiving, with at least one processor of the transaction processing system, a transaction authorization response from the issuer system, the transaction authorization response comprising an IPN transaction identifier associated with the IPN transaction initiated by the issuer system; and transmitting, with at least one processor of the transaction processing system, at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response comprises the IPN transaction identifier.

9. The method of claim 8, wherein the merchant key comprises a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

10. The method of claim 8, wherein transmitting the at least a portion of the transaction authorization response to the POS device causes the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

11 . The method of claim 8, wherein the at least a portion of the transaction authorization request further comprises a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

12. The method of claim 8, wherein the transaction authorization request further comprises (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

13. The method of claim 12, wherein the at least a portion of the transaction authorization request further comprises the second transaction amount, and wherein transmitting the at least a portion of the transaction authorization request to the issuer system further causes the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount.

14. The method of claim 13, wherein the transaction authorization response further comprises a credit card transaction identifier associated with the second transaction, and wherein the at least a portion of the transaction authorization response comprises the credit card transaction identifier.

15. A computer program product, comprising at least one non- transitory computer-readable medium including program instructions that, when executed by at least one processor of a transaction processing system configured in a credit card transaction network, cause the at least one processor to: receive a transaction authorization request from an acquirer system, the transaction authorization request associated with a transaction between a payment device and a merchant, the transaction initiated at a point-of-sale (POS) device of the merchant, and the transaction authorization request comprising a transaction amount, a merchant key of the merchant, an instant payment network (IPN) identifier of an IPN, and a payment device identifier of the payment device; determine an issuer system based on the payment device identifier; cause the issuer system to initiate an IPN transaction from a transaction account associated with the payment device to a transaction account associated with the merchant using the IPN, wherein the program instructions that cause the issuer system to initiate the IPN transaction cause the at least one processor to: transmit at least a portion of the transaction authorization request to the issuer system, the at least a portion of the transaction authorization request comprising the transaction amount, the merchant key, and the IPN identifier; receive a transaction authorization response from the issuer system, the transaction authorization response comprising an IPN transaction identifier associated with the IPN transaction initiated by the issuer system; and transmit at least a portion of the transaction authorization response to the POS device via the acquirer system, wherein the at least a portion of the transaction authorization response comprises the IPN transaction identifier.

16. The computer program product of claim 15, wherein the merchant key comprises a combination of an identifier of the merchant transaction account and an identifier associated with the merchant.

17. The computer program product of claim 15, wherein transmitting the at least a portion of the transaction authorization response to the POS device causes the POS device to provide the at least a portion of the transaction authorization response on a display of the POS device.

18. The computer program product of claim 15, wherein the at least a portion of the transaction authorization request further comprises a processing code configured to cause the issuer system to validate the transaction authorization request and initiate the IPN transaction for the transaction amount.

19. The computer program product of claim 15, wherein the transaction authorization request further comprises (i) an identifier of a split tender transaction type and (ii) a second transaction amount to be processed in a credit card transaction network.

20. The computer program product of claim 19, wherein the at least a portion of the transaction authorization request further comprises the second transaction amount, wherein transmitting the at least a portion of the transaction authorization request to the issuer system further causes the issuer system to initiate a second transaction in the credit card transaction network for the second transaction amount, wherein the transaction authorization response further comprises a credit card transaction identifier associated with the second transaction, and wherein the at least a portion of the transaction authorization response comprises the credit card transaction identifier.