KR20140055414A - Method and system for mobile payment using the mobile deivces of consumer and seller - Google Patents

Abstract

A mobile payment method and system using traders' mobile devices are provided. In the mobile payment method according to the embodiment of the present invention, the mobile payment manager authenticates the mobile devices of the buyer and the seller, and processes the mobile payment while relaying the transaction-related information between them. As a result, mobile settlement for offline transactions becomes possible, and mobile settlement can be utilized more simply and safely for online transactions.

Description

TECHNICAL FIELD The present invention relates to a mobile payment method and system using mobile devices,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a mobile payment method and system, and more particularly, to a mobile payment method and system for paying a payment using a mobile device.

Mobile settlement, in which the amount of payment is added to the mobile communication fee, is being used mainly for small payment. However, such mobile payments are used only for online transactions and not for offline transactions.

In order to activate mobile settlement, mobile settlement should be widely used not only in online transactions but also in offline transactions.

The mobile payment used in online transactions is usually performed by confirming the resident registration number and authenticating the user through the SMS (Short Message Service), which is a hassle for mobile payment users.

In addition, due to the frequent leakage of personal information, users are reluctant to disclose important personal information such as resident registration number, and mobile payment is becoming increasingly shrinking.

Therefore, it is required to search for ways to further activate mobile settlement in online transactions.

Disclosure of the Invention The present invention has been made to solve the above problems, and it is an object of the present invention to provide a mobile payment manager capable of making a mobile settlement in an offline mode and easily and safely supporting a mobile settlement on- And a mobile payment method and system for authenticating mobile devices of a buyer and a seller and processing mobile settlement while relaying transaction related information between them.

According to an aspect of the present invention, there is provided a mobile payment method including: generating an authentication code; Transmitting the generated authentication code to the mobile device of the buyer and the mobile device of the seller; Receiving transaction details and an authentication code from the mobile device of the purchaser; Transmitting the received transaction details and the authentication code to the seller's mobile device; And receiving a transaction approval from the seller's mobile device, processing the mobile payment.

If the authentication code received through the delivery step and the authentication code received through the transmission step match, the seller's mobile device can approve the transaction automatically or through a confirmation of the seller.

In addition, the mobile payment method according to an embodiment of the present invention includes: receiving a seller identification code from a mobile device of the purchaser; And identifying the seller using the received seller identification code, and the transmitting step may transmit the authentication code to the seller's mobile device identified in the holding step.

The seller identification code is displayed on the mobile device of the seller, and the mobile device of the purchaser can recognize and acquire it through the photographing.

Further, the seller identification code is displayed on the terminal device of the purchaser, and the mobile device of the purchaser can recognize and acquire it through the photographing.

The mobile payment method according to an embodiment of the present invention may further include providing information on the seller to the mobile device of the buyer.

According to another aspect of the present invention, there is provided a mobile payment method including: receiving buyer information from a mobile device of a purchaser; And requesting the purchaser's identity authentication while transmitting the purchaser information to the mobile communication company server, wherein the authentication code generation step can be performed when the identity authentication is successful by the mobile communication company server.

The purchaser information may include a part of the telephone number given to the purchaser's mobile device and the resident registration number of the purchaser.

In addition, some of the resident registration numbers of the purchaser may be randomly determined by the purchaser's mobile device.

The mobile payment method according to an embodiment of the present invention further includes the step of informing the purchaser's mobile device of a transaction approval result when notified of transaction approval from the seller's mobile device, When the transaction approval rejection is notified from the device, the transaction approval rejection fact is transmitted to the mobile device of the buyer, and the transaction details and the authentication code are re-executed

The mobile payment processing step may include notifying the mobile phone company server of the telephone number and the transaction details assigned to the mobile device of the purchaser so that the payment amount on the transaction details is added to the mobile communication fee of the purchaser More included

According to another aspect of the present invention, a mobile payment server includes a communication interface connected to communicate with a mobile device of a buyer and a mobile device of a seller; And transmits an authentication code to the buyer's mobile device and the seller's mobile device via the communication interface, receives transaction details and an authentication code from the buyer's mobile device via the communication interface, And a processor for processing a mobile settlement when notified of transaction approval from the seller's mobile device via the communication interface.

As described above, according to the embodiments of the present invention, the mobile payment manager can authenticate the mobile devices of the buyer and the seller, and can process the mobile payment while relaying the transaction-related information between them. Accordingly, it is possible to easily and safely settle the transaction price generated in the offline using the mobile device without using the mobile payment card.

Particularly, since the authentication is performed by a reliable mobile communication company and settlement payment is made, the risk of transaction and settlement is minimized.

In addition, since only a part of the resident registration number is required for the authentication of the user, the input procedure is simplified and the outflow of the personal information can be prevented, thereby enhancing the personal information security.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram of a mobile payment system according to an embodiment of the present invention;
FIG. 2 and FIG. 3 are diagrams provided for explanation of a process in which offline mobile settlement is performed by the mobile settlement system shown in FIG. 1,
4 is a view illustrating a seller's guide and a resident registration number input screen displayed on a buyer's mobile device,
5 is a view illustrating a transaction history input screen displayed on the buyer's mobile device,
6 is a diagram illustrating a transaction history approval screen displayed on a seller mobile device,
FIG. 7 and FIG. 8 are diagrams for explaining a process of performing online mobile settlement by the mobile settlement system shown in FIG. 1;
9 and 10 illustrate another example of online mobile payment,
11 and 12 are diagrams provided for explanation of an offline mobile settlement using a seller & commodity QR code,
13 and 14 are drawings provided for explanation of online mobile settlement using a seller & commodity QR code,
15 is a detailed block diagram of the mobile payment server shown in FIG.

Hereinafter, the present invention will be described in detail with reference to the drawings.

1. Mobile Payment System

1 is a diagram illustrating a mobile payment system according to an exemplary embodiment of the present invention. The mobile payment system according to the present embodiment is a system for paying a payment by relaying a buyer's mobile device and a seller's mobile device.

The mobile payment system performing the above functions is constructed by connecting the purchaser mobile device 110, the seller mobile device 120, the mobile payment server 130, and the mobile communication company server 140 so that they can communicate with each other.

The buyer mobile device 110 is a device carried by the buyer, and it is required that a mobile payment application is installed. The mobile payment application is an application for performing the procedures necessary for mobile settlement and is developed by the mobile payment server 130 and distributed through an application store or the like.

The seller mobile device 120 is a device that the seller carries and it is required that the mobile payment application is installed in the same manner as the buyer mobile device 110. [

The mobile payment server 130 is a server of a mobile payment company that processes and manages mobile payment transactions generated in a transaction between a buyer and a seller. To this end, the mobile payment server 130 requests the mobile communication company server 140 for mobile payment for the payment that the purchaser should pay to the seller after performing the steps necessary for authentication of the purchaser and authentication of the apparatus.

Mobile settlement by the mobile settlement system shown in FIG. 1 can be divided into offline mobile settlement and online mobile settlement.

Offline mobile settlement is a payment for mobile payment made by a buyer through an offline transaction with a seller. On-line mobile payment is a payment for a mobile payment made by a buyer through an online transaction with a seller.

2. Offline mobile payments

Hereinafter, a process of performing offline mobile settlement by the mobile settlement system shown in FIG. 1 will be described in detail with reference to FIG.

As shown in FIG. 2, first, the seller mobile device 120 executes the mobile payment application and enters the seller mode (S205). The seller mobile device 120 entering the seller mode displays a QR code (Quick Response Code) on the screen (S210).

The QR code displayed on the screen of the seller mobile device 120 in step S210 contains information on the seller. That is, in this embodiment, the QR code is assigned differently for each seller.

On the other hand, the buyer mobile device 110 executes the mobile payment application and enters the buyer mode (S215). Then, the buyer mobile device 110 photographs and recognizes the QR code displayed on the screen of the seller mobile device 120 through step S210 (S220).

Then, the buyer mobile device 110 transmits the QR code recognized in operation S220 to the mobile payment server 130 (S225). In step S230, the mobile payment server 130 determines who the seller is from the QR code received in step S225. For step S230, the mobile payment server 130 has a DB in which a QR code and seller information are mapped on a one-to-one basis.

Thereafter, the mobile payment server 130 transmits the seller information to the buyer mobile device 110 (S235).

The purchaser mobile device 110 displays a screen for receiving a portion of the resident registration number of the mobile communication company and the purchaser who subscribed to the purchaser (S240) while guiding the seller information received in step S235 to the purchaser (S240) And a part of the resident registration number (S245).

A part of the resident registration number of the buyer received in step S245 is randomly determined by the mobile payment application executed in the buyer mobile device 110. [ For example, you can ask for the 3rd digit of the resident registration number of the buyer, 1) the 3rd digit, 2) the 6th digit, 3) the 9th digit, and 4) the 11th digit, where "3", "6" "And" 11 "are randomly determined.

FIG. 4 illustrates a seller guidance and a mobile communication company / resident registration number input screen displayed on the buyer mobile device 110 in step S240.

When the input is completed in step S245, the buyer mobile device 110 transmits a part of the inputted resident registration number of the buyer together with the mobile communication company subscribed by the buyer and the telephone number given to the buyer mobile device 110 to the mobile payment server 130 (S250).

In step S255, the mobile payment server 130 determines the mobile communication company to which the purchaser subscribes based on the received information through step S250.

In step S260, the mobile payment server 130 transmits a part of the resident registration number and the telephone number of the purchaser, which are received in step S250, to the mobile communication company server 140 of the mobile communication company,

In step S265, the mobile communication company server 140 determines whether the telephone number and a part of the resident registration number received in step S260 are identical to the telephone number and the resident registration number part of the person DB.

In step S260, the mobile communication company server 140 notifies the mobile payment server 130 of the authentication result in step S265.

If the mobile payment server 130 is informed of the successful authentication of the user in step S270, the mobile payment server 130 generates a device authentication code (S275). The device authentication code generated in step S275 is a code for authenticating the purchaser mobile device 110. [

Accordingly, the mobile payment server 130 transmits the device authentication code generated in step S275 to both the buyer mobile device 110 and the seller mobile device 120 (steps S280 and S285).

Hereinafter, the procedures after step S285 of FIG. 3 will be described in detail with reference to FIG.

The buyer mobile device 110 receiving the device authentication code through step S280 of FIG. 3 displays the transaction history input screen (S305) and receives the transaction details from the buyer (S310). FIG. 5 illustrates a transaction history input screen displayed on the purchaser's mobile device 110 in step S310.

As shown in FIG. 5, the transaction details include the transaction item and the payment amount, but the payment amount may be included in the transaction details for the convenience of the purchaser.

When the input is completed in step S310, the buyer mobile device 110 transmits the device authentication code received in step S280 of FIG. 3 to the mobile payment server 130 together with the transaction details input in step S310 (S315).

Then, the mobile payment server 130 transmits the transaction details and the device authentication code received in step S315 to the seller mobile device 120 (S320). The seller mobile device 120 checks whether the device authentication code received in step S320 is identical to the device authentication code received in step S285 of FIG. 3 (S325).

If it is determined in step S325 that the device authentication codes match, the mobile payment server 130 displays a transaction details approval screen (S330), and receives the approval of the seller (S335).

The transaction details approval screen is a screen for inquiring whether or not the seller has approved the transaction details received from the purchaser mobile device 110 in step S315. In step S330, the transaction details approval screen is displayed in the transaction details displayed on the seller mobile device 120 The approval screen is illustrated.

If the seller approves the transaction details in step S335, the seller mobile device 120 transmits the transaction approval to the mobile payment server 130 (S340). Then, the mobile payment server 130 transmits the transaction approval result to the buyer mobile device 110 (S345).

In step S345, the mobile payment server 130 may send the electronic receipt to the purchaser's mobile device 110. [ Also, the mobile payment server 130 can send the electronic sales slip according to the transaction approval to the seller mobile device 120.

Meanwhile, the mobile payment server 130 transmits the payment information including the purchaser's telephone number and the payment amount to the mobile communication company server 140 (S350). Then, the mobile communication company server 140 adds the payment amount to the mobile communication fee of the buyer's telephone number received in step S350 (S355).

When the additional processed amount is collected, it is delivered from the mobile communication company to the seller through the mobile payment company. However, in this process, the fees allocated to mobile carriers and mobile payment companies can be eliminated.

On the other hand, if the seller declines the transaction details in step S335, the mobile payment server 130 may notify the buyer mobile device 110 that the transaction is to be resumed from step S305. This may be useful in a manner that avoids repeating the procedures shown in FIG. 2 if the buyer has mistakenly entered the payment amount and the seller rejected it.

3. Online Mobile Payment # 1

So far, the offline mobile payment process has been described in detail. Hereinafter, a process of performing online mobile settlement by the mobile settlement system shown in FIG. 1 will be described in detail with reference to FIG.

On-line mobile payment is a payment made by the buyer to mobile payment through online transaction with the seller. Therefore, the premise of online mobile settlement is an online transaction between a buyer and a seller. In this embodiment, a buyer assumes a case of online shopping on his / her PC (personal computer) via the Internet.

In order to settle an online mobile according to the present embodiment, a seller must publish a QR code containing information about him / herself (merchant information) in a merchandise sales page of online shopping.

Then, as shown in FIG. 7, after the buyer mobile device 110 executes the mobile payment application and enters the buyer mode (S405), a QR code displayed on the merchandise sale page of the online shopping screen displayed on the buyer's PC And photographed and recognized (S410).

Steps S415 through S475 performed after step S410 are the same as steps S225 through S285 shown in FIG. 2, and thus detailed description thereof will be omitted and step S475 and subsequent steps will be described in detail with reference to FIG.

The seller mobile device 120 receiving the device authentication code through step S475 of FIG. 7 automatically executes the mobile payment application as shown in FIG. 8 and automatically enters the seller mode (S505).

The mobile payment application automatic execution and the seller mode automatic entry in step S505 are performed without the instruction of the seller and the execution result does not have to be displayed on the screen of the seller mobile device 120. [

On the other hand, the buyer mobile device 110 receiving the device authentication code through step S470 of FIG. 7 displays the transaction history input screen (S510) and receives the transaction details from the buyer (S515).

Upon completion of the input in step S515, the buyer mobile device 110 transmits the device authentication code received in step S470 of FIG. 7 to the mobile payment server 130 along with the transaction details input in step S515 (S520).

Then, the mobile payment server 130 delivers the transaction details and the device authentication code received in step S520 to the seller mobile device 120 (S525). The seller mobile device 120 checks whether the device authentication code received in step S525 is identical to the device authentication code received in step S475 of FIG. 7 (S530).

If it is determined in step S530 that the device authentication codes match, the seller mobile device 120 automatically approves the transaction details (S535) and transmits the transaction approval information to the mobile payment server 130 (S540).

Steps S545 through S555 performed after step S540 are the same as steps S345 through S355 shown in FIG. 3, and therefore, detailed description thereof will be omitted.

On the other hand, if it is determined in step S530 that the device authentication code does not match, the seller mobile device 120 automatically rejects the transaction details, in which case the mobile payment process is not performed.

Further, after the mobile payment processing is completed, the seller can request the mobile payment server 130 to cancel the approved transaction details. This is for canceling the case where the payment amount erroneously inputted by the purchaser is automatically approved by the seller mobile device 120 and is useful in the case of online mobile settlement.

4. Online Mobile Payment # 2

9 and 10 are views showing another example of online mobile settlement. In the online mobile payment shown in FIGS. 9 and 10, it is assumed that the online shopping server 150 performs the role of the seller mobile device 120.

Since the online shopping server 150 does not use the mobile payment application, there is no need to automatically execute the mobile payment application performed by the seller mobile device 120 and automatically enter the seller mode (step S505 of FIG. 8). The rest of the procedure is the same as the online mobile settlement procedure shown in FIGS. 7 and 8, and a detailed description thereof will be omitted.

5. Merchants & Products QR  Code-based offline / online mobile payments

Up to now, the process of relaying the purchaser's mobile device 110 and the seller's mobile device 120 by paying the mobile payment transaction to the mobile payment server 130 is divided into an offline mobile settlement and an online mobile settlement, Are described in detail.

In the above embodiments, it is assumed that the QR code includes information on the seller, but it is also possible to provide additional information, for example, information on a transaction item (goods or service information) or information on a transaction amount (product or service price) . ≪ / RTI > In this case, the purchaser can omit the process of inputting the transaction details through the buyer mobile device 110, and the risk of the buyer mistakenly inputting the transaction details can be eliminated, which will be described in detail below.

First, the process of performing the 'offline' mobile settlement using the seller & commodity QR code will be described in detail with reference to FIGS. 11 and 12. FIG.

11, the seller mobile device 120 executes the mobile payment application to enter the seller mode (S805), and displays the QR code on the screen (S810).

In the QR code displayed on the screen of the seller mobile device 120 in step S810, 'information on the goods to be purchased by the buyer' is included in addition to 'information on the seller'. That is, in this embodiment, the QR code is assigned differently for each product in addition to the seller.

On the other hand, the buyer mobile device 110 executes the mobile payment application to enter the buyer mode (S815), captures and recognizes the QR code displayed on the screen of the seller mobile device 120 through step S810 (S820).

Then, the buyer mobile device 110 transmits the QR code recognized in step S820 to the mobile payment server 130 (S825). The mobile payment server 130 grasps the seller and the goods from the QR code received in step S825 (S830). For the step S830, the mobile payment server 130 holds a DB in which the QR code and the seller & product information are mapped on a one-to-one basis.

Then, the mobile payment server 130 transmits the seller & product information to the buyer mobile device 110 (S835).

The buyer mobile device 110 displays a screen for receiving a part of the resident registration number of the mobile communication company and the buyer subscribed by the purchaser (S840) while informing the buyer of the seller & product information received in step S835, A part of the resident registration number is inputted (S845). Product information includes information on items and amounts.

Since steps S850 to S885 performed after step S845 are the same as steps S250 to S285 shown in FIG. 2, detailed description thereof will be omitted, and steps after step S885 will be described in detail with reference to FIG.

The buyer mobile device 110 receiving the device authentication code through step S880 of FIG. 11 displays a transaction details confirmation screen (S905), and confirms the transaction details from the purchaser (S910). In the screen displayed in the step S905, items and amounts for the corresponding goods are also included in the "transaction item" and "payment amount" processed in the blank in Fig. 5, which is different from the above-described embodiment.

Steps S915 to S955 performed after step S910 are the same as steps S315 to S355 shown in Fig. 3, and therefore, detailed description thereof will be omitted.

So far, the offline mobile settlement process using the seller & product QR code has been described in detail. Hereinafter, the process of performing 'online' mobile settlement using the seller & commodity QR code will be described in detail with reference to FIGS. 13 and 14. FIG.

In order to settle an online mobile according to the present embodiment, a seller must publish a QR code containing information about him / herself (merchant information) and goods on the merchandise sales page of online shopping.

Then, as shown in FIG. 13, after the buyer's mobile device 110 executes the mobile payment application and enters the buyer mode (S1005), a QR code displayed on the goods sale page of the online shopping screen displayed on the buyer's PC And is photographed and recognized (S1010).

The steps S1015 to S1075 performed after step S1010 are the same as those of steps S825 to S885 shown in FIG. 11, so a detailed description thereof will be omitted, and the steps after step S1075 will be described in detail with reference to FIG.

The buyer mobile device 110 receiving the device authentication code through step S1070 of FIG. 13 displays a transaction details confirmation screen (S1105), and confirms the transaction details from the buyer (S1110).

Since steps S1115 to S1150 performed after step S1110 are the same as steps S915 to S955 shown in Fig. 12, detailed description thereof will be omitted.

On the other hand, the online shopping server 150 of FIGS. 13 and 14 can be replaced with the seller mobile device 120.

6. Mobile devices

15 is a detailed block diagram of the mobile payment server 130 shown in FIG. 15, the mobile payment server 130 includes a communication interface 131, a processor 133, and a storage unit 135. As shown in FIG.

The communication interface 131 establishes and maintains communication links with the buyer mobile device 110, the merchant mobile device 120, and the mobile carrier server 140.

The storage unit 135 is a storage medium in which a mobile settlement application is installed, and information required when a mobile settlement application is executed and mobile settlement is performed is stored. In connection with the above embodiments, the QR code / seller DB is stored in the storage unit 135, and transaction details between the buyer mobile device 110 and the seller mobile device 120 are stored.

The processor 133 executes a mobile settlement application installed in the storage unit 135 to perform mobile settlement of transaction details between the buyer mobile device 110 and the seller mobile device 120. [

To this end, the processor 133 performs the steps performed by the mobile payment server 130, among the steps shown in FIGS. 2, 3 and 7-14.

7. Other

On the other hand, the mobile payment application provides a real-time inquiry function for purchasing payment history and settlement cancellation history in buyer mode. In addition, the mobile payment application stores and provides electronic receipts sent from the mobile payment server 130.

In addition, the mobile payment application provides a real-time inquiry function for sales payment history and sales cancellation history in the seller mode. In addition, the mobile payment application stores and provides electronic slips sent from the mobile payment server 130.

Although the buyer mobile device 110 and the seller mobile device 120 shown in FIG. 1 can be implemented as a mobile phone capable of executing a mobile payment application, it does not exclude the implementation of a different kind of mobile device.

It goes without saying that the technical idea of the present invention can also be applied to a computer-readable recording medium having a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical idea according to various embodiments of the present invention may be embodied in computer-readable code form recorded on a computer-readable recording medium. The computer-readable recording medium is any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like. In addition, the computer readable code or program stored in the computer readable recording medium may be transmitted through a network connected between the computers.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention.

110: buyer mobile device 120: seller mobile device
130: mobile payment server 131: communication interface
133: Processor 135:
140: Carrier server

Claims (12)

Generating an authentication code;
Transmitting the generated authentication code to the mobile device of the buyer and the mobile device of the seller;
Receiving transaction details and an authentication code from the mobile device of the purchaser;
Transmitting the received transaction details and the authentication code to the seller's mobile device; And
And receiving a transaction approval from the seller's mobile device, processing the mobile payment.
The method according to claim 1,
The seller's mobile device,
And when the authentication code received through the delivery step matches the authentication code received through the transmission step, the transaction is approved through automatic or seller confirmation.
The method according to claim 1,
Receiving a merchant identification code from the buyer ' s mobile device; And
Further comprising the step of identifying the seller using the received seller identification code,
Wherein,
And transmits the authentication code to the seller's mobile device identified in the determination step.
The method of claim 3,
The merchandise identification code may include:
Wherein the mobile device is displayed on the mobile device of the seller, and the mobile device of the purchaser recognizes and acquires the mobile device by photographing.
The method of claim 3,
The merchandise identification code may include:
Wherein the mobile device is displayed on the terminal device of the purchaser, and the mobile device of the purchaser recognizes and acquires through the photographing.
The method of claim 3,
And providing information on the seller to the mobile device of the purchaser.
The method according to claim 1,
Receiving buyer information from the buyer's mobile device; And
Further comprising: requesting authentication of the purchaser by transmitting the purchaser information to the mobile communication company server,
The authentication code generation step includes:
And when the authentication of the user is successfully performed by the mobile communication company server.
8. The method of claim 7,
The buyer information includes:
And a part of a resident registration number of the purchaser, and a telephone number assigned to the mobile device of the purchaser.
9. The method of claim 8,
Some of the resident registration numbers of the buyer are,
Is determined at random by the buyer's mobile device.
The method according to claim 1,
Further comprising the step of notifying the buyer of the buyer of the transaction approval result when it is notified of the transaction approval from the seller's mobile device,
Wherein the transaction acceptance rejection information is transmitted to the mobile device of the purchaser when the transaction approval rejection is received from the seller's mobile device, and the transaction is re-executed from the transaction details and the authentication code receiving step.
The method according to claim 1,
Wherein the mobile payment processing step comprises:
And notifying the mobile communication company server of the telephone number and the transaction details assigned to the mobile device of the purchaser so that the payment amount on the transaction details is added to the mobile communication fee of the purchaser Way.
A communication interface connected to be able to communicate with the buyer's mobile device and the seller's mobile device; And
And transmits the authentication code to the purchaser's mobile device and the seller's mobile device via the communication interface, receives the transaction details and the authentication code from the purchaser's mobile device through the communication interface, And a processor for processing a mobile payment when the merchant receives notification of transaction approval from the seller's mobile device via the communication interface.

Images