KR102171298B1 - Method and computer-readable medium for providing payment service - Google Patents

Abstract

The present invention relates to a payment service providing method and a recording medium. The payment service providing method includes receiving a payment page creation request corresponding to a receiver account from a receiver terminal, a payment service providing device generating a payment page in response to the payment page creation request, and the generated payment Storing a page in a memory, wherein the payment page includes a payment area in which information on a payment method for paying a payment target amount can be input, and in the payment terminal, the web address of the payment page generated and stored in advance. Extracting and accessing the web address from the photographed data in the form of text or the image code corresponding to the web address, and the payment service providing device provides the payment page corresponding to the web address to the payer terminal The payment service providing device receiving payment information input from the payer terminal through the payment page, the payment service providing device transmitting the payment information to a payment means server, and the And receiving, by the payment service providing device, approval for the payment information from the payment means server.

Description

Payment service providing method and recording medium {Method and computer-readable medium for providing payment service}

The present invention relates to a payment service providing method and a recording medium.

It is a global trend for electronic payment methods such as cards to replace cash. Already, European countries such as Denmark are moving beyond a coinless society to a cashless society. Experts believe that Korea will also become closer to a cashless society in the long run. "It is true that the use of cash is already declining," said Jeong Yoo-shin, a professor of business administration at Sogang University. "If people get used to a world without cash, they can choose to stop using cash based on national consensus like some countries." In this way, as the proportion of use of payment methods that substitute for cash increases and the types of payment methods are also diversified, the grievances of product sellers, that is, recipients, are increasing.

An object of the present invention is to provide a payment service providing method and a recording medium for interpersonal transactions that provide a payment page through which a payer can pay an amount subject to payment using various payment methods including a credit card.

In addition, another object of the present invention is to provide a payment page that allows the payer to directly input the payment target amount to pay the payment target amount, and to settle the paid payment target amount to the recipient's account 　Payment service providing method and recording medium It is to provide.

In addition, another object of the present invention is to allow the payer to easily move to the corresponding payment page and pay the payment target amount through a payment method of his or her choice by photographing a link or image code to the payment page of the recipient previously created. It is to provide a payment service providing method and a recording medium.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention that are not mentioned can be understood by the following description, and will be more clearly understood by examples of the present invention. In addition, it will be easily understood that the objects and advantages of the present invention can be realized by the means shown in the claims and combinations thereof.

A payment service providing method according to an embodiment of the present invention includes receiving a request for generating a payment page corresponding to a recipient account from a receiver terminal, and a payment service providing device, a payment page in response to the request for generating a payment page. And storing the generated payment page in a memory, wherein the payment page includes a payment area for inputting payment method information for paying a payment target amount, in the payer terminal, generated in advance Extracting and accessing the web address from the photographed data in the text form of the web address of the stored payment page or the image code corresponding to the web address, and the payment service providing device, the payment corresponding to the web address Providing a page to the payer terminal, receiving, by the payment service providing device, payment information input from the payer terminal through the payment page, the payment service providing device, to the payment means server And transmitting information, and receiving, by the payment service providing device, approval for the payment information from the payment means server.

In addition, the payment method information may include the payer's card number, card expiration date, or CVC code.

In addition, the payment page may further include a payment target amount input area for inputting the payment target amount information.

In addition, it may further include receiving, from the receiver terminal, a confirmation of the payment target amount input to the payment page.

In addition, the payment page may display the payment target amount input area and the payment area on one page so that a payer can input payment information in the payment page without moving a page.

In addition, the payment page generation request includes payment target amount information including the payment target amount, and the payment page includes a payment target amount input area for changing a type of currency for the payment target amount, and the It may include a payment area in which payment method information for paying a payment target amount can be input.

In addition, the payment page generation request includes information on the payment object amount based on a first currency to be settled by the receiver from the receiver terminal, and the payment page includes the payment object amount as the first currency. And a payment target amount input area that can be changed to a different second currency, and the payment service providing device stores host account information for each of a plurality of currencies, and the plurality of host accounts are in the first currency. At least a host account for and a host account for the second currency, wherein the receiving of approval for the payment information comprises: a target for payment of the first currency from the host account for the first currency to the receiver's account It may include receiving a remittance command to remit money.

In addition, the payment page generation request further includes sales type information, and the payment page providing unit may determine the type of the payment page as one of a plurality of types based on the sales type information.

In addition, the sales type information indicates whether a transaction corresponding to the payment target amount requires delivery of a product, and the type of the payment page includes a first type including an area for receiving a delivery address and a delivery address. It may include a second type that does not include the receiving area.

In addition, the sale type information indicates whether a transaction corresponding to the payment target amount is regularly generated, and the type of the payment page includes a third type including an area for setting periodic payment and an area for setting periodic payment. It may include a fourth type that does not contain.

delete

delete

delete

According to another embodiment of the present invention, a payment service providing method includes the steps of receiving image data including a link or image code of a payment page corresponding to a recipient account from a payer terminal, the link or the image code from the image data. The image code is extracted, and the extracted link or the payment page corresponding to the image code is provided to the payer terminal, wherein the payment page includes a payment target amount input area into which a payment target amount is input and the payment target amount. Including a payment area into which payment method information for payment is input, including payment target amount information input through the payment target amount input area from the payer terminal, and payment method information input through the payment area Receiving payment information, and transmitting the payment information to a payment means server, and receiving approval for the payment information from the payment means server.

In the method of providing payment service and recording medium for interpersonal transactions according to the present invention, the receiver can easily request the creation of a payment page through which payment can be made using various payment methods, and the payer can use the created link or Just by taking an image, you can easily access the payment page and make payment through your preferred payment method. Through this, the present invention can improve payment convenience during a transaction between a receiver and a payer.

In addition, according to the method of providing a payment service for interpersonal transactions and the recording medium according to the present invention, the recipient only needs to subscribe to the payment service according to the embodiments of the present invention without the need to individually register an affiliated store for various types of payment means. You can receive payment regardless of the time, place, amount, or type of payment method.

In addition, according to the method of providing payment service and recording medium for interpersonal transactions according to the present invention, the receiver and the settler can directly transact using not only the same currency but also different currencies, so that payment can be easily performed through various payment methods abroad. You can do so, so you can be free from local restrictions on payment.

The effects of the present invention are not limited to the above-described effects, and those skilled in the art can easily derive various effects of the present invention from the configuration of the present invention.

1 is a diagram showing the configuration of a payment system according to an embodiment of the present invention.
FIG. 2 is a block diagram showing an example of a configuration of a payment service providing device provided in the server shown in FIG. 1.
3 is a detailed configuration diagram according to an embodiment of the payment page providing unit shown in FIG. 2.
4 is a detailed configuration diagram according to an embodiment of the payment page generator shown in FIG. 3.
5 is a detailed configuration diagram according to an embodiment of the financial management unit shown in FIG. 2.
6 is a detailed configuration diagram according to an embodiment of the host account management unit shown in FIG. 2.
7 is a flowchart of a payment service providing method according to an embodiment of the present invention.
8 is a block diagram schematically illustrating an apparatus for obtaining a payment page according to an embodiment of the present invention.
9A and 9B are flowcharts of a method of obtaining a payment page according to an embodiment of the present invention.
10 is an example of a payment page request screen displayed on a receiver terminal.
11 is another example of a payment page request screen displayed on a receiver terminal.
12 is another example of a payment page request screen displayed on a receiver terminal.
13 is an example of a screen in which a web address of a payment page is displayed in a text format on a receiver terminal when any one of the buttons shown in FIGS. 10 to 12 is selected.
14 is an example of a screen on which a second payment page is displayed according to an example.
15 is an example of a screen on which a second payment page is displayed according to another example.
16 is an example of a screen on which a first payment page is displayed according to an example.
17 is an example of a printed material on which an image code is printed according to an example.
18 is another example of a printed material on which an image code is output.

Since the present invention can apply various transformations and have various embodiments, specific embodiments are illustrated in the drawings and will be described in detail in the detailed description. Effects and features of the present invention, and a method of achieving them will be apparent with reference to the embodiments described later in detail together with the drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various forms.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, and when describing with reference to the drawings, the same or corresponding constituent elements are assigned the same reference numerals, and redundant descriptions thereof will be omitted. .

In the following embodiments, terms such as first and second are not used in a limiting meaning, but are used for the purpose of distinguishing one component from another component. In the following examples, the singular expression includes the plural expression unless the context clearly indicates otherwise. In the following embodiments, terms such as include or have means that the features or elements described in the specification are present, and do not preclude the possibility of adding one or more other features or elements in advance. In the drawings, components may be exaggerated or reduced in size for convenience of description. For example, the configurations shown in the drawings are arbitrarily shown for convenience of description, and thus the present invention is not necessarily limited to what is shown.

1 is a diagram showing the configuration of a payment system according to an embodiment of the present invention.

Referring to FIG. 1, a payment system according to an embodiment of the present invention includes a server 100, a plurality of user terminals 200 and 300, a payment means server 400, and a communication network 500 connecting them. . Hereinafter, when the plurality of user terminals 200 and 300 are classified and referred to, for convenience of description, the receiver terminal 200 and the payer terminal 300 are respectively referred to.

Although two user terminals 200 and 300 and one payment means server 400 are shown in FIG. 1, the number is not limited, and a smaller or larger number of user terminals and payment means servers may be provided. .

The payment service provided according to an embodiment of the present invention provides an escrow service that mediates currency transactions between a receiver (eg, a seller who sells a product) and a payer (eg, a purchaser who purchases a product). to provide. The receiver generates a personalized payment page using the payment service provided according to an embodiment of the present invention, and the payer accesses the payment page to perform payment. The payment system according to an embodiment of the present invention provides a payment service that can be used even when a receiver is not registered as an affiliated store for a payment method used by a payer. The payment system according to an embodiment of the present invention may provide a payment service that can be used even when the types of currencies used by the payer and the receiver are different.

Referring to FIG. 1, the server 100 receives a personalized payment page request from the receiver terminal 200 to the receiver, generates a payment page, and provides access information of the payment page to the receiver terminal 200. , The payment is finally established by receiving payment information from the payer terminal 300 connected to the payment page. The receiver terminal 200 may transmit the access information of the payment page to the payer terminal 300, but when the payment page access information is delivered offline, the online delivery may be omitted.

The server 100 may receive information on delivery of the payment amount from the payment method server 400 and generate a remittance command to settle the payment amount to the receiver. Remittance can be made to the bank account of the recipient who has been previously registered. Although not shown in the drawings, the server 100 according to an embodiment of the present invention may include a memory, an input/output unit, a program storage unit, and a control unit.

The user terminals 200 and 300 refer to communication terminals capable of using web services in a wired or wireless communication environment. Here, the user terminals 200 and 300 may be a user's personal computer or a user's portable terminal. In FIG. 1, the user terminals 200 and 300 are shown as smart phones, but the spirit of the present invention is not limited thereto, and a terminal equipped with an application capable of web browsing as described above can be borrowed without limitation. have.

Meanwhile, the user terminals 200 and 300 include a display unit that displays a screen and an input device that receives data from a user. The input device may include, for example, a keyboard, a mouse, a trackball, a microphone, a button, a touch panel, a camera, a motion sensor, etc., but is not limited thereto.

The payment method server 400 provides a service related to a payment method used by a payer. The payer may first receive a payment method provided by the payment method server 400 and then use a previously issued payment method in a payment service provided according to an embodiment of the present invention. According to an embodiment, the payment method used by the payer may be a financial account. For example, the payment means server 400 may be a server managed by a financial institution, and the financial account may be a bank account. According to another example, the payment method server 400 is a server managed by a provider of a payment solution using the Internet (eg, PayPal, Alipay, Tenpay, etc.), and the financial account is an account issued by the aforementioned payment solution provider. Can be According to another example, the payment method server 400 is a server managed by a credit card company, and the payment method may be a credit card. However, since the above-described example has been illustrative of a case in which the embodiments of the present invention can be implemented, the present invention is not limited thereto.

Although not shown in the drawings, the payment means server 400 according to an embodiment of the present invention may include a memory, an input/output unit, a program storage unit, and a control unit.

The communication network 500 may connect the user terminals 200 and 300, the server 100, and the payment means server 400. For example, the communication network 500 provides a connection path so that the user terminals 200 and 300 can transmit and receive packet data after accessing the server 100 and/or the payment means server 400. The communication network 500 is a wired network such as LANs (Local Area Networks), WANs (Wide Area Networks), MANs (Metropolitan Area Networks), ISDNs (Integrated Service Digital Networks), wireless LANs, CDMA, Bluetooth, satellite communication, It may cover wireless networks such as 3G, 4G, and 5G, but the scope of the present invention is not limited thereto.

In the payment system according to an embodiment of the present invention, the payment page, which is requested to be created or provided by the receiver terminal 200, is accessed by the payer terminal 300, not the receiver, and transmits payment information to the server 100. Provide payment service to deliver. A transaction exists between the receiver and the payer, and the payer may use the payment page to pay the payee the amount subject to payment as a transaction benefit. According to this, the receiver in the position of providing the commerce service requests a payment page through which payment can be made using various payment methods, obtains the web address of the payment page, and provides it to the payer, thereby contributing to the convenience of the payer. It has the effect of being able to provide services easily. Since the payer can perform payment without additional page movement or procedure simply by accessing the corresponding payment page and inputting payment information, the payment service according to an embodiment of the present invention greatly contributes to the convenience of the payer.

According to an example, the payment page is provided so that the payer can directly input a payment target amount. In this case, a payment page corresponding to the receiver account is provided, and the payer may access the payment page provided corresponding to the receiver account to directly input the payment object amount to pay the payment object amount to be settled to the receiver. In other words, it is convenient for the payer to perform payment simply by accessing the payee’s payment page without cumbersome procedures and entering and transmitting information without moving the page. From the place of the payer, it is convenient to use various payment methods from the payer. Since it is convenient to have a payment page through which a payment target amount can be received and a web address of the corresponding payment page can be easily requested, the payment service according to an embodiment of the present invention contributes to the convenience of both the receiver and the payer.

FIG. 2 is a block diagram showing an example of a configuration of a payment service providing device 110 provided in the server 100 shown in FIG. 1.

The payment service providing apparatus 110 according to an embodiment of the present invention may correspond to at least one or more processors, or may include at least one or more processors. Accordingly, the payment service providing device 110 may be driven in a form included in another hardware device such as a microprocessor or a general-purpose computer system, and may be mounted on the server 100.

The payment service providing apparatus 110 shown in FIG. 2 shows only the components related to the present embodiment in order to prevent the features of the present embodiment from being blurred. Accordingly, it can be understood by those of ordinary skill in the art related to the present embodiment that other general-purpose components may be further included in addition to the components shown in FIG. 2. In addition, classifying the functions performed by each block included in the payment service providing device 110 shown in FIG. 2 may be for convenience of description. As a result, any one of the payment service providing device 110 The function described as being performed by the block may be performed by another block included in the payment service providing apparatus 110.

The payment service providing apparatus 110 according to an embodiment may receive a payment page generation request from the receiver terminal 200 and provide the payment page to the receiver terminal 200 or the payer terminal 300. The payer may access the payment page using the receiver terminal 200 or the payer's own payer terminal 300. The payment service providing device 110 receives payment information transmitted by a payer through a payment page, checks the payment information, and finally establishes payment. When the payment is established, the server 100 may notify the settlement of the settlement to the receiver, and may notify the settlement of the settlement to the payer. In addition, the server 100 calculates the payment amount to the receiver's account and receives the payment amount from a payment method company (eg, a credit card company) used by the payer, thereby completing a basic procedure related to the payment.

The receiver subscribes to a payment service provided according to an embodiment of the present invention in advance, and registers account information to be settled with the server 100. Recipients, without complicated prior procedures, simply subscribe to the payment service provided according to an embodiment of the present invention and use the payment service, so that the payer can easily pay the price regardless of the time, place, or type of payment method. can do. As the accessibility of the payer is improved, the sales volume of the receiver may increase.

Referring to FIG. 2, a payment service providing device 110 according to an embodiment of the present invention includes a communication unit 111, a payment page providing unit 112, and a financial management unit 113. Hereinafter, each configuration of the payment service providing device 110 will be described in detail.

The communication unit 111 according to the 　 embodiment transmits/receives data with the 　 user terminals 200 and 300 and the payment means server 400, and also transmits/receives data with other external servers. The communication unit 111 receives a request for generating a payment page from the receiver terminal 200.

The payment page provided according to an embodiment of the present invention may be a first payment page or a second payment page. The first payment page does not include information on the amount subject to payment, and the amount subject to payment entered in the area to input the amount subject to payment and the area to enter the amount subject to payment so that the buyer can directly input the amount subject to payment. It is provided to include a payment area where you can pay . The second payment page is provided to display a payment target amount designated by a receiver and include a payment area through which the displayed payment target amount can be settled. On the first payment page, the purchaser may directly input the payment target amount to pay the input payment target amount. The second payment page displays information on the payment target amount received from the receiver by the communication unit 111, and the purchaser can pay the payment target amount designated by the receiver on the second payment page.

The payment page generation request received by the communication unit 111 may be a first payment page generation request or a second payment page generation request. The request for creating the first payment page may include account information of the receiver for receiving settlement of the payment paid by the payer, and the request for generating the first payment page and the first payment page may correspond to the receiver account. The receiver's account may be a financial account, but it will be said that only identification information of the receiver's account subscribed to the payment system according to an embodiment of the present invention is sufficient. The request for generating the first payment page does not include information on the amount subject to payment.

The request for generating the second payment page includes account information of the recipient and information about the payment target. The payment target information includes information about the amount of money to be paid. The payment target amount information may include currency information as a reference. For example, the payment target amount information may be based on the first currency. Hereinafter, the first currency means the base currency of the amount subject to payment. The currency that is the basis of the payment target amount information may be directly input by the receiver terminal 200 or a default currency may be set in advance. According to another example, the currency that is the basis of the payment target amount information may be designated as a specific currency by the server 100, and in this case, the request for generating a second payment page received from the receiver terminal 200 is May not include currency information.

The payment page generation request may further include information such as a name of a product for sale, a sale type, and a payment page link output type.

The communication unit 111 transmits a payment page generation request to the payment page providing unit 112 and obtains a link to access the payment page from the payment page providing unit 112 to provide the receiver terminal 200 and/or the payer terminal 300. ).

The communication unit 111 receives data received through the payment page, for example, payment information including payment target amount information and payment method information input through a payment target amount input area included in the payment page from the payer terminal 300 It is transmitted to the financial management unit 113.

The payment information includes payment method information. Payment information may include reference currency information. For example, the payment information may include information that the currency used as the basis of the payment amount is the second currency, and may further include information on the payment amount based on the second currency. The payment information may include payment method information input through a space provided to input payment method information (eg, credit card information) in the payment page. The communication unit 111 may transmit credit card information to a server of a corresponding credit card through an API for a corresponding credit card to request payment approval, and receive payment approval for this from the credit card server.

The designation of the first currency and the second currency separately is for identification convenience only, and the first currency and the second currency are not necessarily different and may be the same. Payment information may include payment method information, payment amount, and payment currency information. The communication unit 111 may receive payment information and transmit the received payment information to a payment institution to receive payment approval from the payment institution. For example, if the payment method is a credit card, the payment information may include a card number, password, expiration date, and CVC, and the communication unit 111 transmits the received payment information to the card company to receive payment approval from the card company. I can.

However, the present invention is not limited thereto, and a method of transmitting payment approval information from the payer terminal 300 to the communication unit 111 may be used after the payer communicates with the payment institution to directly approve the payment.

According to an embodiment, the 　payment page 　providing unit 112 generates and provides a payment page corresponding to the request for generating a payment page received from the receiver terminal 200 by the communication unit 111. The payment page providing unit 112 generates and provides a first payment page through which a payer can freely input a desired amount and make a payment in response to a request for generating the first payment page. The payment page providing unit 112 creates and provides a second payment page through which a corresponding payment amount can be paid by referring to payment amount information included in the second payment page generation request.

The payment page provider 112 can perform payment by referring to the payment page generation request received from the receiver, and by the payer directly inputting payment information within one payment page without additional dynamic such as page movement. Thus, a payment page that displays a first area for receiving or displaying a payment target amount and a second area for inputting payment method information on one page is generated and provided.

In the first payment page, the first area includes a payment target amount input area in which a payment target amount can be input, and an amount may be input into the payment target amount input area by a payer. In the first payment page, the second area includes a payment area for inputting information on a payment method capable of paying the payment target amount input in the payment target amount input area.

On the second payment page, the first area displays the payment target amount specified by the receiver, and the second area corresponds to the payment target amount specified by the recipient, for example, the payment target amount information included in the request to create the second payment page. And a payment area for inputting information on a payment method through which a payment target amount is settled.

According to an example, the payment page providing unit 112 provides the payment page web address to the receiver terminal 200 through the communication unit 111. The payment page providing unit 112 provides at least one of a text format of a web address of a payment page or an image format corresponding to the web address. That is, the address of the payment page may be provided in the form of a link to a web address in text form or an image code (2D barcode, for example, a QR code) corresponding to the web address. In this example, the receiver terminal 200 transmits the payment page address to the payer terminal 300 online or offline, and the payer terminal 300 accesses the payment page to input payment information.

According to another example, the receiver terminal 200 may transmit a request for generating a payment page including information of the payer terminal 300 to the communication unit 111. In this example, the payment page providing unit 112 directly transfers the payment page address to the payer terminal 300 through the communication unit 111 by referring to the information of the payer terminal 300 received from the receiver terminal 200. I can deliver.

The payment page may provide one or more application programming interfaces (APIs) for payment methods. For example, the payment page may provide an api for each of the plurality of payment methods so that payment information may be input by selecting one of the plurality of payment methods. The api of each payment method may be provided by the server 400 of each payment method or a website. Each of the plurality of payment means may be used to pay for at least one currency. For example, the plurality of payment means may include a first payment method and a second payment method, a first payment method may pay a first currency, and a second payment method may be a second payment method different from the first currency. 2 It may be that you can pay for currency.

The payment method may be a bank account or a credit card, and may include various payment solutions such as PayPal. Depending on the type of api of each payment method, the payment page may directly receive payment method information (e.g., card number, etc.), or user account information for accessing the server of the payment method (e.g., ID And password). The payment page may provide a space for inputting credit card information. The payment page may provide a space for inputting user account information for accessing the payment solution.

The payment page may be generated to use a payment method capable of selecting any one of a plurality of currencies to pay. Examples of such payment methods include worldwide networked credit cards (ex. VISA) and other payment solutions (such as PayPal). After selecting a corresponding payment method, the user may proceed with payment by selecting a currency in which he/she intends to pay, or may proceed with payment in a currency designated by default for the corresponding payment method.

According to an embodiment of the present invention, the receiver may designate a currency to be paid by the payer while transmitting a request for generating a payment page to the communication unit 111. For example, the request for creating a payment page may include a payment target amount based on a first currency to be settled by the receiver and second currency information for the payer to pay the payment target amount. In this case, the payment page providing unit 112 may generate a payment page that selectively provides an api that can use a payment method capable of paying a second currency. The payment page providing unit 112 may generate a payment page displaying payment amount information obtained by converting a payment target amount in a first currency into a second currency. Alternatively, the payment page providing unit 112 may generate a payment page that displays a payment target amount in the first currency and payment amount information obtained by converting the payment target amount in the first currency into a second currency. At this time, the exchange rate may apply a real-time exchange rate obtained using a real-time exchange rate api, and a notice indicating that the detailed payment amount may change depending on the payment method and time may be displayed on the payment page.

The financial management unit 113 according to an embodiment is a payment information authentication operation, a settlement operation between a payment method company and a payment service according to an embodiment of the present invention, and settlement between a payment service and a receiver according to an embodiment of the present invention. Performing financial business related to payment such as work. For example, the financial management unit 113 settles the payment target amount paid by the payer to the account of the receiver.

The financial management unit 113 according to an example transmits the payment information received through the payment page to the payment method server 400 and receives approval for payment information from the payment method server 400. For example, the financial management unit 113 transmits the credit card information and payment amount information received through the payment page to the payment means server 400, and receives approval for payment information from the payment means server 400. Alternatively, the financial management unit 113 transmits the account information of the payment solution (PayPal, Alipay, etc.) received through the payment page to the corresponding payment method server 400, and approves the account information from the payment method server 400. Receive. When approval for payment information is received, the financial management unit 113 processes the payment as being established. The financial management unit 113 accumulates a payment target amount corresponding to the paid amount in the recipient account.

The settlement operation between the payment method company and the payment service according to an embodiment of the present invention is a job of receiving remittance of the second currency from the payment method company of the second currency used by the payer, and the payment service according to an embodiment of the present invention The settlement work between the recipients is the work of transferring the first currency to the recipient's account.

The settlement operation may be performed for each payment case, or may be performed regularly by calculating the accumulated settlement amount according to a preset period standard. Alternatively, when a settlement request is transmitted from the subject to be settled, the settlement may be performed irregularly on the amount requested for settlement or the settlement amount accumulated during that time.

First, in connection with the settlement work between the payment method and the present payment service, the financial management unit 113 receives a second currency remittance from the payment method company of the second currency used by the payer to the host account for the second currency of the present payment service. The remittance may also be performed for each payment case, or may be performed in a manner of calculating the accumulated settlement amount according to a preset period standard and performing regular or irregular settlement. Alternatively, when a settlement request is sent from the settlement server 100, the settlement request may be performed on the requested amount or the accumulated settlement amount during that time.

The financial management unit 113 transfers the payment amount to the host account for the payment currency by referring to the payment approval received after transmitting payment information or payment information including payment institution, payment amount, and payment currency information to the payment institution. The request can be sent to the corresponding payment institution.

However, in connection with the settlement of payments between each payment method and the present payment service, the remittance request does not necessarily need to be pre-transmitted from the present payment server 100, and the settlement may be made without a separate remittance request according to a previously promised method. . For example, the financial management unit 113 may transfer host account information of each currency to a payment method company capable of paying each currency in advance. For example, host account information of the second currency may be provided to a credit card company that handles the second currency. In this case, without a separate request, a method of remittance of the accumulated settlement amount according to a schedule previously agreed upon by the payment method company may be used according to the regularly delivered host account information.

Next, in connection with the settlement operation between the payment service and the receiver, the financial management unit 113 generates a remittance command for remittance of the amount subject to payment of the first currency from the host account for the first currency to the account of the receiver. For example, the financial management unit 113 accumulates the amount subject to payment in the first currency in association with the recipient's information (eg, account information), and the amount subject to payment in the first currency accumulated in association with the recipient's information You can create a remittance order. The financial management unit 113 transmits the generated remittance command to the communication unit 111, the communication unit 111 transmits the remittance command to a financial institution, and the financial institution may transfer money between accounts. However, remittance of the amount subject to payment is not limited to remittance of only the amount subject to payment, but refers to remittance including the amount subject to payment. The financial institution that receives the remittance command is the bank server of the host account for the currency to be remitted (in this embodiment, it is the first currency).

According to an example, a remittance command may be generated for each payment case, and the remittance amount may include only a payment target amount for each payment case. According to another example, a remittance order may be generated on a regular basis according to a preset period or irregularly according to a preset condition, targeting accumulated payments, and the remittance amount is the accumulated payment. It may be the total sum of the amount subject to payment of the cases. According to another example, the remittance order is collectively generated to remit the total amount of the accumulated payments targeting the accumulated payments when there is a settlement request by the receiver, or the settlement request amount specified by the receiver. Can be created to remit.

The remittance order may be transmitted to a financial institution of the first currency that is the basis of the remittance amount. The remittance order contains the account information of the recipient who can deposit the first currency. For example, when the first currency is KRW (KRW) and 10,000 KRW (KRW) is settled to the recipient, the financial management unit 113 may convert KRW 10,000 (KRW) from the host account for KRW (KRW) of the payment service to the recipient's account. A remittance command for remittance of KRW) is transmitted to the server of the first bank that issued the host account. The first bank may be a Korean bank that handles won (KRW). The receiver's account may also be an account issued by a bank that handles KRW, and the receiver's account information is input and stored in advance from the receiver when the receiver subscribes to the payment service according to an embodiment of the present invention. I can.

According to an embodiment, the financial management unit 113 generates a remittance command for remittance of the payment target amount in the first currency from the host account for the first currency to the receiver's account, the amount of which the fee is subtracted from the payment target amount. You can create a remittance order to remit money. The financial management unit 113 may set a higher fee when the first currency of the receiver and the second currency of the payer are different than when the first currency of the receiver and the second currency of the payer are the same. When the first currency of the receiver and the second currency of the payer are different, the financial management unit 113 is a non-major currency (for example, than when both the first currency and the second currency are major currencies (e.g., dollar, euro, yen, etc.) , Pounds, francs, etc.), you can set a higher fee.

3 is a detailed configuration diagram according to an embodiment of the payment page providing unit 112 shown in FIG. 2.

Referring to FIG. 3, the payment page providing unit 112 includes a page type determining unit 1121, a payment page generating unit 1122 and a link output unit 1123.

The page type determination unit 1121 according to an embodiment determines the type of the payment page to one of a plurality of types. The type of payment page may be determined based on a request for generating a payment page received by the communication unit 111. According to an embodiment, the 　 payment page generation request includes type information of the payment page. The type information of the payment page includes information indicating whether the payment page requested by the receiver to be generated is a first payment page or a second payment page.

The receiver may request the creation of the first payment page by selecting the first payment page creation request button provided on the payment page creation page, and the second payment by selecting the second payment page creation request button provided on the payment page creation page You can request the creation of a page. Therefore, according to an example, the type information of the payment page may be determined according to a button selected by the recipient.

Meanwhile, the receiver inputs the amount to be paid and then selects the second payment page creation request button. Accordingly, according to another example, the type information of the payment page may be determined according to whether or not the payment page generation request includes the payment target amount information.

The type information of the payment page may further include sales type information. The sales type information is information indicating whether the sale of the product by the payment is a sale requiring delivery of the product or a sale that does not require delivery of the product. The receiver can designate the type of sale while requesting the payment page creation on the payment page creation page. For example, on the payment page creation page, the receiver designates whether a payment requires delivery of a product or a payment that does not require delivery of a product. A payment that does not require delivery of a product may correspond to, for example, a direct transaction or a simple remittance that does not involve product sales.

Based on the sales type information, the page type determination unit 1121 determines the type of the payment page as a first type to include an area in which a delivery address is input in case of payment requiring delivery of a product, and delivery of a product is unnecessary. In the case of payment, the type of the payment page is determined as the second type so that the area in which the delivery address is input is not included.

The payment page generation unit 1122 according to an embodiment may generate a payment page differently according to the determination of the page type determination unit 1121. When the payment page is determined as the first type by the page type determination unit 1121, the payment page generation unit 1122 generates a first type of payment page including an area for receiving a delivery address. When the payment page is determined as the second type by the page type determination unit 1121, the payment page generation unit 1122 generates a second type of payment page that does not include an area for receiving a delivery address.

For example, if the payment page according to the type information of the payment page is a first type of payment page, the payment page generator 1122 includes an area for receiving an input of a delivery address and a payment target amount is not specified. Create a first type of payment page. When the payment page according to the type information of the payment page is a second payment page of the first type, the payment page generator 1122 includes an area for receiving an input of a delivery address and a second payment of the first type in which a payment target amount is specified. Create a page. When the payment page according to the type information of the payment page is the first payment page of the second type, the payment page generator 1122 does not include an area for receiving an input of the delivery address, and the payment target amount is not specified. Create a first payment page. When the payment page according to the type information of the payment page is a second type of second payment page, the payment page generator 1122 does not include an area for receiving an input of the delivery address, and the second type of payment is specified. Create a payment page.

In an embodiment of the present invention, the type information of the payment page may include sales type information only when a request to generate the second payment page is requested. The payment page generator 1122 may determine the type of the second payment page as any one of a plurality of types based on the sales type information. For example, it may be determined as a first type including an area for receiving an input of a delivery address or a second type not including an area for receiving an input of a delivery address. In the present embodiment, the payment page generator 1122 is a first payment method. When a page is generated, a first type of payment page may always be provided, or a second type of payment page may always be provided. The type of the first payment page may be preset by the receiver and fixed to one type.

The link output unit 1123 according to an embodiment determines the type to output the access address of the payment page. The output type may be determined based on a request for generating a payment page received by the communication unit 111. According to an embodiment, the payment page generation request includes payment page link output type information. The payment page link output type information is information indicating a method of outputting the access address of the payment page generated by the payment page generator 1122.

The receiver may designate a payment page link output type while requesting the payment page creation on the payment page creation page. For example, on the payment page creation page, the recipient designates whether to receive a link to a payment page in a text form of a web address or to receive a link to a payment page in an image code (eg, a QR code). Alternatively, the receiver may designate a payment page link output target on the payment page creation page. For example, if the receiver wants to send the payment page link directly from the server 100 to the payer terminal 300, the payment page link is created by entering the identification information of the payer terminal 300 on the payment page creation page. The payment page may be requested to be directly output to the payer terminal 300.

In response to a payment page generation request received from a receiver, the page type determination unit 1121 according to an embodiment outputs a link output type to a web address of the payment page in text format, and the payment page One of the second types of outputting the image code corresponding to the web address is determined, and the link output unit 1123 outputs the web address of the payment page according to the determined link output type.

The link output unit 1123 according to an embodiment determines a link output target in response to a payment page generation request received from a receiver. For example, when the payment page generation request received from the receiver includes identification information of the payer terminal 300, the link output unit 1123 determines the link output target as the payer, and the payment page generation request is (300) If identification information is not included, the target of link output is determined as the recipient. In this embodiment, the link output unit 1123 is a first type of outputting the web address of the payment page to the receiver terminal in response to the payment page generation request, and corresponding to the web address of the payment page to the receiver terminal. It can be determined as one of the second type for outputting the image code, the third type for outputting the web address of the payment page to the payer terminal, and the fourth type for outputting the image code corresponding to the web address of the payment page to the payer terminal. have.

The link output unit 1123 outputs a link to the payment page according to the determined payment page link output type. When the payment page link output type is the first type, the link output unit 1123 provides the web address of the payment page to the receiver terminal. When the payment page link output type is the second type, the link output unit 1123 provides an image code corresponding to the web address of the payment page to the receiver terminal. When the payment page link output type is the third type, the link output unit 1123 provides a web address of the payment page to the payer terminal. When the payment page link output type is the fourth type, the link output unit 1123 provides an image code corresponding to the web address of the payment page to the receiver terminal.

When the link output unit 1123 outputs a link to the payment page to the receiver terminal 200, the link output unit 1123 may provide a link to the payment page in a pop-up window displayed on the display unit of the receiver terminal 200. have. The link output unit 1123 may provide an icon capable of executing an application capable of transmitting a link of a payment page to the payer terminal 300 together with the link.

In one embodiment of the present invention, after signing up for a payment system provided according to an embodiment of the present invention, the receiver is connected to his/her account to request the creation of a personalized first payment page, and the payment service providing device 110 Can be transferred to. The request for generating the first payment page may be directly generated and transmitted by the recipient, but when the recipient subscribes to the payment system, the request for generating the first payment page may be automatically transmitted to the payment service providing device 110. For example, a request for creating a first payment page may be included in the payment system subscription request.

In this embodiment, the payment service providing device 110 generates a first payment page according to the above-described first payment page creation request, stores the web address of the first payment page, and then requests the first payment page from the receiver. Whenever this is received, the web address of the previously generated first payment page may be provided. For example, when the communication unit 111 receives a request for generating a first payment page, the payment page providing unit 112 may provide a text form and a web address of the web address of the first payment page generated in response to the first payment page generation request. At least one of the types of image codes corresponding to may be stored in a storage (not shown) provided in the server 100 or provided to communicate with the server 100. Thereafter, the communication unit 111 may receive a request for providing the first payment page from the receiver terminal 200. The payment page providing unit 112 provides at least one of a text format of a web address of a payment page stored in the storage and an image code corresponding to the web address to the receiver terminal 200 in response to a request for providing the first payment page. can do.

According to an example, the payment service providing device 110 provides the generated web address of the first payment page to the receiver terminal 200 so that the receiver terminal 200 provides the web address of the first payment page to the receiver terminal. It may be stored in a memory provided in 200 or provided to communicate with the receiver terminal 200. In this case, when the web address of the first payment page is required, the receiver terminal 200 may read the web address of the first payment page stored in the memory by itself without communicating with the payment service providing device 110.

As described above, in the present embodiment, the payment service providing device 110 may separately receive a request for generating a first payment page and a request for providing a first payment page from the receiver terminal 200. In response to a request for generating the first payment page, a first payment page may be created and the web address of the first payment page may be stored in the server 100 or provided to the receiver terminal 200, and the first payment page may be provided. In response to the request, the web address of the first payment page previously generated and stored in the server 100 may be provided to the receiver terminal 200.

The first payment page is provided so that a payer can directly input a payment target amount, and a plurality of payments for paying different payment target amounts may be processed through a pre-generated first payment page. That is, the first payment page may be used repeatedly to generate a plurality of payments. Since the first payment page does not contain information on the amount subject to payment and corresponds to the account information of the recipient to be settled, the first payment page is created 1:1 for each of the plurality of recipient accounts, and the web address of each first payment page May be stored in the server 100 corresponding to each recipient account.

Meanwhile, when the communication unit 111 receives a request for a second payment page, the payment page providing unit 112 generates a second payment page and displays a text form of the web address of the second payment page and an image code corresponding to the web address. At least one of the forms is provided to the recipient terminal 200.

The second payment page is provided to display a payment target amount previously designated by the receiver, and when payment information is received through the second payment page and all processes for payment are completed, the second payment page may be closed. That is, the second payment page may be used for a single use and one payment may be generated.

4 is a detailed configuration diagram of the payment page generator 1122 shown in FIG. 3 according to an embodiment.

Referring to FIG. 4, a payment page generating unit 1122 according to an embodiment of the present invention includes a first payment page generating unit 41 and a second payment page generating unit 42.

The first payment page generation unit 41 generates a first payment page, stores the web address of the first payment page, or transmits it to the receiver terminal 200. The first payment page generation unit 41 generates a first payment page when it is determined by the page type determination unit 1121 that the payment page generation request received by the communication unit 111 is a first page generation request. The first payment page generation unit 41 may store the web address of the first payment page in the server 100, and the link output unit 1123 stores the web address of the first payment page in the form of text or image code. It can be output to the receiver terminal 200.

The second payment page generation unit 42 generates a second payment page and transmits the web address of the second payment page to the receiver terminal 200. The second payment page generation unit 42 generates a second payment page when it is determined by the page type determination unit 1121 that the payment page generation request received by the communication unit 111 is a second page generation request. The second payment page generator 41 may output the web address of the second payment page to the receiver terminal 200 in the form of text or image code. The second payment page generation unit 42 may generate a second payment page of the first type or the second type according to the type determined by the page type determination unit 1121.

Even if there is content omitted in relation to FIG. 4, the content described in connection with the payment page generator 1122 in FIG. 3 may also be applied to the payment page generator 1122 shown in FIG. 4.

5 is a detailed configuration diagram of the financial management unit 113 shown in FIG. 2 according to an embodiment.

Referring to FIG. 5, the financial management unit 113 includes a user account management unit 1131, a host account management unit 1132, and a payment management unit 1133.

The user account management unit 1131 manages accounts of users who have subscribed to the payment service. For example, it manages the accumulated settlement amount, settlement status, settlement processing, etc. for each user account. The user account management unit 1131 manages a task of receiving remittance from a payment method account and a task of remitting money to an account of a user (recipient).

The host of the payment service according to an embodiment may have a host financial account for each currency provided by the payment system according to the embodiment. For example, a first account capable of depositing and withdrawing a first currency and a second account capable of depositing and withdrawing a second currency. The first account and the second account can be operated independently. For example, the user account management unit 1131 receives remittance from the subject of the payment method of the second currency to the second account of the host, and separately from this, performs settlement of remittance of the first currency from the first account of the host to the account of the recipient. can do.

The host account management unit 1132 manages an account of a payment service host. Assuming that payment is made in various currencies, and the deposit amount and the withdrawal amount of the account of each currency of the payment service host are in balance, there is no need for separate settlement between the accounts of each currency of the host. According to this, direct foreign currency movement is minimized, thereby simplifying financial affairs and saving currency exchange fees. In addition, instability caused by exchange rate fluctuations is resolved.

The payment management unit 1133 acquires data received to the communication unit 111 through the payment page, for example, payment information input through the payment page, and generates a payment index based on the payment information. The payment index is identification information given to one payment case, and the payment management unit 1133 may manage a payment list including a plurality of payment indices. The payment management unit 1133 transmits the payment method information included in the payment information to the corresponding payment method server 400 to request payment approval, and receives payment approval for this from the payment method server 400 to process payment as completed. can do.

6 is a detailed configuration diagram of the host account management unit 1132 shown in FIG. 2 according to an embodiment.

6, the host account management unit 1132 includes a monitoring unit 11321, a withdrawal account determination unit 11322, and a remittance processing unit 11323, and the withdrawal account determination unit 11322 is a real-time exchange rate collection unit 11322a ).

The host account management unit 1132 may process overseas remittance between a plurality of host accounts operated by the payment service according to an embodiment of the present invention. Foreign remittances may involve currency exchange. The host account management unit 1132 may monitor a plurality of host accounts to balance deposits of the plurality of host accounts.

The monitoring unit 11321 according to an embodiment may monitor a deposit of each of a plurality of accounts of a plurality of hosts, and generate a notification when an account that satisfies a preset condition is found. The monitoring unit 11321 according to another exemplary embodiment may monitor an expected deposit after a predetermined period of each of a plurality of host accounts, and generate a notification when an account in which the expected deposit satisfies a predetermined condition after a predetermined period is found. The condition may be a condition in which the deposit is less than a preset amount. The account that generated the notification is hereinafter referred to as "first account". The host account management unit 1132 may generate a notification and terminate the process, but may automatically perform subsequent processing when the notification occurs. As an example of the subsequent processing, a remittance order between host accounts may be generated.

The withdrawal account determination unit 11322 according to an embodiment determines a second account to be remitted to the first account that generated the notification. For example, the withdrawal account determination unit 11322 determines the account with the largest amount of deposit (or expected deposit) as the second account, and the remittance processing unit 11323 transfers at least a portion of the deposit of the second account to the first account. You can create a remittance order to send money abroad. Overseas remittance includes currency exchange processing. For another example, the withdrawal account determination unit 11322 determines a second account in consideration of real-time exchange rates for each currency, and the remittance processing unit 11323 allows at least a portion of the deposit in the second account to be transferred overseas to the first account. You can create remittance orders. For another example, the withdrawal account determination unit 11322 may determine a specific account preset by the administrator as the third account.

According to an implementation example, the withdrawal account determination unit 11322 may determine an account of a currency having the highest real-time exchange rate compared to a pre-stored reference exchange rate, that is, the highest real-time value, as the second account. The real-time exchange rate collection unit 11322a collects exchange rates for each currency in real time using an api provided by a public institution, etc., and provides it to the withdrawal account determination unit 11322.

According to an implementation example, the withdrawal account determination unit 11322 may determine a second account by referring to all of the reference exchange rate and real-time exchange rate of each currency, and the current real-time deposit of the host account for each currency.

According to an implementation example, the withdrawal account determination unit 11322 is a host account for a currency that satisfies both the first condition in which the real-time deposit is equal to or greater than a preset amount and the second condition in which the ratio of the real-time exchange rate to the reference exchange rate is equal to or greater than a preset value. May preferentially determine as the second account. If there is no host account that satisfies both the first condition and the second condition, the withdrawal account determination unit 11322 determines the host account for the currency having the highest real-time exchange rate among the host accounts that satisfies the first condition. It is decided by account. When there is no host account that satisfies the first condition, the withdrawal account determination unit 11322 determines that there is no account available for withdrawal and outputs an error message.

7 is a flowchart of a payment service providing method according to an embodiment of the present invention.

The flowchart illustrated in FIG. 7 includes steps that are processed in time series by the payment service providing apparatus 110 illustrated in FIGS. 2 to 6 above. Accordingly, even if the contents are omitted below, it can be seen that the contents described above with respect to the components illustrated in FIGS. 2 to 6 are also applied to the flowchart illustrated in FIG. 7.

Referring to FIG. 7, in step S71, the payment page providing unit 112 includes a payment target amount input area for inputting a payment target amount and payment method information for paying a payment target amount input in the payment target amount input area. A payment page including a payment area in which you can enter is generated.

In step S72, the payment page providing unit 112 provides the web address of the payment page generated in step S71 to the recipient terminal 200 in the form of text or an image code corresponding to the web address. The payment page providing unit 112 may provide at least one of a text format of a web address of a payment page and an image code format.

In step S73, the financial management unit 113 receives payment information from the payer terminal 300 including information on a payment target amount and payment method input through the payment page.

In step S74, the financial management unit 113 establishes a payment for the amount subject to payment by using the payment information received in step S73.

Although not shown in FIG. 7, according to an embodiment, the method of providing a payment service further includes receiving a request for generating a first payment page corresponding to a receiver account from the receiver terminal 200 before step S71.

Although not shown in FIG. 7, according to an embodiment, after step S74, the financial management unit 113 receives the payment object amount from the operating entity of the payment method and calculates the payment object amount with respect to the receiver's account.

8 is a block diagram schematically illustrating a payment page obtaining apparatus 210 according to an embodiment of the present invention.

The payment page obtaining apparatus 210 according to an embodiment of the present invention may correspond to at least one or more processors, or may include at least one or more processors. Accordingly, the payment service acquisition device 210 may be driven in a form included in another hardware device such as a microprocessor or a general-purpose computer system. Meanwhile, the payment page acquisition device 210 illustrated in FIG. 8 is mounted on the receiver terminal 200. The payment page acquisition device 210 is mounted on the receiver terminal 200 to communicate with the server 100, and the server 100 and the receiver terminal 200 described above with reference to FIGS. 2 to 7 Contents of data transmission/reception between data may be equally applied to the payment service obtaining device 210 illustrated in FIG. 8.

The payment service obtaining apparatus 210 shown in FIG. 8 shows only the components related to this embodiment in order to prevent blurring of the features of the embodiment. Accordingly, it can be understood by those of ordinary skill in the art related to the present embodiment that other general-purpose components may be further included in addition to the components shown in FIG. 8.

Referring to FIG. 8, the payment page acquisition device 210 includes a communication unit 211, a user interface unit 212, and a display control unit 213.

The communication unit 211 communicates with the server 100 and the payer terminal 300. The communication unit 211 transmits a request for generating a payment page generated by the receiver terminal 200 to the server 100. The payment page generation request includes information about the type of payment page. For example, the type information of the payment page is information indicating whether the payment page that the recipient wants to generate is a first payment page or a second payment page. As the first payment page does not include the payment target amount information, the payer directly inputs the payment target amount, and the second payment page includes the payment target amount information. The payment page generation request may further include sales type information of the payment page type information. The communication unit 211 receives the web address of the payment page from the server 100 in the form of text and/or image code.

The user interface unit 212 detects a user input input to the receiver terminal 200 and processes the user input.

The display control unit 213 controls a screen displayed on the display unit of the receiver terminal 200. The display control unit 213 displays a payment page generation request screen on the display unit of the receiver terminal 200 and displays the web address of the payment page received from the server 100 on the display unit of the receiver terminal 200. The display control unit 213 according to an embodiment displays the web address of the payment page received from the server 100 on the display of the receiver terminal 200 in a pop-up manner. The display control unit 213 may display a web address of the payment page and an icon for executing an application that can share the web address of the payment page together in a pop-up window.

Includes information on the amount subject to payment. The communication unit 211 receives the web address of the payment page from the server 100 in response to transmission of the payment page generation request. In detail, the communication unit 211 receives a web address of a payment page through which a payment target amount can be paid from the server 100 in the form of text or an image code corresponding to the web address.

9A and 9B are flowcharts of a method of obtaining a payment page according to an embodiment of the present invention. The flowcharts illustrated in FIGS. 9A and 9B are configured with steps that are processed in time series by the payment page obtaining apparatus 210 illustrated in FIG. 8. Therefore, even if omitted below, the contents described above with respect to the components illustrated in FIG. 8 may also be applied to the flowcharts illustrated in FIGS. 9A and 9B. In addition, the payment page acquisition device 210 of FIG. 9 is mounted on the receiver terminal 200 to communicate with the server 100, and the server 100 and the receiver described above with reference to FIGS. 2 to 7 Contents of data transmission/reception between the terminals 200 may be applied to the flowcharts illustrated in FIGS. 9A and 9B.

In detail, FIG. 9A is a flowchart of a method of obtaining a first payment page according to an embodiment of the present invention.

Referring to FIG. 9A, in step S91, the communication unit 211 transmits a request for generating a payment page that does not include information on a payment target amount to the server 100. In this embodiment, the payment page creation request is a payment page that does not include information on the amount subject to payment, that is, a first payment page creation request that requests the creation of a first payment page, and is a request to create a payment page corresponding to the recipient's account. .

In step S92, the communication unit 211 receives the web address of the payment page from the server 100 in at least one of a text format and an image code corresponding to the web address. In this embodiment, the payment page is a first payment page for directly inputting a payment target amount in the payment page and paying the input payment target amount. The first payment page includes a payment target amount input area in which a payment target amount can be input, and a payment area through which a payment target amount input in the payment target amount input area can be settled.

In step S93, the display control unit 213 displays the web address of the first payment page received in step S92 on the display of the receiver terminal 200 in a pop-up manner. The display control unit 213 may also display an icon for executing an application capable of sharing a web address of a payment page.

Next, FIG. 9B is a flowchart of a method of obtaining a second payment page according to an embodiment of the present invention.

Referring to FIG. 9B, in step S91', the communication unit 211 transmits a request for generating a payment page including information on a payment target amount to the server 100. In this embodiment, the payment page generation request is a payment page including information on a payment target amount, that is, a second payment page generation request that requests the generation of a second payment page. The payment page generation request transmitted in step S91' includes information on a payment target amount.

In step S92', the communication unit 211 receives the web address of the payment page from the server 100 in the form of text and/or an image code corresponding to the web address. In this embodiment, the payment page is a second payment page through which a fixed payment target amount can be paid. The second payment page displays a payment target amount according to the payment target amount information included in the payment page creation request transmitted in step S91', and provides a function of paying the displayed payment target amount.

In step S93', the display control unit 213 displays the web address of the first payment page received in step S92' on the display of the receiver terminal 200 in a pop-up manner.

On the other hand, the payment page acquisition method according to an embodiment of the present invention shown in FIGS. 9A and 9B can be written as a program that can be executed on a computer, and is a general purpose of operating the program using a computer-readable recording medium. It can be implemented on a digital computer. The computer-readable recording medium includes a storage medium such as a magnetic storage medium (for example, a ROM, a floppy disk, a hard disk, etc.) and an optical reading medium (for example, a CD-ROM, a DVD, etc.).

The server 100 according to an embodiment of the present invention may distribute a program capable of executing the method for obtaining a payment service according to an embodiment of the present invention to the receiver terminal 200.

10 is an example of a payment page request screen displayed on the receiver terminal 200. In detail, FIG. 10 is an example of a screen for requesting provision of a first payment page.

The screen 1000 of FIG. 10 is an example of a case where a receiver logs in to a payment service according to an embodiment of the present invention and then accesses a payment page provision request page. Referring to FIG. 10, a screen 1000 displays receiver account information 1001, receiver settlement information 1002, and buttons 1003 and 1004.

According to an embodiment of the present invention, the server 100 stores the web address of the first payment page corresponding to the receiver account in the server 100, and a request for providing the first payment page from the receiver terminal 200 Upon receipt, the web address of the first payment page may be transmitted to the receiver terminal 200. In this embodiment, when the button 1003 is selected, the receiver terminal 200 transmits a request for providing the first payment page to the server 100, and sends the web address of the first payment page from the server 100 in text form. It can be received and displayed. In this embodiment, when the button 1004 is selected, the receiver terminal 200 transmits a request for providing the first payment page to the server 100, and sends the web address of the first payment page from the server 100 to the image code ( For example, a QR code) can be received and displayed.

According to another embodiment of the present invention, the server 100 may transmit the web address of the first payment page corresponding to the recipient account to the recipient terminal 200 in advance, and the recipient terminal 200 The web address of the page can be saved in the form of text and image codes. For example, the web address of the first payment page is the number of times when a recipient logs in to his or her account through a program (eg, an application for a smartphone) provided according to a payment service according to an embodiment of the present invention. It may be downloaded to the goldsmith terminal 200 and stored as program internal data. In this embodiment, when the button 1003 is selected, the receiver terminal 200 may display the web address of the first payment page stored in the receiver terminal 200 in text form. In this embodiment, when the button 1004 is selected, the recipient terminal 200 may display the web address of the first payment page stored in the recipient terminal 200 in the form of an image code (eg, a QR code). have.

By selecting the buttons 1003 and 1004 shown in FIG. 10, the receiver terminal 200 can obtain the web address of the first payment page assigned to the receiver's own account. The output type of the payment page web address included in the payment page provision request is determined according to which buttons 1003 and 1004 the receiver selects. When the receiver selects the button 1003, the web address of the payment page is provided in the form of text, and if the receiver selects the button 1004, the web address of the payment page is provided in the form of an image code. The web address in the form of a text or image code obtained accordingly may be displayed on the recipient terminal 200 as a pop-up or may be automatically stored in the clipboard of the recipient terminal 200.

11 is another example of a payment page request screen displayed on the receiver terminal 200. In detail, FIG. 11 is an example of a screen for requesting generation of a second payment page.

The screen 1100 of FIG. 11 is an example of a case where the receiver logs in to the payment service according to an embodiment of the present invention and then accesses the payment page creation request page. Referring to FIG. 11, a box 1101 for entering a product name and a box 1102 for entering a payment amount are displayed on a screen 1100, and a button 1104 for creating a link to a payment page and a payment page. A button 1105 for generating a QR code corresponding to the link is displayed.

In the example shown in FIG. 11, it can be seen that the receiver inputs the product name "postcard" in the box 1101 on the screen 1100 and the payment amount "10,000 won" in the box 1102. Meanwhile, the receiver may select an arrow 1103 in the box 1102 to select a currency type of the payment amount. When the receiver accesses the payment page generation request page displayed on the screen 1100, the currency designated as default may be determined by the receiver's account information or the receiver's preset settings. However, according to an example, the display of the arrow 1103 shown in FIG. 11 may be omitted, and the currency may be designated and displayed as a default.

After filling the boxes 1101 and 1102 as shown in FIG. 11, the receiver transmits a second payment page generation request to the server 100 by selecting the button 1103 or the button 1104. The second payment page generation request includes information input to the boxes 1101 and 1102. When the button 1103 is selected, a second payment page is generated, and a web address of the generated second payment page is provided in text form. When the button 1104 is selected, a second payment page is generated, and an image code (eg, a QR code) corresponding to the web address of the generated second payment page is provided. The web address in the form of a text or image code may be displayed as a pop-up or may be automatically stored in the clipboard of the recipient terminal 200.

The payment page link output type included in the payment page generation request is determined according to which buttons 1104 and 1105 the receiver selects. When the receiver selects the button 53, the server 100 generates a payment page and provides a link to the payment page in text form, and when the receiver selects the button 54, the server 100 creates a payment page and makes payment. Provides an image code corresponding to the web address of the page. The web address in the form of a text or image code obtained accordingly may be displayed on the recipient terminal 200 as a pop-up or may be automatically stored in the clipboard of the recipient terminal 200.

12 is another example of a payment page request screen displayed on the receiver terminal 200. In detail, FIG. 12 is an example of a screen for requesting provision of a first payment page or requesting creation of a second payment page.

The screen 1200 of FIG. 12 is an example of a case where a receiver logs in to a payment service according to an embodiment of the present invention and then accesses the payment page request page. On the screen 1200 illustrated in FIG. 12, the receiver may request to provide a first payment page or to generate a second payment page. Referring to FIG. 12, a screen 1200 includes receiver account information 1201, receiver settlement information 1202, and buttons 1203 and 1204 for requesting provision of a first payment page. The portion displayed at the bottom of the screen 1200 is a portion for requesting generation of a second payment page. The screen 1200 includes a box 1204 for entering a product name and a payment target amount, buttons 1205 and 1206 for selecting a sales type, and buttons 1207 and 1208 for requesting creation of a second payment page. Include.

Referring to FIG. 12, the receiver selects a button 1203 on the screen 1200 to obtain the web address of the first payment page in text form, or selects the button 1204 to image the web address of the first payment page. It can be obtained in code form. In relation to the receiver selecting the buttons 1203 and 1204 to obtain the web address of the first payment page, the items described with reference to the buttons 1003 and 1004 of FIG. 10 may be equally applied.

The receiver can obtain the web address of the second payment page in text form by selecting the button 1207 on the screen 1200, or obtain the web address of the second payment page in the form of image code by selecting the button 1208. have. In relation to the receiver selecting the buttons 1207 and 1208 to obtain the web address of the second payment page, the items described with reference to the buttons 1104 and 1105 of FIG. 11 may be equally applied.

Referring to FIG. 12, a screen 1200 includes buttons 1205 and 1206 for selecting a sales type. The receiver selects the delivery required button 1205 or the direct transaction button 1206 displayed on the screen 1200 to generate sales type information. The sale type information is information indicating whether a transaction corresponding to a payment target amount is a transaction requiring delivery of a product or a transaction requiring delivery of a product. Before requesting creation of a second payment page by pressing buttons 1207 and 1208 on the page displayed on the screen 1200, the receiver may select one of the buttons 1205 and 1206 to designate a sales type. Only one of the icons 1205 and 1206 may be selected in a toggle manner. For example, if the recipient selects the icon 1205 and then selects the icon 1206, the selection for the icon 1205 is released.

Referring to FIG. 12, a receiver may generate a payment page provision request or a payment page generation request by selecting one of a first payment page or a second payment page on one page.

13 is a screen 1300 in which the web address of the payment page is displayed in text form on the receiver terminal 200 when any one of the buttons 1003, 1104, 1203, and 1207 shown in FIGS. 10 to 12 is selected. Yes. Referring to FIG. 13, a web address of a payment page is displayed in text in a pop-up 60, and an icon 61 for executing an application including a function of sharing a link of a payment page is displayed under the web address. . The icons 61 may be linked to applications including functions such as clipboard copying, messenger transmission, and message transmission, respectively.

For example, if the first icon is a clipboard copy, when the receiver clicks the first icon, a link to the payment page is copied to the clipboard of the receiver terminal. For example, when the second icon is a messenger transmission, the receiver selects the second icon and moves to a messenger application, and then transmits a link to the payment page to the payer through the application. For example, if the third icon is a message transmission, the receiver selects the third icon and moves to the message application, enters the payer's identification information (eg, mobile phone number) through the application, and then opens a link to the payment page. Send to the payer. Examples of the function of the icon are not limited to those described above.

14 is an example of a screen 1400 on which a second payment page is displayed according to an example.

In detail, when one of the buttons 1104, 1105, 1207, and 1208 shown in FIGS. 11 and 12 is selected, the payer accesses the second payment page generated by the server 100, and the payer terminal 300 14 shows an example of a screen 1400 in which a second payment page is displayed on ). Referring to FIG. 14, the payment page displays a product name ("postcard" in the example of FIG. 14), a payment amount (10,000 won in the example of FIG. 14), and a payment method 1401. In the screen 1400, a payment page provides an option for the payer to select a currency to pay. The payer can open the currency list to the right of the payment amount and select a different currency. When the payer selects the currency, the communication unit 111 of FIG. 2 receives the currency information selected by the payer, and the payment page generation unit 112 of FIG. 2 converts payment amount information based on the real-time exchange rate for the corresponding currency. The payment page (or a layer of the payment amount item included in the payment page) may be updated to display in the payment amount item. In FIG. 14, an example in which the payer selects KRW and the amount subject to payment is displayed accordingly is shown. Meanwhile, according to another embodiment, the payment page displayed on the screen 1400 may not provide an option for the payer to select a currency to be paid, and may receive payment information only in a default currency.

Referring to FIG. 14, a payment page provides a plurality of payment means 1401. In FIG. 14, an example is shown in which an information input area through which the payer can input credit card information is displayed at the bottom of the payment method 1401 by selecting a “direct payment” item. In addition, the payer may select "Paypal" to perform payment using a PayPal account, or select "Alipay" to perform payment using an Alipay account. Meanwhile, PayPal and Alipay are only examples of fintech services that allow users to conveniently perform online payments using a previously registered account, and embodiments of the present invention are not limited to this example. When the payer selects the "Paypal" item, an area for entering information to log in to a PayPal account will be displayed at the bottom.

The payment method 1401 and the information input area for each payment method displayed below the payment method 1401 may be linked to an api of each payment method. The financial management unit 113 of FIG. 2 may transmit payment information input by the payer to the information input area to the payment method server 400 through an api of the corresponding payment method, and receive approval from the payment institution. However, the present invention is not limited thereto, and the process of inputting payment information into the information input area and obtaining approval from the corresponding payment institution is a direct relationship between the payment terminal 300 and the payment method server 400 without going through the service providing server 100. It could also be handled by communication. In this case, the payer will have to provide the authorization information to the service providing server 100.

Meanwhile, the payment page illustrated in FIG. 14 is an example of a second type of second payment page that does not include an area for receiving an input of a delivery address. To this end, the recipient may have selected the direct transaction button 1206 shown in FIG. 12.

15 is an example of a screen 1500 on which a second payment page is displayed according to another example.

In detail, FIG. 15 is an example of a screen 1500 on which a second payment page of the first type including an area for receiving an input of a delivery address is displayed. To this end, the receiver may have selected the delivery required button 1205 shown in FIG. 12. Referring to FIG. 15, the second payment page further includes a payer's personal information input area 1501. The payer may input personal information including an address to which the goods are to be delivered through the personal information input area 1501. The payer's personal information input through the personal information input area 1501 may be transmitted to the receiver terminal 200 through the server 100. The receiver can deliver the goods by referring to the payer's personal information.

16 is an example of a screen 1600 on which a first payment page is displayed, according to an example.

In detail, the first payment page provided by the server 100 or read from the memory of the receiver terminal 200 when any one of the buttons 1003, 1004, 1203, and 1204 shown in FIGS. 10 and 12 is selected An example of a screen 1600 on which the payer accesses the first payment page corresponding to the web address of and displays the first payment page on the payer terminal 300 is illustrated in FIG. 16. Referring to FIG. 16, a first payment page provides a box 1601 through which a payer can directly input a payment amount, and a box 1602 through which a payer can directly input payer information.

At the bottom of the box 1602, an area 1603 in which payment method information can be input by selecting any one of a plurality of payment methods is displayed. In FIG. 16, an example is shown in which an information input area through which a payer can input credit card information is displayed at the bottom of the item by selecting a “direct payment” item. In addition, the payer may select "Paypal" to perform payment using a PayPal account, or select "Alipay" to perform payment using an Alipay account. Meanwhile, PayPal and Alipay are only examples of fintech services that allow users to conveniently perform online payments using a previously registered account, and embodiments of the present invention are not limited to this example. When the payer selects the "Paypal" item, an area for entering information to log in to a PayPal account will be displayed at the bottom.

The payment method and the information input area for each payment method displayed below the payment method may be linked to an api of each payment method. The financial management unit 113 of FIG. 2 may transmit payment information input by the payer to the information input area to the payment method server 400 through an api of the corresponding payment method, and receive approval from the payment institution. However, the present invention is not limited thereto, and the process of inputting payment information into the information input area and obtaining approval from the corresponding payment institution is a direct relationship between the payment terminal 300 and the payment method server 400 without going through the service providing server 100. It could also be handled by communication. In this case, the payer will have to provide the authorization information to the service providing server 100.

17 is an example of a printed material in which an image code corresponding to a web address of a first payment page is output according to an embodiment of the present invention.

Referring to FIG. 17, an embodiment of the present invention provides a business card 12 in which an image code C corresponding to a web address of a first payment page and personal information of a user are output. As described above, the first payment page is a page that provides a service through which a payer can directly input an amount and payment method information to make a payment. A plurality of payments for paying different payment target amounts may be processed through the first payment page. That is, the first payment page may be used repeatedly to generate a plurality of payments. The first payment page may be a page corresponding to the account information of the recipient of the settlement, that is, the owner of the business card in this embodiment. A first payment page may be generated in advance in response to a receiver's account, and an image code corresponding to a web address of the pre-generated first payment page may be generated. In addition, a business card 12 on which the image code C is printed may be provided.

Businesses frequently require remittance or payment. At this time, it is cumbersome for the receiver to directly inform the account information to be remitted each time, and it is cumbersome for the sender to directly input the account information to remit. There are also users who want to use payment methods other than cash. Using the business card according to an embodiment of the present invention, an image code that allows direct access to the first payment page where you can pay the desired amount using various payment methods, along with personal information such as the user's name and contact information. Is presented. Therefore, as the convenience of remittance and payment is greatly improved, the convenience of business is increased.

For example, when a user who does not have a card payment POS machine sells a product on the street, the user provides the buyer with a business card with an image code printed on the web address of the first payment page corresponding to his/her account. By doing so, buyers can access the first payment page through the image code and pay the product amount using various payment methods.

In addition, the tutor provides a business card with an image code printed on the web address of the first payment page corresponding to his/her account to the student, so that the student accesses the first payment page through the image code and uses various payment methods. You can pay the tutoring fee.

The printed material is not limited to the business card, and may include any type of printed material capable of printing an image code. For example, it can be applied to various printed matters such as promotional materials, signs, signboards, billboards, and banners.

18 is another example of a printed material on which an image code is output. Referring to FIG. 18, it can be seen that an image code accessible to a first payment page corresponding to an account of the present payment service corresponding to a "deal store" is printed on a printed matter promoting a "deal store". Also, on the first payment page, it can be seen that the name is printed together as information of the recipient of the amount paid.

According to the present embodiment, the printed matter illustrated in FIG. 18 may be provided in a store that sells products. In addition, by providing the printed matter to the product buyer, the buyer can access the first payment page corresponding to the store account through the image code, directly input the amount of the product, enter the payment method information, and pay for the product to the store. You can do it.

So far, the present invention has been looked at around its preferred embodiments. The present invention has been described with reference to the embodiments shown in the drawings, but these are only exemplary, and those of ordinary skill in the art to which the present invention pertains, the present invention has been modified within the scope not departing from the essential characteristics of the present invention It may be implemented in a form, it will be understood that other equivalent embodiments are possible. Therefore, the disclosed embodiments should be considered from an illustrative point of view rather than a limiting point of view. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope equivalent thereto should be construed as being included in the present invention.

The present invention can be represented by functional block configurations and various processing steps. These functional blocks may be implemented with various numbers of hardware or/and software configurations that perform specific functions. For example, the present invention is an integrated circuit configuration such as memory, processing, logic, a look-up table, etc., capable of executing various functions by controlling one or more microprocessors or by other control devices. Can be hired. Similar to how the components of the present invention can be implemented with software programming or software elements, the present invention includes various algorithms implemented with a combination of data structures, processes, routines or other programming constructs, including C, C++ , Java, assembler, or the like may be implemented in a programming or scripting language. Functional aspects can be implemented with an algorithm running on one or more processors. In addition, the present invention may employ the prior art for electronic environment setting, signal processing, and/or data processing. Terms such as "mechanism", "element", "means", and "configuration" may be used widely, and are not limited to mechanical and physical configurations. The term may include a meaning of a series of routines of software in connection with a processor or the like.

In the above, the embodiments of the present invention have been mainly described, but various changes or modifications may be made at the level of those of ordinary skill in the art. Accordingly, it will be understood that such changes and modifications are included within the scope of the present invention as long as they do not depart from the scope of the present invention.

100: server
200: receiver terminal
300: payer terminal
400: payment method server
500: network
110: payment service providing device
210: payment page acquisition device

Claims (15)

Receiving a request for generating a payment page corresponding to the receiver account from the receiver terminal;
Generating, by a payment service providing device, a payment page in response to the request for generating the payment page, and storing the generated payment page in a memory;
Extracting and accessing the web address from photographing data photographing an image code corresponding to the web address or text form of the web address of the payment page generated and stored in advance, at a payer terminal;
Providing, by the payment service providing device, the payment page corresponding to the web address to the payer terminal;
Receiving, by the payment service providing device, payment information input from the payer terminal through the payment page;
Transmitting, by the payment service providing device, the payment information to a payment means server; And
Including, by the payment service providing device, receiving approval for the payment information from the payment means server,
The payment page generation request includes a request for creating a first payment page that does not include information on the amount subject to payment, or a request for creating a second payment page including information on the amount subject to payment,
When the request for generating the payment page is the request for generating the first payment page, a payment area in which information on a payment method for paying a payment target amount can be input, and an input area for a payment target amount in which information about a payment target amount can be input Generating a first payment page comprising a,
When the payment page generation request is the second payment page generation request, payment for inputting payment method information for paying a payment target amount corresponding to the payment target amount information included in the second payment page generation request Create a second payment page including an area,
The first and second payment pages provide api for each of a plurality of payment methods in the payment area,
The api of each payment method is provided by the server or website of each payment method,
Each of the payment means is used to pay for at least one currency, and includes a first payment means and a second payment means,
The first payment means pays in a first currency, and the second payment means pays in a second currency different from the first currency.
How to provide payment services.
The method of claim 1,
The payment method information, a payment service providing method including a card number, a card expiration date or a CVC code of the payer.
delete The method of claim 1,
The payment service providing method further comprising the step of receiving a confirmation of the payment target amount input to the payment page from the receiver terminal.
The method of claim 1,
The first payment page,
A payment service providing method for displaying the payment target amount input area and the payment area on one page so that a payer can input payment information in the payment page without moving a page.
delete delete The method of claim 1,
The payment page generation request further includes sales type information,
The payment page providing unit determines a type of the payment page to one of a plurality of types based on the sale type information.
The method of claim 8,
The sale type information indicates whether a transaction corresponding to the payment target amount requires delivery of a product,
The type of the payment page includes a first type including an area for receiving a delivery address and a second type not including an area for receiving a delivery address.
The method of claim 8,
The sales type information indicates whether or not a transaction corresponding to the payment target amount occurs regularly,
The type of the payment page includes a third type including an area for setting periodic payment and a fourth type not including an area for setting periodic payment.
delete delete delete delete delete

Images