WO2019134543A1 - Procédé et appareil de transmission d'informations et dispositif électronique - Google Patents

Procédé et appareil de transmission d'informations et dispositif électronique Download PDF

Info

Publication number
WO2019134543A1
WO2019134543A1 PCT/CN2018/123035 CN2018123035W WO2019134543A1 WO 2019134543 A1 WO2019134543 A1 WO 2019134543A1 CN 2018123035 W CN2018123035 W CN 2018123035W WO 2019134543 A1 WO2019134543 A1 WO 2019134543A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
information
billing information
payer
billing
Prior art date
Application number
PCT/CN2018/123035
Other languages
English (en)
Chinese (zh)
Inventor
彭玉军
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2019134543A1 publication Critical patent/WO2019134543A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/128—Check-book balancing, updating or printing arrangements

Definitions

  • 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.
  • customers can invoice at the merchant's consumption.
  • customers need to provide billing information to the merchant (eg, including name, type, tax ID, unit address, phone number, etc.).
  • billing information eg, including name, type, tax ID, unit address, phone number, etc.
  • the customer can present the billing information by way of dictation, writing, and the like.
  • a method, device and electronic device for transmitting information provided by embodiments of the present specification:
  • a method for information transmission comprising:
  • 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
  • the billing system 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 for information transmission comprising:
  • a payment information containing the billing information is generated.
  • a method for information transmission comprising:
  • the billing system Upon receipt of the payment platform returning the payment success, the billing system generates a paper or electronic invoice for the billing information.
  • a method for information transmission 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;
  • 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.
  • a method for information transmission 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
  • the payment platform acquires default billing information of the payer account when the payee account corresponding to the biometric information is identified;
  • 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.
  • an apparatus for information transmission 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 including the billing information.
  • an apparatus for information transmission comprising:
  • Obtaining a unit obtaining payment information provided by the payer client, and parsing the billing information in the payment information;
  • 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 including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • a payment information containing the billing information is generated.
  • an electronic device including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the billing system Upon receipt of the payment platform returning the payment success, the billing system generates a paper or electronic invoice for the billing information.
  • 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.
  • FIG. 1 is a conceptual diagram of a system architecture for implementing information transmission according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for information transmission provided by an embodiment of the present specification
  • FIG. 3 is a schematic diagram showing display billing information provided by an embodiment of the present specification.
  • FIG. 5 is a flowchart corresponding to the method of FIG. 2 for information transmission by a payer client as an execution subject;
  • FIG. 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. 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. 11 is a schematic block diagram of an apparatus for information transmission according to an embodiment of the present disclosure.
  • 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.
  • first information may also be referred to as the second information without departing from the scope of the present description.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • customers can invoice at the merchant's consumption.
  • customers need to provide billing information to the merchant (eg, including name, type, tax ID, unit address, phone number, etc.).
  • billing information eg, including name, type, tax ID, unit address, phone number, etc.
  • 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.
  • 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.
  • a smartphone with Alipay installed.
  • 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.
  • 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 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.
  • 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.
  • the step 210 may include:
  • the payer client In the case where the payer client makes a payment, the payer client displays the pre-configured invoice information of the payer;
  • the number of invoice information pre-configured by the payer may be multiple, such as 1, 2, 3, and the like.
  • the payer client 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.
  • the payer can also configure a new invoice information by adding a button 313.
  • invoice 3 can be a brief message, and the payer can view the specific invoice information via the details button 314.
  • 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.
  • the payer can also modify the invoice content in the invoice details interface, such as by the edit button 411 in FIG.
  • the step 210 may include:
  • the payer client acquires the billing information.
  • 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.
  • 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.
  • 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.
  • the payment QR code is directly generated in the prior art.
  • the user 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.
  • the user 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.
  • the prior art directly generates a sound wave for payment.
  • the user 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.
  • the payment information includes a payment graphic code
  • 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.
  • 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.
  • the payment information includes a payment sound wave
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 5 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.
  • the payment information includes a payment graphic code or a payment sound wave.
  • the step 510 specifically includes:
  • the billing information is acquired in the case where the condition for obtaining the billing information is satisfied.
  • the step 510 specifically includes:
  • the pre-configured invoice information of the payer is displayed;
  • the obtaining the billing information specifically includes:
  • 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.
  • FIG. 6 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.
  • the payment information includes a payment graphic code
  • the obtaining payment information provided by the payment party client includes:
  • the payment information includes a payment sound wave
  • the payment information provided by the payment party client includes:
  • 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.
  • the payment information provided by the payee client may be determined after the payee client negotiates with the payment platform.
  • 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
  • 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.
  • the paying 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 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.
  • the payer client obtains billing information, which specifically includes:
  • the payer client acquires the billing information.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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. .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. .
  • 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.
  • 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.
  • 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.
  • the processor of the device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • 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.
  • 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.
  • the obtaining unit 910 specifically includes:
  • the billing information is acquired in the case where the condition for obtaining the billing information is satisfied.
  • the payment information includes a payment graphic code or a payment sound wave.
  • the obtaining unit 910 specifically includes:
  • the pre-configured invoice information of the payer is displayed;
  • the obtaining the billing information specifically includes:
  • 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.
  • 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.
  • the payment information includes a payment graphic code
  • the payment information provided by the payment party client includes:
  • the payment information includes a payment sound wave
  • the payment information provided by the payment party client includes:
  • 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.
  • 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.
  • FIG. 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:
  • a memory for storing processor executable instructions
  • a payment information containing the billing information is generated.
  • FIG. 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:
  • a memory for storing processor executable instructions
  • the billing system Upon receipt of the payment platform returning the payment success, the billing system generates a paper or electronic invoice for the billing information.
  • 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.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un procédé et un appareil de transmission d'informations et un dispositif électronique. Le procédé consiste à: acquérir des informations de facturation lorsqu'un client payeur paye (210), les informations de facturation étant utilisées pour générer un papier ou facture électronique; générer les informations de paiement de client payeur comprenant les informations de facturation; acquérir par un client bénéficiaire les informations de paiement fournies par le client payeur, et analyser par le client bénéficiaire les informations de facturation incluses dans les informations de paiement (230); appeler par le client bénéficiaire une interface d'une plate-forme de paiement pour achever le recouvrement; et générer par un système de facturation un papier ou facture électronique comprenant les informations de facturation lors de la réception des informations de recouvrement réussi renvoyées par la plateforme de paiement (250).
PCT/CN2018/123035 2018-01-02 2018-12-24 Procédé et appareil de transmission d'informations et dispositif électronique WO2019134543A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810000863.7 2018-01-02
CN201810000863.7A CN108269135B (zh) 2018-01-02 2018-01-02 信息传输的方法及装置和电子设备

Publications (1)

Publication Number Publication Date
WO2019134543A1 true WO2019134543A1 (fr) 2019-07-11

Family

ID=62773197

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123035 WO2019134543A1 (fr) 2018-01-02 2018-12-24 Procédé et appareil de transmission d'informations et dispositif électronique

Country Status (3)

Country Link
CN (2) CN108269135B (fr)
TW (1) TW201931257A (fr)
WO (1) WO2019134543A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113656415A (zh) * 2021-06-30 2021-11-16 微梦创科网络科技（中国）有限公司 支付方法、支付装置、支付设备及存储介质
US20220180138A1 (en) * 2020-12-09 2022-06-09 Ryoh ARUGA Information processing apparatus, information processing system, and information processing method

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108269135B (zh) * 2018-01-02 2021-08-24 创新先进技术有限公司 信息传输的方法及装置和电子设备
JP2020098504A (ja) * 2018-12-18 2020-06-25 株式会社メルカリ 情報処理方法、情報処理装置、及びプログラム
CN109949110A (zh) * 2019-02-19 2019-06-28 西安艾润物联网技术服务有限责任公司 发票处理方法、系统、设备及计算机可读存储介质
CN110400139B (zh) * 2019-07-31 2022-06-10 中国人民银行数字货币研究所 基于对公数字钱包的支付方法、装置及系统
CN112700318A (zh) * 2021-01-12 2021-04-23 海尔数字科技(青岛)有限公司 财务处理方法、装置、电子设备、及存储介质
CN113362121A (zh) * 2021-06-22 2021-09-07 邓生毛 一种电子发票系统
CN113537973A (zh) * 2021-08-25 2021-10-22 苏州触达信息技术有限公司 基于超声声波的快捷支付方法与系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103500411A (zh) * 2013-08-22 2014-01-08 王亚君 一种实现电子发票系统及方法
CN105374134A (zh) * 2015-12-01 2016-03-02 广州神马移动信息科技有限公司 打印发票的方法、支付系统、付款终端和收款终端
CN106875239A (zh) * 2017-01-25 2017-06-20 金蝶软件（中国）有限公司 发票信息生成方法和装置
CN108269135A (zh) * 2018-01-02 2018-07-10 阿里巴巴集团控股有限公司 信息传输的方法及装置和电子设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105185005A (zh) * 2015-06-25 2015-12-23 税友软件集团股份有限公司 一种生成发票的方法和设备
CN106875238B (zh) * 2017-01-25 2021-02-02 金蝶票据云科技(深圳)有限公司 发票信息生成方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103500411A (zh) * 2013-08-22 2014-01-08 王亚君 一种实现电子发票系统及方法
CN105374134A (zh) * 2015-12-01 2016-03-02 广州神马移动信息科技有限公司 打印发票的方法、支付系统、付款终端和收款终端
CN106875239A (zh) * 2017-01-25 2017-06-20 金蝶软件（中国）有限公司 发票信息生成方法和装置
CN108269135A (zh) * 2018-01-02 2018-07-10 阿里巴巴集团控股有限公司 信息传输的方法及装置和电子设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220180138A1 (en) * 2020-12-09 2022-06-09 Ryoh ARUGA Information processing apparatus, information processing system, and information processing method
US11960949B2 (en) * 2020-12-09 2024-04-16 Ricoh Company, Ltd. Information processing apparatus, information processing system, and information processing method
CN113656415A (zh) * 2021-06-30 2021-11-16 微梦创科网络科技（中国）有限公司 支付方法、支付装置、支付设备及存储介质
CN113656415B (zh) * 2021-06-30 2024-06-07 微梦创科网络科技（中国）有限公司 支付方法、支付装置、支付设备及存储介质

Also Published As

Publication number Publication date
CN108269135B (zh) 2021-08-24
CN108269135A (zh) 2018-07-10
TW201931257A (zh) 2019-08-01
CN113850634A (zh) 2021-12-28

Similar Documents

Publication Publication Date Title
WO2019134543A1 (fr) Procédé et appareil de transmission d'informations et dispositif électronique
US11989708B2 (en) Conversational management of partial payment transactions
US8369828B2 (en) Mobile-to-mobile payment system and method
US8504450B2 (en) Mobile remittances/payments
WO2017041641A1 (fr) Procédé et dispositif pour réaliser une fonction de service
WO2015088853A1 (fr) Lancement d'une application client basée sur un message
US20200005293A1 (en) Cryptocurrency greeting cards
TW201915894A (zh) 基於信用實現分期業務的方法
US20120185382A1 (en) Pay by link system and method
CN112163946A (zh) 基于分布式交易系统的账务处理方法及装置
JP6760974B2 (ja) トランザクション処理方法及びシステム
WO2019179249A1 (fr) Procédé et dispositif de paiement et appareil électronique
KR20150133858A (ko) 실시간 모바일 지불 처리 시스템
CN112732547B (zh) 业务测试方法、装置、存储介质及电子设备
CN108764861B (zh) 信息获取方法及装置和电子设备
JP2019536142A (ja) 送金方法およびシステム
US20160247132A1 (en) Affiliated individual identification and account recoupment
RU2532875C2 (ru) Способ, устройство и система представления услуги
CN112182400B (zh) 消息处理方法、消息处理装置、电子设备及存储介质
CN110378785B (zh) 由服务器执行的交易处理方法、装置、计算设备以及介质
CN110581771B (zh) 利用网络消息服务以处理费用拆分的方法、计算装置可读存储介质以及计算装置
TWI774290B (zh) 基於條碼支付的實現方法和裝置
TWM560633U (zh) 使用一行動裝置取得電子發票資訊的系統
TWI653593B (zh) 使用一行動裝置取得電子發票資訊的系統及方法
CN116228237A (zh) 数据转移方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18898639

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18898639

Country of ref document: EP

Kind code of ref document: A1