CN109426955B - Target object providing method, device and system - Google Patents

Target object providing method, device and system Download PDF

Info

Publication number
CN109426955B
CN109426955B CN201710729392.9A CN201710729392A CN109426955B CN 109426955 B CN109426955 B CN 109426955B CN 201710729392 A CN201710729392 A CN 201710729392A CN 109426955 B CN109426955 B CN 109426955B
Authority
CN
China
Prior art keywords
account
target object
request
payment
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.)
Active
Application number
CN201710729392.9A
Other languages
Chinese (zh)
Other versions
CN109426955A (en
Inventor
陈潇逸
徐永
李敏
谢颖
关昕
裴盼盼
周腾骏
沈嘉舟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201710729392.9A priority Critical patent/CN109426955B/en
Publication of CN109426955A publication Critical patent/CN109426955A/en
Application granted granted Critical
Publication of CN109426955B publication Critical patent/CN109426955B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/386Payment protocols; Details thereof using messaging services or messaging apps
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • G06Q20/227Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223Realising banking transactions through M-devices

Abstract

The application discloses a method, a device and a system for providing a target object, and relates to the field of electronic commerce. The method comprises the following steps: the method comprises the steps that a first terminal obtains presentation information of a target object; the payment server transfers the resource corresponding to the target object from the first account to the second account according to the first request sent by the first terminal; the product server sends a withholding request to the payment server; the payment server transfers the resources corresponding to the target object from the second account to a third account according to the withholding request, and sends a withholding success indication to the product server; the product server provides the target object to the second account. The application provides an indirect payment mode, so that an initial payer and a final payer of a product are not the same person, and the final payer and a product owner who successfully purchases the product are still the same person, and the problem that a target object can only be directly paid and purchased by the product owner who successfully purchases the product is solved.

Description

Target object providing method, device and system
Technical Field
The embodiment of the application relates to the field of electronic commerce, in particular to a method, a device and a system for providing a target object.
Background
With the development of online payment technology, users can purchase financial products through an application program on a mobile phone. Common financial products include: insurance, fund, gold, etc.
Taking insurance purchase as an example, a typical purchase method includes: the method comprises the steps that a user applies for insurance purchase to a server of an insurance company in an application program of a mobile phone, the server of the insurance company sends an insurance purchase page to the mobile phone of the user, the user fills in purchase information and sends the filled insurance purchase page to the server of the insurance company through the mobile phone, the server of the insurance company sends a payment page to the mobile phone of the user after confirming the filling information, the user pays online through the mobile phone, and after payment succeeds, the server of the insurance company provides insurance for the user who executes payment.
In the above-mentioned purchasing process of financial products, the payment of the products can be paid directly only by the owner of the products after successful purchase, the function of the application program with the purchasing capability of the financial products is single.
Disclosure of Invention
In order to solve the problem that the function of an application program with the purchasing capability of financial products is single due to the fact that products and/or services can only be paid by a product owner after successful purchase, the embodiment of the application provides a target object providing method, device and system. The technical scheme is as follows:
in a first aspect, a target object providing method is provided, the method including:
the method comprises the steps that a first terminal obtains presentation information of a target object, wherein the presentation information comprises: the resource, the first account and the second account corresponding to the target object;
the first terminal sends a first request to a payment server according to the presentation information;
the payment server transfers the resource corresponding to the target object from the first account to the second account according to the first request, and sends a transfer success indication to a product server;
the product server sends a withholding request to the payment server according to the transfer success indication, wherein the withholding request is used for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server;
the payment server transfers the resources corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, and sends a withholding success indication to the product server;
the product server provides the target object to the second account according to the withholding success indication.
In a second aspect, a target object providing method is provided, the method comprising:
receiving a transfer success indication sent by a payment server, wherein the transfer success indication is an indication generated after the payment server transfers the resource corresponding to the target object from a first account to a second account;
sending a withholding request to the payment server according to the transfer success indication, wherein the withholding request is used for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server;
receiving a deduction success indication sent by the payment server, wherein the deduction success indication is an indication generated after the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the deduction request;
and providing the target object to the second account according to the withholding success indication.
In a third aspect, a target object providing method is provided, the method including:
receiving a first request sent by a first terminal, wherein the first request is generated by the first terminal according to donation information;
transferring the resource corresponding to the target object from the first account to the second account according to the first request, and sending a transfer success indication to a product server;
receiving a deduction replacing request sent by the product server, wherein the deduction replacing request is used for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server;
and transferring the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, and sending a withholding success indication to the product server.
In a fourth aspect, there is provided a target object providing apparatus, the apparatus comprising:
the first receiving module is used for receiving a transfer success indication sent by a payment server, wherein the transfer success indication is an indication generated after the payment server transfers the resource corresponding to the target object from a first account to a second account;
a sending module, configured to send a withholding request to the payment server according to the transfer success indication, where the withholding request is used to request that resources corresponding to the target object be transferred from the second account to a third account corresponding to the product server;
the first receiving module is further configured to receive a withholding success indication sent by the payment server, where the withholding success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request;
a providing module, configured to provide the target object to the second account according to the withholding success indication.
In a fifth aspect, there is provided a target object providing apparatus, the apparatus comprising:
the second receiving module is used for receiving a first request sent by a first terminal, and the first request is generated by the first terminal according to the presentation information;
the transfer module is used for transferring the resource corresponding to the target object from the first account to the second account according to the first request and sending a transfer success indication to a product server;
the second receiving module is further configured to receive a withholding request sent by the product server, where the withholding request is used to request that resources corresponding to the target object be transferred from the second account to a third account corresponding to the product server;
the transfer module is further configured to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, and send a withholding success indication to the product server.
In a sixth aspect, there is provided a product server comprising a processor and a memory, wherein at least one instruction, at least one program, set of codes, or set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the object providing method according to the second aspect and optional embodiments of the present application.
In a seventh aspect, a payment server is provided, which includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the target object providing method according to the third aspect and optional embodiments of the present application.
In an eighth aspect, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the object providing method according to the second aspect and its optional embodiments of the present application.
In a ninth aspect, there is provided a computer-readable storage medium having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein, which is loaded and executed by a processor to implement the object providing method according to the third aspect and its optional embodiments of the present application.
In a tenth aspect, a target object providing system is provided, where the target object providing system includes a payment server and a product server, the product server is configured to implement the target object providing method according to the second aspect and optional embodiments of the present application, and the payment server is configured to implement the target object providing method according to the third aspect and optional embodiments of the present application.
In an eleventh aspect, a target object providing system is provided, where the target object providing system includes a first terminal, a payment server, a product server, and a second terminal, where the product server is configured to implement the target object providing method according to the second aspect and optional embodiments of the present application, and the payment server is configured to implement the target object providing method according to the third aspect and optional embodiments of the present application.
The technical scheme provided by the embodiment of the invention has the beneficial effects that at least:
the technical scheme is that the method adopts an indirect payment mode, so that an actual payer (a presenter) and an order payer (a presenter) of a product can be different from each other, but the order payer and a product owner (the presenter) after successful purchase are still the same person, the application program has a function of enabling a first user to give the product and/or the service in a donation mode to a second user, and the function of the application program is enriched, so that the problem that the target object can only be purchased directly by a product owner after successful purchase is solved, and the financial product purchasing capability is relatively single due to the fact that the financial application program has the function of giving the product and/or the service in a donation mode.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a block diagram of a target object providing system provided by an exemplary embodiment of the present invention;
fig. 2a to 2b are flowcharts of a target object providing method according to an exemplary embodiment of the present invention;
fig. 3a to 3b are flowcharts of a target object providing method according to another exemplary embodiment of the present invention;
fig. 4a to 4b are flowcharts of a target object providing method according to another exemplary embodiment of the present invention;
fig. 5 is a flowchart of a target object providing method according to another exemplary embodiment of the present invention;
fig. 6a to 6b are flowcharts of a target object providing method according to another exemplary embodiment of the present invention;
fig. 7a to 7b are interface diagrams of a target object providing method according to an exemplary embodiment of the present invention;
fig. 8 is an interface diagram of a target object providing method according to another exemplary embodiment of the present invention;
fig. 9 is an interface diagram of a target object providing method according to another exemplary embodiment of the present invention;
fig. 10 is an interface diagram of a target object providing method according to another exemplary embodiment of the present invention;
fig. 11 is an interface diagram of a target object providing method according to another exemplary embodiment of the present invention;
fig. 12 is an interface diagram of a target object providing method according to another exemplary embodiment of the present invention;
fig. 13 is an interface diagram of a target object providing method according to another exemplary embodiment of the present invention;
fig. 14 is a block diagram of a structure of a target object providing apparatus provided in an exemplary embodiment of the present invention;
fig. 15 is a block diagram of a structure of a target object providing apparatus according to another exemplary embodiment of the present invention;
FIG. 16 is a block diagram of the structure of a product server provided by an exemplary embodiment of the present invention;
fig. 17 is a block diagram of a structure of a payment server provided by an exemplary embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Fig. 1 is a block diagram of a target object providing system according to an exemplary embodiment of the present application. As shown in fig. 1, the system includes: a first terminal 11, a payment server 12, a second terminal 13 and a product server 14.
Wherein the first terminal 11 is a terminal for gifting a target object to a gifted account, the target object may be a product and/or a service. Illustratively, the first terminal 11 may be a mobile terminal, such as: any one of a mobile phone, a tablet and a portable notebook computer. At least one application having the capability of purchasing a target object is installed in the first terminal 11. Alternatively, the application may be an instant messenger and the instant messenger has the ability to purchase the target object. A first account is registered in the application, and the first terminal 11 gifts products and/or services to a second account (gifted account) through the first account. Illustratively, the first account is a first account of a first principal, the first principal being a user gifting a product and/or service to a donor. In this embodiment, the first subject is a subject that donates the target object to the second account via the first terminal. The first account is used to identify the first principal in the payment server 12. But when the application is an instant messaging application, the first account may include a first chat account and a first payment account bound to each other, the first chat account being used to identify the identity of the first principal in the instant messaging functionality logic, the first payment account being used to identify the identity of the first principal in the payment functionality logic, but since the first chat account and the first payment account are bound to each other, the first chat account and the first payment account may be considered equally one first account.
The first terminal 11 may communicate with the payment server 12 via the communication network 15, and optionally, the first terminal 11 may also communicate with the product server 14 via the communication network 15.
Alternatively, the communication network 15 may be at least one of a local area network, a wide area network, and a metropolitan area network.
The payment server 12 is a server for processing a fund transfer between accounts and/or a server for transferring communication information between accounts. Alternatively, the payment server may be composed of an instant messaging server and a resource transfer server, wherein the instant messaging server is a server for transmitting communication information between accounts, and the resource transfer server is a server for processing resource (fund) transfer between accounts.
Alternatively, the payment server 12 may communicate with the product server 14 through the communication network 15, and may also communicate with the second terminal 13 through the communication network 15.
The second terminal 13 is a terminal for receiving a target object given by the first account (the donor account), the target object includes a product and/or a service. The second terminal 13 may be a mobile terminal, such as: at least one of a mobile phone, a tablet and a portable notebook computer, and at least one application program with the capability of purchasing the target object is installed in the second terminal 13. The application may be an instant messenger and the instant messenger has the ability to purchase the target object. A second account is registered in the application program, and the second terminal 13 receives the products and/or services given from the first account through the second account. Illustratively, the second account is a second account of a second principal, and the second principal is a user who receives the gifted product and/or service of the donor, that is, the second principal is a principal that gifts the target object to the second account through the second terminal. The second account is used to identify the second principal in the payment server 12. But when the application is an instant messaging program, the second account may include a second chat account and a second payment account that are bound to each other, the second chat account is used to identify the identity of the second principal in the instant messaging function logic, and the second payment account is used to identify the identity of the second principal in the payment function logic, but since the second chat account and the second payment account are bound to each other, the second chat account and the second payment account may be equivalently regarded as one second account.
Alternatively, the second terminal 13 may communicate with the product server 14 through the communication network 15.
The product server 14 is a server installed in a third main body, and is used for selling a target object to an individual user or an enterprise user. The third principal may be an enterprise user that provides products and/or services. For example, the product server 14 is a server installed by an insurance company, and the product server 14 is used to sell insurance products or insurance services to individual users or other enterprise users. The product server 14 may access the payment server 12 through an open platform provided by the payment server 12. The product server 14 has a third account for identifying a third principal in the payment server 12. But when the application is an instant messenger, the third account may include a third chat account and a third payment account that are bound to each other, the third chat account is used to identify the third principal in the instant messenger function logic, and the third payment account is used to identify the third principal in the payment function logic, but since the third chat account and the third payment account are bound to each other, the third chat account and the third payment account may be equivalently regarded as one third account. The third chat account may be a public or service number applied for by the enterprise user.
It should be noted that, in various embodiments of the present application, the target object involved may be a product with a physical entity, or may be a service without a physical entity. For example, the target object may be an insurance product, a fund, a value-added service, a coupon, and the like.
Fig. 2a is a flowchart of a target object providing method according to an exemplary embodiment of the present invention. Taking the target object providing method applied to the system shown in fig. 1 as an example, as shown in fig. 2a, the target object providing method includes:
in step 201, the first terminal obtains gifting information for the target object.
The target object refers to an object which requires that the payment subject and the owning subject after payment is successful are the same subject, and optionally, the target object can be a product, such as: insurance products, funds, value added services, coupons, etc., the target object may also be a service, such as: financial services, investment consulting services, and the like. In this embodiment, the target object may be a product donated by the first account on the first terminal to the second account on the second terminal, and/or a service donated by the first account on the first terminal to the second account on the second terminal.
Optionally, the comp information comprises: and giving away the ticket number, the second account and the resource corresponding to the target object. The comp number refers to an identification number assigned to the same (group) comp event, typically assigned by the product server. The meaning referred to by the resource corresponding to the target object includes but is not limited to: an entity for purchasing the target object redeems the resource, a credit for purchasing the target object, and a credit for purchasing the target object. Alternatively, "the resource corresponding to the target object" may also be understood as "the amount of the resource corresponding to the target object"; the meaning referred to by the number of resources corresponding to the target object includes but is not limited to: at least one of a price corresponding to the target object, a credit value corresponding to the target object, and a credit score corresponding to the target object.
Optionally, the manner in which the first terminal obtains the donation information of the target object includes, but is not limited to:
the first mode is as follows: the first terminal acquires a presentation page of the target object from the product server, and acquires presentation information of the target object according to input of the first main body on the presentation page.
The second mode is as follows: and the second terminal sends the presentation page of the target object to the first terminal, and the first terminal acquires the presentation information of the target object according to the input of the first main body on the presentation page.
In step 202, the first terminal sends a first request to the payment server.
Optionally, the first request may be: any one of a payment request or a transfer request.
Referring to fig. 2b, schematically, the first request includes, but is not limited to: the method comprises the steps of giving a ticket number, the quantity of resources corresponding to a target object, the identification of a first account and the identification of a second account.
In step 203, the payment server transfers the resource corresponding to the target object from the first account to the second account according to the first request.
Optionally, the payment server directly transfers the resource corresponding to the target object from the first account to the second account according to the first request, and/or the payment server indirectly transfers the resource corresponding to the target object from the first account to the second account according to the first request. The "indirect transfer" refers to that the payment server transfers the resource corresponding to the target object from the first account to the third account, and then transfers the resource corresponding to the target object from the third account to the second account.
Illustratively, the payment server transfers the resource corresponding to the target object from the first account to the second account according to the amount of the resource corresponding to the target object in the first request, the first account and the second account.
In step 204, the payment server sends a transfer success indication to the product server.
The transfer success indication is an indication generated after the payment server transfers the resource corresponding to the target object from the first account to the second account, and as can be seen in fig. 2b, the transfer success indication includes, but is not limited to: the method comprises the steps of giving a ticket number, the quantity of resources corresponding to a target object, the identification of a first account and the identification of a second account.
In step 205, the product server receives a transfer success indication sent by the payment server.
In step 206, the product server sends a withholding request to the payment server.
Alternatively, the product server may send the withholding request to the payment server through a withholding interface provided by the payment server. The deduction is a function that the product server actively transfers the resource from the second account to a third account corresponding to the product server without the second account for operation under the condition of obtaining the authorization of the second account.
And the product server sends a withholding request to the payment server according to the received transfer success indication, wherein the withholding request is a request for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server. As can be seen from fig. 2b, the withholding request at least includes: a gift number, and an identification of the third account. Optionally, the withholding request further includes: and the identification of the second account and the resource quantity corresponding to the target object.
In step 207, the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request.
Optionally, the manner in which the payment server transfers the resource corresponding to the target object from the second account to the third account according to the withholding request includes, but is not limited to:
firstly, the payment server stores the donation order number, the quantity of the resources corresponding to the target object, the identification of the first account and the identification of the second account in the first request received in the step 203 in a database, when the payment server receives the withholding request sent by the product server, the payment server searches the database according to the donation order number in the withholding request, and transfers the resources corresponding to the target object from the second account to the third account according to the quantity of the resources corresponding to the target object corresponding to the donation order number in the database, the identification of the second account and the identification of the third account in the withholding request;
secondly, the withholding request sent by the product server to the payment server comprises: and the payment server transfers the resources corresponding to the target object from the second account to the third account according to the withholding request.
In step 208, the payment server sends a withholding success indication to the product server.
The deduction success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to the third account corresponding to the first product server according to the deduction request, and as can be seen in fig. 2b, the deduction success indication at least includes: a gift number or an identification of the second account.
In step 209, the product server receives the withholding success indication sent by the payment server.
In step 210, the product server provides the target object to the second account according to the withholding success indication.
Alternatively, the product server may store the comp number, the amount of the resource corresponding to the target object, the identifier of the first account, and the identifier of the second account in the database according to the transfer success indication received in step 205, may know that the second account of the target object is given according to matching between the comp number in the discount success indication and the data stored in the database, and may provide the target object to the second account.
Optionally, the ticket number for identifying the presenting event in the embodiment is a presenting ticket number, and it is described by taking an example that the presenting ticket number is carried in the first request, the transfer success indication, the withholding request, and the withholding success indication, in an actual operation, the ticket numbers for identifying the presenting event carried in the first request, the transfer success indication, the withholding request, and the withholding success indication may also be different ticket numbers, the database of the payment server and the database of the product server both store the corresponding relationship between the different ticket numbers and the presenting ticket numbers, and search for each parameter corresponding to the presenting ticket number according to the corresponding relationship.
In summary, in the target object providing method provided in this embodiment, resources corresponding to a target object are first transferred from a first account of a donor to a second account of a donor, and then the payment server transfers the resources corresponding to the target object from the second account of the donor to a third account of a product provider according to a discount request, and the product server provides the target object (product and/or service) to the second account according to a successful indication of the discount.
When the payment server transfers the resource corresponding to the target object from the first account to the second account, there are two solutions:
in the first indirect transfer mode, the payment server transfers the resource corresponding to the target object from the first account to the third account, and then transfers the resource corresponding to the target object from the third account to the second account, which is explained with the embodiment provided in fig. 3 a.
In the second direct transfer mode, the payment server directly transfers the resource corresponding to the target object from the first account to the second account by using a transfer mode, which is explained by using the embodiment provided in fig. 4 a.
In an alternative embodiment, the first request shown in fig. 2a and 2b is a payment request, and the resource corresponding to the target object is first transferred from the first account to the third account and then transferred from the third account to the second account through the payment request. As shown in fig. 3a, it is a flowchart of a target object providing method provided in another exemplary embodiment of the present application, the method includes the following steps:
in step 301, the first terminal obtains gifting information for the target object.
Optionally, the comp information comprises: the gift certificate number, the identification of the second account, the identification of the third account and the quantity of the resources corresponding to the target object. The presentation ticket number is an identification number for the same (group) presentation event in the target object providing method.
Optionally, the manner in which the first terminal obtains the donation information of the target object includes, but is not limited to:
the first mode is as follows: the first terminal acquires a presentation page of the target object from the product server, and acquires presentation information of the target object according to input of the first main body on the presentation page.
The second mode is as follows: and the second terminal sends the presentation page of the target object to the first terminal, and the first terminal acquires the presentation information of the target object according to the input of the first main body on the presentation page.
In step 302, the first terminal sends a payment request to a payment server.
The payment request is used for requesting to transfer the resource corresponding to the target object from the first account to the third account. As can be seen in connection with fig. 3b, the payment request includes: the method comprises the steps of giving a bill number, a resource corresponding to a target object, an identifier of a first account, an identifier of a second account and an identifier of a third account.
In step 303, the payment server transfers the resource corresponding to the target object from the first account to the third account according to the payment request.
Illustratively, the payment server transfers the resource corresponding to the target object from the first account to the third account according to the resource corresponding to the target object in the payment request, the first account and the third account.
In step 304, the payment server sends a payment success indication to the product server.
The payment success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the first account to the third account according to the payment request, and as can be seen in fig. 3b, the payment success indication includes, but is not limited to: a gift number, a resource of the target object, an identification of the first account, and an identification of the second account.
In step 305, the product server receives a payment success indication sent by the payment server.
In step 306, the product server sends a payment request to the payment server.
As can be seen from fig. 3b, the payment request is a request for transferring a resource corresponding to a target object from a third account to a second account, and at least includes: the order number is presented. Optionally, the payment request further includes: and the identifier of the third account, the identifier of the second account and the resource corresponding to the target object.
Optionally, the product server invokes an enterprise payment interface to send the payment request to the payment server, the enterprise payment interface being an interface provided by the payment server for the enterprise user to make payments to the individual users.
In step 307, the payment server transfers the resource corresponding to the target object from the third account to the second account according to the payment request.
Optionally, the payment server stores the gift number, the amount of the resource corresponding to the target object, the identifier of the first account, the identifier of the second account, and the identifier of the third account in the payment request in the database according to the payment request in step 303, and the payment server searches in the database according to the gift number in the payment request and transfers the resource corresponding to the target object from the third account to the second account according to the resource corresponding to the target object corresponding to the gift number, the identifier of the second account, and the identifier of the third account.
In step 308, the payment server sends a transfer success indication to the product server.
The transfer success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the third account to the second account according to the payment request, as can be seen in fig. 3b, the transfer success indication includes, but is not limited to: the gift certificate number.
In step 309, the product server receives a transfer success indication sent by the payment server.
In step 310, the product server sends a withholding request to the payment server.
And the product server sends a withholding request to the payment server according to the received transfer success indication, wherein the withholding request is a request for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server. As can be seen from fig. 3b, the withholding request at least includes: the order number is presented. Optionally, the withholding request further includes: and the identifier of the third account, the identifier of the second account and the quantity of the resources corresponding to the target object.
In step 311, the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request.
Optionally, the manner in which the payment server transfers the resource corresponding to the target object from the second account to the third account according to the withholding request includes, but is not limited to:
firstly, the payment server stores the donation order number, the quantity of the resources corresponding to the target object, the identification of the first account, the identification of the second account and the identification of the third account in the payment request received in the step 303 in a database, when the payment server receives a withholding request sent by a product server, the payment server searches the database according to the donation order number in the withholding request, and transfers the resources corresponding to the target object from the second account to the third account according to the quantity of the resources corresponding to the target object corresponding to the donation order number in the database, the identification of the second account and the identification of the third account;
secondly, the withholding request sent by the product server to the payment server comprises: and the payment server transfers the resources corresponding to the target object from the second account to the third account according to the withholding request.
In step 312, the payment server sends a withholding success indication to the product server.
The deduction success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to the third account according to the deduction request, and as can be seen in fig. 3b, the deduction success indication includes: the gift certificate number.
In step 313, the product server receives the withholding success indication sent by the payment server.
In step 314, the product server provides the target object to the second account according to the withholding success indication.
Alternatively, the product server may store the comp number, the amount of the resource corresponding to the target object, the identifier of the first account, and the identifier of the second account in the database according to the payment success indication received in step 305, may know the second account of the donated target object by matching the comp number in the deduction success indication with the data stored in the database, and may provide the target object to the second account.
Optionally, the ticket number for identifying the presenting event in the above embodiment is a presenting ticket number, which is described as an example that the presenting ticket number is carried in each of the payment request, the payment success indication, the payment request, the transfer success indication, the withholding request, and the withholding success indication, in an actual operation, the ticket numbers for identifying the presenting event carried in the payment request, the payment success indication, the payment request, the transfer success indication, the withholding request, and the withholding success indication may also be different ticket numbers, the database of the payment server and the database of the product server both store the correspondence between the different ticket numbers and the presenting ticket number, and search for each parameter corresponding to the presenting ticket number according to the correspondence.
Optionally, the transfer process and the deduction process are not perceived by the user, but the user may inquire the relevant records of the transfer process and the deduction process from the transaction details.
In summary, the resource corresponding to the target object is transferred from the first account to the third account by calling the enterprise payment interface, then the payment server transfers the resource corresponding to the target object from the third account to the second account according to the withholding request, and finally the resource corresponding to the target object is transferred from the second account to the third account through the withholding request, so that the target object is given, and the problem that the product and/or the service can only be paid by the owner of the product after the product is successfully purchased is solved. Meanwhile, the resource passes through the third account of the product server in the process of transferring the resource from the first account to the second account, so that the product server can timely know whether the transfer process is successful or not, and further timely send out a withholding request.
In an alternative embodiment, the first request shown in fig. 2a and 2b is a transfer request, and the transfer request directly transfers the resource corresponding to the target object from the first account to the second account. As shown in fig. 4a, it is a flowchart of a target object providing method according to another exemplary embodiment of the present application:
in step 401, the first terminal obtains gifting information for a target object.
Optionally, the comp information comprises: and the number of the donation bill number, the second account and the resource corresponding to the target object. The presentation number is an identification number for the same set of presentation events in the target object providing method.
Optionally, the manner in which the first terminal obtains the donation information of the target object includes, but is not limited to: the second terminal sends the presentation page of the target object to the first terminal, and the first terminal acquires the presentation information of the target object according to the presentation page; the first terminal obtains a presentation page from the product server and obtains presentation information of the target object according to the presentation page.
In step 402, the first terminal sends a comp request to the product server.
As can be seen in conjunction with FIG. 4b, the comp request includes: the method comprises the steps of giving a ticket number, the quantity of resources corresponding to a target object, the identification of a first account and the identification of a second account.
In step 403, the product server receives the comp request sent by the first terminal.
In step 404, the product server sends a transfer call request to the payment server.
And the product server sends a transfer calling request to the payment server according to the received donation request sent by the first terminal, wherein the transfer calling request is used for requesting the payment server to initiate a transfer process of transferring the resources corresponding to the target object from the first account to the second account.
Optionally, as can be seen from fig. 4b, the transfer call request includes: the method comprises the steps of giving a ticket number, the quantity of resources corresponding to a target object, the identification of a first account and the identification of a second account.
In step 405, the payment server receives a transfer invocation request sent by the product server.
In step 406, the payment server sends transfer information to the first terminal.
And the payment server sends transfer information to the first terminal according to the received transfer call request sent by the product server.
Optionally, as can be seen in conjunction with fig. 4b, the transfer information includes: the gift ticket number, the amount of resources corresponding to the target object, and the identification of the second account.
In step 407, the first terminal receives transfer information sent by the payment server.
In step 408, the first terminal sends a transfer request to the payment server.
The first terminal sends a transfer request to the payment server according to the received transfer information sent by the payment server, as can be seen in fig. 4b, the transfer request includes but is not limited to: the gift certificate number.
Optionally, the transfer request is used to indicate that the first terminal allows (or authorizes) the payment server to transfer the resource corresponding to the target object from the first account to the second account.
In step 409, the payment server transfers the resource corresponding to the target object from the first account to the second account according to the transfer request.
Optionally, the payment server may store the gift number, the number of resources corresponding to the target object, the identifier of the first account, and the identifier of the second account in the transfer call request according to the transfer call request received in step 405, query the database according to the gift number in the received transfer request, obtain the number of resources corresponding to the target object corresponding to the gift number, the identifier of the first account, and the identifier of the second account according to the matching result, and transfer the resource corresponding to the target object from the first account to the second account.
In step 410, the payment server sends a transfer success indication to the product server.
The transfer success indication is an indication generated after the payment server transfers the resource corresponding to the target object from the first account to the second account, as can be seen in fig. 4b, the transfer success indication includes, but is not limited to: the gift certificate number.
In step 411, the product server receives the transfer success indication sent by the payment server.
In step 412, the product server sends a withholding request to the payment server.
And the product server sends a withholding request to the payment server according to the received transfer success indication, wherein the withholding request is a request for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server. As can be seen from fig. 4b, the withholding request includes: a gift number, and an identification of the third account.
In step 413, the payment server transfers the resource corresponding to the target object from the second account to the third account according to the withholding request.
Optionally, the manner in which the payment server transfers the resource corresponding to the target object from the second account to the third account according to the withholding request includes, but is not limited to:
firstly, the payment server stores the donation order number, the quantity of resources corresponding to the target object, the identification of the first account and the identification of the second account in the transfer call request received in the step 405 in a database, when the payment server receives a withholding request sent by a product server, the payment server searches the database according to the donation order number in the withholding request, and transfers the resources corresponding to the target object from the second account to the third account according to the quantity of resources corresponding to the target object corresponding to the donation order number in the database, the identification of the second account and the identification of the third account in the withholding request;
secondly, the withholding request sent by the product server to the payment server comprises: and the payment server transfers the resource corresponding to the target object from the second account to the third account according to the deduction request.
In step 414, the payment server sends a withholding success indication to the product server.
The withholding success indication is an indication generated after the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the first product server according to the withholding request, as can be seen from fig. 2b, the withholding success indication may include: the order number is presented.
In step 415, the product server receives the withholding success indication sent by the payment server.
In step 416, the product server provides the target object to the second account according to the withholding success indication.
Optionally, the product server may store the comp number, the amount of the resource corresponding to the target object, the identifier of the first account, and the identifier of the second account in the database according to the transfer success indication received in step 402, match the comp number in the discount success indication with the data stored in the database to know the second account of the donated target object, and provide the target object to the second account.
Optionally, the sheet number for identifying the presenting event in the above embodiment is a presenting sheet number, and is described by taking the presenting sheet number as an example in all of the presenting request, the transfer call request, the transfer information, the transfer request, the transfer success indication, the withholding request, and the withholding success indication.
In summary, the resource corresponding to the target object is directly transferred from the first account to the second account through transfer call, and then the payment server transfers the resource corresponding to the target object from the second account to the third account according to the withholding request, and the product server provides the target object to the second account according to the withholding success indication, so that the problem that the product and/or the service can only be paid by the product owner who has successfully purchased the product is solved.
When the payment server provides a transfer call interface to the product server, the embodiment provided in fig. 4a may be adopted, and since the resource is directly transferred from the first account to the second account, the processing steps of the payment server are reduced, and when the service is busy, the processing pressure of the payment server can be effectively reduced, and the processing resource of the payment server is saved.
In an optional embodiment, before sending the withholding request to the payment server, the product server further needs to obtain the withholding right granted by the second terminal, as shown in fig. 5, which is a flowchart of a target object providing method according to another exemplary embodiment of the present invention, the target object providing method includes:
in step 501, the first terminal obtains gifting information for a target object.
The target object refers to a gifted product and/or service, and optionally, the target object may be an insurance product, a fund, a value-added service, a coupon, and the like. In this embodiment, the target object may be a product donated by the first account on the first terminal to the second account on the second terminal, and/or a service donated by the first account on the first terminal to the second account on the second terminal.
Optionally, the comp information comprises: and the number of the donation ticket number, the second account and the resource corresponding to the target object. The presentation order number refers to an identification number for the same set of presentation events in the target object providing method; the meaning of the number of resources corresponding to the target object includes but is not limited to: the price corresponding to the target object.
Optionally, the manner in which the first terminal obtains the donation information of the target object includes, but is not limited to: the first terminal obtains a presentation page from the product server and obtains presentation information of the target object according to the presentation page.
In step 502, the first terminal sends an object gifting request to the product server.
The object presentation request is for requesting the product server to generate a presentation confirmation request and to transmit the presentation confirmation request to the second terminal. Optionally, the object gifting request may include: the method comprises the steps of giving a ticket number, the quantity of resources corresponding to a target object, the identification of a first account and the identification of a second account.
Optionally, the payment server includes an instant messaging server and a resource transfer server, and the first terminal sends the object presentation request to the product server through the instant messaging server after sending the object presentation request to the instant messaging server.
In step 503, the product server generates a gift confirmation request according to the object gift request.
The donation confirmation request is used for the second account to confirm the target object donated by the first account, and optionally, the donation confirmation request includes: the gift certificate number, the amount of resources corresponding to the target object, and the identification of the first account.
Optionally, the donation confirmation request further includes: and the deduction-replacing permission request is used for requesting to acquire deduction-replacing permission for transferring the resource corresponding to the target object from the second account to a third account corresponding to the product server. Alternatively, the discount right request is not explicitly included in the present confirmation request, but the present confirmation request has the same function as the discount right request.
In step 504, the product server sends a comp confirmation request to the payment server.
The product server needs to send a donation confirmation request to the second terminal through the payment server.
Optionally, the payment server comprises: the product server sends the presentation confirmation request to the second terminal through the instant messaging server.
In step 505, the payment server receives a gift certificate request sent by the product server.
In step 506, the payment server forwards the donation confirmation request to the second terminal.
In step 507, the second terminal confirms the presentation confirmation request and generates a presentation confirmation instruction and an authority confirmation instruction.
The second terminal confirms the presentation confirmation request, that is, the second terminal accepts the target object presented by the first terminal and generates a presentation confirmation instruction, optionally, the presentation confirmation instruction includes: the comp number and an identification of the second account.
Optionally, the second terminal confirms the presentation confirmation request and confirms the deduction permission request included in the presentation confirmation request, and generates a permission confirmation instruction according to the deduction permission request, where the permission confirmation instruction is used to grant a deduction permission granted by the product server to deduct the resource corresponding to the target object from the second account to the third account corresponding to the product server, that is, the second terminal allows the product server to actively transfer the resource corresponding to the target object from the second account to the third account corresponding to the product server, and optionally, the permission confirmation instruction includes: the gift certificate number and the identification of the second account.
In a step 508, the process is repeated, and the second terminal sends an authority confirmation instruction to the payment server.
Optionally, the permission confirmation instruction includes: the gift certificate number and the identification of the second account.
Optionally, the rights confirmation indicates that the deduction rights granted to the product server are one-time, or, valid for a short time. Optionally, the permission validation indicates an upper limit of the deduction permission granted to the product server, and the upper limit does not exceed the amount of resources corresponding to the target object.
In step 509, the payment server saves the permission confirmation instruction sent by the second terminal to the database.
Optionally, the payment server responds to the donation confirmation request received in step 504 by: and storing the gift certificate number, the quantity of the resources corresponding to the target object and the identification of the second account in the authority confirmation instruction corresponding to the gift certificate number in a database.
Optionally, the payment server stores the deduction right of the second terminal according to the right confirmation instruction, and the deduction right is used for indicating that the product server has a right for deducting the resource from the second account to a third account corresponding to the product server.
In step 510, the second terminal sends a comp confirmation indication to the product server.
The presentation confirmation instruction is an instruction generated by the second terminal after confirming the received presentation confirmation request, and optionally, the presentation confirmation instruction includes: the gift certificate number and the identification of the second account.
Optionally, the payment server comprises: the second terminal sends the presentation confirmation instruction to the product server through the instant messaging server.
In step 511, the product server receives the comp confirmation instruction sent by the second terminal.
In step 512, the product server sends a comp confirmation indication to the first terminal.
Optionally, the payment server comprises: the product server sends the presentation confirmation instruction to the first terminal through the instant messaging server.
In step 513, the first terminal generates a first request according to the presentation confirmation indication.
The first request is a request for transferring a resource corresponding to the target object from a first account to a second account, and the first request includes but is not limited to: the gift certificate number. Optionally, the first request may be: at least one of a payment request or a transfer request.
In step 514, the first terminal sends a first request to the payment server.
In step 515, the payment server transfers the resource corresponding to the target object from the first account to the second account according to the first request.
Illustratively, the payment server stores the donation form number, the amount of the resource corresponding to the target object, the identifier of the first account, and the identifier of the second account in the donation confirmation request received in step 504 in a database, matches the donation form number in the first request with data in the database to obtain the amount of the resource corresponding to the target object corresponding to the donation form number, the first account, and the second account, and transfers the resource corresponding to the target object from the first account to the second account.
In step 516, the payment server sends a transfer success indication to the product server.
The transfer success indication is an indication generated after the payment server transfers the resource corresponding to the target object from the first account to the second account, and the transfer success indication may include: the gift certificate number.
In step 517, the product server receives the transfer success indication sent by the payment server.
In step 518, the product server sends a withholding request to the payment server.
And the product server sends a withholding request to the payment server according to the received transfer success indication, wherein the withholding request is a request for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server. The withholding request may include: a gift number, and an identification of the third account.
In step 519, the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request.
Optionally, the payment server includes, in the permission confirmation indication received in step 508: and when the gift confirmation instruction corresponding to the gift certificate number is obtained through matching, the payment server transfers the resource corresponding to the target object from the second account to the third account according to the deduction request.
Optionally, a plurality of deduction-substituting rights are stored in the payment server, and the payment server may query the deduction-substituting right according to at least one information of the donation order number, the identifier of the second account, and the identifier of the third account. And when the payment server confirms that the product server has the deduction right for transferring the resources corresponding to the target object from the second account to a third account corresponding to the product server, responding to the deduction request. Otherwise, the withholding request is not responded.
The method for transferring the resource corresponding to the target object from the second account to the third account by the payment server according to the withholding request includes, but is not limited to:
firstly, the payment server stores the donation order number, the quantity of the resources corresponding to the target object, the identification of the first account and the identification of the second account in the donation confirmation request received in the step 504 in a database, when the payment server receives the withholding request sent by the product server, the payment server searches the database according to the donation order number in the withholding request, and transfers the resources corresponding to the target object from the second account to the third account according to the quantity of the resources corresponding to the target object corresponding to the donation order number in the database, the identification of the second account and the identification of the third account in the withholding request;
secondly, the withholding request sent by the product server to the payment server comprises the following steps: and the payment server transfers the resources corresponding to the target object from the second account to the third account according to the withholding request.
In step 520, the payment server sends a withholding success indication to the product server.
The deduction success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to the third account corresponding to the first product server according to the deduction request, and optionally, the deduction success indication may include: the gift certificate number.
In step 521, the product server receives the withholding success indication sent by the payment server.
In step 522, the product server provides the target object to the second account according to the withholding success indication.
Alternatively, the product server may store the comp number in the comp confirmation request received in step 504, the amount of the resource corresponding to the target object, the identifier of the first account, and the identifier of the second account in the permission confirmation instruction received in step 508 in the database, may know the second account of the donated target object by matching the comp number in the deduction success instruction with the data stored in the database, and may provide the target object to the second account.
In the above embodiment, the second account is taken as an example to confirm the deduction authorization request in the presentation confirmation request, when the second account fails to confirm the deduction authorization request, or the network fails or the server fails, the payment server cannot transfer the resource from the second account to the third account, that is, the payment server cannot transfer the resource corresponding to the target object from the second account to the third account, the resource corresponding to the target object is still stored in the second account, and the execution of step 512 to step 515 fails.
In summary, by obtaining the right granted by the second account to transfer the resource from the second account to the third account in the payment server, the payment server transfers the resource corresponding to the target object from the second account to the third account according to the withholding request, and the product server provides the product to the second account according to the successful withholding instruction, and/or provides the service to the second account, the security of resource transfer of the second account is improved.
When the deduction fails, the resource is left in the second account and cannot return to the first account, so that unnecessary refund services of the product server are reduced, the failure times of execution of the donation services relative to the first terminal are avoided, and the donation services can still be considered to be successfully executed or semi-successfully executed.
In an optional embodiment, the payment server may be composed of an instant messaging server and a resource transfer server, and the first terminal obtains the presentation information of the target object through a presentation page sent by the instant messaging server. Fig. 6a is a flowchart of a target object providing method according to another exemplary embodiment of the present invention:
in step 601, the second terminal sends an acquisition request to the product server.
The obtaining request is used for requesting to obtain a target page of the target object, and the target page comprises the quantity of resources corresponding to the target object.
Optionally, the obtaining request includes: an identification of the target object, and a communication address of the second terminal.
Illustratively, the target object is a specified product, and the acquisition request sent by the second terminal to the product server is used to request to acquire a target page of the specified product, where the target page includes a price of the specified product.
In step 602, the product server receives an acquisition request sent by the second terminal.
In step 603, the product server sends a target page of the target object to the second terminal.
Optionally, the product server obtains a target page of the target object according to the identifier of the target object in the obtaining request, and sends the target page to the second terminal according to the communication address of the second terminal.
In step 604, the second terminal receives the target page sent by the product server.
In step 605, the second terminal generates a presentation page according to the target page.
The gift page is used for requesting to gift the target object in the target page, and optionally, the gift page includes: the amount of resources corresponding to the target object and a second account, the second account requesting to be given away from the account of the target object.
In step 606, the second terminal sends the comp page of the target object to the instant messaging server.
Optionally, an instant messaging application program is installed in the second terminal, a second account is logged in the instant messaging application program, the second account communicates with the first account on the first terminal through the instant messaging application program, and then the communication information sent between the second account and the first account needs to pass through an instant messaging server corresponding to the instant messaging application program.
In step 607, the instant messaging server sends the comp page of the target object to the first terminal.
In step 608, the product server sends a withholding permission request to the second terminal.
The deduction permission request is used for requesting to acquire permission for transferring the resource corresponding to the target object from the second account to a third account corresponding to the product server. Optionally, the deduction right request may include: a request for a ticket number and a third account.
Optionally, the product server sends the withholding permission request to the second terminal through the instant messaging server.
In step 609, the second terminal receives the withholding authority request sent by the product server.
In step 610, the second terminal generates an authority confirmation instruction according to the withholding request.
The second terminal generates an authority confirmation instruction after confirming the withholding authority request, and optionally, the authority confirmation instruction includes: the request ticket number, the second account, and an authorization confirmation result, wherein the authorization confirmation result may be a confirmation or a denial.
In step 611, the second terminal sends an entitlement confirmation indication to the resource transfer server.
In step 612, the resource transfer server receives the permission confirmation indication sent by the second terminal.
In step 613, the resource transfer server stores the deduction authority of the second account according to the authority confirmation instruction.
Optionally, the payment server stores the second account and the permission validation result according to the permission validation result in the permission validation instruction.
Optionally, the privilege validation indicates that the granted withholding privilege is one-time, or valid for a short time. The effective short duration is not limited and can be 10 seconds, 1 minute, 1 hour, 1 day, 1 week, or other duration.
In step 614, the resource transfer server generates an authorization indication.
Optionally, when the authorization confirmation result is confirmation, an authorization success indication is generated, and when the authorization result is negative confirmation, an authorization failure indication is generated.
In step 615, the resource transfer server sends an authorization indication to the product server.
At this time, the product server receives the authorization indication, so as to know that the withholding authority is granted by the second terminal.
In step 616, the first terminal obtains the presentation information of the target object according to the presentation page of the target object.
In this embodiment, the first terminal obtains the presentation information of the target object according to the presentation page of the target object sent by the instant messaging server, and optionally, the presentation information includes: and the number of the donation ticket number, the second account and the resource corresponding to the target object. The presentation number is an identification number for the same set of presentation events in the target object providing method.
In step 617, the first terminal sends a payment request to the resource transfer server.
The payment request is used for requesting to transfer the resource corresponding to the target object from the first account to the third account. The payment request may include: the method comprises the steps of giving a ticket number, the quantity of resources corresponding to a target object, the identification of a first account, the identification of a second account and the identification of a third account.
In step 618, the resource transfer server transfers the resource corresponding to the target object from the first account to the third account according to the payment request.
Illustratively, the payment server transfers the resource corresponding to the target object from the first account to the third account according to the amount of the resource corresponding to the target object in the payment request, the first account and the third account.
In step 619, the resource transfer server sends a payment success indication to the product server.
In step 620, the payment server receives the payment success indication sent by the resource transfer server.
The payment success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the first account to the third account according to the payment request, and the payment success indication includes, but is not limited to: a gift number, a resource of the target object, an identification of the first account, and an identification of the second account.
In step 621, the payment server sends a payment request to the resource transfer server.
The payment request is a request for requesting to transfer the resource corresponding to the target object from the third account to the second account, and optionally, the payment request includes: the gift certificate number.
In step 622, the resource transfer server transfers the resource corresponding to the target object from the third account to the second account according to the payment request.
Optionally, the payment server stores the gift certificate number, the amount of the resource corresponding to the target object, the identifier of the first account, the identifier of the second account, and the identifier of the third account in the payment request in the database according to the payment request in step 618, and the payment server searches in the database according to the gift certificate number in the payment request, and transfers the resource corresponding to the target object from the third account to the second account according to the amount of the resource corresponding to the target object corresponding to the gift certificate number, the identifier of the second account, and the identifier of the third account.
In step 623, the resource transfer server sends a transfer success indication to the product server.
The transfer success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the third account to the second account according to the payment request, and the transfer success indication includes, but is not limited to: the gift certificate number.
In step 624, the product server receives the transfer success indication sent by the resource transfer server.
In step 625, the production server sends a withholding request to the resource transfer server.
And the product server sends a withholding request to the payment server according to the received transfer success indication, wherein the withholding request is a request for requesting to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server. Optionally, the withholding request includes: the order number is presented.
In step 626, the resource transfer server transfers the resource corresponding to the target object from the second account to the third account corresponding to the product server according to the withholding request.
Optionally, a plurality of deduction-substituting rights are stored in the resource transfer server, and the payment server may query the deduction-substituting right according to at least one information of the donation order number, the identifier of the second account, and the identifier of the third account. And when the resource transfer server confirms that the product server has the deduction right for transferring the resource corresponding to the target object from the second account to the third account corresponding to the product server, responding to the deduction request. Otherwise, the withholding request is not responded.
Optionally, the manner in which the resource transfer server transfers the resource corresponding to the target object from the second account to the third account according to the deduction request includes, but is not limited to:
firstly, the resource transfer server stores the donation ticket number, the quantity of the resource corresponding to the target object, the identifier of the first account, the identifier of the second account and the identifier of the third account in the payment request received in step 618 in a database, when the resource transfer server receives a withholding request sent by the product server, the resource transfer server searches the database according to the donation ticket number in the withholding request, and transfers the resource corresponding to the target object from the second account to the third account according to the quantity of the resource corresponding to the target object corresponding to the donation ticket number, the identifier of the second account and the identifier of the third account in the database;
secondly, the withholding request sent by the product server to the resource transfer server includes: and the resource transfer server transfers the resources corresponding to the target object from the second account to the third account according to the withholding request.
In step 627, the resource transfer server sends a withholding success indication to the product server.
The deduction success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to the third account according to the deduction request, and optionally, the deduction success indication includes: the gift certificate number.
In step 628, the product server receives the withholding success indication sent by the resource transfer server.
In step 629, the product server provides the target object to the second account in accordance with the deduction success indication.
Optionally, the product server may store the comp number, the amount of the resource corresponding to the target object, the identifier of the first account, and the identifier of the second account in the database according to the payment success indication received in step 620, match the comp number in the deduction success indication with the data stored in the database to know the second account of the donated target object, and provide the target object to the second account.
It should be noted that, when the deduction fails due to a network failure, a server failure, or the like, the payment server cannot transfer the resource corresponding to the target object from the second account to the third account, that is, step 626 to step 629 cannot be performed, and the resource corresponding to the target object remains in the second account.
In summary, by transferring the resource corresponding to the target object from the first account to the third account, transferring the resource corresponding to the target object from the third account to the second account through the payment request, and finally transferring the resource corresponding to the target object from the second account to the third account through the payment server according to the deduction request, the product server provides the product to the second account according to the deduction success indication, and/or provides the service to the second account, the problem that the product and/or the service can only be paid by the product owner who has successfully purchased is solved, and by obtaining the right granted by the second account to transfer the resource from the second account to the third account in the payment server, the payment server transfers the resource corresponding to the target object from the second account to the third account according to the deduction request, the security of resource transfer of the second account is improved.
When the deduction fails, the resource is left in the second account and cannot return to the first account, so that unnecessary refund services of the product server are reduced, the number of times of execution failure of the presenting service relative to the first terminal is avoided, and the presenting service can still be considered to be successfully executed or semi-successfully executed.
In a specific embodiment, a first terminal is used as a presenter terminal, a first account is used as an account of a presenter, a second terminal is used as a presenter terminal, a second account is used as an account of a presenter, a payment server is a server provided by an instant messaging application program, the first account and the second account communicate through the instant messaging application program, the payment server is composed of an instant messaging server and a resource transfer server, a target object is an insurance product a, and a product server is an insurance company server provided by an insurance company to which the insurance product a belongs, as shown in fig. 6b, the method for providing the insurance product a includes:
in step 601, the acquirer terminal sends an acquisition request for insurance product a to the insurance company server.
Illustratively, the acquisition request is an information page for requesting acquisition of insurance product A, which includes the price of insurance product A, such as 20RMB.
Optionally, the obtaining request includes: the identity of insurance product a, and the communication address of the acquirer terminal.
In step 602, the insurance company server receives an acquisition request sent by the terminal of the donor.
In step 603, the insurance company server transmits a target page of the insurance product a to the acquirer terminal.
Optionally, the insurance company server obtains the target page of the insurance product a according to the identifier of the insurance product a in the obtaining request, and sends the target page to the terminal of the giftor according to the communication address of the terminal of the giftor.
In step 604, the giftor terminal receives the target page of the insurance product a sent by the insurance company server.
In step 605, the donor terminal generates a presentation page from the target page.
The gift page is used for requesting to gift insurance product a in the target page, and optionally, the gift page includes: the amount of resources to which insurance product a corresponds and the account of the donor who requested to be gifted.
In step 606, the giftor terminal sends a gifting page for insurance product a to the instant messaging server.
Optionally, an instant messaging application program is installed in the donor terminal, an account of the donor is logged in the instant messaging application program, the account of the donor communicates with an account of the donor on the donor terminal through the instant messaging application program, and then communication information sent between the account of the donor and the account of the donor needs to pass through an instant messaging server corresponding to the instant messaging application program.
In step 607, the instant messaging server sends the gift page for insurance product a to the gift-giver terminal.
The above steps 601 to 607 can be further understood in conjunction with fig. 7a, as shown in fig. 7a, taking the acquirer as xx as an example, the acquirer xx first sends an acquiring request of the insurance product a to the insurance company server, and the insurance company server sends a target page 71 of the insurance product a to the acquirer xx, wherein the target page 71 includes the price of the insurance product a: 20RMB, after the acquirer selects the option of applying for the delivery, a presentation page 72 is generated, which includes the price of the insurance product a: 20RMB and the donor account, namely: xx, the gifter enters the friend selection interface 73 to select the gifter, if the interface 73 shows, the gifter selects friend A as the gifter, if the interface 74 shows, the gifter sends a gift page of the insurance product A to friend A through the instant messaging server.
In an alternative embodiment, shown in the interface 75 of fig. 7b, the donor, in making the selection of the donor, may select a group-by-group buddy cluster, if friend group a is selected, the donor xx and a plurality of members are included in the friend group a, such as 4 members in friend group a: the giftor xx, the member a, the member B and the member C send the gift page of the insurance product a to the friend group a, and the member in the friend group a can gift the insurance product a to the giftor xx through the gift page of the insurance product a, as shown in an interface 76.
In step 608, the insurance company server sends a discount authority request to the acquirer terminal.
The deduction right request is used for requesting to acquire the right of transferring the resource corresponding to the insurance product A from the account of the donator to the account of the insurance company corresponding to the insurance company server. Optionally, the deduction right request may include: a request for a ticket number and an insurance company account.
In step 609, the acquirer terminal receives the discount authority request sent by the insurance company server.
In step 610, the donor terminal generates an authorization confirmation instruction according to the withholding request.
The acquirer terminal confirms the deduction permission request and then generates a permission confirmation instruction, and optionally, the permission confirmation instruction includes: a request ticket number, an account of the acquirer, and an authorization confirmation result, wherein the authorization confirmation result may be a confirmation or a denial.
In step 611, the acquirer terminal sends an authority confirmation indication to the resource transfer server.
In step 612, the resource transfer server receives the permission confirmation instruction sent by the acquirer terminal.
In step 613, the resource transfer server stores the deduction authority of the account of the acquirer according to the authority confirmation instruction.
Optionally, the payment server stores the account of the donor and the permission confirmation result according to the permission confirmation result in the permission confirmation instruction.
In step 614, the resource transfer server generates an authorization indication.
Optionally, when the result of the authority confirmation is confirmation, an authorization success indication is generated, and when the result of the authority confirmation is negative confirmation, an authorization failure indication is generated.
In step 615, the resource transfer server sends an authorization indication to the donor terminal.
Illustratively, the above steps 608 to 615 may be further understood with reference to fig. 8, as shown in fig. 8, which is a schematic diagram of an interface where an insurance company applies for a deduction-substituted permission request to an acquirer, the insurance company sends the deduction-substituted permission request to a acquirer terminal, and generates a deduction-substituted permission request interface 81, as shown in interfaces 81 and 82, the acquirer selects an authorization option and then inputs a password, and sends a permission confirmation instruction to a resource transfer server, the resource transfer server returns an authorization instruction to the acquirer, and as shown in interface 83, the resource transfer server sends an authorization success instruction to the acquirer.
In step 616, the donor terminal obtains the gifting information of the insurance product a according to the gifting page of the insurance product a.
In this embodiment, the donor terminal obtains the donation information of the insurance product a according to the donation page pair of the insurance product a sent by the instant messaging server. Optionally, the comp information comprises: the gift number, the account of the donor, and the amount of resources corresponding to insurance product a. The gift certificate number is an identification number for the same set of gift events in the insurance product a providing method.
In step 617, the donor terminal sends a payment request to the resource transfer server.
The payment request is used to request that the resource corresponding to insurance product a be transferred from the account of the donor to the account of the insurance company. The payment request may include: the gift certificate number, the amount of resource to which the insurance product a corresponds, the identity of the account of the presenter, the identity of the account of the beneficiary, and the identity of the account of the insurance company.
In step 618, the resource transfer server transfers the resource corresponding to the insurance product a from the account of the donor to the account of the insurance company according to the payment request.
Illustratively, the payment server transfers the resource corresponding to the insurance product a from the account of the donor to the account of the insurer based on the amount of the resource corresponding to the insurance product a in the payment request, the account of the donor, and the account of the insurer.
In step 619, the resource transfer server sends a payment success indication to the insurance company server.
In step 620, the payment server receives the payment success indication sent by the resource transfer server.
The payment success indication is an indication generated after the payment server transfers the resource corresponding to the insurance product a from the account of the donor to the account of the insurance company according to the payment request, and the payment success indication includes but is not limited to: the gift number, the resource of insurance product a, the identity of the account of the presenter, and the identity of the account of the beneficiary.
In step 621, the payment server sends a payment request to the resource transfer server.
The payment request is a request for transferring the resource corresponding to the insurance product a from the account of the insurance company to the account of the acquirer, and optionally, the payment request includes: the gift certificate number.
In step 622, the resource transfer server transfers the resource corresponding to insurance product a from the insurance company account to the account of the donor according to the payment request.
Optionally, the payment server stores the gift certificate number, the amount of the resource corresponding to the insurance product a, the identifier of the account of the presenter, the identifier of the account of the beneficiary, and the identifier of the account of the insurance company in the payment request in the database according to the payment request in step 618, and the payment server searches in the database according to the gift certificate number in the payment request and transfers the resource corresponding to the insurance product a from the account of the insurance company to the account of the beneficiary according to the amount of the resource corresponding to the insurance product a corresponding to the gift certificate number, the identifier of the account of the beneficiary, and the identifier of the account of the insurance company.
In step 623, the resource transfer server sends a transfer success indication to the insurance company server.
The transfer success indication is an indication generated after the payment server transfers the resource corresponding to the insurance product a from the insurance company account to the account of the donor according to the payment request, and the transfer success indication includes, but is not limited to: the gift certificate number.
In step 624, the insurance company server receives the transfer success indication sent by the resource transfer server.
In step 625, the insurance company server sends a withholding request to the resource transfer server.
And the insurance company server sends a withholding request to the payment server according to the received transfer success indication, wherein the withholding request is used for requesting to transfer the resource corresponding to the insurance product A from the account of the donor to the account of the insurance company corresponding to the insurance company server. Optionally, the withholding request includes: the gift certificate number.
In step 626, the resource transfer server transfers the resource corresponding to the insurance product a from the account of the transferee to the account of the insurance company corresponding to the insurance company server according to the discount request.
Alternatively, the manner in which the payment server transfers the resource corresponding to the insurance product a from the account of the donor to the account of the insurance company according to the withholding request includes, but is not limited to:
firstly, the payment server stores the gift number, the amount of the resource corresponding to the insurance product a, the identification of the account of the presenter, the identification of the account of the winner, and the identification of the account of the insurance company in the payment request received in step 618 in a database, when the payment server receives a withholding request sent by the insurance company server, the payment server searches the database according to the gift number in the withholding request, and transfers the resource corresponding to the insurance product a from the account of the winner to the account of the insurance company according to the amount of the resource corresponding to the insurance product a corresponding to the gift number, the identification of the account of the winner, and the identification of the account of the insurance company in the database;
secondly, the deduction substitute request sent by the insurance company server to the payment server comprises: the gift certificate number, the identification of the insurance company account, the identification of the account of the beneficiary, and the amount of the resource corresponding to the insurance product A, the payment server transfers the resource corresponding to the insurance product A from the account of the beneficiary to the insurance company account according to the withholding request.
In step 627, the resource transfer server sends a withholding success indication to the insurance company server.
The deduction success indication is an indication generated after the payment server transfers the resource corresponding to the insurance product a from the account of the beneficiary to the account of the insurance company according to the deduction request, and optionally, the deduction success indication comprises: the gift certificate number.
In step 628, the insurance company server receives the withholding success indication sent by the resource transfer server.
As shown in fig. 9, in the communication interface 91 with the beneficiary xx, the gifting party receives the gifting page of the insurance product a sent by the beneficiary xx, the gifting party selects the gifting page to enter the gifting page 92, the gifting party selects the payment option and then enters the password input page 93 to input the password, and optionally, the resource transfer server transfers the account of 20RMB corresponding to the insurance product a and sends a payment success page 94 to the gifting party.
In step 629, the insurance company server provides insurance product a to the account of the donor according to the rebate success indication.
Alternatively, the insurance company server may store the gift number, the amount of the resource corresponding to the insurance product a, the identification of the account of the presenter, and the identification of the account of the beneficiary in the database according to the payment success indication received in step 620, know the account of the beneficiary to which the insurance product a is gifted by matching the gift number in the discount success indication with the data stored in the database, and provide the insurance product a to the account of the beneficiary.
As shown in fig. 10, the insurance product a provided by the insurance company to the account of the donor includes the price of the insurance product a and the donor of the insurance product a.
It should be noted that, in the above embodiment, the result of the right confirmation is used as the confirmation, when the result of the right confirmation is negative, the payment server cannot transfer the funds corresponding to the insurance product a from the account of the transferee to the account of the insurance company, that is, steps 626 to 629 cannot be performed, and the funds corresponding to the insurance product a will remain in the account of the transferee.
In summary, the problem that the insurance product a can only be directly paid by the product owner (i.e. the acquirer) after successful purchase is solved by transferring the funds corresponding to the insurance product a from the account of the presenter to the account of the insurer, transferring the funds corresponding to the insurance product a from the account of the insurer to the account of the acquirer by the payment request, and finally transferring the funds corresponding to the insurance product a from the account of the insurer to the account of the insurer by the deduction request.
In an alternative embodiment, the target object is taken as a product of "baby vault", as shown in fig. 11 to 13:
as shown in fig. 11, in the user interface where the donor initiates the prize, the donor first obtains the prize application interface 1101 of the target object, i.e., "baby vault" product, and after the donor selects the prize application, the prize application is selected and sent to friend a, friend B, or group C, group D, or circle of friends in the user interface 1102, and the friends who have received the prize application can enter the prize interface by selecting the prize message. As shown in fig. 11, after the donor selects friend a to donate the product "baby vault" in user interface 1102, the donor sends a reward message to friend a in user interface 1103.
In an alternative embodiment, as shown in the interface 1102 of fig. 11, when the donor selects the donor, the donor may select a friend cluster in a group unit, such as a group C, which includes the donor and a plurality of members; the rewarding party can also send a rewarding message to the friend circle, and friends with the viewing permission of the rewarding party can reward the rewarding party through the rewarding message.
As shown in fig. 12, for a user interface when a donor gives a product of the treasure little vault to a donor, in a user interface 1201, the donor receives a reward message sent by a donor xx, selects the reward message, enters a reward interface 1202, includes related information about the product requested to be given by the donor in the reward interface 1202, such as that the product of the treasure little vault corresponds to photos of the donor and children, optionally, after the donor selects "i want to reward" in the reward interface 1202, the amount to be appreciated is selected in a selection interface 1203, as shown in fig. 12, the amount selected by the donor is 50 yuan, and selects "reward treasure vault", enters a password input page 1204 and inputs a password, and optionally, the resource transfer server transfers the product of the treasure little vault to the 50 yuan and sends a successful payment to an account page 1205 for the account of the supplier.
Alternatively, since the "baby vault" is a periodically paid savings-type insurance, if the user has previously purchased an insurance product of the "baby vault", then the payment is due for a renewal. As shown in fig. 13, the beneficiary obtains the successful renewal payment of the policy of the baby vault through a renewal success interface 1301, obtains various information including the policy number, the dangerous species, the payment date, the payment amount, the payment mode, and the presenter, and enters an account interface 1302 of the baby vault by clicking the entering account, and the account of the baby vault is displayed with 50 yuan growth money added in the interface. The information about the target object displayed in the user interface 1301 is only an illustrative example, and in actual operation, the information may further include enterprise information providing the target object, an expiration time of the target object, and the like, which is not limited in the embodiment of the present invention.
Fig. 14 is a block diagram of a target object providing apparatus according to an exemplary embodiment of the present application. The target object providing apparatus may be implemented as all or a part of the production server by software, hardware, or a combination of both. As shown in fig. 14, the target object providing apparatus includes: a first receiving module 1401, a transmitting module 1402 and a providing module 1403.
The first receiving module 1401 is configured to receive a transfer success indication sent by a payment server, where the transfer success indication is an indication generated after the payment server transfers a resource corresponding to the target object from a first account to a second account;
a sending module 1402, configured to send, according to the transfer success indication, a withholding request to the payment server, where the withholding request is used to request that a resource corresponding to the target object is transferred from the second account to a third account corresponding to the product server;
the first receiving module 1401 is further configured to receive a deduction success indication sent by the payment server, where the deduction success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the deduction request;
a providing module 1403, configured to provide the target object to the second account according to the withholding success indication. In an optional embodiment, the first receiving module 1401 is further configured to receive a payment success indication sent by the payment server, where the payment success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the first account to the third account;
the sending module 1402 is further configured to send a payment request to the payment server according to the payment success indication, where the payment request is used to request that the resource corresponding to the target object is transferred from the third account to the second account.
In an alternative embodiment, the sending module 1402 is further configured to send a payment request to the payment server through an enterprise payment interface according to the payment success indication, where the enterprise payment interface is an interface provided by the payment server for the enterprise user to pay the individual user.
In an optional embodiment, the first receiving module 1401 is further configured to receive a donation request sent by a first terminal, where the donation request is a request generated by the first terminal according to donation information;
the sending module 1402 is further configured to send a transfer call request to the payment server according to the presentation request, where the transfer call request is used to request the payment server to initiate a transfer process for transferring the resource corresponding to the target object from the first account to the second account.
In an optional embodiment, the sending module 1402 is further configured to send a deduction permission request to the second terminal, where the deduction permission request is used to request to acquire a permission to transfer the resource from the second account to a third account corresponding to the product server.
In an optional embodiment, the first receiving module 1401 is further configured to receive an obtaining request sent by the second terminal, where the obtaining request is used to request to obtain a target page of the target object, and the target page includes: a resource corresponding to the target object;
the sending module 1402 is further configured to send a target page of the target object to the second terminal according to the obtaining request.
Fig. 15 is a block diagram of a target object providing apparatus according to another exemplary embodiment of the present application. The target object providing apparatus may be implemented as all or a part of the payment server by software, hardware, or a combination of both. As shown in fig. 15, the target object providing apparatus includes: a second receive module 1501 and a transfer module 1502.
The second receiving module 1501 is configured to receive a first request sent by a first terminal, where the first request is generated by the first terminal according to the present information;
a transfer module 1502, configured to transfer the resource corresponding to the target object from the first account to the second account according to the first request, and send a transfer success indication to a product server;
the second receiving module 1501 is further configured to receive a deduction request sent by the product server, where the deduction request is used to request that the resource corresponding to the target object is transferred from the second account to a third account corresponding to the product server;
the transferring module 1502 is further configured to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the deduction request, and send a deduction success indication to the product server.
In an optional embodiment, the transferring module 1502 is further configured to transfer the resource corresponding to the target object from the first account to the third account according to the payment request,
the device further comprises: a sending unit, configured to send a payment success indication to the product server;
a second receiving module 1501, configured to receive a payment request sent by the product server, where the payment request is used to request that a resource corresponding to the target object is transferred from the third account to the second account;
the transfer module 1502 is further configured to transfer the resource corresponding to the target object from the third account to the second account according to the payment request.
In an optional embodiment, the second receiving module 1502 is further configured to receive a transfer call request sent by the product server, where the transfer call request is used to initiate a transfer process for transferring the resource corresponding to the target object from the first account to the second account;
the sending unit is also used for sending the transfer information corresponding to the transfer calling request to the first terminal;
the second receiving module 1501 is further configured to receive the transfer request sent by the first terminal.
In an optional embodiment, the second receiving module 1501 is further configured to receive an authority confirmation instruction sent by the second terminal, where the authority confirmation instruction is used to instruct the second terminal to grant, to the product server, a deduction authority to transfer the resource from the second account to a third account corresponding to the product server;
the device further comprises: and the storage unit is used for storing the withholding authority of the second terminal according to the authority confirmation instruction.
Fig. 16 is a block diagram of a product server according to an exemplary embodiment of the present application. As shown in fig. 16, the product server includes: a processor 1601, and a memory 1602.
The processor 1601 may be at least one of a single core processor, a multi-core processor, an embedded chip, and a processor with computing capabilities.
Memory 1602 stores executable instructions for processor 1601. Illustratively, the memory 1602 is a computer-readable storage medium, in which at least one instruction, at least one program, code set, or instruction set is stored, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor 1601 to implement the steps performed by the product server in any one of the object providing methods shown in fig. 1 to 6 b.
Fig. 17 is a block diagram of a structure of a payment server provided in an exemplary embodiment of the present application. As shown in fig. 17, the payment server includes: a processor 1701, and a memory 1702.
The processor 1701 may be at least one of a single core processor, a multi-core processor, an embedded chip, and a processor having computing capabilities.
The memory 1702 stores executable instructions for the processor 1701. Illustratively, the memory 1702 is a computer-readable storage medium having stored therein at least one instruction, at least one program, set of codes, or set of instructions, which is loaded and executed by the processor 1701 for carrying out the steps performed by the payment server in any one of the target object providing methods shown in fig. 1 to 6 b.
Optionally, the present application further provides a computer-readable storage medium, in which a computer-readable storage medium is stored, and the storage medium stores at least one instruction, at least one program, a code set, or a set of instructions, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by the processor to implement the steps executed by the product server in any one of the target object providing methods shown in fig. 1 to 6b, and optionally, the computer-readable storage medium includes a high-speed access memory and a non-volatile memory.
Optionally, the present application further provides a computer-readable storage medium, in which a computer-readable storage medium is stored, and the storage medium stores at least one instruction, at least one program, a code set, or a set of instructions, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by the processor to implement the steps performed by the payment server in any one of the target object providing methods shown in fig. 1 to 6b, and optionally, the computer-readable storage medium includes a high-speed access memory and a non-volatile memory.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (14)

1. A target object providing method, characterized in that the method comprises:
the method comprises the steps that a first terminal obtains presentation information of a target object, wherein the presentation information comprises: the target object is a resource corresponding to the target object, a first account and a second account, wherein the first account is a donor account, the second account is a donated account, the target object is an object requiring that a payment subject and a owning subject after payment succeeds are the same subject, and the first account and the second account belong to different subjects;
the first terminal sends a first request to a payment server according to the presentation information, wherein the first request is a payment request;
the payment server transfers the resource corresponding to the target object from the first account to a third account corresponding to a product server according to the payment request, and sends a payment success indication to the product server;
the product server sends a payment request to the payment server according to the payment success indication, wherein the payment request is used for requesting to transfer the resource corresponding to the target object from the third account to the second account;
the payment server transfers the resource corresponding to the target object from the third account to the second account according to the payment request, and sends a transfer success indication to the product server;
the product server sends a withholding request to the payment server according to the transfer success indication, wherein the withholding request is used for requesting to actively transfer the resource corresponding to the target object from the second account to the third account without operating the second account under the condition of obtaining the authorization of the second account;
the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, and sends a withholding success indication to the product server;
and the product server provides the target object to the second account according to the withholding success indication.
2. The method of claim 1, wherein the product server sending a payment request to the payment server based on the payment success indication comprises:
and the product server calls an enterprise payment interface to send a payment request to the payment server according to the payment success indication, wherein the enterprise payment interface is an interface provided by the payment server for the enterprise user to pay the individual user.
3. The method of claim 1, wherein the first request is a transfer request requesting transfer of the resource corresponding to the target object from the first account to the second account;
the first terminal sends a first request to a payment server according to the presentation information, and the first request comprises the following steps:
the first terminal sends a presentation request to the product server according to the presentation information;
the product server sends a transfer calling request to the payment server according to the presentation request, wherein the transfer calling request is used for requesting the payment server to initiate a transfer process of transferring the resource corresponding to the target object from the first account to the second account;
the payment server sends transfer information corresponding to the transfer calling request to the first terminal;
and the first terminal sends the transfer request to the payment server according to the transfer information.
4. The method of any one of claims 1 to 3, wherein before the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, the method further comprises:
the product server sends a deduction permission request to a second terminal, wherein the deduction permission request is used for requesting to acquire permission for transferring the resource from the second account to a third account corresponding to the product server;
the second terminal generates an authority confirmation instruction according to the withholding authority request and sends the authority confirmation instruction to the payment server;
and the payment server stores the deduction authority of the second terminal according to the authority confirmation instruction, wherein the deduction authority is used for indicating that the product server has the authority of deducting the resource from the second account to a third account corresponding to the product server.
5. A target object providing method, characterized in that the method comprises:
receiving a transfer success indication sent by a payment server, wherein the transfer success indication is an indication generated after the payment server transfers resources corresponding to a target object from a first account to a second account, the first account is a donor account, the second account is a donated account, the target object is an object requiring that a payment subject and a owning subject after payment success are the same subject, and the first account and the second account belong to different subjects;
sending a withholding request to the payment server according to the transfer success indication, wherein the withholding request is used for requesting to actively transfer the resource corresponding to the target object from the second account to a third account without operation of the second account under the condition of obtaining authorization of the second account;
receiving a deduction success indication sent by the payment server, wherein the deduction success indication is generated after the payment server transfers the resource corresponding to the target object from the second account to a third account corresponding to a product server according to the deduction request;
and providing the target object to the second account according to the withholding success indication.
6. A target object providing method, characterized in that the method comprises:
receiving a first request sent by a first terminal, wherein the first request is a payment request;
transferring the resource corresponding to the target object from a first account to a second account according to the first request, and sending a transfer success indication to a product server, wherein the first account is a donor account, the second account is a donated account, the target object is an object which requires that a payment subject and a owning subject after payment is successful are the same subject, and the first account and the second account belong to different subjects;
receiving a deduction replacing request sent by the product server, wherein the deduction replacing request is used for actively transferring the resource corresponding to the target object from the second account to a third account without operation of the second account under the condition that the authorization of the second account is obtained;
transferring the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, and sending a withholding success indication to the product server; the withholding success indication is used for instructing the product server to provide the target object to the second account.
7. A target object providing apparatus, characterized in that the apparatus comprises:
a first receiving module, configured to receive a transfer success indication sent by a payment server, where the transfer success indication is an indication generated after the payment server transfers a resource corresponding to the target object from a first account to a second account, the first account is a donor account, the second account is a donated account, the target object is an object that requires that a payment subject and a owning subject after payment succeeds are the same subject, and the first account and the second account belong to different subjects;
a sending module, configured to send a withholding request to the payment server according to the transfer success indication, where the withholding request is used to request that, when the authorization of the second account is obtained, a resource corresponding to the target object is actively transferred from the second account to a third account without operating the second account;
the first receiving module is further configured to receive a withholding success indication sent by the payment server, where the withholding success indication is an indication generated by the payment server after transferring the resource corresponding to the target object from the second account to a third account corresponding to a product server according to the withholding request;
a providing module configured to provide the target object to the second account according to the withholding success indication.
8. A target object providing apparatus, characterized in that the apparatus comprises:
the second receiving module is used for receiving a first request sent by a first terminal, and the first request is a payment request;
the transfer module is used for transferring the resource corresponding to the target object from a first account to a second account according to the first request, and sending a transfer success indication to a product server, wherein the first account is a donor account, the second account is a donor account, the target object is an object which requires that a payment subject and a owning subject after payment success are the same subject, and the first account and the second account belong to different subjects;
the second receiving module is further configured to receive a deduction request sent by the product server, where the deduction request is used to request that, under the condition of obtaining authorization of the second account, resources corresponding to the target object are actively transferred from the second account to a third account without operation of the second account;
the transfer module is further configured to transfer the resource corresponding to the target object from the second account to a third account corresponding to the product server according to the withholding request, and send a withholding success indication to the product server.
9. A product server, characterized in that the product server comprises a processor and a memory, in which at least one program is stored, which is loaded and executed by the processor to implement the target object providing method according to claim 5.
10. A payment server, characterized in that the payment server comprises a processor and a memory, wherein at least one program is stored in the memory, and the at least one program is loaded and executed by the processor to implement the target object providing method according to claim 6.
11. A computer-readable storage medium, wherein at least one program is stored in the storage medium, and the at least one program is loaded and executed by a processor to implement the target object providing method according to claim 5.
12. A computer-readable storage medium, wherein at least one program is stored in the storage medium, and the at least one program is loaded and executed by a processor to implement the target object providing method according to claim 6.
13. A target object providing system, characterized in that the target object providing system comprises: a payment server for implementing the target object providing method of claim 5, and a product server for implementing the target object providing method of claim 6.
14. A target object providing system, characterized in that the target object providing system comprises: a first terminal, a product server, a payment server and a second terminal, wherein the product server is used for realizing the target object providing method of claim 5, and the payment server is used for realizing the target object providing method of claim 6.
CN201710729392.9A 2017-08-23 2017-08-23 Target object providing method, device and system Active CN109426955B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710729392.9A CN109426955B (en) 2017-08-23 2017-08-23 Target object providing method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710729392.9A CN109426955B (en) 2017-08-23 2017-08-23 Target object providing method, device and system

Publications (2)

Publication Number Publication Date
CN109426955A CN109426955A (en) 2019-03-05
CN109426955B true CN109426955B (en) 2023-01-17

Family

ID=65498670

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710729392.9A Active CN109426955B (en) 2017-08-23 2017-08-23 Target object providing method, device and system

Country Status (1)

Country Link
CN (1) CN109426955B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109978522A (en) * 2019-04-04 2019-07-05 睿驰达新能源汽车科技(北京)有限公司 A kind of method, apparatus and equipment of order payment
CN110517156B (en) * 2019-08-26 2023-05-19 创新先进技术有限公司 Man-machine interaction method, system and equipment for guarantee service
CN111709733B (en) * 2020-06-03 2022-04-29 支付宝(杭州)信息技术有限公司 Resource transfer method, device and equipment
CN112232810B (en) * 2020-09-24 2024-02-23 中国银联股份有限公司 Resource processing method, server, device, equipment, system and medium
CN112232800A (en) * 2020-10-14 2021-01-15 周向前 Consumption data processing method and device, electronic equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143462A (en) * 2010-06-23 2011-08-03 华为技术有限公司 Mobile data service platform, system and method for providing value-added service
CN104618101A (en) * 2013-12-27 2015-05-13 腾讯科技(深圳)有限公司 Data processing method, intermediate server and data processing system
CN105827497A (en) * 2015-01-05 2016-08-03 阿里巴巴集团控股有限公司 Network resource processing method, network resource processing device, and instant messaging system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8762272B1 (en) * 2012-12-27 2014-06-24 Google Inc. Management of emails containing payments

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143462A (en) * 2010-06-23 2011-08-03 华为技术有限公司 Mobile data service platform, system and method for providing value-added service
CN104618101A (en) * 2013-12-27 2015-05-13 腾讯科技(深圳)有限公司 Data processing method, intermediate server and data processing system
CN105827497A (en) * 2015-01-05 2016-08-03 阿里巴巴集团控股有限公司 Network resource processing method, network resource processing device, and instant messaging system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
浅析个人所得赠送礼品的税收问题;刘嘉等;《经济师》;20140805(第8期);第153-154页 *

Also Published As

Publication number Publication date
CN109426955A (en) 2019-03-05

Similar Documents

Publication Publication Date Title
US20220270078A1 (en) Method and system for reloading prepaid card
AU2019200882B2 (en) System and method of registering stored-value cards into electronic wallets
US20220253816A1 (en) Systems and methods for securely generating digital gift cards
US20210279721A1 (en) System and method for using intelligent codes to add a stored-value card to an electronic wallet
CN109426955B (en) Target object providing method, device and system
US20180053157A1 (en) Systems and methods for consumer modifiable payment card transactions
TWI640937B (en) Online payment method and equipment
US11475436B2 (en) System and method for providing a security code
US8589297B2 (en) Prepaid value account with reversion to purchaser systems and methods
CA2892013C (en) System and method for using intelligent codes in conjunction with stored-value cards
US20070266131A1 (en) Obtaining and Using Primary Access Numbers Utilizing a Mobile Wireless Device
CA2897145C (en) System and method for providing a security code
US20080162348A1 (en) Electronic-Purse Transaction Method and System
TWI646478B (en) Remittance system and method
CA2912066C (en) System and method of reloading prepaid cards
KR20190048153A (en) Method providing escrow service for remittance payment and server thereof
KR102277204B1 (en) Reformint service platform and Reformint service method
KR20040099004A (en) Pg system not passing businessman between customer and freelancer by performing direct payment
WO2011068912A2 (en) System and method for remotely conducting and managing money transfers
CA2546433A1 (en) Obtaining and using primary access numbers utilizing a mobile wireless device

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