Abstract: In one aspect, a method includes receiving, from a sender device, a request to initiate a transfer of an asset to a recipient; causing a user interface to be presented on the sender device to receive an input of an amount of the asset to be transferred; causing an indication of the transfer of the asset to be presented via the user interface in association with a graphical icon representing a gift wrapping that conceals at least some information regarding a payload associated with the transfer; associating the graphical icon with the payload to generate a gift-wrapped element that includes the amount and the information regarding the payload; causing a notification to be sent to a recipient device of the recipient that includes the gift wrapped element; and causing assets in the amount to be withdrawn from an account of the sender and transferred to an account of the recipient.

Abstract: In one embodiment, a method includes receiving, by a payment server and from a messaging application executing on a first mobile device operated by a first user, a request to initiate a payment transaction using a payment application. The request includes a payment amount and an identifier associated with the first user. The method includes facilitating a first adjustment to a balance associated with the financial account of the first user in the data store identified based on the identifier. The method includes generating a link associated with the first adjustment and transmitting the link to the first mobile device. The method includes, upon receiving from a second user operating a messaging application, an indication that the second user has interacted with the link within the messaging application, facilitating a second adjustment of a balance of a financial account of the second user according to the payment amount.

Abstract: In one embodiment, a method includes receiving, by a payment server and from a messaging application executing on a first mobile device operated by a first user, a request to initiate a payment transaction using a payment application. The request includes a payment amount and an identifier associated with the first user. The method includes facilitating a first adjustment to a balance associated with the financial account of the first user in the data store identified based on the identifier. The method includes generating a link associated with the first adjustment and transmitting the link to the first mobile device. The method includes, upon receiving from a second user operating a messaging application, an indication that the second user has interacted with the link within the messaging application, facilitating a second adjustment of a balance of a financial account of the second user according to the payment amount.

Abstract: Disclosed herein are systems and methods for processing a payment request. A mobile device associated with a payor may generate a user interface having two screen portions. The first screen portion may be configured to display received and sent messages and further configured to receive a command to transmit a message. The second screen portion may be configured to access a third-party application and configured to populate a new message with a payload. The mobile device may receive an inputted amount in the second screen portion representing the payment amount. The mobile device may transmit a request including the payor's identification and the payment amount to a third-party Payment Processing System (PPS) and receive a payload from the PPS. The mobile device may populate and transmit a message to the recipient that contains the payload.

Abstract: Disclosed herein are systems and methods for processing a payment request. A mobile device associated with a payor may generate a user interface having two screen portions. The first screen portion may be configured to display received and sent messages and further configured to receive a command to transmit a message. The second screen portion may be configured to access a third-party application and configured to populate a new message with a payload. The mobile device may receive an inputted amount in the second screen portion representing the payment amount. The mobile device may transmit a request including the payor's identification and the payment amount to a third-party Payment Processing System (PPS) and receive a payload from the PPS. The mobile device may populate and transmit a message to the recipient that contains the payload.

Abstract: Disclosed herein are systems and methods for processing a payment request. A server may receive a request to transmit a message generated on a payor's mobile device to a second user's mobile device, where the request includes a message including a payload and an identifier for the second user. The payload may not include any information or identifiers associated with the second user. The server may transmit the message and payload from the payor's mobile device to the second user's mobile device.

Abstract: Disclosed herein are systems and methods for processing a payment request from a payor's mobile device. Payment Processing System (PPS) server may receive a payment request from a payor's mobile device, including an amount to pay but not any identification of a recipient. The PPS server may increment a balance of an escrow account and decrement a balance of the payor's account according to the amount of the request. The PPS server may generate a token, associated with the escrow account, including an alphanumeric string based on a random value generator. The PPS server may also generate a payload based on the token and transmit the payload to the payor's mobile device. Upon the recipient receiving and activating the payload, the PPS server may decrement the escrow account and increment the recipient's account.

Abstract: Disclosed herein are systems and methods for processing a payment request. A mobile device associated with a payor may generate a user interface having two screen portions. The first screen portion may be configured to display received and sent messages and further configured to receive a command to transmit a message. The second screen portion may be configured to access a third-party application and configured to populate a new message with a payload. The mobile device may receive an inputted amount in the second screen portion representing the payment amount. The mobile device may transmit a request including the payor's identification and the payment amount to a third-party Payment Processing System (PPS) and receive a payload from the PPS. The mobile device may populate and transmit a message to the recipient that contains the payload.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: Described is a technology for seamless initiation of a transfer of payment from a sender to a recipient by sending email, without requiring any account creation and/or login procedure. The technology can involve sending payment from one mobile device to another. In one aspect, the technology includes receiving a payment amount from a sender via the sender's mobile device, causing an email with pre-populated information to be generated using a native email application on the mobile device, and initiating the process to transfer the payment amount upon sending of the email. The technology enables a simplified payment transaction system for ordinary consumers without the hassle of having to sign up, to remember a user account and a password, and to login for sending or receiving every payment transaction, while not sacrificing the essential security feature of authenticating the user for every payment transaction.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: To help reduce latency when an application presents an embedded web view, the application may provide to a web view controller not only a base uniform resource indicator of a web application defining the web view but also preview data for the web view controller to render for presentation together with a cached version of the web view. In accordance with script logic defined by the web application, the web view controller may then (i) incorporate the provided preview data into the cached version of the web view and render the result as a preview view for presentation at a user interface, (ii) download instance data for the web view while the preview view is presented, and (iii) upon receipt of the instance data, establish and render a full version of the web view based on the instance data, for presentation at the user interface.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

Abstract: Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.