WO2019134543A1

WO2019134543A1 - Method and apparatus for information transmission and electronic device

Info

Publication number: WO2019134543A1
Application number: PCT/CN2018/123035
Authority: WO
Inventors: 彭玉军
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2018-01-02
Filing date: 2018-12-24
Publication date: 2019-07-11
Also published as: CN108269135B; CN108269135A; TW201931257A; CN113850634A

Abstract

A method and apparatus for information transmission and an electronic device. The method comprises: acquiring invoicing information when a payer client is paying (210), wherein the invoicing information is used for generating a paper or electronic invoice; generating by the payer client payment information including the invoicing information; acquiring by a payee client the payment information provided by the payer client, and parsing by the payee client the invoicing information included in the payment information (230); calling by the payee client a payment interface of a payment platform to complete collection; and generating by an invoicing system a paper or electronic invoice including the invoicing information when successful collection information returned by the payment platform is received (250).

Description

Method and device for transmitting information and electronic device

Technical field

The embodiments of the present disclosure relate to the field of Internet technologies, and in particular, to a method and device for transmitting information and an electronic device.

Background technique

In daily life, customers can invoice at the merchant's consumption. Typically, customers need to provide billing information to the merchant (eg, including name, type, tax ID, unit address, phone number, etc.). In general, the customer can present the billing information by way of dictation, writing, and the like.

There is a need to provide a more efficient solution for information transfer.

Summary of the invention

A method, device and electronic device for transmitting information provided by embodiments of the present specification:

According to a first aspect of the embodiments of the present specification, a method for information transmission is provided, the method comprising:

In the case that the payer client makes a payment, the payer client obtains billing information; wherein the billing information is used to generate a paper or electronic invoice;

The payer client generates payment information including the billing information;

The payee client obtains the payment information provided by the payer client, and parses out the billing information in the payment information;

The payee client invokes a payment interface of the payment platform to complete the payment;

When the payee client receives the payment platform to return the payment successfully, the billing system generates a paper or electronic invoice of the billing information.

According to a second aspect of the embodiments of the present specification, a method for information transmission is provided, the method comprising:

Obtaining billing information in the case of making a payment; wherein the billing information is used to generate a paper or electronic invoice;

A payment information containing the billing information is generated.

According to a third aspect of the embodiments of the present specification, a method for information transmission is provided, the method comprising:

Obtaining payment information provided by the payer client, and parsing the billing information in the payment information;

Calling the payment interface of the payment platform to complete the payment;

Upon receipt of the payment platform returning the payment success, the billing system generates a paper or electronic invoice for the billing information.

According to a fourth aspect of the embodiments of the present specification, a method for information transmission is provided, the method comprising:

The paying party client obtains the payment information, and parses out the payee account in the payment information;

The payer client obtains billing information; wherein the billing information is used to generate a paper or electronic invoice;

The payer client invokes a payment interface of the payment platform to complete payment to the payee account and send the billing information to the payment platform;

Receiving, by the payment platform, the billing information, in the case that the payee account is successfully collected, sending a payment success notification to the payee client, where the notification carries the billing information;

The payee client obtains the billing information carried by the notification when receiving the payment success notification by the payment platform, so that the billing system generates a paper or electronic invoice of the billing information.

According to a fifth aspect of the embodiments of the present specification, a method for information transmission is provided, the method comprising:

The payee client collects biometric information of the payer;

The payee client initiates a payment request including the biometric information to a payment platform;

And the payment platform acquires default billing information of the payer account when the payee account corresponding to the biometric information is identified;

And the payment platform returns a payment success notification to the payee client when the payment is completed; the notification carries the billing information;

According to a sixth aspect of the embodiments of the present specification, an apparatus for information transmission is provided, the apparatus comprising:

Obtaining unit, in case of making payment, obtaining billing information; wherein the billing information is used to generate a paper or electronic invoice;

Generating a unit to generate payment information including the billing information.

According to a seventh aspect of the embodiments of the present specification, an apparatus for information transmission is provided, the apparatus comprising:

Obtaining a unit, obtaining payment information provided by the payer client, and parsing the billing information in the payment information;

Calling the unit, calling the payment interface of the payment platform to complete the payment;

The generating unit generates a paper or electronic invoice of the billing information for the billing system upon receiving the payment platform to return the payment successfully.

According to an eighth aspect of the embodiments of the present disclosure, an electronic device is provided, including:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

A payment information containing the billing information is generated.

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

Calling the payment interface of the payment platform to complete the payment;

In the embodiment of the present specification, the billing information of the payer is transmitted during the payment process by the payer; after the payee successfully collects the payment from the payer, the billing information may be provided according to the transmitted billing information. The billing system generates a paper or electronic invoice for the billing information. In this way, the billing efficiency of the payee can be improved; and the billing error caused by human factors can be avoided.

DRAWINGS

1 is a conceptual diagram of a system architecture for implementing information transmission according to an embodiment of the present disclosure;

2 is a flowchart of a method for information transmission provided by an embodiment of the present specification;

3 is a schematic diagram showing display billing information provided by an embodiment of the present specification;

4 is a schematic diagram of invoice details provided by an embodiment of the present specification;

5 is a flowchart corresponding to the method of FIG. 2 for information transmission by a payer client as an execution subject;

6 is a flowchart corresponding to the method of FIG. 2 for transmitting information by the payee client as an execution subject;

FIG. 7 is a flowchart of a method for transmitting information according to an embodiment of the present disclosure;

FIG. 8a is a schematic diagram of a payment interface provided by an embodiment of the present specification; FIG.

FIG. 8b is a pre-configured invoice information of a payer provided by an embodiment of the present specification; FIG.

9 is a flowchart of a method for information transmission provided by an embodiment of the present disclosure;

FIG. 10 is a schematic block diagram of an apparatus for information transmission according to an embodiment of the present disclosure; FIG.

FIG. 11 is a schematic block diagram of an apparatus for information transmission according to an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Instead, they are merely examples of devices and methods consistent with aspects of the present specification as detailed in the appended claims.

The terminology used in the description is for the purpose of describing particular embodiments, and is not intended to The singular forms "a", "the" and "the" It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information without departing from the scope of the present description. Similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to a determination."

As mentioned earlier, customers can invoice at the merchant's consumption. Typically, customers need to provide billing information to the merchant (eg, including name, type, tax ID, unit address, phone number, etc.). In general, the customer can present the billing information by means of dictation, writing, or billing information on the mobile phone, but the merchant manually inputs the billing system to generate an invoice. The whole process is not only inefficient, but also prone to errors. For example, a customer may have mistyped, miswritten billing information, or the merchant entered the wrong billing information, which will result in the wrong invoice being generated.

This specification may relate to one or more systems. An exemplary system architecture concept diagram that can be applied in this specification is shown below with reference to FIG. The system architecture concept map can include a payee client 11, a payee client 12, and a payment platform 13.

The payer client 11 may refer to a client used by a payer (such as a customer, a paying user). The client may refer to a terminal on which a payment application is installed. For example, a smartphone with Alipay installed. In some scenarios, the terminal is not necessarily the paying party's own terminal, and may also be a self-service terminal provided by the merchant, and the paying party may log in to the payment account on the self-service terminal (for example, by using face recognition to log in to the account) to make payment. .

The payee client 12 may refer to a client used by a payee (eg, a merchant, a payee). Similarly, the client can refer to a terminal installed with a payment application. For example, a cashier device or a smartphone with Alipay is installed in the store. The payee client 12 can also be associated with a billing system 121. The billing system 121 can generate an electronic invoice or print out a paper invoice based on the billing information received by the payee client 12.

The payment platform 13 may refer to a server, a server cluster, or a cloud platform built on a server cluster corresponding to the payment application in the payer client 11 and the payee client 12. The payment platform 13 provides an interface for making payment (payment and payment) externally. The accounts of the respective users are usually managed in the payment platform 13.

For example, after the user makes a purchase at the store, the payer (user) client 11 can pay the payee (the merchant) the purchase amount through the payment platform 13; and the payer client 11 can directly or indirectly contact the payee client. 12 provides billing information for invoicing; after receiving the purchase amount paid by the payer, the payment and payment client 12 generates an electronic invoice or prints a paper invoice according to the billing information for the billing system 121.

The following describes an embodiment of a method for implementing information transmission according to the example shown in FIG. 2. As shown in FIG. 2, the method may include the following steps:

Step 210: In the case that the payer client makes a payment, the payer client obtains billing information; wherein the billing information is used to generate a paper or electronic invoice.

In this embodiment, the paying party client obtains the billing information, which may be that the paying party client can directly obtain the default billing information. The default billing information may include: the user may preset a default billing information; or the billing information used most recently; or the billing information with the most history usage.

In practical applications, the default billing information is usually not used directly without user selection; therefore, it is necessary to provide a scheme for the user to select billing information. Specifically, the step 210 may include:

In the case where the payer client makes a payment, the payer client displays the pre-configured invoice information of the payer;

Get the billing information selected by the payer.

In this embodiment, the number of invoice information pre-configured by the payer may be multiple, such as 1, 2, 3, and the like. As shown in the schematic diagram of the billing information shown in FIG. 3, when the payer makes a payment to the payee (merchant), the payer client can display the pre-configured invoice information 311, and the payer can select one of the invoice information, thereby The payer client is made to use the invoice information selected by the payer as the invoice information to be delivered from the plurality of invoice information. The invoice information selected by the payer can be marked, such as the check icon 312 in FIG. 3, so that the user can know which invoice information is currently selected. In FIG. 3, the payer can also configure a new invoice information by adding a button 313. The invoice information shown in FIG. 3 can be a brief message, and the payer can view the specific invoice information via the details button 314. As shown in Figure 4, the invoice details diagram, in general, detailed invoice information can include billing header, tax number, account bank, bank account number, registered address, contact number, and so on. Of course, the specific content of different regions and different countries may be slightly different, and we will not repeat them here. The payer can also modify the invoice content in the invoice details interface, such as by the edit button 411 in FIG.

In practice, not all scenarios require invoicing, and not all payers will invoice. Therefore, it is sometimes not necessary to obtain billing information every time a payment is made. To this end, in a specific embodiment, the step 210 may include:

In the case of payment by the payer client, generate payment information that does not include billing information;

In the case where the condition for obtaining the billing information is satisfied, the payer client acquires the billing information.

In this embodiment, the payment information generated by the payer client for the first time does not include the billing information, which is the same as the traditional payment information; and the second generated payment information after the payment party client obtains the billing information includes the billing information. of.

The condition for satisfying the execution of obtaining the billing information may be preset; for example, for the mobile terminal, a button for obtaining the billing information may be set in the page for making payment, and when the payer clicks the button, the condition is satisfied. Conditions to get billing information. If the payer does not need to invoice, it is not necessary to click the button to directly display the generated payment information that does not include the billing information to the payee.

For another example, for a terminal that provides voice control, a voice control command for obtaining billing information (such as “I want to invoice”) may be preset, and when the payer is detected to speak the voice control command, the condition is met. Thereby obtaining the billing information. If the payer does not need to invoice, the generated payment information that does not include the billing information can be broadcast directly to the payee.

Step 220: The payer client generates payment information including the billing information.

In this embodiment, after obtaining the billing information, the payer client may actively generate payment information including the billing information. That is to say, the payment information includes the conventional payment party identification, for example, and the billing information.

The payment information may include a payment graphic code or a payment sound wave. The payment graphic code may include a payment two-dimensional code, a payment barcode, and the like.

Taking the payment QR code as an example, after the user opens the payment application and clicks the QR code to pay, the payment QR code is directly generated in the prior art. In this embodiment, after the user opens the payment application and clicks the QR code to pay, the user needs to obtain the billing information first, and then generate a payment QR code including the billing information. That is to say, the payment two-dimensional code generated in the prior art does not include billing information, and the payment two-dimensional code generated in this embodiment includes billing information.

Similarly, taking the payment sound wave as an example, after the user opens the payment application and clicks on the sonic payment, the prior art directly generates a sound wave for payment. In this embodiment, after the user opens the payment application and clicks the QR code to pay, the user needs to obtain the billing information first, and then generate a sound wave for payment including the billing information. That is to say, the payment sound wave generated in the prior art does not include the billing information, and the payment sound wave generated in the embodiment includes the billing information.

Step 230: The payee client obtains the payment information provided by the payer client, and parses out the billing information in the payment information.

As described above, in an implementation manner, the payment information includes a payment graphic code, and the payee client obtains payment information provided by the paying party client, and specifically includes:

The payee client scans the payment graphic code provided by the payer client.

Taking the payment QR code as an example, the payer can display the payment QR code generated in the mobile phone to the payee, and the payee can start the camera through the payee client to scan the code. After the scan code is successful, the payee can The client can parse the billing information contained in the payment QR code.

In another implementation, the payment information includes a payment sound wave, and the payee client obtains payment information provided by the paying party client, and specifically includes:

The payee client listens for payment sound waves broadcast by the payer client.

Taking the payment sound wave as an example, the payer can broadcast the generated payment sound wave to the payee through the payer client, and the payee can start the sound wave module through the payee client to listen, and after receiving the payment sound wave, the payee The client can parse out the billing information contained in the payment sound wave.

Step 240: The payee client invokes a payment interface of the payment platform to complete the payment.

The payment platform typically provides a payment interface for making payments externally. Specifically, the payment information generated by the payer client generally includes a payer account identifier, and when the payee client parses the payment information, the payer account identifier may also be identified; further, the payee client invokes the payment. The interface initiates a payment request, and the payment request may include payment information such as a payer account identifier, a payee account identifier, and a payment amount. The payment platform injects the funds for withdrawing the payment amount from the payer's account into the payee's account according to the payment information, thus completing the payment.

In general, after the payment platform completes the payment, the payment platform may separately send a notification of the payment success to the payer client and the payee client.

Step 250: The billing system generates a paper or electronic invoice of the billing information when the payee client receives the payment platform to return the payment successfully.

The payee client may generate a paper or electronic invoice of the billing information for the billing system upon receiving the payment platform to return the payment successfully. For the electronic invoice, the payee client may also send the electronic invoice to the payer client directly after the invoicing system generates the electronic invoice; or send it to the payment platform, and indirectly to the payer client via the payment platform.

An embodiment of the method in which the present application is based on the payer client is described below with reference to FIG. 5, which may correspond to FIG. 2:

Step 510: Acquire billing information in the case of making a payment; wherein the billing information is used to generate a paper or electronic invoice;

Step 520: Generate payment information including the billing information. The payment information is used by the payee client to parse out the billing information, and in the case that the payee client receives the payment platform to return the payment successfully, the billing system generates the paper of the billing information or Electronic invoice.

Optionally, the payment information includes a payment graphic code or a payment sound wave.

Optionally, the step 510 specifically includes:

In the case of making a payment, generating payment information that does not include billing information;

The billing information is acquired in the case where the condition for obtaining the billing information is satisfied.

Optionally, the step 510 specifically includes:

In the case of payment, the pre-configured invoice information of the payer is displayed;

Get the billing information selected by the payer.

Optionally, the obtaining the billing information specifically includes:

Get the default billing information;

The default billing information includes: billing information used last time; or billing information with the most history usage; or default billing information set by the payer.

The method embodiment of the present application with the payee client as the main body is described below with reference to FIG. 6 , which may correspond to FIG. 2 :

Step 610: Obtain payment information provided by the payer client, and parse out the billing information in the payment information.

Step 620: Invoking a payment interface of the payment platform to complete the payment;

Step 630: In case the receiving payment platform returns the payment success, the billing system generates a paper or electronic invoice of the billing information.

Optionally, the payment information includes a payment graphic code, and the obtaining payment information provided by the payment party client includes:

Scan the payment graphic code provided by the payer client;

or,

The payment information includes a payment sound wave, and the payment information provided by the payment party client includes:

Monitor the payment sound waves broadcast by the payer client.

An embodiment of a method for implementing information transmission in the present specification may be introduced in the following with reference to the example shown in FIG. 7. As shown in FIG. 7, the method may include the following steps:

Step 710: The payer client obtains the payment information provided by the payee, and parses out the payee account in the payment information.

In this embodiment, the payment information provided by the payee client may be determined after the payee client negotiates with the payment platform. For example, the payee client can invoke the payment platform receiving link interface, and the payment platform can return the payment link; the payee client generates the payment information according to the returned payment link.

The payment information may include a receipt graphic code, and the paying party client may scan the payment party's receipt graphic code when the payment is required to be paid to the payee; thereby, the payee account in the received graphic code may be parsed.

The payment information may further include a receiving sound wave, and the paying party client may turn on the sound wave module when the payment is required to be paid to the paying party, and after receiving the collected sound wave broadcasted by the paying party, the receiving sound wave may be parsed Party account.

Step 720: In the case of jumping to the payment interface, the payer client obtains billing information; wherein the billing information is used to generate a paper or electronic invoice.

As shown in the embodiment of FIG. 2, the paying party client obtains the billing information, which specifically includes:

The payer client obtains default billing information;

In another mode, the payer client obtains billing information, which specifically includes:

The payer client displays pre-configured invoice information of the payer;

The payer client obtains billing information selected by the payer.

As shown in Figure 8a, the payer client can jump to the payment interface, and the payer can fill in the payment amount on the payment interface. The payer can choose whether or not an invoice is required. If the payer chooses to require an invoice, the payer's pre-configured invoice information can be displayed as shown in Figure 8b. The payer can finally pay by clicking Confirm Payment.

For the foregoing implementation manner, reference may be made to the specific description in the foregoing embodiment of FIG. 2, and details are not described herein again.

Step 730: The payer client invokes a payment interface of the payment platform to complete payment to the payee account and send the billing information to the payment platform.

Different from the embodiment shown in FIG. 2, the embodiment of FIG. 2 is that the payee client initiates a payment request to the payment platform; and in this embodiment, the payer client initiates a payment request to the payment platform, and additionally adds The payment platform sends the billing information. The payment request may include a payer account identifier, a payee account identifier, and a payment amount; the billing information may be included in the payment request or may not be included in the payment request; that is, may be synchronously or asynchronously sent to the payment request. Payment platform. The payment platform injects the funds for withdrawing the payment amount from the payer account according to the payment request into the payee account, thus completing the payment. In general, after the payment platform completes the payment, the payment platform may separately send a payment success notification to the payer client and the payee client.

Step 740: The payment platform receives the billing information, and if the payee account receives the payment successfully, sends a payment success notification to the payee client, where the notification carries the billing information.

When the payment platform completes the payment, that is, if the payment of the payee account is successful, the payment platform may send a payment success notification to the payee client, and the notification carries the invoicing information.

Step 750: The receiving party client obtains the billing information carried by the notification when the payment platform sends the payment success notification, so that the billing system generates the paper or electronic invoice of the billing information. .

After receiving the payment success notification from the payment platform, the payee client may acquire the billing information carried by the notification, so that the billing system generates a paper or electronic invoice of the billing information. For the electronic invoice, the payee client may also send the electronic invoice to the payer client directly after the invoicing system generates the electronic invoice; or send it to the payment platform, and indirectly to the payer client via the payment platform.

An embodiment of a method for implementing information transmission in the present specification may be introduced in the following with reference to the example shown in FIG. 9. As shown in FIG. 9, the method may include the following steps:

Step 810: The payee client collects biometric information of the payer;

The biometric information includes at least one of a fingerprint, a palm print, an iris, an eye, a face, a sound wave, and a brain wave.

Step 820: The payee client initiates a payment request including the biometric information to a payment platform.

Step 830: The payment platform acquires default billing information of the payer account in the case that the payer account corresponding to the biometric information is identified.

Step 840: The payment platform returns a payment success notification to the payee client when the payment is completed; the notification carries the billing information;

Step 850: The receiving party client obtains the billing information carried by the notification when the payment platform sends the payment success notification, so that the billing system generates the paper or electronic invoice of the billing information. .

In the embodiment of the present specification, the paying party may automatically complete the payment and automatically transmit the billing information to the payee client after the payment platform identifies the payer account corresponding to the biometric information only by providing the biometric information. The billing system generates a paper or electronic invoice for the billing information. Compared with the foregoing embodiment, the paying party of the embodiment does not need to carry the payer client, and the user experience is better and the payment efficiency is higher.

Corresponding to the aforementioned method embodiment of information transmission, the present specification also provides an embodiment of an apparatus for information transmission. The device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking the software implementation as an example, as a logical means, the processor of the device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory. At a hardware level, a hardware structure of a device in which the device for information transmission of the present specification is located may include a processor, a network interface, a memory, and a non-volatile memory. In the embodiment, the device in which the device is located is generally transmitted according to the information. The actual function can also include other hardware, which will not be described here.

FIG. 10 is a block diagram of an apparatus for information transmission according to an embodiment of the present disclosure. The apparatus corresponds to the embodiment shown in FIG. 5, and the apparatus includes:

The obtaining unit 910, in the case of making a payment, acquiring billing information; wherein the billing information is used to generate a paper or electronic invoice;

The generating unit 920 generates payment information including the billing information.

In an alternative embodiment:

The obtaining unit 910 specifically includes:

In an alternative embodiment:

The payment information includes a payment graphic code or a payment sound wave.

In an alternative embodiment:

The obtaining unit 910 specifically includes:

Get the billing information selected by the payer.

In an alternative embodiment:

The obtaining the billing information specifically includes:

Get the default billing information;

FIG. 11 is a block diagram of an apparatus for information transmission according to an embodiment of the present disclosure. The apparatus corresponds to the embodiment shown in FIG. 6. The apparatus includes:

The obtaining unit 1010 is configured to obtain payment information provided by the paying party client, and parse out the billing information in the payment information;

Invoking unit 1020, invoking a payment interface of the payment platform to complete the payment;

The generating unit 1030 generates a paper or electronic invoice of the billing information for the billing system upon receiving the payment platform to return the payment successfully.

In an alternative embodiment:

The payment information includes a payment graphic code, and the payment information provided by the payment party client includes:

Scan the payment graphic code provided by the payer client;

or,

Monitor the payment sound waves broadcast by the payer client.

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control. A combination of a tablet, a tablet, a wearable device, or any of these devices.

The implementation process of the function and the function of each unit in the foregoing device is specifically described in the implementation process of the corresponding steps in the foregoing method, and details are not described herein again.

For the device embodiment, since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment. The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present specification. Those of ordinary skill in the art can understand and implement without any creative effort.

Figure 10 above shows the internal functional modules and structural diagrams of the device for information transmission. The substantial execution body of the device may be an electronic device, including:

processor;

a memory for storing processor executable instructions;

A payment information containing the billing information is generated.

Figure 11 above illustrates the internal functional modules and structure of the device for information transmission. The substantial execution body of the device may be an electronic device, including:

processor;

a memory for storing processor executable instructions;

Calling the payment interface of the payment platform to complete the payment;

In the above embodiment of the electronic device, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, CPU for short), or other general-purpose processor, digital signal processor (English: Digital Signal Processor) , referred to as: DSP), ASIC (English: Application Specific Integrated Circuit, referred to as: ASIC). The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and the foregoing memory may be a read-only memory (English: read-only memory, abbreviation: ROM), a random access memory (English) :random access memory (abbreviation: RAM), flash memory, hard disk or solid state disk. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for an electronic device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

Other embodiments of the present specification will be readily apparent to those skilled in the <RTIgt; The description is intended to cover any variations, uses, or adaptations of the present specification, which are in accordance with the general principles of the specification and include common general knowledge or common technical means in the art that are not disclosed in this specification. . The specification and examples are to be regarded as illustrative only,

It is to be understood that the invention is not limited to the details of the details and The scope of the present description is limited only by the accompanying claims.

Claims

A method of information transmission, the method comprising:

In the case that the payer client makes a payment, the payer client obtains billing information; wherein the billing information is used to generate a paper or electronic invoice;

The payer client generates payment information including the billing information;

The payee client obtains the payment information provided by the payer client, and parses out the billing information in the payment information;

The payee client invokes a payment interface of the payment platform to complete the payment;

When the payee client receives the payment platform to return the payment successfully, the billing system generates a paper or electronic invoice of the billing information.
A method of information transmission, the method comprising:

Obtaining billing information in the case of making a payment; wherein the billing information is used to generate a paper or electronic invoice;

A payment information containing the billing information is generated.
The method of claim 2, the payment information comprising a payment graphic code or a payment sound wave.
The method of claim 2, wherein the obtaining the billing information in the case of performing the payment comprises:

In the case of making a payment, generating payment information that does not include billing information;

The billing information is acquired in the case where the condition for obtaining the billing information is satisfied.
The method of claim 2, wherein the obtaining the billing information in the case of performing the payment comprises:

In the case of payment, the pre-configured invoice information of the payer is displayed;

Get the billing information selected by the payer.
The method of claim 2, wherein the obtaining the billing information comprises:

Get the default billing information;

The default billing information includes: billing information used last time; or billing information with the most history usage; or default billing information set by the payer.
A method of information transmission, the method comprising:

Obtaining payment information provided by the payer client, and parsing the billing information in the payment information;

Calling the payment interface of the payment platform to complete the payment;

Upon receipt of the payment platform returning the payment success, the billing system generates a paper or electronic invoice for the billing information.
The method of claim 7, wherein the payment information comprises a payment graphic code, and the obtaining payment information provided by the payment party client comprises:

Scan the payment graphic code provided by the payer client;

or,

The payment information includes a payment sound wave, and the payment information provided by the payment party client includes:

Monitor the payment sound waves broadcast by the payer client.
A method of information transmission, the method comprising:

The paying party client obtains the payment information, and parses out the payee account in the payment information;

The payer client obtains billing information; wherein the billing information is used to generate a paper or electronic invoice;

The payer client invokes a payment interface of the payment platform to complete payment to the payee account and send the billing information to the payment platform;

Receiving, by the payment platform, the billing information, in the case that the payee account is successfully collected, sending a payment success notification to the payee client, where the notification carries the billing information;

The payee client obtains the billing information carried by the notification when receiving the payment success notification by the payment platform, so that the billing system generates a paper or electronic invoice of the billing information.
The method of claim 9 wherein said payment information comprises a payment graphic code or a payment sound wave.
The method according to claim 9, wherein the payment party client obtains the billing information, which specifically includes:

The payer client obtains default billing information;

The default billing information includes: billing information used last time; or billing information with the most history usage; or default billing information set by the payer.
The method according to claim 9, wherein the payment party client obtains the billing information, which specifically includes:

The payer client displays pre-configured invoice information of the payer;

The payer client obtains billing information selected by the payer.
The method according to claim 9, wherein the payment party client obtains the billing information, which specifically includes:

In the case where the condition for obtaining the billing information is satisfied, the payer client acquires the billing information.
A method of information transmission, the method comprising:

The payee client collects biometric information of the payer;

The payee client initiates a payment request including the biometric information to a payment platform;

And the payment platform acquires default billing information of the payer account when the payee account corresponding to the biometric information is identified;

And the payment platform returns a payment success notification to the payee client when the payment is completed; the notification carries the billing information;

The payee client obtains the billing information carried by the notification when receiving the payment success notification by the payment platform, so that the billing system generates a paper or electronic invoice of the billing information.
The method according to claim 14, wherein the biometric information comprises at least one of a fingerprint, a palm print, an iris, an eye, a face, a sound wave, and a brain wave.
The method according to claim 14, wherein the default billing information comprises: billing information used last time; or billing information having the most history usage; or default billing information set by the payer.
An apparatus for transmitting information, the apparatus comprising:

Obtaining unit, in case of making payment, obtaining billing information; wherein the billing information is used to generate a paper or electronic invoice;

Generating a unit to generate payment information including the billing information.
An apparatus for transmitting information, the apparatus comprising:

Obtaining a unit, obtaining payment information provided by the payer client, and parsing the billing information in the payment information;

Calling the unit, calling the payment interface of the payment platform to complete the payment;

The generating unit generates a paper or electronic invoice of the billing information for the billing system upon receiving the payment platform to return the payment successfully.
An electronic device comprising:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

Obtaining billing information in the case of making a payment; wherein the billing information is used to generate a paper or electronic invoice;

A payment information containing the billing information is generated.
An electronic device comprising:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

Obtaining payment information provided by the payer client, and parsing the billing information in the payment information;

Calling the payment interface of the payment platform to complete the payment;

Upon receipt of the payment platform returning the payment success, the billing system generates a paper or electronic invoice for the billing information.