CN108305055B - Payment testing method and device - Google Patents

Payment testing method and device Download PDF

Info

Publication number
CN108305055B
CN108305055B CN201710981671.4A CN201710981671A CN108305055B CN 108305055 B CN108305055 B CN 108305055B CN 201710981671 A CN201710981671 A CN 201710981671A CN 108305055 B CN108305055 B CN 108305055B
Authority
CN
China
Prior art keywords
payment
information
preset
order
order information
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.)
Expired - Fee Related
Application number
CN201710981671.4A
Other languages
Chinese (zh)
Other versions
CN108305055A (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.)
Zhanghe Tianxia Beijing Information Technology Co ltd
Original Assignee
Zhanghe Tianxia Beijing Information 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 Zhanghe Tianxia Beijing Information Technology Co ltd filed Critical Zhanghe Tianxia Beijing Information Technology Co ltd
Priority to CN201710981671.4A priority Critical patent/CN108305055B/en
Publication of CN108305055A publication Critical patent/CN108305055A/en
Application granted granted Critical
Publication of CN108305055B publication Critical patent/CN108305055B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • 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/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]

Abstract

The invention relates to the technical field of internet, in particular to a payment testing method and device. The method comprises the following steps: a. the method comprises the steps of obtaining information filled by a user and generating payment order information after confirmation, wherein the payment order information comprises a payment order number, b, obtaining a plurality of preset order information stored in a test server, wherein the preset order information comprises the preset order number, c, searching the preset order number matched with the payment order number to obtain the preset order information corresponding to the preset order number, taking the preset order information as target order information, d, matching first information included in the payment order information with first preset information included in the target order information, returning to the step a when the preset order information is not matched, and when the preset order information is matched, obtaining a payment result according to the preset state information included in the payment state information and the preset order information. By the method, the problem that a user faces a great obstacle when paying a large amount in a test environment is effectively solved.

Description

Payment testing method and device
Technical Field
The invention relates to the technical field of internet, in particular to a payment testing method and device.
Background
In recent years, electronic commerce is gradually becoming a main trend of economic development of the internet, and online shopping and payment are gradually becoming a convenient life style. One of the key links of the electronic commerce is a payment and settlement system, and the online payment is the most ideal payment scheme of the electronic commerce, and for the feasibility of the online payment in practice, a person skilled in the art needs to perform multiple tests under various scenes, environments and conditions to obtain the online payment system meeting the requirements of modern users.
The inventor finds that the existing online payment generally adopts a mode of accessing an interface of a third-party payment company, but in a test environment, a third-party payment system can only call a real payment interface because a sandbox environment is not provided, so that finance cannot provide support when the amount of a test order is large, and the third party also needs to charge a certain payment commission. These problems lead to significant frustration for users when making large payments in a testing environment.
Disclosure of Invention
In view of the above, the present invention provides a payment testing method and device to effectively solve the problem that a user faces a great obstacle when paying a large amount in a testing environment.
In order to achieve the above object, a preferred embodiment of the present invention provides a payment testing method, including:
a. acquiring information filled by a user according to a payment scene and generating payment order information after confirmation, wherein the payment order information comprises a payment order number;
b. acquiring a plurality of pieces of preset order information stored in a test server, wherein the preset order information comprises preset order numbers;
c. searching a preset order number matched with the payment order number in the plurality of preset order information to obtain preset order information corresponding to the preset order number, and taking the preset order information as target order information;
d. matching first information included in the payment order information with first preset information included in the target order information, and generating first log information and returning to the step a when the first information and the target order information are not matched;
e. and when the order information is matched with the payment order information, obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information, and generating second log information according to the payment result.
In a preferred embodiment of the present invention, in the payment testing method, the first information includes payment amount information and payment user information, and the first preset information includes preset amount information and preset user information.
In a preferred embodiment of the present invention, in the payment testing method, after acquiring information filled by a user according to a payment scenario and generating payment order information after confirmation, the method further includes:
and encrypting the payment order information to obtain the encrypted payment order information.
In a preferred embodiment of the present invention, in the above payment testing method, before acquiring information filled by a user according to a payment scenario and generating payment order information after confirmation, the method further includes:
generating a plurality of payment scenes according to preset application configuration;
and acquiring a payment scene selected by the user from a plurality of payment scenes.
In a preferred embodiment of the present invention, in the payment testing method, the plurality of payment scenarios generated according to the preset application configuration include a simulated order payment scenario, a platform royalty payment scenario, and a deposit payment scenario.
The invention also provides a payment testing device, comprising:
a first obtaining module: the system comprises a payment scene server, a payment server and a payment server, wherein the payment server is used for acquiring information filled by a user according to the payment scene and generating payment order information after confirmation, and the payment order information comprises a payment order number;
a second obtaining module: the system comprises a test server and a server, wherein the test server is used for acquiring a plurality of preset order information stored in the test server, and the preset order information comprises preset order numbers;
a searching module: the system comprises a payment order number acquisition unit, a payment order number acquisition unit and a payment order number acquisition unit, wherein the payment order number acquisition unit is used for acquiring a plurality of preset order information;
a matching module: the system comprises a first information module, a second information module and a third information module, wherein the first information module is used for matching first information included in the payment order information with first preset information included in the target order information, and when the first information and the second preset information are not matched, first log information is generated;
a payment result generation module: and when the order information is matched with the payment order information, obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information, and generating second log information according to the payment result.
In a preferred embodiment of the present invention, in the payment testing apparatus, the first information includes payment amount information and payment user information, and the first preset information includes preset amount information and preset user information.
In a preferred embodiment of the present invention, in the above payment testing apparatus, the apparatus further includes:
an encryption module: and the payment order information is encrypted to obtain the encrypted payment information.
In a preferred embodiment of the present invention, in the above payment testing apparatus, the apparatus further includes:
a scene generation module: the system comprises a payment server and a payment server, wherein the payment server is used for generating a plurality of payment scenes according to preset application configuration;
a scene acquisition module: the method is used for acquiring one payment scene selected by a user from a plurality of payment scenes.
In a preferred embodiment of the present invention, in the payment testing apparatus, the plurality of payment scenarios generated according to the preset application configuration include a simulated order payment scenario, a platform royalty payment scenario, and a deposit payment scenario.
The embodiment of the invention provides a payment testing method and a device, wherein the method comprises the following steps: a. acquiring information filled by a user according to a payment scene and generating payment order information after confirmation, the payment order information comprises a payment order number, b, acquiring a plurality of preset order information stored in the test server, the preset order information comprises a preset order number, c, searching the preset order number matched with the payment order number to obtain the preset order information corresponding to the preset order number, and using the preset order information as target order information, d, matching the first information included in the payment order information with the first preset information included in the target order information, when the first preset information is not matched, generating first log information and returning to the step a, when the first preset information is matched, and obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information, and generating second log information according to the payment result. By the method, the problem that a user faces a great obstacle when paying a large amount in a test environment is effectively solved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a connection block diagram of an electronic device according to an embodiment of the present invention.
Fig. 2 is a schematic flow chart of a payment testing method according to an embodiment of the present invention.
Fig. 3 is another schematic flow chart of a payment testing method according to an embodiment of the present invention.
Fig. 4 is a connection block diagram of a payment testing apparatus according to an embodiment of the present invention.
FIG. 5 is another connection block diagram of a payment testing apparatus according to an embodiment of the present invention
Icon: 10-an electronic device; 12-a memory; 14-a processor; 100-a payment testing device; 110-a first acquisition module; 120-a second acquisition module; 130-a lookup module; 140-a matching module; 150-a payment result generation module; 160-a scene generation module; 170-scene acquisition module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. 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.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Fig. 1 is a block diagram of an electronic device 10 according to a preferred embodiment of the invention. The electronic device 10 in the embodiment of the present invention may be a server, a computer, or the like having a data processing capability. As shown in fig. 1, the electronic device 10 includes: a memory 12 and a processor 14.
The memory 12 and the processor 14 are electrically connected to each other, directly or indirectly, to enable transmission or interaction of data. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 12 stores software functional modules stored in the memory 12 in the form of software or Firmware (Firmware), and the processor 14 executes various functional applications and data processing by running software programs and modules stored in the memory 12, such as the payment testing apparatus 100 in the embodiment of the present invention, so as to implement the payment testing method in the embodiment of the present invention.
The Memory 12 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an Electrically Erasable Read-Only Memory (EEPROM), and the like. Wherein the memory 12 is used for storing a program, and the processor 14 executes the program after receiving the execution instruction.
The processor 14 may be an integrated circuit chip having signal processing capabilities. The Processor 14 may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), and the like. But may also be a digital signal processor 14(DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be appreciated that the configuration shown in FIG. 1 is merely illustrative and that electronic device 10 may include more or fewer components than shown in FIG. 1 or may have a different configuration than shown in FIG. 1. The components shown in fig. 1 may be implemented in hardware, software, or a combination thereof.
Referring to fig. 2, the payment testing method provided by the present invention includes five steps S110 to S150.
Step S110: and acquiring information filled by a user according to a payment scene and generating payment order information after confirmation, wherein the payment order information comprises a payment order number.
The test server may be, but is not limited to, a simulated order payment scenario, a platform royalty payment scenario, or a deposit payment scenario. The payment scene includes information that the user needs to fill in, and the information that needs to fill in may include, but is not limited to, an order number, transaction amount information, payment user information, and the like.
Step S120: the method comprises the steps of obtaining a plurality of pieces of preset order information stored in a test server, wherein the preset order information comprises preset order numbers.
Wherein, the test server can be but is not limited to a WEB server or a database server. The preset order information may further include, but is not limited to, preset amount information, preset user information, and the like.
Step S130: and searching a preset order number matched with the payment order number to obtain preset order information corresponding to the preset order number, and taking the preset order information as target order information.
And when the payment order number is consistent with the preset order number, judging that the preset order number is matched with the payment order number. The payment order number may be composed of numbers, letters, or both letters and numbers. And is not particularly limited herein.
Step S140: and matching the first information included in the payment order information with the first preset information included in the target order information. When there is no match, step S142 is performed: first log information is generated, and the process returns to step S110.
In this embodiment, the first information includes payment amount information and payment user information, and the first preset information includes preset amount information and preset user information.
The first information and the first preset information may be matched in a manner that the payment amount information is matched with the preset amount information, the payment user information is matched with the preset user information, and when the payment amount information is not matched with the preset information and/or the payment user information is not matched with the preset user information, the first log information is generated and the process returns to step S110.
The first log information may include a prompt message, for example, when the payment user information is not matched with the preset user information, the prompt message is "user information error" or "user information invalid" or the like, and when the payment amount information is not matched with the preset information, the prompt message is "payment amount error" or "payment amount does not match with the order amount" or the like. Through the setting, the user can fill in or change information again according to the payment scene and the prompt message included in the first prompt message.
When there is a match, step S150 is executed: and obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information, and generating second log information according to the payment result.
The preset status information may be payment completion or payment waiting, the payment result may be payment success or payment failure, the second log information may include prompt information, when the payment result is payment success, the prompt information included in the second log information is "payment success", or may be an identifier indicating payment success, and when the payment failure occurs, the prompt information included in the second log information may be "payment failure", or may be an identifier indicating payment failure, which is not specifically limited herein
It should be noted that, when the first information included in the payment order information matches the first preset information included in the target order information, the first log information may be generated, and the first log information may include a prompt message, and the prompt message may be information such as "OK" or "order matching", which is not limited specifically herein.
Through the above, make the user when carrying out the payment test, effectively avoid adopting the mode of inserting third party payment company interface, nevertheless under test environment, third party payment system can only call true payment interface because of not providing the sandbox environment, financial affairs can not provide support when leading to test order amount of money great, and the third party still need to collect the problem of certain payment commission charge in addition, and then effectively avoids the user to face the problem of very big hindrance when test environment carries out the payment of large sum of money.
In addition, the first log information and the second log information are generated in the testing process, so that great convenience is brought to a user to quickly search and analyze problems according to the log information when matching or payment is wrong. After the payment is finished, the user can continue to test the subsequent services of the payment order, and the accuracy of the payment test result is effectively guaranteed.
Referring to fig. 3, optionally, in this embodiment, before acquiring information filled by a user according to a payment scenario and generating payment order information after confirmation, the method further includes:
step S160: and generating a plurality of payment scenes according to the preset application configuration.
Where different application configurations generate different payment scenarios. Optionally, in this embodiment, the multiple payment scenarios include a simulated order payment scenario, a platform royalty payment scenario, or a deposit payment scenario, and information filled in different payment scenarios is different.
Step S170: and acquiring a payment scene selected by the user from a plurality of payment scenes.
By the method, the user can fill in information according to the selected payment scene to obtain the corresponding payment order. In addition, the payment testing method can test the payment orders generated under different payment scenes through the steps of the method.
Optionally, in this embodiment, after the obtaining information filled by the user according to the payment scenario and generating payment order information after the confirmation, the method further includes:
and encrypting the payment order information to obtain the encrypted payment order information.
The method for encrypting the payment order information is not particularly limited herein. The payment order information is encrypted so as to effectively avoid the condition that the payment order information is stolen or illegally called.
It should be noted that, in this embodiment, the payment testing method may be applied to actual online payment. When the test method is applied to actual online payment, the mode of acquiring the information filled by the user according to the payment scene and generating the payment order information after confirmation is to acquire the information filled by the user according to the payment scene and generate the payment order information after confirmation of payment, and the order information can be effectively prevented from being stolen or illegally called by encrypting the payment order information, so that the safety of calling the service scene is improved.
Referring to fig. 4, on the basis of the above description, an embodiment of the present invention further provides a payment testing apparatus 100, where the payment testing apparatus 100 includes a first obtaining module 110, a second obtaining module 120, a searching module 130, a matching module 140, and a payment result generating module 150.
The first obtaining module 110 is configured to obtain information filled by a user according to a payment scenario and generate payment order information after confirmation, where the payment order information includes a payment order number. Specifically, the first obtaining module 110 may be configured to execute step S110 shown in fig. 2, and the detailed description of step S110 may be referred to for a specific operation method.
The second obtaining module 120: the order information processing method is used for obtaining a plurality of preset order information stored in the test server, wherein the preset order information comprises preset order numbers. Specifically, the first obtaining module 110 may be configured to execute step S120 shown in fig. 2, and the detailed description of step S120 may be referred to for a specific operation method.
The searching module 130 is configured to search the preset order number matched with the payment order number in the plurality of preset order information to obtain preset order information corresponding to the preset order number, and use the preset order information as target order information. Specifically, the search module 130 may be configured to execute step S130 shown in fig. 2, and the detailed description of step S130 may be referred to for a specific operation method.
The matching module 140 is configured to match first information included in the payment order information with first preset information included in the target order information, and generate first log information when the first information is not matched. Specifically, the matching module 140 may be configured to execute step S140 shown in fig. 2, and the detailed description of step S140 may be referred to for a specific operation method.
Optionally, in this embodiment, the first information includes payment amount information and payment user information, and the first preset information includes preset amount information and preset user information.
The payment result generating module 150 is configured to, when the payment order information matches the preset order information, obtain a payment result according to the preset state information included in the preset order information and the payment state information included in the payment order information, and generate second log information according to the payment result. Specifically, the payment result generation module 150 may be configured to execute step S150 shown in fig. 2, and the detailed description of step S150 may be referred to for a specific operation method.
Referring to fig. 5, in the present embodiment, the payment testing apparatus 100 further includes a scene generating module 160 and a scene acquiring module 170.
The scenario generating module 160 is configured to generate a plurality of payment scenarios according to a preset application configuration. Specifically, the scene generation module 160 may be configured to execute step S160 shown in fig. 3, and a detailed description of step S160 may be referred to for a specific operation method.
The scene acquiring module 170 is configured to acquire a payment scene selected by a user from a plurality of payment scenes. Specifically, the scene acquiring module 170 may be configured to execute step S170 shown in fig. 3, and the detailed description of step S170 may be referred to for a specific operation method.
Optionally, in this embodiment, the multiple payment scenarios generated according to the preset application configuration include a simulated order payment scenario, a platform royalty payment scenario, and a deposit payment scenario.
Optionally, in this embodiment, the payment testing apparatus 100 further includes an encryption module, where the encryption module is configured to encrypt the payment order information to obtain encrypted payment information.
In summary, the payment testing method and apparatus provided by the present invention include, S110: acquiring information filled by a user according to a payment scene and generating payment order information after confirmation, wherein the payment order information comprises a payment order number, and S120: acquiring a plurality of preset order information stored in the test server, where the preset order information includes a preset order number, and S130: searching for a preset order number matched with the payment order number to obtain preset order information corresponding to the preset order number, and taking the preset order information as target order information, S140: and matching the first information included in the payment order information with first preset information included in the target order information, generating first log information and returning to the step S110 when the first information and the target order information are not matched, and obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information when the first information and the target order information are matched, and generating second log information according to the payment result. By the method, the problem that a user faces a great obstacle when paying a large amount in the test environment is effectively solved, and the accuracy of the payment test result is effectively guaranteed.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus and method embodiments described above are illustrative only, as the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based devices that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A payment testing method, the method comprising:
a. acquiring information filled by a user according to a payment scene and generating payment order information after confirmation, wherein the payment order information comprises a payment order number;
b. acquiring a plurality of pieces of preset order information stored in a test server, wherein the preset order information comprises preset order numbers;
c. searching a preset order number matched with the payment order number in the plurality of preset order information to obtain preset order information corresponding to the preset order number, and taking the preset order information as target order information;
d. matching first information included in the payment order information with first preset information included in the target order information, generating first log information when the first information is not matched, and returning to the step a;
e. and when the order information is matched with the payment order information, obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information, and generating second log information according to the payment result.
2. The payment testing method as claimed in claim 1, wherein the first information comprises payment amount information and payment user information, and the first preset information comprises preset amount information and preset user information.
3. The payment testing method as claimed in claim 1, wherein after acquiring information filled in by a user according to a payment scenario and generating payment order information after confirmation, the method further comprises:
and encrypting the payment order information to obtain the encrypted payment order information.
4. The payment testing method as claimed in claim 1, wherein before obtaining information filled in by a user according to a payment scenario and generating payment order information after confirmation, the method further comprises:
generating a plurality of payment scenes according to preset application configuration;
and acquiring a payment scene selected by the user from a plurality of payment scenes.
5. The payment testing method of claim 4, wherein the plurality of payment scenarios generated according to the preset application configuration include a simulated order payment scenario, a platform royalty payment scenario, and a deposit payment scenario.
6. A payment testing apparatus, comprising:
a first obtaining module: the system comprises a payment scene server, a payment server and a payment server, wherein the payment server is used for acquiring information filled by a user according to the payment scene and generating payment order information after confirmation, and the payment order information comprises a payment order number;
a second obtaining module: the system comprises a test server and a server, wherein the test server is used for acquiring a plurality of preset order information stored in the test server, and the preset order information comprises preset order numbers;
a searching module: the system comprises a payment order number acquisition unit, a payment order number acquisition unit and a payment order number acquisition unit, wherein the payment order number acquisition unit is used for acquiring a plurality of preset order information;
a matching module: the system comprises a first information module, a second information module and a third information module, wherein the first information module is used for matching first information included in the payment order information with first preset information included in the target order information, and when the first information and the second preset information are not matched, first log information is generated;
a payment result generation module: and when the order information is matched with the payment order information, obtaining a payment result according to the payment state information included in the payment order information and the preset state information included in the preset order information, and generating second log information according to the payment result.
7. The payment testing apparatus as claimed in claim 6, wherein the first information comprises payment amount information and payment user information, and the first preset information comprises preset amount information and preset user information.
8. The payment testing apparatus of claim 6, wherein the apparatus further comprises:
an encryption module: and the payment order information is encrypted to obtain the encrypted payment information.
9. The payment testing apparatus of claim 6, wherein the apparatus further comprises:
a scene generation module: the system comprises a payment server and a payment server, wherein the payment server is used for generating a plurality of payment scenes according to preset application configuration;
a scene acquisition module: the method is used for acquiring one payment scene selected by a user from a plurality of payment scenes.
10. The payment testing apparatus as claimed in claim 9, wherein the plurality of payment scenarios generated according to the preset application configuration include a simulated order payment scenario, a platform royalty payment scenario, and a deposit payment scenario.
CN201710981671.4A 2017-10-20 2017-10-20 Payment testing method and device Expired - Fee Related CN108305055B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710981671.4A CN108305055B (en) 2017-10-20 2017-10-20 Payment testing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710981671.4A CN108305055B (en) 2017-10-20 2017-10-20 Payment testing method and device

Publications (2)

Publication Number Publication Date
CN108305055A CN108305055A (en) 2018-07-20
CN108305055B true CN108305055B (en) 2021-03-12

Family

ID=62869936

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710981671.4A Expired - Fee Related CN108305055B (en) 2017-10-20 2017-10-20 Payment testing method and device

Country Status (1)

Country Link
CN (1) CN108305055B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109447733A (en) * 2018-09-25 2019-03-08 深圳壹账通智能科技有限公司 Transaction verification method, device and the storage medium of transaction system
CN110310111A (en) * 2019-06-26 2019-10-08 郑州铁路职业技术学院 A kind of third party's Internet payment system Internet-based and method
CN112418835A (en) * 2019-08-21 2021-02-26 腾讯科技(深圳)有限公司 Method and related device for testing online bank payment process
CN110705979B (en) * 2019-09-30 2020-11-10 北京嘀嘀无限科技发展有限公司 Charging information processing method, storage medium and electronic device
CN111679967B (en) * 2020-04-27 2023-04-21 贝壳技术有限公司 Method and device for displaying transaction list for testing
CN111815312A (en) * 2020-06-24 2020-10-23 霓检有限公司 Payment method and device and payee server
CN111967929A (en) * 2020-07-09 2020-11-20 口碑(上海)信息技术有限公司 Order polling method and device, electronic equipment and storage medium
CN112015661B (en) * 2020-09-08 2023-10-03 南京云柜网络科技有限公司 Software testing method and device
CN112820040A (en) * 2021-03-09 2021-05-18 厦门米应科技有限公司 Printing system and printing method

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105589802A (en) * 2014-10-23 2016-05-18 阿里巴巴集团控股有限公司 Software test method and apparatus

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4218766B2 (en) * 2006-03-09 2009-02-04 インターナショナル・ビジネス・マシーンズ・コーポレーション Method, apparatus and program for testing scenarios
CN101211437A (en) * 2006-12-31 2008-07-02 阿里巴巴公司 Electronic payment failure testing method, device and electronic payment system
CN101236523B (en) * 2008-02-29 2011-03-16 华为终端有限公司 Input method test method and device
US9514034B1 (en) * 2014-12-15 2016-12-06 Amazon Technologies, Inc. Ordered test execution to enable faster feedback
CN106021091B (en) * 2016-05-04 2019-05-17 上海携程商务有限公司 Internet bank's simulation system and method
CN106354628A (en) * 2016-08-12 2017-01-25 北京小米移动软件有限公司 Payment app test method and device thereof
CN106557421A (en) * 2016-10-10 2017-04-05 深圳市证通电子股份有限公司 POS applied program testing methods and device
CN106528432B (en) * 2016-12-12 2019-01-25 北京三快在线科技有限公司 The construction method and device of test scene data bury a test method
CN106841975A (en) * 2016-12-14 2017-06-13 新智数字科技有限公司 A kind of test system
CN106815148A (en) * 2016-12-30 2017-06-09 中国银联股份有限公司 A kind of transaction test method and device
CN106897216A (en) * 2017-02-13 2017-06-27 北京趣拿软件科技有限公司 The method and apparatus of test software

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105589802A (en) * 2014-10-23 2016-05-18 阿里巴巴集团控股有限公司 Software test method and apparatus

Also Published As

Publication number Publication date
CN108305055A (en) 2018-07-20

Similar Documents

Publication Publication Date Title
CN108305055B (en) Payment testing method and device
CN109558748B (en) Data processing method and device, electronic equipment and storage medium
CN108156237B (en) Product information pushing method and device, storage medium and computer equipment
EP3207464B1 (en) Method, device, terminal, and server for verifying security of service operation
CN109345214B (en) Payment method and system of digital currency wallet system and related components
US20180357683A1 (en) Rating data management
RU2705455C1 (en) Method and system for collecting and generating authentication data reporting
US20170193624A1 (en) Personal information certification and management system
CN111767578B (en) Data inspection method, device and equipment
KR20180075641A (en) Service processing method and apparatus
US9235840B2 (en) Electronic transaction notification system and method
EP3812997B1 (en) Blockchain-based data processing method and apparatus, and server
JP2018533131A (en) Authentication service customer data management method and system
CN110445768B (en) Login method and device and electronic equipment
CN111510413B (en) Data processing method, device and equipment
US10652276B1 (en) System and method for distinguishing authentic and malicious electronic messages
US20230103398A1 (en) Security Deposits Using Tokenized Reputation Scores
CN115689571A (en) Abnormal user behavior monitoring method, device, equipment and medium
WO2017129068A1 (en) Event execution method and device and system therefor
CN108632348B (en) Service checking method and device
CN110599184A (en) Method and device for network service account transaction, server and storage medium
CN110955464A (en) Service processing method and device, computer equipment and storage medium
US20230306426A1 (en) Systems and methods for automated validation for proprietary security implementations
US11514180B2 (en) Computer-implemented method for removing access to data
US20230401583A1 (en) Method to detect and obstruct fraudulent transactions

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
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20210312

Termination date: 20211020