WO2006055002A1 - Systeme et procede d'execution de transactions commerciales securisees - Google Patents

Systeme et procede d'execution de transactions commerciales securisees Download PDF

Info

Publication number
WO2006055002A1
WO2006055002A1 PCT/US2004/039003 US2004039003W WO2006055002A1 WO 2006055002 A1 WO2006055002 A1 WO 2006055002A1 US 2004039003 W US2004039003 W US 2004039003W WO 2006055002 A1 WO2006055002 A1 WO 2006055002A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer
merchant
service provider
financial
order
Prior art date
Application number
PCT/US2004/039003
Other languages
English (en)
Inventor
Boris Hitalenko
Michael Likterev
Original Assignee
Byz Tek Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Byz Tek Inc. filed Critical Byz Tek Inc.
Priority to PCT/US2004/039003 priority Critical patent/WO2006055002A1/fr
Publication of WO2006055002A1 publication Critical patent/WO2006055002A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the present invention relates generally to a system for enabling commercial transactions that may occur remotely, for example, over one or more communication networks, and more particularly to a data processing and communication system for enabling customers placing orders with merchants to conduct secure payment transactions therewith.
  • On-line fraud can take many forms, but is generally defined as utilization of consumer confidential financial data (CFD) (e.g., credit card number, expiration date, CW2 number, etc), by an unauthorized party to engage in on-line commercial transactions or for related purposes.
  • CFD consumer confidential financial data
  • Theft or misappropriation of the CFD may occur in at least one or more of the following well known and publicized ways:
  • any individual who is able to gain electronic or physical access to the consumer's computer may be able to obtain the CFD.
  • a computer virus infecting the consumer's computer such as a "keystroke logger” or a password capture program, may be able to intercept the CFD being entered, by the consumer during an order process, and then secretly send it to a third party;
  • CFD may be misdirected from a merchant's system, the consumer may be tricked into sending the CFD to a different destination (i.e., "spoofing"), the CFD may be intercepted at the merchant side by a maliciously installed hidden program, etc.
  • Theft of the CFD from the merchant The CFD may be misappropriated by the merchant, by one or more of the merchants' employees, or by a third party breaking into a merchant's customer CFD database.
  • CFD Protection e.g., encryption of CFD data before, during, and/or after transmission
  • Consumer Identity Verification e.g., verification that the individual placing an on-line order is in fact the consumer to whom the CFD belongs, as accomplished through software using consumer-entered security codes, through hardware, such as biometric (fingerprint, retina, palm, voice pattern) scanners, key cards and readers, -global positioning systems, or via a combination of both software and hardware technologies); and
  • Secure Third Party Agents e.g., an third party organization that securely holds the CFD and that communicates with and acts as an intermediary between, the customer, the merchant and the customer's financial service provider (FSP), so that the CFD is never sent to the merchant directly.
  • FSP financial service provider
  • FIG. 1 is a block diagram showing components of a first exemplary embodiment of the inventive secure order transaction system that may be advantageously utilized for placing product and/or service orders on-line, or through any other type of interactive service;
  • FIG. 2 is a process flow chart showing an exemplary embodiment of a novel process for performing commercial order transactions remotely utilizing the system of FIG. 1 ;
  • FIG. 3 is a set of block diagrams showing components of various data items generated in conjunction with the performance of the process of FIG. 2;
  • FIG. 4 is a process flow chart showing an exemplary embodiment of a novel order verification process that is performed in conjunction with the process of FIG. 2;
  • FIG. 5 is a process flow chart showing an exemplary alternate embodiment of the novel order verification process of FIG. 4;
  • FIG. 6 is a block diagram showing components of a second exemplary embodiment of the inventive secure order transaction system that may be advantageously utilized for placing orders by use of voice communication devices (for example, via conventional or mobile telephones);
  • FIG. 7 is a block diagram showing components of a third exemplary embodiment of the inventive secure order transaction system that may be advantageously utilized for placing orders through a wireless service provider utilizing a mobile communication device;
  • FIG. 8 is a process flow chart showing an exemplary embodiment of a novel process for performing commercial transactions remotely utilizing the system of FIG. 7;
  • FIG. 9 is a set of block diagrams showing components of various data items generated in conjunction with the performance of the process of FIG. 8;
  • FIG. 10 is a process flow chart showing an exemplary embodiment of a novel order verification process that is performed in conjunction with the process of FIG. 8;
  • FIG. 11 is a block diagram showing components of a fourth exemplary embodiment of the inventive secure order transaction system that may be advantageously utilized for placing orders through transmission of a written order form;
  • FIG. 12 is a process flow chart showing an exemplary embodiment of a novel process for performing commercial transactions remotely utilizing the system of FIG. 7;
  • FIG. 13 is a block diagram showing elements of an exemplary previously known common order transaction process utilized for placing remote orders online, via communication devices, or through transmission of written order forms.
  • the present invention is directed to a system and method for enabling secure remote commercial order transactions, that through various embodiments described below, advantageously address and meet both of the major security challenges currently facing remote commercial order transactions: (1) theft of confidential financial data (CFD), and (2) verification that the individual placing a remote order using particular CFD, is in fact the person to whom the CFD belongs, or who has otherwise been authorized to use the CFD.
  • CFD confidential financial data
  • the present invention accomplishes the above goals by: (1) ensuring that the complete CFD is never transmitted to the merchant, and in fact is not even necessary for order placement, and by: (2) separating the order process into the stages of order placement and order verification, where the verification of the order is made by the customer's financial service provider (FSP) - a party that has always been in possession of the customer's CFD.
  • FSP financial service provider
  • the inventive system and method also provide FSPs with the opportunity to offer one or more products and/or services to the customer during the order verification process, and also with a unique opportunity to offer certain services when customers are in dire need thereof (e.g., credit line increases, loans, etc.).
  • the inventive system and method enable secure commercial order transactions between customers and merchants, over at least one communication link (which may range from one or more communication networks to the postal mail system, depending on the inventive embodiment thereof).
  • the inventive system and method ensure that customer entire CFD is never transmitted to the merchant, by keeping that CFD proprietary to the customer's exiting FSP with which the customer has an established financial account, that has previously issued a payment instrument (e.g., credit card, debit card, check card, etc.) to the customer, with which the CFD is associated, and that is capable or transmitting (or authorizing transmission of), payments to a merchant's financial account.
  • a payment instrument e.g., credit card, debit card, check card, etc.
  • the customer when an order is placed, the customer provides to the merchant a partial CFD sufficient, along with additional data, also provided as part of the order, to identify the customer's FSP to the merchant, and to identify the customer to the FSP.
  • the merchant then provides the partial CFD, along with at least partial order data, to the FSP and also provides order confirmation data to the customer.
  • the specific way in which the order and the partial CFD are transmitted from the customer to the merchant depends on the specific inventive embodiment thereof, while the financial operations performed between the merchant and the FSP (and related parties) remain substantially identical for the different inventive embodiments.
  • a novel order verification process that enable authorization, by the customer, of the order through contact between the customer and the FSP.
  • contact to authenticate the order is initiated by the customer who contacts their FSP, in another embodiment, the FSP contacts the customer when the at least partial order data along with the partial CFD have been received from the merchant.
  • the exact manner in which the inventive order verification process occurs is preferably pre-arranged between the customer and their FSP.
  • the FSP is provided with the ability to offer additional services and/or products to the customer during the novel order verification process, related, or unrelated to, the order.
  • inventive system and method function equally well for interactive electronic (e.g., online) orders, telephone orders, mobile commerce orders, facsimile orders, electronic mail orders, and mail-order orders.
  • the system and method of the present invention remedy the disadvantages of previously known systems for enabling secure commercial transactions between customers and merchants.
  • the present invention in its various embodiments, in contrast to most recently developed secure transaction techniques (which are focused only on securing on-line transactions), functions equally well for virtually all types of commercial transactions - whether one initiated by electronic orders sent over one or more communication networks (such -as the Internet and/or local or long- distance telephone networks), or ones initiated by other types of contact with merchants, for example, by telephone, facsimile or through the mail.
  • the system and method of the present invention enable customers to conduct secure order transactions with any type of merchant without requiring any special software, encryption, or special hardware on the part of the customer, the merchant, or the financial transaction processor.
  • the inventive system and method do not require utilization of a costly third party (e.g., a secure agent or secure data repository) to manage and limit the flow of the customer's confidential financial data (CFD) between the customer and the merchant.
  • a costly third party e.g., a secure agent or secure data repository
  • CFD confidential financial data
  • the inventive system and method accomplish the above goals by ensuring that the customer's entire confidential financial data (CFD) is never transmitted to the merchant, and is preferably retained by a highly secure party (or parties) that the user has already previously authorized (directly or implicitly) to securely handle their commercial transactions (for example by signing up for a particular credit card, the customer provides transaction handling authorization to 'the issuing bank).
  • a highly secure party or parties
  • Such secure pre- authorized parties may include, but are not limited to, a credit or debit card company, a bank, a brokerage, a financial management firm, etc., or any combination thereof.
  • FSPs financial service providers
  • TPCs transaction processing companies
  • FTIs financial transaction intermediaries
  • the merchant when a customer places an order with a merchant, in addition to the commonly transmitted order information (customer identifying information, a list of the products and/or services ordered, etc.) the merchant only receives a portion of the customer's CFD that is sufficient, in conjunction with at least a portion of the order information, to identify the specific customer to that customer's FSP (and/or to the corresponding TPC depending on how a particular FSP is structured).
  • the provision, by the merchant, of the customer's order and partial CFD information to the FSP enables the FSP to verify (through one or more novel processes disclosed below in connection with the various inventive embodiments) that the order has in fact been placed by the customer identified by the merchant. Once the order is verified, the remainder of the transaction proceeds in the previously known manner - e.g., the FSP authorizes payment for the order to the merchant, and the corresponding FTI transmits payment to the merchant.
  • a credit card CFD may include the credit card number (hereinafter the "CCN"), the expiration date, the card verification value "CW2" or equivalent, and/or the name, address and/or the phone number of the issuing bank.
  • CCN credit card number
  • CW2 card verification value
  • the customer uses a credit card (issued by. their FSP - a bank) to place an order with a merchant
  • the only portion of the CDF that is transmitted to the merchant along with the order information may be the first digit, and the last four digits of the CCN, and the name of the issuing bank.
  • This information is sufficient to enable the merchant to identify the customer to the FSP to initiate the order verification process, but cannot be misused in any way by the merchant, their employees or any unauthorized third parties who somehow obtain this information (siich as by intercepting it during its transmission, or by misappropriating it from the merchant).
  • the full CFD may not even be stored or entered by the customer at the electronic device used for orde ' r placement, such that even if a third party has somehow gained unauthorized access to the device used for order placement (for example, physically, by electronic intrusion, through a virus, a keystroke logger, or through any othe ' r illegal or unauthorized means), they would only be able to gain partial CFD information.
  • Partial CFD information is insufficient to enable unauthorized parties to utilize it to engage in fraudulent activities, because previously known order transaction systems require the full CFD, while the novel order verification process of the inventive system would expose and prevent any such attempts.
  • the inventive system and method advantageously enable the FSPs to derive many additional direct and indirect benefits from this process, for example by offering additional products and/or services (or upgrades thereto) to the customer during the order verification process. In certain cases, as described below in connection with FIGs.
  • the inventive system and method enable the FSPs to offer unprecedented customer service benefits, as a matter of course, or as part of a premium membership program, such as offering to increase the customer's credit limit in situations where it is exceeded by the order charges, or allowing the customer time to make a payment to the credit account prior to charging it for the order, rather than automatically declining the transaction, and inconveniencing both the customer and the merchant, as is the current practice in such situations.
  • Payment Any form of a financial instrument issued by a FSP to a Instrument customer (directly or indirectly), that may be utilized by the customer to authorize the FSP and affiliate organizations (e.g., TPC, FTI, etc.) to make a payment on behalf of the customer to parties designated by the customer (i.e., merchants).
  • customer directly or indirectly
  • affiliate organizations e.g., TPC, FTI, etc.
  • the manner in which this purpose is accomplished, and other aspects of utilization may vary depending on specific type of instrument.
  • financial instruments include, but are not limited to: a credit card, a charge card, a debit card, a cash card, or an equivalent thereof.
  • Other equivalents of the above instruments, that provide a customer with certain CFD linked to an account through, or from, which the customer is able to authorize payments, are likewise contemplated.
  • even certain types of gift certificates that have a unique number specific to a certificate that is linked to a particular consumer may be utilized as payment instruments
  • Table 2 below provides a useful definition guide to the terms and abbreviations used in the respective figures.
  • a customer 602 places an order with a merchant 604 by communicating the order, along with the customer's CFD to be used for payment, through a communication link 606 (e.g., via the Internet, telephone, facsimile, or mail order).
  • the merchant 604 then submits the order for payment authorization from the customer 602's FSP 610, typically through a transaction processing company 608.
  • the FSP 610 ensures that the customer 602 has sufficient funds in their account to cover the required payment, and then instructs a financial transaction intermediary 612 to transmit the payment to the merchant 604. If the funds in the customer 602 account are insufficient, the FSP 610 declines merchant 604's request for payment, which typically results in the order being cancelled.
  • the various embodiments of the inventive system and method described below in conjunction with FIGs. 1-12 provide complete secure transaction capability by modifying the previously known process 600 with one or more novel configurations, while retaining the basic infrastructure of the system underlying the process 600, resulting in secure remote order transactions with virtually no changes to the current commercial transactions infrastructure. Referring now to FIG.
  • a first exemplary embodiment of the inventive secure order transaction system is shown as a system 10.
  • the various novel embodiments of the operation of the system 10 are described in greater detail below in connection with FIGs. 2-5.
  • the system 10 includes an order component 12, and a financial operations component 30, that interact with one another through communication links 26, 42, and 48, described in greater detail below.
  • the order component 12 represents the interaction between a customer 14 and a merchant 16, "that enables the customer 14 to communicate an order for a product and/or service to the merchant 16, and that enables the merchant 16 to communicate order confirmation and other information to the customer 14.
  • the merchant 16 utilizes a merchant system 20, for offering products and/or services in a manner viewable by the customer 14, that also enables the customer 14 to place an order for the products and/or services offered by the merchant 16, utilizing a customer system 18, through a communication link 22.
  • the merchant system 20 is also preferably capable of communicating with the customer system 18, and with various sub-components of the operations component 30 through the communication links 26, 48 (as described in greater detail below).
  • the merchant system 20 is preferably implemented as a data processing system, such as a computer system, or a network of computer systems, that include(s) all necessary equipment and software to accomplish at least the above-indicated purposes thereof.
  • the customer 14 utilizes a customer system 18 for interacting with the merchant system 20 to peruse and view the products and/or services offered by the merchant 16 through the merchant system 20, for remotely placing an order for the desired products and/or services from the merchant 16, and optionally for receiving communications from the merchant system 20 through the communication link 22.
  • the customer system 18 may be implemented as a data processing system that include(s) all necessary equipment and software to accomplish at least the above-indicated purposes thereof. Examples of data processing systems that may be readily utilized as the customer system 18, in accordance with the present invention include, but are not limited to:
  • the communication link 22 may be any form of a communication link or network (whether wire-based, wireless, or a combination thereof) that enables electronic communication between the customer system 18 and the merchant system 20.
  • the specific implementation of the communication link 22 utilized is preferably selected as a matter of necessity and/or design choice, for example based on the implementations of the customer system 18
  • the communication link 22 may be the
  • the communication link 22 may be the cable or satellite network
  • the communication link 22 may be the wireless service network of the wireless service provider and all components necessary for the customer system 18 and the merchant system 20 to communicate therewith.
  • the nature, size, and the composition of the merchant system 20 are preferably selected as a matter of necessity and/or design choice, for example based on the requirements of the merchant 16, the types of products and/or services offered by the merchant 16, the nature of customer systems 18 that will be communicating therewith, and the scale of merchant 16 operation, without departing from the spirit of the present invention.
  • the nature, size, and the composition of the merchant system 20 are preferably selected as a matter of necessity and/or design choice, for example based on the requirements of the merchant 16, the types of products and/or services offered by the merchant 16, the nature of customer systems 18 that will be communicating therewith, and the scale of merchant 16 operation, without departing from the spirit of the present invention.
  • the nature, size, and the composition of the merchant system 20 are preferably selected as a matter of necessity and/or design choice, for example based on the requirements of the merchant 16, the types of products and/or services offered by the merchant 16, the nature of customer systems 18 that will be communicating therewith, and the scale of merchant 16 operation, without departing from the spirit
  • a small on-line merchant 16 that receives a few dozen of orders per day may utilize a personal computer, in conjunction with powerful equipment of a subscription-based web-hosting service
  • a large on-line retailer merchant 16 may utilize their own network of powerful high-throughput computer systems, capable of hosting and operating an on-line store that handles thousands of orders per day;
  • An entertainment service provider merchant 16 may ..utilize their own network of powerful high-throughput computer systems, capable of interacting with the customer system 18 and, optionally, with the systems of their partner merchant(s) (not shown).
  • the customer 14 also utilizes a customer communication device 24 (which may be a telephone or an equivalent thereof) for communicating with the customer 14's FSP 34 (as described in greater detail below in connection with FIGs. 2 to 5).
  • the customer communication device 24 may be incorporated into the customer system 18 as an integral component thereof.
  • the customer communication device 24 may be the voice communication portion of the mobile telephone.
  • the financial operations component 30 represents the interaction between a TPC 32, the FSP 34 and a FTI 46, that, in response to communication with the order component 12, results in approval or denial by the FSP 34, of payment to the merchant 16 for an order placed therewith by the customer 14, and when, the payment is approved, results in processing of the payment to the merchant 16.
  • the FSP 34 utilizes an FSP system 38 for receiving, through a communication link 36, order information submitted by the merchant 16 to the TPC 32 through the communication link 26, relating to the order placed by the customer 14 with the merchant 16.
  • the FSP 34 also utilizes a FSP communication system 40, for communicating with the customer communication device 24, through the communication link 42, to verify that the customer 14 indeed placed the order. If the order is verified, the FSP system 38 is also capable of instructing the appropriate FTI 46 through the communication link 44, to issue payment to the merchant 16 through the communication link 48 (for example by transferring the necessary funds to a predetermined financial account of the merchant 16).
  • the FSP communication system 40 is configured based on the nature of the customer communication device 24, and optionally based on the volume of desirable communications with FSP 34 customers.
  • the FSP communication system 40 may be " a powerful multi-operator telephone system with the capacity of hundreds or thousands of simultaneous telephone connections with various customer communication devices.
  • the communication link 42 is preferably- selected to enable communication between the FSP communication system 40 and the customer communication device 24.
  • the communication link 42 may be a telephone communication network (and would also include a wireless communication network if the consumer communication device 24 is a mobile telephone).
  • the various communication links 26, 36, 44, and 48 may be implemented individually as direct communication lines or in any combination of two or more as part of one or more communication networks (e.g., the Internet, wide area networks, virtual private networks, or equivalent thereof).
  • the communication link 48 is sufficiently secure to enable safe transmission of payments to the merchant 16.
  • the TPC 32, the FSP 34, and the FTI 46 are shown in FIG. 1 as individual entities by way of example only. Accordingly, the FSP 34 may incorporate and implement all the functionality and capabilities of one or both of the TPC 32 and the FTI 46.
  • the various embodiments of the process of operation of the inventive system 10 and the components 12 and 30, are preferably implemented as combinations of steps performed by the customer 14 utilizing the customer system 18, by the merchant 16 utilizing the merchant system 20, and by the TPC 32, the FSP 34, and the FTI 46, that are initiated when the customer 14 places an order with the merchant 16, and that are subject to predetermined rules and/or policies established by the FSP 34 (that may be optionally configured by the customer 14 with the FSP 34 prior approval).
  • some of the steps and functions described below in connection with FIGs. 2, 4, and 5, may be performed by different parties from those described, or by agents of the parties, or may be performed manually or automatically, as a matter of design choice convenience, or necessity, without departing from the spirit of the invention.
  • the process 50 begins at a step 52 when the customer 14 selects a product and/or service offered by the merchant 16, for example utilizing the customer system 18 to communicate with the merchant system 20, through the communication link 22.
  • the customer 14 places the order for the selected product and/or service by causing the customer system 18 to provide the merchant system 20 with PURCH_DATA (shown as PURCHJDATA 70 in FIG. 3, and described in greater detail above in Table 2), which is transmitted to the merchant system 20.
  • PURCH_DATA 70 may be encrypted during transmission to the merchant system 20, using any previously known encryption technique.
  • the PURCHJDATA 70 includes CUSTJNFO 1 PMTJNFO, and P/SJJST as described above in Table 2.
  • the merchant system 20 generates ORDERJDATA (shown as ORDERJDATA 72 in FIG. 3, and described in greater detail above in Table 2), which may include one or more of the following data items (also described above in Table 2): PURCHJDATA, MERCHJD, CHARGE_$, PMTJNFO, and ORDERJD.
  • the merchant 16 submits, via the merchant system 20 or by other means, the ORDER_DATA 72 to the FSP 34 identified in the PMTJNFO (typically by first transmitting the ORDER_DATA 72 to the TPC 32, which then forwards it to the FSP 34 after processing).
  • the FSP 34 determines if PREL_APP should be " issued to the merchant 16, based on whether the customer 14's payment instrument identified in the PMTJNFO has access to sufficient funds through the customer 14 financial account with the FSP 34, to make a payment to the merchant 16 in the amount of the CHARGE_$. If a PREL_APP is not issued, then, at an optional step 62, the FSP 34 provides a PMTJDEC notice to the merchant 16 (which can then be communicated to the customer 14 in accordance with the merchant 16's business policies (e.g., before, or after, cancellation of the order placed by the customer 14 at the step 54)), and the process 50 then ends at a step 64. Otherwise, when a PREL_APP is issued, then the process 50 proceeds to a step 66 where the merchant 16 provides the customer 14 with ORDER_CONF (shown as ORDER_CONF 74 in FIG. 3, and described in greater detail in Table 2 above).
  • ORDER_CONF shown as ORDER_CONF 74 in FIG.
  • an order verification process is performed (through interaction between the customer 14 and the FSP 34) to ensure that the order placed at the step 54, was in fact placed by the authorized holder of the financial account to which the payment instrument identified by the PMTJNFO is linked.
  • the order verification process is key novel feature of the present invention, which may be performed in a variety of ways, but in essence involves predefined contact between the customer 14 and the FSP 34 (for example by the customer 14 contacting an authorized FSP 34 representative or vice versa) during which the customer 14's identity is verified by the FSP 34, and during which at least a portion of the ORDER_CONF 74 is provided by the customer 14 to the FSP 34 and compared to the ORDER_DATA 72 received by the FSP 34 from the merchant 16, to verify and authorize the order placed at the step 54. If the order is verified, then the FSP 34 authorizes the appropriate payment to the merchant 16. The process 50 then ends at the step 64.
  • order verification process 100 in which the customer 14 contacts the FSP 34 to verify the order
  • an alte/nate order verification process 150 in which the FSP 34 contacts the customer 14 to verify the order
  • the exact manner in which the processes 100 and 150 are performed, and all necessary implementation details are pre-arranged between the customer 14 and the FSP 34 in a manner convenient and acceptable to both parties.
  • These arrangements may be simply dictated by the FSP 34 and then accepted by the customer 14, or optionally, the customer 14 may be involved in configuring the arrangements in accordance with their preferences.
  • the order verification process 100 begins at a step 102, when the customer 14 uses the customer communication device 24 to contact the FSP 34 through the ' FSP communication system 40, and verifies their identity to the FSP 34, for example by providing a password or other form of security code or secret information in response to a request from the FSP 34.
  • the customer 14 provides information representative of at least a portion of the ORDER_CONF 74 to the FSP 34, and, when the FSP 34 confirms that the information matches the ORDER_DATA 72 received by the FSP 34 from the merchant 16, the customer 14 provides verification for the order at a step 108.
  • the FSP 34 determines if the financial account of the customer 14, identified by PMTJNFO, has access to sufficient funds to cover payment to the merchant 16 in the amount of CHARGE_$. If the funds are not sufficient, at a step 114, the FSP 34 declines the payment by issuing the PMT_DEC notice to the customer 14 and to the merchant 16 and then returns to the process 50.
  • the FSP 34 is placed into direct contact with the customer 14, thus, during the interaction between the customer 14 and the FSP 34 throughout the process 100, the FSP 34 is able to offer various services to the customer 14, that are related or unrelated to the order being verified (e.g., an purchase protection plan, an additional credit card, etc.), in accordance with the FSP 34 direct marketing policies.
  • the FSP 34 can offer one or more services to the customer 14 that are specifically relevant to the fact that the order transaction being verified may be imminently declined by the FSP 34.
  • Services offered by the FSP 34 at the optional step 112 may include one or more of the following: an increase of the customer 14's payment instrument credit line so that the funds are sufficient to cover the CHARGE_$, a loan, or a predefined period that the FSP 34 will wait for the customer 14 to increase available funds before performing the step 110 again.
  • the process 100 continues to the step 114.
  • the optional step 112 thus provides the FSP 34 with unprecedented customer service and marketing tools that are optimally applied when the customer 14 is in actual need thereof.
  • the FSP 34 provides or guarantees the payment of CHARGE_$ to the merchant 16, and at an optional step 118, stores the TRNSJNFO (described above in Table 2) in a customer 14 record (not shown), before returning to the process 50.
  • the order verification process 150 begins at a step 152, when the FSP 34 uses the FSP communication system 40 to contact the customer 14 through the customer communication device 24, and verifies the customer 14 identity, for example by asking the customer 14 to provide a password or other form of security code or secret information in response to a predetermined request from the FSP 34.
  • the FSP 34 provides information representative of at least a portion of the ORDER_DATA 72 received by the FSP 34 from the merchant 16 to the customer 14, and then proceeds to a step 156.
  • the customer 14 either confirms that they actually placed the order identified at the step 154, in which case the process continues to a step 160, or denies that they placed the identified order, in which case, at an optional step 158, the FSP 34 initiates a fraud investigation of the unauthorized order, and then proceeds to a step 168, where the PMT_DEC notice is provided to the merchant 16 (and of course to the customer 14).
  • the process 150 then performs the steps 160 through 168 in substantially identical manner to how the process 100 (of FIG. 4) performs the corresponding steps 110 to 118, that are described above in connection with FIG. 4.
  • the inventive system 10 may be readily utilized to enable the customer 14 to engage in secure remote order transactions with the merchant 16 without placing their CFD at any risk of misappropriation.
  • the customer 14 does not even need to store their CFD on their customer system 18, further reducing the likelihood of CFD theft.
  • the system and method of the present invention are equally applicable to all forms of remote purchase transactions that do not take place on-line.
  • Various embodiments of the inventive system and method advantageously configured for different types of remote order transactions are shown and described below in connection with FIGs. 6-12.
  • the financial operations component 30 is the same as the financial operations component 30 of FIG. 1. This clearly demonstrates, yet again, that the various embodiments of the present invention can operate equally well with the currently existing commercial order transaction infrastructure.
  • FIG. 6 a second exemplary embodiment of the inventive secure order transaction system, suitable for remote telephone
  • the system 200 includes an order component 202 and a financial operations component 30 (of FIG. 1) that interact with one another through communication links 26, 42, and 48, as described in greater detail below.
  • the order component 202 represents the interaction between a customer 204 and a merchant 206, that enables the customer 204 to communicate an order for a product and/or service to the merchant 206, and that enables the merchant 206 to communicate order confirmation and other information to the customer 204.
  • the merchant 206 can utilize one or more approaches for communicating offered products and/or services to the customer 204, such as by advertising/marketing (e.g., via radio, print, television, promotional, live, direct mail, email, or telemarketing) and/or by providing a manner in which the customer 204 can seek out and peruse the products and/or services offered by the merchant 206, such as via a print catalog, a retail store, an on-line store, or through any combination thereof.
  • advertising/marketing e.g., via radio, print, television, promotional, live, direct mail, email, or telemarketing
  • a manner in which the customer 204 can seek out and peruse the products and/or services offered by the merchant 206 such as via a print catalog, a retail store, an on-line store, or through any combination thereof.
  • the customer 204 preferably utilizes a customer communication device 208, which may be a telephone or equivalent form of voice communication device (for example corresponding to the customer communication device 24 of FIG. 1), to communicate an order for a product and/or service to the merchant 206, via a communication- link 212 connected to a merchant communication system 210.
  • the customer communication device 208 may likewise be used for communication with the FSP communication system 40 when necessary.
  • the merchant communication system 210 may range from a single telephone connected to a telephone line which in turn connects to the communication link 212, to a multi-line multi-operator telephone system capable of handling hundreds or thousands of simultaneous voice communications with customer communication devices.
  • the communication link 212 may be a telephone communication network, or a combination of a telephone communication network and a wireless network, if the customer communication device 20.8 is wireless.
  • the system 200 operates in a substantially similar manner to the system 10 of FIG. 1.
  • the process 50 of FIG. 2, as well as data items 70-74 of FIG. 3, and the order verification processes 100 and 150, of FIGs. 4 and 5, respectively, are all equally applicable to, and useable by the system 200.
  • the merchant 206 may utilize one or more additional systems (not shown), such as a merchant computer system (e.g., the merchant system 20 of FIG. 1), to enter the PURCH_DATA received from the customer 204 into an electronic format, and then to automatically generate the ORDER_DATA which may be sent to the financial operations component 30, and ORDER_CONF (which may be sent to the customer 204 by other means such as electronic mail, postal mail, facsimile, or via an equivalent thereof).
  • a merchant computer system e.g., the merchant system 20 of FIG. 1
  • ORDER_CONF which may be sent to the customer 204 by other means such as electronic mail, postal mail, facsimile, or via an equivalent thereof.
  • a third exemplary embodiment of the inventive secure order transaction system suitable for remote mobile commerce order transactions, is shown as a system 250 of FIG. 7.
  • unique mobile commerce opportunities include, but are not limited to, the following: enhancements to, or additional features for, a customer mobile communication device, additional wireless service provider (WSP) services, various premium mobile services (for example, short message service (SMS) or multimedia message service (MMS) based services for ordering entertainment and/or travel tickets, event notifications, weather notices, news, etc.), and/or products from specific mobile commerce merchants (MCM) that have partnered with the WSP.
  • WSP wireless service provider
  • MMS multimedia message service
  • the system 250 includes a mobile order component 252, and a financial operations component 30 (of FIG. 1), that interact with one another through communication links 26, 42, 48, and optionally link 268, as described in greater detail below.
  • the system 250 operates in a similar manner to the system 10 of FIG. 1 , in that a customer mobile communication device 256 incorporates the functionality of both the customer system 18 and the customer communication device 24, and in that a communication link 264 is equivalent to a wireless embodiment of the communication link 22 of FIG. 1 , with the following key differences:
  • a WSP (see Table 2, above) 260 may serve as both a merchant providing their own products and/or services, or serve as an intermediary between the customer 254 and a MCM (see Table 2 above) 258, that offer products and/or services to the customer 254 through the WSP 260; and
  • the WSP 260 is supplied with the PMTJNFO (see Table 2) of the customer 254 as part of the subscription process, and therefore there is no need to transmit the PMTJNFO, from the customer 254 and the WSP 260, when a mobile order is placed.
  • the order component 252 enables the customer 254 to place an order for a product and/or service, through interaction between the customer 254, and the WSP 260, and optionally between the customer 254 and the MCM 258, with the WSP 260 acting as an intermediary.
  • the WSP 260 (and/or the MCM 258) utilizes the WSP mobile commerce system 262 to offer products and/or services in a manner viewable by the customer 254 (either sought ouf by the customer 254, or offered to the customer 254 by the WSP 260 via SMS, MMS, or equivalent thereof).
  • the customer 254 then utilizes the customer mobile communication device 256 to communicate an order for a product and/or service to the WSP 260, or to the MCM 258 (which communicates with the customer 254 through the communication link 266 and then through the WSP 260).
  • the WSP 260 then utilizes a WSP mobile commerce system 262 to communicate order confirmation and other information from the WSP 260, and/or the MCM 258, to the customer 254, and then communicates with various sub-components of the financial operations component 30, through the communication links 26, 48 (in a manner similar to the merchant system 20 of FIG. 1 ).
  • the MCM 258 may communicate with the operations component 30 via the optional communication link 268, bypassing the WSP 260.
  • the WSP mobile commerce system 262 is preferably implemented as a data processing system, such as a computer system, or a network of computer systems, that includes all necessary equipment to send and receive wireless communications via the communication link 264, and preferably include(s) all necessary equipment and software to accomplish at least the above-indicated purposes thereof.
  • the customer 254 also utilizes the customer mobile communication device 256 for communicating with the customer 254's FSP 34 via the communication link 34 (as described in greater detail below in connection with FIGs. 8 to 10).
  • FIG. 8 an exemplary embodiment of a process of operation of the system 250 is shown as a process 300.
  • the process 300 begins at a step 302 when the customer 254 selects a product and/or service offered by the WSP 260 (and/or the MCM 258), for example utilizing customer mobile communication device 256 to communicate with the WSP 260 (and, optionally, the MCM 258) through the communication link 264.
  • the customer 254 places the order for the selected product and/or service by causing the customer mobile communication device 256 to provide the WSP mobile commerce system 262 with MP_DATA (shown as MP_DATA 350 in FIG. 9, and described in greater detail above in Table 2), by transmitting the MP_DATA 350 thereto along with a standard identification code (not shown), that identifies the specific customer mobile communication device 256 (and in most cases the customer 254) to the WSP
  • MP_DATA shown as MP_DATA 350 in FIG. 9, and described in greater detail above in Table 2
  • the MP_DATA 350 includes the P/SJJST, and, if the order is being placed with the MCM 258, also includes their MCMJD, as described above in Table 2.
  • WSP mobile commerce system 262 generates MOJDATA (shown as MOJDATA 352 in FIG. 9, and described in greater detail above in Table 2), which may include one or more of the following data items, also described above in Table 2: MPJDATA, CUSTJNFO (already in possession of WSP 260), CHARGE_$, and MOJD.
  • the WSP 260 submits, via the WSP mobile commerce system 262, or by other means, the MOJDATA 352, to the FSP 34 identified in the PMTJNFO (typically by first transmitting the MOJDATA 352 to the TPC 32 which then forwards it to the FSP 34 after processing).
  • the FSP 34 determines if PREL_APP should be issued to the WSP 260 (or to the MCM 258), based on whether the customer 254's payment instrument identified in the PMTJNFO has access to sufficient funds in the customer 254 financial account with the FSP 34, to make a payment to the WSP 260 (or to the MCM 258) in the amount of the CHARGE_$.
  • the FSP 34 provides a MP_DEC notice (see Table 2) to the WSP 260 (or to the MCM 258), which can then be communicated to the customer 254 in accordance with the business policies of the WSP 260 (or of the MCM 258) - e.g., before or after cancellation of the order placed by the customer 254 at the step 304, and the process 300 then ends at a step 314.
  • the process 300 proceeds to a step 316 where the WSP 260 (or of the MCM 258) provides the customer 254 with MO_CONF (shown as
  • MO_CONF 354 in FIG. 9, and described in greater detail in Table 2 above).
  • a mobile order verification process is performed (through interaction between the customer 254 and the FSP 34) to ensure that the order placed at the step 304 was in fact placed by the authorized holder of the financial account to which the payment instrument identified by the PMTJNFO is linked.
  • the mobile order-verification process may be performed in a variety of ways, but for example, may involve a predefined contact between the customer 254 and the FSP 34 (for example by the customer 254 contacting an authorized FSP 34 representative or vice versa) during which at the customer 254's identity is verified " by the FSP 34, and during which at least a portion of the MO_CONF 354 is provided by the customer 254 to the FSP 34 and compared to the MOJDATA 352 received by the FSP 34 from the WSP 260 (or from the MCM 258), to authorize and verify the order placed at the step 304. If the order is verified, then the FSP 34 authorizes the appropriate payment to the WSP 260 (or to the MCM 258). The process 300 then ends at the step 314. All order-transaction events occurring after that time (e.g., order fulfillment by the WSP 260 (or to the MCM 258), etc., occur in the same manner as do current conventional post-order mobile commercial transactions.
  • the mobile order verification process performed at the step 318 may be substantially similar to either one of the order verification processes 100 or 150, of FIGs. 4 and 5, respectively.
  • FIG. 10 optionally, an alternate embodiment of the order verification process 150 of FIG. 5, shown as a mobile order verification process 400 of FIG. 10, may be advantageously utilized at the step 318.
  • the exact manner in which the process 400 is performed, and all necessary implementation details are pre-arranged between the customer 254 and the FSP 34 (and, optionally, also between the customer 254 and/or the FSP 34 and the WSP 260) in a manner convenient and acceptable to all parties.
  • These arrangements may be simply dictated by the FSP 34 (and/or the WSP 260) and then accepted by the customer 25 * 4, or optionally, the customer 254 may be involved in configuring the arrangements to their preferences.
  • One of the key arrangements of the process 400 involves a decision whether the steps 402 to 410 are performed by the WSP 260 or by the FSP 34. When these steps are performed by the FSP 34, the process 400 operates very similarly to the process 150 of FIG. 5. However, when the WSP 260 performs the steps 402 to 410, in essence the initial order verification is actually performed by the WSP 260 and not by the FSP 34 (which only enters the process later to ensure that sufficient funds are available for payment, and that the payment is made to the WSP 260 (or to the MCM 258).
  • This approach enables the WSP 260 and the FSP 34 to share the performance of the mobile order verification process 250 while remaining consistent to the essence of the present invention - that the CFD always remains with previously authorized secure parties (because WSP 260 is previously supplied with the customer 254 CDF).
  • the order verification process 400 begins at a step 402, when the WSP 260 (or the FSP 34 using the FSP communication system 40) contacts the customer 254 in a pre-arranged manner - for example via the customer mobile communication device 256, or by other means (e.g., a land-line telephone, etc.), and verifies the identity of the customer 254, for example by asking the customer 254 to provide a password, or other form of security code or secret information, in response to a predetermined request from the WSP 260 (or from the FSP 34).
  • a step 402 when the WSP 260 (or the FSP 34 using the FSP communication system 40) contacts the customer 254 in a pre-arranged manner - for example via the customer mobile communication device 256, or by other means (e.g., a land-line telephone, etc.), and verifies the identity of the customer 254, for example by asking the customer 254 to provide a password, or other form of security code or secret information, in response to a predetermined request from the WSP 260 (
  • the WSP 260 (or the FSP 34, if the WSP 260 previously transmitted it to the FSP 34), provides information representative of at least a portion of the MO_DATA 352, generated by the WSP 260 (and/or the MCM 258) to the "' customer 254, and then proceeds to a step 406.
  • the customer 254 either confirms that they actually placed the order identified at the step 404, in which case the process continues to an optional step 412, or denies that they placed the identified order, in which case, at an optional step 408, the WSP 260 (or the FSP 34) initiates a fraud investigation of the unauthorized order, and then, if the steps 402 to 408 are being performed by the FSP 34, the process 400 proceeds to a step 410, where a MP_DEC (see Table 2) notice is provided to the WSP 260 (and/or the MCM 258), and to the customer 254.
  • a MP_DEC see Table 2
  • the optional step 412 is performed by the process 400, where the WSP 260 submits an AUTH_REQ (see Table 2) to the FSP 34.
  • the process 400 then proceeds to a step 414, which can optionally be performed by the FSP 34 previously at any time after step 402 (assuming that the steps 402 to 410 are being performed by the FSP 34).
  • the FSP 34 determines if the financial account of the customer 254, identified by PMTJNFO, has access to sufficient funds to cover payment to the WSP 260 (or to the MCM 258) in the amount of CHARGE_$. If the funds are not sufficient, then the FSP 34 proceeds to the previously described step 410, where the payment for the order is declined, and then returns to the process 250. If the funds are sufficient, then the process 400 proceeds to a step 418.
  • the FSP 34 is placed into direct contact with the customer 254.
  • the FSP 34 is able to offer various services to the customer 254, that are related or unrelated to the order being verified (e.g., an purchase protection plan, an additional credit card, etc.), in accordance with the FSP 34 direct marketing policies.
  • the WSP 260 is given a similar attractive opportunity for direct one-to-one marketing contact with the customer 254.
  • the FSP 34 can offer one or more services to the customer 254 that are specifically relevant to the fact that the order transaction being verified may be imminently declined by the FSP 34.
  • Services offered by the FSP 34 at the optional step 416 may include one or more of the following: an increase of the customer 254's payment instrument credit line so that the funds are sufficient to cover the CHARGE_$, a loan, or a predefined period that the FSP 34 will wait for the customer 254 to increase available funds before performing the step 414 again.
  • the process 400 continues to the step 410.
  • the optional step 416 thus provides the FSP 34 (or the WSP 260) with unprecedented customer service and marketing tools that are optimally applied when the customer 254 is in actual need thereof.
  • the FSP 34 provides or guarantees the payment of CHARGE_$ to the WSP 260 (or to the MCM 258 indirectly via the WSP 260, or directly via the communication link 268), and, at an optional step 420, stores the MTJNFO (described above, in Table 2) in a customer 254 record (not shown) by the FSP 34 (and or by the WSP 260), before returning to the process 250.
  • inventive system 250 may be readily utilized to enable the customer 254 to engage .-in mobile commerce through secure remote mobile order transactions with the WSP 260, or with any MCM 258 partnering with the WSP 260, without placing their CFD at any risk of misappropriation.
  • a fourth exemplary embodiment of the inventive secure order transaction system suitable for remote postal and electronic mail, facsimile, and equivalent order transactions, is shown as a system 500.
  • the system 500 includes an order component 502, and a financial operations component 30 (of FIG. 1) that interact with one another through communication links 26, 42, and 48, as described in greater detail below.
  • the order component 502 represents the interaction between a customer 504 and a merchant 506, that enables the customer 504 to communicate an order for a product and/or service to the merchant 506, and that also enables the merchant 506 to communicate order confirmation and other information to the customer 504.
  • the merchant 506 can utilize one or more approaches for communicating offered products and/or services to the customer 504, such as by advertising/marketing (e.g., via radio, print, television, promotional, live, direct mail, email, or telemarketing) and/or by providing a manner in which the customer 504 can seek out and peruse the products and/or services offered by the merchant 506, such as via a print catalog, a retail store, an on-line store, .or through any combination thereof.
  • advertising/marketing e.g., via radio, print, television, promotional, live, direct mail, email, or telemarketing
  • the customer 504 preferably places a desired order with the merchant 506 by first generating a written order form 508, representative of PURCH_DATA (e.g., such as PURCH_DATA 70 of FIG. 3), and then transmitting the written order form 508 to the merchant 506 via a written order transmission method 512.
  • the customer 504 may generate and print the written order form 508 automatically, using a computer system (not shown), such as the customer system 18 (of FIG.
  • the customer 504 also preferably is capable of utilizing a customer communication device 514 (such as a telephone or equivalent), to communicate with the FSP 34 during order verification (as described below in connection with FIG. 12).
  • a customer communication device 514 such as a telephone or equivalent
  • the written order transmission method 512 may involve utilization of a postal mail service or equivalent (e.g., courier), in which case the written order form 508 is received by the merchant 506 after a period of time, commensurate with the geographic distance of the merchant 506 from the customer 504, and with the type of transmission method 512 used (e.g., postal mail or courier service).
  • a postal mail service or equivalent e.g., courier
  • the written order transmission method 512 may be a facsimile transmission, in which case the customer 504 transmits the written order 508 to the merchant 506 by using a facsimile device (or equivalent - e.g., a computer equipped with facsimile hardware and/or software) (not shown) through a communication network, and the merchant 506 utilizes a facsimile device or equivalent (which may be optionally incorporated into a merchant written order processing system 510) linked to a communication network, to receive the transmitted written order form 508.
  • the written order form 508 is in electronic mail format, in which case the written order transmission method 512 may involve transmission of an electronic mail message containing (or representative) of the written order from 508, through the Internet or through another communication network.
  • the merchant 506 may utilize the merchant written order processing system 510 to process one or more various types of the written order form 508, to extract the PURCH_DATA therefrom so that ORDER_DATA (e.g., ORDER_DATA 72 of FIG. 3), and, optionally ORDER_CONF (e.g., ORDER_CONF 74 of FIG. 3), may be generated.
  • ORDER_DATA e.g., ORDER_DATA 72 of FIG. 3
  • ORDER_CONF e.g., ORDER_CONF 74 of FIG. 3
  • the merchant written order processing system 510 may include one or more computer systems (not shown) with manual and/or automatic data entry capabilities to optimize extraction of PURCH_DATA from a received written order form 508, and/or one or more facsimile devices (not shown) for receiving written order forms by facsimile, and/or an electronic mail communication system for receiving written order forms by electronic mail.
  • the system 500 operates in a substantially similar manner to the system 10 of FIG. 1 with two key differences: (1) the way in which the customer 504 communicates the PURCH_DATA for the order to the merchant 506 (i.e., via a written order form 508 sent by the written order transmission method 512); and (2) the requirement that the merchant 506 extract the PURCH_DATA from the- written order form 508 in order to generate the ORDER_DATA, and, optionally ORDER_CONF.
  • ORDER_CONF may be sent by any other means, such as via electronic mail, and/or an SMS, MMS, or other message to the customer 504's mobile communication device (not shown), assuming that the customer 504 previously provided the merchant 506 with their corresponding electronic mail address and/or mobile communication device contact number (for example, by including such information on the written order form 508 sent to the merchant 506).
  • FIG. 12 and FIG. 3 an exemplary embodiment of the process of operation of the system 500, is shown as a process 550.
  • the process 550 begins at a step 552, when the customer 504 selects a product and/or service offered by the merchant 506.
  • the customer 504 places the order for the selected product and/or service by generating and sending the written order form 508, containing PURCH_DATA 70 for the order, to the merchant 506 utilizing the written order transmission method 512.
  • the merchant 506 receives the written order form 508, and utilizes the merchant written order processing system 510 to process the written order form 508 to extract the PURCH_DATA 70 therefrom.
  • the merchant 506 then generates the ORDER-DATA 72 from the PURCH_DATA 70 and transmits the ORDER_DATA 72 to the FSP 34 (via the TPC 32, or directly).
  • the FSP 34 determines if PREL_APP should be issued to the merchant 506, based on whether the customer 504's payment instrument identified in the PMTJNFO portion of the ORDER_DATA 72, has access to sufficient funds through the customer 504 financial account with t ⁇ e FSP 34, to make a payment to the merchant 506 in the amount of the CHARGE_$.
  • the FSP 34 provides a PMT_DEC notice to the merchant 506 (which can then be communicated to the customer 504 in accordance with the merchant 506's business policies (e.g., before or after cancellation of the order placed by the customer 504 at the step 554), and the process 550 then ends at a step 564.
  • the process 550 proceeds to an optional step 566, where the merchant 506 provides the customer 504 with ORDER_CONF by the written order transmission method 512 or through other means.
  • the step 566 is optional, because the customer is likely to retain a copy of the written order form 508 which can serve the same purpose as ORDER_CONF during an order verification process.
  • an order verification process is performed (through interaction between the customer 504 and the FSP 34) to ensure that the order placed at the step 554 was in fact placed by the authorized holder of the financial account to which the payment instrument identified by the PMTJNFO is linked.
  • the order verification process of step 568 may be either one of the advantageous order verification processes 100, and 150, shown in FIG. 4 and FIG. 5, respectively. If the. order is verified at the step 568, then the FSP 34 authorizes the appropriate payment to the merchant 506.
  • the process 550 then ends at the step 564-; All order-transaction events occurring after that time (e.g., order fulfillment by the merchant 506, etc.) occur in the same manner as do current conventional post-order transactions.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système et un procédé permettant d'exécuter des transactions commerciales sécurisées à distance entre des clients (14) et des entités commerciales (16). Le système et le procédé de l'invention garantissent que les données financières complètes confidentielles du client (CFD) ne sont jamais transmises à l'entité commerciale en maintenant lesdites données CFD propriété du fournisseur de services financiers (FSP) existant du client avec lequel le client a établi un compte financier, et duquel l'entité commerciale est autorisée à recevoir des paiements. Lorsqu'une commande est passée, le client fournit à l'entité commerciale des données CFD partielles (PCFD) suffisantes, avec des données supplémentaires, pour identifier le FSP auprès de l'entité commerciale, et pour identifier le client auprès du FSP. L'entité commerciale fournit alors les données PCFD, avec au moins des données de commande partielles, au FSP, et des données de confirmation de commande (OCD) au client. L'invention concerne également divers modes de réalisation d'un nouveau procédé (68) de vérification de commande permettant au client d'autoriser la commande, par contact entre le client et le FSP. Les données CFD complètes sont ainsi entièrement sécurisées puisqu'elles restent la propriété du client et du FSP. Le FSP a éventuellement l'opportunité d'offrir des services et/ou des produits supplémentaires au client lors de l'authentification de la commande, associés ou non associés à la commande. Le système et le procédé de l'invention fonctionnent avantageusement aussi bien pour les commandes électroniques (par exemple en ligne) interactives que pour les commandes téléphoniques, les commandes commerciales mobiles, les commandes par fax, les commandes par courrier, et même les commandes faites en personne.
PCT/US2004/039003 2004-11-17 2004-11-17 Systeme et procede d'execution de transactions commerciales securisees WO2006055002A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2004/039003 WO2006055002A1 (fr) 2004-11-17 2004-11-17 Systeme et procede d'execution de transactions commerciales securisees

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2004/039003 WO2006055002A1 (fr) 2004-11-17 2004-11-17 Systeme et procede d'execution de transactions commerciales securisees

Publications (1)

Publication Number Publication Date
WO2006055002A1 true WO2006055002A1 (fr) 2006-05-26

Family

ID=36407443

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/039003 WO2006055002A1 (fr) 2004-11-17 2004-11-17 Systeme et procede d'execution de transactions commerciales securisees

Country Status (1)

Country Link
WO (1) WO2006055002A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014043038A1 (fr) * 2012-09-11 2014-03-20 Equinox Payments, LLC Terminal de transactions financières
EP2731065A1 (fr) * 2012-11-08 2014-05-14 Chien-Kang Yang Procédé de traitement d'un paiement et système et dispositif électronique pour la mise en oeuvre de ce procédé

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5715314A (en) * 1994-10-24 1998-02-03 Open Market, Inc. Network sales system
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5899980A (en) * 1997-08-11 1999-05-04 Trivnet Ltd. Retail method over a wide area network
US6246996B1 (en) * 1994-09-16 2001-06-12 Messagemedia, Inc. Computerized system for facilitating transactions between parties on the internet using e-mail
US6282522B1 (en) * 1997-04-30 2001-08-28 Visa International Service Association Internet payment system using smart card
US6332134B1 (en) * 1999-11-01 2001-12-18 Chuck Foster Financial transaction system
US20020046189A1 (en) * 2000-10-12 2002-04-18 Hitachi, Ltd. Payment processing method and system
US20020069165A1 (en) * 2000-12-06 2002-06-06 O'neil Joseph Thomas Efficient and secure bill payment via mobile IP terminals

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6246996B1 (en) * 1994-09-16 2001-06-12 Messagemedia, Inc. Computerized system for facilitating transactions between parties on the internet using e-mail
US5715314A (en) * 1994-10-24 1998-02-03 Open Market, Inc. Network sales system
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US6282522B1 (en) * 1997-04-30 2001-08-28 Visa International Service Association Internet payment system using smart card
US5899980A (en) * 1997-08-11 1999-05-04 Trivnet Ltd. Retail method over a wide area network
US6332134B1 (en) * 1999-11-01 2001-12-18 Chuck Foster Financial transaction system
US20020046189A1 (en) * 2000-10-12 2002-04-18 Hitachi, Ltd. Payment processing method and system
US20020069165A1 (en) * 2000-12-06 2002-06-06 O'neil Joseph Thomas Efficient and secure bill payment via mobile IP terminals

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014043038A1 (fr) * 2012-09-11 2014-03-20 Equinox Payments, LLC Terminal de transactions financières
US9123037B2 (en) 2012-09-11 2015-09-01 Equinox Payments, Llc. Financial transaction terminal
EP2731065A1 (fr) * 2012-11-08 2014-05-14 Chien-Kang Yang Procédé de traitement d'un paiement et système et dispositif électronique pour la mise en oeuvre de ce procédé
US10108958B2 (en) 2012-11-08 2018-10-23 Chien-Kang Yang Method for processing a payment, and system and electronic device for implementing the same

Similar Documents

Publication Publication Date Title
US20060106699A1 (en) System and method for conducting secure commercial order transactions
US10579977B1 (en) Method and system for controlling certificate based open payment transactions
US5903878A (en) Method and apparatus for electronic commerce
US7635084B2 (en) Electronic transaction systems and methods therefor
US8543497B1 (en) Secure authentication payment system
US20100179906A1 (en) Payment authorization method and apparatus
US20030130958A1 (en) Electronic transactions and payments system
US20070063017A1 (en) System and method for securely making payments and deposits
US20060173776A1 (en) A Method of Authentication
AU2002315501A1 (en) Secure authentication and payment system
MX2011002067A (es) Sistema y metodo de transacciones de pago seguras.
KR20100054757A (ko) 대역밖 인증을 이용한 지불 거래 처리
WO2007047901A2 (fr) Systemes et procedes de prevention de la fraude sur les cartes de credit
JP2004527861A (ja) 安全な現金を使用しない支払取引を行うための方法および現金を使用しない支払システム
US20020082986A1 (en) Method for payment in exchange
US20040054624A1 (en) Procedure for the completion of an electronic payment
EP1134707A1 (fr) Procédé et dispositif d'authorisation de paiement
KR100372683B1 (ko) 개인 휴대단말기를 이용한 사용자 인증 처리 시스템 및 그방법
US6938160B2 (en) Network service user authentication system
CA2347396A1 (fr) Methode et systeme pour effectuer des transactions financieres electroniques anonymes protegees
WO2006055002A1 (fr) Systeme et procede d'execution de transactions commerciales securisees
WO2009108066A1 (fr) Procédé et agencement pour des transactions sécurisées
GB2360383A (en) Payment authorisation
WO2002003214A1 (fr) Systeme de certification
Pisko Enhancing Security of Terminal Payment with Mobile Electronic Signatures

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 04811684

Country of ref document: EP

Kind code of ref document: A1