System and method in electronic commerce from hand-held computer units

• US 20030014327A1
• Filed: 09/24/2002
• Published: 01/16/2003
• Est. Priority Date: 06/29/2001
• Status: Abandoned Application

• Current Assignee: Anoto Group AB
• Original Assignee: Anoto Group AB
• Inventors: Skantze, Kristofer
• Application Number:
  US10/183,389
• Publication Number:
  US 20030014327A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing

Abstract

A system for electronic commerce in a computer network (3) comprises a server unit (CH) which has a first interface with a plurality of first computers (SP), from which users are able to order services using hand-held computer units (1), and a second interface with a plurality of second computers (PP) which handle accounts that are associated with the users of the hand-held computer units. The server unit (CH) has access to a database (20) that for each user stores a user identifier, which indicates the identity of the user, and a computer network address associated with the user identity, the computer network address relating to one of the second computers (PP) that handles an account belonging to the user. The system also comprises a registration unit (RS) which is linked to the database (20) and which allows an association to be made in the database (20) between any computer network address and a given user identifier. Using this arrangement, a service provider that has one of the first computers (SP) is able to accept payment from any payment provider that has one of the second computers (PP), without the service provider needing to have any relationship with the payment provider in advance. A method for enabling financial transactions in such a computer network is also described.

Claims

1. A system for electronic commerce in a computer network (3), comprising a server unit (CH) which has a first interface with a plurality of first computers (SP), from which users are able to order services using hand-held computer units (1), and a second interface with a plurality of second computers (PP) which handle accounts that are associated with the users of the hand-held computer units, wherein the server unit (CH) has access to a database (20) that for each user stores a user identifier, which indicates the identity of the user, and a computer network address associated with the user identity, the computer network address relating to one of said plurality of second computers (PP) that handles an account belonging to the user, said system further comprising a registration device (RS) which is linked to the database (20) and which allows an association to be made in the database (20) between any computer network address and a given user identifier.

2. A system according to claim 1, in which the user identifier is a computer unit identifier that uniquely identifies the user'"'"'s hand-held computer unit (1).

3. A system according to claim 1, in which the user identifier is a digital certificate.

4. A system according to claim 1, in which at least one user identifier is associated in the database (20) with two different computer network addresses that relate to two different second computers (PP) that each handle an account belonging to the user and in which the server unit (CH) has access to conditions for the selection of the respective computer network address.

5. A system according to claim 4, in which the registration device (RS) allows inputting of said conditions into said system.

6. A system according to claim 1, in which the server unit (CH), in response to the receipt of a first message from one of the first computers (SP) and based on the database (20), is arranged to determine a computer network address of one of said plurality of second computers (PP) that handles an account belonging to the user, wherein the first message contains the user identifier that indicates the identity of a user who has ordered a service from the first computer from which the first message was received and an amount that the user is to pay for the service.

7. A system according to claim 6, in which the server unit (CH) is further arranged to send to the determined computer network address a request for approval of payment for the service ordered by the user, which request comprises the identity of the user who placed the order and the amount of the order, and to receive a result of the request for approval and to forward this to the first computer from which the first message was received.

8. A system according to claim 6, in which the server unit (CH) is arranged to send, when the computer network address has been determined, an approval to the first computer from which the message was received, and then to send to the determined computer network address a request for approval of payment for the service ordered by the user, which request comprises the identity of the user who placed the order and the amount of the order.

9. A method for enabling financial transactions in a computer network, comprising:

establishing registration agreements (A) between a transaction enabler (CH_e) and users of hand-held computer units (1) in the network;

establishing first transaction agreements (B) between the transaction enabler (CH_e) and service providers (SP_e) in the network; and

establishing second transaction agreements (C) between the transaction enabler (CH_e) and payment providers (PP_e) in the network;

wherein the users, when ordering services with the service providers (SP_e), are enabled to select a transaction enabler payment method, in which the transaction enabler (CH_e) controls the routing of debit signals and funds between the service providers (SP_e) and the payment providers (PP_e), based on the registration agreements (A) and the first and second transaction agreements (B, C).

10. A method according to claim 9, wherein the transaction enabler payment method includes:

the transaction enabler (CH_e) receiving a first debit signal from a service provider (SP_e), based on the first transaction agreement (B);

the transaction enabler (CH_e) sending a second debit signal to a payment provider (PP_e), based on the registration agreement (A) and the second transaction agreement (C); and

the transaction enabler (CH_e) controlling the transfer of funds from the payment provider (PP_e) to service provider (SP_e), based on the first and second transaction agreements (B, C).

11. A method according to claim 10, wherein the registration agreement (A) includes the user acknowledging an association, as registered with the transaction enabler (CH_e), between the user and one of the payment providers (PP_e);

and wherein the first transaction agreement (B) includes the transaction enabler (CH_e) acknowledging to transfer funds to each service provider (SP_e) in response to the first debit signal being verifiable with respect to the association.

12. A method according to claim 10, wherein the registration agreement (A) includes the user acknowledging an association, as registered with the transaction enabler (CH_e), between the user and one of the payment providers (PP_e);

and wherein the first transaction agreement (B) includes the transaction enabler (CH_e) acknowledging to transfer funds to each service provider (SP_e) in response to the first debit signal being verifiable with respect to the association and the second debit signal being verifiable at the payment provider given by the association.

13. A method according to claim 9, wherein the registration agreement (A) includes the user acknowledging an association, as registered with the transaction enabler (CH_e), between the user and one of the payment providers (PP_e).

14. A method according to claim 10, wherein the second transaction agreement (C) includes the payment provider (PP_e) accepting to receive the second debit signal and acknowledging to transfer funds in response to the second debit signal being verifiable by the payment provider (PP_e).

15. A method according to claim 14, wherein the second transaction agreement (C) includes the payment provider (PP_e) acknowledging to transfer the funds to the transaction enabler (CH_e).

16. A method according to claim 14, wherein the second transaction agreement (C) includes the payment provider (PP_e) acknowledging to transfer funds to an account specified in the second debit signal.

17. A method according to claim 9, wherein the transaction enabler payment method includes:

the service providers (SP_e) obtaining funds from the transaction enabler (CH_e) based on the first transaction agreements (B) and the registration agreements (A), the transaction enabler (CH_e) obtaining corresponding funds from the payment providers (PP_e) based on the second transaction agreements (C), and the payment providers (PP_e) debiting the users.

18. A method according to claim 9, wherein the registration agreement (A) includes the user acknowledging to handle the computer unit (1) as a payment instrument.

19. A method according to claim 9, wherein the transaction enabler (CH_e) collects a subscription fee from the users and/or the service providers (SP_e) and/or the payment providers (PP_e).

20. A method according to claim 9, wherein the transaction enabler (CH_e) collects a transaction fee for every use of the transaction enabler payment method.

21. A method according to claim 9, wherein the transaction fee is calculated as a percentage of the funds transferred to the service providers (SP_e).

22. A method according to claim 10, wherein the registration agreement (A) includes the user acknowledging an association, as registered with the transaction enabler (CH_e), between the user and one of the payment providers (PP_e).