Method, system and computer program product for processing transactions using electronic wallet

Abstract

A computer-implemented method includes storing, by a payment application, payment device data including first and second payment device identifiers, and first and second wallet identifiers corresponding to first and second electronic wallets in which first and second payment device credentials for the first and second payment devices are stored, respectively; initiating a payment transaction with a merchant system; displaying the first and second payment device identifiers; receiving a user input from a user of a user device, the user input comprising a selection of the first payment device identifier; determining that the first electronic wallet contains the first payment device certificate of the first payment device; and facilitating delivery of payment data between the merchant system and the first electronic wallet to initiate processing of the payment transaction.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 390,928, filed on July 20, 2022, the entirety of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to processing transactions and, in non-limiting embodiments or aspects, to methods, systems, and computer program products for processing transactions using an electronic wallet. Background Art

[0004] E-wallets have become an increasingly popular way for users to initiate electronic payment transactions. In order for users to initiate transactions using their e-wallets, merchants must accept that e-wallet as an acceptable form of payment. However, not all merchants accept e-wallets or all types of e-wallets as an acceptable payment method. Summary of the invention

[0005] According to a non-limiting embodiment or aspect, a computer-implemented method is provided, comprising: storing, by a payment application, payment device data of a plurality of payment devices including a first payment device and a second payment device, the payment device data comprising: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which a first payment device credential of the first payment device is stored; and a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which a second payment device credential of the second payment device is stored; initiating, by the payment application, a payment transaction with a merchant system of a merchant; and in response to initiating the payment transaction, displaying the first payment device identifier and the second payment device credential in the payment application and on a user interface of a user device. device identifier; receiving, by the payment application, user input from a user of the user device, the user input comprising a selection of a first payment device identifier; in response to the user selecting the first payment device identifier, determining, by the payment application based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet comprises a first payment device credential of a first payment device corresponding to the first payment device identifier; and in response to determining that the first electronic wallet comprises the first payment device credential, facilitating, by the payment application, the transfer of payment data between the merchant system and the first electronic wallet to initiate processing of a payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0006] In a non-limiting embodiment or aspect, a process of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction may include: retrieving, by a payment application, transaction data associated with the payment transaction from the merchant system; and transmitting, by the payment application, the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, wherein the first electronic wallet may initiate authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) first payment device credentials from the first electronic wallet.

[0007] In a non-limiting embodiment or aspect, a process of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction may include: retrieving, by a payment application, first payment device credentials from the first electronic wallet; and transmitting, by the payment application, the first payment device credentials from the first electronic wallet to the merchant system, wherein the merchant system may initiate authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing transaction data associated with the payment transaction from the merchant system and the first payment device credentials from the first electronic wallet.

[0008] In a non-limiting embodiment or aspect, the first electronic wallet may not be configured to initiate a payment transaction directly with the merchant system.

[0009] In a non-limiting embodiment or aspect, the payment device data of the first payment device may include: a first payment device identifier of the first payment device, a first wallet identifier corresponding to a first electronic wallet in which the first payment device credentials of the first payment device are stored, and a second wallet identifier corresponding to a second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, wherein the selection of the first payment device identifier may further include selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

[0010] In a non-limiting embodiment or aspect, displaying the first payment device identifier may further include displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for the payment transaction.

[0011] In a non-limiting embodiment or aspect, the computer-implemented method may further include providing, by the payment application, a software development kit to a merchant system and / or an acquirer or gateway system of the merchant system, the software development kit comprising a plurality of application programming interfaces (APIs), the plurality of application programming interfaces being configured to cause the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process a payment transaction: a payment application, a first electronic wallet, a second electronic wallet, an electronic payment network, and / or any combination thereof.

[0012] According to a non-limiting embodiment or aspect, a system including a payment application is provided, the payment application including at least one processor, the at least one processor being programmed or configured to: store payment device data of a plurality of payment devices including a first payment device and a second payment device, the payment device data including: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which a first payment device credential of the first payment device is stored; and a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which a second payment device credential of the second payment device is stored; initiate a payment transaction with a merchant system of a merchant; in response to initiating the payment transaction, in the payment application and a user of a user device A first payment device identifier and a second payment device identifier are displayed on an interface; user input is received from a user of a user device, the user input including a selection of the first payment device identifier; in response to the user selecting the first payment device identifier, determining, based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes a first payment device credential of a first payment device corresponding to the first payment device identifier; and in response to determining that the first electronic wallet includes the first payment device credential, facilitating the transfer of payment data between a merchant system and the first electronic wallet to initiate processing of a payment transaction, the payment data including at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0013] In a non-limiting embodiment or aspect, a process of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction may include the payment application including at least one processor, the at least one processor being programmed or configured to: retrieve transaction data associated with the payment transaction from the merchant system; and transmit the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, wherein the first electronic wallet may initiate authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) first payment device credentials from the first electronic wallet.

[0014] In a non-limiting embodiment or aspect, a process of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction may include the payment application including at least one processor, the at least one processor being programmed or configured to: retrieve a first payment device credential from the first electronic wallet; and transmit the first payment device credential from the first electronic wallet to the merchant system, wherein the merchant system may initiate authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing (i) transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credential from the first electronic wallet.

[0015] In a non-limiting embodiment or aspect, the first electronic wallet may not be configured to initiate a payment transaction directly with the merchant system.

[0016] In a non-limiting embodiment or aspect, the payment device data of the first payment device may include: a first payment device identifier of the first payment device, a first wallet identifier corresponding to a first electronic wallet in which the first payment device credentials of the first payment device are stored, and a second wallet identifier corresponding to a second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, wherein the selection of the first payment device identifier may further include selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

[0017] In a non-limiting embodiment or aspect, displaying the first payment device identifier may further include displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for the payment transaction.

[0018] In a non-limiting embodiment or aspect, the payment application may include at least one processor, which is programmed or configured to: provide a software development kit to a merchant system and / or an acquirer or gateway system of the merchant system, the software development kit including multiple application programming interfaces (APIs), and the multiple application programming interfaces are configured to cause the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process a payment transaction: a payment application, a first electronic wallet, a second electronic wallet, an electronic payment network, and / or any combination thereof.

[0019] According to a non-limiting embodiment or aspect, a computer program product is provided, the computer program product comprising at least one non-transitory computer-readable medium, the non-transitory computer-readable medium comprising one or more instructions, the one or more instructions, when executed by at least one processor of a payment application, causing the at least one processor to: store payment device data for a plurality of payment devices including a first payment device and a second payment device, the payment device data comprising: a first payment device identifier for the first payment device and a first wallet identifier corresponding to a first electronic wallet in which first payment device credentials of the first payment device are stored; and a second payment device identifier for the second payment device and a second wallet identifier corresponding to a second electronic wallet in which second payment device credentials of the second payment device are stored; initiate a payment transaction with a merchant system of a merchant; In response to initiating the payment transaction, displaying a first payment device identifier and a second payment device identifier in a payment application and on a user interface of a user device; receiving user input from a user of the user device, the user input including a selection of the first payment device identifier; in response to the user selecting the first payment device identifier, determining, based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes a first payment device credential of a first payment device corresponding to the first payment device identifier; and in response to determining that the first electronic wallet includes the first payment device credential, facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate processing of the payment transaction, the payment data including at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0020] In a non-limiting embodiment or aspect, processing that facilitates the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction may include the one or more instructions causing the at least one processor to: retrieve transaction data associated with the payment transaction from the merchant system; and transmit the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, wherein the first electronic wallet may initiate authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credentials from the first electronic wallet.

[0021] In a non-limiting embodiment or aspect, processing that facilitates the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction may include the one or more instructions causing the at least one processor to: retrieve a first payment device credential from the first electronic wallet; and transmit the first payment device credential from the first electronic wallet to the merchant system, wherein the merchant system may initiate authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising a field containing (i) transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credential from the first electronic wallet.

[0022] In a non-limiting embodiment or aspect, the first electronic wallet may not be configured to initiate a payment transaction directly with the merchant system.

[0023] In a non-limiting embodiment or aspect, the payment device data of the first payment device may include: a first payment device identifier of the first payment device, a first wallet identifier corresponding to a first electronic wallet in which the first payment device credentials of the first payment device are stored, and a second wallet identifier corresponding to a second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, wherein the selection of the first payment device identifier may further include selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

[0024] In a non-limiting embodiment or aspect, displaying the first payment device identifier may further include displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for the payment transaction.

[0025] In a non-limiting embodiment or aspect, the one or more instructions may cause the at least one processor to: provide a software development kit to a merchant system and / or an acquirer or gateway system of the merchant system, the software development kit comprising a plurality of application programming interfaces (APIs), the plurality of application programming interfaces being configured to cause the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process a payment transaction: a payment application, a first electronic wallet, a second electronic wallet, an electronic payment network, and / or any combination thereof.

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

[0027] Clause 1: A computer-implemented method comprising: storing, by a payment application, payment device data of a plurality of payment devices including a first payment device and a second payment device, the payment device data comprising: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which a first payment device credential of the first payment device is stored; and a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which a second payment device credential of the second payment device is stored; initiating, by the payment application, a payment transaction with a merchant system of a merchant; and displaying, in response to initiating the payment transaction, the first payment device identifier and the second payment device identifier in the payment application and on a user interface of a user device ; receiving, by the payment application, user input from a user of a user device, the user input comprising a selection of a first payment device identifier; in response to the user selecting the first payment device identifier, determining, by the payment application based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes a first payment device credential of a first payment device corresponding to the first payment device identifier; and in response to determining that the first electronic wallet includes the first payment device credential, facilitating, by the payment application, the transfer of payment data between a merchant system and the first electronic wallet to initiate processing of a payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0028] Clause 2: A computer-implemented method as described in clause 1, wherein the processing of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction includes: retrieving, by a payment application, transaction data associated with the payment transaction from the merchant system; and transmitting, by the payment application, the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, wherein the first electronic wallet initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) first payment device credentials from the first electronic wallet.

[0029] Clause 3: A computer-implemented method according to clause 1 or 2, wherein the processing of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction includes: retrieving, by a payment application, first payment device credentials from the first electronic wallet; and transmitting, by the payment application, the first payment device credentials from the first electronic wallet to the merchant system, wherein the merchant system initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing transaction data associated with the payment transaction from the merchant system and the first payment device credentials from the first electronic wallet.

[0030] Clause 4: The computer-implemented method of any of clauses 1-3, wherein the first electronic wallet is not configured to initiate the payment transaction directly with the merchant system.

[0031] Clause 5: A computer-implemented method according to any of clauses 1-4, wherein the payment device data of the first payment device includes: a first payment device identifier of the first payment device, a first wallet identifier corresponding to a first electronic wallet in which the first payment device credentials of the first payment device are stored, and a second wallet identifier corresponding to a second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, wherein the selection of the first payment device identifier further includes selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

[0032] Clause 6: A computer-implemented method as described in any of clauses 1-5, wherein displaying the first payment device identifier further comprises displaying at least one icon associated with the first payment device identifier, the at least one icon being configured to accept at least one available offer if the first payment device identifier is selected for a payment transaction.

[0033] Clause 7: A computer-implemented method according to any one of clauses 1-6, further comprising: providing a software development kit by the payment application to the merchant system and / or the merchant system's acquirer or gateway system, wherein the software development kit includes multiple application programming interfaces (APIs), and the multiple application programming interfaces are configured to enable the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process a payment transaction: a payment application, a first electronic wallet, a second electronic wallet, an electronic payment network, and / or any combination thereof.

[0034] Clause 8: A system including a payment application, the payment application including at least one processor, the at least one processor being programmed or configured to: store payment device data of a plurality of payment devices including a first payment device and a second payment device, the payment device data including: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which a first payment device credential of the first payment device is stored; and a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which a second payment device credential of the second payment device is stored; initiate a payment transaction with a merchant system of a merchant; and in response to initiating the payment transaction, display in the payment application and on a user interface of a user device a first payment device identifier and a second payment device identifier; receiving user input from a user of a user device, the user input comprising a selection of the first payment device identifier; in response to the user selecting the first payment device identifier, determining, based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes a first payment device credential of a first payment device corresponding to the first payment device identifier; and in response to determining that the first electronic wallet includes the first payment device credential, facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate processing of a payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0035] Clause 9: A system according to clause 8, wherein the processing that facilitates the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction includes the payment application including at least one processor, the at least one processor being programmed or configured to: retrieve transaction data associated with the payment transaction from the merchant system; and transmit the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, wherein the first electronic wallet initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing: (i) transaction data associated with the payment transaction from the merchant system, and (ii) first payment device credentials from the first electronic wallet.

[0036] Clause 10: A system according to clause 8 or 9, wherein the processing that facilitates the transfer of payment data between the merchant system and the first electronic wallet to initiate a payment transaction includes the payment application including at least one processor, the at least one processor being programmed or configured to: retrieve a first payment device credential from the first electronic wallet; and transmit the first payment device credential from the first electronic wallet to the merchant system, wherein the merchant system initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing (i) transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credential from the first electronic wallet.

[0037] Clause 11: A system according to any of clauses 8-10, wherein the first electronic wallet is not configured to initiate the payment transaction directly with the merchant system.

[0038] Clause 12: A system according to any of clauses 8-11, wherein the payment device data of the first payment device includes: a first payment device identifier of the first payment device, a first wallet identifier corresponding to a first electronic wallet in which the first payment device credentials of the first payment device are stored, and a second wallet identifier corresponding to a second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, wherein the selection of the first payment device identifier further includes selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

[0039] Clause 13: The system of any of clauses 8-12, wherein displaying the first payment device identifier further comprises displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for a payment transaction.

[0040] Clause 14: According to the system described in any of clauses 8-13, the payment application includes at least one processor, and the at least one processor is programmed or configured to: provide a software development kit to the merchant system and / or the merchant system's acquirer or gateway system, the software development kit includes multiple application programming interfaces (APIs), and the multiple application programming interfaces are configured to enable the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process the payment transaction: the payment application, the first electronic wallet, the second electronic wallet, the electronic payment network and / or any combination thereof.

[0041] Clause 15: A computer program product comprising at least one non-transitory computer-readable medium containing one or more instructions that, when executed by at least one processor of a payment application, cause the at least one processor to: store payment device data for a plurality of payment devices including a first payment device and a second payment device, the payment device data comprising: a first payment device identifier for the first payment device and a first wallet identifier corresponding to a first electronic wallet in which a first payment device credential of the first payment device is stored; and a second payment device identifier for the second payment device and a second wallet identifier corresponding to a second electronic wallet in which a second payment device credential of the second payment device is stored; initiate a payment transaction with a merchant system of a merchant; and in response to initiating the payment transaction, A method of processing a payment transaction in which a merchant system and a user device are connected and displayed on a user interface of a user device, wherein the merchant system displays a first payment device identifier and a second payment device identifier in a payment application and on a user interface of a user device; receiving user input from a user of the user device, the user input comprising a selection of the first payment device identifier; in response to the user selecting the first payment device identifier, determining, based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes a first payment device credential of a first payment device corresponding to the first payment device identifier; and in response to determining that the first electronic wallet includes the first payment device credential, facilitating the transfer of payment data between a merchant system and the first electronic wallet to initiate processing of a payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0042] Clause 16: A computer program product according to clause 15, wherein the processing of facilitating the transfer of payment data between a merchant system and a first electronic wallet to initiate a payment transaction includes the one or more instructions causing the at least one processor to: retrieve transaction data associated with the payment transaction from the merchant system; and transmit the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, wherein the first electronic wallet initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing: (i) transaction data associated with the payment transaction from the merchant system, and (ii) first payment device credentials from the first electronic wallet.

[0043] Clause 17: A computer program product according to clause 15 or 16, wherein the processing that facilitates the transfer of payment data between the merchant system and the first electronic wallet to initiate a payment transaction includes the one or more instructions causing the at least one processor to: retrieve a first payment device credential from the first electronic wallet; and transmit the first payment device credential from the first electronic wallet to the merchant system, wherein the merchant system initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message including fields containing (i) transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credential from the first electronic wallet.

[0044] Clause 18: The computer program product of any of clauses 15-17, wherein the first electronic wallet is not configured to initiate a payment transaction directly with the merchant system.

[0045] Clause 19: A computer program product according to any one of clauses 15-18, wherein the payment device data of the first payment device includes: a first payment device identifier of the first payment device, a first wallet identifier corresponding to a first electronic wallet in which the first payment device credentials of the first payment device are stored, and a second wallet identifier corresponding to a second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, wherein the selection of the first payment device identifier further includes selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

[0046] Clause 20: A computer program product according to any of clauses 15-19, wherein displaying the first payment device identifier further comprises displaying at least one icon associated with the first payment device identifier, the at least one icon being configured to accept at least one available offer if the first payment device identifier is selected for a payment transaction.

[0047] Clause 21: A computer program product according to any of clauses 15-20, wherein the one or more instructions cause the at least one processor to: provide a software development kit to a merchant system and / or an acquirer or gateway system of the merchant system, the software development kit comprising a plurality of application programming interfaces (APIs), the plurality of application programming interfaces being configured to cause the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process a payment transaction: a payment application, a first electronic wallet, a second electronic wallet, an electronic payment network, and / or any combination thereof.

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

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

[0050] Figure 1 is a schematic diagram of a system for processing transactions using an electronic wallet according to some non-limiting embodiments or aspects;

[0051] Figure 2 is a registration user interface of a user device according to some non-limiting embodiments or aspects;

[0052] Figure 3 is a checkout user interface of a user device, according to some non-limiting embodiments or aspects;

[0053] Figure 4 is a payment selection user interface of a user device, according to some non-limiting embodiments or aspects;

[0054] Figures 5A-5C are various user interfaces of a user device according to some non-limiting embodiments or aspects;

[0055] Figure 6 is a diagram of steps of a method for processing a transaction using an electronic wallet according to some non-limiting embodiments or aspects; and

[0056] Figure 7 Example components of an apparatus for use in conjunction with non-limiting embodiments or aspects are shown. DETAILED DESCRIPTION

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

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

[0059] 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. For example, an account identifier in a real-time payment (RTP) transaction may include an identifier for a sender's account (referred to as a debtor's account) and an identifier for a recipient's account (referred to as a creditor's account). An account identifier may be alphanumeric or any combination of characters and / or symbols. A token may be associated with a PAN, a debtor's account identifier, a creditor's account identifier, or other original account identifier in one or more data structures (e.g., one or more databases, etc.) so that the token can be used to conduct transactions without directly using the original account identifier. In some instances, an original account identifier may be associated with multiple tokens for different individuals or purposes.

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

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

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

[0063] As used herein, the terms "issuer," "issuer institution," "issuer bank," or "payment device issuer" may refer to one or more entities that provide an individual (e.g., a user, a customer, etc.) with an account for conducting payment transactions, such as credit card payment transactions and / or debit card payment transactions. For example, an issuer institution may provide a customer with an account identifier, such as a PAN, that uniquely identifies one or more accounts associated with the customer. In some non-limiting embodiments, an issuer may be associated with a bank identification number (BIN) that uniquely identifies the issuer institution. As used herein, an "issuer system" may refer to one or more computer systems operated by or on behalf of an issuer, such as a server that executes one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing transactions.

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

[0065] As used herein, the term "payment device" may refer to a payment card (e.g., a credit or debit card), a gift card, a smart card, smart media, a payroll card, a healthcare card, a wristband, a machine-readable medium containing account information, a key chain device or pendant, a radio frequency identification (RFID) transponder, a retailer discount or membership card, etc. A payment device may contain volatile or non-volatile memory to store information (e.g., an account identifier, the name of the account holder, etc.).

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

[0067] As used herein, the term "point of sale (POS) device" may refer to one or more devices that can be used by a merchant to conduct a transaction (e.g., a payment transaction) and / or process a transaction. For example, a POS device may include one or more client devices. Additionally or alternatively, a POS device may include peripheral devices, card readers, scanning devices (e.g., code scanners), Communication receivers, near field communication (NFC) receivers, RFID receivers and / or other contactless transceivers or receivers, contact-based receivers, payment terminals, etc.

[0068] As used herein, the term "point of sale (POS) system" may refer to one or more client devices and / or peripheral devices used by merchants to conduct transactions. For example, a POS system may include one or more POS devices, and / or other similar devices that can be used to conduct payment transactions. In some non-limiting embodiments, a POS system (e.g., a merchant POS system) may include one or more server computers that are programmed or configured to process online payment transactions through a web page, a mobile application, etc.

[0069] As used herein, the term "processor" may refer to any type of processing unit, such as a single processor having one or more cores, one or more cores of one or more processors, multiple processors each having one or more cores, and / or other arrangements and combinations of processing units. References to "at least one processor" may refer to the aforementioned processors or to different processors.

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

[0071] As used herein, the term "system" may refer to one or more computing devices or combinations of computing devices, such as, but not limited to, processors, servers, client devices, software applications, and / or other similar components.

[0072] As used herein, the term "transaction service provider" may refer to an entity that receives transaction authorization requests from merchants or other entities and, in some cases, provides payment assurance through an agreement between the transaction service provider and the issuer organization. For example, a transaction service provider may include, for example The term "transaction processing system" may refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction processing server that executes one or more software applications. The 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.

[0073] Non-limiting embodiments or aspects described herein relate to systems, methods, and computer program products for processing transactions using an electronic wallet. Non-limiting embodiments or aspects include a payment application that stores payment device data for a payment device having payment device credentials stored in different electronic wallets. In response to a user initiating a payment transaction using a payment application, the payment application may display the payment device and enable the user to select a payment device to process the payment transaction. In some non-limiting embodiments or aspects, if the selected payment device stores its payment credentials in multiple wallets, the user may further select an electronic wallet to proceed with. Based on these selections, the payment application facilitates the transfer of payment data between a merchant system and an electronic wallet corresponding to the selected payment device. This may include authorization for the payment application to retrieve payment device credentials from the electronic wallet and provide them to the merchant system to initiate a transaction. This may include authorization for the payment application to retrieve transaction data from the merchant system and provide them to the electronic wallet to initiate a transaction. The arrangement of the payment application between the merchant system and the electronic wallet enables an electronic wallet that is not originally configured to directly initiate a transaction with the merchant system (e.g., because the electronic wallet is not integrated with the merchant system) to be used in a transaction with a payment application operating as an intermediary.

[0074] In some non-limiting embodiments or aspects, the payment transaction may be a cross-border payment transaction initiated outside of the user's country or region. The e-wallet may be located in the user's country, while the merchant may be located in a different country or region. In such transactions, the merchant system may be less likely to accept the e-wallet as a form of payment, so that the payment application may enable the transaction to be processed. However, the payment application may also be used to process non-cross-border transactions.

[0075] See also Figure 1 , system 100 is shown for processing transactions using an electronic wallet. System 100 can process electronic payment transactions. System 100 may include a merchant system 102 of a merchant participating in a payment transaction, and merchant system 102 may include a software development kit (SDK) 104. System 100 may include a user device 106 with a payment application 108, the payment application including an adapter layer 110 and a service provider 112. Payment application 108 may be a mobile application, a web-based application, etc. Payment application 108 may be operated by or on behalf of a transaction service provider.

[0076] The system 100 may include an external (e.g., external to the payment application 108) transaction system 114, which includes a first electronic wallet 116 and a second electronic wallet 118. The user device 106 may also include the first electronic wallet 116 and the second electronic wallet 118 as electronic wallet applications, which may be separate from the payment application 108. The user may utilize the first and / or second electronic wallets 116, 118 to store payment device credentials for their various payment devices. The first and / or second electronic wallets 116, 118 on the user device 106 may be used to initiate payment transactions directly with the merchant system 102 that accepts those electronic wallets as a payment method.

[0077] The system 100 may include an electronic payment network 120 for processing electronic payment transactions, including authorizing, clearing, and settling payment transactions. The electronic payment network 120 may optionally include an acquirer and / or gateway system 122 associated with facilitating contact between the merchant system 102 and a transaction processing system 124. The electronic payment network 120 may include a transaction processing system. The electronic payment network 120 may include an issuer system 126.

[0078] See also Figure 1 and 2 , the system can register payment devices from multiple electronic wallets 116, 118 on the user device 106 with the payment application 108 that is also on the user device 106. The payment application 108 (e.g., via the adapter layer 110) can communicate with the multiple electronic wallets 116, 118 (e.g., and any other external transaction systems 114) to retrieve the user's payment device with the payment credentials stored with the multiple electronic wallets 116, 118, and the payment application 108 can display the payment device identifiers 130a-c of the retrieved payment devices on the user interface 128 of the user device 106. The adapter layer 110 can communicate with the external transaction system 114 and can be a standard interface via which the external transaction system 114 connects to the payment application 108. To register the payment device with the payment application 108, the user can press the "Register" selectable option 132a-c.

[0079] Payment devices from multiple different e-wallets (e.g., a first e-wallet 116 and a second e-wallet 118) may be registered with the payment application 108. For example, a first payment device may have its payment device credentials stored in the first e-wallet 116, and a second payment device may have its payment device credentials stored in the second e-wallet 118.

[0080] In some non-limiting embodiments or aspects, the first and second e-wallets 116, 118 may not be configured to directly initiate payment transactions with the merchant system 102 involved in the payment transaction. Initiating a payment transaction "directly" with the merchant system 102 means that the merchant system 102 does not accept the e-wallet as a form of payment because the merchant system 102 and the e-wallet are not integrated to process the payment transaction.

[0081] A payment device that may be registered from a different e-wallet may include a payment card (eg, a credit or debit card), or may include a user's financial account issued to the user by an e-wallet.

[0082] Registering a payment device with the payment application 108 may utilize the payment application 108 to store certain payment device data of the payment device. The payment application may register the payment device by storing a payment device identifier of the payment device and a wallet identifier of an electronic wallet in which the payment device credentials of the payment device are stored in association with each other. The wallet identifier may identify a related electronic wallet from other electronic wallet products. In embodiments where the payment device credentials of the payment device are contained in multiple wallets, multiple wallet identifiers may be stored in association with the payment device identifier. The payment device identifier may enable a user to identify the payment device relative to other payment devices of the user registered with the payment application 108, and in some embodiments, the payment device identifier may include: the name of the payment device, a nickname of the payment device, a photo of the front of the payment device, the last 4 digits of the payment device PAN number, etc. The payment device identifier may be different from the PAN or token of the payment device, and as an example, may not be transaction data required for the payment network 120 to process payment transactions.

[0083] Registering a payment device with the payment application 108 may not include storing payment device credentials of the registered payment device with the payment application 108. The payment device credentials are different from the payment device identifier and include a unique account identifier for processing payment transactions using the payment device. Examples of payment device credentials that may not be stored on the payment application 108 include PAN, token, cvv code, expiration date, etc.

[0084] See also Figure 1 , 3 and 4, the user may initiate a payment transaction using the payment application 108 . Figure 3 A user interface 128 of a user device 106 is shown displaying a checkout page. The checkout page may display transaction details 134 of the payment transaction. The checkout page may also display a payment selectable option 136 which, once pressed by the user, initiates a payment transaction with the merchant system 102 using the payment application 108.

[0085] See also Figure 1 and4 In response to initiation of a payment transaction, the payment application 108 may display payment device identifiers 130a-c of payment devices registered with the payment application 108 on the user interface 128 of the user device 106. The payment application 108 may further display a wallet identifier 138a-c for each of the displayed payment device identifiers 130a-c. Figure 4 As shown, some payment device identifiers 130b-c may be associated with only a single electronic wallet (e.g., have their payment device credentials stored in only a single electronic wallet), while payment device identifier 130a may be associated with multiple electronic wallets.

[0086] The payment application 108 may further display at least one offer icon 140a-b associated with the payment device identifier 130a-c, the at least one offer icon 140a-b being configured to accept at least one available offer if the payment device identifier 130a-c associated therewith is selected for a payment transaction. Non-limiting examples of offers associated with the offer icons 140a-b include a reduction in an amount or percentage on current or future purchases, reward points, free products or services, rebates, promotional repayment plans, etc. Figure 4 In the non-limiting example of FIG. 1 , the offer icons 140a - b are associated with an installment payment ( 140a ) and 5% of the purchase price ( 140b ).

[0087] See also Figure 1 and 4 , the payment application 108 may receive user input 142 from the user of the user device 106. The user input 142 may include a selection of a payment device to be used in the payment transaction. After providing the user input 142, the user may select a payment submission selectable option 144 to cause the payment application 108 to continue processing the payment transaction.

[0088] In response to the user selecting the payment device identifier, the payment application 108 may determine an electronic wallet that includes the payment device credentials of the selected payment device. The electronic wallet may be determined based on the wallet identifier associated with the selected payment device. In embodiments where the selected payment device is associated with multiple electronic wallets, the payment application 108 may receive further user input including a selection of a single wallet identifier from the multiple wallet identifiers to cause the payment transaction to proceed using the selected electronic wallet using the selected payment device.

[0089] See also Figure 1In response to determining that the electronic wallet includes the payment device credentials of the selected payment device, the payment application 108 can facilitate the transfer of payment data between the merchant system 102 and the corresponding electronic wallet. For the description below, it is determined that the payment device selected by the user stores its payment credentials in the first electronic wallet 116, so that the payment application 108 can facilitate the transfer of payment data between the merchant system 102 and the first electronic wallet 116.

[0090] The payment data communicated may be data required to process an electronic payment transaction via the electronic payment network 120, such as data elements specified in ISO 8583. Certain payment data may be data collected by the merchant system 102 (and / or its acquirer and / or gateway system 122), which may include transaction data associated with the payment transaction. Non-limiting examples of transaction data may include merchant, acquirer or gateway identifiers, transaction time or location, product or service identifiers, merchant classification codes, transaction amounts, etc. Certain payment data may be data collected by the first electronic wallet 116, which may include payment device credentials for a selected payment device. Non-limiting examples of payment device credentials include PAN, tokens, cvv codes, expiration dates, etc.

[0091] In some non-limiting embodiments or aspects, the payment application 108 (e.g., its facilitator 112) can facilitate the communication of payment data. The facilitator 112 of the payment application 108 can communicate with an external transaction system 114 (external to the payment application 108). Figure 1 In a non-limiting example, the service provider 112 can communicate with the first electronic wallet 116 and the second electronic wallet 118.

[0092] In some non-limiting embodiments or aspects, the facilitator 112 may retrieve transaction data for the payment transaction from the merchant system 102. The facilitator 112 may transmit this retrieved transaction data to the first electronic wallet 116. Upon receiving the transaction data, the first electronic wallet 116 may include data required to initiate authorization for the payment transaction. Thus, in response to receiving the transaction data from the facilitator 112, the first electronic wallet 116 may transmit a message to the electronic payment network 120 to initiate authorization for the payment transaction. The message may contain a data field containing the transaction data from the merchant system 102 and the payment device credentials from the first electronic wallet 116.

[0093] Continue to view Figure 1, the first electronic wallet 116 may transmit a message to the transaction processing system 124 (e.g., corresponding to the selected payment device). In response, the transaction processing system 124 may transmit an authorization request to the issuer system 126 (e.g., corresponding to the selected payment device) so that the issuer system 126 generates an authorization decision. The authorization decision may be an authorization, partial authorization, or a denial of the payment transaction. The issuer system 126 may transmit an authorization response back to the transaction processing system 124, the authorization response containing a field including the authorization decision. The transaction processing system 124 may transmit the authorization decision to the first electronic wallet 116 and / or the merchant system 102. The first electronic wallet 116 may transmit the authorization decision to the merchant system 102 via the facilitator 112 of the payment application 108.

[0094] In some non-limiting embodiments or aspects, the facilitator 112 may retrieve the payment device credentials from the first electronic wallet 116. The facilitator 112 may transmit these retrieved payment device credentials to the merchant system 102. Upon receiving the payment device credentials, the merchant system 102 may include the data required to initiate authorization for the payment transaction. Thus, in response to receiving the payment device credentials from the facilitator 112, the merchant system 102 may transmit a message to the electronic payment network 120 to initiate authorization for the payment transaction. The message may contain a data field containing transaction data from the merchant system 102 and the payment device credentials from the first electronic wallet 116.

[0095] Continue to view Figure 1 , the merchant system 102 may transmit a message to the transaction processing system 124 (e.g., corresponding to the selected payment device), which may be transmitted directly to the transaction processing system 124 or transmitted to the transaction processing system 124 via the acquirer and / or gateway system 122. In response, the transaction processing system 124 may transmit an authorization request to the issuer system 126 (e.g., corresponding to the selected payment device) so that the issuer system 126 generates an authorization decision. The authorization decision may be to authorize, partially authorize, or deny the payment transaction. The issuer system 126 may transmit an authorization response back to the transaction processing system 124, the authorization response containing a field including the authorization decision. The transaction processing system 124 may transmit the authorization decision to the merchant system 102 and / or the first electronic wallet 116. The merchant system 102 may transmit the authorization decision to the first electronic wallet 116 via the facilitator 112 of the payment application 108. The authorized transaction may continue to complete the processing of the payment transaction.

[0096] Continue to view Figure 1In some non-limiting embodiments or aspects, the payment application 108 may provide a software development kit (SDK) 104 to the merchant system 102 and / or its acquirer and / or gateway system 122. The SDK 104 may include one or more application programming interfaces (APIs) and / or other mechanisms or protocols for interaction between systems or applications, which are configured to cause the merchant system 102 and / or the acquirer and / or the gateway system 122 to generate at least one API call to initiate processing of a payment transaction initiated using the payment application 108. The API may be configured to cause the merchant system 102 and / or the acquirer and / or the gateway system 122 to generate at least one API call to at least one of the following to process the payment transaction: the payment application 108, the first electronic wallet 116, the second electronic wallet 118, the electronic payment network 120, and / or any combination thereof. In response to the payment application 108 initiating the payment transaction, the merchant system 102 may call the API from the SDK 104 to enable the merchant system 102 to execute the protocols required to process such payment transaction.

[0097] See also Figures 5A-5C , showing various user interfaces 128 of a user device 106 according to some non-limiting embodiments or aspects.

[0098] Figure 5A Display of notification 146 showing status of payment transaction. Notification may be displayed on user interface 128 in payment application 108 of user device 106. Notification 146 may provide the user with the status of the payment transaction, such as whether it is initiated, delayed, authorized, declined, cleared, settled, completed, disputed, etc. Notification 146 may provide updates on the status of a reward, such as the amount of reward points earned by the payment transaction, progress updates for the reward, that the reward has been earned, that the reward has been redeemed or can be redeemed, etc.

[0099] Figure 5B A display of a transaction history 148 on the user interface 128 in the payment application 108 of the user device 106 is shown. The transaction history 148 may show a history of payment transactions initiated and / or completed by the payment application 108, including any relevant data such as merchant information, product information, date / time information, amount information, etc. The transaction history 148 may display data associated with offers earned and / or redeemed.

[0100] Figure 5C A display of selectable offer 150 on user interface 128 in payment application 108 of user device 106 is shown. Selectable offer 150 may correspond to a discounted product or service that may be purchased and / or redeemed by initiating a transaction using payment application 108 (e.g., by user selection of selectable offer 150).

[0101] See also Figure 6 , showing a method 600 for processing transactions using an electronic wallet according to some non-limiting embodiments or aspects. It should be understood that one or more steps of the method 600 can be performed automatically and / or in response to previous steps.

[0102] At step 602, method 600 may include storing, by the payment application, payment device data for a plurality of payment devices including a first payment device and a second payment device. The payment device data may include a first payment device identifier for the first payment device and a first wallet identifier corresponding to a first electronic wallet in which first payment device credentials are stored; and a second payment device identifier for the second payment device and a second wallet identifier corresponding to a second electronic wallet in which second payment device credentials are stored.

[0103] At step 604 , method 600 may include initiating, by the payment application, a payment transaction with a merchant system of the merchant.

[0104] At step 606 , method 600 may include displaying the first payment device identifier and the second payment device identifier in the payment application and on a user interface of the user device in response to initiation of the payment transaction.

[0105] At step 608 , method 600 may include receiving, by the payment application, user input from a user of the user device, the user input comprising a selection of a first payment device identifier.

[0106] At step 610 , method 600 may include, in response to the user selecting the first payment device identifier, determining, by the payment application based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes first payment device credentials of a first payment device corresponding to the first payment device identifier.

[0107] At step 612, method 600 may include: in response to determining that the first electronic wallet includes the first payment device credential, facilitating, by the payment application, the communication of payment data between the merchant system and the first electronic wallet to initiate processing of the payment transaction, the payment data including at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credential from the first electronic wallet, or any combination thereof.

[0108] In some non-limiting embodiments or aspects, a computer program product for processing transactions using an electronic wallet includes at least one non-transitory computer-readable medium, the non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to perform one of the methods previously described. The at least one processor may include Figure 1-5C, any components shown in (e.g., merchant system 102, user device 106, external transaction system 114, first electronic wallet 116, second electronic wallet 118, electronic payment network 120, acquirer and / or gateway system 122, transaction processing system 124 and / or issuer system 126, etc.).

[0109] See also Figure 7 , showing a diagram of example components of a device 700 according to a non-limiting embodiment or aspect. As an example, the device 700 may correspond to Figure 1-5C 102, user device 106, external transaction system 114, first electronic wallet 116, second electronic wallet 118, electronic payment network 120, acquirer and / or gateway system 122, transaction processing system 124, and / or issuer system 126 shown in . In some non-limiting embodiments or aspects, such systems or devices may include at least one device 700 and / or at least one component of device 700. The number and arrangement of the components shown are provided as examples. In some non-limiting embodiments or aspects, Figure 7 Compared to those shown in , device 700 may include additional components, fewer components, different components, or components arranged in a different manner. Additionally or alternatively, a set of components (e.g., one or more components) of device 700 may perform one or more functions described as being performed by another set of components of device 700.

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

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

[0112] Device 700 can perform one or more processes described herein. Device 700 can perform these processes based on processor 704 executing software instructions stored by computer-readable media such as memory 706 and / or storage component 708. Computer-readable media can include any non-temporary memory device. The memory device includes a memory space located inside a single physical storage device or a memory space spread over multiple physical storage devices. Software instructions can be read from another computer-readable medium or from another device to memory 706 and / or storage component 708 via communication interface 714. When executed, the software instructions stored in memory 706 and / or storage component 708 can cause processor 704 to perform one or more processes described herein. In addition or alternatively, hard-wired circuitry can replace software instructions or be used in combination with software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any specific combination of hardware circuitry and software. The term "programmed or configured" used herein refers to the arrangement of software, hardware circuitry, or any combination thereof on one or more devices.

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

Claims

1. A computer-implemented method comprising: The payment application stores payment device data of a plurality of payment devices including a first payment device and a second payment device, the payment device data including: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which first payment device credentials of the first payment device are stored; and a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which second payment device credentials of the second payment device are stored; The payment application initiates a payment transaction with a merchant system of the merchant; In response to initiating the payment transaction, displaying the first payment device identifier and the second payment device identifier in the payment application and on a user interface of a user device; receiving, by the payment application, user input from a user of the user device, the user input comprising a selection of the first payment device identifier; In response to the user selecting the first payment device identifier, determining, by the payment application based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes the first payment device credential of the first payment device corresponding to the first payment device identifier; and In response to determining that the first electronic wallet includes the first payment device credentials, the payment application facilitates communication of payment data between the merchant system and the first electronic wallet to initiate processing of the payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credentials from the first electronic wallet, or any combination thereof.

2. The computer-implemented method of claim 1 , wherein facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate the payment transaction comprises: retrieving, by the payment application, the transaction data associated with the payment transaction from the merchant system; as well as transmitting, by the payment application, the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, The first electronic wallet initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credentials from the first electronic wallet.

3. The computer-implemented method of claim 1 , wherein facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate the payment transaction comprises: retrieving, by the payment application, the first payment device credential from the first electronic wallet; as well as transmitting, by the payment application, the first payment device credentials from the first electronic wallet to the merchant system, wherein the merchant system initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing the transaction data associated with the payment transaction from the merchant system and the first payment device credentials from the first electronic wallet. 4 . The computer-implemented method of claim 1 , wherein the first electronic wallet is not configured to initiate a payment transaction directly with the merchant system.

5. The computer-implemented method of claim 1 , wherein the payment device data of the first payment device comprises: the first payment device identifier of the first payment device, the first wallet identifier corresponding to the first electronic wallet in which the first payment device credentials of the first payment device are stored, and the second wallet identifier corresponding to the second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, Wherein the selection of the first payment device identifier further comprises selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

6. The computer-implemented method of claim 1 , wherein displaying the first payment device identifier further comprises displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for the payment transaction.

7. The computer-implemented method of claim 1 , further comprising: A software development kit is provided by the payment application to the merchant system and / or the acquirer or gateway system of the merchant system, the software development kit comprising a plurality of application programming interfaces (APIs), the plurality of application programming interfaces being configured to enable the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process the payment transaction: the payment application, the first electronic wallet, the second electronic wallet, an electronic payment network and / or any combination thereof.

8. A system comprising a payment application, the payment application comprising at least one processor, the at least one processor being programmed or configured to: The payment device data of a plurality of payment devices including a first payment device and a second payment device are stored, wherein the payment device data includes: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which first payment device credentials of the first payment device are stored; as well as a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which second payment device credentials of the second payment device are stored; Initiating a payment transaction with the merchant's merchant system; In response to initiating the payment transaction, displaying the first payment device identifier and the second payment device identifier in the payment application and on a user interface of a user device; receiving user input from a user of the user device, the user input comprising a selection of the first payment device identifier; In response to the user selecting the first payment device identifier, determining, based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes the first payment device credential for the first payment device corresponding to the first payment device identifier; as well as In response to determining that the first electronic wallet includes the first payment device credentials, facilitating communication of payment data between the merchant system and the first electronic wallet to initiate processing of the payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credentials from the first electronic wallet, or any combination thereof.

9. The system of claim 8, wherein the process of facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate the payment transaction comprises the payment application including at least one processor, the at least one processor being programmed or configured to: retrieving the transaction data associated with the payment transaction from the merchant system; and transmitting the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, The first electronic wallet initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credentials from the first electronic wallet.

10. The system of claim 8, wherein the process of facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate the payment transaction comprises the payment application including at least one processor, the at least one processor being programmed or configured to: retrieving the first payment device credentials from the first electronic wallet; and transmitting the first payment device credentials from the first electronic wallet to the merchant system, The merchant system initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credentials from the first electronic wallet.

11. The system of claim 8, wherein the first electronic wallet is not configured to initiate a payment transaction directly with the merchant system.

12. The system of claim 8, wherein the payment device data of the first payment device comprises: the first payment device identifier of the first payment device, the first wallet identifier corresponding to the first electronic wallet in which the first payment device credentials of the first payment device are stored, and the second wallet identifier corresponding to the second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, Wherein the selection of the first payment device identifier further comprises selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

13. The system of claim 8, wherein displaying the first payment device identifier further comprises displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for the payment transaction.

14. The system of claim 8, wherein the payment application comprises at least one processor programmed or configured to: A software development kit is provided to the merchant system and / or an acquirer or gateway system of the merchant system, the software development kit comprising a plurality of application programming interfaces (APIs) configured to cause the merchant system and / or the acquirer or gateway system to generate at least one API call to at least one of the following to process the payment transaction: the payment application, the first electronic wallet, the second electronic wallet, an electronic payment network, and / or any combination thereof.

15. A computer program product comprising at least one non-transitory computer-readable medium containing one or more instructions that, when executed by at least one processor of a payment application, cause the at least one processor to: The payment device data of a plurality of payment devices including a first payment device and a second payment device are stored, wherein the payment device data includes: a first payment device identifier of the first payment device and a first wallet identifier corresponding to a first electronic wallet in which first payment device credentials of the first payment device are stored; as well as a second payment device identifier of the second payment device and a second wallet identifier corresponding to a second electronic wallet in which second payment device credentials of the second payment device are stored; Initiating a payment transaction with the merchant's merchant system; In response to initiating the payment transaction, displaying the first payment device identifier and the second payment device identifier in the payment application and on a user interface of a user device; receiving user input from a user of the user device, the user input comprising a selection of the first payment device identifier; In response to the user selecting the first payment device identifier, determining, based on the first wallet identifier corresponding to the first electronic wallet, that the first electronic wallet includes the first payment device credential for the first payment device corresponding to the first payment device identifier; as well as In response to determining that the first electronic wallet includes the first payment device credentials, facilitating communication of payment data between the merchant system and the first electronic wallet to initiate processing of the payment transaction, the payment data comprising at least one of: transaction data associated with the payment transaction from the merchant system, the first payment device credentials from the first electronic wallet, or any combination thereof.

16. The computer program product of claim 15, wherein facilitating the transfer of payment data between the merchant system and the first electronic wallet to initiate the payment transaction comprises the one or more instructions causing the at least one processor to: retrieving the transaction data associated with the payment transaction from the merchant system; and transmitting the transaction data associated with the payment transaction from the merchant system to the first electronic wallet, The first electronic wallet initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credentials from the first electronic wallet.

17. The computer program product of claim 15, wherein facilitating the transfer of payment data between the merchant system and the first e-wallet to initiate the payment transaction comprises the one or more instructions causing the at least one processor to: retrieving the first payment device credentials from the first electronic wallet; and transmitting the first payment device credentials from the first electronic wallet to the merchant system, The merchant system initiates authorization of the payment transaction by transmitting a message to an electronic payment network, the message comprising fields containing: (i) the transaction data associated with the payment transaction from the merchant system, and (ii) the first payment device credentials from the first electronic wallet.

18. The computer program product of claim 15, wherein the first electronic wallet is not configured to initiate a payment transaction directly with the merchant system.

19. The computer program product of claim 15, wherein the payment device data of the first payment device comprises: the first payment device identifier of the first payment device, the first wallet identifier corresponding to the first electronic wallet in which the first payment device credentials of the first payment device are stored, and the second wallet identifier corresponding to the second electronic wallet in which the first payment device credentials of the first payment device are additionally stored, Wherein the selection of the first payment device identifier further comprises selecting the first wallet identifier from selectable options of both the first wallet identifier and the second wallet identifier.

20. The computer program product of claim 15, wherein displaying the first payment device identifier further comprises displaying at least one icon associated with the first payment device identifier, the at least one icon configured to accept at least one available offer if the first payment device identifier is selected for the payment transaction.

Images