The file's text, extracted by GovTribe without its formatting.
Attachment 2: SNAP/Cash Requirements
Table of Contents
| 1 | WSEA Project Management, Organization and Staffing | 6 |
| 1.1 | Project Management and Organization | 6 |
| 1.2 | Project Staffing | 8 |
| 2 | SNAP/Cash Technical and Functional Requirements | 11 |
| 2.1 | EBT Benefit Delivery Methods | 11 |
| 2.2 | EBT Account Structure | 11 |
| 2.3 | Account Set-up and Benefit Authorization | 14 |
| 2.4 | EBT Card Production and Management | 26 |
| 2.5 | Card and PIN Issuance | 32 |
| 2.6 | Transaction Processing | 39 |
| 2.7 | Administrative Functionality | 58 |
| 2.8 | Cardholder Customer Service | 61 |
| 2.9 | Retailer Customer Service | 67 |
| 2.10 | State and Local Office Assistance | 69 |
| 2.11 | Retailer Management | 70 |
| 2.12 | Settlement and Reconciliation | 83 |
| 2.13 | ACH Services | 87 |
| 2.14 | Branded Debit Cards | 91 |
| 2.15 | EBT Reporting | 92 |
| 2.16 | USDA Data Files | 98 |
| 2.17 | Change Management Process | 99 |
| 2.18 | Disaster Support | 106 |
| 2.19 | System Security | 115 |
| 2.20 | Fraud Detection | 119 |
| 3 | SNAP/Cash Business Requirements | 122 |
| 3.1 | EBT Contractor Liabilities | 122 |
| 3.2 | Invoicing for Cash and SNAP EBT Services | 123 |
| 3.3 | Accounting and Audit Requirements | 125 |
| 3.4 | Contract Performance Requirements | 127 |
| 4 | SNAP/Cash Project Deliverables and Documentation | 150 |
| 4.1 | Standardized Deliverables and Documentation | 150 |
| 4.2 | Deliverable and Documentation Provision and Format | 151 |
| 4.3 | Deliverable and Documentation Reviews | 152 |
| 4.4 | Deliverable Acceptance Criteria | 152 |
| 4.5 | Deliverable and Documentation Due Dates | 153 |
| 5 | SNAP/Cash Transition/Conversion and Implementation | 169 |
| 5.1 | Requirements for SNAP/Cash | 169 |
| 5.2 | Transition and Conversion of SNAP/Cash EBT | 171 |
| 5.3 | End of Contract Transition | 174 |
| 6 | SNAP/Cash System Testing Requirements | 176 |
| 6.1 | System Testing Requirements | 176 |
| 6.2 | Connectivity Testing | 177 |
| 6.3 | Interface Testing | 178 |
| 6.4 | Functional Demonstration | 179 |
| 6.5 | User Acceptance Test | 179 |
| 6.6 | Performance (Stress) Testing | 181 |
| 6.7 | Contingency Testing | 182 |
| 7 | SNAP/Cash State Specific Requirements | 184 |
| 7.1 | Alaska SNAP/Cash State Specific Requirements | 184 |
| 7.2 | Arizona SNAP/Cash State Specific Requirements | 185 |
| 7.3 | Colorado SNAP/Cash State Specific Requirements | 186 |
| 7.4 | Guam SNAP/Cash State Specific Requirements | 187 |
| 7.5 | Hawaii SNAP/Cash State Specific Requirements | 187 |
| 7.6 | Idaho SNAP/Cash State Specific Requirements | 188 |
| 7.7 | Nebraska SNAP/Cash State Specific Requirements | 189 |
| 7.8 | Washington SNAP/Cash State Specific Requirements | 189 |
| 7.9 | Wyoming SNAP/Cash State Specific Requirements | 190 |
| Table 1: Project Management and Organization | 6 |
| Table 2: Project Management | 8 |
| Table 3: EBT Benefit Delivery Methods – Requirements | 11 |
| Table 4: EBT Account Structure – Requirements | 11 |
| Table 5: Account Set-up and Benefit Authorization – Requirements | 14 |
| Table 6: EBT Card Production and Management – Requirements | 26 |
| Table 7: Card and PIN Issuance – Requirements | 32 |
| Table 8: Transaction Processing – Requirements | 39 |
| Table 9: Administrative Functionality- Requirements | 58 |
| Table 10: Cardholder Customer Service - Requirements | 61 |
| Table 11: Retailer Customer Service - Requirements | 67 |
| Table 12: State and Local Office Assistance | 69 |
| Table 13: Retailer Management – Requirements | 70 |
| Table 14: Settlement and Reconciliation – Requirements | 83 |
| Table 15: ACH Services – Requirements | 87 |
| Table 16: Branded Debit Cards – Requirements | 91 |
| Table 17: EBT Reporting – Requirements | 92 |
| Table 18: USDA Data Files – Requirements | 98 |
| Table 19: Change Management Process- Requirements | 99 |
| Table 20: Disaster Support - Requirements | 106 |
| Table 21: System Security - Requirements | 115 |
| Table 22: Fraud Detection - Requirements | 119 |
| Table 23: EBT Contractor Liabilities - Requirements | 122 |
| Table 24: Invoicing for Cash and SNAP EBT Services – Requirements | 123 |
| Table 25: Accounting and Audit Requirements – Requirements | 125 |
| Table 26: Contract Performance – Requirements | 127 |
| Table 27: Standardized Deliverables and Documentation – Requirements | 150 |
| Table 28: Deliverable and Documentation Provision and Format – Requirements | 151 |
| Table 29: Deliverable and Documentation Reviews - Requirements | 152 |
| Table 30: Deliverable Acceptance Criteria - Requirements | 152 |
| Table 31: Deliverable and Documentation Due Dates - Requirements | 153 |
| Table 32: Requirements for SNAP/Cash Programs – Requirements | 169 |
| Table 33: Transition and Conversion of SNAP/Cash EBT – Requirements | 171 |
| Table 34: End of Contract Transition – Requirements | 174 |
| Table 35: System Testing – Requirements | 176 |
| Table 36: Connectivity Testing – Requirements | 177 |
| Table 37: Interface Testing – Requirements | 178 |
| Table 38: Functional Demonstration Requirements | 179 |
| Table 39: Functional Demonstration Requirements | 179 |
| Table 40: Performance (Stress) Test Requirements | 181 |
| Table 41: Contingency Testing Requirements | 182 |
| Table 42: Alaska Requirements | 184 |
| Table 43: Arizona Requirements | 185 |
| Table 44: Colorado Requirements | 186 |
| Table 45: Guam Requirements | 187 |
| Table 46: Hawaii Requirements | 187 |
| Table 47: Idaho Requirements | 188 |
| Table 48: Nebraska Requirements | 189 |
| Table 49: Washington Requirements | 189 |
| Table 50: Wyoming Requirements | 190 |
WSEA Project Management, Organization and Staffing Project Management and Organization Table 1: Project Management and Organization
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Yes/No Comments:
| Project Organization |
| R |
| The EBT contractor shall have coordination between the EBT Contractor’s personnel (the EBT Contractor’s Project Director and assigned State Project Manager) and the State’s EBT Director. It should be noted that there are separate State EBT Directors for SNAP/Cash and WIC EBT programs. |
| Project Organization |
| R |
| The EBT Contractor shall implement and enforce procedures to provide adequate notification to the States and their EBT Director when potential or actual problems are identified. |
| Project Organization |
| R |
| The EBT Contractor’s personnel (Project Director and designated State Project Managers) shall have decision-making authority within the EBT Contractor’s organization in relation to this EBT project. |
| Project Organization |
| R |
| The EBT contractor shall have a management structure that ensures adequate oversight and executive direction for the EBT Contractor’s personnel (Project Director and assigned State Project Managers). |
| Project Organization |
| R |
| The EBT Contractor shall notify the State, whenever possible in advance, when the State’s normal contact is expected to be unavailable, and the EBT Contractor must provide the State with contact information for an alternative or back-up contact. |
| Project Organization |
| R |
| Calls and/or e-mails from the State’s EBT Project Director to any designated contact must be returned within 24 hours. |
| Project Organization |
| R |
| The EBT contractor shall have lines of authority, communication, escalation, and problem resolution procedures established between the prime EBT Contractor and any subcontractors. |
| Project Organization |
| R |
| The EBT Contractor shall have the appropriate number and mix of project staff, both on and off site, at all times during each State’s conversion phase to ensure the successful transition and operation of the States’ EBT systems. At a minimum, Offeror shall propose a Project Manager, Technical Lead, Retail Manager, and Test Manager during the conversion phase of the project, along with the anticipated percentage of time the staff will be dedicated to the project. |
| Project Organization |
| R |
| The EBT Contractor’s State Project Manager, key personnel, or designees shall be available on-site in Alaska, Arizona, Colorado, Hawaii, Idaho, Nebraska, Washington, or Wyoming within two (2) business days of the State’s request, and in Guam within five (5) business days of Guam’s request, at no cost to the State. |
| Project Organization |
| R |
| If the State deems it necessary for the EBT Contractor to be on site to respond to emergency or critical situations, the EBT Contractor shall be onsite in the timeframe requested by the requested State or Territory, which will not be less than the timeframes provided in Requirement 1.1.9. |
Project Staffing Table 2: Project Management
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Yes/No/ Comments:
| Project Staffing |
| P |
| The EBT Contractor’s proposed WSEA Project Director shall meet the following minimum requirements: |
· At least three years of project management experience, two of which must have been in projects involving State government.
· Have successfully managed within the last five (5) years the implementation and/or operation of an EBT or other financial and/or transaction processing system of comparable size and similar complexity as defined within this RFP.
| Project Staffing |
| P |
| The EBT Contractor’s proposed State Project Manager for each state shall meet the following minimum requirements: |
· Bachelor’s Degree or five years of Project Management experience.
· Minimum of three years of Project Manager experience.
· Five years of work experience.
· Has supported at least 2 State government projects, including the implementation of at least one financial transaction processing systems.
· PMP is desirable.
| Project Staffing |
| R |
| The Contractor’s State Project Manager shall start work on a State’s project no later than 15 days after the effective date of the contract between the Offeror and the State and will continue through the State’s written acceptance of the successful conversion of the current EBT system to the EBT Contractor’s EBT system and into the operations phase. |
| Project Staffing |
| R |
| Each WSEA State will continue to have an assigned Contractor’s State Project Manager for the entire length of the operations phase. During the operations phase, the State Project Manager must maintain regular and frequent contact with the State’s EBT Program Director and designated staff members. |
| Project Staffing |
| R |
| During the contract, the State may request the replacement of the Contractor’s State Project Manager for any legitimate performance reason and the replacement will also be subject to State approval. Staff replacement occurring at the State’s request shall be performed within 30 calendar days of receipt of the request. |
| Project Staffing |
| R |
| Key personnel from the EBT Contractor subject to the approval of the State are: |
· Retail Manager;
· Technical Conversion Coordinator;
· System Test Manager; and
· Technical System Lead.
| Project Staffing |
| R |
| WSEA States may conduct interviews of key personnel prior to award in order to determine acceptability. |
| Project Staffing |
| R |
| If any of the proposed key personnel or project managers are not currently in the employ of the Offeror, a letter of intent to accept employment shall be included in the response. |
| Project Staffing |
| R |
| If a change in key personnel is made after award, the Offeror shall present the replacement to the impacted State, and the State will have right of refusal privileges. |
SNAP/Cash Technical and Functional Requirements EBT Benefit Delivery Methods Table 3: EBT Benefit Delivery Methods – Requirements
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Comments:
| EBT Benefit Delivery Methods |
| R |
| WSEA States are acquiring EBT services to support SNAP and cash benefit delivery via the State issued EBT card. Throughout this RFP document, these services are referred to as core services. |
| EBT Benefit Delivery Methods |
| R |
| Other services, such as direct deposit, branded debit card, Pandemic EBT, fresh fruits and vegetables incentive program, and SNAP Summer Foods program may be acquired through this procurement at the option of the States. Throughout this RFP document, these services are referred to as optional services. |
EBT Account Structure Table 4: EBT Account Structure – Requirements
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Comments:
| EBT Account Structure |
| R |
| The EBT Contractor shall design the EBT Account Structure to ensure that: |
1) benefit balances are accurately maintained;
2) benefits accessed by clients are drawn from the appropriate benefit account; and
3) benefit accounts are not overdrawn.
| EBT Account Structure |
| R |
| The EBT Contractor shall be liable for: |
1) any funds drawn from an incorrect account or program,
2) overdrafts against EBT benefit accounts including allowing access to program benefits prior to the availability date or after the expiration date, and
3) for EBT host transaction processing errors.
| EBT Account Structure |
| R |
| The EBT Contractor shall establish an EBT account structure that supports the characteristics and restrictions of each of the cash and SNAP benefit programs. |
| Cash Benefits |
| R |
| The EBT Contractor shall be required to maintain a bank account to hold and maintain prefunded benefits. Prefunded benefits are subject to Regulation E compliance. |
| Cash Benefits |
| R |
| The EBT Contractor shall be liable for all funds deposited into prefunded benefit accounts. |
| Cash Benefits |
| R |
| The EBT Contractor shall maintain a pooled cash account for each eligible family or person that includes both day-of-draw cash and prefunded cash. |
| Cash Benefits |
| R |
| For audit and control purposes, the EBT Contractor shall be required to track cash benefit transactions and balances by benefit type and State benefit authorization number and must ensure that cash benefits are not commingled with SNAP benefits. |
| SNAP Benefits |
| R |
| For audit and control purposes, the EBT Contractor shall be required to track SNAP benefit transactions and balances by SNAP benefit type and State benefit authorization number. The balance available to cardholders for SNAP purchases or balance inquiries shall be the sum of all Federal and State SNAP benefits in the SNAP account. |
| SNAP Benefits |
| R |
| Clients must be able to access their SNAP benefits at an authorized retailer in any State or Territory. |
| SNAP/Cash Benefits |
| R |
| Due to an ongoing issue with card skimming and fraudulent cardholder transactions, the EBT Contractor shall provide the ability to WSEA States to restrict cardholder transactions in portions of specified foreign States or the whole State. The State EBT Project Director will inform the EBT Contractor which area of the foreign States by zip code or county, or the whole State, that should not be allowed to accept transactions from cardholders of the respective WSEA State. |
| SNAP/Cash Benefits |
| R |
| The EBT Contractor shall provide the State a mechanism to allow specific EBT cards to work in foreign States that have been restricted from processing the WSEA States’ cards. The EBT Contractor shall allow EBT transactions in foreign States immediately after the State has requested access for the EBT cards. |
| SNAP Benefits |
| R |
| SNAP benefits may not be accessed at ATM terminals and may not be commingled with cash benefits in the EBT account. |
| Primary Program Designation |
| R |
| The EBT Contractor shall use a Primary Program Designation (PPD) to determine the benefit type from which funds shall be drawn for disbursement to the client and for settlement when a cardholder has benefits from multiple cash or SNAP benefit types. |
| Primary Program Designation |
| R |
| All Offerors must stipulate that they will use the PPD to allocate withdrawals to the appropriate benefit type. WSEA EBT clients may be eligible to receive SNAP and/or cash benefits from one or more programs. |
Account Set-up and Benefit Authorization Table 5: Account Set-up and Benefit Authorization – Requirements
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Comments:
| Account Set-up and Benefit Authorization |
| R |
| The EBT Contractor shall accommodate changes in interface requirements resulting from modifications to the State’s eligibility or certification system and changes to standards and FNS rules and guidelines. |
| Account Set-up and Benefit Authorization |
| R |
| The EBT Contractor shall be available to accept file and record transmissions within 60 minutes of being notified by the State that their system was not available to accept a file or record transmission. |
| Account Set-up and Benefit Authorization |
| R |
| The EBT Contractor shall establish high performance connectivity between the EBT Contractor’s primary and back-up EBT systems and each State’s primary and back-up systems. |
| Account Set-up and Benefit Authorization |
| R |
| The EBT Contractor shall be required to provide all necessary hardware and software to ensure connectivity. |
| Account Set-up and Benefit Authorization |
| R |
| The EBT Contractor shall provide the services and hardware needed to ensure high performance connectivity between all sites which may include the use of FTP sites. |
| Account Set-up and Benefit Authorization |
| R |
| The EBT Contractor shall have a back-up procedure to transfer and accept account set-up and benefit authorization files and records should the normal file and/or record transfer process fail. |
| Set-Up EBT Account |
| R |
| The EBT system must create EBT accounts upon the receipt of the account set-up record. |
| Pending Account Status |
| R |
| The EBT account shall have no benefit value until the State sends a benefit authorization record and the EBT Contractor processes and posts the benefit to the account. |
| Pending Account Status |
| R |
| An EBT Account that has been created but to which no benefits have been posted shall be held in a pending status. |
| Benefit Authorization |
| R |
| The EBT Contractor shall be required to check the benefit availability date of each benefit file and record to ensure that it is not older than a State specified date. |
| Benefit Authorization |
| R |
| The EBT Contractor shall be required to develop a file edit procedure to detect duplicate files and/or records. |
| Benefit Authorization |
| R |
| For established cases, the WSEA States generate SNAP/cash benefit authorization batch files once per month. In addition, WSEA States generate multiple daily files and overnight SNAP/cash batch files and records for transmission to the EBT Contractor to set up accounts and authorize benefits. In addition to batch files, the EBT Contractor must be able to accept account set-up and benefit authorization records sent through administrative terminals throughout the day. |
| Benefit Authorization |
| R |
| Account set-up and benefit authorization records received must be processed and benefits made available to clients on the benefit availability date by the time specified by the State and agreed upon with the EBT Contractor. |
| Benefit Authorization |
| R |
| Benefits are not considered available unless they have 1) been posted to the Contractor’s host database, and 2) reached or exceeded their availability date. |
| Benefit Authorization |
| R |
| The EBT Contractor shall process and make benefits available to clients within one (1) hour of receipt for batch files received during the day. |
| Benefit Authorization |
| R |
| The EBT Contractor shall provide a return file that confirms processing of the benefit batch file with summary totals and clearly identifies any records not processed and the reason the record was rejected. |
| Benefit Authorization |
| R |
| Records sent on-line must be processed and benefits made available to clients immediately. |
| EBT Account Number |
| R |
| The EBT Contractor shall establish a unique EBT account number for use in identifying each EBT account in the EBT Contractor’s system. Offerors must specify the approach for development of the EBT Account Number and indicate how it will be used within the EBT system and EBT Account Structure to identify cases and programs for which cases are certified. Offerors must also specify the approach for validating the EBT Account Numbers included in the State’s batch files and on-line transmissions. |
| EBT Account Maintenance |
| R |
| The EBT Contractor shall maintain an account for each household or case. The primary purpose of client account maintenance is to ensure that clients have access to their authorized benefits, the States have administrative access and tools to manage client accounts, and that accurate and timely information is maintained regarding client transactions, account balances and client demographic information. |
| EBT Account Maintenance |
| R |
| The EBT Contractor shall not make changes or updates to account demographic information unless authorized to do so by the State. WSEA States will send updates to account demographic information through batch or on-line processes. Depending on State preferences, the EBT Contractor may or may not be required to return a confirmation for updates to account demographic data. |
| Maintain Account Balances |
| R |
| The EBT Contractor must ensure that benefits are available on the benefit availability date and time designated by the WSEA State and that any unused SNAP and cash balance are carried over from month-to-month. |
| Maintain Transaction History |
| R |
| The EBT Contractor shall be required to maintain and provide access to current account balances and a rolling three-year transaction history for each account. |
| Maintain Transaction History |
| R |
| The EBT Contractor shall provide the WSEA States with on-line access through administrative terminal functionality with a minimum of three years of transaction history. However, transaction history data must be maintained as required by State, FNS, Federal Reserve Board, QUEST® Rules or Federal law. |
| Maintain Transaction History |
| R |
| · The EBT Contractor shall provide ready access for authorized entities to data older than three (3) years as required for investigative and auditing purposes. |
| Maintain Transaction History |
| R |
| At the termination of the contract, the EBT Contractor shall transfer the most recent seven (7) full Federal fiscal years of transaction detail to an entity specified by the State and ensure accuracy and readability of such information at the new location, or maintain the transaction detail in such a format that it supports timely access to that data by authorized State and Federal staff. At a minimum, data within the transaction history inquiries shall include: |
· PAN (card number);
· EBT account number;
· Recipient case identification numbers;
· Benefit program identifier;
· Benefit authorization number from the State
· Retailer identification numbers (both USDA-FNS and acquirer)
· Terminal identification number;
· Transaction type;
· Transaction amount;
· Transaction date;
· Transaction time;
· Transaction results (approval code or denial reason);
· Store name and address;
· Account balance after the transaction;
· ACH transaction history.
| Aging Accounts – SNAP |
| R |
| A WSEA client’s SNAP EBT account shall be flagged and reported to the State if there has been no debit transaction posted against the SNAP account for a ninety (90) day period, although there may be a balance in the account and benefits may have been deposited into the account within that same time frame. |
| Aging Accounts – SNAP |
| R |
| If funds have been withdrawn from the SNAP account during the ninety (90) day period, the SNAP account is considered active. |
| Aging Accounts – SNAP |
| R |
| The EBT Contractor shall provide the ability to flag EBT accounts to have benefits moved offline after three (3) months of inactivity. If the offline aging flag is set, the EBT Contractor shall move all SNAP benefits off-line after three (3) months of inactivity, at which point the EBT account is not accessible to households. The household must be notified in writing when benefits are moved off-line. |
| Aging Accounts – SNAP |
| R |
| SNAP benefits that have been available to the household for 274 calendar days or more shall be expunged after 274 days of inactivity on the accountSNAP benefits not accessed by a household for nine months (274 days from date of initial availability) shall be expunged. |
| Aging Accounts - Cash |
| R |
| A client’s EBT cash account shall be considered stale if there has been no financial withdrawal posted against the cash account for a specific period as designated by the State although there may be a balance in the account and benefits may have been deposited into the account within that same time frame. If funds have been withdrawn from the cash account during the period specified by the State, the cash account is considered active. |
| Aging Accounts |
| R |
| Any non-financial transactions by the client, such as balance inquiries, do not affect the aging of the account. |
| Aging Accounts |
| R |
| The Offeror must have the capability to reinstate accounts that have been moved offline for a period of up to six months for SNAP and up to nine months for cash. |
| Aging Accounts |
| R |
| The flag to move stale accounts off-line shall be parameter driven and shall be specific to each WSEA State. States may elect to set the flag to move a benefit off-line at a period greater than the 90-day period. |
| Benefit Aging |
| R |
| On a daily basis the EBT Contractor shall send each WSEA State an extract file of all benefits falling into the aging periods as specified by the State. The WSEA States require a minimum of four (4) aging flags or periods for each client’s SNAP account and four (4) aging flags or periods for each client’s cash account. These flags shall be parameter driven and shall be specific to each WSEA State. Parameters and aging flags can differ by account type (SNAP or cash). |
| Benefit Aging |
| R |
| The file shall include a header record, a detail record for each benefit being reported on, and a trailer record. The detail record shall contain sufficient data, as determined by the State, to identify the client, benefit type, aging period and the balance being aged or expired. |
| SNAP and Cash Expungements |
| R |
| The EBT Contractor shall ensure that all EBT benefits meeting the State specified expungement rules are expunged in the timeframes specified. |
| SNAP and Cash Expungements |
| R |
| The EBT Contractor shall be required to produce an Expungement Report that at a minimum includes the Case Number/Household ID, State benefit authorization number, original benefit authorization date, original benefit amount, and expunged amount. |
| SNAP and Cash Expungements |
| R |
| The Contractor must track aging at both the account and benefit levels. Each benefit begins aging at the time it becomes available to the client. The EBT account begins aging at the point that the first benefit becomes available. Subsequently, each time that the client completes an approved debit [or credit] transaction, the account aging clock is reset to start anew, even if one or more benefits have been expunged. |
| SNAP and Cash Expungements |
| R |
| Each WSEA State shall have the option of expunging SNAP benefits older than 274 calendar days and up to 365 calendar days for cash benefits when the last client activity on the account has reached 274 calendar days for SNAP and the State-specified last benefit activity (up to 365 calendar days) for cash, or just the benefits falling into the account aging criteria for date of last use (274 calendar days for SNAP and up to 365 calendar days for cash depending on the State’s requirement). |
| SNAP and Cash Expungements |
| R |
| Benefits may not be expunged until the account aging clock has reached 274 calendar days for SNAP and the State selected number of calendar days for cash (up to 365). State agencies will now have the option to maintain the current method of expunging unused benefits only from inactive accounts or to expunge benefits based on the date of issuance, regardless of account activity. |
· Option 1: SNAP benefits that have been available to the household for 274 calendar days or more (up to 365 days for cash) can be expunged after 274 days of inactivity on the account (up to 365 days for cash). Any activity (purchase or return) in the account starts the aging period over again.
· Option 2: Regardless of account activity, remaining unused benefits that have aged (274 calendar days for SNAP and up to 365 days for cash) shall be expunged.
All WSEA States are currently using Option 1.
| SNAP and Cash Expungements |
| R |
| If the WSEA State chooses to expunge on a benefit level, if one or more subsequent benefit authorizations for the same client account have been available to the client for less than 274 days for SNAP and less than the selected number of calendar days for cash, they are not expunged. They must remain available to the client until each has reached full expungement age. |
| SNAP and Cash Expungements |
| R |
| If an account that has had all benefits expunged is reactivated because the client has again become eligible, the account must be treated in the same manner as a new account in terms of benefit aging and expungement timeframes. |
| SNAP and Cash Expungements |
| R |
| The 2018 Farm Bill requires that SNAP benefits be expunged when all certified household members are determined to be deceased (7 CFR 272.14). The EBT Contractor shall provide a mechanism through the administrative terminal for States to report households where all members are determined to be deceased. |
| SNAP and Cash Expungements |
| R |
| Several of the WSEA States are in the process of updating their interfaces to report household where all members are determined to be deceased. The EBT Contractor shall support this automated means through the State interface to the EBT System to report these households. |
| Open and closed accounts |
| R |
| EBT accounts shall remain open unless the State directs the EBT Contractor to close an account. |
| Pending Account Purge |
| R |
| Some WSEA States issue pending cards, set-up pending account demographics or pending benefits for individuals whose accounts have not yet been established. In some instances, these individuals will not be certified. The EBT Contractor shall be required to provide the administrative capability to search for pending cards, demographics or benefits and shall be required to provide periodic reports on pending cards, demographics, or benefits. |
| Pending Account Purge |
| R |
| The EBT Contractor shall periodically automatically purge pending cards, demographics or benefits dependent upon parameters specified by the respective WSEA State. |
| Pending Account Purge |
| R |
| The EBT Contractor shall provide the States with the administrative capability to purge accounts and benefits or deactivate a card. These parameters may vary by benefit type or program. |
| Pending Benefit Void |
| R |
| The EBT Contractor shall provide States with the capability to purge or void pending benefits that have been authorized but have not yet reached their benefit availability date. |
| Pending Benefit Void |
| R |
| States may submit benefit detail record(s) for processing that purges or voids the same record that is held in the pending benefit file. The EBT Contractor shall accept the file, identified by an action code, for processing and submit a return file that confirms that the action was completed. |
| Hold SNAP Funds |
| R |
| Under specific conditions (i.e., EBT system downtime or a disaster), a manual SNAP transaction may be performed by a retail merchant. When manual SNAP transactions are performed, the merchant will obtain a voice authorization. The EBT Contractor shall hold funds authorized by voice authorization. |
| Hold SNAP Funds |
| R |
| The number of days that funds shall be placed on hold will be specified by the State, but the maximum hold period shall be 30 calendar days (the acquirer shall be required to convert the manual SNAP transaction to electronic transaction for transmission to the EBT Contractor). If the manual transaction is presented for settlement within the State specified number of calendar days from the date of the manual authorization, the EBT Contractor shall debit the amount from the cardholder account and settle the transaction. |
| Hold SNAP Funds |
| R |
| If the manual transaction is not presented within the specified number of calendar days from the authorization date, the EBT Contractor shall release the hold on funds and make them available for cardholder access. |
| Hold SNAP Funds |
| R |
| A hold may also be placed on a cardholder account in anticipation of a potential debit adjustment to the account to correct a system error. Each WSEA State will determine whether or not to implement a hold for a potential debit adjustment. |
| File and Record Formats |
| R |
| The WSEA States have defined formats established with the current EBT processor for the exchange of Case/Client Maintenance records and Benefit Issuance records. To minimize changes to State systems, the EBT Contractor shall utilize the existing file and record formats for the exchange of this data, unless otherwise stipulated by the State. |
| Alternate Cardholders |
| R |
| The EBT Contractor shall provide a card for the alternate cardholder(s) that has a unique card number and PIN and shall include the alternate cardholder’s name for cards mailed by the EBT Contractor or printed by the State. The client shall have the option of canceling or changing their alternate cardholder. |
| Alternate Cardholders |
| R |
| The EBT Contractor shall provide a method for reporting on alternate cardholder benefit transaction activity. At a State’s option, a client’s ability to perform this function may be restricted. |
| Protective Payees |
| R |
| The EBT Contractor shall provide a card for the protective payee that has a unique card number and PIN. In some instances, the State may require that a single protective payee have access to multiple client accounts. The client shall not have the capability of canceling or changing the protective payee. Only the State or the designated protective payee shall have the option of canceling or changing a protective payee’s access to the EBT account. |
| Fraud Investigative Accounts |
| R |
| The EBT Contractor shall provide the capability to create and maintain EBT accounts and issue EBT cards for use in SNAP fraud investigations |
| Fraud Investigative Accounts |
| R |
| Fraud accounts and compliance accounts and benefit authorizations may be set up through either the batch or administrative terminal (on-line) interface to the EBT Contractor’s EBT system and should have unique identifiers. The States, if desired, should have the ability to create an identifier that is readily distinguishable from “normal” case identifiers or numbers. SNAP fraud accounts shall only contain a primary client. |
| P-EBT |
| R |
| The EBT Contractor shall support the set-up and administration of Pandemic EBT (P-EBT) accounts and benefits. |
| P-EBT |
| R |
| If an EBT account already exists for the household receiving P-EBT benefits, the State will issue P-EBT benefits to the existing EBT account. If an existing EBT account does not exist, the State will provide demographic data to set-up the EBT account before issuing P-EBT benefits. The EBT Contractor shall support both methods of set-up and issuance. |
| P-EBT |
| R |
| P-EBT benefits shall be treated the same as SNAP benefits in terms of issuance, redemption, transaction processing, settlement, and expungement. |
| SEBTC |
| R |
| Summer EBT for Children (SEBTC) is a program that provides SNAP benefits to eligible school age children during the summer months when schools are closed. The SEBTC program is currently administered under grants received from USDA. While none of the WSEA States are currently participating in the SEBTC program, the EBT Contractor shall support SEBTC if requested by a State in the future. |
| SEBTC |
| R |
| The EBT Contractor shall provide all services to participants in the SEBTC program as it would a SNAP client. Benefits issued through the SEBTC program shall follow the same service policies and procedures as SNAP benefits. |
| SEBTC |
| R |
| The EBT Contractor shall ensure the following special reporting requirements are followed: |
· Accommodate processing for a separate Letter of Credit (LOC) for SEBTC benefits.
· Separate and track Summer Food benefits from SNAP benefits,
· On a daily basis, process and transmit to the FRB, a separate Summer Foods AMA Batch Issuance File.
· On a daily basis, produce a separate Summer Foods AMA Batch Issuance and ASAP Balancing Reports.
· List a separate line item for Summer Foods on the Clearing Statement Report.
· Create and Transmit a separate STARS file for Summer Foods.
| SEBTC |
| R |
| The EBT Contractor shall accept Summer Food benefits transmitted to the contractor either online through the EBT Administrative Terminal or by Benefit Issuance File |
| SEBTC |
| R |
| Summer foods benefits shall be used prior to any SNAP benefits in the participant’s EBT account, regardless of when other SNAP benefits were added to the account. |
| SEBTC |
| R |
| The EBT Contractor shall support the special requirements for benefit expungements for the Summer Foods program. Unused Summer Food benefits expire at the end of the summer when school starts. On an annual basis, the state will provide the exact expiration date to the contractor for the respective year. Summer Food benefits should be expunged from the EBT database and reported as expunged on the AMA file. |
| FFV Incentive Program |
| R |
| Should any State decide to implement a fresh fruit and vegetable (FFV) incentive program, the EBT Contractor shall support the implementation and operations of the program. |
| FFV Incentive Program |
| R |
| The FFV Incentive Program shall follow the model implemented by Massachusetts in Hampden County (Healthy Incentive Pilot or HIP) in late 2011. |
EBT Card Production and Management Table 6: EBT Card Production and Management – Requirements
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Comments:
| State Specific EBT Cards |
| R |
| If requested, the EBT Contractor shall work with the requesting WSEA State to develop a card design unique to the State. |
| State Specific EBT Cards |
| R |
| The EBT Contractor shall: |
· Perform all necessary processes and functions to design a State’s EBT card;
· Distribute/deliver cards to designated State and local offices for over-the-counter issuance;
· Issue, replace and distribute/deliver cards to cardholders by mail; and
· Maintain a centralized card issuance management database on behalf of each WSEA State.
| State Specific EBT Cards |
| R |
| The EBT Contractor shall ensure that the WSEA States’ EBT cards are designed and comply with specifications including the QUEST® Operating Rules (SNAP/cash), the International Standards Organization (ISO) and American National Standards Institute (ANSI) specifications and standards relating to cards used for financial transactions. |
| State Specific EBT Cards |
| R |
| The SNAP/cash EBT card must carry the QUEST® service mark. |
| State Specific EBT Cards |
| R |
| The EBT Contractor shall continue to use the current cards and accommodate the required changes in return addresses or customer service numbers through an attrition process. |
| EBT Card Design |
| R |
| The EBT Contractor shall be required to update or maintain a card design for each WSEA State. |
| EBT Card Design |
| R |
| During the contract period, the State shall be allowed one re-design at no additional cost to the State. States will provide input to the design process for their State’s card and absolutely reserve the right for prior approval of any changes in their State’s card design or information printed on the card. Card samples must also be submitted to the State whenever the card is redesigned or changed in any aspect. Redesigned cards will be replaced through attrition. Prior to finalizing card design and prior to card issuance, the Contractor shall submit samples of the card to the State for State approval. |
| EBT Card Design and Production |
| R |
| The Offeror’s proposal must describe in detail its capabilities to design and/or manufacture the States’ EBT cards and identify any third party or subcontractor involved in the process. EBT cards shall be produced and mailed from manufacturing locations that are most geographical advantageous to the WSEA states. |
| Card Security Features |
| R |
| WSEA card security features may include ultraviolet ink, four-color and fine line printing and/or a hologram. |
| Card Security Features |
| R |
| If, in the future, WSEA decides or is required to adopt the Europay, Mastercard and Visa (EMV) standards, or any other changes in security requirements, the Change Request process will be followed. |
| Card Security Features |
| R |
| The EBT Contractor shall comply with changes to security standards dictated by Quest® rules or federal regulations, and work with the respective WSEA States to implement such changes within a mutually agreed upon timeframe. |
| Card Obverse |
| R |
| The obverse of the card must have the following features: |
· Graphics approved by the State using a four-color printing process;
· The Primary Account Number (PAN) must be on the front of the card with contrasting color for readability; an embossed PAN is an optional feature;
· In cases where the EBT Contractor issues a card via mail (such as client-requested card replacement), the Contractor may be required, as an option, to emboss the cardholder’s name depending on State preference.
| Card Reverse |
| R |
| The reverse of the card shall have the following features: |
· FNS abbreviated non-discrimination statement if State requests;
· QUEST® logo if a SNAP/cash card;
· Tamper-evident signature panel;
· Return address;
· High coercivity magnetic stripe; and
· Other printed information as specified by the State.
| Card Reverse |
| R |
| Due to waivers from the FNS, the return address is not required to be printed on the SNAP/cash EBT card for some WSEA States. |
| Compliance with FNS Regulations |
| R |
| The EBT Contractor shall issue and replace EBT cards and PINs in compliance with FNS regulations 7 CFR §274.1-8. |
| High Coercivity Magnetic Stripe |
| R |
| All EBT cards produced for WSEA States, both standard and disaster EBT cards, must have a high-coercivity magnetic stripe. |
| High Coercivity Magnetic Stripe |
| R |
| The EBT Contractor shall produce card specifications and test results to confirm the card meets the RFP specifications and that the stripe for both standard and disaster cards is a high-coercivity magnetic stripe. |
| High Coercivity Magnetic Stripe |
| R |
| The EBT Contractor shall provide each WSEA State with an annual attestation indicating that all cards provided to the State during the preceding year(s), including disaster card inventories, meet the card specifications required in this RFP. |
| High Coercivity Magnetic Stripe |
| R |
| The Contractor shall provide, at no additional cost to the States, for an annual certification test of card quality by an independent third party. This test shall involve six cards pulled at random by the State from a State’s vault and disaster card inventory. The State should submit those six cards directly to an independent card-testing facility and the facility shall report back directly to the State, with a copy to the Contractor. In particular, the test results shall indicate the coercivity level and oersted rating of each tested card. The card test and the test results shall be provided to the State within 90 days of the State’s contract anniversary date. |
| Track 2 Format |
| R |
| Track 2 of the EBT card shall be encoded in accordance with ISO 7813. The maximum character count in Track 2 shall not exceed 40 characters, including all control characters. Following is the current track 2 format for WSEA cards. |
| Track 2 Format |
| R |
| The EBT cards currently have a non-expiring expiration date of “4912” encoded on Track 2. The Service Code field is encoded with a value of 120. Cards have a Card Authentication Value (CAV) encoded. The encryption keys utilized by the current Contractor shall be transferred to the new Contractor. CAV encryption keys shall not be shared among States, but shall be unique to each State |
| Track 2 Format |
| R |
| The new Contractor shall continue to encode the CAV field on Track 2 with a cryptographic value to validate the Track 2 data contents. The CAV shall be validated on all cardholder transactions containing track 2 data. |
| Primary Account Number (PAN) |
| R |
| The new Contractor shall issue EBT cards containing a 16-digit PAN that utilizes the States’ current BIN/Issuer Identification Number (IIN). |
| Primary Account Number (PAN) |
| R |
| The process by which the new EBT Contractor calculates the PAN for new cards shall not duplicate card numbers in use in the WSEA States’ existing card base. |
| Card Sleeve |
| R |
| As an option, the EBT Contractor shall produce/provide a card sleeve to accompany WSEA EBT cards. The card sleeve (envelope) must be produced from a rugged material, such as Tyvek or Mylar, to endure normal wear and tear in the use of the EBT card. |
| Card Sleeve |
| R |
| The card sleeve shall contain a separate pocket so that a client will be able to store transaction receipt(s) with the card. |
| Card Sleeve |
| R |
| The Contractor shall be responsible for securing, maintaining, and providing card sleeves to designated WSEA State, county, or local offices. |
| Personal Identification Number (PIN) |
| R |
| PIN verification shall be conducted at the EBT host. |
| Personal Identification Number (PIN) |
| R |
| The PIN offset shall not be encoded on the magnetic stripe of the card. |
| Personal Identification Number (PIN) |
| R |
| The EBT Contractor shall be required to follow the EBT QUEST® Operating Rules regarding PIN entry, encryption, transmission and key management processes and procedures. |
Card and PIN Issuance Table 7: Card and PIN Issuance – Requirements
Pref’d (P) Opt’l (O)
| Function / Service / Requirement Description |
| Offeror Complies: |
Comments:
| Card and PIN Issuance |
| R |
| The EBT Contractor shall support the card and PIN issuance requirements of each of the WSEA States. |
| Card and PIN Issuance |
| R |
| The EBT Contractor shall provide a method to verify client identity prior to issuing or changing a PIN via the IVR, cardholder portal, or a mobile app. |
| Card and PIN Issuance |
| R |
| The EBT Contractor shall provide a deactivation method for daily or bulk card stock missing (lost/stolen) card inventory that would prevent further linkage of the card to any State’s client identifier number. |
| Card and PIN Issuance |
| R |
| The EBT Contractor shall provide for fraud prevention (both internal and external fraud) and identity verification. |
| Card and PIN Issuance |
| R |
| The EBT Contractor shall restrict cardholders from selecting certain easily guessed PIN (e.g., 1111 or 1234). The list of easily guessed PINs will be provided by the State. |
| Card and PIN Issuance |
| O |
| WSEA is interested in having an automated kiosk that could be used to issue EBT cards to clients. If a WSEA State decided to implement the automated kiosks, the EBT Contractor shall support the State’s implementation.. |
| Card Distribution and Inventory Controls |
| R |
| The EBT Contractor shall deliver EBT cards to designated distribution points in each WSEA State in blocks of sequentially numbered cards. The WSEA States maintain the option to change designated locations for receipt of card shipments over the life of the contract. |
| Card Distribution and Inventory Controls |
| R |
| The EBT Contactor shall track cards and link them to their distribution point via the card numbers. |
| Card Distribution and Inventory Controls |
| R |
| The EBT Contractor shall provide States with an automated tracking tool or report to enable the State and local offices to manage their card inventory. |
| Card Distribution and Inventory Controls |
| R |
| The EBT Contractor shall provide secure card distribution to designated State/local locations, with card management and inventory and card issuance control capabilities. |
| Card Inventory and Shipping |
| R |
| Card inventory is to be provided by the EBT Contractor quarterly or as needed, upon receiving a card stock order from the State or local offices. |
| Card Inventory and Shipping |
| R |
| Card boxes in a bulk card order are to be shipped with a numbering system and accompanying inventory list in hard copy and electronic format that will indicate card numbering sequences, so that the contents of the box may be ascertained without inspection/opening the box. |
| Card Inventory and Shipping |
| R |
| Cards in a bulk card order are to be packaged in sleeves, not to exceed 4500 cards per sleeve. |
| Card Inventory and Shipping |
| R |
| Each sleeve in a bulk card order shall be labeled with the card number sequence it contains and be sealed with security tape to identify unauthorized access. |
| Card Inventory and Shipping |
| R |
| Sleeves in a bulk card order must be packed in cartons in numeric sequence, i.e., from lowest sequence number in lowest carton number to highest sequence number in highest carton number. |
| Card Inventory and Shipping |
| R |
| Sleeves in a bulk card order are to be shipped in cartons that contain six card sleeves to facilitate handling, storage, and distribution by the State. (Less than six card sleeves are allowed if the card order does not have sufficient quantities to fill a carton.) |
| Card Inventory and Shipping |
| R |
| Cartons containing cards in a bulk card order shall be packaged securely in a sturdy box and sealed with a security tape to identify unauthorized access. |
| Card Inventory and Shipping |
| R |
| Cartons containing cards in a bulk card order shall not be labeled in a manner that reveals their contents but shall be labeled with their sequence: “1 of 20”, “2 of 20”, and so on. |
| Card Inventory and Shipping |
| R |
| Produce and provide to the respective WSEA State a single flat file, formatted to display the destination of each card numbered sequence mailed for a bulk card order. |
| Magnetic Stripe Card Readers |
| R |
| To reduce errors in OTC card issuance and/or to improve the efficiency of county/local office operations, the EBT Contractor shall provide each State office with sufficient dual headed or bi-directional card readers to meet the office’s business practices. |
| Magnetic Stripe Card Readers |
| R |
| The card reader (magnetic card swipe terminal) shall enable the State and county/local staff to swipe the EBT card, read the PAN and link the PAN to the designated client record or to assist in accessing a client file. For purposes of responding to this RFP, the Offer may assume that approximately 700 card readers will be required across all WSEA SNAP State Agencies. |
| PIN Selection / Change Terminals |
| R |
| The EBT Contractor may be required to provide PIN selection terminals and any associated supplies if requested by the respective WSEA State. |
| PIN Selection / Change Terminals |
| R |
| The EBT Contractor shall be required to ship replacement PIN selection terminals via overnight express within one business day of receiving the request for a replacement. |
| PIN Selection / Change Terminals |
| R |
| If required for user set-up, the EBT Contractor shall allow a State designated employee process password changes and set-up new users. |
| Issuance Timeframes for Cards Mailed by EBT Contractor |
| R |
| The EBT Contractor shall promptly process requests to issue cards by mail. Card requests entered during the business day shall go to the card vendor for production and mailing the next day. Card replacement requests received on non-business days (e.g., through the help desk over the weekend) shall be mailed the next business day. |
| Issuance Timeframes for Cards Mailed by EBT Contractor |
| R |
| The EBT Contractor shall issue mailed cards in an active status so that the cardholder does not have to engage in card activation procedures. |
| Issuance Timeframes for Cards Mailed by EBT Contractor |
| R |
| If required by the State, corresponding system generated PIN numbers shall be mailed under separate cover and should lag the mailing of the card by one (1) to three (3) days, as designated by the State. |
| New and Replacement Cards Issued by the State |
| R |
| The EBT Contractor shall provide cardholders with 24 hour per day, 7 days per week capability to report lost, stolen or malfunctioning cards. |
This is the start of the file's text. The full file is on GovTribe.