Establishing the use of digital accounts in digital wallets during cross-platform common data processing.

Abstract

A system and method are provided for establishing the use of digital accounts in digital wallets during common data processing across platforms. Users may engage in transactions with other users, such as purchasing goods, services, or other commodities, and merchants may engage in transactions using digital wallets through software applications. Online transaction processors may provide digital accounts for payment processing that can provide loan and installment payment services. If a payment account is not compatible with the protocols and procedures for use in a digital wallet, a specific identifier may be provided, and proxy data may be generated between the transaction processor's system and the digital wallet's system through call and data exchange. The identifier may mimic data used by the digital wallet and may also enable tokenization and processing with token service providers in the payment network.

Description

Technical Field

[0001] This application generally relates to the common use between platforms of digital wallets having separate accounts, and more particularly to establishing and using digital accounts in digital wallets provided by separate online platforms.

Background Art

[0002] Users may utilize online transaction processors to process payments between various entities through device applications and digital accounts. Furthermore, these online transaction processors may also offer payment options, loans, and / or access to in-person transaction processing and use at merchant locations. When offering or providing payment options and installment loan plans, users may receive credit limits and / or purchase limits, and / or access credit balances, real funds, or virtual funds linked to digital accounts. Such balances may be used through digital accounts provided to the user by the online transaction processor. Furthermore, merchants may utilize in-person payment terminals, such as point-of-sale (POS) devices, which may include components and modules for local wireless data exchange and transaction processing. However, digital wallets and mobile software applications may have specific requirements, configurations, and / or specifications regarding data transfer and interaction with portable devices for use with these terminals, and they may be incompatible with certain data processing schemes. This may apply if certain transactions and other data processing requests require real-time analysis at the time of request processing with merchant equipment. Furthermore, due to threats from cyberattacks, phishing schemes, and malware that could endanger user accounts, users and online transaction processors may want to apply pre-configured and / or real-time constraints to account usage through separate platforms, which may require specific integration of data processing operations, API calls and responses, and data formats for appropriate data handling and processing. Therefore, it is desirable for online transaction processors to provide common cross-platform account integration and usage operations with external digital wallet providers. [Brief explanation of the drawing]

[0003] [Figure 1] This is a block diagram of a networked system suitable for carrying out the processing described herein, according to the embodiments. [Figure 2A] This is an exemplary diagram for establishing and using a digital account for near-field wireless data processing with merchant equipment via a digital wallet provided by a separate platform, according to one embodiment. [Figure 2B] This is an exemplary diagram for establishing and using a digital account for near-field wireless data processing with merchant equipment via a digital wallet provided by a separate platform, according to one embodiment. [Figure 3A] This is an exemplary diagram of data processing calls and operations between an online transaction processor system and a digital wallet provider system when establishing and integrating a digital account into a digital wallet, according to an embodiment. [Figure 3B] This is an exemplary diagram of data processing calls and operations between an online transaction processor system and a digital wallet provider system when establishing and integrating a digital account into a digital wallet, according to an embodiment. [Figure 4] This is a set of exemplary user interfaces for a portable device application when registering a digital account with an online transaction processor for use via a digital wallet on a separate digital wallet platform, according to the embodiment. [Figure 5A] This is an exemplary process flow diagram for establishing the use of digital accounts in a digital wallet during cross-platform common data processing, according to an embodiment. [Figure 5B] This is an exemplary processing flowchart for cross-platform common use of digital accounts in separate digital wallets during near-field data processing, according to an embodiment. [Figure 6] This is a block diagram of a computer system suitable for implementing one or more components of Figure 1, according to an embodiment.

[0004] Embodiments of the Disclosure and their advantages are best understood by referring to the detailed description below. The same reference numerals are used to refer to the same elements illustrated in one or more figures, and the illustrations are for illustrative purposes only and not to limit the embodiments of the Disclosure. [Modes for carrying out the invention]

[0005] Methods are provided for establishing the use of digital accounts in digital wallets during cross-platform common data processing, as well as the cross-platform common use of digital accounts in separate digital wallets during data processing. Systems suitable for implementing the methods of this disclosure are also provided.

[0006] Users may utilize digital accounts, payment cards, and / or other sources of funds to process payments via electronic payment and / or transaction networks associated with backend payment processors or other entities on the network. A user's digital account with an online transaction processor may be associated with an identifier, and examples of online transaction processors include payment service providers (e.g., PayPal® and / or Paidy®) that can provide electronic transaction processing services to users through accounts and one or more websites and / or online transaction processor or merchant applications. Digital accounts may be established with credit limits and / or have available balances or values. Online transaction processors may include integration with electronic payment networks (e.g., for payment cards, tokens, etc.) that enable data exchange and communication between two networks. Furthermore, this payment network may provide data communications and backend processing devices that interact with front-end merchants, POS and / or payment terminal processing devices that process transactions using data transfer, such as via digital, online and / or contactless payments including near-field communication (NFC), radio-frequency identification (RFID) fields and communications, Bluetooth or Wi-Fi communications, infrared scanning devices and / or communications, EMV chip readers, magnetic stripe and / or emulation readers and other face-to-face and / or local data transfers.

[0007] However, utilizing such payment mechanisms and networks may require specific data transfer and / or digital wallet terms, systems, and communications. Traditionally, back-payment (BNPL) and / or installment loan balances and accounts may require real-time and / or time-of-transaction processing and / or approval and / or determination (e.g., risk and / or fraud analysis) as they occur. This may conflict with the terms of standard digital wallets, which may not have appropriate digital tokens, identifiers, and other data generated and provided for transaction processing using digital wallets with merchant equipment via near-field communication. Therefore, online transaction processors may provide operations for onboarding and registering digital accounts that provide BNPL, installment loans, and / or other payment services (e.g., balances, budgets, and / or loans that may have repeating or updated amounts (amounts) in each time period or time period and / or that can provide delayed or loan payments) to digital wallets and providers of near-field communication transaction processing services. This can be done by generating and / or providing specific identifiers that conform to corresponding standards regarding the use of identifiers with payment networks, token service providers (TSPs), and / or wireless payment terminals and devices (e.g., International Organization for Standardization (ISO) and / or International Electrotechnical Commission (IEC) standards, including ISO / IEC 7812), such as Bank Identification Numbers (BINs). Such identifiers may be provided for contactless payment providers that can provide components and operations for contactless payments via near-field communication, such as QUICPay® and / or iD®. These identifiers may then be registered and stored for accounts with digital wallets and used during wireless and / or contactless payment processing. These identifiers used for contactless payments may be provided via cardless provision, which does not require a physical payment card or other items to provide the identifier. Instead, cardless provision of identifiers may establish the BIN and / or other data necessary for payment processing at wireless payment terminals without registering and / or using a payment card through mobile applications and digital wallets.

[0008] In this regard, users may wish to purchase goods with portable devices that provide value, credit, or other funds to them through online transaction processors and / or electronic payment networks via software applications and / or digital accounts. Selecting one or more goods in an in-person transaction at a physical merchant location may require payment from the user for electronic transaction processing, which may be provided through tokens, identifiers, data packages, etc., transmitted to the merchant equipment at that location, such as via near-field communication (e.g., contactless payment via NFC, RFID, etc.). Users may make one or more transaction payments using a digital wallet configured to utilize contactless payment terminals and devices using a payment network that includes accounts with online service providers or other transaction processors. A digital account with a service provider may be established by providing account details such as a login, password (or other authentication credentials such as biometric fingerprints, retinal scans, etc.) and other account opening details. Account opening details may include identifying information for establishing an account, such as the user's personal information, corporate or merchant information about the entity, or other types of identifying information including name, address and / or other information.

[0009] Users may also be required to provide financial information, including digital account (e.g., credit / debit card) information, bank account information, gift card information, benefits / incentives, and / or financial investments, when processing transactions with merchants and / or other users or entities. Account opening may also be used to establish account funds and / or value, such as by transferring funds to the account and / or establishing credit limits and corresponding credit values ​​available to the account and / or card. Service providers may provide computing services for sending, storing, and receiving money, processing financial instruments, and / or providing transaction history, including the generation of identifiers (e.g., Funds Payment / Main Account Number (FPAN) and / or Device Payment / Main Account Number (DPAN) fields and BINs used for processing, etc.). Service providers may also provide tokenization of data for transaction processing. Service provider applications or websites, such as PayPal® or other online payment providers, may provide payment and other transaction processing services. Furthermore, digital accounts may be accessed through one or more mobile applications or other software applications for portable devices.

[0010] To make payments for transactions (e.g., transfers or payments to other users, merchants, or other entities), users may provide digital account or source of funds information and / or log in to accounts with service providers via authentication credentials in a software application. When in-person payments are provided through contactless payment terminals and portable devices, external wallets or service provider digital wallets may be used in accounts to wirelessly provide data to the terminals or devices. In this regard, identifiers and / or digital tokens or other data may authorize and / or authenticate a user for the use of their digital wallet and / or for the means of payment in the digital wallet (e.g., an account with an online transaction processor), and such authorization and / or authentication may be transmitted wirelessly to another party for payment processing. Data may be stored and / or transmitted using one or more storage media and / or wireless transceivers, such as NFC / RFID components, FOB antennas, passive antennas, or active antennas, etc., magnetic stripes or EMV chips, displayable codes or data, etc. For example, a POS device and / or card reader may be used to read data provided for an identifier that reproduces or mimics card data from a wireless card, using merchant equipment at the merchant's location. This enables user payments via payment accounts and / or digital wallets using near-field communication and contactless processing. The payment may then be issued to the other party to the transaction.

[0011] To adapt a user's digital account for BNPL or other payment processing mechanisms that may not have been traditionally established or associated with specific identifiers and terms for contactless payments, an online transaction processor may provide an operation to initially receive and process requests for adaptation to a separate digital wallet (e.g., Apple® Wallet for Apple Pay®) and / or establishment of an account with it. Requests for adaptation and / or establishment may be received via a software application (e.g., a mobile or other dedicated resident application) or a website for the online transaction processor providing the digital account, or via the digital wallet platform and the digital wallet's application / website. Once received (e.g., at a front-end such as the transaction processor's application / website for the account), the principal account identifier for the account may be requested and received from the transaction processor's host system, back-end system, or server. Eligibility checks may also be performed for accounts that have (or are associated with) digital wallets and digital wallet providers, and such checks may include querying and / or determining whether the addition of payment accounts and / or secure elements can be performed by the application that has the digital wallet for the digital account.

[0012] When an account is eligible for adding to a digital wallet and using the account through the digital wallet (e.g., for contactless payments), the account's front-end application or website may provide the user with options and / or interfaces to proceed through the flow and interface for adding the account to the wallet and / or for adding the account to the wallet. The application may then request that the account be added to the digital wallet with the wallet provider. The wallet provider may retrieve and obtain a certificate from the wallet provider's back-end server or system that may include a public certificate providing a trust mechanism, digital signatures, and the establishment of a secure connection. The public certificate may be returned to the digital wallet platform and / or front-end application or wallet, thereby returning the certificate to the account's application, website, or other front-end during the registration and establishment of the account with respect to the digital wallet. A nonce (e.g., a random number without repetition) may be returned from the back-end server or system along with the public certificate, and a nonce signature with the nonce may be provided to the account's front-end along with the certificate.

[0013] Online transaction processors may receive these certificates, nonce and / or nonce signatures via a front-end application or website, and they may then encrypt this data with the account's principal account number and provide it to the transaction processor's backend (e.g., a server, processor, device, or other system). This may be provided through an Application Programming Interface (API) call or request, and the backend may correspond to a host or other. The host may then provide an API response with an encrypted principal account number (PAN) corresponding to a BIN or other identifier. The identifier provided in the encrypted PAN may correspond to an identifier that is specifically generated and / or provided to the account by a contactless provider providing contactless payment processing for the payment network used by the merchant device and the digital wallet for contactless payment processing. Furthermore, the host may provide a cryptographically unique one-time password (OTP) and / or temporary public key for the transaction processor. Upon receipt by the transaction processor's frontend for the account, the frontend may interact with the digital wallet to set and establish an identifier (e.g., encrypted PAN), encrypted OTP, and / or temporary public key with the digital wallet for use with the account during contactless payment processing. Specifically, an identifier may be used and / or entered in the FPAN or DPAN field during account registration with a digital wallet to enable tokenization and payment processing via TSP, where the identifier may be a BIN that enables the resolution of payment processing with the transaction processor on the payment network. For example, the identifier may identify the account and transaction processor on the network for payment processing, and may be compatible with and used by the tokenization operation for TSP and contactless payments.

[0014] Subsequently, confirmation of registration may be completed by the digital wallet or account and digital wallet user and transaction processor, other servers, systems and / or backends for the digital wallet and / or payment network. For example, data established with the digital wallet may be passed to a server for the digital wallet and data activation may be performed. A TSP compatible with the BIN or other identifier may be determined, and a network check card with an encrypted PAN or other identifier and a temporary public key may be provided to the TSP (e.g., FeliCa®, etc.). The TSP may send an API request regarding card eligibility from a transaction processor host that can provide an API response regarding the product identifier and issuer card identifier. The TSP may then provide terms and conditions to the digital wallet, which may be requested by the user via the transaction processor's application or website. Once agreed, the digital wallet may provide activation data to the TSP, which can request and receive the card digital processing from the transaction processor host. Tokens can be issued to a digital wallet as DPANs by a TSP regarding an identifier, and can be detoxified to determine the identifier and enable transaction processing during contactless payments. The digital wallet can then respond to the user via the transaction processor's frontend upon successful activation and establishment of an account with the digital wallet.

[0015] Once a digital account is opened for use with contactless payments and registered in a digital wallet, the user may acquire, contribute, and / or receive any available balance available to them. This may correspond to real or virtual assets or values ​​and may be a revolving credit limit granted to the user. The user may receive set balances and / or installment loans or other loans, as well as authorizations and limits for individual transaction processing (e.g., relating to BNPL accounts and / or payment authorizations or balances). In this regard, the user's budget or BNPL grant may include, for example, a $2,000 credit repayment or balance payment (e.g., payment of the balance of the granted credit) in the revolving credit payment claim cycle or period, or may be authorized on a transaction-by-transaction basis for credit grants and payments in a BNPL payment authorization and plan. A BNPL plan for the user may enable the user to lend or borrow part or all of their transaction balance. In this regard, loan decisions, loan grants, and terms (including interest rates, fees, repayment schedules and / or timelines, number of payments, installment loan payment amounts, etc.) may be determined in real time during the transaction and / or at a time associated with the transaction. Thus, each individual transaction may require approval on a transaction-by-transaction basis, or a batch of collected transactions may occur simultaneously, nearly simultaneously, or at other times.

[0016] Users may use mobile and / or resident software applications on computer devices and / or websites to access digital accounts and / or digital account credit limits via digital wallets. These interfaces allow users to view or request transaction and payment processing based on one or more rules, regulations and / or budgets associated with them. For example, available limits for a user may be set by government laws and / or regulatory laws or rules. Furthermore, a user's budget, income, past repayment data, credit rating, or other user data may set these limits. These limits may also be determined using a machine learning (ML)-based artificial intelligence (AI) engine capable of pre-calculating and recalculating such limits based on rules, or real-time and / or available user data, merchant data, merchant agreements and other data. Furthermore, such AI and ML engines may also be used at the time of a transaction to calculate and / or determine risks, potential fraud, repayment or loss risks or possibilities, etc., which may be used to decide whether to approve or reject payments and transactions, including those utilizing BNPL plans and requests. Risk and fraud engines, models, and / or rule sets may be used to authorize, approve, and / or reject transactions on accounts requested via digital wallets (e.g., using contactless payment mechanisms and payment networks / TSPs).

[0017] Transactions may be processed using a digital account through a digital wallet and a contactless payment terminal / device capable of generating and processing transaction data for transactions on a digital payment network with backend payment processors and TSPs. Transaction data may be generated and may include information such as one or more goods, goods costs (e.g., itemized classification), and / or total cost, transaction time, corresponding merchant or merchant identifier, other users involved in the transaction, location of the transaction, MCC identifying a specific category for each transaction, and / or other transaction data. An online transaction processor may provide electronic transaction and payment processing services used to process transactions using transaction data and / or card data. To receive this data, an online transaction processor may be required to interact with electronic card, payment, or transaction networks that transmit, receive, and / or process transaction data based on backend card processors, TSPs, and / or associated payment method data. In this regard, an online transaction processor may utilize application programming interfaces (APIs) to communicate with and integrate with one or more APIs of electronic payment networks. This enables the online trading processor to detect, receive, and process trading data. The trading data can then be detected and / or transmitted to the online trading processor via one or more APIs. This may include receiving and processing data in real time, for example, when a trade occurs to provide approval and authorization for trading units under a BNPL plan.

[0018] When transaction data relating to a transaction is received by an online transaction processor when processing of the transaction is required, the transaction data may be analyzed to determine whether the transaction can be approved or rejected based on a risk assessment or analysis. Receiving transaction data relating to a transaction may involve data transfer, reading, and / or scanning events for corresponding transaction information generated by merchant equipment. For example, a portable device may utilize a mobile application for a digital wallet that has data stored and made available for a transaction processor's digital account. A portable device may interact with nearby or adjacent POS or merchant equipment and / or terminals that may include readers or scanners for magnetic stripes, EMV chips, NFC or RFID transceivers, etc., to read data from local equipment or data storage mechanisms. A portable device may provide and / or generate identifiers (e.g., BINs) for an account for use with the TSP and other backend processors on the payment network via a digital wallet and / or corresponding mobile application. A portable device may utilize a digital wallet that has been previously established (e.g., a DPAN token relating to a BIN provided by the TSP to the digital wallet) or generated for an identifier-based transaction to send tokens containing the identifier. This is provided from a portable device to a merchant device via contactless payment and near-field communication (e.g., through a local transceiver or other terminal communication module), and the authentication and processing of the DPAN or other tokens are required by the payment network.

[0019] Online transaction processors may be established with payment networks to receive communications arriving from payment networks, merchants, point-of-sale (POS) devices, and others, and to identify electronic transaction payments requested through digital accounts. When processing a transaction, a merchant device may receive a token or other data relating to an identifier via contactless readout or data transfer, and then request authorization from a payment network with a backend payment processor or system (e.g., QUICPay® and / or iD®), which may detoxify the token using a TSP associated with the tokenization of the identifier (e.g., by converting a DPAN to an FPAN or other for a BIN or other identifier). Once detoxified, the identifier may be processed by the online transaction processor with transaction data relating to the approval or rejection of the transaction.

[0020] For example, if a transaction matches the limit, the online transaction processor may approve the transaction or allow the transaction to be approved by the payment network (for example, by not rejecting the transaction or causing the electronic card network and / or backend credit card processing system to reject the transaction). However, if a transaction violates or does not match the limit (for example, if the transaction amount causes the balance of a digital account or the digital account to exceed the limit balance cap), the online transaction processor may reject the transaction by refusing to process the transaction and / or by requiring the network and / or backend processing system to reject or deny the transaction. If a transaction exceeds or violates the limit, the online transaction processor may refuse to process the transaction and / or send a message to the user's device with a notice or warning. The device may include an application with one or more interface options, elements or graphics that may include executable options, actions and / or selectable elements for approving or rejecting transaction processing and viewing transaction status, balances, loan information, etc.

[0021] Thus, an account that utilizes real-time and / or approval and authentication mechanisms at the time of a transaction can be made compatible with a digital wallet provider separate from the digital wallet and the account transaction processor. This enables the integration and use of digital accounts with previously incompatible computing systems and networks for data processing, including tokenization requirements and TSPs. Further, thanks to the operations for providing specific identifiers utilized through the digital wallet, another system can correlate and transmit data in a fast and efficient manner that enables real-time data processing and transaction authentication during face-to-face contactless payments and / or at physical storefronts and other points of sale. Accordingly, the system can be correlated for use of such data formats, components, and networks that would otherwise have impeded use and interaction between previously incompatible platforms.

[0022] FIG. 1 is a block diagram of a networked system 100 suitable for implementation of the processes described herein, according to an embodiment. As shown, system 100 may include or implement multiple devices, servers, and / or software components that operate to execute various methods according to the described embodiments. Exemplary devices and servers may include stand-alone devices and enterprise-scale servers that operate an OS such as Microsoft® OS, UNIX® OS, LINUX® OS, or other suitable OS based on devices and / or servers. It is understood that the devices and / or servers illustrated in FIG. 1 may be deployed in other ways and that the operations performed by such devices and / or servers and / or the services provided thereby may be combined or separated by a given embodiment and may be performed by a greater number or fewer number of devices and / or servers. One or more devices and / or servers may be operated and / or maintained by the same or different entities.

[0023] System 100 includes a user device 110 that communicates via a network 150, a transaction processor (transaction processing entity) 120, and a digital wallet platform 140. The user device 110 can be used to establish a transaction and process payment for the transaction using an account managed by the user device 110. In this regard, when a transaction is processed, the transaction data can be provided via a transaction network, which is the network 150 available to the transaction processor 120. The user device 110 can utilize a digital wallet provided by the digital wallet platform 140 to process transactions using a face-to-face contactless payment system and / or wireless communication and communication protocols. The transaction processor 120 can adapt the account used by the user device 110 to the digital wallet platform 140 and register the account with other processors and regulations used by the payment network for use in the digital wallet provided by the TSP and the digital wallet platform 140.

[0024] The user device 110, the transaction processor 120, and the digital wallet platform 140 may each include one or more processors, memories, and other suitable components for executing instructions such as program code and / or data stored on one or more computer-readable media for implementing the various applications, data, and steps described herein. For example, such instructions may be stored on one or more computer-readable media such as memories or data storage devices internal and / or external to the various components of the system 100 and / or accessible via the network 150.

[0025] The user device 110 may be implemented using any suitable hardware and software configured for wired and / or wireless communication with the merchant device, payment terminal, contactless payment transceiver, contactless payment device, and / or transaction processor 120 for processing transactions using a digital wallet provided by the digital wallet platform 140. The user device 110 may accommodate a user who processes payments and sales through an executable software application. In various embodiments, the user device 110 may be implemented as a personal computer (PC), smartphone, laptop / tablet computer, wristwatch with appropriate computer hardware resources, other types of wearable computer devices, and / or other types of computer devices capable of transmitting and / or receiving data. Although only one computer device is illustrated, multiple computer devices can function similarly.

[0026] The user device 110 in Figure 1 includes a payment application 112, a database 116, and a network interface component 118. The payment application 112 may correspond to executable processes, procedures, and / or applications with associated hardware. In other embodiments, the user device 110 may include additional or different modules with specialized hardware and / or software as needed.

[0027] The payment application 112 may correspond to one or more processes for executing software modules and associated components of the user device 110 in order to provide features, services and other operations for the user via the network 150, which may include accessing and utilizing computing services provided by the transaction processor 120 and / or the digital wallet platform 140. In this regard, the payment application 112 may correspond to specialized software used by the user of the user device 110, which may be used to access websites or applications (e.g., mobile applications, rich internet applications, or resident software applications) that can display one or more user interfaces that enable interaction with the computing services of the transaction processor 120 and / or the digital wallet platform 140. In various embodiments, the payment application 112 may correspond to a general browser application configured to retrieve, present, and communicate information via the internet (e.g., using resources on the World Wide Web) or via a private network. For example, payment application 112 may provide a web browser capable of sending and receiving information over network 150, which includes searching for and retrieving information from a website, presenting that website information to the user, and / or communicating information to that website. However, in other embodiments, payment application 112 may include a dedicated application for a transaction processor 120, a digital wallet platform 140, or another entity. Payment application 112 may be used to access and utilize a digital wallet 113 provided and / or serviced by a digital wallet platform 140, which can incorporate an account 114 provided and serviced by a transaction processor 120, which can provide BNPL services for purchase, installment payment loans or loans, or other services.

[0028] The payment application 112 may be associated with account information, user financial information, and / or transaction history. However, in further embodiments, various services, including social networking, posting or sharing on media, microblogging, browsing and searching for data, online shopping, and other services available via the transaction processor 120, may also be provided via the payment application 112. Thus, the payment application 112 may also be compatible with different service applications and others. When the payment application 112 is used with the transaction processor 120, the payment application 112 may request payment requests and / or transaction processing such as payment requests for payment processing using account 114 having the transaction processor 120 and / or contactless data transfer. Data for account 114 may be provided by the digital wallet 113 during contactless payment via corresponding terms, operations, and / or applications relating to the digital wallet 113 and / or the digital wallet platform 140.

[0029] For example, a payment request or other interaction relating to a transaction may correspond to using a payment application 112 to request, establish, and / or process a transaction for payment using account 114, which may have access to a real-time and / or per-transaction approval and authorization mechanism (e.g., for BNPL-type loans and / or payments). The digital wallet 113 may be used to transmit other identifiers generated and / or provided for account 114 on a payment network for contactless payments, tokenized and / or encoded as BIN or DPAN or other FPAN-compatible tokens. Such identifiers and tokens for account 114 may be generated while adapting and establishing account 114 for use with the digital wallet 113, and may be processed by the transaction processor 120 on the digital wallet platform 140 as described herein. The tokens may then be transmitted wirelessly, such as through near-field communication for contactless payment terms, devices and technologies, via the operation of the digital wallet 113, thereby enabling account 114 to be used for payment of transactions. The payment application 112 may provide payment requests to one or more contactless payment devices, terminals, transceivers, etc., having one or more merchants, via a tokenized identifier for account 114 that uses the terms and conditions for the digital wallet 113 after registration. The payment application 112 may then be used to view transaction processing and other results via one or more interfaces.

[0030] In various embodiments, the user device 110 may include other applications that may be desired in certain embodiments to provide features to the user device 110. For example, other applications may include client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) via the network 150, or security applications for implementing other types of applications. Other applications may also include email, mobile email, voice and IM applications that enable the user to send and receive emails, calls, texts and other notifications via the network 150. In various embodiments, other applications may include financial applications, such as banking applications. Other applications may include social networking applications, media browsing and / or merchant applications.

[0031] Other applications may also include location detection applications that can be used to determine the user's location, such as a map, compass, and / or GPS application, which may include a specialized GPS receiver for determining location information for the user device 110. Other applications may include device interface applications and other display modules that can receive input from the user and / or output information to the user. For example, other applications may include software programs that include a graphical user interface (GUI) that can be executed by the processor and is configured to provide an interface to the user. Other applications may therefore use components of the user device 110, such as display devices and other output devices including speakers that can display information to the user.

[0032] The user device 110 may further include a database 116 stored in the temporary and / or non-temporary memory of the user device 110, which may store various applications and data and may be used during the execution of various modulators of the user device 110. The database 116 may include appropriate identifiers, such as operating system registry entries, cookies and / or other applications associated with the payment application 112, identifiers associated with the hardware of the user device 110 that may be communicated when identifying the user / user device 110 to the transaction processor 120, or other identifiers used for payment / user / device authentication or identification. Furthermore, the database 116 may include data for a digital wallet 113 and / or account 114, which may include a digital wallet provided by the transaction processor 120 and the digital wallet platform 140, payment terms and conditions, and identifiers and / or tokens used for contactless and / or wireless payment processing and data transfer over the network.

[0033] The user device 110 includes at least one network interface component 118 adapted to communicate with the transaction processor 120, the digital wallet platform 140, and / or other devices and servers via the network 150. In various embodiments, the network interface component 118 may include DSL (e.g., digital subscriber line) modems, PSTN (public switched telephone network) modems, Ethernet devices, broadband devices, satellite devices, and / or various other types of wired and / or wireless network communication devices, including microwave, radio frequency, infrared, Bluetooth®, and short-range wireless communication devices.

[0034] The transaction processor 120 may be maintained by an online service provider that provides processing to offer account services and processed payments. In this regard, the transaction processor 120 may include one or more processing applications that can be configured to interact with user devices 110, a digital wallet platform 140 and / or other devices / servers to facilitate communication and transactions between users. The transaction processor 120 may be maintained by, or include, another type of platform or service provider, a transaction processor, such as PayPal® (Inc.) in San Jose, California, USA. Although the transaction processor 120 and the digital wallet platform 140 are discussed as separate devices and servers, in some embodiments one or more of the processing described may be provided not separately, but by other devices or servers, or by the same device or server.

[0035] The trading processor 120 in Figure 1 includes a trading processing platform 130 having a trading processing application 122, a database 126, and a network interface component 128. The trading processing platform 130 and the trading processing application 122 may correspond to being able to execute hardware-associated processes, procedures, and / or applications. In other embodiments, the trading processor 120 may include additional or different modules having specialized hardware and / or software as needed.

[0036] The transaction processing platform 130 may support one or more modules and associated specialized hardware of the transaction processor 120 for processing transactions with user devices 110 and one or more merchant or seller devices with respect to goods, which may be based on the fact that accounts 114 are registered and established in a digital wallet 113 for face-to-face, near-field wireless and / or contactless payments, data transfer, communication, etc. In this regard, the transaction processing platform 130 may support specialized hardware and / or software used by the user together with the BNPL service 132 to establish accounts 134, including accounts 114 used by the user device 110. Each account 134 may be opened by providing personal and / or financial information to the transaction processor 120 and selecting authentication credentials. In various embodiments, financial information may include payment method information, such as account / card numbers and card information. Accounts may be used to purchase goods and / or transfer funds. Payment accounts may be accessed and / or used through a browser application and / or a dedicated payment application. However, in other embodiments, account 134 may be used in conjunction with the digital wallet platform 140, for transaction and payment processing through a digital wallet provided by the digital wallet platform 140, by using the digital wallet terms and operations for payment processing, including contactless data transfer and payment processing. The BNPL service 132 may be used to request and / or receive real-time or per-transaction transaction limits, and approvals for transactions, for BNPL type loans and / or loans and other. The BNPL service 132 may process payments and may provide transaction history for the approval, authorization, or denial of transactions.

[0037] The BNPL service 132 may correspond to the services of the transaction processor 120 that can be used by end users, such as for executing, transferring, and otherwise performing electronic payments using one or more accounts and / or financial instruments. The BNPL service 132 may also include or utilize various processors, engines, or models necessary for authentication, account opening and maintenance, electronic transaction processing, deposits and / or withdrawals, dispute resolution, and other purposes. The BNPL service 132 may include one or more API integrations and / or interactions with the payment network to detect, receive, and monitor transaction data for compliance with authorizations and / or spending limits for accounts 134. Thus, the BNPL service 132 may interact with the network through one or more API calls to the APIs of the transaction processing platform 130 that interface with the APIs of the digital payment network and backend processors. BNPL Service 132 may determine transaction data relating to transactions processed on the network based on received communications, and may process such transactions in real time and / or on a per-transaction basis based on the user, transaction and / or account risks of repayment, fraud, default, or other risks.

[0038] BNPL service 132 may receive transaction data relating to transactions processed using accounts accessible through user device 110 and / or other devices or services. BNPL service 132 may then determine spending limits to be set for the use of account data used to perform real-time risk analysis, assessment, and checks for the available balance, credit limit, and / or other funds of the user's digital account, as well as for approving or rejecting corresponding transactions. In this regard, the transaction processing platform's AI engine may be executed to calculate the risks and / or availability of installment loans, financing, and others based on user data, budgets, account assets or balances, available or future funds, and other factors. Devices (e.g., user device 110 and / or merchants, POS, or payment devices) and their corresponding transactions may be detected and processed using API calls with the payment network on network 150. BNPL service 132 may determine whether a transaction meets the spending limit and / or can be approved and authorized in real time and / or for a particular transaction. If it meets and meets and can be approved and authorized, the transaction may be approved or authorized. However, if a transaction does not meet the spending limit or exceeds the risk or limit for electronic transaction processing and / or credit / balance limit approval, the BNPL service 132 may be used to reject transaction processing or to instruct backend credit processors to reject processing the transaction. Furthermore, the BNPL service 132 may send messages to user equipment 110 and / or other equipment to notify the user of the approval or rejection of the transaction.

[0039] In some embodiments, the BNPL service 132 may employ one or more AI engines and / or models, such as rule-based, machine learning, or neural network (NN) models and / or engines, which may be used for intelligent decision-making regarding risk and / or transaction approval. These may include rule-based engines capable of processing user data, transaction data, and / or merchant data, which may be used to determine transaction approval for a requested transaction at a given time or when the transaction occurs. Furthermore, the BNPL service 132 may utilize machine learning engines or other AI models, i.e., engines for determining risk and / or transaction approval. In some embodiments, machine learning engines may include AI models such as ML or neural network (NN) models. AI models can generally correspond to any artificial intelligence that makes decisions, such as rule-based engines and others. However, AI models also include subcategories, including ML and NN models, which instead use algorithmic relationships to provide intelligent decision-making. In general, NN models can include deep learning models and others, and can correspond to a subset of ML models that attempt to mimic human thought by utilizing a set of various algorithms for modeling data through different graphs of neurons, where neurons contain nodes of data representation based on algorithms that can be interconnected at different nodes. ML models can similarly utilize one or more of these mathematical models, and can similarly create layers and nodes connected between layers in a similar manner to the neurons in NN models.

[0040] When building an ML model for a machine learning engine, training data may be used to create one or more classifiers to provide recommendations, predictions, or other outputs based on these classifiers and the ML model. The training data may be used to determine outputs for risk, transaction approval or rejection, or other when input features for training prediction scores and / or transactions are required to be processed using account 134 which may be used by merchants or payment devices via one or more digital wallets and digital wallet platforms 140. For example, an ML model for a machine learning engine may include one or more layers, including an input layer, hidden layers, and output layers with one or more nodes, but other layers may also be utilized. For example, any necessary or appropriate number of hidden layers may be utilized. Each node in a layer is connected to a node in an adjacent layer, where a set of input values ​​may be used to generate one or more output scores or classifications. Within the input layer, each node may correspond to a distinguishable attribute or input data type used to train the ML model about the machine learning engine.

[0041] Subsequently, the hidden layer can be trained with these attributes and corresponding weights using ML algorithms, computations, and / or techniques. For example, each node in the hidden layer may generate a representation that includes mathematical ML computations (or algorithms) that produce values ​​based on the input values ​​of the input nodes. The ML algorithm may assign different weights to each of the data values ​​it receives from the input nodes. Hidden layer nodes may include different algorithms and / or different weights assigned to the input data, and therefore may produce different values ​​based on the input values. The values ​​generated by the hidden layer nodes may be used by output layer nodes to produce one or more output values ​​for an ML model to a machine learning engine attempting to classify and / or provide transaction approval outputs. Thus, when an ML model to a machine learning engine is used to perform predictive analysis and output, the input may provide corresponding outputs based on the classifications trained on the ML model to the machine learning engine.

[0042] An ML model for a machine learning engine can be trained with training data. By providing training data to train an ML model for a machine learning engine, the nodes in the hidden layer can be trained (tuned) so that the optimal output (e.g., classification) is produced in the output layer based on the training data. By continuously providing various sets of training data and penalizing the ML model for the machine learning engine if its output is incorrect, the ML model for the machine learning engine (and specifically, the representation of the nodes in the hidden layer) can be trained (tuned) to improve its performance in data classification. Tuning an ML model for a machine learning engine may include adjusting the weights associated with each node in the hidden layer. Thus, the training data can be used as a set of input / output data that enables the ML model for the machine learning engine to perform classification based on input attributes. The output classification for an ML model trained for a machine learning engine may be a classification used for risk and / or transaction processing by BNPL Service 132.

[0043] Furthermore, the transaction processing platform 130 processes wallet enrollment requests 138 to enroll account 134 into a digital wallet provided by the digital wallet platform 140. Wallet enrollment requests 138 may correspond to requests received to enroll account 134 with the corresponding digital wallet for use by these digital wallets, such as when performing contactless or near-field wireless transaction processing and other data transfers. This may be done by providing and / or generating a BIN or other identifier that can be tokenized as a PAN, such as a DPAN or other token used for processing in a payment network for contactless payments. In this regard, the digital wallet may require an FPAN or DPAN field during the enrollment of the account or financial instruments relating to contactless payments made through the digital wallet using the provided BIN or other identifier. For example, in one wallet enrollment request 138, identifier 136 may be generated and / or provided for use of the digital wallet 113 for using account 114 through the wallet for electronic transaction processing via contactless payments and / or other payment processing using the digital wallet 113. This may be done in conjunction with the digital wallet platform 140, TSP, etc., interacting with the front-end (e.g., front-end processor, server, system equipment, etc.) for the transaction processor 120 and / or digital wallet platform 140, the digital wallet 113, the account 114 and / or the application website, as well as the back-end processor and payment network for tokenization / detoxification. Examples of such identifiers, tokens, components and operations for establishing and using identifiers 136 and other identifiers for account 134 with a digital wallet will be discussed further with respect to Figures 2A to 5B below.

[0044] The transaction processing application 122 may correspond to one or more processes for implementing the module and specialized hardware of the transaction processor 120 for processing transactions or providing other services to customers, merchants and / or other end users and entities of the transaction processor 120. In this regard, the transaction processing application 122 may correspond to specialized hardware and / or software used by the transaction processor 120 to provide computing services to users, which may include electronic transaction processing and / or other computing services using the account 134 provided by the transaction processor 120, such as in response to receiving transaction data along with a dispatched (routed) identifier 124 for electronic transaction processing of transactions initiated using a digital wallet with a registered account 134. In some embodiments, the transaction processing application 122 may be used by a user, such as a user associated with a user device 110, to establish a user and / or payment account and a digital wallet that can be used to process transactions. Account 134 may be accessed and / or used through one or more instances of a web browser application and / or dedicated software application run by the user device 110, and may engage in computing services provided by the transaction processing application 122. In addition to or instead of the above, the computing services of the transaction processing application 122 may support messaging, social networking, posting or sharing media, microblogging, browsing and searching data, online shopping, and other services available through the transaction processor 120.

[0045] In various embodiments, the transaction processing platform 130 may be desirable in certain embodiments for providing features to the transaction processor 120. For example, the transaction processing platform 130 may include security applications for performing server-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) via the network 150, or security applications for performing other types of applications. The transaction processing platform 130 may include software programs, including a graphical user interface (GUI), which is executable by the processor and configured to provide an interface to a user when accessing the transaction processor 120 via one or more user devices 110, where the user or other users can interact with the GUI to more easily view and communicate information. In various embodiments, the transaction processing platform 130 may include additional connectivity and / or communication applications, which may be used to communicate information over the network 150.

[0046] In addition, the transaction processor 120 includes a database 126. The database 126 may store various identifiers associated with the user device 110. The database 126 may also store account data, including payment methods and authorization powers of attorney, as well as transaction processing history and data on processed transactions. The database 126 may store user-associated receipt data, such as transaction data and spending limits in electronic transaction processing. Furthermore, the database 126 may be used to store data about account 134, which can be used to generate, store and / or transfer identifiers and / or tokens used to establish account enrollment and the processing of transactions via the digital wallet and account 134.

[0047] In various embodiments, the transaction processor 120 includes at least one network interface component 128 adapted to communicate with user equipment 110, a digital wallet platform 140, and / or other equipment / servers via the network 150. In various embodiments, the network interface component 128 may include DSL (e.g., digital subscriber line) modems, PSTN (public switched telephone network) modems, Ethernet equipment, broadband equipment, satellite equipment, and / or various other types of wired and / or wireless network communication equipment, including microwave, radio frequency (RF), and infrared (IR) communication equipment.

[0048] The digital wallet platform 140 may be maintained by, for example, other online service providers that provide, utilize, and / or maintain digital wallets for third-party application providers, merchants, transaction processors, and / or users that may be used during electronic transaction processing. The digital wallet platform 140 may correspond to one or more physical and / or online merchant transactions, sales platforms, point-of-sale (POS) devices, websites, and / or online resources that users may visit to shop for goods that can be purchased through processing and funds provided via the digital wallet maintained by the digital wallet platform 140. For example, the digital wallet platform 140 may be used at the locations of physical merchants for processing transactions, as well as at one or more POS devices on a digital platform accessible via websites and / or applications, where users may engage in electronic transaction processing. The digital wallet platform 140 may further include other platforms, websites, and resources that enable users to engage in electronic transaction processing, such as those associated with payment processors, money transfers, payment of utility bills or living expenses, and other payments or purchases that can be used by the user, and that can request payment of balances owed for certain products, services, or other goods. In some embodiments, the digital wallet platform 140 may be implemented as a single or networked personal computer (PC), server, smartphone, laptop computer, wearable computer, and / or other type of computing device. Although only one wallet provider platform is illustrated, multiple platforms may function similarly.

[0049] The digital wallet platform 140 in Figure 1 includes a digital wallet application 142. The digital wallet application 142 may correspond to executable processes, procedures, and / or applications with associated hardware. In other embodiments, the digital wallet platform 140 may include additional or different software as needed.

[0050] The digital wallet application 142 may provide and / or process transactions with and / or on behalf of the user device 110 and / or the user associated with the user device 110 (for example, using one or more of the digital wallet 144 having payment sources including payment cards, digital accounts, cash and others, and accounts 134 registered for use in the digital wallet 144). In one embodiment, the digital wallet application 142 may be accessible via the Internet and may also provide the digital wallet 144 for use in the user device 110 and the transaction processor 120 via the network 150. The digital wallet application 142 may be used at the location of a physical merchant, such as with a POS device used to provide sales at a physical location, including contactless payments and transaction processing through data transfer using near-field communication, signals, and protocols. The digital wallet application 142 may therefore be used to match accounts 134, including accounts 114 having a digital wallet 113 using identifier 136, to the digital wallet 144. In this regard, the digital wallet application 142 may be used to receive one or more identifiers that can be tokenized and stored together with the digital wallet 144 for use in payment processing using payment networks, TSPs, other backend payment processors and systems, etc., as further detailed in relation to Figures 2A to 5B below. Payments may be made using a digital account by sending transaction data back to the transaction processor 120 for payment with the dispatched (routed) identifier 124. After confirmation of receipt of payment by digital account and / or digital account transfer, the digital wallet platform 140 may process the payment to the merchant or other seller at the transaction processor 120, including the account, identifier and loan or lending provided in a BNPL type loan or loan, and such processing may be approved and / or processed in real time and / or per transaction for approval.

[0051] Network 150 can be implemented as a single network or a combination of multiple networks. For example, in various embodiments, network 150 may include the Internet or one or more intranets, fixed telephone networks, wireless networks, and / or other suitable types of networks. Thus, network 150 can correspond to small-scale communication networks such as private or local area networks, or to larger networks such as wide area networks or the Internet that are accessible to various components of system 100.

[0052] Figures 2A and 2B are exemplary diagrams 200a and 200b for establishing and utilizing a digital account for near-field wireless data processing with merchant equipment through a digital wallet provided by a separate platform, according to one embodiment. Diagrams 200a and 200b in Figures 2A and 2B may correspond to the operational flow and data communication between devices, servers, and / or systems when interacting to provide contactless payments through a payment account using a digital wallet from a separate wallet provider, such as the interaction between the user device 110, transaction processor 120, and / or digital wallet platform 140 described with respect to system 100 in Figure 1.

[0053] In diagram 200a of Figure 2A, various interactions, inputs, data communications, and / or processing operations are shown to establish a digital account with a digital wallet to process transactions using a payment network, such as contactless payments and BNPL-type or other loan payment services. Initially, in interaction 1, a consumer 202, such as a customer of an online transaction processor or other service provider that can process transactions with merchants and other sellers, may interact with a BNPL application 204 to request the addition of an account to a digital wallet with a digital wallet provider separate from the online transaction processor that provides the account. The account may correspond to a BNPL-type account and / or an account that utilizes BNPL services, such as for financing transactions through loans, installment loans, and / or periodic repayment plans and other financial services. The account may therefore require real-time and / or per-transaction risk and fraud analysis, processing, and / or authorization via the digital wallet. Thus, the account may initially be incompatible with the digital wallet and / or the payment network used by the digital wallet.

[0054] Consumer 202 may interact with BNPL application 204 in interaction 2 via a dedicated software application and / or website or web application that can retrieve and obtain public certificates from the digital wallet and backend 208. Digital public certificates can be used for trust operations that enable secure communication, trusted data, signatures, and other transactions, such as writing and verifying signatures and establishing a chain of trust to verify other certificates. Thus, public certificates can be used to generate and / or provide identifiers (e.g., BIN or other identifiers, numeric, alphanumeric codes, etc.) for accounts used in trusted payment processing and other signing and trust operations during payment processing and other account or digital wallet activities. BNPL application 204 then provides the public certificate to BNPL backend 206 in interaction 3, and BNPL backend 206 stores the public certificate. Prior to transfer to and / or storage to BNPL backend 206, any public certificate with a nonce or nonce signature may be encrypted for secure storage. In interaction 4, the BNPL backend 206 responds to the BNPL application 204 with encrypted data, such as encrypted card data, which can mimic or reproduce a credit card, debit card, or other payment card by having an identifier (e.g., BIN) that can be used in a card processing and / or payment network, and / or with a card processing terminal including contactless RFID, NFC, or other near-field wireless terminals, devices, transceivers, and communications for payment processing. The provided and / or proxy card identifier or other data may be generated and / or provided so that the account is compatible with the corresponding payment network and TSP, such as TSP 210. Thus, the identifier may correspond to a BIN that enables filling in an application form field for registering an account to a digital wallet in the FPAN field or other PAN fields that enable tokenization and use of the corresponding payment network.

[0055] In interaction 5, the encrypted (card) data is sent from the BNPL application 204 to the digital wallet and backend 208 for processing, where the digital wallet and backend 208 may correspond to the token requester. The digital wallet and backend 208 may recognize the encrypted data as provided or proxy data that mimics or reproduces card data that can be used for electronic transaction processing via the digital wallet, such as a BIN for a payment card. The data may be encrypted using a shared key, such as a public key from a public certificate, so that the digital wallet and backend 208 can decrypt and verify the data for account registration. Thus, the encrypted data may include identifiers that should be registered and / or stored in the account and can be tokenized as a DPAN or FPAN type format for use with payments on the payment network. In interaction 6, the encrypted data and / or identifiers are provided from the digital wallet and backend 208 to a Token Service Provider (TSP) 210 that can tokenize data for storage and use during electronic transaction processing. For security reasons, the TSP210 may support a computing service that generates tokens to represent data without exposing the data, where the decryption of tokens for receiving and / or processing data may be done with (or by) the TSP210.

[0056] In order to register the account and identifier with the digital wallet and backend 208, the BNPL backend 206 performs identification in interaction 7 and / or processes an identification check of the account with TSP 210. TSP 210 may provide DPAN, FPAN, or other PAN-type data tokens for use with the payment network. In interaction 8, the terms and conditions are made to the digital wallet and backend 208, and in interaction 9, backend 208 requests acceptance and agreement to the terms and conditions from consumer 202. Consumer 202 may then agree to the terms and conditions for the use of the digital wallet and the account through the digital wallet for payment processing, including contactless and / or near-field wireless data transfer and payment processing. In interaction 10, the BNPL backend 206 performs an eligibility check with TSP 210 for the account and identifier for tokenization and use with the payment network, and tokens may be generated in response to the determination that the account and / or identifier are eligible. In interaction 11, tokens such as DPAN for identifiers or other data from encrypted data provided by the digital wallet and backend 208 are returned from TSP 210 to the digital wallet and backend 208 for storage. The tokens may be stored with and / or for the consumer 202's digital wallet and associated with a digital account and / or BNPL-type payment service available to consumer 202. Thus, the tokens may enable electronic transaction processing, including contactless payment processing through cards and / or contactless payment terminals. API calls and data processing events for establishing an account with the digital wallet in Figure 2A are further described with reference to Figures 3A and 3B below.

[0057] In diagram 200b of Figure 2B, various interactions, inputs, data communications, and / or processing operations are shown for processing payments from digital accounts in digital wallets using a payment network, such as contactless payments and BNPL or other loan payment services. In interaction 21, the contactless payment terminal 222 reads, receives, or detects a near-field radio signal and / or communication, and / or otherwise determines that a data transfer of a data token representing or acting on behalf of a card or similar data has occurred to the contactless payment terminal 222 from a contactless device or object. For example, a mobile phone may be used to request electronic transaction processing by opening a software application or website via a web browser application and transmitting data to a nearby or nearby device via near-field radio communication. The contactless payment terminal 222 may then read or receive this data and, in interaction 21, request certification for the corresponding transaction based on the read or received data transfer of other data (e.g., tokens, etc.) representing an identifier that enables payment processing using proxy card data or the application.

[0058] Certification may be requested by a payment network 224 that provides a payment network to process and resolve digital tokens between backend payment networks, processors and other frontend contactless devices and terminals, portable devices and applications, websites, digital wallet services and other, such as QUICPay® and / or iD®. In interaction 22, the payment network 224 provides the read, scanned or received proxy data, such as a token for an identifier, to a TSP 226 which can detoxify the token into another form or identifier capable of identifying the corresponding backend processor, host or system that processes the payment for the transaction. The TSP 226 detoxifies the token, such as a DPAN, into corresponding data, such as a BIN or other identifier, and in interaction 23, provides the detoxified data with transaction data to a BNPL service 228 or other computing service that processes transactions in real time and / or on a per-transaction basis for an account and provides approval or rejection of transactions. Such processing may be based on risk assessments and factors, user data and / or balances, credit or loans granted, and other factors that may be used to determine eligibility for financing and / or BNPL services and funding for a transaction.

[0059] Figures 3A and 3B are exemplary diagrams 300a and 300b of data processing calls and operations between an online transaction processor system and a digital wallet provider system when establishing and adapting a digital account to a digital wallet, according to an embodiment. Diagrams 300a and 300b in Figures 3A and 3B include API calls and data processing events from interactions between devices, servers, applications and / or systems that may be used to establish the use of a digital account, such as providing a BNPL-type payment service using a digital wallet as a means of payment. In this regard, such interactions may be performed by a user device 110, a transaction processor 120 and / or a digital wallet platform 140, as described with reference to system 100 in Figure 1.

[0060] The interaction between the user device 110, the digital wallet platform 140, and the transaction processor 120 may be used to configure a digital wallet for the use of a specific digital account as a means of payment or lending during electronic transaction processing, including contactless payment processing and systems. Initially, user 302 may utilize the BNPL application 304 to use a digital account in the BNPL payment and lending services. User 302 may also have a digital wallet 306 with a separate digital wallet platform that provides computing services via applications and websites and utilizes a wallet server 308 for processing data using backend components, servers, systems, etc. Payments may be processed via a payment network 310 that can interact with the TSP 312 for tokenization / detoxification of data, such as identifiers that can be processed by the BNPL host 314 for payment and / or transaction approval, authorization and / or payment.

[0061] In interaction 31, the BNPL application 304 first requests the primary account number (PAN) from the BNPL host 314 through an API call or request that may correspond to a primary identifier or other identifier that serves as an identifier for processing user 302's account. The BNPL application 304 further performs an eligibility check with the digital wallet 306 in interaction 32 to determine eligibility to add the account and / or BNPL payment processing service to the digital wallet 306 as a means of payment for payment processing in face-to-face and / or digital payments and transactions. This may include making API calls for eligibility checks and checks for existing routes for secure addition of the element. Thus, if the eligibility check is passed and the BNPL application 304 and / or the digital wallet 306 are able to offer the option to add the account to the wallet, user 302 selects the option to add the account to the digital wallet 306 in interaction 33, which may correspond to an API call between the BNPL application 304 and the digital wallet 306 to request that the account be added to the digital wallet 306.

[0062] Based on the request, during interaction 34, the public certificate is retrieved by lookup and encrypted for use during the account enrollment process with the digital wallet 306. The digital wallet 306 may, firstly, request the public certificate of the wallet server 308 via an API response, which may respond with the public certificate and a nonce (a random and / or non-repeating number to ensure the first or live data transfer of the public certificate). The digital wallet 306 may generate a nonce signature using the nonce and provide the nonce, nonce signature, and public certificate to the BNPL application 304. In interaction 35, the BNPL application 304 then encrypts the public certificate, nonce, and nonce signature with a PAN for the account and sends the encrypted data to the BNPL host 314.

[0063] In interaction 36, the BNPL host 314 then provides the BNPL application 304 with an API response along with encrypted data having an encrypted PAN or other identifier. The encrypted PAN may correspond to a BIN or other identifier, and the BIN / identifier may be used as a DPAN for the requested fields (e.g., FPAN, etc., which form fields when joining an account with the digital wallet 306 during account joining). The API response may further include activation data as a cryptographically used one-time password (OTP) and a temporary public key used for cryptographic operations, signaling operations and / or security. In interaction 37, the BNPL application 304 may configure the wallet server 308 for account use with the digital wallet 306 with the encrypted PAN or other identifier, the encrypted OTP or other activation data, and the temporary public key. This may correspond to setting encrypted data as data that, by mimicking proxy card data or similar proxy or provided funds or payment means (e.g., payment card), fills the requested fields for adding a payment means to an account in the digital wallet 306 as a payment means usable during electronic transaction processing. Thus, the digital wallet 306 can utilize the encrypted data set and established for payment processing, such as face-to-face payments, contactless payments, wireless payments, and / or digital payments over a network.

[0064] Referring to Figure 3B, in Diagram 300b, the operation may then complete and register and provide access to the digital account of user 302 for BNPL services through the digital wallet 306. Interaction 38 includes a data validity check for validity of use as a payment mechanism in the digital wallet, and the digital wallet 306 and wallet server 308 set up the encrypted PAN or other identifier and temporary public key for use. Interaction 39 may determine or decide on a TSP based on the BIN or other identifier used for the encrypted PAN, which may include a network check card request with the encrypted PAN and temporary public key, with TSP 312 acting as a token provider (e.g., FeliCa® TSP or others) for tokenization and detoxification procedures. TSP 312 may then check card eligibility with BNPL host 314 via an API call, which responds with a product identifier and issuer card reference identifier. Subsequently, during interaction 40, TSP312 requests agreement to the Terms and Conditions (T&Cs) provided to the digital wallet 306 and subsequently transferred or presented to user 302. User 302 agrees to the T&Cs with digital wallet 306 and activation data is sent to TSP312. During interactions 41 and 42, activation is completed, where, during interaction 41, TSP requests the digitization of encrypted data with BNPL host 314, such as through tokenization, and BNPL host 314 provides a level of confidence regarding data tokenization and / or digitization. TSP312 then issues a token in interaction 42, which is provided to digital wallet 306 for payment processing as a DPAN that can be detoxified into a BIN or other identifier relating to the digital account with digital wallet 306 from the FPAN field and / or transaction data. The digital wallet 306 then displays the successful activation of the account that has the digital wallet 306 via the BNPL application 304.

[0065] Figure 4 shows an exemplary set of user interfaces 400 for a portable device application when registering a digital account with an online transaction processor for use via a digital wallet on a separate digital wallet platform, according to an embodiment. User interfaces 400 may be displayed on a computing device including a portable smartphone or other portable devices such as the user device 110 described in Figure 1 with reference to system 100. In this regard, user interfaces 400 include separate user interfaces 402, 404, 406, 408 and 410 which may be displayed when registering and / or adapting a digital account with a digital wallet for use in payment and transaction processing.

[0066] In interface 402 of Figure 4, a software application, such as a desktop or mobile application, may present an interface that allows the user to request the addition of a payment method to a digital wallet, including a digital account with a payment service separate from the digital wallet provider. For example, the digital account may provide transaction processing and payment services via a BNPL computing service that approves transactions in real time and / or on a transaction-by-transaction basis, which may require specific actions for transaction approval at the time of the transaction and / or during the transaction processing request. Interface 402 may show "Add to Wallet Request," where the user viewing interface 402 can then select a specific payment method, such as a card, key, pass, or other account including BNPL or other digital accounts.

[0067] When a request to add a payment method is selected from interface 402, interface 404 presents BNPL account addition, where the user may select an online transaction processor for the BNPL service and account for joining and registering with their corresponding digital wallet. This may include selecting a card or account identifier that displays the account and online transaction processor and further informs the user, for example via near-field communication, that the account can be used with the digital wallet for face-to-face and / or contactless payment processing. The selection of the transaction processor proceeds to interface 406, which requests the input of identification and / or authentication credentials or other contact identifiers such as email and mobile phone numbers to complete the verification and account information. In some embodiments, a password or other confidential information may be required for account login and / or verification.

[0068] Once contact information and other verification information are entered, a two-factor or confidential information gateway may be issued to the user and / or the user's secure or verified device or contact address / account (e.g., mobile phone number and text message or email address, etc.). For example, an OTP may be requested from the user's device at interface 408, where the OTP is sent (e.g., via SMS, email, etc.) to a trusted and / or verified device or account. Interface 408 may then request the user to enter the OTP for verification. Once entered and verified, interface 410 indicates successful enrollment after proceeding with the steps and operations described above for enrolling and registering the BNPL or other digital account in the user's digital wallet. Interface 410 and / or other account or digital wallet application presenting the application may then make electronic transaction processing available through the account.

[0069] Figure 5A is a flowchart 500a of an exemplary process for establishing the use of a digital account in a digital wallet during cross-platform common data processing, according to an embodiment. One or more steps, processes and methods of flowchart 500a described herein may be omitted, performed in a different order, or combined as desired or appropriately.

[0070] In step 502, a request is received to use the account in a digital wallet hosted separately from the account. The request may be received via a software application or website of the online transaction processor providing the account, or the digital wallet platform providing the digital wallet. The request may be received after the account has been determined to be eligible and usable with the digital wallet, such as by determining the user's eligibility for access and / or payment processing using the account. For example, a user may be determined to be eligible for installment loans or loans, such as using a BNPL-type system that provides transaction-by-transaction approval and / or certification based on the user's eligibility to receive loans, lending or installment loans or other provision of credit or funds under a particular transaction.

[0071] In step 504, a public certificate associated with the digital wallet is obtained. The public certificate may be used for authenticity verification, digital signatures, encryption, and other purposes, and may also be used to verify the digital wallet provider and others for secure communication with the online transaction processor when registering and joining an account to the digital wallet. In step 506, encrypted data with a BIN that can be used to fill in the FPAN field requested by the digital wallet is obtained. The encrypted data may include identifiers for the account, such as a PAN, which can be encrypted and used as an FPAN or DPAN during tokenization and processing for payments made using the digital wallet. The encrypted data may also include, or be associated with, an OTP using cryptography, and a temporary public key, which may be provided and verified during the request.

[0072] In step 508, the encrypted data is provided to the digital wallet platform. API calls may be exchanged and processed between the platforms and systems of the online transaction processor and the digital wallet provider, where the online transaction processor may provide data for tokenization and electronic transaction processing, as well as for subsequent processing and use. In step 510, the account and BIN are identified with the backend payment processor. The online transaction processor may perform identification to prove the account and BIN or other identifiers to the payment network and to the backend payment processor and to a system including a TSP that can tokenize data. Once identified and proven, in step 512, the account is activated for use in the digital wallet using the BIN. This may enable transaction processing using the account via the digital wallet, such as for contactless payments using tokens (e.g., DPAN) related to encrypted data including the BIN or other identifiers. This requires resolution in the payment network, as described below with respect to Figure 5B.

[0073] Figure 5B is a flowchart 500b of an exemplary process for cross-platform common use of digital accounts in separate digital wallets during near-field data processing, according to an embodiment. One or more steps, processes and methods of flowchart 500b described herein may be omitted, performed in a different order, or combined as desired or appropriately.

[0074] In step 522, a request to process a transaction is received from a payment network used by the merchant equipment to resolve payment data sent via near-field communication. For example, an interaction detected between the user and the merchant with respect to an application used for electronic transaction processing may be identified, where the interaction may correspond to the data transfer of a token for a BIN or other identifier for an account. The interaction may be via near-field communication used to communicate the token via contactless and / or wireless transmission to the corresponding payment device or terminal for the merchant. The merchant's equipment may utilize a payment network and backend processors to process the received data, including detoxification of the transaction data and use of a BIN or other identifier to request authorization and payment of the transaction. The transaction may be based on user data, including financial data, historical payment and / or repayment data, credit value, etc., and merchant data, including merchant agreements on available credit levels, merchant balances and / or credit value, etc. Such data may be accessed from one or more data storage locations, computing devices, and / or others for the user and the merchant associated with such data.

[0075] In step 524, an identifier for the account used in the payment data is determined. The identifier may be determined by detoxifying the data being transmitted during contactless or near-field wireless data communication. This may be done by the TSP in the payment network used and may provide an operation to retrieve the FPAN (e.g., a BIN or other identifier provided for the account) from a set of DPANs that have a digital wallet for the account. In step 526, it is determined using the identifier that the account and that the account is registered in a digital wallet for payments via near-field wireless communication. An online transaction processor providing the account may provide an account lookup (account lookup table) and authentication operation to identify the account and determine parameters, sources of funds and / or authorization for payments to be made through the account.

[0076] In step 528, one or more risk models or rules for a transaction are executed for the installment payment loan plan. For example, transaction, user, and / or merchant data may be received for the transaction, where data, characteristics, etc., are extracted and processed by one or more transaction approval and risk engines of the online transaction processor. This may be done to determine whether the eligibility of the transaction is approved, such as relating to loans, financing, BNPL payment services, etc. In step 530, the transaction is processed in the payment network. If the transaction is approved, the payment may be processed in the network to the corresponding account of the merchant or other seller. However, if a risk model or rule rejects the transaction, the transaction may be rejected and processing may be rejected in the payment network. As a result, receipts and / or transaction history may be provided via the network to the merchant's equipment and the user's equipment and / or accounts.

[0077] In other embodiments, the system includes non-temporary memory and one or more hardware processors that are coupled to the non-temporary memory and read instructions from the non-temporary memory to detect a request to add a user's account to a digital wallet, the digital wallet being hosted by a digital wallet platform separate from the system, the digital wallet being hosted by a digital wallet platform separate from the system, the proxy wallet data relating to the user's account

[0078] In various embodiments of the above system, 1) determining proxy wallet data includes receiving an Application Programming Interface (API) response from the system's backend that generates the proxy wallet data; 2) prior to transmission of the proxy wallet data to the digital wallet platform, the proxy wallet data is encrypted using a key with cryptography associated with the digital wallet platform; 3) prior to transmission of the proxy wallet data, the operation further includes passing a request to the digital wallet platform, receiving a public digital certificate with a nonce and a digital signature by the nonce from the digital wallet platform, and providing the backend with the association with the proxy wallet data and the associated API request; 4) providing the public digital certificate to the backend involves encrypting the public digital certificate, nonce and digital signature by the nonce with the account's principal account number and providing it to the backend via the API request. The operation includes an encrypted public digital certificate, an encrypted nonce, a digital signature with the encrypted nonce, and an encrypted principal account; 5) the proxy wallet data further includes a one-time password and a temporary public key using cryptography associated with at least the payment processing service; 6) the identifier is an identification number for a financial institution associated with the near-field wireless payment processing service, the digital wallet platform requests a fund identifier for adding an account to the digital wallet, and the fund identifier is supplied using the identification number from the proxy wallet data; 7) prior to activation, the operation further includes performing an eligibility check for at least one of the users or accounts for using the account via the digital wallet, and activation is performed based on the eligibility check; 8) the operation further includes receiving a request for a transaction that uses the account to transfer a token associated with the identifier to a merchant device using near-field wireless communication, based on the digital wallet; the request isUsing a detoxified identifier from a token to route to a payment processing service associated with the system, processing a transaction involves using the account on request, including receiving, and / or 9) the payment processing service is associated with a split payment service and enables transactions on the account during payment processing via the payment processing service on a single transaction basis based on one or more risk models.

[0079] In another embodiment, the method includes receiving a request to add a user's account having an online transaction processor's payment processing service to the user's digital wallet, the digital wallet being hosted by a digital wallet platform separate from the online transaction processor; passing the request to the digital wallet platform; receiving one or more public certificates from the digital wallet platform certifying the digital wallet platform's use of the digital wallet having the user's account; generating provision data relating to the user's account based on one or more public certificates relating to the account and an account identifier, the account identifier uniquely identifying the account to the backend payment processing network during payment processing using the account through the payment processing service; and transmitting the provision data to the digital wallet platform in association with adding the account to the digital wallet for payment processing using the online transaction processor's payment processing service.

[0080] In various embodiments of the above method, 1) the request is passed along with a command to display a user interface in a software application on the user's computing device which enables adding an account to a digital wallet using the provided data; 2) one or more public certificates each have a corresponding nonce and digital signature by the nonce; 3) prior to generating, the method further includes encrypting one or more public certificates and their corresponding nonce and digital signature by the nonce together with the principal account number, and providing the encrypted one or more public certificates and their corresponding nonce and digital signature by the nonce to a host system relating to an online transaction processor; 4) the provided data is generated based on the provided data, the account identifier is encrypted in the provided data, and / or 5) the payment processing service includes a Buy Now, Pay Later (BNPL) payment processing service (deferred payment processing service) which activates the transaction relating to the account during payment processing in the transaction at the time of the transaction based on one or more risk models.

[0081] In yet another embodiment, a non-temporary machine-readable medium stores machine-readable instructions that cause a machine to perform actions including: receiving a request to add a user's account with a payment processing service to a digital wallet hosted separately from the payment processing service; providing the request to an online platform associated with the digital wallet; receiving a digital certificate from the online platform that verifies the online platform while the digital wallet with the account is in use; determining encrypted data relating to the user's account using the digital certificate, wherein the encrypted data includes an account identifier that uniquely identifies the account to a backend payment processing network using the payment processing service for payment processing; transmitting the encrypted data to the digital wallet platform in association with the request; and activating the account in the user's digital wallet.

[0082] In various embodiments of the non-temporary machine-readable medium described above, 1) prior to activation, the operation further includes identifying the account and account identifier to the backend payment processing network with respect to a request to add the account to the digital wallet, and ensuring that the device account number is associated with the account in the user's digital wallet with respect to the use of the payment processing service, so that the device account number is used and associated during payment processing by the payment processing service via detoxification to a fund account number associated with the account identifier; 2) the operation further includes ensuring that the device account number is stored in association with the account that has the digital wallet; and / or 3) the encrypted data further includes activation data, which includes at least a one-time password and a temporary public key using cryptography associated with the payment processing service.

[0083] Figure 6 is a block diagram of a computer system 600 suitable for implementing one or more components of Figure 1 according to an embodiment. In various embodiments, the communication device may include a personal computing device capable of communicating with a network (e.g., a smartphone, a computing tablet, a personal computer, a laptop computer, a wearable computing device such as glasses or a wristwatch, a Bluetooth device, a key fob, a badge, etc.). The service provider may utilize a network computing device capable of communicating with a network (e.g., a network server). It is understood that each of the devices used by the user and the service provider may be implemented as computer system 600 in the following ways.

[0084] The computer system 600 includes a bus 602 or other communication mechanisms for communicating information data, signals, and information between various components of the computer system 600. The components include an input / output (I / O) component 604 that processes user actions such as selecting keys from a keypad / keyboard, selecting one or more buttons, images, or links, and / or moving one or more images, and also sends corresponding signals to the bus 602. The I / O component 604 may also include a display device 611 and cursor control 613 (e.g., keyboard, keypad, mouse, etc.). An optional voice input / output component 605 may also be included to enable the user to input information using their voice by converting voice signals. The voice I / O component 605 may enable the user to hear voice. A transceiver or network interface 606 transmits and receives signals over the network 150 between the computer system 600 and other devices such as other communication devices, service devices, or service provider servers. In one embodiment, transmission is wireless, and other transmission media and methods may also be appropriate. One or more processors 612, which may be a microcontroller, a digital signal processor (DSP), or other processing component, process these various signals for purposes such as display on the computer system 600 or transmission to other devices via the communication link 618. The processors 612 may also control the transmission of information such as cookies or IP addresses to other devices.

[0085] The components of the computer system 600 also include a system memory component 614 (e.g., RAM), a static storage component (storage) 616 (e.g., ROM), and / or a disk drive 617. The computer system 600 performs specific operations by the processor 612 and other components by executing one or more sequences of instructions contained in the system memory component 614. The logic may be encoded in a computer-readable medium that can refer to any medium that participates in providing instructions to the processor 612 for execution. Such a medium can take various forms, non-exclusively including non-volatile mediums, volatile mediums, and transmission mediums. In various embodiments, non-volatile mediums include optical or magnetic disks, volatile mediums include dynamic storage devices such as the system memory component 614, and transmission mediums include coaxial cables, copper wires, and optical fibers, including wires including a bus 602. In one embodiment, the logic is encoded in a non-temporary computer-readable medium. In one embodiment, the transmission medium may take the form of acoustic waves or optical waves, such as those generated during radio wave data communication, optical data communication, and infrared data communication.

[0086] Some common forms of computer-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tapes, and any other magnetic media, CD-ROMs, and any other optical media, punch cards, paper tapes, and any other physical media having a pattern of holes, RAM, PROMs, EEPROMs, FLASH-EEPROMs, and any other memory chips or cartridges, or any other media that a computer can read.

[0087] In various embodiments of the Disclosure, the execution of instruction sequences for implementing the Disclosure may be performed by a computer system 600. In various other embodiments of the Disclosure, multiple computer systems 600 connected by a communication link 618 to a network (e.g., a network including LANs, WLANs, PTSNs, and / or various other wired or wireless telecommunications networks, mobile networks, and cell phone networks) may work together to execute instruction sequences for implementing the Disclosure.

[0088] Where applicable, the various embodiments provided in this disclosure may be implemented using hardware, software, or a combination of hardware and software. Where applicable, the various hardware and / or software components disclosed herein may be combined, without departing from the spirit of this disclosure, to form a composite component comprising software, hardware, and / or both. Where applicable, the various hardware and / or software components disclosed herein may be separated, without departing from the spirit of this disclosure, to form subcomponents comprising software, hardware, or both. In addition, where applicable, a software component may be implemented as a hardware component, and vice versa.

[0089] According to this disclosure, software, such as program code and / or data, may be stored in one or more computer-readable media. It is also conceivable that the software identified herein may be implemented using one or more general-purpose or specific-purpose computers and / or computer systems in networked and / or other forms. Where applicable, the order of the various steps described herein may be changed, combined into composite steps, and / or separated into substeps to provide the features disclosed herein.

[0090] The foregoing disclosure is not intended to limit the disclosure to the disclosed form or to any particular field of use. Therefore, various alternative embodiments and / or modifications to the disclosure, whether expressly or implicitly expressed herein, are possible in light of the disclosure. Those skilled in the art will understand that such embodiments of the disclosure may be modified in form and detail without departing from the scope of the disclosure. Thus, the disclosure is limited only by the claims.

Claims

1. It is a system, Non-temporary memory, and One or more hardware processors, coupled to the non-temporary memory, and reading instructions from the non-temporary memory to the system, Receiving a request from the payment processing network for processing a transaction using an account, the request being received in response to the merchant device receiving a data transfer of proxy wallet data via near-field wireless communication, From the above request, determine an identifier that uniquely identifies the account in the payment processing network, wherein the identifier is usable to enable the payment processing service using the account, and the identifier has been previously detoxified from the tokens of the proxy wallet data. Based on the identifier, it is determined that the account will be registered in a digital wallet hosted by a digital wallet platform separate from the system, and that the data transfer will be performed using the digital wallet. Identifying the aforementioned account and the available payment balance for said account, and The payment processing network, based on the aforementioned request and the available payment balance, processes the transaction with respect to the account and the merchant equipment that uses the payment processing service, The system includes the hardware processor that causes the operation to be performed.

2. The system according to claim 1, The proxy wallet data is based on the system, which mimics digital wallet data from readings from a short-range wireless transceiver of a portable device, and the proxy wallet data is based on the identifier, a one-time password using cryptography associated with at least the payment processing service, and a temporary public key.

3. The system according to claim 2, Prior to receiving the request relating to processing the transaction, the operation further: To detect a request to add the account to the digital wallet, To determine the proxy wallet data with respect to the aforementioned account, and To transmit the proxy wallet data to the digital wallet platform in association with the request to add the account to the digital wallet. The system including the above.

4. The system according to claim 3, Prior to sending the proxy wallet data, the operation further: To pass the request to the digital wallet platform for adding the account, Receiving a public digital certificate with a nonce and a digital signature by the nonce from the digital wallet platform, and To provide the system's processor with respect to the proxy wallet data, to provide the public digital certificate, the nonce, and the API request associated with the digital signature by the nonce, The system including the above.

5. The system according to claim 3, Prior to receiving the request relating to processing the transaction, the operation further: Identifying the account associated with the payment processor in the payment processing network, In the aforementioned digital wallet, the device account number is associated with the identifier, and Activating the payment processing service relating to the account based on the device account number with respect to the digital wallet and the payment processor, The system including the above.

6. The system according to claim 1, The aforementioned account is authorized only for per-transaction payments when used via the aforementioned digital wallet, in the system.

7. The system according to claim 1, The merchant device includes a merchant point-of-sale (POS) device which includes a communication module which includes at least one of an RFID reader, an NFC reader, a Bluetooth transceiver, or a Wi-Fi transceiver, wherein the communication module is used for the near-field wireless communication which utilizes interchangeable tokens for processing via the payment processing network.

8. The system according to claim 1, Prior to processing the aforementioned transaction, the operation further: Activating a risk engine that includes at least a machine learning (ML) based risk model or a rule-based risk rule set using the aforementioned transactions and accounts, and The determination of whether the transaction meets the risk assessment requirements based on the results of the activation of the transaction. The system including the above.

9. The system according to claim 8, The aforementioned operation further, Based on the determination of whether the transaction meets the risk assessment requirements, to generate one of the approval or rejection of the transaction, and The system includes processing one of the aforementioned approval or rejection at the merchant device via the payment processing network.

10. The system according to claim 8, The system wherein the payment processing service is associated with an installment payment service, and uses the risk engine to activate a transaction relating to the account through the payment processing service for each individual transaction, the available payment balance is associated with a time-period loan repayment plan from the installment payment service with respect to the account, and the risk engine activates the transaction in the time-period loan repayment plan.

11. It is a method, Receiving a request from a payment processor on a payment network for processing a transaction using an account having the online transaction processor, wherein the request includes an identifier that uniquely identifies the account having the online transaction processor on the payment network, and the request is detoxified from a token generated by the merchant device based on data received by the merchant device via near-field communication on a portable device. Based on the identifier, it is determined that a digital wallet hosted by a digital wallet platform separate from the online transaction processor was used by the portable device on the merchant device via the near-field communication. Identifying the account and the available sources of funds for the account based on the identifier, Based on the fact that the digital wallet is separate from the online transaction processor, determine a payment processing service that enables the processing of the transaction on the merchant device and the digital wallet platform, and The method, which includes performing one or more operations of the payment processing services based on the transaction and the available source of funds.

12. The method according to claim 11, further, The method, which includes processing the transaction relating to the merchant device in the payment network through one or more operations of the payment processing service based on the request and the available source of funds.

13. The method according to claim 12, Prior to processing the aforementioned transaction, the method further: Operate a risk engine that includes at least one of either a rule-based model or a machine learning (ML)-based model. Based on the results of the aforementioned operation, determine the risk assessment of the transaction for the account using the available source of funds, and The risk assessment determines whether it meets the risk threshold for the certification. The method, including the method described above.

14. The method according to claim 11, The method, wherein one or more of the aforementioned operations include at least one of the following: a user authentication operation, an ML risk assessment operation, a rule-based risk assessment operation, an available balance query for the account, a future balance forecast for the account, or installment payment loan certification for payments associated with the transaction.

15. The method according to claim 11, further, The determination that the transaction does not meet the risk assessment determined using a risk engine that performs one or more of the aforementioned actions, and The method includes refusing to process the transaction via the payment network.

16. The method according to claim 11, The payment processing service includes a deferred payment (BNPL) service that certifies the transaction at the time of the request for processing the transaction via near-field communication based on one or more risk models.

17. The method according to claim 11, Prior to receiving the aforementioned request, the method further Generating the data relating to the account based on one or more public certificates and the identifier relating to the account, and Sending the data to the digital wallet platform, along with a request to add the account to the digital wallet for payment processing using the payment processing service of the online transaction processor. The method, including the method described above.

18. A non-temporary machine-readable medium, which can be used by machines. Receiving payment requests from the payment processing network for transactions that have identifiers relating to accounts with online transaction processors, The payment processing network determines that the transaction was generated by the merchant device in response to receiving a data transfer of a token associated with the identifier from a portable device using a digital wallet associated with the account via near-field wireless communication, and that the merchant device detoxifies the token and uses the detoxified token to route the identifier to the online transaction processor for payment processing services. Determining the identifier from the payment request, wherein the identifier uniquely identifies and determines the account for processing the payment via the payment processing service of the online transaction processor. Identifying the account and the available payment balance relating to the account based on the request and the identifier relating to the account, Based on the identifier, it is determined that the digital wallet was used to generate the payment request using the data transfer via the near-field wireless communication, and that the digital wallet is hosted by a digital wallet platform separate from the online transaction processor, and A non-temporary machine-readable medium storing machine-readable instructions that can be executed to perform an action including performing the payment processing service that processes the transaction using the account.

19. A non-temporary machine-readable medium according to claim 18, The aforementioned operation further, The identifier is stored by the digital wallet platform in association with the account in the digital wallet, wherein the identifier is associated with an identification number relating to a financial institution associated with a payment process using the short-range wireless communication having a wireless terminal relating to the merchant equipment. The non-temporary machine-readable medium, including the above.

20. A non-temporary machine-readable medium according to claim 19, The identifier is stored in the non-temporary machine-readable medium along with a one-time password and a temporary public key using cryptography associated with at least the payment processing service of the online transaction processor.

Images