KR20240055364A - A method of brokering a car transaction and a server providing the same - Google Patents

Abstract

Embodiments of the present disclosure relate to a car transaction brokerage method in which a first server including a processor communicates with a user terminal, the steps of communicating with the user terminal to generate a customer identification value corresponding to the user of the user terminal, a second server transmitting a customer identification value to the user, receiving information on loan products that can be provided to the user from a second server, displaying information on loan products received from the second server on the user terminal, and accessing the third server. Thus, it is possible to provide a car transaction brokerage method including the step of receiving first car information including the inspection result of the car selected by the user of the user terminal. According to embodiments of the present disclosure, a car transaction brokerage method that can alleviate information asymmetry that may occur in car transactions and a server that provides the same can be provided.

Description

Car transaction brokerage method and server providing the same {A METHOD OF BROKERING A CAR TRANSACTION AND A SERVER PROVIDING THE SAME}

The present invention relates to a method for brokering automobile transactions and a server that provides the same.

Car transactions have been active recently. Examples of types of automobile transactions include new car transactions that purchase automobiles manufactured by a manufacturer, and used car transactions that purchase automobiles owned by other owners (including those owned by natural persons, associations, corporations, etc.). .

In the case of used car trading, the following two inconveniences may arise.

First, problems may arise due to information asymmetry. For example, the owner of a car (or the transferor of the car) is quite familiar with the defects of the car that is the subject of the transaction. However, it is difficult for a car transferee who wants to transfer a car to closely identify defects in the car at the time of deciding to purchase the car. This may result in information asymmetry in automobile transactions.

Second, car title loans for purchasing used cars may be somewhat limited. Financial companies that sell auto title loans need to know whether the car transferee is actually applying for a car title loan to purchase a used car, or is trying to misappropriate the used car loan funds for other purposes under the guise of purchasing a used car. difficult. For example, if you apply for a car collateral loan disguised as a used car transaction between individuals and the title to the car does not transfer, there is a risk that the financial company will not be able to place a mortgage on the car. Accordingly, in the case of transactions between individuals, it is difficult for the car transferee to apply for a car collateral loan from a financial company.

Meanwhile, a car transferee may purchase a car from a car dealer (eg, an association of car dealers who sell used cars). In these cases, the car transferee can utilize a car title loan. For example, a car transferee may be provided with a list of car loan products by a car dealer and select a car title loan product. However, in such cases, financial companies often set the interest rate of loan products by considering the commission to be paid to the car dealer.

Therefore, when matching a car transferee with a financial company that provides car loan products, there is a need for a car transaction brokerage method that allows the car transferee to use the loan product at a slightly lower interest rate.

The technical task of the embodiments of the present disclosure is to provide a car transaction brokerage method that can alleviate information asymmetry that may occur in car transactions and a server that provides the same.

The technical task of the embodiments of the present disclosure is to provide a car transaction brokerage method and a server that provides the car transferee with the opportunity to receive a car collateral loan at a low interest rate in the trade of a used car.

Embodiments of the present disclosure relate to a car transaction brokerage method in which a first server including a processor communicates with a user terminal, the steps of communicating with the user terminal to generate a customer identification value corresponding to the user of the user terminal, a second server transmitting a customer identification value to the user, receiving information on loan products that can be provided to the user from a second server, displaying information on loan products received from the second server on the user terminal, and accessing the third server. Thus, it is possible to provide a car transaction brokerage method including the step of receiving first car information including the inspection result of the car selected by the user of the user terminal.

Embodiments of the present disclosure may further include accessing a fourth server to receive second car information. The second car information may include at least one of an accident history of the car selected by the user, an owner change history of the car selected by the user, and a repair history of the car selected by the user.

Embodiments of the present disclosure may further include accessing a fourth server to receive second car information. The second car information may include the car registration register of the car selected by the user.

The first car information may include the user's car purchase intention data regarding the car selected by the user.

The first vehicle information may include evaluation data for undisclosed defects.

Information on loan products may include mortgage loan interest rates and collateral loan limits.

Embodiments of the present disclosure may include receiving a code corresponding to a loan product from a user terminal, and transmitting the customer identification value and code to a second server.

The method may further include displaying a user interface for accessing content provided by the second server on the user terminal.

The user interface may correspond to at least one of an API (Application Programming Interface) and a URL.

A step of checking whether the user has subscribed to mandatory automobile insurance may be further included.

It further includes displaying a user interface for accessing a fifth server on the user terminal, and the fifth server may include a server of an insurance company that sells mandatory automobile insurance products.

It further includes the step of inducing subscription to mandatory automobile insurance, wherein the step of inducing mandatory automobile insurance subscription includes accessing a fifth server to query mandatory automobile insurance products, and sending information on the searched mandatory automobile insurance products to the user terminal. It may include displaying, receiving a code corresponding to one of the mandatory automobile insurance products from the user terminal, and transmitting the customer identification value and code to a fifth server.

The second server is a server for each of the plurality of financial companies, and the first server transmits a customer identification value to the server for each of the plurality of financial companies and information on loan products received from the server for each of the plurality of financial companies. can be displayed on the user terminal.

Embodiments of the present disclosure include a server that communicates with a user terminal through a network, a communicator connected to the network, a memory that stores data, and a controller configured to control the communicator and the memory and communicate with the user terminal through the communicator. It includes, the controller interacts with the user terminal to generate a customer identification value corresponding to the user of the user terminal, transmits the customer identification value to the second server, and receives information about loan products that can be provided to the user from the second server. Provides a server that receives, displays information on the loan product received from the second server on the user terminal, and accesses the third server to receive first car information including the inspection result of the car selected by the user of the user terminal. can do.

The controller may further receive second vehicle information by accessing a fourth server. The second car information may include at least one of an accident history of the car selected by the user, an owner change history of the car selected by the user, and a repair history of the car selected by the user.

The first car information may include the user's car purchase intention data regarding the car selected by the user.

The controller may receive a code corresponding to the loan product from the user terminal and transmit the customer identification value and code to the second server.

The controller can inquire whether the user has subscribed to mandatory automobile insurance.

The controller may query the fifth server for mandatory automobile insurance products, display information on the searched mandatory automobile insurance product on the user terminal, and transmit a code corresponding to the mandatory automobile insurance product selected from the user terminal to the fifth server. there is.

The second server is a server of each of the plurality of financial companies, and the controller transmits the customer identification value to the server of each of the plurality of financial companies and provides information on loan products received from the servers of each of the plurality of financial companies to the user. It can be displayed on the terminal.

According to embodiments of the present disclosure, a car transaction brokerage method that can alleviate information asymmetry that may occur in car transactions and a server that provides the same can be provided.

According to embodiments of the present disclosure, a car transaction brokerage method through which a car transferee can receive a car collateral loan at a low interest rate in the trade of a used car and a server that provides the same can be provided.

Figure 1 is a system block diagram illustrating a server providing a car transaction brokerage method according to embodiments of the present disclosure and other servers and terminals that can be connected to the server through a network.
Figure 2 is a block diagram of a server providing a car transaction brokerage method according to embodiments of the present disclosure.
Figure 3 is a flowchart showing the steps of providing a login page and applying for a car transaction brokerage service in the car transaction brokerage method according to embodiments of the present disclosure.
Figure 4 is a diagram showing the data flow in the step of transmitting the user's customer identification value to the server of a company providing automobile inspection services.
Figure 5A is an overall flow chart of a car transaction brokerage method according to embodiments of the present disclosure.
FIG. 5B is an example of a flowchart further including embodiments of a method for brokering a car transaction that may be performed after the steps of FIG. 5A.
Figure 6a is a flowchart illustrating in more detail the steps for generating a list of automobile mortgage loan products.
Figure 6b is a flowchart illustrating a case where the step of creating a list of car collateral loan products includes a step of checking the accident history of the car and a step of checking the vehicle information of the car.
Figure 7 is another flowchart illustrating in more detail the steps for generating a list of car title loan products.
Figure 8 is a flowchart further illustrating steps that can be additionally performed when a user applies for a car collateral loan from a financial company.
Figure 9 is a flow chart illustrating in more detail the steps for encouraging users to subscribe to mandatory automobile insurance.
Figure 10 is another flowchart illustrating in more detail the steps of inducing a user to subscribe to mandatory automobile insurance.
Figure 11 is a flowchart showing in more detail the steps for generating an automobile transfer certificate online.
Figure 12 is a flowchart showing in more detail the steps of requesting payment of a fee for transferring a car title.
Figure 13 is a diagram showing the data flow that occurs in the step of receiving information on the user's automobile inspection date and time.
Figure 14 is a diagram showing another data flow that occurs in the step of receiving the user's automobile inspection date and time information.
Figures 15a to 15d are diagrams showing the data flow in the step of creating a list of car mortgage loan products.
Figures 16A to 16C are diagrams showing the data flow that occurs in the step of matching a user and a financial company.
Figure 17 is a diagram showing the data flow that occurs in the step of receiving an inspection report.
Figures 18A to 18D are diagrams showing the data flow that occurs in the step of inducing the user to subscribe to mandatory automobile insurance.
Figures 19a to 19c are diagrams showing the data flow that occurs in the step of generating a car transfer certificate online.
Figures 20a and 20b are diagrams showing the data flow that occurs in the step of requesting payment of a fee for transferring the title of a car.
Figure 21 is a diagram showing the data flow that occurs in the step of applying for the transfer of the car title by attaching the stored car transfer certificate and data proving the payment history of the fee.
Figure 22 is a diagram showing the data flow that occurs in the step of transmitting payment proof data such as acquisition tax and title transfer application data to the server of a financial company.

Hereinafter, with reference to the attached drawings, various embodiments of the present invention will be described in detail so that those skilled in the art can easily practice the present invention. The invention may be implemented in many different forms and is not limited to the embodiments described herein.

In order to clearly explain the present invention, parts that are not relevant to the description are omitted, and identical or similar components are given the same reference numerals throughout the specification. Therefore, the reference signs described above can be used in other drawings as well.

In addition, the size and thickness of each component shown in the drawings are arbitrarily shown for convenience of explanation, so the present invention is not necessarily limited to what is shown. In order to clearly represent multiple layers and regions in the drawing, the thickness may be exaggerated.

Additionally, the expression “same” in the description may mean “substantially the same.” In other words, it may be identical to the extent that a person with ordinary knowledge can understand that it is the same. Other expressions may also be expressions where “substantially” is omitted.

In addition, the embodiment shown in the drawings of this specification merely illustratively shows one of the embodiments of the present disclosure. That is, embodiments of the present disclosure may include embodiments in which any one of the plurality of configurations shown in the drawings is omitted.

1 shows a server 110 that provides a car transaction brokerage method according to embodiments of the present disclosure, and other servers 120, 130, 160, 170, which can be connected to the server 110 and the network 100. This is a system block diagram showing examples 180 and 190) and terminals 140 and 150.

The network 100 may be configured to enable connection between the first server 110 described in the embodiments of the present disclosure and other servers or terminals. The network 100 may include an online network using the Internet, etc., an offline network using an offline line, etc.

The first server 110 is a server of a company that provides a car transaction brokerage method or car transaction brokerage service. A “car transaction” may include a used car transaction where the car has different owners. Meanwhile, “car” may comprehensively refer to not only four-wheeled means of transportation, but also means of transportation other than four wheels. For example, “car” refers to two-wheeled vehicles including motorcycles, special-purpose machines that can be used at construction sites, etc. (e.g., construction machines such as excavators), and public transportation for the purpose of transporting passengers (e.g. , bus), etc.

The second server 120 is a server of a company that provides automobile inspection services. For example, a “company providing automobile inspection services” may be a company that closely inspects the condition of used cars and provides the inspection results. For example, a “company providing automobile inspection services” may be a company that provides professional inspection services such as inspection of new cars and whether special-purpose machines function properly. Below, for convenience of explanation, “a company providing a car inspection service” is described as a company providing a used car inspection service, but the embodiments of the present disclosure are not limited thereto. The second server 120 may communicate with the first server 110 through the network 100.

The third server 130 is a server of a financial company. In embodiments of the present disclosure, a financial company may include a company that provides a service that lends money for the purchase of a car, using the car, the object of the transaction, as collateral. Financial companies may include, for example, commercial banks, local banks, savings banks, used car capital companies, etc. In embodiments of the present disclosure, a financial company may include an institution that can inquire credit scores (eg, credit rating, etc.). For example, a financial company may include a credit rating agency (e.g., a credit rating agency) that may provide a credit rating function. The third server 130 may communicate with the first server 110 through the network 100. Below, for convenience of explanation, it is assumed that a financial company is a company that comprehensively performs credit evaluation functions and the screening and approval of collateral loans. However, in some cases, the financial company that provides the credit score and the financial company that provides screening and approval of the loan may be different organizations.

The fourth server 160 is a server of an insurance company. In embodiments of the present disclosure, the insurance company may include a company that provides subscription services for mandatory automobile insurance. Mandatory automobile insurance may include insurance to protect victims by guaranteeing compensation in case a person dies or is injured or property is lost or damaged due to the operation of a automobile. Mandatory automobile insurance is also called liability insurance. The fourth server 160 may communicate with the first server 110 through the network 100.

The fifth server 170 is a server of an organization that provides automobile accident history. Organizations that provide automobile accident history collect automobile accident history and can provide the collected automobile accident history for free or for a small fee. Organizations that provide automobile accident history may include, for example, the Insurance Development Institute. The fifth server 170 may communicate with the first server 110 through the network 100.

The sixth server 180 is a server of an organization that provides automobile registration records. The automobile registration register includes the current owner of the automobile, the automobile registration register, the vehicle name of the automobile, the place of use of the automobile, the motor type of the automobile, the model of the automobile, the purpose of the automobile, the detailed type of the automobile, changes in the structural equipment of the automobile, and the location of the automobile. The inspection validity period, matters related to the seizure of the vehicle or the creation of a mortgage, and other matters that require disclosure may be stated. Organizations that provide automobile registration records may include, for example, the Korea Transportation Safety Authority. The sixth server 180 may communicate with the first server 110 through the network 100.

Meanwhile, in some cases, when the object of a car transaction is a two-wheeled vehicle such as a motorcycle, the sixth server 180 may be replaced by a server of an organization that issues a two-wheeled vehicle ledger.

Meanwhile, in some cases, when the object of automobile transaction is a construction machine that can be used at a construction site, etc., the sixth server 180 may be replaced by a server of an organization that provides a construction machine registration register.

The seventh server 190 is a government office server for car title transfer. Government offices for car title transfers may include, for example, district offices and/or city halls that register cars. The seventh server 190 may communicate with the first server 110 through the network 100.

The user terminal may be provided in the form of a car transferee's terminal 140. For example, the user terminal may include the terminal of a car transferee who wants to purchase a car. In this specification, “car transferee (or user)” means a person who wants to purchase a car using the car brokerage method according to embodiments of the present disclosure. It is sufficient for the “terminal” to be able to connect to the first server 110 through the network 100. For example, a “terminal” may be a mobile electronic device including a mobile phone, tablet, laptop, etc., or a stationary electronic device including a desktop, but its type is not limited to the above.

The automobile transferor's terminal 150 may include the terminal of an automobile transferor who wishes to sell a car. In this specification, a “car transferor” is a person who wishes to sell a car using the car brokerage method according to embodiments of the present disclosure. The car transferor may be the owner of the car that is the subject of the transaction. The description of “terminal” is omitted as it is the same as described above.

In embodiments of the present disclosure, the automobile transferor may be an entity capable of providing personal collateral. For example, a financial company pays a car-secured loan to a car transferee, and the car transferee may provide a personal guarantee for the car-secured loan until the financial company establishes a mortgage on the car. For example, such automobile transferors may include organizations (e.g., corporations, unions, etc.) that own used automobiles. The car transferor may include a trading firm that sells used cars (for example, an automobile trading company). The car transferor may include a used car dealer affiliated with a car trading firm. A car transferor may include a used car dealer (for example, a broker) who is not affiliated with a car trading company and arranges (or brokers) the sale of used cars. The automobile transferor may include an automobile manufacturer (eg, an automobile manufacturer that sells used automobiles that have passed the certification standards preset by the manufacturer). A car transferor may include a dealer affiliated with the car manufacturer (eg, a car dealer selling certified pre-owned cars).

In embodiments of the present disclosure, an automobile transferor may include an individual who owns a used automobile. For example, there may be one person transferring a car, or there may be two or more people. Personal car ownership may include sole ownership by one person or sharing by two or more people.

The first server 110 is connected to the second server 120, third server 130, fourth server 160, fifth server 170, sixth server 180, and seventh server through the network 100. It may communicate directly or indirectly with at least one of the server 190, the car transferee's terminal 140, and the car transferor's terminal 150. For example, the first server 110 may communicate directly with the second server 120 through the network 100. For example, the first server 110 may indirectly communicate with the second server 120 through the network 100 through another server not previously shown. In this specification, the meaning of the term communicate (e.g., transmit data, etc., receive data, etc., inquire, request, etc.) refers to the network 100 between servers (or between servers and terminals). This may include not only cases where communication occurs directly through other servers, but also cases where communication occurs indirectly between servers (or between servers and terminals) via other servers.

Although not shown, the first server 110 may communicate with other servers not shown in FIG. 1 through the network 100. For example, the first server 110 may be connected through the network 100 to a server of an organization that provides the corresponding function in order to check the mandatory automobile insurance subscription history of an individual (eg, a car transferee). For example, the first server 110 is the server and network of the title holder of the escrow account (e.g., a bank) in order to mediate the transfer function between an individual (e.g., a car transferee) and the escrow account holder (e.g., a bank). 100).

Figure 2 is a block diagram of a server 110 that provides a car transaction brokerage method according to embodiments of the present disclosure.

Referring to FIG. 2, the server 110 according to embodiments of the present disclosure may include a communicator 210, a controller 230, and a memory 250.

The communicator 210 may provide a function to connect to the network 100 (see FIG. 1). Through the communicator 210, it is possible to communicate with other servers, other terminals, etc.

The memory 250 may provide a function to store data. The memory 250 according to embodiments of the present disclosure includes a customer identification value 251, customer personal information 252, a lookup table 253 including customer-specific reserved car information and inspection reservation date and time, and an inspection report for each car. (254), automobile transfer certificate (255), and remittance history for each customer (256) can be stored.

The customer identification value 251 is a value given to each customer to identify the customer. For example, the customer identification value 251 may include the name of the customer. As an example, the customer identification value 251 may include an ID set by the customer. For example, the customer identification value 251 may include a string and/or number string randomly assigned in correspondence with the ID set by the customer.

Customer personal information 252 may include customer identification value 251. For example, customer personal information 252 may be obtained at the membership registration stage and stored in memory 250. Customer personal information 252 may be transmitted or received in the form of a code, etc. through procedures such as encryption or pseudonymization for security. In this specification, when customer personal information 252 is communicated, the communicated customer personal information 252 may be used with substantially the same meaning as the customer identification value 251. That is, sending or receiving customer personal information 252 may include sending or receiving customer identification value 251.

The look-up table 253 including the reserved car information and inspection reservation date and time for each customer may be created and stored based on data received from the second server 120 (see FIG. 1).

The inspection report 254 for each vehicle may include data of an inspection report received from the second server 120 (see FIG. 1).

The automobile transfer certificate 255 may include an automobile transfer certificate in a pre-stored format. The car transfer certificate 255 may include a car transfer certificate including the car transferee's electronic signature, the car transferor's electronic signature, the car transferee's personal information, the car transferor's personal information, and the information of the car that is the subject of transfer. You can.

The customer-specific remittance history 256 may include the automobile transferee's acquisition tax remittance history for the transfer of the automobile's title and/or the automobile assignee's incidental cost payment history for the automobile's title transfer, etc.

Memory 250 may include various types of non-volatile storage media that retain stored data even when power is turned off. Non-volatile storage media may include, for example, flash memory, hard disk, etc. Memory 250 may include working memory and/or buffer memory. The memory 250 may include at least one of random access memory (RAM), read only memory (ROM), and a computer-readable medium.

The controller 230 may be configured to control the communicator 210 and memory 250.

Controller 230 may include a processor. One or more modules may be loaded into the controller 230 by the processor. The processor can execute loaded modules. The processor may be either a general-purpose processor or a dedicated processor.

Referring to FIG. 2, a login module 231, a membership registration module 232, a module 233 for transmitting and receiving personal information and/or vehicle information, a module 234 for querying loan products, and whether or not to subscribe to mandatory automobile insurance. module for querying (235), module for requesting input of information for car title transfer (236), module for requesting payment of costs (237), module for mediating remittance (238), application for car title transfer. Module 239, module 241 for generating a vehicle transfer certificate, module 242 for providing notification according to the inspection reservation date and time, module 243 for checking the accident history of the vehicle, module for requesting inspection of vehicle information (244), a module (245) for checking car title loan products, a module (246) for checking remittance history, etc. may be loaded into the controller 230 and executed. Codes and/or instructions for executing the modules (eg, login module 231, etc.) may be stored in the memory 250.

The controller 230 may further include an interface for interfacing with the communicator 210 and the memory 250.

In this specification, the description that the controller 230 can transmit data can be understood to mean that the controller 230 can control the communicator 210 to transmit data. Additionally, the description that the controller 230 can receive data may be understood to mean that the controller 230 can control the communicator 210 to receive data. In addition, operations such as when the controller 230 requests an operation or the controller 230 searches for certain data may also be understood as operations performed by the controller 230 controlling the communicator 210.

Figure 3 is a flowchart showing the steps of providing a login page and applying for a car transaction brokerage service in the car transaction brokerage method according to embodiments of the present disclosure.

Referring to FIG. 3, embodiments of the present disclosure include a step 310 of asking for membership, a step 330 of providing an application page to the car transferee's terminal, and a step 340 of asking whether to consent to providing information. can do.

In step 310 of asking for membership, the first server 110 (see FIG. 1) may transmit a login page to the car transferee's terminal to display a login page.

In some cases, in the step 310 of asking for membership, the login page is not displayed on the car transferee's terminal, but the car transferee's personal information is selected to be loaded from another server to the first server (110; see Figure 1). Pages may be provided. In other words, rather than inducing login through membership registration on the car transferee's terminal, the first server 110 (see Figure 1) provides information to the car transferee's terminal so that it can receive the car transferee's personal information from another server. A page may be provided to select whether to agree to the provision.

If it is selected that you are not a member on the car transferee's terminal (for example, when a request to move to the membership registration page on the car transferee's terminal is selected), the page 320 for proceeding with membership registration is displayed on the car transferee's terminal. It can be displayed in .

In step 330 of providing an application page to the car transferee's terminal, a page for applying for a used car transaction service according to embodiments of the present disclosure may be provided to the car transferee's terminal.

In the step 340 of asking for consent to provide information, a page asking for consent to provide information may be displayed on the car transferee's terminal. Here, consent to provision of information refers to providing at least part of the vehicle transferee's identification number and personal information to the server of the company providing the vehicle inspection service (e.g., the second server 120; see FIG. 1). May include consent or not.

When the result of agreeing to provide information is input from the car transferee's terminal, a step 350 of transmitting the car transferee's customer identification value to the server of the company providing the car inspection service may be performed.

Step 360 may be performed to transmit the Internet address of the server of the company providing the automobile inspection service to the automobile transferee's terminal.

Figure 4 is a diagram showing the data flow in step 350 of transmitting the customer identification value of the car transferee to the server of a company providing car inspection services.

Referring to FIG. 4, the customer identification value of the car transferee is provided from the first server 110 to the second server 120. The first server 110 may receive a response indicating that the customer identification value of the car transferee has been received from the second server 120.

Figure 5A is an example of an overall flow chart of a car transaction brokerage method according to embodiments of the present disclosure.

A step 510 of receiving information on the car inspection date and time of the car transferee may be performed. “Car transferee’s car inspection date and time information” may be received from the server of a company that provides car inspection services. The received “car transferee's car inspection date and time information” includes, for example, the car transferee's customer identification value, the date the car transferee scheduled the inspection, the time the car transferee scheduled the inspection, the location where the car transferee scheduled the inspection, Information on the car reserved by the car transferee (for example, the car for which the car transferor reserved inspection) (for example, the number of the car for which the car transferor reserved inspection), the amount of services paid by the car transferee, etc. It can be included. In this specification, the car that the car transferee wishes to transfer is “the car reserved by the car transferee,” “the car selected by the car transferee,” “the car selected by the user,” or “the car for which the car transferee has reserved inspection,” etc. It may be referred to as .

For example, a company that provides car inspection services may be a company that provides a service that matches car transferees with car mechanics. For example, a company providing a car inspection service may generate car information and transmit the generated car information to the first server 110 (see FIG. 1). For example, for a car for which a car transferee has reserved an inspection, a mechanic can be assigned to perform maintenance, and car information according to the maintenance results can be transmitted.

Vehicle information may include an inspection report. For example, according to the results of car maintenance by a mechanic (eg, a mechanic matched with the user by the server of a company providing car inspection services), an inspection report for the car may be generated. The inspection report covers the presence or absence of defects in the car (e.g., major defects, whether the car is flooded, etc.) that are not disclosed (for example, there is no insurance processing history, accident history, etc.), and the driving system of the car's engine, transmission, etc. It may include data such as whether there is a problem with the part, the status of the car's consumable parts (e.g., remaining life considering the replacement cycle of the consumable part, etc.), and whether there is a problem with the electronic parts included in the car. The maintenance details included in the inspection report are not limited to those listed above, and may vary depending on the year of the vehicle, the price of the inspection service, etc.

Car information may include the user's intention to purchase a car. For example, if it is confirmed that the car has a major defect as a result of inspecting the car, the user can withdraw (or cancel) the purchase of the car. In this case, the user's intention to purchase a car may be written as “very low intention to purchase,” “reason: confirmed major defect (flooding),” etc. For example, in cases where the car inspection was not actually performed (e.g., the user made a reservation for the car inspection, but did not show up at the agreed upon location for the car inspection, etc.), the degree of the user's intention to purchase the car is determined by the user's intention to purchase the car. It can be written as “low intention to purchase”, “reason: failure to appear at car inspection location”, etc. If necessary, if the user's purchase intention is determined to be low (e.g., "very low", etc.), the first server (110: see FIG. 1) does not receive separate maintenance results and You may only receive information on the purchase intention of a user whose purchase intention is low (or very low).

In embodiments of the present disclosure, when the received data of the user's intention to purchase a car is low or very low, data for canceling (or withdrawing) the user's used car mortgage loan application is sent to the third server 130 (see FIG. 1). ) can be sent to.

Embodiments of the present disclosure, when the received data of the user's intention to purchase a car is low or very low, data for canceling (or withdrawing) the user's application for a mandatory car insurance loan is sent to the fourth server 160 (see FIG. 1). ) can be sent to.

Meanwhile, “car information” in the detailed description and drawings of the invention of this specification may be written in ordinal form, such as first car information or second car information, in the claims of this specification.

Step 520 of selecting whether to take out a car collateral loan may be performed. The first server 110 (see FIG. 1) transmits data to the car transferee's terminal and determines whether to select a car collateral loan (also simply referred to herein as “mortgage loan” or “loan”) to the car transferee's terminal. can be displayed.

When the first server 110 (see FIG. 1) receives a response selecting a car secured loan from the car transferee's terminal, step 530 of generating a list of car secured loan products may be performed.

In step 530 of generating a list of car mortgage loan products, a user interface that allows access to content provided by the financial company may be displayed on the car transferee's terminal. The car transferee can access the content over the network by selecting the user interface displayed on the terminal. Content provided by a financial company may include, for example, the homepage of the financial company's server, a page for applying for a selected car mortgage loan, a page showing the interest rates of car mortgage loan products provided by the financial company, etc. Not limited. Access methods may include, for example, banners, advertising text, API (Application Programming Interface), promotional links, URL (Uniform Resource Locator; web address), but are not limited thereto.

In some cases, in step 530 of generating a list of car title loan products, the first server 110 (see FIG. 1) may query the list of car title loan products. The first server 110 (see FIG. 1) may transmit data to the car transferee's terminal to display a list of searched car title loan products on the car transferee's terminal.

If the loan product that can be provided to the car transferee is not searched, the first server 110 (see FIG. 1) displays the message “There are no loan products that can be provided” on the car transferee's terminal. Data can be transmitted to the terminal. Alternatively, if the car title loan product that can be provided to the car transferee is not searched, the first server 110 (see Figure 1) provides a "Learn about credit loans" page and/or a credit loan to the car transferee's terminal. Data can be transmitted to the automobile transferee's terminal to display accessible access means (for example, banner advertisements, etc.) to the server of the providing financial company.

A step 535 of matching the car transferee and the financial company may be performed.

In step 535 of matching the car transferee and the financial company, the car transferee and the financial company may be matched so that the car transferee applies for a car mortgage loan through the financial company's server. For example, when an access means connected to a financial company's server is displayed on the car transferee's terminal, the first server 110 (see Figure 1) determines whether the car transferee applies for a car mortgage loan from the financial company's server. You can receive it.

In step 535 of matching the car transferee and the financial company, the car transferee and the financial company can be matched by transmitting the code of the loan product selected by the car transferee to the server of the financial company providing the loan product. For example, when a list of car mortgage loan products searched from the server of one or more financial companies is displayed on the terminal of the car transferee, the first server 110 (see FIG. 1) sends a message to the car transferee on the server of the financial company. The code of the loan product selected can be transmitted. The first server 110 (see FIG. 1), for example, provides financial information such as the customer identification value of the car transferee, the code of the loan product selected by the car transferee, the personal information of the car transferee, and the information of the car reserved by the car transferee. It can be sent to the company's server.

A step 540 may be performed to check whether the car transferee has subscribed to mandatory car insurance. For example, the first server 110 (see FIG. 1) checks whether the transferee of a car has subscribed to mandatory car insurance by querying the server of an organization that provides mandatory car insurance subscription information. You can check it.

Step 550 of receiving an inspection report may be performed. The first server 110 (see FIG. 1) may receive an inspection report from a server of a company that provides automobile inspection services. The received inspection report may include customer identification values, inspection result information of the vehicle for which the vehicle transferee has reserved inspection, etc. The inspection report may include information on whether the car transferee intends to purchase the car (or the degree of intention to purchase the car). Whether or not the car transferee intends to purchase the car (or the degree of intention to purchase the car) may be evaluated by a mechanic performing a car inspection, but is not limited to this.

If it is determined in step 550 of receiving the inspection report that the car transferee has no intention to purchase, embodiments of the present disclosure may be ended without performing at least one of the above steps and the following steps.

The first server 110 (see FIG. 1) may transmit the inspection report (or at least some of the information included in the inspection report) received in step 550 of receiving the inspection report to the server of the financial company. . Before making a final decision on whether to issue a car-secured loan, a financial company can use the car transferee's intention to purchase the car and the objective condition of the car received through the financial company's server as auxiliary indicators.

A step 565 of inducing subscription to mandatory automobile insurance may be performed depending on the inquired status of mandatory automobile insurance subscription (560). More specifically, if it is determined that the car transferee is not subscribed to mandatory car insurance as a result of the searched mandatory car insurance subscription (560), a step (565) of inducing the car transferee to subscribe to mandatory car insurance is performed. It can be done.

According to embodiments of the present disclosure, companies providing automobile inspection services have an advantage in attracting customers.

According to embodiments of the present disclosure, a car transferee can check the condition of the car with the help of a car inspection expert and closely understand the condition of the car he or she wishes to purchase.

According to embodiments of the present disclosure, a financial company may sell a loan product to an automobile transferee.

According to embodiments of the present disclosure, an insurance company may have the opportunity to induce a car transferee to subscribe to a mandatory car insurance product.

According to embodiments of the present disclosure, a car transferee can compare information on loan products provided from servers of a plurality of financial companies. In addition, the car transferee can access the process of inspecting the car for purchase, introduction of a loan for car purchase, introduction of insurance for mandatory car insurance, etc. through the car transaction brokerage service according to the embodiments of the present disclosure. You can. Accordingly, car transferees can receive a so-called one-stop service that carries out car purchase from start to finish using one platform.

According to embodiments of the present disclosure, a company providing an automobile transaction brokerage service may provide an advantage in terms of attracting customers to companies providing automobile transaction services, financial companies, and insurance companies.

In addition, companies that provide car transaction brokerage services can help car transferees accurately learn about the condition of the car they are purchasing and help them obtain a car purchase loan during the process of purchasing the car.

In the process described above, a company providing automobile transaction brokerage services can earn operating profits.

According to embodiments of the present disclosure, by displaying a list of loan products received from a financial company's server on the car transferee's terminal, the car transferee can easily check the loan products available to the car transferee.

Embodiments of the present disclosure may transmit a code corresponding to a loan product selected from the automobile transferee's terminal to the financial company's server. Meanwhile, when a car transferee purchases a car from a car dealer, etc., a financial company can establish a mortgage on the car sold by the car dealer to the car transferee.

The steps of FIG. 5A may be performed when the car transferee purchases the car from an organization (eg, a car dealer). However, embodiments of the present disclosure can also be applied when a car transferee purchases a car from an individual.

FIG. 5B is an example of a flowchart further including embodiments of a method for brokering a car transaction that may be performed after the steps of FIG. 5A.

The steps in FIG. 5B can be further performed when the car transferee purchases the car from an individual.

Description of the same components (or steps) as described above in FIG. 5A will be omitted, and descriptions of additional components (or steps) in the embodiment shown in FIG. 5B are as follows.

Referring to FIG. 5B, step 570 of generating a vehicle transfer certificate online may be performed. The first server 110 (see FIG. 1) may generate a vehicle transfer certificate. Here, the generated car transfer certificate is a car transfer certificate in a preset format, including personal information of the car transferee, personal information of the car transferor, electronic signature of the car transferee, electronic signature of the car transferor, and information on the car that is the subject of the transaction. It may include a vehicle transfer certificate (e.g., a completed vehicle transfer certificate) including the like.

A step 575 of storing the generated automobile transfer certificate may be performed. The first server 110 (see FIG. 1) may store the generated automobile transfer certificate. The generated automobile transfer certificate may, for example, be stored in the memory 250 (see FIG. 2) described above.

A step 580 of requesting payment of a fee for transferring the title of a car may be performed. “Costs for transferring the title of a car” may include, for example, acquisition tax. In some cases, the cost of transferring a car's title may include registration tax. The cost of transferring a car's title may include incidental costs. Incidental costs may include, for example, stamp duty.

In the step 580 of requesting payment of the cost for transferring the car's title, payment of the car's title transfer fee is made through the car transferee's terminal so that the fee for the car transfer can be paid through the car transferee's terminal. The remittance function for can be activated. The first server 110 (see FIG. 1) may activate a remittance function for payment of the car title transfer fee on the car transferee's terminal. By using the remittance function activated at this stage, the cost for transferring the title of the car can be paid from the car transferee's terminal to the account of a government office (eg, district office, city hall, etc.).

In step 580 of requesting payment of the fee for transferring the car's title, the first server 110 (see FIG. 1) may transmit the payment history of the fee for the car's title transfer to the financial company's server. . When determining whether a car transferee has applied for a car collateral loan to purchase a car, a financial company can refer to the payment history of the acquisition tax received.

A step 590 of applying for title transfer of a car may be performed. The first server 110 (see FIG. 1) may transmit data for applying for a car title transfer to a server of an organization that provides a car title transfer function.

In the step 590 of applying for a title transfer of a car, data of stored car transfer certificate data and materials proving the payment history of fees may be transmitted. For example, the first server 110 (see FIG. 1) stores the car transfer certificate data and the car transferee's remittance history data stored in the memory 250 (see FIG. 2) to the seventh server 190 (see FIG. 1). ) can be sent to.

Embodiments of the present disclosure may further include activating a remittance function on the car transferee's terminal so that the car transferee can remit the car purchase cost.

For example, in embodiments of the present disclosure, after an application for transfer of a car's title is completed, the first server 110 (see FIG. 1) may transmit data for activating a remittance function to the car transferee's terminal. By a remittance function activated on the car transferee's terminal, the car transferee can deposit the car purchase cost into a preset escrow account. The car transferee's terminal may transmit data requesting money transfer to the escrow account to the first server 110 (see FIG. 1).

Here, escrow refers to a sales protection service that relays transactions between buyers and sellers who cannot trust each other to ensure smooth transactions.

Embodiments of the present disclosure may transmit a code corresponding to the loan product selected on the automobile transferee's terminal to the financial company's server, and transmit whether the automobile transferee has paid the fee for title transfer to the financial company's server. there is. Accordingly, even if the car transferee applies for a loan, the financial company must check whether the car transferee is actually willing to transfer the car (i.e., is willing to misappropriate the secured loan) before executing a loan according to the selected loan product. can be judged indirectly.

In such cases, the car transferee can apply for a car title loan from a financial company if the car is purchased directly from the car transferor, who is an individual.

Additionally, in this case, when the car transferee purchases the car directly from the car transferor who is an individual, an application for transfer of the car's title can be performed through embodiments of the present disclosure. Accordingly, car transferees can further benefit from the so-called one-stop service using one platform when purchasing a car.

Figure 6a is a flowchart illustrating in more detail the step 530 of generating a list of car loan products.

The step 530 of generating a list of car collateral loan products may include a step 610 of requesting a loan interest rate and limit inquiry from the server of one or more financial companies. In this step, the first server 110 (see FIG. 1) stores the customer identification value of the car transferee, the personal information of the car transferee stored in the server of the financial company, the information of the car reserved by the stored car transferee, etc., to the server of the financial company. It can be sent to .

The step 530 of generating a list of car title loan products may include a step 620 of receiving information on the searched loan products. The first server 110 (see FIG. 1) may receive loan product information including the loan product code, loan product interest rate information, and loan product limit information from the financial company's server.

Step 530 of generating a list of car title loan products may include step 630 of creating a lookup table including the interest rate and limit of the searched car title loan product. The first server 110 (see FIG. 1) may generate a lookup table including the interest rate and limit of the searched car title loan product. The generated lookup table may include information on loan products received from the server of one or more financial companies.

In some cases, if the loan product that can be provided to the car transferee is not searched (for example, if there is no loan product that can be provided to the car transferee), the lookup table returns a default value (for example, Null). value) may be included.

The step 530 of generating a list of car secured loan products may include a step 640 of displaying the searched car secured loan interest rate and limit on the car transferee's terminal. The first server 110 (see FIG. 1) may transmit data to the car transferee's terminal so that the searched car loan interest rate and limit can be displayed on the car transferee's terminal.

Accordingly, interest rate and limit information on car loan products viewed from one or more financial companies may be displayed on the car transferee's terminal.

FIG. 6B is a flowchart illustrating a case in which the step of generating a list of automobile secured loan products (530) includes an accident history query step (650) of a car and a car information query step (660).

The step 530 of generating a list of car title loan products may include a step 650 of checking the accident history of the reserved car. The first server 110 (see FIG. 1) transmits information about the car reserved by the car transferee (e.g., car number, car owner name, etc.) to the server of an organization that provides car accident history. You can. The first server 110 (see FIG. 1) may receive data including the accident history of the searched car from a server of an organization that provides the accident history of the car.

The step 530 of generating a list of car title loan products may include a step 660 of querying car information of the reserved car. The vehicle information to be searched may include a vehicle registration ledger. The first server 110 (see FIG. 1) may receive information including the owner of the car reserved by the car transferee, the year of the car, whether a mortgage is placed on the car, and whether the car is seized.

Car information may include one or more of the car's accident history, car's owner change history, car's insurance history, and car's repair history.

In this specification, “car information” including the car registration register, car accident history, car owner change history, etc. described in the detailed description and drawings of the invention is referred to as first car information or second car information in the scope of the patent claims of this specification. It can be referred to as an ordinal expression, such as:

The first server 110 (see FIG. 1) transmits data to the car transferee's terminal so that the inquired car mortgage loan interest rate and limit, as well as the accident history of the reserved car, etc. can be displayed on the car transferee's terminal. You can.

Meanwhile, the step 650 of checking the accident history of the reserved car and the step 660 of checking the car information of the reserved car are performed within the step 530 of generating a list of car mortgage loan products. Although described above, the embodiments of the present disclosure are not limited thereto.

For example, only one of the step 650 of checking the accident history of the reserved car and the step 660 of checking the car information of the reserved car may be performed.

For example, at least one of the steps of checking the accident history of the reserved car (650) and the step of checking the car information of the reserved car (660) is separate from the step of generating a list of car mortgage loan products (530). It may be performed over a period of time, and the embodiments may be freely selected without departing from the spirit of the present invention.

Figure 7 is another flowchart illustrating in more detail the step 535 of generating a list of automobile mortgage loan products.

Referring to FIG. 7 , step 535 of generating a list of car title loan products may include step 710 of receiving the code of the selected car title loan product from the terminal of the car transferee. The first server 110 (see FIG. 1) may receive the code of the selected car title loan product from the car transferee's terminal.

The step 535 of generating a list of car-secured loan products may include a step 720 of brokering a loan application between a financial company and a car transferee. The first server 110 (see FIG. 1) may transmit information for applying for an automobile mortgage loan to a server of a financial company.

Information for applying for a car secured loan may include, for example, a customer identification value of the car transferee, personal information of the car transferee, the number of the car that is the subject of the transaction, etc.

The step 535 of generating a list of car title loan products may further include a step 730 of receiving a result of an application for a car title loan. The first server 110 (see FIG. 1) may receive a result from the financial company's server as to whether the car title loan application applied by the car transferee has been received (for example, not rejected). .

Figure 8 is a flowchart further illustrating steps that can be additionally performed when a car transferee applies for a car collateral loan from a financial company.

When the car transferee applies for a car collateral loan, a step 810 of transmitting the received inspection report to the financial company's server may be further performed. The first server 110 (see FIG. 1) may transmit the received inspection report (or at least some of the information included in the received inspection report) to the financial company's server.

When the car transferee applies for a car collateral loan, a step 820 of transmitting payment proof data such as acquisition tax and title transfer application data to the financial company's server may be further performed. The first server 110 (see FIG. 1) may transmit data proving payment of acquisition tax, etc. by the transferee of the car and data on the transfer application for title of the transferee of the car to the server of the financial company.

Accordingly, when determining that a car transferee has applied for a car collateral loan to purchase a car, the financial company uses the car inspection report received through the financial company's server and the car transferee's acquisition tax payment proof data as auxiliary information. It can be used as an indicator.

Figure 9 is a flowchart showing in more detail the step 565 of inducing the car transferee to subscribe to mandatory car insurance.

Referring to FIG. 9, the step of inducing the car transferee to sign up for mandatory car insurance (565) involves displaying an advertisement for mandatory car insurance that includes a link to the insurance company's server on the car transferee's terminal (910). may include. The first server 110 (see FIG. 1) may transmit data to the car transferee's terminal to display an advertisement for mandatory car insurance including a link to the insurance company's server.

The step 565 of inducing the car transferee to subscribe to mandatory car insurance may include a step 920 of receiving the car transferee's mandatory car insurance subscription information from the insurance company's server. The first server 110 (see FIG. 1) may receive mandatory automobile insurance subscription information of the automobile transferee from the insurance company's server.

The first server 110 (see FIG. 1) may display a user interface that allows access to content provided by the insurance company on the automobile transferee's terminal. The car transferee can access the content over the network by selecting the user interface displayed on the terminal. Content provided by the insurance company includes, for example, the homepage of the insurance company's server, a web page for applying for the mandatory automobile insurance product provided by the insurance company, and the quotation information for the mandatory automobile insurance product provided by the insurance company. It may include, but is not limited to, web pages, etc. Access methods may include, but are not limited to, the aforementioned banners, advertising text, API, promotional links, URLs, etc. For example, the first server 110 (see FIG. 1) may induce the car transferee to subscribe to mandatory car insurance by transmitting data to display a banner advertisement on the car transferee's terminal.

Figure 10 is another flowchart showing in more detail the step 565 of inducing the car transferee to subscribe to mandatory car insurance.

The step of inducing the car transferee to subscribe to mandatory car insurance (565) may include the step of inquiring about mandatory car insurance products (1010). The first server 110 (see FIG. 1) may query mandatory automobile insurance products on the server of one or more insurance companies. The first server 110 (see FIG. 1) may receive mandatory automobile insurance data including quote information from the server of one or more insurance companies that have requested an inquiry.

The step 565 of inducing the car transferee to sign up for mandatory car insurance is a step 1020 of generating a lookup table containing insurance quote information (e.g., coverage area, monthly payment amount, etc.) of the searched car mandatory insurance product. may include. The first server 110 (see FIG. 1) may generate a lookup table based on insurance quote information of the searched mandatory automobile insurance product.

The step of inducing the car transferee to subscribe to mandatory car insurance (565) may include the step of displaying a list of insurance products on the car transferee's terminal (1030). The first server 110 (see FIG. 1) may transmit list data of searched insurance products to the car transferee's terminal in order to display the list of searched insurance products on the car transferee's terminal. The first server 110 (see FIG. 1), for example, may transmit data to the car transferee's terminal to display at least part of the information included in the lookup table on the car transferee's terminal based on the generated lookup table. You can. On the car transferee's terminal, a list of insurance products including quote information may be displayed.

The step of inducing the car transferee to sign up for mandatory car insurance (565) may include the step of receiving an insurance code value from the car transferee's terminal (1040). The first server 110 (see FIG. 1) may receive a code corresponding to one insurance product selected on the automobile transferee's terminal from the list of insurance products displayed on the automobile transferee's terminal.

The step of inducing the car transferee to subscribe to mandatory car insurance (565) may include a step (1050) of brokering the application for mandatory car insurance with the car mandatory insurance product selected by the car transferee. The first server 110 (see FIG. 1) may transmit the insurance code corresponding to the insurance product selected by the automobile transferee's terminal to the server of the insurance company providing the selected insurance product. In some cases, the first server 110 (see FIG. 1) may transmit the car transferee's customer identification value, the car transferee's personal information, etc. to the insurance company's server.

Figure 11 is a flow chart illustrating in more detail the step 570 of generating an automobile transfer certificate online.

The step of generating a car transfer certificate (570) may include a step (1110) of loading a car transfer certificate in a preset format. An automobile transfer certificate in a preset format may be stored in the memory 250 (see FIG. 2) of the first server 110 (see FIG. 1). An example of a car transfer certificate in a pre-established format is a car transfer certificate prepared when a car is directly traded between the transferor and transferee (for example, a car transfer certificate in the form of Appendix 15 stipulated in the car registration rules of the Republic of Korea, etc.) ) can refer to.

The step 570 of generating a car transfer certificate may include a step 1120 of entering the car transferee's personal information and information about the car reserved by the car transferee in the retrieved car transfer certificate.

For example, the first server 110 (see FIG. 1) may perform the above steps by referring to the personal information of the car transferee stored in the memory 250 (see Figure 2) and the information of the car reserved by the car transferee. You can.

For example, the first server 110 (see FIG. 1) may transmit data to the car transferee's terminal to input the car transferee's personal information and information on the car reserved by the car transferee. The first server 110 (see FIG. 1) may enter the car transferee's personal information and information about the car reserved by the car transferee in the car transfer certificate based on data received from the car transferee's terminal.

Step 570 of generating a car transfer certificate may include a step 1130 of requesting the car transferee to input an electronic signature on the car transfer certificate. In order for the car transferee to enter an electronic signature on the car transfer certificate, the first server 110 (see FIG. 1) may transmit data requesting an electronic signature to the car transferee's terminal. The first server 110 (see FIG. 1) may receive data of an electronically signed automobile transfer certificate from the automobile transferee's terminal.

Step 570 of generating a car transfer certificate may include a step 1140 of requesting input of the car transferor's contact information into the car transferee's terminal. In order for the car transferee to enter the car transferor's contact information, the first server 110 (see FIG. 1) may transmit data requesting input of the car transferor's contact information to the car transferee's terminal. The first server 110 (see FIG. 1) may receive contact data of the car transferor from the car transferee's terminal.

The step 570 of generating a car transfer certificate may include a step 1150 of requesting the car transferor's terminal to input personal information and an electronic signature in the car transfer certificate. In order for the car transferor to enter personal information and enter an electronic signature, the first server 110 (see FIG. 1) inputs data requesting entry of the car transferor's personal information and the car transferor's electronic signature into the car transferor's terminal. You can send data requesting . The first server 110 (see FIG. 1) may receive a car transfer certificate including the car transferor's personal information and the car transferor's electronic signature from the car transferor's terminal.

Figure 12 is a flow chart illustrating in more detail the step 580 of requesting payment of a fee for transferring a car title.

The step 580 of requesting payment of the cost for transferring the car title may include the step 1210 of sending a notification requesting payment of the acquisition tax and incidental costs to the terminal of the car transferee. The first server 110 (see FIG. 1) may transmit data to the automobile transferee's terminal in order to display a notification requesting payment of acquisition tax and incidental expenses on the automobile transferee's terminal.

The step 580 of requesting payment of a fee for transferring a car title may include a step 1220 of activating a remittance function for payment of acquisition tax and incidental costs of the car transferee. The first server 110 (see FIG. 1) may transmit data to the automobile transferee's terminal so that a function for remitting acquisition tax is activated in the automobile transferee's terminal. The first server 110 (see FIG. 1) may transmit data to the car transferee's terminal so that a function for remitting incidental expenses is activated in the car transferee's terminal.

For example, the first server 110 (see FIG. 1) may transmit data to the automobile transferee's terminal so that acquisition tax and/or incidental expenses can be remitted from an account that the automobile transferee has previously set as a withdrawal account.

For example, the first server 110 (see FIG. 1) transfers acquisition tax and/or to the account of a government office (e.g., district office or city hall, etc.) related to the vehicle transferee's residence based on the pre-stored personal information of the transferee of the car. Alternatively, data can be transmitted to the car transferee's terminal so that incidental costs can be paid.

The step 580 of requesting payment of a fee for transferring a car title may include a step 1230 of checking the transfer history of the car transferee. The first server 110 (see FIG. 1) may check the payment history of acquisition tax and incidental expenses of the automobile transferee based on the stored customer identification value of the automobile transferee and the stored remittance history of the automobile transferee.

In some cases, the first server 110 (see FIG. 1) may transmit the remittance history of the confirmed automobile transferee's acquisition tax and incidental expenses to the server of the financial company to which the automobile transferee applied for a car collateral loan.

Figure 13 is a diagram showing the data flow that occurs in step 510 of receiving information on the vehicle inspection date and time of the vehicle transferee.

Referring to FIG. 13, in step 510 of receiving the car transferee's car inspection date and time information, the first server 110 may receive the car transferee's car inspection date and time information from the second server 120. The first server 110 may transmit result response data to the second server 120 indicating that the data was received without error.

Figure 13 is a diagram showing the data flow that occurs in step 510 of receiving information on the vehicle inspection date and time of the vehicle transferee.

Referring to FIG. 13, in step 510 of receiving the car transferee's car inspection date and time information, the first server 110 may receive the car transferee's car inspection date and time information from the second server 120. The first server 110 may transmit result response data to the second server 120 indicating that the data was received without error.

Figure 14 is a diagram showing another data flow that occurs in step 510 of receiving information on the vehicle inspection date and time of the vehicle transferee.

Referring to FIG. 14, the first server 110 may receive information on the mechanic's automobile inspection date and time from the second server 120. Here, “mechanic” may mean a mechanic who actually performs inspection of the car reserved by the car transferee. The first server 110 receives the mechanic's car inspection date and time information from the second server 120, so that it can know which mechanic actually performs the maintenance on the reserved date. This allows supervision to ensure that the vehicle inspection service is performed closely. The first server 110 may transmit result response data to the second server 120 indicating that the data was received without error.

FIGS. 15A to 15D are diagrams showing the data flow in the step 530 of generating a list of car loan products (see FIGS. 6A and 6B).

Figure 15a shows the data flow of step 610 of requesting a loan interest rate and limit inquiry from the server of one or more financial companies. Referring to FIG. 15A, the first server 110 sends data of customer personal information (for example, personal information of the car transferee, etc.) and information of the car reserved by the car transferee to the third server 130. Can be sent. The first server 110 may receive reception result data indicating that data was received without error from the third server 130.

Figure 15b shows the data flow of step 620 of receiving information on the searched loan product. Referring to FIG. 15B, the first server 110 may receive result data including the car transferee's preliminary examination result, expected loan interest rate, expected loan limit, etc. from the third server 130. The first server 110 may transmit reception result data to the third server 130 indicating that the data was received without error.

Figure 15c shows the data flow of step 650 of checking the accident history of the reserved car. Referring to FIG. 15C, the first server 110 may request an accident history inquiry from the fifth server 170. The first server 110 may transmit data including the license plate number of a car requesting an accident history inquiry, information on the car owner, etc. to the fifth server 170. The first server 110 may receive data including accident history information of a car for which an inquiry has been requested from the fifth server 170.

Figure 15d shows the data flow of step 660 of searching car information of a reserved car. Referring to FIG. 15D, the first server 110 may request vehicle information inquiry from the sixth server 180. The first server 110 may transmit data including the car number, car owner information, etc. requesting car information inquiry to the sixth server 180. The first server 110 may receive car information (eg, car registration ledger, etc.) data of a car for which an inquiry has been requested from the sixth server 180.

Figures 16A to 16C are diagrams showing the data flow that occurs in the step 535 of matching a car transferee and a financial company (see Figure 7).

Figure 16a shows the data flow of step 710 of receiving the code of the loan product selected by the automobile transferee. The first server 110 receives customer identification value data and loan product code data from the automobile transferee's terminal 140. The code of the loan product received from the car transferee's terminal 140 may be the code of the loan product corresponding to the loan product selected on the car transferee's terminal. The first server 110 may transmit result response data to the automobile transferee's terminal 140 indicating that the data was received without error.

Figure 16b shows the data flow of step 720 of brokering a loan application of an automobile transferee to a financial company. The first server 110 provides customer identification value data, customer information (e.g., personal information of the car transferee, etc.) data, and a code of the loan product (e.g., loan selected by the car transferee) to the third server 130. Code of the loan product corresponding to the product) data can be transmitted. The first server 110 may receive response data indicating that data was received without error from the third server 130.

Figure 16c shows the data flow of step 730 of receiving the car title loan application result. The first server 110 may receive data about the results of the car transferee's car loan application from the third server 130. Data on the result of the car transferee's car title loan application may include, for example, information that the car title loan application was successfully received rather than being rejected.

In some cases, the car transferee applies for a car title loan, but the car transferee may cancel the application for the car title loan at some point before the finance company executes the car title loan. In this case, the third server 130 may transmit data including information that the car transferee has canceled the car mortgage loan application to the first server 110.

FIG. 17 is a diagram showing the data flow that occurs in the step 550 of receiving an inspection report (see FIG. 5).

The first server 110 may receive data of an inspection report including a customer identification value from the second server 120. The first server 110 may transmit result response data to the second server 120 indicating that the data was received without error. The description of the inspection report has been described above, so it is omitted.

Figures 18A to 18D are diagrams showing the data flow that occurs in the step 565 of inducing the car transferee to subscribe to mandatory car insurance (see Figure 10).

Figure 18a shows the data flow of step 1010 of searching for mandatory automobile insurance products. The first server 110 may request the fourth server 160 to inquire about mandatory automobile insurance products. The first server 110 may transmit to the fourth server 160 the customer identification value of the car transferee, the car transferee's personal information, and information on the car reserved by the car transferee (for example, car number, etc.). The first server 110 may receive data on a mandatory automobile insurance product including quote information from the fourth server 160.

The first server 110 may request an inquiry of mandatory automobile insurance products from the servers of two or more insurance companies (for example, the fourth server 160 of each of the two or more insurance companies).

Figure 18b shows the data flow of step 1030 of displaying a list of mandatory automobile insurance products on the automobile transferee's terminal. The first server 110 may transmit data of a list including information on mandatory automobile insurance products and data including codes corresponding to the mandatory insurance products to the terminal 140 of the automobile transferee. The first server 110 may receive data indicating that the data was received without error from the car transferee's terminal 140.

Figure 18c shows the data flow of step 1040 of receiving the insurance code value at the automobile transferee's terminal. The first server 110 may receive code data corresponding to the selected insurance product from the automobile transferee's terminal 140. The first server 110 may transmit result response data to the automobile transferee's terminal 140 indicating that the data was received without error.

Figure 18d shows the data flow of the step 1050 of brokering an application for mandatory automobile insurance with the automobile mandatory insurance product selected by the automobile transferee. The first server 110 may transmit the customer's personal information data and code data corresponding to the selected insurance product to the fourth server 160. The first server 110 may receive data from the fourth server 160 indicating that the data was received without error.

FIGS. 19A to 19C are diagrams showing the data flow that occurs in the step 570 of generating a car transfer certificate online (see FIGS. 5B and 11).

Figure 19a shows the data flow of step 1130 of requesting input of an electronic signature on a car transfer certificate to the car transferee's terminal. The first server 110 may transmit data requesting an electronic signature on the automobile transfer certificate to the automobile transferee's terminal 140. The first server 110 may receive data of an electronically signed automobile transfer certificate from the terminal 140 of the automobile transferee.

Figure 19b shows the data flow of step 1140 of requesting input of the car transferor's contact information to the car transferee's terminal. The first server 110 may transmit data requesting input of the car transferor's contact information to the car transferee's terminal 140. The first server 110 may receive contact data of the car transferor from the car transferee's terminal 140. The first server 110 may store the received contact data of the car transferor in the memory 250 (see FIG. 2).

Figure 19c shows the data flow of step 1150 of requesting the automobile transferor's terminal to enter personal information and electronic signature on the automobile transfer certificate. The first server 110 may transmit data to the car transferor's terminal 150 requesting the car transferor's personal information to be entered in the car transfer certificate and the car transferor's electronic signature. The first server 110 may receive car transfer certificate data including the car transferor's personal information and the car transferor's electronic signature from the car transferor's terminal 150.

Figures 20a and 20b are diagrams showing the data flow that occurs in the step 580 of requesting payment of the cost for transferring the title of a car (see Figures 5b and 12).

Figure 20a shows the data flow of step 1210 of sending a notification requesting payment of acquisition tax and incidental costs to the terminal of the transferee of the car. The first server 110 transmits data requesting to display a message requesting payment of acquisition tax and incidental costs to the terminal 140 of the vehicle transferee. The first server 110 may receive response data indicating that data was received without error from the car transferee's terminal 140.

Figure 20b shows the data flow of step 1220 of activating the remittance function for payment of acquisition tax and incidental expenses of the vehicle transferee. The first server 110 may activate a money transfer function to a set account on the car transferee's terminal 140. The established account may be, for example, an account of a government office (e.g., district office or city hall, etc.) that receives acquisition tax for transfer of car title. The first server 110 may receive data on the result of whether or not the payment has been made (for example, payment has been completed or payment has not been made, etc.) from the terminal 140 of the car transferee.

Figure 21 is a diagram illustrating the data flow that occurs in the step of applying for title transfer of a car (590; see Figure 5b) by attaching the stored car transfer certificate and data proving the payment history of the fee.

The first server 110 may apply to the seventh server 190 for a title transfer to change the owner of the car that is the subject of the transaction from the transferor of the car to the transferee of the car. The first server 110 may transmit the stored data of the automobile transfer certificate, data of the automobile transferee's acquisition tax payment history, and data of the automobile transferee's incidental expense payment history to the seventh server 190. The first server 110 may receive data on the result of the title transfer application (for example, that the title transfer application was accepted or rejected, etc.) from the seventh server 190.

Figure 22 is a diagram showing the data flow that occurs in the step 820 (see Figure 8) of transmitting data proving payment of acquisition tax, etc. and title transfer application data to the server of a financial company.

Although not shown, in some cases, the third server 130 may be used by the transferee of the car from a server other than the first server 110 (for example, a server of a government office for transfer of car title or a server of another financial company, etc.). You can receive data on whether you have paid the fee for transferring your name.

This case may include, for example, a case where the first server 110 transmits to the third server 130 that the car transferee has no history of paying fees for transferring the car's title. This case may include, for example, a case where the car transferee pays a fee for transferring the title to an account other than the account previously stored in the first server 110. This case may include, for example, a case where the car transferee directly pays the cost for title transfer at a government office, etc.

In this case, the first server 110 may transmit data to the third server 130 indicating that the car transferee has no history of paying fees for transferring the car's title. In this case, the third server 130 may receive data on whether the transferee of the vehicle has paid the fee for title transfer from a server other than the first server 110.

In any of the above-described cases, the third server 130 may receive data on whether the car transferee has paid the fee for transferring the car's title. Based on this, the financial company can conduct a loan screening for the loan product applied for by the car transferee, and can approve or reject the car transferee's loan depending on the loan screening results.

The first server 110 may transmit to the third server 130 data proving the payment of acquisition tax, etc. by the car transferee and data requesting transfer of the title of the car that is the subject of the transaction. The first server 110 may receive response data indicating that data was received without error from the third server 130.

The drawings and detailed description of the invention described so far are merely illustrative of the present invention, and are used only for the purpose of explaining the present invention, and are not used to limit the meaning or scope of the present invention described in the claims. That is not the case. Therefore, those skilled in the art will understand that various modifications and other equivalent embodiments are possible therefrom. Therefore, the true scope of technical protection of the present invention should be determined by the technical spirit of the appended claims.

100: network 110: first server
120: second server 130: third server
140: Automobile transferee's terminal 150: Automobile transferor's terminal
160: 4th server 170: 5th server
180: 6th server 190: 7th server
210: Communicator 230: Controller
250: memory

Claims (20)

In an automobile transaction brokerage method in which a first server including a processor communicates with a user terminal,
communicating with the user terminal to generate a customer identification value corresponding to a user of the user terminal;
transmitting the customer identification value to a second server;
Receiving information on loan products available to the user from the second server;
Displaying information about the loan product received from the second server on the user terminal; and
A car transaction brokerage method comprising accessing a third server and receiving first car information including an inspection result of a car selected by the user of the user terminal.
According to paragraph 1,
Further comprising accessing a fourth server to receive second vehicle information,
The second car information includes at least one of an accident history of the car selected by the user, an owner change history of the car selected by the user, and a repair history of the car selected by the user.
According to paragraph 1,
Further comprising accessing a fourth server to receive second vehicle information,
The second car information includes a car registration register of the car selected by the user.
According to paragraph 1,
The first car information includes the user's purchase intention data for the car selected by the user.
According to paragraph 1,
A car transaction brokerage method wherein the first car information includes evaluation data on undisclosed defects.
According to paragraph 1,
Information on the above loan products is a method of brokering automobile transactions, including mortgage loan interest rates and collateral loan limits.
According to paragraph 1,
Receiving a code corresponding to the loan product from the user terminal; and
An automobile transaction brokerage method comprising transmitting the customer identification value and the code to the second server.
According to paragraph 1,
An automobile transaction brokerage method further comprising displaying a user interface for accessing content provided by the second server on the user terminal.
According to clause 8,
The user interface is an automobile transaction brokerage method corresponding to at least one of an API (Application Programming Interface) and a URL.
According to paragraph 1,
A car transaction brokerage method further comprising the step of checking whether the user has subscribed to mandatory car insurance.
According to clause 10,
Further comprising displaying a user interface for accessing a fifth server on the user terminal,
An automobile transaction brokerage method wherein the fifth server includes a server of an insurance company that sells mandatory automobile insurance products.
According to clause 10,
It further includes steps to encourage subscription to mandatory automobile insurance,
The step of inducing subscription to mandatory automobile insurance is,
Accessing a fifth server to query the mandatory automobile insurance product;
Displaying information on the searched mandatory automobile insurance products on the user terminal;
Receiving a code corresponding to one of the mandatory automobile insurance products from the user terminal; and
An automobile transaction brokerage method comprising transmitting the customer identification value and the code to the fifth server.
According to paragraph 1,
The second server is a server for each of a plurality of financial companies,
The first server,
Transmitting the customer identification value to the server of each of the plurality of financial companies,
An automobile transaction brokerage method for displaying information on loan products received from servers of each of the plurality of financial companies on the user terminal.
In a server that communicates with a user terminal through a network,
A communicator connected to the network;
memory to store data; and
A controller configured to control the communicator and the memory and communicate with the user terminal through the communicator,
The controller is,
Interacting with the user terminal to generate a customer identification value corresponding to the user of the user terminal,
transmitting the customer identification value to a second server,
Receive information about loan products available to the user from the second server,
Displaying information on the loan product received from the second server on the user terminal,
A server that accesses a third server and receives first car information including an inspection result of a car selected by the user of the user terminal.
According to clause 14,
The controller accesses a fourth server to further receive second vehicle information,
The second car information includes at least one of an accident history of the car selected by the user, an owner change history of the car selected by the user, and a repair history of the car selected by the user.
According to clause 14,
The first car information includes data on the user's intention to purchase a car for the car selected by the user.
According to clause 14,
The controller is,
Receiving a code corresponding to the loan product from the user terminal,
A server transmitting the customer identification value and the code to the second server.
According to clause 14,
The controller is a server that inquires whether the user has subscribed to mandatory automobile insurance.
According to clause 18,
The controller is,
Querying the mandatory automobile insurance product on the fifth server,
Displaying information on the searched mandatory automobile insurance product on the user terminal,
A server that transmits a code corresponding to the mandatory automobile insurance product selected from the user terminal to the fifth server.
According to clause 14,
The second server is a server for each of a plurality of financial companies,
The controller is,
Transmitting the customer identification value to the server of each of the plurality of financial companies,
A server that displays information on loan products received from servers of each of the plurality of financial companies on the user terminal.

Images