INTEGRATION FOR PERFORMING ACTIONS WITHOUT ADDITIONAL AUTHORIZATION REQUESTS

1 .- 20 . (canceled)

21 . A computer-implemented method comprising:

causing a payment application to launch on a user device of a user;

based on an interaction with a first interactive element of a user interface of the payment application, causing a website of a merchant to load to an in-app browser within the payment application, wherein the website is rendered as a web view within the payment application;

presenting, via a second user interface of the user device, a second interactive element on a checkout page of the website, wherein selection of the second interactive element is associated with use of the payment application as a form of payment, of one or more forms of payment, for a transaction with the merchant;

determining that the second interactive element has been selected;

presenting, via a third user interface of the user device, a third interactive element associated with a confirmation of user intent to use the payment application, wherein selection of the third interactive element generates a payment request for a payment to the merchant from a user account associated with the payment application;

receiving, via the in-app browser, the payment request associated with initiating the payment to the merchant from the user account;

responsive at least in part to receiving the payment request, determining that the payment request originated from within the payment application and is associated the user account; and

causing, based at least in part on determining that the payment request originated from within the payment application, the payment to be authorized without additional input from the user.

22 . The computer-implemented method of claim 21 , further comprising:

causing an indication that the payment has been authorized to be presented on the website within the in-app browser based at least in part on the payment having been authorized.

23 . The computer-implemented method of claim 21 , further comprising:

causing a checkout process to proceed via the website within the in-app browser based at least in part on the payment having been authorized.

24 . The computer-implemented method of claim 21 , wherein causing the payment to be authorized comprises:

accessing user data associated with the user; and

causing a checkout process to be completed, without user intervention, via the website based at least in part on the user data.

25 . The computer-implemented method of claim 21 , further comprising:

receiving, via the user device, an access request to access the payment application, wherein the access request is associated with data to authenticate the user,

wherein, upon authentication the user is authorized to use the user account associated with the payment application for making payments, and

wherein causing the payment to be authorized is based at least in part on the data.

26 . The computer-implemented method of claim 21 , further comprising:

receiving touch data corresponding to touch input received via a display of the user device,

wherein determining that the second interactive element has been selected is based at least in part on receiving the touch data.

27 . The computer-implemented method of claim 21 , wherein the additional input from the user comprises at least one of:

input provided to another application launched on the user device based on a deep link;

entry of a one-time passcode via the user device;

multi-factor authentication input provided via the user device; or

entry of user credentials via the user device.

28 . The computer-implemented method of claim 21 , wherein the first interactive element is associated with an offer, by a payment service associated with the payment application, awarded based on completion of the transaction with the merchant.

29 . The computer-implemented method of claim 21 , wherein the user interface includes an input element comprising a search field, search entry box, or search bar, wherein the input element is configured to accept user input to submit a search query for a particular merchant of a plurality of merchants with corresponding websites accessible via the in-app browser.

30 . One or more non-transitory computer-readable media storing instructions executable by one or more processors that, when executed by the one or more processors, cause the one or more processors to perform acts comprising:

causing a payment application to launch on a user device of a user;

based on an interaction with a first interactive element of a user interface of the payment application, causing a website of a merchant to load to an in-app browser within the payment application, wherein the website is rendered as a web view within the payment application;

presenting, via a second user interface of the user device, a second interactive element on a checkout page of the website, wherein selection of the second interactive element is associated with use of the payment application as a form of payment, of one or more forms of payment, for a transaction with the merchant;

determining that the second interactive element has been selected;

presenting, via a third user interface of the user device, a third interactive element associated with a confirmation of user intent to use the payment application, wherein selection of the third interactive element generates a payment request for a payment to the merchant from a user account associated with the payment application;

receiving, via the in-app browser, the payment request associated with initiating the payment to the merchant from the user account;

responsive at least in part to receiving the payment request, determining that the payment request originated from within the payment application and is associated the user account; and

causing, based at least in part on determining that the payment request originated from within the payment application, the payment to be authorized without additional input from the user.

31 . The one or more non-transitory computer-readable media of claim 30 , the acts further comprising:

causing an indication that the payment has been authorized to be presented on the website within the in-app browser based at least in part on the payment having been authorized.

32 . The one or more non-transitory computer-readable media of claim 30 , the acts further comprising:

causing a checkout process to proceed via the website within the in-app browser based at least in part on the payment having been authorized.

33 . The one or more non-transitory computer-readable media of claim 30 , the acts further comprising:

receiving, via the user device, an access request to access the payment application, wherein the access request is associated with data to authenticate the user,

wherein, upon authentication the user is authorized to use the user account associated with the payment application for making payments, and

wherein causing the payment to be authorized is based at least in part on the data.

34 . The one or more non-transitory computer-readable media of claim 30 , the acts further comprising:

receiving touch data corresponding to touch input received via a display of the user device,

wherein determining that the second interactive element has been selected is based at least in part on receiving the touch data.

35 . A system comprising:

one or more processors; and

one or more non-transitory computer-readable media storing instructions executable by the one or more processors, wherein the instructions cause the one or more processors to perform acts comprising:

causing a payment application to launch on a user device of a user;

based on an interaction with a first interactive element of a user interface of the payment application, causing a website of a merchant to load to an in-app browser within the payment application, wherein the website is rendered as a web view within the payment application;

presenting, via a second user interface of the user device, a second interactive element on a checkout page of the website, wherein selection of the second interactive element is associated with use of the payment application as a form of payment, of one or more forms of payment, for a transaction with the merchant;

determining that the second interactive element has been selected;

presenting, via a third user interface of the user device, a third interactive element associated with a confirmation of user intent to use the payment application, wherein selection of the third interactive element generates a payment request for a payment to the merchant from a user account associated with the payment application;

receiving, via the in-app browser, the payment request associated with initiating the payment to the merchant from the user account;

responsive at least in part to receiving the payment request, determining that the payment request originated from within the payment application and is associated the user account; and

causing, based at least in part on determining that the payment request originated from within the payment application, the payment to be authorized without additional input from the user.

36 . The system of claim 35 , the acts further comprising:

causing an indication that the payment has been authorized to be presented on the website within the in-app browser based at least in part on the payment having been authorized.

37 . The system of claim 35 , the acts further comprising:

causing a checkout process to proceed via the website within the in-app browser based at least in part on the payment having been authorized.

38 . The system of claim 35 , wherein causing the payment to be authorized comprises:

accessing user data associated with the user; and

causing a checkout process to be completed, without user intervention, via the website based at least in part on the user data.

39 . The system of claim 35 , the acts further comprising:

receiving, via the user device, an access request to access the payment application, wherein the access request is associated with data to authenticate the user,

wherein, upon authentication the user is authorized to use the user account associated with the payment application for making payments, and

wherein causing the payment to be authorized is based at least in part on the data.

40 . The system of claim 35 , the acts further comprising:

receiving touch data corresponding to touch input received via a display of the user device,

wherein determining that the second interactive element has been selected is based at least in part on receiving the touch data.