A computer-implemented method for allowing purchase of virtual gift cards includes receiving a communication indicating a gift card type and specifying a value amount. Responsive to the communication, a purchase of a virtual gift card of that type and storing that value amount is processed. This processing includes processing a payment for the specified value amount. Further, a gift card merchant application programming interface (API) capable of processing a purchase of a virtual gift card of the indicated gift card type is identified from amongst a set of such APIs. That API is used to initiate purchase of the virtual gift card. After the purchase is processed, an indication of the purchased virtual gift card is sent to a mobile computing device. The mobile computing device uses the indication to configure itself to allow transactions using the purchased virtual gift card to be initiated. Fraud detection may also be performed.

In one embodiment, a receipt server includes an acquisition unit and an output unit. The acquisition unit acquires receipt data on a commercial transaction, identified by transaction identification information included in settlement sales data reported from a settlement terminal to a settling agent that assists settlement of the commercial transaction, from a receipt storage unit that stores receipt data generated by the settlement terminal at a time of settlement of the commercial transaction. The output unit outputs information, relating to a purchased commercial product included in the receipt data acquired by the acquisition unit to a settlement server of the settling agent.

A system and method to conduct secure electronic financial transactions are provided. The method includes receiving a request, from a user, to perform a transaction with a merchant; generating a virtual check comprising a checking account number, a bank routing number, and a date; displaying the virtual check on at least one of a display of an electronic device of a user or the merchant; receiving input from the user corresponding to at least one of a plurality of check fields; receiving a virtual signature from the user; encrypting the virtual signature; storing the encrypted virtual signature in a database; decrypting and embedding, in the image of the virtual check, the virtual signature received from the user; populating the virtual check based on the received input and depositing the virtual check.

Systems as described herein generate an outstanding check alert. An alert generating server may receive transaction records associated with a plurality of checking accounts. The alert generating server may user a first machine learning classifier to determine a transaction pattern indicating a merchant has failed to process outstanding checks for a period of time. The alert generating server may receive sequential check information comprising at least one missing check number associated with a particular checking account. The alert generating server may user a second machine learning classifier to determine at least one outstanding check associated with the particular checking account. The alert generating server may send an alert indicating the at least one outstanding check to a user device.

An exemplary method comprises receiving information associated with a game-playing transaction conducted between a user device and a game-playing terminal, wherein the game-playing transaction is associated with a request for playing a game; determining a location of the user device associated with the game; determining the user device is located in an approved location associated with the game; and processing the game-playing transaction based on determining the user device is located in the approved location associated with the game. The game-playing transaction is conducted on a first communication interface, and the information associated with the game-playing transaction is received on a first or second communication interface.

The present application discloses a method of issuing pseudonymous authorisation tickets to nodes of a cooperative ITS, for signing messages, comprising: receiving a ticket request from a node in an authorisation server, and sending a validation request to an enrolment server, conducting a validity check in the enrolment server, and, when the validity check is passed, incrementing a counter value of a counter assigned to an account at an account server enrolled with the enrolment server for the requesting node, sending a validation message to the authorisation server, and issuing a pseudonymous authorisation ticket from the authorisation server to the requesting node, repeating the aforementioned steps until a predetermined charging period expires, and, upon expiry, sending, from the enrolment server to the authorisation server, said counter value, and sending a charging request calculated from said counter value from the authorisation server to the account server for charging said account.

Techniques are described herein for selecting an optimal financial account for a financial transaction. In an embodiment, a multi-account payment card is used to initiate a financial transaction. Transaction information of the financial transaction including a multi-account payment card ID is transmitted to a server for processing. The server determines that the multi-account payment card ID is associated with a plurality of financial accounts, wherein each of the plurality of financial accounts is associated with any one of a credit card, a debit card, an automatic teller machine (ATM) card, a gift card, or a credit line. A financial account of the plurality of financial accounts is selected by the server based on financial account information, such as reward information, associated with the plurality of financial accounts and the transaction information of the financial transaction. The financial transaction is then charged to the selected financial account.

A device may receive first information related to a transaction. The device may identify a first device from which to receive an image of a receipt related to the transaction. The device may provide, to the first device, a notification to cause the first device to perform a set of actions including activating a camera associated with the first device to capture the image of the receipt, or providing, for display, an instruction related to capturing the image of the receipt associated with the transaction. The device may receive, from the first device, the image of the receipt. The device may process the image of the receipt to perform an analysis of the transaction. The device may perform an action related to the transaction based on a result of processing the image of the receipt.

Aspects described herein may provide determination of a pedestrian route for a user to reach a seating area inside of a venue. Financial transaction data of the user may be reviewed to determine the user purchased one or more tickets to an event at the venue. Information regarding the event or the venue may be determined including seating charts for the venue and whether the tickets are for assigned or unassigned seats. Crowd densities inside and outside of the venue may be determined. The pedestrian route may be determined based on the crowd densities, number of tickets, and type of seating. The route may be updated as conditions change including any change to the crowd densities or change to seating availability. The route may increase a likelihood that the user reaches the seating area prior to a start of the event, and in a less stressful manner.

A device, system and method for mode-based synchronization of data records is provided. Booking data is received, at one or more computing devices, from one of a first and second client device. When received from the first client device, in a first order mode for the booking data, the device(s): cause an order management system (OMS) to generate: order data at a first database; and cause a legacy system to generate a corresponding passenger name record (PNR) at a second database, the corresponding PNR being slaved to the order data. When received from the second client device, in a legacy mode for the booking data, the device(s): cause the legacy system to generate, a PNR and/or ticket data at the second database; and cause the OMS to generate corresponding order data at the first database, the corresponding order data being slaved to the PNR and/or the ticket data.