CN107748985B - Network-based payment method and network payment server - Google Patents
Network-based payment method and network payment server Download PDFInfo
- Publication number
- CN107748985B CN107748985B CN201711086778.9A CN201711086778A CN107748985B CN 107748985 B CN107748985 B CN 107748985B CN 201711086778 A CN201711086778 A CN 201711086778A CN 107748985 B CN107748985 B CN 107748985B
- Authority
- CN
- China
- Prior art keywords
- payment
- merchant
- channel
- user
- server
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000012795 verification Methods 0.000 claims abstract description 27
- 230000006870 function Effects 0.000 description 11
- 238000011161 development Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/085—Payment architectures involving remote charge determination or related payment systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3227—Aspects of commerce using mobile devices [M-devices] using secure elements embedded in M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention provides a payment method based on a network and a network payment server. The method comprises the following steps: verifying the registration authentication information of the merchant, and displaying a plurality of payment channels on a merchant interface after the registration authentication information is verified; entering a parameter setting interface corresponding to the payment channel according to the payment channel selected by the merchant, so that the merchant sets channel party parameters related to the payment channel on the parameter setting interface; opening a payment service of a payment channel set by the parameters according to the access operation of the merchant; and receiving a payment instruction of the user, verifying the relevant information of the merchant, and automatically connecting a payment channel according to the payment instruction of the user after the verification is passed, thereby completing order payment. The method of the invention can provide payment service for the merchant more conveniently, thereby improving the payment efficiency.
Description
Technical Field
The invention relates to the technical field of network payment, in particular to a payment method based on a network and a network payment server.
Background
With the rapid development of internet e-commerce, channels for mobile payment and web payment are more and more, and the cost for a developer to access a payment channel is higher and higher, so that the development of network payment is limited to a certain extent, and a great deal of inconvenience is brought to a consumer to use network payment.
Disclosure of Invention
In view of this, embodiments of the present invention provide a network-based payment method and a network server, which may simplify payment operations and improve payment efficiency by automatically connecting a payment channel.
One aspect of the present invention provides a network-based payment method, including: verifying the registration authentication information of the merchant, and displaying a plurality of payment channels on a merchant interface after the registration authentication information is verified; entering a parameter setting interface corresponding to the payment channel according to the payment channel selected by the merchant, so that the merchant sets channel party parameters related to the payment channel on the parameter setting interface; opening a payment channel configured by the network parameters according to the access operation of the merchant; and receiving a payment instruction of the user, verifying the relevant information of the merchant, and automatically connecting a payment channel according to the payment instruction of the user after the verification is passed, thereby completing order payment.
In one embodiment, the information related to verifying the merchant includes: and verifying whether the registration of the merchant is authenticated, whether the payment channel is opened and whether the configuration of the payment parameters is correct, and if so, passing the verification.
In one embodiment, the method further comprises: entering a second payment setting interface when a merchant finishes setting channel party parameters of a certain payment channel on the merchant parameter setting interface, wherein the second payment interface comprises an unopened payment channel list and an opened payment channel list; adding the payment channel after the user sets the channel party parameters into the non-opened payment channel, wherein the opened payment channel list is displayed on a payment channel page selected by the user for the user to select a payment mode; the automatically connecting a payment channel according to a payment instruction of a user comprises: automatically connecting at least one payment channel in the list of opened payment channels.
In one embodiment, the payment service of opening a payment channel configured by parameters according to the access operation of the merchant comprises the following steps: providing the execution code and the calling code to the merchant, so that the merchant configures the execution code and the calling code; the automatically connecting at least one payment channel in the opened payment channel list according to the payment instruction of the user comprises: the execution code is invoked through the invocation code upon receipt of a payment instruction by a user, whereby the execution code introduces order parameters in the user interface relating to order title, order amount, order number and security verification.
In one embodiment, the method further comprises: and verifying the order parameters, if the order parameters pass the verification, connecting at least one payment channel in the opened payment channel list according to a payment instruction of the user, and completing order payment.
Another aspect of the present invention provides a network payment server, including a memory and a processor, wherein the memory stores payment application software, and when the processor calls the payment application software, the following steps are performed: verifying the registration authentication information of the merchant, and displaying a plurality of payment channels on a merchant interface after the registration authentication information is verified; entering a parameter setting interface corresponding to the payment channel according to the payment channel selected by the merchant, so that the merchant sets channel party parameters related to the payment channel on the parameter setting interface; opening a payment service of a payment channel set by the parameters according to the access operation of the merchant; and receiving a payment instruction of the user, verifying the relevant information of the merchant, and automatically connecting a payment channel according to the payment instruction of the user after the verification is passed, thereby completing order payment.
In one embodiment, the information related to verifying the merchant includes: and verifying whether the merchant is successfully registered, whether the registered merchant passes enterprise authentication, whether a payment channel is opened and whether the configuration of the payment parameters is correct, and if so, verifying to pass.
In one embodiment, the steps further comprise: entering a second payment setting interface when a merchant finishes setting channel party parameters of a certain payment channel on the merchant parameter setting interface, wherein the second payment interface comprises an unopened payment channel list and an opened payment channel list; automatically adding the payment channel after the user sets the channel party parameter into the non-opened payment channel, and displaying the opened payment channel list on a payment channel page selected by the user for the user to select a payment mode; the automatically connecting the payment channel according to the user payment instruction comprises: automatically connecting at least one payment channel in the list of opened payment channels.
In one embodiment, opening a payment service through a parameter-set payment channel according to an access operation of a merchant includes providing an execution code and a calling code to the merchant; the automatically connecting at least one payment channel in the opened payment channel list according to the payment instruction of the user comprises: the execution code is invoked through the invocation code upon receipt of a payment instruction by a user, whereby the execution code introduces order parameters in the user interface relating to order title, order amount, order number and security verification.
In one embodiment, the above steps further comprise: and verifying the order parameters, if the order parameters pass the verification, connecting at least one payment channel in the opened payment channel list according to a payment instruction of the user, and completing order payment.
The network payment method and the network payment server provided by the embodiment of the invention can assist the user to complete payment more conveniently, thereby improving the payment efficiency.
Drawings
Fig. 1 is a flowchart illustrating a network payment method according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of a second payment page according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of a network payment server according to an embodiment of the present invention.
Fig. 4 is a schematic diagram of a payment process according to an embodiment of the present invention.
Fig. 5 is a schematic view of an application scenario according to an embodiment of the present invention.
Detailed Description
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 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 payment channel is currently accessed, for example, one by one through the documents of the channel side, or various types of SDK languages are developed by third-party payment companies. The former is complex and complex in development, difficult in debugging, high in development technology threshold and high in cost, development requirements need to be newly increased when payment channels need to be added, and development modes of all channels are often different. The latter, although less complex than the former, still has a high technical threshold and requires a certain debugging development cycle.
Compared with the prior art, the second payment of the embodiment of the invention can access a plurality of payment channels only by three lines of codes, and the management of the payment channels only needs to be operated on one of a BeeCloud platform, a BeeCloud merchant system, a merchant platform and a merchant management platform, so that the technical threshold is reduced. In addition, the second payment mode of the invention also supports debug debugging, and can be better compatible with a PC, a mobile terminal and the like.
Specifically, in order to reduce the development cost of accessing the payment channel and the technical threshold of accessing the payment channel, the invention adopts a payment mode of second payment Button. In developing the second payment program, for example, three lines of code may be used to implement the functionality of accessing many payment channels. In addition, the second payment can be applied to both the PC side and the mobile side. For developers, the second payment of the embodiment of the invention can reduce development cost and optimize the experience of users in the payment process. In addition, the embodiment of the invention can ensure that the payment channel is accessed simply and quickly on the premise of ensuring the safety, and the visual operation can be carried out on the merchant management background only by non-developers after the payment channel is accessed.
One aspect of the present invention provides a network-based payment method. Referring to fig. 1, the method includes: s100, verifying the registration authentication information of a merchant, and displaying a plurality of payment channels on a merchant interface after the registration authentication information is verified; s101, entering a parameter setting interface corresponding to a payment channel according to the payment channel selected by a merchant, and setting channel party parameters related to the payment channel on the parameter setting interface by the merchant; s102, according to the access operation of the user, a payment service of a payment channel configured by the parameters is opened; s103, receiving a payment instruction of the user, verifying the relevant information of the merchant, and automatically connecting a payment channel according to the payment instruction of the user after the verification is passed, thereby completing order payment. The invention can realize the automatic connection of the payment channel through simple registration, thereby leading the payment operation to be more convenient and efficient.
In one embodiment, as described above, verifying the registration request of the merchant, and after the registration request is verified, after displaying the plurality of payment channels on the user interface, the method further includes: and entering a merchant parameter setting interface corresponding to the payment channel according to the payment channel selected by the merchant, so that the merchant sets channel party parameters related to the payment channel on the merchant parameter setting interface. For example, after selecting a common payment channel (such as WeChat or Payment treasure), the merchant may click on the payment channel to enter the merchant parameter setting interface. For example, the set parameter may be which account is charged. For example, the setting parameters of different payment channel parameters may be different. For example, the parameters to be set for the payment instrument include: payment treasure public key, private key, payment treasure APPID, channel rate. For example, the WeChat payment parameters include: WeChat public number, APPID, merchant number, API key, API certificate upload, API password, rate, and the like.
In one embodiment, the method further comprises: and entering a second payment setting interface when the merchant finishes setting the channel party parameters of a certain payment channel on the user parameter setting interface. Referring to fig. 2, the second payment interface includes a list 1 of unopened payment channels and a list 2 of opened payment channels (horizontal lines in the lists represent different payment channels), and a payment channel after a merchant has set channel party parameters can be automatically added to the opened payment channel. Further, automatically connecting the plurality of payment channels according to the payment instruction of the user includes: and automatically connecting the payment channels in the opened payment channel list according to the payment instruction of the user.
It should be noted that the payment instruction of the user is usually to select a certain payment channel. However, in some scenarios, for example, when a certain payment channel is low in funds, the user may select two or more payment channels at the same time, so that upon clicking the payment button, simultaneous payment of the two or more payment channels may be achieved. By providing a mode of simultaneously using a plurality of payment ways, the operation times of the user are simplified, and the payment experience is improved.
In this embodiment, for example, the merchant may drag the selection of these unopened payment channels into the list of opened channels and click, e.g., save or confirm, in the page to open the payment channel. For example, the merchant may ask all the pre-opened channels from the list of non-opened payment channels into the list of opened payment channels, and click to save. For example, the merchant clicks a certain payment channel in the list of the unopened payment channels, keeps a mouse in a pressed state, moves the mouse to drag the payment channel into the list of the opened payment channels, and releases the mouse, so that the payment channel enters the list of the opened payment channels. For example, when the mouse is released, whether the page is saved or not can be automatically popped up, so that the merchant can add the payment channel into the list of the opened payment channels when clicking the save button. For example, it is also possible to double click a certain payment channel in the unopened payment list, thereby popping up whether to add the payment channel to the opened payment channel list, and when the merchant clicks yes, the payment channel is added to the opened payment channel list by itself. According to the embodiment of the invention, the payment channels required to be used by the user and the payment channels which are not commonly used can be well distinguished by respectively setting the list of the payment channels which are not opened and the list of the payment channels which are opened, and the content of the two payment channel lists can be conveniently adjusted by a merchant along with the adjustment of the use habits of the payment channels of the user, so that the misoperation is effectively avoided. In addition, as the payment channels which are not commonly used by the users are arranged in the unopened payment channel list, when the users send out payment instructions, the payment channels which are not commonly used by the users do not need to be automatically connected, and therefore the occupation amount of network resources is reduced.
In this embodiment, for example, the payment priority may also be automatically adjusted according to the payment habits of the user. That is, the payment method commonly used by a certain user is set at the top, and the payment channel not commonly used is set at the bottom. For example, when a payment instruction of the user is received, the identity of the user can be judged through the instruction, that is, the user is identified. Therefore, when payment instructions of different users are received, the payment priority in the opened payment list can be adjusted correspondingly.
In one embodiment, the js file is generated when a merchant finishes entering the second payment setting interface when the merchant parameter setting interface sets the channel party parameter of a certain payment channel (e.g., the js file may be generated before); thereby the automatically connecting the payment channels in the list of the opened payment channels according to the payment instruction of the merchant comprises: and calling a BC.click () method in the js file according to a payment instruction received by a user, so as to introduce order parameters related to an order title, an order amount, an order number and security verification into a user interface, wherein the parameters are parameters required by the BC.click () method.
It should be noted that, the above parameters are essential parameters, for example, other parameters may also be added. These parameters may have different functions, and may include, for example, parameters for use in counting transactions, parameters for enabling a coupon function, and the like. The mode of the embodiment of the invention can support various extended functions, and a merchant only needs to add optional parameters. As mentioned above, these extended functions are implemented in the imported js file and the called back-end code, and the merchant only needs to call these codes.
Specifically, for example, a developer on the merchant side may access the merchant to the payment channel in their project by the following three lines of codes. The first line of code: and generating a js file in a second payment Button setting page introduced into the page needing payment. The second line of code: when the user clicks the pay button, the bc. Briefly, after a merchant registers and is authenticated by a server, the merchant may be provided with a first line code that may be used to perform a payment function after the merchant configures the code. The second line of code is used for calling the first line of code, so that the first line of code executes corresponding functions; that is, when the user clicks on payment, the merchant receives the payment information and the information is transmitted to the facilitator. For example, the facilitator calls the function of the first line code through the second line code to complete the payment process, verifying that the merchant is registered. The third line code is used for security verification, such as verifying the register authentication condition of the merchant, parameter configuration condition and the like. These codes may be provided when the merchant's registration is verified or may be automatically generated when the user completes the payment channel parameter configuration so that the merchant can configure the codes. It will be appreciated that the codes are used to essentially authorize the merchant, and the merchant accesses the server-side services through the codes, so that payment can be made through a payment channel when the user purchases goods from the merchant.
In case the first line code is called, the method will introduce some information of the order to be paid, such as the order title, the order amount, the order number, security verification and some other optional order parameters. For example, these order parameters may be used for statistical analysis of the amount of the order product, debug, etc. The specific determination can be according to user's demand. Namely, the order parameters appear on the user operation interface for the user to confirm. The third line of codes: and the safety check label in the third line of code needs to be generated in a back-end language of the server. The signature is used to verify order parameters such as price, order title and order number. If the verification is passed, the payment channels in the opened payment channel list can be connected according to the payment instruction of the user (for example, application appld, title, amount, out trade no (order number), and payment application appexecute are connected in sequence), and then the connected character string MD5 is calculated so as to assist the user in completing order payment.
Another aspect of the invention provides a network payment server. Referring to fig. 3, the server may for example comprise a memory 10 and a processor 20, wherein said memory 10 stores payment application software, and when said processor 20 invokes said payment application software, the following steps are performed: verifying a registration request of a merchant, and displaying a plurality of payment channels on a merchant interface after the registration request is verified; entering a parameter setting interface corresponding to the payment channel according to the payment channel selected by the merchant, so that the merchant sets channel party parameters related to the payment channel on the parameter setting interface; opening a payment channel configured by the network parameters according to the access operation of the merchant; and receiving a payment instruction of the user, verifying the relevant information of the merchant, and automatically connecting a payment channel according to the payment instruction of the user after the verification is passed, thereby completing order payment. For example, the server may be a third party server other than the user client, the merchant server. And the server can execute the above functions when the user of the client performs the above operations. Specifically, the merchant at the merchant server may click to register, and after submitting a registration request, validate the payment request, and after the payment request passes, the backend server may cause a plurality of payment channels to be displayed on the user interface. Therefore, when a user purchases commodities and clicks payment, the payment channels are automatically connected, and the payment of the commodities is completed quickly and conveniently by the user.
As described above, in one embodiment, the verifying the registration request of the merchant, and after the registration request is verified, after displaying the plurality of payment channels on the merchant interface, further includes: and entering a merchant parameter setting interface corresponding to the payment channel according to the payment channel selected by the merchant, so that the merchant sets channel party parameters related to the payment channel on the merchant parameter setting interface. For example, after selecting a common payment channel (such as WeChat or Payment treasure), the merchant may click on the payment channel, so that the server may enter the merchant interface into the parameter setting interface of the channel party. For example, these parameters may include a payment password, daily payment limit, single payment maximum limit, and the like.
In one embodiment, the server may cause the merchant interface to enter the second payment setting interface when the merchant completes setting the channel party parameters for a certain payment channel at the user parameter setting interface. Wherein the second payment interface comprises a list of unopened payment channels and a list of opened payment channels. And the server can automatically add the payment channel after the merchant sets the channel party parameters to the unopened payment channel, and the opened payment channel list is displayed on a payment channel page selected by the user so that the user can select a payment mode. The above-mentioned automatic connection includes according to the payment channel of user's payment instruction: the server automatically connects with at least one of the payment channels in the opened payment channel list.
In this embodiment, for example, the list of unopened payment channels is payment channels that were unopened in the second payment page. For example, the user may drag the selection of the unopened payment channels to the list of opened channels and click, e.g., save or confirm, on the page to open the payment channel. Those skilled in the art will appreciate that the above operations of the merchant are performed with the aid of the server background. Specifically, for example, the merchant may click on a certain payment channel in the list of the unopened payment channels, keep the mouse in a pressed state, move the mouse to drag the payment channel into the list of the opened payment channels, and after the mouse is released, store the payment channel into the list of the opened payment channels. For example, when the mouse is released, a save or not page may pop up automatically so that the payment channel may be added to the list of opened payment channels when the merchant may click on the save button. For example, it is also possible to double click a certain payment channel in the unopened payment list, thereby popping up whether the payment channel is added to the opened payment channel list, and when the user clicks yes, the payment channel is saved into the opened payment channel list by itself. The server of the embodiment of the invention can obviously distinguish the payment channels needed by the user from the payment channels which are not used temporarily by setting the payment channel lists which are not opened by the payment channel list, and can conveniently adjust and change the contents of the two payment channel lists along with the adjustment of the use habits of the payment channels of the user, thereby not only effectively avoiding misoperation, but also reducing the occupation of the server on network resources.
In one embodiment, the merchant accessing the payment channel may operate as follows: the payment server may generate a js file when the merchant completes setting of the channel party parameter of a certain payment channel on the user parameter setting interface and enters the second payment setting interface, the js file including the execution code. The automatically connecting payment channels in the list of opened payment channels comprises: call bc.click () method in the js file upon receiving a payment instruction from a user to introduce order parameters in the user interface relating to order title, order amount, order number and security verification.
Specifically, for example, a merchant developer may access a payment channel through the following three lines of codes. The first line of code: and generating a js file in a second payment Button setting page introduced to the shadow needing payment. The second line of code: when the user clicks the pay button, the bc. When the first line of code is called, some information of the order to be paid is introduced, such as the order title, the order amount, the order number, the security verification and some other optional order parameters. For example, these order parameters may be used for order product quantity amount statistical analysis, debug, and the like. The specific determination can be according to user's demand. Namely, the order parameters appear on the user operation interface for the user to confirm. The third line of codes: the security check in the second line of code requires the developer to generate in the server-side back-end language. The signature is used to verify order parameters such as price, order title, etc. If the verification is passed, at least one of the payment channels in the opened payment channel list (for example, applications appld, title, amount, and the payment application appexecute) can be connected according to the payment instruction of the user, and then the connected character string MD5 is calculated, so that the user can complete order payment.
The verification process includes, for example, verifying whether the merchant is registered, whether the registration information of the merchant passes the enterprise authentication, whether the payment channel is opened, whether the channel parameter configuration is correct, and the like. If the verification is unsuccessful, the order is displayed as unsuccessful at the buyer interface. Normally, when the method is used by a merchant, the merchant will usually test the method in advance after the parameters are configured, and after the test is successful, the merchant will put the method on line for use. If an unsuccessful order payment occurs, the merchant may reconfigure the channel side parameters to ensure successful payment by the buyer. The server of the embodiment of the invention can quickly access the payment channel only by three lines of codes, thereby greatly reducing the technical threshold, facilitating the user to quickly finish the selection of the payment channel and the payment of the fee, and greatly reducing the occupation of payment resources.
In one embodiment, the server further receives order information from a merchant server; verifying the order parameters according to the received order information, if the order information is consistent with the order parameters, connecting payment channels in the opened payment channel list according to a payment instruction (for example, sequentially connecting application appl, title, amount, and out trade no payment application appexecute), and then calculating a connected character string MD5 so that a user can complete order payment.
Note that in this embodiment, the order information is transmitted to the server after the user has filled the order. For example, the user may give up the payment or wait to pay at the same time for the next purchase for some reason. In this case, when the user purchases a product and fills an order at the merchant next time, the first-filled order information may be compared with the information stored in the server, and if it is consistent, the first-time purchase is valid, and the subsequent steps may be continued.
In addition, the network payment server can comprise a plurality of servers, so that background environments required for realizing the payment function are better deployed. This may also alleviate the possible poor operation in the case of a larger user population and a higher concurrency ratio. For example, the number of servers may be dynamically adjusted based on a statistical user population. For example, the correspondence between the number of users and the number of servers may be set so that the number of servers is automatically adjusted according to a change in the user group. A payment interface required for invoking payment is deployed in the back-end environment, so that when a merchant requests payment, a corresponding service is provided.
FIG. 4 illustrates a payment flow diagram of an embodiment of the present invention. Referring to fig. 4, the payment process includes: s2001: first, the merchant registers (for example, the merchant may register on a page on the internet), the server receives and verifies the registration authentication information of the merchant, and after the registration authentication information is verified, the merchant configures the payment parameters. S2002, after the merchant has configured the parameters, for example, the page supported by the server may enter a second payment button setup page. It should be noted that, after the user configures the parameters, the user may automatically jump to the second payment setting page, or the user may actively enter the second payment setting page according to the provided configuration information. The payment channels, e.g., the unopened channel and the opened channel as above, are provisioned and enabled and at least one payment channel is added to the opened payment channel. And S2003, accessing the payment channel through three lines of codes, wherein the process is also a link between the service function of the server and the merchant terminal, so as to ensure that the merchant terminal smoothly executes the payment process. After the merchant successfully accesses the payment channel, that is, establishes service authentication with the server, so as to acquire the service provided by the server, S2004 may be performed: the merchant can publish the configured system on-line for use by the user. In flow 2005: after the user selects the payment channel and clicks on payment, the process 2006 is executed: namely, the server side verifies the registration information of the merchant. For example, the information may include, but is not limited to, whether the registration is successful, whether the merchant's registration authentication information passes, whether the payment channel is opened, whether the payment parameter configuration is correct, and the like. And after the verification is passed, the page is transferred to a payment address of a payment channel, so that the whole payment process is completed. The payment method and the payment server provided by the embodiment of the invention can simply complete the setting and opening of the payment channel through the service provided by the server after the merchant accesses the service, so that the user can conveniently complete the purchase when purchasing the product of the merchant, and the development of the payment mode of the merchant is greatly simplified.
FIG. 5 illustrates an application scenario of an embodiment of the present invention. Referring to fig. 5, when a user makes an online payment, three terminals, namely, a merchant server side, a user side and a payment server, may be involved. First, the user needs to find the pre-purchased goods on the web page, and fill in the goods order parameters such as the purchase quantity after finding the goods. These parameters (which may include, for example, payment channel, order checkmark, order information, and user information, etc.) are passed to a server (the BeeCloud server) via the merchant server, which may then return the content of the channel collection address and payment information to the merchant server. The payment channel list and payment information are also returned to the user. I.e. the user may send these orders and verification information to the payment server via the merchant server. Therefore, the BeeCloud payment server can assist the user to simply and quickly complete the whole payment process after the orders are verified.
It should be noted that the server may be composed of two website servers and a plurality of payment system backend servers. For example, the two web servers include a disaster recovery. The website server is provided with an environment, a database and a merchant system code which are required by website operation, and is used for a system operation such as merchant registration, login authentication, payment parameter configuration, channel opening and the like. For example, multiple payment system servers deploy environments, databases, payment backend codes, etc. that run at the back end of the payment system. Through the configuration mode, high concurrency and load balance can be supported, and technologies such as multi-defense attack, wind control and the like are used, so that a safe and stable payment environment is provided for merchant users.
The network payment method and the network payment server provided by the embodiment of the invention can assist the user to complete payment more conveniently, thereby improving the payment efficiency.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place. Or may be distributed over multiple network elements. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units 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, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program check codes, such as a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (8)
1. A network-based payment method, comprising:
the network payment server verifies the registration authentication information of the merchant and displays a plurality of payment channels on a merchant interface after the registration authentication information is verified;
the network payment server enters a corresponding merchant parameter setting interface according to the payment channel selected by the merchant, so that the merchant sets channel party parameters of the payment channel selected by the merchant on the merchant parameter setting interface;
the network payment server opens payment service through a payment channel set by channel party parameters according to the access operation of a merchant;
the network payment server receives a payment instruction of a user, verifies relevant information of a merchant, and automatically connects a payment channel according to the payment instruction of the user after the verification is passed, so that order payment is completed, wherein the network payment server is a third-party server except a user client and the merchant server;
the network payment server enters a second payment setting interface when a merchant finishes setting channel party parameters of a payment channel selected by the merchant on the merchant parameter setting interface, wherein the second payment setting interface comprises an unopened payment channel list and an opened payment channel list; and is
The network payment server automatically adds the payment channel after the merchant sets the channel party parameter into the opened payment channel list, and the opened payment channel list is displayed on a payment channel page selected by the user for the user to select a payment mode;
the automatically connecting a payment channel according to a payment instruction of a user comprises:
automatically connecting at least one payment channel in the list of opened payment channels.
2. The payment method of claim 1, wherein the verifying the merchant-related information comprises: and verifying whether the merchant is successfully registered, whether the registered merchant passes enterprise authentication, whether a payment channel is opened and whether the configuration of the payment parameters is correct, and if so, verifying to pass.
3. The payment method according to claim 1, wherein the provisioning, by the network payment server, of the payment service through the payment channel set by the channel party parameter according to the access operation of the merchant comprises: the network payment server provides the execution code and the calling code to the merchant, so that the merchant configures the execution code and the calling code;
the automatically connecting at least one payment channel in the list of opened payment channels comprises:
the execution code is invoked through the invocation code upon receipt of a payment instruction by a user, whereby the execution code introduces order parameters in the user interface relating to order title, order amount, order number and security verification.
4. A payment method as recited in claim 3, further comprising:
and the network payment server verifies the order parameters, and if the order parameters pass the verification, the network payment server automatically connects at least one payment channel in the opened payment channel list and completes order payment.
5. A network payment server comprising a memory and a processor, wherein the memory stores payment application software, and when the processor invokes the payment application software, the following steps are performed:
verifying the registration authentication information of the merchant, and displaying a plurality of payment channels on a merchant interface after the registration authentication information is verified;
entering a corresponding merchant parameter setting interface according to the payment channel selected by the merchant, so that the merchant sets channel party parameters of the payment channel selected by the merchant on the merchant parameter setting interface;
opening payment service of a payment channel set by channel party parameters according to the access operation of a merchant;
receiving a payment instruction of a user, verifying relevant information of a merchant, and automatically connecting a payment channel according to the payment instruction of the user after the verification is passed, so as to complete order payment, wherein the network payment server is a user client and a third-party server except the merchant server;
entering a second payment setting interface when the merchant finishes setting the channel party parameters of the payment channel selected by the merchant on the merchant parameter setting interface, wherein the second payment setting interface comprises an unopened payment channel list and an opened payment channel list, and the second payment setting interface is used for allocating and starting the plurality of payment channels; and is
Adding the payment channel after the merchant sets the channel party parameters into the opened payment channel list;
the automatically connecting a payment channel according to a payment instruction of a user comprises:
automatically connecting at least one payment channel in the list of opened payment channels.
6. The server according to claim 5, wherein the information related to verifying the merchant comprises: and verifying whether the merchant is successfully registered, whether the registered merchant passes enterprise authentication, whether a payment channel is opened and whether the configuration of the payment parameters is correct, and if so, verifying to pass.
7. The server according to claim 5, wherein the provisioning of the payment service through the payment channel set by the channel party parameter according to the access operation of the merchant comprises: providing the execution code and the calling code to the merchant, so that the merchant configures the execution code and the calling code;
the automatically connecting a payment channel according to a payment instruction of a user comprises:
the execution code is invoked through the invocation code upon receipt of a payment instruction by a user, whereby the execution code introduces order parameters in the user interface relating to order title, order amount, order number and security verification.
8. The server of claim 7, further comprising:
and verifying the order parameters, and if the order parameters pass the verification, automatically connecting at least one payment channel in the opened payment channel list and completing order payment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711086778.9A CN107748985B (en) | 2017-11-07 | 2017-11-07 | Network-based payment method and network payment server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711086778.9A CN107748985B (en) | 2017-11-07 | 2017-11-07 | Network-based payment method and network payment server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107748985A CN107748985A (en) | 2018-03-02 |
| CN107748985B true CN107748985B (en) | 2021-05-28 |
Family
ID=61251957
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711086778.9A Expired - Fee Related CN107748985B (en) | 2017-11-07 | 2017-11-07 | Network-based payment method and network payment server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107748985B (en) |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110390520A (en) * | 2018-04-20 | 2019-10-29 | 上海憬承信息科技有限公司 | A kind of multichannel payment platform and its method of payment based on wechat payment |
| CN110490572B (en) * | 2018-05-15 | 2023-06-09 | 腾讯科技（深圳）有限公司 | Payment method, device, related equipment and system |
| CN108694574B (en) * | 2018-06-08 | 2021-08-20 | 创新先进技术有限公司 | Resource transfer channel processing method, device and equipment |
| CN109559102A (en) * | 2018-12-18 | 2019-04-02 | 厦门商集网络科技有限责任公司 | A kind of polymerization method of payment and terminal |
| CN109934589A (en) * | 2019-03-18 | 2019-06-25 | 农业部沼气科学研究所 | A network payment accounting transaction processing system and method based on the Internet of Things |
| CN110264171B (en) * | 2019-06-06 | 2023-04-18 | 深圳前海微众银行股份有限公司 | Distributed bill processing method, device, equipment and computer readable storage medium |
| CN110378688A (en) * | 2019-07-15 | 2019-10-25 | 深圳乐信软件技术有限公司 | A kind of generation method of trade company number, device, storage medium and electronic equipment |
| CN110648126A (en) * | 2019-09-29 | 2020-01-03 | 深圳乐信软件技术有限公司 | Payment type configuration method, device, server and storage medium |
| CN111222877A (en) * | 2019-10-31 | 2020-06-02 | 北京三快在线科技有限公司 | Commodity information processing method and device, storage medium and electronic equipment |
| CN111260342B (en) * | 2019-11-26 | 2023-04-07 | 泰康保险集团股份有限公司 | Authentication payment method and device |
| CN111222872B (en) * | 2020-01-08 | 2021-11-02 | 口碑(上海)信息技术有限公司 | User piece-entering method, device and system based on payment channel |
| CN111639927A (en) * | 2020-05-25 | 2020-09-08 | 上海中通吉网络技术有限公司 | Method and system for collecting money of network cashier desk |
| CN111935125B (en) * | 2020-08-05 | 2022-10-21 | 嘉联支付有限公司 | Authentication method and device based on distributed architecture and micro-service system |
| CN111966343A (en) * | 2020-08-11 | 2020-11-20 | 福建博思数字科技有限公司 | Method and system for visually constructing payment developer platform |
| CN112396411A (en) * | 2020-10-16 | 2021-02-23 | 深圳市科漫达智能管理科技有限公司 | Processing method of multiple payment channels and related device |
| CN112258173A (en) * | 2020-10-22 | 2021-01-22 | 广州市汇聚支付电子科技有限公司 | Intelligent payment routing method and system |
| CN112288418A (en) * | 2020-10-27 | 2021-01-29 | 广州小鹏汽车科技有限公司 | Payment method, payment device and storage medium for vehicle |
| CN113837746A (en) * | 2021-09-24 | 2021-12-24 | 商派软件有限公司 | Method and system for multi-channel simultaneous payment |
| CN114677196A (en) * | 2022-03-16 | 2022-06-28 | 国术之光文化传媒有限责任公司 | An online sales system for the sale of cultural and creative products |
| CN116029792A (en) * | 2023-01-16 | 2023-04-28 | 中国联合网络通信集团有限公司 | Mobile payment-based multi-tenant payment access method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105046482A (en) * | 2015-06-24 | 2015-11-11 | 上海海漾软件技术有限公司 | Mobile terminal payment method, device, and system |
| CN106408278A (en) * | 2016-09-08 | 2017-02-15 | 北京小度信息科技有限公司 | Payment method and apparatus |
| CN106412041A (en) * | 2016-09-20 | 2017-02-15 | 徐蔚 | System for connecting mobile terminal with service providing equipment and service providing method |
| CN106529918A (en) * | 2016-10-20 | 2017-03-22 | 北京众联享付科技股份有限公司 | Network payment technology channel management system for Unicom subscribers, merchants and third party payment channels |
| CN103679445B (en) * | 2013-12-17 | 2017-10-13 | 广州云移信息科技有限公司 | Method of network payment and its network payment system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186860A (en) * | 2011-12-30 | 2013-07-03 | 上海博泰悦臻电子设备制造有限公司 | Electronic payment system based on cloud data processing technology |
| CN105184554A (en) * | 2015-08-21 | 2015-12-23 | 广州博鳌纵横网络科技有限公司 | On-line transaction method for intellectual property |
| US20170068952A1 (en) * | 2015-09-03 | 2017-03-09 | Bank Of America Corporation | System for electronic collection and display of account token usage and association |
-
2017
- 2017-11-07 CN CN201711086778.9A patent/CN107748985B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103679445B (en) * | 2013-12-17 | 2017-10-13 | 广州云移信息科技有限公司 | Method of network payment and its network payment system |
| CN105046482A (en) * | 2015-06-24 | 2015-11-11 | 上海海漾软件技术有限公司 | Mobile terminal payment method, device, and system |
| CN106408278A (en) * | 2016-09-08 | 2017-02-15 | 北京小度信息科技有限公司 | Payment method and apparatus |
| CN106412041A (en) * | 2016-09-20 | 2017-02-15 | 徐蔚 | System for connecting mobile terminal with service providing equipment and service providing method |
| CN106529918A (en) * | 2016-10-20 | 2017-03-22 | 北京众联享付科技股份有限公司 | Network payment technology channel management system for Unicom subscribers, merchants and third party payment channels |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107748985A (en) | 2018-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107748985B (en) | Network-based payment method and network payment server | |
| US10796313B2 (en) | Method and system for facilitating online payments based on an established payment agreement | |
| US10152705B2 (en) | Quick payment using mobile device binding | |
| CN107533708B (en) | Unified login across applications | |
| US11144916B2 (en) | Techniques for conducting single or limited use purchases via a mobile device | |
| JP2015517143A (en) | System and method for payment approval by formula calculation and electronic signature | |
| CN110766394A (en) | Bus taking payment method and device based on credit degree, electronic equipment and storage medium | |
| US10771365B2 (en) | Optimizing timeout settings for nodes in a workflow | |
| CN111415146A (en) | Resource data processing method, device and equipment | |
| EP2980739A1 (en) | Multi-destination routing of transactions | |
| CN113988844A (en) | Service subscription method, device and system | |
| US11698800B2 (en) | Integration of third-party electronic transaction processing | |
| CN115018484A (en) | Skip payment method, aggregate payment platform, storage medium and computer equipment | |
| US20230325215A1 (en) | Integration of fragment modules in user interfaces | |
| US20240037515A1 (en) | Graphical user interface and card system for engaging in cryptocurrency transactions | |
| US20220335491A1 (en) | Method and system for providing electronic commerce service using partnership service cart realized by api in shopping mall | |
| KR20150021833A (en) | Method and system for paying on online | |
| US20240037536A1 (en) | Cryptocurrency card with customizable wallet assignment | |
| US12373269B2 (en) | Software orchestration framework for implementing application programming interfaces | |
| US20250061013A1 (en) | Software orchestration framework for implementing application programming interfaces | |
| JP2024134534A (en) | Method and device relating to payment service | |
| WO2022271138A2 (en) | A platform providing multiple applications | |
| HK40071422A (en) | Resource transfer method and apparatus based on instant messaging, medium and electronic device | |
| HK40071416A (en) | Test system, system test method, related equipment and storage medium | |
| CN119809626A (en) | Asset handling methods, devices, equipment, media and products |
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 |
Granted publication date: 20210528 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |