A real-time third-party payment system accepts payments to a lender from third-party merchants in real-time. The payment system may receive real-time payment information from the third-party, and various services within the payment system validate the customer account information, create a payment, store the payment in a database, and post the payment to a real-time ledger. The payment system may also receive an end-of-day file including file-based payment information. The file-based payment information may be verified against the real-time payments stored in the database. Upon validation, the payment system creates a file based payment and posts the file-based payment to a file-based ledger. The payment system may detect fraud, errors, and other discrepancies in real-time payments and make corrections based on settlement rules and self-healing rules provided by the third-party.

Disclosed are various embodiments for frictionless payment. A computing device obtains a document with native format transaction data from a merchant device, and determines a bill based at least in part on the native format transaction data and a trained predictive model. The computing device determines payment methods available for payment of the bill via a client device. The computing device generates a network page that can cause payment of the bill to be initiated by one of the payment methods that is unassociated with a user providing payment card information or personal information to the merchant, and transmit an indication to the merchant device that the bill was paid.

A central computer system transforms identification information of a consumer into an identity code that hides the identification information and stores it with contact information of a consumer's computer system. When a computer system on the network of the central computer system conducts a transaction with a subject who uses the identity code of the consumer, the central computer system contacts the consumer's computer system so that the consumer can stop the transaction if it is not authorized. Because only the identity code is used to protect the consumer, the original identification information of the consumer is fully protected.

A vehicle diagnostic system and method utilizing a plurality of diagnostic data corpuses. A first corpus comprises conventional and well-known diagnostic data useful in a broad range of common service tasks. A second corpus comprises less well-known diagnostic data useful in less common service tasks. One or more specialty corpuses may comprise obscure, protected, or emerging diagnostic data for the last-common tasks specific to particular manufacturers of the vehicle or its components. The second corpus and one or more specialty corpuses may offer access only to users that have acquired sufficient authorization.

A matching system that matches a first vehicle requiring substitution when being at least either loaded into or unloaded from a parking place and a remote driver driving the first vehicle as a substitute through remote operation includes a terminal and a server. The terminal transmits substitution request information to the server. The server that has received the request information transmits waiting time information to the terminal. The terminal notifies a user or a staff of the received waiting time information, accepts a waiting time information approval or additional fee payment instructions, and settles the additional fee through cooperation with the server, upon receiving the payment instructions. The server changes the turn of the first vehicle in a queue for the remote operation service such that the first vehicle is prioritized more than a second vehicle that has not paid the additional fee, upon completing the additional fee settlement.

A method of processing a settlement includes setting a chatroom for interaction with a payment method; and sending payment details using the payment method to the chatroom and sharing the payment details with a member participating in the chatroom.

A computer-implemented method for generating and maintaining shared ledgers for sub-merchant onboarding includes receiving a request from a payment facilitator to onboard a sub-merchant, receiving information about the sub-merchant from the payment facilitator or the sub-merchant, providing the information about the sub-merchant to a third party, receiving underwriting information corresponding to the information about the sub-merchant from the third party, generating an onboarding decision based on the information about the sub-merchant and the underwriting information, storing the information about the sub-merchant, the underwriting information, and the onboarding decision to a shared ledger, and generating and transmitting an electronic offer of a product or a service to the sub-merchant based on the stored contents of the shared ledger.

Computer-implemented methods, non-transitory, computer-readable media, and computer-implemented systems for blockchain-based payment withholding and agreement signing are described. In one computer-implemented method, an agreement signing transaction submitted by a user is received and used to authorize a payment system to provide a payment withholding service for a payment order of the user in a third-party service system. The agreement signing transaction includes agreement signing information of a tripartite agreement submitted by the user. Withholding verification logic declared in a first smart contract published on the blockchain is invoked to check whether there is a withholding agreement signed between the payment system and the third-party service system on the blockchain. If yes, the tripartite agreement is created that authorizes the payment system to provide the payment withholding service for the payment order for the user and published to the blockchain for certificate storage.

A computer-implemented method and system that operates on a server includes a time and expense management interface for obtaining crew specific information for crews maintaining a utility distribution system. The server is coupled to a wireless communication infrastructure for receiving crew specific information. A portable electronic device receives a selection of a crew with members. The portable electronic device receives the identifier of the at least one or more members of the crew. Once verified, the portable device receives time entries and expense entries, for the at least one or more members of the crew. Business rules are applied to the time entries and expense entries. Once the business rules are satisfied, the time entries and expense entries are stored on the portable electronic device. When the portable electronic device is in proximity to the wireless communication infrastructure, the crew specific information is transmitted to server.

A system for integrating third-party software components with point of sale (POS) systems includes a memory and a processor in communication therewith. The processor deploys a POS adapter on a POS system. The POS adapter configures a framework for the POS system, interacts with transaction data generated by the POS system, generates an API request based on the first configured framework, accesses a façade gateway based on the API request, and receives one or more responses to the first API request from the façade gateway. The façade gateway translates the API request to be interpretable by the third-party software components, transmits the translated API request to the third-party software components, receives a response to the API request from the third-party software components, translates the response to be interpretable by the POS adapter, and transmits the translated response to the POS adapter such that it is executable by the POS system.