# US 2009/0276322 A1 · Retailer debit card system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0276322 A1
- Document ID: US20090276322A1
- Status: Published application
- Kind: A1
- Application number: 12/501,930
- Filed: 2009-07-13
- Published: 2009-11-05
- Earliest claimed: 2007-02-14
- Assignees: Target Brands, Inc.
- Inventors: Catherine Michelle Sunde; Michele Lynn Gaida; Timothy Michael Bardell; Robert Joseph Meissner; Brent Allan Pier; Brian James Short-Ohana
- Web page: https://patentgrep.com/patent/US20090276322A1

## CPC

- G06Q 30/0253: {During e-commerce, i.e. online transactions}
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- G06Q 40/03: Credit; Loans; Processing thereof
- G06Q 40/12: Accounting
- 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

## Abstract

Methods for soliciting and enrolling customers for a retailer payment instrument are disclosed. For example, a method is disclosed for enrolling a customer for a retailer debit card which includes receiving enrollment data from the customer, establishing a check writer rating for the customer based on a history of checks associated with the customer and stored by the retailer, adjusting a validation threshold score based on the check writer rating, and denying enrollment of the customer if the validation score is less than the adjusted validation threshold score. Other associated methods and systems are also disclosed.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A retailer debit card system adapted for use with at least one retail store operated by a retail corporation, the system comprising:
at least one checkout lane with a point-of-sale (POS) device in the at least one retail store, wherein the POS device is configured to scan a magnetic ink character recognition (MICR) line from a check presented by a customer for purchasing one or more items from the at least one retail store during a purchase transaction, and the MICR line includes a demand deposit account (DDA) number and a routing number associated with the check; and
a central computing network in communication with the POS device, the central computing network including:
a comprehensive negative check file maintained by the retail corporation and comprising an internal negative check file and an external negative check file, wherein the internal negative check file includes at least a list of outstanding checks to the retail corporation which are unpaid due to non-sufficient funds, and the external negative check file includes a copy of a file compiled by a third party check authorization service, and
a solicitation module configured to determine whether to solicit the customer to apply for a retailer debit card offered by the retail corporation based in part on the comprehensive negative check file, wherein the solicitation module is configured to compare the MICR line scanned by the POS device to the comprehensive negative check file, wherein:
when the DDA number and the routing number of the MICR line scanned by the POS device match a DDA number and a routing number of a MICR line of a check in the comprehensive negative check file, the solicitation module is configured to determine not to solicit the customer to apply for the retailer debit card, and
when the DDA number and the routing number of the MICR line scanned by the POS device fail to match a DDA number and a routing number of a MICR line of a check in the comprehensive negative check file, the solicitation module is configured to determine that the solicitation module will continue considering whether to solicit the customer to apply for the retailer debit card based on other considerations.

### Claim 22 (depends on 21)

The retailer debit card system of claim 21, wherein the central computing network further comprises a messaging module configured to issue a solicitation message to the POS device providing a retail employee operating the POS device with instructions to complete the purchase transaction with the customer based on a determination, previously made by the solicitation module, whether to solicit the customer to apply for the retailer debit card.

### Claim 23 (depends on 22)

The retailer debit card system of claim 22, wherein when the solicitation module determines not to solicit the customer to apply for the retailer debit card, the messaging module is configured to send the solicitation message to the POS device instructing the retail employee to complete the purchase transaction using the check presented by the customer, wherein the solicitation message is free from any instructions to offer the customer an opportunity to apply for the retailer debit card.

### Claim 24 (depends on 23)

The retailer debit card system of claim 23, wherein when the solicitation module determines the customer should be solicited to apply for the retailer debit card, the message module is configured to send the solicitation message to the POS device instructing the retail employee to solicit the customer to apply for the retail debit card prior to completing the purchase transaction.

### Claim 25 (depends on 24)

The retailer debit card system of claim 24, wherein if the customer accepts the solicitation and is enrolled for the retail debit card, the POS device is configured to enable the customer to fund the retail debit card and to use the retail debit card to pay for the one or more items being purchased by the customer during the purchase transaction.

### Claim 26 (depends on 21)

The retailer debit card system of claim 21, wherein the solicitation module is configured to determine the customer should not be solicited to apply for the retail debit card when the DDA number and the routing number of the MICR line scanned from the check match a DDA number and a routing number of the MICR line of a check in the internal negative check file.

### Claim 27 (depends on 21)

The retailer debit card system of claim 21, wherein the central computing network includes:
an internal electronic payment delivery (EPD) system file maintained by the retail corporation and comprising a list of financial institutions participating in an EPD system associated with the retail corporation, each financial institution having a corresponding routing number;
wherein the solicitation module is configured to compare the routing number from the scanned MICR line to the internal EPD system file and to determine the customer should not be solicited to apply for the retail debit card when the routing number of the scanned MICR line is not listed in the internal EPD system file.

### Claim 28 (depends on 27)

The retailer debit card system of claim 27, wherein the EPD system comprises the automated clearing house system.

### Claim 29 (depends on 21)

The retailer debit card system of claim 21, wherein the central computing network includes a list of MICR lines from checks previously discovered by the retail corporation to be associated with non-viable DDAs, wherein the solicitation module is configured to determine not to solicit the customer to apply for the retail debit account when the DDA number and routing number of the scanned MICR line match an account number and a routing number of a MICR line of one of the non-viable DDAs.

### Claim 30 (depends on 21)

The retailer debit card system of claim 21, wherein the central computing network includes an account database having a list of credit and debit accounts associated with the retail corporation, wherein the solicitation module, based on the MICR line scanned by the POS device, is configured to access the account database to determine whether the customer has an existing debit account associated with the retail corporation, and is configured to determine the customer should not be solicited to apply for the retail debit card when the customer has an existing debit account associated with the retail corporation.

### Claim 31 (depends on 21)

The retailer debit card system of claim 21, wherein the solicitation module is configured to access the account database to determine whether the customer has an existing credit account associated with the retail corporation, and is configured to determine that the customer should not be solicited to apply for the retail debit card when the customer has an existing credit account associated with the retail corporation.

### Claim 32 (depends on 21)

The retailer debit card system of claim 21, wherein the central computing network includes:
an internal electronic payment delivery (EPD) system file maintained by the retail corporation and comprising a list of financial institutions participating in an EPD system associated with the retail corporation, each financial institution having a corresponding routing number; wherein the solicitation module is configured to compare the routing number from the scanned MICR line to the internal EPD system file and to determine the customer should not be solicited to apply for the retail debit card when the routing number of the scanned MICR line is not listed in the internal EPD system file, and
a list of MICR lines from checks previously discovered by the retail corporation to be associated with non-viable DDAs, wherein the solicitation module is configured to determine not to solicit the customer to apply for the retail debit account when the DDA number and routing number of the scanned MICR line match an account number and a routing number of a MICR line of one of the non-viable DDAs.

### Claim 33 (depends on 32)

The retailer debit card system of claim 32, wherein the central computing network includes an account database having a list of credit and debit accounts associated with the retail corporation, wherein the solicitation module, based on the MICR line scanned by the POS device, is configured to access the account database to determine whether the customer has an existing debit account associated with the retail corporation, and is configured to determine the customer should not be solicited to apply for the retail debit card when the customer has an existing debit account associated with the retail corporation.

### Claim 34

A method of processing a purchase transaction for one or more items using a retailer debit card system, the method comprising:
accepting a check with a magnetic ink character recognition (MICR) line from a customer at a checkout lane with a point-of-sale (POS) device in a retail store operated by a retail corporation, wherein the POS device is in communication with a central computing network including a comprehensive negative check file and a solicitation module, the comprehensive negative check file is maintained by the retail corporation and comprises an internal negative check file and an external negative check file, the internal negative check file includes at least a list of outstanding checks to the retail corporation which are unpaid due to non-sufficient funds, and the external negative check file includes a copy of a file compiled by a third party check authorization service;
scanning the MICR line of the check with the POS device, the MICR line including a demand deposit account (DDA) number and a routing number associated with the check; and
using the solicitation module to determine whether to solicit the customer to apply for a retail debit card including:
determining if any of a plurality of predefined reasons exist not to solicit the customer to apply for the retail debit card, wherein one of the plurality of predefined reasons includes if the MICR line scanned by the POS device matches an MICR line of a check listed in the comprehensive negative check file,
if any of the plurality of predefined reasons exist, deciding not to solicit the customer to apply for the retail debit card, and
if none of the plurality of predefined reasons exist, deciding to solicit the customer to apply for the retail debit card.

### Claim 35 (depends on 34)

The method of claim 34, wherein the central computing network further comprises a messaging module, and the method further comprises:
the messaging module issuing a solicitation message to the POS device providing a retail employee operating the POS device with instructions to complete the purchase transaction with the customer based on a determination made by the solicitation module whether to solicit the customer to apply for the retail debit card.

### Claim 36 (depends on 34)

The method of claim 34, wherein if while using the solicitation module to determine whether to solicit the customer to apply for the retail debit card it is determined that the customer should be solicited to apply for the retail debit card, the method further includes:
soliciting the customer via a retail employee operating the POS device as prompted by the POS device based on the determination of the solicitation module;
if the customer accepts the solicitation, enrolling the customer for a retail debit card using the POS device, using the POS device to enable the customer to fund the retail debit card, and using the POS device to accept the retail debit card to pay for the one or more items being purchased by the customer during the purchase transaction.

### Claim 37 (depends on 34)

The method of claim 34, wherein the central computing network includes an internal electronic payment delivery (EPD) system file maintained by the retail corporation and comprising a list of financial institutions participating in an EPD system associated with the retail corporation, each financial institution having a corresponding routing number, and the plurality of pre-defined reasons include the routing number of the MICR line of the check scanned by the POS device being absent from the internal EPD system file, and determining if any of the plurality of predefined reasons exists includes:
using the solicitation module to compare the routing number from the scanned MICR line to the internal EPD system file and to determine if the routing number of the scanned MICR line is absent from the internal EPD system file.

### Claim 38 (depends on 34)

The method of claim 34, wherein the central computing network includes a list of MICR lines from checks previously discovered by the retail corporation to be associated with non-viable DDAs, the plurality of pre-defined reasons include the DDA number and routing number of the scanned MICR line matching an account number and a routing number of any MICR lines associated with the non-viable DDAs, and determining if any of the plurality of predefined reasons exists includes:
using the solicitation module to determine if the DDA number and routing number of the scanned MICR line match the account number and the routing number of any MICR lines associated with the non-viable DDAs.

### Claim 39 (depends on 34)

The method of claim 34, wherein the central computing network includes an account database having a list of credit and debit accounts associated with the retail corporation, the plurality of pre-defined reasons include the customer having an existing debit account associated with the retail corporation, and determining if any of the plurality of predefined reasons exists includes:
using the solicitation module to determine an identity of the customer based on the MICR line scanned by the POS device, and
using the solicitation module to determine if the customer has an existing debit account associated with the retail corporation including accessing the account database.

### Claim 40 (depends on 39)

The method of claim 39, wherein:
the central computing network includes a list of MICR lines with DDAs previously determined to be non-viable and an internal electronic payment delivery (EPD) system file,
the EPD system file is maintained by the retail corporation and comprises a list of financial institutions participating in an EPD system associated with the retail corporation,
each financial institution having a corresponding routing number, the plurality of pre-defined reasons include the scanned MICR line matching any MICR line in the list of MICR lines and the routing number from the scanned MICR line not being listed in the internal EPD system file, and
determining if any of the plurality of predefined reasons exists includes:
using the solicitation module to determine if the routing number of the scanned MICR line is not listed in the internal EPD system file, and
using the solicitation module to determine if the scanned MICR line matches any MICR line from the list of MICR lines with DDAs previously determined to be non-viable.
