TWM664282U - Payment service management system - Google Patents

Abstract

A payment service management system includes a central server and a operation device. The central server electrically connects to plural electronic payment service servers. The operation device electrically or wirelessly connects to the central server, and includes a verification interface and a management interface. The verification interface is configured to input a verification data such that the central server verifies the operation device by using the verification data. The management interface is configured to display a service list, in which the service list is configured to list the electronic payment service servers.

Description

Payment Service Management System

This disclosure relates to a payment service management system.

With the popularity of handheld electronic devices such as mobile phones and tablet computers, various electronic payment services that use these handheld electronic devices for small transactions are becoming more and more common. Among the various electronic payment services provided by multiple operators, a considerable portion of electronic payment services allow users to bind with the online banking services provided by banking operators, making functions such as fee deduction more convenient.

If users want to use electronic payment services provided by multiple operators, they may bind multiple electronic payment services to the same online banking service account. However, even if they are bound to the same online banking service, these electronic payment services are often managed by the software or operating interface launched by each operator, which may cause a certain degree of inconvenience to users.

According to an embodiment of the present disclosure, a payment service management system includes a central server and an operating device. The central server is electrically connected to a plurality of electronic payment servers. The operating device is electrically or wirelessly connected to the central server and includes a verification interface and a management interface. The verification interface is configured to input verification data so that the central server verifies the operating device through the verification data. The management interface is configured to display a service list, wherein the service list is configured to list the electronic payment servers.

In one embodiment, the service list displayed by the management interface is configured to list the electronic payment servers as the electronic payment servers bound to the operating device verified by the central server.

In one embodiment, the operating device is configured to send an unbinding instruction corresponding to one of the electronic payment servers to the central server.

In one embodiment, the unbinding instruction sent by the operating device is configured so that when the central server receives a request instruction from the electronic payment server corresponding to the unbinding instruction, the central server sends a rejection instruction to the electronic payment server.

In one embodiment, the rejection command sent by the central server is configured to unbind the electronic payment server and the operating device.

In one embodiment, the management interface further includes a plurality of release options. The plurality of release options correspond to a plurality of electronic payment servers displayed in the service list, and are configured to control the operating device to send release instructions corresponding to the electronic payment servers to the central server.

In one embodiment, the service list displayed by the management interface is configured to list the time when the electronic payment server is bound to the operating device.

In one embodiment, the management interface is configured to be opened by sending authentication data to the central server for authentication via the authentication interface.

In one embodiment, the verification data input into the verification interface includes a code and a password, wherein the code corresponds to the operating device.

In one embodiment, the operating device is a handheld electronic device.

In the above-mentioned payment service management system, after the user authenticates the operating device through the authentication interface, the central server can manage all bound electronic payment services at the same time in the management interface, thus eliminating the trouble of opening multiple operation interfaces separately.

100: Payment service management system

110: Central Server

200: Operating device

210: Verification interface

212: Input area

220: Management interface

222: Service list

224: Uncheck option

300:Menu interface

310:Options

S: Electronic payment server

S1, S2, S3: Steps

The present disclosure is best understood from the following embodiments when read in conjunction with the accompanying illustrations. Note that in accordance with standard practice in the industry, the various features are not drawn to scale. In fact, the dimensions of the various features may be arbitrarily increased or decreased for clarity of discussion.

Figure 1 is a block diagram of a payment service management system according to an embodiment of the present disclosure

Figure 2 is a schematic diagram of the verification interface in Figure 1.

Figure 3 is a schematic diagram of a menu interface according to an embodiment of the present disclosure.

Figure 4 is a schematic diagram of the management interface in Figure 1.

Figure 5 is a flow chart of the unbinding instruction according to an embodiment of the present disclosure.

The following disclosure provides many different embodiments or examples for implementing different features of the described subject matter. Specific examples of components and configurations are described below to simplify the description. Of course, these are merely examples and are not limiting. For example, forming a first feature on or above a second feature in the subsequent description may include embodiments in which the first feature and the second feature are formed in direct contact, and may also include embodiments in which additional features may be formed between the first feature and the second feature, so that the first feature and the second feature may not be in direct contact. In addition, the disclosure may repeat reference numbers and/or reference letters in multiple examples. Such repetition is for the purpose of simplicity and clarity, and does not in itself indicate a relationship between the multiple embodiments and/or configurations discussed.

Spatially relative terms such as "under", "beneath", "bottom", "over", "top", etc. may be used herein for descriptive purposes to describe the relationship of one element or feature to another element or feature as shown in the accompanying figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation other than the orientation shown in the accompanying figures. The device may be oriented in other ways (rotated 90 degrees or in other orientations) and the spatially relative descriptors used herein may be interpreted accordingly.

FIG. 1 is a block diagram of a payment service management system 100 according to an embodiment of the present disclosure. Referring to FIG. 1, the payment service management system 100 includes a central server 110 and an operating device 200. The central server 110 is electrically connected to a plurality of electronic payment servers S. In this embodiment, the central server 110 may be configured to provide online banking services, and the electronic payment servers S may provide electronic payment services of a plurality of operators respectively. The operating device 200 is connected to the central server 110. In this embodiment, the operating device 200 is a handheld electronic device, and the operating device 200 is wirelessly connected to the central server 110. In other embodiments, the operating device 200 may be electrically connected to the central server 110.

The operating device 200 includes an authentication interface 210 and a management interface 220. The authentication interface 210 can be used to input authentication data, so that the central server 110 can authenticate the identity of the operating device 200 or the user of the operating device 200 through the authentication data. In this embodiment, the authentication data may include a code and a password, and the code corresponds to the operating device 200 (or the user of the operating device 200). In other embodiments, the authentication data may also include biometric authentication data (such as fingerprint authentication data, facial authentication data, etc.) or quick response code (QR code) authentication data, etc.

The management interface 220 is opened by transmitting the verification data to the central server 110 through the verification interface 210. Specifically, the user inputs the verification data in the verification interface 210, and after the verification data is transmitted to the central server 110 through the connection between the operating device 200 and the central server 110, the operating device 200 can open the management interface 220 after verification by the central server 110. In other words, the verification interface 210 allows the user of the operating device 200 to log in to the online banking service provided by the central server 110 through the verification of the central server 110, and can open the management interface 220 for operation. In some embodiments, after the verification interface 210 transmits the verification data to the central server 110, other interfaces (such as a menu interface) may be opened, and the management interface 220 is opened through the other interfaces opened by the verification interface 210.

FIG. 2 is a schematic diagram of the verification interface 210 in FIG. 1. Referring to FIG. 2, the verification interface 210 includes a plurality of input areas 212. In this embodiment, at least two of the input areas 212 are configured to input a code of verification data and a password of verification data. In this embodiment, other input areas 212 can be configured to input data such as a verification code or an ID number.

FIG. 3 is a schematic diagram of a menu interface 300 according to an embodiment of the present disclosure. In this embodiment, after the verification information is input in the verification interface 210 in FIG. 2, the menu interface 300 is opened. The menu interface 300 includes a plurality of options 310. In this embodiment, one of the options 310 corresponds to opening the management interface 220 in FIG. 1. In some embodiments, other options 310 may correspond to other operations related to online banking services, such as opening a payment function, etc. This allows the operating device 200 (see FIG. 1) to integrate more functions related to online banking services, so that after the user logs into the online banking service provided by the central server 110 (see FIG. 1) through the verification interface 210 (see FIG. 2), he can also perform other operations related to online banking services, thereby improving the overall convenience.

FIG. 4 is a schematic diagram of the management interface 220 in FIG. 1. Referring to FIG. 1 and FIG. 4 at the same time, the management interface 220 is configured to display a service list 222. The service list 222 is configured to list the electronic payment server S in FIG. 1, and the electronic payment server S listed in the service list 222 is the electronic payment server S bound to the operating device 200 verified by the central server 110. In this embodiment, the service list 222 lists a plurality of electronic payment operator names representing a plurality of electronic payment servers S, that is, the service list 222 lists the electronic payment operator names bound to the operating device 200 (or the user of the operating device 200). The service list 222 also lists the time when the electronic payment server S is bound to the operating device 200. Such a service list 222 allows the user to confirm all bound electronic payment services in the same interface (i.e., management interface 220) without having to open the software provided by each electronic payment service provider for confirmation.

The management interface 220 further includes a plurality of release options 224. The release options 224 correspond to the electronic payment server S (refer to FIG. 1) displayed in the service list 222 or the name of the electronic payment operator representing the electronic payment server S. The release option 224 is configured to control the operating device 200 to send the corresponding electronic payment server S release command to the central server 110 in FIG. 1.

FIG. 5 is a flow chart of an unbinding instruction according to an embodiment of the present disclosure. Referring to FIG. 5 and FIG. 1, in step S1, the operating device 200 transmits an unbinding instruction corresponding to one of the electronic payment servers S to the central server 110. Then, in step S2, after receiving the unbinding instruction, the central server 110 marks the electronic payment server S corresponding to the unbinding instruction. Then, in step S3, when the central server 110 receives a request instruction (including top-up, withdrawal or other instructions) from the marked electronic payment server S (that is, the electronic payment server S corresponding to the unbinding instruction), it returns a rejection instruction to the electronic payment server S, thereby blocking the request instruction of the electronic payment server S and achieving the purpose of unbinding.

In this embodiment, the rejection instruction simultaneously releases the binding between the electronic payment server S and the operating device 200. Specifically, when the electronic payment server S receives the rejection instruction, it is equivalent to notifying the electronic payment operator that the operating device 200 releases the binding with the electronic payment server S, so that the user side, the bank side (i.e., the central server 110) and the electronic payment operator side can all uniformly eliminate the binding relationship between the electronic payment server S and the operating device 200.

The above-mentioned unbinding command operation process allows the user to not only confirm all bound electronic payment services in a single interface (i.e., management interface 220), but also unbind any bound electronic payment service without opening other interfaces, thereby providing the user with a more convenient management method.

In summary, in the payment service management system 100, after the user has the central server 110 verify the operating device 200 through the verification interface 210, all bound electronic payment services can be managed simultaneously in the management interface 220, thereby eliminating the trouble of opening multiple software or operating interfaces separately. In addition, the payment service management system 100 provides a release option 224 (see Figure 4) corresponding to each electronic payment service, so the operation of releasing the binding between the electronic payment service and the online banking account is more convenient.

The foregoing summarizes the features of several embodiments so that those skilled in the art can better understand the various aspects of the present disclosure. Those skilled in the art should understand that they can easily use the present disclosure as a basis for designing or modifying other methods and structures for achieving the same purpose and/or obtaining the same advantages of the embodiments introduced herein. Those skilled in the art should also recognize that such equivalent structures do not depart from the spirit and scope of the present disclosure, and that they can be variously changed, substituted, and modified herein without departing from the spirit and scope of the present disclosure.

100: Payment service management system

110: Central Server

200: Operating device

210: Verification interface

220: Management interface

S: Electronic payment server

Claims (10)

A payment service management system comprises: A central server electrically connected to a plurality of electronic payment servers; and An operating device electrically or wirelessly connected to the central server and comprising: A verification interface configured to input a verification data so that the central server verifies the operating device by the verification data; and A management interface configured to display a service list, wherein the service list is configured to list the electronic payment servers. A payment service management system as described in claim 1, wherein the service list displayed by the management interface is configured to list the electronic payment servers as the electronic payment servers bound to the operating device verified by the central server. A payment service management system as described in claim 2, wherein the operating device is configured to send an unbinding instruction corresponding to one of the electronic payment servers to the central server. A payment service management system as described in claim 3, wherein the unbinding instruction sent by the operating device is configured so that when the central server receives a request instruction from the electronic payment server corresponding to the unbinding instruction, the central server sends a rejection instruction to the electronic payment server. A payment service management system as described in claim 4, wherein the rejection instruction sent by the central server is configured to unbind the electronic payment server and the operating device. The payment service management system as described in claim 3, wherein the management interface further comprises: A plurality of release options, each corresponding to the electronic payment servers displayed in the service list, configured to control the operating device to transmit the release instructions corresponding to the electronic payment servers to the central server. A payment service management system as described in claim 1, wherein the service list displayed by the management interface is configured to list a time when the electronic payment server is bound to the operating device. A payment service management system as described in claim 1, wherein the management interface is configured to be opened by transmitting the verification data to the central server for verification via the verification interface. A payment service management system as described in claim 1, wherein the verification data input into the verification interface includes a code and a password, wherein the code corresponds to the operating device. A payment service management system as described in claim 1, wherein the operating device is a handheld electronic device.