One-Card Transaction Management System

• US 20110011931A1
• Filed: 07/14/2009
• Published: 01/20/2011
• Est. Priority Date: 07/14/2009
• Status: Abandoned Application

• Current Assignee: FideliSoft, Inc.
• Original Assignee: FideliSoft, Inc.
• Inventors: Farley, Pierre, Vienneau, Marcel
• Application Number:
  US12/503,032
• Publication Number:
  US 20110011931A1
• Time in Patent Office: Days
• US Class Current: 235/382.5
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

A transaction management system enabling a user to perform a transaction using a neutral card at a point-of-sale unit in communication with a central server via a system network is provided. The system includes a terminal application at the point-of-sale unit and a data storage module connected to the central server, having a user profile corresponding to the neutral card. The user profile is linked to a plurality of transaction accounts and defines one or more specification for each transaction account linked thereto, each specification being associated to a weight. The system further including a server application at the central server for associating the card information to the corresponding user profile, generating one or more transaction scenario based on the transaction data and the weight of each specification of each transaction account linked to the user profile, and transmitting the transaction scenario(s) to the point-of-sale unit.

Claims

1. A transaction management system for enabling a user to perform a transaction using a neutral card at a point-of-sale unit in communication with a central server via a system network, the neutral card bearing card information, the system comprising:

a terminal application at the point-of-sale unit for inputting said card information, inputting transaction data related to said transaction, forwarding said card information and transaction data to the central server, receiving at least one transaction scenario from the central server, presenting said at least one transaction scenario to the user, inputting a user selection of one of the at least one transaction scenario, thereby defining a selected scenario, and forwarding said selected scenario to the central server for completing the transaction based thereon;

a data storage module connected to said central server and comprising a user profile corresponding to said neutral card, the user profile being linked to a plurality of transaction accounts, the user profile comprising at least one specification for each transaction account linked thereto, each specification being associated to a weight; and

a server application at the central server for associating the card information to the corresponding user profile, generating the at least one transaction scenario based on the transaction data and the weight of each specification of each transaction account linked to the user profile, and transmitting the at least one transaction scenario to the point-of-sale unit.

2. The transaction management system according to claim 1, wherein the point-of-sale unit comprises at least one point-of-sale device, which is selected from the group consisting of a payment terminal, a PINpad, a cash register, an integrated cash register system, a computer and a mobile phone.

3. The transaction management system according to claim 2, wherein the terminal application is distributed on at least one point-of-sale device.

4. The transaction management system according to claim 1, wherein the card information comprises at least one of a unique identification code and an authentication code associated with the neutral card.

5. The transaction management system according to claim 4, wherein the authentication code is at least one of a PIN, a password, fingerprint data, voice authentication data and retinal authentication data.

6. The transaction management system according to claim 4, wherein the authentication code is associated with said transaction accounts linked to the user profile.

7. The transaction management system according to claim 1, wherein the transaction data comprises at least one of an amount, a transaction type, transaction account data and point-of-sale data.

8. The transaction management system according to claim 1, wherein at least a portion of the card information, the transaction data and the selected scenario forwarded to the central server is encrypted.

9. The transaction management system according to claim 1, wherein the server application comprises a validation server module for validating at least a portion of the card information and transaction data.

10. The transaction management system according to claim 1, wherein each of the at least one transaction scenario comprises at least one transactional operation for debiting from or crediting to one of the transaction accounts associated with the user profile, the transactional operations being selected from a group consisting of a payment, a reimbursement, a loyalty value earning, a loyalty value redemption, a credit value, an insurance coverage, an insurance claim and a discount.

11. The transaction management system according to claim 1, wherein each of said transaction accounts is selected from the group consisting of a credit card account, a debit card account, a loyalty card account, a discount card account, a token card account, a store value card account, an insurance account, a running bill account, a gift card account and a pre-paid card account.

12. The transaction management system according to claim 1, wherein the specification is selected from the group consisting of a loyalty value percentage, an interest rate, a loyalty value, an insurance coverage, a warranty, an account balance, an account limit and a user preference.

13. The transaction management system according to claim 1, wherein the weight is a value based on at least one factor selected from the group consisting of the point-of-sale unit, one of the at least one specification of the user profile, the selected scenario and one of the transaction accounts.

14. The transaction management system according to claim 1, further comprising a plurality of said transaction scenarios, wherein the presenting of said transaction scenarios to the user by the point-of-sale unit comprises sorting said transaction scenarios according to a scenario weight value associated with each transaction scenario.

15. The transaction management system according to claim 14, wherein the scenario weight value is based on at least one of a monetary value, a point value, an interest rate value, a monetary equivalent value, a loyalty percentage and a loyalty value.

16. The transaction management system according to claim 14, wherein the scenario weight value is calculated on the basis of the weight of each specification of each transaction account associated to the transaction scenario.

17. The transaction management system according to claim 1, wherein the data storage module is connected to a telecommunication network accessible to the user.

18. The transaction management system according to claim 17, further comprising a user access application at the central server allowing a user to update said user profile through the telecommunication network.

19. The transaction management system according to claim 1, wherein the data storage module comprises history data linked to the user profile.

20. The transaction management system according to claim 1, wherein the server application is connected to a communication network for transmitting a message to a remote device accessible to the user when a transaction associated to the neutral card occurs or when the user profile is updated.

21. The transaction management system according to claim 20, wherein the message is at least one of an email, a text message, a ring tone, a sound, an image, an animation and a vibration.

22. The transaction management system according to claim 1, wherein the terminal application comprises a terminal-server reconciliation module for reconciling the transaction data between the point-of-sale unit and the central server.

23. The transaction management system according to claim 1, wherein the server application comprises a server-terminal reconciliation module for reconciling the transaction data between the central server and the point-of-sale unit.

24. The transaction management system according to claim 1, wherein the central server is in communication with at least one authorization host for authorizing the transaction.

25. The transaction management system according to claim 24, wherein the server application comprises a server-host reconciliation module for reconciling the transaction data between the central server and the at least one authorization host.

26. A method for enabling a user to complete a transaction using a neutral card, the method comprising:

a) at a point-of-sale, inputting card information related to said neutral card and transaction data related to said transaction, and forwarding said card information and transaction data to a central server;

b) at the central server;

i) associating the card information to a user profile corresponding to said neutral card, the user profile being linked to a plurality of transaction accounts, the user profile comprising at least one specification for each transaction account linked thereto, each specification being associated to a weight;

ii) generating at least one transaction scenario based on the transaction data and the weight of each specification of each transaction account linked to the user profile, and transmitting the at least one transaction scenario to the point-of-sale unit;

c) at the point-of-sale, obtaining a user selection of one of the at least one transaction scenario, thereby defining a selected scenario, and forwarding said selected scenario to the central server;

d) completing the transaction based on the selected scenario.

27. The method for enabling a user to complete a transaction according to claim 26, wherein, at step a), the point-of-sale unit encrypts at least a portion of said card information and transaction data prior to forwarding to the central server and, prior to step b) i), the central server decrypts the portion of said card information and transaction data.

28. The method for enabling a user to complete a transaction according to claim 26, wherein, prior to step b) ii), the central server validates at least a portion of the card information and transaction data.

29. The method for enabling a user to complete a transaction according to claim 26, wherein, at step b) ii), the central server generates the at least one transaction scenario in a sorted order according a scenario weight value.

30. The method for enabling a user to complete a transaction according to claim 26, wherein the scenario weight value is at least one of a monetary value, a point value, an interest rate value, a monetary equivalent value, based the weight corresponding to each specification.