Request handling via a rich messaging system

A framework for rich messaging enables secure payment transactions over offline channels by using encrypted authorization data to facilitate payment collection without direct access to sensitive information, addressing the challenge of payment authorization in existing systems.

JP7577763B2Active Publication Date: 2024-11-05LIVEPERSON INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2022574295
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-06-05
Filing Date
2021-06-04
Publication Date
2024-11-05
Estimated Expiration
2041-06-04

AI Technical Summary

Technical Problem

Existing systems lack efficient methods for enabling rich messaging over offline channels to facilitate payment transactions between customers and brands, particularly when sensitive payment information is not directly accessible by the end agent.

Method used

A framework that utilizes rich messaging to enable payment authorization and collection without direct access to payment information, involving a computer-implemented method that includes receiving a payment request, prompting the customer for authorization, and using encrypted data to obtain payment through a processing service.

Benefits of technology

Enables secure and efficient payment transactions over offline channels by allowing customers to authorize payments without exposing sensitive information to the end agent, ensuring secure and seamless communication between customers and brands.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007577763000001
    Figure 0007577763000001
  • Figure 0007577763000002
    Figure 0007577763000002
  • Figure 0007577763000003
    Figure 0007577763000003
Patent Text Reader

Abstract

The disclosed embodiments provide a framework for enabling rich messaging over offline channels to obtain payment for the completion of a business transaction. In response to a request to obtain information associated with a customer to support a transaction conducted over a communication session, the messaging platform sends a request to a computing device associated with the customer to obtain authorization for the information. In response to obtaining authorization for the information from the computing device associated with the customer, the messaging platform uses the authorization in a processing service to obtain the information subject to the authorization. The information is provided to fulfill the initial request.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 035,418, filed June 5, 2020, the disclosure of which is incorporated herein by reference.

[0002]

[0002] The present disclosure relates generally to systems and methods for facilitating digital messaging over offline channels to enable rich messaging between entities. More particularly, techniques are provided for deploying a framework for enabling rich messaging over offline channels to obtain payment for the completion of a business transaction. Summary of the Invention

[0003]

[0003] The disclosed embodiments provide a framework for enabling rich messaging over offline channels to obtain payment for completion of a transaction between a customer and a brand. According to some embodiments, a computer-implemented method is provided. The computer-implemented method comprises receiving a payment request associated with a customer. The payment request is further associated with an end agent requiring a payment associated with the customer. Furthermore, the information used to access the payment is not directly accessible by the end agent. The computer-implemented method further comprises sending an authorization request to obtain authorization for the payment. The authorization request is sent such that when the authorization request is received at a computing device associated with the customer, the authorization request is used to prompt the customer for authorization data and information used to access the payment. The computer-implemented method further comprises receiving the authorization data and information. The computer-implemented method further comprises using the authorization data and information to obtain the payment. The authorization data and information are used such that when the authorization data and information are received at a processing service, the processing service uses the authorization data and information to collect the payment. The computer-implemented method further comprises providing a transaction code. The transaction code is provided such that when the transaction code is received by the end agent, the end agent uses the transaction code to obtain the payment without having direct access to the information.

[0004] In one example, a system includes one or more processors and a memory containing instructions that, when executed by the one or more processors, cause the system to perform a process described herein. In another example, a non-transitory computer-readable storage medium has executable instructions stored thereon that, when executed by one or more processors of a computer system, cause the computer system to perform a process described herein.

[0005]

[0005] Various embodiments of the present disclosure are discussed in detail below. Although specific implementations are discussed, it should be understood that this is done for illustrative purposes only. Those skilled in the art will recognize that other components and configurations can be used without departing from the spirit and scope of the present disclosure. Therefore, the following description and drawings are illustrative and should not be construed as limiting. Numerous specific details are described to provide a thorough understanding of the present disclosure. However, in some instances, well-known or conventional details are not described to avoid obscuring the description. Reference to an embodiment or an embodiment in the present disclosure may be a reference to the same embodiment or any embodiment, and such reference means at least one of the embodiments.

[0006]

[0006] Reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. The appearances of the phrase "one embodiment" in various places in this specification do not necessarily all refer to the same embodiment, or to separate or alternative embodiments that are mutually exclusive of other embodiments. Moreover, various features are described that may be exhibited by some embodiments but not by other embodiments.

[0007]

[0007] The terms used herein generally have their ordinary meanings in the art, within the context of this disclosure and in the specific context in which each term is used. Alternative wording and synonyms may be used for any one or more of the terms described herein, and no special importance should be placed on whether a term is detailed or explained herein. In some cases, synonyms for some terms are provided. The detailed explanation of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any term described herein, is illustrative only and is not intended to further limit the scope and meaning of the disclosure or any exemplary term. Similarly, the disclosure is not limited to the various embodiments provided herein.

[0008]

[0008] Without intending to limit the scope of the present disclosure, examples of devices, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Please note that titles or subtitles may be used in the examples for the convenience of the reader, and in no case should this limit the scope of the present disclosure. Unless otherwise defined, technical and scientific terms used herein have the meaning as commonly understood by those skilled in the art to which the present disclosure pertains. In case of conflict, the present document, including definitions, shall control.

[0009]

[0009] Additional features and advantages of the present disclosure will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the principles disclosed herein. The features and advantages of the present disclosure may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the present disclosure will become more fully apparent from the following description and the appended claims, or may be learned by practice of the principles described herein.

[0010]

[0010] The present disclosure is described in conjunction with the accompanying drawings, in which: [Brief description of the drawings]

[0011] [Figure 1]

[0011] FIG. 1 illustrates an illustrative example of an environment in which a brand messaging platform, in conjunction with a payment processing service, processes payment transactions between customer computing devices and brands, according to at least one embodiment. [Diagram 2]

[0012] FIG. 1 illustrates an illustrative example of an environment in which a brand messaging platform identifies a customer computing device's capabilities for rich messaging and payment authorization in response to a request from a brand, according to at least one embodiment. [Diagram 3]

[0013] FIG. 1 illustrates an illustrative example of an environment in which a brand messaging platform payment orchestration service completes a payment transaction between a customer and a brand, according to at least one embodiment. [Figure 4]

[0014] FIG. 1 illustrates an illustrative example of a process for determining rich messaging and payment capabilities of a customer computing device to determine whether a payment is authorized and can be submitted from the customer computing device, according to at least one embodiment. [Diagram 5]

[0015] FIG. 1 illustrates an illustrative example of a process for conducting a payment transaction between a customer and a brand, according to at least one embodiment. [Figure 6]

[0016] FIG. 1 illustrates an illustrative example of an environment in which various embodiments may be implemented. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012]

[0017] In the accompanying figures, similar components and / or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. When only a first reference label is used in this specification, the description is applicable to any one of the similar components having the same first reference label, regardless of the second reference label.

[0013]

[0018] The following description merely provides preferred examples of embodiments and is not intended to limit the scope, applicability or configuration of the present disclosure. Instead, the following description of preferred examples of embodiments provides those skilled in the art with an enablement description for implementing the preferred examples of embodiments. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the appended claims.

[0014]

[0019] FIG. 1 illustrates an illustrative example of an environment 100 in which a brand messaging platform 102, along with a payment processing service 120, processes payment transactions between a customer computing device 118 and a brand 112, according to at least one embodiment. In the environment 100, customers of the brand messaging platform 102 engage in communication sessions with a response system 114 of the brand 112 via an intent messaging service 104 provided by the brand messaging platform 102. The intent messaging service 104 may provide a platform for customers and brands to connect to provide recommendations and advice regarding intents submitted by these customers. An intent may be (for example) a topic, sentiment, complexity, and / or urgency level. A topic may include, but is not limited to, a subject, a product, a service, a technical issue, a usage question, a complaint, a refund request or a purchase request, etc.

[0015]

[0020] The intent messaging service 104 may utilize an intent submitted by a customer via a customer computing device 118 to identify a brand, such as the brand 112, that may provide a relevant response to the intent. Based on the response submitted by the brand 112, the customer may determine whether to further engage with the brand 112 regarding the intent. If so, the intent messaging service 104 may establish a communication session between the customer computing device 118 and the response system 114 of the brand 112. Using an intent messaging application provided by the brand messaging platform 102 and implemented on the customer computing device 118, the customer may engage in a communication session with the response system 114 of the brand 112. Through this communication session, the customer and the response system 114 may exchange messages or other information regarding an intent previously submitted by the customer to the intent messaging service 104.

[0016]

[0021] The communication session established by the intent messaging service 104 between the customer computing device 118 and the answering system 114 may be implemented according to the Rich Communication Services (RCS) protocol or other multimedia protocol through which the customer and the answering system 114 may exchange rich messages or other in-call multimedia. In some cases, the communication session may be established as a voice or video call through which the customer may interact with the answering system 114 of the brand 112. Alternatively, the communication session may be established as instant messaging or other forms of chat messaging through which the customer and the answering system 114 may exchange text-based messages over the communication session.

[0017]

[0022] During a communication session between the customer computing device 118 and the response system 114 of the brand 112, the response system 114 may determine that a payment from the customer is required to provide the brand 112's goods and / or services to the customer. For example, the response system 114 may determine that the customer may be required to purchase one or more items or use one or more services offered by the brand 112 in order for the brand 112 to address an intent submitted by the customer. Throughout the communication session, the response system 114 may promote these goods and / or services and prompt the customer to determine whether the customer wishes to purchase said goods and / or services. If the customer indicates a desire to purchase any of these goods and / or services, the response system 114 may determine whether the customer is able to provide payment for said goods and / or services via a rich messaging and / or intent messaging application implemented on the customer computing device 118.

[0018]

[0023] In one embodiment, when a payment is required from a customer, the response system 114 sends a request to the device capabilities service 106 of the brand messaging platform 102 to identify the capabilities of the customer computing device 118 to submit a payment using rich messaging via the RCS protocol or through an intent messaging application implemented on the customer computing device 118. The device capabilities service 106 may comprise one or more computer systems of the brand messaging platform 102 or may be implemented as an application or process running on a computer system of the brand messaging platform 102. The request from the response system 114 may include identification information of the customer. To obtain this identification information of the customer, the response system 114 may solicit information from the customer that may be used by the brand messaging platform 102 to identify the customer and query the customer's account. For example, the response system 114 may ask the customer over the communication session for its username or other customer identifier associated with the brand messaging platform 102. Alternatively, if the communication session between the customer and the response system 114 is mediated through the intent messaging service 104 , the device capabilities service 106 may obtain the customer's identifier from the intent messaging service 104 .

[0019]

[0024] In some instances, if the customer has an existing relationship with the brand 112, the intent messaging service 104 may pass account information associated with the customer for the brand 112 to the response system 114 of the brand 112. During a communication session between the customer computing device 118 and the response system 114 of the brand 112, the response system 114 may prompt the customer to confirm its identity. In response to this prompt, the intent messaging service 104 may prompt the customer to provide authentication information that may be used by the intent messaging service 104 to authenticate the customer. For example, the intent messaging service 104 may prompt the customer to provide biometric information that may be used to verify and authenticate the customer. If the customer is successfully authenticated by the intent messaging service 104, the intent messaging service 104 may send a response to the response system 114 indicating that the customer has been authenticated. This may allow the response system 114 to continue the communication session with the customer in an authenticated state.

[0020]

[0025] In some instances, if the intent messaging service 104 determines that the customer does not have an existing relationship with the brand 112 (e.g., account information specific to the brand 112 is not available for the customer), the response system 114 may request the brand messaging platform 102 to release the customer information. In response to the request, the intent messaging service 104 may notify the customer of the brand's request. This may allow the customer to decide whether to allow the response system 114 associated with the brand 112 to release the customer information. Using the released customer information, the brand 112 may create a new account for the customer and provide the account information associated with this account to the brand messaging platform 102. The brand messaging platform 102 may maintain this account information, which may be used to authenticate the customer for the brand 112 in future communications.

[0021]

[0026] In response to a request from the response system 114 of the brand 112, the device capabilities service 106 may determine whether the customer computing device 118 is known to support the submission of payments via rich messaging and / or via an intent messaging application. For example, the device capabilities service 106 may utilize a customer identifier provided by the response system 114 to retrieve configuration information for the customer computing device 118. For example, as part of the registration process with the brand messaging platform 102, a customer may be prompted to provide specifications of the computing device to be used to access the brand messaging platform 102 and any of the services offered by the brand messaging platform 102. These specifications may include the storage capacity of the computing device, the amount of memory of the computing device, the processor implemented on the computing device, the mobile network operator utilized by the computing device, etc. In some instances, if the customer computing device 118 implements the intent messaging application described above, the intent messaging application may identify the capabilities of the computing device 118 and send information corresponding to these capabilities to the brand messaging platform 102.

[0022]

[0027] If the device capabilities service 106 determines that the customer computing device 118 is known to be capable of sending rich messages through which payments may be submitted, the device capabilities service 106 may send a request to the presence service 108 of the brand messaging platform 102 to determine whether the customer computing device 118 is currently capable of sending rich messages to the brand messaging platform 102 for submission of payments or other information that may be requested by the brand 112. The presence service 108 may comprise one or more computer systems of the brand messaging platform 102 or may be implemented as an application or process running on a computer system of the brand messaging platform 102. In response to the request from the device capabilities service 106, the presence service 108 may determine whether an intent messaging application implemented on the customer computing device 118 is available to provide a response to a query from the brand messaging platform 102. For example, the presence service 108 may ping an intent messaging application implemented on the customer computing device 118 to determine whether the intent messaging application is receiving and sending data packets.

[0023]

[0028] If an intent messaging application is available, the presence service 108 may send a request to the intent messaging application to identify the current capabilities of the customer computing device 118 to support rich messaging for the submission of payments. In response to the request from the presence service 108, the intent messaging application may evaluate the customer computing device 118 to determine the current capabilities of the customer computing device 118 and to determine whether the device can support rich messaging for the submission of payments or other information that may be requested by the brand 112. The intent messaging application may send a response to the presence service 108 indicating the current capabilities of the customer computing device 118 to support rich messaging for the submission of payments or other information. It should be noted that although an intent messaging application is utilized extensively throughout this disclosure for purposes of illustration, the determination of the current capabilities of the customer computing device 118 may be performed according to the RCS protocol. For example, the presence service 108 may send a request to any application of the customer computing device 118 that supports the RCS protocol, and thus may determine the current capabilities of the customer computing device 118.

[0024]

[0029] If the presence service 108 determines that the customer computing device 118 is currently capable of supporting the transmission of payment or other information via rich messaging and / or via intent messaging applications, the presence service 108 may alert the brand 112 via the device capabilities service 106 to indicate that the customer computing device 118 is capable of supporting the submission of payment or other information using rich messaging and / or via intent messaging applications. In response to the alert, the brand 112 may prompt an agent 116 associated with the brand 112 to submit a request to a payment orchestration service 110 of the brand messaging platform 102 to obtain payment or other information from the customer for goods and / or services to be provided by the brand 112 to the customer. The payment orchestration service 110 may comprise one or more computer systems of the brand messaging platform 102 or may be implemented as an application or process executing on a computer system of the brand messaging platform 102.

[0025]

[0030] An agent 116 associated with a brand 112 may submit a request to the payment orchestration service 110 to obtain payment or other information from a customer. The request may specify the amount of payment to be obtained from the customer, as well as a description of the goods and / or services for which payment is requested of the customer. Additionally, the request may include an identifier for the customer (e.g., an identifier assigned to the customer by the brand messaging platform 102, etc.) or other identifying information for the customer (e.g., the customer's contact information, the customer's network address, etc.). The request from the agent 116 may also include authentication information for the brand 112. This authentication information may be used by the payment orchestration service 110 to authenticate the agent 116 and to determine whether the agent 116 is authorized to request and obtain payments from customers on behalf of the brand 112.

[0026]

[0031] If the payment orchestration system successfully authenticates the agent 116 and determines that the agent 116 is authorized to submit a request for payment or other information from the customer, the payment orchestration service 110 may generate, via the payment processing service 120, a virtual cart designated by the brand 112 for processing the payment from the customer. The virtual cart may specify the goods and / or services to be provided by the brand 112 to the customer. Additionally, the virtual cart may specify the amount of payment being requested by the agent 116 as part of the transaction between the customer and the brand 112. The payment orchestration service 110 may assign the virtual cart a unique identifier associated with the request submitted by the agent 116. This unique identifier may also be associated with an identifier of the brand 112 and an identifier of the customer. In one embodiment, the virtual cart also includes a timestamp corresponding to the time the request was submitted by the agent 116. This timestamp may be used to determine expiration of the virtual cart if payment authorization is not received from the customer within an expiration period extending from the time indicated in the timestamp. The payment orchestration service 110 may track the expiration period of the virtual cart to determine if the virtual cart has expired prior to obtaining payment authorization from the customer.

[0027]

[0032] The payment orchestration service 110 may send a request to an intent messaging application implemented on the customer computing device 118 to obtain a payment authorization that may be used to obtain a payment for the brand 112. The request may include a virtual cart generated by the payment orchestration service 110. Additionally, the request may specify goods and / or services for which the customer agrees to provide payment as part of a transaction between the customer and an agent 116 associated with the brand 112. The request may also specify associated costs to the customer for each of the goods and / or services to be provided by the brand 112. These costs, together with any other associated fees, may amount to a total payment requested for the customer. The request may be sent to the customer computing device 118 as a rich message generated according to the RCS protocol. Alternatively, the request may be sent directly to the intent messaging application implemented on the customer computing device 118. It should be noted that the request to obtain a payment authorization that may be used to obtain a payment for the brand 112 may be submitted to any application that has the capability to support payments or proactive messaging (in addition to intent messaging applications).

[0028]

[0033] An intent messaging application implemented on the customer computing device 118 may present a payment request to the customer and prompt the customer for authorization to release the payment to the agent 116. For example, the intent messaging application may update a user interface of the customer computing device 118 to present a request for payment to the customer. The intent messaging application may also prompt the customer to provide its payment authorization via one or more authorization methods approved by the payment orchestration service 110 and / or the payment processing service 120. The customer may submit, via the user interface, a PIN, a password, one or more forms of biometric information (e.g., fingerprint, retina scan, face scan, hearing recording, video recording, etc.), or any other identification information of the customer that may serve as an indication of authorization to pay. In addition to prompting the customer for its authorization information, the intent messaging application may prompt the customer to select a method of payment. For example, via the intent messaging application, the customer may provide its credit card information, banking information, digital wallet information, etc.

[0029]

[0034] The intent messaging application may send the encrypted data packet to the payment orchestration service 110 using a rich message via the RCS protocol or through any other available communication protocol. The packed encrypted data may include payment authorization information provided by the customer, as well as payment information corresponding to the method of payment selected by the customer. In response to obtaining the encrypted data packet from the intent messaging application, the payment orchestration service 110 may evaluate the packet data and determine whether the customer has provided its authorization for the payment to be made to the agent 116 associated with the brand 112. For example, in response to obtaining the encrypted data packet from the intent messaging application, the payment orchestration service 110 may verify that the encrypted data packet is authentic using a cryptographic key or shared secret, and if so, decrypt the encrypted data packet to obtain the customer's payment information and the payment authorization information.

[0030]

[0035] In response to obtaining the customer's payment authorization information, the payment orchestration service 110 may evaluate the information to determine whether it is valid. For example, the payment orchestration service 110 may evaluate the authorization information obtained from the intent messaging application against known valid authorization information stored in the customer's account to determine whether the authorization information provided by the customer is valid. If the payment orchestration service 110 determines that the authorization information is valid, the payment orchestration service 110 may send the payment information provided by the customer, as well as a unique identifier corresponding to the virtual cart, to the payment processing service 120.

[0031]

[0036] The payment processing service 120 may initiate a transaction according to the method selected by the customer and the payment information submitted by the customer. In some cases, the payment orchestration service 110 may provide the customer's payment authorization information to the payment processing service 120, which may provide the payment authorization information to the payment provider. The payment provider may evaluate the authorization information to ensure that it is valid. If so, the payment provider may release the required payment to the payment processing service 120. When the payment is obtained from the payment provider by the payment processing service 120, the payment processing service 120 may provide the payment orchestration service 110 with a transaction code corresponding to the payment. The payment orchestration service 110 may generate a digital receipt specifying the goods and / or services for which the customer submitted the payment, the payment amount, the transaction code corresponding to the payment transaction, etc. The payment orchestration service 110 may send the digital receipt to the intent messaging application to have the intent messaging application present the digital receipt to the customer.

[0032]

[0037] In addition to providing a digital receipt to the intent messaging application, the payment orchestration service 110 may send a transaction code from the payment processing service 120 to the agent 116. The agent 116 may use the transaction code to verify that the customer has provided its payment for the goods and / or services offered by the brand 112 and to collect the payment from the payment processing service 120. The agent 116 may confirm with the customer over the communication session that the payment has been received. Additionally, the agent 116 may provide the goods and / or services indicated in the transaction to the customer.

[0033]

[0038] While payment transactions are described extensively throughout this disclosure for illustrative purposes, it should be noted that during the course of a communication session between the customer and the agent 116, other information may be provided to the agent 116 associated with the brand 112 without exposing any sensitive information of the customer (e.g., the customer's credit card or other payment information, personally identifiable information (PII), etc.) to the agent 116. For example, the agent 116 associated with the brand 112 may submit a request to the brand messaging platform 102 to obtain recommendations that may be provided by the agent 116 to the customer 118 over the communication session. As another example, the agent 116 may submit a request to the brand messaging platform 102 to obtain support materials, transaction confirmation information, account management confirmation information, etc. In the request, the agent 116 may provide information regarding the nature of the communication session (e.g., the topic, the problem posed by the customer, the time frame provided by the customer, any products identified by the customer and / or the agent 116, etc.). The brand messaging platform 102 may provide the requested information to the agent 116 without descriptive information of other brands that may utilize the brand messaging platform 102, as referred to herein.

[0034]

[0039] In response to a request from the agent 116, the brand messaging platform 102 may utilize a machine learning model to process the incoming request from the agent 116 as well as information associated with the customer that is not otherwise accessible by the agent 116 to generate an output. This output may specify recommendations and / or customer traits that may be used by the agent 116 in communicating with the customer over a communication session. The machine learning model may be trained using supervised learning techniques. For example, a dataset of requester input requests and corresponding recommendations and / or traits may be selected for training the machine learning model. In some examples, the input requests may be obtained from an administrator of the brand messaging platform 102, a customer of the brand messaging platform 102, or other sources associated with the brand messaging platform 102. In some implementations, the known recommendations and / or customer traits used to train the machine learning model 208 may include customer characteristics or expected recommendations provided by an entity that generated the sample request. The machine learning model may be evaluated to determine whether the machine learning model is providing useful recommendations and / or traits of the requesting entity that may be provided to the requesting entity based on the input sample requests fed to the machine learning model. Based on this evaluation, the machine learning model may be modified (e.g., one or more parameters or variables may be updated) to increase the likelihood that the machine learning model will produce the desired outcome.

[0035]

[0040] In response to a request from an agent 116, the brand messaging platform 102 utilizes the request and information associated with the customer maintained by the brand messaging platform 102 and inaccessible to the agent 116 as input to a machine learning model. The output of the machine learning model may include recommendations that the agent 116 may present to the customer over a communication session. These recommendations may correspond to goods and / or services offered by the brand 112, responses to customer issues and / or concerns, etc. that may result in a positive response from the customer. Additionally, the output may include details regarding customer traits, such as the customer's stress level depending on the customer's tone or language use. These recommendations and / or traits may be utilized by the agent 116 to provide tailored responses to the customer over a communication session without the agent 116 having access to any sensitive information of the customer that may be maintained by the brand messaging platform 102.

[0036]

[0041] 2 illustrates an illustrative example of an environment 200 in which a brand messaging platform 202 identifies a customer computing device's capabilities for rich messaging and payment authorization in response to a request from a brand 210, according to at least one embodiment. In the environment 200, an integrated voice response (IVR) system of the brand 210, or an agent associated with the brand 210, sends a request to a device capabilities service 204 of the brand messaging platform 202 to determine the capabilities of the customer's computing device to submit a payment using rich messaging, such as through an RCS protocol or via an intent messaging application 214 implemented on the customer's computing device. For example, during the course of a communication session between a customer 212 and the brand 210, the brand 210 may determine that the customer 212 is requested to provide a payment to the brand 210. The communication session may include a voice call, a video call, a text-based communication session (e.g., SMS messaging, RCS messaging, instant messaging, etc.), and the like.

[0037]

[0042] The request from the brand 210 may include identification information of the customer 212. For example, the brand 210 may solicit information from the customer 212 that may be used by the brand messaging platform 202 to identify the customer 212 and query the customer 212's account during a communication session with the customer 212. For example, the brand 210 may ask the customer 212 for its username or other customer identifier associated with the brand messaging platform 202. Alternatively, if the communication session between the customer 212 and the brand 210 was mediated through an intent messaging service implemented by the brand messaging platform 202, the device capabilities service 204 may obtain the customer's identifier from the intent messaging service.

[0038]

[0043] In response to the request, the device capabilities service 204 may determine whether the customer's computing device is known to support the submission of payments via rich messaging and / or via the intent messaging application 214. For example, the device capabilities service 204 may utilize a customer identifier provided by the brand 210 to retrieve configuration information for the customer's computing device from a device database 206 maintained by the device capabilities service 204. The device database 206 may include, for each customer, an entry corresponding to a computing device utilized by the customer 212 to engage with brands and other entities via the brand messaging platform 202. For example, as part of the registration process for the brand messaging platform 202, the customer 212 may be prompted to provide specifications of the computing device utilized to access the brand messaging platform 202 and any of the services offered by the brand messaging platform. These specifications may include the storage capacity of the computing device, the amount of memory of the computing device, the processor implemented on the computing device, the mobile network operator utilized by the computing device, etc. If the computing device implements an intent messaging application 214 provided by the branded messaging platform 202, the intent messaging application 214 may identify the capabilities of the computing device and send information corresponding to those capabilities to the branded messaging platform 202. The device capabilities service 204 may update an entry corresponding to the customer's computing device in the device database 206 to indicate the known capabilities of the customer's computing device.

[0039]

[0044] If the device capabilities service 204 determines that the customer's computing device is known to support rich messaging for payment submission or is otherwise known to support rich messaging, the device capabilities service 204 may send a request to the presence service 208 of the brand messaging platform 202 to determine whether the customer's computing device is currently capable of submitting payments via rich messaging and / or via the intent messaging application 214. In response to this request, the presence service 208 implemented by the brand messaging platform 202 may determine whether the intent messaging application 214 implemented on the customer's computing device is available to provide a response to a query from the brand messaging platform 202. The presence service 208 may, for example, ping the intent messaging application 214 to determine its availability. If the intent messaging application 214 is available, the presence service 208 may send a request to the intent messaging application 214 to identify the current capability of the customer's computing device to support rich messaging for payment submission. The intent messaging application 214 may evaluate the customer's computing device to determine the current capabilities of the customer's computing device and, based on these current capabilities, to determine whether the customer's computing device can support rich messaging. The intent messaging application 214 may send a response to the request to the presence service 208 indicating the current capabilities of the customer's computing device and / or a determination regarding whether the customer's computing device supports rich messaging for payment submission.

[0040]

[0045] Based on the response from the intent messaging application 214, the presence service 208 may determine whether the customer's computing device is currently capable of supporting payment via rich messaging and / or via the intent messaging application 214. If the presence service 208 determines that the customer's computing device supports the submission of payments via rich messaging and / or through the intent messaging application 214, the presence service 208 may alert the brand 210 to indicate that the customer's computing device is capable of supporting the submission of payments using rich messaging and / or via the intent messaging application 214. This alert may cause the brand 210 to prompt an agent associated with the brand 210 to submit a request to a payment orchestration service of the brand messaging platform 202 to obtain payment from the customer 212 for goods and / or services to be provided by the brand to the customer.

[0041]

[0046] 3 illustrates an illustrative example of an environment 300 in which a payment orchestration service 304 of a brand messaging platform 302 completes a payment transaction between a customer 310 and a brand 306, according to at least one embodiment. In the environment 300, an agent 308 associated with a particular brand 306 submits a request to the payment orchestration service 304 of the brand messaging platform 302 to obtain payment from the customer 310 for goods and / or services provided by the brand 306 to the customer 310. For example, during the course of a communication session (e.g., a voice call, a video call, etc.) between the customer 310 and an agent 308 associated with the brand 306, the agent 308 may determine that the customer 310 should submit a payment to the brand 306 to fulfill the customer's request, to address a pending issue of the customer, or to otherwise continue the communication session.

[0042]

[0047] As described above, an agent 308 associated with a brand 306 may be alerted by the brand messaging platform 302 that the customer's computing device is capable of supporting the submission of a payment via rich messaging or via an intent messaging application 312 implemented on the customer's computing device. As a result, the agent 308 associated with the brand 306 may send a request to the payment orchestration service 304 of the brand messaging platform 302 to obtain a payment from the customer 310 via rich messaging or an intent messaging application 312 implemented on the customer's computing device. The request may specify a total payment amount, an invoice for goods and / or services to be provided to the customer 310, an identifier for the customer 310 (e.g., an identifier assigned to the customer 310 by the brand messaging platform 302, etc.) or other identifying information for the customer 310 (e.g., contact information for the customer 310, a network address for the customer 310, etc.).

[0043]

[0048] In one embodiment, the request from the agent 308 also includes the authentication information of the brand 306. This authentication information may be used by the payment orchestration service 304 to authenticate the agent 308 and to determine whether the agent 308 is authorized to request and obtain payments from the customer 310 on behalf of the brand 306. For example, an administrator or other entity that manages the brand 306 may be associated with the brand and may identify one or more agents authorized to request and obtain payments on behalf of the brand 306. This administrator or other entity may create accounts for each of these authorized agents via the brand messaging platform 302, through which these authorized agents may access the brand messaging platform 302 and its corresponding services (e.g., the payment orchestration service 304, etc.) to submit requests on behalf of the brand 306 according to any policies or rules implemented by the brand 306, as defined in the agent account.

[0044]

[0049] If the payment orchestration service 304 successfully authenticates the agent 308 associated with the brand 306 and determines, based on the policies and rules specified in the agent's account, that the agent 308 is authorized to submit requests on behalf of the brand 306 to solicit and obtain payments from customers, including the customer 310, the payment orchestration service 304 may proceed with processing the request from the agent 308. For example, the payment orchestration service 304 may generate a virtual cart with a payment processing service 314 designated by the brand 306 for processing payments from the customer 310. The virtual cart may specify goods and / or services to be provided by the brand 306 to the customer 310. Additionally, the virtual cart may specify the payment amount being requested by the agent 308 for the goods and / or services shown in the virtual cart. The payment orchestration service 304 may assign the virtual cart a unique identifier associated with the request submitted by the agent 308. This unique identifier may also be associated with the identifier of the brand 306 and the identifier of the customer 310. In one embodiment, the virtual cart also includes a timestamp corresponding to the time the request was submitted by the agent 308. This timestamp may be used to determine expiration of the virtual cart if payment authorization is not received from the customer 310 within an expiration period extending from the time indicated in the timestamp. For example, if the expiration period has passed, the virtual cart expires and the payment request for the customer is terminated. The payment orchestration service 304 may track the expiration period of the virtual cart to determine if the virtual cart has expired prior to obtaining payment authorization from the customer 310.

[0045]

[0050] In one embodiment, the payment orchestration service 304 sends a request to an intent messaging application 312 implemented on the customer's computing device to obtain a payment authorization that can be used to obtain a payment for the brand 306. The request may include a virtual cart generated by the payment orchestration service 304. For example, the request may specify a unique identifier associated with the request submitted by the agent 308. Additionally, the request may specify goods and / or services for which the customer 310 is agreeing to provide payment as part of a transaction between the customer 310 and the agent 308 associated with the brand 306. The request may also specify associated costs to the customer 310 for each of the goods and / or services to be provided by the brand 306. These costs may be the total of the payment required for the customer 310 along with any other associated charges (e.g., sales tax, value-added tax, etc.). In some instances, the request may indicate an expiration time before which the customer 310 should provide its payment authorization to complete the transaction. The request may be transmitted to the customer's computing device as a rich message generated according to the RCS protocol. Alternatively, the request may be sent directly to an intent messaging application 312 implemented on the customer's computing device.

[0046] Requests submitted by the payment orchestration service 304 to the intent messaging application 312 may be encrypted using an encryption key or other encryption method of the brand messaging platform 302. This may prevent the request from the payment orchestration service 304 from being tampered with on its way to the intent messaging application 312 and may provide a means for the intent messaging application 312 to authenticate the request from the payment orchestration service 304. For example, if the request includes a digital signature of the payment orchestration service 304, the intent messaging application 312 may use the encryption key or shared secret to verify that the digital signature is authentic and was generated with the payment orchestration service 312.

[0047]

[0051] If the payment request obtained from the payment orchestration service 304 is successfully authenticated by the intent messaging application 312, the intent messaging application 312 may present the payment request to the customer 310 and prompt the customer 310 for authorization to release the payment to the agent 308. For example, the intent messaging application 312 may update a user interface of the customer's computing device to present the request for payment to the customer 310. The intent messaging application 312 may also prompt the customer 310 to provide its payment authorization via one or more authorization methods approved by the payment orchestration service 304 and / or the payment processing service 314. For example, the intent messaging application 312 may prompt the customer 310 via a user interface to submit a PIN, a password, one or more forms of biometric information (e.g., fingerprint, retinal scan, face scan, hearing recording, video recording, etc.), or any other identifying information of the customer 310 that may serve as an indication of authorization for payment. The customer 310, via his / her computing device, may provide the requested authorization information to the intent messaging application 312. In addition to prompting the customer for his / her authorization information, the intent messaging application 312 may prompt the customer 310 to select a method of payment. For example, via the intent messaging application 312, the customer 310 may provide his / her credit card information, banking information, digital wallet information, etc.

[0048]

[0052] The intent messaging application 312 may encrypt the customer's payment information and the customer's authorization information to generate an encrypted data packet that may be provided to the payment orchestration service 304 to fulfill a request from the payment orchestration service 304. The intent messaging application 312 may send the encrypted data packet to the payment orchestration service 304 using a rich message via the RCS protocol or through any other available communication protocol. In response to obtaining the encrypted data packet from the intent messaging application 312, the payment orchestration service 304 may determine whether the customer 310 has provided its authorization for a payment to be made to an agent 308 associated with the brand 306. For example, in response to obtaining the encrypted data packet from the intent messaging application 312, the payment orchestration service 304 may verify that the encrypted data packet is authentic using a cryptographic key or shared secret, and if so, decrypt the encrypted data packet to obtain the customer's payment information and the payment authorization information.

[0049]

[0053] In response to obtaining the customer's payment authorization information, the payment orchestration service 304 may evaluate it to determine whether the information is valid. For example, the branded messaging platform 302 may maintain a customer account for the customer 310, including valid authorization information for the customer 310. For example, as part of the account registration process with the branded messaging platform 302, the customer 310 may be required to provide a unique PIN or password for their account, biometric information that may be associated with the account, or any other information that may be used to authorize payments on behalf of the customer 310 or other operations associated with the customer 310. The payment orchestration service 304 may evaluate the authorization information obtained from the intent messaging application 312 against known valid authorization information stored in the customer's account to determine whether the authorization information provided by the customer 310 is valid.

[0050]

[0054] If the payment orchestration service 304 determines that the authorization information is valid, the payment orchestration service 304 may send the payment information provided by the customer 310, as well as a unique identifier corresponding to the virtual cart previously provided to the payment processing service 314, to the payment processing service 314. The payment processing service 314 may initiate a transaction according to the method selected by the customer 310 and the payment information submitted by the customer 310. For example, the payment processing service 314 may send a request to a payment provider to obtain the required payment. In some cases, the payment orchestration service 314 may provide the payment authorization information of the customer 310 to the payment processing service 314, which may provide the payment authorization information to the payment provider. The payment provider may evaluate the authorization information to ensure that it is valid. If so, the payment provider may release the required payment to the payment processing service 314. If the payment is obtained from the payment provider by the payment processing service 314, the payment processing service 314 may provide the payment orchestration service 304 with a transaction code corresponding to the payment.

[0051]

[0055] In response to receiving confirmation from the payment processing service 314 that the requested payment has been obtained, the payment orchestration service 304 may generate a digital receipt specifying the goods and / or services for which the customer 310 submitted the payment, the payment amount, a transaction code corresponding to the payment transaction, etc. The payment orchestration service 304 may send the digital receipt to the intent messaging application 312 to cause the intent messaging application 312 to present the digital receipt via a user interface of the customer's computing device. Alternatively, the intent messaging application 312 may indicate to the customer 310 via the computing device that the authorized payment has been submitted and that the transaction has been completed. In addition to providing the digital receipt to the intent messaging application 312, the payment orchestration service 304 may send a transaction code from the payment processing service 314 to the agent 308. The agent 308 may use the transaction code to verify that the customer 310 has submitted its payment for the goods and / or services offered by the brand 306, as well as to collect the payment from the payment processing service 314. The agent 308 may confirm with the customer 310 over the communication session that payment has been received. Additionally, the agent 308 may provide the customer 310 with the goods and / or services indicated during the transaction.

[0052]

[0056] FIG. 4 illustrates an illustrative example of a process 400 for determining rich messaging and payment capabilities of a customer computing device to determine whether a payment is authorized and can be submitted from the customer computing device, according to at least one embodiment. The process 400 may be implemented by a brand messaging platform, which may utilize device capability services and presence services to process incoming requests to determine the capabilities of computing devices utilized by customers of the brand messaging platform. Computing devices utilized by customers to communicate with brands associated with the brand messaging platform may, in some cases, implement intent messaging applications provided by the brand messaging platform. The intent messaging applications implemented on the customer's computing device may be provided by the intent messaging service to enable the customer to interact with brands associated with the intent messaging service and other users (e.g., a community of users utilizing the intent messaging service) and may offer products and services to the customer. The intent messaging applications may also be implemented to facilitate payment transactions between the customer and the brands for any products and / or services offered by these brands.

[0053]

[0057] In step 402, the brand messaging platform receives a request from an agent associated with the brand to determine the payment capabilities of a computing device utilized by a particular customer via a device capability service implemented by the brand messaging platform. For example, during the course of a communication session between the customer and an agent associated with the brand, the agent may determine that the customer is required to provide a payment to the brand. The communication session may include a voice call (e.g., a telephone call, etc.), a video call, a text-based communication session (e.g., SMS messaging, RCS messaging, instant messaging, etc.), etc. The customer may engage in a communication session with the agent associated with the brand to obtain goods and / or services offered by the brand. Alternatively, the customer may engage in a communication session with the agent associated with the brand to address a particular issue associated with goods and / or services offered by the brand.

[0054]

[0058] During a communication session with a customer, an agent associated with a brand may submit a request to a device capabilities service of the brand messaging platform to determine whether the customer may provide a payment via the customer's computing device (e.g., a smartphone, a tablet computing device, etc.) via a message using the RCS protocol or other similar protocol and / or via an intent messaging application provided by the brand messaging platform. In some instances, an agent associated with a brand may solicit information from the customer that may be used by the brand messaging platform to identify the customer and query the customer's account. For example, the agent may ask the customer for its username or other customer identifier associated with the brand messaging platform. Alternatively, if the communication session between the customer and an agent associated with a brand is mediated via an intent messaging service implemented by the brand messaging platform, the device capabilities service may obtain the customer's identifier from the intent messaging service. In another example, the device capabilities service may utilize automatic number identification (ANI) to automatically determine the customer's phone number that may be used by the agent to identify the customer.

[0055]

[0059] In response to the request, the device capabilities service of the branded messaging platform, in step 404, determines whether the customer's computing device is known to support providing payments via rich messaging and / or via an intent messaging application installed on the computing device. For example, the device capabilities service may utilize a customer identifier provided by an agent associated with the brand to retrieve the customer's account. The customer's account may specify information about the customer's computing device. For example, as part of the registration process with the branded messaging platform, the customer may be prompted to provide specifications of the computing device that will be utilized to access the branded messaging platform and any of the services offered by the branded messaging platform (e.g., the intent messaging service, etc.). These specifications may include the storage capacity of the computing device, the amount of memory (e.g., random access memory (RAM), etc.) of the computing device, the processor implemented on the computing device, the mobile network operator utilized by the computing device, etc. In one embodiment, if the customer implements an intent messaging application on the computing device, the intent messaging application may identify the capabilities of the computing device and send information corresponding to these capabilities to the branded messaging service. For example, an intent message application may discover various features of a computing device, as well as the configuration of those features, via the computing device's operating system. Additionally, the intent message application may send configuration information to a device capabilities service that corresponds to features of interest to the intent message application.Thus, the device capabilities service may automatically determine the capabilities of a customer's computing device to implement intent messaging applications or other applications offered by the branded messaging platform.

[0056]

[0060] If the device capabilities service determines, based on an evaluation of the known device capabilities of the customer's computing device, that the customer's computing device is incapable of supporting rich messaging for payment submission or is otherwise not known to support rich messaging, the device capabilities service indicates in step 406 that the computing device is incapable of supporting payment submission. For example, the device capabilities service may send a notification to an agent associated with the brand to indicate that payments cannot be obtained from the customer's computing device using rich messaging or through an intent messaging application. The agent associated with the brand may communicate with the customer to indicate that the payment should be submitted via a communication session (e.g., the customer will provide its payment information via a voice call) or that the payment should be submitted through other methods (e.g., the customer will access the brand's website and submit the payment via the website). The agent associated with the brand may alternatively end or otherwise terminate the communication session as a result of the notification from the device capabilities service.

[0057]

[0061] If the device capabilities service determines that the customer's computing device is known to support rich messaging for payment submission or is otherwise known to support rich messaging, the brand messaging platform sends a request to an intent messaging application implemented on the customer's computing device in step 408 to identify a current payment capability. For example, the brand messaging platform may determine, via a presence service implemented by the brand messaging platform, whether an intent messaging application implemented on the customer's computing device is available to provide a response to a query from the brand messaging platform. The presence service may, for example, ping the intent messaging application to determine its availability. If the intent messaging application is available, the presence service may send a request to the intent messaging application to identify the current capability of the customer's computing device to support rich messaging for payment submission. The intent messaging application may evaluate the customer's computing device to determine the current capabilities of the customer's computing device and, based on these current capabilities, to determine whether the customer's computing device can support rich messaging. The intent messaging application may send a response to the request to the presence service indicating the current capabilities of the customer's computing device and / or a determination as to whether the customer's computing device supports rich messaging for payment submission.

[0058]

[0062] In step 410, the presence service of the brand messaging platform determines whether the customer's computing device is currently capable of supporting payments via rich messaging. For example, if the presence service is unable to determine whether the customer's computing device is currently capable of supporting payments via rich messaging (e.g., the presence service is unable to communicate with the intent messaging application, the intent messaging application did not provide a response, etc.), the presence service may determine that the customer's computing device is not currently capable of supporting payments via rich messaging. Similarly, if the intent messaging application sends a notification to the presence service indicating that the customer's computing device does not support the submission of payments via rich messaging, the presence service may determine that the customer's computing device is not capable of supporting the submission of payments. This may cause the presence service to indicate in step 406 that the customer's computing device is not capable of supporting the submission of payments via rich messaging. As described above, the device capabilities service may send a notification to an agent associated with the brand to indicate that payments cannot be obtained from the customer's computing device using rich messaging or through the intent messaging application.

[0059]

[0063] If the presence service determines that the customer's computing device supports the submission of a payment via rich messaging or through an intent messaging application, the presence service alerts an agent associated with the brand to indicate that the customer's computing device is capable of supporting the submission of a payment using rich messaging or through an intent messaging application, in step 412. This alert may cause the agent associated with the brand to submit a request to a payment orchestration service of the brand messaging platform to obtain payment from the customer for goods and / or services to be provided by the brand to the customer.

[0060]

[0064] In addition to alerting an agent associated with the brand, the presence service may send a notification to the customer's computing device in step 414 to indicate that the computing device may be used to submit a payment via rich messaging or through an intent messaging application. This may enable the customer to receive a request from the payment orchestration service via its computing device (such as through a rich message generated according to the RCS protocol) to obtain the customer's authorization to submit a payment to the brand for goods or services discussed between the customer and an agent associated with the brand. A process for providing requests and other rich messages to the customer's computing device is described in more detail below with respect to FIG. 5. It should be noted that step 414 may be optional, whereby process 400 may be performed without the execution of step 414.

[0061]

[0065] FIG. 5 illustrates an illustrative example of a process 500 for conducting a payment transaction between a customer and a brand, according to at least one embodiment. The process 500 may be performed by a payment orchestration service of a brand messaging platform. As described above, the payment orchestration service may interact with a payment processing service designated by the brand for processing and distributing payments from customers and other entities to the brand. Additionally, the payment orchestration service may communicate with an intent messaging application implemented on a customer computing device to obtain payment information and authorization that may be provided to the payment processing service to process payments requested by the brand.

[0062]

[0066] In step 502, a payment orchestration service of the brand messaging platform receives a request to obtain a customer payment for a particular transaction. The request may be submitted by an agent associated with the brand. For example, an agent associated with the brand may determine that a payment from the customer is needed to complete a transaction between the brand and the customer (e.g., a payment is needed to complete a purchase order, a payment is needed for an agent to perform a service on behalf of the customer, etc.). As described above, the agent associated with the brand may have previously obtained a notification from the presence service of the brand messaging platform indicating the ability of the customer's computing device to generate and process rich messages and provide payments using rich messaging. For example, the presence service may determine whether the customer's computing device is capable of utilizing the RCS protocol to transmit rich messages that may be used to deliver payment information and any other information that may act as a payment authorization to provide payment to the brand. The agent associated with the brand may thus determine that the customer may submit authorization to release payment from its computing device to the brand via rich messaging, so that the payment may be provided to the brand securely (e.g., via cryptographically secure messages, etc.).

[0063]

[0067] The request to obtain a customer payment may include the brand's authentication information, which the brand messaging platform's payment orchestration service may use to authenticate the agent and determine whether the agent is authorized to request and obtain payments from customers on behalf of the brand. For example, the brand may develop a trust relationship with the brand messaging platform, such that the brand may be surveyed by the brand messaging platform as providing available resources and services to customers who may interact with the brand via the brand messaging platform. Through this trust relationship, the brand may identify one or more agents who may be associated with the brand and authorized to request and obtain payments from customers on behalf of the brand. For example, the brand may create an account with the brand messaging platform for each one or more authorized agents, through which the agent may access the brand messaging platform and submit requests on behalf of the brand according to any policies or rules implemented by the brand via the brand messaging platform and defined in the agent account. If the agent is authenticated by the brand messaging platform and the brand messaging platform determines that the agent is authorized to submit a request to obtain a customer payment, the brand messaging platform may proceed with processing the request. However, if the branded messaging platform is unable to authenticate the agent or the agent is not authorized to submit this request, the payment orchestration service of the branded messaging platform may deny the request.

[0064]

[0068] In step 504, the payment orchestration service generates a virtual cart with a payment processing service designated by the brand for processing the customer's payment. The virtual cart may specify goods and / or services to be provided by the brand to the customer to which the payment should be billed. Additionally, the virtual cart may specify a payment amount being requested by an agent associated with the brand for the goods and / or services shown in the virtual cart. The virtual cart may further specify an account number, an invoice number, or any other information that may be used to identify the transaction and the entity to which the payment should be credited. In one embodiment, the virtual cart is assigned a unique identifier associated with a request submitted by an agent to obtain payment from the customer. This unique identifier may also be associated with an identifier of the brand and an identifier of the customer. In one embodiment, the virtual cart also includes a timestamp corresponding to the time the request was submitted by the agent associated with the brand. This timestamp may be used to determine expiration of the virtual cart if a payment authorization is not received by the customer within a period of time extending from the time shown in the timestamp. For example, the payment orchestration service may implement an expiration period for each virtual cart, such that if the expiration period has passed, the virtual cart expires and the payment request for the customer is terminated. The payment orchestration service may track the expiration period of a virtual cart to determine if the virtual cart has expired prior to obtaining payment authorization from the customer.

[0065]

[0069] In step 506, the payment orchestration service sends to an intent messaging application implemented on the customer's computing device a request to obtain the customer's authorization to submit a payment to the brand for the goods or services discussed between the customer and an agent associated with the brand. The request may include the customer's version of the virtual cart provided by the payment orchestration service to the payment processing service. For example, the request may specify a unique identifier associated with the request submitted to the payment orchestration service by the agent associated with the brand. Additionally, the request may specify goods and / or services for which the customer is agreeing to provide payment as part of a transaction between the customer and an agent associated with the brand. The request may also specify associated costs to the customer for each of the goods and / or services to be provided by the brand. These costs may be the total of the payment required for the customer along with any other associated charges (e.g., sales tax, value-added tax, etc.). In some instances, the request may indicate an expiration time before which the customer should provide its payment authorization to complete the transaction. For example, the request may include instructions that, as a result of being executed by an intent messaging application implemented on the customer's computing device, cause the intent messaging application to continually provide updates to the customer regarding the amount of time remaining before the request is set to expire. The request may be transmitted to the customer's computing device as a rich message generated according to the RCS protocol.

[0066]

[0070] In one embodiment, the request sent to the intent messaging application implemented on the customer's computing device is encrypted using an encryption key or other encryption method of the brand messaging platform. In response to obtaining the encrypted request from the payment orchestration service, the intent messaging application may attempt to authenticate the request as originating from the payment orchestration service. For example, if the request includes a digital signature of the payment orchestration service, the intent messaging application may use an encryption key or a shared secret to verify that the digital signature is authentic and originated with the payment orchestration service. If the request from the payment orchestration service cannot be verified by the intent messaging application, the intent messaging application may send a notification to the payment orchestration service to indicate that the request for payment could not be authenticated. This may cause the payment orchestration service to implement one or more remedial actions, such as sending a new payment request to the intent messaging application, identifying the source of the authentication failure (e.g., the request did not originate from the payment orchestration service), or any other action to address the authentication failure.

[0067]

[0071] If the payment request obtained from the payment orchestration service is successfully authenticated, the intent messaging application may present the payment request to the customer and prompt the customer for authorization to release the payment to an agent associated with the brand. For example, the intent messaging application may update a user interface of the computing device to present the customer with a request for payment from an agent associated with the brand. Additionally, the intent messaging application may prompt the customer to provide its payment authorization via one or more authorization methods approved by the payment orchestration service. For example, the intent messaging application may prompt the customer via a user interface of the customer's computing device to submit a PIN, a password, one or more forms of biometric information (e.g., fingerprint, retina scan, face scan, hearing recording, video recording, etc.), etc. Using one or more peripheral devices (e.g., touch screen, camera, microphone, etc.) of the customer's computing device, the customer may provide the requested authorization information to the intent messaging application. In addition to prompting the customer for its authorization information, the intent messaging application may prompt the customer to select a method of payment. For example, via an intent messaging application, a customer may provide their credit card information, banking information, digital wallet information, and the like.

[0068]

[0072] In one embodiment, in response to obtaining the customer's payment information and authorization information, the intent messaging application encrypts the customer's payment information and authorization information to generate an encrypted data packet. The intent messaging application may send the encrypted data packet to the payment orchestration service using a rich message via the RCS protocol or through any other available communication protocol. Thus, in step 508, the payment orchestration service may determine whether the customer's authorization for payment to an agent associated with the brand has been received. For example, in response to obtaining the encrypted data packet from the intent messaging application implemented on the customer's computing device, the payment orchestration service may verify that the encrypted data packet is authentic using a cryptographic key or shared secret, and if so, decrypt the encrypted data packet to obtain the customer's payment information and payment authorization information.

[0069]

[0073] In one embodiment, the payment orchestration service evaluates the authorization information for a payment to determine whether the authorization information is valid. For example, the branded messaging platform may maintain a customer account for the customer, including valid authorization information for the customer. When the customer creates an account with the branded messaging platform, the customer may be prompted to provide authorization information or any other information that may be used to authenticate the customer. For example, as part of the account registration process, the customer may be prompted to provide biometric information that may be associated with the account, to generate a unique PIN or password for its account, or any other information that may be used to authorize payments on behalf of the customer or other operations associated with the customer. Thus, the payment orchestration service may evaluate the authorization information obtained from the intent messaging application against known valid authorization information stored in the customer's account to determine whether the authorization information provided by the customer is valid.

[0070]

[0074] If the payment orchestration service determines that the customer's authorization was not received (e.g., the encrypted data packet is invalid, the authorization information provided is invalid, the payment request has expired, etc.), the payment orchestration service may indicate in step 510 that the payment for the goods or services could not be completed. For example, the payment orchestration service may send a notification to the agent associated with the brand that submitted the payment request to indicate that the payment request could not be fulfilled. The notification may specify the cause of the failure to fulfill the payment request. This information may be used by the agent associated with the brand to communicate to the customer a failure in providing payment for goods and / or services requested by the customer or otherwise provided by the agent during a communication session with the customer (e.g., a voice call, a video call, etc.). The agent associated with the brand may, in response to the notification, submit a new payment request to the payment orchestration process, thereby restarting process 500. Alternatively, the agent associated with the brand may terminate the communication session with the customer as a result of the failure to provide payment for the offered goods and / or services.

[0071]

[0075] If the payment orchestration service has received the customer's authorization information and determines that the authorization information is valid, the payment orchestration service completes the payment transaction with the payment processing service in step 512. For example, the payment orchestration service may send the payment information provided by the customer to the payment processing service, as well as a unique identifier corresponding to the virtual cart previously provided to the payment processing service. Using this payment information, the payment processing service may initiate a transaction according to the method selected by the customer and the payment information submitted by the customer. For example, the payment processing service may send a request to a payment provider (e.g., a credit card company, a financial institution, etc.) to obtain the required payment. In some cases, the payment orchestration service may provide the customer's payment authorization information to the payment processing service, which may provide the payment authorization information to the payment provider. The payment provider may evaluate the authorization information to ensure that it is valid. If so, the payment provider may release the required payment to the payment processing service. In one embodiment, when the payment is obtained by the payment processing service, the payment processing service provides the payment orchestration service with a transaction code corresponding to the payment.

[0072]

[0076] In step 514, the payment orchestration service confirms payment completion with the customer via a digital receipt to the customer's computing device. For example, in response to receiving confirmation from the payment processing service that the requested payment for the goods and / or services shown in the virtual cart has been obtained, the payment orchestration service may generate a receipt specifying the goods and / or services for which the customer submitted payment, the payment amount, a transaction code corresponding to the payment transaction, etc. The payment orchestration service may send the digital receipt to an intent messaging application implemented on the customer's computing device, which may cause the intent messaging application to present the digital receipt via a user interface of the customer's computing device. Alternatively, the intent messaging application may indicate to the customer via the computing device that the authorized payment has been submitted and that the transaction is complete. Through the intent messaging application, the customer may access the digital receipt by reference to a unique transaction number or order number, etc., associated with the transaction.

[0073]

[0077] In step 516, the payment orchestration service transmits a transaction code from the payment processing service to an agent associated with the brand to complete the payment for the goods and / or services offered by the agent to the customer. The agent may utilize the transaction code to verify that the customer has provided its payment for the offered goods and / or services and to collect the payment from the payment processing service. The agent may confirm with the customer over a communication session between the agent and the customer that the payment has been received. Additionally, the agent associated with the brand may provide the goods and / or services indicated during the transaction to the customer. For example, the agent may initiate a process to ship some goods ordered over the communication session to the customer at a specified address or location. Alternatively, the agent may update the brand to provide its services to the customer. For example, the customer may be provided with credentials to access one or more services offered by the brand.

[0074]

[0078] 6 illustrates a computing system architecture 600 including various components in electrical communication with each other using a connection 606, such as a bus, according to some implementations. The exemplary system architecture 600 includes a processing unit (CPU or processor) 604 and system connections 606 coupling various system components, including a system memory 620, such as a ROM 618 and a RAM 616, to the processor 604. The system architecture 600 may include a cache 602 of high-speed memory connected directly to the processor 604, in close proximity to the processor 604, or integrated as part of the processor 604. The system architecture 600 may copy data from the memory 620 and / or storage device 608 to the cache 602 for quick access by the processor 604. In this manner, the cache may provide performance improvements that avoid processor 604 delays while waiting for data. These and other modules may control or be configured to control the processor 604 to perform various actions.

[0075]

[0079] Other system memory 620 may also be available for use. Memory 620 may include multiple different types of memory with different performance characteristics. Processor 604 may include any general purpose processor and hardware or software services, such as service 1 610, service 2 612, and service 3 614 stored in storage device 608, configured to control processor 604 as well as special purpose processors, where software instructions are incorporated into the actual processor design. Processor 604 may be a fully self-contained computing system, including multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0076]

[0080] To enable user interaction with the computing system architecture 600, the input devices 622 can represent any number of input mechanisms, such as a microphone for audio, a touch-sensitive screen for gesture or graphic input, a keyboard, a mouse, motion input, voice, etc. The output devices 624 can also be one or more of several output mechanisms known to those skilled in the art. In some cases, a multimodal system can enable a user to provide multiple types of input to communicate with the computing system architecture 600. The communication interface 626 can generally govern and manage user input and system output. There is no restriction to operating on any particular hardware configuration, and thus the basic features herein can be easily substituted with improved hardware or firmware configurations as they are developed.

[0077]

[0081] The storage device 608 is a non-volatile memory and may be a hard disk or other type of computer-readable medium capable of storing data that is accessible by a computer, such as a magnetic cassette, a flash memory card, a solid-state memory device, a digital versatile disk, a cartridge, RAM 616, ROM 618, and hybrids thereof.

[0078]

[0082] The storage device 608 can include services 610, 612, 614 for controlling the processor 604. Other hardware or software modules are contemplated. The storage device 608 can be connected to a system connection 606. In one aspect, a hardware module performing a particular function can include software components stored in a computer readable medium in relation to the necessary hardware components, such as the processor 604, the connection 606, the output device 624, etc., to perform that function.

[0079]

[0083] The disclosed methods may be performed using a computing system. An exemplary computing system may include a processor (e.g., a central processing unit), a memory, a non-volatile memory, and an interface device. The memory may store data and / or one or more sets of code, software, scripts, etc. The components of the computer system may be coupled together via a bus or through some other known or convenient device. The processor may be configured, for example, to perform all or part of the methods described herein by executing code stored in the memory, for example. One or more of the user device or computer, the provider server or system, or the suspended database update system may include components of a computing system or variations of such systems.

[0080]

[0084] The present disclosure contemplates a computer system taking any suitable physical form, including, but not limited to, a point-of-sale system ("POS"). By way of example and not limitation, the computer system may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (e.g., a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile phone, a personal digital assistant (PDA), a server, or a combination of two or more of these. Where appropriate, the computer system may include one or more computer systems that are unitary or distributed, across multiple locations, across multiple machines, and / or reside in a cloud that may include one or more cloud components in one or more networks. Where appropriate, the one or more computer systems may perform one or more steps of one or more methods described or illustrated herein without substantial spatial or temporal limitations. By way of example and not limitation, the one or more computer systems may perform one or more steps of one or more methods described or illustrated herein in real time or in batch mode. One or more computer systems may perform one or more steps of one or more methods described or illustrated herein at different times or at different locations, where appropriate.

[0081]

[0085] The processor may be, for example, a conventional microprocessor such as an Intel Pentium microprocessor or a Motorola Power PC microprocessor. Those skilled in the relevant art will recognize that the terms "machine-readable (storage) medium" or "computer-readable (storage) medium" include any type of device that can be accessed by a processor.

[0082]

[0086] The memory may be coupled to the processor, for example, by a bus. The memory may include, by way of example and not limitation, random access memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). The memory may be local, remote, or distributed.

[0083]

[0087] The bus may also couple the processor to non-volatile memory and drive units. Non-volatile memory is often a magnetic floppy disk or hard disk, a magneto-optical disk, an optical disk, a CD-ROM, a read-only memory (ROM) such as an EPROM or EEPROM, a magnetic or optical card, or another form of storage for large amounts of data. Part of this data is often written to the memory during the execution of software in the computer by a direct memory access process. Non-volatile storage may be local, remote, or distributed. Non-volatile storage is optional since a system may be created with all applicable data available in the memory. A typical computer system usually includes at least a processor, a memory, and a device (e.g., a bus) that couples the memory to the processor.

[0084]

[0088] The software may be stored in a non-volatile memory and / or a drive unit. In fact, for large programs, it may not even be possible to store the entire program in memory. Nevertheless, it should be understood that in order for the software to run, it is moved, when necessary, to a computer-readable location suitable for processing, and for purposes of explanation, that location is referred to herein as memory. Even when the software is moved to memory for execution, the processor may utilize hardware registers to store values ​​related to the software, and ideally, a local cache that serves to speed up execution. As used herein, a software program is assumed to be stored in any known or convenient location (from non-volatile storage to hardware registers) when the software program is referred to as being "implemented in a computer-readable medium." A processor is considered to be "configured to execute a program" when at least one value related to the program is stored in a register readable by the processor.

[0085]

[0089] The bus may also couple the processor to a network interface device. The interface may include one or more of a modem or a network interface. It will be appreciated that the modem or network interface may be considered to be part of the computer system. The interface may include an analog modem, an integrated services digital network (ISDN0 modem, a cable modem, a token ring interface, a satellite transmission interface (e.g., "Direct PC"), or other interface for coupling the computer system to other computer systems. The interface may include one or more input and / or output (I / O) devices. The I / O devices may include, by way of example and not limitation, a keyboard, a mouse or other pointing device, a disk drive, a printer, a scanner, and other input and / or output devices including a display device. The display device may include, by way of example and not limitation, a cathode ray tube (CRT), a liquid crystal display (LCD), or any other applicable known or convenient display device.

[0086]

[0090] In operation, a computer system may be controlled by operating system software, including a file management system, such as a disk operating system. One example of operating system software with its associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Washington, and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux® operating system and its associated file management system. The file management system may be stored in non-volatile memory and / or the drive unit, and may cause the processor to perform various actions required for the operating system to input and output data and store data in memory, including storing files on the non-volatile memory and / or the drive unit.

[0087]

[0091] Some portions of the detailed descriptions may be presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, primarily for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0088]

[0092] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.Unless otherwise indicated, and as will be apparent from the following description, it will be appreciated that throughout the description, descriptions utilizing terms such as "processing" or "calculating" or "computing" or "determining" or "displaying" or "generating" refer to the acts and processes of a computer system or similar electronic computing device that manipulates and converts data represented as physical (electronic) quantities in the computer system's registers and memory into other data that is similarly represented as physical quantities in the computer system's memory or registers or other such information storage, transmission or display device.

[0089]

[0093] The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform some example methods. The required structure for a variety of these systems will appear from the description below. In addition, the techniques are not described with reference to any particular programming language, and thus the various examples may be implemented using a variety of programming languages.

[0090]

[0094] In various implementations, the system may operate as a standalone device or may be connected (e.g., networked) to other systems. In a networked deployment, the system may operate in the capacity of a server or a client system in a client-server network environment, or as a peer system in a peer-to-peer (or distributed) network environment.

[0091]

[0095] The system may be a server computer, a client computer, a personal computer (PC), a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, a Blackberry, a processor, a telephone, a web appliance, a network router, a switch or bridge, or any system capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by the system.

[0092]

[0096] Although a machine-readable medium or machine-readable storage medium is shown as being a single medium by way of example, the terms "machine-readable medium" and "machine-readable storage medium" should be interpreted to include a single medium or multiple media (e.g., a centralized or distributed database and / or associated caches and servers) that store one or more sets of instructions. The terms "machine-readable medium" and "machine-readable storage medium" are also intended to include any medium capable of storing, encoding, or carrying a set of instructions for a system to execute, causing the system to perform any one or more of the methods or modules disclosed herein.

[0093]

[0097] Generally, the routines executed to implement implementations of the present disclosure may be implemented as parts of an operating system or a specific application, component, program, object, module or set of instructions referred to as a "computer program." A computer program generally comprises one or more sets of instructions at different times in various memory and storage devices in the computer that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to implement elements involved in various aspects of the present disclosure.

[0094]

[0098] Furthermore, while the examples have been described in the context of fully functional computers and computer systems, those skilled in the art will appreciate that the various examples may be distributed as program objects in a variety of forms, and that the present disclosure applies equally regardless of the particular type of machine or computer-readable medium used to actually affect the distribution.

[0095]

[0099] Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable-type media such as volatile and non-volatile memory devices, floppy disks and other removable disks, hard disk drives, optical disks (e.g., compact disks read-only (CD ROM), digital versatile disks (DVD), etc.), and transmission-type media such as digital and analog communications links, among others.

[0096]

[0100] In some circumstances, an operation of a memory device, such as a change of state from a binary 1 to a binary 0 or vice versa, may comprise a transformation, such as, for example, a physical transformation. In certain types of memory devices, such a physical transformation may comprise a physical transformation of an article to a different state or thing. For example, but not limited to, for some types of memory devices, a change of state may involve the accumulation and storage of an electric charge or the release of a stored electric charge. Similarly, in other memory devices, a change of state may comprise a physical change or transformation of a magnetic orientation or a physical change or transformation of a molecular structure from crystalline to amorphous or vice versa. The above is not intended to be an exhaustive list of all examples in which a change of state of a binary 1 to a binary 0 or vice versa in a memory device may comprise a transformation, such as a physical transformation. Rather, the above is intended as an illustrative example.

[0097]

[0101] Storage media may generally be non-transitory or comprise a non-transitory device. In this context, non-transitory storage media may include a device that is tangible, meaning that the device has a concrete physical form, but the device may change its physical state. Thus, for example, non-transitory refers to a device that remains tangible despite this change in state.

[0098]

[0102] The above description and drawings are illustrative and should not be construed as limiting the subject matter to the precise form disclosed. Those skilled in the art can appreciate that many modifications and variations are possible in light of the above disclosure. Numerous specific details have been described in order to provide a thorough understanding of the present disclosure. However, in some instances, well-known or conventional details have not been described in order to avoid obscuring the description.

[0099]

[0103] As used herein, the terms "connected," "coupled," or any variation thereof, when applied to modules of a system, refer to any direct or indirect connection or coupling between two or more elements, and the coupling of connections between elements may be physical, logical, or any combination thereof. Additionally, terms such as "herein," "above," "below," and terms of similar import, when used herein, shall refer to this specification as a whole and not to any particular portion of this specification. Where the context permits, terms in the above detailed description using the singular or plural may also include the plural or singular, respectively. The term "or" referring to a list of two or more items covers all of the interpretations of the term: any of the items in the list, all of the items in the list, or any combination of the items in the list.

[0100]

[0104] Those skilled in the art will appreciate that the disclosed subject matter may be embodied in other forms and manners not set forth below. It should be understood that the use of relationship-indicating terms such as first, second, top, and bottom, if any, are used only to distinguish one entity or act from another, without requiring or implying any such actual relationship or order between such entities or acts.

[0101]

[0105] Although processes or blocks are presented in a given order, alternative implementations may perform routines having steps or employ systems having blocks in a different order, and some processes or blocks may be deleted, moved, added, sub-divided, substituted, combined, and / or modified to provide alternative or sub-combinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are sometimes shown as being performed in sequence, these processes or blocks may instead be performed in parallel or at different times. Additionally, any specific numbers referenced herein are examples only, and alternative implementations may employ different values ​​or ranges.

[0102]

[0106] The teachings of the disclosure provided herein may be applied to other systems, not necessarily limited to the systems described above. Elements and acts of the various examples described above may be combined to provide further examples.

[0103]

[0107] Any patents and applications and other references referred to above, including any that may be listed in accompanying application papers, are incorporated herein by reference. Aspects of the present disclosure may be modified, where necessary, to adopt the systems, functions, and concepts of the various references described above to provide yet further examples of the present disclosure.

[0104]

[0108] These and other changes may be made to the present disclosure in light of the above detailed description. Although the above description describes some examples and describes the best modes contemplated, no matter how detailed in text it may appear, the teachings may be implemented in many ways. The details of the system are still encompassed by the subject matter disclosed herein, but may vary widely in its implementation details. As stated above, a particular term used when describing some features or aspects of the present disclosure should not be taken to imply that the term is redefined herein to be limited to any particular characteristic, feature, or aspect of the disclosure with which the term is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the particular implementations disclosed herein, unless the above detailed description section explicitly defines such terms. Thus, the actual scope of the present disclosure encompasses not only the disclosed implementations, but also all equivalent ways of practicing or implementing the present disclosure under the claims.

[0105]

[0109] Although some aspects of the disclosure are presented below in some claim form, the inventors contemplate various aspects of the disclosure in any number of claim forms. Any claim intended to be treated under 35 U.S.C. 112(f) will begin with the phrase "means for." Accordingly, the applicants reserve the right to add additional claims after filing this application to pursue such additional claim forms for other aspects of the disclosure.

[0106]

[0110] The terms used in this specification generally have their ordinary meaning in the art in the specific context in which each term is used within the context of this disclosure. Some terms used to describe this disclosure are explained above or elsewhere in this specification to provide additional guidance to attorneys regarding the description of this disclosure. For convenience, some terms may be highlighted, for example, using capitalization, italics, and / or quotation marks. The use of highlighting has no effect on the scope and meaning of a term, and the scope and meaning of a term is the same in the same context whether it is highlighted or not. It will be appreciated that the same element may be described in more than one way.

[0107]

[0111] Thus, alternative wording and synonyms may be used for any one or more of the terms described herein, and no special importance is placed on whether a term is recited or explained herein. Synonyms for some terms are provided. The recitation of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any term described herein, is merely illustrative and is not intended to further limit the scope and meaning of the disclosure or any exemplified term. Similarly, the disclosure is not limited to the various examples provided herein.

[0108]

[0112] Without intending to further limit the scope of the present disclosure, examples of instruments, devices, methods and their related results according to the examples of the present disclosure are given below. Please note that titles or subtitles may be used in the examples for the convenience of the reader, and in any case, this should not limit the scope of the present disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present disclosure pertains. In case of conflict, this document, including definitions, shall prevail.

[0109]

[0113] Some portions of this specification describe examples in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to effectively convey the substance of their work to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Further, it has proven convenient at times to refer to these configurations of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combination thereof.

[0110]

[0114] Any of the steps, operations, or processes described herein may be performed or implemented using one or more hardware or software modules, alone or in combination with other devices. In some examples, a software module is implemented in a computer program object comprising a computer-readable medium containing computer program code, which may be executed by a computer processor to perform any or all of the steps, operations, or processes described.

[0111]

[0115] Examples may also relate to an apparatus for performing the operations herein. The apparatus may be specially constructed for the required purposes and / or may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a non-transitory tangible computer-readable storage medium or any type of medium suitable for storing electronic instructions that may be coupled to a computer system bus. Furthermore, any computing system referred to herein may include a single processor or may be an architecture employing a multiple processor design to increase computing power.

[0112]

[0116] Examples may also relate to objects generated by the computing processes described herein. Such objects may comprise information resulting from the computing processes, which may be stored on a non-transitory, tangible, computer-readable storage medium, and may include any implementation of the computer program objects or other data combinations described herein.

[0113]

[0117] The language used herein has been selected primarily for ease of reading and instructional purposes, and may not have been selected to delineate or limit the subject matter. Accordingly, the scope of the disclosure is intended to be limited not by this detailed description, but by any claims issued on an application based hereon. Accordingly, the disclosure of the examples is intended to be illustrative, but not limiting, of the scope of the subject matter described in the following claims.

[0114]

[0118] Specific details have been provided in the preceding description to provide a thorough understanding of various implementations of systems and components for a context-connected system. However, those skilled in the art will appreciate that the implementations described above may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail so as to avoid obscuring the embodiments.

[0115]

[0119] It should also be noted that the individual implementations may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe operations as a sequential process, many of the operations may be performed in parallel or simultaneously. Additionally, the order of operations may be rearranged. A process is terminated when its operations are completed, but may have additional steps not included in the diagram. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or to the main function.

[0116]

[0120] The client devices, network devices, and other devices may be computing systems that include, among other things, one or more integrated circuits, input devices, output devices, data storage devices, and / or network interfaces. The integrated circuits may include, among other things, one or more processors, volatile memory, and / or non-volatile memory. The input devices may include, among other things, keyboards, mice, keypads, touch interfaces, microphones, cameras, and / or other types of input devices. The output devices may include, among other things, display screens, speakers, haptic feedback systems, printers, and / or other types of output devices. Data storage devices, such as hard drives or flash memory, may enable the computing device to store data temporarily or permanently. Network interfaces, such as wireless or wired interfaces, may enable the computing device to communicate with a network. Examples of computing devices include desktop computers, laptop computers, server computers, handheld computers, tablets, smartphones, personal digital assistants, digital home assistants, and machines and equipment in which computing devices are embedded.

[0117]

[0121] The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or transporting instructions and / or data. Computer-readable media may include non-transitory media on which data may be stored, which does not include carrier waves and / or transitory electronic signals propagating wirelessly or over wired connections. Examples of non-transitory media may include, but are not limited to, magnetic disks or tapes, optical storage media such as compact disks (CDs) or digital versatile disks (DVDs), flash memory, memory or memory devices. A computer-readable medium may have code and / or machine-executable instructions stored thereon, which may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0118]

[0122] The various examples described above may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments (e.g., computer program product) for performing the necessary tasks may be stored in a computer-readable or machine-readable storage medium (e.g., a medium for storing program code or code segments). A processor implemented in an integrated circuit may perform the necessary tasks.

[0119]

[0123] When a component is described as being "configured to" perform a certain operation, such configuration may be achieved, for example, by designing electronic circuitry or other hardware to perform the operation, by programming a programmable electronic circuitry (e.g., a microprocessor or other suitable electronic circuitry) to perform the operation, or by any combination thereof.

[0120]

[0124] The various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the implementations disclosed herein may be implemented as electronic hardware, computer software, firmware, or a combination thereof. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0121]

[0125] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices, such as a general purpose computer, a wireless communication device handset, or an integrated circuit device having multiple uses, including applications in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together in an integrated logic device, or separately as separate but interoperable logic devices. When implemented in software, the techniques may be realized at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods described above. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise a memory or data storage medium, such as a random access memory (RAM), such as a synchronous dynamic random access memory (SDRAM), a read-only memory (ROM), a non-volatile random access memory (NVRAM), an electrically erasable programmable read-only memory (EEPROM), a FLASH memory, a magnetic or optical data storage medium, or the like. The techniques may additionally or alternatively be realized at least in part by a computer-readable communications medium, such as a propagated signal or radio wave, that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0122]

[0126] The program code may be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such a processor may be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Thus, the term "processor" as used herein may refer to any of the above structures, any combination of the above structures, or any other structure or apparatus suitable for implementing the techniques described herein. Furthermore, in some aspects, the functionality described herein may be provided within dedicated software or hardware modules configured to implement an interrupted database update system.

[0123]

[0127] The above detailed description of the present technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the present technology to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. The described embodiments have been chosen to best explain the principles of the present technology and its practical application, and to enable others skilled in the art to best utilize the present technology in various embodiments with various modifications as may be suitable for the particular applications contemplated. It is intended that the scope of the present technology be defined by the claims. The following is a summary of the claims as originally filed: [C1] 1. A computer-implemented method comprising: receiving a payment request associated with a customer, wherein the payment request is associated with an end agent requiring a payment associated with the customer, and wherein information used to access the payment is not directly accessible by the end agent; sending an authorization request to obtain authorization for the payment, wherein the authorization request, when received at a computing device associated with the customer, is used to prompt the customer for authorization data and the information to be used to access the payment; receiving the authorization data and the information; using the authorization data and the information to obtain the payment, wherein when the authorization data and the information are received at a processing service, the processing service uses the authorization data and the information to collect the payment; and providing a transaction code, where when the transaction code is received by the end agent, the end agent uses the transaction code to obtain the payment without having direct access to the information; A computer-implemented method comprising: [C2] The computer-implemented method of C1, wherein the payment request is received as a result of a determination that the computing device associated with the customer is capable of providing the authorization data using rich messaging. [C3] The computer-implemented method of C1, wherein the information specifies a payment method. [C4] 4. The computer-implemented method of claim 1, wherein the authorization data includes biometric information associated with the customer. [C5] The computer-implemented method of C1, further comprising providing a digital receipt corresponding to the transaction, wherein the digital receipt is presented to the customer when the digital receipt is received at the computing device associated with the customer. [C6] The computer-implemented method of C1, wherein the authorization request is encrypted using a cryptographic key, where the authorization request is decryptable by the computing device associated with the customer. [C7] the authorization data and the information are encrypted using an encryption key of the computing device associated with the customer; the method further comprising decrypting the authorization data and the information. The computer-implemented method of claim 1. [C8] 1. A system comprising: one or more processors; A memory that stores instructions the instructions, when executed by the one or more processors, cause the system to: receiving a payment request associated with a customer, wherein the payment request is associated with an end agent requiring a payment associated with the customer, and wherein information used to access the payment is not directly accessible by the end agent; sending an authorization request to obtain authorization for the payment, wherein the authorization request, when received at a computing device associated with the customer, is used to prompt the customer for authorization data and the information to be used to access the payment; receiving the authorization data and the information; using the authorization data and the information to obtain the payment, wherein when the authorization data and the information are received at a processing service, the processing service uses the authorization data and the information to collect the payment; and providing a transaction code, where when the transaction code is received by the end agent, the end agent uses the transaction code to obtain the payment without having direct access to the information; A system that allows the user to: [C9] The instructions include: sending a query to obtain configuration information for the computing device; using the configuration information of the computing device to determine that the computing device is capable of providing the authorization data using rich messaging; and The system according to C8, further comprising: [C10] The system of C8, wherein the information specifies a payment method. [C11] The system of C8, wherein the authorization request is encrypted using an encryption key, and wherein the second request is decryptable by the computing device associated with the customer. [C12] The system of C8, wherein the instructions further cause the system to send a digital receipt corresponding to the transaction, wherein the digital receipt is presented to the customer when the digital receipt is received at the computing device associated with the customer. [C13] The system of C8, wherein the authorization data includes biometric information associated with the customer. [C14] The system of C8, wherein the communication session is a voice call between the customer and the agent. [C15] A non-transitory computer-readable storage medium having executable instructions stored thereon, the executable instructions, when executed by one or more processors of a computer system, causing the computer system to: receiving a payment request associated with a customer, wherein the payment request is associated with an end agent requiring a payment associated with the customer, and wherein information used to access the payment is not directly accessible by the end agent; sending an authorization request to obtain authorization for the payment, wherein the authorization request, when received at a computing device associated with the customer, is used to prompt the customer for authorization data and the information to be used to access the payment; receiving the authorization data and the information; using the authorization data and the information to obtain the payment, wherein when the authorization data and the information are received at a processing service, the processing service uses the authorization data and the information to collect the payment; and providing a transaction code, where when the transaction code is received by the end agent, the end agent uses the transaction code to obtain the payment without having direct access to the information; A non-transitory computer-readable storage medium that causes [C16] The non-transitory computer-readable storage medium of C15, wherein the payment request is received as a result of a determination that the computing device associated with the customer is capable of providing the authorization data using rich messaging. [C17] The non-transitory computer-readable storage medium of C15, wherein the authorization request is encrypted using an encryption key, wherein the authorization request is decryptable by the computing device associated with the customer. [C18] The non-transitory computer-readable storage medium of C15, wherein the executable instructions further cause the computer system to provide a digital receipt corresponding to the transaction, wherein the digital receipt is presented to the customer when the digital receipt is received at the computing device associated with the customer. [C19] 16. The non-transitory computer-readable storage medium of claim 15, wherein the authorization data includes biometric information associated with the customer. [C20] 16. The non-transitory computer-readable storage medium of claim 15, wherein the authorization data includes biometric information associated with the customer.

Claims

1. A method implemented by a brand messaging platform, comprising: receiving a capabilities request from an end agent to determine a set of capabilities of a customer computing device for submitting a payment associated with the customer computing device, where the capabilities request is received during ongoing communication between a customer and the end agent using a first communication protocol and where the payment is submitted using a second communication protocol; receiving a payment request from the end agent during the ongoing communication, wherein the payment request is for obtaining the payment using the second communication protocol, the payment request being associated with the end agent, and wherein the payment request is received based on the set of capabilities satisfying a predetermined condition; sending an authorization request to the customer computing device during the ongoing communication, wherein the authorization request is sent using the second communication protocol; and receiving authorization data and payment information from the customer computing device during the ongoing communication, wherein the authorization data and the payment information are received using the second communications protocol; and A method comprising:

2. The method of claim 1 , wherein the payment information specifies a payment method.

3. The method of claim 1 , wherein the authorization data includes biometric information associated with the customer.

4. 10. The method of claim 1, further comprising providing a digital receipt corresponding to the payment request, wherein the digital receipt is presented to the customer when the digital receipt is received at the customer computing device.

5. 2. The method of claim 1, wherein the authorization request is encrypted using an encryption key, where the authorization request is decryptable by the customer computing device.

6. the authorization data and the payment information are encrypted using an encryption key associated with the customer computing device; the method further comprising decrypting the authorization data and the payment information. The method of claim 1.

7. A brand messaging platform, comprising: one or more processors; A memory that stores instructions the instructions, when executed by the one or more processors, cause the brand messaging platform to: receiving a capabilities request from an end agent to determine a set of capabilities of a customer computing device for submitting a payment associated with the customer computing device, where the capabilities request is received during ongoing communication between a customer and the end agent using a first communication protocol and where the payment is submitted using a second communication protocol; receiving a payment request from the end agent during the ongoing communication, wherein the payment request is for obtaining the payment using the second communication protocol, the payment request being associated with the end agent, and wherein the payment request is received based on the set of capabilities satisfying a predetermined condition; sending an authorization request to the customer computing device during the ongoing communication, wherein the authorization request is sent using the second communication protocol; and receiving authorization data and payment information from the customer computing device during the ongoing communication, wherein the authorization data and the payment information are received using the second communications protocol; and A brand messaging platform that enables

8. The brand messaging platform of claim 7 , wherein the payment information specifies a payment method.

9. 8. The brand messaging platform of claim 7, wherein the permission request is encrypted using an encryption key, where the permission request is decryptable by the customer computing device.

10. 8. The brand messaging platform of claim 7, wherein the instructions further cause the brand messaging platform to provide a digital receipt corresponding to the payment request, wherein the digital receipt is presented to the customer when the digital receipt is received at the customer computing device.

11. The brand messaging platform of claim 7 , wherein the authorization data includes biometric information associated with the customer.

12. A non-transitory computer-readable storage medium having executable instructions stored thereon, the executable instructions, when executed by one or more processors of a brand messaging platform, causing the brand messaging platform to: receiving a capabilities request from an end agent to determine a set of capabilities of a customer computing device for submitting a payment associated with the customer computing device, where the capabilities request is received during ongoing communication between a customer and the end agent using a first communication protocol and where the payment is submitted using a second communication protocol; receiving a payment request from the end agent during the ongoing communication, wherein the payment request is for obtaining the payment using the second communication protocol, the payment request being associated with the end agent, and wherein the payment request is received based on the set of capabilities satisfying a predetermined condition; sending an authorization request to the customer computing device during the ongoing communication, wherein the authorization request is sent using the second communication protocol; and receiving authorization data and payment information from the customer computing device during the ongoing communication, wherein the authorization data and the payment information are received using the second communications protocol; and A non-transitory computer-readable storage medium for causing

13. 13. The non-transitory computer-readable storage medium of claim 12, wherein the authorization request is encrypted using an encryption key, where the authorization request is decryptable by the customer computing device.

14. 13. The non-transitory computer-readable storage medium of claim 12, wherein the executable instructions further cause the branded messaging platform to provide a digital receipt corresponding to the payment request, wherein the digital receipt is presented to the customer when the digital receipt is received at the customer computing device.

15. The non-transitory computer-readable storage medium of claim 12 , wherein the authorization data includes biometric information associated with the customer.

16. The method of claim 1, wherein the second communication protocol is a Rich Communication Services (RCS) protocol.

17. The method of claim 17, wherein the authorization data and the payment information are encrypted using an encryption key associated with the customer computing device; the instructions further cause the brand messaging platform to decrypt the authorization data and the payment information. The brand messaging platform of claim 7.

18. The branded messaging platform of claim 7, wherein the second communication protocol is a Rich Communication Services (RCS) protocol.

19. The non-transitory computer-readable storage medium of claim 12, wherein the payment information specifies a payment method.

20. The method of claim 1, wherein the authorization data and the payment information are encrypted using an encryption key associated with the customer computing device; The executable instructions further cause the brand messaging platform to decrypt the authorization data and the payment information.

13. The non-transitory computer-readable storage medium of claim 12.

21. The non-transitory computer-readable storage medium of claim 12, wherein the second communication protocol is a Rich Communication Services (RCS) protocol.

Citation Information

Patent Citations

  • Intermediary payment system and method

    JP2018120619A

  • Information processing unit and information processing method

    JP2020017786A