Automatic synchronization of a device for transaction processing based on geo-fenced locations
There are provided systems and methods for automatic synchronization of a device for transaction processing based on geo-fenced locations. A merchant may geo-fence an area corresponding to the merchant's location where a user may visit to purchase an item. The merchant may provide multiple transaction processing and payment options at the merchant location, including payment applications with a mobile communication device. A payment provider may detect the location of the user and determine that the user's location matches the merchant's location through the geo-fenced area for the merchant. The payment provider may then configure a payment process for the user to utilize at the merchant location using payment mechanisms accepted at the merchant location. Where multiple merchants are located nearby, the payment provider may utilize additional known information for the user to select the most likely merchant for the user.
1. A system, comprising:
a non-transitory memory comprising instructions; and
one or more hardware processors coupled to the non-transitory memory and configured to read the instructions to cause the system to perform operations comprising:
detecting that a user is located within a first geo-fenced area based on a GPS locator of a user device of the user or based on a determination that the user device has performed a check-in with a merchant, wherein the merchant corresponds to the first geo-fenced area;
in response to detecting that the user is located within the first geo-fenced area:
identifying merchant data of the merchant;
determining, based on the merchant data, a payment acceptance mechanism of a plurality of payment acceptance mechanisms that is supported by a corresponding physical merchant device of the merchant;
alerting the user that the payment acceptance mechanism can be used to process a transaction with the corresponding physical merchant device;
automatically filling information of the merchant into a payment application executing on the user device; and
the payment application processing the transaction.
2. The system of claim 1 , the operations further comprising determining that the user is allowed to transact with the merchant based on identifying a past transaction conducted between the user and the merchant.
3. The system of claim 1 , wherein the payment acceptance mechanism is a quick response (QR) code, and wherein the alerting includes causing the payment application to display the QR code.
4. The system of claim 1 , wherein the operations further comprise causing the payment application to communicate with the corresponding physical merchant device over a short-range wireless communication to provide an electronic tokenized payment to the corresponding physical merchant device.
5. The system of claim 4 , wherein the operations further comprise: transmitting, in response to the detecting that the user is located within the first geo-fenced area, an alert to the merchant, the alert informing that the user is at a location of the merchant.
6. The system of claim 1 , the operations further comprising:
loading user information of the user onto the corresponding physical merchant device, wherein the user information includes a payment token or information corresponding to a payment instrument of the user.
7. The system of claim 1 , the operations further comprising:
providing an offer to the user device for use at a location of the merchant based on determining that the user is located within the first geo-fenced area.
8. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:
detecting that a user is located within a first geo-fenced area based on a GPS locator of a user device of the user or based on a determination that the user device has performed a check-in with a merchant, wherein the merchant corresponds to the first geo-fenced area;
in response to detecting that the user is located within the first geo-fenced area:
identifying merchant data of the merchant;
determining, based on the merchant data, a payment acceptance mechanism of a plurality of payment acceptance mechanisms that is supported by a corresponding physical merchant device of the merchant;
alerting the user that the payment acceptance mechanism can be used to process a transaction with the corresponding physical merchant device; and
automatically filling information of the merchant into a payment application executing on the user device; and
the payment application processing the transaction.
9. The non-transitory machine-readable medium of claim 8 , the operations further comprising determining that the user is allowed to transact with the merchant based on identifying a past transaction conducted between the user and the merchant.
10. The non-transitory machine-readable medium of claim 8 , wherein the payment acceptance mechanism is a quick response (QR) code, and wherein the alerting includes causing the payment application to display the QR code.
11. The non-transitory machine-readable medium of claim 8 , wherein the operations further comprise causing the payment application to communicate with the corresponding physical merchant device over a short-range wireless communication to provide an electronic tokenized payment to the corresponding physical merchant device.
12. The non-transitory machine-readable medium of claim 8 , wherein the operations further comprise: transmitting, in response to the detecting that the user is located within the first geo-fenced area, an alert to the merchant, the alert informing that the user is at a location of the merchant.
13. A method, comprising:
detecting that a user is located within a first geo-fenced area based on a GPS locator of a user device of the user or based on a determination that the user device has performed a check-in with a merchant, wherein the merchant corresponds to the first geo-fenced area;
in response to detecting that the user is located within the first geo-fenced area:
identifying merchant data of the merchant;
determining, based on the merchant data, a payment acceptance mechanism of a plurality of payment acceptance mechanisms that is supported by a corresponding physical merchant device of the merchant;
alerting the user that the payment acceptance mechanism can be used to process a transaction with the corresponding physical merchant device; and
automatically filling information of the merchant into a payment application executing on the user device; and
the payment application processing the transaction.
14. The method of claim 13 , further comprising determining that the user is allowed to transact with the merchant based on identifying a past transaction conducted between the user and the merchant.
15. The method of claim 13 , wherein the payment acceptance mechanism is a quick response (QR) code, and wherein the alerting includes causing the payment application to display the QR code.
16. The method of claim 13 , further comprising causing the payment application to communicate with the corresponding physical merchant device over a short-range wireless communication to provide an electronic tokenized payment to the corresponding physical merchant device.
17. The method of claim 13 , further comprising:
transmitting, in response to the detecting that the user is located within the first geo-fenced area, an alert to the merchant, the alert informing that the user is at a location of the merchant.
18. The method of claim 13 , further comprising:
loading user information of the user onto the corresponding physical merchant device, wherein the user information includes a payment token or information corresponding to a payment instrument of the user.
19. The method of claim 13 , further comprising:
providing an offer to the user device for use at a location of the merchant based on determining that the user is located within the first geo-fenced area.
20. The method of claim 15 , wherein the corresponding physical merchant device comprises a scanner that scans the QR code.