WO2024237902A1 - Système, procédé et produit programme d'ordinateur pour transférer des actifs avec un compte virtuel - Google Patents

Système, procédé et produit programme d'ordinateur pour transférer des actifs avec un compte virtuel Download PDF

Info

Publication number
WO2024237902A1
WO2024237902A1 PCT/US2023/022008 US2023022008W WO2024237902A1 WO 2024237902 A1 WO2024237902 A1 WO 2024237902A1 US 2023022008 W US2023022008 W US 2023022008W WO 2024237902 A1 WO2024237902 A1 WO 2024237902A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
account
user
virtual account
processor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2023/022008
Other languages
English (en)
Inventor
Shibabrata Sanjib Kundu
Sandipa Das
Rakesh Kumar BARIK
Varadharajan SESHADRI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Visa International Service Association
Original Assignee
Visa International Service Association
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Visa International Service Association filed Critical Visa International Service Association
Priority to PCT/US2023/022008 priority Critical patent/WO2024237902A1/fr
Publication of WO2024237902A1 publication Critical patent/WO2024237902A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/342—Cards defining paid or billed services or quantities
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes

Definitions

  • the present disclosure relates generally to transferring assets and, in some non-limiting embodiments or aspects, to systems, methods, and computer program products for transferring assets with a virtual account.
  • Electronic wallets use applications installed on electronic devices to allow users to seamlessly transfer assets (e.g., funds) from one electronic wallet to another.
  • assets e.g., funds
  • Some existing applications are not compatible with other applications. For example, where a first type of electronic wallet is not compatible with a second type of electronic wallet, a user of the first type of electronic wallet may not be able to transfer funds to a user of the second type of electronic wallet.
  • some existing applications do not protect users from risks associated with such transfers (e.g., fraud). In some cases, users affected by fraud may have to coordinate with their respective financial institutions (e.g., banks) to settle disputes that may arise.
  • the method may further include communicating, with at least one processor, the virtual account creation request to the payment system associated with the peer- to-peer payment account. In some non-limiting embodiments or aspects, the method may further include receiving, with at least one processor, a virtual account identifier corresponding to the second user in response to the virtual account creation request. In some non-limiting embodiments or aspects, the method may further include transferring, with at least one processor, the payment amount from the first user account associated with the first user to an account corresponding to the virtual account identifier.
  • the method may further include receiving an account identifier associated with the second user and the peer- to-peer payment account; querying the payment system to request data associated with the payment system corresponding to the peer-to-peer payment account based on the account identifier; and receiving the data associated with the payment system corresponding to the peer-to-peer payment account.
  • the method when determining the payment system, may include determining the payment system corresponding to the peer-to-peer payment account based on the data associated with the payment system corresponding to the peer-to-peer payment account.
  • the method may further include receiving a response message from the payment system corresponding to the peer-to-peer payment account, the response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • the method may further include receiving an input from the first user via a graphical user interface of an application associated with the first payment processing network; and generating the request based on the input received from the user.
  • the method may further include generating the virtual account identifier corresponding to the second user based on determining to generate the virtual account identifier to receive the payment amount from the first user account; generating a response to the virtual account creation request, the response comprising the virtual account identifier corresponding to the second user; and communicating the response to the first payment processing network.
  • the virtual account identifier corresponds to at least one of a debit card and a prepaid payment card.
  • the payment system comprises an issuer system corresponding to the peer-to-peer payment account.
  • the system may include at least one processor programmed or configured to receive a request from a first device operated by a first user to transfer a payment amount from a first user account corresponding to the first user and a first payment processing network to a second user having a peer-to-peer payment account.
  • the at least one processor may be further programmed or configured to determine a payment system corresponding to the peer- to-peer payment account.
  • the at least one processor may be further programmed or configured to generate a virtual account creation request based on the peer-to-peer payment account; communicate the virtual account creation request to the payment system associated with the peer-to-peer payment account.
  • the at least one processor may be further programmed or configured to receive a virtual account identifier corresponding to the second user in response to the virtual account creation request.
  • the at least one processor may be further programmed or configured to transfer the payment amount from the first user account associated with the first user to an account corresponding to the virtual account identifier.
  • the at least one processor may be further programmed or configured to receive an account identifier associated with the second user and the peer-to-peer payment account; query the payment system to request data associated with the payment system corresponding to the peer-to-peer payment account based on the account identifier; and receive the data associated with the payment system corresponding to the peer-to-peer payment account.
  • the at least one processor when determining the payment system, may be programmed or configured to determine the payment system corresponding to the peer-to-peer payment account based on the data associated with the payment system corresponding to the peer-to- peer payment account.
  • the at least one processor may be further programmed or configured to receive a response message from the payment system corresponding to the peer-to-peer payment account, the response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • the at least one processor may be further programmed or configured to receive an input from the first user via a graphical user interface of an application associated with the first payment processing network; and generate the request based on the input received from the user.
  • the at least one processor may be further programmed or configured to generate the virtual account identifier corresponding to the second user based on determining to generate the virtual account identifier to receive the payment amount from the first user account; generate a response to the virtual account creation request, the response comprising the virtual account identifier corresponding to the second user; and communicate the response to the first payment processing network.
  • the virtual account identifier corresponds to at least one of a debit card and a prepaid payment card.
  • the payment system comprises an issuer system corresponding to the peer-to-peer payment account.
  • a computer program product comprising at least one non-transitory computer readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to receive a request from a first device operated by a first user to transfer a payment amount from a first user account corresponding to the first user and a first payment processing network to a second user having a peer- to-peer payment account.
  • the one or more instructions may further cause the at least one processor to determine a payment system corresponding to the peer-to-peer payment account.
  • the one or more instructions may further cause the at least one processor to generate a virtual account creation request based on the peer-to- peer payment account; communicate the virtual account creation request to the payment system associated with the peer-to-peer payment account.
  • the one or more instructions may further cause the at least one processor to receive a virtual account identifier corresponding to the second user in response to the virtual account creation request.
  • the one or more instructions may further cause the at least one processor to transfer the payment amount from the first user account associated with the first user to an account corresponding to the virtual account identifier.
  • the one or more instructions may further cause the at least one processor to receive an account identifier associated with the second user and the peer-to-peer payment account; query the payment system to request data associated with the payment system corresponding to the peer-to-peer payment account based on the account identifier; and receive the data associated with the payment system corresponding to the peer-to-peer payment account.
  • the one or more instructions when determining the second system, may cause the at least one processor to determine the second system corresponding to the peer-to-peer payment account based on the data associate with the payment system corresponding to the peer-to- peer payment account.
  • the one or more instructions may further cause the at least one processor to receive a response message from the payment system corresponding to the peer-to-peer payment account, the response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • the one or more instructions may further cause the at least one processor to receive an input from the first user via a graphical user interface of an application associated with the first payment processing network; and generate the request based on the input received from the user.
  • the one or more instructions further cause the at least one processor to: generate the virtual account identifier corresponding to the second user based on determining to generate the virtual account identifier to receive the payment amount from the first user account; generate a response to the virtual account creation request, the response comprising the virtual account identifier corresponding to the second user; and communicate the response to the first payment processing network.
  • the virtual account identifier corresponds to at least one of a debit card and a prepaid payment card.
  • the payment system comprises an issuer system corresponding to the peer-to-peer payment account.
  • Clause 2 The method of clause 1 , further comprising: receiving an account identifier associated with the second user and the peer-to-peer payment account; querying the payment system to request data associated with the payment system corresponding to the peer-to-peer payment account based on the account identifier; and receiving the data associated with the payment system corresponding to the peer- to-peer payment account.
  • Clause 3 The method of clause 1 or clause 2, wherein determining the payment system comprises: determining the payment system corresponding to the peer-to-peer payment account based on the data associated with the payment system corresponding to the peer-to-peer payment account.
  • Clause 4 The method of any of clauses 1 -3, further comprising: receiving a response message from the payment system corresponding to the peer-to-peer payment account, the response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • Clause 5 The method of any of clauses 1 -4, further comprising: receiving an input from the first user via a graphical user interface of an application associated with the first payment processing network; and generating a request based on the input received from the user.
  • Clause 6 The method of any of clauses 1 -5, further comprising: generating the virtual account identifier corresponding to the second user based on determining to generate the virtual account identifier to receive the payment amount from the first user account; generating a response to the virtual account creation request, the response comprising the virtual account identifier corresponding to the second user; and communicating the response to the first payment processing network.
  • Clause 7 The method of any of clauses 1 -6, wherein the virtual account identifier corresponds to at least one of a debit card and a prepaid payment card.
  • Clause 8 The method of any of clauses 1 -7, wherein the payment system comprises an issuer system corresponding to the peer-to-peer payment account.
  • Clause 10 The system of clause 9, wherein the at least one processor is further programmed or configured to: receive an account identifier associated with the second user and the peer-to-peer payment account; query the payment system to request data associated with the payment system corresponding to the peer-to-peer payment account based on the account identifier; and receive the data associated with the payment system corresponding to the peer-to-peer payment account.
  • Clause 11 The system of clause 9 or clause 10, wherein, when determining the payment system, at least one processor is programmed or configured to: determine the payment system corresponding to the peer-to-peer payment account based on the data associated with the payment system corresponding to the peer-to- peer payment account.
  • Clause 12 The system of any of clauses 9-1 1 , wherein the at least one processor is further programmed or configured to: receive a response message from the payment system corresponding to the peer-to-peer payment account, the response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • Clause 13 The system of any of clauses 9-12, wherein the at least one processor is further programmed or configured to: receive an input from the first user via a graphical user interface of an application associated with the first payment processing network; and generate a request based on the input received from the user.
  • Clause 14 The system of any of clauses 9-13, wherein the at least one processor is further programmed or configured to: generate the virtual account identifier corresponding to the second user based on determining to generate the virtual account identifier to receive the payment amount from the first user account; generate a response to the virtual account creation request, the response comprising the virtual account identifier corresponding to the second user; and communicate the response to the first payment processing network.
  • Clause 15 The system of any of clauses 9-14, wherein the virtual account identifier corresponds to at least one of a debit card and a prepaid payment card.
  • Clause 16 The system of any of clauses 9-15, wherein the payment system comprises an issuer system corresponding to the peer-to-peer payment account.
  • Clause 18 The computer program product of clause 17, wherein the one or more instructions further cause the at least one processor to: receive an account identifier associated with the second user and the peer-to-peer payment account; query the payment system to request data associated with the payment system corresponding to the peer-to-peer payment account based on the account identifier; and receive the data associated with the payment system corresponding to the peer- to-peer payment account.
  • Clause 20 The computer program product of any of clauses 17-19, wherein the one or more instructions further cause the at least one processor to: receive a response message from the payment system corresponding to the peer-to-peer payment account, the response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • Clause 21 The computer program product of any of clauses 17-20, wherein the one or more instructions further cause the at least one processor to: receive an input from the first user via a graphical user interface of an application associated with the first payment processing network; and generate a request based on the input received from the user.
  • Clause 23 The computer program product of any of clauses 17-22, wherein the virtual account identifier corresponds to at least one of a debit card and a prepaid payment card.
  • Clause 24 The computer program product of any of clauses 17-23, wherein the payment system comprises an issuer system corresponding to the peer-to-peer payment account.
  • FIG. 1 is a diagram of a non-limiting embodiment or aspect of an environment in which systems, devices, products, and/or methods, described herein, may be implemented according to the principles of the present disclosure
  • FIG. 2 is a schematic diagram and flow chart of a non-limiting embodiments or aspects of a system for transferring assets with a virtual account according to some non-limiting embodiments or aspects;
  • FIG. 3 is a diagram of a non-limiting embodiment or aspect of components of one or more devices of FIG. 1 .
  • the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based at least partially on” unless explicitly stated otherwise. The phrase “based on” may also mean “in response to” where appropriate.
  • the terms “communication” and “communicate” may refer to the reception, receipt, transmission, transfer, provision, and/or the like of information (e.g., data, signals, messages, instructions, commands, and/or the like).
  • one unit e.g., a device, a system, a component of a device or system, combinations thereof, and/or the like
  • communicate may refer to the reception, receipt, transmission, transfer, provision, and/or the like of information (e.g., data, signals, messages, instructions, commands, and/or the like).
  • one unit e.g., a device, a system, a component of a device or system, combinations thereof, and/or the like
  • This may refer to a direct or indirect connection that is wired and/or wireless in nature.
  • two units may be in communication with each other even though the information transmitted may be modified, processed, relayed, and/or routed between the first and second unit.
  • a first unit may be in communication with a second unit even though the first unit passively receives information and does not actively transmit information to the second unit.
  • a first unit may be in communication with a second unit if at least one intermediary unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and transmits the processed information to the second unit.
  • a message may refer to a network packet (e.g., a data packet and/or the like) that includes data.
  • issuer may refer to one or more entities that provide accounts to individuals (e.g., users, customers, and/or the like) for conducting payment transactions, such as credit payment transactions and/or debit payment transactions.
  • issuer institution may provide an account identifier, such as a primary account number (PAN), to a customer that uniquely identifies one or more accounts associated with that customer.
  • PAN primary account number
  • issuer may be associated with a Bank Identification Number (BIN) that uniquely identifies the issuer institution.
  • BIN Bank Identification Number
  • transaction service provider may refer to an entity that receives transaction authorization requests from merchants or other entities and provides guarantees of payment, in some cases through an agreement between the transaction service provider and an issuer institution.
  • a transaction service provider may include a payment network such as Visa®, MasterCard®, American Express®, or any other entity that processes transactions.
  • transaction service provider system may refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction service provider system executing one or more software applications.
  • a transaction service provider system 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.
  • the term “merchant” may refer to one or more entities (e.g., operators of retail businesses) that provide goods and/or services, and/or access to goods and/or services, to a user (e.g., a customer, a consumer, and/or the like) based on a transaction, such as a payment transaction.
  • the term “merchant system” may refer to one or more computer systems operated by or on behalf of a merchant, such as a server executing one or more software applications.
  • the term “product” may refer to one or more goods and/or services offered by a merchant.
  • the term “acquirer” may refer to an entity licensed by the transaction service provider and approved by the transaction service provider to originate transactions (e.g., payment transactions) involving a payment device associated with the transaction service provider.
  • the term “acquirer system” may also refer to one or more computer systems, computer devices, and/or the like operated by or on behalf of an acquirer.
  • the transactions the acquirer may originate may include payment transactions (e.g., purchases, original credit transactions (OCTs), account funding transactions (AFTs), and/or the like).
  • the acquirer may be authorized by the transaction service provider to assign merchant or service providers to originate transactions involving a payment device associated with the transaction service provider.
  • the acquirer may contract with payment facilitators to enable the payment facilitators to sponsor merchants.
  • the acquirer may monitor compliance of the payment facilitators in accordance with regulations of the transaction service provider.
  • the acquirer may conduct due diligence of the payment facilitators and ensure proper due diligence occurs before signing a sponsored merchant.
  • the acquirer may be liable for all transaction service provider programs that the acquirer operates or sponsors.
  • the acquirer may be responsible for the acts of the acquirer’s payment facilitators, merchants that are sponsored by the acquirer’s payment facilitators, and/or the like.
  • an acquirer may be a financial institution, such as a bank.
  • the term “payment gateway” may refer to an entity and/or a payment processing system operated by or on behalf of such an entity (e.g., a merchant service provider, a payment service provider, a payment facilitator, a payment facilitator that contracts with an acquirer, a payment aggregator, and/or the like), which provides payment services (e.g., transaction service provider payment services, payment processing services, and/or the like) to one or more merchants.
  • the payment services may be associated with the use of portable financial devices managed by a transaction service provider.
  • the term “payment gateway system” may refer to one or more computer systems, computer devices, servers, groups of servers, and/or the like operated by or on behalf of a payment gateway.
  • client device may refer to one or more computing devices, such as processors, storage devices, and/or similar computer components, that access a service made available by a server.
  • a client device may include a computing device configured to communicate with one or more networks and/or facilitate transactions such as, but not limited to, one or more desktop computers, one or more portable computers (e.g., tablet computers), one or more mobile devices (e.g., cellular phones, smartphones, personal digital assistant, wearable devices, such as watches, glasses, lenses, and/or clothing, and/or the like), and/or other like devices.
  • client may also refer to an entity that owns, utilizes, and/or operates a client device for facilitating transactions with another entity.
  • server may refer to one or more computing devices, such as processors, storage devices, and/or similar computer components that communicate with client devices and/or other computing devices over a network, such as the Internet or private networks and, in some examples, facilitate communication among other servers and/or client devices.
  • a network such as the Internet or private networks and, in some examples, facilitate communication among other servers and/or client devices.
  • 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 like components.
  • a server or “a processor,” as used herein, may refer to a previously-recited server and/or processor that is recited as performing a previous step or function, a different server and/or processor, and/or a combination of servers and/or processors.
  • a first server and/or a first processor that is recited as performing a first step or function may refer to the same or different server and/or a processor recited as performing a second step or function.
  • Non-limiting embodiments or aspects of the present disclosure are directed to systems, methods, and computer program products for transferring assets with a virtual account.
  • the non-limiting embodiments described in the present disclosure enable users to transfer assets to and/or from a virtual account.
  • a first user may transfer funds to a second user using a virtual account created ad hoc in correspondence with a peer-to-peer (“P2P”) payment account, such as Unified Payments Interface (“UPI”) or other P2P payment platforms (e.g., PayPal, Venmo ®, and/or the like).
  • P2P peer-to-peer
  • UPI Unified Payments Interface
  • PayPal PayPal
  • Venmo ® Venmo ®
  • Non-limiting embodiments disrupt the typical flow of events that occur in response to a payment transfer request by effectively bridging the gap between two different and/or separate payment systems and allowing users of the payment systems to engage in P2P transactions without the need to have a common payment service provider.
  • This provides a seamless payment process to the payer, who does not have to perform additional steps and/or use different applications and/or services to make a payment to a recipient that does not have a compatible payment account.
  • the reduction of steps needed to make such a payment also reduces the number of parties and, thus, reduces the amount of computing resources and communications needed to make such a payment.
  • FIG. 1 shown is a diagram of an example environment 100 in which devices, systems, and/or methods, described herein, may be implemented.
  • environment 100 includes transaction service provider system 102, issuer system 104, payment system 106, and user device 108.
  • Transaction service provider system 102, issuer system 104, payment system 106, and/or user device 108 may interconnect (e.g., establish a connection to communicate) via wired connections, wireless connections, or a combination of wired and wireless connections.
  • transaction service provider system 102 may be associated with a transaction service provider system, as described herein. In some non-limiting embodiments or aspects, transaction service provider system 102 may be in communication with a data storage device, which may be local or remote to transaction service provider system 102. In some non-limiting embodiments or aspects, transaction service provider system 102 may be capable of receiving information from, storing information in, transmitting information to, and/or searching information stored in the data storage device.
  • Issuer system 104 may include one or more devices configured to communicate with transaction service provider system 102.
  • issuer system 104 may include a server, a group of servers, and/or other like devices.
  • issuer system 104 may include a processor and/or a memory, as described herein.
  • issuer system 104 may include one or more software instructions (e.g., one or more software applications) executing on a server (e.g., a single server), a group of servers, a computing device (e.g., a single computing device), a group of computing devices, and/or other like devices.
  • issuer system 104 may be associated with a financial institution (e.g., a bank), as described herein. In some non-limiting embodiments or aspects, issuer system 104 may be in communication with a data storage device, which may be local or remote to issuer system 104. In some non-limiting embodiments or aspects, issuer system 104 may be capable of receiving information from, storing information in, transmitting information to, and/or searching information stored in the data storage device.
  • Payment system 106 may include one or more devices configured to communicate with transaction service provider system 102.
  • payment system 106 may include a server, a group of servers, and/or other like devices.
  • payment system 106 may include a processor and/or a memory, as described herein.
  • payment system 106 may include one or more software instructions (e.g., one or more software applications) executing on a server (e.g., a single server), a group of servers, a computing device (e.g., a single computing device), a group of computing devices, and/or other like devices.
  • payment system 106 may be associated with a transaction service provider, a P2P network, and/or a financial institution (e.g., a bank), as described herein.
  • payment system 106 may include a P2P network (e.g., UPI, Venmo®, etc.) and/or a second issuer system.
  • P2P network e.g., UPI, Venmo®, etc.
  • payment system 106 may refer to a P2P payment network and one or more financial institutions (e.g., associated with issuer systems) that users of the P2P payment network have linked to their P2P accounts (e.g., a linked account with an issuer for depositing and/or transferring).
  • the payment system 106 may be separate systems and entities and not a single system as shown for illustration purposes in FIG. 1 .
  • payment system 106 may be in communication with a data storage device, which may be local or remote to payment system 106.
  • payment system 106 may be capable of receiving information from, storing information in, transmitting information to, and/or searching information stored in the data storage device.
  • User device 108 may include a computing device configured to communicate with transaction service provider system 102.
  • user device 108 may include a computing device, such as a desktop computer, a portable computer (e.g., tablet computer, a laptop computer, and/or the like), a mobile device (e.g., a cellular phone, a smartphone, a personal digital assistant, a wearable device, and/or the like), and/or other like devices.
  • user device 108 may be associated with a user (e.g., an individual operating user device 108).
  • transaction service provider system 102 may receive a request from user device 108.
  • transaction service provider system 102 may receive a request from user device 108 operated by a first user to transfer a payment amount from a first user account corresponding to the first user and a first payment processing network to a second user having a P2P payment account.
  • user device 108 may receive an input from the first user via a graphical user interface (GUI) of an application being executed on user device 108.
  • GUI graphical user interface
  • the GUI of the application may display data associated with the input from the user via a screen of user device 108.
  • the input may also be spoken, audio input, gesture input, and/or other like forms of input with or without a GUI.
  • user device 108 and/or the application associated with the first payment processing network running on user device 108 may generate the request based on the input received from the user.
  • user device 108 and/or the application associated with the first payment processing network running on user device 108 may communicate the request to transaction service provider system 102.
  • transaction service provider system 102 may receive an account identifier (e.g., a unique handle) associated with the second user and the P2P payment account.
  • account identifier e.g., a unique handle
  • transaction service provider system 102 may receive an account identifier comprising a unique identifier of the second user and/or a unique identifier of a financial institution (e.g., xxxx@ffff, where xxxx is the unique identifier of the second user and where ffff is the unique identifier of the financial institution) associated with the second user and the P2P payment account from payment system 106 and/or user device 108.
  • transaction service provider system 102 may determine a payment system corresponding to the P2P payment account. In some non-limiting embodiments or aspects, when determining the payment system corresponding to the P2P payment account, transaction service provider system 102 may query the payment system 106 (e.g., the P2P payment network and/or the second issuer) to request data associated with the payment system corresponding to the P2P payment account.
  • the payment system 106 e.g., the P2P payment network and/or the second issuer
  • transaction service provider system 102 may query the P2P payment network and/or the second issuer to request data (e.g., an identifier of an issuer such as a code and/or a BIN) associated with the P2P network and/or the second issuer corresponding to the P2P payment account based on the account identifier.
  • transaction service provider system 102 may receive the data (e.g., the code and/or the BIN) associated with the payment system 106 corresponding to the P2P payment account from the P2P payment network and/or the second issuer.
  • transaction service provider system 102 may determine the payment system corresponding to the P2P payment account based on receiving the account identifier and/or data associated with the payment system corresponding to the P2P payment account.
  • transaction service provider system 102 may generate a virtual account creation request based on the P2P payment account (e.g., data associate with the P2P payment account). For example, transaction service provider system 102 may generate the virtual account creation request automatically in response to receiving the data associated with the P2P payment account and by including the data (e.g., an identifier of an issuer such as the code and/or the BIN) or a portion thereof in a virtual account creation request message.
  • the data e.g., an identifier of an issuer such as the code and/or the BIN
  • transaction service provider system 102 may communicate (e.g., transmit) the virtual account creation request to the payment system associated with the P2P payment account.
  • transaction service provider system 102 may communicate the virtual account creation request to the P2P payment network and/or the second issuer.
  • payment system 106 may determine whether or not to generate a virtual account identifier to receive the payment amount from the first user account.
  • the P2P payment network and/or the second issuer may determine to generate the virtual account identifier to receive the payment amount from the first user account based on receiving the virtual account creation request from transaction service provider system 102.
  • the second issuer may automatically generate a response message comprising an indication that the payment system determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • the P2P payment network and/or the second issuer may communicate the response message to transaction service provider system 102.
  • transaction service provider system 102 may receive the response message.
  • transaction service provider system 102 may receive the response message from the P2P payment network and/or the second issuer, the response message comprising an indication that the P2P payment network and/or the second issuer has determined to generate the virtual account identifier.
  • payment system 106 may generate the virtual account identifier corresponding to the second user.
  • the second issuer may generate the virtual account identifier corresponding to the user (e.g., automatically) based on receiving the virtual account creation request from transaction service provider system 102.
  • the response message may include the virtual account identifier corresponding to the second user.
  • the P2P payment network and/or the second issuer may generate a second response message comprising the virtual account identifier corresponding to the second user and communicate the second response message to transaction service provider system 102.
  • the virtual account identifier corresponds to at least one of a debit card and/or a prepaid payment card.
  • transaction service provider system 102 may receive a virtual account identifier from the P2P payment network and/or second issuer in response to communicating the virtual account creation request.
  • transaction service provider system 102 may transfer the payment amount from the first user account associated with the first user to an account corresponding to the virtual account identifier.
  • FIG. 1 The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. There may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as multiple, distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.
  • a set of devices e.g., one or more devices
  • transaction service provider system 202 may be the same as, similar to, and/or part of transaction service provider system 102.
  • first issuer 204 and/or second issuer 210 may be the same as, similar to, and/or part of issuer system 104.
  • P2P network 206 may be the same as, similar to, and/or part of payment system 106.
  • first user device 208a and/or second user device 208b may be the same as, similar to, and/or part of user device 108.
  • second issuer 210 may be the same as, similar to, and/or part of payment system 106.
  • database 214 may include a data storage device, as described herein.
  • application 216 may be a payment application accessible by a user device, including one or more server-side software applications hosted by transaction service provider system 102 and/or payment system 106, one or more client-side applications (e.g., mobile applications) executable by a user device, such as first user device 208a and/or second user device 208b, that communicates with a remote server, and/or the like.
  • client-side applications e.g., mobile applications
  • application 216 may be accessible by a user device through a browser, such as a web-based application.
  • first user device 208a and second user device 208b may be computing devices operated by a first user and a second user, respectively.
  • a first user account may correspond to the first user (operating first user device 208a) and/or a first payment processing network.
  • a P2P payment account may correspond to the second user (operating second user device 208b).
  • first user device 208a may correspond to the first user (e.g., a sender/payer) and/or second user device 208b may correspond to the second user (e.g., a receiver/payee).
  • first user device 208a may communicate with the second user and/or second user device 208b.
  • second user device 208b may communicate data comprising at least an account identifier to first user device 208a upon request, in response to an initial message, or the like.
  • the account identifier may include data associated with second user device 208b, the second user, and/or the P2P account.
  • the account identifier may include an identification code associated with the P2P payment account (e.g., a UPI identification code) and/or a handle associated with the P2P payment account (e.g., xxxxxx@ffff, where xxxxxx is a unique identification associated with the second user and ffff is a unique identification associated with second issuer 210).
  • an identification code associated with the P2P payment account e.g., a UPI identification code
  • a handle associated with the P2P payment account e.g., xxxxxx@ffff, where xxxxxx is a unique identification associated with the second user and ffff is a unique identification associated with second issuer 210.
  • first user device 208a may receive the data comprising the account identifier from the second user via second user device 208b and/or any other communication means (e.g., scanning a QR code or other indicia, Bluetooth® communication, near field communication, and/or the like).
  • first user device 208a may communicate with application 216. For example, upon receiving the account identifier from second user device 208b, first user device 208a may automatically communicate the account identifier to application 216.
  • first user device 208a may include application 216.
  • application 216 may be a software application installed and/or running on first user device 208a and/or second user device 208b.
  • application 216 may be executed on first user device 208a.
  • application 216 may be accessible by a webpage via first user device 208a.
  • application 216 may provide users with the option to perform money transfers. For example, when installed on first user device 208a, application 216 may provide the first user with the option to transfer a payment amount from the first account associated with the first user to the P2P payment account associated with the second user.
  • first user device 208a and/or application 216 may store data associated with the first user.
  • first user device 208a and/or application 216 may store data associated with the first user account corresponding to the first user and the first payment processing network, such as a PAN or other account identifier (e.g., a debit card number, a prepaid payment card number, a payment token, and/or the like).
  • a PAN or other account identifier e.g., a debit card number, a prepaid payment card number, a payment token, and/or the like.
  • step S3 application 216 may communicate with transaction service provider system 202.
  • application 216 may generate and communicate a request to transfer a payment amount from the first user account corresponding to the first user and a first payment processing network to the second user having the P2P payment account.
  • the request to transfer the payment amount from the first user account corresponding to the first user and the first payment processing network to the second user having the P2P payment account may be a first request.
  • the first request may include data including at least the account identifier.
  • first user device 208a may communicate the first request to transaction service provider system 202.
  • transaction service provider system 202 may receive the first request from first user device 208a and/or application 216.
  • transaction service provider system 202 may communicate with P2P payment network 206. For example, in response to receiving the first request, transaction service provider system 202 may generate and send a second request including a message configured to cause P2P payment network 206 to provide data associated with the payment system corresponding to the P2P payment account. In some non-limiting embodiments or aspects, the second request may include at least the account identifier.
  • transaction service provider system 202 may communicate with database 214. For example, the transaction service provider system 202 may query database 214 and/or extract data from database 214 to determine the payment system corresponding to the P2P payment account.
  • transaction service provider system 202 may determine the payment system corresponding to the P2P payment account. For example, in response to receiving the second request, transaction service provider system 202 may determine that the payment system corresponding to the P2P payment account is the same as and/or part of second issuer 210 based on the account identifier.
  • transaction service provider system 202 may query P2P payment network 206 to request data associated with the payment system corresponding to the P2P payment account based on receiving the account identifier. For example, the querying may be performed automatically in response to receiving the account identifier. In some non-limiting embodiments or aspects, in response to the querying, transaction service provider system 202 may receive the data (e.g., identifier code, a payment service provider code, and/or BIN) associated with the payment system corresponding to the P2P payment account from P2P payment network 206.
  • data e.g., identifier code, a payment service provider code, and/or BIN
  • the data associated with the payment system corresponding to the P2P payment account may comprise a unique identification code associated with a financial institution.
  • transaction service provider system 202 may determine that the payment system corresponding to the P2P payment account is second issuer 210 based on receiving a unique identification code associated with second issuer 210.
  • transaction service provider system 202 may generate a virtual account creation request based on determining the payment system corresponding to the P2P payment account.
  • the virtual account creation request may include, for example, a message with data associated with the payment system and/or the unique identification code associated with second issuer 210.
  • the virtual account creation request may be a third request.
  • transaction service provider system 202 may communicate with second issuer 210.
  • transaction service provider system 202 may communicate the virtual account creation request to the payment system associated with the P2P payment account (e.g., the second issuer 210).
  • the virtual account creation request may comprise a message configured to cause the second issuer 210, or other payment system, to create and/or provide a virtual account identifier number associated with a virtual account to receive the payment amount from the first user account.
  • second issuer 210 may communicate with second user device 208b.
  • second issuer 210 may generate and send a message to user device 208b, the message requesting approval for the creation of the virtual account.
  • the second user may receive the message via second user device 208b from second issuer 210 and determine whether to approve or deny the creation of the virtual account.
  • determining to approve the creation of the virtual account may be automatic and/or based on a previous approval for the creation of a virtual account and/or a user preference (e.g., a preference set by the second user).
  • second user device 208b in response to determining to approve the creation of the virtual account, may communicate a response message to second issuer 210 indicating that the second user approves the creation of the virtual account to receive the payment amount from the first user account.
  • second issuer 210 may automatically determine whether to approve or deny the creation of the virtual account based on performing one or more fraud determinations, risk determinations, and/or the like, based on the transaction data available to it and/or based on a user preference.
  • transaction service provider system 202 may receive a response to the virtual account creation request from second issuer 210.
  • the response may include a message comprising an indication that the second user and/or second issuer 210 has approved the creation of the virtual account.
  • the response may include data indicating that the second issuer 210 has determined to generate the virtual account identifier to receive the payment amount from the first user account.
  • second issuer 210 may generate a virtual account identifier corresponding to the second user, for example, based on determining to generate the virtual account identifier to receive the payment amount from the first user account.
  • the virtual account identifier may be automatically generated in response to determining to generate the virtual account identifier.
  • second issuer 210 may generate a response to the virtual account creation request comprising the virtual account identifier corresponding to the second user and/or communicate the response to transaction service provider system 202.
  • the virtual account identifier may correspond to at least one of a debit card and/or a prepaid payment card.
  • transaction service provider system 202 may communicate, to second issuer 210, a request to transfer the payment amount from the first user account to the virtual account.
  • the request to transfer the payment amount from the first user account to the virtual account may be a fourth request.
  • the fourth request may include data including at least the virtual account identifier.
  • the payment amount may be transferred from the first user account associated with the first user to the account corresponding to the virtual account identifier.
  • first user device 208a may communicate with first issuer 204.
  • user device 208a may send, to first issuer 204, the payment amount from the first user account corresponding to the first user and the first payment processing network.
  • the payment amount may be debited from the first user account corresponding to the first user and the first payment processing network and/or credited to an account associated with first issuer 204.
  • First issuer 204 may be a financial institution (e.g., bank) associated with the first user.
  • first issuer 204 may communicate with second issuer 210.
  • first issuer 204 may send the payment amount to second issuer 210.
  • the payment amount may be debited from an account associated with first issuer 204 and/or credited to an account associated with second issuer 210 (e.g., the account corresponding to the virtual account identifier).
  • the payment amount may be credited to the virtual account.
  • second user device 208b may receive a message and/or notification from second issuer 210. For example, in response to the payment amount being credited to the virtual account, second user device 208b may receive a message indicating that the payment amount has been credited to the virtual account.
  • the message indicating the payment amount has been credited to the virtual account may include data including the virtual account identifier and/or the payment amount.
  • second issuer 210 may send an approval request to transaction service provider system 202.
  • transaction service provider system 202 may provide an approval response to application 216, indicating that the payment amount from the first user account associated with the first user to the account corresponding to the virtual account identifier have been approved and/or the payment amount has been transferred successfully.
  • FIG. 2 The number and arrangement of devices, networks, and/or steps shown in FIG. 2 are provided as an example. There may be additional devices, networks, and/or steps fewer devices, networks, and/or steps, different devices, networks, and/or steps, or differently arranged devices, networks, and/or steps than those shown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may be implemented within a single device, or a single device shown in FIG. 2 may be implemented as multiple, distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) of system 200 may perform one or more functions described as being performed by another set of devices of system 200.
  • a set of devices e.g., one or more devices
  • Device 300 may correspond to transaction service provider system 102 (e.g., one or more devices of transaction service provider system 102), issuer system 104 (e.g., one or more devices of issuer system 104), payment system 106 (e.g., one or more devices of payment system 106), and/or user device 108.
  • transaction service provider system 102, issuer system 104, payment system 106, and/or user device 108 may include at least one device 300 and/or at least one component of device 300.
  • device 300 may include bus 302, processor 304, memory 306, storage component 308, input component 310, output component 312, and communication interface 314.
  • Bus 302 may include a component that permits communication among the components of device 300.
  • processor 304 may be implemented in hardware, software, or a combination of hardware and software.
  • processor 304 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and/or any processing component (e.g., a field-programmable gate array (FPGA), an applicationspecific integrated circuit (ASIC), etc.) that can be programmed to perform a function.
  • Memory 306 may include random access memory (RAM), read-only memory (ROM), and/or another type of dynamic or static storage memory (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and/or instructions for use by processor 304.
  • RAM random access memory
  • ROM read-only memory
  • static storage memory e.g., flash memory, magnetic memory, optical memory, etc.
  • Storage component 308 may store information and/or software related to the operation and use of device 300.
  • storage component 308 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive.
  • Input component 310 may include a component that permits device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally or alternatively, input component 310 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 312 may include a component that provides output information from device 300 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).
  • GPS global positioning system
  • LEDs light-emitting diodes
  • Communication interface 314 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections.
  • Communication interface 314 may permit device 300 to receive information from another device and/or provide information to another device.
  • communication interface 314 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi® interface, a cellular network interface, and/or the like.
  • Device 300 may perform one or more processes described herein. Device 300 may perform these processes based on processor 304 executing software instructions stored by a computer-readable medium, such as memory 306 and/or storage component 308.
  • a computer-readable medium e.g., a non-transitory computer-readable medium
  • a non-transitory memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices.
  • Software instructions may be read into memory 306 and/or storage component 308 from another computer-readable medium or from another device via communication interface 314.
  • software instructions stored in memory 306 and/or storage component 308 may cause processor 304 to perform one or more processes described herein.
  • hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein.
  • embodiments or aspects described herein are not limited to any specific combination of hardware circuitry and software.
  • device 300 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 3. Additionally or alternatively, a set of components (e.g., one or more components) of device 300 may perform one or more functions described as being performed by another set of components of device 300.
  • a set of components e.g., one or more components

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne des systèmes, des procédés et des produits programmes d'ordinateur pour transférer des actifs avec un compte virtuel. Le système peut recevoir une demande provenant d'un premier dispositif exploité par un premier utilisateur, la demande tendant à transférer un montant de paiement d'un premier compte d'utilisateur correspondant au premier utilisateur et d'un premier réseau de traitement de paiement à un second utilisateur ayant un compte de paiement poste à poste (P2P), et déterminer le système de paiement qui correspond au compte de paiement P2P. Une demande de création de compte virtuel peut être générée sur la base du compte de paiement P2P et communiquée au système de paiement associé au compte de paiement P2P. Le système peut recevoir un identifiant de compte virtuel correspondant au second utilisateur en réponse à la demande de création de compte virtuel et transférer le montant de paiement depuis le premier compte d'utilisateur associé au premier utilisateur vers un compte correspondant à l'identifiant de compte virtuel.
PCT/US2023/022008 2023-05-12 2023-05-12 Système, procédé et produit programme d'ordinateur pour transférer des actifs avec un compte virtuel Ceased WO2024237902A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2023/022008 WO2024237902A1 (fr) 2023-05-12 2023-05-12 Système, procédé et produit programme d'ordinateur pour transférer des actifs avec un compte virtuel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2023/022008 WO2024237902A1 (fr) 2023-05-12 2023-05-12 Système, procédé et produit programme d'ordinateur pour transférer des actifs avec un compte virtuel

Publications (1)

Publication Number Publication Date
WO2024237902A1 true WO2024237902A1 (fr) 2024-11-21

Family

ID=93519371

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/022008 Ceased WO2024237902A1 (fr) 2023-05-12 2023-05-12 Système, procédé et produit programme d'ordinateur pour transférer des actifs avec un compte virtuel

Country Status (1)

Country Link
WO (1) WO2024237902A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080040261A1 (en) * 2006-04-24 2008-02-14 Robert Nix Systems and methods for implementing financial transactions
US20120123924A1 (en) * 2010-10-20 2012-05-17 Mark Rose Virtual currency configuration apparatuses, methods and systems
US20120209749A1 (en) * 2011-02-16 2012-08-16 Ayman Hammad Snap mobile payment apparatuses, methods and systems
US20150269539A1 (en) * 2014-03-18 2015-09-24 nTrust Technology Solutions Corp. Virtual currency system
US20150278799A1 (en) * 2014-03-27 2015-10-01 Karthikeyan Palanisamy System incorporating wireless share process
US20160162882A1 (en) * 2014-12-08 2016-06-09 Guy LaMonte McClung, III Digital money choice and eWallet selection

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080040261A1 (en) * 2006-04-24 2008-02-14 Robert Nix Systems and methods for implementing financial transactions
US20120123924A1 (en) * 2010-10-20 2012-05-17 Mark Rose Virtual currency configuration apparatuses, methods and systems
US20120209749A1 (en) * 2011-02-16 2012-08-16 Ayman Hammad Snap mobile payment apparatuses, methods and systems
US20150269539A1 (en) * 2014-03-18 2015-09-24 nTrust Technology Solutions Corp. Virtual currency system
US20150278799A1 (en) * 2014-03-27 2015-10-01 Karthikeyan Palanisamy System incorporating wireless share process
US20160162882A1 (en) * 2014-12-08 2016-06-09 Guy LaMonte McClung, III Digital money choice and eWallet selection

Similar Documents

Publication Publication Date Title
US11823138B2 (en) System, method, and computer program product for conducting a payment transaction involving payment on delivery
US12231402B2 (en) Method, system, and computer program product for preventing transmission of malicious data
US12008585B2 (en) System, method, and computer program product for real-time payment gateway event monitoring
US11144919B2 (en) System, method, and computer program product for guaranteeing a payment authorization response
US20220156742A1 (en) System and method for authorizing a transaction
US11875348B2 (en) System, method, and computer program product to ensure data integrity for conducting a payment transaction
US20250112922A1 (en) System, Method, and Computer Program Product for Controlling Access to Online Actions
US20220245516A1 (en) Method, System, and Computer Program Product for Multi-Task Learning in Deep Neural Networks
US20240119460A1 (en) System, Method, and Computer Program Product for Real-Time Account Level Rule Exclusion for Real-Time Payments
US20240273521A1 (en) Method, System, and Computer Program Product for Generating a Single-Use Digital Asset
US12555104B2 (en) Method, system, and computer program product for dynamically ensuring SDK integrity
WO2019040047A1 (fr) Système, procédé et produit-programme informatique permettant d'effectuer une transaction de paiement
AU2022282203A1 (en) System, method, and computer program product for an account-to-account transaction network
US20250014011A1 (en) Method, System, and Computer Program Product for Controlling Issuer Transactions
US20250131404A1 (en) Method, System, and Computer Program Product for Processing a Group Payment Credential
WO2024025859A1 (fr) Système, procédé et produit programme informatique pour couche de communication pour la gestion de services en ligne
US11636490B2 (en) System, method, and computer program product for linking accounts across systems
US12051068B2 (en) System, method, and computer program product for remote authorization of payment transactions
US20240144258A1 (en) System, Method, and Computer Program Product for Secure Client Device and Consumer Authentication
Witkowski et al. Method, System, and Computer program product for transaction authentication
US20250029090A1 (en) System, Method, and Computer Program Product for Real-Time Transactions
WO2024138030A1 (fr) Système, procédé et produit programme informatique pour déterminer une valeur d'échange dynamique sur la base d'un réseau de chaîne de blocs

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23937684

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202517124833

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202517124833

Country of ref document: IN