TWM621128U - System for providing formal receipts - Google Patents

Abstract

A system for providing formal receipts is provided. The system includes a client electronic device, a receiving server, and a bank server. The receiving server stores a client bill corresponding to a client identification, and the client bill includes a bill amount and a receiving account corresponding to the receiving server. The bank server stores a client account corresponding to the client identification. The bank server transfers the bill amount from the client account to the receiving account. The bank server receives a formal receipt request including the client bill from the client electronic device. If the bank server includes a formal receipt corresponding to the client bill, the bank server provides the formal receipt to the client electronic device in response to receiving the formal receipt request.

Description

System for providing official receipts

This disclosure is about a system that provides formal receipts.

After the user pays the bill with the deposit in the bank account, the user can only know the transferred amount through the deposit transaction details. However, the user cannot obtain the official receipt provided by the payee. In other words, the user cannot confirm that the payee has received the payment. In addition, for users who need formal receipts (for example, formal receipts are required to write off/reimburse accounts), users must additionally apply for formal receipts from the payee, which is more inconvenient. Based on this, it is necessary to propose an improved system for providing formal receipts.

The present disclosure provides a system for providing formal receipts, which can improve the convenience for users to obtain formal receipts.

The system for providing official receipts disclosed in this disclosure includes electronic devices on the client side, a server on the receiving side, and a server on the bank side. The receiving end server stores the user bill corresponding to the user identification, and the user bill includes the bill amount and the receiving account number corresponding to the receiving end server; the bank end server communicates with the client electronic device and the receiving end Server, and store the user account corresponding to the user identification, wherein: in response to receiving a bill query request including the user identification from the electronic device on the client side, the bank-side server receives the user bill from the receiving-side server; The electronic device on the client side receives the payment request including the user identification and the user bill. The server on the bank side transfers the bill amount from the user account to the receiving account; the server on the bank side receives the official receipt including the user bill from the electronic device on the client side. Request; if the bank-side server includes an official receipt corresponding to the user's bill, the bank-side server provides the official receipt to the user-side electronic device in response to receiving the official receipt request.

Based on the above, the system for providing official receipts of the present disclosure can provide the official receipt (via the bank server) to the user after the receiving end server receives the bill amount paid by the user and generates an official receipt. The user can also retrieve the barcode (generated by the bank-side server) to obtain an official receipt. In addition, if the receiving end server has not generated an official receipt, the receiving end server can notify the user (via the bank server) of the processing status of the official receipt, thereby improving the convenience for the user to obtain an official receipt.

In order to make the above-mentioned features and advantages of the present disclosure more comprehensible, the following specific embodiments are described in detail in conjunction with the accompanying drawings.

FIG. 1 is a schematic diagram of a system 10 for providing formal receipts according to an exemplary embodiment of the present disclosure. Please refer to FIG. 1, the system 10 includes a user-side electronic device 100, a receiving-side server 200 and a bank-side server 300. The bank server 300 is communicatively connected to the client electronic device 100 and the payment server 200.

The client electronic device 100, the receiving server 200, and the bank server 300 are, for example, a personal computer, a smart phone, a tablet computer, or other similar devices. The client electronic device 100, the receiving server 200, and the bank server 300 can all include a communication chip (not shown in the figure), a storage device (not shown in the figure), and a processing module (not shown in the figure) In the picture).

The communication chip can support Global System for Mobile communication (GSM), Personal Handy-phone System (PHS), Code Division Multiple Access (CDMA) system, and broadband code division. Multiple access (WCDMA, Wideband Code Division Multiple Access) system, Long Term Evolution (LTE, Long Term Evolution) system, Worldwide interoperability for Microwave Access (WiMAX, Worldwide interoperability for Microwave Access) system, Wireless Fidelity (Wi-Fi, Wireless Fidelity) ) system, the fifth generation of mobile communication network ^{(5G, 5 th Generation Mobile Network} ) system, or component signal transmission Bluetooth.

The storage device can be any type of fixed or removable random access memory (RAM, Random Access Memory), read-only memory (ROM, Read-Only Memory), flash memory (flash memory), hard disk ( HDD, Hard Disk Drive), Solid State Drive (SSD, Solid State Drive) or similar components or a combination of the above components.

The processing module can be a central processing unit (CPU, Central Processing Unit), or other programmable general-purpose or special-purpose microprocessor (Microprocessor), digital signal processor (DSP, Digital Signal Processor), programmable Integrated circuit (ASIC, Application Specific Integrated Circuit) or other similar components or a combination of the above components.

In this embodiment, the payee server 200 may be set by the payee (for example, the telecommunication service provider used by the user) who pays the bill.

The payee server 200 may store a user bill corresponding to the user identification (e.g., a telecommunication bill of the user). The user identification is, for example, the user's ID card number.

The user bill may include the bill amount and the receiving account number corresponding to the receiving terminal server 200. In addition, user bills can also include payment deadlines and payment status. The payment status may include, for example, different statuses such as unpaid and overdue, unpaid and overdue (and no late fee), unpaid and overdue (and overdue amount).

The bank server 300 may store a user account (for example, a bank account) corresponding to the user identification.

When the user wants to use the user account of his bank to pay (for example, to pay the telecommunications bill fee), the user can input the user identification to the user-side electronic device 100 to check the bill status first. For example, the user can enter the user ID to log in to online banking or online ATM. The electronic device 100 on the client side may send a bill query request including the user identification to the server 300 on the bank side.

The bank-side server 300 can send the bill query request to the receiving-side server 200. Then, the payee server 200 can obtain the corresponding user bill according to the user identification (in the bill query request), and send the user bill to the bank server 300.

The bank-side server 300 may transmit the bill query result screen including the user's bill to the user-side electronic device 100 so that the user-side electronic device 100 can display it to the user. The bill query result screen may include the aforementioned bill amount, payment deadline, and payment status. In other words, the bill query result of the system 10 for providing formal receipts of the present disclosure may include bills of various payment statuses of the user (as described above).

After the user terminal electronic device 100 displays the bill query result screen to the user, the user can select the bill to be paid with his user account (bank account) from the bill query result screen. Then, the electronic device 100 on the client side may send a payment request including the user identification and the user bill to the server 300 on the bank side. After receiving the payment request, the bank-side server 300 may transfer the bill amount from the user account to the receiving account (corresponding to the receiving-side server 200).

After the payee server 200 (the manager of) confirms that the payee account has received the payment, the payee server 200 may generate a formal receipt corresponding to the user's bill.

FIG. 2 is a schematic diagram of a formal receipt 20 according to an exemplary embodiment of the present disclosure. As shown in FIG. 2, the official receipt 20 may include a receipt stamp 201 corresponding to the payment terminal server 200. For example, the payee server 200 can attach a receipt stamp 201 to the electronic file (graphic file) of the user's bill as a formal receipt.

In addition, the official receipt generated by the receiving end server 200 may also include an anti-counterfeiting label (corresponding to the receiving end server 200).

In another embodiment, the payee server 200 may use digital signature technology (Digital Signature) to generate a formal receipt. For example, the user can apply to the payee who sets up the payee server 200 in advance, so that the payee server 200 uses key technology (public key/private key) to generate the specific user (specific client electronic device). 100) Official receipt.

After the official receipt is generated, the receiving end server 200 may send the official receipt to the bank end server 300.

FIG. 3 is a schematic diagram of requesting a formal receipt according to an exemplary embodiment of the present disclosure.

When the user wants to obtain the official receipt (for bills paid), the user can query the bill payment record for a specific period (see Figure 3 for period 30) as shown in Figure 3 (in online banking or online ATM) , And after selecting the specific paid bill 31, select the interface 32 to request an official receipt from the bank server 300. Then, the electronic device 100 on the client side may send a formal receipt request including the user bill to the server 300 on the bank side.

Since the bank server 300 already includes the official receipt 20 of FIG. 2 (that is, the bank server 300 has received the official receipt 20 from the receiving server 200), the bank server 300 receives the official receipt 20 from the client electronic device 100 After receiving the official receipt request, the bank-side server 300 can provide the official receipt 20 to the user-side electronic device 100.

In another embodiment, the bank server 300 (or the receiving server 200) can store the official receipt 20 on a specific web page (this web page corresponds to a specific web address). The bank server 300 can generate the official receipt barcode including the specific website address, and provide the official receipt barcode to the client electronic device 100. The user can retrieve the official receipt barcode via the client electronic device 100 to obtain the website address, and use the website address to connect to the web page to obtain the official receipt.

In another embodiment, it is assumed that (the administrator of) the receiving end server 200 requires a long operation time (for example, the third day after the user makes the payment) to confirm that the receiving account has received the payment (ie, the receiving end The server 200 needs a longer operation time to generate an official receipt). If the client electronic device 100 sends (for example, the user sends immediately after the payment is completed) a formal receipt request to the bank server 300 before this working time, since the payment server 200 has not yet generated a formal receipt (that is, the receipt The cashier server 200 has not sent the official receipt to the bank server 300), and the bank server 300 cannot provide the official receipt to the client electronic device 100 at this time.

In this case, the bank-side server 300 can confirm to the receiving-side server 200 that it has not yet generated an official receipt, and the bank-side server 300 can obtain the current status of the receiving-side server 200 processing the official receipt. Then, the bank server 300 can send a formal receipt processing status message to the client electronic device 100.

The official receipt processing status message may indicate, for example, the estimated time (for example, the third day after the user makes a payment) that the bank-side server 300 can provide the official receipt to the user-side electronic device 100. Based on this, the user can again (as described in the foregoing embodiment) use the user-side electronic device 100 to send a formal receipt request to the bank-side server 300 at the estimated time.

On the other hand, suppose the receiving end server 200 confirms that the receiving account has received the payment in advance (for example, the second day after the user makes the payment) and the official receipt is generated, the receiving end server 200 can send the official receipt to the bank. The server 300 allows the bank server 300 to send the official receipt to the client electronic device 100 (in other words, there is no need for the client electronic device 100 to send the official receipt request to the bank server 300 again).

In addition, the bank server 300 can set a storage period (for example, 2 years) for the official receipt. After the bank server 300 receives a specific official receipt from the receiving server 200, the bank server 300 may delete the official receipt 2 years after the date of receipt.

It should be noted that the foregoing embodiment takes as an example the storage of a single telecommunication bill of a specific user by the payee server 200 as an example, but the present disclosure does not limit this. For example, the payee server 200 may also store multiple telecommunication bills of a specific user. Alternatively, the number of servers at the receiving end can also be multiple (for example, server A at the receiving end can store the user's telecommunications bill, and server B at the receiving end can store the user's water bill). These implementation examples can also be implemented in a manner similar to the above-mentioned embodiments, and will not be repeated here.

FIG. 4 is a schematic diagram of a system 40 for providing formal receipts according to another exemplary embodiment of the present disclosure.

The difference between FIG. 4 and FIG. 1 is that the receiving end server 200a~the receiving end server 200c of the system 40 can be set up by different receiving companies. In addition, because the bank server 300 (because it does not have a business relationship with the various businesses that set up the beneficiary server 200a~the beneficiary server 200c) cannot directly connect to the beneficiary server 200a ~Receiving end server 200c, in order to allow the bank end server 300 to receive the bills and/or official receipts in the foregoing embodiment from the receiving end server 200a~receiving end server 200c, respectively, the bank end server 300 It can be connected to the payment provider server 400 (for example, the national payment network), and the bills and/or official receipts in the foregoing embodiments are respectively received through the payment provider server 400.

FIG. 5 is a flowchart of a method for providing a formal receipt according to an exemplary embodiment of the present disclosure.

In step S501, in response to receiving a bill query request including user identification from the electronic device on the client side, the bank-end server receives the user bill from the beneficiary server, wherein the beneficiary server stores information corresponding to the user identification. The user bill, and the user bill includes the bill amount and the receiving account number corresponding to the receiving end server, wherein the bank end server stores the user account corresponding to the user identification.

In step S502, in response to receiving a payment request including a user identification and a user bill from the electronic device on the user side, the bank server transfers the amount of the bill from the user account to the receiving account.

In step S503, the bank-side server receives the official receipt request including the user's bill from the user-side electronic device.

In step S504, if the bank-side server includes an official receipt corresponding to the user's bill, the bank-side server provides the official receipt to the user-side electronic device in response to receiving the request for obtaining the official receipt.

In summary, the system for providing official receipts of the present disclosure can provide the official receipt (via the bank server) to the user after the receipt server receives the bill amount paid by the user and generates the official receipt. The user can also retrieve the barcode (generated by the bank-side server) to obtain an official receipt. In addition, if the receiving end server has not generated an official receipt, the receiving end server can notify the user (via the bank server) of the processing status of the official receipt, thereby improving the convenience for the user to obtain an official receipt.

Although this disclosure has been disclosed in the above embodiments, it is not intended to limit this disclosure. Anyone with ordinary knowledge in the relevant technical field can make some changes and modifications without departing from the spirit and scope of this disclosure. Therefore, The scope of protection of this disclosure shall be subject to those defined by the attached patent scope.

10.40: System to provide formal receipts 100: Client electronic device 200, 200a~200c: Receiving terminal server 300: Bank-side server 20: Official receipt 201: Receipt Chapter 30: To query the period 31: The bill has been paid 32: Interface 400: Payer's server S501~S504: steps

FIG. 1 is a schematic diagram of a system for providing formal receipts according to an exemplary embodiment of the present disclosure. Fig. 2 is a schematic diagram of a formal receipt according to an exemplary embodiment of the present disclosure. FIG. 3 is a schematic diagram of requesting a formal receipt according to an exemplary embodiment of the present disclosure. FIG. 4 is a schematic diagram of a system for providing official receipts according to another exemplary embodiment of the present disclosure. FIG. 5 is a flowchart of a method for providing a formal receipt according to an exemplary embodiment of the present disclosure.

10: A system to provide official receipts

100: Client electronic device

200: Receiving end server

300: Bank-side server

Claims (7)

A system for providing official receipts, including: A client electronic device; A receiving end server storing a user bill corresponding to a user identification, and the user bill includes a bill amount and a receiving account number corresponding to the receiving end server; and A bank-side server, which is communicatively connected to the user-side electronic device and the receiving-side server, and stores a user account corresponding to the user identification, wherein: In response to receiving a bill query request including the user identification from the user-end electronic device, the bank-end server receives the user bill from the receiving-end server; In response to receiving a payment request including the user identification and the user bill from the user-side electronic device, the bank-side server transfers the bill amount from the user account to the collection account ； Receiving, by the bank-side server, a formal receipt request including the user bill from the user-side electronic device; If the bank-side server includes an official receipt corresponding to the user bill, the bank-side server provides the official receipt to the user-side electronic device in response to receiving the official receipt request. The system for providing formal receipts according to claim 1, wherein the user bill further includes a payment period and a payment status, wherein: The bank-side server transmits a bill query result screen including the user's bill to the user-side electronic device, and the bill query result screen includes the bill amount, the payment deadline, and the Payment status. The system for providing formal receipts as described in claim 1, in which: If the receiving account has received the payment, the receiving terminal server generates the official receipt corresponding to the user bill; The bank-side server receives the official receipt from the receiving-side server. The system for providing formal receipts as described in claim 3, in which: The receiving terminal server uses a digital signature technology to generate the official receipt. The system for providing an official receipt according to claim 1, wherein the official receipt includes a receipt corresponding to the server of the payment terminal. The system for providing official receipts according to claim 1, wherein the official receipt is stored in a web page, and the web page corresponds to a website address, wherein: The bank-side server generates an official receipt barcode including the website address; The client electronic device retrieves the official receipt barcode to obtain the website address, and uses the website address to connect to the web page to obtain the official receipt. The system for providing formal receipts as described in claim 1, in which: If the bank-side server does not include the official receipt and the receiving-side server does not include the official receipt, the bank-side server sends an official receipt processing status message in response to receiving the official receipt request To the electronic device on the client side.

Images