KR20170049481A - Transaction processing for payment of simplified and driven structure - Google Patents

Abstract

Disclosed is a method for processing payment transactions having a simplified and leading structure. The method of payment service comprises the following steps of: providing a uniform resource locator (URL) corresponding to payment information linked to the service account of a user on a service screen when a user terminal enters a service screen which is related to a specific product; and performing the payment processing directly by using the payment information without inputting additional information upon receiving a selection of the URL from the terminal of the user. In this case, the performing the payment processing may include the following steps of: performing an independent authentication procedure which is independent of the financial institution which is related to the payment information, and checking a payment risk level of the user; and performing an authentication process for the user by applying an authentication method corresponding to the payment risk level. The disclosure provides a one-click payment model which simplifies the payment procedure by using a uniform resource locator (URL) method as much as possible.

Description

[0001] TRANSACTION PROCESSING FOR PAYMENT OF SIMPLIFIED AND DRIVEN STRUCTURE [0002]

Embodiments of the invention relate to transaction processing techniques.

As wired / wireless network infrastructure is established and Internet technology is developed, e-commerce related market is growing, which enables commerce activities in online space.

Electronic commerce is a collective term for trading goods and services using electronic media such as the Internet. Transaction activities include general commodity trading as well as transactions that provide advertising, marketing, and services. Typical examples of e-commerce include internet shopping or cyber shopping, such as building an internet homepage or a virtual shop to sell goods or provide services.

The transaction price is generally settled by credit card, digital currency or electronic payment means. In order to settle such a payment, a payment system for a credit card or a payment system using a digital cash is required such as a Secure Transaction Technology (STT) and a Secure Electronic Payment Protocol (SEPP). In addition, an electronic authentication system using SSL (Secure Socket Layer) or S-HTTP (Secure-HTTP) is required for transaction security.

As an example of electronic commerce, Korean Patent Laid-Open No. 10-1997-0049810 (published on July 29, 1997) entitled " Online shopping system and payment method " And an online shopping system that enables the ordering and settlement of the order.

It provides a one-click settlement model that simplifies the settlement procedure to the simplest by using a uniform resource locator (URL) method.

A settlement model capable of providing a direct settlement notification according to a purchase pattern according to a transaction history of a user or a reservation setting for a regular purchase.

In order to secure transaction of settlement of accounts, a settlement model which can directly execute the authentication led by a financial institution (for example, credit card company, bank company, etc.) in the settlement system is provided.

It provides a payment model that can differentiate the authentication procedure from one-click to non-payment according to the risk level of the user or transaction situation.

In a payment service method implemented by a computer, when a user terminal enters a service screen related to a specific product, a URL (uniform resource locator) corresponding to the payment information linked to the service account of the user is provided on the service screen ; And directly receiving a selection of the URL from the terminal of the user, and performing a payment process directly using the payment information without inputting any additional information. The step of performing the settlement processing may include the steps of: confirming the payment risk level of the user by performing an independent authentication procedure independent of the financial company associated with the settlement information; And performing an authentication process for the user by applying an authentication method corresponding to the payment risk level.

At least one program loaded memory; And at least one processor coupled to the service account of the user on the service screen when the user's terminal enters a service screen associated with a particular product under control of the program, Providing a uniform resource locator (URL) corresponding to the settlement information; And a payment system that performs a payment process directly using the payment information without inputting additional information upon receiving a selection of the URL from the terminal of the user. In this case, the step of performing the settlement processing may include performing an independent authentication procedure that is independent of the financial institution related to the settlement information, and checking the payment risk level of the user. And performing an authentication process for the user by applying an authentication method corresponding to the payment risk level.

According to the embodiment of the present invention, the order step can be simplified through the simple inflow path by omitting the unnecessary procedure and providing the one-click settlement model that can directly settle the settlement through the URL method.

According to the embodiment of the present invention, it is possible to maximize the convenience of a user who has a regular purchasing behavior by providing a notice of direct settlement according to a purchase pattern or a reservation setting according to a user's transaction history.

According to the embodiment of the present invention, it is possible to apply a leading and free authentication policy by performing the authentication in charge of the financial institution directly in the payment system for the secure transaction of the payment.

According to the embodiment of the present invention, the authentication process is differentiated from one-click to non-settlement according to the risk level of the user or the transaction situation, so that the authentication policy is more flexible and rational than the conventional uniformity can do.

1 is a diagram for explaining an example of a settlement service environment in an embodiment of the present invention.
2 is a block diagram for explaining an internal configuration of a settlement system according to an embodiment of the present invention.
3 is a flowchart showing a method of registering an account for settlement in an embodiment of the present invention.
FIGS. 4 to 8 illustrate exemplary user interface screens associated with an account registration procedure, according to an embodiment of the present invention.
9 is a flowchart illustrating a method of providing a payment path in an embodiment of the present invention.
10 to 14 illustrate a user interface screen related to a payment path providing procedure according to an exemplary embodiment of the present invention.
FIG. 14 is a flowchart showing a settlement processing method including an authentication procedure for each grade, according to an embodiment of the present invention.
15 and 16 are flowcharts showing a remittance processing method in an embodiment of the present invention.
17 to 21 illustrate a user interface screen related to a remittance processing procedure in an embodiment of the present invention.
22 is a flowchart showing a remittance receiving method in an embodiment of the present invention.
23 illustrates an exemplary user interface screen associated with a remittance receiving procedure in an embodiment of the present invention.
FIG. 24 is a flowchart illustrating a method of notifying a periodic payment in an embodiment of the present invention. FIG.
25 illustrates an example of a user interface screen related to a periodic payment notification procedure according to an exemplary embodiment of the present invention.
26 is a block diagram for explaining an example of the internal configuration of a computer system according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The present invention relates to a settlement model for processing a payment in an online shopping environment via the Internet. More specifically, the settlement procedure can be simplified using a URL scheme, And a system and a recording medium that can apply the authentication procedure differentially according to the level of risk of the transaction situation.

1 is a diagram for explaining an example of a settlement service environment in an embodiment of the present invention. Figure 1 shows a user terminal 101, 102 and a payment system 100. In FIG. 1, the arrow indicates that data can be transmitted and received between the components using the wired / wireless network 10.

User terminals 101 and 102 may execute one or more processes configured to perform one or more of the features described herein. The user terminals 101 and 102 may refer to all terminal devices capable of connecting to a web / mobile site associated with the payment system 100 or installing and executing a service-dedicated application. At this time, the user terminals 101 and 102 can perform service overall operation such as service screen configuration, data input, data transmission / reception, and data storage under the control of a web / mobile site or a dedicated application.

Examples of user terminals 101 and 102 include a personal computer (PC), a laptop computer, a laptop computer, a smart phone, a tablet, a wearable computer, But is not limited thereto.

User terminals 101 and 102 may be directly or indirectly coupled to a network 10 (e.g., the Internet or a local area network, etc.). For example, the personal computer and the notebook computer may be directly coupled to the network 10 via a wired network connection. The laptop computer may be wirelessly coupled to the network 10 via a wireless communication channel established between the laptop computer and a wireless access point (i.e., WAP). The smartphone may be wirelessly coupled to the network 10 via an established wireless communication channel between the smartphone and the cellular network / bridge. At this time, the network 10 can communicate with one or more secondary networks (not shown), and examples of secondary networks include a local area network, a wide area network, or an intranet < / RTI > intranet).

The user terminals 101 and 102 may interface with the settlement system 100 through the network 10 described above.

The payment system 100 serves as a service platform for providing a settlement service for paying for online shopping to a client. The billing system 100 may execute one or more processes configured to perform one or more of the features described herein.

The billing system 100 corresponds to a server computer, and examples of the server computer may include a server computing device, a personal computer, a server computer, a series of server computers, a minicomputer, and / or a mainframe computer But is not limited thereto. The server computer may be a distributed system, and the operations of the server computer may be executed concurrently and / or sequentially on one or more processors.

The payment system 100 may provide a payment settlement environment for online shopping using a user identifier associated with a payment service. In this specification, the user identifier may refer to all the information that identifies the user registered in the payment service, and in particular to connect the payment information (for example, account information, card information, etc.) registered by the user, And may include, but is not limited to, account (ID), telephone number, email, and the like. At this time, the service account includes a user registered in the settlement service, a user registered in another service (for example, portal service, integrated search service, shopping service, map service, community service, social network service, ID, < / RTI > and the like.

As an example of the payment means, when utilizing automatic transfer via remittance, the user identifier is applied as information that can specify the sender and recipient in place of the account number for real-time remittance between the seller and the purchaser. For example, the settlement system 100 may provide a remittance process for an individual, such as home banking, when transferring money between individuals. As another example, the settlement system 100 can also transfer the amount of remittance from the parent to the account of the recipient first after transferring the remittance amount to the parent account of the remittance service. In other words, the settlement system 100 can perform remittance processing between individuals through firm banking using a parent account.

In particular, the billing system 100 can directly provide a simplified settlement procedure using a URL scheme based on a user identifier, and can directly perform authentication, which has been led by a financial company, Procedures can be applied differently.

The payment system 100 may interface with a financial service server (e.g., a server company of a financial institution such as a credit card company or a bank company) 103 through the network 10 to perform one or more processes required in the settlement process. At this time, the settlement system 100 may be constituted by one system combined with the financial company server 103, or may be constituted by a separate system from the financial company server 103 and may provide a settlement service in cooperation with the financial company server 103 However, the present invention is not limited thereto, and in some cases, the form or the manner of constructing the settlement system 100 may be changed in any way. When the billing system 100 is configured as a separate system from the financial company server 103, a configuration of the billing system 100 may be configured to reside on the side of the financial company server 103, depending on the system implementation or service type. The settlement system 100 may be constructed as a one-to-one system for each bank, or may be separately configured as an integrated system for a service for a plurality of bank companies.

The billing system 100 may be implemented as a system with at least one service platform among services requiring a payment function such as a portal service, an integrated search service, a shopping service, a map service, a community service, and a social network service, System and can provide payment service through linkage between services.

The billing system 100 can provide a web-based online shopping environment by itself, and can be implemented in a service platform that provides a payment service in a client-server environment. The billing system 100 may be implemented in a form of being included in a platform of a shopping system that provides a shopping environment based on the Internet. However, the billing system 100 is not limited thereto and may be constructed as a separate system from the shopping system, It is also possible to implement payment services through the Internet. As another example of an implementation of payment system 100, billing system 100 may be implemented in the form of a client device application, such as a mobile-specific application installed on user terminals 101 and / or 102, But is not limited thereto.

2 is a block diagram for explaining an internal configuration of a settlement system according to an embodiment of the present invention.

2, the billing system 200 according to the present embodiment may include a processor 210, a bus 220, a network interface 230, and a memory 240 and a database 250 . The memory 240 may include an operating system 241 and a payment processing routine 242. The processor 210 may include a registering unit 211, a providing unit 212, a settlement unit 213, and a monitor unit 214. In other embodiments, the billing system 200 may include more components than the components of FIG.

The memory 240 may be a computer-readable recording medium and may include a permanent mass storage device such as a random access memory (RAM), a read only memory (ROM), and a disk drive. Also, the memory 240 may store program codes for the operating system 241 and the payment processing routine 242. [ These software components may be loaded from a computer readable recording medium separate from the memory 240 using a drive mechanism (not shown). Such a computer-readable recording medium may include a computer-readable recording medium (not shown) such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, or a memory card. In other embodiments, the software components may be loaded into the memory 240 via the network interface 230 rather than from a computer readable recording medium.

The bus 220 may enable communication and data transfer between components of the payment system 200. The bus 220 may be configured using a high-speed serial bus, a parallel bus, a Storage Area Network (SAN), and / or other suitable communication technology.

Network interface 230 may be a computer hardware component for connecting billing system 200 to a computer network. The network interface 230 may connect the billing system 200 to the computer network via a wireless or wired connection.

The database 250 stores and maintains all information necessary for providing a settlement service. At this time, the database 250 stores basic personal information (e.g., name, sex, nationality, date of birth, etc.) for each user, a user identifier (service account, mobile phone number, (E.g., passwords, voices, fingerprints, etc.) necessary for payment authentication, payment information (e.g., account information, card information, electronic payment means And so on. In FIG. 2, the payment system 200 includes the database 250, but it is also possible to exist as an external database built on a separate system.

The processor 210 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations of the payment system 200. The instructions may be provided by the memory 240 or the network interface 230 and to the processor 210 via the bus 220. The processor 210 may be configured to execute program codes for the registering unit 211, the providing unit 212, the settlement unit 213, and the monitor unit 214. [ Such program code may be stored in a recording device such as memory 240. [

The registering unit 211, the providing unit 212, the settlement unit 213, and the monitor unit 214 may be configured to perform the steps of the remittance method described below.

Hereinafter, the automatic payment via remittance is described as an example of the payment means. However, the present invention is not limited to this, and all payment means capable of real-time settlement such as card settlement, mobile phone settlement, electronic money, May be applied.

3 is a flowchart showing a method of registering an account for settlement in an embodiment of the present invention. The account registration method according to the present invention can be performed by the registration unit 211 described with reference to FIG.

In step 301, the registration unit 211 may perform user authentication on a user requesting a service subscription. At this time, the registration unit 211 can perform the authentication process through one or more of the known authentication methods such as the mobile phone authentication method, the real name authentication method, the authentication method using the public certificate, and the ARS-based authentication method.

4 illustrates an example of a user authentication screen 400 displayed on the user terminal as a user interface related to a user authentication process of the registration unit 211. As shown in FIG. For example, the user authentication screen 400 shows a user authentication screen according to a mobile phone authentication method, and may include a user interface for requesting input of personal information for mobile phone authentication. The registration unit 211 authenticates the mobile phone based on personal information (for example, name, sex, nationality, date of birth, mobile phone number, communication company, etc.) input through the identity authentication screen 400, The verification procedure can be performed.

In steps 302 and 303, the registration unit 211 determines whether the user authentication is successful according to the result of the user authentication using the mobile phone authentication method or the like, and may restrict the registration of the payment service if the user authentication fails.

In steps 302 and 304, the registration unit 211 may perform a password registration procedure for registering the password of the user when the user authentication through the authentication process is successful. At this time, the password can be used for authentication for secure payment when making a payment using a registered account to be described below.

5 shows an example of a password input screen 500 displayed on the user terminal as a user interface related to the password registration procedure of the registration unit 211. [ For example, the password input screen 500 may include a user interface for requesting input of a password used for authentication at the time of transfer or payment. The password input screen 500 may include a keypad area and a character input area to which a character selected through the keypad (e.g., a number) is input. At this time, the keypad area is automatically accessed when the password input screen 500 is accessed And a security keypad for converting the actual input value into a random number when the keyboard layout is changed or the keyboard is pressed each time.

The registration unit 211 can register the completed character through the password input screen 500 with the password for authentication of the user and repeatedly requests re-input of the password at least once more, A method of registering a corresponding password when a character is input can be applied.

Then, the registration unit 211 may perform a procedure for accepting a contract for use of the payment service before or after performing the password registration procedure. At this time, the Terms and Conditions may include all the terms necessary for the use of the payment service, such as service member's terms and conditions, electronic financial transaction terms, personal information collection and use agreement, and payment information third party provision agreement.

In steps 305, 306, 307, and 308, the registration unit 211 may perform an account registration procedure for registering an account to be used as a payment means. For example, the registering unit 211 may register only one account in the form of one account per person, and may delete the existing registered account and register the new account in order to change the account. As another example, it is also possible for the registering unit 211 to register a plurality of accounts in the form of one N account without limiting the number of registered accounts.

For example, the registering unit 211 may perform an account registration procedure in the order of inputting account information -> withdrawal agreement of input account -> test deposit authentication -> registration completion. 6 shows an exemplary diagram of an account entry screen 600 displayed on a user terminal as a user interface associated with an account registration procedure of the registration unit 211. As shown in FIG. For example, the account input screen 600 may include a user interface requesting input of account information such as a bank, an account number, and the like. In a user interface that requires the selection of a bank, the bank may be exposed as selected when the bank is selected. An alert message (for example, 'only numbers can be input') can be displayed on the account entry screen 600 when characters other than numbers are input when the account number is input. The user's basic personal information (name, date of birth, mobile phone number, etc.) necessary for registering the account is not input separately, but is stored in the personal information previously registered in the payment service or another service (for example, a portal service including the payment service) And can be automatically exposed to the account entry screen 600. [

The registration unit 211 may perform an account name confirmation procedure for an account to register only the account of the user's name in the account information input process. If the account name is not the user's account, the registration unit 211 may transmit an account- 'Failed to register the account because it is not confirmed as the account of the applicant').

When the user requests the account registration for the input account, the registration unit 211 can perform the automatic transfer withdrawal agreement procedure using the ARS (305). 6 and 7, when the user inputs the account information on the account input screen 600 and then inputs the registration button 601, the registration unit 211 displays the automatic transfer withdrawal agreement on the ARS guidance screen 710 If the user requests the ARS guidance from the ARS guidance screen 710, the ARS phone can be connected to the mobile phone number included in the user's personal information. At this time, the ARS can provide an announcement related to the automatic transfer of the account entered by the user when the user receives the telephone call.

The registration unit 211 confirms the user's intention to withdraw the automatic transfer through the ARS (306). If the user does not consent to the automatic withdrawal withdrawal, the registration unit 211 transmits an Alert message (e.g., Failed to register the account ') (307). On the other hand, if the user agrees to the automatic withdrawal, the registering unit 211 registers the input account as a remittance account to be used as a payment means (308) and transmits an Alert message (for example, Account registration is completed '). At this time, the registering unit 211 may register the account of the user with the personal information including the user identifier.

The registering unit 211 may perform an authentication procedure using the test deposit for the input account authentication. For example, the registering unit 211 registers the user's input account number (eg, a transfer amount, a transfer date and time, etc.) included in the account transfer history provided by the bank of the account at the time of test deposit, Can be authenticated. As another example, the registering unit 211 may perform the account authentication procedure using the processing information generated when the test deposit is completed. For example, the registering unit 211 transfers a predetermined amount (for example, one won) to the account with the remitter identification number arbitrarily generated for the test deposit to the account inputted by the user as the remitter information, Can be used to authenticate the user's input account. The user can confirm the account deposit details provided by the bank of the input account through SMS or ARS, and can authenticate the input account by using some information based thereon. The above-mentioned account authentication process is limited to use of transfer related information or separate process information, but the present invention is not limited to this.

8 shows an example of the account authentication screen 810 and 820 displayed on the user terminal as a user interface related to the test deposit authentication procedure of the registration unit 211. [ For example, the account authentication screen 810 may include a user interface requesting input of a remittance identification number confirmed by the user in the test deposit details of the input account. As another example, the account authentication screen 820 may include a user interface requesting input of a test deposit amount deposited in a user's input account. If the remittance identification number input from the user matches the remittance identification number generated at the time of test deposit of the input account or the amount input by the user matches the amount remitted at the time of test deposit into the input account The input account can be normally registered as a remittance account. At this time, the registration unit 211 can guide a route (for example, an ARS telephone number or the like) through which the account deposit details for the test deposit can be confirmed through the account authentication screens 810 and 820, ), The input account can be registered as a remittance account and the account registration can be canceled after a predetermined time elapses.

Accordingly, the registering unit 211 may register the payment information of the user in advance through the registration procedure of the above-described process, and may connect the registered user information with the corresponding user identifier. In addition, the registering unit 211 may link the registered shipping destination information or recent shipping destination information with the user identifier through the pre-registration procedure.

As another example, in the present invention, besides setting the remittance account, the settlement information and the password can be set as dedicated payment means for simple settlement using the URL scheme. For example, when the user wishes to use the card as a means for simple URL-based payment, the registration unit 211 registers card information (card number, etc.) in advance through a separate registration procedure, Passwords can be set together. Accordingly, when authentication is required in the case of simple settlement using a URL, payment can be processed immediately after user authentication using a password set for the simple settlement.

The payment information for simple payment can be registered and used in place of the virtual number in order to avoid exposing the payment information, that is, the card number or the account number. The card number or the account number registered as payment information can be masked at the time of exposure. For example, in the case of a card, the card company may provide a virtual number (e.g., a token) mapped to the card number without providing the actual card number so that the user is exposed to at least some of the number (e.g., the first four digits) The remaining numbers can be exposed in the form of masking. The entire settlement information is not exposed before the simple settlement is used in the state that the settlement information is registered, and if some settlement occurs even after one time, a part of the settlement information may be masked and exposed.

9 is a flowchart illustrating a method of providing a payment path in an embodiment of the present invention. The method of providing a settlement route according to the present invention can be performed by the provider 212 described with reference to FIG.

At step 901, the user terminal can receive a service page in which a specific product is exposed. At this time, the service page includes a shopping service, an integrated search service, a community service, a cafe / blog service, The service page is a service screen in which the goods of the seller are exposed, for example, a product detail page on which detailed information of a specific product is exposed, a post on a specific product The service page may be provided directly in the billing system 200 or may be provided in another service that can be interlocked with the billing system 200. For example,

In step 902, the providing unit 212 transmits a payment containing a payment URL as an interaction for providing a payment path for the product on the service page in the case where the user terminal enters the service page related to the specific goods. UI is provided. In the present invention, the billing URL means a shortened URL of a shortcut function for directly paying a specific item without inputting additional information for ordering and payment. In particular, the billing URL includes a plurality of procedures (for example, The payment method selection, the payment information input, the financial institution authentication, etc.) can be directly entered into the settlement environment in one step.

For this, the service provider 212 generates a shortened URL corresponding to the payment information linked to the corresponding service account based on the service account of the user accessing the service page, and stores the shortened URL generated on the corresponding service page in a specific product As a payment URL for the user. As another example, the billing URL may be generated including shipping address information associated with the user's service account (e.g., recent shipping address, preset shipping address, etc.) along with the payment information.

In step 903, the providing unit 212 receives a selection (that is, a payment request) for the payment UI from the user terminal through the service page of the specific goods, and displays a payment screen for ordering and payment for the specific goods at the same time to provide. In particular, the provider 212 may provide a payment screen including payment information linked to the user's service account according to the payment URL configured as the payment UI. As another example, when the settlement URL includes the coupon information, a billing screen including payment information and coupon information linked to the user's service account may be provided when accessing the settlement URL

10 to 13 illustrate exemplary views of service pages displayed on a user terminal as a user interface related to a payment path providing procedure of the provider 212. [

FIG. 10 shows a product detail page 1000 in which detailed information of the product 1 sold by the seller AAA is exposed. The user can enter the product detail page 1000 by selecting a specific product through various routes such as a shopping service, an integrated search service, a community service, a cafe / blog service, and a social network service.

As shown in FIG. 10, detailed information (a product image, a product price, a product description, a seller information, a category, etc.) of the product 1 is exposed on the product detail page 1000, The payment UI 1001 of the shortcut function may be exposed together.

11 shows a post screen 1100 related to a specific commodity, which is posted on the Internet. The user can enter the posted screen 1100 in which the information of the product 1 created by the other person (for example, a seller) through various routes such as an integrated search service, a community service, a cafe / blog service, have.

11, when at least a part of the detailed information of the product 1 is exposed on the posting screen 1100 and a shortcut function capable of immediately ordering and payment of the product 1 is attached at the time of creating the posting, The payment UI 1101 may be exposed together.

12 shows a chat screen 1200 in which a product 1 sold by a seller AAA can inquire a product through a one-to-one chat with a seller AAA. The user can enter the one-on-one chat screen 1200 with the seller AAA for the product 1 through various routes such as an integrated search service, a community service, a cafe / blog service, and a social network service. It is also possible that the user directly registers the seller AAA in the chat target list and enters the one-to-one chat screen 1200 with the seller AAA.

As shown in FIG. 12, the user can order goods together with a product inquiry about the product 1 through the one-to-one chat screen 1200 between the seller AAA and the user. In the one-to-one chat screen 1200, a payment UI 1201 of a shortcut function that enables immediate ordering and settlement of the product 1 in response to a user's order request can be exposed. For example, if the supplier 212 receives a separate request such as an order form creation request from the seller AAA in response to a user's order request in the seller AAA and the user-to-user chat environment, the provider 212 generates a payment URL, As a payment UI 1201. [

As described above, the shortcut UIs 1001, 1101, and 1201 of the payment function on the service page related to a specific product such as the product detail page 1000, the post screen 1100, and the chat screen 1200 with the seller are exposed .

When the selection of the payment UI exposed on the service page is received from the user terminal, the provider 212 can directly provide the payment screen 1300 on the service page as shown in FIG. At this time, the settlement screen 1300 may automatically expose the settlement information 1310 and the destination information 1320 linked to the service account of the user as information corresponding to the settlement URL.

Therefore, the supplier 212 can simplify the ordering step by omitting the information input and confirmation steps for ordering and payment and directly entering the settlement environment by the URL method.

14 is a flowchart showing a payment processing method in an embodiment of the present invention. The settlement processing method according to the present invention can be performed by the settlement unit 213 described with reference to FIG.

In step 1401, the payment unit 213 can confirm the payment risk level for the user when the payment request for the specific product is received from the user terminal. In the payment service according to the present invention, the user is classified according to the payment risk level, and the user who belongs to the secure class can omit the authentication process to the utmost and apply the stricter authentication policy to the user belonging to the high-risk class.

For example, the settlement unit 213 may classify the payment risk level into a safety level belonging to the whitelist, a high risk level belonging to the blacklist, a general level not belonging to both the whitelist and the blacklist, and the like. For example, the payment risk evaluation conditions are: (1) a case in which a large number of normal transactions are performed for a predetermined period of time (for example, three months) in the case of a safety level, (2) (Or a preset shipping address), (4) the case where the mobile phone number used for the dedicated service of the payment service matches the mobile phone number used for the payment, and so on. If all of the payment risk evaluation conditions except for some of the evaluation conditions (for example, (3) delivery conditions, etc.) are satisfied, the main evaluation condition (for example, (4) If they can not be met, they can be classified as high risk. In the case of a general grade, it can be divided into two or more detailed grades (eg, general grade 1, general grade 2), depending on the unevaluated evaluation criteria.

Then, the settlement unit 213 sets the personal authentication history in a specific application (for example, a portal service, an integrated search service, a shopping service, a map service, a community service, or a social network service) It can be used as an evaluation condition for classifying. For example, the payment unit 213 determines whether the self-authentication completed in the corresponding application is valid at the time of inflow, when the number of times of failure of self-authentication during a certain period (for example, 3 months) (For example, 10 times), and so on.

The settlement unit 213 may classify the settlement risk level based on user media environment information, search / settlement / transaction type information, and accident type information. The user media environment information is collected by the monitor unit 214 to be described below. The user media environment information includes payment means, terminal information, connection information, and the like used by the user for payment. For example, MAC, IP, S / Can be collected by hash processing. The search / settlement / transaction type information is also collected and analyzed by the monitor unit 214 and may include transaction patterns or inclinations that can be analyzed from the user's overall behavior leading to product ordering to product ordering on the Internet. Incident type information can be collected through related organizations, domestic and overseas trends, and malicious code analysis. In the present invention, a criterion for classifying the payment risk level based on the user's media environment information, search / settlement / transaction type information, and accident type information can be prepared. Through the classification standard, Classification can be classified.

In step 1402, if the user belongs to the safety level, the payment unit 213 omits or minimizes the authentication procedure and directly processes the order and payment for the specific commodity using the payment information corresponding to the settlement URL and the coupon information . For example, the settlement unit 213 may perform a settlement process immediately after confirming only the settlement information corresponding to the settlement URL and the coupon information about the settlement request of the user in the case of the safety class user.

In step 1403, if the user belongs to a high-risk class, the settlement unit 213 may process the settlement request of the user as payment impossible, and may provide the user terminal with an Alert message in response to the payment failure. If a user belonging to a high-risk class wishes to pay the bill, the user can authorize the upgrade to a payable grade after a separate procedure, such as checking out a customer center call or proof of the applicant's proof.

In step 1404, the settlement unit 213 may perform the identity authentication process through one or more authentication methods when the user belongs to the general category. The settlement unit 213 may be an authentication method using a password, an authentication method using an OTP (one time password), an authentication method using a fingerprint, an authentication method using a voice, an authentication method using an ARS, Method, a real name authentication method, and the like can be used.

The payment unit 213 can apply the authentication process differentiated according to the class when the general class is divided into a plurality of classes. For example, when the general class is divided into the first class and the second class, The user may apply the first authentication method using a password or OTP, and the second-level user may apply the second authentication using fingerprint or voice or ARS together with the first authentication. For example, the settlement unit 213 may perform the user authentication by using the simple settlement password described above according to the user class in performing the simple settlement using the URL scheme.

In step 1405, if the authentication of the user belonging to the general rank is successful, the settlement unit 213 can immediately process the order and settlement for the specific commodity by using the settlement information and the coupon information corresponding to the settlement URL. For example, the settlement unit 213 can perform payment processing by automatic transfer using the remittance account or settlement processing by using the settlement information (for example, a card number, etc.) registered for exclusive use of URL-based simple settlement have.

The settlement unit 213 may transmit a settlement approval request including payment information corresponding to the settlement URL to the financial company server, and may transmit the payment approval result of the financial company server to the user terminal to complete the settlement process.

Accordingly, the settlement unit 213 can perform the authentication that was originally initiated in the existing financial company for the user who requested the payment, but can apply the authentication policy differently from the authentication pass to the non-settlement according to the risk level of the user, The payment processing process can be carried out by the authentication method.

The settlement unit 213 may process the remittance process between the individuals using the account information linked to the service account of the user. Hereinafter, the remittance process will be described in detail.

15 and 16 are flowcharts showing a remittance processing method in an embodiment of the present invention. The remittance processing method according to the present invention can be performed by the settlement unit 213 described with reference to FIG.

In step 1501, the payment unit 213 may determine whether or not the remittance account is registered for the user when a service request for remittance is received from the user terminal.

In step 1502, if the remittance account is an unregistered user, the settlement unit 213 may request the registration unit 211 to register the remittance account in the account registration process for the user.

In steps 1503 to 1507, the settlement unit 213 may perform a recipient selection procedure in which, when the remittance account is already registered, the recipient's ID for remittance and the real name are input from the user. Examples of identifiers are service accounts, phone numbers, emails, etc. In addition, all information that can identify the recipient is available. In this specification, the real name may mean the actual name of the user, but it is not limited to this, and may include a name that the user actually uses in the remittance service, for example, a name pre-registered on the remittance service upon joining the service.

For example, the settlement unit 213 may select a recipient using the service account of the recipient (for example, a user ID registered in the payment service, a user ID registered in another service linked to the payment service, and the like) 1504). As another example, the settlement unit 213 may select a recipient using the recipient's mobile phone number (1505). The settlement unit 213 may receive the real name of the selected recipient together with the selected recipient using the service account or mobile phone number (1506). At this time, the real name of the recipient can be inputted through the direct input method.

When the recipient is selected using the service account and the mobile phone number, the payment unit 213 may directly input the service account or mobile phone number of the recipient by providing the direct input method. Alternatively, the settlement unit 213 may receive the service account or mobile phone number of the selected recipient in the address book after exposing the address book stored on the user terminal. Alternatively, the payment unit 213 exposes the address book on the address book application in cooperation with a separate application (hereinafter referred to as an 'address book application') having the address book, and then inputs the service account or mobile phone number of the recipient selected in the address book Can receive.

As another example, the settlement unit 213 may specify a recipient selected in the remittance friend list after having a recent remittance history or exposing a remittance friend list set by the user (1507). To this end, the registration unit 211 automatically registers the service account and / or mobile phone number of the person who has recently been sent or received by the user as a remittance friend, And / or mobile phone number, and real name. At this time, if the payment unit 213 selects the recipient using the remittance friend list, the real name entry procedure may be omitted because the remittance friend list includes the real name.

17 shows an example of a remittance information input screen 1700 displayed on the user terminal as a user interface related to the remittance processing procedure of the settlement unit 213. [ For example, the remittance information input screen 1700 may include a user interface requesting input of remittance information including a recipient, a remittance amount, a remittance-related message, and the like. At least a part of the information on the remittance account registered by the user may be exposed on the remittance information input screen 1700. The remittance information input screen 1700 may further include a user interface requesting a personal information third party provision agreement. The payment unit 213 may provide a recipient selection page when inputting an interface for recipient selection on the remittance information input screen 1700. [

18 shows an example of a recipient selection screen 1800 for recipient selection as a user interface related to the remittance processing procedure of the payment unit 213. [ For example, the recipient selection screen 1800 may include a first user interface for selecting a recipient using at least one of a service account, a mobile phone number, and an identifier such as e-mail.

When the first user interface is selected on the recipient selection screen 1800, the payment unit 213 receives an input page for inputting a real name together with any one of service account, mobile phone number, e-mail, (1910, 1920).

When the first user interface is selected on the recipient selection screen 1800, the payment unit 213 accesses the address book on the user terminal or the address book on the address book application and displays the selected page 2010 including the address book, And then, when a specific recipient is selected in the selection page 2010, the input page 2020 for inputting the real name of the recipient can be provided.

In consideration of the service providing environment, the settlement unit 213 provides the input pages 1910 and 1920 for inputting the identifier and real name of the recipient as shown in FIG. 19 in the remittance environment through the web browser, The selection page 2010 using the address book can be provided in cooperation with the address book as shown in FIG.

Referring to FIG. 18, if there is a remittance friend list, the remittee selection screen 1800 may further include a second user interface for selecting a remittee using the remittance friend list. A profile image, a service account, a real name, and the like may be exposed in the remittance friend list of the recipient selection screen 1800.

The settlement unit 213 can expose the information of the recipient selected by the user on the remittance information input screen 2100 as shown in FIG. 21 when the recipient selection is completed. At this time, the information of the receiver exposed on the remittance information input screen 2100 may include an identifier (service account, telephone number, e-mail, name, etc.) corresponding to the receiver selection method in addition to the real name inputted by the user .

In step 1508, the settlement unit 213 may request the user to input the remittance amount, and may receive the remittance amount input by the user through the remittance information input screen 2100. [ For example, the remittance information input screen 2100 may include an area for directly inputting an amount in a unit of a circle, an amount button for automatically inputting a predetermined amount, and the like.

The following procedure after the remittance procedure described with reference to FIG. 16 through FIG. 15 will be described next.

In step 1609, the payment unit 213 can confirm the remittance limit per unit period of the user when the recipient selection and remittance amount input from the user is completed and the remittance request is received. As an example, the remittance limit per unit period can be set automatically by default or directly set by the user, for example, 500,000 won per 1day 1ID. As another example, the remittance limit per unit period may be set differently depending on whether the child is a minor or not, for example, an adult may be set at 500,000 won per 1 day 1ID and a minor 100,000 won per 1 day 1ID. The minimum remittance limit with the remittance limit per unit period can also be preset to a certain amount (e.g., one thousand won).

In step 1610, the settlement unit 213 adds the remittance amount requested by the recent remittance to the existing remittance amount transferred in the unit period, and stops the remittance process if the sum amount exceeds the remittance limit per unit period, Message. ≪ / RTI >

In step 1611, the settlement unit 213 may add the remittance amount requested by the recent remittance to the existing remittance amount transferred in the unit period, and if the sum amount does not exceed the remittance limit, the remittance of the parent account related to the remittance account can be confirmed. The parent account balance limit can be set automatically or can be set by the user directly. For example, the balance limit can be set at 2 million won when remitting money.

The settlement unit 213 may sum up the remittance amount requested to be remitted recently with the remittance amount that is waiting to be received, and may provide an alittle message indicating the exceeding limit when the sum amount exceeds the remaining amount limit of the mother's account (1610).

In step 1612, the settlement unit 213 may add the remittance amount requested for the recent remittance to the remittance amount waiting to be received, and may request the user to input the password for authentication if the sum amount does not exceed the remaining amount limit of the parent account.

In step 1613, the settlement unit 213 may compare the password input by the user with the pre-registered password to confirm whether or not they match. If the two passwords do not match, an Alert message indicating a password error may be provided.

In step 1614, the settlement unit 213 can confirm the balance of the remittance account when the password input by the user matches the pre-registered password.

In step 1615, the settlement unit 213 provides an alittle message indicating the insufficient balance if the remittance amount requested by the recent remittance exceeds the remittance amount of the remittance account. If the remittance account balance is not exceeded, You can send remittance details for the remittance amount.

In steps 1616 and 1617, the settlement unit 213 may provide a function of canceling the remittance before the remittance is received by the recipient for the remittance that is waiting to be received. When the user requests the cancellation of the remittance You can cancel the transfer of the case.

In steps 1618 and 1617, the settlement unit 213 can cancel the remittance when the remittance acceptance deadline has elapsed, if the recipient has not received the money sent by the user within the preset remittance acceptance period. A remittance acceptance period (for example, three days) may be set as a time limit for the recipient to receive the remittance amount, wherein the remittance acceptance period is automatically set to default or can be set directly by the user who is the remittance sender .

In steps 1619, 1620 and 1617, the settlement unit 213 can confirm whether or not the real name entered by the user together with the identifier coincides with the actual real name corresponding to the corresponding identifier. If the real name inputted by the user is different from the actual real name You can provide an Alert message indicating the blindness error and cancel the transfer of the case.

The settlement unit 213 can confirm the real name by comparing the identity of the recipient included in the transfer information and the real name with the real name in the personal information registered in the database with respect to the real name, , And may be omitted when the recipient is selected in the remittance friend list.

If the real name of the recipient matches the real name included in the remittance information of the user, the payment unit 213 sends the money to the recipient, thereby completing the remittance processing process can do.

In steps 1621, 1622, and 1623, the settlement unit 213 checks whether the user has an original account issue when the remittance is canceled. If there is no specific issue, the settlement unit 213 returns the canceled amount to the original account. You can redeem the canceled amount with the set balance.

22 is a flowchart showing a remittance receiving method in an embodiment of the present invention. The remittance receiving method according to the present invention can be performed by the settlement unit 213 described with reference to FIG.

In step 2201, the settlement unit 213 can provide a receipt notification to the user together with the transfer details when the sender's transfer details are received. For example, the settlement unit 213 may send a text message including a remittance reception history (sender information, remittance date, remittance amount, etc.) to a corresponding user terminal through a text service (SMS, Can be transmitted. As another example, the settlement unit 213 may expose the remittance receipt through the reminder page of the user associated with the settlement service for the remittance using the user as the recipient. As another example, the settlement unit 213 can simultaneously apply the two remittance notification methods. The remittance notification may include a link to a remittance receipt detail screen from which the sender can receive the remittance.

Furthermore, the settlement unit 213 can determine the remittance reception notification method according to the recipient selection method by the sender. For example, if a sender selects a recipient using his / her mobile phone number, he / she can notify the receipt of the remittance through a text message. If the recipient is selected using the service account, If you select a recipient using the transfer friend list, you can notify the recipient of the transfer by using both the text message and the notification page.

The settlement unit 213 can provide a remittance reception notification through a text message even if the user selected by the sender is not a member registered in the settlement service (or another service linked to the settlement service), and then proceeds to the remittance receiving step In order to do so, you can proceed with the necessary procedures for receipt of the remittance, including the membership registration procedure and the agreement procedure for using the payment service.

In steps 2202 and 2203, the settlement unit 213 can cancel the remittance of the relevant case when the user receives a remittance cancellation request from the sender before receiving the remittance of the sender, The reminder page associated with the service may provide a reminder to remind the sender that the remittance has been canceled by the sender.

In step 2204 or 2203, if the user does not receive the sender's remittance within the predetermined remittance acceptance period, the payment unit 213 cancels the remittance of the relevant case and sends a notice page associated with the text service and / or the payment service to the user A remittance cancellation notice indicating that the remittance has been canceled due to the passage of time can be provided.

In steps 2205, 2206 and 2203, the settlement unit 213 can confirm whether or not the real name of the user who received the remittance notification for the sender's remittance matches the real name included in the remittance details of the sender, If this is not the case, you can provide an Alert message indicating the blindness error and cancel the transfer of the case. The blindness check procedure is performed when the sender selects the recipient using the service account or cell phone number, and may be omitted if the recipient is selected in the remittance friend list.

In step 2207, the settlement unit 213 may request the reception of the amount sent by the sender within the remittance acceptance period, and perform the remittance reception method selection procedure when the real name authentication is normally processed.

23 shows an example of a remittance receiving detailed screen 2300 displayed on the user terminal as a user interface related to a remittance receiving procedure of the payment unit 213. [ For example, the remittance reception detail screen 2300 may be configured to expose details of remittance details of the sender (e.g., sender name, remittance date, remittance amount, remittance related message, etc.), and a remittance reception method May be included. Accordingly, the user can confirm the remittance detailed information exposed on the remittance receiving detailed screen 2300, and then select a remittance receiving method for receiving the remittance amount of the sender.

The method of receiving remittance may include, but is not limited to, the manner in which it is received in a bank account and the manner in which it is received in electronic payment means (e.g., points) associated with the payment service. In order to receive a bank account, it is necessary to register an account on the payment service. In case of points, you can receive remittance without a registered account.

In steps 2208 and 2209, the payment unit 213 can confirm whether or not a bank account registered on the payment service exists for the user when the user selects the reception method to the bank account in the remittance receiving method.

In step 2210 and step 2211, if the account of the user registered on the payment service does not exist, the payment unit 213 requests the user to proceed with the account registration process. If the user does not proceed with the account registration process, An Alert message indicating an error can be provided. At this time, if the user does not proceed with the account registration process, the settlement unit 213 may suspend remittance reception of the relevant case or request reselection of the remittance reception mode.

In steps 2209, 2210, and 2212, when the account of the user registered on the payment service already exists or a new account is registered through the account registration process, the payment unit 213 determines whether the state of the corresponding account is a normal receivable state . At this time, if the registered account of the user is not in the remittance reception state, the payment unit 213 provides an Alert message indicating a remittance reception error, and if the user's registered account is in a normal state, the remittance amount of the sender is deposited into the account Thereby completing the remittance receiving process.

In steps 2213 and 2214, the settlement unit 213 can confirm the balance of the user when the user selects the accumulation method as the electronic payment means in the remittance receiving system. The balance limit can be set automatically or directly by the user, for example, the point balance limit can be set at 2 million won.

The settlement unit 213 adds up the remittance amount received from the sender and the current balance of the electronic payment means of the user, and if the sum amount does not exceed the balance limit, the remittance amount of the sender is converted into the electronic payment means so as to be accumulated in the corresponding user Thereby completing the remittance receiving process.

The payment unit 213 can perform the user authentication procedure using the authentication password registered on the payment service, but the authentication procedure using the password can be omitted in the remittance receiving procedure.

On the other hand, the settlement unit 213 may sum up the remittance amount received from the sender and the current balance of the electronic payment means of the user, and provide an Alert message indicating the remittance reception error if the sum amount exceeds the remaining amount limit. At this time, the settlement unit 213 may suspend the receipt of the request or request the reselection of the remittance reception method if the sum amount exceeds the preset limit of the electronic payment means balance.

In the above description, the amount of money remitted by the sender is fully received by one of the bank account and the electronic payment means. However, the present invention is not limited to this, and the remittance receiving method may be applied differently or enlargedly. For example, it is possible to provide a multiple reception method by which the user can receive the remittance by dividing the remittance into a bank account and an electronic payment means, whereby the user can selectively distribute the remittance amount, part of the remittance amount to the bank account, It is also possible to receive it by means.

Accordingly, the settlement unit 213 can process the direct transfer between the individuals subscribed to the service using the service account and the real name of the recipient, and in addition to receiving the money received from the other person in the bank account of the user, It can be converted into a means. The settlement unit 213 may provide a settlement environment that can be immediately used as a payment for online commerce (e.g., Internet shopping, etc.) after the user receives the amount sent by the sender by means of an account or an electronic payment means . In addition, when the simple settlement is registered, the settlement unit 213 can provide a convenient settlement environment even in face-to-face settlement in the off-line. For example, the electronic payment means can be used as a payment means based on short-range wireless communications such as bar codes or NFC.

Furthermore, the settlement unit 213 comprehensively analyzes various collected information (user media environment information, search / settlement / transaction type information, accident type information, and the like), and applies various rules for abnormal transaction detection Such rules can be used to discriminate the existence of an abnormal financial transaction and support appropriate responses (for example, notification, card suspension, illegal transaction report, etc.). For example, if the payment unit 213 changes the destination through an individual contact after placing an order with a recent delivery destination, remit or use the electronic payment means immediately, or attempt to make a high payment after a small payment, It is possible to detect various kinds of abnormal transactions including the case of attempting settlement of the form.

FIG. 24 is a flowchart illustrating a method of notifying a periodic payment in an embodiment of the present invention. FIG. The periodic payment notification method according to the present invention can be performed by the monitor unit 214 described with reference to FIG.

In step 2401, the monitor unit 214 may collect payment type information associated with the user. For example, the payment type information may include product order information (e.g., product name, product category, date of order, number of orders, etc.) that the user has actually purchased two or more times,

In step 2402, the monitor unit 214 may analyze the user's regular purchase pattern based on the payment type information. In other words, the monitor unit 214 can analyze a product that the user regularly purchases and a purchase cycle of each product according to the product order history. For example, if the user orders the bottled water 30 days after the first order and then orders another 28 days, the user's bottled water purchase cycle can be analyzed as the average purchase cycle 29 days.

In steps 2403 and 2404, the monitor unit 214 may provide a periodical purchase notification to the user terminal according to the analyzed product purchase cycle based on the payment type information of the user. The regular purchase notification may include product information as a regular purchase target. For example, the monitor unit 214 may provide a notification of a regular purchase item at a predetermined point in time (for example, one week before, one day before, on the same day, etc.) according to a product purchase cycle of the user.

25 is an exemplary diagram of a periodic payment notification screen 2500 displayed on the user terminal as a user interface related to the periodic payment notification procedure of the monitor unit 214. [ For example, the periodical payment notification screen 2500 may include a message indicating a periodical payment notification, and may include a payment UI including information on the periodical purchase product and a payment URL for the periodical purchase product. At this time, the billing URL may correspond to the payment information and the coupon information associated with the service account of the user, or may be a shortened URL corresponding to payment information and coupon information used for settlement of the latest order of the product. When the user selects the payment UI exposed on the periodical payment notification screen 2500, the user can directly enter the payment screen (for example, the payment screen described with reference to FIG. 13) and proceed directly with the payment.

In the above description, the periodical payment notification is automatically provided by analyzing the purchase pattern of the user. However, the present invention is not limited to this, and it is also possible to provide the periodical payment notification through presetting by the user in some cases. For example, the user may periodically set a commodity (for example, bottled water, diaper, wipes, etc.) and a commodity purchasing cycle in advance, and the monitor unit 214 displays a commodity and a commodity purchase cycle The user terminal can provide a periodic payment notification for each product.

Accordingly, the monitor unit 214 can provide notifications enabling direct settlement for regular purchase according to purchase patterns or reservation settings according to the transaction history of the user.

The above-mentioned payment service method may include more shortened operations or additional operations based on the details of the settlement system described with reference to FIGS. 1 to 25. In addition, more than one operation may be combined, and the order or location of the operations may be changed.

FIGS. 4 to 8, FIGS. 10 to 13, 17 to 22, 23, and 25 are exemplary screens for facilitating understanding of the invention and for convenience of explanation, .

26 is a block diagram for explaining an example of the internal configuration of a computer system according to an embodiment of the present invention. The computer system 2600 includes at least one processor 2610, a memory 2620, a peripheral interface 2630, an input / output subsystem 2640, A power circuit 2650, and a communication circuit 2660. [ At this time, the computer system 2600 may correspond to a user terminal.

The memory 2620 may include, for example, a high-speed random access memory, a magnetic disk, SRAM, DRAM, ROM, flash memory or non-volatile memory. have. Memory 2620 may include software modules, a set of instructions, or various other data required for operation of computer system 2600. At this point, accessing memory 2620 from other components, such as processor 2610 or peripheral device interface 2630, may be controlled by processor 2610.

Peripheral device interface 2630 may couple the input and / or output peripheral devices of computer system 2600 to processor 2610 and memory 2620. The processor 2610 may execute a variety of functions and process data for the computer system 2600 by executing a software module or set of instructions stored in the memory 2620.

The input / output subsystem 2640 can couple various input / output peripheral devices to the peripheral interface 2630. For example, input / output subsystem 2640 may include a controller for coupling a peripheral, such as a monitor, keyboard, mouse, printer, or a touch screen or sensor, as needed, to peripheral interface 2630. According to another aspect, the input / output peripheral devices may be coupled to the peripheral device interface 2630 without going through the input / output subsystem 2640.

The power circuitry 2650 may provide power to all or a portion of the components of the terminal. For example, the power circuitry 2650 may include one or more power supplies, such as a power management system, a battery or alternating current (AC), a charging system, a power failure detection circuit, a power converter or inverter, And may include any other components for creation, management, distribution.

The communication circuit 2660 may enable communication with other computer systems using at least one external port. Alternatively, as needed, communication circuitry 2660 may communicate with other computer systems by sending and receiving RF signals, also known as electromagnetic signals, including RF circuitry.

26 is merely an example of a computer system 2600, and the computer system 2600 may include additional components not shown in Fig. 26, Lt; RTI ID = 0.0 > components. ≪ / RTI > For example, in addition to the components shown in FIG. 26, a computer system for a mobile communication terminal may further include a touch screen, a sensor, and the like, and may be connected to a communication circuit 2660 in various communication methods (WiFi, , Bluetooth, NFC, Zigbee, etc.). Components that may be included in computer system 2600 may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing or application specific integrated circuits.

As described above, according to the embodiment of the present invention, the order step can be simplified through the simple inflow path by omitting the unnecessary procedure and providing the one-click settlement model which can directly settle the settlement through the URL method. Furthermore, according to the embodiment of the present invention, it is possible to maximize the convenience of a user who has a regular purchasing behavior by providing a notice of direct settlement according to a purchase pattern or a reservation setting according to a user's transaction history. According to the embodiment of the present invention, a leading and free authentication policy can be applied by performing the authentication in charge of the financial institution directly in the payment system for safe transaction of payment. According to the embodiment of the present invention, by differentiating the authentication procedure from the one-click to the non-payment according to the risk level of the user or the transaction situation, it is possible to provide a more flexible and rational yet more rigorous and strong authentication policy Can be applied.

The methods according to embodiments of the present invention may be implemented in the form of a program instruction that can be executed through various computer systems and recorded in a computer-readable medium.

The program according to the present embodiment can be configured as a PC-based program or an application dedicated to a mobile terminal. The app relating to the payment service according to the present embodiment may be implemented in a form of an independently operating program or in the form of an in-app of a specific application (for example, a portal service app or a search service app) It can be implemented so that it can operate on a specific application.

In addition, methods according to embodiments of the present invention can be performed by an application associated with a server system providing a payment service by controlling a user terminal. As an example, such an application may execute one or more processes configured to perform one or more of the features described herein. Further, such an application can be installed in a user terminal through a file provided by a file distribution system. For example, the file distribution system may include a file transfer unit (not shown) for transferring the file at the request of the user terminal.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA) , A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The embodiments of the present invention described above can be embodied in the form of a computer program that can be executed on various components on a computer, and the computer program can be recorded on a computer-readable medium. At this time, the medium may be a program that continuously stores a computer executable program, or temporarily stores the program for execution or downloading. In addition, the medium may be a variety of recording means or storage means in the form of a combination of a single hardware or a plurality of hardware, but is not limited to a medium directly connected to a computer system, but may be dispersed on a network. Examples of the medium include a magnetic medium such as a hard disk, a floppy disk and a magnetic tape, an optical recording medium such as CD-ROM and DVD, a magneto-optical medium such as a floptical disk, And program instructions including ROM, RAM, flash memory, and the like. As another example of the medium, a recording medium or a storage medium managed by a site or a server that supplies or distributes an application store or various other software to distribute the application may be mentioned.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

200: Payment System
211: Register
212:
213:
214:

Claims (20)

A computer-implemented payment service method,
Providing a URL (uniform resource locator) corresponding to the payment information linked to the service account of the user on the service screen when the user terminal enters a service screen related to a specific product; And
And performing direct settlement processing using the settlement information without inputting additional information upon receiving a selection of the URL from the terminal of the user,
The step of performing the payment processing includes:
An independent authentication procedure independent of a financial institution related to the payment information is performed,
Checking the payment risk level of the user; And
And performing an authentication process for the user by applying an authentication method corresponding to the payment risk level. The method according to claim 1,
The step of providing the URL further comprises:
Providing the URL including destination information connected to the service account of the user,
The step of performing the payment processing includes:
And directly performing settlement processing using the settlement information and the destination information
Wherein the payment service method comprises the steps of: The method according to claim 1,
The step of performing the payment processing includes:
When receiving a selection of the URL from the terminal of the user, providing the payment screen automatically inputting the payment information to the terminal of the user
Wherein the payment service method comprises the steps of: The method according to claim 1,
The step of performing the identity authentication procedure comprises:
If the payment risk level of the user is a safety level belonging to the whitelist, the payment processing is performed without a separate authentication procedure
Wherein the payment service method comprises the steps of: The method according to claim 1,
The step of performing the identity authentication procedure comprises:
If the delivery address included in the payment request information is the same as the delivery address connected to the service account of the user or the address of the mail address which has recently been successfully processed,
Wherein the payment service method comprises the steps of: The method according to claim 1,
The step of performing the identity authentication procedure comprises:
Performing primary authentication using at least one authentication method according to the payment risk level of the user or performing secondary authentication using at least another authentication method together with the primary authentication
Wherein the payment service method comprises the steps of: The method according to claim 1,
The step of verifying the payment risk level comprises:
Using the at least one of the user's previous normal settlement history of settlement of payment, the use of the service exclusive application, the recent successful payment destination, the mobile phone number used at the settlement, and the personal authentication history in the specific application linked to the settlement service, Checking the rating
Wherein the payment service method comprises the steps of: The method according to claim 1,
The step of verifying the payment risk level comprises:
The payment risk level is checked using the user's medium environment information including at least one of payment means, terminal information, and access information used by the user in past payment
Wherein the payment service method comprises the steps of: The method according to claim 1,
Analyzing a periodic purchase item and a purchase period for each periodical purchase item using the past payment information of the user; And
Providing a settlement notification of the periodically purchased product to the terminal of the user according to the purchase cycle
Further comprising: 10. The method of claim 9,
The step of providing the payment notice to the terminal of the user includes:
Providing a notification message including information on the regular purchase product and a URL corresponding to payment information linked to the service account of the user
Wherein the payment service method comprises the steps of: A computer-readable storage medium storing a program for executing the method according to any one of claims 1 to 10. At least one program loaded memory; And
At least one processor
Lt; / RTI >
Wherein the at least one processor, under control of the program,
Providing a URL (uniform resource locator) corresponding to the payment information linked to the service account of the user on the service screen when the user terminal enters a service screen related to a specific product; And
When the selection of the URL is received from the terminal of the user, performing a direct settlement process using the settlement information without inputting any additional information,
The step of performing the payment processing includes:
An independent authentication procedure independent of a financial institution related to the payment information is performed,
Checking the payment risk level of the user; And
Performing a personal authentication procedure for the user by applying an authentication method corresponding to the payment risk level;
. 13. The method of claim 12,
The step of providing the URL includes:
Providing the URL including destination information connected to the service account of the user,
The step of performing the payment processing includes:
And directly performing settlement processing using the settlement information and the destination information
. 13. The method of claim 12,
The step of performing the payment processing includes:
When receiving a selection of the URL from the terminal of the user, providing the payment screen automatically inputting the payment information to the terminal of the user
. 13. The method of claim 12,
The step of performing the authentication process includes:
If the delivery address included in the payment request information is the same as the delivery address connected to the service account of the user or the address of the mail address which has recently been successfully processed,
. 13. The method of claim 12,
The step of performing the authentication process includes:
Performing primary authentication using at least one authentication method according to the payment risk level of the user or performing secondary authentication using at least another authentication method together with the primary authentication
. 13. The method of claim 12,
The process for confirming the payment risk level comprises:
Using the at least one of the user's previous normal settlement history of settlement of payment, the use of the service exclusive application, the recent successful payment destination, the mobile phone number used at the settlement, and the personal authentication history in the specific application linked to the settlement service, Checking the rating
. 13. The method of claim 12,
The process for confirming the payment risk level comprises:
The payment risk level is checked using the user's medium environment information including at least one of payment means, terminal information, and access information used by the user in past payment
. 13. The method of claim 12,
Wherein the at least one processor, under control of the program,
Analyzing a periodic purchase item and a purchase period for each periodical purchase item using the past payment information of the user; And
Providing a settlement notification for the periodically purchased product to the terminal of the user according to the purchase cycle
Lt; / RTI > 20. The method of claim 19,
The step of providing the settlement notification to the terminal of the user includes:
Providing a notification message including information on the regular purchase product and a URL corresponding to payment information linked to the service account of the user
.

Images