Embodiments are directed to a method comprising, obtaining, by a first device, a first token, the first token associated with an amount of funds and a funds availability starting date. After the first token is obtained by the first device, the first device generates a second token linked to the first token and second token generation data. The second token generation data may include evidence that the second token was generated by the first device, and not another device. The second token generation data could be a first device identifier and the second token generation details, or could be a hashed value of the first device identifier and the second token generation details. The method also includes provisioning, by the first device, the second token and the second token generation data to the second device.

A computer-implemented method includes providing, by one or more processing devices, a service code management interface; receiving, by the one or more processing devices, a specified quantity that is input by a user in the service code management interface; generating, by the one or more processing devices, the specified quantity of service codes, wherein the specified quantity of service codes comprise the same user identification information; and displaying, by the one or more processing devices, the specified quantity of service codes.

A method for tokenizing non-payment identifier, comprising storing a plurality of account profiles, wherein each account profile is a structured data set related to a transaction account including at least a non-payment identifier, at least one of a personal account number (PAN), and quantity of points affiliated with the non-payment identifier. Receiving a data signal from a consumer communication device, wherein the data signal may be superimposed with a tokenization request, the tokenization request including at least a non-payment identifier. Provisioning, by a generation module of the processing server, a token linking to the non-payment identifier. Transmitting, by a transmitting device of the processing server, the token linked to the non-payment identifier to the consumer communication device.

According to an approach for processing image data at network sites, a user invokes functionality on a client device, a scanning device, or a multi-function peripheral (MFP) to cause one or more printed receipts to be scanned to generate image or scan data. The scan data is transmitted by the client device or the MFP to a receipt data management system that maintains access data for a plurality of users and sites. The sites each include a graphical user interface that allows users to manually renter receipt data and request the generation of receipt data processing results. The receipt data management system manages the processing of the receipt data by a specified site on behalf of the user to generate receipt data processing results that satisfy third party requirements. This includes satisfying any authentication requirements of the specified site.

A computer-implemented method and system for providing IT support on demand. The computer-implemented method includes presenting a chat session to the customer through a user interface thereby connecting a customer to a job evaluator to create a ticket. Further, the computer-implemented method includes sending a customer's job quote, the job quote includes a service order with a price estimate. Furthermore, the computer-implemented method includes allowing the customer to schedule an appointment with the job evaluator. Moreover, the computer-implemented method also includes establishing one of a remote support type and an onsite support type to the customer to solve one or more issues. The computer-implemented method includes permitting the customer to rate the job evaluator in response to completing the job, wherein a reduced rating initiates a new job evaluator to fix the one or more issues.

A cross-blockchain data processing method is provided. The method includes: obtaining an asset transfer instruction triggered for a first asset on the first blockchain, and configuring an asset state of the first asset to a locked state on the first blockchain; determining the first asset in the locked state as an asset, and determining a cross-chain asset transfer request corresponding to the asset; obtaining an asset transfer interface associated with a second blockchain, and calling the asset transfer interface to transmit the cross-chain asset transfer request to a second server node on the second blockchain; and receiving signing response information transmitted by the second server node in response to determining that the verification succeeds, freezing the asset on the first blockchain according to the signing response information, and notifying the second server node to release a second asset associated with the asset on the second blockchain.

A method for a secure check of an electronic ticket, in which the electronic ticket is stored on a first mobile terminal device allocated to an end consumer, and the ticket is checked using a second terminal device allocated to a ticket inspector or to a control system, wherein the method the following steps: sending a request message from the second terminal device to the first terminal device via a first communication channel; sending a response message from the first terminal device to the second terminal device via a second communication channel, the response message being signed by the first terminal device, and the second communication channel; verifying the signed response message by the second terminal device; and confirming the authenticity of the response message by the second terminal device, if the second terminal device was previously able to verify the authenticity of the signature.

A method of registering a ticket medium for use of a transport service, including detecting, by a validator device of a transit system, at least one electronic medium identifier of an unregistered ticket medium used for a use of the transport service, transmitting an identification data set containing at least the detected electronic medium identifier to a computing device that generates and outputs a billing data set based at least on the transmitted electronic identification data set, wherein the billing data set contains at least one transaction identifier associated with the used transport service. At least the transaction identifier is associated to the electronic medium identifier and the association is stored. The computing device receives at least one registration message containing at least the transaction identifier of the output billing data set and determines the electronic medium identifier based on at least the at least one stored association and the transaction identifier of the received registration message. Registering the unregistered ticket medium by creating a user data set containing at least the determined electronic medium identifier.

A system is provided as a computer server platform and application programming software installed in primary devices of users for exchanging and trading digital asset securely and anonymously between two users of the system. The digital asset is registered under a device account of a primary device of a user with the system using a unique device account name. The system respects “privacy by design” in GDPR by using device account based-on anonymized data instead of personal account based-on personal data of prior art to ensure the system does not collect, store and process users' personal data in the course of device accounts' set-up and transactions of digital assets.

Systems and methods for facilitating use of physical tokens in a transit system are disclosed. In one implementation, a method for facilitating use of physical tokens by a server includes generating a token identifier and generating, using a private key associated with the server, a cryptographic signature based on the token identifier. The method further includes transmitting the token identifier and the cryptographic signature to a token dispenser. The token dispenser is configured to dispense a physical token, and the physical token is configured to provide the token identifier and the cryptographic signature to a token validator. The method also includes receiving, from the token dispenser, (i) a first indication that the physical token is dispensed, (ii) selection of a fare type, and (iii) dispenser context data including a dispense location, associating the token identifier with the selected fare type and the dispenser context data, and receiving, from the token validator, a second indication that the physical token is being validated. The second indication (i) is transmitted after the token validator verifies the cryptographic signature using a public key associated with the server, and (ii) includes the token identifier provided by the physical token and validator context data including a validation location. Furthermore, the method includes identifying the fare type associated with the token identifier, accessing, based on the fare type, a set of restrictions governing use of the physical token, and determining whether the physical token is valid based on (i) the accessed set of restrictions, (ii) the validator context data associated with the token identifier provided by the physical token, and (iii) the dispenser context data received from the token validator. Moreover, the method includes transmitting a communication to the ticket validator indicating whether the physical token is valid, wherein the ticket validator, in response to receiving the communication, outputs an indicator whether the physical token is valid.