CN116228244A - Method and device for providing service information and service assembly - Google Patents

Method and device for providing service information and service assembly Download PDF

Info

Publication number
CN116228244A
CN116228244A CN202310127721.8A CN202310127721A CN116228244A CN 116228244 A CN116228244 A CN 116228244A CN 202310127721 A CN202310127721 A CN 202310127721A CN 116228244 A CN116228244 A CN 116228244A
Authority
CN
China
Prior art keywords
payment
user
service
information
solution
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310127721.8A
Other languages
Chinese (zh)
Inventor
皮达峰
林燕燕
朱泉龙
钱婵
陈思颖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Alibaba Overseas Internet Industry Co ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202310127721.8A priority Critical patent/CN116228244A/en
Publication of CN116228244A publication Critical patent/CN116228244A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0281—Customer communication at a business location, e.g. providing product or service information, consulting

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The embodiment of the application discloses a method, a device and a service component for providing service information, wherein the method comprises the following steps: monitoring a system response message after the user executes the payment operation in the payment page; if the payment failure event is determined according to the monitored system response message, acquiring corresponding error type identification information; determining a solution configured in advance for the error type identification information, and providing service information to the user according to the solution. By the embodiment of the application, more timely and deterministic service can be provided for the user, so that the user can be helped to solve the problems in the payment process.

Description

Method and device for providing service information and service assembly
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to a method and an apparatus for providing service information, and a service component.
Background
In merchandise information service systems, consumer users typically experience long links from merchandise information viewing to final order generation and payment, any of which may result in a transaction failure if a problem occurs. In particular, in a system involving cross-border commodity transaction, the link may be longer, and the problems that may occur may be more diverse, for example, in a cross-border commodity transaction scenario, for the payment link, since the involved cross-border payment manner may be relatively more and may not be a common payment manner of daily online transaction, if a transaction failure or the like occurs, a user may be required to contact a system customer service personnel or a customer service robot to help solve the problem. However, in the process of dictating the problems encountered by the user, the user may have situations of inaccurate description and even unaware of how to describe, so that the customer service personnel or the customer service robot may have difficulty in understanding the problems of the user, or cannot fully restore the real scene or the error reasons encountered by the user, and cannot be provided with insight into the core problems to be solved after the buyer encounters the abnormality, so that the provided solution is relatively one-sided, and the problems cannot be fundamentally solved. In addition, even if the user's problem can be understood, because the application system such as cross-border transaction is more complex, it may also require a customer service person or a robot to answer by requiring multiple queries, which may affect the problem solving efficiency and user experience.
Disclosure of Invention
The method, the device and the service component for providing the service information can provide more timely and deterministic service for the user, so that the user is helped to solve the problems in the payment process, and the user experience is improved.
The application provides the following scheme:
a method of providing service information, comprising:
monitoring a system response message after the user executes the payment operation in the payment page;
if the payment failure event is determined according to the monitored system response message, acquiring corresponding error type identification information;
determining a solution configured in advance for the error type identification information, and providing service information to the user according to the solution.
The obtaining the corresponding error type identification information includes:
and acquiring error type identification information included in the system response message.
Wherein said providing service information to said user according to said solution comprises:
providing operation options for acquiring the service in a payment failure result page;
and after receiving a request of a user through the operation options, displaying a dialogue window for dialogue with a manual customer service or a robot customer service, and displaying information about the solution in the dialogue window.
Wherein said providing service information to said user according to said solution comprises:
if customer service components are mounted in the payment failure result page, a dialogue window is popped up by calling the customer service components, and information about the solution is displayed in the dialogue window.
Wherein said providing service information to said user according to said solution comprises:
and determining a touch mode of service information according to the solution, and providing the service information for the user through the touch mode.
The method is applied to the service components embedded in the payment page.
A service component for performing the following processing after embedding into a target page:
monitoring a system response message after a user executes target operation in the target page;
if the operation failure is determined according to the monitored system response message, acquiring corresponding error type identification information;
determining a solution configured for the error type identification information in advance, and providing service information to the user according to the solution.
A method of providing service information, comprising:
receiving payment operation executed by a user through a payment page;
if a payment failure event is generated, displaying a payment failure result page;
providing corresponding service information for the user based on the payment failure result page, wherein the service information is generated according to error type identification information corresponding to the payment failure event and a solution configured for the error type identification information in advance.
Wherein the providing corresponding service information to the user based on the payment failure result page includes:
providing operation options for acquiring service information in the payment failure result page;
and after receiving a request of a user through the operation options, displaying a dialogue window for dialogue with a manual customer service or a robot customer service, and displaying the service information in the dialogue window.
Wherein, customer service components are mounted in the payment failure result page;
the providing corresponding service information to the user based on the payment failure result page includes:
and popping up a dialogue window in the payment failure result page in a mode of calling the customer service component, and displaying corresponding service information in the dialogue window.
An apparatus for providing service information, comprising:
the monitoring unit is used for monitoring the system response message after the user executes the payment operation in the payment page;
the error type identification determining unit is used for acquiring corresponding error type identification information if a payment failure event is determined according to the monitored system response message;
and the service information providing unit is used for determining a solution configured for the error type identification information in advance and providing service information for the user according to the solution.
An apparatus for providing service information, the apparatus being applied to a service component for embedding into a target page, the apparatus comprising:
the monitoring unit is used for monitoring a system response message after the user executes the target operation in the target page;
the error type identification determining unit is used for acquiring corresponding error type identification information if the operation failure is determined according to the monitored system response message;
and the service information providing unit is used for determining a solution configured for the error type identification information in advance and providing service information for the user according to the solution.
An apparatus for providing service information, comprising:
a payment operation receiving unit for receiving a payment operation performed by a user through a payment page;
the page display unit is used for displaying a payment failure result page if a payment failure event is generated;
and the service information providing unit is used for providing corresponding service information for the user based on the payment failure result page, wherein the service information is generated according to error type identification information corresponding to the payment failure event and a solution configured for the error type identification information in advance.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method of any of the preceding claims.
An electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the steps of the method of any of the preceding claims.
According to a specific embodiment provided by the application, the application discloses the following technical effects:
by the scheme provided by the embodiment of the application, the system response message after the user executes the payment operation in the payment page can be monitored, if the payment failure event is monitored, the corresponding error type identification information can be acquired, the solution configured for the error type identification information in advance can be determined, and the service information can be provided for the user according to the solution. By the method, the corresponding solution can be provided according to the monitored error type identification, and the user is not required to describe the problem encountered by the user, so that the problem cannot be solved because the user does not know how to describe the problem, or the core problem of the user cannot be solved because customer service personnel cannot comprehensively restore the real scene and the error reporting reason encountered by the user. In addition, because the solution corresponding to the specific error type identifier can be preconfigured, multi-terminal inquiry is not needed, more deterministic service information can be provided for the user more timely, so that the user is practically helped to solve the problems in the payment process, the user experience is improved, and the achievement of specific transactions is facilitated.
Of course, not all of the above-described advantages need be achieved at the same time in practicing any one of the products of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application;
FIG. 2 is a flow chart of a first method provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of a first interface provided by an embodiment of the present application;
FIG. 4 is a schematic diagram of a second interface provided by an embodiment of the present application;
FIG. 5 is a flow chart of a second method provided by an embodiment of the present application;
FIG. 6 is a schematic diagram of a first apparatus provided in an embodiment of the present application;
FIG. 7 is a schematic diagram of a second apparatus provided in an embodiment of the present application;
fig. 8 is a schematic diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.
It should be noted that, in implementing the present application, the inventor of the present application finds that, in the merchandise information service system, from merchandise browse to order to pay, although the link is relatively long, if the payment node has been performed and the payment operation is performed, it means that the payment will of the user is very clear, and the current transaction can be completed as long as the payment is successful, so the payment operation plays a role of "one-touch" in the whole transaction link, and its importance is self-evident. However, if the user encounters a problem during the payment process, that is, after the user initiates the payment, the result of the payment failure is received, at this time, if the system cannot help the user to solve the problem in time (although the user may describe his own problem through the customer service system and seek help, as described in the background section, there may be a problem that the user cannot describe clearly, or the customer service personnel may take a relatively long time to find a solution, etc., which may result in the failure to help the user solve the problem in time), the transaction may fail, even the user may choose to cancel the order because of losing the patience, etc. That is, the failure of a transaction occurs after the user has made an explicit willingness to pay, which is a relatively tiring situation for the system or vendor user.
In view of the above, an object of the embodiments of the present application is to, after a user enters a payment link for an order, if a problem is encountered in a payment process to cause a payment failure, discover the situation in time and provide a deterministic solution for the user in time, so as to actually help the user to solve the problem encountered in the payment process. To achieve the objective, the embodiments of the present application may provide a service component of a SDK (Software Development Kit ) or the like, which may be embedded in a payment page for monitoring a message or the like generated in the payment page, where a system response message given by a payment system after a user performs a payment operation may be included. By monitoring the system response message, whether the payment failure occurs or not can be determined, and if the payment failure occurs, specific error type identifiers such as error codes and the like can be obtained from the payment system. In this way, the specific service component can timely learn of the payment failure event, and can explicitly learn of the specific error type identification. On the other hand, the service component can also store configuration information, the configuration information can be configured in advance by operators and the like, specifically, various error type identifiers which can occur in a payment process can be collected, then, which error type identifiers can trigger active service can be determined, for the error type identifiers needing to trigger the active service, the mapping relationship between the specific error type identifiers and solutions (which can be text information or links and the like) can be configured according to specific corresponding error reasons and the like, and in an optional manner, the touch mode (for example, manual customer service, robot customer service, mail, outbound call, system message notification and the like) of the specific service information can be configured. In this way, after the payment failure event is monitored and the corresponding error type identifier is determined, the corresponding solution can be automatically analyzed according to the configured mapping relationship, and then service information can be provided for the user according to the solution.
By the intelligent processing mode, the user is provided with service under the condition that events such as payment failure are monitored and specific error type identification is known, the user does not need to describe the problems encountered by the user, and the specific solution can be preconfigured and finished without multi-terminal inquiry, so that more deterministic service can be provided for the user more timely, the user can solve the problems encountered in the payment process timely, and the probability of transaction failure under the condition that the user has clear payment will is reduced.
From the system architecture perspective, referring to fig. 1, the embodiment of the present application may be applied to a merchandise information service system, where the system may include a client and a server. In addition, a service component in the form of an SDK (software development kit) and the like can be provided, the service component can be embedded into a payment page of a client, when a user executes payment operation on a specific transaction order through the payment page, the service component can realize information interaction with a payment system, namely, information such as a specific system response message and the like can be acquired from the payment system, and if a payment failure event is detected, specific error type identification information can also be acquired. In addition, by configuring a mapping relation between the error type identifier and the solution in the service component in advance, after a specific payment failure event is monitored and the corresponding error type identifier is determined, service information can be provided for the user according to the solution in the mapping relation. The specific service information may be presented to the user in various ways, including a conversation window of a customer service component, or a system message notification, or a mail/short message system, or a telephone call, etc. Of course, in a specific implementation, the code for providing the service may also be implemented directly in the specific payment page, so that the payment page itself has the capability of providing the service. In addition, for the service components in the specific SDK form, the service components can be embedded into payment pages and other pages with similar requirements, and the mapping relation information of the configuration can be correspondingly adjusted.
Specific embodiments provided in the embodiments of the present application are described in detail below.
Example 1
First, the first embodiment provides a method for providing service information, and an execution subject of the method may be a service component embedded in a payment page, or may also be a service module implemented in the payment page, or the like. Specifically, referring to fig. 2, the method may include:
s201: and monitoring a system response message after the user executes the payment operation in the payment page.
The payment page may specifically be a page for performing payment operation on a specific transaction order, that is, a page entered after completing order information confirmation and clicking on "pay-off" and other operation options, where a plurality of different payment modes may be displayed for the user to select for use, including a plurality of selectable bank cards, or a balance pre-stored in a system account, and so on. After the user selects a certain payment mode and clicks the option of "pay" in the payment page, the payment operation is performed. After the user performs the payment operation, the system may respond, including a successful payment, or a failure of the payment, etc. In the embodiment of the application, the service component is embedded in the payment page, or the function module related to the specific service is implemented in the payment page, so that the monitoring of the system response message can be implemented through the service component or the function module.
Specifically, there may be multiple ways to monitor the system response message, for example, in one way, a relevant interface for providing the system response message in the payment system may be determined in advance, and the service component or the functional module may monitor the specific system response message by monitoring the specific interface, etc. Alternatively, the system may also negotiate with the payment system, and when the payment system returns a system response message, the system response message may be synchronously provided to the SDK component or related functional module in the payment page, so as to monitor the system response message, and so on.
S202: and if the payment failure event is determined according to the monitored system response message, acquiring corresponding error type identification information.
After the system response message is monitored, information about the success or failure of payment can be included, and after the event of the failure of payment is determined, corresponding error type identification information can be obtained. That is, there may be various reasons for specifically making the payment failure, including a platform risk control class (e.g., some users may be recognized by the system that there is a "swipe" action, at which time the user may not be allowed to pay), or a bank card (e.g., a bank card has insufficient balance), or a bank specified reason (e.g., an opening operation may be required when online payment is made using a bank card of a certain bank), etc. Different failure reasons may correspond to different error codes (i.e. error type identifiers), and a system response message returned by the payment system may carry a specific error code, so that the service component or module may learn a payment failure event from the system response message and acquire specific error code information. Of course, in a specific implementation, if the system response message does not carry the error code information, the service component or the service module may also query the specific error code information by initiating a query request to the payment system, and so on.
S203: determining a solution configured in advance for the error type identification information, and providing service information to the user according to the solution.
After determining the error type identification, a solution configured for the error type identification information in advance can be determined from the pre-stored configuration information, and then the service can be provided for the user according to the solution. The specific solution may include text information or links, for example, if the reason for the payment failure corresponding to the specific error type is that the balance of the currently selected bank card is insufficient, the user may be prompted to replace other bank cards by the text information to make the payment. Alternatively, if the reason for the failure of payment is that the opening operation needs to be performed first, a specific solution may include performing a link corresponding to the opening operation, and so on. Thus, after providing the service information to the user according to the specific solution, the user can perform the operation according to the prompt in the specific service information and solve the corresponding problem, and then re-execute the payment operation, at this time, a successful payment result can be obtained generally.
When the solution provides service to the user, in one mode, active service mode can be adopted, that is, the user is not required to describe the problems to customer service, and the specific solution can be provided to the user directly. Specifically, in the case of displaying a payment page on a PC (computer) side, a customer service component can be generally mounted in the specific payment failure result display page, so that a user can communicate with customer service at any time when encountering a problem; in this case, the service component or the service module in the embodiment of the present application may call a specific customer service component, so that a dialog window may be popped up in the payment failure result display page, and information about the solution may be displayed in the dialog window. For example, as shown in fig. 3, in the case of a PC-side presentation, after presenting a payment failure result presentation page, a customer service dialog box may be automatically popped up in the page and corresponding solution information presented therein, for example, as shown at 31 in fig. 3, to help the user solve a specifically encountered payment problem. Of course, the user may also continue to talk to the customer service through the talk window to obtain further assistance.
In the case of displaying a payment page on a mobile terminal, because the area of the payment page is limited, the payment page is not suitable for too high information display density, and therefore, operation options for acquiring the service can be provided in a payment failure result display page, so that after receiving a request of a user through the operation options, a dialogue window for conducting dialogue with a manual customer service or a robot customer service can be displayed, and information about the solution can be displayed in the dialogue window. That is, in the case of the mobile terminal, the customer service dialog window may not be directly popped up, but may be presented after the user clicks a specific operation option. For example, as shown in fig. 4, the "customer service" shown at 41 may correspond to an operation option described in the embodiments of the present application, and after the user finds that payment fails, the user may obtain specific service information by clicking on the operation option. In particular, the avatar shown at 41 may be provided with a moving effect to draw attention of the user, for example, the avatar may be made to slide left and right within a certain area, or a moving effect of a rotating effect may be provided, or the like. After the user clicks the operation option, the user can automatically display the solution information corresponding to the specifically monitored error type identification in the pop-up dialogue window without describing the problems encountered by the user, and the user can solve the problems encountered by the user according to the solution information.
It should be noted that, in a specific implementation, a touch manner of service information may also be determined according to a specific solution, so as to provide services to the user according to the touch manner. For example, a specific touch-up may include the foregoing customer service components, or may also include system messages, mail, outgoing calls, etc.
In summary, by the solution provided by the embodiment of the present application, a system response message after a user performs a payment operation in a payment page may be monitored, if a payment failure event is monitored, corresponding error type identification information may be obtained, a solution configured for the error type identification information in advance may be determined, and service information may be provided to the user according to the solution. By the method, the corresponding solution can be provided according to the monitored error type identification, and the user is not required to describe the problem encountered by the user, so that the problem cannot be solved because the user does not know how to describe the problem, or the core problem of the user cannot be solved because customer service personnel cannot comprehensively restore the real scene and the error reporting reason encountered by the user. In addition, because the solution corresponding to the specific error type identifier can be preconfigured, multi-terminal inquiry is not needed, more deterministic service information can be provided for the user more timely, so that the user is practically helped to solve the problems in the payment process, the user experience is improved, and the achievement of specific transactions is facilitated.
Example two
As described in the first embodiment, in a specific implementation, a service component in the form of an SDK or the like may be provided, and by embedding the service component in a payment page, a function of monitoring a system response message and identifying corresponding solution configuration information according to the monitored error type may be provided to provide service information for a user. In addition, in practical application, the service component can be embedded into other pages, and the mapping relation between the specific problem type identifier and the solution is modified according to the possible problems in the specific page. Specifically, the second embodiment provides a service component, specifically, the service component is configured to be embedded in a target page, and then the service component may perform the following processing: and monitoring a system response message after the user executes the target operation in the target page, if the operation failure is determined according to the monitored system response message, acquiring corresponding error type identification information, determining a solution configured for the error type identification information in advance, and providing service for the user according to the solution.
Example III
The third embodiment provides a method for providing service information from the perspective of user interaction of a client, referring to fig. 5, the method may include:
s501: receiving payment operation executed by a user through a payment page;
s502: if a payment failure event is generated, displaying a payment failure result page;
s503: providing corresponding service information for the user based on the payment failure result page, wherein the service information is generated according to error type identification information corresponding to the payment failure event and a solution configured for the error type identification information in advance.
Specifically, for the scenes such as the mobile terminal, an operation option for acquiring service information can be provided in the payment failure result page; after receiving the request of the user through the operation options, displaying a dialogue window for dialogue with the manual customer service or the robot customer service, and displaying the service information in the dialogue window.
Or for the scenes such as the PC end, if the customer service component is mounted in the payment failure result page, a dialogue window is popped up in the payment failure result page in a mode of automatically calling the customer service component, and corresponding service information is displayed in the dialogue window.
For the undescribed parts in the second and third embodiments, reference may be made to the description of the first embodiment and other parts in this specification, and the description is omitted here.
It should be noted that, in the embodiments of the present application, the use of user data may be involved, and in practical applications, user specific personal data may be used in the schemes described herein within the scope allowed by applicable legal regulations in the country where the applicable legal regulations are met (for example, the user explicitly agrees to the user to actually notify the user, etc.).
Corresponding to the first embodiment of the foregoing method, the embodiment of the present application further provides an apparatus for providing service information, referring to fig. 6, the apparatus may include:
a monitoring unit 601, configured to monitor a system response message after a user performs a payment operation in a payment page;
an error type identification determining unit 602, configured to obtain corresponding error type identification information if a payment failure event is determined according to the monitored system response message;
a service information providing unit 603 for determining a solution configured in advance for the error type identification information and providing a service to the user according to the solution.
In a specific implementation, the error type identification determining unit may specifically be configured to:
and acquiring error type identification information included in the system response message.
Wherein, the service information providing unit may specifically be configured to:
providing operation options for acquiring the service in a payment failure result page;
and after receiving a request of a user through the operation options, displaying a dialogue window for dialogue with a manual customer service or a robot customer service, and displaying information about the solution in the dialogue window.
Alternatively, the service information providing unit may be configured to:
if customer service components are mounted in the payment failure result page, a dialogue window is popped up by calling the customer service components, and information about the solution is displayed in the dialogue window.
In addition, in a specific implementation, the service information providing unit may specifically be configured to:
and determining a touch mode of service information according to the solution, and providing the service information for the user through the touch mode.
In particular, the apparatus may be applied to service components embedded in a payment page.
Corresponding to the embodiment, the embodiment of the application also provides a device for providing service information, which is applied to a service component, wherein the service component is used for being embedded into a target page, and the device can comprise:
the monitoring unit is used for monitoring a system response message after the user executes the target operation in the target page;
the error type identification determining unit is used for acquiring corresponding error type identification information if the operation failure is determined according to the monitored system response message;
and the service information providing unit is used for determining a solution configured for the error type identification information in advance and providing service information for the user according to the solution.
Corresponding to the embodiment, the embodiment of the application further provides an apparatus for providing service information, referring to fig. 7, the apparatus may include:
a payment operation receiving unit 701, configured to receive a payment operation performed by a user through a payment page;
a page display unit 702, configured to display a payment failure result page if a payment failure event is generated;
a service information providing unit 703, configured to provide corresponding service information to the user based on the payment failure result page, where the service information is generated according to error type identification information corresponding to the payment failure event and a solution configured for the error type identification information in advance.
Wherein, the service information providing unit may specifically be used for:
providing operation options for acquiring service information in the payment failure result page;
and after receiving a request of a user through the operation options, displaying a dialogue window for dialogue with a manual customer service or a robot customer service, and displaying the service information in the dialogue window.
Or if customer service components are mounted in the payment failure result page, the service information providing unit may specifically be configured to:
and popping up a dialogue window in the payment failure result page in a mode of calling the customer service component, and displaying corresponding service information in the dialogue window.
In addition, the embodiment of the application further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the method of any one of the foregoing method embodiments.
And an electronic device comprising:
one or more processors; and
a memory associated with the one or more processors for storing program instructions that, when read for execution by the one or more processors, perform the steps of the method of any of the preceding method embodiments.
Fig. 8, among other things, illustrates an architecture of an electronic device, for example, device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, an aircraft, and so forth.
Referring to fig. 8, device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods provided by the disclosed subject matter. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and the like. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 806 provides power to the various components of the device 800. The power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 800.
The multimedia component 808 includes a screen between the device 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data when the device 800 is in an operational mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the device 800. For example, the sensor assembly 814 may detect an on/off state of the device 800, a relative positioning of the components, such as a display and keypad of the device 800, the sensor assembly 814 may also detect a change in position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, an orientation or acceleration/deceleration of the device 800, and a change in temperature of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication between the device 800 and other devices, either wired or wireless. The device 800 may access a wireless network based on a communication standard, such as WiFi, or a mobile communication network of 2G, 3G, 4G/LTE, 5G, etc. In one exemplary embodiment, the communication part 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including instructions executable by processor 820 of device 800 to perform the methods provided by the disclosed subject matter. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the embodiments or some parts of the embodiments of the present application.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a system or system embodiment, since it is substantially similar to a method embodiment, the description is relatively simple, with reference to the description of the method embodiment being made in part. The systems and system embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing has described in detail the methods, apparatuses and service components for providing service information provided by the present application, and specific examples have been applied herein to illustrate the principles and embodiments of the present application, where the foregoing examples are provided to assist in understanding the methods and core ideas of the present application; also, as will occur to those of ordinary skill in the art, many modifications are possible in view of the teachings of the present application, both in the detailed description and the scope of its applications. In view of the foregoing, this description should not be construed as limiting the application.

Claims (12)

1. A method of providing service information, comprising:
monitoring a system response message after the user executes the payment operation in the payment page;
if the payment failure event is determined according to the monitored system response message, acquiring corresponding error type identification information;
determining a solution configured in advance for the error type identification information, and providing service information to the user according to the solution.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the obtaining the corresponding error type identification information includes:
and acquiring error type identification information included in the system response message.
3. The method of claim 1, wherein the step of determining the position of the substrate comprises,
said providing service information to said user according to said solution comprising:
providing operation options for acquiring the service in a payment failure result page;
and after receiving a request of a user through the operation options, displaying a dialogue window for dialogue with a manual customer service or a robot customer service, and displaying information about the solution in the dialogue window.
4. The method of claim 1, wherein the step of determining the position of the substrate comprises,
said providing service information to said user according to said solution comprising:
if customer service components are mounted in the payment failure result page, a dialogue window is popped up by calling the customer service components, and information about the solution is displayed in the dialogue window.
5. The method of claim 1, wherein the step of determining the position of the substrate comprises,
said providing service information to said user according to said solution comprising:
and determining a touch mode of service information according to the solution, and providing the service information for the user through the touch mode.
6. The method of claim 1, wherein the method is applied to service components embedded in a payment page.
7. A service component is characterized in that,
after the service component is used for being embedded into the target page, the following processing is executed:
monitoring a system response message after a user executes target operation in the target page;
if the operation failure is determined according to the monitored system response message, acquiring corresponding error type identification information;
determining a solution configured for the error type identification information in advance, and providing service information to the user according to the solution.
8. A method of providing service information, comprising:
receiving payment operation executed by a user through a payment page;
if a payment failure event is generated, displaying a payment failure result page;
providing corresponding service information for the user based on the payment failure result page, wherein the service information is generated according to error type identification information corresponding to the payment failure event and a solution configured for the error type identification information in advance.
9. The method of claim 8, wherein the step of determining the position of the first electrode is performed,
the providing corresponding service information to the user based on the payment failure result page includes:
providing operation options for acquiring service information in the payment failure result page;
and after receiving a request of a user through the operation options, displaying a dialogue window for dialogue with a manual customer service or a robot customer service, and displaying the service information in the dialogue window.
10. The method of claim 8, wherein the step of determining the position of the first electrode is performed,
customer service components are mounted in the payment failure result page;
the providing corresponding service information to the user based on the payment failure result page includes:
and popping up a dialogue window in the payment failure result page in a mode of calling the customer service component, and displaying corresponding service information in the dialogue window.
11. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the steps of the method of any one of claims 1 to 6, 8 to 10.
12. An electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors for storing program instructions that, when read for execution by the one or more processors, perform the steps of the method of any of claims 1 to 6, 8 to 10.
CN202310127721.8A 2023-02-01 2023-02-01 Method and device for providing service information and service assembly Pending CN116228244A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310127721.8A CN116228244A (en) 2023-02-01 2023-02-01 Method and device for providing service information and service assembly

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310127721.8A CN116228244A (en) 2023-02-01 2023-02-01 Method and device for providing service information and service assembly

Publications (1)

Publication Number Publication Date
CN116228244A true CN116228244A (en) 2023-06-06

Family

ID=86572679

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310127721.8A Pending CN116228244A (en) 2023-02-01 2023-02-01 Method and device for providing service information and service assembly

Country Status (1)

Country Link
CN (1) CN116228244A (en)

Similar Documents

Publication Publication Date Title
WO2016045277A1 (en) Method, device, and system for information acquisition
WO2023045220A1 (en) Information interaction method and apparatus
EP3731088A1 (en) Method and device for displaying information and storage medium
CN111667328B (en) Page content display method and device and electronic equipment
CN114025181B (en) Information display method and device, electronic equipment and storage medium
CN108011990B (en) Contact management method and device
CN112291631A (en) Information acquisition method, device, terminal and storage medium
CN113556614B (en) Information release method and device and electronic equipment
CN113031837B (en) Content sharing method and device, storage medium, terminal and server
CN110347460B (en) Prompting method and device
US20170201479A1 (en) Group message display method, device and medium
CN111211963A (en) Chat group joining method and device, electronic equipment and storage medium
CN116228244A (en) Method and device for providing service information and service assembly
CN114443160A (en) Message pushing method and device, electronic equipment and storage medium
CN114596131A (en) Commodity information processing method and device and electronic equipment
CN110162366B (en) Information display method and device, electronic equipment and storage medium
CN109889662B (en) Information forwarding method and device, electronic equipment and computer readable storage medium
CN112581102A (en) Task management method and device, electronic equipment and storage medium
CN111538554A (en) Payment method, payment device, mobile terminal and storage medium
CN112398667A (en) Page sharing method and device and electronic equipment
CN111325595A (en) User rights information display method and device and electronic equipment
CN109460277B (en) Commodity first-order flow display method and device
CN108173846B (en) Login method and device
CN116012003A (en) Recharging service information processing method and electronic equipment
CN117215450A (en) Sharing interface display method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20240223

Address after: Room 303, 3rd Floor, Building 5, No. 699 Wangshang Road, Changhe Street, Binjiang District, Hangzhou City, Zhejiang Province, 310052

Applicant after: Hangzhou Alibaba Overseas Internet Industry Co.,Ltd.

Country or region after: China

Address before: Room 554, 5 / F, building 3, 969 Wenyi West Road, Wuchang Street, Yuhang District, Hangzhou City, Zhejiang Province

Applicant before: Alibaba (China) Co.,Ltd.

Country or region before: China

TA01 Transfer of patent application right