Systems and methods for managing electronic tip recommendations on mobile devices
Abstract
The disclosed embodiments provide systems, methods, and techniques for managing merchandising cards. A merchandising card may be, for example, a gift card, loyalty card, or the like. Consistent disclosed embodiments, a system for managing merchandising cards may include one or more memory devices storing instructions and one or more processors configured to acquire, from a device over a network, a plurality of locations associated with the device, the device locations being acquired at different instances in time within a predetermined period of time. Additionally, the processor may be configured to calculate a merchant confidence rating for a merchant using the device locations. Further, the one or more processors may be configured to, based on the merchant confidence rating, determine that the merchant matches a merchant that is associated with merchandising card, and send a reminder a user of the device.
Claims
exact text as granted — not AI-modified1 - 9 . (canceled)
10 . A server for providing a tip recommendation, the server comprising:
one or more memory devices storing instructions; and one or more processors configured to execute the stored instructions to:
determine that a transaction account has been used in connection with a transaction to pay an amount to a merchant; and
determine that a customer device has been enabled to receive a notification;
in response to the determination that the transaction account has been used and that the customer device has been enabled to receive the notification:
send a notification to the customer device; and
determine, based on a merchant category code, whether it is customary that tips are accepted by the merchant; and
if it is determined that it is customary that tips are accepted by the merchant:
determine a default tip parameter based on a machine learning algorithm, the machine learning algorithm being configured to receive as inputs at least one of historical tipping data of the customer, historical tipping data of the merchant, or a date of the transaction;
determine a tip recommendation based on the default tip parameter; and
send, to the customer device, data comprising the first tip recommendation, wherein sending the data to the customer device causes the customer device to alter the notification.
11 . The server of claim 10 , wherein the processor is further configured to execute instructions to:
receive a request to change the first tip recommendation based on a customer input, the request comprising a second tip recommendation; and send, to the customer device, data comprising the second tip recommendation, wherein sending the data to the customer device causes the customer device to replace the first tip recommendation with the second tip recommendation.
12 . The server of claim 10 , wherein the processor is further configured to execute instructions to:
receive a request to change the first tip recommendation based on a customer input, the request comprising a second tip recommendation; and modify the notification by replacing the first tip recommendation with the second tip recommendation.
13 . (canceled)
14 . The server of claim 10 , wherein the processor is further configured to execute instructions to:
determine the default tip parameter further based on historical tipping data of the customer.
15 . The server of claim 10 , wherein the processor is further configured to execute instructions to:
determine the default tip parameter further based on historical tipping data of the merchant.
16 . (canceled)
17 . The server of claim 10 , wherein the notification is represented by at least one of a text message, a push notification, an email message, a voice message, or a video message.
18 . The server of claim 10 , wherein the processor is further configured to execute instructions to:
save the first tip recommendation; receive a final transaction amount from the merchant, wherein the final transaction amount comprises a final tip amount; compare the final tip amount to the first tip recommendation; determine whether the final tip amount matches the first tip recommendation; and save the determination of whether the final tip amount matches the first tip recommendation.
19 . The server of claim 18 , wherein the processor is further configured to execute instructions to:
determine the default tip parameter based on a machine learning algorithm, wherein the machine learning algorithm receives as input the saved determination of whether the final tip amount matches the first tip recommendation.
20 . An electronic system for providing a tip recommendation, the electronic system comprising:
one or more memory devices storing instructions; and one or more processors configured to execute the stored instructions to:
determine that a transaction account has been used in connection with a transaction to pay an amount to a merchant; and
determine that a customer device has been enabled to receive a notification;
in response to the determination that the transaction account has been used and that the customer device has been enabled to receive the notification:
determine, based on a merchant category code, whether it is customary that tips are accepted by the merchant; and
if it is determined that it is customary that tips are accepted by the merchant:
determine a default tip parameter based on a machine learning algorithm, the machine learning algorithm being configured to receive as inputs at least one of historical tipping data of the customer, historical tipping data of the merchant, or a date of the transaction;
determine a tip recommendation based on the default tip parameter; and
display a notification, the notification comprising the first tip recommendation.
21 . The electronic system of claim 20 , wherein the processor is further configured to execute instructions to:
receive a request to change the first tip recommendation based on a customer input, the request comprising a second tip recommendation; and send, to a customer device, data comprising the second tip recommendation, wherein sending the data to the customer device causes the customer device to replace the first tip recommendation with the second tip recommendation.
22 . The electronic system of claim 20 , wherein the processor is further configured to execute instructions to:
receive a request to change the first tip recommendation based on a customer input, the request comprising a second tip recommendation; and modify the notification by replacing the first tip recommendation with the second tip recommendation.
23 . (canceled)
24 . The electronic system of claim 20 , wherein the processor is further configured to execute instructions to:
determine the default tip parameter further based on historical tipping data of the customer.
25 . The electronic system of claim 20 , wherein the processor is further configured to execute instructions to:
determine the default tip parameter further based on historical tipping data of the merchant.
26 . (canceled)
27 . The electronic system of claim 20 , wherein the notification is represented by at least one of a text message, a push notification, an email message, a voice message, or a video message.
28 . The electronic system of claim 20 , wherein the processor is further configured to execute instructions to:
store the first tip recommendation; receive a final transaction amount from the merchant, wherein the final transaction amount comprises a final tip amount; compare the final tip amount to the first tip recommendation; determine whether the final tip amount matches the first tip recommendation; and store the determination of whether the final tip amount matches the first tip recommendation.
29 . The electronic system of claim 28 , wherein the processor is further configured to execute instructions to:
determine the characteristic based on a machine learning algorithm, wherein the machine learning algorithm receives the stored determination of whether the final tip amount matches the first tip recommendation.Join the waitlist — get patent alerts
Track US2019220837A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.