Abstract: Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include receiving from the first computing device an indication of a financial service account associated with the first computing device, detecting a payment field in a web page provided by the computing device through the web browser application and, in response, generating a secure token mapped to the financial service account.

Abstract: Example embodiments of systems and methods for data transmission system between transmitting and receiving devices are provided. In an embodiment, each of the transmitting and receiving devices can contain a master key. The transmitting device can generate a diversified key using the master key, protect a counter value and encrypt data prior to transmitting to the receiving device, which can generate the diversified key based on the master key and can decrypt the data and validate the protected counter value using the diversified key.

Abstract: The disclosed embodiments include a mobile client device for automatically performing a mobile financial service function, including a memory storing software instructions, the software instructions including a mobile financial service application configured to perform financial service processes. The system may also include and one or more processors configured to execute the software instructions to detect a physical action performed on the mobile client device, and determine a first financial service function to perform based on the detected physical action, wherein the first financial service function is a function provided by the mobile financial service application. The one or more processors may also determine whether verification of a user is required, verify the user if verification of the user is required, and automatically initiate the first financial service function.

Abstract: Embodiments of a smart card and systems and methods for secure data access using a smart card are described. The smart card may be formed a substrate and may include a microprocessor, a memory containing an applet, a counter, and a unique identifier. The smart card may dynamically generate a unique uniform resource location (URL) and transmit the URL to via a contactless communication interface to securely facilitate data access from other devices.

Abstract: One-tap payment using a contactless card. An application may output an indication specifying to tap a contactless card to complete a transaction initiated in the application. The application may receive encrypted data generated by the contactless card based on a private key stored in the contactless card. The application may transmit a merchant identifier, a transaction identifier, and the encrypted data to an authentication server. The authentication server may verify the encrypted data based on the private key for the contactless card stored by the authentication server. A virtual account number server may generate a virtual account number. A merchant server may receive the merchant identifier, the transaction identifier, the virtual account number, an expiration date, and a card verification value (CVV), and process the transaction using the transaction identifier, the virtual account number, the expiration date, and the CVV.

Abstract: Systems and methods are provided for managing electronic tokens for device interactions. In some embodiments, a unified graphical user interface is provided for an account, for controlling the activation status and settings associated with authorized electronic devices used for conducting transactions on the account. The electronic devices may be programmed with an electronic token that allows a server to look up sensitive account information, although the electronic token does not divulge the account information itself. Therefore, if an electronic token is compromised or stolen, the account does not need to be closed, and sensitive information remains safe. Moreover, the unified graphical user interface provides detailed and highly customizable controls for settings and restrictions associated with each of the electronic tokens, without modifying or accessing sensitive account or personal information.

Abstract: Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include receiving from the first computing device an indication of a financial service account associated with the first computing device, detecting a payment field in a web page provided by the computing device through the web browser application and, in response, generating a secure token mapped to the financial service account.

Abstract: A first application may output a form comprising payment fields. An operating system (OS) may receive, from a contactless card, a uniform resource locator (URL) comprising encrypted data. A second application received from the URL by the OS may be executed. The second application may transmit the encrypted data to an authentication server, the authentication server to verify the encrypted data. The second application may receive, from a virtual account number server, a virtual account number, an expiration date associated with the virtual account number, and a CVV associated with the virtual account number. The second application may provide the virtual account number, expiration date, and CVV to an autofill service of the OS. The autofill service of the OS may autofill the virtual account number the payment fields of the first application.

Abstract: Disclosed embodiments include methods, systems, and computer-readable media configured to provide wearable devices storing tokens associated with digital versions of physical documents/cards. The wearable devices may further transfer tokens securely to interested parties without Bluetooth® or other network connectivity beyond NFC radio. In some embodiments, a token vault operator system may receive a request to establish a token vault account for a user, authenticate an identity of the user based at least on the received request, and generating a token vault ID associated with the user. The token vault operator system may further configure access to data sets generated for and associated with the token vault ID, generate tokens associated with the token vault ID, each token corresponding to one of the one or more data sets, and provide the generated plurality of tokens associated with the token vault ID to at least one user device.

Abstract: Systems and methods are provided for managing electronic tokens for device interactions. In some embodiments, a unified graphical user interface is provided for an account, for controlling the activation status and settings associated with authorized electronic devices used for conducting transactions on the account. The electronic devices may be programmed with an electronic token that allows a server to look up sensitive account information, although the electronic token does not divulge the account information itself. Therefore, if an electronic token is compromised or stolen, the account does not need to be closed, and sensitive information remains safe. Moreover, the unified graphical user interface provides detailed and highly customizable controls for settings and restrictions associated with each of the electronic tokens, without modifying or accessing sensitive account or personal information.

Abstract: A system and method for generating a user customized order interface, which displays a customer's previous orders and corresponding specific order information and order recommendations, that may be utilized for ordering and payment. A mobile application may request a merchant ID upon determination by the mobile device that a customer is within a close proximity of a particular merchant location. A payment terminal may pass the corresponding merchant ID to a transaction system, which may retrieve, for example, the customer's previous transactions and corresponding transaction IDs associated with the merchant ID, which may be utilized to generate a user customized order interface, which may be utilized to initiate a transaction by selecting a specific order item to order, and which may utilize the mobile application to confirm the order and proceed to payment, which will transmit the order to a merchant system.

Abstract: Disclosed embodiments include methods, systems, and computer-readable media configured to provide wearable devices storing tokens associated with digital versions of physical documents/cards. The wearable devices may further transfer tokens securely to interested parties without Bluetooth® or other network connectivity beyond NFC radio. In some embodiments, a token vault operator system may receive a request to establish a token vault account for a user, authenticate an identity of the user based at least on the received request, and generating a token vault ID associated with the user. The token vault operator system may further configure access to data sets generated for and associated with the token vault ID, generate tokens associated with the token vault ID, each token corresponding to one of the one or more data sets, and provide the generated plurality of tokens associated with the token vault ID to at least one user device.

Abstract: Systems and methods are provided for managing electronic tokens for device interactions. In some embodiments, a unified graphical user interface is provided for an account, for controlling the activation status and settings associated with authorized electronic devices used for conducting transactions on the account. The electronic devices may be programmed with an electronic token that allows a server to look up sensitive account information, although the electronic token does not divulge the account information itself. Therefore, if an electronic token is compromised or stolen, the account does not need to be closed, and sensitive information remains safe. Moreover, the unified graphical user interface provides detailed and highly customizable controls for settings and restrictions associated with each of the electronic tokens, without modifying or accessing sensitive account or personal information.

Abstract: Disclosed embodiments include methods, systems, and computer-readable media configured to, for example, provide payment tokens for conducting transactions, as well as reprovisioning tokens, on wearable devices without Bluetooth® or other network connectivity beyond NFC radio.

Abstract: A system and method for generating a user customized order interface, which displays a customer's previous orders and corresponding specific order information and order recommendations, that may be utilized for ordering and payment. A mobile application may request a merchant ID upon determination by the mobile device that a customer is within a close proximity of a particular merchant location. A payment terminal may pass the corresponding merchant ID to a transaction system, which may retrieve, for example, the customer's previous transactions and corresponding transaction IDs associated with the merchant ID, which may be utilized to generate a user customized order interface, which may be utilized to initiate a transaction by selecting a specific order item to order, and which may utilize the mobile application to confirm the order and proceed to payment, which will transmit the order to a merchant system.

Abstract: The present invention relates to a door member (1) for mounting to a vehicle door (43). The door member (1) is moulded from a plastics material. The door member (1) includes a door seal mounting channel (3) for receiving a mounting portion (19) of a door seal (13). The door seal mounting channel (3) has first and second sidewalls (5, 7). A first projection (11) is optionally provided on the first sidewall (5) for engaging the mounting portion (19) of the door seal (13). The invention also relates to a door member (101) having an inner finisher (165) and an outer finisher (147). The invention further relates to a vehicle door (43) including a door member (1; 101) of the type described herein.

Abstract: Systems and methods are provided for managing electronic tokens associated with an account. A system may include a memory storing instructions and account information associated with an account, and a processor configured to executed the stored instructions to: access information associated with one or more electronic tokens associated with the account, wherein the information includes one or more token settings, receive, via a network, information for a transaction request including a first token; analyze the received information to determine whether at least one rule in the one or more token settings is violated, responsive to a determination that at least one rule is violated, transmit an indication that the transaction request is denied, and responsive to a determination that no rules are violated, detokenize the transaction request.

Abstract: Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include receiving from the first computing device an indication of a financial service account associated with the first computing device, detecting a payment field in a web page provided by the computing device through the web browser application and, in response, generating a secure token mapped to the financial service account.

Abstract: Systems and methods are provided for managing electronic tokens for device interactions. In some embodiments, a unified graphical user interface is provided for an account, for controlling the activation status and settings associated with authorized electronic devices used for conducting transactions on the account. The electronic devices may be programmed with an electronic token that allows a server to look up sensitive account information, although the electronic token does not divulge the account information itself. Therefore, if an electronic token is compromised or stolen, the account does not need to be closed, and sensitive information remains safe. Moreover, the unified graphical user interface provides detailed and highly customizable controls for settings and restrictions associated with each of the electronic tokens, without modifying or accessing sensitive account or personal information.

Abstract: Disclosed embodiments include methods, systems, and computer-readable media configured to provide wearable devices storing tokens associated with digital versions of physical documents/cards. The wearable devices may further transfer tokens securely to interested parties without Bluetooth® or other network connectivity beyond NFC radio. In some embodiments, a token vault operator system may receive a request to establish a token vault account for a user, authenticate an identity of the user based at least on the received request, and generating a token vault ID associated with the user. The token vault operator system may further configure access to data sets generated for and associated with the token vault ID, generate tokens associated with the token vault ID, each token corresponding to one of the one or more data sets, and provide the generated plurality of tokens associated with the token vault ID to at least one user device.