CN114022153B - Payment result determining method and device, computer storage medium and electronic equipment - Google Patents

Payment result determining method and device, computer storage medium and electronic equipment Download PDF

Info

Publication number
CN114022153B
CN114022153B CN202111320799.9A CN202111320799A CN114022153B CN 114022153 B CN114022153 B CN 114022153B CN 202111320799 A CN202111320799 A CN 202111320799A CN 114022153 B CN114022153 B CN 114022153B
Authority
CN
China
Prior art keywords
payment
polling
application program
behavior
marking
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.)
Active
Application number
CN202111320799.9A
Other languages
Chinese (zh)
Other versions
CN114022153A (en
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.)
Yancheng Tianyanchawei Technology Co ltd
Original Assignee
Yancheng Tianyanchawei Technology 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 Yancheng Tianyanchawei Technology Co ltd filed Critical Yancheng Tianyanchawei Technology Co ltd
Priority to CN202111320799.9A priority Critical patent/CN114022153B/en
Publication of CN114022153A publication Critical patent/CN114022153A/en
Application granted granted Critical
Publication of CN114022153B publication Critical patent/CN114022153B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, 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/405Establishing or using transaction specific rules
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/42Confirmation, e.g. check or permission by the legal debtor of payment

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The embodiment of the application provides a payment result determining method and a device thereof, a computer storage medium and electronic equipment, wherein the payment result determining method comprises the following steps: monitoring the life cycle of the transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program; if yes, in response to the fact that the payment behavior is initiated according to the payment behavior marking variable, polling a background application server matched with the application program to determine a payment result of the payment behavior. The embodiment of the application enables the application program to accurately judge the payment result.

Description

Payment result determining method and device, computer storage medium and electronic equipment
Technical Field
The application relates to the technical field of data processing, in particular to a payment result determining method and device, a computer storage medium and electronic equipment.
Background
When the service or commodity is purchased on the application program, the application program initiates payment, the payment is paid to the merchant depending on the payment page provided by the third party payment platform, and after the payment page of the third party payment platform is completely paid, the application program is informed of the completion of the payment by clicking a [ return merchant ] button (or other similar buttons) to switch to the application program initiating the payment. However, in the payment process, the application program cannot acquire the notification that the payment has been successful due to the operation of other non-payment actions of the user, such as switching to the application program initiating the payment by a background switching manner, or the application program cannot acquire the notification that the payment has been successful due to network delay and other reasons, so that the judgment of the payment result is inaccurate.
Disclosure of Invention
The embodiment of the application provides a payment result determining method and device, a computer storage medium and electronic equipment, which are used for overcoming or relieving the technical problems in the prior art.
The application adopts the technical scheme that:
a payment result determination method, comprising:
Monitoring the life cycle of the transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program;
If yes, in response to the fact that the payment behavior is initiated according to the payment behavior marking variable, polling a background application server matched with the application program to determine a payment result of the payment behavior.
Optionally, in an embodiment, in response to determining that the payment action has been initiated according to the set payment action flag variable, polling a background application server matched with the application program to determine a payment result of the payment action includes: and in response to jumping from the transaction interface of the application program to a payment page of a third party payment platform, marking the payment behavior marking variable as a first marking used for representing the initiated payment, so as to judge the initiated payment behavior according to the first marking.
Optionally, in an embodiment, the responding to the determining that the payment action is initiated according to the set payment action marking variable, polling a background application server matched with the application program to determine a payment result of the payment action includes:
In response to determining that a payment action has been initiated according to the set payment action marking variable, polling a background application server for an account credited message to determine a payment result of the payment action;
and if the account check-in message is polled, generating a payment result of successful payment, otherwise, generating a payment result of unsuccessful payment, wherein the account check-in message is generated by a background server in response to the successful check-in message fed back by the merchant terminal.
Optionally, in an embodiment, the polling the background application server matched with the application program to determine a payment result of the payment action includes: and polling a background application server matched with the application program based on the set polling time interval to determine a payment result of the payment action.
Optionally, in an embodiment, if the account deposited message is not polled from the background application server at the ith polling, the polling time interval is prolonged at the (i+1) th polling, where i is an integer greater than or equal to 1.
Optionally, in an embodiment, the polling the background application server matched with the application program to determine a payment result of the payment action includes:
And counting the polling times in real time, and when the total polling times reach a set polling times threshold value, not polling the account deposited information, ending the polling of the background application server to generate a payment result of unsuccessful payment.
Optionally, in an embodiment, the method further includes: and counting the payment results of the unsuccessful payments to form an unpaid order list.
A payment result determination device, comprising:
the monitoring unit is used for monitoring the life cycle of the transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program;
and the polling unit is used for responding to the judgment that the payment behavior is initiated according to the payment behavior marking variable when the payment page of the third party payment platform is judged to jump to the transaction interface of the application program, and polling a background application server matched with the application program so as to determine the payment result of the payment behavior.
A computer storage medium having stored thereon a computer executable program that is executed to implement the payment result determination method according to any of the embodiments of the present application.
An electronic device comprising a memory for storing a computer executable program thereon, and a processor for running the computer executable program to implement any of the payment result determination methods of the embodiments of the present application.
According to the embodiment of the application, according to the life cycle monitoring function, the life cycle of the transaction interface of the application program is monitored to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program; if yes, in response to the fact that the payment behavior is initiated according to the payment behavior marking variable, polling is conducted on a background application server matched with the application program to determine a payment result of the payment behavior, and therefore the application program can accurately judge the payment result.
Drawings
Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;
FIG. 2 is a schematic diagram of another application scenario according to an embodiment of the present application;
FIG. 3 is a flow chart of a payment result determination method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a payment result determining apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application; as shown in fig. 1, the application scenario is directed to a callback system of a payment result, where the callback system of the payment result includes an electronic device 101 and a background server 102, where the background server 102 may be an independent physical server, may be a server cluster or a distributed system formed by a plurality of physical servers, and may also be a cloud server that provides cloud services, a cloud database, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and an artificial intelligence platform. The electronic device 101 may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc. The electronic device 101 and the background server 102 may be directly or indirectly connected through a wireless communication manner (such as a network), which is not limited herein.
In this embodiment, an application program for implementing enterprise and/or personal information query is installed on the electronic device 101, the background application server 102 stores enterprise and personal information, and when a query request initiated by a user operating the application program on the electronic device 101 is received, the request is responded, and the matched enterprise or and/or personal information is transmitted to the application program and displayed on the electronic device 101.
FIG. 2 is a schematic diagram of another application scenario according to an embodiment of the present application; as shown in fig. 2, based on the application program, the user may also initiate a purchase action on the service or commodity provided by the application program, such as purchasing different levels of inquiry service rights, initiate payment by the application program, and pay money to the merchant depending on the payment page provided by the third party payment platform. In the payment process, the user can switch to the application program initiating the payment due to other operations of non-payment actions (such as switching the application program from the foreground to the background and then from the background to the foreground), so that the application program cannot acquire a notification that the payment is successful, or the application program cannot acquire a notification that the payment is successful due to network delay, network signal difference and the like, and the judgment of the payment result is inaccurate, thereby affecting the user experience.
In fig. 2, the third party paymate is in communication with a merchant, which is in communication with an application server via a network.
For this reason, in the embodiment of the present application, the following payment result determining method is executed on the electronic device:
Monitoring the life cycle of the transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program;
If yes, in response to the fact that the payment behavior is initiated according to the payment behavior marking variable, polling a background application server matched with the application program to determine a payment result of the payment behavior.
Specifically, a sub-thread may be started on the electronic device to be dedicated to performing the above-described payment result determination method. Of course, this is merely an example and is not intended to limit the use of only one sub-thread to exclusively perform the above-described payment result determination method. If sufficient computational resources are available, multiple sub-threads may also be used to perform the different steps of the above method, respectively.
FIG. 3 is a flow chart of a payment result determination method according to an embodiment of the present application; as shown in fig. 3, it includes:
S301, monitoring the life cycle of a transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from a payment page of a third party payment platform to the transaction interface of the application program;
Alternatively, in this embodiment, the application may be the application that performs enterprise and/or personal information query, and has a purchase of goods or services. Of course, in other embodiments, applications with other functions, but with goods or services purchase, are also possible.
Alternatively, in this embodiment, the transaction interface of the application may be a payment interface of the application, or an order interface with a payment interface function.
If the transaction interface of the application program is jumped from the payment page of the third party payment platform, the life cycle of the transaction interface is changed, so that the life cycle of the transaction interface of the application program is monitored according to the life cycle monitoring function, and whether the payment page of the third party payment platform is jumped to the transaction interface of the application program can be simply and directly judged.
Optionally, in this embodiment, if the system running the application is an android system, the onResume function of the Activity of the android system may be used as the life cycle monitoring function. Of course, for IOS systems, it is sufficient to select a function that enables lifecycle monitoring of the transaction interface.
Specifically, in an application scenario, considering each switching of the transaction interface of the application program, such as jumping from the payment page of the third party payment platform to the transaction interface of the application program, the life cycle of the transaction interface is accurately monitored and changed by using the onResume function.
If yes, executing step S302, if not, jumping to step S301 to continue monitoring;
s302, in response to the fact that the payment behavior is initiated according to the payment behavior marking variable, a background application server matched with the application program is polled to determine a payment result of the payment behavior.
Illustratively, in this embodiment, in response to determining that a payment action has been initiated according to the set payment action flag variable, polling a background application server that matches the application program to determine a payment result for the payment action includes: and in response to jumping from the transaction interface of the application program to a payment page of a third party payment platform, marking the payment behavior marking variable as a first marking used for representing the initiated payment, so as to judge the initiated payment behavior according to the first marking.
Illustratively, when jumping from the transaction interface of the application to the payment page of the third party payment platform, the value of the payment behavior marking variable is modified, such as to any value, as long as it is able to characterize that a jump from the transaction interface of the application to the payment page of the third party payment platform has occurred. Specifically, in an application scenario, for example, the payment behavior marking variable is named as payants, the value of the payment behavior marking variable defaults to a payment page indicating that no jump from the transaction interface of the application program to the third party payment platform occurs, for example, the value is 0 at this time, and when a jump from the transaction interface of the application program to the payment page of the third party payment platform occurs, the value of the payment behavior marking variable is modified to 1, that is, the marking of the payment behavior marking variable as a first mark for representing an initiated payment is realized, so as to accurately determine the initiated payment behavior according to the first mark.
Specifically, the step of marking described above may be performed between step S301 and step S302, or before step S301.
Illustratively, in this embodiment, the polling the background application server matched with the application program to determine the payment result of the payment action in response to determining that the payment action has been initiated according to the set payment action flag variable includes:
In response to determining that a payment action has been initiated according to the set payment action marking variable, polling a background application server for an account credited message to determine a payment result of the payment action;
and if the account check-in message is polled, generating a payment result of successful payment, otherwise, generating a payment result of unsuccessful payment, wherein the account check-in message is generated by a background server in response to the successful check-in message fed back by the merchant terminal.
Through the polling, even if network delay, poor network signals and the like occur, or an application program is switched from the foreground to the background and then from the background to the foreground, if the actual payment is completed, the possibility of polling the account deposit information is increased, and the accuracy of payment result judgment is further ensured.
Optionally, in some application scenarios, such as poor network conditions, resulting in a larger network delay or weaker network signals, the background application server may need to be polled multiple times to obtain the account-for-account message, so, for example, in this embodiment, the polling the background application server matched with the application program to determine the payment result of the payment behavior includes: and polling a background application server matched with the application program based on the set polling time interval to determine a payment result of the payment action. Since the polling interval defines the interval between two polling initiation times, if the current polling does not acquire the account deposit message, when the waiting time reaches the polling interval, a polling is initiated again to acquire the account deposit message until the account deposit message is successfully acquired or the account deposit message acquisition fails.
In this embodiment, if the account check-in message is not polled from the background application server at the i-th polling, the polling time interval is extended at the i+1th polling, where i is an integer equal to or greater than 1. If the account deposit information is not acquired in the current polling, when the waiting time reaches the extended polling time interval, polling is started again to acquire the account deposit information until the account deposit information is successfully acquired or the account deposit information is acquired, so that the account deposit information can be successfully acquired as far as possible, or the account deposit information acquisition failure is successfully determined, which is equivalent to successfully acquiring the account deposit information by reducing the polling times as far as possible, or the account deposit information acquisition failure is successfully determined, thereby saving resources and reducing the requirement on calculation force.
Specifically, in this embodiment, when the polling time interval is prolonged, the polling time interval used for initiating the current polling may be specifically expanded by a certain multiple to be used as the polling time interval used for initiating the next polling, and so on, so as to ensure that the account deposited message is acquired as much as possible in the next polling.
For example, if the polling time interval used for initiating the current polling is marked as X, the polling time interval used for initiating the next polling is 2X, and so on, and the polling time interval used for initiating the next polling is 2X.
Illustratively, in this embodiment, the polling the background application server matched with the application program to determine the payment result of the payment action includes:
And counting the polling times in real time, and when the total polling times reach a set polling times threshold value, not polling the account deposited information, ending the polling of the background application server to generate a payment result of unsuccessful payment.
Therefore, the number of times of polling initiation is controlled through the polling number threshold value, so that the resource consumption is further reduced, and the calculation power is saved.
Specifically, a count variable may be assigned to simply and effectively implement the recording of the total number of polls.
The size of the polling times threshold can be flexibly determined according to application scenes. Of course, it may also be determined by machine learning.
When the account deposit information is acquired, the values of the payment behavior marking variable and the count variable are consumed, so that the account deposit information corresponding to other payment behaviors is acquired conveniently, statistics of corresponding polling times are carried out, meanwhile, the fact that the life cycle of the transaction interface is changed through onresume functions is avoided, but the transaction interface is not actually jumped to the application program from the payment page of the third party payment platform, but the application program is switched to the foreground in the background, but the payment behavior marking variable is not consumed due to the consumption, so that the wrong determination initiates the payment behavior, and further the execution step S302 is triggered by mistake, and the waste of resources and the white consumption of calculation power are caused.
On the basis of the foregoing embodiment, in another embodiment, the method further includes: and counting the unsuccessfully paid payment results to form an unpaid order list, wherein the unpaid order list comprises orders which are really unpaid by a user and orders which are paid and do not receive account deposit information due to various special reasons.
To this end, further, pull-down refresh settings are configured for all orders in the unpaid order list to update the status of the order. For example, if a subsequent account check-in message is acquired by polling again, the corresponding order is refreshed as paid. If it is really paid but is not changed to paid all the time.
Fig. 4 is a schematic structural diagram of a payment result determining device according to an embodiment of the present application; as shown in fig. 4, it includes:
The monitoring unit 401 is configured to monitor, according to the life cycle monitoring function, a life cycle of a transaction interface of the application program, so as to determine whether to jump from a payment page of the third party payment platform to the transaction interface of the application program;
And the polling unit 402 is configured to, when it is determined that the payment page of the third party payment platform jumps to the transaction interface of the application program, poll a background application server matched with the application program to determine a payment result of the payment behavior in response to determining that the payment behavior has been initiated according to the payment behavior flag variable.
Optionally, in an embodiment, the apparatus further includes a marking unit, configured to mark, before polling a background application server matched to the application program to determine a payment result of the payment action in response to determining that the payment action has been initiated according to the set payment action marking variable, the payment action marking variable as a first marking for characterizing the initiated payment in response to jumping from a transaction interface of the application program to a payment page of a third party payment platform, so as to determine the initiated payment action according to the first marking.
Optionally, in an embodiment, the polling unit 402 is specifically configured to:
In response to determining that a payment action has been initiated according to the set payment action marking variable, polling a background application server for an account credited message to determine a payment result of the payment action;
and if the account check-in message is polled, generating a payment result of successful payment, otherwise, generating a payment result of unsuccessful payment, wherein the account check-in message is generated by a background server in response to the successful check-in message fed back by the merchant terminal.
Optionally, in an embodiment, the polling unit 402 is specifically configured to:
And polling a background application server matched with the application program based on the set polling time interval to determine a payment result of the payment action.
Optionally, in an embodiment, if the account deposited message is not polled from the background application server at the ith polling, the polling time interval is prolonged at the (i+1) th polling, where i is an integer greater than or equal to 1.
Optionally, in an embodiment, the polling unit 402 is specifically configured to:
And counting the polling times in real time, and when the total polling times reach a set polling times threshold value, not polling the account deposited information, ending the polling of the background application server to generate a payment result of unsuccessful payment.
Optionally, in an embodiment, the apparatus further includes a statistics unit, configured to count payment results of unsuccessful payments, so as to form an unpaid order list.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application; as shown in fig. 5, the electronic device includes: a memory 501 and a processor 502, the memory having stored thereon a computer executable program for running the computer executable program to implement the method of any of the embodiments of the present application.
If the embodiment shown in fig. 3 is executed on the side of the electronic device, the electronic device may be used as an execution body for executing the embodiment in fig. 3.
The embodiment of the application also provides a computer storage medium, and a computer executable program is stored on the computer storage medium and is operated to implement the payment result determining method according to any one of the embodiments of the application.
The above examples are only specific embodiments of the present application, and are not intended to limit the scope of the present application, but it should be understood by those skilled in the art that the present application is not limited thereto, and that the present application is described in detail with reference to the foregoing examples: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (8)

1. A payment result determination method, comprising:
Monitoring the life cycle of the transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program;
If yes, responding to the judgment that the payment behavior is initiated according to the payment behavior marking variable, and polling a background application server matched with the application program to determine a payment result of the payment behavior;
Wherein the responding to the judgment that the payment behavior is initiated according to the set payment behavior marking variable polls a background application server matched with the application program to determine the payment result of the payment behavior, and the method comprises the following steps: in response to jumping from the transaction interface of the application to a payment page of a third party paymate, marking the payment behavior marking variable as a first marking for characterizing an initiated payment to determine the initiated payment behavior based on the first marking;
Wherein the responding to the judgment that the payment behavior is initiated according to the set payment behavior marking variable polls a background application server matched with the application program to determine the payment result of the payment behavior comprises the following steps:
In response to determining that a payment action has been initiated according to the set payment action marking variable, polling a background application server for an account credited message to determine a payment result of the payment action;
and if the account check-in message is polled, generating a payment result of successful payment, otherwise, generating a payment result of unsuccessful payment, wherein the account check-in message is generated by a background server in response to the successful check-in message fed back by the merchant terminal.
2. The method of claim 1, wherein the polling a background application server that matches the application to determine a payment result for the payment action comprises: and polling a background application server matched with the application program based on the set polling time interval to determine a payment result of the payment action.
3. The method of claim 2, wherein if the account posted message is not polled from the background application server at the i-th poll, the polling interval is extended at the i+1th poll, i being an integer greater than or equal to 1.
4. A method according to claim 3, wherein said polling a background application server that matches the application to determine a payment result for the payment action comprises:
And counting the polling times in real time, and when the total polling times reach a set polling times threshold value, not polling the account deposited information, ending the polling of the background application server to generate a payment result of unsuccessful payment.
5. The method according to any one of claims 1-4, further comprising: and counting the payment results of the unsuccessful payments to form an unpaid order list.
6. A payment result determination apparatus, comprising:
the monitoring unit is used for monitoring the life cycle of the transaction interface of the application program according to the life cycle monitoring function so as to judge whether to jump from the payment page of the third party payment platform to the transaction interface of the application program;
The polling unit is used for responding to the judgment that the payment behavior is initiated according to the payment behavior marking variable when the payment page of the third party payment platform is judged to jump to the transaction interface of the application program, and polling the background application server matched with the application program so as to determine the payment result of the payment behavior;
The device further comprises a marking unit, wherein the marking unit is used for marking the payment behavior marking variable as a first marking used for representing the initiated payment in response to the jump from the transaction interface of the application program to the payment page of a third party payment platform before polling a background application server matched with the application program to determine the payment result of the payment behavior in response to the determination of the initiated payment behavior according to the set payment behavior marking variable, so as to determine the initiated payment behavior according to the first marking;
the polling unit is specifically configured to:
In response to determining that a payment action has been initiated according to the set payment action marking variable, polling a background application server for an account credited message to determine a payment result of the payment action;
and if the account check-in message is polled, generating a payment result of successful payment, otherwise, generating a payment result of unsuccessful payment, wherein the account check-in message is generated by a background server in response to the successful check-in message fed back by the merchant terminal.
7. A computer storage medium having stored thereon a computer executable program that is run to implement the payment result determination method of any of claims 1-5.
8. An electronic device comprising a memory for storing a computer executable program thereon and a processor for running the computer executable program to implement the payment result determination method of any of claims 1-5.
CN202111320799.9A 2021-11-09 2021-11-09 Payment result determining method and device, computer storage medium and electronic equipment Active CN114022153B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111320799.9A CN114022153B (en) 2021-11-09 2021-11-09 Payment result determining method and device, computer storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111320799.9A CN114022153B (en) 2021-11-09 2021-11-09 Payment result determining method and device, computer storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN114022153A CN114022153A (en) 2022-02-08
CN114022153B true CN114022153B (en) 2024-07-16

Family

ID=80062483

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111320799.9A Active CN114022153B (en) 2021-11-09 2021-11-09 Payment result determining method and device, computer storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN114022153B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108280640A (en) * 2018-01-11 2018-07-13 口碑(上海)信息技术有限公司 The payment result page shows method and device
CN108960792A (en) * 2018-06-05 2018-12-07 阿里巴巴集团控股有限公司 A kind of polling method, method of payment, device, server and payment system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106096945A (en) * 2016-06-06 2016-11-09 乐视控股(北京)有限公司 A kind of method of payment, device, terminal, server and payment system
CN106228367A (en) * 2016-07-27 2016-12-14 北京奇虎科技有限公司 The method and apparatus of payment verification
CN108520454B (en) * 2018-04-10 2023-04-18 平安科技(深圳)有限公司 Method and system for calling back orders in real time
CN109118183B (en) * 2018-07-06 2021-02-02 武汉斗鱼网络科技有限公司 Third party payment method, device, equipment and medium
CN111680990A (en) * 2020-05-09 2020-09-18 苏州中仑网络科技有限公司 Payment method and device, cash register and storage medium in weak network environment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108280640A (en) * 2018-01-11 2018-07-13 口碑(上海)信息技术有限公司 The payment result page shows method and device
CN108960792A (en) * 2018-06-05 2018-12-07 阿里巴巴集团控股有限公司 A kind of polling method, method of payment, device, server and payment system

Also Published As

Publication number Publication date
CN114022153A (en) 2022-02-08

Similar Documents

Publication Publication Date Title
CN111831420B (en) Method for task scheduling, related device and computer program product
CN109376050A (en) A kind of APP monitoring method, computer readable storage medium and terminal device
US9842338B1 (en) System to identify vulnerable card readers
CN107390983B (en) Service instruction execution method, client and storage medium
CN108111554B (en) Control method and device for access queue
CN109948882B (en) Task processing method based on block data structure and related equipment
CN105376719A (en) Information pushing method and device
CN114328132A (en) Method, device, equipment and medium for monitoring state of external data source
CN110727523B (en) Service request processing method, service request processing device and readable storage medium
CN112487838B (en) Information prompting method, device, electronic equipment and storage medium
US11900387B2 (en) Monitoring account usage to provide transaction retry notifications
CN114022153B (en) Payment result determining method and device, computer storage medium and electronic equipment
CN113377608A (en) Method and device for alarming task abnormity, terminal equipment and storage medium
CN112965799A (en) Task state prompting method and device, electronic equipment and medium
CN113839855B (en) Session reminding method, device and storage medium
CN115658745A (en) Data processing method, data processing device, computer equipment and computer readable storage medium
CN114500426B (en) Message reminding method, device, computer equipment and storage medium
CN111488625B (en) Data processing method and device
CN112418848A (en) Order processing method and device, computer equipment and storage medium
JP2011198250A (en) Information processor for processing request, method therefor, and computer program
CN109741101A (en) Supervisory methods, system and the storage medium of electronic coupons granting
US20180253654A1 (en) Generating rules based on patterns in a communication time series
CN110264211B (en) Wind control method, system, device and equipment
CN117557211B (en) Intelligent financial business processing method, platform and medium based on flow automation
US20230198844A1 (en) Dynamic installation of mobile application modules

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
TA01 Transfer of patent application right

Effective date of registration: 20230801

Address after: Room 404-405, 504, Building B-17-1, Big data Industrial Park, Kecheng Street, Yannan High tech Zone, Yancheng, Jiangsu Province, 224000

Applicant after: Yancheng Tianyanchawei Technology Co.,Ltd.

Address before: 224000 room 501-503, building b-17-1, Xuehai road big data Industrial Park, Kecheng street, Yannan high tech Zone, Yancheng City, Jiangsu Province (CNK)

Applicant before: Yancheng Jindi Technology Co.,Ltd.

GR01 Patent grant
GR01 Patent grant