TW201931257A - Method and apparatus for information transmission and electronic device - Google Patents

Abstract

A method and apparatus for information transmission and an electronic device. The method comprises: acquiring invoicing information when a payer client is paying, 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; 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.

Description

Information transmission method and device and electronic device

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.

In daily life, customers can invoice at the merchant's consumption. Typically, customers need to provide billing information (including name, type, tax ID, unit address, phone number, etc.) to the merchant. 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 means of information transfer.

A method, device and electronic device for information transmission 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 payment party user makes a payment, the paying party user obtains the billing information; wherein the billing information is used to generate a paper or an electronic invoice;
The payer client generates payment information including the billing information;
The payee user obtains the payment information provided by the payer user, and parses out the billing information in the payment information;
The payee user end invokes a payment interface of the payment platform to complete the payment;
And in the case that the payee user end receives the payment platform to return the payment successfully, the billing system generates the 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;
Generate payment information including the billing information.
According to a third aspect of the embodiments of the present specification, a method for information transmission is provided, and the method includes:
Obtaining the payment information provided by the payment party user, and parsing the invoicing information in the payment information;
Invoking 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 user obtains the payment information, and parses out the payee account in the payment information;
The paying party user obtains billing information; wherein the billing information is used to generate a paper or an electronic invoice;
The payer user invokes a payment interface of the payment platform to complete payment to the payee account, and sends the billing information to the payment platform;
Receiving, by the payment platform, the billing information, and sending a payment success notification to the payee user in the case that the payee account is successfully received, the notification carrying the billing information;
The receiving party user acquires the billing information carried by the notification when receiving the payment success notification by the payment platform, so that the billing system generates the 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, and the method includes:
The payee user collects biometric information of the payer;
Receiving, by the payee user, a payment request including the biometric information to a payment platform;
And the payment platform acquires the billing information preset by the payer account in the case that the payer account corresponding to the biometric information is identified;
And the payment platform returns a payment success notification to the payee user end when the payment is completed; the notification carries the billing information;
The receiving party user acquires the billing information carried by the notification when receiving the payment success notification by the payment platform, so that the billing system generates the paper or electronic invoice of 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 a unit, in the case of making a payment, obtaining billing information; wherein the billing information is used to generate a paper or an 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 paying party user, and parsing out 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, in case the receiving payment platform returns the payment success, the billing system generates the paper or electronic invoice of the billing information.
According to an eighth aspect of the embodiments of the present specification, an electronic device is provided, including:
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;
Generate payment information including the billing information.
According to an eighth aspect of the embodiments of the present specification, an electronic device is provided, including:
processor;
a memory for storing processor executable instructions;
Wherein the processor is configured to:
Obtaining the payment information provided by the payment party user, and parsing the invoicing information in the payment information;
Invoking 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.
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.

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the drawings. When the following description refers to the drawings, the same numerals in the different figures represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of devices and methods consistent with aspects of the 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 specification. 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 (including name, type, tax ID, unit address, phone number, etc.) to the merchant. In general, the customer can present the billing information by means of dictation, writing or invoicing 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 be mistaken, misinformed, or the merchant enters the wrong billing information, which will result in the wrong invoice.
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 may include a payer 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 installed with a payment application. For example, a smart phone 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 (such as a merchant, a payee). Similarly, the client may refer to a terminal installed with a payment application. For example, a cashier device or a smart phone 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 a paper invoice based on the billing information received by the payee user terminal 12.
The payment platform 13 may refer to a server, a server cluster, or a cloud platform built based on a server cluster in the payer client 11 and the payee client 12 . The payment platform 13 provides an interface for making payment (payment and payment) externally. Accounts of individual users are typically 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 payment party user makes a payment, the paying party user obtains the billing information; wherein the billing information is used to generate a paper or an electronic invoice.
In this embodiment, the paying party user obtains the billing information, which may be that the paying party user can directly obtain the preset billing information. The preset billing information may include: the user may preset a preset billing information; or the billing information used last time; or the billing information with the most history usage.
In practical applications, the preset billing information is usually not directly used without the user's 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 that the payer user 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 user is used 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, as shown in 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 information, and the payer can view the specific invoice information through the detail button 314. As shown in Figure 4, the invoice details diagram, in general, detailed invoice information can include billing header, tax number, bank account, 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 user, payment information is generated that does not include billing information;
The payment party user obtains the billing information in the case that the condition for obtaining the billing information is satisfied.
In this embodiment, the payment information generated by the payer user for the first time does not include the billing information, which is the same as the traditional payment information; and the second payment information generated after the paying party user 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 payment information generated without 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 paying party user may actively generate payment information including the billing information. That is to say, the payment information includes the traditional payment party identifier, 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 barcode, a payment barcode, and the like.
Taking the payment 2D barcode as an example, after the user opens the payment application and clicks the 2D barcode payment, the payment 2D barcode is directly generated in the prior art. In this embodiment, after the user opens the payment application and clicks the two-dimensional barcode payment, the user needs to obtain the billing information first, and then generate a payment two-dimensional barcode including the billing information. That is to say, the payment two-dimensional barcode generated in the prior art does not include the billing information, and the payment two-dimensional barcode generated in the embodiment includes the 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 two-dimensional barcode payment, 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 user obtains the payment information provided by the payer user, 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 user obtains payment information provided by the paying party user, specifically:
The payee client scans the payment graphic code provided by the payer client.
Taking the payment 2D barcode as an example, the payer can display the payment 2D barcode generated by the mobile phone to the payee, and the payee can start the camera through the receiver to scan the code. After the scan is successful, the payee The client can parse the billing information contained in the payment 2D barcode.
In another implementation manner, the payment information includes a payment sound wave, and the payee user obtains payment information provided by the paying party user, specifically:
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 user end, and the payee can start the sound wave module through the payee user side to monitor, and after receiving the payment sound wave, collect the payment. The party client can parse the billing information included in the payment sound wave.
Step 240: The payee user 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 paying party user generally includes a payer account identifier, and when the payee user end parses the payment information, the payer account identifier may also be identified; further, the payee user calls 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 account according to the payment information into the payee account, 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 user and the payee user.
Step 250: The billing system generates a paper or electronic invoice of the billing information when the payee user receives the payment platform to return the payment successfully.
The payee user 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 user can also send the electronic invoice to the paying party after the electronic invoice is generated by the billing system; or send it to the payment platform, and indirectly to the paying party via the payment platform.
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.
The following is a description of an embodiment of the method in which the payment client is the main body of the present application, and the embodiment may correspond to FIG. 2:
Step 510: In the case of making a payment, obtaining billing information; wherein the billing information is used to generate a paper or an electronic invoice;
Step 520: Generate payment information including the billing information. The payment information is used by the payee user to parse out the billing information, and in the case that the payee user receives the payment platform to return the payment successfully, the billing system generates 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 payment, generate payment information that does not include billing information;
The billing information is obtained in the case where the conditions for obtaining the billing information are 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 includes:
Obtain preset billing information;
The preset billing information includes: billing information used last time; or billing information with the most history usage; or preset billing information set by the payer.
The method embodiment of the present application centered on the payee client is described below with reference to FIG. 6, which may correspond to FIG. 2:
Step 610: Acquire payment information provided by the payment party user, and parse out the invoicing 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 the 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 user 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 user includes:
Monitor the payment sound waves broadcast by the payer client.
The following describes an embodiment of a method for implementing information transmission according to the example shown in FIG. 7. As shown in FIG. 7, the method may include the following steps:
Step 710: The payer user 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 user end may be determined after the payee user end negotiates with the payment platform. For example, the payee client can invoke the payment platform receiving connection interface, and the payment platform can return the payment link; the payee user terminal generates the payment information according to the returned payment link.
The payment information may include a receipt graphic code, and the paying party user 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 receipt graphic code may be parsed.
The payment information may further include a receiving sound wave, and the paying party user may open the sound wave module when the payment is required to be paid to the paying party, and after the receiving sound wave broadcasted by the paying party, the receiving sound wave may be parsed. Payee account.
Step 720: In the case of jumping to the payment interface, the paying party user 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 user obtains the billing information, which specifically includes:
The payer client obtains preset billing information;
The preset billing information includes: billing information used last time; or billing information with the most history usage; or preset billing information set by the payer.
In another mode, the paying party 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.
In another mode, the paying party obtains the billing information, which specifically includes:
The payment party user obtains the billing information in the case that the condition for obtaining the billing information is satisfied.
As shown in Figure 8a, the payer client can jump to the payment interface, and the payer can fill in the payment amount in 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 user invokes a payment interface of the payment platform to complete payment to the payee account, and sends the billing information to the payment platform.
Different from the embodiment shown in FIG. 2, the embodiment of FIG. 2 is that the payee user initiates a payment request to the payment platform; in this embodiment, the payer user 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 synchronized with the payment request or sent asynchronously Give the 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 user and the payee user.
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 user end, and the notification carries the billing information.
When the payment platform completes the payment, that is, if the payment by the payee account is successful, the payment platform may send a payment success notification to the payee user, and the notification carries the invoicing information.
Step 750: The receiving party user obtains the billing information carried by the notification when receiving the payment success notification by the payment platform, 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 user may acquire the billing information carried by the notification, so that the billing system generates the paper or electronic invoice of the billing information. For the electronic invoice, the payee user can also send the electronic invoice to the paying party after the electronic invoice is generated by the billing system; or send it to the payment platform, and indirectly to the paying party via the payment platform.
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.
The following describes an embodiment of a method for implementing information transmission according to the example shown in FIG. 9. As shown in FIG. 9, the method may include the following steps:
Step 810: The payee user 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 user initiates a payment request including the biometric information to the payment platform.
Step 830: The payment platform acquires the billing information preset by the payer account in the case that the payer account corresponding to the biometric information is identified.
The preset billing information includes: billing information used last time; or billing information with the most history usage; or preset billing information set by the payer.
Step 840: The payment platform returns a payment success notification to the payee user end when the payment is completed; the notification carries the billing information;
Step 850: The receiving party user obtains the billing information carried by the notification when receiving the payment success notification by the payment platform, 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 user end by providing the biometric information only after the payment platform identifies the payer account corresponding to the biometric information. The billing system generates a paper or electronic invoice for the billing information. Compared with the foregoing embodiment, in this embodiment, the payer does not need to carry the payer client, and the user experience is better and the payment efficiency is higher.
Corresponding to the foregoing 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 by a combination of hardware or hardware and software. Taking the software implementation as an example, as a logical device, the processor of the device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory. On 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, and the device in which the device is located in the embodiment is generally The actual function of information transmission 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 is configured to obtain billing information when the payment is made; wherein the billing information is used to generate a paper or an electronic invoice;
The generating unit 920 generates payment information including the billing information.
In an alternative embodiment:
The obtaining unit 910 specifically includes:
In the case of payment, generate payment information that does not include billing information;
The billing information is obtained in the case where the conditions for obtaining the billing information are satisfied.
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:
In the case of payment, the pre-configured invoice information of the payer is displayed;
Get the billing information selected by the payer.
In an alternative embodiment:
The obtaining the billing information includes:
Obtain preset billing information;
The preset billing information includes: billing information used last time; or billing information with the most history usage; or preset billing information set by the payer.
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 payment party user, and parse out the invoicing 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 for 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 user 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 user includes:
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. The specific form of the computer can be a personal computer, a notebook computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an e-mail receiving device, 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 function module and structure of the device for information transmission. The substantial execution body of the device can be an electronic device, including:
processor;
a memory for storing processor executable instructions;
Obtaining billing information in the case of making a payment; wherein the billing information is used to generate a paper or electronic invoice;
Generate payment information including the billing information.
Figure 11 above illustrates the internal function module 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;
Obtaining the payment information provided by the payment party user, and parsing the invoicing information in the payment information;
Invoking 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.
In the embodiment of the foregoing electronic device, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, CPU for short), or may be other general-purpose processors and digital signal processors (English: Digital Signal Processor) , referred to as: DSP), dedicated integrated circuit (English: Application Specific Integrated Circuit, referred to as: ASIC). The general purpose processor may be a microprocessor or the processor or any conventional processor, and the foregoing memory may be a read-only memory (English: read-only memory, abbreviation: ROM), random access memory. Body (English: random access memory, referred to as: RAM), flash memory, hard disk or solid state hard 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 a hardware and a software module in a 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, and the true scope and spirit of the specification
It is to be understood that the invention is not limited to the details of the details and The scope of the present specification is limited only by the scope of the appended claims.

11‧‧‧Payer client

12‧‧‧ Receiver client

121‧‧‧Invoicing system

13‧‧‧Payment platform

210-250‧‧‧Steps

311‧‧‧Invoice Information

312‧‧‧ icon

313‧‧‧Add button

314‧‧‧Detail button

411‧‧‧Edit button

510-520‧‧‧Steps

610-630‧‧‧Steps

710-750‧‧ steps

810-850‧‧‧Steps

910‧‧‧Acquisition unit

920‧‧‧Generating unit

1010‧‧‧Acquisition unit

1020‧‧‧call unit

1030‧‧‧Generating unit

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 disclosure;

3 is a schematic diagram showing the 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 for transmitting information of the paying party as the execution subject of FIG. 2;

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

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

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.

Claims (20)

A method of information transmission, the method comprising: In the case that the paying party user makes a payment, the paying party user obtains the billing information; wherein the billing information is used to generate a paper or an electronic invoice; The payer client generates payment information including the billing information; The payee user obtains the payment information provided by the payer user, and parses out the billing information in the payment information; The payee user invokes the payment interface of the payment platform to complete the payment; In the case that the payee user end receives the payment platform and returns the payment success, the billing system generates a paper or electronic invoice of the billing information. A method of information transmission, the method comprising: In the case of making a payment, obtaining billing information; wherein the billing information is used to generate a paper or electronic invoice; Generate payment information that includes the billing information. According to the method of claim 2, the payment information includes a payment graphic code or a payment sound wave. According to the method of claim 2, in the case of making a payment, obtaining the billing information includes: In the case of payment, generate payment information that does not include billing information; The billing information is obtained in the case where the conditions for obtaining the billing information are satisfied. According to the method of claim 2, in the case of making a payment, obtaining the billing information includes: In the case of payment, the pre-configured invoice information of the payer is displayed; Get the billing information selected by the payer. According to the method of claim 2, the obtaining the billing information includes: Obtain preset billing information; The preset billing information includes: the latest billing information used; or the most used billing information in history; or the default billing information set by the payer. A method of information transmission, the method comprising: Obtain payment information provided by the payer user, and parse out the billing information in the payment information; Invoking the payment interface of the payment platform to complete the payment; In case the receiving payment platform returns the payment successfully, the billing system generates a paper or electronic invoice of the billing information. According to the method of claim 7, the payment information includes a payment graphic code, and the payment information provided by the payment party user 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 user includes: Monitor the payment sound waves broadcast by the payer client. A method of information transmission, the method comprising: The paying party user 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 user 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 the billing information, the payment platform sends a payment success notification to the payee user in the case that the payee account is successfully received, and the notification carries the billing information; When receiving the payment success notification, the payee user obtains the billing information carried by the notification, so that the billing system generates the paper or electronic invoice of the billing information. According to the method of claim 9, the payment information includes a payment graphic code or a payment sound wave. According to the method of claim 9, the paying party obtains the billing information, which specifically includes: The payer client obtains preset billing information; The preset billing information includes: the latest billing information used; or the most used billing information in history; or the default billing information set by the payer. According to the method of claim 9, the paying party obtains the billing information, which specifically includes: The payer client displays pre-configured invoice information of the payer; The payer client obtains the billing information selected by the payer. According to the method of claim 9, the paying party obtains the billing information, which specifically includes: The payee client obtains the billing information in the case that the condition for obtaining the billing information is satisfied. A method of information transmission, the method comprising: The payee user collects biometric information of the payer; The payee client initiates a payment request including the biometric information to the payment platform; The payment platform acquires the billing information preset by the payer account in the case that the payer account corresponding to the biometric information is identified; The payment platform returns a payment success notification to the payee user end when the payment is completed; the notification carries the billing information; When receiving the payment success notification, the payee user obtains the billing information carried by the notification, so that the billing system generates the paper or electronic invoice of the billing information. According to the method of claim 14, 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. According to the method of claim 14, the preset billing information includes: the latest billing information used; or the billing information with the most history usage; or the preset billing information set by the payer. A device for information transmission, the device comprising: Obtaining a unit, in the case of making a payment, obtaining billing information; wherein the billing information is used to generate a paper or an electronic invoice; A generating unit generates payment information including the billing information. A device for information transmission, the device comprising: Obtaining a unit, obtaining payment information provided by the paying party user, 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, in case the receiving payment platform returns the payment success, the billing system generates the paper or electronic invoice of the billing information. An electronic device comprising: processor; a memory for storing processor executable instructions; Wherein the processor is configured to: In the case of making a payment, obtaining billing information; wherein the billing information is used to generate a paper or electronic invoice; Generate payment information that includes the billing information. An electronic device comprising: processor; a memory for storing processor executable instructions; Wherein the processor is configured to: Obtain payment information provided by the payer user, and parse out the billing information in the payment information; Invoking the payment interface of the payment platform to complete the payment; In case the receiving payment platform returns the payment successfully, the billing system generates a paper or electronic invoice of the billing information.