TWI695337B - Method of binding a credit card and transaction system - Google Patents

Abstract

When a first server of a transaction system receives from a user-terminal a credit card binding request which includes identity data, the first server transfers a target wallet user identity data which matches the identity data to a second server of the transaction system. The second server elects target credit card holder data which matches the target wallet user identity data and transfers a bindable credit card list which includes target credit card data corresponding to the target credit card holder data to the user-terminal. The second server transfers the target credit card data to the first server upon receiving a binding command from the user-terminal. The first server generates and storages binding credit card data which includes the target credit card data and is corresponding to the target wallet user identity data.

Description

Credit card binding method and transaction system

The invention relates to a credit card binding method, in particular to a credit card binding method involving network communication technology. The invention also relates to a transaction system capable of implementing the credit card binding method.

Existing e-wallets usually provide a credit card binding function. If a user binds a credit card held by them to an e-wallet account, if they use the e-wallet account for consumption in the future, it is equivalent to using the The credit card consumption of the e-wallet account. However, when binding a credit card to an e-wallet account, it is usually necessary to enter the card number, valid year and month, and security check code of the credit card. If the user does not memorize the credit card number, valid year, month, and security check code data , And the credit card is just not at hand, the user needs to find the credit card to continue the binding operation, which makes the existing technology inconvenient.

Therefore, one of the objects of the present invention is to provide a credit card binding method that can improve the inconvenience of the prior art.

Therefore, the credit card binding method of the present invention is implemented by a transaction system, which is suitable for a user terminal to be electrically connected and includes a first server and a second server, where the first server stores multiple records corresponding to The wallet user identification data of multiple e-wallet accounts. The second server stores multiple credit card data and multiple card account identification data corresponding to the credit card data. The credit card binding method includes the following steps: (A) the first When a server receives a credit card binding request from the user end and contains an identity data, and determines that there is a target wallet user identification data in the wallet user identification data that matches the identity data, the server uses the target Wallet user identification data is sent to the second server; (B) The second server receives the target wallet user identification data from the first server and determines that the cardholder identification data exists with the After a target card account identification data that matches the target wallet user identification data, a binding credit card list is generated and transmitted to the user terminal, and the binding card list includes the credit card information corresponding to the target card account identification data. The credit card data as a target credit card data; (C) after receiving a binding instruction from the user terminal indicating the target credit card data, the second server transmits the target credit card data to the first credit card data Server; (D) When the first server receives the target credit card data from the second server, it generates and stores a bound credit card data containing the target credit card data and corresponding to the target wallet user identification data.

In some embodiments of the credit card binding method of the present invention, each card user identification data includes at least one communication data corresponding to a mobile device. In step (B), the second server determines the card users When the target cardholder identification data exists in the identification data, a one-time password is first generated, and according to the communication data contained in the target cardholder identification data, the one-time password is transmitted to the corresponding mobile device, the The second server generates and transmits the list of bindable credit cards to the user terminal when it receives a verification password from the user terminal and determines that the verification password is consistent with the one-time password.

In some embodiments of the credit card binding method of the present invention, in step (B): when the second server determines that the target card account identification data does not exist in the card account identification data, the first server is controlled The device generates and sends a first warning notification to the user end; when the second server receives the verification password and determines that the verification password does not match the one-time password, generates and sends a verification password related to the verification password A second warning notification to the user end; when the second server determines that it receives the verification password and determines that the verification password does not match the one-time password a predetermined number of times, it generates and transmits a The third warning notification related to the verification password is notified to the user terminal.

In step (C), when the second server receives the binding instruction, and determines that the target credit card data is not passed a credit card opening procedure and is not allowed to be used in the specific electronic wallet application In the state of consumption, the second server also sets the target credit card data to a state that has not passed the credit card opening procedure but is allowed to be used for consumption in the specific electronic wallet application.

In some embodiments of the credit card binding method of the present invention, in step (A), when the first server determines that the target wallet user identification data does not exist in the wallet user identification data, the first server The device generates and sends an identification failure notification to the user end.

Another object of the present invention is to provide a transaction system that can implement the credit card binding method.

The transaction system of the present invention is suitable for a user terminal to be electrically connected. The transaction system includes a first server and a second server. The first server stores a plurality of wallet user identification data respectively corresponding to multiple electronic wallet accounts , The second server is electrically connected to the first server, and stores a plurality of credit card data and a plurality of credit card identification data corresponding to the credit card data, respectively. When the first server receives a credit card binding request from the user terminal and contains an identity data, and determines that there is a target wallet user identification data in the wallet user identification data that matches the identity data, it will The target wallet user identification data is sent to the second server. After the second server receives the target wallet user identification data from the first server, and determines that there is a target card account identification data in the card account identification data that matches the target wallet user identification data, A binding credit card list is generated and transmitted to the user terminal. The binding credit card list includes the credit card data corresponding to the target card account identification data in the credit card data and used as a target credit card data. After receiving a binding instruction from the user terminal and indicating the target credit card data, the second server transmits the target credit card data to the first server. When receiving the target credit card data from the second server, the first server generates and stores a bound credit card data containing the target credit card data and corresponding to the target wallet user identification data.

In some embodiments of the transaction system of the present invention, each cardholder identification data includes at least one communication data corresponding to a mobile device, and the second server determines that the target cardholder exists in the cardholder identification data When identifying data, a one-time password is first generated, and the one-time password is transmitted to the corresponding mobile device according to the communication data included in the target card user identification data, and the second server receives the When a verification password from the user terminal is judged to be consistent with the one-time password, the list of bindable credit cards is generated and transmitted to the user terminal.

In some implementations of the transaction system of the present invention, when the second server determines that the target cardholder identification data does not exist in the cardholder identification data, the first server is controlled to generate and send a first warning notification To the user end; when the second server receives the verification password and determines that the verification password does not match the one-time password, generates and sends a second alert notification related to the verification password to the user end ; When the second server determines that it has received the verification password and determines that the number of times the verification password does not match the one-time password reaches a predetermined number of times, it generates and transmits a third alert related to the verification password Notify the user.

In some embodiments of the transaction system of the present invention, when the second server receives the binding instruction, and determines that the target credit card information is not through a credit card opening procedure and is not allowed in the specific electronic wallet When the application is used for consumption, the second server also sets the target credit card data to a state that has not passed the credit card opening procedure but is allowed to be used for consumption in the specific electronic wallet application .

In some embodiments of the transaction system of the present invention, when the first server determines that the target wallet user identification data does not exist in the wallet user identification data, the first server generates and sends a body identification failure notification To the end of use.

The effect of the present invention is that when a user wants to bind a credit card he holds to an electronic wallet account, he only needs to send the credit card binding request including the identity data to the first server through the user terminal , The first server sends the target wallet user identification data that matches the identity data to the second server, so that the second server selects the target card account that matches the target wallet user identification data Identify the data, and return the list of bindable credit cards containing the target credit card data corresponding to the target card account identification data to the user end, so that the user only needs to select the desired binding by the user end Credit card and send the binding instruction indicating the target credit card data to the second server, so that the second server can transmit the target credit card data to the first server, thereby enabling the first server The device stores the bound credit card data containing the target credit card data and corresponding to the target wallet user identification data to complete the binding between the credit card and the e-wallet account, so that the user does not need to enter the credit card number and expiration year The data such as the month and the security check code can easily and quickly complete the binding, and completely overcome the inconvenience of using the existing technology.

Before the present invention is described in detail, it should be noted that the "electrical connection" in this patent specification refers to the wired electrical connection between electronic devices/devices/elements connected by a conductor, and the data transmission through wireless communication. Radio connection.

Referring to FIG. 1, an embodiment of the transaction system 1 of the present invention is managed by a banking unit, for example, and the transaction system 1 is suitable for multiple users 5 (only one shown in FIG. 1) via the Internet. connection. For ease of understanding, the following uses only the user terminal 5 shown in FIG. 1 as an example. The user terminal 5 may be, for example, a smartphone, a tablet computer, a notebook computer, or a desktop computer, but not This is the limit.

The transaction system 1 includes a first server 11 and a second server 12 electrically connected to the first server 11. In this embodiment, the first server 11 is, for example, implemented as an electronic wallet transaction server related to a specific type of electronic wallet, and stores multiple wallet user identification data, and multiple corresponding user IDs of the wallets respectively E-wallet account of information.

In this embodiment, the wallet user identification data and the electronic wallet accounts correspond to multiple users, respectively. Taking the user terminal 5 as an example, assuming that the user terminal 5 is held by a user A among the users, the user terminal 5 can be installed according to the operation received, for example, issued by the banking unit And a specific electronic wallet application corresponding to a specific type of electronic wallet, and using the electronic wallet account corresponding to the user A to connect through the specific electronic wallet application and log in to the first server 11, and use the specific Kinds of electronic wallets for consumption, but not limited to this. In this embodiment, each wallet user identification data is, for example, the identity information provided by the corresponding user when applying for an e-wallet account. Specifically, the wallet user identification data includes, for example, an identity card of the corresponding user Font size, a date of birth, and a communication data, and the communication data is, for example, the mobile phone number of a mobile device held by the user, but not limited to this. It is added that in another embodiment, the transaction system 1 may also include multiple first servers 11 (that is, multiple electronic wallet transaction servers), and the first servers 11 are related to each other, for example. In multiple different specific types of electronic wallets, and each first server 11 is electrically connected to the second server 12, not limited to this embodiment.

The second server 12 is implemented as a credit card accounting server, for example, and stores a plurality of credit card data and a plurality of credit card identification data corresponding to the credit card data, respectively.

In this embodiment, each credit card data corresponds to a credit card that has been verified by the bank unit, and the credit card data includes, for example, a credit card number and a valid year and month, but not limited to this. The card account identification data corresponding to each piece of credit card data is, for example, identity information provided to the banking unit by a user when applying for a credit card. Specifically, in this embodiment, each card account identification data includes, for example, an identity card Font size, a date of birth and a communication data, but not limited to this.

In particular, for each credit card data, when the credit card data has just been created and stored in the second server 12 (that is, when the credit card corresponding to the credit card data has just passed the review by the bank unit) The credit card data is preset to a first state, and the credit card data can also be set to a second state, a third state, or a fourth state by the second server 12. Specifically, in this embodiment, the first state indicates that the credit card data has not passed a credit card opening procedure and is not allowed to be used for consumption in the specific electronic wallet application. The second state indicates that the credit card information has passed the credit card opening procedure, but is not allowed to be used for consumption in the specific electronic wallet application. The third state indicates that although the credit card information has not passed the credit card opening procedure, it has been allowed to be used for consumption in the specific electronic wallet application. The fourth state indicates that the credit card information has passed the credit card opening procedure and has also been allowed to be used for consumption in the specific electronic wallet application. It is added that the aforementioned credit card issuance procedure refers to the entity that the user receives the newly issued credit card issued by the bank unit, at least according to the credit card information printed on the credit card through the voice or network built by the bank unit The system performs the procedure of login and card opening, which can be understood by those of ordinary skill in the technical field of the present invention, so the details are not described here.

In particular, in this embodiment, each wallet user identification data and each card account identification data each contain the corresponding user ID number, date of birth, and communication data. Therefore, taking the aforementioned user A as an example, if the user A has an e-wallet account and also holds a credit card issued by the banking unit, the wallet user identification data stored in the first server 11 will There is one piece of wallet user identification data corresponding to user A, and there is also one piece of card account identification data corresponding to user A among the card identification data stored in the second server 12, and The wallet user identification data corresponding to user A and the card user identification data corresponding to user A will match each other.

Referring to FIGS. 1 and 2 (FIG. 2a and FIG. 2b) at the same time, the following exemplarily illustrates how the transaction system 1 of this embodiment implements a credit card binding method.

First, proceed to step S1. When the first server 11 receives a credit card binding request from the user terminal 5 and contains an identity data, it determines whether there is a target in the wallet user identification data stored that matches the identity data Wallet user identification information. When the judgment result of the first server 11 is NO, then proceed to step S2, and when the judgment result of the first server 11 is YES, then proceed to step S3. It is added that in this embodiment, the credit card binding request is generated by the user terminal 5 according to the user's operation in the state of logging in the first server 11, but not limited to this.

In step S2, when the first server 11 determines that the target wallet user identification data does not exist in the wallet user identification data (that is, there is no wallet user identification data that matches the identity data), the The first server 11 generates and transmits a body identification failure notification to the user terminal 5 for the user terminal 5 to output the body identification failure notification. In this embodiment, the failure of the body identification may indicate, for example, "user identification data input error", but not limited to this.

In step S3, when the first server 11 determines that there is the target wallet user identification data matching the identity data in the wallet user identification data, the target wallet user identification data is sent to the second server 12. Next, step S4 is performed.

In step S4, when the second server 12 receives the target wallet user identification data from the first server 11, it determines whether the stored card user identification data exists with the target wallet user A target cardholder identification data that matches the identification data. When the judgment result of the second server 12 is NO, then proceed to step S5, and when the judgment result of the second server 12 is YES, then proceed to step S6.

In step S5, when the second server 12 determines that the target cardholder identification data does not exist in the cardholder identification data (that is, there is no cardholder identification data that matches the target wallet user identification data) At this time, a corresponding first command is generated and sent to the first server 11 to control the first server 11 to generate and send a corresponding first warning notification to the user terminal 5 according to the first command. In this embodiment, the first warning notice may indicate, for example, "check no credit card holding/application information", but it is not limited to this.

In step S6, when the second server 12 determines that the target cardholder identification data that matches the target wallet user identification data exists in the cardholder identification data, the second server 12 generates a single Password (One Time Password, OTP for short), and send the one-time password to the mobile device corresponding to the communication data in the form of a short message according to the communication data contained in the target cardholder identification data (not shown) . Taking the aforementioned user A as an example, assuming that the target wallet user identification data described in step S3 is the wallet user identification data corresponding to the user A, the target described in step S6 The cardholder identification data is the cardholder identification data corresponding to the user A. It is added that the mobile device for receiving the one-time password may be, for example, the user terminal 5 itself, or may be another smart phone different from the user terminal 5. After transmitting the one-time password to the mobile device, the second server 12 proceeds to step S7.

In step S7, when the second server 12 receives a verification password from the user terminal 5, it is determined whether the verification password is consistent with the one-time password. When the judgment result of the second server 12 is NO, then proceed to step S8, and when the judgment result of the second server 12 is YES, then proceed to step S11 (shown in FIG. 2b).

In step S8, when the second server 12 determines that the verification password does not match the one-time password, the second server 12 further determines that it has received the verification password and determines that the verification password and the Whether the number of times the one-time password does not match reaches a predetermined number of times. In this implementation, the predetermined number of times may be three times, but not limited thereto. When the judgment result of the second server 12 is NO, then step S9 is executed. When the judgment result of the second server 12 is YES, step S10 follows.

In step S9, when the second server 12 determines that the number of times it has received the verification password that does not match the one-time password has not reached the predetermined number of times, it generates and transmits a second alert related to the verification password The notification is output to the user terminal 5. In this embodiment, the second warning notification may indicate, for example, "verification password input error", but not limited to this. Then, step S7 is performed again.

In step S10, when the second server 12 determines that the number of times it has received the verification password that does not match the one-time password has reached the predetermined number of times, it generates and transmits a third related to the verification password The warning notice is output to the user terminal 5, and the credit card binding method ends. In this embodiment, the third warning notification may indicate, for example, "The number of incorrect password verification has reached the upper limit, please try again", but not limited to this.

In step S11 (shown in FIG. 2b) following step S7, the second server 12 further determines whether a target credit card data corresponding to the target card user identification data in the credit card data is in the first state or The second state is to determine whether the target credit card data is in an unbound state that is not allowed to be used for consumption in the specific electronic wallet application. When the judgment result of the second server 12 is NO, then proceed to step S12, and when the judgment result of the second server 12 is YES, then proceed to step S13.

In step S12, when the second server 12 determines that the target credit card information is not in the first state or the second state (that is, not in the unbound state), but in the third state Or in the fourth state (that is, in a bound state that has been allowed to be used for consumption in the specific electronic wallet application), generate and send a second command to the first server 11, Therefore, the first server 11 generates a corresponding fourth warning notification to the user terminal 5 according to the second command. In this embodiment, the fourth warning notice may indicate, for example, "Your credit cards are all bound", but not limited to this.

In step S13 following step S11, when the second server 12 determines that the target credit card data is in the first state or the second state (that is, the target credit card data is in the unbound state ), the second server 12 generates a list of bindable credit cards containing the target credit card information, and sends the list of bindable credit cards to the user terminal 5 for output. Next, step S14 is performed.

In step S14, when receiving a binding instruction from the user terminal 5 indicating the target credit card data, the second server 12 sets the target credit card data to the third state or the fourth state ( That is, the target credit card data is set to the bound state) to allow the credit card corresponding to the target credit card data to be used for consumption in the specific electronic wallet application, and the second server 12 also Generate and send a binding request containing the target credit card information to the first server 11. Specifically, if the second server 12 determines in step S11 that the target credit card data is in the first state, the second server 12 will set the target credit card data as the third in this step On the other hand, if the second server 12 determines in step S11 that the target credit card data is in the second state, the second server 12 will set the target credit card data as the The fourth state. It is added that the binding instruction is generated by the user terminal 5 according to the user's operation on the list of bindable credit cards, for example. Next, step S15 is performed.

In step S15, when receiving the binding request from the second server 12, the first server 11 generates and stores a target wallet user identification data containing the target credit card information according to the binding request Binding credit card data, the first server 11 is equivalent to binding the target credit card data to the e-wallet account corresponding to the target wallet user identification data, so that the target credit card data can be used by the target wallet The electronic wallet account corresponding to the user identification data is used for consumption. Next, step S16 is performed.

In step S16, the first server 11 generates and transmits a pair of binding success notifications that should be bound to the credit card information to the user terminal 5 for the user terminal 5 to output the binding success notification.

It is added that after approving the credit card applied by the user, the bank unit will send the physical credit card to the user by post. Since the mailing process takes time, there may be several days between the time a bank unit issues a credit card and the user actually receives the credit card, that is, the user cannot start using the bank unit within the first time. credit card.

However, the transaction system 1 of this embodiment can solve the aforementioned inconvenience. According to the aforementioned user A, for example, in step S11, if the target credit card data is in the first state (that is, has not passed the credit card opening procedure and is not allowed to be used in the specific electronic wallet application The status of the purchase) may mean that the user A has not received the credit card corresponding to the target credit card information, and cannot open the credit card opening procedure for the credit card. However, in step S14, the target credit card data is set to the third state by the second server 12 (that is, it has not passed the credit card opening procedure but is allowed to be used in the specific electronic wallet application State of consumption), the target credit card data can be used for consumption in the specific electronic wallet application, therefore, in step S15, the first server 11 generates and stores the bound credit card data After that, even if the user A has not received the credit card corresponding to the target credit card data and cannot perform the credit card opening procedure, he can still consume the target credit card data in the specific e-wallet application. Therefore, this The transaction system 1 of the embodiment allows the user to start using the credit card through the specific electronic wallet application within the first time the credit card is approved by the bank.

In summary, by implementing the credit card binding method, the transaction system 1 of this embodiment can enable the user to complete credit card and electronic conveniently and quickly without entering the credit card number, valid year and month, and security check code. The binding between wallet accounts completely overcomes the inconvenience of the existing technology. In addition, the transaction system 1 of this embodiment can also allow users to bind the credit card to the e-wallet account and consume through the specific e-wallet application before receiving the approved credit card, so it can indeed be achieved The purpose of the invention.

However, the above are only examples of the present invention, and should not be used to limit the scope of the present invention. Any simple equivalent changes and modifications made according to the scope of the patent application of the present invention and the content of the patent specification are still classified as This invention covers the patent.

1······················································································································S1~S16·· ········Steps

Other features and functions of the present invention will be clearly presented in the embodiment with reference to the drawings, in which: FIG. 1 is a schematic diagram of a hardware block in which an embodiment of the trading system of the present invention is connected to a user terminal; and 2 (composed of Fig. 2a and Fig. 2b) is a flow chart exemplarily illustrating how this embodiment implements a credit card binding method.

1································· First server 12················· Second server 5···········

Claims (8)

A credit card binding method is implemented by a transaction system, which is suitable for a user terminal to be electrically connected and includes a first server and a second server, where the first server stores multiple pens corresponding to multiple Wallet user identification data of an electronic wallet account. The second server stores multiple credit card data and multiple card account identification data corresponding to the credit card data. The credit card binding method includes the following steps: (A) the first server When the device receives a credit card binding request from the user terminal and contains an identity data, and determines that there is a target wallet user identification data in the wallet user identification data that matches the identity data, the target wallet user The identification data is sent to the second server; (B) The second server receives the target wallet user identification data from the first server, and determines that the cardholder identification data exists with the target wallet After a target card account identification data matching the user identification data, a binding credit card list is generated and transmitted to the user end, and the binding card list contains the credit card information corresponding to the target card account identification data and is used as The credit card data of a target credit card data; (C) after receiving a binding instruction from the user terminal indicating the target credit card data, the second server transmits the target credit card data to the first server And (D) when the first server receives the target credit card data from the second server, it generates and stores a bound credit card data containing the target credit card data and corresponding to the target wallet user identification data; , In step (C), when the second server receives the binding Command, and it is determined that the target credit card data is in a state where it has not passed a credit card opening procedure and is not allowed to be used for consumption in the specific electronic wallet application, the second server also uses the target credit card data It is set to a state where it has not passed the credit card opening procedure but is allowed to be used for consumption in the specific electronic wallet application. The credit card binding method according to claim 1, wherein each card user identification data includes at least one communication data corresponding to a mobile device, and in step (B), the second server determines the card users When the target cardholder identification data exists in the identification data, a one-time password is first generated, and according to the communication data contained in the target cardholder identification data, the one-time password is transmitted to the corresponding mobile device, the The second server generates and transmits the list of bindable credit cards to the user terminal when it receives a verification password from the user terminal and determines that the verification password is consistent with the one-time password. The credit card binding method according to claim 2, wherein in step (B): when the second server determines that the target card account identification data does not exist in the card account identification data, the first server is controlled The device generates and sends a first warning notification to the user end; when the second server receives the verification password and determines that the verification password does not match the one-time password, generates and sends a verification password related to the verification password A second warning notification to the user end; when the second server determines that it receives the verification password and determines that the verification password does not match the one-time password a predetermined number of times, it generates and transmits a Third warning notice related to the verification password To the end of use. The credit card binding method according to claim 1, wherein, in step (A), when the first server determines that the target wallet user identification data does not exist in the wallet user identification data, the first server The device generates and sends an identification failure notification to the user end. A transaction system suitable for an electrical connection of a user terminal. The transaction system includes: a first server storing a plurality of wallet user identification data corresponding to multiple electronic wallet accounts; and a second server electrically connecting The first server, and stores a plurality of credit card data and a plurality of credit card identification data corresponding to the credit card data; wherein, the first server receives a credit card binding from the user terminal and contains an identity data If a certain request is made and it is determined that there is a target wallet user identification data in the wallet user identification data that matches the identity data, the target wallet user identification data is sent to the second server; the second server receives After reaching the target wallet user identification data from the first server, and judging that there is a target card account identification data in the card account identification data that matches the target wallet user identification data, a bindable is generated and transmitted A credit card list to the user end, the bindable credit card list contains the credit card data corresponding to the target card account identification data in the credit card data and used as a target credit card data; the second server receives a Use the end and indicate the After the binding instruction of the target credit card data, the target credit card data is sent to the first server; when receiving the target credit card data from the second server, the first server generates and stores a file containing the target Credit card data and the bound credit card data corresponding to the target wallet user identification data; wherein, when the second server receives the binding instruction, and determines that the target credit card data is not passed a credit card opening procedure and is not When allowed to be used for consumption in the specific electronic wallet application, the second server also sets the target credit card data as not passing through the credit card opening procedure but being allowed to be used in the specific electronic wallet application The state used for consumption. The transaction system according to claim 5, wherein each cardholder identification data includes at least one communication data corresponding to a mobile device, and the second server determines that the target cardholder exists in the cardholder identification data When identifying data, a one-time password is first generated, and the one-time password is transmitted to the corresponding mobile device according to the communication data included in the target card user identification data, and the second server receives the When a verification password from the user terminal is judged to be consistent with the one-time password, the list of bindable credit cards is generated and transmitted to the user terminal. The transaction system according to claim 6, wherein: when the second server determines that the target cardholder identification data does not exist in the cardholder identification data, the first server is controlled to generate and send a first warning notification To the user end; when the second server receives the verification password and determines the verification When the password does not match the one-time password, a second warning notification related to the verification password is generated and sent to the user end; when the second server determines that it receives the verification password and determines the verification password When the number of times that does not match the one-time password reaches a predetermined number of times, a third warning notification related to the verification password is generated and transmitted to the user terminal. The transaction system according to claim 5, wherein when the first server determines that the target wallet user identification data does not exist in the wallet user identification data, the first server generates and sends a body identification failure notification To the end of use.

Images