Ca, Inc.

Talisma Corporation Private Ltd.

Sharath Lakshman Kumar

Mahesh Malatesh Chitragar

Stephen Prasad

Vishwanatha Salian

Mohammed Mujeeb Kaladgi

Aneesh Bhatnagar

Rajendra Pachouri

Pradeep G Nair

Arun Shetty

Deepak Dhondaley Satyanarayana

Vinay Narasimhamurthy

Dhivya Kalyanasundaram

Sanjay Rai

Methods, server, devices and registered terminals for requiring approval of toll charges are provided. A server receives, from a fixed communication device at a toll booth location, a tollway transponder identifier of a vehicle tollway transponder on a vehicle. The server determines whether a registered terminal is associated with the tollway transponder identifier. Responsive to determining that the registered terminal is associated with the tollway transponder identifier, a toll approval request message is transmitted to the registered terminal, which sends a response message back to the server. The server determines if a location of the registered terminal is within a defined distance from the toll booth location. Responsive to the location of the registered terminal being within the defined distance, the server triggers a toll charge against an account associated with the tollway transponder identifier when the response message indicates approval of the toll.

Toll booth added security to code scanner

A method includes receiving a security profile comprising user-defined rules for processing sensitive data, and identifying a plurality of sensitive data components in a data file according to the security profile. The method further includes generating a respective format-preserving token for each of the identified plurality of sensitive data components. The method additionally includes generating a corresponding token key for each of the respective-format preserving tokens, and replacing each of the plurality of sensitive data components in the data file with the respective format-preserving token. Further, the method includes cryptographically camouflaging each of the token keys using a first password and storing each of the cryptographically camouflaged token keys.

Restricting access to sensitive data using tokenization

A restriction request message, including a restriction parameter for a secondary account, is received from a device that is associated with a primary account, via a network node that is outside of a secure authorization network. A replenishment request message, including a password and an account replenishment parameter for the secondary account, is also received via a network node that is outside of the authorization network. Authentication is performed based on the password, and the restriction parameter for the secondary account is identified responsive to receiving the replenishment request message. Responsive to determining that the account replenishment parameter satisfies the restriction parameter, a replacement key is generated and associated with the account replenishment parameter for the secondary account. A replenishment response message including the replacement key is transmitted to a device that is associated with the secondary account, via a network node that is outside of the authorization network.

Restricting account use by controlled replenishment

A method for preventing mobile payment is described. The method comprises generating an authorization request, via a payment module, based on sensitive data on a mobile device. The authorization request is transmitted from the payment module to an issuer system. The issuer system sends a neutralization trigger. In response to receiving the neutralization trigger, the payment module is disabled.

System for preventing mobile payment

Provided are systems and methods for operating a mobile device of a first user that may include accessing a data repository to retrieve a first location of a future event scheduled at an event time to be attended by the first user and a second user, obtaining, from a position determination circuit of the mobile device, a second location of the mobile device, initiating transmission of a query to a route server to responsively obtain a time of arrival message including an arrival time for the first user to arrive at the first location from the second location, and, responsive to a difference in the arrival time and the event time exceeding a threshold duration, initiating transmission of a notification message that triggers a change in attendees that are physically present at the first location of the event without altering the event time of the event.

Automating notifications for modification of events based on geographic positioning

A method for preventing mobile payment is described. The method comprises receiving an authorization request at an issuer system from a payment module on a mobile device. The authorization request may be based on sensitive data on the mobile device. The issuer system determines whether the mobile device is missing. The issuer system sends a neutralization trigger to the mobile device, and in response to receiving the neutralization trigger, the payment module is disabled.

System and method of neutralizing mobile payment

Methods of de-tokenizing secure payment tokens are disclosed. A method according to some embodiments includes receiving a request from an issuer to de-tokenize a secure payment token associated with a transaction conducted using a mobile terminal, generating a metric indicative of a risk of de-tokenizing the secure payment token, comparing the metric indicative of the risk of de-tokenizing the secure payment token to a predetermined threshold, and transmitting a response to the request to de-tokenize the secure payment token, wherein the response is based on the comparison of the metric indicative of the risk of de-tokenizing the secure payment token with the predetermined threshold.

Payment de-tokenization with risk evaluation for secure transactions

A method to adjust the colors of skin of a graphical user interface (GUI) of a customer relationship management (CRM) application based upon a color scheme of an operating system is provided. In the method, a color code of the color scheme of an operating system is fetched from a registry entry of the operating system and is saved as a base color. This color code is converted from ARGB format to RGB format and further converted from RGB format to HSL format. Different luminance values are set for various elements of the CRM application to provide different brightness and legibility to different elements of the GUI. The modified color code is converted back to RGB format and assigned to various pixels of GUI skin whereby the CRM application is rendered with new color scheme similar to that of the operating system.

Growing community of inventors

Bengaluru, India

Sharath Lakshman Kumar