EP1687764A4 - Systeme et methodes de traitement de carte de paiement - Google Patents

Systeme et methodes de traitement de carte de paiement

Info

Publication number
EP1687764A4
EP1687764A4 EP03749468A EP03749468A EP1687764A4 EP 1687764 A4 EP1687764 A4 EP 1687764A4 EP 03749468 A EP03749468 A EP 03749468A EP 03749468 A EP03749468 A EP 03749468A EP 1687764 A4 EP1687764 A4 EP 1687764A4
Authority
EP
European Patent Office
Prior art keywords
account
dual card
card
private label
customer
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
EP03749468A
Other languages
German (de)
English (en)
Other versions
EP1687764A1 (fr
Inventor
Peter Jones
Jim Mitchell
Mike Brumfitt
Deborah Falkingbridge
Robert Humphreys
Stewart Macphail
Jeremy Shreurs
Amanda Atherton
Ross Marshall
Lockie Carolyn
Jeffrey V Manchester
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
General Electric Co
Original Assignee
General Electric Capital Corp
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 General Electric Capital Corp filed Critical General Electric Capital Corp
Publication of EP1687764A1 publication Critical patent/EP1687764A1/fr
Publication of EP1687764A4 publication Critical patent/EP1687764A4/fr
Ceased legal-status Critical Current

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/403—Solvency checks
    • G06Q20/4037—Remote solvency checks
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/357—Cards having a plurality of specified features
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/357—Cards having a plurality of specified features
    • G06Q20/3576—Multiple memory zones on card
    • 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
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
    • G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system

Definitions

  • Embodiments of the present invention relate to a payment card processing system and method. More particularly, embodiments relate to a payment card processing system that allows a payment card to be used on two different payment networks.
  • a number of different types of payment card are available.
  • one common type of payment card is a credit card or bankcard issued by a bank or other financial institution.
  • Many credit cards are issued pursuant to the rules of one or more credit card associations.
  • banks issue credit cards pursuant to the rules of associations or companies such as VISA®, MasterCard®, DISCOVER® or American Express® (e.g., for their Optima® brand cards).
  • the bank that issues the credit card is referred to as the "issuer" of the card.
  • Transactions using the card are routed through the "bankcard networks". The routing typically depends on the card association under which the card is issued (e.g., a credit card issued pursuant to the MasterCard® rules will typically be routed using the MasterCard® processing networks).
  • Credit cards allow a cardholder to purchase goods and services at a wide number of merchant locations. Credit cards allow cardholders to pay off charges on a monthly basis or a cardholder may choose to pay a portion of the outstanding balance each month. Any unpaid balance typically is subject to interest charges. The cardholder may pay an annual fee as well. Often, issuers of these credit cards provide a number of different levels of card. For example, a bank may issue credit cards ranging from a standard card, to premium cards such as a "Gold Card” or a "Platinum Card". Each level may have different annual charges, different interest rates, and different cardholder services. The issuer issues each account with a credit limit depending upon the credit worthiness of the cardholder. Each transaction conducted with the card may involve one or more interchange fees paid to the credit card association. For example, a merchant may be assessed an interchange fee based upon a percentage of the amount of each transaction conducted using a credit card.
  • a second type of card is a "charge card” such as the American Express® series of charge cards.
  • Charge cards allow cardholders to charge purchases and services to the account. The cardholder is expected to pay the balance in full monthly. There is usually no interest charged. Charge cards often have a higher account limit than credit cards. This limit often is established based on a cardholder's usage history. There is an annual fee paid by the cardholder and the merchant typically is assessed an interchange fee. For example, the interchange fee assessed by American Express is usually higher than the interchange fee assessed by other bankcard networks. Charge card and bankcard transactions are typically processed using bankcard networks (such as those operated by VISA®, MasterCard®, American Express®, etc.).
  • a third type of card is a "private label" credit card.
  • a private label credit card is a payment card issued by (or in conjunction with) a merchant such as Wal-Mart, Harrods, Sears, or Brooks Brothers. Some private label cards are issued and serviced by the merchant, while others are issued and serviced by a financial institution acting in conjunction with the merchant. From the cardholder's perspective, a transaction involving a private label card is similar to a transaction involving a bankcard or charge card — the cardholder presents the card for payment at a merchant and is later invoiced for the transaction. However, unlike most bankcard or charge cards, a private label card can only be used at merchant locations associated with the sponsoring merchant. For example, a Sears private label card can only be used for purchases at Sears (or designated Sears affiliates). A private label cardholder may be required to pay the monthly balance in full
  • the merchant pays the financial institution a fee similar to the interchange fee of a bankcard. This fee is usually lower than the interchange fee associated .with bankcard transactions.
  • the networks that are used to process private label card transactions are frequently different than the networks that are used to process bankcard transactions.
  • a private label card transaction is typically routed through a closed network or a limited access network that has been established or configured specially for a particular private label merchant. This limited access provides some benefits to private label cardholders.
  • private label merchants are able to offer incentives, promotions, and enhanced statement details which are better in many respects to those available through the bankcard networks.
  • One advantage of the private label card is the availability of special promotional financing offers (such as "no interest for x months" promotions) and merchandise information from the issuer or associated merchant of the private label credit card.
  • the primary advantage of the bankcard is the almost universal acceptance world wide of a VISA® card, MasterCard®, or DISCOVER® card. These cards also typically have lower interest rates.
  • a number of solutions to this problem have been suggested, including the issuance of payment cards which have multiple magnetic stripes (each encoded with different account numbers for each card replaced), magnetic stripes encoded with multiple account numbers, smart cards storing account information for each different account to be accessed, etc. None of these solutions provide a desirable solution to the technical problem of allowing a single payment card to provide features of different products.
  • the technical problem is exacerbated by the fact that different types of payment cards may be routed using different networks having different protocols. Further, different accounts may be hosted on, or processed using, different processing platforms. Accordingly, there is a need for a payment card that provides merchants, cardholders, and issuers the benefits of both a bankcard and a private label card and which can be routed and used with existing bankcard and payment card networks and processing platforms.
  • the present invention introduces systems, methods, apparatus, computer program code and means for upgrading accounts, including selecting a private label account maintained on a first processing platform for upgrade to a dual card account, the private label account associated with an account holder and having associated monetary and non-monetary data; creating the dual card account with a zero balance on a second processing platform; transferring the non-monetary data associated with the private label account to the second processing platform for association with the dual card account; and causing a dual card associated with the dual card account to be transmitted to account holder, the dual card and the dual card account being inactive until activated.
  • private label accounts can be upgraded individually (e.g., at the request of a cardholder) or in groups.
  • an activation process is provided to transfer monetary data associated with the private label account to the dual card account.
  • a trailing activity process is provided to ensure that monetary and non-monetary transactions associated with the private label account are reflected in the dual card account.
  • systems, methods, apparatus, computer program code and means for processing an application for a new account including receiving an application for a new account, the application including sponsoring merchant information, customer information and a proposed transaction amount; performing a credit analysis based on the customer information; determining, based at least in part on the credit analysis, to issue one of a private label card and a dual card to the customer; communicating an approval to the customer; providing a temporary card to the customer, the temporary card having an account number associated with one of the private label card and the dual card and available for purchases at the sponsoring merchant; charging the transaction amount using the temporary card.
  • systems, methods, apparatus, computer program code and means for activating an account including receiving, from a customer, a request to activate a dual card; updating a risk profile of the customer; confirming that the customer remains eligible for the dual card; confirming that the customer desires to activate the dual card; and transferring monetary data from a private label processing platform to a dual card processing platform to complete an activation of the dual card account.
  • systems, methods, apparatus, computer program code and means for routing a transaction including generating an authorization request, the request including a transaction amount and an account identifier, the account identifier including a portion identifying an issuer of the account and a portion identifying a type of the account; routing the authorization request to the issuer via a first authorization network if the account identifier indicates that the account is a first type of account; and routing the authorization request to the issuer via a second authorization network if the account identifier indicates that the account is a second type of account.
  • FIG. 1 is a block diagram depicting a payment card system pursuant to some embodiments of the present invention.
  • FIGs. 2A-2B are flow charts of methods for performing an account conversion pursuant to some embodiments of the present invention.
  • FIG. 3 is a diagram illustrating data structures used tin conjunction with the account conversion methods of FIG. 2.
  • FIG. 4 is a flow chart of a method for performing a new account application process pursuant to some embodiments of the present invention.
  • FIG. 5A-5D are flow charts of methods for activating dual cards issued pursuant to embodiments of the present invention.
  • the term "payment card” is used to refer to a financial transaction card that is issued by a financial institution (the “issuer") to a customer (the “cardholder”) for use in conducting transactions to be charged or credited to a financial account (the “card account”).
  • a financial institution the “issuer”
  • the customer the “cardholder”
  • a financial account the financial account
  • a “dual card” introduced herein (which combines features of different types of payment cards)
  • a “bankcard” and a “private label card”.
  • a “private label card” is a payment card which is issued by (or in conjunction with) a sponsoring merchant (the “private label merchant” or the “homebrand”) and which can only be used for purchases at sponsoring merchant locations.
  • a dual card similar to a bankcard
  • a primary account number identifying the financial account accessed by the card
  • BIN card number embossed on, or otherwise associated with the card
  • both of these identifiers may generally be referred to herein as the "account identifier" associated with the dual card.
  • BINs are selected in a manner that identifies a payment card as a dual card product.
  • BINs are further selected to identify the particular homebrand merchant associated with a dual card.
  • dual card is used to refer to a payment card product that has functionality as a private label card and as a bankcard.
  • each dual card is associated with a dual card account.
  • a private label account is upgraded to become a dual card account, the same account is used (that is, the cardholder does not receive a new account relationship with the issuer, instead, the cardholder receives a new card to access the existing account
  • bankcard refers to a credit, debit or charge card which is associated with a “bankcard network”.
  • bankcard network refers to processing networks established and/or operated on behalf of bankcard issuers or associations such as, for example, the networks operated by (or on behalf of) Visa International Service Association (or "VISA®”), MasterCard International®, American Express®, etc.
  • Other bankcard networks include regional or local networks that may operate in conjunction with other bankcard networks (e.g., such as the Plus network or the Switch network).
  • bankcard network refers to any of these types of networks or other networks that are used to route and process bankcard transactions at multiple merchant locations and cash machines (e.g., such as merchant locations accepting VISA or MasterCard branded payment cards).
  • private label network is used to refer to processing networks that are established and/or operated on behalf of particular private label card programs.
  • a retailer may operate a private label network to process private label card transactions made at any of its retailer locations.
  • a retailer may contract with a merchant acquirer or other processing entity to operate a private label network for the retailer.
  • these private label networks allow a number of processing features that are not available for transactions conducted using bankcard networks.
  • many private label networks allow the capture and transmission of "enhanced data" or item level details associated with purchases.
  • many private label networks allow the application of loyalty and promotional programs.
  • Embodiments provide a payment card processing system that enables a single payment card to be processed over both private label and bankcard networks.
  • a system, method, apparatus, means and computer program code are provided for processing a payment card transaction which utilizes a card (referred to herein as a "dual card” or a “dual credit card” or a “dual purpose card”) which is issued to a cardholder and which is issued in conjunction with both a sponsoring merchant (the "private label merchant” or the "homebrand merchant") and a sponsoring bankcard association (e.g., such as VISA® or MasterCard®).
  • a sponsoring merchant the "private label merchant” or the "homebrand merchant”
  • a sponsoring bankcard association e.g., such as VISA® or MasterCard®.
  • Each dual card is associated with a single account having an account identifier.
  • Each transaction using the dual card is processed based on the account identifier.
  • the account identifier For transactions conducted at a merchant location that is a private label merchant, the account identifier will cause the transaction to be processed using a private label processing network. For transactions conducted at a merchant location that is not a private label merchant, the account identifier will cause the transaction to be processed using a bankcard network.
  • information associated with both types of transactions is provided to the cardholder in a single statement.
  • private label transactions may include additional transaction detail (e.g., such as detailed information about each product purchased at a private label merchant).
  • private label transactions are eligible for additional services provided by private label merchants (e.g., such as additional loyalty programs, promotional programs, etc.). In this manner, embodiments provide cardholders with the benefits of a private label card and the ease and convenience of a bankcard. A single account is opened for each cardholder, and a single card is used to access the account.
  • a dual card is issued to a consumer upon receipt of an application by the consumer or upon a customer "opting in” (or not “opting out") of an upgrade invitation/notification.
  • customers apply for a dual card by making an application at a sponsoring merchant location.
  • the issuance or approval process begins with the receipt of the application by the merchant.
  • the issuing organization determines the interest rate and the credit line and may issue the dual card to the applicant. This is a combined private label and bankcard product with one interest rate and one credit line.
  • the dual card includes features of both a private label card and a credit card, and may have one or more credit plans associated with it (e.g., a different interest rate may apply depending on whether the card is used for purchases at the homebrand, at bankcard merchants, for balance transfers, etc.).
  • the dual card is associated with a single account and has a single credit line.
  • the credit line may have a portion that is available only at the merchant's location.
  • the issuer of the dual card will determine the size of the single credit line and the interest rate. Further details of the issuance (and later activation) will be provided below.
  • certain private label cardholders may be selected to receive an invitation to/notification of upgrade from their existing private label card to a dual card. These cardholders may accept the invitation by opting in or remain eligible as a result of not opting out following notification. At the end of a predetermined period, these cardholders receive a personalized dual card that is ready for activation, and that may be used after activation.
  • the cardholder may make a purchase with the dual credit card at either a private label merchant location or at a location accepting the bankcard.
  • Either location may be an Internet site or a physical location.
  • a location includes physical locations as well as Internet, mail order, telephone or other remote transactions.
  • the processing or routing of the purchase is done via a private-label processing channel.
  • the private-label channel interchange fee (if any) is paid as part of this process.
  • the private label back office operation processes the merchant location purchase as a private label purchase and then feeds the transaction to the dual card issuer or other processor (e.g., such as an issuer processor acting on behalf of the dual card issuer). Details of the transaction are then incorporated into the dual card balance and statement and settlement with the merchant occurs.
  • the purchase is processed or routed through a bankcard network. Any associated network interchange fees are paid as part of this process.
  • the cooperating back office operation processes the non-merchant purchase as a bankcard purchase.
  • One feature of some embodiments is the use of a common back office facility for both bankcard purchases and private label purchases.
  • cardholder statements may include merchant promotion material as well as normal operational customer service matters for both the merchant channel as well as the bankcard channel.
  • the customer service functions may include normal customer service matters as well as collections and settlement issues.
  • FIG. 1 is a block diagram overview of a payment card processing system 10 according to some embodiments of the present invention.
  • system 10 is shown having an issuer 24 operating a private label processing platform 30 and a bank card processing platform 40 to process payment card transactions received over a private label network 20 and a bankcard network 22.
  • These payment card transactions may originate from a number of locations, including for example from a homebrand retailer 14, a non-homebrand retailer 16, an automated teller machine (ATM) 18, etc.
  • ATM automated teller machine
  • transactions at any of these locations using a dual card 12 may be processed using system 10.
  • two separate processing platforms are shown, embodiments may also be implemented using a single processing platform, where private label and bank card account information is separated (e.g., in separate account databases).
  • a transaction involving dual card 12 is routed either through private label network 20 or bankcard network 22 depending on whether or not the transaction involves a homebrand merchant (such as the homebrand mechant 14).
  • a transaction involving dual card 12 and a merchant which sponsors the dual card 12 (the homebrand merchant) will be routed to issuer 24 via private label network 20.
  • a transaction involving dual card 12 and a merchant other than the homebrand merchant will be routed to issuer 24 via bankcard network 22.
  • a transaction involving dual card 12 and an ATM will be routed to issuer 24 through the bankcard network 22.
  • Homebrand merchant 14 may also accept other bankcards for purchases.
  • point of sale terminals at the homebrand merchant 14 may conduct transactions involving at least three different types of payment cards: dual cards (as introduced herein); private label cards (usable only at the homebrand merchant); and normal bankcards.
  • dual cards as introduced herein
  • private label cards usable only at the homebrand merchant
  • normal bankcards normal bankcards.
  • a communication path is shown between homebrand merchant 14 and bankcard network 22 to indicate that, in many configurations, when a bankcard is presented for a purchase at a homebrand merchant, the bankcard transaction is routed through the bankcard network 22.
  • private label network 20 is a public switched X.25 network that uses APACS 30-standard financial messages
  • bankcard network 22 is the MasterCard network using ISO 8583 standard messages.
  • issuer 24 operates two processing platforms: a private label platform
  • issuer 24 may issue both private label cards and bankcards.
  • Account data associated with each type of payment card are stored at databases 36, 46. Those skilled in the art will appreciate that the account data may actually be stored in a single database or single data store where each type of account is separated by a logical partition or by separate account structures.
  • Private label processing platform 30 is coupled to receive transaction data from private label network 20. Authorization requests received via the private label network are authorized using a private label authorization module 32 and transactions are settled using a private label settlement module 34.
  • a number of different processing platforms may be used as private label processing platform 30.
  • private label processing platform 30 is based on the CARDPAC platform offered by PaySys International Inc.®.
  • a routing module 25 is provided to determine whether transaction messages received via private label network 20 should be passed to private label processing platform 30 or to bankcard processing platform 40 for authorization. For example (as will be discussed further below), routing module 25 may route a dual card transaction to bankcard processing platform 40, and a private label transaction to private label processing platform 30.
  • Bankcard processing platform 40 is coupled to receive transaction data from bankcard network 22 (or from private label network 20 via routing module 25). Authorization requests received at the bankcard processing platform 40 are authorized using a bankcard authorization module 42 and transactions are settled using a bankcard settlement module 44.
  • bankcard processing platform 40 is based on the VisionPLUS platform offered by PaySys International Inc.
  • both the bankcard processing platform 40 and the private label processing platform 30 may interact with other entities to authorize and settle transactions.
  • stand in processing may be performed by an intermediary (e.g., such as a merchant acquirer or other processor) to provide stand in authorization processing.
  • private label processing platform 30 and bankcard processing platform 40 may be the same platform (e.g., both platforms may be implemented using the VisionPLUS platform), but have separate account structures and datastores. Similar processing to upgrade and cross reference private label accounts and dual card accounts will be used as in embodiments in which the private label processing platform 30 and the bankcard processing platform 40 are separate or different.
  • Issuer 24 also operates (or interacts with) one or more support systems 50 to provide supporting functionality that may be used pursuant to some embodiments.
  • issuer 24 may operate (or interact with) an embossing or personalization function 52 to create embossed or personalized dual cards pursuant to the present invention.
  • a customer service function 54 may also be provided to support dual card activation and customer services activities.
  • Customer service function 54 may include the use of one or more front line associates ("FLAs") or customer service representatives as well as integrated voice response (“IVR”) units to respond to customer activation requests as well as other customer inquiries.
  • customer service function 54 may also include a Web front-end allowing customers to interact with customer service function 54 over the Internet (e.g., to request individual account upgrades as discussed in conjunction with FIG.
  • a risk and credit analysis function 56 is used to analyze potential new dual card accounts, establish pricing and establish credit lines.
  • the issuer also maintains a general ledger 58.
  • a statement generation function 60 is also operated by (or on behalf of) the issuer to generate account statements for dual card customers (including transactions made at both homebrand and non-homebrand locations).
  • a homebrand 14 may include a number of different point of sale devices, including retail point of sale terminals, Internet sales locations, mail order or telephone ("MOTO") locations, etc. Each of these locations may process transactions using dual cards by routing transaction information to the issuer 24 via a private label network 20. Further, there may be a number of different homebrand programs associated with different programs issued by issuer 24. For example, issuer 24 may issue dual cards in conjunction with several major retailers. Each of these retailers may operate (or be associated with) separate private label processing networks 20 that route transactions from their merchant locations to issuer 24. Further still, there may be a number of different issuers that issue dual cards pursuant to embodiments of the present invention. Transaction Examples
  • the cardholder presents dual card 12 to a sales representative at a homebrand retailer location to make a purchase.
  • the sales representative may key the dual card account identifier into a card terminal or the dual card may be swiped or presented to a card reader to read the account identifier.
  • the account identifier along with other transaction information, is transmitted in a request message to request authorization of the purchase.
  • the account identifier embossed or stored on dual card 12 identifies the dual card as a payment card that is routed via private label network 20. This identification may be made by a routing table stored in (or accessible to) the homebrand merchant's point of sale system or it may be made by a merchant acquirer (not shown) associated with the homebrand merchant.
  • the account identifier, along with transaction details, is routed to issuer 24 (or to a stand in processor) via private label network 20 for authorization.
  • Private label processing platform 30 identifies the incoming authorization as an authorization associated with a dual card and routes the transaction to bankcard processing platform 40 for authorization (although, in some embodiments, private label processing platform 30 may be assigned stand in authorization responsibilities on behalf of the bankcard platform 40).
  • Issuer 24 authorizes the transaction if the transaction complies with relevant authorization criteria. Settlement information may be captured along with the authorization or may be received in a batch file submitted by the merchant, causing the dual card account database 46 to be updated to reflect the purchase transaction. Dual card transactions which involve the homebrand retailer (and which are routed via the private label network 20 for authorization) may enjoy processing benefits generally unavailable to bankcards.
  • homebrand transactions may include "enhanced data" associated with purchases made at the homebrand retailer.
  • this enhanced data is provided in an authorization or settlement message transmitted to the issuer 24, and may include detailed information about the merchant location, the product purchased, etc. This information is presented to the customer on his statement, allowing the customer to have a highly detailed and accurate listing of items purchased at homebrand retailers.
  • homebrand transactions may enjoy promotional or loyalty benefits not typically available to purchases made with bankcards. These promotional or loyalty benefits may be based, at least in part, on the enhanced data associated with dual card purchases at homebrand retailers. Further, in some embodiments, private label network processing is subject to lower interchange fees than bankcard network transactions, providing homebrand retailers with less expensive transactions.
  • promotion or loyalty benefits may be applied during settlement processing.
  • Settlement processing may be performed as a batch process on a regular basis.
  • homebrand merchant 14 may send a daily settlement file to issuer 24 including transaction details associated with the day's transactions which were conducted with the issuer's PLCC cards and the issuer's dual cards.
  • issuer 24 including transaction details associated with the day's transactions which were conducted with the issuer's PLCC cards and the issuer's dual cards.
  • the cardholder presents dual card 12 to a sales representative at a non-homebrand retailer location to make a purchase (or inserts the dual card into an ATM to retrieve cash).
  • the account identifier identifies the card as a bankcard and also identifies the issuer so that an authorization request may be routed to the issuer 24 via the bankcard networks 22 for authorization.
  • Issuer 24 authorizes the transaction if the transaction complies with relevant authorization criteria. Settlement information may be captured along with the authorization or may be received in a batch file submitted by the merchant, causing the dual card account database 46 to be updated to reflect the purchase transaction.
  • embodiments allow a single card, accessing a single account, to be used at different types of merchant locations and be processed using at two different types of networks (each of which provides different benefits to the customer and to the issuer). Other features and benefits will become apparent to those skilled in the art upon reading this disclosure. Further details will now be provided describing various approaches to the creation, activation, and management of dual card accounts.
  • existing private label account holders may have their private label accounts upgraded to dual card accounts and be issued a dual card to replace their private label card.
  • a number of different account upgrade processes may be utilized pursuant to embodiments of the present invention, including processes adapted to upgrade large numbers of existing cardholders (which will be discussed in conjunction with FIG. 2A) and processes to upgrade individual cardholders (which will be discussed in conjunction with FIG. 2B).
  • FIG. 2A is a flow chart of one embodiment of a method 100 for upgrading groups of existing private label cardholders into dual card cardholders.
  • the flow charts described herein do not imply a fixed order to the steps, and embodiments of the present invention may be practiced in any order that is practicable.
  • Method 100 may be performed by, or on behalf of, issuer 24.
  • an "opt out" system may be used (e.g., where an existing cardholder may be given the opportunity to opt out of a dual card opportunity).
  • an "opt in” system may be used, where an existing cardholder may be required to affirmatively opt in to take advantage of a dual card opportunity. Both embodiments will be described in conjunction with FIG. 2A.
  • Processing begins at 102 where existing customer data is retrieved from private label processing platform 30 (e.g., from private label account database 36 associated with private label processing platform 30). In some embodiments, only selected customer data is retrieved at 102 (e.g., such as customer data meeting a minimum risk threshold, etc.). Processing continues at 104 where the customer data retrieved at 102 is further processed to select existing customers to receive an invitation to upgrade/notification of upgrade of their existing private label account to a dual card account. In some embodiments, processing at 104 includes flagging each selected customer's account with an indicator designating the account as associated with a customer having been selected for an invitation/notification. In this manner, an issuer may ensure that a customer does not receive duplicate invitations/notifications. Processing at 104 may include further risk or credit scoring to identify suitable or desirable customers.
  • processing at 106 includes generating an invitation/notification letter that includes detailed terms and conditions associated with the proposed dual card account. Further, information may be provided indicating whether the customer can opt out of the upgrade notified (or, in some embodiments, whether the customer needs to take steps to opt in to accept the invitation). In some embodiments, a time flag is associated with each selected account to identify when the opt out period (or the opt in period) expires for each selected account.
  • certain information may not be sent to individual customers (instead, the information may be provided after a customer has opted in or even in conjunction with an activation process).
  • the invitation/notification communicated at 106 also includes a detailed listing and explanation of the terms of the proposed dual card account.
  • the terms may include a proposed credit limit, interest rate, and other terms associated with the dual card account.
  • an additional "retailer reserve" associated with the homebrand merchant may also be established and communicated to the customer at 106.
  • a homebrand merchant and/or the issuer 24
  • a customer may be issued a dual card having a credit limit of $1,000.
  • the homebrand merchant and/or the issuer 24) may determine that the customer is also eligible for a 10% retailer reserve.
  • This retailer reserve allows the customer to make an additional $100 of purchases at the homebrand, even though the outstanding balance on the dual card has reached its $1,000 credit limit.
  • the customer is reminded (or informed) of this retailer reserve amount when the customer's account balance nears the credit limit (e.g., the customer may be notified of the additional retailer reserve amount in the customer's monthly statement in a month in which the account balance is nearing the credit limit).
  • processing at 108 determines that the customer has accepted the invitation (or, has failed to opt out within the opt out period)
  • processing continues at 112 where a zero balance account is created on the dual card processing platform 40 (e.g., by assigning a new dual card account identifier to a new account record in dual card account database 46).
  • Customer information and other non- monetary details associated with the customer's private label account may also be associated with the new account record in the dual card account database 46. For example, sufficient information may be associated with the new account record to allow an inactive dual card to be personalized for the customer.
  • processing at 112 may include performing a risk reevaluation of the customer to ensure that there have not been any events that would disqualify the customer from upgrading to a dual card account. For example, this may include performing an additional risk or credit analysis to determine if the customer has experienced any defaults or other major credit events. If the risk reevaluation identifies that the customer is no longer eligible for the upgrade, a FLA may communicate this to the customer, and processing may terminate at 110. This risk reevaluation may be performed at a number of different times after the selection of an account for upgrade to ensure that an upgrade is not performed for a customer who is not eligible for the upgrade. For example, in some embodiments, a customer's credit risk is continually evaluated until the customer's account is ultimately activated (or declined).
  • a cross-reference table is updated to cross- reference the cardholder's private label account identifier with the new dual card account identifier assigned at 112.
  • this cross- reference table may be used to manage and identify any monetary and non-monetary trailing activity associated with the private label account.
  • the dual card is a magnetic stripe card and processing at 116 involves creating an embossing record.
  • the dual card is a smart card having a memory and processing at 116 involves creating a personalization record for personalizing the memory of the smart card (those skilled in the art will appreciate that the smart card personalization record may also include information used to emboss the smart card as well).
  • Information may be transferred to the embosser (or personalizer) in any of a number of different ways common in the art (e.g., by file transfer protocol, via a diskette or other storage device, etc.).
  • the embosser utilizes the information transferred at 116 to create a dual card personalized for the customer. Processing continues at 118 where the embossed (or personalized) dual card is sent to the cardholder along with information on how to activate the account for use. An activation process pursuant to some embodiments will be discussed further below in conjunction with FIG. 5. In some embodiments, during the time period after creation of the cross-reference table at 114 and before activation of the dual card, the private label account on the private label processing platform 38 is monitored to detect any non-monetary data changes.
  • processing associated with FIG. 2A may be performed on a batch basis to upgrade batches or groups of accounts.
  • processing associated with FIG. 2A may be structured to ensure that system processing impacts are eased. For example, invitations sent at 106 may be sent out in groups having similar opt out (or opt in) periods to ensure that processing - demands are spread over the course of a period of time.
  • FIG. 2B is a flow chart of a method 120 for upgrading individual accounts at the request of existing private label cardholders.
  • Method 120 may be performed by, or on behalf of, issuer 24.
  • Method 120 may be initiated by an existing customer who wishes to upgrade her private label account to a dual card account.
  • the method of FIG. 2B may involve upgrades of individual accounts based on customer-initiated requests for upgrade.
  • Processing begins at 122 where issuer 24 (or an agent of issuer 24) receives a request from an existing PLCC customer to upgrade a PLCC account to a dual card account. This request may be received in a number of different ways.
  • the request is received by a customer service Web site operated on behalf of issuer 24 (e.g., associated with customer service function 54 of FIG. 1).
  • the request is received by a FLA over a telephone or in person (e.g., staffing a kiosk at a homebrand merchant location).
  • the request is received by an interactive voice response (INR) unit.
  • ISR interactive voice response
  • the request is received by an operator or device coupled to receive and interact with account information from issuer 24.
  • the customer is required to provide account and other verifying information. Processing continues at 124 where the account and other verifying information is used to retrieve the customer's existing customer data from the PLCC platform.
  • processing at 126 may include determining whether the customer has previously been offered a dual card upgrade (and, if so, whether the current upgrade request should be terminated or allowed to proceed).
  • processing at 128 the issuer 24 (or an agent of the issuer) performs account scoring and other analyses to determine if the customer is eligible to upgrade to a dual card account, and, if so, the terms of the upgraded account. The terms are presented to the customer for approval.
  • a listing of different products may be presented for which the customer is eligible (e.g., if the customer is eligible for different levels of upgraded accounts, information about each of the different levels may be presented to the customer for their consideration).
  • processing continues at 130, a zero balance account is created on the dual card processing platform, and processing similar to the processing of FIG. 2A (processes 112-118) are performed to complete the issuance of a dual card account.
  • processing may continue at 132 where a cross-reference table is updated, associating the customer's PLCC account information with the dual card account established at 130.
  • Account and customer information is transferred to the embosser or personalizer to create the card and the card is sent to the customer for subsequent activation.
  • embodiments allow individual customers to take affirmative actions to upgrade their accounts from PLCC accounts to dual card accounts, thereby enjoying the added benefits and features of the dual card account.
  • FIG. 3 where a block diagram 80 depicts features of the conversion processes of FIGs. 2 A and 2B.
  • data is extracted from private label account database 36.
  • This selected account information is used to create a table 82 of selected private label account data and to manage the conversion process.
  • the table may include, for example, fields identifying the selected private label account identifiers, a status (e.g., such as "selected", “opted in”, “accepted”, etc.), a selection date, an elapse date (when the opt out, or opt in periods expire), a credit limit to be offered, etc.
  • a customer accepts an invitation to/does not opt-out of a notified upgrade a private label account to a dual card account (e.g., when the status indicates "accepted” or "opted in")
  • a dual card account is created and a cross-reference record (such as the records illustrated by table 84) is created associating the new dual card account identifier with the old private label account identifier along with other information.
  • This cross-reference record is used to ensure that any trailing activity associated with the private label account is properly associated in the dual card account.
  • the cross-reference record associates the private label account identifier with the dual card account identifier stored in the dual card account database 46 associated with the dual card processing platform 30 at issuer 24.
  • Table 86 represents sample dual card account database records. Similar tables may be created and used to assist in upgrades as described with reference to FIG. 2A. For example, when a current private label customer initiates a process to upgrade her account to a dual card account, the private label account data is extracted into a table such as table 82 and is referenced in a cross reference table 84 which associates the private label information with the newly created dual card account information. As will be described further below, the use of this cross-reference table allows embodiments to track and identify trailing activities associated with the private label account and appropriately update dual card account information to reflect the trailing activity.
  • the process of FIG. 2B may be initiated by a customer desiring an upgrade and may cause information to be used in a process similar to the process of FIG. 2A. For example, customer requests for upgrades may be processed and risk evaluated, and then added to the opt-in batch processing associated with FIG. 2A.
  • dual card accounts may be issued as both upgraded accounts (as described above in conjunction with FIGs. 2 and 3, for example) as well as new accounts.
  • New dual card accounts may be issued based on "in-store” applications received from new customers as well as other applications received from customers.
  • a new account application process will now be described by reference to FIG. 4, where an "in-store” application process is described.
  • FIG. 4 is a flow chart of a method 140 for performing a new account application process pursuant to some embodiments.
  • Method 140 may be performed by, or on behalf of, issuer 24.
  • Method 140 begins at 142 where the issuer (or an agent of the issuer) receives data from an in-store customer application (including information identifying a proposed transaction). For example, pursuant to some embodiments, customers shopping at homebrand merchant locations may be solicited to apply and receive either a private label card or a dual card. Customers may be offered an incentive to apply for a new account (e.g., such as 10% off the total amount of their purchases made at the homebrand retailer at the time of the application).
  • the dual card application is performed at the homebrand merchant's point of sale register.
  • the customer when the customer approaches the point of sale to purchase items, the customer is asked to complete an application form for either a private label card or a dual card.
  • the application form is designed to capture sufficient information to make a credit decision for issuance of either a private label card or a bankcard.
  • the application form allows the customer to opt-out of either the private label or the dual card products (that is, the customer may specify which card product he wishes to apply for).
  • Processing at 142 may include scanning or entering application information from the application form so that it may be communicated to the issuer 24 (or to an agent of the issuer responsible for performing new account scoring or decisioning).
  • Processing at 144 may involve, for example, referencing or communicating with third party resources (e.g., such as the account scoring resources of Experian Corp., or the like; similar scoring resources may be used in conjunction with other credit rating and evaluation processes described elsewhere herein). Processing at 144 may also include performing duplicate checks to ensure that the customer has not previously been issued a PLCC or dual card by the issuer 24.
  • the account decision may be to issue the customer a dual card account, to issue the customer a private label account, or to decline the customer for any account.
  • the customer may be approved for a private label account at 152 (if the customer has not opted out of the private label product).
  • Processing continues at 156 where a PLCC record and account information are created on the PLCC platform, including terms of the PLCC account (e.g., such as the credit limit and interest rate associated with the account).
  • Processing continues at 158 where a temporary account number is communicated to the sales representative. This temporary account number may be the same as the account number of the PLCC account established on the PLCC platform at 156. In some embodiments, this temporary account number is only useable for purchases made at the homebrand merchant and may be subjected to additional authorization controls (e.g., such as special floor limits, etc.).
  • processing proceeds from 146 to 148 where issuer 24 (or an agent of issuer) determines terms associated with the dual card account to be issued to the customer, including a dual card credit limit, a retailer reserve amount, and an interest rate. Other terms may also be determined at 148.
  • Processing at 148 includes creating a dual card account record and account information on the dual card platform.
  • Processing continues at 150 where, in some embodiments, the dual card account number established at 148 is used to issue a temporary card.
  • the account number may be provided to the sales representative at 160 so that the sales representative can provide a temporary card associated with the account number to the customer. In some embodiments, this temporary account number is only usable for purchases made at the homebrand merchant and may be subject to additional authorization controls (e.g., such as special floor limits, etc.).
  • the customer may be allowed to make purchases at homebrand merchant locations during the period between when the new account is approved and when the customer actually receives his embossed card for activation.
  • the temporary card provided to the customer at 160 is activated with a limited duration (e.g., an expiration date of several days or weeks may be provided).
  • temporary cards may be identified as such by their account identifiers, allowing transactions involving the temporary cards to be processed with additional authorization controls (such as reduced credit limits or special floor limits).
  • a homebrand merchant may elect to not issue temporary cards and processing at 160 is not performed.
  • the card and associated account information is sent to the customer at 164 to await activation.
  • Card Activation Pursuant to some embodiments, dual cards issued as a result of upgrades or new applications (such as described above in conjunction with FIGs. 2-4) are not usable until they are activated by the customer associated with the card.
  • a customer service function such as the customer service function 54 associated with issuer 24.
  • Process 200 begins at 202 where a dual card activation request is received from a customer.
  • this activation request may be received by a customer service representative or FLA associated with a customer service function 54 of issuer 24.
  • the customer may follow activation instructions provided with the dual card mailed to the customer (which may, for example, instruct the customer to telephone a customer service telephone number to interact with an IVR or to speak with a FLA).
  • the customer may provide information identifying the particular dual card to be activated (such as the account identifier embossed on the card, etc.).
  • Processing at 204 includes determining whether the request is for an activation of a dual card which is an upgrade from a PLCC (e.g., as described in conjunction with FIG. 2 above), whether the request is for an activation of a new dual card (e.g., issued as described in conjunction with FIG. 4, above) or whether the request is for modification of an existing dual card account. If the former, processing continues at 208 where non-monetary data (e.g., such as account information and the customer information provided to the embosser) is retrieved from the dual card platform. This non-monetary information may be displayed to the FLA so that the FLA may orally confirm the accuracy of the information with the customer.
  • non-monetary data e.g., such as account information and the customer information provided to the embosser
  • the FLA may ask the customer security questions and/or seek additional confirmations of the customer's identity and the accuracy of the information. Any missing non-monetary data may be identified and entered by the FLA. The missing data may be used to update the issuer's records.
  • processing at 218 includes comparing these eligibility requirements to information about the customer (such as the non-monetary and monetary data retrieved at 208 and 210) to identify which (if any) offers the customer is eligible for.
  • a number of different types of offers may be available, including loyalty offers, promotional discounts, etc.
  • credit and risk processes may be executed to determine whether the customer's risk or credit profile has changed.
  • a determination may be made at 244 whether the customer remains eligible for the dual card account. If the customer is not eligible (e.g., a credit event has occurred since the time of the issuance of the card that, has rendered the customer ineligible for the upgrade), processing continues at 246 where information is displayed to the FLA regarding the activation decline reason.
  • the FLA may determine if any resolution is possible at 252 (for example, if the customer has a past due amount associated with the private label account, arrangements may be made to pay the past due amount and allow the customer to remain qualified for the dual card upgrade). If resolution is possible, processing continues to 252. If resolution is not possible, processing terminates. In some embodiments, the customer's private label account information is flagged to indicate that the customer was declined for the upgrade and the zero balance account on the dual card platform is blocked or deleted to prevent use and to free up the account identifier for future use.
  • processing continues at 254 where the FLA confirms with the customer that the customer still wishes to activate the dual card account upgrade. If, for some reason, the customer declines or objects to one or more terms of the dual card account, processing may continue to 256 where one or more rebuttal or alternative terms may be presented to the customer. For example, in some embodiments, a sequence of rebuttal presentations may be made, depending on information associated with the customer. A customer having a very high credit rating may, for example, be offered a lower interest rate or a higher credit limit. Each of these rebuttal terms may be offered to the customer in a predefined sequence until the customer either confirms the dual card upgrade or finally declines the upgrade. If the customer declines the upgrade, processing continues at 302 (discussed below in conjunction with FIG. 5D). If the customer confirms the upgrade with the varied or alternate term(s), processing continues at 272 (shown at the top of FIG. 5C).
  • the posting to the PLCC account should net the PLCC account balance to zero as of the time that processing at 274 is performed. Processing at 274 may also include blocking the PLCC account to prevent further use of the PLCC account. In some embodiments, some trailing activity (both monetary and non-monetary) may occur after the date of the posting at 274. Processing at 276 includes activating a trailing activity process on the PLCC platform to ensure that any activity associated with the upgraded PLCC account is reflected on the dual card account. This trailing activity process may be perfo ⁇ ned on a regular basis (e.g., such as on a nightly batch process) to quickly identify any trailing activity. The cross-reference table generated during the new account upgrade process of FIG. 2 may be used to manage this trailing activity process and to help ensure that transactions involving an upgraded PLCC account are properly reflected on the dual card account. This trailing activity process may be performed on a regular (or constant) basis until all trailing activities have been identified.
  • Processing continues at 282 where a determination is made whether the customer can receive promotional offers or not. For example, in some embodiments, customers may indicate to issuer 24 that they do not wish to receive any promotional offers or solicitations. Such an indication can be reflected in the dual card account database using a flag indicating that the customer is not to be promoted or "do not promote”. If the flag indicates "do not promote" processing is complete and the dual card is ready for use by the customer.
  • processing may continue at 284 where one or more promotional offers are presented to the customer.
  • Processing at 284 may include determining whether any offers are available for presentation to the customer.
  • types of offers may be made, including, for example: balance transfers; preferential interest rates; credit limit changes; insurance; in-store promotions; loyalty programs and other benefits; etc.
  • processing may continue at 290 where the customer's account on the dual card platform is updated to reflect the terms of the offer (e.g., if the customer accepts an incentive promotion which will provide him with a six month interest-free period for all purchases made at the homebrand merchant on September 15, the terms of the offer will be reflected in the account so that the incentive can be appropriately credited to the customer's account balance). Additional offers may be selected and presented until there are no more offers available for the customer or until the customer indicates a desire to terminate the offer process. At this point, the dual card is activated and available for use by the customer.
  • Similar processing can be performed to activate dual cards issued to new customers or dual cards issued to existing dual card customers, with the exception that no processing is needed to transfer a monetary balance or non-monetary information from the PLCC processing platform to the dual card platform.
  • processing continues at 304 a determination is made whether the customer used or was provided with a temporary shopping card. If so, processing continues at 306 where the issuer generates a statement and blocks the account on the dual card platform from any further use. Any amounts charged to the temporary shopping card will be invoiced to the customer and the balance on the temporary shopping card will be settled. Processing continues at 308 where a letter or other correspondence is generated and transmitted to the customer confirming that the dual card has not been activated.
  • Processing continues at 310 where a determination is made whether or not the account was an upgrade to a dual card account from an existing PLCC account. If the account was not an upgrade (e.g., if the dual card account was set up in response to an in-store application for a new account) processing continues at 312 where the zero balance account established on the dual card platform is cancelled and blocked so that it will not be inadvertently used.
  • processing at 310 indicates that the account was an upgrade from an existing PLCC account
  • processing continues at 314 where the PLCC account on the PLCC platform is flagged to indicate that the customer does not desire a dual card at this time or that the customer has opted-out from receiving a dual card upgrade.
  • the zero balance account established on the dual card platform may also be cancelled and blocked so that it will not be inadvertently used.
  • Processing at 314 may also include removing the dual card account identifier from the cross-reference table associating the account identifier with the PLCC account.
  • an issuer may operate a single settlement platform for both dual card and private label products.
  • multiple issuers may cooperatively interact to provide processing as described herein.

Landscapes

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

Abstract

L'invention concerne un système et une méthode de traitement de carte de paiement.
EP03749468A 2003-09-05 2003-09-05 Systeme et methodes de traitement de carte de paiement Ceased EP1687764A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2003/027929 WO2005033997A1 (fr) 2003-09-05 2003-09-05 Systeme et methodes de traitement de carte de paiement

Publications (2)

Publication Number Publication Date
EP1687764A1 EP1687764A1 (fr) 2006-08-09
EP1687764A4 true EP1687764A4 (fr) 2007-04-18

Family

ID=34421178

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03749468A Ceased EP1687764A4 (fr) 2003-09-05 2003-09-05 Systeme et methodes de traitement de carte de paiement

Country Status (3)

Country Link
EP (1) EP1687764A4 (fr)
CA (1) CA2537917A1 (fr)
WO (1) WO2005033997A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015134384A2 (fr) 2014-03-07 2015-09-11 Starbucks Corporation Dba Starbucks Coffee Company Carte à double fonction avec fonctionnalité de carte clé et fonctionnalité de carte à valeur stockée
US20170032371A1 (en) * 2015-07-29 2017-02-02 Mastercard International Incorporated Method and system for next generation fleet network
US10339529B2 (en) 2015-11-18 2019-07-02 Mastercard Internatioinal Incorporated Rules engine for applying rules from a reviewing network to signals from an originating network
US10430795B2 (en) * 2015-11-18 2019-10-01 Mastercard International Incorporated Rules engine for applying rules from a reviewing network to signals from an originating network

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1989011130A1 (fr) * 1988-05-04 1989-11-16 Humble David Raymond Systeme de compte de transactions generique
EP0658862A2 (fr) * 1993-12-14 1995-06-21 AT&T Corp. Méthode et système intermédiaire pour transactions utilisant des cartes à puces portables
US5530232A (en) * 1993-12-22 1996-06-25 Datamark Services, Inc. Multi-application data card
WO1998025237A1 (fr) * 1996-12-06 1998-06-11 American Express Travel Related Services Company, Inc. Procedes et appareil destines a regenerer un compte a transaction preprovisionne
WO2000033497A2 (fr) * 1998-12-02 2000-06-08 Transactionsecure, L.L.C. Systeme de paiement electronique utilisant un numero de compte a usage limite
WO2001003033A1 (fr) * 1999-07-02 2001-01-11 Namesafe.Com Inc. Procede de fourniture de carte de paiement electronique anonyme prepayee compatible avec les reseaux existants de cartes de credit
US6189787B1 (en) * 1997-07-10 2001-02-20 Robert E. Dorf Multifunctional card system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6615190B1 (en) * 2000-02-09 2003-09-02 Bank One, Delaware, National Association Sponsor funded stored value card
US6915277B1 (en) * 2000-05-10 2005-07-05 General Electric Capital Corporation Method for dual credit card system
US20030191709A1 (en) * 2002-04-03 2003-10-09 Stephen Elston Distributed payment and loyalty processing for retail and vending

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1989011130A1 (fr) * 1988-05-04 1989-11-16 Humble David Raymond Systeme de compte de transactions generique
EP0658862A2 (fr) * 1993-12-14 1995-06-21 AT&T Corp. Méthode et système intermédiaire pour transactions utilisant des cartes à puces portables
US5530232A (en) * 1993-12-22 1996-06-25 Datamark Services, Inc. Multi-application data card
WO1998025237A1 (fr) * 1996-12-06 1998-06-11 American Express Travel Related Services Company, Inc. Procedes et appareil destines a regenerer un compte a transaction preprovisionne
US6189787B1 (en) * 1997-07-10 2001-02-20 Robert E. Dorf Multifunctional card system
WO2000033497A2 (fr) * 1998-12-02 2000-06-08 Transactionsecure, L.L.C. Systeme de paiement electronique utilisant un numero de compte a usage limite
WO2001003033A1 (fr) * 1999-07-02 2001-01-11 Namesafe.Com Inc. Procede de fourniture de carte de paiement electronique anonyme prepayee compatible avec les reseaux existants de cartes de credit

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2005033997A1 *

Also Published As

Publication number Publication date
CA2537917A1 (fr) 2005-04-14
EP1687764A1 (fr) 2006-08-09
WO2005033997A1 (fr) 2005-04-14

Similar Documents

Publication Publication Date Title
US7774274B2 (en) Payment card processing system and methods
US7174314B2 (en) Debit purchasing of stored value card for use by and/or delivery to others
US7917432B2 (en) Dual card
US7581674B2 (en) Financial transaction system and method
US6088682A (en) Funds distribution system connected with point of sale transactions
US7809642B1 (en) Debit purchasing of stored value card for use by and/or delivery to others
GB2376787A (en) Converting stored value card into credit card
WO2005033997A1 (fr) Systeme et methodes de traitement de carte de paiement
AU2003262344B8 (en) Payment card processing system and methods
AU2003271997B2 (en) Dual card

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060404

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

R17P Request for examination filed (corrected)

Effective date: 20060405

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20070320

RIC1 Information provided on ipc code assigned before grant

Ipc: G07F 7/10 20060101AFI20070314BHEP

17Q First examination report despatched

Effective date: 20060404

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20151226