Interface widget tool for automatic QR code generation and display without application launching
There are provided systems and methods for an interface widget tool for automatic QR CODE® generation and display without application launching. A user may engage in a transaction with another user, such as a purchase of goods, services, or other items a merchant at a merchant location using machine-readable codes. A machine-readable code may be provided via a mobile device of a user. In order to provide faster and more efficient code generation, an interface widget or other tool may be provided, which, on selection, may execute API calls to a server of a transaction processor. The transaction processor may generate a code without requiring the user to go through a code generation and processing flow in a corresponding application. The code may be limited in validity and may be presented via the widget. Once scanned, the code may provide encoded data for a financial instrument.
1 . A system comprising:
a non-transitory memory; and
one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising:
detecting, via one or more processes of a first software development kit (SDK) for an application on a mobile device of a user, an activation of a code widget on the mobile device, wherein the activation comprises bringing the code widget to a foreground of a home screen interface on the mobile device independent of opening or executing the application;
determining, in response to the activation independent of a user input and an approval in the application, a first machine-readable code of a plurality of machine-readable codes displayable by the mobile device, wherein the first machine-readable code provides data for electronic transaction processing when the first machine-readable code is scanned;
generating the first machine-readable code using a digital token associated with an account of the user;
receiving an application programming interface (API) call from the one or more processes of the first SDK for the first machine-readable code for a transaction being processed via the code widget;
connecting with the application using the one or more processes of the first SDK;
transmitting the first machine-readable code to the application on the mobile device, wherein receiving the first machine-readable code by the application causes the first machine-readable code to be loaded in the code widget from the first SDK;
detecting a first scan performed by a merchant device of the first machine-readable code using a second SDK for a sales application on the merchant device, wherein the first scan is detected as being performed in association with the transaction being processed at the merchant device;
initiating, independent of interacting with the mobile device, a transaction processing request for the transaction directly with the merchant device via one or more API calls exchanged with the sales application using the second SDK;
validating the first scan of the first machine-readable code, wherein the validating comprises:
executing a risk analysis of the transaction based on a plurality of parameters associated with an analysis of the account associated with the digital token, a condition for an expiration of the first machine-readable code, and whether a previous scan of the first machine-readable code has occurred;
providing an event in the application on the mobile device using the first SDK based on the transaction processing request using the first machine-readable code, wherein the event indicates at least the first scan by the merchant device;
determining whether to process the transaction processing request using the account based on the validating;
providing an animation via the mobile device indicating a result of the transaction processing request using the first SDK; and
updating the code widget in the home screen interface, wherein the updating the code widget includes replacing the first machine-readable code with a second machine-readable code.
2 . The system of claim 1 , wherein the risk analysis is further based on information for the merchant device.
3 . The system of claim 2 , wherein the risk analysis is further based on at least one of mobile device data or a history for the account.
4 . The system of claim 1 , wherein the first machine-readable code comprises a quick response (QR) code, and wherein the QR code is limited for an amount of time and a single scan of the QR code.
5 . The system of claim 1 , wherein subsequent to the detecting the first scan, the operations further comprise:
detecting a second scan of the first machine-readable code; and
rejecting processing a transaction associated with the second scan based on the first scan.
6 . The system of claim 1 , wherein the operations further comprise:
invalidating the first machine-readable code after the expiration, wherein the updating is in response to one of a further request by the mobile device or an automatic generation decision by the system based on the invalidating.
7 . The system of claim 1 , wherein the first machine-readable code is generated based on a location of the mobile device, and wherein the condition for the expiration is associated with the location.
8 . The system of claim 1 , wherein, after the detecting the first scan, the operations further comprise:
determining encoded data in the first machine-readable code based on the first scan; and
determining the account associated with the encoded data, wherein the account is utilized to process the transaction processing request.
9 . The system of claim 1 , wherein the activation is detected by the system based on an application programming interface (API) request from the mobile device to the system from the code widget without having a user approval via the application, and wherein the activation comprises a launching of the code widget.
10 . The system of claim 1 , wherein the merchant device is configured with a development kit that executes API calls with the system, and wherein the detecting the first scan comprises receiving the transaction processing request in response to the first scan via the development kit.
11 . A method comprising:
detecting, via one or more processes of a first software development kit (SDK) for an application on a mobile device of a user, a use of a code widget on the mobile device, wherein the use comprises bringing the code widget to a foreground of a home screen interface on the mobile device independent of opening or executing the application;
determining, in response to the use independent of the user requesting a generation of a first machine-readable code in the application, a first machine-readable code displayable by the mobile device via the code widget, wherein the first machine-readable code provides data for electronic transaction processing when the first machine-readable code is scanned;
generating the first machine-readable code using a digital token associated with an account of the user;
receiving an application programming interface (API) call from the one or more processes of the first SDK for the first machine-readable code for a transaction being processed via the code widget;
connecting with the application using the one or more processes of the first SDK;
transmitting the first machine-readable code to the application on the mobile device, wherein receiving the first machine-readable code by the application causes the first machine-readable code to be loaded in the code widget from the first SDK;
detecting a first scan performed by a merchant device of the first machine-readable code using a second SDK for a sales application on the merchant device, wherein the first scan is detected as being performed in association with the transaction being processed at the merchant device;
initiating, independent of interacting with the mobile device, a transaction processing request for the transaction directly with the merchant device via one or more API calls exchanged with the sales application using the second SDK;
validating the first scan of the first machine-readable code, wherein the validating comprises:
executing a risk analysis of the transaction based on a plurality of parameters associated with an analysis of the account associated with the digital token, a condition for an expiration of the first machine-readable code, and whether a previous scan of the first machine-readable code has occurred;
providing an event in the application on the mobile device using the first SDK based on the transaction processing request using the first machine-readable code, wherein the event indicates at least the first scan by the merchant device;
determining whether to process the transaction processing request using the account based on the validating;
providing an animation via the mobile device indicating a result of the transaction processing request using the first SDK; and
updating the code widget in the home screen interface, wherein the updating the code widget includes replacing the first machine-readable code with a second machine-readable code.
12 . The method of claim 11 , wherein the risk analysis is further based on information for the merchant device.
13 . The method of claim 12 , wherein the risk analysis is further based on at least one of mobile device data or a history for the account.
14 . The method of claim 11 , wherein the first machine-readable code comprises a quick response (QR) code, and wherein the QR code is limited for an amount of time and a single scan of the QR code.
15 . The method of claim 11 , wherein subsequent to the detecting the first scan, the method further comprises:
detecting a second scan of the first machine-readable code; and
rejecting processing a transaction associated with the second scan based on the first scan.
16 . The method of claim 11 , further comprising:
invalidating the first machine-readable code after the expiration, wherein the updating is in response to one of a further request by the mobile device or an automatic generation decision based on the invalidating.
17 . The method of claim 11 , wherein the first machine-readable code is generated based on a location of the mobile device, and wherein the condition for the expiration is associated with the location.
18 . The method of claim 11 , wherein, after the detecting the first scan, the method further comprises:
determining encoded data in the first machine-readable code based on the first scan; and
determining the account associated with the encoded data, wherein the account is utilized to process the transaction processing request.
19 . The method of claim 11 , wherein the use is detected based on an application programming interface (API) request from the mobile device without having a user approval via the application, and wherein the use comprises a launching of the code widget.
20 . A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:
detecting, via one or more processes of a first software development kit (SDK) for an application on a mobile device of a user, an activation of a code widget on the mobile device, wherein the activation comprises bringing the code widget to a foreground of a home screen interface on the mobile device independent of opening or executing the application;
determining, in response to the activation independent of a user input and an approval in the application, a first machine-readable code of a plurality of machine-readable codes displayable by the mobile device, wherein the first machine-readable code provides data for electronic transaction processing when the first machine-readable code is scanned;
generating the first machine-readable code using a digital token associated with an account of the user;
receiving an application programming interface (API) call from the one or more processes of the first SDK for the first machine-readable code for a transaction being processed via the code widget;
connecting with the application using the one or more processes of the first SDK;
transmitting the first machine-readable code to the application on the mobile device, wherein receiving the first machine-readable code by the application causes the first machine-readable code to be loaded in the code widget from the first SDK;
detecting a first scan performed by a merchant device of the first machine-readable code using a second SDK for a sales application on the merchant device, wherein the first scan is detected as being performed in association with the transaction being processed at the merchant device;
initiating, independent of interacting with the mobile device, a transaction processing request for the transaction directly with the merchant device via one or more API calls exchanged with the sales application using the second SDK;
validating the first scan of the first machine-readable code, wherein the validating comprises:
executing a risk analysis of the transaction based on a plurality of parameters associated with an analysis of the account associated with the digital token, a condition for an expiration of the first machine-readable code, and whether a previous scan of the first machine-readable code has occurred;
providing an event in the application on the mobile device using the first SDK based on the transaction processing request using the first machine-readable code, wherein the event indicates at least the first scan by the merchant device;
determining whether to process the transaction processing request using the account based on the validating;
providing an animation via the mobile device indicating a result of the transaction processing request using the first SDK; and
updating the code widget in the home screen interface, wherein the updating the code widget includes replacing the first machine-readable code with a second machine-readable code.