EP1342146A2 - Bar coded bill payment system and method - Google Patents
Bar coded bill payment system and methodInfo
- Publication number
- EP1342146A2 EP1342146A2 EP01988313A EP01988313A EP1342146A2 EP 1342146 A2 EP1342146 A2 EP 1342146A2 EP 01988313 A EP01988313 A EP 01988313A EP 01988313 A EP01988313 A EP 01988313A EP 1342146 A2 EP1342146 A2 EP 1342146A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- payment
- data
- bar code
- payor
- biller
- 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.)
- Withdrawn
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/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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/04—Payment circuits
- G06Q20/042—Payment circuits characterized in that the payment protocol involves at least one cheque
-
- 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/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- 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/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
-
- 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/385—Payment protocols; Details thereof using an alias or single-use codes
-
- 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/04—Billing or invoicing
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
Definitions
- the present invention relates to a system and method for performing financial transactions, and more particularly, to a payment system and method using bar code identification.
- Traditional Bill Payment Paradigm The current paradigm of the bill payment cycle for goods and services rendered has improved only in incremental steps since the beginning of time. In ancient times, most goods and services were exchanged between individuals, using the common currency of the realm or by a mutually agreed upon barter arrangement. Extension of credit for goods and services was generally limited to the affluent and wealthy. When payment was due, handwritten invoices were hand delivered. Sometime later, cash payment would be remitted in person. Most trade occurred at the local level between individuals, exchanging cash or barter goods.
- the national mail network is a very cost-effective delivery system for local and remote customers of automated or machine printed monthly invoice statements, which average 15.9 billion annually.
- Customers write checks, as payment for these invoices, and return them via the mail network.
- these mail payments When received at the merchant directed return location (a bill payment- processing center), these mail payments are opened, the checks deposited, and the customer accounts credited with the face amount of these check payments. If everyone were to pay their bills on or before the due date with valid checks, this state of the bill payment industry might be sufficient to satisfy most of today's societal needs. However, this is not the case. Some people never pay their bills on time, for a variety of reasons. Payments made with a check are not always covered with sufficient funds at their bank.
- the end-result consequence to the biller is a finite cost that is directly attributable to the disruption of the flow of goods and services through his business.
- billers have only two options available to them.
- One option is to spread this overhead cost over of all the goods and services that they provide, with the possible consequence of pricing their products or services out of the competitive price range for similar or substitute set of products and services.
- the second option is to impose payment penalties on those customers who pay late - for whatever reason. This second option is generally more preferable since it targets the problem population segment directly.
- billers are often unable to recover the full cost of late payment consequences from those customers and still stay within the public legal and regulatory mandates.
- the proprietor-operated check cashing storefronts may service some of the needs of these individuals. Weekly paychecks are cashed for a transaction charge (mostly based on the face value of the check), and money orders are then bought, to be enclosed with mailed bill payments. When bill payments are long past their due date, these individuals may have to resort to more expensive electronic wire services to avoid service disconnects. For the great majority of printed bill payment invoices that are distributed every month, each biller automates and optimizes its bill collection and remittance process to suit the requirements of its installed paper handling equipment and flavor of customer account numbering assignments and schemes.
- Bill remittance stub sizes and formats vary from postcards printed with dot matrix printers to full-page 8 V" by H" sheets with laser printed invoice information on pre-printed forms. Each has a tear-off bill remittance stub portion that is then mailed back with a check payment. Account numbers on these bill remittance stubs appear in different (and sometime multiple) spatial positions, formats and fonts. While still not universal, most billers have formatted their account numbers (and other customer related information) on bill remittance stubs in Optical Character Recognition (OCR) readable scan lines.
- OCR Optical Character Recognition
- FIG. 1 shows an exemplary local gas company remittance stub 100 utilizing this manner of design.
- the biller in this example has assigned a numeric account number to each of his customers.
- the customer account number is printed three times, the human readable one 102 under the "Your Account Number" heading, and the other two 103, 104 printed twice in machine-readable form.
- Account number check digits 101 are used to validate the account number.
- FIG. 2 shows an exemplary remittance stub 200 from a local power company that assigns a combination of letters and digits to its customer base. There are two forms of the customer account number 201 that appear on the bill remittance stub.
- the first 201 is designed to be human readable because it appears within a printed text box labeled "Account Number".
- the last digit in the Account Number box is the customer account number check digit.
- the second form of the customer account number 202 appears in machine-readable form and is embedded in the OCR scan line (underlined for illustration).
- the leading "4" digit is the customer account number check digit and the remainder of the underlined portion of the OCR line are the digits that can be mapped into the human readable "Account Number” form.
- the format of this machine-readable OCR scan line 202 is probably a confluence of many internal design decisions, based on several factors.
- Figure 3 shows an exemplary remittance stub 300 from a gas company, in which the biller automates part of the bill payment remittance process by including, on the bill remittance stub, company proprietary bar coded information 301 that does not appear to be related in any way to the printed customer account number. While the format of this bill remittance stub 300 may marginally advance that biller' s state- of-the-art bill collection and system processing with the use of newer and improved automation equipment, it does not significantly decrease, in favor of the customer, the overall bill payment cycle. The great majority of the bill payment cycle time consists of non-deterministic time delays in the national mail network during the biller-to- customer and the payment-to-biller delivery paths.
- a universal national bill payment network could be implemented that addresses the above list of industry problems, resulting in a positive economic impact to the business community at large.
- the cooperation of several large organizations would be required; however increases in raw profit and new business growth opportunities should induce such cooperation.
- a system 400 consistent with the existing bill payment paradigm uses the national mail network and biller payment processing centers to convert physical paper into electronic data and bank credits.
- the current bill payment network is a paper based network that primarily relies on the central banking system for processing customer remitted bank draft payments and the national mail network for customer invoice delivery and the return of mailed bill payments.
- the biller accounts receivable 401 accumulates a dollar total and generates a detailed machine printed invoice (which may take 4-5 days after account cut-off time to process) that is sent to the customer 403 via U.S. Mail 402.
- the customer (i.e. payee) 403 typically receives the invoice 2-3 days later (which time is variable, without any direct traceability from the perspective of either the biller or the customer).
- the customer makes out a check payment or procures a money order 404 to remit with a mail payment, which occurs sometime later, depending on the availability of cash resources and other circumstances.
- the customer mails the payment via U.S.
- Processing time may be 2-3 business days or more (which time is variable, without any direct traceability from the perspective of either the biller or the customer).
- the following operations are typically performed: opening all received mail; microfilming and/or otherwise recording all received payments; electronically reading and processing OCR bill remittance stub information; preparing all received check or money order payments for bank submission; and electronically remitting bill payment data, based on check payment verification.
- Processing time within the processing center 406 may be 2-3 days.
- Payment data is next remitted electronically from the processing center 406 to the biUer's bank 408, and processing and distribution of electronic payment data is typically done using the Federal Reserve Automated Clearing House (ACH) Network 407, which typically takes 6-9 hours.
- ACH Federal Reserve Automated Clearing House
- the electronic payment data is received from the ACH Network, stripped and reformatted according to biller specified formats, which may take 4-6 hours.
- the biller's accounts receivable 401 and/or customer service computer files are updated. Depending on the "legacy factor" of the biller's computer processing systems, this process can range anywhere from 2-3 hours to 4-5 days.
- the cycle time between the customer account cut-off time and the time that the customer payment is applied to his account may range from 13- 18 days. Since there is usually some customer delay, the observed bill payment cycle time will be longer.
- the present invention involves the transmission of payment information via one or more networks (e.g. the Internet and the Federal Reserve ACH Network) to billers of consumer goods and services. This payment information is captured using existing scanners in cash register systems at supermarkets, chain stores, or other retail ⁇ outlets. Retailers gain access to a valuable affinity draw because everyone has bills to pay regularly. Billers save millions of dollars in collection and processing expenses.
- a bill payment system and method consistent with the present invention relies on an additional ISO standard printed bar code on the biller invoice, which is then delivered to the customer via the national mail network. Thereafter, payment information and payment credits are returned to the biller electronically.
- UPC Universal Product Codes
- a proprietary router/application interface may be non-invasively attached, indirectly, to the retailer's checkout scanner. Through this portal, other services can be offered to consumers. For example, in addition to payments, money transfers (a financial services which may be lucrative to provide) may be provided through a system consistent with the invention. Bank account transactions such as deposits may be made or Internet wallets replenished. Though not required, the U.S. Postal Service (USPS) could be offered a new income stream for simply authorizing this system. The power of an "electronic" postmark may impact the way billers view this system. It is contemplated that the retail industry should provide advertising as they promote the affinity pull they already wish to impart upon the consumer marketspace.
- USPS U.S. Postal Service
- a bill payment system consistent with the invention comprises a payee and a scanning apparatus.
- the payee transmits or transfers to at least one payor a unique bar code comprising data identifying at least the payee and the payor.
- the scanning apparatus is configured to scan a printed representation of the bar code .
- the scanning apparatus is capable, based on information stored in the bar code and a payment made by the payor, of transmitting funds or initiating a funds transfer to the payee in a predetermined amount and transmitting data or initiating a data transfer to the payee regarding the payment.
- a bill payment method consistent with the invention comprises: transmitting or transferring to at least one payor a unique bar code comprising data identifying at least the payee and the payor; and permitting a third party to scan a printed representation of the bar code and, based on the identifying information of the bar code and a payment made by the payor, to transmit funds or initiate a funds transfer to the payee in a predetermined amount and transmit data or initiate a data transfer to the payee regarding the payment.
- a method of transferring money consistent with the invention comprises: scanning a printed bar code comprising data identifying at least an account number corresponding to an account to which a deposit can be made and a destination payment network corresponding to the account; and transmitting funds or initiating a funds transfer, based on information stored in the bar code and a payment made by a payor, in a predetermined amount to the account.
- a deposit slip consistent with the invention comprises a printed account number and a unique bar code comprising data identifying at least the account number and a destination payment network corresponding to the account number.
- a printed bar code consistent with the invention comprises data identifying at least an account number and a destination payment network corresponding to the account number.
- a method for performing an Internet financial transaction consistent with the invention comprises transmitting or transferring to a payor a unique bar code comprising data identifying at least a payee and a destination payment network corresponding to the payee.
- a method of providing for payment from a payor to a payee comprises: making available to one or more payees a standard format for representing on a printed document data including at least a payee and a destination payment network corresponding to said payee; providing at one or more locations of one or more third parties one or more scanning apparatus adapted to read data in said standard format; receiving by electronic transmission data comprising said destination payment network identification, payee identification and payment amount; and providing information to said destination payment network to effect transmission of funds to an account of said payee in an amount identified by said payment amount and concurrently effecting or initiating transmission of payment information to said payee.
- Figure 1 is an exemplary prior art remittance stub from a utility company
- Figure 2 is another exemplary prior art remittance stub from a utility company
- Figure 3 is another exemplary prior art remittance stub from a utility company
- Figure 4 is a process flow diagram of an exemplary prior art bill payment system
- Figure 5 is a process flow diagram of an exemplary bill payment system consistent with the present invention
- Figure 6 is an illustration of an exemplary data structure of elements underlying the bar code "signature" in one embodiment of the present invention
- Figure 7 is an illustration of another exemplary data structure of elements underlying the bar code "signature” in one embodiment of the present invention
- Figure 8 is an illustration of an exemplary bar code bill payment "signature" in one embodiment of the present invention
- Figure 9 is a table illustrating the results of an exemplary split modulus matching calculation in one embodiment of the present invention
- Figures 10 and 11 are illustrations of an exemplary Level 3 envelope in one embodiment of the present invention
- Figures 10 and 11
- a bar coded bill payment based system 500 consistent with the present invention utilizes a bar code on the biller invoice, which is then delivered to the customer via mail, and payment information and payment credits are returned to the biller electronically.
- nationally recognized and federally sanctioned payment electronic networks may be utilized for remitting customer payment data and funds.
- the biller's accounts receivable 501 accumulates a dollar total and generates a detailed machine printed invoice including a special bar code, which is mailed to the customer 503 via U.S. Mail 502.
- Time for processing and mailing may be 4-5 days after account cut-off time, and the mail transit time to the customer may add an additional 2-3 business days or more before the customer receives the invoice (which time is variable, without any direct traceability from the perspective of either the biller or the customer).
- the customer 503 then receives the invoice in the mail. Sometime later when cash resources are available, or depending on other factors, the customer 503 decides to pay bill. The time for this to occur is variable, depending upon the customer's circumstances. To pay the bill, the customer 503 takes the bar-coded invoice to a participating store (e.g. a supermarket) that processes bill payments.
- a participating store e.g. a supermarket
- the customer presents his bar-coded bill remittance stub to the checkout cashier for scanning at the checkout scanner 504, which may be done while paying for other UPC-coded items.
- the scanner 504 picks up the bill payment bar code that identifies the biller to be paid and the account number to be credited.
- the customer informs the checkout cashier the amount to be paid on that account, payment is tendered to the cashier, and the cashier inputs the amount to be paid into a terminal which is in communication with a backend host processing system 505.
- Upon receiving payment from the customer that bill payment is then complete. The check out of any remaining products and items (or bills) continues until the complete total for all goods and services is calculated.
- the customer may receive a printed receipt of the payment tendered with date and time that the payment was made.
- the backend host processing system 505 forwards all the payment data to the data collection network interface 506 ("DCNI").
- DCNI data collection network interface 506
- the processing time for all of the payment steps may be as little as a few seconds.
- payments made in this manner are time-stamped, so that once payment is made, the customer may rest assured that payment has been timely acknowledged.
- the data collection network interface 506 collects and stores all the customer payment data in non-volatile memory. Periodically throughout the day (based on time and transaction volume thresholds), or at other predetermined intervals, the interface 506 transmits the payment data to the central site transaction collection system 507. Additional transmissions may be scheduled before the daily transaction collection system 507 aggregation times.
- the time for the back-end and collection system processing has no impact on customer payment time, since all payments may be time- stamped. Separately calculated calendar day payment counts and totals may also be sent to the transaction collection system 507 as an independent transaction audit balancing mechanism.
- the transaction collection system 507 may continuously receive payment data information from a distributed network comprising a plurality of data collection network interface units 506 deployed at field retail establishments. Before the last processing window closes at the Federal Reserve Automated Clearing House (ACH) Network 508, all customer payments are sorted and aggregated for direct remission to their respective billers, which may take approximately an hour. Processing and distribution of electronic payment data is done using the Federal Reserve Automated Clearing House (ACH) Network 508, which may take 6-9 hours.
- ACH Federal Reserve Automated Clearing House
- the electronic payment data is received from the ACH Network, stripped and reformatted according to biller specified formats, which may take 4-6 hours. Finally, the biller's accounts receivable 501 and/or customer service computer files are updated. Depending on the "legacy factor" of the biller's computer processing systems, this process can range anywhere from 2-3 hours to 4-5 days. Assuming zero latency on the part of the customer paying his bill, the cycle time between the customer account cut-off time and the time that the customer payment is applied to his account, using the above time estimates, may range from 9- 12 days (in contrast to the 13-18 days of the prior art system). Since there is usually some customer delay, the observed bill payment cycle time will be longer.
- the biller recognized the customer payment date and time as the creditor date of receipt as specified in the Federal Reserve Regulation Z, Section 226.10, then the total bill payment cycle time would be reduced to 6-8 days. Explicit agreement from the biller would be secured through the biller registration process.
- the biller may validate the customer payment date with the transaction embedded "electronic postmark", which can not be performed within the current frameworks of either the paper based bill payment or the electronic payment paradigms, today.
- billers can incorporate this bar coding standard into their bill remittance processing centers, as older OCR recognition equipment is replaced with simpler and more reliable laser bar code scanning equipment.
- a biller contemplating a conversion of one or more legacy customer account numbering systems to a simpler, newer scheme, can use this system of bar coding in its conversion process.
- electronic invoice delivery whereby the customer receives and prints the bar-coded invoice at his own computer system, may be used to reduce the time and labor required for the biller to prepare and mail invoices to the customer.
- billers would register with a centralized organization in order to receive an assigned biller bar code, just as all companies must register with the Uniform Code Council (UCC) to get their Universal Product Code (UPC) assignment for their products.
- UPC Uniform Code Council
- UPC Universal Product Code
- Bar code is more efficient than OCR by several magnitudes because bar codes can be detected reliably and processed by relatively simple hardware and firmware, whereas OCR requires long physical scan times and significant host CPU processing requirements for character recognition (and then only for a selected set of fonts).
- Bar code consists of binary elements that are parity checked for every bar code symbol and globally checked digited at the message level.
- OCR consists of many analog segments that have to be neurally correlated and matched to the human readable character set with no internal self-checking controls. In short, bar code is the future digital solution whereas OCR is a dated analog solution that still plagues most bill payment processes today.
- the Universal Product Code (UPC) printed on most retail products today, is a 12-digit number that is a concatenation of four numeric fields - a classification number (1), a producer identification number (5), a product identification number (5), and a check digit (1).
- UPC Uniform Code Council
- the need for a standards authority first arose in 1972 when the supermarket industry decided to mark each of the grocery point-of-sale packages with a unique identifier to speed checkout transactions, therein creating an organization that today is called the Uniform Code Council (UCC).
- the underlying bar code symbology is merely a convenient representation of this UPC code format that can be reliably detected by simple point-of-sale scanning equipment (thus, it does not matter which particular bar code is used).
- Validating a bar code bill payment "signature" in the course of the bill payment process is a component of an embodiment of the present invention.
- a bar code scanning system may reliably recognize and validate a valid bill payment bar code.
- the concept of paper envelopes may be used as an analogy for relating the validation method of the invention. In the embodiment described herein, three “envelopes” are used (although those skilled in the art will recognize that any number of "envelopes” or levels of validation may be used), the first being inside the second, and the second inside the third.
- the third "envelope” has printed, on the outside, the bill payment bar code "signature". If the bar code is detected and read correctly by the hardware scanner, the resulting alphanumeric information is valid in that it compared correctly with the embedded encoded bar code check symbol. If this first operation is successful, the "envelope" is opened. The directions printed on the inner “envelope” specify to calculate a check digit on the resulting alphanumeric information derived from the bar code, comparing the calculated result against the last digit in the string. If this second operation is successful, the next “envelope” is opened. The printed directions on the innermost “envelope” specify to use the format designator digit(s) to decode and to verify the data integrity of the embedded component data elements.
- each signature data field consists of three elements: a format designator ("fd") consisting of one or more digits, a data field (“data”) consisting of one or more fixed or variable length sub-data fields, and a check digit (“cd”) algorithm associated with the format designator and the level at which it appears.
- Figure 6 illustrates a bar code "signature” 600 in one embodiment of the invention, utilizing four levels of successive embedded "signature” data fields.
- the Level 1 data validation 601 is simply the hardware decode of the bar code symbology, using the embedded check symbol character as data validation — i.e., all the bar code symbols were detected and processed correctly. Applicability of the data to the intended target application is demonstrated when all the remaining levels of validation are successful.
- Level 2 data validation 602 consists of one signature data field (although it could have had more).
- the data validation of the Level 2 signature data field consists of two checks - that the format designator value (for that level) is correct and that the check digit calculation for the data string consisting of the format designator digit(s) and the data field digits matches the check digit character.
- the Level 2 format designator defines at least three characteristics: the check digit algorithm implementations (in this example, 1), the number of data elements (in this example, 1), and the number of trailing discard characters for bar code odd / even count padding (in this example, 2). The number of unique combinations of the above three characteristics will determine the number of format designator values required at this level.
- the Level 3 signature data field 603 checks operate on the residual Level 2 data.
- the Level 3 data validation checks are similar to the Level 2 checks and the format designator defines at least these three characteristics: the check digit algorithm implementations (in this example, 1), the number of data elements (in this example, one fixed, one variable or fixed), and the field lengths for one or more data elements. As shown in Figure 6, there are two data element fields. The number of data splits defined for this data field would determine the number of format designator values that are required for this level.
- the fourth 604 to nth 605 levels comprise a continuing iterative process of Level 3.
- the target application receives all the data fields from the final level of data validation.
- a carefully chosen set of conventions for the format designators at each level will facilitate correct data field parsing with the additional security that multiple levels of check digit validation will ensure data integrity and "positive ownership" to the target application.
- the format designator digit(s) do not necessarily have to be leading as illustrated above.
- An alternative format for the leading format designators could be as is illustrated in the bar code signature 700 of Figure 7, in which the data strings precede the format designator digits.
- a bar code typically consists of 6 sections: (1) a quiet zone ( ⁇ 0.25" of white space) before the bar code; (2) a unique bar code symbol that represents the "START” character; (3) bar code symbols representing data characters (1300017350764058410363); (4) bar code check symbol that represents a calculated check digit of the preceding data character block; (5) a unique bar code symbol the represents the "STOP" character; and (6) a quiet zone ( ⁇ 0.25" of white space) after the bar code.
- a good hardware decode of a bar coded scan line is defined as the detection of valid bar code symbols within the string that, when processed through the defined check digit algorithm, matches the embedded string check symbol character. This is the first level of data validation check that must pass.
- the Level 2 format designator value (1) is chosen to indicate the check digit algorithm (Split Modulus 10 with mathematical weights of 1313... ), the number of data field elements (1), and number of trailing padding characters (0) to utilize the high density Code 128 Type C symbol set.
- the Level 2 format designator value (2) is chosen to indicate the check digit algorithm (Split Modulus 10 with mathematical weights of 1313%), the number of data field elements (1), and number of trailing padding characters (1) to utilize the high density Code 128 Type C symbol set.
- the modulus (or the remainder) of the resulting sum of the digits (87 divided by 10) yields 7.
- This calculated result is the check digit of the above digit string, and successfully matches the last digit in this illustrative example.
- the Level 1 check is a hardware validation data check.
- the Level 2 check is a pre- qualifying software validation data check.
- the Level 3 check is an "ownership" data check (i.e. whether this is the "signature" for bill payment data under the present invention).
- Format designators are arbitrary indicators with which to properly decode the format of and to validate the ensuing data string - in this case, the format designator is placed as the first (one or more) leading digit(s). At different levels, the same format designator values can have different meanings. Turning.now to Figures 10 and 11, two format designator values have been chosen in this example (at Level 3) to encapsulate six format and validation data characteristics - all of which must be correct for the third and final data validation check to pass. The Biller ID in each of these examples is "173" in a 6-digit numbering system.
- the embedded spaces in the encoded data examples 1000 and 1100 of Figures 10 and 11 are not significant and are inserted to show more clearly the various fields within the example digit strings.
- the six format designator characteristics shown in Figures 10 and 11 define either format (1,2,4,5) or data validation (1,2,3,6) checks.
- a format characteristic defines the layout of the data whereas a validation characteristic facilitates data checking.
- To validate a unique bar code application program "signature" the more dependencies that exist within the data at each level for subsequent cross checking and validation, the better.
- Condition #1 is checked against valid range of format designator values for the current Level (in this case 3, 4).
- Biller Identification Number (in this example, 173) is determined if Condition #3 is TRUE and if it exists within the list of current and valid billers (an independent table acquired by another means).
- this bar code "signature” design is to unconditionally identify the detected scanned bar code as being proprietary to a system or method according to the present invention, in the absence of any other external information, and to validate (using mathematical formulae and/or independent table look-up methods, if possible) all the data element components therein.
- the methods and procedures by which the format designator concept could be extended are strictly an implementation issue of design schemes and an adopted set of orthogonal convention(s). While the foregoing illustrative working example uses only three levels of "envelopes" to validate the unique bar code bill payment "signature", more levels could have been used, as required.
- the format designators in the foregoing example utilized a fixed data format with a set of predefined check digit algorithms for each level.
- Possible design extensions in further embodiments might include: (1) a format designator design scheme that defines a dynamic variable number of sub-field elements and/or a set of dynamic component string lengths for each of the defined set of the sub-field elements (in contrast to the foregoing illustrated predefined fixed schemes); (2) a format designator design scheme having more than one digit in length, wherein each digit specifies an independent set of predefined orthogonal attributes that can be combined in a mix-and-match fashion (e.g. a two digit format designator would specify a primary set of attributes in the tens digit that is qualified by a secondary set of attributes in the units digit); and (3) format designator design schemes wherein subsequent trees of sub-field elements are controlled by one or more preceding levels of format designators.
- the bill payment application bar code printed on each bill remittance stub might minimally consist of four basic fields, printed as a single string of digits: a format designator (1 digit); a biller identification number with optional embedded check digit (7 digits); a customer account number with optional embedded check digit (22 digits); and a check digit of the previous three fields (1 digit).
- a format designator (1 digit)
- a check digit of the previous three fields (1 digit).
- the number of fields and/or digits per field as described herein is specified by way of example, and not limitation, and that the number and length of fields may vary according to each embodiment of the invention.
- the outermost bar code envelope for this information conforms to documented ISO bar coding convention standards, utilizing an embedded check digit algorithm to verify the integrity of the entire bar code scan line data. It is strongly recommended that the biller defined customer account number also contain an embedded check digit, as a prudent secondary validation measure. If an embedded check digit does not already exist within the biller customer account numbering scheme (or the biller does not wish to disclose that information as being company proprietary), an alternate account number format provides a temporary check digit that is checked then discarded before presentment to the biller. If the detected bar code scan line data correctly passes the triple tiered and multiple embedded check digit calculations, this mechanism will virtually guarantee "defect free" biller and customer account data.
- an expanded set of format designators could define new data format structures or redefine the characteristics of current data fields.
- the following is a possible list of characteristics that a format designator element might define within a digit string: number of sub-field elements; component string lengths of one or more of these sub-field elements; check digit algorithms to be applied to each of the sub-field elements; odd/even string packing factors when a single bar code character represents one or more digits (Code 128 is a good example of this compression feature); or subsequent trees of dependent sub-field elements.
- the bar code data detected by the retail checkout scanner, is passed directly to the data collection network interface unit for secondary validation and translation.
- the parsed "translated" form of this data is then passed back to the back-end host processor system for completing the bill payment transaction at the checkout counter.
- the bar code might either be printed vertically on the left (bottom to top) or right (top to bottom) hand side of the bill remittance stub with sufficient surrounding white space to satisfy the criteria of the ISO bar code format. If there are other proprietary bar codes present on the bill remittance stub, the checkout counter cashier could have the option of folding or bending the bill remittance stub such that only the required bar code is visible for a successful bar code scan of the bill payment information.
- the biller include a check digit within the account numbering scheme. While it is unlikely that a customer account number would be read in error if the hardware bar code check symbol scan validates, this additional check digit provides double assurance to the biller that the customer account number is correct. This is especially important from the biller's point of view when accepting bill payments from many sources of ACH submitted data, many of which may be human entered from the myriad of home banking software packages available - known empirically to have very high human input error rates. To this point, it has been tacitly assumed that the biller will want to print this new bar code on the face of his bill remittance stub.
- the most common point-of-sale bar code used throughout the retail industry is the UPC-A variant.
- most scanners employ an internal firmware auto- recognition mechanism that permits them to detect and to read several bar code symbologies.
- the bar code symbology under current consideration for the most general specification of an alphanumeric customer account number, is the Code 128 family. Where there are only numerics, the Code 128 Type C variant features a high- density bar code - one printed symbol per two digits of information.
- the back-end host processor recognizes a bar code data scan line as a valid bill payment transaction and requires the cashier to enter an amount to be paid. When this amount is entered, a fixed transaction fee is added to the bill payment amount.
- the bill payment is recorded in a form similar to the following, including biller name and account number, amount paid, transaction ID, date and time, and transaction fee charged:
- PMNT Biller Name
- ACCT Customer Account Number
- AMNT $ ddd.cc
- TRID rrrrrrrr yjjj ssss
- DATE mm/dd/yy hh:mm
- FEE $ dd.cc
- This time-stamped transaction data is then stored in the data communication network interface unit for later transmission to the transaction collection system.
- the checkout scanner detects multiple bar codes
- the retailer cashier can be trained to recognize the placement of a valid bill payment "signature" bar code to be scanned for the proper processing of a customer payment. Scanning any other bar code, present on the bill remittance stub, that does not pass all of the bill payment "signature” tests results in an immediate validation reject by the data communication network interface unit.
- Back-end Host Processor The retailer back room host processor may be required to support two well- defined interfaces, the front-end checkout counter scanner system and the back-end data collection network interface.
- the Code 128 bar code format When the Code 128 bar code format is encountered from bill remittance stubs, it should be recognized as a customer bill payment, rather than the UPC code for a customer selected product.
- This decision can be performed in a number of ways by the back-end host processor.
- the easiest logic path to implement within the back-end host processor is as follows: if this bar code scan is not recognized as one of several defined pre-programmed sequences, pass it to the data collection network interface before rejecting the scanned data completely.
- the back-end host processor passes the complete scan line data to the data collection network interface unit for secondary level validation and data translation. If secondary level validation is successful, the parsed translated data is passed back to the back-end host processor to complete the processing for this bill payment transaction.
- the returned translated data consists of the Biller Name, the Customer Account Number, and Transaction ID that is printed on the customer printed receipt.
- bill payment data As bill payment data is processed by the front-end checkout scanner system and completed, it may be relayed by the back-end host processor to the data collection network interface unit to be stored in non- volatile memory for later transmission to the central transaction collection system.
- the back-end host processor system There are a number of standard data collection network interface functions that may be accessed by the back-end host processor system, e.g. validating the biller name, adding a transaction, voiding a transaction, printing daily or weekly processed totals and reports, and setting or reading operational configuration parameters.
- the retailer on-site data collection network interface unit should provide a well documented, protocol neutral features and functions front-end interface to the retailer back-end host processor.
- the DCNI should also provide a non-volatile memory storage capability of accumulated customer bill payment data. This may be accomplished with a solid state hardware design that is electrically isolated at all the critical interfaces and has no moving elements that mechanically wear and eventually cause the unit to fail.
- the back-end of the data collection network interface should provide a transparent interface to the central site transaction collection system and include functionality such as: (1) performing secure validation procedures with the transaction collection system; (2) downloading DCNI unit operating system and program application code firmware; (3) downloading DCNI unit operational configuration parameters; (4) uploading DCNI unit memory image (emergency and debug use); (5) downloading Verification Biller ID and Name data; (6) uploading transaction data (compressed & encrypted); and (7) setting DCNI unit system date or time.
- the primary function of the data collection network interface unit is to provide 1 a set of support functions to the retailer host processor to aid in the collection,
- the host processor next validates the bar code 1202 and 10 passes the resulting data to the DCNI. Since the account number is valid, an
- the checkout scanner 0 first reads the bar code 1301 and passes it to the retailer host processor.
- the host 1 processor next validates the bar code 1302 and passes the resulting data to the DCNI. 2 Since some aspect of the data passed to the DCNI is invalid, an acknowledgment of 3 invalidity (NAK) is returned 1303 to the host processor with a reason code.
- NAK acknowledgment of 3 invalidity
- the 4 Reject Payment status, passed to the checkout scanner 1304 from the host processor, 5 may or may not contain the DCNI reject reason code for human feedback.
- the Transaction ID that is returned to the retailer back-end 1 host processor is a 15 digit number consisting of: DCNI unit identification (7 digits), last digit of year (1 digit), Julian date (3 digits), and transaction sequence number (4 digits).
- This information may be printed on the customer receipt as three groups of digits (7,4,4) as an ease-of-use issue, should it be necessary for the consumer to dictate his Transaction ID to a customer service representative over the telephone.
- the DCNI unit should transmit its stored data to the transaction collection system after it has aged past the "transaction void" window.
- the "transaction void" window is defined as the time past which the transaction cannot be canceled after it is taken (e.g. 15 minutes to eliminate the possibility of fraud).
- the data elements of each transaction transmitted to the host consist of the following: Retailer ID, Biller ID, Biller Account Number, Amount Paid, Sequence Number, Transaction Date/Time Stamp, Status as Active or Void, and Operator ID.
- these transactions may be sent in batches whose batch name conforms to the following naming convention: DCNI unit identification (7 digits), last digit of year (1 digit), Julian date (3 digits), and last transaction sequence number in batch (4 digits).
- DCNI unit identification 7. digits
- Julian date 3 digits
- last transaction sequence number in batch 4 digits
- Transaction Collection System While the data collection network interface may be a single unit, the central site transaction collection system may consist of multiple central processor server units acting in concert to perform a collective set of functions and processes. This design approach permits scaleable processing and avoids the possibility of single point failures that might curtail or impact the production processing of incoming transaction batches.
- Figure 14 illustrates one possible configuration for the transaction collection system 1400.
- incoming encrypted data files from the field data collection network interface units would come through a dial-up network or modem bank 1401 over a TI or similar connection 1402 into an entry router 1403 outside the central site firewall, via a channel service unit/data service unit 1404 (CSU/DSU) or other similar device for providing isolation between the network and the on-premises equipment.
- CSU/DSU channel service unit/data service unit
- Parallel firewall machines 1405, one operating in "hot back up" mode filter the inbound data traffic from validated and secure data sources.
- one of the ancillary functions of the firewalls 1405 is to load balance the data traffic across all available file transfer protocol (FTP) engines 1407.
- FTP file transfer protocol
- a plurality of FTP engines 1407 are shown in the diagram as being in a scaleable multi-server configuration, coupled via one or more integration hubs (e.g. 100 MB or 1 GB Ethernet hubs) 1425.
- the FTP engines 1407 provide the raw computing power to transfer data packets from the firewalls 1405, to coalesce the data packets into data files and to write them to the FTP storage server 1408, which may comprise RAID (redundant array of inexpensive disk) storage or similar mass storage.
- RAID redundant array of inexpensive disk
- the file decryption keys are fetched from the central transaction collection server 1410 and the file name is packaged in a message packet that is sent to one of a plurality of transaction processor (TP) engines 1409 in a scaleable multi-server configuration, coupled via one or more integration hubs 1425.
- TP transaction processor
- the transaction processor engines 1409 and FTP engines 1407 may optionally be provided with a console switching unit 1460 for sharing a single console (e.g. monitor, mouse, keyboard) across the plurality of engines 1407, 1409.
- a transaction processor engine 1409 (TPE) upon receiving this message packet, then has sufficient information available to locate, to decompress and to decrypt the inbound data file into its component data record types.
- the various received data record types are stored in a database (e.g. Structured Query Language, or SQL) on the transaction collection server 1410.
- the transaction collection server 1410 database is configured across several partitioned sets of physical hardware 1411 set up for RAID storage operation. The primary purpose for spreading the databases over several pieces of physical and logical hardware and/or software is to avoid having single points of data congestion and equipment failure.
- the transaction collection server 1410 database is the destination for all the data collected at all the retail processing locations. On a scheduled production basis, the data is aggregated and sorted, according to the biller identification associated with each transaction customer account number. ACH transaction files are prepared and formatted by biller identification, which then maps into biller-designated destination ABA bank routing and bank account numbers.
- the administrative/data reporting server 1420 provides access to a copy of the production data for back office operations and monitoring by one or more work stations 1427, without burdening the front end collection system.
- the "glue” that holds the whole network together is one or more 100 MB or 1 GB Ethernet hubs 1425. This technology provides the foundation cornerstone by which various elements of the network communicate with each other and access each other's mass storage as local devices.
- the web/fax server 1430 provides on-demand reports to retailers through a web server application. It also provides periodic reports to retailers that can be faxed out through the normal public telephone network 1445.
- the electronic transmission interface (ETI) machine 1440 prepares the data that has been accumulated and processed by the transaction collection server 1410 for transmission to the Federal Reserve ACH Network.
- ACH CIE customer initiated entry
- An optical drive 1432, tape storage unit 1433, or other such storage means may be provided for creating removable backups, which may be stored off-site.
- AMOUNT (Field 6) is populated with the Customer Payment
- INDIVIDUAL NAME (Field 7) is populated with the Transaction Sequence Number (which contains the Julian date of payment)
- INDIVIDUAL IDENTIFICATION NUMBER (Field 8) is populated with the Biller Customer Account Number
- DISCRETIONARY DATA (Field 9) is populated with the Payment Complete Time encoded as a two digit time field ranging from 00 to 95. This number may be divided by 4 to calculate military hours (decimal) to the nearest quarter hour. For example, the number 26 divided by 4 would yield 6.5 (0630 or 6:30 AM).
- FIG. 15 illustrates an exemplary transaction processor executive controller (TPEC) display screen 1500, in one embodiment of the invention.
- the TPEC monitor program resides in the FTP storage server 1408 and is responsible for detecting complete inbound data files from the field retailer based data communication network interface units. When an inbound data file is detected, TPEC fetches the file decryption key from a master database and then dispatches it and the data file name to one of the transaction processor engine (TPE) 1409 program threads.
- TPE transaction processor engine
- the TPE 1409 decompresses and decrypts the inbound data file and stores the component plain text data records in the SQL database that resides within the transaction collection server 1410 on RAID storage 1411.
- display screen 1500 may include features such as jobs attempted 1501 (i.e. batches received) and transactions processed 1502 (i.e. individual data records processed from the batches received).
- This display 1500 shows the current Transaction Process Engine(s) batch job statistics for the system batch dated 10/12/2000 at 13:44:31.
- TPEC is in PAUSEd State - it is not currently dispatching any detected inbound data files to the TPE engines.1409. For this batch, 129 inbound data files were processed that resulted in 244 data records, stored in the SQL database.
- FIG. 16 illustrates an exemplary system monitor station (SMS) display screen 1600, in one embodiment of the invention.
- This display 1600 shows that individual retailers may be configured in a directory tree-like structure, with each of a plurality of distributors 1601 being a parent to one or more retailer bill pay sites 1602.
- the directory framework of retailers 1602 may conform to any convenient form of administrative structure, e.g. a distributor model, based on a hierarchy of people, or a physical model, based on territories with defined boundaries (states, counties, or towns).
- INSTRUCTION files 1603 that can reside at any level within an arbitrary configuration structure.
- An INSTRUCTION file 1603 contains operational directives to be applied to retailer terminals at or below the level of placement in the directory structure (i.e.
- FIG. 17 illustrates an exemplary end of batch monitor (EBM) display screen 1700, in one embodiment of the invention.
- EBM may be a Visual Basic program that orchestrates the series of Structured Query Language (SQL) scripts and ancillary programs to perform transaction consolidation, general system batch reporting, database trimming and data archiving.
- Figure 18 illustrates an exemplary electronic transmission interface (ETI) display screen 1800, in one embodiment of the invention.
- This display 1800 includes a summary 1801 of the dollar amounts sent to each of the electronically connected remittance partners.
- the batch status window 1802 shows the current status of the transmission batches (QUEUED, ACTIVE, DELETED, or COMPLETED).
- An additional column (not shown) may be included to show the confirmed time of transmission completion.
- Figure 19 illustrates an exemplary ETI transaction detail display screen 1900, in one embodiment of the invention.
- MasterCard RPS MasterCard RPS
- this display shows the details for each remitted transaction - biller name 1901, originating source transaction detail for direct traceability 1902, customer account number 1903 and amount paid 1904. From an electronic perspective, the biller is only interested in the payment amounts to be applied to various customer account numbers .
- FIG. 20 illustrates an exemplary ETI map biller-to-partner display screen 2000, in one embodiment of the invention.
- ETI map biller-to-partner display screen 2000 For each biller defined in the system, there is a one-to-one mapping of electronic destinations. While ninety-five percent or more billers may have their remittances delivered via the Federal Reserve ACH network, the remainder of the remittances may be delivered by a combination of directly connected links and secondary consolidator links.
- Display screen 2000 shows, for each biller, a Biller ID 2001 and Biller Name 2002 mapped to a particular electronic destination 2003. Not explicitly demonstrated by this display is the implicit dynamic mapping of internal Biller IDs 2001 to external Merchant IDs (depending on the electronic link utilized) that has to take place for this system to interoperate successfully with a variety of external electronic networks.
- Figure 21 illustrates an exemplary transaction browser display screen 2100, in one embodiment of the invention.
- the transaction browser program accesses and displays all the relevant information pertaining to that transaction, either locally or through a secure Web Server Application access to remote billers.
- Such information may include, e.g., a selection entry portion 2101, check and trail record 2102, and payment record 2103.
- the system derives the biller account number from the proposed standard format of biller imprinted bar codes, as described herein.
- the primary function of the central site transaction collection system 1400 is to collect transaction data from the retail network, sort and aggregate the data by biller, and to remit the customer payment data and the money to the biller by the Federal Reserve ACH Network.
- the ACH Network is used to electronically debit the retailers for the payments that they have collected from their customers.
- the transaction fee, paid by the customer may be shared by the retailer and the transaction processor.
- Central Biller Registry System The current state of the bill payment industry is very fragmented, and many billers currently print their own customer invoices to suit the needs of their own remittance processing systems. There is no universal invoice printing standard to which everyone adheres because there is no economic motivation to do so.
- assigned biller bar code identification numbers may be 7 digits in length. The first 6 digits identify the biller (in a maximum population of 1 million) with the 7 th digit being the check digit.
- the following information might be required for central collection: (1) Biller Name, Address, Phone Number, Fax Number; (2) Biller Administrative Contact Name, Phone Number, E-Mail Address; (3) Biller Remittance Contact Name, Phone Number, E-Mail Address; (4); Electronic Connection Type (ACH or Direct); (5) Bank Name, Address, Remit Account Information, Type; (6) Bank Contact Name, Phone Number, E-Mail Address; (7) Account Number Information - detailed account format specifications.
- a biller bar code identification number would be assigned and a set of bar code print specifications sent to the biller contact. It would then be the responsibility of the biller to print and to remit a set of test bill remittance stubs for conformance testing and validation. Conformance testing on the set of sample bill remittance stubs would ensure that the bar code image quality and physical bar code dimensions satisfied the lowest common denominator bar code scanners at retail. Validation testing would ensure that information, supplied by the biller, regarding the printed bar coded customer account number conformed to published account number validation specifications.
- the INDIVIDUAL NAME field (Field 7) in the ACH CIE Batch Detail Record contains the customer payment transaction number, which is composed of the following 4 data fields: DCNI unit identification (7 digits), last digit of year (1 digit), Julian Date (3 digits), and the transaction sequence number (4 digits). While the DCNI unit number identifies the retailer where the customer payment was taken, the next four digits specify the year and the Julian date of payment submission and completion.
- the DISCRETIONARY DATA (Field 9) in the ACH CIE Batch Detail Record may be populated with the Payment Complete Time encoded as a two digit time field ranging from 00 to 95.
- this number may be divided by 4 to calculate military hours (decimal) to the nearest quarter hour. For example, the number 26 divided by 4 would yield 6.5 (0630 or 6:30 AM).
- Time synchronization may be acquired from universal time standards available through the Internet or national dial-up time services (U.S. Naval Observatory, Washington, DC or the National Institute of Standards and Technology, Boulder, CO). " Whether or not sanctioned by a governmental agency, such as the U.S. Post Office, this time stamp could be recognized in much the same way that the U.S. Post Office postmark on letters is used to prove on-time submission. The customer would have printed proof of payment date and time, by virtue of his store receipt, that a biller could not artificially manipulate for purposes of assessing penalty payments.
- Bill payment "due date" as specified in the small print of every credit contract can have a variety of individual definitions, none of which is directly visible to or traceable later by the customer.
- a universal bill payment time stamp would eliminate all the variability of these "due date” definitions if the biller recognized this time stamp as the creditor date of receipt as specified in the Federal Reserve Regulation Z Section 226.10. The advantage of this date stamping mechanism to the customer is that it would give him marginally more time to remit his bill payment on time to the biller.
- the customer could pay his bill payment at a late-hours store at one minute to midnight on the due date. The customer would no longer have to worry about remittance delivery times.
- the advantage of this date stamping mechanism to the biller is that extremely late payments may be electronically credited to the biller no later than 36 hours after customer payment. In the majority of cases in which the biller had multiple daily data feeds from his bank, the credit would probably issue in fewer than 24 hours. Electronically delivered and electronically applied, the current level of biller effort in the handling of late payments would be entirely eliminated with this system in place. In the extreme case, billers could safely invoke 48-hour cut-off notices with little or no error of service call recalls.
- FTP FTP
- File data formats and the particular delivery mechanisms may be tailored to meet any biller requirement, so long as it expedites the flow of customer payment information.
- biller data would be available for processing within minutes after the scheduled transaction collection system production "system roll” completes.
- the "system roll” sorts and aggregates biller data on a daily production schedule - once every 12 hours. Payment totals for these transaction batches would be delivered via the ACH Network.
- ACH Network For a trusted remitter, it is not necessary to directly couple the transaction dollars with the transaction data.
- the time lag between transaction data and transaction dollars via the Federal Reserve ACH Network should be no more than 24 hours.
- the embodiments described hereinabove relate, generally, to bar code based biller/payor systems for electronic bill payment.
- an exemplary electronic bill payment infrastructure e.g., see reference numeral 500 of Figure 5
- consumers can pay their bills at supermarkets and large retail chain stores and receive immediate credit from billers for their payments.
- the biller receives good payment funds, deposited directly into his bank account, and error-free electronic payment data for consumer bill payments by 6 AM the very next business day.
- the biller backdates the received bill payments to the "electronic postmark" time and date paid at retail, regardless of the time that the payment data takes to post to the biller's accounts receivable system.
- an infrastructure provides for an electronic process that remits error-free payment funds and data directly to billers within hours, rather than days.
- this electronic bill payment process may be, it may not be fast enough for the needs of Internet commerce based companies, selling products to electronically connected remote consumers.
- the electronic bill payment process still depends on the biller generating a paper bar coded invoice statement and sending it to the consumer by US Mail, a process that can take, on average, anywhere between 6-8 days.
- the consumer has the financial resources in hand to pay his bill, he can then remit his payment directly to the biller, electronically, within hours.
- Internet commerce-based companies can now choose a new bill payment method that is very simple and can reduce the time interval between biller invoice statement generation and consumer payment notification to the biller, to less an hour.
- Another improvement to the electronic infrastructure for this process, described in this section is the provision for person-to-person money transfers.
- Improved Electronic Bill Payment Network relate to an improved national electronic bill payment network, wherein bar coded invoice statements are generated immediately by the biller or the consumer and remitted to the consumer in the span of seconds to minutes via facsimile, e-mail or other image transmission method.
- the consumer Upon receipt of such an imaged invoice statement, the consumer, with payment in hand, may go to a local store that accepts and processes these bill payments.
- the consumer payment is processed at retail, it is electronically remitted to the biller with 1 absolute accuracy within 24 hours after receipt of payment, and electronic notification
- An exemplary embodiment of the improved bar coded bill payment based 6 system consistent with the present invention utilizes a bar code on the biller invoice, 7 which is delivered to the customer electronically, i.e., by fax, e-mail, or, other image 8 transmission method, and payment information and payment credits are returned to 9 the biller electronically.
- This system may augment some elements of the biller/payor 0 network 500 (described hereinabove with respect to Figure 5) with faster and parallel 1 processing elements.
- the biller accounts receivable and US Mail 2 consumer remittance mechanisms may be enhanced with a new accounts receivable invoice statement image generation mechanism that can be activated, on demand, either by a biller customer service representative or by a consumer initiated action.
- the result of either action is a bar coded invoice statement image that is electronically remitted to the consumer within a time frame of seconds to minutes.
- the transaction collection system described hereinabove which already has an inherent user Internet accessible transaction browser capability, may be enhanced with e-mail, facsimile or other means of electronic notification to the biller when specifically designated payments have been received.
- An automated caller response system may provide for consumer inquiry confirmation of payments.
- FIG 22 an exemplary improved electronic bill payment network 2200 is illustrated.
- the biller accounts receivable 2202 may accumulate a dollar total and generate a detailed bar coded invoice statement image 2203 that can be electronically remitted to the consumer 2204.
- This same process can also be used by a biller customer service representative 2201 to replicate a previous invoice statement that a consumer may have lost. For example, if a consumer wants an immediate replacement copy of the invoice for payment, the consumer can access a biller web site to generate a remittance or deposit document.
- the time for a consumer to request the electronic invoice statement 2203 may be as little as a few minutes after a request is made.
- the invoice 2203 is transmitted to the consumer 2204, which transmission may be from a few seconds to several minutes, depending on factors such as the method of transmission, queue capacity, and number of open queue slots.
- the consumer 2204 receives the bar coded invoice statement image 2203.
- To pay the bill the consumer 2203 might go to a local store (or other location with appropriate hardware/software/network connection) that processes these bill payments.
- the time for this to occur is variable, depending upon the consumer's circumstances, and may occur in as little as a few minutes.
- the consumer 2203 presents his imaged bar coded invoice statement 2203 to the checkout cashier for scanning by the checkout scanner 2205, which may be done while other retail UPC coded items are being scanned. Instead of looking up an in-house UPC code for pricing, the scanner 2205 would pick up the bill payment bar code that identifies the biller to be paid and the account number to be credited. The consumer tells the checkout cashier the amount to be paid on that account and his option for requesting "normal" or "express” payment processing, and the cashier inputs the amount to be paid into a terminal (which may be integrated into a point-of-sale system) which is in communication with a backend host processing system 2206.
- a terminal which may be integrated into a point-of-sale system
- the checkout of remaining products and items (or bills) continues until the complete total for all goods and services is calculated.
- that bill payment is then complete.
- the consumer may receive a printed receipt of the payment tendered with the date and time the payment was made.
- the in-store backend host processing system 2206 immediately completes and forwards all the payment data to the data collection network interface unit 2207, which may occur in a little as a few seconds.
- the data collection network interface 2207 (DCNI) unit collects and stores all the consumer bill payment data in non-volatile memory.
- the DCNI 2207 Periodically (e.g., throughout the day, and/or based on time and transaction volume thresholds), the DCNI 2207 transmits the bill payment data to the central site transaction collection system 2211, which is part of a central site computer system 2210 that may also include an Internet server/browser 2212 and/or automatic caller response system 2213. Additional transmissions may be scheduled before the daily transaction collection system 2211 aggregation times. If a particular consumer payment is designated for "express" processing, it may immediately be transmitted to the central site computer system 2210 when the transaction void window expires for that payment. The time for the back-end and collection system processing has no impact on customer payment time, since all payments may be time-stamped.
- the transaction collection system 2211 may continuously (and/or periodically) receive payment data information from a distributed network comprising a plurality of data collection network interface units 2207 deployed at field retail establishments. Before the last processing window closes at the Federal Reserve Automated Clearing House (ACH) Network 2214, all customer payments may be sorted and aggregated for direct remission to their respective billers, which may take approximately an hour. As the transaction collection system 2211 receives payment data information from the network of data collection network interface units 2207, it processes and stores each consumer bill payment into a database.
- ACH Federal Reserve Automated Clearing House
- an automated caller response system 2213 can verbally confirm the receipt of a particular transaction, particularly for customers 2209 seeking "comfort call” confirmation regarding the status of a payment.
- the biller customer service toll-free number may be nominally printed on the consumer receipt.
- the biller customer service toll-free number may be replaced with a special in-house toll-free number to relieve biller customer service representatives 2208 of nervous consumer confirmation inquiry calls, typically for payments that are long overdue.
- Processing and distribution of electronic payment data may be done using the Federal Reserve Automated Clearing House (ACH) Network 2214, which may take 6- 9 hours.
- ACH Federal Reserve Automated Clearing House
- the electronic payment data may be received from the ACH Network 2214 and stripped and reformatted according to biller specified formats, which may take 4-6 hours.
- the biller's accounts receivable 2202 and/or customer service computer files may be updated.
- the payment network/system 2200 described in this section may be contrasted with the biller-payor network/system 500 (described hereinabove with reference to Figures 5 et seq.), as follows: From the biller perspective, both networks 500, 2200 may be capable of delivering good payment funds and data directly into the biller's bank account by 6 AM the next business day after the consumer pays his bill at retail. The improved network 2200 may deliver electronic notification of consumer payment information to the biller within minutes after the payment is made at retail with the "express" delivery service.
- the improved network 2200 can deliver a consumer invoice electronically and immediately, assuming the biller can generate and remit an electronic invoice statement image 2203 and the consumer has a corresponding device or means with which to receive the electronic biller invoice statement image (e-mail, facsimile etc.).
- the biller having Internet access and using his choice of standard Internet browsers, can confirm a consumer's payment by querying the database of processed transactions in the transaction collection system 2211 with a variety of database selection keys and criteria. Further, the biller can receive full payment funds for the amount stated on the bar coded invoice statement 2203.
- the consumer does not have to divulge any personal financial information to a remote Internet storefront that electronically generates and delivers bar coded invoice statements directly to a consumer.
- the consumer can subsequently confirm the electronic receipt of his processed payment at retail from an automatic caller response system 2213.
- the consumer having Internet access and using his choice of standard Internet browsers, can confirm his own payment by querying the database of processed transactions in the transaction collection system 2211 with a specific transaction identification number.
- Internet commerce based companies there is no mechanism available for conducting a purely "cash" sale over the Internet, where consumer cash and retail product can be exchanged in one anonymous atomic transaction.
- the enhanced electronic bill payment network 2200 consistent with the present invention permits remote buyers and sellers to perform anonymous "cash" sale transactions, using the Federal Reserve banking system as the trusted escrow agent to safely and securely transfer funds between buyers and sellers.
- An advantageous feature of this enhanced bill payment network, with a standardized bar coded bill payment "signature" featured as its centerpiece remittance mechanism, is that all the non-deterministic time delays have been removed from the total bill payment cycle.
- the two largest delay factors are the biller invoice paper statement preparation, printing, mailing systems and the US Post Office mail delivery system.
- the consumer can now exercise a larger control function over his bill payment remittance process.
- the consumer can request an immediate invoice statement, which only requires minutes to formulate and to deliver electronically.
- the consumer has his choice of payment methods at a trusted local retail establishment and receives a printed bill payment receipt confirmation, guaranteed by the biller.
- the consumer payment method to the biller is completely anonymous, in terms of divulged personal financial information. Subsequently, the consumer, as well as the biller, can verify that the bill payment has been received and processed at the central payment distribution site.
- payment funds and information may be electronically remitted to the biller within hours, by 6 AM the following business day directly into the biller's bank account.
- facsimile transmission to or from a computer, facsimile machine, e-mail, file transfer protocol (FTP), hypertext markup language (HTML), extended markup language (XML), hypertext transport protocol (HTTP), modem, the Internet, a wide-area network (WAN), a local-area network (LAN), diskette, or other removable storage medium.
- FTP file transfer protocol
- HTML hypertext markup language
- XML extended markup language
- HTTP hypertext transport protocol
- modem the Internet
- WAN wide-area network
- LAN local-area network
- diskette or other removable storage medium.
- domestic person-to-person money transfers can be easily accomplished with a bar coded deposit slip that permits a remote sender to remit funds directly into a receiver's bank checking account, providing funds that are subsequently accessible at a convenient local automated teller machine (ATM) or for a debit card purchase.
- ATM automated teller machine
- Future international (e.g., Mexican) person-to-person money transfers can be coordinated with appropriate financial organizations or banks that commonly distribute a form of debit card to their customer base. These organizations would distribute to their customer base plastic bar coded deposit-only cards keyed directly to their debit card, which may then be sent to a remitter in another country (e.g., the United States). Using that bar coded plastic deposit-only card instead of a bar coded bank deposit slip would effect a deposit of the funds directly into the debit card account corresponding to the deposit-only card. In this way, domestic and international money transfers could cost far less than the fees charged today for this equivalent service.
- the retail based electronic bill payment infrastructure is utilized, with the modification that the biller identification number is now used to identify the destination payment network instead of a destination biller organization.
- the standard bank account numbering scheme is based on a two-part number system consisting of an ABA (American Banking Association) number (8 digits plus a check digit), uniquely identifying the U.S. bank institution, and a local account numbering convention within that banking institution.
- the definition of a new format designator validation template would offer several advantages: An additional customer account number validation step further reduces data errors. Within the full customer specified account number, the ABA portion of the account number can be independently verified. The biller identification number would be reduced from 6 to 2 digits, in recognition of the fact that there are many fewer bank based or money transfer payment networks than billers. With a reduced number string, shorter bar code strings fit more appropriately on small banking deposit slips that measure, on average, 6" wide by 3" high.
- this bar code 2401 appearing on a bank deposit slip 2400 could be presented at a retail checkout aisle, equipped for bill payment transactions, to initiate domestic person-to-person money transfers.
- the money remitted the previous day may be available to the recipient to withdraw from a local ATM machine or to make payment from a debit card keyed or associated with that account.
- the ATM or debit card PIN personal identification number
- the ATM or debit card PIN provides the same level of access security to the receiver of these person-to-person money transfers as exists for local funds that already reside in the account.
- the biller identification number may be used to uniquely identify the target destination payment network.
- a new format designator validation template definition offers extended customer account number verification advantages only if the destination payment network is willing to divulge its mathematical or other method of customer account numbering validation scheme.
- GasoMax a national chain of retail gas stations/convenience supermarket stores called GasoMax is located throughout the whole of Mexico, serving the public at large.
- GasoMax issues PIN protected debit cards to all their customers, in effect, setting up a pseudo-bank account for each of them. Instead of carrying cash, these customers deposit or apply money to these accounts so that they can later purchase food staples or convenience items at the same time they come for fuel.
- PIN protected debit cards to their customer base, one or more bar coded deposit only cards are included (and/or a bar code might be printed on the debit card itself).
- the debit card can either be used to deposit local money into their account or to withdraw money in the form of purchases at the national chain GasoMax gas stations.
- Figure 25 illustrates an exemplary GasoMax debit card 2500, which resembles a standard debit card.
- Figure 26 illustrates an exemplary deposit-only card 2600 comprising a bar code 2601 consistent with the invention.
- the bar coded deposit-only card 2600 (or, alternatively, a bar code printed on the standard debit card) would be used in U.S. retail stores that offer access to the electronic bill payment network.
- GasoMax Payments remitted to this payment network are automatically converted to local currency by GasoMax at a better rate than the larger commercial money transfer organizations.
- Commercial money transfer companies charge up to $25 per $300 remittance as a foreign exchange (FX) fee on top of the base $35 remittance fee.
- FX foreign exchange
- wire transfer companies have been sanctioned for these usurious currency exchange practices.
- GasoMax would have a greater incentive to offer a better exchange rate to its customer base for its money transfer services than the current crop of commercial money transfer services.
- GasoMax could expand its local customer base to shop for goods and services through its chain of gas station supermarkets that also offers a convenient money transfer service, as an affinity draw or loyalty program, for relatives working outside of the country to support their loved ones in Mexico.
- Example 1 Payment for Mobile Telephone Service A client procures a mobile phone subscription from a well-known national vendor. The client gives his place of employment as his cell phone billing address. As a new customer, he is assigned a total credit limit and an accrued monthly limit. When this client subsequently leaves his place of employment, he forgets about changing his mobile phone billing address and continues to use his mobile phone regularly, until one day his mobile phone stops working. When he calls the customer service office to inquire about the matter, he finds out that his mobile phone usage is well within his credit limits but that the reason for his mobile phone being disconnected is that bill payment is overdue by ten days.
- Example 2 Payment for Internet-Based Auction
- the business model for the Internet-based auction (e.g., eBay) is very basic in concept, a meeting place for bringing together Internet buyers and sellers, wherein an electronic framework displays sellers' goods and services.
- the online auction house charges a sales commission. It is the responsibility of the seller and the buyer to establish a lowest common denominator payment exchange method. Individuals selling items, are generally not equipped to process Mastercard or VISA credit or debit cards. If the seller accepts a personal check payment from the buyer, shipment of the sold item is delayed until the buyer check clears. A buyer can mitigate a seller shipment delay if he is willing to go out and purchase a money order to send to the seller. If the buyer and seller wish to use a third-party payment clearinghouse, (e.g., Billpoint or PayPal), then both must register personal financial information about their respective bank accounts to transfer money, as well as pay yet another sales commission charge.
- a third-party payment clearinghouse e.g., Billpoint or PayPal
- an online auction house could provide a cost-effective and value-added anonymous payment alternative within its framework of auction services.
- the online auction house provides the means for the buyer to print out a bar coded invoice statement, citing the online auction house as the biller of record with a transaction identification number. Instead of purchasing a money order, which would then have to be physically remitted, the buyer then pays this invoice at a local supermarket.
- the online auction house receives the electronic payment the very next business day, it notifies the seller of the completed payment via e-mail and then sends a check for that payment amount to the seller.
- Example 4 Payment to College Student When a parent agrees to send money for college expenses to a child away at school, a question that typically arises is, "how fast do you need the money?"
- a printed bar coded bill payment "signature" on out-of-town bank checking account deposit slips would enable remote deposits with a simple cash, check, debit card or any credit card payment at a local supermarket.
- a college-bound child could have previously sent home an ample supply of these deposit slips to cover for such eventualities. If a supply of originals is not available, a facsimile copy (sent at high resolution mode) will generally perform the job equally well. Funds deposited with this payment mechanism are electronically available the very next morning for withdrawal from a local ATM cash-dispensing machine.
- the present invention may use the public Internet and Internet compatible HTTP and UDP protocols for the network interconnections described herein, as well as the Federal Reserve Automated Clearing House (ACH) Network or other networks.
- ACH Federal Reserve Automated Clearing House
- scanning bar codes in methods consistent with the invention, may be performed using, e.g., wand or handheld scanning devices, scanning devices mounted to or near a point of sale system, and other such scanning devices, and such devices may be devices coupled to other devices, e.g., a computer, cash register, or point of sale system, or alternatively, integrated therein.
- a scanning device consistent with the invention may alternatively be coupled to or integrated into a PDA, handheld or pocket computer, as well as- a mobile telephone or other portable, wireless, or computerized device.
- an account corresponding to a mobile telephone or other such device, or other credit or debit account corresponding to the user of such a device could be automatically debited for payment to a payee, in methods consistent with the invention.
- conventional general purpose computers e.g. IBM-compatible, Apple Macintosh, and/or RISC microprocessor-based computers
- mainframes e.g. mainframes
- minicomputers e.g. modem, DSL, satellite and/or ISDN communications
- memory storage means e.g.
- RAM, ROM and storage devices e.g. computer- readable memory, disk array, direct access storage
- network hardware and software e.g. LAN/WAN network backbone systems and/or Internet
- other types of computers and network resources may be used without departing from the present invention.
- the invention as described herein may be embodied in one or more computers residing on one or more server systems, and input/output access to the invention may comprise appropriate hardware and software (e.g. personal and/or mainframe computers provisioned with Internet wide area network communications hardware and software (e.g.
- the above-described servers consistent with the present invention may be remote Internet-based servers accessible through conventional communications channels (e.g. conventional telecommunications, broadband communications, wireless communications) using conventional browser software (e.g. Netscape Navigator or Microsoft Internet Explorer ), and that the present invention should be appropriately adapted to include such communication functionality.
- conventional communications channels e.g. conventional telecommunications, broadband communications, wireless communications
- conventional browser software e.g. Netscape Navigator or Microsoft Internet Explorer
- each of the functional components of the present invention may be embodied as one or more distributed computer program processes running on one or more conventional general purpose computers networked together by conventional networking hardware and software.
- Each of these functional components may be embodied by running distributed computer program processes (e.g., generated using "full-scale” relational database engines such as IBM DB2TM, Microsoft SQL Server TM, Sybase SQL ServerTM, or Oracle 8.0 TM database managers, and/or a JDBC interface to link to such databases) on networked computer systems (e.g. comprising mainframe and/or symmetrically or massively parallel computing systems such as the IBM SB2 or HP 9000 computer systems) including appropriate mass storage, networking, and other hardware and software for permitting these functional components to achieve the stated function.
- networked computer systems e.g. comprising mainframe and/or symmetrically or massively parallel computing systems such as the IBM SB2 or HP 9000 computer systems
- These computer systems may be geographically distributed and connected together via appropriate wide- and local- area network hardware and software.
- Primary elements of the invention may be server-based and may reside on hardware supporting an operating system such as Microsoft Windows NT/2000TM or UNIX.
- Clients may include computers with windowed or non- windowed operating systems, e.g., a PC that supports Apple Macintosh TM, Microsoft Windows 95/98/NT/ME/2000 TM, or MS-DOS TM, a UNIX Motif workstation platform, a Palm TM, Windows CE TM -based or other handheld computer, a network- or web-enabled mobile telephone or similar device, or any other computer capable of TCP/IP or other network-based interaction.
- the communications media described herein may be a wired or wireless network, or a combination thereof.
- the aforesaid functional components may be embodied by a plurality of separate computer processes (e.g. generated via dBase TM, Xbase TM, MS Access TM or other "flat file” type database management systems or products) running on IBM-type, Intel Pentium TM or RISC microprocessor-based personal computers networked together via conventional networking hardware and software and including such other additional conventional hardware and software as is necessary to permit these functional components to achieve the stated functionalities.
- a non-relational flat file "table" may be included in at least one of the networked personal computers to represent at least portions of data stored by a system consistent with the present invention.
- These personal computers may run, e.g., Unix, Microsoft Windows NT/2000 TM or Windows 95/98/METM operating system.
- the aforesaid functional components of a system consistent with the present invention may also comprise a combination of the above two configurations (e.g. by computer program processes running on a combination of personal computers, RISC systems, mainframes, symmetric or parallel computer systems, and/or other appropriate hardware and software, networked together via appropriate wide- and local-area network hardware and software).
- possible embodiments of the invention may include one- or two-way data encryption and/or digital certification for data being input and output, to provide security to data during transfer.
- Further embodiments may comprise security means in the including one or more of the following: password or PIN number protection, use of a semiconductor, magnetic or other physical key device, biometric methods (including fingerprint, nailbed, palm, iris, or retina scanning, handwriting analysis, handprint recognition, voice recognition, or facial imaging), or other security measures known in the art.
- security measures may be implemented in one or more processes of the invention.
- Source code may be written in an object-oriented or non-object-oriented programming language using relational or flat-file databases and may include the use of other programming languages, e.g., C++, Java, HTML, Perl, UNIX shell scripting, assembly language, Fortran, Pascal, Visual Basic, and QuickBasic.
- screen displays illustrated herein at Figures 15-21 are provided by way of example only, and are not to be construed as limiting the invention or any component thereof to the exemplary embodiments illustrated therein.
- the system and method described herein may be implemented as part of a business method, wherein payment is received from users, which might include customers, retailers, and/or billers employing the invention. Such users may pay for the use of the invention based on the number of files, messages, bills, or other units of data sent or received or processed, based on bandwidth used, on a periodic (weekly, monthly, yearly) or per-use basis, or in a number of other ways consistent with the invention, as will be appreciated by those skilled in the art.
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/737,011 US6993507B2 (en) | 2000-12-14 | 2000-12-14 | Bar coded bill payment system and method |
US737011 | 2000-12-14 | ||
PCT/US2001/048442 WO2002048835A2 (en) | 2000-12-14 | 2001-12-14 | Bar coded bill payment system and method |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1342146A2 true EP1342146A2 (en) | 2003-09-10 |
EP1342146A4 EP1342146A4 (en) | 2009-11-18 |
Family
ID=24962246
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01988313A Withdrawn EP1342146A4 (en) | 2000-12-14 | 2001-12-14 | Bar coded bill payment system and method |
Country Status (5)
Country | Link |
---|---|
US (4) | US6993507B2 (en) |
EP (1) | EP1342146A4 (en) |
CA (1) | CA2432750A1 (en) |
MX (1) | MXPA03005301A (en) |
WO (1) | WO2002048835A2 (en) |
Families Citing this family (273)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7016524B2 (en) * | 1994-04-14 | 2006-03-21 | Moore Lewis J | System for authenticating and processing of checks and other bearer documents |
US7451114B1 (en) | 1999-02-19 | 2008-11-11 | Visa International Service Association | Conducting commerce between individuals |
GB9925227D0 (en) | 1999-10-25 | 1999-12-22 | Internet Limited | Data storage retrieval and access system |
US7104440B2 (en) * | 1999-10-26 | 2006-09-12 | First Data Corporation | Money transfer systems and methods for travelers |
US8036905B2 (en) * | 2000-02-29 | 2011-10-11 | Newgistics, Inc. | Method and system for processing the local return of remotely purchased products |
US8386337B2 (en) | 2000-03-24 | 2013-02-26 | Newgistics, Inc. | System and method for single-action returns of remotely purchased merchandise |
US7146338B2 (en) * | 2001-06-28 | 2006-12-05 | Checkfree Services Corporation | Inter-network financial service |
US6993507B2 (en) * | 2000-12-14 | 2006-01-31 | Pacific Payment Systems, Inc. | Bar coded bill payment system and method |
US6564996B2 (en) * | 2000-12-29 | 2003-05-20 | Ncr Corporation | System and method of correlating a check tendered as payment for a purchase to the particular purchase transaction |
EP1237108A3 (en) * | 2001-02-23 | 2003-08-13 | Navaho Networks Inc. | Secure electronic commerce |
US7555462B2 (en) * | 2001-04-12 | 2009-06-30 | International Business Machines Corporation | Method and apparatus for incorporating scanned checks into financial applications |
US7716091B2 (en) * | 2001-05-24 | 2010-05-11 | Newgistics, Inc. | Local returns of remotely purchased merchandise with return code validation |
US20040199545A1 (en) * | 2001-08-14 | 2004-10-07 | Frederico Wagner | Networked disposal and replenishment apparatus |
US7080777B2 (en) * | 2001-08-14 | 2006-07-25 | Ikan Technologies Inc. | Networked disposal and information distribution apparatus |
US7165721B2 (en) * | 2001-08-14 | 2007-01-23 | Ikan Technologies Inc. | Networked disposal and sample provisioning apparatus |
US6663004B2 (en) * | 2001-08-14 | 2003-12-16 | Frederico Wagner | Method and system for disposing of discarded items |
US7328842B2 (en) * | 2001-08-14 | 2008-02-12 | Ikan Technologies Inc. | Networked waste processing apparatus |
US7054430B2 (en) | 2001-08-23 | 2006-05-30 | Paymentone Corporation | Method and apparatus to validate a subscriber line |
JP3815671B2 (en) * | 2001-12-20 | 2006-08-30 | 村田機械株式会社 | Internet facsimile machine |
US20030135454A1 (en) * | 2002-01-11 | 2003-07-17 | Keller Joseph F. | Debit authorization post card |
MXPA04007821A (en) * | 2002-02-14 | 2005-04-19 | Pessin Zachary | Apparatus and method of a distributed capital system. |
US20030167232A1 (en) * | 2002-03-01 | 2003-09-04 | Linton Lascelles A. | Method of reducing online fraud |
US20030177090A1 (en) * | 2002-03-12 | 2003-09-18 | Guy Eden | System and method for automatic bill payment |
US20040039715A1 (en) * | 2002-06-24 | 2004-02-26 | Gullo John F. | Systems and methods for providing an express mail label |
US7685049B1 (en) | 2002-06-26 | 2010-03-23 | Trading Technologies International Inc. | System and method for coalescing market data at a client device |
US7580873B1 (en) * | 2002-07-23 | 2009-08-25 | At&T Intellectual Property I, L.P. | Electronic financial assistant |
IES20020712A2 (en) | 2002-09-04 | 2004-03-10 | Mainline Corporate Holdings | A method and system for transferring funds |
US7814012B2 (en) * | 2002-12-12 | 2010-10-12 | Oracle International Corporation | Aggregated postal billing and payment methods and systems |
US20040215531A1 (en) * | 2003-02-10 | 2004-10-28 | Stashluk Edward J. | Computer generated merchandise return labels with rules-based coding |
US20040193436A1 (en) * | 2003-02-10 | 2004-09-30 | Stashluk Edward J. | Method and system using return labels with dynamically generated multiple datapoint coding |
GB0303051D0 (en) * | 2003-02-11 | 2003-03-19 | William Sinclair & Sons Statio | Identifiable documents |
US7195151B2 (en) * | 2003-02-25 | 2007-03-27 | American Cash Exchange, L.L.C. | Method and system for automated value transfer |
US20040236631A1 (en) * | 2003-03-10 | 2004-11-25 | Graham Roger D. | Single point of entry collection system |
US11205321B2 (en) * | 2003-10-01 | 2021-12-21 | Everi Payments Inc. | System and method for redeeming cashless gaming tickets to bank accounts via multifunction ATM |
US20050097046A1 (en) | 2003-10-30 | 2005-05-05 | Singfield Joy S. | Wireless electronic check deposit scanning and cashing machine with web-based online account cash management computer application system |
US20050125345A1 (en) * | 2003-11-25 | 2005-06-09 | Pitney Bowes Incorporated | Early bill payment process |
US20050125294A1 (en) * | 2003-12-04 | 2005-06-09 | Trilogy Payment Services, Inc. | Method for paying invoices |
US20050177510A1 (en) * | 2004-02-09 | 2005-08-11 | Visa International Service Association, A Delaware Corporation | Buyer initiated payment |
US20050203857A1 (en) * | 2004-03-09 | 2005-09-15 | Friedman Lawrence J. | Methods for transaction processing |
US7499873B2 (en) * | 2004-03-18 | 2009-03-03 | Jack Barron | Communication through a financial services network |
US8016185B2 (en) * | 2004-07-06 | 2011-09-13 | Visa International Service Association | Money transfer service with authentication |
US20100205063A1 (en) * | 2004-08-30 | 2010-08-12 | Randy Mersky | Electronic payment transaction system |
US20060085335A1 (en) * | 2004-10-19 | 2006-04-20 | First Data Corporation | Point of sale systems and methods for consumer bill payment |
US8152054B2 (en) | 2004-10-19 | 2012-04-10 | The Western Union Company | Money transfer systems and methods |
US20060089907A1 (en) * | 2004-10-22 | 2006-04-27 | Klaus Kohlmaier | Invoice verification process |
US9821344B2 (en) | 2004-12-10 | 2017-11-21 | Ikan Holdings Llc | Systems and methods for scanning information from storage area contents |
US7783558B1 (en) | 2004-12-28 | 2010-08-24 | Trading Technologies International, Inc. | System and method for providing market updates in an electronic trading environment |
US20060149577A1 (en) * | 2004-12-30 | 2006-07-06 | Newgistics, Inc. | System and method for the customized processing of returned merchandise |
US7669245B2 (en) | 2005-06-08 | 2010-02-23 | Searete, Llc | User accessibility to electronic paper |
US7643005B2 (en) | 2005-01-20 | 2010-01-05 | Searete, Llc | Semi-permanent electronic paper |
US8640259B2 (en) | 2005-01-20 | 2014-01-28 | The Invention Science Fund I, Llc | Notarizable electronic paper |
US7865734B2 (en) * | 2005-05-12 | 2011-01-04 | The Invention Science Fund I, Llc | Write accessibility for electronic paper |
US8281142B2 (en) | 2005-01-20 | 2012-10-02 | The Invention Science Fund I, Llc | Notarizable electronic paper |
US7739510B2 (en) | 2005-05-12 | 2010-06-15 | The Invention Science Fund I, Inc | Alert options for electronic-paper verification |
US7774606B2 (en) | 2005-01-20 | 2010-08-10 | The Invention Science Fund I, Inc | Write accessibility for electronic paper |
US7856555B2 (en) | 2005-01-20 | 2010-12-21 | The Invention Science Fund I, Llc | Write accessibility for electronic paper |
US8063878B2 (en) | 2005-01-20 | 2011-11-22 | The Invention Science Fund I, Llc | Permanent electronic paper |
EP1684225A1 (en) * | 2005-01-24 | 2006-07-26 | Sap Ag | Data processing system and method of providing a payment |
US10719859B2 (en) | 2005-01-28 | 2020-07-21 | Wells Fargo Bank, N.A. | Electronic bill pay and bill presentment account number treatment system and method |
JP4725148B2 (en) * | 2005-03-18 | 2011-07-13 | カシオ計算機株式会社 | Printing apparatus and program |
US9919014B2 (en) * | 2005-04-05 | 2018-03-20 | Membrane Protective Technologies, Inc. | Reproductive cell maintenance system |
US8672220B2 (en) | 2005-09-30 | 2014-03-18 | The Western Union Company | Money transfer system and method |
US8296649B2 (en) * | 2005-05-31 | 2012-10-23 | Sorenson Media, Inc. | Method, graphical interface and computer-readable medium for generating a preview of a reformatted preview segment |
US7975219B2 (en) * | 2005-05-31 | 2011-07-05 | Sorenson Media, Inc. | Method, graphical interface and computer-readable medium for reformatting data |
US7885979B2 (en) * | 2005-05-31 | 2011-02-08 | Sorenson Media, Inc. | Method, graphical interface and computer-readable medium for forming a batch job |
US8571980B1 (en) | 2005-06-01 | 2013-10-29 | Stragent, Llc | System, method and computer program product for transferring money |
US7427017B2 (en) | 2005-06-22 | 2008-09-23 | Remettra, Inc. | Method and system for collecting bank account information from an individual and authenticating the individual prior to allowing the bank account to receive an electronic fund transfer |
EP1922673A2 (en) * | 2005-08-19 | 2008-05-21 | Global Payment Technologies, Inc. | Information readers, apparatuses including information readers, and related methods |
US20070214078A1 (en) * | 2005-09-28 | 2007-09-13 | Transpayment, Inc. | Bill payment apparatus and method |
US20070150386A1 (en) * | 2005-12-14 | 2007-06-28 | Alina Deibler | Method for encouraging reporting of income/tips by sole proprietors and employees of cash based businesses |
EP1857971A1 (en) * | 2006-05-15 | 2007-11-21 | Siemens Aktiengesellschaft | Method for handling payments, pre-printed invoice form for handling payments, device for creating pre-printed invoice forms and device for communicating with a financial institution |
US8028902B2 (en) * | 2006-05-17 | 2011-10-04 | Mastercard International Incorporated | Methods for providing stand-in services for transaction card customization |
US7584890B2 (en) * | 2006-06-23 | 2009-09-08 | Global Payment Technologies, Inc. | Validator linear array |
US20080015985A1 (en) * | 2006-07-11 | 2008-01-17 | Armand Abhari | System and process for expedited payment through online banking/payment channel |
US8027917B2 (en) * | 2006-08-15 | 2011-09-27 | Frank Easterly | Method for facilitating financial and non financial transactions between customers, retailers and suppliers |
US8125667B2 (en) | 2006-09-15 | 2012-02-28 | Avery Levy | System and method for enabling transactions by means of print media that incorporate electronic recording and transmission means |
FR2906625B1 (en) * | 2006-09-29 | 2008-12-26 | Advanpost Sarl | METHOD FOR THE PERSONALIZED EDITING OF INTERACTIVE PAPER MAIL |
US20080228646A1 (en) * | 2006-10-04 | 2008-09-18 | Myers James R | Method and system for managing a non-changing payment card account number |
US7885451B1 (en) | 2006-10-31 | 2011-02-08 | United Services Automobile Association (Usaa) | Systems and methods for displaying negotiable instruments derived from various sources |
US8351677B1 (en) | 2006-10-31 | 2013-01-08 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of checks |
US7873200B1 (en) | 2006-10-31 | 2011-01-18 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of checks |
US8708227B1 (en) | 2006-10-31 | 2014-04-29 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of checks |
US8799147B1 (en) | 2006-10-31 | 2014-08-05 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of negotiable instruments with non-payee institutions |
US7876949B1 (en) | 2006-10-31 | 2011-01-25 | United Services Automobile Association | Systems and methods for remote deposit of checks |
US7548890B2 (en) * | 2006-11-21 | 2009-06-16 | Verient, Inc. | Systems and methods for identification and authentication of a user |
WO2008086428A1 (en) | 2007-01-09 | 2008-07-17 | Visa U.S.A. Inc. | Mobile phone payment process including threshold indicator |
US8566240B2 (en) | 2007-01-16 | 2013-10-22 | E2Interactive, Inc. | Systems and methods for the payment of customer bills utilizing payment platform of biller |
US20080172331A1 (en) * | 2007-01-16 | 2008-07-17 | Graves Phillip C | Bill Payment Card Method and System |
US8239325B2 (en) * | 2007-01-18 | 2012-08-07 | Paymentone Corporation | Method and system to verify the identity of a user |
US7809652B2 (en) | 2007-01-30 | 2010-10-05 | Visa U.S.A. Inc. | Signature based negative list for off line payment device validation |
US8234341B2 (en) * | 2007-02-05 | 2012-07-31 | Reagan Inventions, Llc | System and method for linking terrestrial mail over a network |
US8959033B1 (en) | 2007-03-15 | 2015-02-17 | United Services Automobile Association (Usaa) | Systems and methods for verification of remotely deposited checks |
US10380559B1 (en) | 2007-03-15 | 2019-08-13 | United Services Automobile Association (Usaa) | Systems and methods for check representment prevention |
US20080243685A1 (en) * | 2007-04-02 | 2008-10-02 | Nizam Antoo | Bill payment system |
BRPI0810369B8 (en) | 2007-04-17 | 2019-05-28 | Visa Usa Inc | method, computer readable medium, directory server, and telephone |
US7904353B2 (en) * | 2007-04-17 | 2011-03-08 | Christensen Mitchell T | Method and system for processing payments |
US20080288400A1 (en) | 2007-04-27 | 2008-11-20 | Cashedge, Inc. | Centralized Payment Method and System for Online and Offline Transactions |
US8433127B1 (en) | 2007-05-10 | 2013-04-30 | United Services Automobile Association (Usaa) | Systems and methods for real-time validation of check image quality |
US8538124B1 (en) | 2007-05-10 | 2013-09-17 | United Services Auto Association (USAA) | Systems and methods for real-time validation of check image quality |
US9058512B1 (en) | 2007-09-28 | 2015-06-16 | United Services Automobile Association (Usaa) | Systems and methods for digital signature detection |
US20090319421A1 (en) * | 2007-10-02 | 2009-12-24 | Mathis Kenneth A | Method and Apparatus for Performing Financial Transactions |
US9892454B1 (en) | 2007-10-23 | 2018-02-13 | United Services Automobile Association (Usaa) | Systems and methods for obtaining an image of a check to be deposited |
US9159101B1 (en) | 2007-10-23 | 2015-10-13 | United Services Automobile Association (Usaa) | Image processing |
US9898778B1 (en) | 2007-10-23 | 2018-02-20 | United Services Automobile Association (Usaa) | Systems and methods for obtaining an image of a check to be deposited |
US8358826B1 (en) | 2007-10-23 | 2013-01-22 | United Services Automobile Association (Usaa) | Systems and methods for receiving and orienting an image of one or more checks |
US7996316B1 (en) | 2007-10-30 | 2011-08-09 | United Services Automobile Association | Systems and methods to modify a negotiable instrument |
US7996314B1 (en) | 2007-10-30 | 2011-08-09 | United Services Automobile Association (Usaa) | Systems and methods to modify a negotiable instrument |
US7996315B1 (en) | 2007-10-30 | 2011-08-09 | United Services Automobile Association (Usaa) | Systems and methods to modify a negotiable instrument |
US8046301B1 (en) | 2007-10-30 | 2011-10-25 | United Services Automobile Association (Usaa) | Systems and methods to modify a negotiable instrument |
US8001051B1 (en) | 2007-10-30 | 2011-08-16 | United Services Automobile Association (Usaa) | Systems and methods to modify a negotiable instrument |
US20090108080A1 (en) * | 2007-10-31 | 2009-04-30 | Payscan America, Inc. | Bar coded monetary transaction system and method |
US8320657B1 (en) | 2007-10-31 | 2012-11-27 | United Services Automobile Association (Usaa) | Systems and methods to use a digital camera to remotely deposit a negotiable instrument |
US8290237B1 (en) | 2007-10-31 | 2012-10-16 | United Services Automobile Association (Usaa) | Systems and methods to use a digital camera to remotely deposit a negotiable instrument |
US7900822B1 (en) | 2007-11-06 | 2011-03-08 | United Services Automobile Association (Usaa) | Systems, methods, and apparatus for receiving images of one or more checks |
US7896232B1 (en) | 2007-11-06 | 2011-03-01 | United Services Automobile Association (Usaa) | Systems, methods, and apparatus for receiving images of one or more checks |
DE112009000137T5 (en) * | 2008-01-15 | 2011-02-17 | Visa U.S.A. Inc., San Francisco | System and method for data completion with start detection |
US10528925B2 (en) | 2008-01-18 | 2020-01-07 | Mitek Systems, Inc. | Systems and methods for mobile automated clearing house enrollment |
US20110196786A1 (en) * | 2008-01-31 | 2011-08-11 | Rene Lacerte | Determining trustworthiness and familiarity of users of an electronic billing and payment system |
US10043201B2 (en) * | 2008-01-31 | 2018-08-07 | Bill.Com, Inc. | Enhanced invitation process for electronic billing and payment system |
US20110184843A1 (en) * | 2008-01-31 | 2011-07-28 | Bill.Com, Inc. | Enhanced electronic anonymous payment system |
US20090204530A1 (en) * | 2008-01-31 | 2009-08-13 | Payscan America, Inc. | Bar coded monetary transaction system and method |
US7809615B2 (en) * | 2008-01-31 | 2010-10-05 | Bill.Com, Inc. | Enhanced automated capture of invoices into an electronic payment system |
US10769686B2 (en) | 2008-01-31 | 2020-09-08 | Bill.Com Llc | Enhanced invitation process for electronic billing and payment system |
US20140129431A1 (en) * | 2008-01-31 | 2014-05-08 | Bill.Com, Inc. | Enhanced System and Method For Private Interbank Clearing System |
US9141991B2 (en) | 2008-01-31 | 2015-09-22 | Bill.Com, Inc. | Enhanced electronic data and metadata interchange system and process for electronic billing and payment system |
US10380562B1 (en) | 2008-02-07 | 2019-08-13 | United Services Automobile Association (Usaa) | Systems and methods for mobile deposit of negotiable instruments |
US8412595B2 (en) * | 2008-03-07 | 2013-04-02 | American Express Travel Related Services Company, Inc. | Lifecycle tracking and management using RF |
US8219558B1 (en) | 2008-04-25 | 2012-07-10 | David Scott Trandal | Methods and systems for inventory management |
US7899823B1 (en) | 2008-04-25 | 2011-03-01 | Trandal David S | Methods and systems for inventory management |
US9715709B2 (en) | 2008-05-09 | 2017-07-25 | Visa International Services Association | Communication device including multi-part alias identifier |
US8351678B1 (en) | 2008-06-11 | 2013-01-08 | United Services Automobile Association (Usaa) | Duplicate check detection |
US8229861B1 (en) | 2008-06-11 | 2012-07-24 | Trandal David S | Methods and systems for online warranty management |
US8165934B2 (en) * | 2008-06-20 | 2012-04-24 | Micro Graphic Information Services Corp. | Automated invoice processing software and services |
US8447669B2 (en) | 2008-08-26 | 2013-05-21 | Visa U.S.A. Inc. | System and method for implementing financial assistance programs |
US8422758B1 (en) | 2008-09-02 | 2013-04-16 | United Services Automobile Association (Usaa) | Systems and methods of check re-presentment deterrent |
US10504185B1 (en) | 2008-09-08 | 2019-12-10 | United Services Automobile Association (Usaa) | Systems and methods for live video financial deposit |
US20100082467A1 (en) * | 2008-09-26 | 2010-04-01 | Mark Carlson | Phone and method of using the phone for beneficiary initiated payments |
US7885880B1 (en) | 2008-09-30 | 2011-02-08 | United Services Automobile Association (Usaa) | Atomic deposit transaction |
US7974899B1 (en) | 2008-09-30 | 2011-07-05 | United Services Automobile Association (Usaa) | Atomic deposit transaction |
US8275710B1 (en) | 2008-09-30 | 2012-09-25 | United Services Automobile Association (Usaa) | Systems and methods for automatic bill pay enrollment |
US7962411B1 (en) | 2008-09-30 | 2011-06-14 | United Services Automobile Association (Usaa) | Atomic deposit transaction |
US20100306080A1 (en) * | 2008-10-08 | 2010-12-02 | Trandal David S | Methods and systems for receipt management and price comparison |
US7792709B1 (en) | 2008-10-08 | 2010-09-07 | Trandal David S | Methods and systems for receipt management and price comparison |
US8391599B1 (en) | 2008-10-17 | 2013-03-05 | United Services Automobile Association (Usaa) | Systems and methods for adaptive binarization of an image |
US20100106646A1 (en) * | 2008-10-23 | 2010-04-29 | Passeri Stacy M | System and method for asset identification, evaluation, and control |
US7970677B1 (en) | 2008-10-24 | 2011-06-28 | United Services Automobile Association (Usaa) | Systems and methods for financial deposits by electronic message |
US7949587B1 (en) | 2008-10-24 | 2011-05-24 | United States Automobile Association (USAA) | Systems and methods for financial deposits by electronic message |
US8452689B1 (en) | 2009-02-18 | 2013-05-28 | United Services Automobile Association (Usaa) | Systems and methods of check detection |
US10956728B1 (en) | 2009-03-04 | 2021-03-23 | United Services Automobile Association (Usaa) | Systems and methods of check processing with background removal |
US8146805B1 (en) | 2009-04-22 | 2012-04-03 | United Services Automobile Association (Usaa) | Systems and methods for depositing cash into deposit account |
US8295452B1 (en) | 2009-06-17 | 2012-10-23 | Trandal David S | Methods and systems for processing telephonic communications and product data |
US8542921B1 (en) | 2009-07-27 | 2013-09-24 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of negotiable instrument using brightness correction |
US9779392B1 (en) | 2009-08-19 | 2017-10-03 | United Services Automobile Association (Usaa) | Apparatuses, methods and systems for a publishing and subscribing platform of depositing negotiable instruments |
US8977571B1 (en) | 2009-08-21 | 2015-03-10 | United Services Automobile Association (Usaa) | Systems and methods for image monitoring of check during mobile deposit |
US8699779B1 (en) | 2009-08-28 | 2014-04-15 | United Services Automobile Association (Usaa) | Systems and methods for alignment of check during mobile deposit |
CN102597060B (en) * | 2009-09-02 | 2014-05-07 | 纳幕尔杜邦公司 | Polyaramid comprising fluorovinylether functionalized aromatic moieties |
JP2011060649A (en) * | 2009-09-11 | 2011-03-24 | Toyota Motor Corp | Electrode active material layer, all solid battery, manufacturing method for electrode active material layer, and manufacturing method for all solid battery |
WO2011133958A2 (en) * | 2010-04-22 | 2011-10-27 | Cashedge, Inc. | Inter-network invoice and payment method and system |
US9129340B1 (en) | 2010-06-08 | 2015-09-08 | United Services Automobile Association (Usaa) | Apparatuses, methods and systems for remote deposit capture with enhanced image detection |
WO2012027694A2 (en) * | 2010-08-27 | 2012-03-01 | Visa International Service Association | Account number based bill payment platform apparatuses, methods and systems |
KR20120040880A (en) * | 2010-10-20 | 2012-04-30 | 삼성전자주식회사 | Device and method for controlling giro charge payment in wireless terminal |
US20120209677A1 (en) | 2010-10-20 | 2012-08-16 | Mehta Kaushal N | Person-2-person social network marketing apparatuses, methods and systems |
CN102041945B (en) * | 2010-11-24 | 2013-04-03 | 苏州先施科技有限公司 | Method for improving safety and monitoring efficiency of financial warehouse |
US20120158583A1 (en) * | 2010-12-21 | 2012-06-21 | Harald Evers | Automated bank transfers using identifier tokens |
WO2012106655A2 (en) | 2011-02-05 | 2012-08-09 | Visa International Service Association | Merchant-consumer bridging platform apparatuses, methods and systems |
US9953334B2 (en) | 2011-02-10 | 2018-04-24 | Visa International Service Association | Electronic coupon issuance and redemption apparatuses, methods and systems |
BR112013021059A2 (en) | 2011-02-16 | 2020-10-27 | Visa International Service Association | Snap mobile payment systems, methods and devices |
US10586227B2 (en) | 2011-02-16 | 2020-03-10 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
AU2012220669A1 (en) | 2011-02-22 | 2013-05-02 | Visa International Service Association | Universal electronic payment apparatuses, methods and systems |
AU2012223415B2 (en) | 2011-02-28 | 2017-05-18 | Visa International Service Association | Secure anonymous transaction apparatuses, methods and systems |
WO2012122060A1 (en) | 2011-03-04 | 2012-09-13 | Visa International Service Association | Cloud service facilitator apparatuses, methods and systems |
US10592792B2 (en) | 2011-04-14 | 2020-03-17 | Handle Financial, Inc. | Systems and methods for barcode translation |
US9547861B2 (en) | 2011-05-11 | 2017-01-17 | Mark Itwaru | System and method for wireless communication with an IC chip for submission of pin data |
US10223674B2 (en) | 2011-05-11 | 2019-03-05 | Riavera Corp. | Customized transaction flow for multiple transaction types using encoded image representation of transaction information |
US9715704B2 (en) * | 2011-05-11 | 2017-07-25 | Riavera Corp | Merchant ordering system using optical machine readable image representation of invoice information |
WO2012155081A1 (en) | 2011-05-11 | 2012-11-15 | Visa International Service Association | Electronic receipt manager apparatuses, methods and systems |
US9785935B2 (en) | 2011-05-11 | 2017-10-10 | Riavera Corp. | Split mobile payment system |
US9721243B2 (en) | 2011-05-11 | 2017-08-01 | Riavera Corp. | Mobile payment system using subaccounts of account holder |
MX2013013166A (en) | 2011-05-11 | 2014-09-01 | Mark Itwaru | Split mobile payment system. |
US8616453B2 (en) | 2012-02-15 | 2013-12-31 | Mark Itwaru | System and method for processing funds transfer between entities based on received optical machine readable image information |
US9734498B2 (en) | 2011-05-11 | 2017-08-15 | Riavera Corp | Mobile image payment system using short codes |
CN103797500A (en) | 2011-06-03 | 2014-05-14 | 维萨国际服务协会 | Virtual wallet card selection apparatuses, methods and systems |
WO2013006725A2 (en) | 2011-07-05 | 2013-01-10 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
US9582598B2 (en) | 2011-07-05 | 2017-02-28 | Visa International Service Association | Hybrid applications utilizing distributed models and views apparatuses, methods and systems |
US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US10438176B2 (en) | 2011-07-17 | 2019-10-08 | Visa International Service Association | Multiple merchant payment processor platform apparatuses, methods and systems |
US10242358B2 (en) | 2011-08-18 | 2019-03-26 | Visa International Service Association | Remote decoupled application persistent state apparatuses, methods and systems |
US10825001B2 (en) | 2011-08-18 | 2020-11-03 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US9710807B2 (en) | 2011-08-18 | 2017-07-18 | Visa International Service Association | Third-party value added wallet features and interfaces apparatuses, methods and systems |
US10318941B2 (en) | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
US9117225B2 (en) | 2011-09-16 | 2015-08-25 | Visa International Service Association | Apparatuses, methods and systems for transforming user infrastructure requests inputs to infrastructure design product and infrastructure allocation outputs |
US10223730B2 (en) | 2011-09-23 | 2019-03-05 | Visa International Service Association | E-wallet store injection search apparatuses, methods and systems |
SE1200088A1 (en) | 2012-02-10 | 2013-08-11 | Seamless Distrib Ab | Procedure and systems |
US20140344127A1 (en) * | 2011-10-21 | 2014-11-20 | Daniel B. Thomas | Network-based electronic invoicing system with reverse invoicing |
GB201119375D0 (en) | 2011-11-10 | 2011-12-21 | Merburn Ltd | Financial transaction processing system and method |
US9953378B2 (en) | 2012-04-27 | 2018-04-24 | Visa International Service Association | Social checkout widget generation and integration apparatuses, methods and systems |
WO2013090611A2 (en) | 2011-12-13 | 2013-06-20 | Visa International Service Association | Dynamic widget generator apparatuses, methods and systems |
US10223710B2 (en) | 2013-01-04 | 2019-03-05 | Visa International Service Association | Wearable intelligent vision device apparatuses, methods and systems |
US10380565B1 (en) | 2012-01-05 | 2019-08-13 | United Services Automobile Association (Usaa) | System and method for storefront bank deposits |
US11308227B2 (en) | 2012-01-09 | 2022-04-19 | Visa International Service Association | Secure dynamic page content and layouts apparatuses, methods and systems |
US10262148B2 (en) | 2012-01-09 | 2019-04-16 | Visa International Service Association | Secure dynamic page content and layouts apparatuses, methods and systems |
AU2013214801B2 (en) | 2012-02-02 | 2018-06-21 | Visa International Service Association | Multi-source, multi-dimensional, cross-entity, multimedia database platform apparatuses, methods and systems |
US8819789B2 (en) | 2012-03-07 | 2014-08-26 | Bill.Com, Inc. | Method and system for using social networks to verify entity affiliations and identities |
US9747600B2 (en) * | 2012-03-30 | 2017-08-29 | United State Poastal Service | Item status tracking |
US8608053B2 (en) * | 2012-04-30 | 2013-12-17 | Honeywell International Inc. | Mobile communication terminal configured to display multi-symbol decodable indicia |
US9626701B2 (en) * | 2012-05-23 | 2017-04-18 | Paynearme, Inc. | System and method for facilitating cash payment transactions using a mobile device |
US9053312B2 (en) | 2012-06-19 | 2015-06-09 | Paychief, Llc | Methods and systems for providing bidirectional authentication |
US9342611B2 (en) | 2012-06-22 | 2016-05-17 | Paychief Llc | Systems and methods for transferring personal data using a symbology |
US8919640B2 (en) | 2012-06-22 | 2014-12-30 | Paychief Llc | Methods and systems for registering relationships between users via a symbology |
US8997184B2 (en) | 2012-06-22 | 2015-03-31 | Paychief Llc | Systems and methods for providing a one-time authorization |
US9087330B2 (en) | 2012-09-14 | 2015-07-21 | Bank Of America Corporation | Geography based transaction cost recovery |
US9691060B2 (en) | 2012-10-15 | 2017-06-27 | Bank Of America Corporation | Low value based acceptance cost recovery |
US9576282B2 (en) | 2012-10-15 | 2017-02-21 | Bank Of America Corporation | Merchant category code (“MCC”) based acceptance cost recovery |
US8905295B2 (en) * | 2012-11-15 | 2014-12-09 | Pierre Serhal | Method and apparatus for adding value to a stored value account |
US10467612B2 (en) | 2012-11-19 | 2019-11-05 | Bank Of America Corporation | Volume based transaction cost recovery |
US9818266B2 (en) | 2012-12-05 | 2017-11-14 | Bank Of America Corporation | Remote disabling of target point-of-sale (“POS”) terminals |
US8972293B2 (en) | 2012-12-05 | 2015-03-03 | Bank Of America Corporation | Surcharge auditing |
US11138525B2 (en) | 2012-12-10 | 2021-10-05 | Trading Technologies International, Inc. | Distribution of market data based on price level transitions |
US8706554B1 (en) | 2012-12-17 | 2014-04-22 | Bank Of America Corporation | Transaction cost recovery inventory management |
US8712855B1 (en) * | 2012-12-17 | 2014-04-29 | Bank Of America Corporation | Transaction cost recovery queue management |
US10552810B1 (en) | 2012-12-19 | 2020-02-04 | United Services Automobile Association (Usaa) | System and method for remote deposit of financial instruments |
US9262756B2 (en) | 2013-01-01 | 2016-02-16 | Bank Of America Corporation | Point-of-sale (“POS”) controller |
CN103971447B (en) * | 2013-02-04 | 2017-11-14 | 山东新北洋信息技术股份有限公司 | Paper money identifier and its processing method and bill handling state recording method |
US10417674B2 (en) | 2013-03-14 | 2019-09-17 | Bill.Com, Llc | System and method for sharing transaction information by object tracking of inter-entity transactions and news streams |
US10115137B2 (en) | 2013-03-14 | 2018-10-30 | Bill.Com, Inc. | System and method for enhanced access and control for connecting entities and effecting payments in a commercially oriented entity network |
US20150012442A1 (en) | 2013-03-14 | 2015-01-08 | Bill.Com, Inc. | Enhanced system and method for scanning and processing of payment documentation |
US20140279466A1 (en) * | 2013-03-15 | 2014-09-18 | Paynearme, Inc. | Cash-Based Check System |
US20140279323A1 (en) * | 2013-03-15 | 2014-09-18 | Mitek Systems, Inc. | Systems and methods for capturing critical fields from a mobile image of a credit card bill |
US10572921B2 (en) | 2013-07-03 | 2020-02-25 | Bill.Com, Llc | System and method for enhanced access and control for connecting entities and effecting payments in a commercially oriented entity network |
US10664548B2 (en) | 2013-07-12 | 2020-05-26 | Trading Technologies International, Inc. | Tailored messaging |
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US11138578B1 (en) | 2013-09-09 | 2021-10-05 | United Services Automobile Association (Usaa) | Systems and methods for remote deposit of currency |
FR3011366B1 (en) * | 2013-09-27 | 2020-09-25 | Compagnie Ind Et Financiere Dingenierie Ingenico | TRANSACTIONAL DATA PROCESSING METHOD, TERMINAL, SERVER AND CORRESPONDING COMPUTER PROGRAMS. |
US9286514B1 (en) | 2013-10-17 | 2016-03-15 | United Services Automobile Association (Usaa) | Character count determination for a digital image |
US20150134517A1 (en) * | 2013-11-08 | 2015-05-14 | Brian Cosgray | System and Method for Payment of Bills From Periodic Income Sources |
US10163148B1 (en) | 2013-11-13 | 2018-12-25 | Square, Inc. | Wireless beacon shopping experience |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US10192407B2 (en) | 2014-01-10 | 2019-01-29 | Handle Financial, Inc. | Systems and methods for cash payments for online gaming |
US9223991B2 (en) * | 2014-03-17 | 2015-12-29 | Saudi Arabian Oil Company | Systems, methods, and computer medium to securely transfer large volumes of data between physically isolated networks having different levels of network protection |
KR20150109640A (en) * | 2014-03-20 | 2015-10-02 | 삼성전자주식회사 | Method and apparatus for making goods in electronic device |
US11507931B1 (en) | 2014-07-31 | 2022-11-22 | Block, Inc. | Payout payment platform |
CN104112224A (en) * | 2014-08-11 | 2014-10-22 | 税友软件集团股份有限公司 | Method, device and system for generating electronic invoice assigned code based on enterprise tax number |
US9990613B1 (en) | 2014-12-12 | 2018-06-05 | Square, Inc. | Bill payment using direct funds transfer |
US11216468B2 (en) | 2015-02-08 | 2022-01-04 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
US10743149B2 (en) * | 2015-03-31 | 2020-08-11 | Energycomnetwork, Inc. | Systems and methods for checkout line utility payments |
US9679431B2 (en) | 2015-04-15 | 2017-06-13 | Bank Of America Corporation | Detecting duplicate deposit items at point of capture |
US10402790B1 (en) | 2015-05-28 | 2019-09-03 | United Services Automobile Association (Usaa) | Composing a focused document image from multiple image captures or portions of multiple image captures |
US11488122B2 (en) * | 2015-06-11 | 2022-11-01 | Antony J. H. Diamond | System and method for electronically transferring money |
CN105205706A (en) * | 2015-09-01 | 2015-12-30 | 深圳市金蝶友商电子商务服务有限公司 | Invoice query method and device |
US10387881B2 (en) | 2015-10-02 | 2019-08-20 | Chicago Mercantile Exchange Inc. | Virtual payment processing system |
US10380589B2 (en) | 2015-10-02 | 2019-08-13 | Chicago Mercantile Exchange Inc. | Virtual payment processing system |
MX2018004496A (en) | 2015-10-12 | 2018-11-09 | Walmart Apollo Llc | Check-in to checkout systems and methods. |
US10796348B2 (en) * | 2016-04-22 | 2020-10-06 | International Business Machines Corporation | Data resiliency of billing information |
US10445571B1 (en) * | 2016-09-01 | 2019-10-15 | United Services Automobile Association | Document data capture |
US9886689B1 (en) | 2016-09-12 | 2018-02-06 | Square, Inc. | Processing a mobile payload |
USD837227S1 (en) | 2016-09-12 | 2019-01-01 | Square, Inc. | Display screen with graphical user interface for a mobile device |
US11625785B2 (en) | 2017-06-05 | 2023-04-11 | Chicago Mercantile Exchange Inc. | Secure electronic tokens in an electronic tokening system |
US20190095899A1 (en) * | 2017-09-26 | 2019-03-28 | American Express Travel Related Services Company, Inc. | Segmenting multiple repayment schemes |
FR3074946B1 (en) * | 2017-12-11 | 2021-08-27 | Oney Bank | ELECTRONIC TRANSACTION METHODS AND SYSTEMS |
US11836709B2 (en) | 2017-12-22 | 2023-12-05 | Walmart Apollo, Llc | Digital wallet management system |
US11030752B1 (en) | 2018-04-27 | 2021-06-08 | United Services Automobile Association (Usaa) | System, computing device, and method for document detection |
US20190385241A1 (en) * | 2018-06-18 | 2019-12-19 | Adp, Llc | Bill payment mechanism for payroll deduction |
US11521186B2 (en) | 2018-08-21 | 2022-12-06 | The Toronto-Dominion Bank | Recipient management in computer network initiated data transfers |
US11265324B2 (en) | 2018-09-05 | 2022-03-01 | Consumerinfo.Com, Inc. | User permissions for access to secure data at third-party |
CN109685551A (en) * | 2018-12-05 | 2019-04-26 | 深圳正品创想科技有限公司 | Information processing method and its device, server and information processing system |
US10650369B1 (en) | 2019-03-07 | 2020-05-12 | Capital One Services, Llc | Systems and methods for managing transactions by consolidating associated transactions |
US11392924B2 (en) * | 2019-09-11 | 2022-07-19 | Ebay Inc. | In-person transaction processing system |
US11410194B1 (en) * | 2019-10-18 | 2022-08-09 | Wells Fargo Bank, N.A. | Systems and methods for linking ATM to retailer transaction to preserve anonymity |
US11580339B2 (en) * | 2019-11-13 | 2023-02-14 | Oracle International Corporation | Artificial intelligence based fraud detection system |
US11900755B1 (en) | 2020-11-30 | 2024-02-13 | United Services Automobile Association (Usaa) | System, computing device, and method for document detection and deposit processing |
GB2604116A (en) * | 2021-02-24 | 2022-08-31 | Vocalink Ltd | An apparatus, method and computer program product for identifying a validation check for a set of numbers |
US11941684B2 (en) * | 2021-04-26 | 2024-03-26 | Bolt Financial, Inc. | Method and system for embedded one-click checkout |
CN113554029B (en) * | 2021-09-17 | 2022-03-11 | 北京奇虎科技有限公司 | Bill verification method, device, equipment and storage medium |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4982071A (en) * | 1987-08-26 | 1991-01-01 | Hitachi, Ltd. | Information recording card and charge making/paying system employing the same |
WO1996008797A1 (en) * | 1994-09-12 | 1996-03-21 | Lottery Enterprises, Inc. | Bill pay system and method |
WO1997008643A1 (en) * | 1995-08-31 | 1997-03-06 | Visa International Service Association | Electronic bill pay system |
DE19701697A1 (en) * | 1997-01-20 | 1998-07-23 | Werner Debold | Automatic account settlement system using credit cards |
Family Cites Families (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3812328A (en) * | 1972-05-31 | 1974-05-21 | Pitney Bowes Inc | Credit card |
US5053607A (en) * | 1986-10-06 | 1991-10-01 | Carlson Steven R | Point-of-sale device particularly adapted for processing checks |
US5121945A (en) | 1988-04-20 | 1992-06-16 | Remittance Technology Corporation | Financial data processing system |
US5992752A (en) * | 1993-11-24 | 1999-11-30 | Metrologic Instruments, Inc. | Internet-based system for enabling information-related transactions over the internet using Java-enabled internet terminals provided with bar code symbol readers for reading Java-Applet encoded bar code symbols |
US5317135A (en) * | 1991-05-24 | 1994-05-31 | Richard Finocchio | Method and apparatus for validating instant-win lottery tickets |
US6289322B1 (en) * | 1998-03-03 | 2001-09-11 | Checkfree Corporation | Electronic bill processing |
US5640835A (en) * | 1991-10-16 | 1997-06-24 | Muscoplat; Richard | Multiple envelope with integrally formed and printed contents and return envelope |
US5306899A (en) * | 1992-06-12 | 1994-04-26 | Symbol Technologies, Inc. | Authentication system for an item having a holographic display using a holographic record |
US5326959A (en) | 1992-08-04 | 1994-07-05 | Perazza Justin J | Automated customer initiated entry remittance processing system |
US5324922A (en) | 1993-02-25 | 1994-06-28 | Verifone, Inc. | Apparatus and method for managing transactions |
US5450491A (en) * | 1993-08-26 | 1995-09-12 | At&T Corp. | Authenticator card and system |
US5465206B1 (en) | 1993-11-01 | 1998-04-21 | Visa Int Service Ass | Electronic bill pay system |
US5920847A (en) * | 1993-11-01 | 1999-07-06 | Visa International Service Association | Electronic bill pay system |
US6321986B1 (en) * | 1993-11-05 | 2001-11-27 | Intermec Ip Corporation | Robust machine-readable symbology and method and apparatus for printing and reading same |
JPH07160951A (en) * | 1993-12-08 | 1995-06-23 | Fujitsu Ltd | Terminal equipment having print and read function of high density bar code |
US5602377A (en) * | 1995-03-01 | 1997-02-11 | Metanetics Corporation | Bar code dataform scanning and labeling apparatus and method |
US5978773A (en) * | 1995-06-20 | 1999-11-02 | Neomedia Technologies, Inc. | System and method for using an ordinary article of commerce to access a remote computer |
US5596501A (en) * | 1995-07-19 | 1997-01-21 | Powerplant Fuel Modules, Llc | System for dispensing fuel at remote locations, and method of operating same |
US5640002A (en) * | 1995-08-15 | 1997-06-17 | Ruppert; Jonathan Paul | Portable RF ID tag and barcode reader |
US6056199A (en) * | 1995-09-25 | 2000-05-02 | Intermec Ip Corporation | Method and apparatus for storing and reading data |
US20020023055A1 (en) * | 1996-03-01 | 2002-02-21 | Antognini Walter Gerard | System and method for digital bill presentment and payment |
CA2170834C (en) * | 1996-03-01 | 2006-11-21 | Calin A. Sandru | Apparatus and method for enhancing the security of negotiable documents |
US5761686A (en) * | 1996-06-27 | 1998-06-02 | Xerox Corporation | Embedding encoded information in an iconic version of a text image |
US5930767A (en) | 1997-05-28 | 1999-07-27 | Motorola, Inc. | Transaction methods systems and devices |
US5978772A (en) * | 1996-10-11 | 1999-11-02 | Mold; Jeffrey W. | Merchandise checkout system |
US6070150A (en) * | 1996-10-18 | 2000-05-30 | Microsoft Corporation | Electronic bill presentment and payment system |
US6070798A (en) | 1997-02-21 | 2000-06-06 | Nethery; Kee | Purchaser generated transaction recording and negotiable instrument payment system |
US6036086A (en) * | 1997-03-28 | 2000-03-14 | Lucent Technologies Inc. | Apparatus and method for initiating a telephone transaction using a scanner |
US5969324A (en) * | 1997-04-10 | 1999-10-19 | Motorola, Inc. | Accounting methods and systems using transaction information associated with a nonpredictable bar code |
US6097834A (en) | 1997-06-13 | 2000-08-01 | Paystation America Inc. | Financial transaction processing systems and methods |
US5978780A (en) * | 1997-11-21 | 1999-11-02 | Craig Michael Watson | Integrated bill consolidation, payment aggregation, and settlement system |
US6334116B1 (en) * | 1998-02-02 | 2001-12-25 | Checkfree Corporation | Technique for centrally tracking transactions in an electronic billing system |
US6173272B1 (en) * | 1998-04-27 | 2001-01-09 | The Clearing House Service Company L.L.C. | Electronic funds transfer method and system and bill presentment method and system |
US6032195A (en) | 1998-07-31 | 2000-02-29 | Motorola, Inc. | Method, system, and article for navigating an electronic network and performing a task using a destination-specific software agent |
US6438322B1 (en) * | 1998-11-16 | 2002-08-20 | Kenneth H. Reiker | Ceiling fan with attached heater and secondary fan |
JP2000251012A (en) * | 1999-03-01 | 2000-09-14 | Hitachi Ltd | Method and system for document processing |
AU4350699A (en) * | 1999-08-11 | 2001-02-15 | Khai Hee Kwan | Method, apparatus and program to make payment in any currencies through a communication network system |
US20030023553A1 (en) * | 2000-01-31 | 2003-01-30 | Perot Systems Corporation | Remote self-servicing management of invoicing for billing parties |
JP2004501420A (en) * | 2000-03-29 | 2004-01-15 | マスターカード インターナショナル インコーポレイテツド | A method and system for processing messages in a bill payment and presentation system across a communication network. |
US6676016B1 (en) * | 2000-05-04 | 2004-01-13 | Ncr Corporation | Retail terminal configured as consumer gateway to electronic billing application |
JP3527211B2 (en) * | 2000-08-01 | 2004-05-17 | 日立マクセル株式会社 | Electronic coupon system |
US7523067B1 (en) * | 2000-08-02 | 2009-04-21 | Softbankbb Corporation | Electronic settlement system, settlement apparatus, and terminal |
JP2002117360A (en) * | 2000-10-11 | 2002-04-19 | Sharp Corp | Payment system, method for account settlement, ordering device, and information providing device |
US7203158B2 (en) * | 2000-12-06 | 2007-04-10 | Matsushita Electric Industrial Co., Ltd. | OFDM signal transmission system, portable terminal, and e-commerce system |
US6993507B2 (en) * | 2000-12-14 | 2006-01-31 | Pacific Payment Systems, Inc. | Bar coded bill payment system and method |
US7044362B2 (en) * | 2001-10-10 | 2006-05-16 | Hewlett-Packard Development Company, L.P. | Electronic ticketing system and method |
US20050187872A1 (en) * | 2002-09-06 | 2005-08-25 | Mike Schmidt | Interactive electronic bill payment system |
US20090108080A1 (en) * | 2007-10-31 | 2009-04-30 | Payscan America, Inc. | Bar coded monetary transaction system and method |
-
2000
- 2000-12-14 US US09/737,011 patent/US6993507B2/en not_active Expired - Fee Related
-
2001
- 2001-12-14 US US10/020,691 patent/US20020128967A1/en not_active Abandoned
- 2001-12-14 EP EP01988313A patent/EP1342146A4/en not_active Withdrawn
- 2001-12-14 WO PCT/US2001/048442 patent/WO2002048835A2/en not_active Application Discontinuation
- 2001-12-14 MX MXPA03005301A patent/MXPA03005301A/en unknown
- 2001-12-14 CA CA002432750A patent/CA2432750A1/en not_active Abandoned
-
2009
- 2009-02-13 US US12/371,547 patent/US20090204522A1/en not_active Abandoned
-
2014
- 2014-05-12 US US14/275,726 patent/US20140310167A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4982071A (en) * | 1987-08-26 | 1991-01-01 | Hitachi, Ltd. | Information recording card and charge making/paying system employing the same |
WO1996008797A1 (en) * | 1994-09-12 | 1996-03-21 | Lottery Enterprises, Inc. | Bill pay system and method |
WO1997008643A1 (en) * | 1995-08-31 | 1997-03-06 | Visa International Service Association | Electronic bill pay system |
DE19701697A1 (en) * | 1997-01-20 | 1998-07-23 | Werner Debold | Automatic account settlement system using credit cards |
Non-Patent Citations (1)
Title |
---|
See also references of WO0248835A2 * |
Also Published As
Publication number | Publication date |
---|---|
MXPA03005301A (en) | 2005-06-20 |
US20020128967A1 (en) | 2002-09-12 |
WO2002048835A3 (en) | 2003-03-13 |
US20140310167A1 (en) | 2014-10-16 |
EP1342146A4 (en) | 2009-11-18 |
WO2002048835A2 (en) | 2002-06-20 |
US20020077976A1 (en) | 2002-06-20 |
US20090204522A1 (en) | 2009-08-13 |
US6993507B2 (en) | 2006-01-31 |
CA2432750A1 (en) | 2002-06-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20140310167A1 (en) | Bar coded bill payment system and method | |
US20140236817A1 (en) | Bar coded monetary transaction system and method | |
US20150287005A1 (en) | Bar coded monetary transaction system and method | |
AU2009200162B2 (en) | Method and system for completing a transaction between a customer and a merchant | |
US6678664B1 (en) | Cashless transactions without credit cards, debit cards or checks | |
US7890393B2 (en) | Method and system for completing a transaction between a customer and a merchant | |
AU2001252496B2 (en) | Method and apparatus for managing remittance processing within account receivables | |
EP1049056A2 (en) | Electronic bill presentment and/or payment clearinghouse | |
US20070106558A1 (en) | System and method of automatic insufficient funds notification and overdraft protection | |
US20100205063A1 (en) | Electronic payment transaction system | |
US20020103756A1 (en) | Business method for implementing on-line check acceptance and processing | |
WO2007025110A2 (en) | System and method for consumer opt-out of payment conversions | |
US20060080240A1 (en) | Electronic payment transaction system | |
AU2002247093B8 (en) | Method and system for completing a transaction between a customer and a merchant | |
WO2001008068A9 (en) | System, device, and method for coordinating and facilitating commercial transactions | |
AU2002247093A1 (en) | Method and system for completing a transaction between a customer and a merchant | |
CN1703707A (en) | Aggregated postal billing and payment methods and systems |
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: 20030611 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK RO SI |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: PACIFIC PAYMENT SYSTEMS, INC |
|
DIN1 | Information on inventor provided before grant (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: PACIFIC PAYMENT SYSTEMS, INC. Owner name: MEYER, JOHN |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20091020 |
|
17Q | First examination report despatched |
Effective date: 20100616 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20100701 |