Abstract: An authentication application may receive, from a merchant application of a client device, a merchant identifier, a transaction identifier of a transaction, encrypted data, and a location of the client device. The authentication application may decrypt the encrypted data based at least in part on a private key. The authentication application may determine that the contactless card has been used to make a previous purchase with the merchant and that the location of the client device is within a threshold distance of a known location associated with a contactless card. A virtual account number generator may generate a virtual account number and transmit the merchant identifier, the transaction identifier, the virtual account number, an expiration date, and a card verification value (CVV) to a merchant server associated with the merchant to process the transaction using the transaction identifier, the virtual account number, the expiration date, and the CVV.

Abstract: Embodiments may be generally directed to techniques, systems, and devices to control settings stored on contactless cards.

Abstract: An authenticated data sharing system may include a contactless card comprising a processor and a memory including one or more applets and an application comprising instructions for execution on a device. The application is configured to determine a capability associated with the contactless card after a first entry into a communication field. The application is configured to request additional information based on the determination. The one or more applets are configured to transmit, to the application, a generated tokenized link after a second entry into the communication field based on the requested additional information. The application is configured to transmit the link to obtain the requested additional information.

Abstract: Account registration using a contactless card. A payment application executing on a device may receive a request to generate a payment account using a contactless card. The payment application may receive encrypted data from the contactless card and transmit the encrypted data to a server associated with the contactless card. The device may receive a push notification from the server and open an account application associated with the contactless card responsive to selection of the push notification. The account application may receive confirmation to generate the payment account using the contactless card and transmit the confirmation to the server. The device may open the payment application responsive to receiving verification of the encrypted data from the server. The payment application may fill form fields with account data received from the server and generate the payment account using the account data received from the server filled into the form fields.

Abstract: An authenticated data sharing system may include a contactless card comprising a processor and a memory including one or more applets and an application comprising instructions for execution on a device. The application is configured to determine a capability associated with the contactless card after a first entry into a communication field. The application is configured to request additional information based on the determination. The one or more applets are configured to transmit, to the application, a generated tokenized link after a second entry into the communication field based on the requested additional information. The application is configured to transmit the link to obtain the requested additional information.

Abstract: Account registration using a contactless card. A payment application executing on a device may receive a request to generate a payment account using a contactless card. The payment application may receive encrypted data from the contactless card and transmit the encrypted data to a server associated with the contactless card. The device may receive a push notification from the server and open an account application associated with the contactless card responsive to selection of the push notification. The account application may receive confirmation to generate the payment account using the contactless card and transmit the confirmation to the server. The device may open the payment application responsive to receiving verification of the encrypted data from the server. The payment application may fill form fields with account data received from the server and generate the payment account using the account data received from the server filled into the form fields.

Abstract: A rating may be received for a user based on a stay at a lodging establishment, the rating comprising a positive attribute and a negative attribute. The rating may be based on data entered by a user of the lodging establishment and programmatically generated data. An overall rating may be generated based on the rating and a plurality of prior ratings for the user. A request to reserve a second stay at the lodging establishment may be received. A price for the second stay at the lodging establishment may be received. A reduced price for the second stay may be determined based on the overall rating for the user being above a threshold rating. An indication of the reduced price may be outputted for display. A dwelling unit in the lodging establishment for the second stay may be reserved at the reduced price.

Abstract: Account registration using a contactless card. A payment application executing on a device may receive a request to generate a payment account using a contactless card. The payment application may receive encrypted data from the contactless card and transmit the encrypted data to a server associated with the contactless card. The device may receive a push notification from the server and open an account application associated with the contactless card responsive to selection of the push notification. The account application may receive confirmation to generate the payment account using the contactless card and transmit the confirmation to the server. The device may open the payment application responsive to receiving verification of the encrypted data from the server. The payment application may fill form fields with account data received from the server and generate the payment account using the account data received from the server filled into the form fields.

Abstract: A rating may be received for a user based on a stay at a lodging establishment, the rating comprising a positive attribute and a negative attribute. The rating may be based on data entered by a user of the lodging establishment and programmatically generated data. An overall rating may be generated based on the rating and a plurality of prior ratings for the user. A request to reserve a second stay at the lodging establishment may be received. A price for the second stay at the lodging establishment may be received. A reduced price for the second stay may be determined based on the overall rating for the user being above a threshold rating. An indication of the reduced price may be outputted for display. A dwelling unit in the lodging establishment for the second stay may be reserved at the reduced price.

Abstract: Systems and methods for debt prevention are disclosed. The system retrieves customer data for a customer and identifies account spending patterns from the customer data. The system also identifies current purchases from the customer data and compares the current purchases to the previous account spending patterns to determine an unusual spending pattern and/or an unusual purchase. The system further compares previous and current bill pay patterns from the customer data to determine a bill payment deviation. Next, the system compares previous and current customer engagement to determine any unusual customer engagement. The system then calculates a predicted payment risk based on any unusual customer engagement, unusual purchases, unusual spending patterns, and/or bill payment deviation. The system then determines one or more remediation tasks based on the payment risk and sends a request to the customer to choose and/or perform the desired remediation task.

Abstract: A rating may be received for a user based on a stay at a lodging establishment, the rating comprising a positive attribute and a negative attribute. The rating may be based on data entered by a user of the lodging establishment and programmatically generated data. An overall rating may be generated based on the rating and a plurality of prior ratings for the user. A request to reserve a second stay at the lodging establishment may be received. A price for the second stay at the lodging establishment may be received. A reduced price for the second stay may be determined based on the overall rating for the user being above a threshold rating. An indication of the reduced price may be outputted for display. A dwelling unit in the lodging establishment for the second stay may be reserved at the reduced price.

Abstract: An authentication application may receive, from a merchant application of a client device, a merchant identifier, a transaction identifier of a transaction, encrypted data, and a location of the client device. The authentication application may decrypt the encrypted data based at least in part on a private key. The authentication application may determine that the contactless card has been used to make a previous purchase with the merchant and that the location of the client device is within a threshold distance of a known location associated with a contactless card. A virtual account number generator may generate a virtual account number and transmit the merchant identifier, the transaction identifier, the virtual account number, an expiration date, and a card verification value (CVV) to a merchant server associated with the merchant to process the transaction using the transaction identifier, the virtual account number, the expiration date, and the CVV.

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.