Program, method, and information processing system

Abstract

The issue is that we are not able to provide convenient payment services using cryptocurrencies. [Solution] A program used in an information processing system consisting of a user terminal that can be operated by a user and a server, the program executing the following steps: a storage step in which the server stores crypto assets in a specified user wallet associated with the user; an allocation step in which the server assigns a contract related to the payment destination to the specified user wallet; a payment step in which the server makes a payment to a system provided by a payment service provider in response to receiving a payment request made by the user terminal; and a transfer step in which the server executes a process to transfer crypto assets corresponding to the payment from the user wallet based on the contract, without obtaining approval from the user for the withdrawal corresponding to the payment.

Description

[Technical Field]

[0001] The present disclosure relates to a program, a method, and an information processing system. [Background technology]

[0002] Credit card payment services using crypto assets are known. Patent Document 1 discloses a technology that provides a user-friendly wallet while ensuring the authenticity of transactions between wallets. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-030671 Summary of the Invention [Problem to be solved by the invention]

[0004] The issue is that we are not able to provide convenient payment services using cryptocurrencies. Therefore, the present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a highly convenient payment service using crypto assets. [Means for solving the problem]

[0005] A program used in an information processing system consisting of a user terminal operable by a user and a server, the program causing the server to execute the following steps: a storage step of storing crypto assets in a specified user wallet associated with the user; an allocation step of storing in the user wallet the address of a collateral contract associated with a specified payee as the transfer destination of the crypto assets; a payment step of making a two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment business operator in response to receiving a request for two-dimensional code payment made by the user terminal; and a transfer step of executing a process to transfer crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee as a transaction on a blockchain based on the collateral contract, without obtaining approval from the user for the withdrawal corresponding to the two-dimensional code payment. [Effects of the Invention]

[0006] According to the present disclosure, it is possible to provide a highly convenient payment service using crypto assets. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing the functional configuration of the system 1. [Figure 2] FIG. 2 is a block diagram showing the operation of the system 1. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of the server 10. [Figure 4] FIG. 2 is a block diagram showing the functional configuration of a user terminal 20. [Figure 5] FIG. 10 is a diagram showing the data structure of a user table 1012. [Figure 6] 10 is a flowchart showing the operation of an initial setting process. [Figure 7] FIG. 10 is a block diagram showing the operation of the initial setting process. [Figure 8] FIG. 10 is a sequence diagram showing the operation of the initial setting process. [Figure 9] 10 is a flowchart showing the operation of a card usage process. [Figure 10] FIG. 10 is a block diagram showing the operation of card usage processing. [Figure 11] FIG. 10 is a sequence diagram showing the operation of a card usage process. [Figure 12] 10 is a flowchart showing the operation of settlement processing A (first embodiment). [Figure 13] FIG. 10 is a block diagram showing the operation of settlement processing A (first embodiment). [Figure 14] FIG. 10 is a sequence diagram showing the operation of settlement processing A (first embodiment). [Figure 15] 10 is a flowchart showing the operation of settlement processing A (second embodiment). [Figure 16] FIG. 10 is a block diagram showing the operation of settlement processing A (second embodiment). [Figure 17] FIG. 10 is a sequence diagram showing the operation of settlement processing A (second embodiment). [Figure 18] 10 is a flowchart showing the operation of settlement processing A (third embodiment). [Figure 19] FIG. 10 is a block diagram showing the operation of settlement processing A (third embodiment). [Figure 20] FIG. 10 is a sequence diagram showing the operation of settlement processing A (third embodiment). [Figure 21] 10 is a flowchart showing the operation of a two-dimensional code use process. [Figure 22] FIG. 10 is a block diagram showing the operation of the two-dimensional code utilization process. [Figure 23] FIG. 10 is a sequence diagram showing the operation of a two-dimensional code use process. [Figure 24] 10 is a flowchart showing the operation of settlement processing B (first embodiment). [Figure 25] FIG. 10 is a block diagram showing the operation of settlement processing B (first embodiment). [Figure 26] FIG. 10 is a sequence diagram showing the operation of settlement processing B (first embodiment). [Figure 27] 10 is a flowchart showing the operation of settlement processing B (second embodiment). [Figure 28]FIG. 10 is a block diagram showing the operation of settlement processing B (second embodiment). [Figure 29] FIG. 10 is a sequence diagram showing the operation of settlement processing B (second embodiment). [Figure 30] 10 is a flowchart showing the operation of settlement processing B (third embodiment). [Figure 31] FIG. 10 is a block diagram showing the operation of settlement processing B (third embodiment). [Figure 32] FIG. 10 is a sequence diagram showing the operation of settlement processing B (third embodiment). [Figure 33] 10 is a flowchart showing the operation of a transfer process. [Figure 34] FIG. 10 is a block diagram showing the operation of a transfer process. [Figure 35] FIG. 10 is a sequence diagram showing the operation of a transfer process. [Figure 36] 10 is a flowchart showing the operation of a limit change process. [Figure 37] FIG. 10 is a block diagram showing the operation of limit change processing. [Figure 38] FIG. 10 is a sequence diagram showing the operation of a limit change process. [Figure 39] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all drawings describing the embodiments, common components are designated by the same reference numerals, and repeated description will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily a precise illustration.

[0009] <System 1 Configuration> The system 1 in the present disclosure is an information processing system that provides payment services (card payment and two-dimensional code payment) secured by crypto assets. The system 1 includes information processing devices, such as a server 10, a user terminal 20, a payment terminal 30, a blockchain 50, a third-party approval entity 60, a card system 70, and a two-dimensional code payment system 80, all connected via a network N. FIG. 1 is a block diagram showing the functional configuration of the system 1. As shown in FIG. FIG. 2 is a block diagram showing the operation of the system 1. FIG. 3 is a block diagram showing the functional configuration of the server 10. As shown in FIG. FIG. 4 is a block diagram showing the functional configuration of the user terminal 20. As shown in FIG.

[0010] Each information processing device is configured by a computer equipped with an arithmetic unit and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, user terminal 20, payment terminal 30, blockchain 50, third-party approval entity 60, card system 70, and two-dimensional code payment system 80, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted. In this disclosure, the card system 70 and two-dimensional code payment system 80 are collectively referred to as the payment system.

[0011] <Server 10 configuration> The server 10 is an information processing device that provides a payment service secured by crypto assets. Specifically, the payment service includes payment using a two-dimensional code such as a two-dimensional barcode, and card payment. The server 10 includes a storage unit 101 and a control unit 104 .

[0012] <Configuration of the storage unit 101 of the server 10> The storage unit 101 of the server 10 includes an application program 1011 and a user table 1012 .

[0013] User table 1012 is a table that stores and manages information about member users (hereinafter, "users") who use the service. When a user registers to use the service, the user's information is stored in a new record in user table 1012. This allows the user to use the service according to the present disclosure. The user table 1012 is a table having the user ID as a primary key and columns of the user ID, user name, user data, credit limit, registered cryptographic assets for payment, and unsettled balance. FIG. 5 is a diagram showing the data structure of the user table 1012. As shown in FIG.

[0014] The user ID is an item that stores user identification information for identifying a user. The user identification information is an item that is set with a unique value for each user. The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name. The user data includes information specific to the individual user and attribute information relating to the user's characteristics and background. The user's unique information includes information unique to the user, such as the user's date of birth (age), sex, and the like. The user's attribute information includes information such as the user's educational history (highest level of education, major, graduation year), occupation, work history, interests, place of residence, and language. The spending limit is an item that stores the upper limit set by the user for payments using cryptocurrency. This amount cannot be set to exceed the value of the cryptocurrency stored in the user wallet 501. The spending limit applies to the total amount used for card payments and two-dimensional code amount code payments. The registered payment cryptocurrency asset is an item that stores the type of cryptocurrency (token) that the user uses for payment. Multiple tokens can be registered, and the address and identifier of each cryptocurrency asset are saved. This information is referenced during asset management in the user wallet 501 and during payment processing in the card system 70 and two-dimensional code payment system 80. Cryptocurrency assets that are not registered in the registered payment cryptocurrency asset cannot be used for payment, but the user can freely deposit and withdraw them. The unsettled balance is an item that stores the amount of the user's card payment and two-dimensional code payment that has not yet been settled. This balance is the total amount of card payment and two-dimensional code payment made by the user with cryptocurrency minus the amount that has already been settled. The settlement contract 521 or collateral contract 522 references this value during periodic settlement processing and transfers the necessary funds. In addition, the unsettled balance is checked when the credit limit is changed, and the credit limit cannot be set to an amount lower than the unsettled balance.

[0015] The user table 1012 may include the following payment method setting items. The payment method settings are an item that stores the setting information for the payment methods available to the user. The user can select card payment only, 2D code payment only, or both payment methods. By default, both card payment and 2D code payment are enabled. This setting allows the user to control the payment method according to their own usage style. The 2D payment settings are items that store setting information specific to 2D code payments. Specifically, they include the selection of the 2D code generation method (fixed 2D code, dynamic 2D code), the authentication level for 2D code payments (requiring PIN entry, using biometric authentication), the 2D code payment limit (maximum amount per transaction, maximum amount per day), and automatic settlement settings for 2D code payments. These settings are managed independently of the card payment settings, allowing you to adjust the balance between convenience and security for 2D code payments. Payment history management is an item for separately managing the usage history of card payments and 2D code payments. It includes information on the payment type (card payment or 2D code payment), payment date and time, payment amount, merchant information, payment status (approved, rejected, waiting for settlement, settled), and in the case of 2D code payments, the type of 2D code used (static 2D, dynamic 2D, NFC). This information is referenced during settlement processing in the collateral contract 522 to transfer funds to the appropriate settlement destination depending on the payment type. It is also used to analyze user payment patterns and generate usage statistics by payment method.

[0016] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041. The control unit 104 executes an application program 1011 stored in the storage unit 101, thereby realizing each functional unit.

[0017] The user registration control unit 1041 performs processing to store information about users who wish to use the service according to the present disclosure in the user table 1012. The information stored in the user table 1012 is generated when a user opens a web page operated by a service provider from any information processing terminal, enters information into a predetermined input form, and transmits the information to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, completing the user registration. This allows the user stored in the user table 1012 to use the service. Before the user registration control unit 1041 registers the user information in the user table 1012, the service provider may conduct a predetermined examination to restrict whether or not the user is permitted to use the service. The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or may be automatically set by the user registration control unit 1041.

[0018] <Configuration of User Terminal 20> The user terminal 20 is an information processing device operated by a user who uses a service. The user terminal 20 may be, for example, a mobile terminal such as a smartphone or tablet, a stationary personal computer (PC) or a laptop PC, or a wearable terminal such as a head mounted display (HMD) or a wristwatch terminal. The user terminal 20 includes a storage unit 201 , a control unit 204 , an input device 206 , and an output device 208 .

[0019] <Configuration of the storage unit 201 of the user terminal 20> The storage unit 201 of the user terminal 20 includes a user ID 2011 , an application program 2012 , and an EOA wallet 2013 .

[0020] The user ID 2011 is the user's account ID. The user transmits the user ID 2011 from the user terminal 20 to the server 10. The server 10 identifies the user based on the user ID 2011 and provides the user with the service according to the present disclosure. The user ID 2011 includes information such as a session ID temporarily assigned by the server 10 to identify the user using the user terminal 20.

[0021] The application program 2012 may be stored in advance in the storage unit 201, or may be configured to be downloaded from a web server or the like operated by a service provider via a communication IF. The application programs 2012 include applications such as a web browser application. The application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the user terminal 20.

[0022] EOA Wallet 2013 (Externally Owned Account Wallet) is a software component for crypto asset management. This wallet controls Externally Owned Accounts (EOA) on the blockchain and serves as the foundation for users to securely interact with the system and the blockchain network.

[0023] <Configuration of the control unit 204 of the user terminal 20> The control unit 204 of the user terminal 20 includes an input control unit 2041 and an output control unit 2042. The control unit 204 executes an application program 2012 stored in the storage unit 201, thereby realizing each functional unit.

[0024] <Configuration of the input device 206 of the user terminal 20> The input device 206 of the user terminal 20 includes a camera 2061 , a microphone 2062 , a position information sensor 2063 , a motion sensor 2064 , and a touch device 2065 .

[0025] <Configuration of the output device 208 of the user terminal 20> The output device 208 of the user terminal 20 includes a display 2081 and a speaker 2082 .

[0026] <Configuration of payment terminal 30> The payment terminal 30 is an information processing device for performing credit card payments and two-dimensional code payments at credit card member stores and two-dimensional code payment member stores (general stores selling products, services, etc., websites, etc.). The payment terminal 30 may be, for example, a mobile terminal such as a smartphone or tablet, or may be a desktop personal computer (PC) or laptop PC. The payment terminal 30 is equipped with a camera 3061 or a two-dimensional code scanner, etc., and includes a function to read the two-dimensional code presented by the user, and a display 3081 for outputting a dynamic two-dimensional code including the payment amount and store information.

[0027] <Configuration of Blockchain 50> Blockchain is a system that implements distributed digital ledger technology. This system serves as the foundation for securely and transparently recording and managing cryptocurrency transactions and contract execution. Blockchain is maintained by multiple nodes and has a structure that makes it extremely difficult to tamper with.

[0028] <Configuration of Third-Party Approval Entity 60> The third-party approval entity 60 is an information processing device provided by a third party different from the business that provides the server. The third-party approval entity 60 is an approval authority that ensures the security and reliability of transactions in a credit card payment system secured by crypto assets. The third-party approval entity 60 provides additional approval for withdrawals of funds from the user wallet 501 and for operations throughout the system. The third-party approval entity functions as part of a multi-signature process to prevent fraudulent transactions and erroneous operations. The existence of this entity strengthens the security of the entire system and increases the trust of both users and businesses.

[0029] <Configuration of Card System 70> The card system 70 is an information processing device that provides traditional credit card services such as card issuance, transaction processing, authorization, and settlement. The card system 70 provides a secure payment environment by encrypting communications with affiliated stores and payment information, and detecting fraud.

[0030] <Configuration of two-dimensional code payment system 80> The two-dimensional code payment system 80 is an information processing device that provides two-dimensional code payment services such as payment processing, transaction authentication, and settlement using QR codes (registered trademark) and barcodes. The two-dimensional code payment system 80 provides a secure and high-speed payment environment, including communication with affiliated stores, encryption of payment information, real-time fraud detection, and instant payment processing.

[0031] <System 1 Operation> Each process of the system 1 will be explained below. FIG. 6 is a flowchart showing the operation of the initial setting process. FIG. 7 is a block diagram showing the operation of the initial setting process. FIG. 8 is a sequence diagram showing the operation of the initial setting process. FIG. 9 is a flowchart showing the operation of the card usage process. FIG. 10 is a block diagram showing the operation of the card usage process. FIG. 11 is a sequence diagram showing the operation of the card usage process. FIG. 12 is a flowchart showing the operation of the settlement process A (first embodiment). FIG. 13 is a block diagram showing the operation of the settlement process A (first embodiment). FIG. 14 is a sequence diagram showing the operation of the settlement process A (first embodiment). FIG. 15 is a flowchart showing the operation of the settlement process A (second embodiment). FIG. 16 is a block diagram showing the operation of the settlement process A (second embodiment). FIG. 17 is a sequence diagram showing the operation of the settlement process A (second embodiment). FIG. 18 is a flowchart showing the operation of the settlement process A (third embodiment). FIG. 19 is a block diagram showing the operation of the settlement process A (third embodiment). FIG. 20 is a sequence diagram showing the operation of the settlement process A (third embodiment). FIG. 21 is a flowchart showing the operation of the two-dimensional code utilization process. FIG. 22 is a block diagram showing the operation of the two-dimensional code utilization process. FIG. 23 is a sequence diagram showing the operation of the two-dimensional code utilization process. FIG. 24 is a flowchart showing the operation of the settlement process B (first embodiment). FIG. 25 is a block diagram showing the operation of the settlement process B (first embodiment). FIG. 26 is a sequence diagram showing the operation of the settlement process B (first embodiment). FIG. 27 is a flowchart showing the operation of the settlement process B (second embodiment). FIG. 28 is a block diagram showing the operation of the settlement process B (second embodiment). FIG. 29 is a sequence diagram showing the operation of the settlement process B (second embodiment). FIG. 30 is a flowchart showing the operation of the settlement process B (third embodiment). FIG. 31 is a block diagram showing the operation of the settlement process B (third embodiment). FIG. 32 is a sequence diagram showing the operation of the settlement process B (third embodiment). FIG. 33 is a flowchart showing the operation of the transfer process. FIG. 34 is a block diagram showing the operation of the transfer process. FIG. 35 is a sequence diagram showing the operation of the transfer process. FIG. 36 is a flowchart showing the operation of the limit change process. FIG. 37 is a block diagram showing the operation of the limit change process. FIG. 38 is a sequence diagram showing the operation of the limit change process.

[0032] <Initial setting process> The initial setting process is a process for performing initial settings when using the payment service according to the present disclosure. FIG. 6 is a flowchart showing the operation of the initial setting process. FIG. 7 is a block diagram showing the operation of the initial setting process. FIG. 8 is a sequence diagram showing the operation of the initial setting process.

[0033] <Overview of the initial setting process> The initial setting process is a series of steps including a user registration step, a user wallet creation step, a wallet information registration step, a payment cryptographic asset transfer step, a payment registration step, and a credit limit setting step.

[0034] <Details of the initial setting process> The initial setting process will be described in detail below.

[0035] <User registration steps> In step S101, the user operates the input device 206 of the user terminal 20 to execute the application program 2012 (hereinafter referred to as the user application) stored in the storage unit 201, and registers the user with the payment service provided by the server 10 according to the present disclosure. The control unit 104 of the server 10 stores the user information received from the user terminal 20 in the user name and user data fields of a new record in the user table 1012. This causes the user information to be stored in the server 10.

[0036] <User wallet generation steps> In step S102, the user application sends a signed request for wallet generation to the EOA wallet 2013. The EOA wallet 2013 sends a signed transaction for wallet generation to the Wallet Factory contract 531. The Wallet Factory contract 531 generates a new user wallet 501.

[0037] <Wallet information registration steps> In step S103, the generated user wallet 501 sends a webhook to the server 10 to notify the completion of generation. The control unit 104 of the server 10 completes the user registration including the information of the user wallet 501, and updates the corresponding record in the user table 1012. The server 10 notifies the user terminal 20 of the completion of registration.

[0038] <Payment cryptocurrency asset sending steps> In step S104, the control unit 104 of the server 10 executes a storing step of storing the crypto asset in a predetermined user wallet associated with the user. Specifically, the user sends (transfers) payment crypto assets to the created user wallet 501. The user performs a remittance operation via the user app and transfers the payment crypto assets from the EOA wallet 2013 to the user wallet 501. This operation causes the user wallet 501 to store the crypto assets for payment.

[0039] <Payment destination registration step> In step S105, the control unit 104 of the server 10 executes an allocation step of allocating the settlement contract related to the payee to a predetermined user wallet. Specifically, the user uses the user application to register a payee. The user application sends a signature request for payee registration to the EOA wallet 2013. The EOA wallet 2013 sends a signed transaction for payee registration to the user wallet 501. The user wallet 501 registers the payee and returns the result to the user application. The server 10 records the registered payee information in the registered payment cryptographic asset field of the corresponding record in the user table 1012.

[0040] <Steps for setting credit limit> In step S106, the user uses the user application to register a spending limit. The user application sends a signed request for spending limit registration to the EOA wallet 2013. The EOA wallet 2013 sends a signed transaction for spending limit registration to the user wallet 501. The user wallet 501 checks whether the spending limit is appropriate by comparing it with the current balance. Specifically, the spending limit cannot be set to exceed the value of the cryptocurrency stored in the user wallet 501. The server 10 registers the credit limit based on the check result and returns the result to the user application. The server 10 records the approved credit limit in the credit limit item of the corresponding record in the user table 1012. For details on the usage limit setting step, refer to the usage limit change process described below.

[0041] <Card usage processing> The card usage process is a process in which a user purchases goods or services with a credit card at a card member store (general store) or the like. FIG. 9 is a flowchart showing the operation of the card usage process. FIG. 10 is a block diagram showing the operation of the card usage process. FIG. 11 is a sequence diagram showing the operation of the card usage process.

[0042] <Card usage processing overview> The card usage process is a series of steps consisting of a payment initiation step, an available balance confirmation step, and a sales processing step.

[0043] <Card usage processing details> The card usage process will be described in detail below.

[0044] <Payment start steps> In step S301, the control unit 104 of the server 10 executes a payment step of making a card payment to a card system provided by a card payment business operator in response to receiving a request related to a card payment made by a user terminal. Specifically, the user operates the input device 206 of the user terminal 20 to execute the user application stored in the memory unit 201, and makes a card payment to purchase goods or services at a card member store such as a shop or website. The user performs a payment operation via a user application. The control unit 204 of the user terminal 20 transmits payment information to the payment terminal 30 of the affiliated store. The payment terminal 30 of the affiliated store transmits an authorization (credit) acquisition request to the card system 70 provided by the credit card payment service provider (VISA, MasterCard, JCB, etc.), including a user ID 2011 that can identify the user (the user ID 2011 includes information for identifying the credit card, such as the user's credit card number), the payment amount (the amount of the purchased item, such as a product or service), and other information necessary for credit card payment. The card system 70 transmits the received authorization acquisition request to the server 10. The control unit 104 of the server 10 receives and accepts the authorization acquisition request.

[0045] <Available Amount Check Step> In step S302, the payment step executes a step of making a card payment within the upper limit amount set in the upper limit amount setting step. Prior to the payment step, the control unit 104 of the server 10 executes an authorization acquisition step of receiving an authorization acquisition request based on a request related to card payment. Specifically, the control unit 104 of the server 10 searches the user ID field in the user table 1012 based on the received user ID 2011, and acquires the credit limit field. The control unit 104 of the server 10 compares the amount obtained by subtracting the unsettled balance from the credit limit with the current payment amount, and determines whether the payment is possible. Specifically, if the deducted amount is greater than the payment amount, it is determined that the payment is possible, and if the deducted amount is less than the payment amount, it is determined that the payment is not possible. If the control unit 104 of the server 10 determines that payment is possible, it requests the settlement contract 521 to temporarily lock the authorized amount. The settlement contract 521 temporarily locks the authorized amount in the user wallet 501. This prevents duplicate payments. Note that in the present disclosure, if a spending limit is set for the user, the balance in the user wallet 501 is not queried. This eliminates the need to query the user wallet, thereby improving the speed of card payment processing. The settlement contract 521 may be configured to check the balance of the user wallet 501. The control unit 104 of the server 10 confirms that the authorized amount has been successfully locked and sends a response including information indicating that payment is possible to the card system 70. The card system 70 sends a response including payment approval to the payment terminal 30 of the affiliated store. If the control unit 104 of the server 10 determines that the payment is not possible, it sends a response including information indicating that the payment is not possible to the card system 70. The card system 70 sends a response including a payment refusal to the payment terminal 30 of the affiliated store.

[0046] <Sales processing steps> In step S303, the settlement step executes a step of making a card settlement without referencing a predetermined user wallet if an upper limit amount has been set in the upper limit amount setting step. The control unit 104 of the server 10 executes a lockstep to lock the transfer of the crypto asset in the user wallet in response to the authorization acquisition request received in the authorization acquisition step. After the lockstep, the payment step executes a step of making a card payment. Specifically, the payment terminal 30 of the affiliated store sends a sales processing request to the card system 70. The card system 70 sends the received sales processing request to the server 10. The server 10 confirms the sales based on the sales processing request received from the card system 70. The server 10 updates the unsettled balance of the corresponding record in the user table 1012 to a new unsettled balance obtained by adding the current sales amount to the original unsettled balance. The server 10 requests the settlement contract 521 to lock the confirmed sales amount. The settlement contract 521 completely locks the temporarily locked authorization amount by the confirmed sales amount. The settlement contract 521 locks the confirmed sales amount in the user wallet 501, and the amount is reserved until settlement. This will enable secure and transparent payments using blockchain technology while maintaining the same convenience as regular cards. A temporary lock at the time of authorization and a complete lock after the sale is confirmed will enable proper management of funds and prevent duplicate payments.

[0047] <Two-dimensional code payment processing> The two-dimensional code payment process is a process in which a user purchases a product or service using a two-dimensional code at a two-dimensional code payment affiliated store (general store) or the like. This process supports multiple code formats, including 2D code model 2, EAN-128, NFC standards, and Bluetooth POS protocols, and can be used for both store-presented and consumer-presented payment methods. FIG. 21 is a flowchart showing the operation of the two-dimensional code payment process. FIG. 22 is a block diagram showing the operation of the two-dimensional code payment process. FIG. 23 is a sequence diagram showing the operation of the two-dimensional code payment process.

[0048] <Outline of 2D code payment processing> The two-dimensional code payment process is a series of steps consisting of a two-dimensional code payment start step, an available balance confirmation step, and a payment processing step. This 2D code payment process supports payment triggers in the following various code formats: 2D code model 2: Standard QR code format used in traditional 2D code payments EAN-128: A one-dimensional barcode format widely used for product identification and logistics management NFC standard: Payment by short-distance wireless communication using Near Field Communication technology Bluetooth POS protocol: Communication with store terminals using Bluetooth Low Energy (BLE) For each code format, the user terminal 20 and the payment terminal 30 acquire payment information using a corresponding reader function (camera 2061, NFC reader, Bluetooth module, etc.). The acquired payment information is sent to the server 10 in a unified format regardless of the code format.

[0049] <Details of 2D code payment processing> The two-dimensional code payment process will be described in detail below.

[0050] <Steps to start 2D code payment> In step S401, the control unit 104 of the server 10 executes a payment step to perform two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment operator in response to receiving a request for two-dimensional code payment made by a user terminal. Specifically, the user operates the input device 206 of the user terminal 20 to execute the user application stored in the memory unit 201, and makes a purchase of goods or services, etc. at a two-dimensional code payment affiliated store such as a store or website using the two-dimensional code payment method. The user performs a two-dimensional code payment operation via a user app. The control unit 204 of the user terminal 20 reads the two-dimensional code generated by the affiliated store's payment terminal 30, or presents the two-dimensional code generated by the user to the affiliated store's payment terminal 30. The affiliated store's payment terminal 30 sends a payment processing request to the two-dimensional code payment system 80 provided by the two-dimensional code payment business operator, including a user ID 2011 that can identify the user, the payment amount (the amount of the purchased item, such as a product or service), and other information necessary for two-dimensional code payment. The two-dimensional code payment system 80 sends the received payment processing request to the server 10. The control unit 104 of the server 10 receives and accepts the payment processing request.

[0051] Specifically, when a user uses the camera 2061 of the user terminal 20 to read a two-dimensional code displayed on the display 3081 of the payment terminal 30, the payment terminal 30 generates a dynamic two-dimensional code including the payment amount and store information and displays it on the display 3081. The user terminal 20 uses the camera 2061 to read the two-dimensional code and obtains the payment information. This method is called a store-presented method, in which the user initiates payment by scanning the two-dimensional code on the store's side. In the store-presented payment method, the payment terminal 30 generates a two-dimensional code including the payment amount and store information. The user terminal 20 reads the two-dimensional code, confirms the payment information, and then the user approves the payment. The user terminal 20 transmits a payment request including the read payment information and user ID 2011 to the payment terminal 30. Alternatively, the user terminal 20 may transmit the user ID 2011 and payment information directly to the two-dimensional code payment system 80. In the case of via the payment terminal 30, the payment terminal 30 transmits a payment request including the payment information and user ID 2011 received from the user terminal 20 to the two-dimensional code payment system 80. In the case of direct transmission, the user terminal 20 transmits a payment request including the payment information and user ID 2011 to the two-dimensional code payment system 80. In the store-presented payment method using the NFC standard, the payment terminal 30 writes payment information to an NFC tag or NFC-compatible device, and the NFC reader of the user terminal 20 reads the information. When using EAN-128, the payment terminal 30 generates a barcode containing the payment amount and store information, which is read by the camera 2061 of the user terminal 20. In the Bluetooth POS protocol, the payment terminal 30 broadcasts payment information using a BLE signal, which is received by the Bluetooth module of the user terminal 20.

[0052] Specifically, when a two-dimensional code displayed on display 2081 of user terminal 20 is read by camera 3061 of payment terminal 30, user terminal 20 generates a two-dimensional code including user identification information and payment amount information and displays it on display 2081. Payment terminal 30 reads the two-dimensional code using camera 3061 or a scanner, acquires user information, and then enters the payment amount to begin payment processing. This method is called the consumer-presented method, in which the user initiates payment by having the store scan their own two-dimensional code. In the consumer-presented type, the two-dimensional code generated by user terminal 20 contains user ID 2011, so when payment terminal 30 reads the two-dimensional code, payment terminal 30 identifies the user. Payment terminal 30 displays the read user information, and a store staff member inputs the payment amount via input device 306. After inputting the payment amount, payment terminal 30 combines the acquired user ID 2011 with the input payment amount to generate a payment processing request. In the consumer-presented payment method using the NFC standard, the NFC function of the user terminal 20 is used to send user identification information to the payment terminal 30, and the payment amount is entered at the payment terminal 30 to start the process. In the Bluetooth POS protocol, the user terminal 20 broadcasts user information using a BLE signal, which is received by the payment terminal 30, where the payment process is carried out after the amount is entered.

[0053] The payment terminal 30 of the affiliated store or the user terminal 20 transmits a payment processing request to the two-dimensional code payment system 80 provided by the two-dimensional code payment business operator, including a user ID 2011 that can identify the user, the payment amount (the amount of the purchased item such as a product or service), and other information necessary for two-dimensional code payment. The two-dimensional code payment system 80 transmits the received payment processing request to the server 10. The control unit 104 of the server 10 receives and accepts the payment processing request. The two-dimensional code payment process of the present disclosure may be used for payment by either a store-presented or consumer-presented method. The present disclosure may also be applied to any other two-dimensional code payment process. While typical store-presented and consumer-presented processes have been described above, the user ID 2011, payment terminal 30 identification information, payment amount, etc. may be transmitted from any information processing terminal, such as the user terminal 20 or the payment terminal 30, to the two-dimensional code payment system 80. The two-dimensional code payment process of the present disclosure may be applied to any type of two-dimensional code payment.

[0054] <Available Amount Check Step> In step S402, the payment step executes a step of performing two-dimensional code payment within the upper limit amount set in the upper limit amount setting step. Prior to the payment step, the control unit 104 of the server 10 executes a payment processing request receiving step of receiving a payment processing request based on a request related to two-dimensional code payment. Specifically, the control unit 104 of the server 10 searches the user ID field in the user table 1012 based on the received user ID 2011, and acquires the credit limit field. The control unit 104 of the server 10 compares the amount obtained by subtracting the unsettled balance from the credit limit with the current payment amount, and determines whether the payment is possible. Specifically, if the deducted amount is greater than the payment amount, it is determined that the payment is possible, and if the deducted amount is less than the payment amount, it is determined that the payment is not possible. If the control unit 104 of the server 10 determines that payment is possible, it requests the collateral contract 522 to temporarily lock the payment amount. The collateral contract 522 temporarily locks the payment amount in the user wallet 501. This prevents duplicate payments. Note that in this disclosure, if a spending limit is set for the user, the balance in the user wallet 501 is not queried. This eliminates the need to query the user wallet, thereby improving the speed of the two-dimensional code payment process. In addition, the collateral contract 522 may be configured to check the balance of the user wallet 501. The control unit 104 of the server 10 confirms that the payment amount has been successfully locked and sends a response including information indicating that payment is possible to the two-dimensional code payment system 80. The two-dimensional code payment system 80 sends a response including payment approval to the payment terminal 30 of the affiliated store. If the control unit 104 of the server 10 determines that payment is not possible, it sends a response including information indicating that payment is not possible to the two-dimensional code payment system 80. The two-dimensional code payment system 80 sends a response including a payment refusal to the payment terminal 30 of the affiliated store.

[0055] <Payment processing steps> In step S403, the payment step executes a step of performing two-dimensional code payment without referencing a predetermined user wallet if an upper limit amount has been set in the upper limit amount setting step. The control unit 104 of the server 10 executes a lockstep to lock the transfer of crypto assets in the user wallet in response to the payment processing request received in the payment processing request receiving step. The payment step executes a step of performing two-dimensional code payment after the lockstep. Specifically, the payment terminal 30 of the affiliated store sends a payment confirmation request to the two-dimensional code payment system 80. The two-dimensional code payment system 80 sends the received payment confirmation request to the server 10. The server 10 confirms the payment based on the payment confirmation request received from the two-dimensional code payment system 80. Server 10 updates the outstanding balance of the corresponding record in the user table 1012 to a new outstanding balance obtained by adding the current settlement amount to the original outstanding balance. Server 10 requests a lock on the settled amount for the collateral contract 522. The collateral contract 522 fully locks the temporarily locked settlement amount by the amount of the confirmed settlement amount. The collateral contract 522 executes a lock on the settled amount for the user wallet 501, thereby holding the amount in reserve until settlement. This enables the realization of a safe and highly transparent settlement utilizing blockchain technology while maintaining the same convenience as general two-dimensional code settlement. Appropriate management of funds and prevention of double spending can be achieved through the temporary lock at the time of settlement and the full lock after settlement confirmation.

[0056] <External system integration through SDK / API cooperation> This two-dimensional code settlement process is equipped with an SDK / API mechanism that enables cooperation with external applications (such as POS systems, e-commerce sites, subscription services, P2P money transfer functions within SNS, etc.). The external system can implement settlement processing using the following three API endpoints: · Payment instruction API: Receives a settlement request (parameters such as code type, payment target, amount, deadline, etc.) from the external system and registers a payment reservation with the collateral contract 522 · Status inquiry API: Responds in real time to inquiries from the external system regarding the settlement status (processing / approved / denied) and the settlement status (unpaid / settled) · Settlement processing API: Receives a settlement trigger from the external system and executes each embodiment of settlement processing B The control unit 104 of server 10 processes the settlement request received from the external system via the API internally in the same way as a request from the two-dimensional code settlement system 80. As a result, the external system can seamlessly implement a Slash collateralized post-payment settlement experience within its own application.

[0057] <Settlement Process A (First Embodiment)> The settlement process A (first embodiment) is a process for periodically transferring crypto assets from a user wallet in response to the user's use of card payment. Furthermore, when issuing a card, the user individually entrusts the business operator, the third-party approval entity, and the BIN sponsor with signing for the transfer of crypto assets in advance, which allows each entity to sign independently, ensuring security and transparency. FIG. 12 is a flowchart showing the operation of the settlement process A (first embodiment). FIG. 13 is a block diagram showing the operation of the settlement process A (first embodiment). FIG. 14 is a sequence diagram showing the operation of the settlement process A (first embodiment).

[0058] <Outline of Settlement Process A (First Embodiment)> The settlement process A (first embodiment) is a series of processes including a usage history inquiry step, a billing aggregation step, and a transfer step.

[0059] <Details of Settlement Process A (First Embodiment)> The settlement process A (first embodiment) will be described in detail below.

[0060] <Usage history inquiry step> In step S501A, the card system 70 sends a request for payment including the card usage history for a predetermined period to the server 10. The request includes the user ID of the user associated with the usage history (information identifying the user, in this disclosure, the user ID 2011).

[0061] In step S502A, the control unit 104 of the server 10 executes a billing totaling step of totaling, for each predetermined period, the billing amount according to the user's usage history of one or more card payments from the card system. Specifically, the control unit 104 of the server 10 searches the user ID field in the user table 1012 based on the user ID 2011 included in the received request, and acquires user information. The control unit 104 of the server 10 tally up billing data for each user based on the received usage history. The control unit 104 of the server 10 checks the usage history and the locked amount, and calculates the amount to be settled (usage fee) for the user's card usage over a specified period. Specifically, the control unit 104 of the server 10 calculates the amount to be settled by adding up the amounts of all transactions within a specified period (total transaction amount), subtracting the amount that has already been locked (the amount locked at the time of authorization), and adding any unprocessed amounts from past settlements. In the settlement process A (first embodiment) of the present disclosure, the control unit 104 of the server 10 does not send the user a message containing information to make payment by a predetermined payment due date. However, the control unit 104 of the server 10 may send the user a message containing information to make payment by a predetermined payment due date. In this case, the user can perform the settlement process without waiting for the settlement due date by the settlement process A (second embodiment) and settlement process A (third embodiment) described below.

[0062] <Relocation steps> In step S503A, the control unit 104 of the server 10 executes a transfer step that executes a process to transfer crypto assets corresponding to the card payment from the user wallet based on the settlement contract without obtaining approval from the user for the withdrawal corresponding to the card payment. The transfer step executes a step of transferring crypto assets from the user wallet in response to receiving approval from a third-party approval entity when transferring crypto assets from the user wallet. The transfer step executes a step of transferring crypto assets corresponding to the billing amount totaled in the billing totaling step from the user wallet to the business wallet of the business that provides the server. Specifically, when the payment due date arrives, the control unit 104 of the server 10 transfers the crypto asset to the deposit wallet using a joint signature (multi-sig method) with the private keys of the business operator, the third-party approval entity, and the BIN sponsor. In this case, the transfer cannot be made using a single signature with the private key of either the business operator or the third-party approval entity.

[0063] Specifically, when the payment due date arrives, the control unit 104 of the server 10 transfers the crypto asset to the deposit wallet using a joint signature (multi-sig method) with the private keys of the business (the business that operates and provides the information processing system 1 according to the present disclosure), the third-party approval entity, and the BIN sponsor. In this case, the transfer cannot be made using a single signature with the private key of either the business or the third-party approval entity.

[0064] The control unit 104 of the server 10 registers the settlement process including information such as the user ID 2011, the settlement amount, and the settlement date in the settlement contract 521. The control unit 104 of the server 10 transmits an approval request including detailed information of the settlement process to the third-party approval entity 60. The third-party approval entity 60 sends a request to the card system 70 to inquire about the amount of usage for the user. The card system 70 sends a response to the third-party approval entity 60 including the amount of usage for the user for the requested period.

[0065] The third-party approval entity queries the card system for the amount used for card payment in the payment step, and if the query result is consistent with the cryptocurrency to be transferred from the user wallet, outputs information indicating approval, and if it is not consistent, does not output information indicating approval. Specifically, the third-party approval entity 60 collates the information received from the card system 70 with the details of the settlement process received from the server 10 to confirm consistency. The third-party approval entity 60 confirms that the settlement period and settlement amount received from the server 10 match the usage period and usage amount received from the card system 70. In addition, the third-party approval entity may also confirm, to the extent possible, whether each piece of information about the transaction details (date and time, amount, affiliated store, etc.) received from the server 10 matches the usage details (date and time, amount, affiliated store, etc.) received from the card system 70. If the third-party approval entity 60 determines that the settlement processing information received from the server 10 and the information regarding usage received from the card system 70 are consistent, it sends a signature to the settlement contract 521. On the other hand, if the third-party approval entity 60 determines that there is no consistency, it does not sign the settlement contract 521. In this case, the third-party approval entity 60 may send information indicating the consistency (including the user ID 2011, the content of the inconsistency, a timestamp, etc.) to the server 10 and the card system 70.

[0066] When the clearing contract 521 receives the signature of the third-party approval entity 60, it sends a signature request to the server 10. The control unit 104 of the server 10 checks the details of the clearing process, confirms its legitimacy, and then generates a signature using the business's private key. The control unit 104 of the server 10 sends the generated signature to the clearing contract 521. The clearing contract 521 confirms that both the signature of the third-party approval entity 60 and the business's signature have been received, and verifies whether the multi-signature (joint signature) requirements are met.

[0067] The settlement contract 521 verifies the requirements for the joint signature, and if the signature confirmation is complete, executes a process to withdraw the usage fee from the user wallet 501. This process is performed without the user's explicit approval. This allows the user to realize a user-friendly card payment service that does not require the user to go through the trouble of approving the transfer of crypto assets for each card payment. In the present disclosure, in the transfer step, the user's crypto assets are transferred without presenting a screen for approving the transfer of crypto assets on the display 2081 of the user's user terminal 20, etc., and without receiving any input operation for approval on the screen. The settlement contract 521 verifies the requirements for the joint signature, and if the signature verification fails, issues an error event and sends a message including information indicating the details of the error to the server 10.

[0068] The settlement contract 521 selects the operator wallet, or the BIN sponsor's wallet if necessary, as the withdrawal destination based on the current situation (whether it is a normal settlement or a situation where funds need to be preserved by the BIN sponsor). Normally, the settlement contract 521 selects the operator wallet as the withdrawal destination. In a situation where funds need to be preserved by the BIN sponsor, the settlement contract 521 selects the BIN sponsor's wallet as the withdrawal destination.

[0069] A BIN sponsor is a financial institution or licensed entity that plays a central role in a card issuance program. The BIN sponsor owns a Bank Identification Number (BIN) assigned by an international card brand (e.g., Visa, Mastercard), which typically comprises the first six digits of the card number. The BIN sponsor is an organization that has no capital relationship with the business that provides the information processing system 1 disclosed herein or with the third-party approval entity, and is in a position to make independent decisions. The BIN sponsor has special authority when it determines that the right to claim settlement money needs to be preserved, and has the authority to transfer collateral crypto assets to the BIN sponsor's own wallet by co-signing (multi-sig) with the third-party approval entity. BIN sponsors enhance the security and reliability of the entire system.

[0070] The settlement contract 521 transfers crypto assets equivalent to the usage fee to the selected withdrawal destination. The settlement contract 521 generates a transaction on the blockchain and transmits it along with the source address (the address of the user wallet 501), the destination address (the selected withdrawal destination address), the transfer amount (the amount of crypto assets equivalent to the usage fee), and other transaction data (settlement information, timestamp, etc.). The settlement contract 521 monitors the status of the submitted transaction and waits until it is confirmed on the blockchain. After the transaction is included in a block and a certain number of block confirmations have passed, the settlement contract 521 determines that the transfer is complete. The settlement contract 521 updates the balance and settled record of the user wallet 501.

[0071] The settlement contract 521 sends information indicating the completion of the transfer process, including the user ID 2011, transfer amount, transfer destination address, transaction hash, timestamp, etc., to the server 10. The control unit 104 of the server 10 records the completion of the settlement process. The server 10 updates the current unsettled balance of the corresponding record in the user table 1012 to a new unsettled balance obtained by subtracting the current settlement amount (usage fee) from the current unsettled balance. This enables secure and highly transparent settlement processing using a multi-sig method based on the user's prior signature entrustment. The involvement of a third-party approval entity and a BIN sponsor ensures the legitimacy of the processing, while at the same time enabling flexible fund management. Furthermore, security and transparency are ensured by each entity signing independently.

[0072] <Settlement Process A (Second Embodiment)> The settlement process A (second embodiment) is a process in which the user pays the price with cryptographic assets at any timing according to the use of card payment by the user. Specifically, by the payment due date, the user transfers crypto assets equivalent to the usage fee from any wallet to a deposit wallet managed by the operator, BIN sponsor, and third-party approval entity using a multi-sig method. FIG. 15 is a flowchart showing the operation of the settlement process A (second embodiment). FIG. 16 is a block diagram showing the operation of the settlement process A (second embodiment). FIG. 17 is a sequence diagram showing the operation of the settlement process A (second embodiment).

[0073] <Outline of Settlement Process A (Second Embodiment)> The settlement process A (second embodiment) is a series of processes including a settlement registration step, a deposit step, a settlement clearing step, and a transfer step.

[0074] <Details of Settlement Process A (Second Embodiment)> The settlement process A (second embodiment) will be described in detail below.

[0075] <Payment registration steps> Step S501B is the same process as step S501A, and therefore the explanation will be omitted.

[0076] <Deposit Steps> In step S502B, the user selects to start the settlement process at any time (before the specified payment date) via the user application by operating the input device 206 of the user terminal 20. The control unit 104 of the server 10 checks the user's outstanding balance and transmits the amount to be settled to the user terminal 20, and the control unit 204 of the user terminal 20 presents the outstanding balance to the user. The user selects the cryptocurrency to be used for payment. The selected cryptocurrency is a cryptocurrency supported by the system. The user sends the selected cryptocurrency to a deposit wallet managed by the operator, BIN sponsor, and third-party authorization entity using a multi-sig method. The control unit 104 of the server 10 confirms receipt of the cryptocurrency in the deposit wallet. The confirmation process includes verifying the transaction, checking the accuracy of the deposit amount, checking the validity of the cryptocurrency used, etc. When the deposit is confirmed, the control unit 104 of the server 10 stores the deposit in association with the user. After confirming the deposit, the control unit 104 of the server 10 transmits a notification of the completion of the deposit to the user.

[0077] <Checkout Clear Step> In step S503B, the control unit 104 of the server 10 instructs the settlement contract 521 to clear the settlement data. Upon receiving the clear instruction, the settlement contract 521 checks all related data (user ID, deposit amount, deposit date and time, etc.). The settlement contract 521 checks the consistency between the amount of deposited cryptographic assets and the amount to be liquidated. If consistency is confirmed, the settlement contract 521 releases the temporary lock that was set on the user wallet 501. The settlement contract 521 updates the user's settlement status to "settled" and records information such as the settlement date and time and the settlement amount. The settlement contract 521 issues an event indicating the completion of the settlement data clearing on the blockchain. The settlement contract 521 notifies the control unit 104 of the server 10 of the completion of the settlement data clearing.

[0078] <Relocation steps> Step S504B is the same process as step S503A, and therefore the explanation will be omitted.

[0079] <Settlement Process A (Third Embodiment)> The settlement process A (third embodiment) is a process in which the user pays the price in cash at any timing according to the user's use of card payment. The user transfers the payment from their own bank account to the business operator's bank account by the due date. FIG. 18 is a flowchart showing the operation of the settlement process A (third embodiment). FIG. 19 is a block diagram showing the operation of the settlement process A (third embodiment). FIG. 20 is a sequence diagram showing the operation of the settlement process A (third embodiment).

[0080] <Outline of Settlement Process A (Third Embodiment)> The settlement process A (third embodiment) is a series of processes including a settlement registration step, a deposit step, and a settlement clearing step.

[0081] <Details of Settlement Process A (Third Embodiment)> The details of the settlement process A (third embodiment) will be described below.

[0082] <Payment registration steps> Step S501C is the same process as step S501A, and therefore the explanation will be omitted.

[0083] <Deposit Steps> In step S502C, the user selects to start the settlement process at any time (before the specified payment date) through the user application. The control unit 104 of the server 10 checks the user's outstanding balance and presents the amount to be settled to the user. The user transfers cash from their own bank account to the business's bank account (business account). The control unit 104 of the server 10 confirms the deposit into the business account. When the deposit in the business account is confirmed, the control unit 104 of the server 10 stores the deposit in association with the user's record. The control unit 104 of the server 10 sends a notification to the user that the deposit has been completed.

[0084] <Checkout Clear Step> Step S503C is similar to step S503B, and therefore a description thereof will be omitted.

[0085] In settlement process A (third embodiment), no direct transfer of crypto assets takes place. By using settlement contract 521, consistency between records on the blockchain and records in the conventional system can be maintained. Transparency and reliability of the entire system are ensured. Users can make payments using the familiar method of conventional bank transfer, so it is also suitable for users who are unfamiliar with handling crypto assets.

[0086] <Settlement Process B (First Embodiment)> Settlement process B (first embodiment) is a process for periodically transferring crypto assets from a user wallet in response to the user's use of two-dimensional code payment. This embodiment supports payment triggers using a variety of code formats, such as 2D code model 2, EAN-128, NFC standard, and Bluetooth POS protocol, and can be used for both customer-presented and store-presented payment methods. When users start using the 2D code payment service, they individually entrust the business operator, third-party approval entity, and BIN sponsor with signing for the transfer of crypto assets. This allows each entity to sign independently, ensuring security and transparency. FIG. 24 is a flowchart showing the operation of the settlement process B (first embodiment). FIG. 25 is a block diagram showing the operation of the settlement process B (first embodiment). FIG. 26 is a sequence diagram showing the operation of the settlement process B (first embodiment).

[0087] <Outline of Settlement Process B (First Embodiment)> The settlement process B (first embodiment) is a series of processes including a usage history inquiry step, a billing aggregation step, and a transfer step.

[0088] <Details of Settlement Process B (First Embodiment)> The settlement process B (first embodiment) will be described in detail below.

[0089] <Usage history inquiry step> In step S511A, the two-dimensional code payment system 80 sends a request for payment including the usage history of the two-dimensional code payment for a predetermined period to the server 10. The request includes the user ID of the user related to the usage history (information for identifying the user, in this disclosure, the user ID 2011).

[0090] In step S512A, the control unit 104 of the server 10 executes a billing totaling step of totaling, for each predetermined period, the billing amount according to the user's usage history of one or more two-dimensional code payments from the two-dimensional code payment system. Specifically, the control unit 104 of the server 10 searches the user ID field in the user table 1012 based on the user ID 2011 included in the received request, and acquires user information. The control unit 104 of the server 10 tally up billing data for each user based on the received usage history. The control unit 104 of the server 10 checks the usage history and the locked amount, and calculates the amount to be settled (usage fee) for the user's use of two-dimensional code payment for a specified period. Specifically, the control unit 104 of the server 10 calculates the amount to be settled by adding up the amounts of all transactions within a specified period (total transaction amount), subtracting the amount that has already been locked (the amount locked at the time of payment approval), and adding any unprocessed amounts from past settlements. In the settlement process B (first embodiment) of the present disclosure, the control unit 104 of the server 10 does not send the user a message including information to make payment by a predetermined payment due date. However, the control unit 104 of the server 10 may send the user a message including information to make payment by a predetermined payment due date. In this case, the user can perform the settlement process without waiting for the settlement due date by the settlement process B (second embodiment) and the settlement process B (third embodiment) described below.

[0091] <Relocation steps> In step S513A, the control unit 104 of the server 10 executes a transfer step in which the crypto asset corresponding to the two-dimensional code payment is transferred from the user wallet based on the collateral contract without obtaining approval from the user for the withdrawal corresponding to the two-dimensional code payment. The transfer step executes a step of transferring crypto assets from the user wallet in response to receiving approval from a third-party approval entity when transferring crypto assets from the user wallet. The transfer step executes a step of transferring crypto assets corresponding to the billing amount totaled in the billing totaling step from the user wallet to the business wallet of the business that provides the server. Specifically, when the payment due date arrives, the control unit 104 of the server 10 transfers the crypto asset to the deposit wallet using a joint signature (multi-sig method) with the private keys of the business operator, the third-party approval entity, and the BIN sponsor. In this case, the transfer cannot be made using a single signature with the private key of either the business operator or the third-party approval entity.

[0092] Specifically, when the payment due date arrives, the control unit 104 of the server 10 transfers the crypto asset to the deposit wallet using a joint signature (multi-sig method) with the private keys of the business (the business that operates and provides the information processing system 1 according to the present disclosure), the third-party approval entity, and the BIN sponsor. In this case, the transfer cannot be made using a single signature with the private key of either the business or the third-party approval entity.

[0093] The control unit 104 of the server 10 registers the settlement process including information such as the user ID 2011, the settlement amount, and the settlement date in the security contract 522. The control unit 104 of the server 10 transmits an approval request including detailed information of the settlement process to the third-party approval entity 60. The third-party approval entity 60 sends a request to the two-dimensional code payment system 80 to inquire about the amount used by the user. The two-dimensional code payment system 80 sends a response to the third-party approval entity 60 including the amount used by the user for the requested period.

[0094] The third-party approval entity queries the two-dimensional code payment system regarding the amount used for the two-dimensional code payment in the payment step, and if the query result is consistent with the cryptocurrency to be transferred from the user wallet, outputs information indicating approval, and if it is not consistent, does not output information indicating approval. Specifically, the third-party approval entity 60 collates the information received from the two-dimensional code payment system 80 with the details of the settlement process received from the server 10 to confirm consistency. The third-party approval entity 60 confirms that the settlement period and settlement amount received from the server 10 match the usage period and usage amount received from the two-dimensional code payment system 80. In addition, the third-party approval entity may also confirm, to the extent possible, whether each piece of information about the transaction details (date and time, amount, affiliated store, etc.) received from the server 10 matches the usage details (date and time, amount, affiliated store, etc.) received from the two-dimensional code payment system 80. If the third-party approval entity 60 determines that the settlement processing information received from the server 10 and the usage information received from the two-dimensional code payment system 80 are consistent, it sends a signature to the security contract 522. On the other hand, if the third-party approval entity 60 determines that there is no consistency, it does not sign the security contract 522. In this case, the third-party approval entity 60 may send information indicating the consistency (including the user ID 2011, the details of the consistency, a timestamp, etc.) to the server 10 and the two-dimensional code payment system 80.

[0095] When the collateral contract 522 receives the signature of the third-party approval entity 60, it sends a signature request to the server 10. The control unit 104 of the server 10 checks the details of the settlement process, confirms its legitimacy, and then generates a signature using the business's private key. The control unit 104 of the server 10 sends the generated signature to the collateral contract 522. The collateral contract 522 confirms that both the signature of the third-party approval entity 60 and the business's signature have been received, and verifies whether the multi-signature (joint signature) requirements are met.

[0096] The collateral contract 522 verifies the requirements for the joint signature, and if the signature confirmation is complete, executes a process to withdraw the usage fee from the user wallet 501. This process is performed without the user's explicit approval. This allows the user to realize a user-friendly two-dimensional code payment service that does not require the user to take the trouble of approving the transfer of crypto assets for each two-dimensional code payment. In the present disclosure, in the transfer step, the user's crypto assets are transferred without being presented with a screen for approving the transfer of crypto assets on the display 2081 of the user's user terminal 20, or the like, and without receiving any input operation for approval on the screen. The collateral contract 522 verifies the requirements for the co-signature, and if the signature verification fails, it issues an error event and sends a message to the server 10 containing information indicating the details of the error.

[0097] The collateral contract 522 selects the operator wallet, or if necessary, the BIN sponsor's wallet, as the withdrawal destination based on the current situation (normal settlement or a situation requiring BIN sponsored fund preservation). Normally, the collateral contract 522 selects the operator wallet as the withdrawal destination. In a situation requiring BIN sponsored fund preservation, the collateral contract 522 selects the BIN sponsor's wallet as the withdrawal destination.

[0098] A BIN sponsor is a financial institution or licensed entity that plays a central role in a two-dimensional code payment program. A BIN sponsor owns a payment identification number assigned by an international payment network. The BIN sponsor is an organization that has no capital relationship with the business that provides the information processing system 1 disclosed herein or with the third-party approval entity, and is in a position to make independent decisions. The BIN sponsor has special authority when it determines that the right to claim settlement money needs to be preserved, and has the authority to transfer collateral crypto assets to the BIN sponsor's own wallet by co-signing (multi-sig) with the third-party approval entity. BIN sponsors enhance the security and reliability of the entire system.

[0099] The collateral contract 522 transfers crypto assets equivalent to the usage fee to the selected withdrawal destination. The collateral contract 522 generates a transaction on the blockchain and sends it including the source address (the address of the user wallet 501), the destination address (the selected withdrawal destination address), the transfer amount (the amount of crypto assets equivalent to the usage fee), and other transaction data (settlement information, timestamp, etc.). The Collateral Contract 522 monitors the status of the submitted transaction and waits until it is confirmed on the blockchain. After the transaction is included in a block and a certain number of block confirmations have passed, the Collateral Contract 522 considers the transfer complete. The Collateral Contract 522 updates the balance and cleared records in the User Wallet 501.

[0100] The collateral contract 522 sends information indicating the completion of the transfer process, including the user ID 2011, transfer amount, transfer destination address, transaction hash, timestamp, etc., to the server 10. The control unit 104 of the server 10 records the completion of the settlement process. The server 10 updates the current unsettled balance of the corresponding record in the user table 1012 to a new unsettled balance obtained by subtracting the current settlement amount (usage fee) from the current unsettled balance. This enables secure and highly transparent settlement processing using a multi-sig method based on the user's prior signature entrustment. The involvement of a third-party approval entity and a BIN sponsor ensures the legitimacy of the processing, while at the same time enabling flexible fund management. Furthermore, security and transparency are ensured by each entity signing independently.

[0101] <Settlement Process B (Second Embodiment)> The settlement process B (second embodiment) is a process in which the user pays the price with cryptocurrency at any timing in response to the user's use of two-dimensional code payment. This embodiment allows users to choose to settle using stablecoins such as USDC from a separate non-custodial wallet, and constitutes one of the elements that structurally avoids the applicability of prepaid payment instruments. Specifically, by the payment due date, the user transfers crypto assets equivalent to the usage fee from any wallet to a deposit wallet managed by the operator, BIN sponsor, and third-party approval entity using a multi-sig method. FIG. 27 is a flowchart showing the operation of the settlement process B (second embodiment). FIG. 28 is a block diagram showing the operation of the settlement process B (second embodiment). FIG. 29 is a sequence diagram showing the operation of the settlement process B (second embodiment).

[0102] <Outline of Settlement Process B (Second Embodiment)> The settlement process B (second embodiment) is a series of processes including a settlement registration step, a deposit step, a settlement clearing step, and a transfer step.

[0103] <Details of Settlement Process B (Second Embodiment)> The settlement process B (second embodiment) will be described in detail below.

[0104] <Payment registration steps> Step S511B is the same process as step S511A, and therefore the explanation will be omitted.

[0105] <Deposit Steps> In step S512B, the user selects to start the settlement process at any time (before the specified payment date) via the user application by operating the input device 206 of the user terminal 20. The control unit 104 of the server 10 checks the user's outstanding balance and transmits the amount to be settled to the user terminal 20, and the control unit 204 of the user terminal 20 presents the outstanding balance to the user. The user selects the cryptocurrency to be used for payment. The selected cryptocurrency is one supported by the system. The user then sends the selected cryptocurrency to a deposit wallet managed by the operator, BIN sponsor, and third-party authorization entity using a multi-sig method. The control unit 104 of the server 10 confirms receipt of the cryptocurrency in the deposit wallet. The confirmation process includes verifying the transaction, confirming the accuracy of the deposit amount, and confirming the validity of the cryptocurrency used. When the deposit is confirmed, the control unit 104 of the server 10 stores the deposit in association with the user. After confirming the deposit, the control unit 104 of the server 10 transmits a notification of the completion of the deposit to the user.

[0106] <Checkout Clear Step> In step S513B, the control unit 104 of the server 10 instructs the collateral contract 522 to clear the settlement data. Upon receiving the clear instruction, the collateral contract 522 checks all related data (user ID, deposit amount, deposit date and time, etc.). The collateral contract 522 checks the consistency between the amount of deposited cryptocurrency and the amount to be cleared. If consistency is confirmed, the collateral contract 522 releases the temporary lock that was set on the user wallet 501. The collateral contract 522 updates the user's settlement status to "settled" and records information such as the settlement date and time and the settlement amount. The collateral contract 522 issues an event indicating the completion of the settlement data clearing on the blockchain. The collateral contract 522 notifies the control unit 104 of the server 10 of the completion of the settlement data clearing.

[0107] <Relocation steps> Step S514B is the same process as step S513A, and therefore a description thereof will be omitted.

[0108] <Settlement Process B (Third Embodiment)> The settlement process B (third embodiment) is a process in which the user pays the price in cash at any timing according to the user's use of two-dimensional code payment. This embodiment enables off-chain settlement using fiat, etc., and is an important component in structurally avoiding the applicability of prepaid payment instruments. The user transfers the payment from their own bank account to the business operator's bank account by the due date. FIG. 30 is a flowchart showing the operation of the settlement process B (third embodiment). FIG. 31 is a block diagram showing the operation of the settlement process B (third embodiment). FIG. 32 is a sequence diagram showing the operation of the settlement process B (third embodiment).

[0109] <Outline of Settlement Process B (Third Embodiment)> The settlement process B (third embodiment) is a series of processes including a settlement registration step, a deposit step, and a settlement clearing step.

[0110] <Details of Settlement Process B (Third Embodiment)> The details of the settlement process B (third embodiment) will be described below.

[0111] <Payment registration steps> Step S511C is the same process as step S511A, and therefore the explanation will be omitted.

[0112] <Deposit Steps> In step S512C, the user selects to start the settlement process at any time (before the specified payment date) through the user application. The control unit 104 of the server 10 checks the user's outstanding balance and presents the amount to be settled to the user. The user transfers cash from their own bank account to the merchant's bank account (merchant account). The control unit 104 of the server 10 confirms the deposit in the merchant account. When the control unit 104 of the server 10 confirms the deposit in the merchant account, it saves this deposit in association with the user's record. The control unit 104 of the server 10 sends a notice of deposit completion to the user.

[0113] <Settlement Clearance Step> Step S513C is the same as step S513B, so the description is omitted.

[0114] In the settlement process B (third embodiment), no direct transfer of crypto assets is performed. By using the collateral contract 522, the consistency between the records on the blockchain and the records in the conventional system can be maintained. The transparency and reliability of the entire system are ensured. Since the user can make payments in a familiar way like the conventional bank transfer, it can also accommodate users who are not familiar with handling crypto assets. Even in two-dimensional code settlement, while enjoying the convenience of settlement, settlement can be performed in the conventional payment method, and it is possible to provide services corresponding to a wide range of user groups. The collateral contract manages the consistency between the usage history of two-dimensional code settlement and the settlement record by cash, and achieves both the transparency by blockchain technology and the affinity with the conventional financial system. According to the first embodiment, second embodiment, and third embodiment of this settlement process B, by ensuring the freedom of choice of settlement means, it is established as a practical specification that does not fall under transaction businesses such as prepayment payment means and electronic payment means. Also, since it is a fund transfer based on the user's signature, the applicability of the fund transfer business is also structurally excluded.

[0115] <External System Integration by SDK / API Linkage> The settlement process B includes an SDK / API mechanism that enables linkage with external applications (such as POS systems, e-commerce sites, subscription services, P2P money transfer functions within SNS, etc.). External systems can implement a secured deferred payment experience within their apps by using three endpoints: a payment instruction API (sending parameters such as code type, payment target, amount, deadline, etc.), a status inquiry API (checking unpaid / settled status), and a settlement processing API (executing settlement triggers). The settlement processing API executes one of three modes in response to settlement requests from external systems: the first mode (regular automatic settlement), the second mode (cryptocurrency settlement at any time), or the third mode (cash settlement). The settlement results are notified to the external system via webhook or API, and are configured to be reflected in billing processing and UX updates. This allows for general-purpose infrastructure for deferred payment. Using the provided SDK, external systems can implement payment flows that support a variety of code formats (QR Code (registered trademark), NFC, EAN-128, Bluetooth POS, etc.) using a unified interface.

[0116] <Technological advantages independent of international brands> Settlement Process B does not rely on international card brand payment networks (such as VISA and MasterCard), and can build an independent infrastructure that achieves full integration with code payments such as QR / NFC. Autonomous settlement processing using collateral contract 522, decentralized governance using a multi-sig method, and decentralized management of payment records using a blockchain platform will realize a highly flexible payment UX that is not restricted by international card brand payment networks. This allows it to function as a comprehensive payment solution, covering in-store payments at convenience stores, code payments between individuals, and even API integration with D2C apps and SaaS.

[0117] <Transfer processing> The transfer process is a series of steps in which a user withdraws funds from the contract wallet (user wallet 501). This process consists of three main steps: a transfer instruction step, a balance check step, and a transfer step. FIG. 33 is a flowchart showing the operation of the transfer process. FIG. 34 is a block diagram showing the operation of the transfer process. FIG. 35 is a sequence diagram showing the operation of the transfer process.

[0118] <Transfer process overview> The transfer process is a series of steps including the user's withdrawal instruction, confirmation of the payment cryptocurrency assets and balance check, and the actual transfer of funds. During this process, the user wallet, EOA wallet, and withdrawal destination wallet work together.

[0119] <Relocation instruction steps> In step S701, the user performs a withdrawal operation from the user wallet 501 via the user application by operating the input device 206 of the user terminal 20. The user specifies the withdrawal destination wallet and the withdrawal amount via the user application by operating the input device 206 of the user terminal 20. The user application sends a signature request for the withdrawal operation to the EOA wallet 2013. The EOA wallet 2013 sends a signed transaction for the withdrawal operation to the user wallet 501.

[0120] <Balance check step> In step S702, the user wallet 501 checks whether the cryptographic asset for which withdrawal is requested is registered as a payment cryptographic asset. If it is registered as a payment cryptographic asset, the user wallet 501 checks whether the amount obtained by subtracting the requested withdrawal amount from the current balance is equal to or greater than the usage limit. If the check shows that the amount is below the usage limit, the user wallet 501 rejects the withdrawal and ends the process. If the user wallet 501 is not registered as a payment cryptographic asset, the user wallet 501 does not check the balance and proceeds to the next step.

[0121] <Relocation steps> In step S703, the user wallet 501 executes the withdrawal based on the result of the balance check step. If the withdrawal is approved, the user wallet 501 transfers the cryptographic assets to the specified destination wallet. After the transfer is complete, the user wallet 501 sends a withdrawal completion notification to the user application. The user application displays the withdrawal completion notification to the user. The settlement contract 521 records the completion of the transfer process and issues an event as necessary. The control unit 104 of the server 10 updates the balance information of the corresponding user in the user table 1012.

[0122] <Limit change processing> The limit change process is a process for setting the upper limit amount for card payments and two-dimensional code payments. FIG. 36 is a flowchart showing the operation of the limit change process. FIG. 37 is a block diagram showing the operation of the limit change process. FIG. 38 is a sequence diagram showing the operation of the limit change process.

[0123] <Overview of limit change processing> The limit change process is a series of steps consisting of a limit change operation step, a balance check, and a limit update step.

[0124] <Details of limit change processing> The limit change process will be described in detail below.

[0125] <Steps for changing limit> In step S901, the user operates the input device 206 of the user terminal 20 to change the spending limit via the user application of the user terminal 20. The user specifies a new spending limit. The user application sends a signature request for the limit change operation to the EOA wallet 2013. The EOA wallet 2013 sends a signed transaction for the limit change operation to the user wallet 501.

[0126] <Balance check step> In step S902, the user wallet 501 checks whether the requested new limit does not exceed the wallet balance. If the new limit exceeds the wallet balance, the change request is rejected and the user is notified. The user wallet 501 queries the settlement contract 521 for the outstanding amount. The settlement contract 521 checks the outstanding amount of the user and returns it to the user wallet 501. The user wallet 501 checks that the new limit is equal to or greater than the outstanding amount.

[0127] <Steps for updating limit> In step S903, if all checks in the balance check step are successful, the user wallet 501 sets a new spending limit. When the update is complete, the user wallet 501 sends a limit change completion notification to the user application. The user application displays the result of the limit change to the user. The settlement contract 521 records the completion of the limit change and issues an event as necessary. The control unit 104 of the server 10 updates the usage limit item of the corresponding user in the user table 1012. This limit change process allows users to flexibly manage their spending limits. It maintains consistency between wallet balances and outstanding balances, ensuring system security. Users can conveniently make card payments and two-dimensional code payments within the limit amount. Furthermore, since there is no need to query the user wallet when making card payments or two-dimensional code payments, the speed of card payment and two-dimensional code payment processing can be improved.

[0128] <Basic computer hardware configuration> 39 is a block diagram showing the basic hardware configuration of a computer 90. The computer 90 includes at least a processor 901, a main memory device 902, an auxiliary memory device 903, and a communication IF 991 (interface), which are electrically connected to one another by a communication bus 921.

[0129] The processor 901 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0130] The main storage device 902 is for temporarily storing programs, data to be processed by the programs, etc. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0131] The auxiliary storage device 903 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0132] The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using wired or wireless communication standards. The network is composed of the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi (registered trademark)) that can connect to the Internet via a predetermined access point. In the case of a wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), and Bluetooth (registered trademark). In the case of a wired connection, the network also includes a direct connection using a USB (Universal Serial Bus) cable, etc.

[0133] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration across multiple computers 90 and interconnecting them via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0134] <Basic functional configuration of computer 90> The following describes the functional configuration of a computer realized by the basic hardware configuration (FIG. 39) of the computer 90. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

[0135] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0136] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903, expanding them in the main storage device 902, and executing processing in accordance with the programs. The control unit can realize functional units that perform various types of information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0137] The functions performed by the components described herein may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes programs stored in memory. In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed herein or any hardware known to be programmed to realize or perform the described functions. If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

[0138] The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Furthermore, the processor 901 can allocate a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with the programs. Furthermore, the control unit can cause the processor 901 to execute processes for adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0139] A database refers to a relational database, which manages data sets called masters and tables in a tabular format structurally defined by rows and columns, by relating them to each other. In a database, a table is called a table, a master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated. Typically, each table and each master has a column set as a primary key to uniquely identify a record, but setting a primary key to a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in specific tables and masters stored in the storage unit according to various programs. Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

[0140] Note that the databases and masters in this disclosure may include any data structure in which information is structurally defined (such as a list, dictionary, associative array, or object). The data structure also includes data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

[0141] The communication unit is realized by the communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information to the control unit. The control unit can cause the processor 901 to execute information processing on the received information in accordance with various programs. In addition, the communication unit can transmit information output from the control unit to other computers 90.

[0142] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0143] (Appendix 1) A program used in an information processing system consisting of a user terminal operable by a user and a server, which causes the server to execute the following steps: a storage step (S104) of storing crypto assets in a specified user wallet associated with the user; an allocation step (S105) of storing in the user wallet the address of a collateral contract associated with a specified payee as the transfer destination of the crypto assets; a payment step (S401) of making a two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment business operator in response to receiving a request for two-dimensional code payment made by the user terminal; and a transfer step (S513) of executing a process to transfer crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee as a transaction on a blockchain based on the collateral contract, without obtaining approval from the user for the withdrawal corresponding to the two-dimensional code payment. This will enable the realization of a highly convenient two-dimensional code payment service using crypto assets. Specifically, it will enable the realization of a user-friendly two-dimensional code payment service that does not require users to go through the trouble of approving the transfer of crypto assets for each two-dimensional code payment.

[0144] (Appendix 2) The information processing system includes a third-party approval entity, which is an information processing device provided by a third party other than the operator providing the server, and the transfer step (S513) is a step of transferring crypto assets from the user wallet in response to receiving approval from the third-party approval entity when transferring crypto assets from the user wallet. This will improve the security and reliability of the system, and will enable detection of fraudulent transactions, incorrect operations, etc.

[0145] (Appendix 3) The third-party approval entity queries the two-dimensional code payment system for the amount used for the two-dimensional code payment in the payment step, and outputs information indicating approval if the query result is consistent with the cryptocurrency to be transferred from the user wallet, and does not output information indicating approval if it is not consistent, as described in Appendix 2. This will ensure that cryptocurrency transfers are carried out appropriately and improve the reliability of the system.

[0146] (Appendix 4) A program as described in Appendix 1, which causes a server to execute an upper limit amount setting step (S901) in which a user sets an upper limit amount for two-dimensional code payment, and a payment step (S402) in which two-dimensional code payment is made within the upper limit amount set in the upper limit amount setting step. This allows users to conveniently make two-dimensional code payments within the upper limit amount.

[0147] (Appendix 5) The program according to Appendix 4, wherein the payment step (S403) is a step of performing two-dimensional code payment without querying a specified user wallet when an upper limit amount is set in the upper limit amount setting step. This eliminates the need to query the user wallet, thereby improving the speed of two-dimensional code payment processing.

[0148] (Appendix 6) A program described in Appendix 1, which causes a server to execute, before a payment step, an authorization acquisition step (S402) of receiving an authorization acquisition request based on a request regarding two-dimensional code payment, and a lock step (S403) of locking the transfer of cryptocurrency in a user wallet in accordance with the authorization acquisition request received in the authorization acquisition step, wherein the payment step (S403) is a step of performing two-dimensional code payment after the lock step. This will improve the security of transactions and the reliability and stability of the system.

[0149] (Appendix 7) A program as described in Appendix 1, which causes a server to execute a billing aggregation step (S512) of aggregating billing amounts based on the user's usage history of one or more two-dimensional code payments from a two-dimensional code payment system at predetermined intervals, and a transfer step (S513) of transferring crypto assets from the user wallet based on the billing amounts aggregated in the billing aggregation step. Periodic billing aggregation allows multiple small transactions to be processed together, reducing the number of transactions on the blockchain and improving the efficiency and economy of the entire system.

[0150] (Appendix 8) The program described in Appendix 1, wherein the transfer step (S513) is a step of transferring crypto assets from the user wallet to the operator wallet of the operator that provides the server. This allows crypto assets to be transferred from a user wallet to a business wallet.

[0151] (Appendix 9) The information processing system includes a BIN sponsor, which is an information processing device provided by a party other than the operator that provides the server, and the transfer step (S513) is a step of transferring crypto assets from the user wallet in response to receiving approval from the BIN sponsor when transferring crypto assets from the user wallet, a program as described in Appendix 1. This will improve the security and reliability of the system, and will enable detection of fraudulent transactions, incorrect operations, etc.

[0152] (Appendix 10) A method executed by an information processing system consisting of a user terminal operable by a user and a server, the method comprising: a storage step (S104) in which the server stores crypto assets in a specified user wallet associated with the user; an allocation step (S105) in which a collateral contract associated with a specified payee as the transfer destination of the crypto assets is stored in association with the user wallet; a payment step (S401) in which, in response to receiving a request for two-dimensional code payment made by the user terminal, a two-dimensional code payment is made to a two-dimensional code payment system provided by a two-dimensional code payment business; and a transfer step (S513) in which, without obtaining approval from the user for the withdrawal corresponding to the two-dimensional code payment, a process is executed to transfer crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee based on the collateral contract as a transaction on a blockchain. This will enable the realization of a highly convenient two-dimensional code payment service using cryptocurrencies.

[0153] (Appendix 11) An information processing system comprising a user terminal operable by a user and a server, wherein the server comprises: a storage means (S104) for storing crypto assets in a specified user wallet associated with the user; an allocation means (S105) for storing a collateral contract associated with a specified payee as the transfer destination of the crypto assets in association with the user wallet; a payment means (S401) for making a two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment business operator in response to receiving a request for two-dimensional code payment made by the user terminal; and a transfer means (S513) for executing a process to transfer crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee as a transaction on a blockchain based on the collateral contract, without obtaining approval from the user for the withdrawal corresponding to the two-dimensional code payment. This will enable the realization of a highly convenient two-dimensional code payment service using cryptocurrencies. [Explanation of symbols]

[0154] 1 System, 10 Server, 101 Memory Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 User Terminal, 201 Memory Unit, 204 Control Unit, 206 Input Device, 208 Output Device, 30 Payment Terminal, 301 Memory Unit, 304 Control Unit, 306 Input Device, 308 Output Device, 50 Blockchain, 501 Memory Unit, 504 Control Unit, 506 Input Device, 508 Output Device, 60 Third-Party Approval Entity, 601 Memory Unit, 604 Control Unit, 606 Input Device, 608 Output Device, 70 Card System, 80 Two-Dimensional Code Payment System, 701 Memory Unit, 704 Control Unit, 706 Input Device, 708 Output Device

Claims

1. A program used in an information processing system comprising a user terminal operable by a user and a server, The server, a storing step of storing the crypto asset in a predetermined user wallet associated with the user; An allocation step of storing in the user wallet the address of a collateral contract associated with a predetermined payee as a transfer destination of crypto assets; a payment step of performing a two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment business operator in response to receiving a request related to the two-dimensional code payment made by the user terminal; a transfer step of executing a process of transferring crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee as a transaction on a blockchain based on the collateral contract without obtaining approval for withdrawal corresponding to the two-dimensional code payment from the user; A program to execute.

2. the information processing system includes a third-party approval entity that is an information processing device provided by a third party different from the business that provides the server, The transfer step is a step of transferring the crypto asset from the user wallet in response to receiving approval from the third-party approval entity when transferring the crypto asset from the user wallet. The program according to claim 1.

3. The third-party approval entity inquires with the two-dimensional code payment system about the amount of the two-dimensional code payment used in the payment step, and outputs information indicating approval if the inquiry result is consistent with the cryptocurrency to be transferred from the user wallet, and does not output information indicating approval if the inquiry result is inconsistent. The program according to claim 2.

4. The server, an upper limit amount setting step in which the user sets an upper limit amount for the two-dimensional code payment; Execute The payment step is a step of performing a two-dimensional code payment within the upper limit amount set in the upper limit amount setting step. The program according to claim 1.

5. the payment step is a step of performing a two-dimensional code payment without referencing the predetermined user wallet when an upper limit amount is set in the upper limit amount setting step; The program according to claim 4.

6. The server, an authorization acquisition step of receiving an authorization acquisition request based on the request related to the two-dimensional code payment before the payment step; a lock step of locking the transfer of the crypto asset in the user wallet in response to the authorization acquisition request received in the authorization acquisition step; Execute The payment step is a step of performing the two-dimensional code payment after the lock step. The program according to claim 1.

7. The server, a billing aggregation step of aggregating, for each predetermined period, billing amounts according to the user's usage history of one or more two-dimensional code payments from the two-dimensional code payment system; Execute The transfer step is a step of transferring crypto assets corresponding to the billing amount totaled in the billing totaling step from the user wallet. The program according to claim 1.

8. The transfer step is a step of transferring crypto assets from the user wallet to a business wallet of a business that provides the server. The program according to claim 1.

9. the information processing system includes a BIN sponsor, which is an information processing device provided by a party different from the business providing the server; The transfer step is a step of transferring crypto assets from the user wallet in response to receiving approval from the BIN sponsor when transferring crypto assets from the user wallet. The program according to claim 1.

10. A method executed by an information processing system including a user terminal operable by a user and a server, The server: a storing step of storing the crypto asset in a predetermined user wallet associated with the user; an allocation step of storing a collateral contract associated with a predetermined payee as a transfer destination of crypto assets in association with the user wallet; a payment step of performing a two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment business operator in response to receiving a request related to the two-dimensional code payment made by the user terminal; a transfer step of executing a process of transferring crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee as a transaction on a blockchain based on the collateral contract without obtaining approval for withdrawal corresponding to the two-dimensional code payment from the user; To execute method.

11. An information processing system comprising a user terminal operable by a user and a server, The server: A storage means for storing crypto assets in a predetermined user wallet associated with the user; An allocation means for storing a collateral contract associated with a predetermined payee as a transfer destination of crypto assets in association with the user wallet; A payment means for performing a two-dimensional code payment to a two-dimensional code payment system provided by a two-dimensional code payment business operator in response to receiving a request for two-dimensional code payment made by the user terminal; a transfer means for executing a process of transferring crypto assets corresponding to the two-dimensional code payment from the user wallet to the specified payee as a transaction on a blockchain based on the collateral contract, without obtaining approval for the withdrawal corresponding to the two-dimensional code payment from the user; Equipped with Information processing system.

Images