CN111966426A - An API docking method, system, device and storage medium - Google Patents

Abstract

The invention relates to an API docking method, system, device and storage medium, comprising: configuring a sandbox test environment for the user account according to user account request information; The judging factor for the account to pass the sandbox test; review the production request information of the user account that has passed the sandbox test; verify the production key of the user account whose generation request information has passed the review, and complete the API docking with the user account. The invention can automatically complete the API docking with the user, so that the automation degree of the API docking process is greatly improved, and there is no need to manually carry out the cumbersome approval process, the efficiency of the API docking is also greatly improved, the user experience is enhanced, and a lot of time is saved.

Description

An API docking method, system, device and storage medium

technical field

The present invention relates to the technical field of API, and in particular, to an API docking method, system, device and storage medium.

Background technique

APIs (Application Programming Interfaces) are predefined functions designed to provide applications and developers with the ability to access a set of routines based on a piece of software or hardware without having to access the source code or understand the inner workings Details of the mechanism. Internet-based applications are becoming more and more popular, and in the process, more sites open their own resources to developers to call. The API calls provided externally make the content between sites more relevant, and these open platforms also bring greater value to users, developers, and small and medium-sized websites. Nowadays, more and more e-commerce companies use API docking technology to provide customers with more online services.

The current well-known logistics and express industry customer docking API process, first, the customer connects with the sales staff of the company that provides API, and then applies for the ECP process, after the ECP process is archived, the sales staff provides the API interface specification document to the customer, and then the tester provides the API interface specification document to the customer. Connect with customer R&D personnel, and apply for production environment after joint debugging. The process is cumbersome and inconvenient for quick access. In the process of customer docking, too much manual coordination is required, which can easily cause bottlenecks. On the one hand, it causes high communication costs, and on the other hand, it affects the progress of docking, which directly affects the development of the company's business.

SUMMARY OF THE INVENTION

In order to solve the above technical problems, the purpose of the present invention is to provide an API docking method, system, device and storage medium.

According to one aspect of the present invention, an API docking method is provided, comprising:

Configure a sandbox testing environment for the user account according to the user account request information;

The number of successful times of uploading transaction voucher information in the sandbox test environment is used as the judgment factor for the user account to pass the sandbox test;

Review the production request information of user accounts that pass the sandbox test;

It is verified that the generation request information passes through the production key of the audited user account, and the API docking with the user account is completed.

Further, configure a sandbox testing environment for the user account according to the user account request information, including:

Generate an API docking account based on user registration information;

Generate the corresponding sandbox test environment according to the basic parameters of the API interface configured by the user account;

Send the sandbox test environment key to the user according to the registration information;

The corresponding sandbox test environment is configured for the user account by validating the user's sandbox test environment key.

Further, the number of successful times of uploading transaction credential information in the sandbox test environment will be used as a judgment factor for the user account to pass the sandbox test, including:

Set the sandbox testing period;

Record the number of successful times of uploading transaction credential information by the user account within the test period;

Determine whether the number of successes reaches a preset number:

If yes, it is determined that the user account has passed the sandbox test;

If not, it is determined that the user account has failed the sandbox test, and an error message is returned.

Further, verifying that the generation request information passes the production key of the audited user account, and completes the API docking with the user account, including:

Determine whether the production request information has passed the audit:

If yes, send the production configuration key to the user and complete the API connection with the user by verifying the user's production configuration key;

If not, it returns the production request information audit failure and the reason for the failure.

According to another aspect of the present invention, an API docking system is provided, comprising:

an initial configuration unit, configured to configure a sandbox testing environment for the user account according to the user account request information;

The sandbox test unit is configured to use the number of successful uploading of transaction credentials in the sandbox test environment as a judging factor for the user account to pass the sandbox test;

The production audit unit is configured to audit the production request information of the user account that has passed the sandbox test;

The docking completion unit is configured to verify the production key of the user account whose generation request information has passed the audit, and complete the API docking with the user account.

Further, the initial configuration unit includes:

The account generation module is configured to generate an API docking account according to the user registration information;

The sandbox generation module is configured to generate the corresponding sandbox test environment according to the basic parameters of the API interface configured by the user account;

A sandbox key module, configured to send a sandbox test environment key to the user according to the registration information;

The sandbox configuration module is configured to configure the corresponding sandbox test environment for the user account by verifying the user's sandbox test environment key.

Further, the sandbox testing unit includes:

The deadline setting module is configured to set the sandbox testing deadline;

A times recording module, configured to record the successful times of uploading transaction credential information by the user account within the test period;

a number of times judgment module, configured to judge whether the number of successful times reaches a preset number of times;

A test pass module, configured to determine that the user account passes the sandbox test;

The test failure module is configured to determine that the user account fails the sandbox test, and returns an error prompt.

Further, the docking completion unit includes:

A production judging module, configured to judge whether the production request information passes the audit;

The verification docking module is configured to send the production configuration key to the user and complete the API docking with the user by verifying the user's production configuration key;

The failure return module is configured to return the production request information audit failure and the reason for the failure.

In addition, the present invention also provides a device, comprising:

one or more processors;

memory for storing one or more programs,

The one or more programs, when executed by the one or more processors, cause the one or more processors to perform a method as described in any of the above.

According to another aspect of the present invention, there is provided a computer-readable storage medium storing a computer program, the program implementing the method according to any one of the above when executed by a processor.

Compared with the prior art, the present invention has the following beneficial effects:

1. An API docking method of the example of the present invention configures a sandbox test environment for the user account according to the user account request information, wherein the user account request information includes the basic parameters of the API interface that the user requests for docking according to his own business needs. Selecting settings and configuring a sandbox testing environment for users based on user account request information allows users to select API interfaces according to their own business needs, improving user experience. After the user enters the sandbox test, the number of successful uploads of transaction voucher information in the sandbox test environment will be used as the judgment factor for the user account to pass the sandbox test. Since the user uploads the transaction voucher information in the sandbox environment, the user uploads The information and the operation of modifying the information will not affect the API provider's system, which ensures the security of the API provider's system. Review the production request information of the user account that has passed the sandbox test, verify that the production key of the user account whose request information has passed the review is generated, and complete the API docking with the user account. After passing the sandbox test, the user enters the production review process. The production review process is not carried out in the sandbox environment. The production request information is automatically reviewed without manual review. After the production request is approved, the API connection is completed and can be used normally. The present invention can automatically complete the API docking with the user, so that the automation degree of the API docking process is greatly improved, and no manual cumbersome approval process is required, the efficiency of the API docking is also greatly improved, the user experience is enhanced, and a lot of time is saved.

2. An API docking system exemplified in the present invention configures a sandbox test environment for the user account according to the user account request information through the initial configuration unit, wherein the user account request information includes the user's request for docking API interface according to his own business needs. The selection and setting of basic parameters and the configuration of the sandbox test environment for users according to the user account request information allows users to select API interfaces according to their own business needs, which improves the user experience. After the user enters the sandbox testing session, the sandbox testing unit takes the number of successful uploading of transaction voucher information in the sandbox test environment as the judgment factor for the user account to pass the sandbox test. Since the user uploads transaction voucher information in the sandbox environment The information uploaded by the user and the operation of modifying the information will not affect the API provider's system, which ensures the security of the API provider's system. Review the production request information of the user account that has passed the sandbox test, verify that the production key of the user account whose request information has passed the review is generated, and complete the API docking with the user account. After passing the sandbox test, the user enters the production review process. The production review process is not carried out in the sandbox environment. The production request information is automatically reviewed without manual review. After the production request is approved, the API connection is completed and can be used normally. The invention can automatically complete the API docking with the user, so that the automation degree of the API docking process is greatly improved, and there is no need to manually carry out the cumbersome approval process, the efficiency of the API docking is also greatly improved, the user experience is enhanced, and a lot of time is saved.

3. The device exemplified in the present invention can complete the API docking more quickly and improve the service quality by executing the API docking method through the processor.

4. The readable storage medium exemplified in the present invention stores the API docking method implemented when executed by the processor, so as to facilitate docking with the user's API.

Description of drawings

Fig. 1 is a flow chart of the present invention.

FIG. 2 is a schematic structural diagram of the apparatus of the present invention.

Detailed ways

In order to better understand the technical solutions of the present invention, the present invention will be further described below with reference to specific embodiments and accompanying drawings.

Example 1:

This embodiment provides an API docking system, including:

an initial configuration unit, configured to configure a sandbox testing environment for the user account according to the user account request information;

The sandbox test unit is configured to use the number of successful uploading of transaction credentials in the sandbox test environment as a judging factor for the user account to pass the sandbox test;

The production audit unit is configured to audit the production request information of the user account that has passed the sandbox test;

The docking completion unit is configured to verify the production key of the user account whose generation request information has passed the audit, and complete the API docking with the user account.

In this embodiment, through the process of automatic API docking, the user selects the order placing interface and the order screening interface according to business needs, and configures the basic information of the order placing interface and the basic information of the order screening interface as required. For example, if there is an interface configuration option For the following order interface, you need to bind the monthly account number to be correct and legal, and confirm whether you need to use the routing label. If there is no interface configuration option such as order filtering interface, the default configuration is sufficient. After the configuration is complete, the API connection can be completed through sandbox testing and production environment review.

Among them, the initial configuration unit includes:

The account generation module is configured to generate an API docking account according to the user registration information;

The sandbox generation module is configured to generate the corresponding sandbox test environment according to the basic parameters of the API interface configured by the user account;

A sandbox key module, configured to send a sandbox test environment key to the user according to the registration information;

The sandbox configuration module is configured to configure the corresponding sandbox test environment for the user account by verifying the user's sandbox test environment key.

Sandbox testing units include:

The deadline setting module is configured to set the sandbox testing deadline;

A times recording module, configured to record the successful times of uploading transaction credential information by the user account within the test period;

a number of times judgment module, configured to judge whether the number of successful times reaches a preset number of times;

A test pass module, configured to determine that the user account passes the sandbox test;

The test failure module is configured to determine that the user account fails the sandbox test, and returns an error prompt.

The docking completion unit includes:

A production judging module, configured to judge whether the production request information passes the audit;

The verification docking module is configured to send the production configuration key to the user and complete the API docking with the user by verifying the user's production configuration key;

The failure return module is configured to return the production request information audit failure and the reason for the failure.

In the API docking system of this embodiment, the initial configuration unit first configures a sandbox test environment for the user account according to the user account request information, and then the sandbox test unit uploads the transaction credential information in the sandbox test environment. The number of successes is used as a judging factor for the user account to pass the sandbox test. The production audit unit audits the production configuration requests sent by the users who have passed the sandbox test, and the docking completion unit completes the API docking by issuing and verifying the keys to the users whose production configuration requests have passed the audit. The API interface can be used in the production environment. use. The invention can automatically complete the API docking with the user, reduce the work of regional sales colleagues to connect with customers, and reduce the labor cost of the enterprise; reduce the process approval procedure, realize the zero ECP approval process, and improve the work efficiency of the enterprise; It can quickly complete the API docking operation.

Taking the docking platform of Fengqiao as an example, the API docking method corresponding to the above-mentioned API docking system provided by the present invention is described, including:

S1. Configure a sandbox testing environment for the user account according to the user account request information.

The user account is generated according to the registration information entered by the user, and the registration information includes the company name, the contact information of the person in charge of the connection, etc. After logging in to the account, the user selects the required API interface and configures the corresponding basic parameters according to the business needs. The user selects the order placing interface and the order screening interface according to the business needs, and configures the basic information of the order placing interface and the basis of the order screening interface according to the requirements. For example, if there is the following order interface of the interface configuration option, the monthly account number that needs to be bound is correct and legal, and it is necessary to confirm whether the routing label needs to be used. If there is no interface configuration option such as order filtering interface, the default configuration is sufficient. In other embodiments of the present invention, if the platform of the API interface provider has only one API interface provided to the client, the client does not need to select an API interface and configure basic parameters.

After the user configures the API interface that needs to be connected according to the business needs, the user sends the request information to the upper-layer system (the system that the customer actually uses the API interface, such as the Fengqiao platform), and the upper-layer system generates the sandbox test environment according to the request information, such as the user request information. If the order interface is selected, the sandbox test environment of the order interface is generated. The upper-layer system issues the sandbox test environment use key to the user according to the registration information of the user account (the contact information of the person in charge), and the user enters the sandbox test environment use key to enter the sandbox test environment. The use time limit of the test environment is 7×24h. In the field of computer security, the application sandbox environment (also known as sandbox environment, English sandbox): refers to the test environment and development environment, which is provided to developers for development and testing. Testing performed in an internal environment or network before going live is a security mechanism that provides an isolated environment for running programs. It is usually used for experimentation with programs whose sources are untrustworthy, destructive, or whose intent cannot be determined. Therefore, neither the information uploaded by the user to the sandbox test environment nor the modification operations performed on the information in the sandbox test environment will affect the upper-layer system, ensuring the security of the upper-layer system.

S2. The number of successful times of uploading transaction credential information in the sandbox test environment is taken as a judging factor for the user account to pass the sandbox test.

In this embodiment, the preset number of times is set to 3 times, and the transaction voucher information is the user's electronic receipt. Review the electronic face sheet uploaded by the user, check whether the template of the electronic face sheet meets the requirements, whether the electronic face sheet contains the order information, whether the barcode conforms to the coding specification, whether the terminal can scan the code for identification, etc., currently fixed The following points are not approved: 1. The format of the face sheet does not conform to the specification 2. The electronic face sheet is self-designed 3. The electronic face sheet is not the latest template 4. The picture of the non-electronic face sheet is not required to be included on the face sheet of test data. If the electronic form uploaded by the user fails to pass the review, the notification of failure to upload the electronic form and the reason for the failure will be returned so that the user can improve. If the electronic bill is approved, upload the electronic bill to the upper-level system and record it. The user can modify the electronic bill before it has passed the review, and it cannot be modified after passing the review. Within the validity period of the sandbox test environment (7×24h), it is judged whether the number of times the user has successfully uploaded the electronic face sheet has reached 3 times, and if it reaches 3 times, it is judged that the user has passed the sandbox test and entered the production audit link of step S3. If the number of successful times of uploading electronic face slips by the user does not reach 3, it will be determined that the user's sandbox test has not passed, and a failure prompt will be returned.

S3. Review the production request information of the user account that has passed the sandbox test.

User accounts that have passed the sandbox test can dynamically transition from the sandbox environment to the production environment according to the process status of the customer's application for API. The user uploads the production request information. The production request information mainly includes the company name, address, license information, and monthly card number in the company information. Check whether the customer is the company's monthly account customer and has corresponding customer information on the monthly account customer platform (this system has data synchronization with the monthly account customer platform, and the latest company's monthly account customer information can be queried in real time). If the production request information uploaded by the user can find the matching customer company information and monthly card number, it is determined that the production request information has passed the verification. If the production request information uploaded by the user cannot be queried, it will return to the user a prompt that the production information cannot pass the verification, and display the reason for the failure, so that the user can modify it.

S4. Verify the production key of the user account whose generation request information has passed the audit, and complete the API docking with the user account.

After the user's production request information is verified, the production configuration key is issued to the user (which can be sent to the reserved mailbox of the person in charge of the docking, etc.) The user enters the received production configuration key into the system, and the system records the production configuration key entered by the user. After the key verification, the user account enters the production environment, completes the API connection, and can be used normally.

Store user information in the API connection completion database. If the user account is frozen, the frozen user will call the API configuration interface, pass the TYPE as DELETE, and the API status will be information initialization, delete all the data in the database after the user has completed the API connection, thus prohibiting the use of all functions of the API. When the user needs to unfreeze the API and re-connect to the API, he needs to configure the basic parameters of the API interface and send a request again to perform sandbox testing and production environment review. After the above steps are completed, the interface status of the user returns to the normal use status.

If a user who has connected to an API interface needs to connect to another type of API interface, the user needs to reconfigure the basic parameters of the API interface to be connected to send a request for sandbox testing.

If users need to change their permissions from monthly account customers to multi-month account customers, they only need to pass the production environment review process again, and no need to pass the sandbox test.

A device in this embodiment, the device includes: one or more processors;

memory for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors are made to execute any of the methods described above, and the API docking method can be executed more quickly by the processors. Complete API docking and improve service quality.

A computer-readable storage medium storing a computer program in this embodiment is characterized in that, when the program is executed by a processor, any one of the methods described above is implemented, and the API implemented when executed by the processor is stored. The docking method is convenient for docking with the user's API. Further introduction is as follows:

The computer system includes a central processing unit (CPU) 101 that can perform various appropriate actions and in accordance with a program stored in a read only memory (ROM) 102 or a program loaded from a storage portion into a random access memory (RAM) 103. deal with. In the RAM 103, various programs and data necessary for system operation are also stored. The CPU 101 , the ROM 102 , and the RAM 103 are connected to each other through a bus 104 . An input/output (I/O) interface 105 is also connected to the bus 104 .

The following components are connected to the I/O interface 105: an input section 106 including a keyboard, a mouse, etc.; an output section including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 108 including a hard disk, etc.; And a communication section 109 including a network interface card such as a LAN card, a modem, and the like. The communication section 109 performs communication processing via a network such as the Internet. Drives are also connected to the I/O interface 105 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 108 as needed.

In particular, according to an embodiment of the present invention, the process described above with reference to flowchart 1 may be implemented as a computer software program. For example, Embodiment 1 of the present invention includes a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion, and/or installed from a removable medium. When the computer program is executed by the central processing unit (CPU) 101, the above-described functions defined in the system of the present application are executed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Block diagram 2 of the accompanying drawings illustrates the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments 1 of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

The units involved in the embodiments of the present invention may be implemented in a software manner, or may be implemented in a hardware manner, and the described units may also be provided in a processor. Among them, the name of these units does not constitute a limitation of the unit itself under certain circumstances. The described unit or module can also be set in the processor. For example, it can be described as: an API docking system, including: a sandbox testing unit, a process triggering unit, a request verification unit, and a docking completion unit, wherein the In some cases, the name does not constitute a limitation on the unit itself. For example, the sandbox test unit can also be described as "used to call the API interface in the sandbox environment according to the transaction credential information of the docking requester and record the calling API A sandbox test unit for interface successes".

As another aspect, the present application also provides a computer-readable medium. The computer-readable medium may be included in the electronic device described in the above embodiments; it may also exist alone without being assembled into the electronic device. middle. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the API docking method described in the above embodiments.

For example, the electronic device can implement as shown in FIG. 1: Step S1: call the API interface in the sandbox environment according to the transaction credential information of the docking requester and record the number of successful calls to the API interface; Step S2: according to the success The number of times triggers the application production process; Step S3: verify the request information of the docking request sender entering the application production process, and send the API production configuration key to the docking request sender after the verification is passed; Step S4: verify the docking request sender The API production configuration key completes the docking with the API of the docking request sender.

It should be noted that although several modules or units of the apparatus for action performance are mentioned in the above detailed description, this division is not mandatory. Indeed, according to embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into multiple modules or units to be embodied.

Additionally, although the various steps of the methods of the present disclosure are depicted in the figures in a particular order, this does not require or imply that the steps must be performed in the particular order or that all illustrated steps must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, and the like.

The above description is only a preferred embodiment of the present application and an illustration of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to the technical solution formed by the specific combination of the above-mentioned technical features, and should also cover the above-mentioned technical features without departing from the inventive concept. Other technical solutions formed by any combination of its equivalent features. For example, the above features have similar functions to those disclosed in this application (but not limited to).

Claims (10)

1. an API docking method, is characterized in that, comprises: Configure a sandbox testing environment for the user account according to the user account request information; The number of successful times of uploading transaction voucher information in the sandbox test environment is used as the judgment factor for the user account to pass the sandbox test; Review the production request information of user accounts that pass the sandbox test; It is verified that the generation request information passes through the production key of the audited user account, and the API docking with the user account is completed. 2. The method according to claim 1, wherein, configuring a sandbox testing environment for the user account according to the user account request information, comprising: Generate an API docking account based on user registration information; Generate the corresponding sandbox test environment according to the basic parameters of the API interface configured by the user account; Send the sandbox test environment key to the user according to the registration information; The corresponding sandbox test environment is configured for the user account by validating the user's sandbox test environment key. 3. The method according to claim 1, wherein the successful number of times of uploading transaction credential information in the sandbox test environment is used as a judgment factor for the user account to pass the sandbox test, comprising: Set the sandbox testing period; Record the number of successful times of uploading transaction credential information by the user account within the test period; Determine whether the number of successes reaches a preset number: If yes, it is determined that the user account has passed the sandbox test; If not, it is determined that the user account has failed the sandbox test, and an error message is returned. 4. The method according to claim 1, wherein the verification generation request information passes through the production key of the audited user account, and completes the API docking with the user account, comprising: Determine whether the production request information has passed the audit: If yes, send the production configuration key to the user and complete the API connection with the user by verifying the user's production configuration key; If not, it returns the production request information audit failure and the reason for the failure. 5. an API docking system, is characterized in that, comprises: an initial configuration unit, configured to configure a sandbox testing environment for the user account according to the user account request information; The sandbox testing unit is configured to use the number of successful uploading of transaction voucher information in the sandbox testing environment as a judging factor for the user account to pass the sandbox testing; The production audit unit is configured to audit the production request information of the user account that has passed the sandbox test; The docking completion unit is configured to verify the production key of the user account whose generation request information has passed the audit, and complete the API docking with the user account. 6. The system according to claim 5, wherein the initial configuration unit comprises: The account generation module is configured to generate an API docking account according to the user registration information; The sandbox generation module is configured to generate the corresponding sandbox test environment according to the basic parameters of the API interface configured by the user account; A sandbox key module, configured to send a sandbox test environment key to the user according to the registration information; The sandbox configuration module is configured to configure the corresponding sandbox test environment for the user account by verifying the user's sandbox test environment key. 7. The system according to claim 5, wherein the sandbox testing unit comprises: The deadline setting module is configured to set the sandbox testing deadline; A times recording module, configured to record the successful times of uploading transaction credential information by the user account within the test period; a number of times judgment module, configured to judge whether the number of successful times reaches a preset number of times; A test pass module, configured to determine that the user account passes the sandbox test; The test failure module is configured to determine that the user account fails the sandbox test, and returns an error prompt. 8. The system according to claim 5, wherein the docking completion unit comprises: A production judging module, configured to judge whether the production request information passes the audit; The verification docking module is configured to send the production configuration key to the user and complete the API docking with the user by verifying the user's production configuration key; The failure return module is configured to return the production request information audit failure and the reason for the failure. 9. A device, characterized in that the device comprises: one or more processors; memory for storing one or more programs, The one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-4. 10. A computer-readable storage medium storing a computer program, characterized in that, when the program is executed by a processor, the method according to any one of claims 1-4 is implemented.

Images