1. An information processing method performed by an information processing apparatus including one or more processors that perform:

a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user;

a process of selling the offering; and

allowing delayed repayment of the debt corresponding to the first user based on the sale price or market price of the offering.

2. The information processing method according to claim 1, wherein the process of allowing for delayed reimbursement includes:

allowing for delayed processing of repayment of a debt corresponding to the first user based on the offering price or market price of the offering and the credit score of the first user.

3. The information processing method according to claim 1, wherein the process of allowing for delayed reimbursement includes:

determining a number of days to delay the debt and/or a processing of the amount of the debt to delay the debt based on the action on the offering from the second user.

4. The information processing method according to claim 3, wherein the process of allowing for delayed reimbursement includes:

determining a number of days to delay the debt and/or a handling of the amount of the debt to delay the debt based on the number of actions from the second user.

5. The information processing method of claim 3, wherein the action comprises:

at least one of browsing pages of the offering, registering the offering to a favorites, and giving a comment to the offering.

6. The information processing method according to claim 2, wherein the process of allowing for delayed reimbursement includes:

determining, based on the credit score, a number of days to delay the debt and/or a processing of the amount of the debt to delay the debt.

7. The information processing method according to claim 6, wherein the process of allowing for delayed reimbursement includes:

a higher credit score, a longer number of days to delay the debt and/or a larger number of processes to delay the debt.

8. The information processing method according to claim 1, wherein when the sale of the offering is cancelled, further performing:

the allowance is delayed for the processing of the redemption of the reimbursement.

9. The information processing method according to claim 1, wherein after the offering is traded, further performing:

processing of the repayment of the debt to be dialled to the repayment of the debt corresponding to the first user for at least a portion of the sale of the offering.

10. The information processing method according to claim 9, wherein the processing of the repayment dialled to the debt includes:

allocating the sale amount of the offering for redemption of the debt on a recent redemption date after the date the offering was traded.

11. A computer-readable non-transitory storage medium storing a program that causes one or more processors included in an information processing apparatus to execute:

a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user;

a process of selling the offering; and

allowing a delayed processing of repayment of a debt corresponding to the first user based on a selling price or a market price of the offering.

12. An information processing apparatus comprising one or more processors that perform:

a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user;

a process of selling the offering; and

allowing a delayed processing of repayment of a debt corresponding to the first user based on a selling price or a market price of the offering.

13. An information processing method performed by an information processing apparatus including one or more processors that perform:

a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user;

a process of selling the offering; and

the process of adding into a credit line adds a credit determined based on a selling price or market price of the offering and the credit score of the first user into a credit line corresponding to the first user.

14. The information processing method according to claim 13, wherein the process of appending to a credit line includes:

determining processing of the credit based on the action on the offering from the second user.

15. The information processing method according to claim 14, wherein the process of appending to a credit line includes:

determining a processing of the credit based on the number of actions from the second user.

16. The information processing method of claim 14, wherein the action comprises:

at least one of browsing pages of the offering, registering the offering to a favorites, and giving a comment to the offering.

17. The information processing method according to claim 13, wherein the process of appending to a credit line includes:

the higher the credit score, the greater the processing that determines the credit.

18. The information processing method according to claim 13, wherein when the sale of the offering is cancelled, further performing:

processing to cancel the credit.

19. The information processing method according to claim 13, wherein further performing:

a process of obtaining a financing commission from the first user within the limits of the first user's line of credit granted on the offering; and

and providing financing processing, and providing financing to the first user according to the financing delegation.

20. The information processing method according to claim 19, wherein the process of providing financing includes:

the financing process is provided by a monetary equivalent available on an e-commerce transaction platform.

21. The information processing method of claim 19, wherein after the offering is traded, further performing:

processing of reimbursement of said financing is awarded at least a portion of the sales of the offering.

22. A computer-readable non-transitory storage medium storing a program that causes one or more processors included in an information processing apparatus to execute:

a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user;

a process of selling the offering; and

a process of adding credit determined based on the selling price or market price of the offering and the credit score of the first user to a credit line corresponding to the first user.

23. An information processing apparatus comprising one or more processors that perform:

a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user;

a process of selling the offering; and

a process of adding credit determined based on the selling price or market price of the offering and the credit score of the first user to a credit line corresponding to the first user.

Background

In recent years, sales between individuals have been traded using the internet and communication lines. For example, a selling user registers and sells an item on a predetermined trading platform, and a purchasing user applies for purchase of the sold item on the predetermined trading platform.

In such an electronic commerce transaction, a certain amount of time is required from the sale of an article to the actual collection of the sale user, and the collection cannot be immediately or promptly performed from the sale. To solve this problem, for example, patent document 1 discloses a technique of, when a seller makes a financing application, providing a predetermined financing after a credit investigation of whether the seller is suitable as a financing recipient based on a result of an auction participation or the like.

Patent document 1: japanese laid-open patent application No. 2001-202469

However, a mechanism to support more flexible debt reimbursement by leveraging sales on e-commerce transaction platforms is also desired.

Disclosure of Invention

The present disclosure has been made in view of the above circumstances, and an object thereof is to provide an information processing method, a computer-readable non-transitory storage medium storing a program, and an information processing apparatus, which can realize more flexible debt repayment by selling on an electronic commerce transaction platform.

An information processing method according to an embodiment of the present disclosure is executed by an information processing apparatus including one or more processors that execute: a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user; a process of selling the offering; and allowing delayed processing of repayment of the debt corresponding to the first user based on the selling price or market price of the offering.

In addition, an information processing method according to another embodiment of the present disclosure is executed by an information processing apparatus including one or more processors that execute: a process of acquiring a sales request for a sales item from a first information processing apparatus used by a first user; a process of selling the offering; and a process of adding a credit determined based on the selling price or market price of the offering and the credit score of the first user to a credit line corresponding to the first user.

Drawings

Fig. 1 is a diagram showing an example of a configuration of a transaction system according to one aspect of the first embodiment, an example of a hardware configuration of a server according to the present disclosure, an example of a hardware configuration of a terminal according to the present disclosure, and an example of a block diagram showing a configuration of a transaction system according to the first embodiment.

Fig. 2 is a diagram illustrating a hardware configuration of the server 110B according to one embodiment of the first embodiment.

Fig. 3 schematically shows the structure of the transaction system according to the first embodiment.

Fig. 4 is a diagram showing an example of user management data stored in the memory of the server 110A according to the first embodiment.

Fig. 5 is a diagram showing an example of transaction management data stored in the memory of the server 110A according to the first embodiment.

Fig. 6 is a diagram showing an example of the liability management data stored in the memory of the server 110B according to the first embodiment.

Fig. 7 is a diagram showing an example of a processing sequence of the transaction system according to the first embodiment.

Fig. 8 is a diagram showing an example of the processing sequence according to the example of the first embodiment.

Fig. 9 schematically shows the structure of a transaction system according to the second embodiment.

Fig. 10 is a diagram showing an example of a configuration of a transaction system according to one aspect of the second embodiment, an example of a hardware configuration of a server according to the present disclosure, an example of a hardware configuration of a terminal according to the present disclosure, and an example of a block diagram showing a configuration of a transaction system according to the second embodiment.

Fig. 11 is a diagram showing an example of user management data stored in the memory of the server 110A according to the second embodiment.

Fig. 12 is a diagram showing an example of transaction management data stored in the memory of the server 110A according to the second embodiment.

Fig. 13 is a diagram showing an example of financing management data stored in the memory of the server 110A according to the second embodiment.

Fig. 14 is a diagram showing an example of a processing sequence of the transaction system according to the second embodiment.

Fig. 15 shows an example of the processing sequence according to the example of the second embodiment.

Description of the reference numerals

1 … … trading system,

110. 110A, 110B … … server

111. 121, 141, 151, 161 … … processor

112. 122, 142, 152, 162 … … memory

113. 123, 143, 153, 163 … … memory

114 … … input/output interface (I/F)

115. 125, 145, 155, 165 … … input device

116. 126, 146, 156, 166 … … output device

117. 127, 147, 157, 167 … … transceiver

120. 120A, 120B, 120C, 120X … … terminal

130 … … network

200 … … information processing device

1121 … … procedure

1122 … … sale management module

1123 … … debt information management module

1124 … … repayment processing module

1125 … … user management data

1126 … … transaction management data

1221 … … procedure

1222 … … display control module

1223 … … transaction processing module

1224 … … delay delegation module

1225 … … settlement processing module

1421 … … display control module

1422 … … display control module

1423 … … transaction processing module

1424 … … financing delegation module

1522 … … settlement management module

1523 … … debt management data

1622 … … sale management module

1623 … … Credit granting Module

1624 … … financing management module

1625 … … user management data

1626 … … transaction management data

1627 … … financing management data

Detailed Description

< compliance with laws and regulations >

When the disclosure described in this specification is implemented, it is implemented in compliance with the statutory regulations in the countries in which the disclosure is implemented. Further, the disclosure described in this specification is implemented by all changes, substitutions, variations, alterations, and modifications that may be made by those skilled in the art necessary to comply with the laws and regulations of various countries.

A computer-readable non-transitory storage medium storing a program, an information processing apparatus, and a mode for implementing an information processing method according to the present disclosure will be described with reference to the accompanying drawings.

< System Structure >

Fig. 1 shows a configuration of a transaction system 1 for effectively implementing an information processing method according to an embodiment of the present disclosure. As disclosed in fig. 1, in the transaction system 1, connected via the network 130 are: server 110A, server 110B; and terminal 120A, terminal 120B, terminal 120C.

In the present disclosure, when it is not necessary to distinguish the server 110A and the server 110B, respectively, the server 110A and the server 110B may also be denoted as the server 110, respectively. In addition, the number of servers 110 connected to the network 130 is not limited.

In the present disclosure, when it is not necessary to distinguish the terminal 120A, the terminal 120B, and the terminal 120C, respectively, the terminal 120A, the terminal 120B, and the terminal 120C may also be denoted as the terminal 120, respectively. In addition, the number of terminals 120 connected to the network 130 is not limited.

In the present disclosure, when it is not necessary to distinguish the server 110 and the terminal 120, respectively, the server 110 and the terminal 120 may also be represented as the information processing apparatus 200, respectively. Further, the number of information processing apparatuses 200 connected to the network 130 is not limited.

The server 110 provides a predetermined service to the terminal 120 used by the user via the network 130. By way of example, and not limitation, the predetermined services include: a settlement Service, a financial Service, an electronic commerce transaction Service, a Social Networking Service (SNS) typified by a message Service using instant messaging, and a content providing Service of music, video, books, and the like. The server 110 may provide more than one predetermined service individually or may provide more than one predetermined service in plurality. One or more terminals 120 are provided with a predetermined service through the server 110 so that a user can use the predetermined service via the terminal 120.

In the present disclosure, the settlement service refers to a service in which one or more users can give and receive money or money equivalents. The settlement service includes, by way of example and not limitation, a service for performing settlement using a one-dimensional code (barcode or the like), a two-dimensional code (QR code (registered trademark) or the like) (hereinafter, the one-dimensional code and the two-dimensional code are collectively referred to as "two-dimensional code or the like"), Near Field Communication (NFC), Bluetooth Low Energy (BLE), Wi-Fi (registered trademark), ultrasonic Communication, infrared Communication, or the like. Further, settlement performed by reading a two-dimensional code or the like by a terminal 120 of a user (payer) who pays a payment for goods is expressed as "user-read code settlement" or "Merchant Present Mode (MPM)", and settlement performed by displaying a two-dimensional code or the like by a terminal 120 of a user who pays a payment and reading a displayed two-dimensional code or the like by a terminal 120 of a user (seller, claimant) such as a store side who claims a payment for goods is expressed as "store-read code settlement" or "Consumer Present Mode (CPM)". In addition, MPM and CPM may be dynamic or static.

As necessary, a terminal used by the user X is denoted as a terminal 120X, and information corresponding to the user in a predetermined service corresponding to the user X or the terminal 120X is denoted as user information X. By way of example and not limitation, the user information may include information corresponding to the user, such as a name of the user, an icon image of the user, an age of the user, a sex of the user, an address of the user, a taste of the user, an identifier of the user, balance information of an electronic value (electronic money) corresponding to the user, credit card information (credit card number, etc.) corresponding to the user, which is input by the user or given by a predetermined service.

The network 130 connects two or more servers 110 or two or more terminals 120. The network 130 provides a connection path to enable the terminal 120 to transceive data after connecting to the server 110.

More than one portion of the network 130 may be a wired network or a wireless network. By way of example, and not limitation, the network 130 may be: ad Hoc Network (Ad Hoc Network), intranet, extranet, Virtual Private Network (VPN), Local Area Network (LAN), Wireless LAN (WLAN), Wide Area Network (WAN), Wireless WAN (WWAN, Wireless WAN), Metropolitan Area Network (MAN), a portion of the internet, a portion of Public Switched Telephone Network (PSTN), a mobile Telephone Network, Multiple Integrated Services Digital Networks (ISDNs), Multiple Wireless LANs, Long Term Evolution (LTE), Code Division Multiple Access (CDMA, Code Multiple Access), Bluetooth (registered trademark), and the like, and combinations thereof. The network 130 may include one or more networks.

The server 110 and the terminal 120 may be any information processing apparatus as long as they can implement the functions and methods described in the present disclosure.

By way of example and not limitation, the server 110, the terminal 120 may be: a smart phone, a mobile phone (feature phone), a computer (by way of example and not limitation, a desktop, a notebook, a tablet, etc.), a server device, a media computer platform (by way of example and not limitation, a cable, a satellite set-top box, a Digital video recorder, etc.), a handheld computer device (by way of example and not limitation, a Personal Digital Assistant (PDA), an email client, etc.), a wearable terminal (by way of example and not limitation, a glasses-type device, a watch-type device, etc.), other kinds of computers, or a communication platform, etc., as well as combinations thereof.

< hardware configuration of each information processing apparatus >

(1) Hardware structure of server

The hardware configuration of the server 110 included in the transaction system 1 will be described with reference to fig. 1.

The server 110 includes a processor 111, a memory 112, a storage 113, an input/output interface (I/F) 114, an input device 115, an output device 116, and a transmitting/receiving unit 117. By way of example, and not limitation, the various structural elements of the hardware of server 110 are interconnected via a bus B.

The server 110 realizes the processes, functions, or methods described in the present disclosure by cooperation of the processor 111, the memory 112, the storage 113, the input/output I/F114, and the transmission/reception unit 117.

The processor 111 executes processes, functions, or methods implemented by codes or instructions contained in the program stored in the memory 113. By way of example, and not limitation, processor 111 includes: one or more Central Processing Units (CPUs), Micro Processing Units (MPUs), Graphics Processing Units (GPUs), microprocessors (microprocessors), processor cores (processor cores), multiprocessors (multiprocessors), Application-Specific Integrated circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and the like, and the processes, functions, or methods disclosed in the embodiments may be implemented by logic circuits (hardware) or dedicated circuits formed in an Integrated Circuit (LSI) chip, a Large Scale Integrated Circuit (Large Scale Integration), or the like. Further, these circuits can be implemented by one or a plurality of integrated circuits, and a plurality of processes shown in each embodiment can be implemented by one integrated circuit. Furthermore, the LSI is also called a Very Large Scale Integration (VLSI), super LSI, ultra LSI, or the like depending on the difference in integration level.

The memory 112 temporarily stores the program 1121 loaded from the storage 113 and provides a work area for the processor 111. In the memory 112, various data generated during execution of a program by the processor 111 are also temporarily stored. By way of example and not limitation, the Memory 112 may be a Random Access Memory (RAM), a Read Only Memory (ROM), and the like, as well as combinations thereof.

The memory 113 stores programs, modules, and various data. By way of example and not limitation, the memory 113 may be a Hard Disk Drive (HDD), a Solid State Drive (SSD), a flash memory, or the like, or a combination thereof.

The input/output I/F114 is connected to an input device 115 for inputting various operations for the server 110 and an output device 116 for outputting processing results processed by the server 110.

The input device 115 is implemented by any one or a combination of all kinds of devices that can accept an input from a user and transfer information related to the input to the processor 111 via the input/output I/F114. By way of example and not limitation, the input device may be a touch panel, a touch display, a hard key such as a keyboard, a pointing device such as a mouse, a camera (operation input via an image), a microphone (operation input by sound), or the like, and may also be a combination thereof.

The output device 116 is implemented by any one or a combination of all kinds of devices capable of outputting the processing result processed by the processor 111 via the input/output I/F114. When the processing result is output as a video or a video, the output device 116 is realized by any one or a combination of all kinds of devices capable of displaying the display data written in the frame buffer based on the display data. By way of example and not limitation, the output device 116 may be a touch panel, a touch Display, a monitor (by way of example and not limitation, a liquid crystal Display, an Organic electroluminescent Display (OELD), or the like), a Head Mounted Display (HMD), a device capable of displaying images, text information, and the like in projection maps, holograms, air, and the like (which may also be vacuum), a speaker (audio output), a printer, or the like, or may be a combination thereof. Further, these output devices may also be capable of displaying the display data in 3D.

The input device 115 and the output device 116 may be integrated, or the input device 115 and the output device 116 may be separated.

The transmission/reception unit 117 transmits and receives various data via the network 130. The communication may be performed by either wired or wireless, and any communication protocol may be used as long as mutual communication is possible. The transceiver 117 has a function of communicating with another information processing apparatus via the network 130. The transmission/reception unit 117 transmits various data to other information processing apparatuses in accordance with instructions from the processor 111. The transceiver 117 receives various data transmitted from other information processing apparatuses and transmits the data to the processor 111.

(2) Hardware architecture of terminal 120

The hardware configuration of the terminal 120 included in the transaction system 1 will be described with reference to fig. 1.

The terminal 120 includes a processor 121, a memory 122, a storage 123, an input/output I/F124, an input device 125, an output device 126, and a transmitting/receiving unit 127. By way of example and not limitation, the various structural elements of the hardware of the terminal 120 are interconnected via a bus B.

The terminal 120 implements the processes, functions, or methods described in the present disclosure through cooperation among the processor 121, the memory 122, the storage 123, the input/output I/F124, the input device 125, the output device 126, and the transmission/reception unit 117.

The processor 121 executes a process, a function, or a method implemented by code or instructions contained in a program stored in the memory 123. By way of example, and not limitation, processor 121 comprises: a Central Processing Unit (CPU), a Micro Processing Unit (MPU), a Graphics Processing Unit (GPU), a microprocessor (microprocessor), a processor core (processor core), a multiprocessor (multiprocessor), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like, and the processes, functions, or methods disclosed in the embodiments may be implemented by a logic Circuit (hardware) or an Application-Specific Circuit formed in an Integrated Circuit (IC) chip, a Large Scale Integrated Circuit (LSI), or the like. Further, these circuits can be implemented by one or a plurality of integrated circuits, and a plurality of processes shown in each embodiment can be implemented by one integrated circuit. Furthermore, the LSI is also called a Very Large Scale Integration (VLSI), super LSI, ultra LSI, or the like depending on the difference in integration level.

The memory 122 temporarily stores the program 1221 loaded from the storage 123 and provides a work area for the processor 121. In the memory 122, various data generated during the execution of the program 1221 by the processor 121 are also temporarily stored. By way of example and not limitation, the Memory 122 may be a Random Access Memory (RAM), a Read Only Memory (ROM), and the like, as well as combinations thereof.

The memory 123 stores programs and various data. By way of example and not limitation, the memory 123 may be a Hard Disk Drive (HDD), a Solid State Drive (SSD), a flash memory, or the like, or a combination thereof.

The input/output I/F124 is connected to an input device 125 for inputting various operations for the terminal 120 and an output device 126 for outputting a processing result processed by the terminal 120.

The input device 125 is implemented by any one or a combination of all kinds of devices capable of accepting an input from a user and transferring information related to the input to the processor 121. By way of example and not limitation, the input device may be a touch panel, a touch display, a hard key such as a keyboard, a pointing device such as a mouse, a camera (operation input via an image), a microphone (operation input by sound), or the like, and may also be a combination thereof.

The output device 126 is implemented by any one or a combination of all kinds of devices capable of outputting the processing result processed by the processor 121. When the processing result is output as a video or a video, the output device is realized by any one or a combination of all kinds of devices capable of displaying the display data written in the frame buffer based on the display data. By way of example and not limitation, the output device may be a touch panel, a touch Display, a monitor (by way of example and not limitation, a liquid crystal Display, an Organic electroluminescent Display (OELD), or the like), a Head Mounted Display (HMD), a device capable of displaying an image, text information, or the like in a projection map, a hologram, air, or the like (which may be vacuum), a speaker (audio output), a printer, or the like, or may be a combination thereof. Further, these output devices may also be capable of displaying the display data in 3D.

The input device 125 and the output device 126 may be integrated, or the input device 125 and the output device 126 may be separated.

The transmission/reception unit 127 transmits and receives various data via the network 130. The communication may be performed by either wired or wireless, and any communication protocol may be used as long as mutual communication is possible. The transmitting/receiving unit 127 communicates with other information processing apparatuses via the network 130. The transmission/reception unit 127 transmits various data to other information processing apparatuses in accordance with instructions from the processor 121. The transceiver 127 receives various data transmitted from other information processing apparatuses and transfers the data to the processor 121.

(3) Others

The cloud computing configured by one or more information processing apparatuses may implement at least part of processing, functions, or methods in the server 110 or the terminal 120.

The other information processing apparatus may implement at least a part of the processing, functions, or methods in the server 110 or the terminal 120. In this case, the processor of the other information processing apparatus may also realize at least part of the processing realized by the processor 111 or the processor 121.

The program that executes the processing of the embodiments of the present disclosure may be provided in a state stored in a computer-readable storage medium. The storage medium is capable of storing the program in a "non-transitory tangible medium". By way of example, and not limitation, the programs may be software programs and computer programs.

The storage medium may be one or more semiconductor-based or other Integrated Circuits (ICs) (by way of example and not limitation, Field Programmable Gate Arrays (FPGAs), application specific ICs (asics), and the like), Hard Disk Drives (HDDs), hybrid hard disk drives (HHDs), optical disks, Optical Disk Drives (ODDs), magneto-optical disks, magneto-optical drives, floppy disks, Floppy Disk Drives (FDDs), magnetic tape, Solid State Drives (SSDs), RAM drives, secure digital cards or drives, any other suitable storage medium, and the like, as well as combinations thereof. The storage medium may be volatile, nonvolatile, or a combination of volatile and nonvolatile.

Further, the program of the present disclosure may be provided to the server 110 or the terminal 120 via any transmission medium (a communication network, a broadcast wave, or the like) capable of transmitting the program.

Furthermore, the embodiments of the present disclosure may also be implemented in the form of a data signal embedded in a carrier wave that embodies the program by electronic transmission.

Further, by way of example and not limitation, the program of the present disclosure is implemented using JavaScript (registered trademark), a script language such as Python, a C language, a Go language, Swift, Kotlin, Java (registered trademark), or the like.

< others >

Unless explicitly mentioned, the determination structure in the embodiment of the present disclosure is not essential, and it is also possible to operate a predetermined process when the determination condition is satisfied, or to execute a predetermined process when the determination condition is not satisfied.

The present disclosure encompasses all changes, substitutions, variations, alterations, and modifications that may be made by those skilled in the art to which the present disclosure pertains. Furthermore, the appended claims encompass all changes, substitutions, variations, alterations, and modifications that may be made by those skilled in the art to the patent claims. Furthermore, this disclosure encompasses any combination of one or more features of an implementation or embodiment in this disclosure with one or more features of other implementations or embodiments in this disclosure that may be made by a person skilled in the art.

Further, with reference to a device or system or a structural element of a device or system adapted, configured, capable, configured, usable, operable, or operable to carry out a particular function in the appended claims, reference to the device, system, structural element or the structural element of the device or system encompasses that device, system, structural element, whether or not that device, system, structural element or the particular function is activated, unlocked, or unlocked, so long as that device, system, or structural element is adapted, configured, capable, configured, usable, operable, or operable to carry out the particular function.

Unless explicitly stated otherwise, the present disclosure may obtain user consent when implementing any of the embodiments or examples, in advance of, or immediately prior to implementation. Moreover, the consent obtained may be general or may be obtained at any time.

Embodiments according to an example of the present disclosure will be described below with reference to the drawings. However, the embodiments and examples described below are examples, and are not intended to exclude the application of various modifications or techniques not explicitly described below. That is, an example of the present disclosure can be implemented by being variously modified within a scope not departing from the gist thereof. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals, and the drawings are schematic and do not necessarily correspond to actual dimensions, proportions, and the like. Further, the drawings include portions having different dimensional relationships or ratios from each other.

< first embodiment >

The first embodiment is an embodiment that allows a sale user to be delayed in the payment of debts based on offerings by allowing the payment of debts corresponding to a sale user by delaying the payment based on the offerings based on the sale price or market price of offerings sold by a first user, namely, the sale user, in the inter-user trading system 1.

Fig. 3 is a diagram for explaining the configuration of the transaction system according to the first embodiment. In this configuration, the transaction system 1 is constructed by the plurality of information processing apparatuses 200, for example, the terminal 120A of the selling user, the terminal 120B of the purchasing user, and the server 110A used by the operator and manager of the electronic commerce transaction platform.

Further, the server 110A may cooperate with the server 110B that manages the debt possessed by the user by the creditor as necessary. The server 110B may be a server associated with a settlement service in cooperation with an e-commerce transaction platform. Further, without being limited thereto, each process, each function, or each method of the present disclosure may also be implemented by one server in which the server 110A and the server 110B are integrated. Further, server 110A may also implement at least one process, function, or method implemented by server 110B, and server 110B may also implement at least one process, function, or method implemented by server 110A.

In addition, the settlement service provided by the server 110B may be any settlement service to which the present disclosure is applicable. For example, the settlement may be performed using a code such as a two-dimensional code, or may be performed using electronic money.

In the example shown in fig. 3, the service of associating the e-commerce transaction with the allowable delayed payment liability is performed according to the following procedures, i.e., a. Next, the flow of the service will be described.

(A. sell offerings on an e-commerce trading platform)

The selling user registers information and price of an offering desired to be sold to the electronic commerce transaction platform using the terminal 120A. Thus, the offerings will be sold on the e-commerce transaction platform. On the electronic commerce transaction platform, commodity information is disclosed, and any user can browse the commodity information. In addition, the server 110A determines a market price of the offering based on the transaction information of the e-commerce transaction platform. In this case, the server 110A may further determine a credit score for the selling user.

(B. allowing delayed repayment of debt)

The server 110A determines whether to allow delayed repayment of the debt corresponding to the selling user based on the selling price of the offering or the market price of the offering when the offering is sold. In addition, in this case, it is also possible to determine the number of days, due date, number of times (hereinafter, simply referred to as "delay days") that allows the payment of the debt as the extension subject to be delayed, and the amount of the debt (hereinafter, simply referred to as "delay amount") that allows the payment to be delayed.

(C. delayed delegation and delayed processing of debt repayment)

Server 110A then sends a notification to the selling user regarding the allowance of the delayed repayment of the debt. Then, the server 110A, upon receiving a delayed delegation desiring to delay the payment of the debt from the terminal 120A used by the selling user, performs a delay process of the payment of the debt corresponding to the selling user.

The determination of the number of delay days and/or the amount of delay may be made at predetermined occasions. For example, the server 110A may determine the number of delay days and/or amount of delay in the event that an offering is sold or in the event that an action is received from the terminal 120B used by the purchase candidate user on the sold offering. The action from the purchase candidate user may be any action as long as it is an action for the sold offering. By way of example and not limitation, the action from the purchase candidate user may be browsing a page of offerings, registering the offerings to favorites, giving comments to the offerings.

Additionally, the server 110A may determine the number of delay days and/or the amount of delay if a predetermined condition is satisfied. For example, the predetermined condition may include: the selling price or market price of the offerings is a predetermined value or more, the number of offerings in sale is a predetermined value or more, the number of transactions is a predetermined number of times or more, or the number of offerings registered in the favorites is a predetermined value or more, and the like.

(D. trade of offerings)

The purchasing user browses the commodity information of the offerings sold on the electronic commerce transaction platform and determines the offerings to be purchased. For the transaction, a transaction process of a known electronic commerce transaction platform may be executed. This establishes the transaction, and executes the distribution process of the sold item and the payment process of the payment of the money.

(E. repayment of debt delayed)

The selling user who has accepted the extension of the debt payment date pays the debt before the extended payment date. The method of repayment of the debt is not particularly limited, and may be performed according to the method determined at the time of delayed delegation. For example, when the transaction of the sales item is established, a part of the payment may be allocated to the debt payment, or the sales user may pay back by a known payment method before a predetermined time limit regardless of the establishment of the transaction of the sales item.

< effects of the first embodiment >

According to the first embodiment, the selling user can accept the allowance of the delayed repayment of the debt based on the selling price or market price of the offering. This allows the selling user to suspend the payment of the debt due to the sale of the sales item, for example, and thus the debt payment can be performed more flexibly. Further, the server 110A can directly or indirectly collect the right to debt from the sales of the sales by extending the repayment date in accordance with the sales. Thereby, the risk of recovering the debt can be reduced for the person who provides financing.

< Structure of the first embodiment >

The configurations of server 110A, server 110B, and terminal 120 will be described with reference to fig. 1 to 2.

(1) Architecture of server 110A

Fig. 1 shows an example of a block diagram of the configuration of a server 110A according to the first embodiment. The server 110A performs processing related to the liability delay service using offerings on the e-commerce transaction platform. The server 110A has, for example, a sales management module 1122, a debt information management module 1123, and a repayment processing module 1124. In addition, each process can be realized by machine learning or Artificial Intelligence (AI) within an implementable range.

Each module disclosed in fig. 1 is realized by cooperation with the processor 111, the memory 112, the storage 113, the input/output I/F114, the input device 115, the output device 116, and the transmission/reception unit 117 provided in the server 110A. For example, the sales management module 1122, the debt information management module 1123, and the repayment processing module 1124 may be implemented by the processor 111 reading out and executing a program saved in the memory 113.

The sales management module 1122 sets an article ID based on a sales request for an article, and stores the article information and the sales price transmitted by the sales user in the transaction management data 1126. The product information is information for specifying an article to be sold, such as an article image of the article to be sold captured by the selling user, and an article name input or selected by the selling user. The sales management module 1122 may determine a market price of the sales item based on the transaction management data 1126, and save the market price thereof in correspondence with the sales item into the transaction management data 1126.

In addition, the sales management module 1122 may also calculate credit scores for users utilizing the e-commerce transaction platform based on the transaction management data 1126 and store into the user management data 1125. Here, the credit score of the user is an index indicating the credit degree of the user, and may vary depending on the user information and the action of the user. By way of example and not limitation, such credit scores may also be calculated based on user action information such as the number of trades, the number of trades evaluated, the proportion of good scores in the trades evaluated, and the speed of the trades. The credit score may be calculated by a known technique, or may include a known calculation element.

Next, the sales management module 1122 uses the commodity information and the sales price stored in the transaction management data 1126 to sell the offerings and executes the processing relating to the electronic commerce transaction. For example, the sales management module 1122 discloses product information, executes a transaction of a sales item, and executes a process of intermediating a transaction between a sales user and a purchase user before the transaction is established. The sales management module 1122 receives the agreement between the sales user and the purchasing user, and then determines that the transaction is established, and executes the settlement process.

In the settlement process, the sales management module 1122 may instruct the repayment processing module 1124 to perform the repayment process of the debt in the case where the transaction management data 1126 is confirmed and the debt is allowed to be delayed based on the sold being traded.

The debt information management module 1123 determines whether to allow delayed repayment of the debt based on the selling price or market price of the offering. In addition, the debt information management module 1123 may also determine whether to allow delayed repayment of the debt based on the selling price or market price of the offering and the credit score of the selling user. Then, in the case where the selling user wishes to delay the payment of the debt, the debt information management module 1123 performs delay processing of the payment of the debt. For example, the debt information management module 1123 may also allow for delayed repayment of the debt only if the selling price or market price is within a predetermined price range or if the credit score is above a predetermined threshold. In addition, the debt information management module 1123 may determine that the higher the selling price or the market price is, the longer the delay number of days is determined or the larger the delay amount is determined. In addition, the debt information management module 1123 may determine that the delay amount is larger or the delay number is larger as the credit score is higher.

Before obtaining the allowable delayed debt payment as described above, the debt information management module 1123 may further perform a process of acquiring debt information on the debt of the user using the e-commerce transaction platform. For example, the debt information management module 1123 acquires settlement information, which is settlement information received from the terminal 120 of the user or the terminal of the store, or the server 110B and is settlement information when settlement processing is performed after a predetermined period of time has elapsed such as post-payment, as the debt information. In this case, the debt information may include information on the payment amount and the payment date for each settlement information, for example.

The debt information management module 1123 controls to transmit the debt information to the terminal 120 via the transmitting/receiving part 117 in case that the user using the electronic commerce transaction platform has a debt. In addition, the debt information management module 1123 controls to transmit a notification of recommendation of sale of the sales on the electronic commerce transaction platform to the terminal 120 via the transceiver 117 together with the debt information.

The debt information management module 1123 receives a delay request indicating that it is desired to delay the payment of the debt based on the sold material at the time of sale or during the sale, from the terminal 120A used by the selling user having the debt via the transceiver 117. For example, in the case where such a delayed delegation is received, the debt information management module 1123 may also store the meaning in the information on the corresponding offering in the transaction management data 1126.

The repayment processing module 1124 performs a process of repayment the debt of the selling user. For example, the repayment processing module 1124 performs a repayment process of appropriating the sale amount of the offering corresponding to the delayed delegation to the debt repayment in a case where the transaction of the offering has been completed. In addition, in the case where the payment processing has been completed, the payment processing module 1124 may also update the debt information of the subscriber and transmit the debt balance to the subscriber.

The repayment processing module 1124 may also perform repayment processing of the debt by aggregating sales of a plurality of offerings in a case where the user obtains sales through the plurality of offerings. In this case, the repayment processing module 1124 may surely give a combination of the total amount of sales being larger than the debt amount and the sales closest to the debt amount, and dial the total of the sales to the debt repayment.

The repayment processing module 1124 may correspond an amount of money exceeding the debt amount among the total amount of sales to the user as a money equivalent available on the e-commerce transaction platform. Additionally, the redemption processing module 1124 may also fill in the difference with a monetary equivalent that the user stores by adding value or points if the total of sales is not sufficient for the debt. Here, the money equivalent includes the electronic value of the user's stored value by adding value or points.

In addition, the debt for the redemption processing module 1124 performing redemption processing may also include debt generated by a settlement service cooperating with the e-commerce transaction platform. Here, the debt generated by the settlement service cooperating with the electronic commerce transaction platform includes the debt generated by the electronic commerce transaction platform in addition to the debt generated by the transaction within the electronic commerce transaction platform. Therefore, for example, debts generated by settlement processing using an information code such as a barcode or a QR code (registered trademark) in an actual store can be paid out by the sales amount of the sold goods on the electronic commerce transaction platform.

Further, the debt of the repayment processing module 1124 for performing the repayment processing may further include a debt generated by a service provided by the above-described settlement service in cooperation with the electronic commerce transaction platform. More specifically, debts resulting from post-payment, financing-based debts may also be included. The post-payment here may include payment methods such as post-payment, installment payment, and circulation payment that are aggregated for one month.

The debt generated outside the electronic commerce transaction platform may be managed by the server 110B providing the settlement service, or may be managed by the server 110 in which the server 110A and the server 110B are integrated. Further, the server 110A may acquire information related to the debt from the server 110B. In the case where the debt is managed by the server 110B, in the repayment process by the repayment processing module 1124 of the server 110A, for example, including the delivery of money equivalent to the repayment to the server 110B, the server 110B is caused to perform the debt repayment process.

Through the above processing, the selling user can accept the extension of the debt repayment date based on the selling of the e-commerce transaction platform, thereby realizing more flexible debt repayment. Further, this makes it possible to promote sales on an electronic commerce transaction platform for the purpose of extending the debt payment date.

The timing at which the debt information management module 1123 determines the allowance of the delayed payment of the debt is not particularly limited, and the delayed payment of the debt may be allowed when the status of the sold item is changed, other than at the time of sale. Examples of such a case include a case where the article is sold, a case where an action from the purchase candidate user on the article is received, a case where the market price of the article is changed, and a case where the scarcity of the article is changed.

The debt information management module 1123 is not limited to the number of delay days or the timing of determining the delay amount, and may allow debt to be paid out with a delay when the sold item is changed, other than at the time of sale. The debt information management module 1123 may update the information of the transaction management data 1126 if the number of delay days and the delay amount are determined or updated.

For example, the debt information management module 1123 may determine the delay number of days, the delay amount, and the like based on the selling ease of the offering on the electronic commerce transaction platform determined according to the selling price and the market price of the offering and the credit score of the selling user in a case where the offering has been sold.

More specifically, when the selling price specified by the selling user is lower than the market price, the debt information management module 1123 sets the delay number of days and the delay amount to be large because the possibility of selling the sold item is high. In addition, in the case where the scarcity of the sold items is high, even in the case where the selling price of the sold items is higher than the market price, since the possibility of selling the sold items is high, the debt information management module 1123 sets the delay number of days and the delay amount to be large.

In addition, in the case where the credit score of the selling user is high, since the possibility that the transaction of the sales item is established is high or since the reliability of the debt paid out by the selling user is high, the debt information management module 1123 may set the delay number of days to be longer and/or the delay amount to be larger as the credit score of the selling user is higher. The number of delay days and the delay amount may be determined independently of each other, or may be determined based on the balance between the number of delay days and the delay amount. As an example of determination based on the balance between the both, for example, the delay amount may be set to be larger as the delay number of days is shorter, or the delay number of days may be set to be longer as the delay amount is smaller. The setting may be automatically determined by the server 110A or the server 110B, or may be set by the first user.

Thus, the number of delay days and the delay amount can be determined more flexibly based on the reliability of the debt paid out by the selling user.

After the sale, when the market price of the sold item belonging to the category of the sold item and the scarcity of the sold item change, the debt information management module 1123 may determine the delay number of days and the delay amount again. The sales management module 1122 of the server 110A may determine a market price and a credit score of the item to be sold based on current or past transaction data of the transaction management data 1126, and store the market price and the credit score in the user management data 1125 and the transaction management data 1126.

In addition, the debt information management module 1123 may determine the number of delay days and/or the amount of delay based on the action performed on the offering by the purchase candidate user (second user). Examples of the action include browsing a sales page, registering a sales in a favorite, or giving a comment to the sales. Since the possibility of selling the offerings is higher as the number of views on the offerings page, the number of registered favorites, or the number of comments is larger, the debt information management module 1123 may set the delay number of days or the delay amount to be larger. In addition, the number of delay days, the delay amount may also be determined according to the ratio between the number of views of the offering page and the number of favorite registrations of the offering or the number of comments given to the offering.

More specifically, if the ratio of the number of registered favorites of the offering or the number of comments given to the offering is large with respect to the number of views on the offering page, the number of delay days or delay amount may be set higher than in the case where the ratio is low. This is because if the ratio of the number of registered favorites of the offering or the number of comments given to the offering is larger with respect to the number of views of the offering page, it can be estimated that the ratio of users whose purchase intention is high is larger.

Further, the debt information management module 1123 may determine the number of delay days, the delay amount based on the content of the comment. For example, in the case where the sales include keywords frequently appearing immediately before the sales such as "immediately … …", "thank you", and the like, the debt information management module 1123 may set the delay number of days and the delay amount to be large because the sales are likely to be sold.

Thus, the number of delay days and the delay amount can be determined more flexibly based on the ease of selling the sales on the electronic commerce transaction platform.

In addition, the debt information management module 1123 may also cancel the allowance delayed repayment granted for the offering in the case where the sale of the offering is cancelled. In addition, the debt information management module 1123 may determine not to execute the delayed payment of the debt allowed based on the offering in a case where the sale of the offering is cancelled and the same item is sold within a predetermined period. In this case, the debt information management module 1123 may determine that the cancelled offering and the newly sold offering are the same item based on the similarity between the cancelled offering and the newly sold offering. Further, the debt information management module 1123 may perform a process of reducing the credit score of the selling user when the sale of the sales related to the delayed delegation is cancelled after the delayed delegation of the debt repayment.

Thereby, on the premise that cancellation is performed, the risk of selling for the purpose of allowing delayed repayment of the debt can be reduced. In addition, the debt information management module 1123 allows the predetermined number of sales even when the sales of the sold item is cancelled and the same product is sold within a predetermined period, so that it is possible to suppress the allowance of the delayed debt from being excessively limited against the sales error due to the erroneous operation or the like. In addition, when cancellation is performed after the estimated repayment date (the original repayment date) before the allowable delayed repayment debt given to the sold object is performed, the latest expected repayment date after the estimated repayment date and after the estimated repayment date may be set as the new expected repayment date.

The debt information management module 1123 may cancel the allowance delay paid for the sold offering in the case where the sold offering is traded. More specifically, the debt information management module 1123 may allow the debt cancellation to be delayed, and the repayment processing module 1124 may perform a repayment process of repayment of at least a part of the sales of the offering to the debt corresponding to the selling user. In this case, the redemption processing module 1124 may dial the sales of the offering to the redemption of the debt on the most recent redemption date after the date the offering was traded. In addition, the redemption processing module 1124 may also perform a process of increasing the credit score of the selling user after performing the redemption process.

This enables smooth payment of the debt when the sales are traded. Further, by preferentially paying off the debt on the latest payment day after the date on which the sales were traded, the risk of the payment day expiring can be reduced.

In addition, the debt information management module 1123 may calculate a total amount of selling prices or a total amount of market prices for a plurality of offerings sold by the selling user, for example, and determine the delay days and the delay amount based on the total amount and the credit score. Further, the total amount of the calculated selling price or the total amount of the market price may be limited to the offerings sold within a predetermined period.

Thus, even when the price of each item sold by the selling user is low, and one item cannot specify a sufficient number of delay days or the amount of debt to be extended, the number of delay days or the amount of debt to be extended can be specified.

When the debt payment date extension process is performed, the debt information management module 1123 may limit the increase or decrease of the selling price of the sales material for which the sale is cancelled and/or sold, as the guarantee of the extension process, for a part or all of the sales materials sold by the selling user. In addition, increases and decreases in the selling price may be permitted within a predetermined amount or a predetermined amount ratio. Further, in the case where the selling user pays out all or a part of the debt related to the extension process, the debt information management module 1123 may also release the limitation of the increase and decrease amount of the selling price for the sales cancelled and/or sold. When such a restriction is added or removed, the debt information management module 1123 may store information related to the restriction into the transaction management data 1126.

This can suppress the situation in which the selling user improperly receives permission to pay off the debt later by canceling the sale, increasing or decreasing the sale price, or the like, and can reduce the risk of failing to collect the debt.

The debt information management module 1123 may perform a process of requesting that a part or all of the sales items sold by the selling user be stored in a facility managed by the electronic commerce transaction platform and detecting storage of the sales items, when the debt payment date is extended. Further, when the selling user pays out all or a part of the debt, the debt information management module 1123 may further perform processing for receiving a return request for returning the sales stored in the facility to the selling user. In this way, when storing or returning the sales, the debt information management module 1123 may also store information on the storage or return in the transaction management data 1126.

In this way, when the debt repayment date is extended, the sales under the management of the selling user is placed under the management of the electronic commerce transaction platform, so that the risk of transaction failure due to the selling user not sending the sales to the purchasing user or the like can be reduced. Therefore, the risk of failing to collect the claims can be reduced.

The debt information management module 1123 may execute a process of allocating a part or all of the sales amount of the sales item to the extended payment of the debt when the transaction of the sales item is established.

Thus, the credit right can be collected when the selling user obtains the sales amount, and therefore, the risk that the credit right cannot be collected can be reduced. In addition, for the selling user, since the procedure of paying out the debt can be simplified, the trouble of paying out can be reduced.

The memory 113 stores a program executed by the server 110A according to the first embodiment, user management data 1125 for managing users who are members of the electronic commerce transaction platform, and transaction management data 1126 for managing transactions executed on the electronic commerce transaction platform. These data will be described later.

In addition, one or more processors 111 read out and execute the modules from the memory 112 as necessary. For example, the one or more processors 111 may constitute a sales manager, a debt information manager, and a repayment processor by respectively executing the sales manager module 1122, the debt information manager module 1123, and the repayment processor module 1124.

(2) Architecture of Server 110B

Fig. 2 shows an example of a block diagram of the configuration of the server 110B according to the first embodiment. The server 110B is a server related to settlement services in cooperation with the electronic commerce transaction platform, and performs a process of managing debts possessed by the user by the creditor. The server 110B has, for example, a settlement management module 1522. In addition, each process can be realized by machine learning or Artificial Intelligence (AI) within an implementable range.

Each module disclosed in fig. 2 is realized by cooperation with the processor 151, the memory 152, the storage 153, the input/output I/F154, the input device 155, the output device 156, and the transmission/reception unit 157 included in the server 110B. For example, the settlement management module 1522 may be implemented by the processor 151 reading out and executing a program stored in the memory 153.

In fig. 2, the processor 151, the memory 152, the storage 153, the input/output I/F154, the input device 155, the output device 156, and the transmission/reception unit 157 correspond to the processor 111, the memory 112, the storage 113, the input/output I/F114, the input device 115, the output device 116, and the transmission/reception unit 117, respectively.

The settlement management module 1522 executes various processes for making settlement of debts. For example, the settlement management module 1522 receives settlement information from the terminal 120 owned by the user, and stores the debt of the user in the debt management data 1523. The settlement information may include the date of occurrence of the debt, the amount of the debt, and the date of repayment. The settlement management module 1522 may receive settlement information from another terminal owned by the user or a store terminal of the settlement party.

The settlement management module 1522 executes the debt payment processing in the server 110B in a case where money equivalent to the payment is received from the server 100A and an instruction to execute the debt payment processing is received.

In addition, one or more processors 151 read out and execute the respective modules from the memory 152 as necessary. For example, the one or more processors 151 may constitute a settlement confirming section and a display control section by executing the settlement management module 1522.

(3) Structure of terminal 120

Fig. 1 shows an example of a block diagram of the configuration of a terminal 120 according to the first embodiment. The terminal 120 is a terminal used by a selling user or a purchasing user on an electronic commerce transaction platform. The terminal 120 includes, for example, a display control module 1222, a transaction processing module 1223, a delay delegation module 1224, and a settlement processing module 1225. In addition, each process can be realized by machine learning or Artificial Intelligence (AI) within an implementable range.

Each module disclosed in fig. 1 is realized by cooperation with the processor 121, the memory 122, the storage 123, the input/output I/F124, the input device 125, the output device 126, and the transceiver 127 included in the terminal 120. For example, the display control module 1222, the transaction processing module 1223, the delay delegation module 1224, and the settlement processing module 1225 may be implemented by the processor 121 reading out and executing a program stored in the memory 123.

The display control module 1222 displays and controls a sales assistance screen, an electronic commerce transaction screen, a screen for delayed request for debt payment, a screen for confirmation of payment, and the like on a display device (for example, a touch panel) based on, for example, screen information received from the server 110A.

The display control module 1222 may display and control a screen for displaying information on the held item list received from the server 110A, and a screen for displaying the number of delay days and/or delay amount allowed when the product included in the held item list is sold.

The transaction processing module 1223 performs processing related to e-commerce transactions. For example, the transaction processing module 1223 is a selling user side, and executes processing for registering product information or processing for negotiating with a purchasing user about a sales product. The transaction processing module 1223 is a side of the purchasing user, and executes processing for browsing the offerings, selecting the offerings, and instructing various actions and settlement for the offerings.

The delayed delegation module 1224 executes processing of performing delayed delegation of liability repayment to the server 110A based on offerings sold by the selling user side. For example, the delayed delegation module 1224 may be responsive to operations of a selling user to send a delayed delegation of liability repayment via the transceiver 127 based on offerings at the time of sale or at the time of sale. The delay delegation module 1224 may acquire debt information on the selling user from the server 110A in response to an operation by the selling user, and may cause the display control module 1222 to perform display control on the screen.

The settlement processing module 1225 performs settlement of the occurred debt. For example, the terminal 120 controls to read a two-dimensional code of a store or the like, and to transmit settlement information including a settlement party ID, a debtor ID, an input amount of money, and the like included in the two-dimensional code to the server 110B via the transmitting/receiving unit 127.

The memory 123 stores a program executed by the terminal 120 according to the first embodiment, for example, a program for executing a process related to an electronic commerce transaction used by a selling user or a purchasing user, a process for assisting the repayment of debt used by the selling user, or the like. In addition, the program for executing the processing relating to the electronic commerce transaction and the program for executing the processing for assisting the debt payment may be different programs.

In addition, one or more processors 121 read out and execute the respective modules from the memory 122 as necessary. For example, the one or more processors 121 may be configured to include a display control unit, a transaction processing unit, a delay delegation unit, and a settlement processing unit by executing the display control module 1222, the transaction processing module 1223, the delay delegation module 1224, and the settlement processing module 1225, respectively.

< data example >

Data of the server 110A and the server 110B will be described with reference to fig. 4 to 6.

Fig. 4 is a diagram showing an example of user management data 1125 stored in the storage 113 or the memory 112 of the server 110A according to the first embodiment. In the user management data 1125, information about each user created by an operator and manager of the electronic commerce transaction platform is managed. The "user ID" contains user identification information for uniquely identifying the user by the server 110A. The user management data 1125 may include user information such as an address and a telephone number in addition to the "name" of the user.

The user management data 1125 includes, for example, debt information related to the debt of the user, account information such as electronic value or point held by the user, and credit score. The "debt information" may include, as information related to the debt possessed by the user, a debt ID for uniquely identifying the debt, a payment date and a payment amount of the debt determined by the debt ID. The "debt information" is updated by the debt information management module 1123 when a debt occurs, and is updated by the repayment processing module 1124 when debt repayment is performed, for example. In addition, the "credit score" is an index indicating the degree of credit of the user.

Fig. 5 is a diagram showing an example of the transaction management data 1126 stored in the memory 113 or the memory 112 of the server 110A according to the embodiment. The "offering ID" includes identification information for uniquely identifying the offering from the server 110A. The "selling user ID" includes a user ID of the selling user. The "product information" includes information on a delayed request for the sold product, a description of the product name and the sold product, a registration date of the sold product, and information on another product. The "selling price" includes a selling price at which the user determines the commodity is sold.

The "state" of the transaction management data 1126 includes the state of a transaction in an electronic commerce transaction. The status includes "in transaction" indicating that the transaction is currently in progress, "in engagement" indicating that the user is in engagement with the purchasing user, "completed" indicating that the transaction is completed, and so on. In the "transaction establishment date", a date of establishment of the transaction includes a date of occurrence of the profit. The "purchasing user ID" includes a user ID of a user who purchases the product.

In addition, the "allowance delay" of the transaction management data 1126 includes information on the presence or absence of an allowance delay indicating whether or not a liability delay is allowed based on the offering of the offering ID. The presence or absence of the allowable delay may further include an ID for specifying the debt of the allowable delay. The "delay days" and "delay amount" include the number of days for which delay is permitted and the amount of debt. The "allowed delay", "delay days", and "delay amount" are updated, for example, by the debt information management module 1123.

Fig. 6 is a diagram showing an example of the liability management data 1523 stored in the memory 153 or the memory 152 of the server 110B according to the embodiment. The "debt ID" contains identification information for uniquely identifying the debt by the server 110B. Identification information for identifying the user issued by the settlement operator is included in the "debtor ID". The "settlement party ID" is, for example, identification information for specifying a store read by a two-dimensional code or the like, and includes information issued by a settlement operator. The "debt amount", "debt occurrence date" and "payment date" include the amount of the debt determined by the debt ID, the occurrence date thereof and the payment date thereof. The "status" includes the repayment status of the debt. The status includes "complete" indicating that the redemption is complete, "incomplete" indicating that the redemption is not complete, and the like. Further, although not shown, identification information that can identify the calculation operator may be included.

< operation processing of the first embodiment >

The processing of the transaction system 1 according to the first embodiment will be described with reference to fig. 7.

(step S701)

The transaction processing module 1223 of the terminal 120A transmits a sales request for the sales item to the server 110A via the transmitting/receiving unit 127 together with the product information and the price of the sales item in accordance with the operation of the sales user. The commodity information includes, for example, image information of an article to be sold, a name of the article to be sold, and the like.

(step S702)

The sales management module 1122 of the server 110A performs a sales process of the sales item for which the sales order is received. For example, the transceiver 127 of the server 110A receives information on the sold item together with the sales order, and the sales management module 1122 sets a sales ID according to the sales order and stores the information on the sold item in the transaction management data 1126. In addition, the sales management module 1122 of the server 110A discloses the commodity information and the sales price on the electronic commerce transaction platform so that any user can browse.

(step S703)

The debt information management module 1123 of the server 110A determines whether to allow delayed repayment of debt based on the sold offerings, and stores into the transaction management data 1126. In this case, the debt information management module 1123 may also determine the delay number of days and/or delay amount based on the selling price or market price of the offering and the credit score of the selling user, and store into the transaction management data 1126. In addition, in the process of determining permission to extend the debt, it may also be determined that the extension of the debt is not permitted. In this case, the debt information management module 1123 may also store the meaning that extension of the debt is not allowed in the transaction management data 1126.

In addition, the debt information management module 1123 of the server 110A may also transmit the determination whether to allow the delayed repayment of the debt to the terminal 120A via the transceiver 117. In this case, when the debt information management module 1123 determines the number of delay days and/or the delay amount, the number of delay days and the delay amount may be transmitted to the terminal 120A via the transceiver unit 117.

(step S704)

The sales management module 1122 of the server 110A receives, via the transmitter/receiver unit 127, an operation performed on a sold item from the terminal 120B used by the purchase candidate user. The action may be browsing a sales page, registering a sales in a favorite, or giving a comment on a sales. The sales management module 1122 stores information on actions, such as the number of views of the sales page, the number of registered favorites of the sales, the number of comments, and/or the contents of the comments, in the transaction management data 1126.

(step S705)

The debt information management module 1123 of the server 110A determines the number of delay days and/or delay amount, for example, based on the action stored by the transaction management data 1126, and stores into the transaction management data 1126. In this case, the number of delay days and/or delay amount previously stored in the transaction management data 1126 may also be updated.

(step S706)

In step S706, the delayed delegation module 1224 of the terminal 120A transmits the delayed delegation of the liability repayment to the server 110A together with the offering ID according to the operation of the selling user. In this case, agreement may be made between the delay delegation module 1224 of the terminal 120A and the debt information management module 1123 of the server 110A on the repayment method and the repayment condition of the debt to be delayed. Further, the delayed delegation of the debt repayment may be sent simultaneously with the selling delegation (step S701).

(step S707)

The debt information management module 1123 of the server 110A performs processing related to delay of the debt payment. For example, the debt information management module 1123 may store the number of delay days and delay amount involved in the delay commitment into the transaction management data 1126. In addition, when the server 110B exists independently, the liability information management module 1123 of the server 110A may notify the server 110B of the fact that the delay delegation has been performed, the delay number of days and the delay amount involved in the delay delegation.

(step S708)

The liability information management module 1123 of the server 110A may perform processing for limiting the increase/decrease amount of the price of the sales cancelled and/or sold for the sales corresponding to the sales ID related to the delayed delegation, for example.

(step S709)

The debt information management module 1123 of the server 110A instructs the transceiver 117 to transmit a notification to the seller that the debt repayment has been performed based on the delayed delegation.

(step S710)

The selling management module 1122 of the server 110A mediates between the selling user and the purchasing user to perform a transaction process of the offerings. The sales management module 1122 can establish a transaction of an offering by executing processing provided by a known electronic commerce transaction platform.

(step S711)

The sales management module 1122 of the server 110A confirms the transaction management data 1126, and instructs the repayment processing module 1124 to execute repayment processing of the debt related to the delayed consignment when the commodity for which the transaction is established is the subject of the delayed consignment. Then, the repayment processing module 1124 refers to the transaction management data 1126 to perform a repayment process of dialling the benefit of the commodity for which the transaction is completed to the debt repayment.

The repayment processing module 1124 may control to transmit a request for performing the debt repayment processing to the server 110B via the transceiver 117 with respect to the debt generated in the server 110B outside the e-commerce transaction platform. The completed transaction may be the sale of the product to be sold, the payment of the product by the purchasing user, the notification of the receipt of the product by the purchasing user to the server 110A, or the completion of the evaluation by both the purchasing user and the selling user.

The present disclosure is not limited to the above-described embodiments, and may be implemented in other various forms without departing from the spirit and scope of the present disclosure. For example, the above-described processing steps may be arbitrarily changed in order or executed in parallel within a range where the processing contents do not contradict each other.

< example >

An example of the first embodiment is an example in which a product list including unsold products held by a selling user (hereinafter, simply referred to as "held product list") is acquired, and delay days and/or delay amounts allowed in a case where the products included in the held product list are sold are transmitted to the terminal 120A giving the selling user together with the held product list.

< effects of the embodiment >)

According to the embodiment, the selling user can easily know the own belongings and the number of delay days and/or delay amount after selling them before selling them. Therefore, sales on the electronic commerce transaction platform for the purpose of extending the debt payment date can be further promoted. Further, it is possible to have an incentive to register the product in the holding list.

< Structure of embodiment >

In the following description, the same components as those of the first embodiment are denoted by the same reference numerals, and description thereof is omitted. Note that the same operations and effects as those of the first embodiment will not be described. The following description focuses on differences from the first embodiment.

In this embodiment, the sales management module 1122 is able to create a holding list held by the selling user by extracting, from the transaction management data 1126, the goods that the selling user purchased and did not sell using the electronic commerce transaction platform. In addition, the sales management module 1122 may also receive unsold information about unsold items from the terminal 120A of the selling user, and create a held item list held by the selling user based on the unsold information. In this case, the sales management module 1122 can save information on the held item list to the user management data 1125.

Further, the debt information management module 1123 transmits the number of delay days and/or delay amount allowed when each product included in the holding item list is sold, together with the holding item list of the user, to the terminal 120A that gives the selling user.

Further, the debt information management module 1123 may delay the allowance of the debt repayment when an unsold product is added to the holding list. The number of delay days and the delay amount in this case may be determined based on information on the items included in the holding list, the number of items, and the like.

As a result, it is possible to promote the registration of the product with the holding item list as a preliminary stage of the sale, and as a result, it is possible to further promote the sale recognized by the electronic commerce transaction platform.

Action processing of embodiment >

The processing of the transaction system 1 according to the embodiment is explained with reference to fig. 8.

(step S801)

In this embodiment, after step S801 of the held object list creation process, the same procedure as in the first embodiment may be performed. Step S801 is a step before the sales order (S701). The sales management module 1122 of the server 110A creates a list of belongings of the user with reference to the transaction management data 1126. In addition, the sales management module 1122 may also receive unsold information about unsold commodities from the terminal 120A of the selling user, and create a held item list held by the selling user based on the unsold information.

(step S802)

The debt information management module 1123 of the server 110A creates data on the number of delay days and/or delay amount allowed in the case where each of the commodities included in the holding list is sold. In this case, the debt information management module 1123 can create data on the number of delay days and/or delay amount based on the market price of the goods, the credit score of the user.

(step S803)

The debt information management module 1123 of the server 110A instructs the transceiver 127 to transmit the data on the delay number of days and/or delay amount to the terminal 120A together with the held item list. Then, the display control module 1222 of the terminal 120A displays the control possessory list and the data related to the delay number of days and/or delay amount on the screen of the terminal 120A.

By the above processing, the number of delay days and/or the delay amount in the case of selling the product held by the user is notified, whereby the selling can be promoted. Further, the selling user can increase the chance of collecting the claim as the selling user obtains the sales amount, and thus the risk of failing to collect the claim can be reduced.

The manner in which delayed repayment of the debt corresponding to the selling user is allowed based on the selling price or market price of the offering and the credit score of the selling user is described above. Furthermore, the structure involved in the credit score is arbitrary. More specifically, it may be configured to allow delayed repayment of the debt corresponding to the selling user based on the selling price or market price of the offering without using the credit score.

< second embodiment >

The second embodiment is an embodiment in which, in the inter-user transaction system 1, financing based on the credit line of a sold item can be performed on a selling user by determining credit based on the selling price or market price of the sold item sold by a first user, i.e., the selling user, and the credit score of the selling user, and adding the credit to the credit line corresponding to the selling user.

Fig. 9 is a diagram for explaining the configuration of the transaction system according to the second embodiment. In this configuration, the transaction system 1 is constructed by the plurality of information processing apparatuses 200, for example, the terminal 120A of the selling user, the terminal 120B of the purchasing user, and the server 110A used by the operator and manager of the electronic commerce transaction platform. Further, the server 110A may also cooperate with the server 110B providing settlement services as needed to achieve financing. Further, as the server 110B, the same manner as the first embodiment may be employed.

In the example shown in fig. 9, a service of associating an electronic commerce transaction with financing is performed according to a procedure of selling an offering on an electronic commerce transaction platform, b granting credit based on the sold offering, c performing financing, d purchasing the offering, and e recovering a claim for the performed financing. Next, the flow of the service will be described.

(A. sell offerings on an e-commerce trading platform)

The selling user registers information and price of an offering desired to be sold to the electronic commerce transaction platform using the terminal 120A. Thus, the offerings will be sold on the e-commerce transaction platform. On the electronic commerce transaction platform, commodity information is disclosed, and any user can browse the commodity information.

(B. grant of credit based on offerings sold)

The server 110A determines the credit to be awarded for an offering based on the selling or market price of the offering and the credit score when the offering is sold. Here, credit is granted for each sold offering, and the selling user can accept financing within the limit of the total of credit granted for each sold offering (hereinafter, also referred to as "credit limit") that the selling user sells by himself.

The determination of credit may be made at predetermined times. For example, the server 110A may determine credit if an offering is sold or if an action is received from the terminal 120B used by the purchase candidate user on the sold offering. The action from the purchase candidate user may be any action as long as it is an action for the sold offering. By way of example and not limitation, a review may be registered, appended for a favorite for the offering being sold. Additionally, the server 110A may also determine credit if predetermined conditions are met. The predetermined conditions include, for example: the amount of the sales is equal to or greater than a predetermined value, the number of the sales in sale is equal to or greater than a predetermined value, or the number of the sales registered in the favorite is equal to or greater than a predetermined value.

(C, executing financing)

The selling user may use the terminal 120A to submit a financing commitment to the server 110A. According to the financing request, the server 110A performs the financing process. The financing method is not particularly limited, and for example, the server 110A may perform by issuing money equivalents usable on an electronic commerce transaction platform, and may also finance predetermined funds via an external system operated by other operator such as a financial institution.

(D. Purchase offerings)

The purchasing user browses the commodity information of the offerings sold on the electronic commerce transaction platform and determines the offerings to be purchased. For the transaction, a transaction process of a known electronic commerce transaction platform may be executed. This establishes the transaction, and executes the distribution process of the sold item and the payment process of the payment of the money.

(E. recovering the creditor against the financing performed)

The selling user who accepts the financing pays the debt before the predetermined period. The method of repayment of the debt is not particularly limited and may be performed according to the method determined at the time of financing delegation. For example, when the transaction of the sales is established, a part of the payment may be paid back to the debt, or the sales user who has received financing may pay back before a predetermined term regardless of the establishment of the transaction of the sales.

< effects of the second embodiment >

According to the second embodiment, the selling user can get credit based on the selling price or market price of the offering and the credit score of the selling user. Thus, for example, a selling user can accept financing through the sale of offerings. In addition, by granting credit to an offering, the right to debt to financing can also be reclaimed directly or indirectly from the sales of the offering. This reduces the risk of recovering the debt for the financing person.

< Structure of the second embodiment >

The configuration of the server 110A and the terminal 120 will be described with reference to fig. 10.

(1) Architecture of server 110A

Fig. 10 shows an example of a block diagram of the configuration of the server 110A according to the second embodiment. Server 110A performs processing related to financing services on an e-commerce transaction platform. The server 110A has, for example, a sales management module 1622, a credit granting module 1623, and a financing management module 1624. In addition, each process can be realized by machine learning or Artificial Intelligence (AI) within an implementable range.

Each module disclosed in fig. 10 is realized by cooperation with the processor 161, the memory 162, the storage 163, the input/output I/F164, the input device 165, the output device 166, and the transmitter/receiver 167, which are provided in the server 110A. For example, the sales management module 1622, credit granting module 1623, and financing management module 1624 may be implemented by the processor 161 reading and executing programs stored in the memory 163.

In fig. 10, the processor 161, the memory 162, the storage 163, the input/output I/F164, the input device 165, the output device 166, and the transmission/reception unit 167 correspond to the processor 111, the memory 112, the storage 113, the input/output I/F114, the input device 115, the output device 116, and the transmission/reception unit 117, respectively.

The sales management module 1622 sets an sales ID based on a sales request of the sales, and stores commodity information and a sales price transmitted by the sales user in the transaction management data 1626. The product information is information for specifying an article to be sold, such as an article image of the article to be sold captured by the selling user, and an article name input or selected by the selling user. In this case, the sales management module 1622 may determine a market price of the offering based on the transaction management data 1626 and save the market price thereof in the transaction management data 1626 in correspondence with the offering.

In addition, the sales management module 1622 may also calculate a credit score for the user using the e-commerce transaction platform based on the transaction management data 1626 and store the credit score in the user management data 1625. Here, the credit score of the user is an index indicating the credit degree of the user, and may vary depending on the user information and the action of the user. By way of example and not limitation, such credit scores may also be calculated based on user action information such as the number of trades, the number of trades evaluated, the proportion of good scores in the trades evaluated, and the speed of the trades. The credit score may be calculated by a known technique, or may include a known calculation element.

Next, the sales management module 1622 sells the offerings using the commodity information and the sales price held in the transaction management data 1626, and performs processing related to the electronic commerce transaction. For example, the sales management module 1622 opens the product information and executes a transaction of the sales item, and executes a process of intermediating between the sales user and the purchase user before the transaction is established. The sales management module 1622 determines that the transaction is established after receiving the agreement between the sales user and the purchasing user, and executes the settlement process.

The credit granting module 1623 determines the credit granted to the offering based on the offer price or market price of the offering and the credit score, and appends the credit to the line of credit corresponding to the selling user. More specifically, the credit granting module 1623 saves the determined credit to the transaction management data 1626 and updates the credit line in the user management data 1625. The credit may also be determined, for example, by multiplying the price of the offering by the credit rate. Here, the credit rate refers to a proportion of financable amount among prices of the offerings. For example, for 1 ten thousand yen offerings, a credit of 1000 yen is granted with a credit rate of 10%.

The timing at which the credit granting module 1623 determines credit is not particularly limited, and the credit granting module 1623 may also determine credit in the event that circumstances of the offerings change. For example, the sales may be sold, the purchase candidate user may receive an action on the sold sales, the sales price may be changed, or the scarcity of the sales may be changed. The credit granting module 1623 may adjust the credit rate at these occasions according to the sell expectation value of the offering to determine credit. The credit granting module 1623 may also update the credits stored in the transaction management data 1626 and update the credit line of the user management data 1625 if credits are determined at each opportunity.

For example, the credit granting module 1623 may also determine a credit based on the ease of sale (ease of sale) of a predetermined offering on the e-commerce transaction platform determined according to the market price of the offering and/or scarcity of the offering being sold, etc., in the case where the offering is sold. For example, in the case where the selling price of the offering is lower than the market price, the credit granting module 1623 may set the credit rate to be larger because the possibility that the offering is sold is high. In addition, in the case where the scarcity of the sold items is high, even in the case where the selling price of the sold items is higher than the market price, the credit granting module 1623 may set the credit rate to be large because the possibility of selling the sold items is high.

In addition, in the case where the credit score of the selling user is high, since the possibility that the transaction of the sales is established is high or since the reliability of the debt repayment of the selling user is high, the credit granting module 1623 may set the credit to be larger as the credit score of the selling user is higher. The setting of the credit may be automatically determined by the server 110A or the server 110B, or may be set by the first user.

Thereby, the credit can be determined more flexibly based on the reliability of the debt paid out by the selling user.

Additionally, the credit granting module 1623 may also re-determine the line of credit after the sale in the event that the market price, scarcity, or credit score of the offering has changed. Further, regarding the offering market price, scarcity of offerings, ease of sale of predetermined offerings on the e-commerce trading platform, the server 110A may also be determined based on current or past trading data of the trading management data 1626.

Additionally, the credit granting module 1623 may determine credit based on an action performed by the terminal 120B used by the purchase candidate user on the offerings being sold, if the action is performed. More specifically, credit may be determined based on the number of actions. The action may include, for example, browsing a sell page, registering the sell to a favorite, or giving a comment on the sell. The credit granting module 1623 may set the credit rate to be larger because the larger the browsing amount of the offering page, the registered amount of the favorite, or the comment amount, the higher the possibility that the offering will be sold. Additionally, credits may also be determined based on a ratio between the viewed quantity of the offering page and the favorite registered quantity of the offering or the number of comments given to the offering. More specifically, if the ratio of the number of registered favorites of the offering or the number of comments given to the offering is large with respect to the number of views on the offering page, the credit may be set higher than in the case where the ratio is low. This is because if the ratio of the number of registered favorites of the offering or the number of comments given to the offering is larger with respect to the number of views of the offering page, it can be estimated that the ratio of users whose purchase intention is high is larger.

The credit granting module 1623 may determine credit based on the content of the comment. For example, in the case of a sale containing a keyword such as "immediately … …", "thank you" which frequently appears immediately before the sale, the credit granting module 1123 may set the credit rate to be large because the possibility of the sale being sold is high.

In addition, since credit is granted for the offerings being sold, the credit granting module 1623 may cancel the credit granted for the offering in the event that the offering being sold is traded or the offer is cancelled. In addition, the credit granting module 1623 may also determine not to grant credit based on the offering in a case where the same merchandise is sold within a predetermined period after the sale of the offering is cancelled. In this case, the credit granting module 1623 may determine that the cancelled offering and the newly sold offering are the same item based on the similarity between the cancelled offering and the newly sold offering. Further, the credit granting module 1623 may perform a process of decreasing the credit score of the selling user in a case where the sale of the offering to which the grant of credit is related is cancelled after it is determined that the credit is granted.

Thereby, it is possible to avoid providing financing based on credit granted according to offerings that are not sold. In addition, on the premise of cancellation, the risk of carrying out selling for the purpose of credit granting can be reduced. In addition, the credit granting module 1623 allows a predetermined number of sales even in a case where the same merchandise is sold within a predetermined period after the sales of the offerings are cancelled, so that it is possible to suppress excessive limit of credit granting against a sales error due to a malfunction or the like.

The financing management module 1624 executes a process of providing financing for the selling user in accordance with the financing commission when the financing commission is acquired from the terminal 120A used by the selling user within the limit of the credit line of the first user. For example, the financing management module 1624 sets a financing ID for each financing commission, and saves financing-related information such as a sale ID corresponding to a financing amount and credit to be used, and repayment conditions, to the financing management data 1627. Thus, the selling user can collectively receive financing within a credit line that is the sum of credits for a plurality of offerings.

The financing management module 1624 may finance predetermined funds from a predetermined account to an account owned by the selling user via an external system operated by another operator such as a financial institution, or may provide financing to the selling user by issuing a money equivalent available on an e-commerce transaction platform.

In particular, financing is provided by currency or points available on the e-commerce transaction platform, thereby enabling the use of financed funds within the e-commerce transaction platform. Thus, through financing, an e-commerce transaction within the e-commerce transaction platform can be further activated.

In addition, financing management module 1624 may append reimbursement terms to the selling user when providing financing. For example, a date after a predetermined period has elapsed from the date of financing provision may be designated as a refund day, or a part or all of the financing amount may be refunded from the sales amount of the offerings for which credit has been granted.

Through the above process, the selling user can accept financing based on the credit granted to the offering. In addition, for the manager of the electronic commerce transaction platform, the sales amount from the user for financing can be increased. Further, since financing is provided based on the credit granted to the sold offerings, the creditability can be directly or indirectly recovered from the sales volume of the offerings. Therefore, the risk that the administrator of the electronic commerce transaction platform cannot recover the debt can be reduced.

Additionally, the credit granting module 1623 may also calculate an aggregate price for the offerings, for example, for a plurality of offerings sold by the selling user, and multiply by a predetermined credit rate to determine credit. Further, the aggregate amount of the calculated selling prices or the aggregate amount of the market prices may be limited to the offerings sold within a predetermined period. In this case, the timing of credit determination and the method of credit determination may be the same as those described above.

Thus, credit can be awarded even when the price of each of the offerings sold by the selling user is low and one offering cannot be individually awarded sufficient credit.

When financing is provided to the selling user, the financing management module 1624 may perform, as guarantee of the financing, processing of limiting an increase/decrease amount of the price of the selling item for which the selling is cancelled and/or sold with respect to a part or all of the selling items sold by the selling user. In addition, the increase or decrease of the selling price may be allowed within a predetermined amount or in a predetermined amount ratio. Further, in the event that the selling user tenders all or a portion of the financing amount, financing management module 1624 may free the limit of the amount of the increase or decrease to the price of the cancelled sale and/or the sold offering. When such restrictions are added or removed, financing management module 1624 may store information related to the restrictions in transaction management data 1626.

Thus, the selling user who receives financing can be restrained from avoiding repayment by canceling the selling and the like, and the risk that the administrator of the electronic commerce transaction platform cannot collect the debt can be reduced.

When financing is provided to the selling user, the financing management module 1624 may perform processing for requesting that a part or all of the offerings sold by the selling user be stored in a facility managed by the electronic commerce transaction platform and detecting storage of the offerings as a guarantee of the financing. Further, when the selling user pays back all or a part of the financing amount, the financing management module 1624 may perform a process of receiving a return request for returning the sales stored in the facility to the selling user. In this manner, when the offerings are kept or returned, the financing management module 1624 may also store information relating to the keeping or returning into the transaction management data 1626.

In this way, when financing is provided, by placing the offerings under the management of the selling user under the management of the electronic commerce transaction platform, it is possible to reduce the risk that the selling user does not send the offerings to the purchasing user and the like, which results in failure of the transaction. Therefore, for the manager of the e-commerce transaction platform, the risk that the debt cannot be recovered can be reduced.

Financing management module 1624 may perform a process of transferring a portion or all of the sales of the offering to the reimbursement of the financing in the event that the offering is traded.

Thus, the credit can be collected when the selling user obtains the sales amount, so that the manager of the electronic commerce transaction platform can reduce the risk that the credit cannot be collected. In addition, for the selling user, since the procedure of paying out the debt can be simplified, the trouble of paying out can be reduced.

The memory 163 stores, for example, a program executed by the server 110A according to the second embodiment, user management data 1625 for managing a user who is a member of the electronic commerce transaction platform, transaction management data 1626 for managing a transaction executed on the electronic commerce transaction platform, and financing management data 1627. These data will be described later.

In addition, one or more processors 161 read from memory 162 and execute the modules as needed. For example, the one or more processors 161 may constitute a sales management department, a credit granting department, and a financing management department by executing a sales management module 1622, a credit granting module 1623, and a financing management module 1624, respectively.

(2) Structure of terminal 120

Fig. 10 shows an example of a block diagram of the configuration of the terminal 120 according to the second embodiment. The terminal 120 is a terminal used by a selling user or a purchasing user on an electronic commerce transaction platform. The terminal 120 has, for example, a display control module 1421, a transaction processing module 1423, and a financing delegation module 1424. In addition, each process can be realized by machine learning or Artificial Intelligence (AI) within an implementable range.

Each module disclosed in fig. 10 is realized by cooperation with the processor 141, the memory 142, the storage 143, the input/output I/F144, the input device 145, the output device 146, and the transmission/reception unit 147 provided in the terminal 120. For example, the display control module 1422, the transaction processing module 1423, and the financing delegation module 1424 may be implemented by the processor 141 reading and executing programs stored in the memory 143.

In fig. 10, the processor 161, the memory 162, the storage 163, the input/output I/F164, the input device 165, the output device 166, and the transmission/reception unit 167 correspond to the processor 111, the memory 112, the storage 113, the input/output I/F114, the input device 115, the output device 116, and the transmission/reception unit 117, respectively.

The transaction processing module 1423 performs processing related to e-commerce transactions. For example, the transaction processing module 1423 is configured to execute a process of registering product information or a process of negotiating with a selling user about an article, as the selling user side. In addition, the transaction processing module 1423 performs processing for browsing the offerings, selecting the offerings, or instructing settlement, as the purchasing user side.

The financing delegation module 1424 performs processing of proposing a financing delegation to the server 110A based on a credit line granted to offerings sold by the selling user side. For example, the financing delegation module 1424 accesses the user management data of the server 110A to refer to information of credit line in response to the operation of the selling user. In addition, the financing delegation module 1424 may also transmit a display request of a selling list to the server 110A in response to an operation of the user, acquire the selling list displayed in correspondence with the selling item and the credit line granted to the selling item from the server 110A, and perform display control on the screen.

The financing delegation module 1424 then sends the financing delegation to the server 110A within the range of the credit line in response to the user's operation. In this case, the financing delegation module 1424 may transmit information on offerings granted credit for financing to the server 110A together with the financing amount to be delegated.

Thus, for example, when selling the offering a and the offering B, the selling user can select the offering subject to the restriction such as the cancellation of the sale. Therefore, convenience of management of offerings by the selling user is further improved.

The memory 143 stores a program executed by the terminal 120 according to the second embodiment. For example, a program or the like for executing processing related to an electronic commerce transaction used by a selling user or a purchasing user, processing for assisting financing and debt repayment used by a selling user may be stored. In addition, the program for performing the processing related to the e-commerce transaction and the program for performing the processing for assisting the financing and debt payment may be different programs.

Further, the one or more processors 141 read out and execute the respective modules from the memory 142 as necessary. For example, the one or more processors 141 may execute the display control module 1422, the transaction processing module 1423, and the financing delegation module 1424 to configure a display control unit, a transaction processing unit, and a financing delegation unit.

< data example >

Data of the server 110A will be described with reference to fig. 11 to 13.

Fig. 11 shows an example of user management data according to the second embodiment. In the user management data, information about each member user on the electronic commerce transaction platform is managed. The "user ID" contains user identification information for uniquely identifying the user by the server 110A. The "user information" includes "name", "address", "telephone number", and the like, which are personal information of the user. In addition, the "credit limit" may also include information relating to the total of credits that the user has. Further, "credit score" is an index indicating the degree of credit of the user.

Fig. 12 shows an example of the transaction management data 1126 according to the second embodiment. The "offering ID" includes identification information for uniquely identifying the offering from the server 110A. The "selling user ID" includes a user ID of the selling user. The "product information" includes a product name, a description of an article to be sold, and information relating to another article to be sold. The "amount" includes a selling price of the offering determined by the selling user. The "credit" includes credits of the respective offerings determined by the credit granting module 1623 of the server 110A. The "selling time" includes the time when the article is sold. The "state" includes a state of a transaction in an electronic commerce transaction. The status includes "in transaction" indicating that the current transaction is in progress, "in engagement" indicating that the user is in engagement with the purchasing user, "completed" indicating that the sale is completed, and so on. The "purchasing user ID" includes the user ID of the user who purchased the offering.

Fig. 13 shows an example of financing management data 1627 according to the second embodiment. The "financing ID" contains identification information for uniquely identifying the financing by the server 110A. The "selling user ID" includes the user ID of the selling user who proposed the financing delegation. The "financing amount" includes the amount financed for the financing request. The "offering ID" includes an offering ID of an offering to which a credit line used when a financing agreement is proposed is granted. The "financing time" includes the time when financing was performed. The "repayment condition" includes a repayment date, a repayment method, and the like. The "state" includes the state of financing in an electronic commerce transaction. The status includes "complete" indicating that the redemption is complete, "incomplete" indicating that the redemption is not complete, and the like.

The memory 142 may store account information such as electronic value and points held by the user in association with the user ID.

< operation processing of the second embodiment >

The processing of the transaction system 1 according to the second embodiment will be described with reference to fig. 14. Fig. 14 shows an example of a sequence of processing in the transaction system 1 according to the second embodiment. In the example of the sequence shown in fig. 14, the terminal 120A is a terminal used by the selling user to register commodity information or to issue a financing request, and the terminal 120B is a terminal used by the purchasing user.

(step S1401)

The transmitter/receiver 147 of the terminal 120A transmits a sales request for the sales item to the server 110A together with the product information and the price of the sales item according to the operation of the sales user. The commodity information includes, for example, image information of an article to be sold, a name of the article to be sold, and the like.

(step S1402)

The sales management module 1122 of the server 110A performs a sales process of the sales item for which the sales order is received. For example, the transceiver 167 of the server 110A receives the sales request, the product information, and the price of the sales item, and the sales management module 1122 sets the sales ID according to the sales request and stores the information on the sales item in the transaction management data 1126. In addition, the sales management module 1122 of the server 110A discloses the commodity information and the price on the electronic commerce transaction platform so that any user can browse.

(step S1403)

The credit granting module 1623 of server 110A determines the credit granted to the offerings sold and stores into the transaction management data 1126. For example, it may be mentioned that the credit is determined based on the market price of the offering of the category to which the offering belongs and/or the scarcity of the offering being sold. More specifically, the credit rate may be calculated based on the difference between the price of the sold item and the market price of the sold item, the scarcity of the sold item, or the expected value of the sold item, and the amount of money obtained by multiplying the price of the sold item by the credit rate may be used as the credit. In addition, instead of using the credit rate, credit may be determined directly from the price of the offering. Further, in determining credit to be granted, it may also be determined not to be credited. When the credit is determined based on the difference between the price of the sold item and the market price of the sold item, in the case where the price of the sold item is lower than the market price of the sold item, the credit rate may be set higher than in the case where the price of the sold item is higher than the market price of the sold item.

(step S1404)

The sales management module 1122 of the server 110A receives, via the transmitter/receiver unit 167, an operation performed on a sold item from the terminal 120B used by the user as a purchase candidate. As actions, browsing the offerings page, registering the offerings to favorites, or giving comments to the offerings may be included. The sales management module 1122 stores information on actions such as the number of views of the sales page, the number of registered favorites of the sales, the number of comments, and/or the contents of the comments in the transaction management data 1126.

(step S1405)

Credit granting module 1623 of server 110A determines credits based on actions stored by transaction management data 1126 and stores into transaction management data 1126. In this case, the credit line previously stored in the transaction management data 1126 may be updated to the credit line obtained after the credit determined in step S1405 is added.

(step S1406)

The financing delegation module 1424 of the terminal 120A transmits the financing delegation to the server 110A together with the financing amount and the offering ID having credit for financing, according to the operation of the selling user. In this case, it is possible to agree on a payback method and payback conditions for financing between the financing delegation module 1424 of the terminal 120A and the financing management module 1624 of the server 110A.

(step S1407)

The financing management module 1624 of the server 110A executes processing relating to financing in accordance with the financing request. For example, the transceiver 167 of the server 110A receives information on financing such as a financing request and a financing amount, and the financing management module 1624 sets a financing ID in accordance with the financing request and stores the information on financing in the financing management data 1627. Financing management module 1624 then performs financing. For example, the financing management module 1624 may finance predetermined funds from a predetermined account to an account owned by a selling user via an external system operated by another operator such as a financial institution, or may perform financing by issuing money or points available on an e-commerce transaction platform.

(step S1408)

The financing management module 1624 of the server 110A may perform processing for limiting the amount of cancellation of sales and/or increase or decrease of the price of sold offerings for offerings corresponding to the offerings ID stored in the financing management data 1627.

(step S1409)

The financing management module 1624 of the server 110A instructs the transceiver 167 to transmit a notification of completed financing to the selling user.

(step S1410)

The selling management module 1122 of the server 110A mediates between the selling user and the purchasing user to perform transaction processing of the offerings. The sales management module 1122 can establish a transaction of an offering by executing processing provided by a known electronic commerce transaction platform.

(step S1411)

Financing management module 1624 of server 110A performs a process of allocating a portion or all of the sales of the offering to the reimbursement for the financing. For example, if the payment is of electronic value, the creditor can be recovered by subtracting a value corresponding to the electronic value of the credit amount portion granted to the offering from the balance of the account of the selling user.

< example >

An example of the second embodiment is an example in which, together with information relating to repayment of financing, a notification recommending sale of an offering suitable for repayment is transmitted to a selling user who has received financing.

< effects of the embodiment >)

According to the embodiment, the seller who has received financing is urged to sell the offerings, so that the repayment can be assisted, and the manager of the electronic commerce transaction platform can reduce the risk of failing to recover the debt.

< Structure of embodiment >

In the following description, the same components as those of the second embodiment are denoted by the same reference numerals, and description thereof is omitted. Note that the same operations and effects as those of the second embodiment will not be described. The following description focuses on differences from the second embodiment.

In this embodiment, the financing management module 1624 of the server 110A performs processing of transmitting a notification of the recommended sale of offerings to the selling user who accepted financing. Here, the notification of the recommended sold item may include market price information of a product included in a held item list held by the selling user, information of a sold item for which a trade is easily established, and the like, from the viewpoint of financing.

In addition, the sales management module 1622 may also create a holding list held by the selling user by extracting, from the transaction management data 1626, goods that the selling user purchased and did not sell using the electronic commerce transaction platform. In addition, the sales management module 1622 may also receive unsold information about unsold commodities from the terminal 120A of the selling user, and create a held item list held by the selling user based on the unsold information. In this case, sales management module 1622 may also save information related to the holding list to user management data 1625.

Action processing of embodiment >

The processing of the transaction system 1 according to the embodiment is explained with reference to fig. 15.

In the embodiment, the steps up to step S1409 of financing processing may be the same as those of the second embodiment. Step S1501 is a step after financing processing. In step S1501, the financing management module 1624 of the server 110A refers to the financing management data 1627 to confirm the financing and repayment of the selling user who has accepted the financing. In this case, financing management module 1624 determines the remaining tender.

In step S1502, the financing management module 1624 of the server 110A determines information on offerings recommended to be sold to the selling user. For example, the financing management module 1624 determines market information and the transaction amount of a commodity included in the holding list of the selling user. Thus, it is possible to obtain market information useful for setting a price at the time of sale and a transaction amount as one index for evaluating the purchase easiness of sold commodities, with respect to commodities held by a selling user.

The financing management module 1624 may also refer to the transaction management data 1626 in addition to selling the commodities included in the user's holding list, and specify the category of the commodity with the large number of transactions and its market information, the category of the commodity with a short period from sale to purchase and its market information, and the like. Such information on the offerings is information on the offerings that are easily sold at the time of sale.

In step S1503, the financing management module 1624 of the server 110A instructs the transceiver 167 to collect information on the offerings recommended to be sold to the selling user and transmit the information to the terminal 120A.

By the above processing, the sales can be promoted by notifying the sales user of the product included in the held item list and the information on the easily sold item. The more the selling user sells the sales amount, the more the manager of the e-commerce transaction platform can increase the chance of recovering the debt, thereby reducing the risk that the debt cannot be recovered.

The manner in which delayed repayment of the debt corresponding to the selling user is allowed based on the selling price or market price of the offering and the credit score of the selling user is described above. Furthermore, the structure involved in the credit score is arbitrary. More specifically, it may be configured to allow delayed repayment of the debt corresponding to the selling user based on the selling price or market price of the offering without using the credit score.

As described above, the present invention is not limited to the above embodiments and examples, and various modifications can be made without departing from the spirit thereof. That is, the above embodiments are merely illustrative in any respect, and are not to be construed as restrictive.