Methods and Systems for Managing Card Programs and Processing Card Transactions
First Claim
1. A method for design, deployment, and management of Card Programs and processing Card transactions where a. a plurality of Clients, Cards, Limits, Card Types, Issuers, Acquirers, Locations, Program Groups, Terminals, Distributors, and Agents may be configured on a Host System;
- b. Clients, their designees, and Cardholders having available Web Interface user forms for input, queries, and reports;
c. Inbound Transactions may be received at the Host System from a plurality of Card transaction acquiring sources, Open Networks, Third Party Networks and Terminals;
d. Issuers and Acquirers associated with a Card transaction may or may not be of the same Client configured in the Host System database;
e. Card transaction strings arriving at the Host System for processing containing data relevant to a singular transaction, (for example date, time, transaction type, amount, Card number, and Terminal ID) are captured and parsed by the Host System for proper ultimate Card Transaction Set processing based on the relevant Client choices configured in Program Groups associated with Locations;
f. Client Card Programs are configured within the Host System database typically by Card Type, Card Limits, Locations, Program Groups, and Locations.
0 Assignments
0 Petitions
Accused Products
Abstract
Methods and systems are provided for processing Card transactions. The Cards and Card Programs are configured on a Host System by a Client and transactions are received at a Host System. Issuers of Cards and their Program Groups are configured on the Host System. Acquirers of Card transactions and their Program Groups are configured on the Host System. An Issuer and Acquirer associated with singular Card transactions may or may not belong to the same Client. The Card transactions carry associated data relevant to the Card Type and transaction type captured and identified by the Host System for proper Transaction Set build and ultimate Card transaction processing based on the relevant Issuer and Acquirer set choices. A Web Interface is provided for Clients, their designees, and Cardholders.
138 Citations
61 Claims
-
1. A method for design, deployment, and management of Card Programs and processing Card transactions where
a. a plurality of Clients, Cards, Limits, Card Types, Issuers, Acquirers, Locations, Program Groups, Terminals, Distributors, and Agents may be configured on a Host System; -
b. Clients, their designees, and Cardholders having available Web Interface user forms for input, queries, and reports;
c. Inbound Transactions may be received at the Host System from a plurality of Card transaction acquiring sources, Open Networks, Third Party Networks and Terminals;
d. Issuers and Acquirers associated with a Card transaction may or may not be of the same Client configured in the Host System database;
e. Card transaction strings arriving at the Host System for processing containing data relevant to a singular transaction, (for example date, time, transaction type, amount, Card number, and Terminal ID) are captured and parsed by the Host System for proper ultimate Card Transaction Set processing based on the relevant Client choices configured in Program Groups associated with Locations;
f. Client Card Programs are configured within the Host System database typically by Card Type, Card Limits, Locations, Program Groups, and Locations. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58)
-
-
59. A computer-readable storage medium having a computer-readable program embodied therein for directing operation of the Host System including a communications system, a processor, and a storage device, wherein the computer-readable program includes instructions for operating the Host System to process Card transactions in accordance with the following
a. receiving, with the communications system, a transaction string in either bitmap or XML characters; - receiving, with the communications system, fields within the transaction string that may contain codes to be interpreted by the computer-readable program that define the transaction type, the Card Type, the Card, the Acquirer, the Card Issuer, transaction values, transaction time, transaction ID or trace number, size of transaction string, Cardholder Personal Identification Numbers (PINs), Card expiration date, merchant location information, and Cardholder Verification Values (CVV);
b. receiving, with the communications system, a transaction string that cannot be processed due to data contained therein that the host computer readable program determines is invalid based on the transaction type and data contained within the storage device. - View Dependent Claims (60, 61)
- receiving, with the communications system, fields within the transaction string that may contain codes to be interpreted by the computer-readable program that define the transaction type, the Card Type, the Card, the Acquirer, the Card Issuer, transaction values, transaction time, transaction ID or trace number, size of transaction string, Cardholder Personal Identification Numbers (PINs), Card expiration date, merchant location information, and Cardholder Verification Values (CVV);
Specification