KR101624289B1 - Method for providing payment history list and payment server - Google Patents

Abstract

A method by which a payment server provides a payment statement list in order to verify payment according to an embodiment of the present invention comprises: (a) a step of receiving a request for the payment including identification information on an affiliate store and payment amount information from a user terminal and approving the requested payment; (b) a step of transmitting an approval number and a payment statement including the payment amount information to the user terminal when the payment approving is completed; and (c) a step of selecting, when an application installed on an employee terminal at the affiliate store is executed, based on positional information of the employee terminal, an adjacent affiliate store located within a preestablished radius from the location of the employee terminal and transmits the payment statement lists of the adjacent affiliate store to the employee terminal in order to verify that approval of the requested payment is completed based on the approval number.

Description

METHOD FOR PROVIDING PAYMENT HISTORY LIST AND PAYMENT SERVER < RTI ID = 0.0 >

The present invention relates to a payment history list providing method and a payment server, and more particularly, it relates to a payment history list providing method and a payment server which transmit a payment history to a user terminal, transmit a payment history list of a nearby merchant to an employee terminal, And a settlement server for providing a settlement service for allowing completion of approval for the settlement service.

In the conventional offline merchant, the payment means used for payment is limited to cash and plastic cards. However, since the mobile card service has recently been provided, it has become possible to make payment using a mobile card issued to a smart phone.

However, even if payment is made using cash or credit card as well as a mobile card, the payment means must present the payment means directly to the employee, so that waiting time at the merchant will be long.

In addition, there is a problem that it is difficult for the customer and the employee to confirm whether or not the approval for the requested payment is normally completed.

Therefore, it is imperative that a method of easily confirming whether or not a payment approval has been made between a customer and an employee is possible, while paying the payment without offering a payment means directly to an employee at an offline merchant.

Korean Patent Publication No. 2004-0088154

SUMMARY OF THE INVENTION The present invention has been made in order to solve the above problems of the related art, and it is an object of the present invention to provide a method and apparatus for transmitting payment history to a user terminal, transmitting a payment history list of a nearby merchant to an employee terminal, And a settlement server for providing a settlement service for allowing completion of the approval for the settlement service.

The objects of the present invention are not limited to the above-mentioned objects, and other objects not mentioned can be clearly understood from the following description.

According to an aspect of the present invention, there is provided a method of providing a payment history list for a payment confirmation, the method comprising the steps of: (a) receiving identification information and payment amount information of a merchant from a user terminal; Receiving the payment request including the payment request, and performing approval for the requested payment; (b) when the payment approval is completed, transmitting the payment details including the approval number and the payment amount information to the user terminal; And (c) when the application installed in the employee terminal of the affiliate shop is executed, selecting a nearby affiliate shop located within a predetermined radius from the position of the employee terminal, based on the position information of the employee terminal, To the employee terminal so that the approval completion of the requested payment can be confirmed through the approval number.

Wherein the step (a) comprises receiving, from the user terminal, a payment request further including information of the payment means, and performing approval of the payment using the payment means, and the step (c) And transmitting the payment history list of the nearby merchant to the employee terminal, which has been approved by using the payment history list.

The step (c) may include transmitting to the employee terminal a payment history list of the nearby merchant that has been approved up to a predetermined period before execution of the application.

The step (a) may include receiving, from the user terminal, the identification information of the franchisee, the identification information including at least one of the mutual franchisee's name, the representative phone number, and the business number.

The step (a) may include receiving identification information of the franchisee from the user terminal that recognizes any one of the tag information, the QR code, and the bar code attached to the franchisee.

The step (a) may include selecting a nearby affiliate shop located within a predetermined radius from the position of the user terminal, and transmitting the list of the nearby affiliate shop to the user terminal; And receiving, from the user terminal, identification information of a selected affiliate store from a list of the nearby affiliate stores.

According to another aspect of the present invention, there is provided a payment approval unit for receiving a payment request including identification information of a merchant and payment amount information from a user terminal, ; A payment history transfer unit for transferring payment details including the approval number and the payment amount information to the user terminal when the payment approval is completed; And selecting a nearby merchant located within a predetermined radius from the position of the employee terminal based on the position information of the employee terminal when the application installed in the employee terminal of the merchant is executed, And a payment history list transmission unit for transmitting the payment approval request to the terminal and confirming the approval completion of the requested payment through the approval number.

Wherein the payment approval section receives from the user terminal a payment request further including information of the payment means and performs approval for payment using the payment means, and the payment history list transfer section uses the payment means And transmits the payment history list of the nearby merchant to the employee terminal that has been approved.

The payment history list transmission unit may transmit a payment history list of the nearby merchant that has been approved before the predetermined time period from execution of the application to the employee terminal.

The settlement approval unit may receive identification information of the franchisee, which includes at least one of the mutual franchisee's name, the representative phone number, and the business number from the user terminal.

The settlement approval unit may receive the identification information of the franchisee from the user terminal that recognized any one of the tag information, the QR code, and the barcode attached to the franchisee.

Wherein the payment approval section selects a nearby affiliate shop located within a predetermined radius from the position of the user terminal and transmits a list of the nearby affiliate shops to the user terminal and identifies, from the user terminal, identification of a selected affiliate shop Information can be received.

According to the embodiment of the present invention, even if the customer presents the payment means directly to the employee and does not request payment, the customer can request payment through the user terminal held by the customer. Therefore, The convenience of the customer can be increased.

In addition, according to the embodiment of the present invention, since the employee can be provided as a member of a payment service providing application or receive a payment history list of a nearby merchant without having to log in separately, the convenience of the employee can be increased.

According to an embodiment of the present invention, it is possible to easily confirm whether payment approval has been normally performed between a customer and an employee through an approval number.

In addition, according to the embodiment of the present invention, since the merchant information is not exposed to the payment history list of the nearby merchant, the security of the sales information of the merchant can be secured.

It should be understood that the effects of the present invention are not limited to the above effects and include all effects that can be deduced from the detailed description of the present invention or the configuration of the invention described in the claims.

1 is a diagram illustrating a payment history list providing system according to an embodiment of the present invention.
2 is a block diagram illustrating a configuration of a payment server according to an embodiment of the present invention.
3 is a diagram illustrating a process of providing a payment history list according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "indirectly connected" . Also, when an element is referred to as "comprising ", it means that it can include other elements, not excluding other elements unless specifically stated otherwise.

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

1 is a diagram illustrating a payment history list providing system according to an embodiment of the present invention.

Referring to FIG. 1, the payment history list providing system may include a user terminal 100, an employee terminal 200, and a payment server 300 that can communicate with each other through a communication network.

First, the communication network can be configured without regard to its communication mode such as wired and wireless. A local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), and the like.

The user terminal 100 and the employee terminal 200 can be connected to an external server such as a payment server 300 through a network such as a mobile phone, a smart phone, a PDA (Personal Digital Assistant), a PMP (Portable Multimedia Player) (IPTV) including a desktop PC, a tablet PC, a laptop PC, and a set-top box, and may be connected to a payment server 300 or the like via a network. And a communication device that can be connected to an external server.

The user terminal 100 and the employee terminal 200 may be provided with an application for providing payment details. At this time, the application management server (not shown) can provide an application store capable of distributing various applications. When an operator who operates the payment server 300 registers the payment service providing application in the application store, 100 and the employee terminal 200 can download the payment service providing application registered in the application store and install it in the memory. Here, the payment service providing application may provide various services related to the payment service such as a payment request, a payment history, and a payment history list.

The payment service providing application is distributed and distributed as an employee application for an employee of an affiliate store, which provides services such as a payment application, a customer application for a customer, and a payment history list, . At this time, the customer application may be installed in the user terminal 100, and the employee application may be installed in the employee terminal 200. [

The payment service providing application may be a program module capable of communicating with an external device. Such a program module may be included in the user terminal 100, the employee terminal 200, or another device capable of communicating with the user terminal 100 in the form of an operating system, an application program module, and other program modules, and may be physically stored on various known storage devices Lt; / RTI > Such program modules, on the other hand, encompass but are not limited to routines, subroutines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types as described below in accordance with the present invention.

Hereinafter, a process performed through the payment service provision application installed in the user terminal 100 and the employee terminal 200 will be described. However, the user terminal 100 and the employee terminal 200 can perform all processes Of course.

After executing the payment service providing application, the user terminal 100 may transmit the payment request to the payment server 300. Here, the payment request may include the identification information of the merchant and the payment amount information, and may be a request to settle the payment amount corresponding to the payment amount information to the merchant corresponding to the identification information of the merchant.

According to one embodiment, the identification information of the franchisee may include at least one of a name of a franchisee, a representative phone number, and a business registration number, and the user terminal 100 may store identification information of a franchisee To the payment server (300).

According to another embodiment, the identification information of the merchant may be any one of tag information, a barcode and a QR code attached to the merchant, and the user terminal 100 may recognize the tag information through short-range wireless communication, The identification information of the recognized merchant can be transmitted to the payment server 300 after recognizing the photographed bar code or QR code.

According to another embodiment, the identification information of the merchant may be selected from a list of nearby merchants, where the list of nearby merchants is located within a predetermined radius (e.g., 100 meters) from the location of the user terminal 100 It can be a list of merchants.

Specifically, the user terminal 100 may include a device for managing current location information, and may transmit the location information to the payment server 300. For example, the user terminal 100 may include a global positioning system (GPS), and may transmit the GPS signal, which is the location information of the user terminal 100, to the payment server 300.

Then, the user terminal 100 can receive from the payment server 300 a list of nearby merchants located within a predetermined radius from a location corresponding to the location information transmitted to the payment server 300, The identification information of the selected merchant can be transmitted to the payment server 300. [

When requesting payment, the user terminal 100 may transmit a payment request including information on the payment means to the payment server 300 and request payment using the payment means corresponding to the information of the payment means. At this time, the user terminal 100 can transmit the information of the previously registered payment means to the payment server 300 at the time of joining the membership to use the payment service providing application, To the server 300.

When payment approval is completed at the payment server 300, which will be described later, the user terminal 100 can receive payment details from the payment server 300. [ At this time, the user terminal 100 can receive payment details through a payment service providing application, an SMS, a messenger, an e-mail service, and the like, execute a program for providing the service, and display the payment details on the screen. Here, the payment details may include an approval number, payment amount information, merchant information, approval completion time information, and the like, and may be replaced with a receipt for the payment requested through the user terminal 100. [

After executing the payment service application, the employee terminal 200 can receive the payment history list of the nearby merchant from the payment server 300. [ Here, the nearby affiliate shop may be an affiliate shop located within a predetermined radius (for example, 100 m) from the position of the employee terminal 200, and the payment history list of the nearby affiliate shop may include an approval number, Amount information, approval completion time information, and the like.

Specifically, the employee terminal 200 may include a device that manages current location information (e.g., a GPS signal), may transmit the location information to the payment server 300, And may transmit location information (e.g., address information) to the payment server 300.

After that, the employee terminal 200 can receive a payment history list of the nearby merchant that is adjacent to the location corresponding to the location information from the payment server 300. At this time, the employee terminal 200 receives the payment history list of the nearby merchant through the payment service providing application, the SMS, the messenger, and the email service, executes the program for providing the service, Can be displayed on the screen.

The payment server 300 may receive a payment request from the user terminal 100 and perform approval of the requested payment.

The payment server 300 can transmit the payment details to the user terminal 100 when the payment approval is completed.

The payment server 300 can select a nearby affiliate shop located within a predetermined radius (for example, 100 m) from the position of the employee terminal 200 and transmit the payment history list of the nearby affiliate shop to the employee terminal 200.

2 is a block diagram illustrating the configuration of a payment server 300 according to an embodiment of the present invention.

2, the payment server 300 may include a payment approval unit 310, a payment history transfer unit 320, and a payment history list transfer unit 330.

First, the payment server 300 can store identification information of the merchant, location information of the merchant, payment details of the merchant, and the like in a database.

The payment approval unit 310 may receive a payment request including the identification information of the merchant and the payment amount information from the user terminal 100. [ Here, the settlement request may be a request to settle the settlement amount corresponding to the settlement amount information to the merchant corresponding to the identification information of the merchant.

According to one embodiment, the payment approval unit 310 receives identification information of an affiliated store including at least one of mutual merchant names, representative phone numbers, and merchant numbers input to the user terminal 100 from the user terminal 100 .

According to another embodiment, the payment acceptance unit 310 can receive the identification information of the recognized merchant from the user terminal 100 that has recognized any one of the tag information, the QR code, and the barcode attached to the merchant.

According to another embodiment, the payment approval unit 310 receives location information of the user terminal 100 from the user terminal 100, and based on the location information of the affiliated store stored in the database of the payment server 300, It is possible to select a nearby franchise located within a predetermined radius (for example, 100 m) from the position of the terminal 100, and transmit the list of the selected nearby franchisees to the user terminal 100.

Then, the payment approval unit 310 can receive the identification information of the selected affiliate store from the list of the nearby affiliate stores from the user terminal 100. [

The payment approval unit 310 compares the identification information of the affiliated store included in the payment request with the identification information of the affiliated store stored in the database of the payment server 300, can do.

The payment acceptance unit 310 may receive a payment request further including information of the payment means from the user terminal 100 and perform payment approval using the payment means.

When the payment approval unit 310 completes the payment approval, the payment history transfer unit 320 can generate payment details including the approval number, the payment amount information, the merchant information, the approval completion time information, And transmits the details to the user terminal 100. Here, the approval number may be a number arbitrarily given by the payment approval unit 310 upon completion of the payment approval, and the payment amount information may be information indicating the payment approval amount.

The payment history list transmission unit 330 may receive a payment history list request from the employee terminal 200. At this time, when the payment service providing application is executed, the employee terminal 200 can automatically transmit a payment history list request to the payment history list transmission unit 330, and after execution of the payment service providing application, And may transmit a payment history list request to the payment history list transmission unit 330.

When the payment service providing application is executed, the payment history list transmission unit 330 receives the location information of the employee terminal 200 from the employee terminal 200 and stores the location information of the affiliate store stored in the database of the payment server 300 (For example, 100 meters) from the position of the employee terminal 200. In this case,

Thereafter, the payment history list transmission unit 330 can generate a payment history list of the nearby merchant through the process of acquiring and collecting payment details of each selected nearby merchant from the database of the payment server 300, And transmits the payment history list of the nearby merchant to the employee terminal 200.

When the payment approval section 310 transmits the payment history list, when the payment approval section 310 receives a payment request including the information of the payment means from the user terminal 100 and approves the payment using the payment means, The control unit 330 can transmit the payment history list of the nearby merchant to the employee terminal 200 using the payment means.

For example, when the payment approval unit 310 performs the payment approval using the card, the payment history list transmission unit 330 selects and collects only the payment completion approved cards among the payment details of the nearby merchants , The card payment history list of the nearby merchant can be generated and the card payment history list of the nearby merchant can be transmitted to the employee terminal 200.

At the time of transmitting the payment history list, the payment history list transmission unit 330 can generate a payment history list of the nearby merchant that has been approved before the predetermined period before execution of the payment service providing application, To the terminal 200.

For example, the employee terminal 200 may execute a payment service provision application at 2:00 PM and transmit a payment history list request to the payment history list transmission unit 330. At this time, the payment history list transmission unit 330 can generate a payment history list of the nearby authorized merchants from 2:00 to 1 hour before, that is, between 1:00 and 2:00, And transmits the payment history list of the nearby merchant to the employee terminal 200.

According to an embodiment of the present invention, the payment history list of the nearby merchant may include a list of authorization number, payment amount information, approval completion time information, Will be described in detail.

Table 1 shows a payment history list of a nearby merchant according to an exemplary embodiment of the present invention.

number Approval time Approval number Amount of payment One 15:30 7788567 $ 15 2 15:35 6515445 $ 25 3 16:00 7844511 $ 12,120

For example, the payment approval section 310 receives a payment request including the identification information of the merchant A from the user terminal 100 and payment amount information corresponding to "25,000 won ", and performs approval of the requested payment , The approval can be completed at "15:35".

Thereafter, the payment history transferring unit 320 transmits payment completion information corresponding to "15:35", approval number "6515445", payment amount information corresponding to "25,000 won" and A merchant information (location of the merchant A, Telephone number, etc.) to the user terminal 100. [0060]

Thereafter, when the payment service providing application is executed in the employee terminal 200, the payment history list transmission unit 330 can transmit the payment history list of the nearby merchant as shown in Table 1 to the employee terminal 200. Here, the payment history list of the nearby merchant may include only the approval completion time information, the approval number, and the payment amount, and may not include the merchant information.

Thereafter, the employee or the customer confirms whether the approval number included in the payment history transmitted to the user terminal 100 is in the payment history list of the nearby merchant transmitted to the employee terminal 200, Since the number "6515445" is the same as the approval number of the payment history list 2, it can be determined whether or not the payment request through the user terminal 100 is normally approved. That is, it is possible to easily determine whether or not the payment approval has been completed using only the approval number without exposing the merchant information.

Employees or customers can check the payment history and approval time, in addition to the approval number, by comparing the payment history with the payment history list of the nearby merchant.

3 is a diagram illustrating a process of providing a payment history list according to an embodiment of the present invention.

First, in step S301, the user terminal 100 may execute a payment service providing application, and a "payment request" menu may be selected on the payment service providing application.

Then, the user terminal 100 can receive the identification information of the merchant including at least one of the merchant's mutual name, the representative phone number, and the merchant number from the customer, and the tag information, the QR code and the barcode attached to the merchant And may receive a list of nearby affiliate stores that are adjacent to the location of the user terminal 100 from the payment server 300 and may select any of the lists of nearby affiliate stores.

Then, the user terminal 100 can receive payment amount information from the customer.

In step S302, the user terminal 100 may transmit a payment request including the identification information of the merchant acquired in step S301 and the payment amount information to the payment server 300. [ At this time, the user terminal 100 may transmit a payment request including the information of the payment means to the payment server 300.

In step S303, the payment server 300 can approve the requested payment according to the payment request received in step S302. At this time, the payment server 300 can use the information of the payment means included in the payment request to perform payment approval with the corresponding payment means.

In step S303, when the payment approval is completed, the payment server 300 can transmit the payment details including the approval number and payment amount information of the payment approval completed to the user terminal 100 in step S304. At this time, the payment server 300 can transmit the payment details to the user terminal 100 through the payment service providing application, the SMS, the messenger, and the e-mail service, and the user terminal 100 displays the received payment details on the screen can do.

In step S305, the employee terminal 200 can execute a payment service providing application.

In step S305, when the execution of the payment service providing application is completed, the employee terminal 200 can automatically transmit a payment history list request to the payment server 300 in step S306, Request "menu is selected, the payment history list request may be transmitted to the payment server 300. [

In addition, the employee terminal 200 can automatically transmit the current location information of the employee terminal 200 to the payment server 300. When the location information is inputted on the payment service providing application, the input location information is transmitted to the payment server 300 ).

In step S307, based on the location information received in step S306, the payment server 300 may select a nearby merchant located within a predetermined radius from a location corresponding to the location information, Can be generated.

In step S308, the payment server 300 may transmit the payment history list of the nearby merchant created in step S307 to the employee terminal 200. [ At this time, the payment server 300 can transmit the payment history list of the nearby merchant to the employee terminal 200 through the payment service providing application, the SMS, the messenger, the e-mail service, The history list can be displayed on the screen.

Thereafter, the customer or the employee receives the payment history displayed on the screen by the user terminal 100 from the payment server 300 in step S304, and receives the payment history from the payment server 300 in step S308, The payment history list of the nearby merchant that is displayed on the screen can be compared and confirmed. At this time, whether the approval number of the payment history displayed on the screen of the user terminal 100 is included in the payment history list displayed on the screen of the employee terminal 200, the customer or the employee confirms the payment You can determine if the authorization was successful.

As described above, according to the embodiment of the present invention, even if the customer presents payment means directly to the employee and does not request payment, the payment can be requested through the user terminal 100 held by the customer, The convenience of the customer can be increased because there is no need to wait for the request.

In addition, according to the embodiment of the present invention, since the employee can be provided as a member of a payment service providing application or receive a payment history list of a nearby merchant without having to log in separately, the convenience of the employee can be increased.

According to an embodiment of the present invention, it is possible to easily confirm whether payment approval has been normally performed between a customer and an employee through an approval number.

In addition, according to the embodiment of the present invention, since the merchant information is not exposed to the payment history list of the nearby merchant, the security of the sales information of the merchant can be secured.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present invention.

100: User terminal
200: Employee terminal
300: Payment Server
310:
320: payment history transfer unit
330: Payment history list transmission unit

Claims (12)

A method of providing a payment history list for confirming a payment in a payment server,
(a) receiving, from a user terminal, a payment request including identification information of a merchant and payment amount information, and performing approval of the requested payment;
(b) when the payment approval is completed, transmitting the payment details including the approval number and the payment amount information to the user terminal; And
(c) selecting, when an application installed in the employee terminal of the affiliate shop is executed, a nearby affiliate shop located within a predetermined radius from the position of the employee terminal, based on the position information of the employee terminal, And transmitting the payment history list of the nearby merchant including the approval number and the payment amount information to the employee terminal so that approval completion of the requested payment can be confirmed through the approval number. How to provide a payment history list. The method according to claim 1,
The step (a)
Receiving from the user terminal a payment request further including information of the payment means, performing approval for payment using the payment means,
The step (c)
And transmitting to the employee terminal a payment history list of the nearby merchant that has been approved using the payment means. The method according to claim 1,
The step (c)
And transmitting to the employee terminal a payment history list of the nearby merchant that has been approved before the predetermined time period from execution of the application. The method according to claim 1,
The step (a)
And receiving from the user terminal identification information of the franchisee, the identification information including at least one of the mutual franchisee's name, the representative telephone number, and the business number. The method according to claim 1,
The step (a)
And receiving the identification information of the merchant from the user terminal that recognizes any one of the tag information, the QR code, and the bar code attached to the merchant. The method according to claim 1,
The step (a)
Selecting a nearby affiliate shop located within a predetermined radius from the position of the user terminal and transmitting a list of the nearby affiliate shop to the user terminal; And
And receiving, from the user terminal, identification information of a selected affiliate store from a list of the nearby affiliate stores. A payment approval unit for receiving a payment request including the identification information of the merchant and the payment amount information from the user terminal and performing approval of the requested payment;
A payment history transfer unit for transferring payment details including the approval number and the payment amount information to the user terminal when the payment approval is completed; And
When the application installed in the employee terminal of the franchisee is executed, selects a nearby franchisee located within a predetermined radius from the position of the employee terminal, based on the position information of the employee terminal, And a payment history list transmission unit transmitting the payment history list of the nearby merchant including the number and the payment amount information to the employee terminal so that the approval completion of the requested payment can be confirmed through the approval number. Payment server. 8. The method of claim 7,
The settlement approval unit,
Receiving from the user terminal a payment request further including information of the payment means, performing approval for payment using the payment means,
The payment history list transferring unit,
And transmits to the employee terminal a payment history list of the nearby merchant that has been approved using the payment means. 8. The method of claim 7,
The payment history list transferring unit,
And transmits to the employee terminal a payment history list of the nearby merchant that has been approved before the predetermined time period from execution of the application. 8. The method of claim 7,
The settlement approval unit,
From the user terminal, identification information of the franchisee, the identification information including at least one of the mutual franchisee's name, the representative phone number, and the business number. 8. The method of claim 7,
The settlement approval unit,
Wherein the identification information of the merchant is received from the user terminal that recognizes any one of the tag information, the QR code, and the bar code attached to the merchant. 8. The method of claim 7,
The settlement approval unit,
And transmitting the list of the nearby affiliate points to the user terminal and receiving the identification information of the selected affiliate store from the list of the nearby affiliate stores from the user terminal, Payment server.

Images