CN110007904B - Data processing method, device and equipment - Google Patents
Data processing method, device and equipment Download PDFInfo
- Publication number
- CN110007904B CN110007904B CN201910226965.5A CN201910226965A CN110007904B CN 110007904 B CN110007904 B CN 110007904B CN 201910226965 A CN201910226965 A CN 201910226965A CN 110007904 B CN110007904 B CN 110007904B
- Authority
- CN
- China
- Prior art keywords
- payment
- section
- function
- check
- tangent plane
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
-
- 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/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a data processing method, a data processing device and data processing equipment, belongs to the technical field of mobile payment, and is used for reducing the difficulty of payment code development and saving resources. The method comprises the following steps: when a payment request is received, executing each check section for payment check in sequence; when the verification result of the last verification section is successful, sequentially executing all the splicing sections for splicing the payment parameters; and when the last splicing section returns the parameters of successful splicing, triggering a payment process to process the payment data. In the data processing method provided by the embodiment of the invention, the payment logic is combed and analyzed to obtain the main flow of front-end payment, the main flow can be used as an integral framework of later code development, the codes of the main flow do not need to be developed, and the multiplexing of the main flow codes is realized, so that the development amount of the codes is reduced, and the resources are saved.
Description
Technical Field
The invention relates to the technical field of mobile payment, in particular to a data processing method, a data processing device and data processing equipment.
Background
With the development of internet technology, various payment products come up endlessly. Services paid by users via the internet are increasing. Generally, a user browses commodity objects first, determines that the user selects a corresponding payment channel (such as bank card payment, electronic wallet payment and the like) to initiate a payment request after purchasing, and then the device completes payment according to the payment request of the user.
Because the contents of the display pages of the commodity objects are variable, and the display pages and the payment logic are different along with different sales strategies. For example, 1 yuan of purchased goods is processed by payment logic of the purchase, and the group purchase goods and the goods with no discount strategy are different according to different products or merchants.
However, if the sales strategy of the commodity object needs to be changed in the prior art, the code development of the corresponding payment logic needs to be performed again. The competitive shopping commodities often have the characteristics of short period and strong timeliness, which further causes the workload of the development of the payment logic code to be aggravated and also causes certain resource waste.
Disclosure of Invention
The embodiment of the invention provides a data processing method, a data processing device and data processing equipment, which are used for reducing the problem that the workload of development and test of payment codes is heavy and certain resources are wasted.
In one aspect, a data processing method is provided, and the method includes:
when a payment request is received, each check section for payment check is executed in sequence, and when the check result of the last check section is that the check is successful, the next check section is executed;
when the check result of the last check section is successful, sequentially executing all the assembling sections for assembling the payment parameters, and executing the next assembling section when the assembling result of the last assembling section is successful;
in a second aspect, an embodiment of the present invention further provides a data processing apparatus, where the apparatus includes:
the verification tangent plane execution module is used for sequentially executing each verification tangent plane used for payment verification when a payment request is received, and executing the next verification tangent plane when the verification result of the last verification tangent plane is successful;
the assembling tangent plane executing module is used for sequentially executing each assembling tangent plane for assembling the payment parameters when the verification result of the last verifying tangent plane is successful, and executing the next assembling tangent plane when the assembling result of the last assembling tangent plane is successful;
and the payment module is used for triggering a payment process to process the payment data when the last splicing section returns the parameters of successful splicing.
In a third aspect, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor,
the processor realizes the method steps of the above aspects when executing the computer program.
In a fourth aspect, a computer-readable storage medium is provided,
the computer readable storage medium stores computer instructions that, when executed on a computer, enable the computer to perform the method of the above aspect.
In the embodiment of the invention, when a payment request is received, each check section for payment check is executed in sequence; when the verification result of the last verification section is successful, sequentially executing all the splicing sections for splicing the payment parameters; and when the last splicing section returns the parameters of successful splicing, triggering a payment process to process the payment data. In the data processing method provided by the embodiment of the invention, the payment logic is combed and analyzed to obtain the main flow of front-end payment, the main flow can be used as an integral framework of later code development, the codes of the main flow do not need to be developed, and the multiplexing of the main flow codes is realized, so that the development amount of the codes is reduced, and the resources are saved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a diagram illustrating a payment scenario for an exemplary affiliate product according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an embodiment of the present invention provided for changing payment logic by way of a cut plane;
FIG. 3 is a schematic flow chart of a data processing method according to an embodiment of the present invention;
fig. 4 is a schematic diagram of reported data according to an embodiment of the present invention;
FIG. 5 is a schematic diagram illustrating an execution flow of each section according to an embodiment of the present invention;
FIG. 6 is a schematic flow chart of a data processing method according to an embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. The embodiments and features of the embodiments of the present invention may be arbitrarily combined with each other without conflict. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
In order to facilitate understanding of the technical solutions provided by the embodiments of the present invention, some key terms used in the embodiments of the present invention are explained first:
cutting into noodles: the method is an implementation mode for extracting codes related to non-business logic and positioning the codes to a specific cut-in point. AOP is an idea to implement facet-oriented programming.
In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document generally indicates that the preceding and following related objects are in an "or" relationship unless otherwise specified.
As shown in fig. 1, a payment scenario of a typical member product is provided in the embodiment of the present invention: and the user opens the payment page through different terminals, and the payment page can display the information of the commodity object. After the user selects the commodity object and clicks the payment button, the page can pull up different payment channels (such as bank card payment, mobile phone charge payment and the like), and the user selects one of the channels to pay. And after successful payment, the billing service background informs the member service background of commodity delivery processing, and after successful delivery, the page shows that the user successfully purchases the commodity.
After analyzing the above payment process, the inventor summarizes and researches and finds that most of the current payment products have the following characteristics:
1. the types of the terminals are many: such as android phones, iPhones, PCs, etc.;
2. the types of the accounts are multiple: WeChat, QQ, cell phone number, etc.;
3. the payment channel is many: such as WeChat Payment, QQ wallet Payment, Q coin Payment, Bank card Payment, apple Payment, Mobile Phone Payment, etc.;
4. the types of commodities are many: monthly members, individual commodities, and the like.
In addition, merchants often conduct targeted offers for different types of users. Authentication of the user for purchase qualification is also required.
In summary, as a Web page carrying payment, the payment logic becomes more and more complex accordingly. When different forms of paid products are more and more, if one payment page is developed for each product, the development and debugging work is huge, and certain resources are wasted.
In view of this, an embodiment of the present invention provides a data processing method, in which after a payment request is received, each verification tangent plane for payment verification is sequentially executed; if the verification result of the last verification section is successful, sequentially executing all the splicing sections for splicing the payment parameters; and if the last splicing section returns the parameters of successful splicing, entering a process of initiating payment to finish payment operation.
In the data processing method provided by the embodiment of the invention, the payment logic is combed and analyzed to obtain the main flow of front-end payment, the main flow can be used as an integral framework of later code development, the codes of the main flow do not need to be developed, and the multiplexing of the main flow codes is realized, so that the development amount of the codes is reduced.
Specifically, in the main process of front-end payment, payment verification, payment parameter assembly and trigger payment are included. The payment call is usually triggered by a lower-layer universal payment interface, and a service party for code development does not need to change too much. Therefore, front-end payments focus more on the logic of payment verification and payment parameter packing. When a user clicks various opening buttons for confirming payment, confirming upgrading and the like, the front end generally needs to perform payment verification firstly, and the payment verification comprises the following steps: checking the region of the user, checking the type of the user account, authenticating the purchase qualification, checking the strong login and the like. When the verification passes, processing various payment parameters for payment parameter assembly is started, wherein the assembled parameters include: login state information, commodity information, coupon information of the user, callback processing parameters after successful purchase and the like. And finally, calling a corresponding payment method to trigger payment according to specific service requirements, and obtaining a final processing result.
Based on the analysis of the payment main body flow, in the embodiment of the invention, the payment verification and the payment parameter assembly are realized by adopting the section, so that the user can conveniently increase the section according to different service requirements to realize the change of the payment logic. Fig. 2 is a schematic diagram illustrating a payment logic modified by a tangent plane. In fig. 2, the original payment verification logic includes two verification sections numbered 1 and 2, respectively, and the payment parameter assembling logic includes three sections numbered 3, 4, and 5, respectively. After the logic is added, two tangent planes are added to the payment verification logic, namely Aspect A and Aspect B in the graph 2, and 1 tangent plane, namely Aspect C, is added to the payment parameter assembly logic.
When the payment logic is executed, the execution sequence of each section in the original logic is 1, 2, 3, 4 and 5 in sequence. The execution sequence of each section in the newly added logic is Aspect A, 1, 2, Aspect B, 3, Aspect C, 4 and 5. Therefore, in the process of code development, only the section of the newly added logic is inserted into the original logic, and each section of the original logic is not required to be repeatedly developed, so that the code development is reduced, the development period is shortened, and the development cost is reduced.
After introducing the design concept of the embodiment of the present invention, the following further describes an implementation method of the embodiment of the present invention, as shown in fig. 3, which is a schematic flow chart of the method, and may include the following steps:
step 301: and when the payment request is received, executing each verification tangent plane for payment verification in sequence, and executing the next verification tangent plane when the verification result of the last verification tangent plane is verification success.
Step 302: and when the verification result of the last verification section is successful verification, sequentially executing all the assembling sections for assembling the payment parameters, and executing the next assembling section when the assembling result of the last assembling section is successful assembling.
Step 303: and when the last splicing section returns the parameters of successful splicing, triggering a payment process to process the payment data.
In order to facilitate determining the execution sequence of each section, each section in the embodiment of the present application is a function that performs a corresponding function. And storing the sections of different classes in different function arrays, and sequentially executing according to the sequence of the sections in the function arrays. Specifically, each check tangent plane is a function which is registered in the processor in advance, and the functions of the check tangent planes form a first function group; each assembling section is a function which is registered in the processor in advance, and the functions of each assembling section form a second function array. In this way, the payment checking tangent plane is stored in the first function array, the splicing tangent plane is stored in the second function array, and each function in the first function array is executed in sequence when the payment checking tangent plane and the splicing tangent plane are executed; after the function of the first function array is executed, each function in the second function array is sequentially executed, and sequential execution of each section can be achieved.
In specific implementation, the base class PayBase can be defined first, attributes and methods related to payment and general processes are defined in the base class, but a specific payment method is not realized. When using the method of this scheme, it is first necessary to extend classes based on the PayBase class, such as: the MidasPay class. This class is responsible for implementing the specific payment pay method. Instantiating the MidasPay class results in a payment SDK, e.g., SDK ═ new MidasPay (). The sdk. The SDK is registered into the first function array where the check-up section is located by calling the SDK.
Similarly, the sdk addproc method may be predefined to register the assembly cut plane into the second function array.
In order to facilitate management of parameters of the payment logic entirety and extension of various tangent planes, in the embodiment of the application, the functions in the first function array and the second array are functions of input parameters and output parameters with the same data type; wherein the input parameters and the output parameters respectively comprise parameters of two objects, wherein the first object is used for storing relevant parameters for paying for the purchased commodity object; the second object is for storing payment account related parameters. For example, two objects are defined, namely payable and options, wherein payable is an object related to the commodity, and the attributes of payable comprise a commodity ID, a commodity type, a commodity quantity and the like, and options are objects related to the payment account, and the attributes of options comprise an account type, an account ID, a payment environment and the like. In specific implementation, the respective parameters of the two objects may be determined according to actual requirements, which is not limited in the present application.
When the verification section for payment verification is executed, corresponding parameters can be obtained from the two objects, and then the verification result of the verification section is obtained. In specific implementation, the verification of the verification tangent plane is finished, and a Promise object can be returned. The main process of the payment engine will return either resolve or reject according to this Promise, and then determine whether to enter the execution of the next tangent plane. If resolve is returned, then execute the next tangent plane; if a reject is returned, this indicates that the check is not passed, the payment is aborted, and the next cut is not executed.
In addition, the returned Promise object may further include a solution method, and for each check section, if the check result of the check section is a check failure, a corresponding processing method is queried from the check result; and if the corresponding processing method is inquired, processing according to the inquired processing method, returning and executing the operation of each check tangent plane for payment check when the payment request is received.
After entering the parameter assembling process, reading the parameters of the first object and the second object as input parameters for the function in the second function array, reading the first function from the second function array and executing to assemble the new parameters obtained by executing the first function into the second object; and for each function in the second array of functions other than the first function, performing: and splicing the new parameters obtained after the function is executed into the second object input to the function by using the first object and the second object obtained by executing the previous function as the input of the function. For example, when all the verification sections are executed, the assembling section for assembling the payment parameters is entered. The input parameters of the splicing section are also payable and options. The attributes on the layout object only need to be read, and the attributes of options need to be assembled. For example, an assembly section for account processing is realized, different methods are called to obtain account information according to the type of the account, the obtained information is used as a new attribute of options, and after the assembly section is processed, the processed options are output. And then entering the next assembling section, wherein the output of the last assembling section is used as the input of the next assembling section, so that the next assembling section is processed until all the assembling sections are completely executed. Like this, each section of assembling realizes independent function, when carrying out payment process development, can go to increase the section through the mode of simple easily realizing on main part flow's basis according to actual demand.
In practice, the addition of the verification section may be implemented as: receiving an insertion instruction for inserting a function of a newly added check tangent plane into a first function array, wherein the insertion instruction comprises an entry point of the newly added check tangent plane; then determining the position of the function of the newly added check tangent plane in the first function array according to the entry point; and inserting the function of the newly added check tangent plane into the determined position.
Similarly, the increase of the splicing tangent plane can be realized as follows: receiving an insertion instruction for inserting the function of the newly added splicing tangent plane into a second function array, wherein the insertion instruction comprises an insertion point of the newly added splicing tangent plane; determining the position of the function of the newly added splicing tangent plane in the second function array according to the entry point; and inserting the function of the newly added splicing tangent plane into the determined position.
Because each section can complete an independent function, each section can be regarded as the minimum payment abnormity positioning point, the execution condition of each section before payment is initiated can be monitored for convenient realization, and the positioning problem during abnormal payment is convenient. Particularly, when complaints of users of the external network are received, the execution condition of each section is conveniently searched, and the section is positioned to which step the user has problems, so that the user is helped to quickly solve the payment problem. In the embodiment of the invention, each checking section and each assembling section have corresponding unique section identifiers; in executing the payment logic, for each of the cuts: reporting the input parameters of the section to an exception handling center before executing the section; and if the section is abnormal in the execution process, reporting the unique section identification of the section to an abnormal processing center. Therefore, the abnormal condition of the payment link can be judged according to the reported data.
As shown in fig. 4, which is a schematic diagram of data reporting, after a user clicks to confirm payment, a payment page firstly checks whether a region where the user is located supports purchasing of a current commodity through a first check plane, secondly checks whether the user is qualified to participate in an activity to purchase the current commodity through a second check plane, and then checks whether a current login state of the user is valid through a third check plane, if the login state of the user is expired, the payment is abnormal, the user needs to log in again, the user initiates payment again after logging in, and a next payment flow is performed again. In this way, in the whole process, because the first and second checking sections are successfully executed, the respective parameters of the first and second checking sections do not report the section unique identifiers of the first and second checking sections when reporting, however, because the third checking section is abnormal, the parameters of the third checking section and the section unique identifier corresponding to the parameters can be reported, the problem of the third checking section can be quickly positioned according to the section unique identifier, and the reason of the problem can be analyzed according to the reported third checking section.
In summary, the processing sequence of each slice in the present application can be as shown in fig. 5, and the whole process of paying pay () can be divided into two main steps of executing slices runa features and initiating pay. In runassocts, two types of slices are included, one type is execBeforePay (check-up slice) and the other type is execProc (splice slice). Wherein the execbeforesay comprises four sequentially executed check facets, and the execProc comprises four sequentially executed splicing facets. During execution, the check sections are executed first, the assembly sections are executed in sequence after the check sections are checked successfully, and if the assembly sections are executed successfully, the step of doPay is carried out.
To further understand the payment process provided by the embodiments of the present application, the description is made with reference to fig. 6, and as shown in fig. 6, the following steps may be included:
step 601: a payment request of a user is received.
The payment request may be triggered by a user confirming payment.
Step 602: the check section is executed in sequence.
Step 603: and judging whether the verification is passed, if the verification is passed, returning to the step 602, and if the verification is failed, executing the step 603.
Step 604: and inquiring whether a corresponding processing method exists from the checking result, if not, ending the operation, and if so, executing the step 605.
Step 605: and after executing the corresponding processing method, returning to execute the step 601.
Step 606: and after the last checking section passes the checking, sequentially executing the splicing sections.
Step 607: and (4) judging whether the assembly is successful, if so, executing a step 608, and otherwise, ending the operation.
Step 608: and triggering a payment process to process the payment data.
Step 609: and displaying the payment result according to the processing result.
Referring to fig. 7, based on the same inventive concept, an embodiment of the present invention further provides a data processing apparatus, including:
a check section executing module 701, configured to, when a payment request is received, sequentially execute each check section for payment check, and execute a next check section when a check result of a previous check section is a check success;
an assembling section executing module 702, configured to sequentially execute each assembling section for assembling the payment parameters when the verification result of the last verifying section is successful, and execute the next assembling section when the assembling result of the previous assembling section is successful;
and the payment module 703 is configured to trigger a payment process to process the payment data when the last assembly section returns the parameter of successful assembly.
Furthermore, each check tangent plane is a function which is registered in the processor in advance, and the functions of the check tangent planes form a first function group;
each assembling section is a function which is registered in the processor in advance, and the functions of each assembling section form a second function array.
Further, the functions in the first function array and the second array are functions of input parameters and output parameters with the same data type;
the input parameters and the output parameters respectively comprise parameters of two objects, wherein the first object is used for storing relevant parameters for paying for the purchased commodity object; the second object is for storing payment account related parameters.
Further, the splicing tangent plane execution module includes:
the first processing unit is used for reading the parameters in the first object and the second object which are used as input parameters for the functions in the second function array, reading the first function from the second function array and executing the first function so that new parameters obtained by executing the first function are spliced into the second object;
a second processing unit, configured to execute, for each function other than the first function in the second function array: and splicing the new parameters obtained after the function is executed into the second object input to the function.
Further, the apparatus further comprises:
the first receiving module is used for receiving an insertion instruction for inserting a function of the newly added check tangent plane into a first function array, wherein the insertion instruction comprises an insertion point of the newly added check tangent plane;
the first position determining module is used for determining the position of the function of the newly added check tangent plane in the first function array according to the access point;
and the first inserting module is used for inserting the function of the newly added check tangent plane into the determined position.
Further, the apparatus further comprises:
the second receiving module is used for receiving an insertion instruction for inserting the function of the newly added splicing tangent plane into a second function array, wherein the insertion instruction comprises an insertion point of the newly added splicing tangent plane;
the second position determining module is used for determining the position of the function of the newly added splicing tangent plane in the second function array according to the entry point;
and the second inserting module is used for inserting the function of the newly added assembling tangent plane into the determined position.
Further, the apparatus further comprises:
the query module is used for querying a corresponding processing method from the verification result if the verification result of the verification tangent plane is verification failure aiming at each verification tangent plane;
and the return execution module is used for processing according to the inquired processing method and then returning to execute the operation of each check tangent plane for payment check in sequence when the payment request is received if the corresponding processing method is inquired.
Furthermore, each checking section and each assembling section have corresponding unique section identification; the device further comprises:
a data reporting module, configured to execute, for each tangent plane:
reporting the input parameters of the section to an exception handling center before executing the section;
and if the section is abnormal in the execution process, reporting the unique section identification of the section to an abnormal processing center.
The apparatus may be configured to execute the method shown in the embodiment shown in fig. 3 and/or fig. 6, and therefore, for functions and the like that can be realized by each functional module of the apparatus, reference may be made to the description of the embodiment shown in fig. 3 and/or fig. 6, which is not described repeatedly.
Referring to fig. 8, based on the same technical concept, an embodiment of the present invention further provides a computer device 130, which may include a memory 1301 and a processor 1302.
The memory 1301 is used for storing computer programs executed by the processor 1302. The memory 1301 may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to use of the computer device, and the like. The processor 1302 may be a Central Processing Unit (CPU), a digital processing unit, or the like. The specific connection medium between the memory 1301 and the processor 1302 is not limited in the embodiments of the present invention. In fig. 8, the memory 1301 and the processor 1302 are connected through a bus 1303, the bus 1303 is shown by a thick line in fig. 8, and the connection manner between other components is only schematically illustrated and is not limited. The bus 1303 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
The memory 1301 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 1301 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD), or the memory 1301 may be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Memory 1301 may be a combination of the above.
A processor 1302 for executing the method performed by the device in the embodiment shown in fig. 3 or fig. 6 when calling the computer program stored in the memory 1301.
In some possible embodiments, various aspects of the methods provided by the present invention may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of the methods according to various exemplary embodiments of the present invention described above in this specification when the program product is run on the computer device, for example, the computer device may perform the methods performed by the devices in the embodiments shown in fig. 3 or fig. 6.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A method of data processing, the method comprising:
when a payment request is received, each check section for payment check is executed in sequence, and when the check result of the last check section is that the check is successful, the next check section is executed;
when the verification result of the last verification section for payment verification is successful, sequentially executing all the splicing sections for splicing the payment parameters, and executing the next splicing section when the splicing result of the last splicing section is successful;
and when the last splicing section returns the parameters of successful splicing, triggering a payment process to process the payment data.
2. The method of claim 1,
each check tangent plane is a function which is registered in the processor in advance, and the functions of the check tangent planes form a first function group;
each assembling section is a function which is registered in the processor in advance, and the functions of each assembling section form a second function array.
3. The method of claim 2, wherein the functions in the first array of functions and the second array are functions of input parameters and output parameters having the same data type;
the input parameters and the output parameters respectively comprise parameters of two objects, wherein the first object is used for storing relevant parameters for paying for the purchased commodity object; the second object is for storing payment account related parameters.
4. The method of claim 3, wherein said sequentially executing respective assembling facets for assembling payment parameters comprises:
reading parameters in the first object and the second object which are used as input parameters for the functions in the second function array, reading a first function from the second function array and executing to splice new parameters obtained by executing the first function into the second object;
for each function other than the first function in the second array of functions, performing:
and splicing the new parameters obtained after the function is executed into the second object input to the function.
5. The method of claim 2, further comprising:
receiving an insertion instruction for inserting a function of a newly added check tangent plane into a first function array, wherein the insertion instruction comprises an entry point of the newly added check tangent plane;
determining the position of a function of the newly added check tangent plane in the first function array according to the entry point;
and inserting the function of the newly added check tangent plane into the determined position.
6. The method of claim 2, further comprising:
receiving an insertion instruction for inserting the function of the newly added splicing tangent plane into a second function array, wherein the insertion instruction comprises an insertion point of the newly added splicing tangent plane;
determining the position of the function of the newly added splicing tangent plane in the second function array according to the entry point;
and inserting the function of the newly added splicing tangent plane into the determined position.
7. The method of claim 1, further comprising:
for each check section, if the check result of the check section is check failure, inquiring a corresponding processing method from the check result;
and if the corresponding processing method is inquired, processing according to the inquired processing method, returning and executing the operation of each check tangent plane for payment check when the payment request is received.
8. The method of claim 1, wherein each of the verification section and the assembly section has a corresponding unique section identifier; the method further comprises the following steps:
for each slice:
reporting the input parameters of the section to an exception handling center before executing the section;
and if the section is abnormal in the execution process, reporting the unique section identification of the section to an abnormal processing center.
9. A data processing apparatus, characterized in that the apparatus comprises:
the verification tangent plane execution module is used for sequentially executing each verification tangent plane used for payment verification when a payment request is received, and executing the next verification tangent plane when the verification result of the last verification tangent plane is successful;
the assembling tangent plane executing module is used for sequentially executing each assembling tangent plane for assembling payment parameters when the verification result of the last verifying tangent plane for payment verification is successful, and executing the next assembling tangent plane when the assembling result of the last assembling tangent plane is successful;
and the payment module is used for triggering a payment process to process the payment data when the last splicing section returns the parameters of successful splicing.
10. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor,
the processor, when executing the computer program, performs the method steps of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910226965.5A CN110007904B (en) | 2019-03-25 | 2019-03-25 | Data processing method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910226965.5A CN110007904B (en) | 2019-03-25 | 2019-03-25 | Data processing method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110007904A CN110007904A (en) | 2019-07-12 |
| CN110007904B true CN110007904B (en) | 2020-11-20 |
Family
ID=67167994
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910226965.5A Active CN110007904B (en) | 2019-03-25 | 2019-03-25 | Data processing method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110007904B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105024980A (en) * | 2014-04-29 | 2015-11-04 | 孙银海 | On-line near-field payment system and method based on cell phone number |
| CN105139205A (en) * | 2015-08-18 | 2015-12-09 | 宇龙计算机通信科技(深圳)有限公司 | Payment verification method, terminal and server |
| CN107230058A (en) * | 2017-04-27 | 2017-10-03 | 努比亚技术有限公司 | A kind of method of payment, equipment, server and computer-readable recording medium |
| EP3349162A1 (en) * | 2017-01-13 | 2018-07-18 | Flytech Technology Co., Ltd. | Hybrid mobile payment architecture and mobile pos module thereof |
| CN109325744A (en) * | 2018-10-23 | 2019-02-12 | 北京三快在线科技有限公司 | Payment processing method, device, medium and electronic equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016029319A1 (en) * | 2014-08-27 | 2016-03-03 | Samer Ziade | Systems and methods for facilitating secure ordering, payment and delivery of goods or services |
-
2019
- 2019-03-25 CN CN201910226965.5A patent/CN110007904B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105024980A (en) * | 2014-04-29 | 2015-11-04 | 孙银海 | On-line near-field payment system and method based on cell phone number |
| CN105139205A (en) * | 2015-08-18 | 2015-12-09 | 宇龙计算机通信科技(深圳)有限公司 | Payment verification method, terminal and server |
| EP3349162A1 (en) * | 2017-01-13 | 2018-07-18 | Flytech Technology Co., Ltd. | Hybrid mobile payment architecture and mobile pos module thereof |
| CN107230058A (en) * | 2017-04-27 | 2017-10-03 | 努比亚技术有限公司 | A kind of method of payment, equipment, server and computer-readable recording medium |
| CN109325744A (en) * | 2018-10-23 | 2019-02-12 | 北京三快在线科技有限公司 | Payment processing method, device, medium and electronic equipment |
Non-Patent Citations (2)
| Title |
|---|
| By Ryan Gandolfo.You May Be Asked to Verify WeChat Pay. Here"s How to Do It.《https://www.thatsmags.com/china/post/27250/you-may-be-asked-to-verify-wechat-pay-here-s-how-to-do-it》.2019, * |
| spring Aop实现身份验证和springboot异常统一处理;欧阳思海;《https://blog.csdn.net/sihai12345/article/details/80924870》;20180715;第1-5页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110007904A (en) | 2019-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108346028B (en) | Business approval processing method, device and system | |
| CN107038042B (en) | Service execution method and device | |
| CN109298926B (en) | Method and device for entering resource transfer party into resource transfer platform and electronic equipment | |
| CN108958711B (en) | Method and device for realizing interface platform | |
| CN107797854B (en) | Transaction file processing method and device, storage medium and computer equipment | |
| CN109240908B (en) | Method and device for creating abnormal test case template | |
| CN111597120B (en) | Interface test apparatus, method, electronic device, and computer-readable storage medium | |
| CN108897729B (en) | Transaction template sharing method and device, electronic equipment and storage medium | |
| CN110942377A (en) | Method and system for implementing asynchronous verification of telecom CRM (customer relationship management) service | |
| CN112348326A (en) | Bank business processing method and system | |
| CN113076410A (en) | Abnormal information processing method, device, equipment and storage medium | |
| CN117609449A (en) | Task type dialogue response method and device | |
| CN110007904B (en) | Data processing method, device and equipment | |
| CN109120509B (en) | Information collection method and device | |
| CN115358761A (en) | After-sale processing method and device, after-sale processing equipment and storage medium | |
| CN106528718B (en) | Method and apparatus for processing data from third party | |
| CN115375278A (en) | Business work order processing method and device, electronic equipment and storage medium | |
| US20140344179A1 (en) | Automated supplier management processes | |
| CN112181817B (en) | Test method and test device for SOA architecture platform | |
| CN111881020B (en) | Payment center interface testing method, device and system | |
| CN112307305B (en) | Service component pre-processing method, device and equipment | |
| CN109447806B (en) | Front-end control method and device, storage medium and electronic equipment | |
| CN111242731B (en) | Service execution method and device | |
| CN109582450B (en) | Application program management method, device, medium and electronic equipment | |
| CN113065927A (en) | Account checking method and device, electronic equipment and computer readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |