Abstract: An example process includes causing a payment application to launch on a user device. Based on an interaction with a first interactive element of a user interface of the payment application, a merchant website loads to an in-app browser within the payment application. Selection of a second interactive element on a checkout page of the website is associated with use of the payment application as a form of payment for a transaction with the merchant. A third interactive element associated with confirmation that the user intends to pay with the payment application from a user account associated with the payment application can be presented. A payment request is received via the in-app browser and it is determined that the request originated from within the payment application and that it is associated with the user account. Payment is authorized without additional input.

Abstract: Permission management via a mobile payment application is described. A first request to authorize an account of a customer for payment a transaction between the customer and a third-party merchant can be received from a third-party application. Based on the first request indicating that the third-party merchant is permitted to store payment data associated with the account of the customer for processing payment(s) for future transaction(s), a token can be sent to the third-party merchant to be stored for processing the payment(s) for the future transaction(s). A user interface presented via an instance of a mobile payment application, associated with the payment service, on a computing device of the customer, can enable the customer to manage permission(s) associated with the token. A permission associated with the token can be modified based at least in part on receiving a second request via the mobile payment application.

Abstract: An example process includes causing a website of a merchant to load to an in-app browser within a payment application executing on a user device of a user. The example process further includes presenting, via a user interface of the user device, an interactive element on a checkout page of the website. A determination is made that the interactive element has been selected. The selection generates a payment request for a payment to the merchant from a user account associated with the payment application. The payment request is received via the in-app browser to initiate payment from the user account. The example process further includes determining that the payment request originated from within the payment application and is associated with a stored balance associated with the user account. The user account is accessed, and the payment is caused to be authorized without additional input from the user.

Abstract: Application integration for web payments is described. In an example, a peer-to-peer (P2P) payment platform can present, via a web browser, a merchant web page that includes an actuation mechanism for selection of a payment making platform for making a payment for a transaction. The peer-to-peer (P2P) payment platform detects interaction with the actuation mechanism and presents a prompt for a user identifier via the web browser. The peer-to-peer (P2P) payment platform sends the user identifier (which is associated with an account of the user) to the payment making platform and receives an indication of the user account from the payment making platform. Based on the indication and the transaction data, the peer-to-peer (P2P) payment platform transfers funds from a stored balance of the user to a merchant account of the merchant. The peer-to-peer (P2P) payment platform presents at least a portion of the transaction data.

Abstract: In examples, the claimed techniques comprise a point-of-sale (POS) application monitoring a POS device for an indication that a transaction has been initiated; contextually associating the POS device with a mobile payment application executing on a customer device to cause receiving an indication of the transaction initialized between the customer device and the POS device; the mobile payment application receiving at least a portion of transaction data generated by the POS application; the mobile payment application generating a payment-ready message that is configured for processing the transaction by the mobile payment application instead of the POS application and that includes at least the portion of the transaction data; and the mobile payment application presenting, on a display of the customer device, user interface element(s), at least one of which selectable to complete the processing of the transaction.

Abstract: Transaction identification is described. A payment processing platform can receive (i) transaction data associated with a transaction between a merchant and a customer and (ii) a transaction code from a payment making platform. The payment processing platform can receive an indication of an interaction between a computing device of the customer and the transaction code, wherein the indication is associated with context data associated with the interaction. Based at least partly on comparing the transaction data with the context data, determining that the customer is associated with the transaction and causing an association between the customer and the transaction, wherein the association causes at least a portion of the transaction data to be provided to a mobile payment application, associated with the payment making platform, on the computing device of the customer.

Abstract: An example process includes causing a website of a merchant to load to an in-app browser within a payment application executing on a user device of a user. The example process further includes presenting, via a user interface of the user device, an interactive element on a checkout page of the website. A determination is made that the interactive element has been selected. The selection generates a payment request for a payment to the merchant from a user account associated with the payment application. The payment request is received via the in-app browser to initiate payment from the user account. The example process further includes determining that the payment request originated from within the payment application and is associated with a stored balance associated with the user account. The user account is accessed, and the payment is caused to be authorized without additional input from the user.

Abstract: Techniques, devices, and systems for performing actions, within an application provided by a service provider, without additional authorization requests are described. An example process includes receiving an access request to access an application on a user device, and presenting an interactive element via a user interface of the application, wherein the interactive element, when selected, causes a website of a merchant to load to an in-app browser within the application. The example process further includes receiving, via the in-app browser, a payment request to initiate a payment to the merchant from an account associated with the application, determining, based at least in part on the payment request, that the payment request originated from within the application, and based at least in part on the determining, causing the payment to be authorized without additional input from a user associated with the user device.

Abstract: Application integration for web payments is described. In an example, a peer-to-peer (P2P) payment platform can present, via a web browser, a merchant web page that includes an actuation mechanism for selection of a payment making platform for making a payment for a transaction. The peer-to-peer (P2P) payment platform detects interaction with the actuation mechanism and presents a prompt for a user identifier via the web browser. The peer-to-peer (P2P) payment platform sends the user identifier (which is associated with an account of the user) to the payment making platform and receives an indication of the user account from the payment making platform. Based on the indication and the transaction data, the peer-to-peer (P2P) payment platform transfers funds from a stored balance of the user to a merchant account of the merchant. The peer-to-peer (P2P) payment platform presents at least a portion of the transaction data.

Abstract: Application integration for contactless payments is described. In an example, a payment making platform can provide a transaction code to a payment processing platform. The transaction code can be presented at a point-of-sale of a transaction between a customer and a merchant associated with the payment processing platform. Upon detecting an interaction between the transaction code and a computing device of the customer, the payment making platform and the payment processing platform can exchange data to enable the customer to participate in the transaction via the computing device of the customer. In some examples, the payment making platform and the payment processing platform can process a contactless payment for the transaction by transferring funds associated with an account of the customer from the payment making platform to the payment processing platform for depositing into an account of the merchant.

Abstract: Transaction identification is described. A payment processing platform can receive (i) transaction data associated with a transaction between a merchant and a customer and (ii) a transaction code from a payment making platform. The payment processing platform can receive an indication of an interaction between a computing device of the customer and the transaction code, wherein the indication is associated with context data associated with the interaction. Based at least partly on comparing the transaction data with the context data, determining that the customer is associated with the transaction and causing an association between the customer and the transaction, wherein the association causes at least a portion of the transaction data to be provided to a mobile payment application, associated with the payment making platform, on the computing device of the customer.

Abstract: Transaction identification is described. A payment processing platform can receive (i) transaction data associated with a transaction between a merchant and a customer and (ii) a transaction code from a payment making platform. The payment processing platform can receive an indication of an interaction between a computing device of the customer and the transaction code, wherein the indication is associated with context data associated with the interaction. Based at least partly on comparing the transaction data with the context data, determining that the customer is associated with the transaction and causing an association between the customer and the transaction, wherein the association causes at least a portion of the transaction data to be provided to a mobile payment application, associated with the payment making platform, on the computing device of the customer.

Abstract: Application integration for contactless payments is described. In an example, a payment making platform can provide a transaction code to a payment processing platform. The transaction code can be presented at a point-of-sale of a transaction between a customer and a merchant associated with the payment processing platform. Upon detecting an interaction between the transaction code and a computing device of the customer, the payment making platform and the payment processing platform can exchange data to enable the customer to participate in the transaction via the computing device of the customer. In some examples, the payment making platform and the payment processing platform can process a contactless payment for the transaction by transferring funds associated with an account of the customer from the payment making platform to the payment processing platform for depositing into an account of the merchant.

Abstract: Transaction identification is described. A payment processing platform can receive (i) transaction data associated with a transaction between a merchant and a customer and (ii) a transaction code from a payment making platform. The payment processing platform can receive an indication of an interaction between a computing device of the customer and the transaction code, wherein the indication is associated with context data associated with the interaction. Based at least partly on comparing the transaction data with the context data, determining that the customer is associated with the transaction and causing an association between the customer and the transaction, wherein the association causes at least a portion of the transaction data to be provided to a mobile payment application, associated with the payment making platform, on the computing device of the customer.

Abstract: Application integration for contactless payments is described. In an example, a payment making platform can provide a transaction code to a payment processing platform. The transaction code can be presented at a point-of-sale of a transaction between a customer and a merchant associated with the payment processing platform. Upon detecting an interaction between the transaction code and a computing device of the customer, the payment making platform and the payment processing platform can exchange data to enable the customer to participate in the transaction via the computing device of the customer. In some examples, the payment making platform and the payment processing platform can process a contactless payment for the transaction by transferring funds associated with an account of the customer from the payment making platform to the payment processing platform for depositing into an account of the merchant.