WO2017126837A1 - Procédé de règlement d'un montant de paiement de facture - Google Patents
Procédé de règlement d'un montant de paiement de facture Download PDFInfo
- Publication number
- WO2017126837A1 WO2017126837A1 PCT/KR2017/000289 KR2017000289W WO2017126837A1 WO 2017126837 A1 WO2017126837 A1 WO 2017126837A1 KR 2017000289 W KR2017000289 W KR 2017000289W WO 2017126837 A1 WO2017126837 A1 WO 2017126837A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bill
- payment
- electronic
- server
- application
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 239000000284 extract Substances 0.000 claims abstract description 11
- 238000007726 management method Methods 0.000 description 4
- 230000008520 organization Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000005611 electricity Effects 0.000 description 2
- 238000011017 operating method Methods 0.000 description 2
- 238000012015 optical character recognition Methods 0.000 description 2
- 239000010865 sewage Substances 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000005021 gait Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 229910044991 metal oxide Inorganic materials 0.000 description 1
- 150000004706 metal oxides Chemical class 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 210000003462 vein Anatomy 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/16—Payments settled via telecommunication systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- 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
Definitions
- Embodiments according to the concept of the present invention relates to a method for paying the bill amount of the bill (bill), in particular the bill of the user corresponding to the recipient of the bill using an application and a server running on the user's terminal It is about how to pay the amount paid.
- bill amount of the bill in particular the bill of the user corresponding to the recipient of the bill using an application and a server running on the user's terminal It is about how to pay the amount paid.
- a bill is a document that imposes a certain amount on a natural person, corporation, or organization, such as a country, public agency, or company, and can be called by various names, such as a car tax bill, a water and sewage bill, a resident tax bill, a local tax bill, or an electricity bill. .
- the technical problem to be achieved by the present invention is to classify the electronic bills for each bill recipient by using a server, and to connect to the server using an application running on the user's terminal electronic bills and payment information imposed on the user To provide to the application and to provide a method for securely paying the payment amount charged to the user using the application.
- a method of paying a bill for a bill for the user using an application and a server executed in a user terminal may include generating a bill image for the bill by the camera of the terminal.
- An application extracting a recipient name and a recipient address from the bill image, and transmitting the extracted recipient name and the extracted recipient address to the server, wherein the server extracts the extracted recipient name and the extracted recipient address;
- a name of an electronic bill, a payment amount included in the first electronic bill, and a first payment means mapped to the first electronic bill among the payment means are displayed on the display device, and the user inputs first authentication information.
- a method of paying a bill for a bill for the user using an application and a server executed in a user terminal may include generating a bill image for the bill by the camera of the terminal.
- An application extracting a recipient name and a recipient address from the bill image, and transmitting the extracted recipient name and the extracted recipient address to the server, wherein the server extracts the extracted recipient name and the extracted recipient address;
- the server corresponds to the first electronic bill and the first electronic bill corresponding to the selection information among the electronic bills stored in the database.
- the application receiving the first electronic bill and the first payment means, wherein the application is the name of the first electronic bill, the first electronic bill Payment amount included in, and the first payment Displaying the terminal on the display device and requesting the user to input first authentication information; and when the application receives the first authentication information, the application receives the name of the first electronic bill, the payment amount, Transmitting the first payment means and the first authentication information to the server.
- a method for paying a bill for a bill for a user using an application and a server executed in a user terminal may include generating a bill image for the bill by a camera of the terminal. Extracting a recipient name and a recipient address from the bill image, and transmitting the extracted recipient name and the extracted recipient address to the server, wherein the server includes the extracted recipient name and the extracted recipient address; Using a recipient address, the electronic bills and payment means for the user are read from a database accessible by the server, and the electronic bills and payment means are sent to the terminal, whereby the application sends the electronic bill.
- the application includes the payment means.
- a method of paying a bill amount of a bill may be used to easily pay the bill amount of the bill imposed on the user corresponding to the bill recipient using an application and a server running on a user's terminal. It can be effective.
- the payment method of the bill according to the embodiments of the present invention the payment deadline for each of the bills imposed on the user by managing the electronic bills imposed on the user corresponding to the bill recipient by the payment period integrated There is an effect that can easily provide information.
- FIG. 1 is a block diagram showing a bill payment system payment system according to embodiments of the present invention.
- FIG. 2 illustrates an embodiment of electronic bill information stored in the electronic bill information database shown in FIG. 1.
- FIG. 3 illustrates a data flow for explaining an operation method of the bill payment amount payment system shown in FIG. 1.
- FIG. 4 illustrates an embodiment of electronic bills displayed on a display device of a user terminal shown in FIG. 1.
- FIG. 5 illustrates another embodiment of the electronic bills displayed on the display device of the user's terminal shown in FIG. 1.
- FIG. 6 shows detailed information of the electronic bill displayed at the user's terminal shown in FIG. 1 when one electronic bill is selected from among the electronic bills shown in FIG. 4 or 5.
- FIG. 7 illustrates a data flow for explaining an operation method of the bill payment amount payment system shown in FIG. 1.
- FIG. 8 illustrates electronic bill lists displayed at a terminal of a user according to the operating method illustrated in FIG. 7.
- FIG. 9 illustrates a data flow for explaining a method of operating the bill payment amount payment system shown in FIG. 1.
- FIG. 10 illustrates payment means displayed on a terminal of a user according to the operating method of FIG. 9.
- FIG. 11 shows detailed information of an electronic bill displayed on a user's terminal shown in FIG. 1 when one electronic bill is selected among electronic bills and one payment method is selected among payment methods.
- the database may mean a functional and / or structural combination of software and hardware for storing information in each DB.
- the DB may be implemented with at least one table, and the DB may further include a separate device, such as a database management system (DBMS), for storing, retrieving, and / or managing stored information.
- DBMS database management system
- the DB may be implemented in various ways, such as in the form of a linked-list, tree, or relational DB.
- the DB may be any data storage medium capable of storing information in the DB and And / or include data structures.
- a bill is a document that charges a certain amount by a state, a public agency, or an enterprise (or an agency), and various names such as an automobile tax bill, a water and sewage bill, a resident tax bill, a local tax bill, and an electricity bill are assigned.
- the notice in this specification includes all notices in the form of a paper that charges a certain amount to the recipient.
- the electronic notice may mean an image file including the contents of the notice.
- the bill payment amount payment system 10 is a user terminal (100, hereinafter referred to as "terminal"), the network 200, the server 300, the electronic bill information database 400, and It may include a payment server 500.
- the bill payment system 10 may further include various servers 510, 520, 530, and 540.
- Each of the terminal 100 and the payment server 500 may perform data communication with the server 300 through the network 200.
- the network 200 may be implemented as a wired network, a wireless network, or a wired / wireless hybrid network.
- the terminal 100 includes an application (APP) 110 and a camera 120.
- the APP 110 may be executed by a central processing unit (CPU) included in the terminal 100.
- the terminal 100 may be a personal computer (PC), a smartphone, a personal digital assistant (PDA), an enterprise digital assistant (EDA), a mobile internet device (MID), or an Internet of Things. It can be implemented as a Thing (IoT) device or an Internet of Everything (IoE) device.
- PC personal computer
- PDA personal digital assistant
- EDA enterprise digital assistant
- MID mobile internet device
- IoT Thing
- IoE Internet of Everything
- the APP 110 installed in the terminal 100 may be downloaded from an app store to a memory device of the terminal 100 through a wired network or a wireless network, and executed by the CPU of the terminal 100.
- APP 110 is called a web application or a web app, and the web application or the web app refers to application software that can be used in a web browser through the Internet or an intranet.
- the APP 110 may provide a user with an interface for inputting a name, address, bill information (eg, information for identifying a bill), a payment method, and authentication information.
- the payment means when the payment means is a bank, the payment means may include a bank, a bank account number, and a password.
- the payment means when the payment means is a credit card, the payment means may include a credit card company, a credit card number, an expiration date, a card verification value (CVV) number, and a password.
- the authentication information may be authentication information about a payment means, and may be authentication information for identifying a user of the terminal 100.
- the server 300 When the user clicks or touches the registration 111, the name, address, bill information, payment means, and authentication information input by the user are transmitted to the server 300 via the network 200, and the server 300 May store the name, the address, the bill information, the payment means, and the authentication information in the electronic bill information DB 400.
- the server 300 generates an encryption key using 'name' and 'address', and uses the encryption key to name 'electronic bill name' (eg, information on the electronic bill). ), 'Payment means', and 'authentication information' may be encrypted, and the encrypted information may be stored in the electronic bill information DB 400. Therefore, the electronic bill name, the payment means, and the authentication information may be securely stored in the electronic bill information DB 400 using an encryption key.
- name 'electronic bill name' eg, information on the electronic bill.
- 'Payment means', and 'authentication information' may be encrypted, and the encrypted information may be stored in the electronic bill information DB 400. Therefore, the electronic bill name, the payment means, and the authentication information may be securely stored in the electronic bill information DB 400 using an encryption key.
- the server 300 generates a decryption key using the 'extracted recipient name' and the 'extracted recipient address' transmitted in each of steps S125, S225, and S325, and generates an electronic bill information DB.
- the encrypted electronic bill name and the encrypted payment means transmitted from 400 may be decrypted using the decryption key, and the decrypted information may be transmitted to the terminal 100 through the network 200.
- the camera 120 may include an original camera, a two-dimensional or three-dimensional barcode reader, an optical character reader (OCR), or a radio frequency identification (RFID) reader, a near field (NFC). communication)
- OCR optical character reader
- RFID radio frequency identification
- NFC near field
- a device capable of reading user information (for example, a recipient name and a recipient address) described in a bill (for example, a bill printed on paper) may be collectively referred to.
- a bill refers to a document in which a certain amount of money is charged by a state, a public agency, or a company, and the bill is a tax notice, a fine bill, an electric bill, a telephone bill, a credit card bill, a bill, etc. It can be called various names.
- the camera 120 may generate a bill image for the bill and transmit the generated bill image to the CPU or the memory device under the control of the CPU or APP 110 of the terminal 100.
- the camera 120 may be implemented as a charge coupled device (CCD) camera or a complementary metal-oxide semiconductor (CMOS) camera, and may acquire a 2D image or a 3D image.
- CCD charge coupled device
- CMOS complementary metal-oxide semiconductor
- the APP 110 may include the one-dimensional, the two-dimensional, or the like contained in the bill image photographed by the camera 120.
- a recipient name and a recipient address may be extracted from the 3D barcode.
- Bill payment amount payment system 10 the amount of bills imposed on the user (for example, the bill recipient) of the terminal 100, using the APP 110 and the server 300 running on the terminal 100 (E.g., the payment amount) can be settled electronically.
- FIG. 2 illustrates an embodiment of electronic bill information stored in the electronic bill information database shown in FIG. 1. 1 and 2, the electronic bill information database 400 includes a plurality of fields for managing electronic bill information, each of the fields 'name', 'address', It may include, but is not limited to, an electronic bill name, a payment amount, a payment due date, a payment method, and authentication information.
- the name of the electronic bill name may mean information that may identify each electronic bill (EB1, EB2, EB3, or EM4) or may include the information.
- the electronic bill information database 400 may store the electronic bills EB1 to EB4 including the same or similar contents as those described in the paper or printed bill.
- the electronic bill name, payment amount, and due date shown in FIG. 2 may be the same as the descriptions of the bill corresponding to the name and address (or specified by the name and the address), and the payment means and authentication information It may be a payment method and authentication information for each electronic bill (EB1 ⁇ EB4).
- the electronic bills EB1 to EB4 may be unpaid electronic bills, and each of the unpaid electronic bills EB1 to EB4 may be mapped one-to-one with each of the payment methods PM1 to PM4.
- the payment method may include information identifying a payment method, such as a bank account number, credit card number, or check card number, but may be able to pay each payment amount listed on each electronic bill (EB1 to EB4). It can mean various kinds of payment numbers.
- the authentication information may be a password that can uniquely identify a user of the terminal 100 or biometric information, but is not limited thereto.
- the biometric information may include a fingerprint, an iris, a vein, a face, a voice, a handwriting, or a gait.
- the server 300 may access and manage the electronic bill information database 400 including the electronic bill information shown by way of example in FIG. 2 for the user.
- a user who receives the B bill, the C bill, the A bill, and the D bill by mail may register the user information and the bill information with the server 300 by using the APP 110 executed in the terminal 100.
- the APP 110 stores the user information including the user's name (eg, Hong Gil-dong) and the user's address (eg, 123 YY Building, XX-ro XX-gu, Seoul) via the network 200 ( 300).
- the server 300 may store the user information in the electronic bill information database 400.
- the user who received the B bill inputs the information about the B bill (for example, information for identifying the B bill) by using the APP 110 executed in the terminal 100, and the payment means of the B bill.
- the information about the B bill for example, information for identifying the B bill
- APP 110 connected to the server 300 through the login information about the bill B, account number of the bank B ( PM1) and the authentication information W may be transmitted to the server 300 through the network 200.
- the server 300 may store the information on the B bill, the account number PM1 of the B bank, and the authentication information W in the electronic bill information database 400 storing the user information.
- a user who receives the C bill inputs the information about the C bill (for example, information for identifying the C bill) by using the APP 110 executed in the terminal 100, and the payment means of the C bill.
- the information about the C bill for example, information for identifying the C bill
- APP 110 connected to the server 300 through the login information about the bill C, account number of the bank C ( PM2) and the authentication information (X) may be transmitted to the server 300 via the network 200.
- the server 300 may store the information about the C bill, the account number PM2 of the C bank, and the authentication information X in the electronic bill information database 400 that stores the user information.
- a user who receives the A bill inputs the information about the A bill (for example, information for identifying the A bill) by using the APP 110 executed in the terminal 100, and the payment means of the A bill.
- the server 300 may store the information on the A bill, the card number PM3 of the A card company, and the authentication information Y in the electronic bill information database 400 storing the user information.
- the user who received the D bill inputs the information about the D bill (for example, information for identifying the D bill) by using the APP 110 executed in the terminal 100, and the payment means of the D bill.
- Set to the card number (PM4) of the D card company, and set the authentication information (Z), APP 110 connected to the server 300 through the login information about the D bill, card number ( PM4) and the authentication information Z may be transmitted to the server 300 via the network 200.
- the server 300 may store the information about the D bill, the card number PM4 of the D card company, and the authentication information Z in the electronic bill information database 400 storing the user information.
- the server 300 includes the server 510 of the B organization that issues the B bill, the server 520 of the C organization that issues the C bill, the server 530 of the A organization that issues the A bill, and the D bill.
- the server 540 of the issuing agency D may transmit request information requesting to transmit the electronic bill to the server 300 together with the user information (for example, the name of the recipient and the address of the recipient).
- the server 510 of agency B, the server 520 of agency C, and the server 530 of agency A, and the server 540 of agency D correspond to the B electronic bill (EB1), C corresponding to the B bill.
- Each of the C electronic bill (EB2) corresponding to the bill, the A electronic bill (EB3) corresponding to the A bill, and the D electronic bill (EB4) corresponding to the D bill may be transmitted to the server 300 at a predetermined time or a predetermined date. have.
- the server 300 When a user of the terminal 100 registers bill information for each bill imposed on him or her using the APP 110 in the server 300, the server 300 includes the bill information together with the user's name and address. May be transmitted to the servers 510, 520, 530, and 540 of each of the institutions generating each of the bills. Accordingly, each of the institutions may mail each of the bills to the user, and a server of each of the institutions may transmit an electronic bill corresponding to each of the bills to the server 300. Therefore, the server 300 may store and electronically manage various electronic bills corresponding to various bills in the electronic bill information DB 400 based on the registered recipient's name and the recipient's address.
- the B electronic bill (EB1) is received from the server 510 of the B institution that the B bill is generated every month to the user (for example, "Hong Gil-dong") whose address is "123 XX-ro XX-ro, Seoul ⁇ -gu, Seoul".
- the server 300 may update the monthly payment amount and the due date of the B electronic bill EB1 stored in the electronic bill information DB 400. Also.
- a server of agency C, agency A, or agency D which generates monthly notices C, A, or D to users addressing "Building YY XX-ro XX-ro, ⁇ -gu, Seoul,"
- the server 300 receives the electronic bill information DB 400. You may update monthly payment amounts and due dates of the C Electronic Bill (EB2), the A Electronic Bill (EB3), or the D Electronic Bill (EB4).
- Each of the electronic bills EB1 to EB4 stored in the “electronic bill name” field of FIG. 2 may include all or a part of contents included or included in each bill.
- FIG. 3 illustrates a data flow for explaining an operation method of the bill payment amount payment system shown in FIG. 1. 1 to 3, when the user photographs the bill 101 in printed form using the camera 120 of the terminal 100, the camera 120 may generate a bill image for the bill ( S110).
- the APP 110 installed in the terminal 100 may be automatically executed when the bill image is generated (S115). For example, the APP 110 determines whether the image generated by the camera 120 is a bill image, and when the generated image is the bill image, the recipient name and the recipient address from the generated bill image. 'Can be extracted (S120). For example, the APP 110 may recognize a letter of “bill” or “bill” from the image, and determine whether the image is a bill image based on the recognition result. According to embodiments, the APP 110 may be executed before photographing the bill using the camera 120. That is, step S115 may be performed before step S110.
- the extracted recipient name may be the name of the recipient receiving the bill 101
- the extracted recipient address may be the address of the recipient receiving the bill 101.
- the APP 110 may transmit the extracted recipient name and the extracted recipient address to the server 300 through the network 200 (S125).
- the network 200 may be a wireless local area network (WLAN) such as Wi-Fi (Wireless fidelity), a wireless personal area network (WPAN) such as Bluetooth, or a wireless universal serial (USB). bus, Zigbee, near field communication (NFC), radio-frequency identification (RFID), or mobile cellular network (mobile cellular network), but is not limited thereto.
- WLAN wireless local area network
- WPAN wireless personal area network
- USB wireless universal serial
- bus Zigbee, near field communication (NFC), radio-frequency identification (RFID), or mobile cellular network (mobile cellular network), but is not limited thereto.
- 3rd generation) mobile networks 4G (4th generation) mobile communication network, TM LTE (Long term evolution) mobile communication network or a LTE-Advanced (LTE-a), but may comprise a mobile communication network, but is not limited to such.
- the server 300 may generate a decryption key using the extracted recipient name and the extracted recipient address transmitted from the terminal 100.
- the server 300 is an electronic bill for a user (e.g., a user corresponding to the extracted recipient name and an extracted recipient address (e.g., Hong Gil-dong)) from the electronic bill information database 400 accessible by the server 300.
- the electronic bills EB1 to EB4 and the payment means PM1 to PM4 stored by the server 300 in the electronic bill information database 400 are encrypted by 'name' and 'address'. to be.
- the server 300 decrypts the electronic bills EB1 to EB4 and the payment means PM1 to PM4 using the decryption key, and decrypts the electronic bills EB1 to EB4 and the decrypted payment means PM1.
- PM4 may be transmitted to the terminal 100 through the network 200 (S135).
- the server 300 may decrypt the encrypted electronic bills EB1 to EB4 and the encrypted payment means PM1 to PM4 using the decryption key.
- the electronic bill name, payment method, and authentication information stored in (or stored in) the electronic bill information database 400 means information encrypted by the name and address of the user of the terminal 100 and the server 300.
- the information transmitted from) to the terminal 100 means information decrypted by the extracted recipient name and the extracted recipient address.
- Information stored in the electronic bill information database 400 or information to be stored by the server 300 may be specified and encrypted based on 'name' and 'address'.
- the information read from the electronic bill information database 400 by the server 300 is specified based on the extracted recipient name (in some cases the name) and the extracted recipient address (in some cases the address). Can be decrypted.
- FIG. 2 and FIG. 3 show an embodiment in which each of the electronic bills EB1 to EB4 is mapped to each payment means PM1 to PM4 on a one-to-one basis, two or more electronic bills are included in one payment method. Can be mapped.
- FIG. 4 illustrates an example of electronic bills displayed on the display device of the user's terminal shown in FIG. 1
- FIG. 5 illustrates another example of electronic bills displayed on the display device of the user's terminal shown in FIG. 1. .
- the APP 110 receives the electronic bills EB1 to EB4 received from the server 300 through the network 200, and receives the received electronic bills EB1 to EB4.
- the arranged electronic bills EB1 to EB4 may be displayed on the display device 130 of the terminal 100 (S140).
- the received electronic bills EB1 to EB4 may be stored in the memory device of the terminal 100.
- each of the electronic bills EB1 to EB4 may include a name, an address, an electronic bill name, a payment amount, and a due date.
- each of the electronic bills EB1 to EB4 may further include authentication information W, X, Y, and Z.
- the APP 110 may extract a "payment due date" included in each of the electronic bills EB1 to EB4 stored in the memory device. APP 110 arranges (or rearranges) the electronic bills EB1 to EB4 in the order from which the extracted payment due date (or payment due date) is from the lowest to the lowest, and the arranged (or rearranged) electronic bills ( EB3, EB1, EB2, and EB4 may be displayed on the display device 130 of the terminal 100 (S140).
- the APP 110 may display the electronic bills EB3, EB1, EB2, and EB4 arranged in the order of the payment due date, on the display device 130 of the terminal 100. .
- Methods of displaying the electronic bills EB3, EB1, EB2, and EB4 on the display device 130 may be variously changed by the APP 110.
- the user may set the payment amount in the small order, the payment amount in the large order, or the late payment deadline in the APP 110.
- the APP 110 may display the electronic bills EB1, EB2, EB2, and EB4 on the display device 130 in the order set by the user.
- the user of the terminal 100 selects the check box 141 to select any one of the electronic bills EB1 to EB4 displayed on the display device 130. Click (or select) and pay (145) can be clicked (or selected) (S145).
- FIG. 6 shows detailed information of the electronic bill displayed at the user's terminal shown in FIG. 1 when one electronic bill is selected from among the electronic bills shown in FIG. 4 or 5.
- the APP 110 may include an electronic bill name of a selected electronic bill EB3 stored in a memory device, a payment amount (eg, 10,000) included in the selected electronic bill EB3, a payment due date (eg, , 2015.12.15), and the first authentication information while displaying the payment means PM3 (for example, the card number of the A card: XXXX-XXXX-XXX-XXXX) mapped to the selected bill EB3 through the display device 130.
- An input of ID1 may be requested to the user of the terminal 100 (S150).
- the user may input the first authentication information ID1 into the graphical user interface 146 displayed on the display device 130 and click (or select) the payment 147.
- FIG. 6 shows "password" as an example of the first authentication information ID1
- the first authentication information ID1 may be replaced with the above-described biometric information.
- the APP 110 when the APP 110 receives the first authentication information ID1 input from the user (S155), the APP 110 displays the name of the selected electronic bill EB3 and the amount of payment (eg, the amount of payment). , 10,000), the selected payment method (PM3, for example, the card number of the A card: XXXX-XXXX-XXXX-XXXX), and the first authentication information ID1 may be transmitted to the server 300 (S160).
- the name of the electronic bill EB3 may mean information that may identify the A electronic bill or may include the information.
- the server 300 receives the name EB3, the payment amount, the selected payment method PM3, and the first authentication information ID1 of the selected electronic bill, and the authentication information Y for the selected payment method PM3. It can be read from the electronic bill information database 400 as the second authentication information. Since the server 300 generates a decryption key using the extracted recipient name and the extracted recipient address, the server 300 decrypts the authentication information Y by using the decryption key, and the first authentication information ( ID1) and the decrypted authentication information (Y) can be compared (S170).
- the server 300 displays the name EB3, the payment amount, and the selected payment method PM3 of the selected electronic bill.
- Payment information (PI) including a may be transmitted to the payment server 500 (S175).
- the payment server 500 may pay the payment amount using payment information PI, and transmit the payment result information to the server 300.
- the server 300 may store the payment result information in the electronic bill information DB 400.
- the payment server 500 may transmit payment result information to at least one of the A server 530, the server 300, and the terminal 100.
- the server 300 provides error information indicating that an error occurs through the network 200.
- the transmission may be performed at 100.
- the APP 110 may display the error information through the display device 130.
- step S155 when the authentication information (W, X, Y, and Z) is stored in the secure memory device of the terminal 100, the APP 110 and the first authentication information (ID1) in step S155 The authentication information Y stored in the secure memory device may be compared and the operation 160 may be performed only when the authentication information Y is matched. In this case, step S170 may or may not be performed to enhance security.
- FIG. 7 illustrates a data flow for explaining an operation method of the bill payment amount payment system shown in FIG. 1, and FIG. 8 illustrates a list of electronic bills displayed on a user's terminal according to the operation method illustrated in FIG. 7.
- a bill image of the bill 101 is generated (S210).
- the APP 110 installed in the terminal 100 detects the generation of the bill image and may be automatically executed according to the detection result (S215).
- the application for generating the bill image and the APP 110 may be implemented as different applications, the application and APP 110 may be implemented as a single application.
- the APP 110 determines that the bill image is stored in the memory device (eg, an image folder). Can be detected and executed automatically. 3 and 7 show that the APP 110 is executed after the bill image is generated according to the above-described premise, but when the application for generating the bill image and the APP 110 are implemented as one application, the APP After 110 is executed by the CPU of the terminal 100 by the user request, the APP 110 may generate a bill image corresponding to the photographed bill. That is, step S215 may be performed before step S210.
- the APP 110 may extract at least one of a 'recipient name' and a 'recipient address' from the bill image (S220).
- the APP 110 may transmit at least one of the extracted recipient name and the extracted recipient address to the server 300 through the network 200 (S225).
- the server 300 generates a decryption key using the extracted recipient name and the extracted recipient address, and the user of the terminal 100 (eg, from the electronic bill information database 400 accessible by the server 300).
- Search for the electronic bill list (LIST) for the electronic bill list (S230) decode the electronic bill list (LIST) including the information for the electronic bills (EB1 to EB4) using the decryption key, and decrypt the decrypted key.
- the electronic bill list LIST including information on the electronic bills EB1 to EB4 may be transmitted to the terminal 100 through the network 200 (S235).
- the method of displaying the electronic bills EB1 to EB4 on the display device 130 is as described with reference to FIGS. 4 and 5.
- the information T1 to T4 for each of the electronic bills EB1 to EB4 may include, but is not limited to, a name and a payment deadline for the electronic bill.
- the APP 110 may transmit selection information T1I for the selected electronic bill EB3 to the server 300 through the network 200 (S250).
- the server 300 receives the selection information T1I, the electronic bill information DB 400 corresponding to the electronic bill EB3 and the payment method PM3 mapped to the electronic bill EB3 corresponding to the received selection information T1I. Can be read from
- the server 300 may transmit the electronic bill EB3 and the payment means PM3 to the terminal 100 through the network 200 (S260).
- the APP 110 displays the name of the electronic bill EB3 shown in FIG. 6, the amount of payment (eg, 10,000) included in the electronic bill EB3, and the payment means PM3 on the display device 130.
- the user may request input of the authentication information ID1 (S265).
- the user may input first authentication information ID1 on a screen displayed on the display device 130 and click or touch the payment 145 shown in FIG. 6.
- the APP 110 When the APP 110 receives the first authentication information ID1 (S270), the APP 110 displays the name of the electronic bill EB3, the payment amount, the payment method PM3, and the first authentication information ID1. It may be transmitted to the server 300 via the network (200) (S275).
- the server 300 receives the name of the electronic bill EB3, the payment amount, the payment means PM3, and the first authentication information ID1, and transmits the authentication information Y for the payment means PM3 to the second.
- the electronic bill information DB 400 can be read as the authentication information.
- the server 300 Since the server 300 generates a decryption key using the extracted recipient name and the extracted recipient address, the server 300 decrypts the authentication information Y by using the decryption key, and the first authentication information ( ID1) and the decrypted authentication information Y may be compared (S280).
- the server 300 determines the name of the electronic bill EB3, the payment amount, and the payment means PM3. Including payment information (PI) may be transmitted to the payment server 500 (S285).
- the payment server 500 may pay the payment amount using payment information PI, and transmit the payment result information to the server 300.
- the server 300 may store the payment result information in the electronic bill information DB 400.
- the payment server 500 may transmit payment result information to at least one of the A server 530, the server 300, and the terminal 100.
- the server 300 provides error information indicating that an error occurs through the network 200. 100 may be transmitted to (S290).
- the APP 110 may display the error information through the display device 130.
- step S270 when the authentication information (W, X, Y, and Z) is stored in the secure memory device of the terminal 100, the APP 110 and the first authentication information (ID1) in step S270
- the authentication information Y stored in the secure memory device may be compared and the operation 280 may be performed only when the authentication information Y is matched. In this case, step S280 may or may not be performed to enhance security.
- FIG. 9 illustrates a data flow for explaining an operation method of the bill payment amount payment system shown in FIG. 1
- FIG. 10 illustrates payment means displayed on a user terminal according to the operation method illustrated in FIG. 9, and
- FIG. 11 Represents detailed information of the electronic bill displayed on the user's terminal shown in FIG. 1 when one electronic bill is selected from the electronic bills and one payment method is selected from the payment methods.
- the bill image for the bill 101 is generated by the camera 120 of the terminal 100 (S310), APP (installed in the terminal 100 ( When 110 is executed (S315), the APP 110 can extract the recipient name and the recipient address from the bill image (S320).
- the application for generating the bill image and the APP 110 may be implemented as different applications, the application and APP 110 may be implemented as a single application.
- the APP 110 determines that the bill image is stored in the memory device (eg, an image folder). Can be detected and executed automatically. 3, 7, and 9 illustrate that the APP 110 is executed after the bill image is generated according to the above-described premise, but the application for generating the bill image and the APP 110 are implemented as one application.
- the APP 110 may generate a bill image corresponding to the photographed bill. That is, step S315 may be performed before step S310.
- the APP 110 may transmit the extracted recipient name and the extracted recipient address to the server 300 through the network 200 (S325).
- the server 300 generates a decryption key using the extracted recipient name and the extracted recipient address, and the user (eg, Hong Gil-dong) from the electronic bill information DB 400 accessible by the server 300.
- the electronic bills EB1 to EB4 and payment methods PM1 to PM4 are searched and read (S330), and the decryption key is read from the electronic bills EB1 to EB4 and payment methods PM1 to PM4.
- Decoded using the electronic bills (EB1 ⁇ EB4) and the decrypted payment means (PM1 ⁇ PM4) can be transmitted to the terminal 100 via the network 200 (S335).
- each of the payment methods PM1 to PM4 is not mapped one-to-one with each of the electronic bills EB1 to EB4.
- the user may change the payment method for the A electronic bill EB3 to the payment method PM1 using the APP 110.
- the APP 110 receives the electronic bills EB1 to EB4, arranges the received electronic bills EB1 to EB4 as described with reference to FIGS. 4 and 5, and arranges the arranged electronic bills EB1 to EB4.
- the EB4 may be displayed on the display device 130 of the terminal 100 (S340).
- a user selects and pays the check box 141 shown in FIG. 4 or 5 to select one EB3 among the electronic bills EB1 to EB4 displayed on the display device 130 (145). It may be selected (S345).
- the APP 110 may display payment methods PM1 to PM4 on the display device 130 (S350).
- the user may select the check box 141-2 and select 149 to select any one of the payment methods PM1 to PM4 displayed on the display device 130 (S355). ).
- the APP 110 displays the name of the electronic bill EB3, the amount of payment, the date of payment, and the selected payment method PM1 on the display device 130, thereby displaying the first authentication information ID1.
- the user may request an input (S360).
- the user may input first authentication information ID1 on a screen displayed on the display device 130 and select payment 147.
- the APP 110 receives the first authentication information ID1 (S365), and the name of the electronic bill EB3 selected by the APP 110, the payment amount, and the selected payment.
- the means PM1 and the first authentication information ID1 may be transmitted to the server 300 through the network 200 (S370).
- the server 300 receives the name of the electronic bill EB3, the payment amount, the payment means PM1, and the first authentication information ID1, and transmits the authentication information W for the payment means PM1 to the second.
- the electronic bill information DB 400 can be read as the authentication information. Since the server 300 generates a decryption key based on the extracted recipient name and the extracted recipient address, the server 300 decrypts the authentication information W using the decryption key, and the first authentication information ( ID1) may be compared with the decrypted authentication information (W380).
- the server 300 determines the name of the electronic bill EB3, the payment amount, and the payment means PM1. Including payment information (PI) may be transmitted to the payment server 500 (S385).
- the payment server 500 may pay the payment amount using payment information PI, and transmit the payment result information to the server 300.
- the server 300 may store the payment result information in the electronic bill information DB 400.
- the payment server 500 may transmit payment result information to at least one of the A server 530, the server 300, and the terminal 100.
- the server 300 provides error information indicating that an error occurs through the network 200.
- the method may transmit the data to the 100.
- the APP 110 may display the error information through the display device 130.
- step S270 when the authentication information (W, X, Y, and Z) is stored in the secure memory device of the terminal 100, the APP 110 and the first authentication information (ID1) in step S270
- the authentication information W stored in the secure memory device may be compared and the operation 380 may be performed only when the authentication information W is matched. In this case, step S380 may or may not be performed to enhance security.
- the server 300 extracts the payment due date from each of the electronic bills EB1 to EB4 stored in the electronic bill information DB 400, compares the extracted payment due date with the current date, and the server 300
- the APP 110 may generate a notification window in response to the comparison result, and notify the user in the form of a message that the payment due date is imminent through the notification window.
- APP 110 may notify the user in the form of a message that the payment due date is imminent through the notification window before a certain period (eg, three days) from the payment due date (eg, December 15, 2015) of the electronic bill A. .
- the APP 110 may automatically insert the due date of each electronic bill (EB1 ⁇ EB4) to the schedule of the schedule management application in conjunction with the schedule management application. Therefore, the user does not have to input the due date of each electronic bill (EB1 ⁇ EB4) to the schedule of the schedule management application.
- the APP 110 may automatically extract a payment due date included in each of the electronic bills EB1 to EB4.
- the APP 110 compares the payment due date extracted for each of the electronic bills EB1 to EB4 and the current date, and when the payment due date of a specific electronic bill has elapsed among the electronic bills EB1 to EB4 according to the comparison result.
- the delayed interest for the particular electronic bill may be automatically calculated, and the new payment amount may be displayed on the display device 130 by adding the delayed interest and the payment amount included in the specific electronic bill.
- the present invention can be used in the method of paying the bill payment amount for the user using the application running on the server and the user's terminal.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Finance (AREA)
- Software Systems (AREA)
- Development Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
La présente invention concerne une application permettant d'effectuer un procédé de règlement d'un montant de paiement d'une facture pour un utilisateur à l'aide d'un serveur et d'une application exécutée dans un terminal d'utilisateur, qui extrait un nom de destinataire et une adresse de destinataire écrits sur la facture et transmet le nom de destinataire extrait et l'adresse de destinataire extraite au serveur. Le serveur peut fournir, à l'application, des factures électroniques facturées à l'utilisateur spécifié par le nom de destinataire extrait et l'adresse de destinataire extraite, ainsi qu'un moyen de paiement pour les factures électroniques. L'application peut utiliser une facture électronique choisie parmi les factures électroniques et un moyen de paiement mis en correspondance dans la facture électronique sélectionnée pour effectuer un règlement du montant de paiement de la facture électronique sélectionnée.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020160005954A KR101798023B1 (ko) | 2016-01-18 | 2016-01-18 | 고지서의 납부 금액을 결제하는 방법 |
KR10-2016-0005954 | 2016-01-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017126837A1 true WO2017126837A1 (fr) | 2017-07-27 |
Family
ID=59361906
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2017/000289 WO2017126837A1 (fr) | 2016-01-18 | 2017-01-09 | Procédé de règlement d'un montant de paiement de facture |
Country Status (2)
Country | Link |
---|---|
KR (1) | KR101798023B1 (fr) |
WO (1) | WO2017126837A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
IT201700110188A1 (it) * | 2017-10-03 | 2019-04-03 | Ppro S R L | Un metodo per controllare e gestire elettronicamente pagamenti e archiviazioni dati |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101951271B1 (ko) * | 2017-11-14 | 2019-02-22 | 주식회사 스마트솔루션 | 모바일 메신저 인증 기반의 실시간 지로 고지 및 납부 시스템과 그 방법 |
KR102004652B1 (ko) * | 2018-03-09 | 2019-07-29 | 김상오 | 자동차 등록번호 및 메신저 인증 기반의 모바일 고지 및 결제 시스템과 그 방법 |
KR102522576B1 (ko) | 2022-02-17 | 2023-04-14 | 엔에이치엔페이코 주식회사 | 전자고지서 및 종이고지서의 통합 관리 방법 및 단말 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010037297A1 (en) * | 2000-03-09 | 2001-11-01 | Mcnair Edward Parry | Bill paying with the aid of a scanner |
KR100851227B1 (ko) * | 2007-05-15 | 2008-08-07 | 에스케이 텔레콤주식회사 | 모바일 전자지로 관리 방법 및 시스템 |
KR20110133197A (ko) * | 2010-06-04 | 2011-12-12 | 주식회사 아레오네트웍스 | 고지서 처리 에이전트를 이용한 고지서의 전자적 처리 방법 및 시스템과 모바일 에이전트를 구비한 모바일 단말과 이를 위한 프로그램 기록매체 |
KR20120020699A (ko) * | 2010-08-31 | 2012-03-08 | 주식회사 비즈모델라인 | 바코드 기반 고지서 관리/납부 방법 및 무선단말과 이를 위한 프로그램 기록매체 |
WO2016007334A1 (fr) * | 2014-06-30 | 2016-01-14 | Shaaban Ahmed | Système et procédé de collecte automatisée de dettes pour entreprises |
-
2016
- 2016-01-18 KR KR1020160005954A patent/KR101798023B1/ko active IP Right Grant
-
2017
- 2017-01-09 WO PCT/KR2017/000289 patent/WO2017126837A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010037297A1 (en) * | 2000-03-09 | 2001-11-01 | Mcnair Edward Parry | Bill paying with the aid of a scanner |
KR100851227B1 (ko) * | 2007-05-15 | 2008-08-07 | 에스케이 텔레콤주식회사 | 모바일 전자지로 관리 방법 및 시스템 |
KR20110133197A (ko) * | 2010-06-04 | 2011-12-12 | 주식회사 아레오네트웍스 | 고지서 처리 에이전트를 이용한 고지서의 전자적 처리 방법 및 시스템과 모바일 에이전트를 구비한 모바일 단말과 이를 위한 프로그램 기록매체 |
KR20120020699A (ko) * | 2010-08-31 | 2012-03-08 | 주식회사 비즈모델라인 | 바코드 기반 고지서 관리/납부 방법 및 무선단말과 이를 위한 프로그램 기록매체 |
WO2016007334A1 (fr) * | 2014-06-30 | 2016-01-14 | Shaaban Ahmed | Système et procédé de collecte automatisée de dettes pour entreprises |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
IT201700110188A1 (it) * | 2017-10-03 | 2019-04-03 | Ppro S R L | Un metodo per controllare e gestire elettronicamente pagamenti e archiviazioni dati |
Also Published As
Publication number | Publication date |
---|---|
KR101798023B1 (ko) | 2017-11-16 |
KR20170086289A (ko) | 2017-07-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11544394B2 (en) | Information processing apparatus and method for processing information | |
WO2013137528A1 (fr) | Système de règlement de transaction hors-ligne, et procédé et dispositif à cet effet | |
CN110457957B (zh) | 电子票据的信息处理方法、装置、电子设备及介质 | |
WO2017126837A1 (fr) | Procédé de règlement d'un montant de paiement de facture | |
WO2013176474A1 (fr) | Application permettant d'utiliser un terminal de communication mobile à titre de terminal de paiement, procédé et système de fournisseur de services d'applications | |
CN106572091A (zh) | 发票信息传递生成方法及其系统 | |
US20130121490A1 (en) | Method and apparatus for trust based data scanning, capture, and transfer | |
WO2016153170A1 (fr) | Traitement de transactions pour versement direct utilisant un compte d'utilisateur | |
KR101168272B1 (ko) | 엔에프씨 티켓 발급 시스템 및 그 방법 | |
CN114329290B (zh) | 能力开放平台及其授权访问方法 | |
US20230043361A1 (en) | Modular data processing and storage system | |
CN109918865A (zh) | 一种基于区块链的摄影图片确权方法、装置及设备 | |
CA2958267A1 (fr) | Systeme et procede de gestion d'informations de beneficiaire | |
WO2013147484A1 (fr) | Système permettant d'utiliser des tickets de file d'attente et son procédé d'utilisation | |
WO2015069028A1 (fr) | Authentification multicanal, procédé de transfert financier et système utilisant un terminal de communication mobile | |
WO2018186713A1 (fr) | Procédé de souscription à un produit financier et système associé | |
CN109785138A (zh) | 一种支持数字货币与实物货币之间兑换的终端设备 | |
KR102243130B1 (ko) | 무인 출력 처리 시스템 | |
WO2010110625A2 (fr) | Procédé de service de portefeuille électronique et système basé sur une application d'écran de veille | |
US20230036355A1 (en) | Server apparatus, terminal, authentication system, authentication method, and storage medium | |
JP5853233B2 (ja) | 重複申込判定方法およびそのシステム | |
KR20170126830A (ko) | 고지서의 납부 금액을 결제하는 방법 | |
WO2017022916A1 (fr) | Dispositif et procédé de génération de document électronique | |
WO2017164613A1 (fr) | Procédé, système et dispositif de traitement de paiement | |
JP2007249690A (ja) | 会員管理システム、サービス提供端末、及びその方法 |
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: 17741603 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: 17741603 Country of ref document: EP Kind code of ref document: A1 |