WIC Direct to MIS Interface Control Document · Cleaned up rules for managing the Status code field...

Florida eWIC to MIS Interface Control Document Version: 2.15Dated July 27, 2017

eWIC to MIS Interface Control Document

Table of Contents

1 Document Information ............................................................................................................. 5

1.1 Document History ............................................................................................................. 5

1.2 Definitions and Acronyms ................................................................................................. 7

2 Introduction ............................................................................................................................10

2.1 Document Purpose ..........................................................................................................10

3 Interface Types ......................................................................................................................11

3.1 Message Based System Interfaces ..................................................................................11

3.1.1 Data Required in All Message Based System Interfaces ...........................................12

3.1.2 Message Processing Standards ................................................................................13

3.2 Batch System Interfaces ..................................................................................................13

3.2.1 Data Required in All Batch System Interfaces ...........................................................13

3.2.2 Confirmation File Format ...........................................................................................14

3.2.3 Batch Processing Standards .....................................................................................15

3.2.4 File Naming Standards ..............................................................................................15

4 Interface .................................................................................................................................16

4.1 WIC EBA Account Maintenance ......................................................................................16

4.1.1 Add EBA ...................................................................................................................16

4.1.2 Update EBA ..............................................................................................................17

4.1.3 Get EBA Details ........................................................................................................18

4.2 WIC EBA Benefit Maintenance ........................................................................................19

4.2.1 Add or Update Benefits .............................................................................................19

4.2.2 Get Benefit Balance ..................................................................................................20

4.2.3 Get Benefit Maintenance History ...............................................................................21

4.2.4 Get Benefit Redemption History ................................................................................22

4.3 Cardholder/Card Maintenance .........................................................................................26

4.3.1 Add Cardholder/Card ................................................................................................26

4.3.2 Add or Update PIN ....................................................................................................27

4.3.3 Validate PIN ..............................................................................................................28

4.3.4 Update Card/Cardholder ...........................................................................................29

4.3.5 Get Cardholders/Cards .............................................................................................30

4.3.6 Get Card History .......................................................................................................31

4.3.7 Report Card Updates ................................................................................................32

ii


4.4 Vendor Maintenance .......................................................................................................33

4.4.1 Add or Update WIC Vendor File ................................................................................33

4.5 WIC Food Maintenance ...................................................................................................35

4.5.1 Add or Update Category/Sub-category Information ...................................................35

4.5.2 Add or Update UPC/PLU Information ........................................................................36

4.6 WIC EBT Data Files ........................................................................................................37

4.6.1 Report WIC Benefit Redemptions .............................................................................37

4.6.2 Report WIC Benefit Changes ....................................................................................41

4.6.3 Report WIC Benefits Purged .....................................................................................42

4.7 Financial Settlement ........................................................................................................43

4.7.1 Request ACH Payment .............................................................................................43

4.7.2 Report ACH Payments ..............................................................................................44

4.8 Recoupment Files ............................................................................................................45

4.8.1 Report Recoupment Requests ..................................................................................45

4.8.2 Report Recoupment Status .......................................................................................46

4.9 Warehouse Authorization ................................................................................................47

4.9.1 Request Warehouse Authorization ............................................................................47

4.9.2 Void Warehouse Authorization ..................................................................................48

4.9.3 Get Warehouse Authorizations ..................................................................................48

4.9.4 Get Warehouse Authorization Code ..........................................................................49

Appendix A - Data Dictionary ....................................................................................................51

Appendix B - Data Element Code Tables ..................................................................................70

B.1 Action Code ....................................................................................................................70

B.2 Function Return Code .....................................................................................................70

B.3 Hierarchy Code ...............................................................................................................77

B.4 Language Code...............................................................................................................77

B.5 PIN Activity Code ............................................................................................................77

B.6 Reason Code ..................................................................................................................78

B.7 Status Code ....................................................................................................................79

B.8 Type Code ......................................................................................................................79

B.9 Message Type.................................................................................................................81

B.10 File Type .......................................................................................................................81

B.11 ICD Version ...................................................................................................................82

iii


B.12 WIC EBT System ID ......................................................................................................82

B.13 WIC MIS System ID ......................................................................................................82

B.14 POS Data Code ............................................................................................................84

Appendix C - Common Objects .................................................................................................87

C.1 Cardholder Object ...........................................................................................................87

C.2 Person Object .................................................................................................................87

C.3 Address Object ...............................................................................................................87

C.4 Head of Household Object ..............................................................................................88

Appendix D - Configurability ......................................................................................................89

Appendix E - jQuery PIN Pad Plug-in ........................................................................................90

Appendix F - Examples .............................................................................................................94

F.1 Straddle Scenario in WIC Benefit Redemption File ..........................................................94

F.2 Sample Files ...................................................................................................................99

Appendix G - Date Field Considerations ................................................................................. 131

iv


1 Document Information

1.1 Document History Version Date Effective Details 0.1 10/25/2013 Initial draft 0.2 11/12/2013 Cleaned up a few errors and added WIC State Agency ID to batch

header. Should have this added back to UI through a change request. 0.3 11/27/2013 Updated based on output of JADs. 0.4 12/6/2013 Added details for recoupment files.

Added file naming conventions. 0.5 12/9/2013 Added Record sequence number fields.

Renamed the Unique EBT transaction identifier in the redemption file to Host generated trace number. Corrected some issues.

0.6 12/19/2013 Added XML Element Name to Data Dictionary for fields that appear in batch files. Fixed style issues with Appendix. Removed MessageHeaderObject from file layout in Report WIC Benefit Changes as it contained many redundant elements. Added XML object names for file objects.

0.7 1/9/2014 Very minor correction by removing confusing rule 4.3.3.8 0.8 4/15/2014 Adding details on straddle scenarios in the WIC Benefit Redemption

File. 1.0 7/1/2014 Updated for compliance with WUMEI June 2014 draft specification. 2.0 8/18/2014 Updated based on expected changes in 3.0 version of WUMEI. 2.1 9/11/2014 Updated based on State and Q/A feedback. 2.2 9/22/2014 Fixed Appendix B.6 links, clarified some business rules, and changed

some search date requirements. Added additional function return codes. Updated straddle example. Added some missing elements from data dictionary.

2.3 10/3/2014 Now returning PIN activity code in Get Card History. Added missing definition for PIN status code to Data Dictionary.

2.4 11/2/2014 Several clarifications and improvements to accuracy based on actual eWIC operation. In Add or Update Benefits, noted that eWIC can accept more than one month at a time. Add Warehouse Authorization functions.

2.5 12/13/2014 Some clarifications and improvements. Additional clarifications/rules added for Warehouse Authorization. New values for Type code, vendor for farmer’s market and formula warehouse. Adding PIN activity code to Report Card Updates Changes to align better with WUMEI 3:

• Adding Message reason code, Item action code to GetBenefit Redemption History and Report WIC BenefitRedemptions

• Using ANSI language codes• Updates to some file and message types• Added appendix describing POS data code field values


Version Date Effective Details 2.6 4/17/2015 Some corrections, clarifications, and improvements.

Added maximum search range parameters to Configurability section and noted where they are used. Cleaned up rules for managing the Status code field in the Cardholder Object during the Update Card/Cardholder operation. In the data dictionary, clarified that “flags” can accept either 0 or N for “no” and 1 or Y for “yes”. Clarified the correct usage for date-only fields in the data dictionary and added a new appendix (Appendix G - Date Field Considerations) for additional clarification.

2.7 7/21/2015 Some corrections, clarification, and improvements. Inquiry functions will return data for households regardless of status. Added Get Warehouse Authorizations and Get Warehouse Authorization Code. Several clean up items in Data Dictionary. New Function Return Codes. New Message Types.

2.7.1 7/22/2015 Clarification to confirmation file naming standards. Clarification that .zip files may be accepted. Data Dictionary updates to better align with WUMEI.

2.8 8/14/2015 Added new APL type data element to Add or Update WIC Vendor File and Add or Update UPC/PLU Information.

2.8.1 8/28/2015 Some reference cleanup. Added clarification on how certain type codes may be used by eWIC .

2.9 9/8/2015 Modified condition code on card acceptor codes in redemption data. 2.10 1/12/2016 Some corrections, clarification, and improvements.

Updates on condition codes for online history functions to make them consistent with the history files. Some clarifications/corrections added to the Data Dictionary. Removed some unnecessary error codes.

2.11 3/28/2016 Rebranded 2.12 3/20/2017 Some corrections, clarification, and improvements.

Updates on processing rules for Add or Update PIN. Updated and added conditions and usage notes for Add or Update WIC Vendor File. Added values and descriptions to Function Return Code. Added values and descriptions to WIC MIS System ID. Updates to Report Card Updates.

2.13 4/24/2017 Added new Validate PIN method. 2.14 7/11/2017 Added usage notes to Add or Update WIC Vendor File.

Added usage notes to Add or Update UPC/PLU Information. Added values and descriptions to Report WIC Benefits. Added values and descriptions to Appendix A Data Dictionary. Added value to Function Return Code.

2.15 7/27/2017 Minor updates for clarity. Updated Definitions and Acronyms table.

6


1.2 Definitions and Acronyms Acronym or Term Definition ACH Automated Clearing House. An electronic network for financial transactions in the

United States. Adjustment A special transaction that modifies benefits or payment amounts in relation to a

previous transaction that was either processed in error or processed in a manner deemed to be “unfair” to one party in the transaction.

APL Authorized Product List. A listing of approved products provided to retailers by WIC authorities.

BDK Base Derivation Key. A static key stored on a PIN pad device, which is used to derive unique keys for encrypting data.

Benefit A product provided by the WIC State Agency to a WIC participant. For the purposes of this system, a WIC benefit is an authorized food product.

Benefit Period A time period during which WIC benefits may be redeemed. This includes the beginning benefit availability and ending benefit availability dates.

BIN Bank Identification Number (also known as IIN). It identifies the major industry (e.g., finance or banking) and the card issuer.

BKLK Base Key Loading Key. A key used to encrypt keys stored on a PIN pad device. Broadband Subcategory This is subcategory 000. UPCs can be specified under the broadband subcategory

only, a specific subcategory (subcategory greater than 000), or under both the broadband subcategory and one specific subcategory. This allows the WIC State Agency to issue specific food items via a specific subcategory to a participant in a food prescription. Another participant’s nutritional needs may allow a greater choice of food items within a category (e.g., milk). In this case, this food prescription issuance is made via the broadband subcategory. Since a household’s food benefits are aggregated on the card, in some cases UPCs may be redeemed via both the broadband and specific subcategories.

Card Acceptor Terminal A number that uniquely identifies a card terminal (i.e., the POS device in the store). Cardholder The individual who is in possession of the WIC EBT card for a household. Category A grouping of WIC authorized food products, such as milk or formula CMS Clinic Management System. CDP’s WIC certification and management information

system. CVB Cash Value Benefit Discount A reduction in the total redemption transaction amount due to a coupon and/or

store promotion. DUKPT Derived Unique Key Per Transaction EBA Electronic Benefit Account EBT, eWIC Electronic Benefits Transfer. The electronic transfer of government benefits to

individuals through the use of card technology and point-of-sale terminals. Exchange Size The amount that is decremented from a balance upon the purchase of a product. Expungement Period The number of days after which an unused benefit is removed. FMNP Farmers Market Nutrition Program FNS Food and Nutrition Service Generator Date Begin/End A date range applied to the date/time assigned by the message initiator, such as a

specific retailer. HGTN Host Generated Trace Number. The unique trace number assigned to a transaction

by the host server. IIN Issuer Identification Number. A six digit number that is unique to a single card issuer. IVR Interactive Voice Response. An automated phone system that allows WIC

participants to obtain current account and benefit information. KSI Key Set Identifier. The first N digits of the KSN.

7


Acronym or Term Definition KSN Key Serial Number. A number stored on a PIN pad device that is incremented each

time a PIN is entered. The KSN and BDK together are used to derive a key that is used to encrypt a PIN.

Merchant See Retailer MIS Management Information System. A state’s WIC certification and management

information system. NTE Not to Exceed Price. WIC authorities establish the maximum price that the state will

reimburse for an approved WIC item. PAN Personal Account Number. The PAN is a 16-19 digit numeric field that provides the

means of identifying the issuing state and the recipient to whom the card was issued.

Participant The individual to whom WIC benefits are issued. PIN Personal Identification Number. An alphanumeric code issued to or selected by a

cardholder, which must be utilized by the cardholder in conjunction with a card to initiate a transaction.

PLU Price Look-Up Code. A store-assigned numeric designation for products that are typically of variable measure (e.g., meat, seafood, fruits, grains).

POS Point of Sale. An electronic device used by retail businesses to process credit and debit transactions.

Receiver The entity that receives a file or transaction request. Retailer A dealer in foodstuffs, meats, produce, and dairy products. In the context of this

document, the term also covers any parties authorized by the state to be a vendor of WIC-approved items, or who perform WIC-related computing or financial transactions for them.

S&F Store and Forward. The process by which a WIC retail transaction is stored during a system disruption, and then forwarded to the EBT host when service is restored.

SOAP Simple Object Access Protocol. A protocol standard used for exchanging information in computer networks.

STAN System Trace Audit Number. A number assigned by the message initiator to uniquely identify a transaction.

Subcategory A specific type of authorized food product within a WIC category. For example, subcategories for milk include whole milk and skim milk. Subcategories can be either broadband (code 000) or specific (codes greater than 000).

Transaction Any event that effects change to the eWIC database. This includes participant balance inquiries and WIC redemptions.

Transaction Time The date and time when the transaction occurred. UI User Interface Unit of Measure The measurements used for WIC-approved products that are stored in eWIC . UPC Universal Product Code. The code used to identify retail items, including WIC-

approved items. It is represented by a bar code. USDA United States Department of Agriculture Vendor See Retailer WIC Women, Infants, and Children. A special supplemental nutrition program for

Women, Infants, and Children. WIC State Agency A governmental organization that oversees the WIC program for a jurisdiction, such

as a state or tribal organization. A WIC Authority is responsible for issuing WIC food benefits.

WIC-allowable, WIC-eligible

An FNS designation. A WIC-allowable or WIC-eligible food item meets federal WIC dietary and nutritional standards and guidelines.

WIC-approved, WIC- A WIC State Agency designation. A WIC-approved or WIC-authorized food item is an

8


Acronym or Term Definition authorized item identified as WIC-allowable or WIC-eligible by FNS and approved or authorized

by the WIC State Agency for purchase with WIC benefits. WIC Host An information system that manages data exchange between a retailer and a WIC

State Agency. The WIC host includes communication, database, file posting, security authorization, and may include terminal application downloads. Electronically, it acts as a proxy for a WIC State Agency in the processing of WIC EBT benefits and redemptions.

WSDL Web Service Definition Language. A format used to describe the specific layout of messages using SOAP.

WUMEI WIC Universal MIS to EBT Interface X9.93 The standard that defines the message and file formats used in performing WIC EBT

transactions. XML Extensible Markup Language XSD XML Schema Definition

9


2 Introduction

2.1 Document Purpose

This document describes WIC Direct’s implementation of the Universal Interface between the WIC Management Information Systems (WIC MIS) and eWIC . The interface is based upon the WIC Universal MIS – EBT Interface - Functional Requirements – Version 3 November 2014 (WUMEI) document, the Technical Implementation Guide (TIG), and related bulletins which are available from the USDA-FNS.

The document defines and describes those interfaces currently supported by eWIC . It provides a description of:

The types of interfaces between the WIC MIS and eWIC .

The functions supported by eWIC .

The core data elements required by the defined functions.

The processing rules to be implemented to support the functions.

10


3 Interface Types When first implementing a WIC EBT system or when replacing a WIC EBT system, a WIC State Agency chooses a system based on an analysis of the functions and types of interfaces offered that best work within the capabilities of its WIC MIS environment. The types of WIC EBT and WIC MIS interfaces described in this document are:

Message Based System interface – the systems exchange messages to perform the function. Message based system interfaces are used for performing real time transfers of data between The WIC MIS and WIC EBT systems.

Batch System interface – the systems exchange batches containing data to perform the function.

The message based system interface and batch system interface types may be used independently or in combination depending on the needs and preferences of the MIS developer. The following sections describe each type of interface and the common data elements for each type of interface. Throughout the document, data elements used in a specific function are listed in alphabetic order.

The common data elements are defined in Appendix A - Data Dictionary. The condition codes used in the data element tables shown in each function are:

Condition Code Description M (Mandatory) – Indicates that a data element is mandatory in both directions of the

interface and may not be NULL. ME (Mandatory Echo) – Indicates that a data element is required to be echoed from the

previous message(s). C (Conditional) – Indicates that if the condition identified applies, then the data element

shall be present, otherwise its inclusion is subject to bilateral agreement. If a data element is not present, the default value indicated shall be used with fixed length data elements to fill the position for the data element. For alphanumeric and alpha data elements, the default values shall be spaces, unless otherwise indicated. For numeric data elements, the default value shall be zeroes, unless otherwise noted.

CE (Conditional Echo) – Indicates that if the data element was supplied in the request message, then the data element is echoed in the response message.

O (Optional) – Indicates that a data element is optional and may be NULL. For update functions, if the field has an existing value and that value is to be preserved, then the existing value shall be supplied as a data element in the update function. A value of null will cause the existing value to be overwritten with null. The use of data elements indicated as optional shall be decided by bilateral agreement.

N/A (Not applicable) – Indicates that the data is not currently implemented and will be NULL.

3.1 Message Based System Interfaces WIC regulations require “same day service” for WIC Participants which means that once notice of certification is provided, the WIC Participant may leave the clinic with benefits and shop at an authorized WIC Vendor location. Consequently, many of the functions performed between the

11


WIC MIS and the WIC EBT systems, such as account set up or benefit issuance, require a real time, message based system interface. A requirement for the Universal Interface is to make access to WIC EBT functions seamless to a user in the WIC clinic and to allow the use of the WIC EBT system to be driven by the WIC MIS user.

Some MIS designs permit remote or disconnected clinic operations. These MIS may still use a message based interface although some functions may not be fully completed until the MIS is connected to the WIC EBT or WIC State Agency system.

Message based system interfaces shall have the WIC MIS invoke WIC EBT functions by sending a message to the WIC EBT system. The WIC MIS provides the user interface, when appropriate, that either gathers the data necessary to execute a WIC EBT function or presents the results of a WIC EBT query to the clinic user. The response in a message based interface may be one or more messages providing the requested data.

eWIC supports a web service implementation of this ICD using Simple Object Access Protocol (SOAP). The eWIC team will provide access to end point that implements this ICD using a SOAP interface. The end point will access a Web Service Definition Language (WSDL) file that defines the specific implementation of the messages in this ICD as SOAP messages.

3.1.1 Data Required in All Message Based System Interfaces The following list of data elements and their associated condition codes (CC’s) will be included in both directions of the messages exchanged in a message based system interface. See Appendix A - Data Dictionary for definitions. This record shall appear as a Message Header Object.

Data element name

Condition sending

Condition responding

Usage Notes

Clinic ID O CE If provided, this is the ID of the clinic that initiates the request (rather than the ID of the clinic to which the household belongs)

Date and time, transmission

M ME

Function return code

N/A M May be used to explicitly indicate that a message was received and the result of processing the message; See Appendix B.2 for values

Initiating user ID O CE Local agency ID O CE If provided, this is the ID of the local agency that initiates

the request (rather than the ID of the local agency to which the household belongs)

Message type M ME Message type, see Appendix B.8.1 ICD message version M ME ICD version, see Appendix B.11 Password M ME Unique EBT transaction identifier

M ME This value must be unique in every request that updates or adds data and shall not be repeated. Uniqueness is not enforced for read operations. If a request is declined, then a new value must be supplied on resubmission.

12


Data element name

Condition sending

Condition responding

Usage Notes

Username O CE WIC EBT system ID M ME See Appendix B.12 WIC MIS system ID M ME See Appendix B.13 WIC state agency ID M ME Workstation ID C CE Mandatory if Clinic ID present and nonzero

3.1.2 Message Processing Standards The following processing standards shall be applied to processing done with a message system interface.

Rule ID Description 3.1.2.1 The WIC EBT system and the WIC MIS shall maintain the necessary computer hardware

and software to interface directly with data processing facilities required to accommodate message based system interfaces.

3.1.2.2 All message based system interface messages shall be processed and responded to within 20 seconds.

3.1.2.3 If the condition specified for a data element is not met, the data element may be omitted from the message.

3.1.2.4 The receiver shall validate uniqueness of the Unique EBT transaction identifier from a given originator.

3.1.2.5 The receiver shall validate the WIC MIS system ID and Password combination is valid. 3.1.2.6 If a data is shown as optional, the sender may or may not provide the data element at

their discretion.

3.2 Batch System Interfaces A batch system interface is used for the transfer of bulk data between the WIC MIS and WIC EBT system and to synchronize data stored in separate locations. This may be a two-way data flow, with some of the transfers being initiated by the WIC MIS and others by the WIC EBT system.

Use of this form of system interface is left to the WIC State Agency and the MIS developer and depends upon where certain WIC EBT related functions have been implemented. In some instances, a message based system interface may be used instead of, or in addition to, a batch system interface.

eWIC supports an Extensible Markup Language (XML) implementation for files defined in this ICD. The eWIC team will provide an XML Schema Definition (XSD) that defines the specific implementation of the files in this ICD as XML files.

3.2.1 Data Required in All Batch System Interfaces The following list of data elements and their associated condition codes (CC’s) shall be included in all files exchanged. See Appendix A - Data Dictionary for definitions. The object name is BatchFileHeader.

Data element name Condition Usage Notes

13


Data element name Condition Usage Notes Count, detail records M Date and time, transmission

M File create date and time

File type M Code identifying the type of file see Appendix B.10; used in lieu of File name field from WUMEI

File sequence number M eWIC will validate that the sequence number is unique for the given File Type and Originator of file. An error returned if a duplicate number is received for a previous file that was not entirely rejected.

ICD version M ICD version, see Appendix B.11 Originator of file M Sender of file (WIC EBT system ID or WIC MIS System ID) Receiving institution M Receiver of file (WIC EBT system ID or WIC MIS System ID) Type Code M Type code, see Appendix B.8; always use “U” for Update file WIC state agency ID M

The following is a list of data elements that will appear in every detail record in a batch file. The elements will be packaged into a DetailRecordHeader object:

Data element name Condition Usage Notes Record sequence number M A Record sequence number shall appear as a mandatory data

element in each detail record included in the batch file. Username O Mandatory if record was created as the result of an action by a

user. Workstation ID O

3.2.2 Confirmation File Format All batch files should be acknowledged with a batch confirmation file. The batch confirmation file will include header followed by detail records of erroneous records (if any) from the original file. A file with no errors is acknowledged by a confirmation file with only a header.

The following is a list of data elements included in the header record for a confirmation file. The object name is BatchConfirmationFileHeader.

Data element name Condition Usage Notes Count, detail records M Echoed from original file Date and time, transmission

M File create date and time

File type M Echoed from original file File sequence number M Echoed from original file ICD version M ICD version, see Appendix B.11 Originator of file M Sender of file (WIC EBT system ID or WIC MIS System ID) Receiving institution M Receiver of file (WIC EBT system ID or WIC MIS System ID) Rejected row count M Number of rows rejected from original file Type Code M Echoed from original file WIC state agency ID M

The following is a list of data elements included in the detail records for a confirmation file. The object name is BatchConfirmationRejectedDetail.

14


Data element name Condition Usage Notes Function return code M See B.2 for values Original line number M The line number from the original file with an error. Each line in

a file is terminated with a “CR” and/or “LF” character. Record sequence number M The record sequence number of the record from the original file

with an error

3.2.3 Batch Processing Standards The following processing standards shall be applied to processing done with a batch system interface.

Rule ID Description 3.2.3.1 A confirmation shall be provided to the sending party that the file was received for the

files listed. The confirmation may take the form of a return file. 3.2.3.2 Batch level errors (e.g. wrong record count, etc.) shall be reported to the sending party

in a confirmation file. 3.2.3.3 Detail record errors (e.g. provide specific record identifier and indication of specific

error) shall be reported to the sending party in a confirmation file. 3.2.3.4 Batches may be transmitted on an as needed or periodic basis e.g., daily or monthly. 3.2.3.5 A batch with a header and no detail records shall indicate that no action is to be taken

by the receiving system. 3.2.3.6 If the condition specified for a data element is not met, the data element may be

defaulted to NULL or the default value indicated in the Data Dictionary. 3.2.3.7 For files consumed by eWIC will create a confirmation file within five (5) minutes of

receiving the original file.

3.2.4 File Naming Standards All files shall be named according to the following convention: [YYMMDDHHMMSS].<File Extension> where [YYMMDDHHMMSS] corresponds to the date and time that originator creates the <File Extension> is the unique file extension assigned to the type of file being created. See Appendix B.10 for a listing of file types and the associated extensions.

Confirmation files shall be the name of the original file with “.c” included after the [YYMMDDHHMMSS] element.

All files incoming to eWIC (including confirmation files) may also be individually zipped if desired in order to reduce bandwidth usage and transfer times. The content of the zip file archives shall contain only one file and shall also not have any additional folder structure. The zip files themselves shall be named according to the conventions above with “.zip” appended to the end of the file name, and the file within the archive shall be named according to the conventions above.

15


4 Interface This section describes each functional area and their related functions. Each description of a functional area is organized as follows:

1. Description – Describes the functional area.

2. Functions – A table listing the functions implemented for the functional area, whether thefunction is required or optional in an implementation, the system interface type used forthat function and the party responsible for originating the function.

The function table is followed by subsections for each function organized as follows:

1. Description - There is a brief description of the function.

2. Data elements - There is a table of input data elements for the function. The table onlycovers the core data elements needed for the specific function. The table contains thefollowing columns:

a. Data element name – Name of the data element as it appears in the Data ElementDictionary.

b. Data element condition code (“Condition”) – Indicates whether the data element isMandatory (M), Conditional (C) or Optional (O)

c. Usage notes – Explains the condition or requirements of data element usage.

3. Processing Rules – Any processing rules governing the function are listed.

4.1 WIC EBA Account Maintenance The WIC EBA Account Maintenance functional area comprises functions for maintaining an Electronic Benefit Account (EBA) in eWIC . An EBA is account data maintained either on the WIC EBT host (WIC Online EBT) or on the chip in the Smart Card (WIC Smart Card EBT) in combination with data maintained at the WIC EBT system (WIC Smart Card EBT). The EBA is linked to an account on the WIC MIS using the WIC MIS account (MSA) ID. An EBA ties together all of the various data elements required to enable WIC EBT for a WIC account, such as benefit information, card data and transaction history. The EBA is updated when card information is changed, such as when a card is replaced.

4.1.1 Add EBA The Add EBA function is a required function that uses a message based system interface to establish an EBA in the WIC EBT System and link the EBA to a WIC account from the WIC MIS. To establish an EBA account, only the WIC MIS account ID is required. The WIC EBT System expects that the WIC MIS shall perform any necessary checks for dual participation. The addition of cards and cardholders is described in 4.3.1. The following table lists the data elements sent for the Add EBA function:

Data element name Condition Usage Notes Head of household object C See Appendix C.4. Required if the State Agency is configured for

IVR – household zip (see Appendix D -Configurability).

16


Data element name Condition Usage Notes Reason code O Default to “E001 – new”; see Appendix B.6 for values. Type code M WIC MIS account type (Household, Emergency Disaster,

Compliance buy, Vendor), see Appendix B.8 for values WIC MIS account ID M

The following table lists the processing rules for the Add EBA function:

Rule ID Description 4.1.1.1 Validate that the WIC MIS account ID does not already exist for calling WIC State

Agency (not necessarily applicable for WIC Smart Card EBT system). 4.1.1.2 The Type code assigned when adding an EBA cannot be changed. The account must be

deactivated and a new EBT account established.

The following table lists the processing rules specific to Reason code and Status code:

Reason code (send)

Status code (result)

Notes

Any valid value A001 (Activated)

The Reason code is validated but not recorded or used in any processing.

4.1.2 Update EBA The Update EBA function is a required function that uses a message based system interface to change the head of household date of birth, name, or address that is held in the WIC EBT database and/or to update an EBA with a new WIC MIS account ID. It is also used to change the status of an EBA by deactivating or reactivating or placing on hold an EBA in the WIC EBT system as indicated by the Action code. The WIC MIS account Type code for an EBA should not be changed using this function; instead the account should be deactivated and a new one with the correct type established. It is recommended that WIC MIS support unique WIC MIS account IDs statewide. The following table lists the data elements sent for the Update EBA function:

Data element name Condition Usage Notes Action code M Update, Deactivate, Hold, etc. See Appendix B.1 for values Date, effective O While eWIC will accept this data element, the requested

action is still effective immediately. eWIC does not honor the future data on a requested action.

Head of household object C See Appendix C.4. Required if the State Agency is configured for IVR – household zip (see Appendix D -Configurability).

Reason code O See B.6 for values. WIC MIS account ID M WIC MIS account ID, new O If present, this WIC MIS account ID will be associated to the EBA

and the old WIC MIS account ID will be deactivated.

The following data elements are returned for the Update EBA function:

Data element name Condition Usage Notes Status code M Indicates result, Activated, Deactivated, etc. See Appendix B.7 for

values

17


The following table lists the processing rules for the Update EBA function:

Rule ID Description 4.1.2.1 Validate that the (OLD) WIC MIS account ID exists. 4.1.2.2 If a (NEW) WIC MIS account ID is provided, then the WIC EBT System shall validate that

the WIC MIS account ID, new does not already exist. 4.1.2.3 If a WIC MIS account ID, new is provided, then the WIC EBT System shall deactivate the

(OLD) WIC MIS account ID. 4.1.2.4 If the WIC MIS account ID is deactivated, the WIC EBT System shall purge the

remaining benefits when they expire.

The following table lists the processing rules specific to Action code, Reason code, and Status code:

Action code (send)

Reason code (send)


Notes

001 (Activate) N/A N/A Not allowed 002 (Update) 005 (Reactivate)

Any valid value

A001 (Activated)

An Action code of 002 or 005 causes the EBA Status Code to be set to A001. The Reason code is validated but not recorded or used in any processing.

003 (Deactivate) 006 (Hold)

Any valid value

A002 (Deactivated)

An Action code of 003 or 006 causes the EBA Status Code to be set to A002. The Reason code is validated but not recorded or used in any processing.

4.1.3 Get EBA Details The Get EBA Details function is a required function that uses a message based system interface to return detailed information on the EBA. This function allows a WIC MIS user the ability to have EBA information displayed via a WIC MIS screen. The WIC EBT System shall identify the EBA and return the household data information available.

The following table lists the data elements sent for the Get EBA Details function:

Data element name Condition Usage Notes Type code O WIC MIS Account type, default “Household”, see Appendix B.8

for other values WIC MIS account ID M

The following data elements are returned for the Get EBA Details function:

Data element name Condition Usage Notes Head of household object C Mandatory if provided when the EBA was added or updated (See

Appendix C.4) Status code M Status code assigned when EBA was last updated, see Appendix

B.7 for values Type code M Type code assigned when EBA was added, see Appendix B.8 for

values WIC MIS account ID M

The following table lists the processing rules for the Get EBA function:

Rule ID Description

18


Rule ID Description 0.1 Validate that the WIC MIS account ID exists.

4.2 WIC EBA Benefit Maintenance The WIC EBA Benefit Maintenance functional area comprises functions for maintaining and querying benefit information associated with the EBAs in the WIC EBT System.

4.2.1 Add or Update Benefits The Add or Update Benefits function is a required function that uses a message based system interface to add (issue) or subtract (void) a Benefit quantity from an EBA. Issuing benefits results in an addition (credit) to the WIC Cardholder’s benefits; voiding benefits results in a subtraction (debit). Current and future benefits may be issued, voided or placed on hold by using the Date, begin benefit and Date, end benefit data elements in this function.

A unique Benefit issuance ID is assigned to benefits at the WIC MIS account ID level when issued.

The following table lists the data elements sent for the Add or Update Benefits function:

Data element name Condition Usage Notes Action code M Issue (add) or Void (subtract); see Appendix B.1 for values.

eWIC currently does not support placing benefits on Hold. Card number O WIC MIS account ID M Reason code O New, Request, Withdrawal, etc. See Appendix B.6 for values A list of the following elements may appear: Benefit issuance ID C Required if the transaction is an Issue (add). Assigned by the MIS

system. Date, begin benefit C Required if the transaction is an Issue (add). Date, end benefit M A list of the following elements are repeated for each Benefit issuance ID: Benefit quantity M Category code M Category long description O Sub-Category code M Sub-Category long description

O

The following table lists the processing rules for the Add or Update Benefits function:

Rule ID Description 4.2.1.1 Validate that the WIC MIS account ID exists and is active. 4.2.1.2 Validate that the combination of Category code and Sub-Category code is valid for the

WIC State Agency. 4.2.1.3 The WIC MIS shall perform a balance inquiry before updating benefits. 4.2.1.4 If the transaction is a subtraction (void): a) Date, end benefit shall exactly match the

Date, end benefit for the benefits to be debited or the transaction is rejected; b) if the optional Benefit issuance ID and/or Date, begin benefit is provided then these field values shall exactly match the Benefit issuance ID and/or Date, begin benefit for the

19


Rule ID Description benefits to be debited or the transaction is rejected.

4.2.1.5 If the transaction is a subtraction (void), then the WIC EBT System shall only perform the subtraction if there is sufficient balance to post the entire subtraction. Partial approvals of void requests are not allowed.

4.2.1.6 If the transaction is an addition (issue), then there shall be a validation that the total Benefit quantity (units) available for the Category code and Sub-Category code on a given date shall not exceed the maximum balance (999.99).

4.2.1.7 Validate that EBA exists and is active 4.2.1.8 If the transaction is a subtraction (void) (where the optional Date, begin benefits is not

provided) that spans multiple benefits with staggered Date, begin benefits, then the WIC EBT processor shall order the debit such that benefits with later Date, begin benefits are debited prior to benefits with earlier Date, begin benefits.

4.2.1.9 If the transaction is an addition (issue) and the State Agency is configured for Enforce unique benefit issuance ID, then eWIC will reject the addition if the Benefit issuance ID has already been used with a previous approved addition.

4.2.2 Get Benefit Balance The Get Benefit Balance function is a required function that uses a message based system interface to retrieve benefit information for a particular EBA. This function allows the WIC MIS to retrieve from the WIC EBT system the remaining balance for the EBA and display it via the WIC MIS.

The following table lists the data elements sent for the Get Benefit Balance function:

Data element name Condition Usage Notes Benefit issuance ID C Mandatory if a specific remaining balance in a specific Benefit

issuance ID is requested. Send “999,999,999,999” to request a balance broken down across all Benefit issuance IDs where benefits match the requested date range.

Card number C Mandatory if WIC MIS account ID not present Date, begin request O See 4.2.2.2 Date, end request O See 4.2.2.2 WIC MIS account ID C Mandatory if Card number not present

The following data elements are returned for the Get Benefit balance function:

Data element name Condition Usage Notes Card number CE WIC MIS account ID CE Also, if the Card number was sent in the request and there is

balance data to return, then the WIC MIS account ID is also returned.

The following data is repeated for each Benefit issuance ID or date range: Benefit issuance ID C Mandatory if requested Date, begin benefit M Date, end benefit M The following data is repeated for each Category code and Sub-Category code: Benefit quantity, active hold

M

Benefit quantity, available M Depleted benefits (i.e. items with Benefit quantity available = 0) are returned

20


Data element name Condition Usage Notes Category code M Sub-Category code M

The following table lists the processing rules for the Get Benefit Balance function:

Rule ID Description 4.2.2.1 Validate that the WIC MIS account ID exists. 4.2.2.2 If Date, begin request, Date, end request and Benefit issuance ID are not provided, then

the WIC EBT System shall only return records where the current date is between the Date, begin benefit and Date, end benefit.

4.2.2.3 The Category code long description, Category code short description, Sub-Category code long description and Sub-Category code short description data shall be maintained in the MIS and EBT system.

4.2.3 Get Benefit Maintenance History The Get Benefit Maintenance History function is a required function that uses a message based system interface to retrieve benefit maintenance transaction data for a particular EBA. This function allows the WIC MIS to retrieve from the WIC EBT system the benefit maintenance transaction history for a given period for the EBA and display it via the WIC MIS. This function may also be used by the WIC EBT system to retrieve information from the WIC MIS. Any filter parameter values sent with this function will result in the return values being filtered to just those items that match. All benefit additions, voids, and purges may be retrieved using this function. The retention period for benefit data shall be defined by bilateral agreement.

The following table lists the data elements sent for the Get Benefit Maintenance History function:

Data element name Condition Usage Notes Card number C Mandatory if WIC MIS account ID not present Date, begin request M Date, end request M Type code O Used to request specific types of maintenance (Add, Void,

Purged), see Appendix B.8 for values WIC MIS account ID C Mandatory if Card number not present

The following data elements are returned for the Get Benefit Maintenance History function:

Data element name Condition Usage Notes Action code C Add or subtract; see Appendix B.1 for values, echoed from

the original message if the benefit update was initiated by the MIS using Add or Update Benefits (purges are not typically MIS initiated)

Card number C Echoed from original message if present Clinic ID C Echoed from original message if present Date and time, transmission (host)

M

Initiating user ID C Echoed from original message if present Local agency ID C Echoed from original message if present Reason code C Echoed from original message if present

21


Data element name Condition Usage Notes Type code M Valid types are:

E - Expunged/expired I – Issuance/Add D – Void/Subtract

Unique EBT transaction identifier

M

Username N/A WIC MIS account ID M Workstation ID C Echoed from original message if present Multiple month’s benefits may be added/voided for each WIC MIS account ID and/or Card number. The object name is UniqueIssuanceObject. Benefit issuance ID M Date, begin benefit M Date, end benefit M A list of the following elements are repeated for each Benefit issuance ID. The object name is UniqueIssuanceObjectDetailObject. Benefit quantity M Category code M Category long description N/A Note that the data element is returned as a nil element. Sub-Category code M Sub-Category long description

N/A Note that the data element is returned as a nil element.

The following table lists the processing rules for the Get Benefit Maintenance History function:

Rule ID Description 4.2.3.1 Validate that the WIC MIS account ID exists. 4.2.3.2 If both WIC MIS account ID and Card number are sent, then the values must both

belong to the same account. 4.2.3.3 If WIC MIS account ID is sent, return all benefit maintenance history for the household. 4.2.3.4 If Card number is sent, return all benefit maintenance history for the card. 4.2.3.5 If identified by the EBT System when added or voided, Type code may be used to

indicate future benefits. 4.2.3.6 Validate that the Date, begin request to Date, end request timeframe is not greater

than the timeframe configured by the WIC State Agency in the Maximum search range – Get Benefit Maintenance History setting (see Appendix D - Configurability).

4.2.4 Get Benefit Redemption History The Get Benefit Redemption History function is a required function that uses a message based system interface to retrieve benefit redemption data for a particular EBA. This function allows the WIC MIS to retrieve from the WIC EBT system the benefit redemption history for a given period and a specific transaction type for the EBA and display it via the WIC MIS. Any filter parameter values sent with this function will result in the return values being filtered to just those items that match. Only transactions where redemption was attempted or completed (including those adjusted) are reported.

The following table lists the data elements sent for the Get Benefit Redemption History function:

22


Data element name Condition Usage Notes Card number C Mandatory if WIC MIS account ID not present Date, begin request M Date, end request M Type code O Used to request specific types of maintenance (Add, Void,

Purged), see Appendix B.8 for values WIC MIS account ID C Mandatory if Card number not present WIC MIS vendor ID O If provided, only transactions for the specified WIC vendor are

retrieved

The following data elements are returned for the Get Benefit Redemption History function:

Data element name Condition Usage Notes Acquiring institution ID code

M Identifies entity that obtained the transaction from the WIC Vendor

Amount, discount M The absolute value of the amounts deducted from the gross amount of the transaction due to coupons or other reductions in the amount

Amount, paid M The Amount, paid at the transaction level shall equal the sum of the Amount, paid of all of the reported line items less the Amount, discount at the transaction level. Also, Amount, paid = Amount, transaction - Amount, discount - Amount, total adjustments.

Amount, total adjustments M The sum of all adjustments to the reported line items. Includes adjustments to the transaction for NTE price or other adjustments.

Amount, transaction M The original requested amount. The amount of the transaction before any adjustments or discounts.

Card acceptor identification code

C Mandatory if data element included in transaction from retailer

Card acceptor terminal identification code


Card number M Date and time, host M Date and time, local transaction

M

Date, business M Date, settlement M As recorded by the EBT system Forwarding institution ID code

M Identifies entity that submitted the transaction for payment

Host generated trace number

M Identifies the Host generated trace number that was assigned to the transaction being reported; for redemptions being reported it contains a host assigned unique identifier (e.g., an approval code or Systems trace audit number). This field is referred to as Unique EBT transaction ID in WUMEI.

Initiating user ID N/A Message reason code C Mandatory if the transaction represents an adjustment.

(eWIC does not currently utilize this field. This field will be included in the response message, but will remain uninitialized for now. When eWIC implements more formalized adjustment processing, eWIC will begin populating this field.)

23


Data element name Condition Usage Notes Original host generated trace number

C For a reversal, refers to the original transaction

POS data code, card data input capability

M

POS data code, cardholder authentication capability

M

POS data code, card capture capability

M

POS data code, operating environment

M

POS data code, cardholder present

M

POS data code, card present

M

POS data code, card data input mode

M

POS data code, cardholder authentication method

M

POS data code, cardholder authentication entity

M

POS data code, card data output capability

M

POS data code, terminal output capability

M

POS data code, PIN capture capability

M

Systems trace audit number

M

Transaction reason code M Value is the action code (bit 39) for WIC Online EBT and will always be set to “000” or “002”; see Technical Implementation Guide for corresponding values. eWIC currently only supports the return of approved (or partially approved) redemptions.

Type code M Indicates transaction type (Purchase, Void, Adjustment, etc.); See Appendix B.8 for values

WIC MIS account ID M WIC MIS WIC Vendor ID M WIC Vendor peer group ID M Workstation ID N/A The following data elements will be repeated for each food item purchased. The object name is RedemptionDetailObject. Amount, item discount M Amount, NTE adjustment C Mandatory if line item includes an NTE adjustment Amount, recoupment adjustment

C Mandatory if line item includes a recoupment adjustment

Amount, paid M The amount paid to a WIC vendor for a purchase transaction for the specific item purchased less any adjustments. The Amount, paid is equal to the requested Item price as adjusted for NTE and recoupment, times the approved Purchase quantity and cannot be less than zero.

24


Data element name Condition Usage Notes Benefit issuance ID M Original value from the benefits issued at the

WIC MIS account ID level Benefit unit description M Only first 6 characters are significant (this is the same as the Unit

of measure field in the WUMEI that is optional). Category code M Category code of the benefit applied to the item Category long description N/A Clinic ID C Clinic ID of location that issued the benefit, echoed from original

message if present Date, begin benefit M Date, end benefit M Item action code M Item description M Item price M The item price after any adjustments are applied, i.e. Item price

= Original item price - Amount, item discount - Amount, NTE adjustment - Amount, recoupment adjustment

Line item ID C Mandatory when a single food item in a purchase requires multiple reporting records to account for applying units across Sub-Categories or Benefit IDs.

Local agency ID C Local agency ID for location that issued the benefit, echoed from original message if present

Original amount M The amount requested by a WIC vendor for a purchase transaction for the specific item purchased. The Original amount is equal to the requested Item price times the approved Original purchase quantity and cannot be less than zero.

Original category code M Category code assigned to the UPC or PLU Original item price M The requested item price before any adjustments Original purchase quantity M The quantity requested as prorated for the specific amount of

benefit units redeemed Original sub-category code M Sub-Category code assigned to the UPC or PLU Package size C The size of the contents of the package quantified in the

standard benefit units of measure Purchase quantity M The quantity approved as prorated for the specific amount of

benefit units redeemed Sub-Category code M Sub-Category code of the benefit applied to the item Sub-Category long description

N/A

Units M Number of units of benefit of this item redeemed UPC/PLU data M UPC/PLU data length M

The following table lists the processing rules for the Get Benefit Redemption History function:

Rule ID Description 4.2.4.1 Validate that the WIC MIS account ID exists. 4.2.4.2 If both WIC MIS account ID and Card number are sent, then the values must both

belong to the same account. 4.2.4.3 If WIC MIS account ID is sent, return all benefit redemption history for the Household. 4.2.4.4 If Card number is sent, return all benefit redemption history for the card.

25


Rule ID Description 4.2.4.5 Transactions utilizing multiple Benefit issuance IDs or where redemption straddles the

Sub- Category code and Broadband Sub-Category code shall report all details for each food item redeemed.

4.2.4.6 Validate that the Date, begin request to Date, end request timeframe is not greater than the configured by the WIC State Agency in the Maximum search range – Get Benefit Redemption History setting (see Appendix D - Configurability).

4.3 Cardholder/Card Maintenance The Cardholder/Card Maintenance functional area comprises functions for maintaining WIC Cardholders and their cards in the WIC EBT System. WIC Cardholders and cards are required to access WIC EBT benefits associated with an EBA in the WIC EBT System.

A WIC Card is issued to a WIC Cardholder. The WIC Cardholder may be the WIC Participant, i.e., the person receiving the benefit, or a proxy such as a parent or caretaker for a child. The WIC Card may contain benefits (WIC Smart Card EBT) or may be linked to benefits (WIC Online EBT) for one or more WIC Participants identified by a WIC MIS account ID. A WIC MIS account ID may include one or more WIC Participants however a single EBA is provided to avoid confusion when redeeming benefits.

4.3.1 Add Cardholder/Card The Add Cardholder/Card function is a required function that uses a message based system interface to create a WIC Cardholder and an associated Card number.

The following table lists the data elements sent for the Add Cardholder/Card function:

Data element name Condition Usage Notes Cardholder Object M See Appendix 0 WIC MIS account ID M

The following table lists the processing rules for the Add Cardholder/Card function:

Rule ID Description 4.3.1.1 Validate that the WIC MIS account ID exists and is active. 4.3.1.2 If the cardholder Type code is “Primary”, then the WIC EBT System shall validate that

there is not already an active primary cardholder associated with the given household. 4.3.1.3 If the cardholder Type code is “Secondary”, then the WIC EBT System shall validate that

there is already a primary cardholder associated with the household. 4.3.1.4 If the cardholder Type code is “Secondary”, then the WIC EBT System shall validate that

the addition of the new cardholder will not exceed the maximum number of allowed cardholders per household.

4.3.1.5 If all validations are passed, then the WIC EBT System shall create a new cardholder record and associate the cardholder with the given card and household.

4.3.1.6 Validate that the Card number (in the Cardholder object) is not already issued.

The following table lists the processing rules specific to Reason code and Status code. Note that the Status Code is not used on the send.

26


Reason code (send)


Notes

Any valid value A001 (Activated)

The Reason code is not recorded or used in any processing.

4.3.2 Add or Update PIN The Add or Update PIN function is an optional function that uses a message based system interface to associate a PIN with the cardholder of the given card for WIC Online EBT PIN verification.

The following table lists the data elements sent for the Add or Update PIN function:

Data element name Condition Usage Notes Action code M Change, Unlock see Appendix B.1 for values Card number M PIN, encrypted C Required when used to select (change) a PIN.

The following table lists the processing rules for the Add or Update PIN function:

Rule ID Description 0.1 Validate that the Card number is active and associated with a valid EBA. 0.2 Validate that the PIN, encrypted is valid. 0.3 If the PIN, encrypted is supplied and is valid then the WIC EBT System Processor shall

translate the PIN, encrypted into a new PIN, encrypted that is suitable for internal database storage.

0.4 The PIN will be effective upon successful processing of the request by the WIC EBT system.

0.5 If the PIN, encrypted is supplied, then it must be sent in one of three available formats within this method:

1. The first format is for use with DUKPT encryption.a. The value supplied must be 32 characters long.b. The first 16 characters must be an unpadded (without the leading

“FFFF” value) KSN.c. The final 16 characters must be the DUKPT-encrypted PIN.

2. The second format is also for use with DUKPT encryption. This format allowsfor dual entry and validation of a PIN (for instance, if a given PIN device doesnot internally support this functionality). This format consists of two 36character parts. Those two parts are each made up of a separate KSN andDUKPT-encrypted PIN.

a. The value supplied must be 72 characters long.b. The first 20 characters must be the first padded KSN (by padded here

we mean with the leading “FFFF” value).c. The next 16 characters must be the first DUKPT-encrypted PIN.d. The next 20 characters must be the second padded KSN (by padded

here we mean with the leading “FFFF” value).e. The final 16 characters must be the second DUKPT-encrypted PIN.

3. The final format is for simple working key encryption.a. The value supplied must be 16 characters long.b. All 16 characters must be the PIN encrypted under the working key

currently assigned to the WIC MIS system ID presented in themessage header.

Note that if using the jQuery plug-in, then the PIN, encrypted field should consist exactly

27


Rule ID Description of the KSN and PinBlock fields concatenated together as returned from the GetPinInformation method in the jQuery PIN Pad Plug-In (see Appendix E - jQuery PIN Pad Plug-in).

0.6 When Action Code = Unlock, then the PIN counter of invalid PIN attempts shall be set to 0 by the WIC EBT system.

4.3.3 Validate PIN The Validate PIN function is an optional function that uses a message based system interface to validate a PIN against the set PIN for cardholder of the given card.

The following table lists the data elements sent for the Validate PIN function:

Data element name Condition Usage Notes Card number M PIN, encrypted M

The following table lists the processing rules for the Validate PIN function:

Rule ID Description 4.3.3.1 Validate that the Card number is active and associated with a valid EBA. 4.3.3.2 Validate that the PIN, encrypted is valid. 4.3.3.3 The PIN, encrypted value must be sent in one of three available formats within this

method: 1. The first format is for use with DUKPT encryption.

a. The value supplied must be 32 characters long.b. The first 16 characters must be an unpadded (without the leading

“FFFF” value) KSN.c. The final 16 characters must be the DUKPT-encrypted PIN.

2. The second format is also for use with DUKPT encryption. This format not onlyvalidates the PIN against the set PIN, but it also allows for dual entry andvalidation of the two entered PIN against each other (for instance, if a givenPIN device does not internally support this functionality). This format consistsof two 36 character parts. Those two parts are each made up of a separate KSNand DUKPT-encrypted PIN.

a. The value supplied must be 72 characters long.b. The first 20 characters must be the first padded KSN (by padded here

we mean with the leading “FFFF” value).c. The next 16 characters must be the first DUKPT-encrypted PIN.d. The next 20 characters must be the second padded KSN (by padded

here we mean with the leading “FFFF” value).e. The final 16 characters must be the second DUKPT-encrypted PIN.

3. The final format is for simple working key encryption.a. The value supplied must be 16 characters long.b. All 16 characters must be the PIN encrypted under the working key

currently assigned to the WIC MIS system ID presented in themessage header.

Note that if using the jQuery plug-in, then the PIN, encrypted field should consist exactly of the Ksn and PinBlock fields concatenated together as returned from the GetPinInformation method in the jQuery PIN Pad Plug-In (see Appendix E - jQuery PIN Pad Plug-in).

28


4.3.4 Update Card/Cardholder The Update Card function is a required function that uses a message based system interface to update the status and information on a WIC card or cardholder. It is used by either the WIC EBT system or the WIC MIS to advise the other that there has been a change in the card or cardholder information. If the card status is changed because it is reported lost or stolen, a WIC Smart Card EBT system shall add the card to the Hot Card List (HCL) that is provided to WIC Vendors and the card shall not be reactivated. The WIC Online EBT system maintains the card status on the EBA linked to the card.

If a cardholder does not know the Card number of the card that they are reporting as lost or stolen, the Get Cardholders/Cards or Get Cardholders/Cards by Household function may be used to retrieve the Card number.

The following table lists the data elements sent for the Update Card function:

Data element name Condition Usage Notes Action code M Activate, Deactivate, etc., see Appendix B.1 for values Cardholder Object M Card number, replacement

C New card number on a replacement. Mandatory if replacing card.

Date, effective M While eWIC will accept this data element, the requested action is still effective immediately. eWIC does not honor the future data on a requested action.

WIC MIS account ID O

The following table lists the processing rules for the Update Card function:

Rule ID Description 4.3.4.1 The card status is changed according to the rules listed in the table below. 4.3.4.2 Optional data elements are updated with the information provided. If a data element is

omitted, then the current value in eWIC is cleared and set to NULL. 4.3.4.3 Validate that card is active and assigned. For deactivations, card allowed to be inactive

only when the Reason code of C018 is used and only when Reason code of C018 wasn’t used originally for the deactivation in order to allow restrictions to be overlaid when needed.

4.3.4.4 Validate the identity of the individual reporting the card. 4.3.4.5 Validate that the Card number exists and has not been previously issued. 4.3.4.6 If a Card number, replacement is provided, then the Card number from the Cardholder

Object is deactivated (if it is not already deactivated). 4.3.4.7 (WIC Online EBT only) Since the PIN is associated with the cardholder, the PIN is

unchanged for the new replacement card. Note that the PIN may still be changed by invoking the Add or Update PIN function separately. (WIC Smart Card EBT only) The PIN is selected by the WIC cardholder.

4.3.4.8 If the Reason code is C018 (cancel and restrict access), then the card cannot be replaced. In other words, the card number cannot be used in the Card number field of the Cardholder Object in a subsequent call to Update Card/Cardholder when Card number, replacement is supplied. Note Add Cardholder/Card may be used to set up a

29


Rule ID Description new card associated with the EBA.

4.3.4.9 If a card is deactivated, then the card cannot be reactivated. 4.3.4.10 If the existing cardholder Type code is “Secondary”, then the WIC EBT System will not

allow the Type code to be updated to “Primary” if there is an active primary cardholder associated with the household.

The following table lists the processing rules specific to Action code, Reason code, and Status code. Note that the Status Code is not used on the send.

Action code (send)

Reason code (send)

Card number, replacement


Notes

001 (Activate) 005 (Reactivate) 006 (Hold)

N/A N/A N/A Not allowed

002 (Update) C011 or NULL NULL N/A This is the “update” path. The cardholder information is updated with the provided information in the Cardholder object. The Reason code and Status code (that is sent in the cardholder object) are not used for processing A replacement card number is not allowed for this path.

002 (Update) Any valid value other than C008 (not supported), C011 (reserved for the update path) or C018 (reserved for the deactivate path)

Any valid card number

A002 (Deactivated)

This is the “replacement” path. The card number associated with the cardholder is updated with the provided information in Card Number, replacement. The Status code (that is sent in the cardholder object) is not used for processing. The Reason code of the “old” card record is set to whatever is supplied and the Status code of the “old” card is set to A002. The Status code of the “new” card is A001.

003 (Deactivate) Any valid value other than C008 (not supported) or C011 (reserved for update path)

NULL A002 (Deactivated)

This is the “deactivate” path. An Action code of 003 causes the card Status Code to be set to A002. The Reason code is recorded but only used in processing when set to C018. In that case, the card may not be subsequently replaced.

4.3.5 Get Cardholders/Cards The Get Cardholders/Cards function is a required function that uses a message based system interface to get a list of cardholders and cards. It is designed to provide maximum flexibility to the WIC MIS and to support the varying methods that different systems may use to search for cards/cardholders. For those implementations where the WIC EBT system is the database of record for cards, this function allows the WIC MIS to access the WIC EBT system, obtain card and cardholder data associated with an EBA and display that data via the WIC MIS user interface.

30


The following table lists the data elements sent for the Get Cardholders/Cards function:

Data element name Condition Usage Notes Address, cardholder mailing

O If used, note that the formatting of address information may result in mismatches.

Cardholder relationship O Card number C Mandatory if WIC MIS account ID not present Date of birth, cardholder O Date, begin request O Ignored for this method Date, end request O Ignored for this method Name, cardholder O Status code C May only be used with an optional data element to request a

card in a specific status (Lost, Stolen, Valid, Activated, Deactivated, etc.); see Appendix B.7 for values.

Type code C May only be used with an optional data element to request a specific cardholder type (Primary, Secondary, Proxy); see Appendix B.8 for values

WIC MIS account ID C Mandatory if Card number not present

A list of the following data elements are returned for the Get Cardholders/Cards function:

Data element name Condition Usage Notes Cardholder object M PIN status code M WIC MIS account ID M Date, effective M

The following table lists the processing rules for the Get Cardholders/Cards function:

Rule ID Description 4.3.5.1 Validate that the Card number or card retrieved is associated with an EBA.

4.3.6 Get Card History The Get Card History function is a required function that uses a message based system interface to retrieve the history of the card, i.e., creation, status changes, updates. The request may be filtered by supplying one or more of the optional data elements in the request. Any filter parameter values sent with this function will result in the return values being filtered to just those items that match.

The following table lists the data elements sent for the Get Card History function:

Data element name Condition Usage Notes Card number C Mandatory if WIC MIS account ID not present Date, begin request M Date, end request M Type code O Cardholder type (Primary, Secondary, Proxy), see Appendix B.8

for values WIC MIS account ID C Mandatory if Card number not present

The following data elements are returned for the Get Card History function for each action performed:

31


Data element name Condition Usage Notes Action code M Action code indicated in original action being reported (Activate,

Deactivate, etc.) See Appendix B.1 for values Cardholder relationship C This is returned if the Cardholder relationship was provided with

Add Cardholder/Card or Update Card/Cardholder Card number M Card number, replacement

C Mandatory if Card number was replaced

Date and time, host M Date, effective M of action being reported (in GMT) Name, cardholder M PIN activity code M Reason code M Reason code sent with the action indicated, see Appendix B.6 for

values Status code M Resulting Status code from the action indicated, see

Appendix B.7 for values Type code M Resulting Cardholder Type code (Primary, Secondary, Proxy)

from the action indicated, see Appendix B.8 for values User ID C If the action was initiated from the MIS, then this will contain the

User ID of the User ID identified in the header of add or update message that prompted this action

WIC MIS account ID M

The following table lists the processing rules for the Get Card History function:

Rule ID Description 4.3.6.1 Validate that the Card number exists and is associated with an EBA. 4.3.6.2 Validate that the Date, begin request to Date, end request timeframe is not greater

than the timeframe configured by the WIC State Agency in the Maximum search range – Get Card History setting (see Appendix D - Configurability).

4.3.7 Report Card Updates The Report Card Updates function is an optional function that uses a batch system interface to allow the WIC MIS to update its records to reflect any changes made via the WIC EBT system. The Report Card Updates function is required If a WIC State Agency chooses to maintain card status on the WIC MIS and also allows changes to be made to card status via the WIC EBT system (e.g., as a result of a call to the toll-free help desk number) . The WIC EBT system shall provide the WIC MIS with any updates that have occurred within a given period. The file only contains card updates for those households that were originally created by the WIC MIS for which the file is created. In a situation where a state agency has more than one WIC MIS (which can happen temporarily if a state agency is transitioning from a legacy WIC MIS to a new WIC MIS), then the WIC EBT system shall create a separate file for each WIC MIS. In essence, each file for a given WIC MIS contains a record of card updates for the set of households that were created by the given WIC MIS. The WIC EBT system shall not change the Type code of the card and may be restricted from changing other card information at the WIC State Agency’s option.

The batch name is WIC EBT Card Updates file.

32


Note: For WIC Smart Card EBT, the WIC State Agency shall provide the Hot Card List batch file to the WIC EBT system. The specifications for the Hot Card List can be found in the WIC EBT Technical Implementation Guidelines (TIG) document.

The following table lists the data elements in the WIC EBT Card Updates file for the Report Card Updates function. See Appendix F.2.2 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Action code M Action code indicated in original update record (Activate,

Deactivate, etc.) See Appendix B.1 for values Cardholder object M Card number, replacement

C Mandatory when card was replaced

Date, effective M of action being reported (in GMT) Date and time, host M Initiating user ID C If the action was initiated from the MIS, then this will contain the

User ID of the User ID identified in the header of add or update message that prompted this action

PIN activity code C Used if the PIN was changed, unlocked, or locked. WIC MIS account ID M

4.4 Vendor Maintenance The WIC Vendor Maintenance functional area provides functions for maintaining WIC Vendor information, including banking information that is needed by the WIC EBT System.

4.4.1 Add or Update WIC Vendor File A single file format is used to handle the following functions from the Universal Interface:

Add WIC Vendor - The Add WIC Vendor function is a required function that uses a batch based system interface to establish WIC Vendor information in the WIC EBT System.

Update WIC Vendor - The Update WIC Vendor function is a required function that uses a batch system interface to modify WIC Vendor information in the WIC EBT System. It is not used to change the Status code for the WIC Vendor.

Update WIC Vendor Status - The Update WIC Vendor Status function is an optional function that uses a batch system interface to set the new status of the WIC Vendor. The WIC Vendor status is assigned based on the Reason code provided in Appendix B.6

The name of the file is the WIC Vendor File. The following lists the data elements for the WIC Vendor File. The object name is VendorObject. See Appendix F.2.3 for sample files.

Data element name Condition Usage Notes DetailRecordHeader M ABA routing transit number

O

33


Data element name Condition Usage Notes Above fifty percent vendor

O

ACH settlement time C Mandatory when vendor is flagged as direct connect Action code M Always use 002 (Update). If the vendor does not already exist,

then the action will be treated as an insert of a new vendor. Address, WIC Vendor mailing

M

Address, WIC vendor physical

M

Amount, total food sales O APL type O All APL type values are pre-defined and must be coordinated

with eWIC so that values can be loaded. Bank account number O Bank name O Business name, WIC Vendor

M

Corporation ID O Date, begin vendor M Date Vendor is active accepting WIC Date, effective M While eWIC will accept this data element, the requested

action is still effective immediately. eWIC does not honor the future data on a requested action.

Date, end vendor C Required if deactivating a vendor at a future date. Date Vendor no longer accepting WIC

Direct connect auto-recon C Mandatory when vendor is flagged as direct connect Direct connect flag O Email, WIC Vendor contact O FNS number O Local agency ID O Agency contracting with WIC Vendor Name, WIC Vendor contact

M

Phone number, alternate WIC Vendor contact

O

Phone number, WIC vendor contact

M

Reason code M Default is “V-006 Vendor eligible to be paid”, see Appendix B.6 for all values

Type code M WIC Vendor type (Chain, Independent grocer, etc.), see Appendix B.8 for values

WIC MIS WIC Vendor ID M WIC Vendor peer group ID M Any WIC Vendor peer group ID encountered by eWIC within this

file that are not already present within eWIC will automatically be added with generic names.

WIC Vendor tax ID O

The following lists the business rules for the Add/Update WIC Vendor File:

Rule ID Description 4.4.1.1 The WIC EBT System shall not accept transactions from a WIC Vendor after the Date,

end vendor has been reached. 4.4.1.2 Validate that WIC MIS WIC Vendor ID does not already exist for the calling system if

34


Rule ID Description adding a WIC Vendor and that it already exists for the calling system if updating a WIC Vendor.

4.4.1.3 Appropriate measures shall be applied to ensure that the security of banking data is maintained.

4.4.1.4 eWIC does not deactivate any vendors not presented in this file (i.e. eWIC accepts a delta file). However, eWIC will generate an email alert listing existing vendors that were not included in the file.

4.4.1.5 eWIC will process any valid records in the file and will not reject the entire file if some records are in error.

4.4.1.6 If the APL type is included, then the vendor will be configured to receive an APL containing UPC/PLU records that are associated with the same APL type as the vendor.

4.5 WIC Food Maintenance The WIC Food Maintenance functional area includes functions for creating and updating the list of food categories and sub-categories used by the WIC State Agency, creating and maintaining the list of UPC/PLU data for food items and creating and maintaining the NTE price for a food item.

The National Universal Product Code (NUPC) database provides the standard list of food categories, subcategories and common UPCs and PLUs maintained by FNS.

Note that due to processing schedules of various parties (e.g. gateways, switches, third party processors, etc.) that exist between eWIC and a retail store, it may take up to 48 hours for category/sub-category or UPC/PLU updates to propagate to a retail store’s system.

4.5.1 Add or Update Category/Sub-category Information The Add or Update Category/Sub-Category Information function is a required function that uses a batch system interface to provide updates to the Category and Sub-Category information from the system maintaining the interface to the NUPC database or MIS.

The batch name is WIC Category Sub-Category file.

The following table lists the data elements in the WIC Category Sub-Category file. The object name is CategorySubcategoryObject. See Appendix F.2.4 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Action code M Always use 002 (Update). If the category/sub-category does not

already exist, then the action will be treated as an insert of a new category/sub-category.

Benefit unit description M Only first 6 characters are significant Category code M Category long description M Category short description M It is acceptable to use the same value for this field as what is

supplied in the Category long description Date, begin category C Mandatory if not effective immediately Date, begin sub-category C Mandatory if not effective immediately

35


Data element name Condition Usage Notes Date, end category O Date, end sub-category O Sub-Category code M Sub-Category long description

M

Sub-Category short description

M

The following table lists the processing rules for the Add or Update Category/Sub-Category Information function:

Rule ID Description 4.5.1.1 Benefit unit description may use the values defined in the Technical Implementation

Guide. If the State agency elects to not use values from the Technical Implementation Guide, then those values must be supplied in advance to eWIC for a manual load into the eWIC database.

4.5.1.2 Date, begin sub-category shall be greater than the existing Date, begin sub-category. 4.5.1.3 eWIC will deactivate any category/sub-category records not presented in this file and

products with the associated category/sub-category will no longer be approved (i.e. eWIC expects a full replacement file each time).

4.5.1.4 Any errors encountered result in the entire file being rejected. 4.5.1.5 If the file includes a Date, end category for a given Category code, then eWIC shall

verify that any Sub-category codes with the given Category code have a Date, end sub-category that is the same as or prior to the Date, end category.

4.5.1.6 If the file includes a Date, end sub-category for a given Sub-category code, then eWIC shall verify that all benefits with the given Sub-category code and Benefit quantity greater than zero have a Date, end benefit that is the same as or prior to the Date, end sub-category.

4.5.2 Add or Update UPC/PLU Information The Add or Update UPC/PLU Information function is a required function that uses a batch system interface to provide updates to the UPC/PLU information from the system maintaining the WIC State Agency APL file.

The batch name is the WIC UPC/PLU file. This file differs from the Authorized Product List (APL) File provided to WIC Vendors as it contains WIC Vendor peer group data.

The following table lists the data elements in the WIC UPC/PLU file for the Add or Update UPC/PLU information function. See Appendix F.2.5 for sample files.

Data element name Condition Usage Notes DetailRecordHeader M Action code M Always use 002 (Update). If the UPC/PLU does not already exist,

then the action will be treated as an insert of a new UPC/PLU. Benefit quantity M Benefit unit description O This field is not used from this file Category code M Date, begin UPC/PLU data M

36


Data element name Condition Usage Notes Date, end UPC/PLU data C Item description M Manual voucher indicator O This field is not used by eWIC Number of APL types O Identifies how many APL types will be associated with this

UPC/PLU record and are included in the repeating section below Number of WIC vendor peer groups

M Identifies how many WIC Vendor peer group IDs are included in the repeating section below

Package size O Price type M Distinguishes CVB items from non-CVB items; values are “03” for

CVB and “00” for non-CVB Purchase indicator M Values are 1 to indicate that item may be purchased with benefits

in Broadband and 0 to indicate that item may not be purchased with benefits in Broadband

Rebate flag M Identifies whether a food item is eligible for manufacturer rebates; values are “Y” for yes, “N” for no

Sub-Category code M UPC /PLU data M UPC/PLU data length M The following data elements are repeated for each UPC/PLU data data element where an NTE price is provided: NTE price O WIC Vendor peer group ID O All WIC Vendor peer group ID values are pre-defined and must

either be 1) coordinated with eWIC so that values can be loaded or 2) automatically loaded via a WIC Vendor File.

The following data elements are repeated for each UPC/PLU data data element where the UPC/PLU record should be associated with the listed APL types: APL type O All APL type values are pre-defined and must be coordinated

with eWIC so that values can be loaded.

The following table lists the processing rules for the Add or Update UPC/PLU Information function:

Rule ID Description 4.5.2.1 The information provided shall be a complete replacement of the existing information

for the UPC/PLU data identified. 4.5.2.2 All peer group pricing data shall be included for each UPC/PLU data food item

identified. 4.5.2.3 eWIC does not deactivate any products not presented in this (i.e. eWIC accepts

a delta file). 4.5.2.4 Any errors encountered result in entire file being rejected. 4.5.2.5 If the list of APL types is provided, then the UPC/PLU shall be included in the APL for

each of the APL types that are provided. 4.5.2.6 eWIC will reject the WIC UPC/PLU file if it contains more than one occurrence of a

given UPC/PLU data value (i.e. if the file contains a duplicate UPC/PLU number).

4.6 WIC EBT Data Files

4.6.1 Report WIC Benefit Redemptions The Report WIC Benefit Redemptions function is a required function that uses a batch system interface to provide a detailed record of all benefit redemption activity on a daily basis from the WIC

37


EBT system. The file only contains redemption activity for those households that were originally created by the WIC MIS for which the file is created. In a situation where a state agency has more than one WIC MIS (which can happen temporarily if a state agency is transitioning from a legacy WIC MIS to a new WIC MIS), then the WIC EBT system shall create a separate file for each WIC MIS. In essence, each file for a given WIC MIS contains a record of redemption activity for the set of households that were created by the given WIC MIS. A WIC MIS may receive this batch for NTE calculation and maintenance, reporting, reconciliation and program management. Redemption transactions included in this function are established via bilateral agreement between the EBT and MIS systems and at a minimum shall include approved purchase transactions. Currently, eWIC only supports reporting approved redemption activity in this file.

The Report WIC Benefit Redemptions function provides information that differs from the WIC Auto- reconciliation file as follows:

1. Information is based on the WIC EBT system business day or timeframe specified by the WICState Agency instead of the WIC Vendor business day.

2. Information is a full historical account (audit trail) of the transaction and the information(Category code, Sub-Category code, Unit of measure, Item description, Benefit begin dateand Benefit end date) that was current and used at the time of the transaction.

3. WIC Vendor peer group ID is provided.

The batch name is WIC Benefit Redemption File.

The following table lists the data elements in the WIC Benefit Redemption File for the Report WIC Benefit Redemptions function. See Appendix F.2.5.2 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Acquiring institution ID code

M Identifies entity that obtained the transaction from the WIC Vendor

Amount, discount M Amount, paid M The Amount, paid at the transaction level shall equal the sum of

the Amount, paid of all of the reported line items less the Amount, discount at the transaction level. Also, Amount, paid = Amount, transaction - Amount, discount - Amount, total adjustments.

Amount, total adjustments M The sum of all adjustments to the reported line items Amount, transaction M The original amount of the transaction before any adjustments

or discounts Card acceptor identification code




Card number M Date and time, host M Date and time, local transaction

M

Date, business M

38


Data element name Condition Usage Notes Date, settlement M As recorded by the EBT system Forwarding institution ID code

M Identifies entity that submitted the transaction for payment

Host generated trace number

M Identifies the Host generated trace number that was assigned to the transaction being reported; for redemptions being reported it contains a host assigned unique identifier. This field is referred to as Unique EBT transaction ID in WUMEI.

Initiating user ID N/A Message reason code C Mandatory if the transaction represents an adjustment. (eWIC

does not currently utilize this field. This field will be included in the redemption file, but will remain uninitialized for now. When eWIC implements more formalized adjustment processing, eWIC will begin populating this field.)

Original host generated trace number

C For a reversal, refers to the original transaction


M

POS data code, cardholder authentication capability

M


M


M

POS data code, cardholder present

M

POS data code, card present

M


M


M


M


M


M


M

Systems trace audit number

M

Transaction reason code M Value is the action code (bit 39) for WIC Online EBT and will always be set to “000” or “002”; see Technical Implementation Guide for corresponding values. eWIC currently only supports the return of approved (or partially approved) redemptions.

Type code M Indicates transaction type (Purchase, Void, Adjustment, etc.); See Appendix B.8 for values

WIC MIS account ID M WIC MIS WIC Vendor ID M

39


Data element name Condition Usage Notes WIC Vendor peer group ID M The following data elements will be repeated for each food item purchased. The object name is RedemptionDetailObject. Amount, item discount M Amount, NTE adjustment C Mandatory if line item includes an NTE adjustment Amount, recoupment adjustment

C Mandatory if line item includes a recoupment adjustment

Amount, paid M The amount paid to a WIC vendor for a purchase transaction for the specific item purchased less any adjustments. The Amount, paid is equal to the requested Item price as adjusted for NTE and recoupment, times the approved Purchase quantity and cannot be less than zero.

Benefit issuance ID M Original value from the benefits issued at the WIC MIS account ID level

Benefit unit description M Only first 6 characters are significant (this is the same as the Unit of measure field in the WUMEI that is optional).

Category code M Category code of the benefit applied to the item Category long description N/A Clinic ID C Clinic ID of location that issued the benefit, echoed from original

message if present Date, begin benefit M Date, end benefit M Item action code M Item description M Item NTE O Item price M The item price after any adjustments are applied, i.e. Item price

= Original item price - Amount, item discount - Amount, NTE adjustment - Amount, recoupment adjustment

Line item ID C Mandatory when a single food item in a purchase requires multiple reporting records to account for applying units across Sub-Categories or Benefit IDs.

Local agency ID C Local agency ID for location that issued the benefit, echoed from original message if present

Original amount M The amount requested by a WIC vendor for a purchase transaction for the specific item purchased. The Original amount is equal to the requested Item price times the approved Original purchase quantity and cannot be less than zero.

Original category code M Category code assigned to the UPC or PLU Original item price M The requested item price before any adjustments Original purchase quantity M The quantity requested as prorated for the specific amount of

benefit units redeemed Original sub-category code M Sub-Category code assigned to the UPC or PLU Package size C The size of the contents of the package quantified in the

standard benefit units of measure Purchase quantity M The quantity approved as prorated for the specific amount of

benefit units redeemed Sub-Category code M Sub-Category code of the benefit applied to the item Sub-Category long N/A

40


Data element name Condition Usage Notes description Units M Number of units of benefit of this item redeemed UPC/PLU data M UPC/PLU data length M

The following table lists the processing rules for the Report WIC Benefit Redemptions function:

Rule ID Description 4.6.1.1 Validate that the WIC MIS account ID exists and is active. 4.6.1.2 Reversals shall be reported as two separate transactions; the original transaction and

the subsequent reversal. 4.6.1.3 Note that any adjustments that use Add or Update Benefits are reported using the

Report WIC Benefit Changes function. 4.6.1.4 Transactions with discounts and coupons are reported as specified in the Technical

Implementation Guide. 4.6.1.5 Transactions utilizing multiple Benefit IDs or where redemption straddles the Sub-

Category code and Broadband Sub-Category code shall report details for each item redeemed.

4.6.1.6 The transaction must balance as follows: Amount, paid (at the global transaction level) = sum(Amount, paid at the item level) – Amount, discount (at the global transaction level).

Note that in order for the transaction to balance, eWIC may adjust prorated amounts and quantities to offset rounding errors. For a detailed example, see Appendix F.1.

4.6.2 Report WIC Benefit Changes The Report WIC Benefit Changes function is a required function that uses a batch system interface to create a batch file that contains information for each WIC MIS initiated Add or Update Benefits transaction (issuances, updates and voids) that was accepted and approved by the WIC EBT system during the prior 24 hour period. The WIC MIS uses this information to match against its record of successful Add or Update Benefits transactions initiated by the WIC MIS during the same period. The file also includes Add or Update Benefits transactions that may have been issued outside of the WIC MIS (for example, through an administrative interface in the WIC EBT system) for any household that was originally created by the WIC MIS. In a situation where a state agency has more than one WIC MIS (which can happen temporarily if a state agency is transitioning from a legacy WIC MIS to a new WIC MIS), then the WIC EBT system shall create a separate file for each WIC MIS. In essence, each file for a given WIC MIS contains a record of Add or Update Benefits activity for the set of households that were created by the given WIC MIS.

The batch name is WIC Daily Interface Reconciliation file.

The following table lists the data elements in the WIC Daily Interface Reconciliation file for the Report WIC Benefit Changes function. The object name is BenefitActivityObject. See Appendix F.2.7 for a sample file.

Data element name Condition Usage Notes

41


Data element name Condition Usage Notes DetailRecordHeader M Action code M Add or subtract; see Appendix B.1 for values Card number C Echoed from original message if present Clinic ID C Echoed from original message if present Date and time, transmission

M

Initiating user ID C Echoed from original message if present Local agency ID C Echoed from original message if present Reason code C Echoed from original message if present Type code M Valid types are:

I – Issuance/Add D – Void/Subtract

Unique EBT transaction identifier

M

WIC MIS account ID M Multiple month’s benefits may be added/voided for each WIC MIS account ID and/or Card number. The object name is UniqueIssuanceObject. Benefit issuance ID M Date, begin benefit M Date, end benefit M A list of the following elements are repeated for each Benefit issuance ID. The object name is UniqueIssuanceObjectDetailObject. Benefit quantity M Category code M Category long description N/A Sub-Category code M Sub-Category long description

N/A

4.6.3 Report WIC Benefits Purged The Report WIC Benefits Purged function is a required function that uses a batch system interface to provide a detailed record of benefits purged from the WIC EBT system. The file only contains information for those households that were originally created by the WIC MIS for which the file is created. In a situation where a state agency has more than one WIC MIS (which can happen temporarily if a state agency is transitioning from a legacy WIC MIS to a new WIC MIS), then the WIC EBT system shall create a separate file for each WIC MIS. In essence, each file for a given WIC MIS contains a record of benefits purged for the set of households that were created by the given WIC MIS. A benefit is eligible to be purged or expunged on a configurable number of days after the Date, end benefit is reached. A WIC MIS may receive this information for reporting, reconciliation and program management. All benefits purged by the WIC EBT system are included in this function for those households created by the WIC MIS. The information may be reported by Benefit month or daily to provide for WIC State Agencies using a rolling Benefit month.

The batch name is WIC Benefits Purged File.

42


The following table lists the data elements in the WIC Benefits Purged File for the Report WIC Benefits Purged function. See Appendix F.2.8 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Benefit issuance ID O Original value from the benefits issued at the WIC MIS account ID

level Card number N/A Date, begin benefit M Date, effective M This is the date (in GMT) that the benefits were purged Date, end benefit M WIC MIS account ID M A list of the following elements are repeated for each Benefit issuance ID purged: Benefit quantity M Category code M Category long description N/A Sub-Category code M Sub-Category long description

N/A

The following table lists the processing rules for the Report WIC Benefits Purged function:

Rule ID Description 4.6.3.1 Validate that the WIC MIS account ID exists.

4.7 Financial Settlement The Financial Settlement functional area comprises functions for effecting financial transactions from the WIC EBT system to the WIC Vendor. The settlement process moves funds between parties to resolve payments due to or from each other. The WIC Universal Interface conforms to the National Automated Clearing House Association (NACHA) Operating Rules and Guidelines wherever possible (see http://www.achrulesonline.org for detailed requirements).

4.7.1 Request ACH Payment The Request ACH Payment function is an optional function that uses a batch based system interface to allow the WIC State Agency or EBT Card Issuer Processor to make a payment or adjustment to a WIC Vendor, a WIC Vendor corporate entity or their agent that is outside the normal course of benefit redemption and settlement. This function may be used in situations where an adjustment is needed for a transaction that has already been settled. This function may also be used for payments to other WIC State Agency WIC EBT vendors such as mail-order vendors or infant formula warehouses.

This function requires that banking data be provided. This does not mean that banking data needs to be stored by the sending system for all WIC Vendors. Banking data shall be verified by the system that is the database of record for this information.

43


This function eliminates the need to maintain an alternate check process for these types of payments that may occur outside of daily WIC EBT settlement activities by utilizing the ACH payment capability of the WIC EBT system.

The batch name is WIC ACH Payment File.

The following table lists the data elements sent for the Request ACH Payment function and in the WIC ACH Payment File for the Report WIC Benefit function. See Appendix F.2.9 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Action code M Add or Issue, see Appendix B.1 for values ABA routing transit number

M Receiving institution bank identifier

Amount, ACH payment M Limited to 10 positions Bank account number M Receiving institution account number Bank Name O Card acceptor identification code

O

Corporation ID C Mandatory if payment at a hierarchy level other than the WIC Vendor

Date, effective M Default is current date. Not the same as the NACHA Effective Entry Date calculated by the EBT system

Hierarchy code M Mandatory if payment at a hierarchy level other than the WIC Vendor, default is “no hierarchy”, see Appendix B.3 for values

Original systems trace audit number

C Mandatory if this payment is related to a single, previous transaction

Reason code M ACH payment reason code (Adjustment, Payment to warehouse, etc.), see Appendix B.6 for values

Receiving institution identification code

O Used by sender as additional identifier for entity receiving the file

WIC MIS WIC Vendor ID M

The following table lists the processing rules for the Request ACH Payment function:

Rule ID Description 4.7.1.1 Validate that the WIC MIS WIC Vendor ID already exists and is valid for the calling

system. 4.7.1.2 Any entries received in this file are treated as new credit or debit payments (i.e.

eWIC accepts a delta file). 4.7.1.3 Any errors encountered result in the entire file being rejected.

4.7.2 Report ACH Payments The Report ACH Payments function is an optional function that uses a batch based system interface to have the WIC EBT System report all WIC ACH payments requested by the WIC MIS and any initiated by the WIC EBT system. The WIC MIS reconciles these transactions to the ACH payments reported by the WIC State Agency’s financial institution entity.

The following table lists the data elements sent for the Report ACH Payment function:

44


Data element name Condition Usage Notes DetailRecordHeader M ABA routing transit number

M Receiving institution bank identifier

ACH Trace Number M Uniquely identifies the item within an ACH input file Amount, ACH payment M Limited to 10 positions Bank account number M Receiving institution account number Bank Name O Card acceptor identification code

O

Corporation ID C Mandatory if original transaction originated from a clinic Date, effective M In report, corresponds to NACHA Effective Entry Date assigned by

the EBT system. Initiating user ID C Mandatory if initiated from a clinic Local agency ID C Mandatory if original transaction originated from a local agency Original systems trace audit number

C Mandatory if this payment is related to a single, previous transaction

Reason code M ACH payment reason code (Adjustment, Payment to warehouse, etc.), see Appendix B.6 for values


O Used by sender as additional identifier for entity receiving the file


The following table lists the processing rules for the Request ACH Payment function:

Rule ID Description 4.7.2.1 If the payment was not completed, the Date, effective shall be the original payment

request date.

4.8 Recoupment Files

4.8.1 Report Recoupment Requests The Report Recoupment Requests function uses a batch system interface to allow the sender to notify eWIC of the amounts to be recouped from each vendor.

The file name is the WIC Recoupment Request File. The following table lists the data elements in the WIC Recoupment Request File. The object name is RecoupmentRequestObject. See Appendix F.2.10 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Amount, recoupment M Recoupment processing month

M

Type code M Indicates transaction type (Reversal, Void); See Appendix B.8 for values


The following table lists the processing rules for the Report Recoupment Requests function:

45


Rule ID Description 4.8.1.1 Processing Month is populated with a date representing the first of the month that was

used in computing the recoupment amount. For example, sometime in March 2014, the State agency will create a file of recoupments based on redemptions that occurred in February. In this case, the Processing Month is set to “2014-02-01”.

4.8.1.2 A record should be included in the file for every vendor with a nonzero recoupment amount. If a vendor does not appear in the file, then eWIC shall assume that there is no new recoupment for the vendor.

4.8.1.3 A debit may not take the net outstanding recoupment to the negative. In such a case, recoupment processing for that vendor’s transactions is suspended (i.e. the amount is not credited to the vendor during redemption processing) until there are enough subsequent credits or new recoupments (the following month) to make the net recoupment amount a positive value.

4.8.1.4 Any entries received in this file are treated as new credits or debits to pending vendor recoupment totals (i.e. eWIC accepts a delta file).

4.8.1.5 Any errors encountered result in the entire file being rejected.

4.8.2 Report Recoupment Status The Report Recoupment Status function uses a batch system interface to allow eWIC to report the daily status of recoupment activity by vendor.

The file name is the WIC Recoupment Status File. The following table lists the data elements in the WIC Recoupment Status File. The object name is RecoupmentStatusObject. See Appendix F.2.11 for a sample file.

Data element name Condition Usage Notes DetailRecordHeader M Amount, beginning recoupment

M

Amount, ending recoupment

M

Amount, new recoupment M Amount, recoupment credit adjustment

M

Amount, recoupment debit adjustment

M

Amount, recoupment recovered

M

Amount, recoupment reversed

M

Amount, recoupment variance

M

Reason code M Vendor status, see Appendix B.6 for all values

Date, recoupment activity M WIC MIS WIC Vendor ID M

The following table lists the processing rules for the Report Recoupment Requests function:

Rule ID Description 4.8.2.1 eWIC will include every active vendor in the Recoupment Status File whether or

46


Rule ID Description not the vendor has a nonzero position and will include those deactivated vendors that have a nonzero Beginning and/or Ending Recoupment Amount.

4.9 Warehouse Authorization The Warehouse Authorization functional area comprises functions geared toward generating and removing authorizations for the purchase of items from warehouse vendors that ship authorized items. Since the cardholder is not present when a warehouse fulfills an order, an alternative to PIN entry is required to maintain the integrity of the transaction.

4.9.1 Request Warehouse Authorization The Request Warehouse Authorization function uses a message based interface to allow the MIS to request that eWIC generate an Authorization code that must be presented in the redemption request at the time of fulfillment.

Data element name Condition Usage Notes Authorization quantity M Card number C Mandatory if WIC MIS account ID not present Date, begin benefit M Date, begin benefit of the benefit that will be utilized in the

redemption Date, end benefit M Date, end benefit of the benefit that will be utilized in the

redemption UPC/PLU data M UPC/PLU data length M WIC MIS account ID C Mandatory if Card number not present WIC MIS WIC vendor ID M Identifies the vendor that will perform the redemption; note that the

authorization will be not valid from a different vendor

The following table lists the data elements returned for the Request Warehouse Authorization function:

Data element name Condition Usage Notes Authorization code M Authorization quantity M The remaining unredeemed quantity for the UPC/PLU data after the

current request has been applied. Card number M The primary card associated with the account

The following table lists the processing rules for the Request Warehouse Authorization function:

Rule ID Description 4.9.1.1 The WIC MIS WIC vendor ID must represent an active warehouse vendor. 4.9.1.2 The Card number (if provided) must be active, linked to an active EBA, and the primary

card for the EBA. 4.9.1.3 The WIC MIS account ID (if provided) must represent an active EBA. 4.9.1.4 The provided UPC/PLU data must represent an item that will be active during the Date,

begin benefit and Date, end benefit period. 4.9.1.5 The provided UPC/PLU data must be assigned to a subcategory that is allowed for

warehouse authorizations. 4.9.1.6 There must be sufficient quantity of unauthorized, non-broadband benefits available in

47


Rule ID Description the category/subcategory associated with the UPC/PLU data.

4.9.1.7 If an existing authorization exists for the same card/account, vendor, UPC, and benefit date combination with an unredeemed quantity remaining, the authorization will be allowed as a credit and the original authorization code will be returned again.

4.9.1.8 The stored Price type of the provided UPC/PLU data determines if a fractional Authorization quantity is allowed or not; “00” for non-CVB results in allowing whole numbers only, “03” for CVB results in allowing fractional numbers.

4.9.2 Void Warehouse Authorization

The Void Warehouse Authorization function uses a message based interface to allow the MIS to request that eWIC void a given authorization that has previously been requested.

Data element name Condition Usage Notes Card number C Mandatory if WIC MIS account ID not present Date, begin benefit M Date, begin benefit of the benefit that will be utilized in the

redemption Date, end benefit M Date, end benefit of the benefit that will be utilized in the

redemption UPC/PLU data M UPC/PLU data length M WIC MIS account ID C Mandatory if Card number not present WIC MIS WIC vendor ID M Identifies the vendor that will perform the redemption; note that the

authorization will be not valid from a different vendor

The following table lists the data elements returned for the Void Warehouse Authorization function:

Data element name Condition Usage Notes Authorization quantity M The remaining unredeemed quantity for the UPC/PLU data before the

current void has been applied.

The following table lists the processing rules for the Void Warehouse Authorization function:

Rule ID Description 4.9.2.1 The presented data must correlate to an unexpired authorization with non-zero

authorization quantity remaining.

4.9.3 Get Warehouse Authorizations The Get Warehouse Authorizations function is an optional function that uses a message based system interface to get a list of matching warehouse authorizations. The function requires a least one primary filter to be provided to return authorizations for an account, vendor, or product.

The following table lists the data elements that will be sent for the new function:

Data element name Condition Usage Notes Card number C Mandatory if the UPC/PLU data, WIC MIS account ID, and WIC MIS

WIC vendor ID filters are not present Date, begin benefit O See 4.9.3.5 Date, end benefit O See 4.9.3.5 UPC/PLU data C Mandatory if the Card number, WIC MIS account ID, and WIC MIS WIC

48


Data element name Condition Usage Notes vendor ID filters are not present

UPC/PLU data length C Mandatory if UPC/PLU data is present WIC MIS account ID C Mandatory if the Card number, UPC/PLU data, and WIC MIS WIC

vendor ID filters are not present WIC MIS WIC vendor ID C Mandatory if the Card number, UPC/PLU data, and WIC MIS account

ID filters are not present

The following data elements will be returned for the new function:

Data element name Condition Usage Notes The following data is repeated for each matching authorization: Card number M Returns the primary card, or the latest primary card if all cards

are deactivated. Date, begin benefit M Date, end benefit M UPC/PLU data M UPC/PLU data length M WIC MIS account ID M WIC MIS WIC vendor ID M Authorization quantity, available

M Depleted authorizations are returned

Authorization quantity, original

M Sum of all requests

The following table lists the processing rules for the Get Warehouse Authorizations function:

Rule ID Description 4.9.3.1 The WIC MIS WIC vendor ID (if provided) must represent a warehouse vendor that

exists. 4.9.3.2 The Card number (if provided) must represent a primary card number that exists and is

linked to an EBA. 4.9.3.3 The WIC MIS account ID (if provided) must represent an EBA that exists. 4.9.3.4 The provided UPC/PLU data (if provided) must represent an item that exists. 4.9.3.5 If Date, begin request, Date, end request and Benefit issuance ID are not provided, then

the WIC EBT System shall only return records where the current date is between the Date, begin benefit and Date, end benefit.

4.9.4 Get Warehouse Authorization Code The Get Warehouse Authorization Code function is an optional function that uses a message based system interface to get an authorization code from a previously approved warehouse authorization.

The following table lists the data elements that will be sent for the new function:

Data element name Condition Usage Notes Card number C Mandatory if WIC MIS account ID not present Date, begin benefit M Date, end benefit M UPC/PLU data M UPC/PLU data length M WIC MIS account ID C Mandatory if Card number not present

49


Data element name Condition Usage Notes WIC MIS WIC vendor ID M

The following data elements will be returned for the new function:

Data element name Condition Usage Notes Authorization code M Authorization quantity M The remaining unredeemed quantity for the UPC/PLU data Card number M The primary card associated with the account

The following table lists the processing rules for the Request Warehouse Authorization function:

Rule ID Description 4.9.4.1 The Card number / WIC MIS account ID, UPC/PLU data, and WIC MIS WIC vendor ID

must match to an existing warehouse authorization.

50


Appendix A - Data Dictionary The Data Dictionary lists 1) the specific formats allowed and 2) the data elements identified for the all of the functions in the Universal Interface in alphabetical order. Note that data elements may be combined to create “objects” or constructed data elements containing related information, i.e., banking information, food benefit information etc.

Format Description a Alphabetical characters (A through Z and a through z). an Alphabetical characters (A through Z and a through z) and numeric digits (0 through 9). anp Alphabetical characters (A through Z and a through z), numeric digits (0 through 9), and padding (spaces). ans Alphabetical characters (A through Z and a through z), numeric digits (0 through 9), and special characters. ansp Alphabetical characters (A through Z and a through z), numeric digits (0 through 9), special characters, and padding (spaces). as Alphabetical characters (A through Z and a through z) and special characters. asp Alphabetical characters (A through Z and a through z), special characters, and padding (spaces). b Binary representation of data. CCYY Century and year (0000 through 9999). See ISO 8601. DD Day (01 through 31). hh Hour (00 through 23). mm Minute (00 through 59). n Numeric digits (0 through 9). ns Numeric digits (0 through 9) and special characters. p Padding (spaces). s Special characters: !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~. ss Second (00 through 59). xn Numeric data with a preceding sign of “c” for credit or “d” for debit. YY Year (00 through 99). z Tracks 2 and 3 code set as defined in ISO 4909 and ISO 7813.

Data element name Description Format XML Element Name XML Data Type ABA routing transit number The number that identifies the financial

institution to which a WIC Vendor is paid via ACH and conforms to the American Bankers Association standard.

n 9 ABARoutingTransitNumber xs:string

Above fifty percent (A50) vendor A flag (0 or N for no, 1 or Y for yes) indicating whether or not the volume of

an 1 Above50Percent xs:string


Data element name Description Format XML Element Name XML Data Type WIC sales is above 50% of the total sales for the WIC Vendor.

ACH settlement time For a direct connect WIC Vendor, this is the time (date portion is ignored) that the WIC EBT System uses for processing WIC Vendor activity for the purpose of computing the daily WIC Vendor settlement amount. The WIC EBT System will process transactions that occurred during the 24 hours prior to this time.

CCYY-MM-DDThh:mm:ss[Z]

ACHSettlementTime xs:dateTime

ACH trace number A number that uniquely identifies an entry detail record within a batch in an ACH input file.

n 15 ACHTraceNumber xs:string

Acquiring institution ID code A code identifying the entity acquiring the transaction

n 11 AcquiringInstitutionID xs:string

Action code A code which defines the action to be taken. See Appendix B.1

n 3 ActionCode xs:string

Address, cardholder mailing A constructed data element including Address line 1, Address line 2, Address city, Address state and Address ZIP code where the cardholder receives mail.

ansp, max 96

CardholderMailingAddressObject AddressObject

Address, household mailing A constructed data element including Address line 1, Address line 2, Address city, Address state and Address ZIP code where the household receives mail.

ansp, max 96

HouseholdMailingAddressObject AddressObject

Address city Sub-element of address data elements identifying the city name of the address specified

ansp, max 25

City xs:string

Address, clinic A constructed data element including Address line 1, Address line 2, Address city, address, state and Address ZIP code where the clinic receives mail.

ansp, max 96

ClinicAddressObject AddressObject

Address, corporation mailing A constructed data element including Address line 1, Address line 2, Address city, Address state and Address ZIP code where the corporation receives mail.

ansp, max 96

CorporationMailingAddressObject AddressObject

52


Data element name Description Format XML Element Name XML Data Type Address line 1 Sub-element of address data elements

identifying the first line of the address specified.

ansp, max 30

StreetAddressLine1 xs:string

Address line 2 Sub-element of address data elements identifying the second line, if present, of the address specified.

ansp, max 30

StreetAddressLine2 xs:string

Address, local agency A constructed data element including Address line 1, Address line 2, Address city, Address state and Address ZIP code where the local agency receives mail.

ansp, max 96

LocalAgencyAddressObject AddressObject

Address, state Sub-element of address data elements; conforms to the U.S. Post Office state and territory abbreviations.

ansp, max 2

StateAbbreviation xs:string

Address, WIC Vendor mailing A constructed data element including Address line 1, Address line 2, Address city, Address state and Address ZIP code where the WIC vendor receives mail.

ansp, max 96

VendorMailingAddressObject AddressObject

Address, WIC Vendor physical A constructed data element including Address line 1, Address line 2, Address city, Address state and Address ZIP code where the WIC vendor is located.

ansp, max 96

VendorPhysicalAddressObject AddressObject

Address ZIP code Sub-element of address data elements and a constructed data element including the Address ZIP code, primary and the Address ZIP code, extended for the address specified.

n 9 ZipCode xs:string

Address ZIP code, extended A sub-element of Address ZIP code, identifying the ZIP+4 U.S. postal codes for the address specified.

n 4 ExtendedZipCode xs:string

Address ZIP code, primary A sub-element of Address ZIP code identifying the U.S. postal code associated with the address specified.

n 5 PrimaryZipCode xs:string

Amount, ACH payment The amount to be debited or credited to the WIC vendor identified

n 10 PaymentAmount xs:decimal

Amount, beginning recoupment The beginning balance of recoupment on a given activity day

n 12 RecoupmentAmountBeginning xs:decimal

53


Data element name Description Format XML Element Name XML Data Type Amount, discount The absolute value of the amounts deducted

from the gross amount of the transaction due to coupons or other reductions in the amount

n 12 DiscountAmount xs:decimal

Amount, ending recoupment The ending balance of recoupment on a given activity day

n 12 RecoupmentAmountEnding xs:decimal

Amount, item discount The amount deducted from the Item price for an individual item; not available in X9.93

n 12 DiscountAmount xs:decimal

Amount, new recoupment The amount of new recoupment amounts received on a given activity day

n 12 RecoupmentAmountNew xs:decimal

Amount, NTE adjustment The amount of the adjustment applied to the price of a food item due to the original item price being in excess of the not to exceed amount for the peer group of the vendor, not available in X9.93

n 6 NTEAmount xs:decimal

Amount, paid At the transaction level: The Amount, paid at the transaction level shall equal the sum of the Amount, paid of all of the reported line items less the Amount, discount at the transaction level. Also, Amount, paid = Amount, transaction - Amount, discount - Amount, total adjustments. At the item level: The amount paid to a WIC vendor for a purchase transaction for the specific item purchased less any adjustments. The Amount, paid is equal to the requested Item price as adjusted for NTE and recoupment, times the approved Purchase quantity and cannot be less than zero.

n 12 SettledAmount PaidAmount

xs:decimal

Amount, recoupment The amount to debit or credit from the running total of recoupment according the action in Type code

n 12 RecoupmentAmount xs:decimal

Amount, recoupment adjustment The amount of the adjustment applied to the price of a food item by the WIC State Agency, not available in X9.93

n 6 RecoupmentAmount xs:decimal

54


Data element name Description Format XML Element Name XML Data Type Amount, recoupment credit adjustment

The amount of credit adjustments to recoupment received on a given activity day

n 12 RecoupmentAmountCredit xs:decimal

Amount, recoupment debit adjustment

The amount of debit adjustments to recoupment received on a given activity day

n 12 RecoupmentAmountDebit xs:decimal

Amount, recoupment recovered The amount of recoupment recovered through redemptions on a given activity day

n 12 RecoupmentAmountRecovered xs:decimal

Amount, recoupment reversed The amount of recoupment added back through purchase reversals/voids on a given activity day

n 12 RecoupmentAmountReversed xs:decimal

Amount, recoupment variance The discrepancy between a snapshot balance of recoupments and the amount calculated from the eWIC audit trail

n 12 RecoupmentAmountVariance xs:decimal

Amount, total adjustments Sum of all adjustments made to the Item prices of the individual items for a transaction.

n 12 TotalAdjustments xs:decimal

Amount, total food sales The volume of total food sales reported by the WIC Vendor.

n 12 TotalFoodSalesAmount xs:decimal

Amount, transaction Amount requested by the cardholder in the local currency of the acquirer or source location of the transaction including any surcharges

n 12 RequestedAmount xs:decimal

Amounts, settled Total of funds to be transferred between the parties identified where “x” indicates “C” for a credit and “D” for a debit

x + n 12 SettledAmounts

APL type A code used to restrict what UPCs may be included in a particular “type” of APL that a vendor may receive.

n 4 APLType xs:short

Authorization code Code to be presented in redemptions against warehouse authorizations.

n 4 AuthorizationCode xs:string

Authorization quantity The quantity of products that have been requested by a warehouse vendor for the purpose of a warehouse authorization.

n 5 AuthorizationQuantity AuthorizationQuantityAvailable AuthorizationQuantityOriginal

xs:decimal

Bank account number The number identifying the WIC Vendor’s bank checking account.

n 17 BankAccountNumber xs:string

Bank name The business entity holding the bank account of the WIC Vendor

asp, max 10 BankName xs:string

55


Data element name Description Format XML Element Name XML Data Type Benefit issuance ID A unique number identifying a benefit

issuance; assigned by the WIC MIS system. n 12 UniqueBenefitID xs:integer

Benefit month The first of the month for a period defined by the WIC State Agency in which benefits are in effect; may be a calendar month or a rolling number of days

CCYY-MM-DD

BenefitMonth xs:string

Benefit quantity The quantity of an item defined in the sender’s specified benefit issuance Unit of measure

n 5 BenefitQuantity xs:decimal

Benefit quantity, active hold The quantity of an item defined in the sender’s specified benefit issuance Unit of measure in active hold at a WIC Vendor for manual voucher authorization

n 5 BenefitQuantityActiveHold xs:decimal

Benefit quantity, available The quantity of an item defined in the sender’s specified benefit issuance Unit of measure available for purchase

n 5 BenefitQuantityAvailable xs:decimal

Benefit quantity, expired The quantity of an item defined in the sender’s specified benefit issuance Unit of measure that have passed the last day to spend

n 5 BenefitQuantityExpired xs:decimal

Benefit quantity, issued The quantity of an item defined in the sender’s specified benefit issuance Unit of measure issued

n 5 BenefitQuantityIssued xs:decimal

Benefit quantity, redeemed The quantity of an item defined in the sender’s specified benefit issuance Unit of measure redeemed in a purchase

n 5 BenefitQuantityRedeemed xs:decimal

Benefit quantity, voided by WIC MIS

The quantity of an item defined in the sender’s specified benefit issuance Unit of measure that has been voided

n 5 BenefitQuantityVoidedByMIS xs:decimal

Benefit unit description Text description of the originator’s specified benefit issuance unit of measure, e.g., can , pkg., jar

ans, max 50; only first 6 characters are significant

BenefitUnitDescription xs:string

Business name, clinic Business name of the clinic. ansp, max ClinicName xs:string

56


Data element name Description Format XML Element Name XML Data Type 50

Business name, corporation Business name of the corporation. ansp, max 50

CorporationName xs:string

Business name, local agency Business name of the local agency. ansp, max 50

LocalAgencyName xs:string

Business name, WIC Vendor Business name of the WIC Vendor. ansp, max 50

VendorName xs:string

Card acceptor identification code A code assigned by the acquirer to identify the WIC Vendor that defines the point of service

an 15 CardAcceptorIDCode xs:string


A unique value that identifies the terminal at the WIC Vendor location

anp 8 CardAcceptorTerminalIDCode xs:string

Card number A series of digits appearing on the face of the WIC Card or encoded on the magnetic stripe of a card or assigned to a Smart Card.

n, max 19 CardNumber xs:string

Card number, replacement A series of digits used to identify the new customer account or relationship

n, max 19 CardNumberReplacement xs:string

Cardholder object Composite data element with cardholder information (see 0)

CardholderObject CardholderObject

Cardholder relationship Relationship of cardholder within the household (e.g. “Mother”)

ansp 30 CardholderRelationship xs:string

Category code A code identifying the type of product as defined in the National UPC database.

n 2 CategoryCode xs:string

Category long description A literal describing the Category code as specified by the originating WIC State Agency suitable for printing or displaying in areas where display width is not a concern.

anp 50 CategoryLongDescription xs:string

Category short description A short literal describing the Category code suitable for displaying on screen and reports where display width is a concern.

anp 20 CategoryShortDescription xs:string

Clinic ID WIC MIS assigned identifier for a clinic. n 10 ClinicID xs:integer Corporation ID A unique number assigned to a corporation

to which WIC Vendors may be associated. n 12 VendorCorporationID xs:integer

Count, detail records Count of detail records contained in the file (does not count the header record)

n 9 RecordCount xs:int

57


Data element name Description Format XML Element Name XML Data Type Date and time, host Date/time when a transaction occurred

based on date/time of EBT Card Issuer Processor system expressed in GMT in accordance with ISO 8601.


HostDateTime xs:dateTime

Date and time, local transaction Date/time when a transaction occurred based on date and time of WIC Vendor system


LocalDateTime xs:dateTime

Date and time, transmission Date and time the originator of the function sends the message or batch expressed in GMT in accordance with ISO 8601.


MessageDatetime xs:dateTime

Date, begin benefit First date on which benefits may be used. During retail transaction processing, eWIC uses midnight on this date in the local time in effect at the retail location as the starting date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

BenefitBeginDate xs:date

Date, begin category The date for which the Category code shall become available for use. During retail transaction processing, eWIC uses midnight on this date in the local time in effect at the retail location as the starting date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

CategoryBeginDate xs:date

Date, begin request Begin of period being referenced for this function. This is midnight of the UTC date.

CCYY-MM-DD

RequestBeginDate SearchStartDate

xs:date

Date, begin sub-category The date for which the Sub-Category code shall become available. During retail transaction processing, eWIC uses midnight on this date in the local time in effect at the retail location as the starting date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

SubcategoryBeginDate xs:date

Date, begin UPC/PLU The date for which the UPC/PLU data shall CCYY-MM- UpcPluBeginDate xs:date

58


Data element name Description Format XML Element Name XML Data Type become available for use. During retail transaction processing, eWIC uses midnight on this date in the local time in effect at the retail location as the starting date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

DD

Date, begin vendor The first date for which the vendor is active and may accept transactions. During retail transaction processing, eWIC uses midnight on this date in the local time in effect at the retail location as the starting date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

VendorBeginDate xs:date

Date, business The calendar date on which a transaction occurred or date reported by the EBT system for the transaction. This is the UTC date of the transaction.

CCYY-MM-DD

BusinessDate xs:date

Date, effective The calendar date on which the action is to be effective.

CCYY-MM-DD

EffectiveDate xs:date

Date, end benefit Last date on which benefits may be used. During retail transaction processing, eWIC uses 11:59:59 PM on this date in the local time in effect at the retail location as the ending date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

BenefitEndDate xs:date

Date, end category The last date for which the Category code shall be used. During retail transaction processing, eWIC uses 11:59:59 PM on this date in the local time in effect at the retail location as the ending date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

CategoryEndDate xs:date

59


Data element name Description Format XML Element Name XML Data Type Date, end request End of period being referenced for this

function. This is 11:59:59 PM of the UTC date.

CCYY-MM-DD

RequestEndDate SearchEndDate

xs:date

Date, end sub-category The last date for which the Sub- Category code shall be used. During retail transaction processing, eWIC uses 11:59:59 PM on this date in the local time in effect at the retail location as the ending date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

SubcategoryEndDate xs:date

Date, end UPC/PLU data The last date for which the UPC/PLU data shall be used. During retail transaction processing, eWIC uses 11:59:59 PM on this date in the local time in effect at the retail location as the ending date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

UpcPluEndDate xs:date

Date, end vendor The last date for which the vendor is active and may accept transactions. During retail transaction processing, eWIC uses 11:59:59 PM on this date in the local time in effect at the retail location as the ending date and time. See Appendix G - Date Field Considerations for additional considerations with respect to date fields.

CCYY-MM-DD

VendorEndDate xs:date

Date of birth, cardholder Month, day and year the cardholder was born.

CCYY-MM-DD

CardholderObject.BirthDate xs:date

Date of birth, head of household Month, day and year the head of household was born.

CCYY-MM-DD

HeadOfHouseholdObject.BirthDate xs:date

Date, recoupment activity The year, month and day of recoupment activity being summarized.

CCYY-MM-DD

ActivityDate xs:date

Date, settlement The year, month and day funds are transferred between the acquirer and the card issuer. In WIC EBT, the EBT system’s

CCYY-MM-DD

SettlementDate xs:date

60


Data element name Description Format XML Element Name XML Data Type recorded date of settlement.

Direct connect auto-recon flag A flag (0 or N for no, 1 or Y for yes) indicating whether a WIC Auto- reconciliation file is generated for the WIC Vendor location.

an 1 DirectConnectARF xs:string

Direct connect flag A flag (0 or N for no, 1 or Y for yes) indicating if the WIC Vendor connects directly to the WIC EBT System

an 1 DirectConnect xs:string

Email, corporation contact Email address of a point of contact at the corporation.

anp 254 CorporationContactEmailAddress xs:string

Email, local agency contact Email address of a point of contact at the local agency

anp 254 LocalAgencyContactEmailAddress xs:string

Email, WIC Vendor contact Email address of a point of contact at the WIC Vendor location.

anp 254 VendorContactEmailAddress xs:string

File header object A record of fields that appear in all files; see 3.2.1

BatchFileHeader BatchFileHeader

File sequence number A unique number that is incremented by 1 for each file that is successfully transferred

n 11 FileSequenceNumber xs:integer

File type Code identifying the type of file; see Appendix B.10

n 4 MessageType xs:string

FNS number Number assigned by the Supplemental Nutrition Assistance Program (SNAP) to a retail location

n 11 FNSNumber xs:integer

Forwarding institution ID code The identity of the institution forwarding the information

n 11 ForwardingInstitutionID xs:string

Function return code A value returned in a message based system interface to explicitly indicate the information sent was received and the action taken. See Appendix B.2 for values.

n 4 FunctionReturnCode xs:string

Gender A value indicating whether the person being identified is male or female

a 1, F = female, M = male, blank if not used

Gender xs:string

Head of household object A composite data element containing head of household information (see C.4)

HeadOfHouseholdObject HeadOfHouseholdObject

61


Data element name Description Format XML Element Name XML Data Type Hierarchy code A value indicating the position of the WIC

Vendor location within the corporation hierarchy. See Appendix B.3 for values.

n 1 HierarchyCode xs:string

Host generated trace number A number assigned by eWIC that uniquely identifies the transaction.

n 18 EBTTransactionID xs:string

ICD version The version of this standard ansp 20 MessageVersion xs:string Initiating user ID An identifier assigned to a WIC MIS user

that is used to track activity in the system. ansp, max 50

InitiatingUserID xs:string

Item action code Code indicating the action taken on an item; corresponds to bit 62-PS-6, see X9.93:1 for values.

n 2 ItemActionCode xs:string

Item description A name for a WIC food item ansp 50 UpcPluDescription xs:string Item NTE The NTE amount assigned to one unit of a

food item for a given peer group and in effect at the time of the transaction.

n 6 ItemNTE xs:decimal

Item price The purchase amount assigned to one unit of an item.

n 6 ApprovedItemAmount xs:decimal

Language code A code indicating the preferred language spoken by the person identified. The ANSI/ISO Z39.53:2001 standard values are used. See Appendix B.4 for more information.

a 3 LanguageCode xs:string

Line item ID Unique identifier for a line item within a transaction

n 6 LineItemID xs:integer

Local agency ID WIC MIS assigned identifier that uniquely identifies a local agency within the WIC State Agency.

an 10 LocalAgencyID xs:string

Manual voucher indicator A flag (0 or N for no, 1 or Y for yes) indicating if a food item is allowed for purchase with a manual voucher

an 1 ManualVoucherIndicator xs:string

Message header object A record of fields that appear in all real-time messages; see 3.1.1

MessageHeaderObject MessageHeaderObject

Message reason code Provide the receiver of a request, advice or notification message with the reason or purpose of that message; see X9.93 for values.

n 4 MessageReasonCode xs:short

62


Data element name Description Format XML Element Name XML Data Type Message type A value that identifies the kind of message

being sent in a message based system interface

n 4 MessageType xs:string

Name, cardholder A constructed data element including the sub-elements Name, first, Name, middle initial, Name, last and Name, suffix for the cardholder.

ansp, max 47

CardholderPersonObject PersonObject

Name, clinic contact A constructed data element including the sub-elements Name, first, Name, middle initial, Name, last and Name, suffix for a contact at the clinic.

ansp, max 47

ClinicContactPersonObject PersonObject

Name, corporation contact A constructed data element including the sub-elements Name, first, Name, middle initial, Name, last and Name, suffix for a contact at the corporation.

ansp, max 47

CorporationContactPersonObject PersonObject

Name, first Sub-element of name data elements ansp, max 20

FirstName xs:string

Name, head of household A constructed data element including the sub-elements Name, first, Name, middle initial, Name, last and Name, suffix for the head of the household

ansp, max 47

HeadOfHouseholdPersonObject PersonObject

Name, last Sub-element of name data elements ansp, max 20

LastName xs:string

Name, local agency contact A constructed data element including the sub-elements Name, first, Name, middle initial, Name, last and Name, suffix for a contact at the local agency.

ansp, max 47

LocalAgencyContactPersonObject PersonObject

Name, middle initial Sub-element of name data elements ansp, max 1

MiddleInitial xs:string

Name, suffix Sub-element of name data elements ansp, max 6

SuffixName xs:string

Name, WIC Vendor contact A constructed data element including the sub-elements Name, first, Name, middle initial, Name, last and Name, suffix for a contact at the WIC Vendor.

ansp, max 47

VendorContactPersonObject PersonObject

NTE (Not to Exceed) price The maximum allowed price for a food item n 6 NTEPrice xs:decimal

63


Data element name Description Format XML Element Name XML Data Type as established by the WIC State Agency

Number of APL types Number of iterations of APL type in the UPC/PLU record

n 4 NumberOfAPLTypes xs:short

Number of WIC Vendor peer groups

Number of iterations of WIC Vendor peer groups and NTE prices for those groups

n 2 NumberOfWicVendorPeerGroups xs:short

Operation hours The times of day when entity is available an 12, hhmmhhmm in 24 hour format

OperationHours xs:string

Original amount The amount requested by a WIC vendor for a purchase transaction for the specific item purchased. The Original amount is equal to the requested Item price times the approved Original purchase quantity and cannot be less than zero.

n 12 OriginalAmount xs:string

Original category code A code identifying the requested type of product as defined in the National UPC database.

n 2 CategoryCodeOriginal xs:string

Original host generated trace number

A number that uniquely identifies the original purchase transaction from a WIC Vendor that was subsequently reversed.

n 18 OriginalEBTTransactionID xs:string

Original item price The original purchase amount for a single food item in the original request

n 6 RequestedAmount xs:decimal

Original purchase quantity The number of items or quantity of an item originally requested (this correlates with the Purchase quantity from the Technical Implementation Guide)

n 5 RequestedQuantity xs:decimal

Original row count The line number of a record in error from the original file

n 10 OriginalRowCount xs:integer

Original sub-category code A code further identifying the requested type of product as defined in the National UPC database.

n 3 SubcategoryCodeOriginal xs:string

Originator of file Unique identifier of the entity that is sending the file, e.g., Forwarding institution ID, WIC EBT system ID or WIC MIS System ID

n 11 FileOriginiator xs:string

64


Data element name Description Format XML Element Name XML Data Type Package size The size of the contents of the package

quantified in the standard benefit units of measure

n 5 PackageSize xs:decimal

Password Valid used in conjunction with WIC MIS system ID to validate the authenticity of the calling system

an 20 Password xs:string

Phone number, alternate corporation contact

Other phone number for a point of contact at the corporation

n 7 or n 10 CorporationSecondaryPhoneNumber

xs:string

Phone number, alternate WIC Vendor contact

An alternate phone number of a point of contact at the WIC Vendor.

n 7 or n 10 VendorSecondaryPhoneNumber xs:string

Phone number, cardholder Phone number for cardholder. n 7 or n 10 CardholderObject.PhoneNumber xs:string Phone number, clinic contact Phone number for the clinic. n 7 or n 10 ClinicContactPhoneNumber xs:string Phone number, corporation contact

Phone number for the corporation n 7 or n 10 CorporationContactPhoneNumber xs:string

Phone number, local agency contact

Phone number for the local agency. n 7 or n 10 LocalAgencyContactPhoneNumber xs:string

Phone number, WIC Vendor contact

The phone number for a point of the contact at the WIC Vendor.

n 7 or n 10 VendorPrimaryPhoneNumber xs:string

PIN, encrypted A number assigned to a cardholder intended to uniquely identify that cardholder at the point of service; ASCII encoded encrypted block

an 100 EncryptedPIN xs:string

PIN activity code A value returned to indicate changes made to PINs associated with cards. See Appendix B.5 for values.

n 4 PINActivityCode xs:string

PIN status code A code identifying whether the PIN associated with the card is locked or unlocked

a 1, N = unlocked (default), Y = locked, U = not selected

PINStatusCode xs:string


A sub-element of POS data code that indicates the primary means of getting the information on the card into the terminal. See Appendix 0 for values

an 1 POSDataCodeCardDataInputCapability

xs:string

65


Data element name Description Format XML Element Name XML Data Type POS data code, cardholder authentication capability

A sub-element of POS data code that indicates the primary means of verifying the cardholder at this terminal. See Appendix 0 for values

an 1 POSDataCodeCardholderAuthenticationCapability

xs:string


A sub-element of POS data code that indicates whether or not the terminal has the ability to capture a card. See Appendix 0 for values

an 1 POSDataCodeCardCaptureCapability

xs:string


A sub-element of POS data code that indicates if the terminal is attended by the Card acceptor and its location. See Appendix 0 for values

an 1 POSDataCodeOperatingEnvironment

xs:string

POS data code, cardholder present A sub-element of POS data code that indicates if the cardholder is present at the POS or not and if not why not. See Appendix 0 for values

an 1 POSDataCodeCardholderPresent xs:string

POS data code, card present A sub-element of POS data code that indicates if the card is present at the POS or not. See Appendix 0 for values

an 1 POSDataCodeCardPresent xs:string


A sub-element of POS data code that indicates the method used to input the information from the card to the terminal. See Appendix 0 for values. This is the field that indicates manual card entry.

an 1 POSDataCodeCardDataInputMode xs:string


A sub-element of POS data code that indicates the method for verifying the cardholder. See Appendix 0 for values

an 1 POSDataCodeCardholderAuthenticationMethod

xs:string


A sub-element of POS data code that indicates the entity verifying the cardholder. See Appendix 0 for values

an 1 POSDataCodeCardholderAuthenticationEntity

xs:string


A sub-element of POS data code that indicates the ability of the terminal to update the card. See Appendix 0 for values

an 1 POSDataCodeCardDataOutputCapability

xs:string


A sub-element of POS data code indicating the ability of the terminal to print/display

an 1 POSDataCodeTerminalOutputCapability

xs:string

66


Data element name Description Format XML Element Name XML Data Type messages. See Appendix 0 for values


A sub-element of POS data code indicating the length of PIN which a terminal is capable of capturing. See Appendix 0 for values

an 1 POSDataCodePINCaptureCapability xs:string

Price type A code indicating the kind of price being sent in the record; distinguishes CVB items from non-CVB items; values are “03” for CVB and “00” for non-CVB

an 2 PriceType xs:string

Purchase indicator A flag (0 or N for no, 1 or Y for yes) indicating a food item that can be purchased with benefits assigned in a non-zero Sub-Category code (any Sub-Category code that is not equal to “000”) as well as with benefits assigned in the Broadband Sub- Category code; values are 1 to indicate that item may be purchased with benefits in Broadband and 0 to indicate that item may not be purchased with benefits in Broadband (see Technical Implementation Guide for more details)

an 1 PurchaseIndicator xs:string

Purchase quantity The number of items or quantity of an item being purchased (this correlates with the Purchase quantity from the Technical Implementation Guide)

n 5 ApprovedQuantity xs:decimal

Reason code Reason for an action; see Appendix B.6 for values

an 4 ACHReasonCode BenefitReasonCode VendorReasonCode RecoupmentReasonCode

xs:string

Rebate flag A flag (0 or N for no, 1 or Y for yes) indicating that a food item is eligible for rebate to the WIC State Agency

an 1 RebateFlag xs:string


Code identifying the entity receiving the message or batch

n 11 ReceivingInstitution xs:string

Record sequence number A sequential number assigned to each record within a batch by the batch sender

n 6 RecordSequenceNumber xs:integer

67


Data element name Description Format XML Element Name XML Data Type Recoupment processing month The first of the month used to calculate the

new amount, recoupment CCYY-MM-DD

ProcessingMonth xs:date

Rejected row count Number of rows (lines) rejected from original file

n 10 RejectedCount xs:integer

Status code A code indicating the status of the entity indicated. See Appendix B.6 for values.

an 4 CardholderStatusCode xs:string

Sub-Category code A code further identifying the type of product within a Category code as defined in the National UPC database.

n 3 SubcategoryCode xs:string

Sub-Category long description A long description of the Sub-Category code suitable for printing or displaying in areas where display width is not a concern.

anp 50 SubcategoryLongDescription xs:string

Sub-Category short description A short description of the Sub- Category code suitable for displaying in areas (particularly POS stand-beside receipts) where display width is a concern.

anp 24 SubcategoryShortDescription xs:string

Systems trace audit number A number assigned by the message initiator to uniquely identify a transaction in WIC redemption processing

n 6 SystemTraceAuditNumber xs:integer

Transaction reason code Provides the reason the transaction was declined or adjusted. Value is the action code (bit 39) for WIC Online EBT; see Technical Implementation Guide for corresponding values.

n 4 TransactionReasonCode xs:string

Type code A code indicating the kind of entity being acted or reported upon in the function, See Appendix B.7 for values.

an 1 TypeCode FileTypeCode VendorTypeCode TransactionTypeCode RecoupmentTypeCode

xs:string

Unique EBT transaction identifier A number that uniquely identifies a transaction from a clinic, WIC Vendor or other party within the WIC MIS and WIC EBT system interface.

n 18 UniqueTransactionID (Online) UniqueTransactionIdentifier (Batch)

xs:string

Unit of measure A determinant amount or quantity adopted as a standard of measurement, e.g.,

an 10 BenefitUnitDescription xs:string

68


Data element name Description Format XML Element Name XML Data Type gallons, pounds, etc. applied to an individual item, see TIG and ANS 260.1.

Units Number of benefits deducted in the redemption

n 5 BenefitsDeducted xs:decimal

UPC/PLU data Information identifying the UPC or PLU assigned to an item; see Technical Implementation Guide for formatting.

n 17 UpcPluCode xs:string

UPC/PLU data length Indicate the number of significant digits in the UPC or PLU

n 2 UpcPluDataLength xs:string

Username String used to identify user in the WIC EBT System. Used in conjunction with the WIC EBT System ID to uniquely identify a user.

ans 50 Username xs:string

WIC EBT system ID Value identifying the WIC EBT system n 3 WICEBTSystemID xs:string WIC MIS account ID Value assigned by the WIC MIS to identify

an account for a WIC participant, economic unit or household

an, min 2, max 19

HouseholdID WICMISAccountID

xs:string

WIC MIS account ID, new New value assigned by the WIC MIS to identify an account for a WIC participant, economic unit or household

an, min 2, max 19

NewHouseholdID xs:string

WIC MIS system ID Value identifying the WIC Management Information System

n 3 WICMISSystemID xs:string

WIC MIS WIC Vendor ID Value assigned by the WIC Management Information System to identify the WIC Vendor equal to WIC merchant ID from X9.93

an 12 VendorID xs:string

WIC State Agency ID Value assigned by FNS to identify the WIC State Agency; see TIG for values.

n 3 WICStateAgencyID xs:string

WIC Vendor peer group ID An identifier assigned to a set of vendors defined by the WIC State Agency for managing cost containment

n 5 PeerGroupID xs:integer

WIC Vendor tax ID A value identifying the federal and/or state tax identification number assigned to the WIC Vendor

n 9 FederalTaxID xs:string

Workstation ID A value identifying the workstation initiating the function.

an 20 WorkstationID xs:string

69


Appendix B - Data Element Code Tables The Data Element Code tables list the code values assigned for the data elements used in the Universal Interface in alphabetical order.

B.1 Action Code The Action code is used to identify the action to be taken in a function. The following table defines the values.

Value Description 001 Activate or Add 002 Change or Update 003 Deactivate or Subtract 005 Reactivate or Unlock 006 Hold

B.2 Function Return Code Message based interfaces return a positive confirmation in the form of a four character numeric string.

The Function return code is used to identify the action taken in response to a request. The following table defines the Function return code values defined in the WUMEI.

Value Description 0000 accepted (no errors) 0001 Rejected 0003 Modified

The following sections detail the Function return code values that are returned by the MIS to EBT interface functions.

General validations performed on Security Authorization parameter of all message based interface functions and Batch File Header records. The term Invalid is intended to encompass validation of values that don’t meet expectation of exchange and string values that exceed maximum defined lengths. The term Missing is intended to note values that are required but not provided.

Value Description 0101 Invalid/Missing WIC State Agency ID 0102 Invalid/Missing WIC MIS System ID 0103 Invalid/Missing Password 0104 Invalid/Missing Message Type 0105 Invalid/Missing EBT System ID 0106 Invalid/Missing Message Version 0107 Invalid/Missing Message Date and Time 0108 Provided WIC Clinic ID was Invalid 0109 Invalid/Missing Username 0110 Provided Workstation ID was Invalid 0111 System Locked Out


Value Description 0112 Invalid/Missing File Sequence Number 0113 Provided File Sequence Number is transmitted out of order 0114 Invalid/Missing Record Count 0115 Invalid/Missing Rejected Count 0116 Invalid/Missing Original Row Count 0117 Invalid/Missing Function Return Code 0118 Duplicate File Has Already Been Processed 0119 Invalid/Missing Initiating User ID 0120 Invalid/Missing Local Agency ID 0121 Invalid/Missing Unique Transaction ID 0122 Invalid/Missing Action Code 0123 System Not Authorized To Perform Action 0197 Missing Security Authorization Object 0198 Batch File corruption or other general processing error 0199 Database communication error 9999 Unknown (internal) error

Validations performed on the data parameters of the MIS to EBT interface functions.

Value Description 1001 Missing Household Function Parameter Object 1002 Missing Head of Household Person Object 1003 WIC MIS Account ID already exists 1004 WIC MIS Account ID is not known to the EBT System 1005 Invalid/Missing Household Status ID 1006 Invalid/Missing Household Type ID 1007 Provided Email Address was Invalid 1008 Invalid/Missing Cardholder Relationship 1009 Invalid/Missing Cardholder Gender 1010 Invalid/Missing Cardholder Language Code 1011 Invalid/Missing Cardholder Phone Number 1012 Account Does Not Have a Primary Cardholder 1013 Account Id and Account Type do not match 1015 Invalid/Missing Cardholder Mailing Address Line 1 1016 Invalid/Missing Cardholder Mailing Address Line 2 1017 Invalid/Missing Cardholder Mailing Address City 1018 Invalid/Missing Cardholder Mailing Address State 1019 Invalid/Missing Cardholder Mailing Address Zip Code 1020 Invalid/Missing WIC MIS Account ID Number 1021 Provided WIC MIS Account ID is Invalid 1022 Invalid/Missing Reason Code 1024 Invalid/Missing Head of Household Last Name 1025 Provided Household Mailing Address had an Invalid/Missing Street Address Line 1 1026 Provided Household Mailing Address had an Invalid/Missing City 1027 Provided Household Mailing Address had an Invalid/Missing State Abbreviation 1028 Provided Household Mailing Address had an Invalid/Missing Zip Code 1029 Household Mailing Address is Missing 1030 Invalid/Missing Head of Household Date of Birth 1031 Invalid/Missing Head of Household Gender 1032 Invalid/Missing Head of Household Language Code

71


Value Description 1033 Head of Household Name is Missing 1034 Provided Head of Household Person Object’s Suffix was Invalid 1035 Provided Card is Active 1036 Provided Card has been Replaced 1045 Provided Household Mailing Address had an Invalid/Missing Street Address Line 2 1046 Invalid/Missing Head of Household First Name 1047 Invalid/Missing Head of Household Middle Name 1059 EBT Card Number has already been issued 1060 Replacement EBT Card Number has already been issued 1061 Not Enough Filtering Parameters Were Provided 1062 EBT Card Number is Inactive 1301 Invalid/Missing EBT Card Number 1302 Invalid/Missing Cardholder Type ID 1303 Missing Cardholder Person Function Parameter Object 1304 Primary Cardholder already exists for the Household 1305 Number of active Cardholders is exceeded by this new Cardholder 1306 Invalid/Missing Cardholder Last Name 1307 Invalid/Missing Cardholder Date of Birth 1308 Provided Cardholder Person Object’s First Name was Invalid 1309 Provided Cardholder Person Object’s Middle Name was Invalid 1310 Provided Cardholder Person Object’s Email Address was Invalid 1311 Cardholder name is a duplicate for the Household 1312 Invalid/Missing Cardholder Id Provided 1313 Provided Cardholder Person Object’s Suffix was Invalid 1314 PIN number for cardholder/number is not locked. 1315 No search results found for the entered filter criteria 1316 Invalid/Missing Replacement Card Number 1401 EBT Card Number is not known to the EBT System 1402 Invalid/Missing Card Status Date 1403 Invalid/Missing Card Status ID 1404 Invalid/Missing Card Status Reason ID 1405 Invalid Card Status/Reason Code combination 1601 Invalid/Missing Encrypted PIN Block 1602 EBT Card number provided doesn’t match with the WIC MIS Account ID 1603 Invalid/Missing Effective Date 1604 Dual PIN Blocks do not match 1605 Provided Card Number Not Primary Card on Account 1606 Account Does Not Have an Active Primary Card 1607 PIN Failure Count Exceeded 2001 Missing Monthly Food Benefit Function Parameter Object 2002 EBA is not active 2004 Unique Benefit ID already exists thus indicating a Duplicate Benefit Adjustment 2006 Benefit timeframe provided doesn’t match to a Category/Sub-Category balance with

sufficient quantity to post the entire debit 2007 Invalid/Missing Credit/Debit ID 2008 Invalid/Missing Benefit Start Date 2009 Invalid/Missing Benefit End Date 2013 Invalid/Missing Category Code 2014 Invalid/Missing Sub-category Code

72


Value Description 2015 Invalid/Missing Benefit Quantity 2017 Resulting Food Benefit Quantity exceeds 999.99 2019 Benefit End Date cannot precede the Benefit Start Date 2021 Invalid/Missing Benefit Reason ID 2022 Invalid/Missing Unique Benefit ID 2023 Invalid/Missing APL type 2044 Invalid/Missing Clinic ID 2046 Category/Sub-category combination is not active 2050 Benefit timeframe provided would overlap an existing benefit timeframe containing

valid benefits for the Family, which is not allowed. 3202 Provided Search Start Date is Invalid 3203 Provided Search End Date is Invalid 3204 Search End Date cannot be before Search Start Date 3205 Invalid/Missing Maximum Requested Count 3206 Neither the WIC MIS Account ID nor the EBT Card Number was provided 3207 Date Range must be less than the value in the system setting 3601 Provided Card Status ID was Invalid 3602 Provided Cardholder Person Object’s Last Name was Invalid 3603 Provided Cardholder Person Object’s Date of Birth was Invalid 3604 Provided Cardholder has been Deactivated and Access Restricted 3701 Supplied PIN was not correctly verified 4001 Missing Vendor Function Parameter Object 4036 Vendor ID was not known to the EBT System 4037 Vendor ID already exists 4038 Invalid/Missing Vendor ID 4039 Invalid/Missing Vendor Name 4040 Invalid/Missing Peer Group ID 4042 Invalid/Missing Vendor Status ID 4045 Invalid/Missing Above 50% Vendor Code 4046 Invalid/Missing Vendor Type ID 4047 Invalid/Missing Federal Tax ID 4048 Invalid/Missing Direct Connect Flag 4049 Invalid/Missing Direct Connect ARF flag 4051 Missing Vendor Physical Address Object 4052 Missing Vendor Mailing Address Object 4055 Invalid/Missing Vendor Physical Address’ Line 1 4056 Invalid/Missing Vendor Physical Address’ City 4057 Invalid/Missing Vendor Physical Address’ State Abbreviation 4058 Missing Vendor Contact Person Object 4059 Invalid/Missing Vendor Mailing Address’ Line 1 4060 Invalid/Missing Vendor Mailing Address’ City 4061 Invalid/Missing Vendor Mailing Address’ State Abbreviation 4062 Invalid/Missing Vendor Primary Phone Number 4063 Provided Vendor Secondary Phone Number was Invalid 4066 Provided Corporation ID was Invalid 4067 Provided Vendor Physical Address’ Line 2 was Invalid 4068 Provided Vendor Mailing Address’ Line 2 was Invalid 4070 Invalid/Missing Vendor Authorization Start Date 4071 Invalid/Missing Vendor Authorization End Date

73


Value Description 4073 Invalid/Missing Vendor Physical Address’ Zip Code 4074 Invalid/Missing Vendor Mailing Address’ Zip Code 4075 Authorization End Date cannot be before the Authorization Start Date 4080 Missing Vendor Banking Information Object 4081 Invalid/Missing Vendor Banking Information’s Bank Name 4082 Invalid/Missing Vendor Banking Information’s ABA Routing Transit Number 4083 Invalid/Missing Vendor Banking Information’s Bank Account Number 4084 Invalid/Missing Banking Account Type ID 4090 Invalid/Missing Vendor Contact Person’s First Name 4091 Invalid/Missing Vendor Contact Person’s Last Name 4092 Provided Vendor Contact Person’s Middle Name was Invalid 4093 Provided Vendor Contact Person’s Email Address was Invalid 4094 Provided Vendor Contact Person’s Date of Birth was Invalid 4095 Provided Vendor Contact Person Object’s Suffix was Invalid 4096 Invalid/Missing Vendor Reason Code 4097 Invalid/Missing ACH Settlement Time 4098 Invalid/Missing FNS Number 4099 Invalid/Missing Total Food Sales Amount 5001 Missing Local Agency Function Parameter Object 5002 Local Agency ID already exists 5003 Local Agency ID is unknown to the EBT System 5005 Invalid/Missing Local Agency Name 5006 Missing Local Agency Contact Person Object 5007 Invalid/Missing Local Agency Contact Person’s First Name 5008 Invalid/Missing Local Agency Contact Person’s Last Name 5009 Provided Local Agency Contact Person’s Middle Name was Invalid 5010 Provided Local Agency Contact Person’s Email Address was Invalid 5011 Provided Local Agency Contact Person’s Date of Birth was Invalid 5012 Missing Local Agency Mailing Address Object 5013 Invalid/Missing Local Agency Mailing Address’ Line 1 5014 Provided Local Agency Mailing Address’ Line 2 was Invalid 5015 Invalid/Missing Local Agency Mailing Address’ City 5016 Invalid/Missing Local Agency Mailing Address’ State Abbreviation 5017 Invalid/Missing Local Agency Mailing Address’ Zip Code 5018 Invalid/Missing Local Agency Primary Phone Number 6001 Missing Clinic Function Parameter Object 6002 Clinic ID already exists 6003 Clinic ID is unknown to the EBT System 6005 Invalid/Missing Clinic Name 6006 Missing Clinic Contact Person Object 6007 Invalid/Missing Clinic Contact Person’s First Name 6008 Invalid/Missing Clinic Contact Person’s Last Name 6009 Provided Clinic Contact Person’s Middle Name was Invalid 6010 Provided Clinic Contact Person’s Email Address was Invalid 6011 Provided Clinic Contact Person’s Date of Birth was Invalid 6012 Missing Clinic Mailing Address Object 6013 Invalid/Missing Clinic Mailing Address’ Line 1 6014 Provided Clinic Mailing Address’ Line 2 was Invalid 6015 Invalid/Missing Clinic Mailing Address’ City

74


Value Description 6016 Invalid/Missing Clinic Mailing Address’ State Abbreviation 6017 Invalid/Missing Clinic Mailing Address’ Zip Code 6018 Invalid/Missing Clinic Phone Number 7001 Invalid/Missing Corporation ID 7002 Invalid/Missing Corporation Name 7003 Invalid/Missing Corporation Contact Person’s First Name 7004 Invalid/Missing Corporation Contact Person’s Last Name 7005 Provided Corporation Contact Person’s Middle Name was Invalid 7006 Provided Corporation Contact Person’s Email Address was Invalid 7007 Provided Corporation Contact Person’s Date of Birth was Invalid 7008 Invalid/Missing Corporation Mailing Address’ Line 1 7009 Provided Corporation Mailing Address’ Line 2 was Invalid 7010 Invalid/Missing Corporation Mailing Address’ City 7011 Invalid/Missing Corporation Mailing Address’ State Abbreviation 7012 Invalid/Missing Corporation Mailing Address’ Zip Code 7013 Invalid/Missing Corporation Primary Phone Number 7014 Provided Corporation Secondary Phone Number was Invalid 7015 Invalid/Missing Corporation Banking Information’s Bank Name 7016 Invalid/Missing Corporation Banking Information’s ABA Routing Transit Number 7017 Invalid/Missing Corporation Banking Information’s Bank Account Number 7101 Invalid/Missing Vendor Operational Activation Code 7102 Invalid/Missing Vendor Operational Activation Effective Start Date 7201 Invalid or Missing processing month 7202 Invalid or Missing Recoupment Type Code 7203 Invalid or Missing Recoupment Amount 7204 Invalid or Missing Record Sequence Number 7205 Additional Recoupment Amount Would Exceed Maximum For Merchant 7206 Provided Vendor Type Not Permitted 7207 Insufficient Benefits for Authorization 7208 Authorization quantity must be whole number for given product code. 7209 No Matching Benefit Authorization Found 8001 Invalid/Missing Category Description 8002 Invalid/Missing Subcategory Description 8003 Invalid/Missing Unit of Measure Description 8004 Invalid/Missing Activation Date 8005 Provided Deactivation Date is Invalid 8006 Invalid/Missing Category Begin Date 8007 Invalid/Missing Category End Date 8008 Invalid/Missing Subcategory Begin Date 8009 Invalid/Missing Subcategory End Date 8010 A Subcategory Code Which Was Omitted From the File Has Active Benefits in System 8011 Invalid/Missing Vendor Effective Date 8012 Invalid/Missing Original EBT Transaction ID 8013 Invalid/Missing POS data code card data input capability 8014 Invalid/Missing POS data code cardholder authentication capability 8015 Invalid/Missing POS data code, card capture capability 8016 Invalid/Missing POS data code, operating environment 8017 Invalid/Missing POS data code, cardholder present 8018 Invalid/Missing POS data code, card present

75


Value Description 8019 Invalid/Missing POS data code, card data input mode 8020 Invalid/Missing POS data code, cardholder authentication method 8021 Invalid/Missing POS data code, cardholder authentication entity 8022 Invalid/Missing POS data code, card data output capability 8023 Invalid/Missing POS data code, terminal output capability 8024 Invalid/Missing POS data code, PIN capture capability 8025 Invalid/Missing NTE Adjustment Amount 8026 Invalid/Missing Approved Item Amount 8027 Invalid/Missing Original Line Number 8028 Invalid/Missing Status Code 8100 UPC/PLU Will Expire Before Provided Benefit End Date 8101 Invalid/Missing UPC or PLU Code 8102 Invalid/Missing UPC or PLU Description 8103 Invalid/Missing Broadband Flag 8104 Invalid/Missing Package Size 8106 Invalid/Missing Exchange Size 8107 Invalid/Missing Rebate Flag 8108 Invalid/Missing UPC or PLU Effective Start Date 8109 Invalid/Missing UPC or PLU Deactivation Start Date 8110 Invalid/Missing NTE Price 8111 Invalid/Missing Manual Authorization Flag 8112 Invalid/Missing Is PLU Flag 8113 Invalid/Missing Purchase Indicator 8114 Invalid/Missing UPC or PLU Code Length 8115 Invalid/Missing Number of WIC Vendor Peer Groups 8116 Invalid/Missing Price Type 8117 Invalid/Missing Peer Group NTE Price Object 8118 Invalid/Missing Number of APL Types 8801 Invalid/Missing EBT’s Transaction ID 8802 Invalid/Missing Redemption Transaction Type ID 8803 Invalid/Missing EBT’s Transaction Date and Time 8804 Invalid/Missing Vendor’s Transaction Date and Time 8805 Invalid/Missing Settlement Date 8806 Invalid/Missing Business Date 8807 Invalid/Missing Forwarding Institution ID 8808 Invalid/Missing Receiving Institution ID 8809 Invalid/Missing Acquiring Institution ID 8810 Invalid/Missing Terminal ID 8811 Invalid/Missing Requested Amount 8812 Invalid/Missing Settled Amount 8813 Invalid/Missing Total NTE Adjustments 8814 Invalid/Missing Discount Amount 8815 Invalid/Missing Requested Purchase Detail Amount 8816 Invalid/Missing UPC Category Code 8817 Invalid/Missing UPC Subcategory Code 8818 Invalid/Missing Requested Quantity 8819 Invalid/Missing Paid Amount 8820 Invalid/Missing Benefit Category Code 8821 Invalid/Missing Benefit Subcategory Code

76


Value Description 8822 Invalid/Missing Approved Quantity 8823 Invalid/Missing Record Sequence Number 8901 Invalid/Missing Payment Trace Number 8902 Invalid/Missing Payor Vendor ID 8903 Provided Vendor ID is unknown to the EBT System 8904 Invalid/Missing Payment Amount 8905 Provided Descriptive Purpose is Invalid 8906 Provided System Trace Audit Number is Invalid 8907 Provided System Trace Audit Number is unknown to the EBT System 8908 Invalid/Missing Payment Effective Date 8909 Invalid/Missing Category Short Description 8910 Invalid/Missing Subcategory Short Description 8911 Invalid/Missing Payor Name 8914 Invalid/Missing Hierarchy Code 8915 Invalid/Missing Card Acceptor ID Code 9000-9998 Reserved range

B.3 Hierarchy Code The Hierarchy code is used to identify the level of the WIC Vendor within the corporate organization structure. The following table defines the values.

Value Description 0 No hierarchy 1 Level 1, vendor 2 Level 2 3 Level 3 4 Corporate headquarters

B.4 Language Code The Language code is used to identify the language to be used with the WIC MIS account users. The ANSI/ISO Z39.53:2001 standard values are used. The following table defines the most common Language code values used in WIC EBT, see the standard for a complete list.

Value Description crp Creole eng English spa Spanish oth Other

B.5 PIN Activity Code The PIN activity code is used to identify changes made to the PIN associated with the card. The following table defines the values.

Value Description 0000 Default

77


Value Description 0001-2599 Reserved 2600 PIN change 2601 PIN unlock (administrative) 2602 PIN lock 2603-9999 Reserved

B.6 Reason Code The Reason code is used to explain the action being requested or taken in a function. The following table defines the values.

Function Value Description EBA add/update E001 New

E002 Account data update E003 Fraud E004 Hold expired

Card add/update C001 Lost C002 Stolen C003 Damaged after issued C004 Returned C005 Undeliverable C006 Damaged before issued C007 Issued C008 Hold expired C009 Compromised, other than lost or stolen C010 Hold requested C011 Cardholder data update C012 Failed to function prior to issuance C013 Missing - delivered but prior to issuance C014 Failed to function after issuance C015 Dual participation, card in C016 Administrative lock C017 Change in family status C018 Cancel and restrict access (this Reason code applies to the

cardholder; a cardholder with this Reason code cannot receive a replacement card)

C019-C098 Reserved C099 Other C100-C998 Reserved C999 PIN Change Activity

Benefit add/update B001 New benefit issuance B002 WIC participant request B003 Voluntary withdrawal of authorization B004 Involuntary withdrawal of authorization B005 WIC disqualification B006 Nutrition evaluation

78


Function Value Description B007 Deceased B008 Formula exchange B009 Benefit data update

Local agency or clinic add/update

L001 New local agency

L002 New clinic L003 Local agency or clinic relocated L004 Local agency or clinic closed L005 Local agency or clinic data update

Vendor add/update V001 Vendor not WIC EBT certified and functional V002 Vendor WIC EBT certified and functional V003 Vendor WIC EBT certified only V004 Vendor WIC EBT functional only V005 Vendor ineligible for reactivation V006 Vendor eligible to be paid V007 Vendor payment withheld V008 Vendor data update

ACH payment P001 Adjustment P002 Payment to warehouse P003 ACH payment update

B.7 Status Code The Status code is used to describe the condition of the entity acted or reported upon in a function. The following table defines the values.

Value Description A001 Activated A002 Deactivated A003 Reactivated A004 Lost card A005 Stolen card A006 Valid/ready to shop card A007 On hold (in eWIC , A007 On hold is synonymous with A002 Deactivated)

B.8 Type Code The Type code is used to describe the action or entity being acted or reported upon in a function. The following table defines the values.

Function Value Description Type code, cardholder P Primary cardholder

S Secondary cardholder X Proxy cardholder

Type code, file N New file R Replacement file U Update file

Type code, transaction A Debit Adjustment, specific transaction

79


Function Value Description B Purchase C Credit Adjustment, specific transaction D Debit/Subtract E Expunged/expired F Future benefit issuance/add G Future benefit void H Hold I Issuance/Add J Debit Adjustment, non-specific transaction K Reversal of hold M Manual authorization clear Q Balance inquiry R Reversal S Store and forward purchase T Credit Adjustment, non-specific transaction V Void of a purchase

Type code, vendor C Chain F Farmers market (FMNP and CVB) G Farmers market (FMNP only) H Farmers market (CVB only) I Independent grocer L Sole proprietor W Warehouse Y Pharmacy

Type code, WIC MIS account D Emergency disaster E Educational H Household O Compliance buy V Vendor

Type code, recoupment requests

C Credit (adjustment)

D Debit (adjustment) N New recoupment (initial credit)

B.8.1 Vendor Type Code Considerations The following table lists those Type code, vendor values that must be supported by WIC MIS for state agencies which require that eWIC performs special processing based upon the vendor type. If a state agency does not require special processing for eWIC , then the Type code, vendor value should not be used.

Value Description eWIC Processing W Warehouse This setting causes eWIC to perform validation on a eWIC

generated authorization code in lieu of a cardholder PIN. This is intended for “warehouse” vendors that may be shipping WIC-approved items for a cardholder from a central location where the cardholder is not present at the time of order fulfillment.

80


B.8.2 WIC MIS Account Type Code Considerations The following table lists those Type code, WIC MIS account values that must be supported by WIC MIS for state agencies which require that eWIC performs special processing based upon the WIC MIS account type. If a state agency does not require special processing for eWIC , then the Type code, WIC MIS account value should not be used.

Value Description eWIC Processing E Educational A household with this setting appears “normal” by default to

most users of eWIC . However, users with certain security roles defined by the state agency may be able identify that the household is an educational household for research purposes. O Compliance buy A household with this setting appears “normal” by default to most users of eWIC . However, users with certain security roles defined by the state agency may be able identify that the household is a compliance household for research purposes.

B.9 Message Type The Message type is used to identify the function. The following table defines the values.

Value Description 1000 Add EBA 1100 Update EBA 1200 Get EBA Details 1300 Add Cardholder/Card 1400 Update Cardholder/Card 1700 Add or Update PIN 1701 Validate PIN 1800 Get Warehouse Authorizations 1850 Get Warehouse Authorization Code 1900 Request Warehouse Authorization 1950 Void Warehouse Authorization 2000 Add or Update Benefits 3200 Get Benefit Balance 3300 Get Benefit Maintenance History 3400 Get Benefit Redemption History 3600 Get Cardholders/Cards 3700 Get Card History 4100 Request ACH Payment

B.10 File Type The File type is used to identify the function. The following table defines the values.

Value Description Extension 9000 WIC Card Updates File .ccxml-2014 9100 WIC Vendor File .wvxml-2014 9400 WIC Category/Sub-category File .csxml-2014 9500 WIC UPC/PLU File .upnxml-2014 9600 WIC Daily Interface Reconciliation File .bxml-2014

81


Value Description Extension 9700 WIC Benefit Redemption File .rxml-2014 9701 WIC Benefit Redemption Reversals File .rrxml-2012 9750 WIC Benefits Purged File .bpxml-2014 9800 WIC ACH Payment Report File .achsxml-2014 9850 WIC ACH Payment Request File .achxml-2014 9900 WIC Recoupment Requests File .wrrxml-2014 9901 WIC Recoupment Status File .wrsxml-2014

B.11 ICD Version The ICD version is used to identify the version of the ICD from which the function is drawn. The following table defines the values.

Value Description ICD.2012.1.0 Version 1.0 ICD based on the 2012 interface. ICD.2014.2.5 Version 2.5 (or higher) ICD based on the 2014 interface.

B.12 WIC EBT System ID The WIC EBT System ID is used to identify the EBT system. The following table defines the values.

Value Description 1 JP Morgan 2 Xerox 3 CDP/FIS

B.13 WIC MIS System ID The WIC MIS System ID is used to identify the MIS system. The following table defines the values.

Value Description 1 eWIC 3 Crossroads (WV) 4 CMS (KY) 5 FIS IVR 6 Participant Portal 7 STORC (WV) 8 FL-WiSE (FL) 9 JPMA 10 EOS (MA) 11 SPIRIT (ME) 12 ROSIE (WI) 13 TWIST (OR) 14 FIS Gateway 15 MPSC (IA) 16 MPSC (CO) 17 SPIRIT (C4) 18 WOW (DE) 19 Open Domain (NV) 20 Open Domain (I5)

82


Value Description 21 SDWIC-IT (SD) 22 SPIRIT (C4 Summer) 23 Open Domain (NV Summer) 24 SWEM-SC (MO) 25 MIS Placeholder (A1) 26 SPIRIT (AK) 27 MIS Placeholder (AL) 28 MIS Placeholder (AR) 29 HANDS (AS) 30 HANDS (AZ) 31 MIS Placeholder (C1) 32 MIS Placeholder (C2) 33 MIS Placeholder (C3) 34 SPIRIT (C5) 35 MIS Placeholder (C6) 36 HANDS (C7) 37 MIS Placeholder (CA) 38 MIS Placeholder (CT) 39 MIS Placeholder (DC) 40 MIS Placeholder (E1) 41 MIS Placeholder (E2) 42 MIS Placeholder (F1) 43 MIS Placeholder (GA) 44 HANDS (GU) 45 MIS Placeholder (HI) 46 MIS Placeholder (I1) 47 SPIRIT (I2) 48 MIS Placeholder (I3) 49 STARS (I4) 50 MIS Placeholder (I5) 51 MIS Placeholder (ID) 52 MIS Placeholder (IL) 53 MIS Placeholder (IN) 54 KWIC (KS) 55 MIS Placeholder (LA) 56 SPIRIT (M2) 57 MIS Placeholder (MD) 58 MIS Placeholder (MI) 59 MIS Placeholder (MN) 60 MIS Placeholder (MO) 61 MIS Placeholder (MS) 62 MIS Placeholder (MT) 63 MIS Placeholder (N1) 64 HANDS (N2) 65 MIS Placeholder (NC) 66 MIS Placeholder (ND) 67 MPSC (NE) 68 MIS Placeholder (NH) 69 MIS Placeholder (NJ)

83


Value Description 70 MIS Placeholder (NM) 71 MIS Placeholder (NY) 72 SPIRIT (O1) 73 SPIRIT (O2) 74 MIS Placeholder (OH) 75 MIS Placeholder (OK) 76 MIS Placeholder (P1) 77 SPIRIT (P2) 78 MIS Placeholder (PA) 79 MIS Placeholder (PR) 80 MIS Placeholder (R2) 81 MIS Placeholder (RI) 82 MIS Placeholder (S1) 83 MIS Placeholder (S2) 84 MIS Placeholder (S3) 85 MIS Placeholder (S6) 86 MIS Placeholder (S7-060) 87 MIS Placeholder (S7-071) 88 MIS Placeholder (SC) 89 MIS Placeholder (T1) 90 MIS Placeholder (TN) 91 MIS Placeholder (TX) 92 MIS Placeholder (U1) 93 MIS Placeholder (UT) 94 MIS Placeholder (VA) 95 MIS Placeholder (VI) 96 MIS Placeholder (VT) 97 SPIRIT (W1) 98 MIS Placeholder (W2) 99 Crossroads (WA) 100 MIS Placeholder (WY) 101 MIS Placeholder (Z1) 102 MPSC (NZ) 103 MPSC (I9) 104 MPSC (NZ Summer) 105 RMS (KY) 106 EzWIC (AZ)

B.14 POS Data Code The POS data code is a 12-position data element providing information about the environment at the point of sale. The following table lists the POS data code values. See X9.93:1 for usage.

Function Value Description Card data input capability 0 Unknown

1 Manual, no terminal 2 Magnetic stripe read 3 Bar code 4 OCR

84


Function Value Description 5 ICC 6 Key entered

Cardholder authentication capability

0 No electronic authentication

1 PIN 2 Electronic signature analysis 3 Biometrics 4 Biographic 5 Electronic authentication inoperative 6 Other

Card capture capability 0 None 1 Capture

Operating environment 0 No terminal used 1 On premises of Card acceptor, attended 2 On premises of Card acceptor, unattended 3 Off premises of Card acceptor, attended 4 Off premises of Card acceptor, unattended 5 On premises of cardholder, unattended

Cardholder present 0 Cardholder present 1 Cardholder not present, unspecified 2 Cardholder not present, mail order 3 Cardholder not present, telephone 4 Cardholder not present, standing authorization

Card present 0 Card not present 1 Card present

Card data input mode 0 Unspecified 1 Manual, no terminal 2 Magnetic stripe read 3 Bar code 4 OCR 5 ICC 6 Key entered

Cardholder authentication method

0 Not authenticated

1 PIN 2 Electronic signature analysis 3 Biometrics 4 Biographic 5 Manual signature verification 6 Other manual verification (e.g., driver’s license)

Cardholder authentication entity

0 Not authenticated

1 ICC 2 Card accepting device 3 Authorizing agent 4 By merchant 5 Other

Card data output capability 0 Unknown 1 None

85


Function Value Description 2 Magnetic stripe write 3 ICC

Terminal output capability 0 Unknown 1 None 2 Printing 3 Display 4 Printing and display

PIN capture capability 0 No PIN capture capability 1 Device PIN capture capability unknown 4 4 characters 5 5 characters

86


Appendix C - Common Objects This section describes the structure of the common objects used in this ICD. The “Condition request” column lists the condition code for the data element for add and update operations. The “Condition response” column lists the condition code for the data element for read operations. The “CE” and “OE” conditions indicate that the data element is returned in reads if it was originally provided in an add or update.

C.1 Cardholder Object Data element name Condition

request Condition response

Usage Notes

Address, cardholder mailing

C CE Required if the State Agency is configured for IVR – cardholder zip or Mailed card replacement (see Appendix D - Configurability)

Card number M M Cardholder relationship O OE Date of birth, cardholder C CE Required if the State Agency is configured for IVR –

cardholder zip, IVR – household zip, or Mailed card replacement (see Appendix D - Configurability)

Gender O OE Language code O OE See Appendix B.4 for values Name, cardholder O OE Phone number, cardholder O OE Reason code C M Valid/read to shop card, mandatory if replacing card via

update card/cardholder; see Appendix B.6 for values Status code O M Mandatory in Get Cardholders/Cards. Type code M M Cardholder type (Primary, secondary, proxy), see

Appendix B.8 for values

C.2 Person Object Data element name Condition


Usage Notes

Name, first C CE Mandatory whenever Person Object is required Name, middle initial O OE Name, last C CE Mandatory whenever Person Object is required Name, suffix O OE

C.3 Address Object Data element name Condition


Usage Notes

Address, city C CE Mandatory whenever Address Object is required Address line 1 C CE Mandatory whenever Address Object is required Address line 2 O OE Address, state C CE Mandatory whenever Address Object is required Address, ZIP code C CE Mandatory whenever Address Object is required

The following lists some additional validation rules used for addresses:

87


Rule ID Description C.3.1 If the Address object is optional but is still provided, then eWIC will not validate the

presence or absence of any fields. C.3.2 When the Address, ZIP code is provided, eWIC validates that it is known zip code. If

the Address, city and/or Address, state are also provided, then eWIC validates that the Address, ZIP code is consistent with the provided Address, city and/or Address, state.

C.4 Head of Household Object Data element name Condition


Usage Notes

Address, household mailing

C CE Required if the State Agency is configured for IVR – household zip (see Appendix D - Configurability)

Date of birth, head of household

O OE

Gender O OE Language code O OE See Appendix B.4 for values Name, head of household O OE

88


Appendix D - Configurability eWIC offers some optional features that impact interface requirements. A State agency’s election to exercise certain optional features causes some data elements to be required that may otherwise be optional. The following table lists the optional features in eWIC and the impact to the interface requirements.

Option Impact Enforce unique benefit issuance ID

Some State Agencies require that eWIC enforce uniqueness of the Benefit issuance ID for credit operations using Add or Update Benefit requests. eWIC maintains a parameter that controls whether or not eWIC enforces uniqueness.

IVR – household zip IVR validations requires that the cardholder enters a zip code and cardholder date of birth. Some states track household demographics and some states track cardholder demographics (and some states track both). States that track household demographics may elect to have the IVR use the household zip code for validation. Therefore, for states that elect to use the IVR with household zip, the following data elements are required: Add EBA: in the Head of household object, the Address, household mailing is mandatory. Add Cardholder/Card: in the Cardholder object, the Date of birth, cardholder is mandatory.

IVR – cardholder zip IVR validations requires that the cardholder enters a zip code and cardholder date of birth. Some states track household demographics and some states track cardholder demographics (and some states track both). States that track cardholder demographics may elect to have the IVR use the cardholder zip code for validation. Therefore, for states that elect to use the IVR with cardholder zip, the following data elements are required: Add Cardholder/Card: in the Cardholder object, the Address, cardholder mailing is mandatory. Add Cardholder/Card: in the Cardholder object, the Date of birth, cardholder is mandatory.

Mailed card replacement

In order to mail a replacement, eWIC requires a valid address on file for a cardholder. Therefore, for States that elect to have the option to mail replacement cards, the following data elements are required: Add Cardholder/Card: in the Cardholder object, the Address, cardholder mailing and Date of birth, cardholder are mandatory.

Maximum search range – Get Benefit Maintenance History

The maximum number of days between Date, being request and Date, end request that are allowed in the Get Benefit Maintenance History request. This is used to restrict the span of time in search requests.

Maximum search range – Get Benefit Redemption History

The maximum number of days between Date, being request and Date, end request that are allowed in the Get Benefit Redemption History request. This is used to restrict the span of time in search requests.

Maximum search range – Get Card History

The maximum number of days between Date, being request and Date, end request that are allowed in the Get Card History request. This is used to restrict the span of time in search requests.

89


Appendix E - jQuery PIN Pad Plug-in The eWIC JQuery Plugin for PIN Pad devices provides access to make use of the eWIC Core Interop functionality. As the name would indicate, this is a JavaScript library built on the JQuery framework. It provides all of the necessary functionality to bind core interop to a web application using common JQuery constructs.

The plugin is designed in a way that allows the web application developer to determine how to call the underlying functions. For example, if you wanted to call the “GetDeviceInformation” method on the click of a button, you would simply set the button’s on click handler to make a call to $.fn.GetDeviceInformation. See the example below:

input type="button" value="Get Device Info" onClick="GetDeviceInfo();"/>

function GetDeviceInfo() {

$.fn.getDeviceInformation(

function(data) {

$('#getDeviceInfoResult').html(

'Customer: ' + data.Customer + ',

Model: ' + data.Model + ',

Firmware: ' + data.Firmware

);

},

function(error) {

$('#getDeviceInfoResult').html(

'Error occurred: ' + error

);

}

);

Each of the following methods are available using the eWIC JQuery Plugin.

CancelQueue - Cancels the current device action, for example a card read.

Input Parameters:

HandleSuccess: Represents a function to call upon success.

HandleError: Represents a function to call upon error.Returns:

Void on success via HandleSuccess callback

90


Error detail on error via HandleError callbackSample Code:

function CancelQueue() { $.fn.cancelQueue(

function() { $('#cancelQueueResult').html('Queue cancelled.');

}, function(error){ $('#cancelQueueResult').html('Error occurred: ' + error);

} );

} GetCoreInteropVersion – Get the version number for the installed version of Core Interop.

Input Parameters:



A Version Information Object on success via HandleSuccess callback

Version (string) – Contains the full version number (ex. 1.0.0.1) in the format of {Major.Minor.Build.Revision}

Major (int) – Contains the major increment value of the version number

Minor (int) – Contains the minor increment value of the version number

Build (int) – Contains the build increment value of the version number

Revision (int) – Contains the revision increment value of the version number

Error detail on error via HandleError callbackSample Code:

function GetVersion() { $.fn.getCoreInteropVersion(

function(data) { $('#getInteropVersionResult').html(data.Version);

}, function(error) { $('#getInteropVersionResult').html('Error occurred: ' + error);

} );

}

GetDeviceInformation – Retrieves various bits of information about the connected card / PIN device.

Input Parameters:



91


A device information object on success via HandleSuccess callback

Firmware – The firmware version number for the connected device.

Customer – The Customer ID for the connected device.

Model – The model number of the selected device.

Error detail on error via HandleError callback

Sample Code:

function GetDeviceInfo() { $.fn.getDeviceInformation(

function(data) { $('#getDeviceInfoResult').html('Customer: ' + data.Customer + ', Model: ' + data.Model + ', Firmware: ' + data.Firmware);

}, function(error) { $('#getDeviceInfoResult').html('Error occurred: ' + error);

} );

}

GetCardInformation – Gets information about a swiped card from the device.

Input Parameters:



A card information object on success via HandleSuccess callback

CardNumber – The card number of the swiped card.

ExpiryDate – The expiry date of the swiped card.

Track2 – The complete track 2 data of the swiped card.


Sample Code:

function GetCardInfo() { $.fn.getCardInformation(

function(data) { $('#getCardInfoResult').html('Card Number: ' + data.CardNumber + ', Expiry Date: ' + data.ExpiryDate + ', Track 2 Data: '

+ data.Track2); cardNumber = data.CardNumber;

}, function(error) { $('#getCardInfoResult').html('Error occurred: ' + error);

} );

}

92


GetPinInformation – Gets PIN information from the device.

Input Parameters:

EnterPinMessage: A message to display on the device to prompt for PIN Entry.

CardNumber: The card number associated with the PIN

HandleData: Represents a function to call upon success.


A PIN information object on success via HandleSuccess callback

Ksn – The key serial number of the encryption operation.

PinBlock – The encrypted pin block.


Sample Code:

function GetPinInfo() { $.fn.getPinInformation(

'ENTER PIN', cardNumber, function(data) { $('#getPinInfoResult').html('KSN: ' + data.Ksn + ', PIN Block: ' + data.PinBlock);

}, function(error) { $('#getPinInfoResult').html('Error occurred: ' + error);

} );

}

93


Appendix F - Examples

F.1 Straddle Scenario in WIC Benefit Redemption File In this section, we show an example of a straddle scenario and how the item details will appear in the WIC Benefit Redemption File as specified in Section 4.6.1. Consider the following breakdown for a single redemption involving 3 jars (containers) of peanut butter with a shelf price of $4.99 per jar:

Line item ID

UPC/PLU data

Original category code

Original sub-category code

Original item price

Original purchase quantity

Original amount

Amount, item discount

Amount, NTE adjustment

Amount, recoupment adjustment

Category code

Sub-category code

Item price

Purchase quantity

Amount, paid

Units Benefit issuance ID

1 123456 6 1 $4.99 1.00 $4.99 $0.00 $0.10 $0.10 6 1 $4.79 1.00 $4.79 1.00 111 2 123456 6 1 $4.99 1.00 $4.99 $0.00 $0.10 $0.10 6 1 $4.79 1.00 $4.79 1.00 222 3 123456 6 1 $4.99 0.50 $2.50 $0.00 $0.10 $0.10 6 1 $4.79 0.50 $2.40 0.50 333 4 123456 6 1 $4.99 0.50 $2.49 $0.00 $0.10 $0.10 6 0 $4.79 0.50 $2.39 0.50 111

Note that Amount paid for 0.5 units is split into $2.50 and $2.49 to ensure that the total for 1 unit still adds up to $4.99. The data on this transaction would appear as follows in the file:


<RedemptionActivityObject> <EBTTransactionID>178</EBTTransactionID> <TransactionTypeCode>B</TransactionTypeCode> <TransactionReasonCode>000</TransactionReasonCode> <HostDateTime>2014-02-04T23:11:12</HostDateTime> <LocalDateTime>2014-02-04T07:00:00</LocalDateTime> <SettlementDate>2014-02-05</SettlementDate> <BusinessDate>2014-02-04</BusinessDate> <SystemTraceAuditNumber>0</SystemTraceAuditNumber> <AcquiringInstitutionID>99999999999</AcquiringInstitutionID> <ForwardingInstitutionID>99999999999</ForwardingInstitutionID> <CardNumber>6063709000000007</CardNumber> <HouseholdID>500001</HouseholdID> <VendorID>500101</VendorID> <PeerGroupID>1</PeerGroupID> <CardAcceptorIDCode>23523563532</CardAcceptorIDCode> <CardAcceptorTerminalIDCode>32432342</CardAcceptorTerminalIDCode> <RequestedAmount>14.97</RequestedAmount> <TotalAdjustments>0.00</TotalAdjustments> <DiscountAmount>0.00</DiscountAmount> <SettledAmount>14.97</SettledAmount> <InitiatingUserID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <WorkstationID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

<RedemptionDetailObject> <ClinicID>1234</ClinicID>

<LocalAgencyID>567</LocalAgencyID> <UniqueBenefitID>111</UniqueBenefitID> <BenefitBeginDate>2014-02-03</BenefitBeginDate> <BenefitEndDate>2014-03-03</BenefitEndDate> <CategoryCode>06</CategoryCode>


<CategoryCodeOriginal>06</CategoryCodeOriginal> <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <SubcategoryCode>001</SubcategoryCode> <SubcategoryCodeOriginal>001</SubcategoryCodeOriginal> <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcPluCode>123456</UpcPluCode> <UpcPluDataLength xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcDescription>Peanut Butter 18 Oz.</UpcDescription> <RequestedAmount>4.99</RequestedAmount> <RequestedAmountOriginal xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <DiscountAmount>0.00</DiscountAmount> <PaidAmount>4.99</PaidAmount> <RequestedQuantity>1.00</RequestedQuantity> <ApprovedQuantity>1.00</ApprovedQuantity> <BenefitsDeducted>1.00</BenefitsDeducted> <PackageSize>1.00</PackageSize> <BenefitUnitDescription>cont</BenefitUnitDescription> <LineItemID>1</LineItemID>

</RedemptionDetailObject> <RedemptionDetailObject>

<ClinicID>1234</ClinicID> <LocalAgencyID>567</LocalAgencyID> <UniqueBenefitID>222</UniqueBenefitID> <BenefitBeginDate>2014-02-03</BenefitBeginDate> <BenefitEndDate>2014-03-03</BenefitEndDate> <CategoryCode>06</CategoryCode> <CategoryCodeOriginal>06</CategoryCodeOriginal> <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <SubcategoryCode>001</SubcategoryCode> <SubcategoryCodeOriginal>001</SubcategoryCodeOriginal>

96


<SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcPluCode>123456</UpcPluCode> <UpcPluDataLength xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcDescription>Peanut Butter 18 Oz.</UpcDescription> <RequestedAmount>4.99</RequestedAmount> <RequestedAmountOriginal xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <DiscountAmount>0.00</DiscountAmount> <PaidAmount>4.99</PaidAmount> <RequestedQuantity>1.00</RequestedQuantity> <ApprovedQuantity>1.00</ApprovedQuantity> <BenefitsDeducted>1.00</BenefitsDeducted> <PackageSize>1.00</PackageSize> <BenefitUnitDescription>cont</BenefitUnitDescription> <LineItemID>2</LineItemID>


<ClinicID>1234</ClinicID> <LocalAgencyID>567</LocalAgencyID> <UniqueBenefitID>333</UniqueBenefitID> <BenefitBeginDate>2014-02-03</BenefitBeginDate>

<BenefitEndDate>2014-03-03</BenefitEndDate> <CategoryCode>06</CategoryCode> <CategoryCodeOriginal>06</CategoryCodeOriginal> <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <SubcategoryCode>001</SubcategoryCode> <SubcategoryCodeOriginal>001</SubcategoryCodeOriginal> <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcPluCode>123456</UpcPluCode> <UpcPluDataLength xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcDescription>Peanut Butter 18 Oz.</UpcDescription>

97


<RequestedAmount>4.99</RequestedAmount> <RequestedAmountOriginal xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <DiscountAmount>0.00</DiscountAmount> <PaidAmount>2.50</PaidAmount> <RequestedQuantity>0.50</RequestedQuantity> <ApprovedQuantity>0.50</ApprovedQuantity> <BenefitsDeducted>0.50</BenefitsDeducted> <PackageSize>1.00</PackageSize> <BenefitUnitDescription>cont</BenefitUnitDescription> <LineItemID>1</LineItemID>

</RedemptionDetailObject> <RedemptionDetailObject> <ClinicID>1234</ClinicID> <LocalAgencyID>567</LocalAgencyID> <UniqueBenefitID>111</UniqueBenefitID> <BenefitBeginDate>2014-02-03</BenefitBeginDate> <BenefitEndDate>2014-03-03</BenefitEndDate> <CategoryCode>06</CategoryCode> <CategoryCodeOriginal>06</CategoryCodeOriginal> <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <SubcategoryCode>000</SubcategoryCode> <SubcategoryCodeOriginal>001</SubcategoryCodeOriginal>

<SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcPluCode>123456</UpcPluCode> <UpcPluDataLength xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <UpcDescription>Peanut Butter 18 Oz.</UpcDescription> <RequestedAmount>4.99</RequestedAmount> <RequestedAmountOriginal xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <DiscountAmount>0.00</DiscountAmount> <PaidAmount>2.49</PaidAmount>

98


<RequestedQuantity>0.50</RequestedQuantity> <ApprovedQuantity>0.50</ApprovedQuantity> <BenefitsDeducted>0.50</BenefitsDeducted> <PackageSize>1.00</PackageSize> <BenefitUnitDescription>cont</BenefitUnitDescription> <LineItemID>1</LineItemID>

</RedemptionDetailObject>

F.2 Sample Files

F.2.1 Confirmation File <?xml version="1.0" encoding="utf-8"?> <BatchConfirmationFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance> <BatchConfirmationFileHeader>

<MessageType>9100</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2015-03-09T06:10:51.2637603Z</MessageDatetime>  <FileOriginator>3</FileOriginator>  <ReceivingInstitution>13</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>3</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RejectedCount>2</RejectedCount>  <RecordCount>57</RecordCount> 

</BatchConfirmationFileHeader> <BatchConfirmationRejectedDetail>

<FunctionReturnCode>4073</FunctionReturnCode>  <RecordSequenceNumber>43</RecordSequenceNumber>  <OriginalLineNumber>2489</OriginalLineNumber> 

99


</BatchConfirmationRejectedDetail> <BatchConfirmationRejectedDetail>

<FunctionReturnCode>4074</FunctionReturnCode>  <RecordSequenceNumber>43</RecordSequenceNumber>  <OriginalLineNumber>2489</OriginalLineNumber> 

</BatchConfirmationRejectedDetail> </BatchConfirmationFile>

F.2.2 Report Card Updates <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9000</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>3</FileOriginator>  <ReceivingInstitution>13</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>1</RecordCount>  </BatchFileHeader> <CardChangeBatchFile> <DetailRecordHeader>

<RecordSequenceNumber>1</RecordSequenceNumber>  <Username>bill.smith</Username>  <WorkstationID>BILLSPC</WorkstationID> 

<DetailRecordHeader> <ActionCode>002</ActionCode>  <InitiatingUserID>john.doe</InitiatingUserID> 

100


<HouseholdID>123456</HouseholdID>  <EffectiveDate>2014-08-19</EffectiveDate>  <HostDateTime>2014-08-22T19:28:15.550</HostDateTime>  <PINActivityCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <CardNumberReplacement>6103200000000001</CardNumberReplacement>  <CardholderObject>

<CardNumber>6103200000000000</CardNumber>  <CardholderRelationship>Mother</CardholderRelationship>  <CardholderPersonObject>  <FirstName>Jane</FirstName>  <MiddleInitial xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <LastName>Doe</LastName>  <SuffixName xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  </CardholderPersonObject> <CardholderMailingAddressObject>  <StreetAddressLine1>123 Person Street</StreetAddressLine1>  <StreetAddressLine2 xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <City>Lexington</City>  <StateAbbreviation>KY</StateAbbreviation>  <ZipCode> 

<PrimaryZipCode>40511</PrimaryZipCode> <ExtendedZipCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

</ZipCode> </CardholderMailingAddressObject> <BirthDate>2014-08-19</BirthDate>  <Gender>M</Gender>  <LanguageCode>E</LanguageCode>  <PhoneNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <CardholderStatusCode>A004</CardholderStatusCode>  <CardholderReasonCode>C001</CardholderReasonCode> 

101


<CardholderTypeCode>P</CardholderTypeCode>  </CardholderObject> </CardChangeBatchFile> </BatchFile>

F.2.3 Add or Update WIC Vendor

F.2.3.1 Without Optional APL Type <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9100</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>1</RecordCount>  </BatchFileHeader> <VendorObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <VendorID>123456</VendorID>  <VendorName>Good Foods and Stuff</VendorName> 

102


<VendorReasonCode>V006</VendorReasonCode>  <VendorTypeCode>C</VendorTypeCode>  <VendorBeginDate>2009-10-23</VendorBeginDate>  <VendorEndDate xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <EffectiveDate>2014-08-19</EffectiveDate>  <VendorCorporationID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <PeerGroupID>1</PeerGroupID>  <Above50Percent xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <ACHSettlementTime xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <DirectConnect xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <DirectConnectARF xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <TotalFoodSalesAmount xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <FNSNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <LocalAgencyID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <VendorPrimaryPhoneNumber>5551235555</VendorPrimaryPhoneNumber>  <VendorSecondaryPhoneNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <VendorContactPersonObject> 

<FirstName>John</FirstName>  <MiddleInitial xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <LastName>Doe</LastName>  <SuffixName xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

</VendorContactPersonObject> <VendorContactEmailAddress xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <VendorMailingAddressObject> 

<StreetAddressLine1>123 Food Street</StreetAddressLine1>  <StreetAddressLine2 xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <City>Lexington</City>  <StateAbbreviation>KY</StateAbbreviation>  <ZipCode> 

103


<PrimaryZipCode>40511</PrimaryZipCode> <ExtendedZipCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

</ZipCode> </VendorMailingAddressObject> <VendorPhysicalAddressObject> 

<StreetAddressLine1>123 Food Street</StreetAddressLine1>  <StreetAddressLine2 xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <City>Lexington</City>  <StateAbbreviation>KY</StateAbbreviation>  <ZipCode>  <PrimaryZipCode>40511</PrimaryZipCode> <ExtendedZipCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> </ZipCode>

</VendorPhysicalAddressObject> <BankName xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <ABARoutingTransitNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <BankAccountNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <FederalTaxID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  </VendorObject> </BatchFile>

F.2.3.2 With Optional APL Type <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9100</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution> 

104


<WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>1</RecordCount>  </BatchFileHeader> <VendorObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <VendorID>123456</VendorID>  <VendorName>Good Foods and Stuff</VendorName>  <VendorReasonCode>V006</VendorReasonCode>  <VendorTypeCode>C</VendorTypeCode>  <VendorBeginDate>2009-10-23</VendorBeginDate>  <VendorEndDate xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <EffectiveDate>2014-08-19</EffectiveDate>  <VendorCorporationID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <PeerGroupID>1</PeerGroupID>  <Above50Percent xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <ACHSettlementTime xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <DirectConnect xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <DirectConnectARF xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <TotalFoodSalesAmount xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <FNSNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <LocalAgencyID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <VendorPrimaryPhoneNumber>5551235555</VendorPrimaryPhoneNumber> 

105


<VendorSecondaryPhoneNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <VendorContactPersonObject> 

<FirstName>John</FirstName>  <MiddleInitial xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <LastName>Doe</LastName>  <SuffixName xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

</VendorContactPersonObject> <VendorContactEmailAddress xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <VendorMailingAddressObject> 

<StreetAddressLine1>123 Food Street</StreetAddressLine1>  <StreetAddressLine2 xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <City>Lexington</City>  <StateAbbreviation>KY</StateAbbreviation>  <ZipCode>  <PrimaryZipCode>40511</PrimaryZipCode> <ExtendedZipCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

</ZipCode> </VendorMailingAddressObject> <VendorPhysicalAddressObject> 

<StreetAddressLine1>123 Food Street</StreetAddressLine1>  <StreetAddressLine2 xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <City>Lexington</City>  <StateAbbreviation>KY</StateAbbreviation>  <ZipCode>  <PrimaryZipCode>40511</PrimaryZipCode> <ExtendedZipCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

</ZipCode> </VendorPhysicalAddressObject> <BankName xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

106


<ABARoutingTransitNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <BankAccountNumber xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <FederalTaxID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <APLType>1</APLType> </VendorObject> </BatchFile>

F.2.4 Add or Update Category/Sub-category Information <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9400</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader> <CategorySubcategoryObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <CategoryCode>02</CategoryCode>  <CategoryLongDescription>Cheese</CategoryLongDescription> 

107


<CategoryShortDescription>Cheese</CategoryShortDescription>  <CategoryBeginDate>2014-01-01</CategoryBeginDate>  <CategoryEndDate>2014-12-31</CategoryEndDate>  <SubcategoryCode>007</SubcategoryCode>  <SubcategoryLongDescription>Round Cheese</SubcategoryLongDescription>  <SubcategoryShortDescription>Round Cheese</SubcategoryShortDescription>  <SubcategoryBeginDate>2014-01-01</SubcategoryBeginDate>  <SubcategoryEndDate>2014-12-31</SubcategoryEndDate>  <BenefitUnitDescription>Pound</BenefitUnitDescription>  </CategorySubcategoryObject> <CategorySubcategoryObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <CategoryCode>03</CategoryCode>  <CategoryLongDescription>Eggs</CategoryLongDescription>  <CategoryShortDescription>Eggs</CategoryShortDescription>  <CategoryBeginDate>2014-01-01</CategoryBeginDate>  <CategoryEndDate>2014-12-31</CategoryEndDate>  <SubcategoryCode>777</SubcategoryCode>  <SubcategoryLongDescription>Shelled Eggs</SubcategoryLongDescription>  <SubcategoryShortDescription>Shelled Eggs</SubcategoryShortDescription>  <SubcategoryBeginDate>2014-01-01</SubcategoryBeginDate>  <SubcategoryEndDate>2014-12-31</SubcategoryEndDate>  <BenefitUnitDescription>Doz</BenefitUnitDescription>  </CategorySubcategoryObject> </BatchFile>

108


F.2.5 Add or Update UPC/PLU Information

F.2.5.1 Without Optional APL Type <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9500</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader> <UpcPluNteObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <UpcPluCode>10000000000040112</UpcPluCode>  <UpcPluDataLength>5</UpcPluDataLength>  <UpcPluDescription>Bananas</UpcPluDescription>  <UpcPluBeginDate>2014-01-01</UpcPluBeginDate>  <UpcPluEndDate>2014-12-31</UpcPluEndDate>  <CategoryCode>19</CategoryCode>  <SubcategoryCode>000</SubcategoryCode> 

109


<BenefitQuantity>1</BenefitQuantity>  <BenefitUnitDescription>$$$</BenefitUnitDescription>  <PurchaseIndicator>0</PurchaseIndicator>  <PackageSize>1</PackageSize>  <ManualVoucherIndicator>0</ManualVouncherIndicator>  <RebateFlag>0</RebateFlag>  <PriceType>03</PriceType>  <NumberOfWicVendorPeerGroups>1</NumberOfWicVendorPeerGroups>  <PeerGroupNTEPriceObject>

<PeerGroupID>1</PeerGroupID>  <NTEPrice>2.99</NTEPrice> 

</PeerGroupNTEPriceObject> </UpcPluNteObject> <UpcPluNteObject> <DetailRecordHeader>

<RecordSequenceNumber>2</RecordSequenceNumber>  <Username>john.doe</Username>  <WorkstationID>JOHNSPC</WorkstationID> 

</DetailRecordHeader> <ActionCode>002</ActionCode>  <UpcPluCode>00000011110417008</UpcPluCode>  <UpcPluDataLength>12</UpcPluDataLength>  <UpcPluDescription>Kroger 2% Milk Gallon</UpcPluDescription>  <UpcPluBeginDate>2014-01-01</UpcPluBeginDate>  <UpcPluEndDate>2014-12-31</UpcPluEndDate>  <CategoryCode>52</CategoryCode>  <SubcategoryCode>004</SubcategoryCode>  <BenefitQuantity>1</BenefitQuantity>  <BenefitUnitDescription>GAL</BenefitUnitDescription>  <PurchaseIndicator>0</PurchaseIndicator> 

110


<PackageSize>1</PackageSize>  <ManualVoucherIndicator>0</ManualVouncherIndicator>  <RebateFlag>0</RebateFlag>  <PriceType>00</PriceType>  <NumberOfWicVendorPeerGroups>2</NumberOfWicVendorPeerGroups>  <PeerGroupNTEPriceObject>


</PeerGroupNTEPriceObject> <PeerGroupNTEPriceObject>


</PeerGroupNTEPriceObject> </UpcPluNteObject> </BatchFile>

F.2.5.2 With Optional APL Type <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9500</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader>

111


<UpcPluNteObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <UpcPluCode>10000000000040112</UpcPluCode>  <UpcPluDataLength>5</UpcPluDataLength>  <UpcPluDescription>Bananas</UpcPluDescription>  <UpcPluBeginDate>2014-01-01</UpcPluBeginDate>  <UpcPluEndDate>2014-12-31</UpcPluEndDate>  <CategoryCode>19</CategoryCode>  <SubcategoryCode>000</SubcategoryCode>  <BenefitQuantity>1</BenefitQuantity>  <BenefitUnitDescription>$$$</BenefitUnitDescription>  <PurchaseIndicator>0</PurchaseIndicator>  <PackageSize>1</PackageSize>  <ManualVoucherIndicator>0</ManualVouncherIndicator>  <RebateFlag>0</RebateFlag>  <PriceType>03</PriceType>  <NumberOfWicVendorPeerGroups>1</NumberOfWicVendorPeerGroups>  <PeerGroupNTEPriceObject>

<PeerGroupID>1</PeerGroupID>  <NTEPrice>2.99</NTEPrice>  </PeerGroupNTEPriceObject> <NumberOfAPLTypes>2</NumberOfAPLTypes> <APLType>1</APLType> <APLType>2</APLType> </UpcPluNteObject>

112


<UpcPluNteObject> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>002</ActionCode>  <UpcPluCode>00000011110417008</UpcPluCode>  <UpcPluDataLength>12</UpcPluDataLength>  <UpcPluDescription>Kroger 2% Milk Gallon</UpcPluDescription>  <UpcPluBeginDate>2014-01-01</UpcPluBeginDate>  <UpcPluEndDate>2014-12-31</UpcPluEndDate>  <CategoryCode>52</CategoryCode>  <SubcategoryCode>004</SubcategoryCode>  <BenefitQuantity>1</BenefitQuantity>  <BenefitUnitDescription>GAL</BenefitUnitDescription>  <PurchaseIndicator>0</PurchaseIndicator>  <PackageSize>1</PackageSize>  <ManualVoucherIndicator>0</ManualVouncherIndicator>  <RebateFlag>0</RebateFlag>  <PriceType>00</PriceType>  <NumberOfWicVendorPeerGroups>2</NumberOfWicVendorPeerGroups>  <PeerGroupNTEPriceObject>

<PeerGroupID>1</PeerGroupID>  <NTEPrice>99.99</NTEPrice>  </PeerGroupNTEPriceObject> <PeerGroupNTEPriceObject>


</PeerGroupNTEPriceObject>

113


<NumberOfAPLTypes>2</NumberOfAPLTypes> <APLType>1</APLType> <APLType>4</APLType> </UpcPluNteObject> </BatchFile>

F.2.6 Report WIC Benefit Redemptions <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9700</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>3</FileOriginator>  <ReceivingInstitution>13</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader> <RedemptionActivityObject> <DetailRecordHeader>

<RecordSequenceNumber>1</RecordSequenceNumber>  <Username xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <WorkstationID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

</DetailRecordHeader> <EBTTransactionID>123456</EBTTransactionID>  <OriginalEBTTransactionID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <TransactionTypeCode>B</TransactionTypeCode> 

114


<TransactionReasonCode>000</TransactionReasonCode>  <HostDateTime>2014-08-23T04:46:21</HostDateTime>  <LocalDateTime>2014-08-23T00:46:02</LocalDateTime>  <SettlementDate>2014-08-23</SettlementDate>  <BusinessDate>2014-08-23</BusinessDate>  <SystemTraceAuditNumber>12345</SystemTraceAuditNumber>  <AcquiringInstitutionID>2</AcquiringInstitutionID>  <ForwardingInstitutionID>2</ForwardingInstitutionID>  <CardNumber>6103200000000000</CardNumber>  <HouseholdID>123456</HouseholdID>  <VendorID>123456</VendorID>  <PeerGroupID>1</PeerGroupID>  <CardAcceptorIDCode>340923489241</CardAcceptorIDCode>  <CardAcceptorTerminalIDCode>35923592</CardAcceptorTerminalIDCode>  <POSDataCodeCardDataInputCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderAuthenticationCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardCaptureCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeOperatingEnvironment xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderPresent xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardPresent xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardDataInputMode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderAuthenticationMethod xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

115


<POSDataCodeCardholderAuthenticationEntity xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardDataOutputCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeTerminalOutputCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodePINCaptureCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <RequestedAmount>24.85</RequestedAmount>  <TotalAdjustments>0.00</TotalAdjustments>  <DiscountAmount>2.30</DiscountAmount>  <SettledAmount>22.55</SettledAmount>  <InitiatingUserID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <MessageReasonCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <!—Message reason code --> <RedemptionDetailObject>

<ClinicID>1</ClinicID>  <LocalAgencyID>1</LocalAgencyID>  <UniqueBenefitID>123456</UniqueBenefitID>  <BenefitBeginDate>2014-08-16</BenefitBeginDate>  <BenefitEndDate>2014-09-15</BenefitEndDate>  <CategoryCode>52</CategoryCode>  <CategoryCodeOriginal>52</CategoryCodeOriginal>  <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <SubcategoryCode>000</SubcategoryCode>  <SubcategoryCodeOriginal>004</SubcategoryCodeOriginal>  <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <UpcPluCode>00000011110417008</UpcPluCode>  <UpcPluDataLength>12</UpcPluDataLength>  <UpcPluDescription>Kroger 2% Milk Gallon</UpcPluDescription> 

116


<RequestedAmount>2.99</RequestedAmount>  <OriginalAmount>2.99</OriginalAmount> <NTEAmount>0.00</NTEAmount> <RecoupmentAmount>0.00</RecoupmentAmount>  <DiscountAmount>0.00</DiscountAmount>  <ApprovedItemAmount>2.99</ApprovedItemAmount>  <PaidAmount>2.99</PaidAmount>  <RequestedQuantity>1.00</RequestedQuantity>  <ApprovedQuantity>1.00</ApprovedQuantity>  <BenefitsDeducted>1.00</BenefitsDeducted>  <PackageSize>1.00</PackageSize>  <BenefitUnitDescription>GAL</BenefitUnitDescription>  <ItemActionCode>00</ItemActionCode> <!—Item action code --> <LineItemID>1</LineItemID> 



description --> <UpcPluCode>10000000000040112</UpcPluCode>  <UpcPluDataLength>5</UpcPluDataLength> 

117


<UpcPluDescription>Bananas</UpcPluDescription>  <RequestedAmount>1.00</RequestedAmount>  <OriginalAmount>1.76</OriginalAmount> <NTEAmount>0.00</NTEAmount> <RecoupmentAmount>0.00</RecoupmentAmount>  <DiscountAmount>0.00</DiscountAmount>  <ApprovedItemAmount>1.00</ApprovedItemAmount>  <PaidAmount>1.76</PaidAmount>  <RequestedQuantity>1.76</RequestedQuantity>  <ApprovedQuantity>1.76</ApprovedQuantity>  <BenefitsDeducted>1.76</BenefitsDeducted>  <PackageSize>1.00</PackageSize>  <BenefitUnitDescription>$$$</BenefitUnitDescription>  <ItemActionCode>00</ItemActionCode> <!—Item action code --> <LineItemID>1</LineItemID> 

</RedemptionDetailObject> </RedemptionActivityObject> <RedemptionActivityObject> <DetailRecordHeader>


</DetailRecordHeader> <EBTTransactionID>123457</EBTTransactionID>  <OriginalEBTTransactionID>123456</OriginalEBTTransactionID>  <TransactionTypeCode>V</TransactionTypeCode>  <TransactionReasonCode>000</TransactionReasonCode>  <HostDateTime>2014-08-24T04:46:21</HostDateTime>  <LocalDateTime>2014-08-24T00:46:02</LocalDateTime>  <SettlementDate>2014-08-24</SettlementDate> 

118


<BusinessDate>2014-08-24</BusinessDate>  <SystemTraceAuditNumber>12346</SystemTraceAuditNumber>  <AcquiringInstitutionID>2</AcquiringInstitutionID>  <ForwardingInstitutionID>2</ForwardingInstitutionID>  <CardNumber>6103200000000000</CardNumber>  <HouseholdID>123456</HouseholdID>  <VendorID>123456</VendorID>  <PeerGroupID>1</PeerGroupID>  <CardAcceptorIDCode>340923489241</CardAcceptorIDCode>  <CardAcceptorTerminalIDCode>35923592</CardAcceptorTerminalIDCode>  <POSDataCodeCardDataInputCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderAuthenticationCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardCaptureCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeOperatingEnvironment xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderPresent xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardPresent xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardDataInputMode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderAuthenticationMethod xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardholderAuthenticationEntity xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodeCardDataOutputCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

119


<POSDataCodeTerminalOutputCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <POSDataCodePINCaptureCapability xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <RequestedAmount>24.85</RequestedAmount>  <TotalAdjustments>0.00</TotalAdjustments>  <DiscountAmount>2.30</DiscountAmount>  <SettledAmount>22.55</SettledAmount>  <InitiatingUserID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <MessageReasonCode xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> <!—Message reason code --> <RedemptionDetailObject>


description --> <UpcPluCode>00000011110417008</UpcPluCode>  <UpcPluDataLength>12</UpcPluDataLength>  <UpcPluDescription>Kroger 2% Milk Gallon</UpcPluDescription>  <RequestedAmount>2.99</RequestedAmount>  <OriginalAmount>2.99</OriginalAmount> <NTEAmount>0.00</NTEAmount> <RecoupmentAmount>0.00</RecoupmentAmount> 

120


<DiscountAmount>0.00</DiscountAmount>  <ApprovedItemAmount>2.99</ApprovedItemAmount>  <PaidAmount>2.99</PaidAmount>  <RequestedQuantity>1.00</RequestedQuantity>  <ApprovedQuantity>1.00</ApprovedQuantity>  <BenefitsDeducted>1.00</BenefitsDeducted>  <PackageSize>1.00</PackageSize>  <BenefitUnitDescription>GAL</BenefitUnitDescription>  <ItemActionCode>00</ItemActionCode> <!—Item action code --> <LineItemID>1</LineItemID> 



description --> <UpcPluCode>10000000000040112</UpcPluCode>  <UpcPluDataLength>5</UpcPluDataLength>  <UpcPluDescription>Bananas</UpcPluDescription>  <RequestedAmount>1.00</RequestedAmount>  <OriginalAmount>1.76</OriginalAmount> <NTEAmount>0.00</NTEAmount>

121


<RecoupmentAmount>0.00</RecoupmentAmount>  <DiscountAmount>0.00</DiscountAmount>  <ApprovedItemAmount>1.00</ApprovedItemAmount>  <PaidAmount>1.76</PaidAmount>  <RequestedQuantity>1.76</RequestedQuantity>  <ApprovedQuantity>1.76</ApprovedQuantity>  <BenefitsDeducted>1.76</BenefitsDeducted>  <PackageSize>1.00</PackageSize>  <BenefitUnitDescription>$$$</BenefitUnitDescription>  <ItemActionCode>00</ItemActionCode> <!—Item action code --> <LineItemID>1</LineItemID> 

</RedemptionDetailObject> </RedemptionActivityObject> </BatchFile>

F.2.7 Report WIC Benefit Changes <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader>

<MessageType>9600</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>3</FileOriginator>  <ReceivingInstitution>13</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID> 

<FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>1</RecordCount>  </BatchFileHeader> <BenefitActivityObject>

122


<DetailRecordHeader> <RecordSequenceNumber>1</RecordSequenceNumber>  <Username>bill.smith</Username>  <WorkstationID>BILLSPC</WorkstationID> 

</DetailRecordHeader> <ActionCode>001</ActionCode>  <BenefitReasonCode>B001</BenefitReasonCode>  <TransactionTypeCode>I</TransactionTypeCode> 

<CardNumber>6103200000000000</CardNumber>  <HouseholdID>123456</HouseholdID>  <ClinicID>1</ClinicID>  <MessageDateTime>2012-09-04T11:34:02.1304353-04:00</MessageDatetime>  <InitiatingUserID>1</InitiatingUserID>  <LocalAgencyID>1</LocalAgencyID>  <UniqueTransactionIdentifier>123456789</UniqueTransactionIdentifier>  <UniqueIssuanceObject>

<UniqueBenefitID>1234</UniqueBenefitID>  <BenefitBeginDate>2014-08-21</BenefitBeginDate>  <BenefitEndDate>2014-09-20</BenefitEndDate>  <UniqueIssuanceObjectDetailObject> <CategoryCode>02</CategoryCode>  <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <SubcategoryCode>001</SubcategoryCode>  <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <BenefitQuantity>1.00</BenefitQuantity>  </UniqueIssuanceObjectDetailObject> <UniqueIssuanceObjectDetailObject> <CategoryCode>03</CategoryCode> 

<CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

123


<SubcategoryCode>001</SubcategoryCode>  <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> 

<BenefitQuantity>1.00</BenefitQuantity>  </UniqueIssuanceObjectDetailObject>

</UniqueIssuanceObject> </BenefitActivityObject> </BatchFile>

F.2.8 Report WIC Benefits Purged <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9750</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>3</FileOriginator>  <ReceivingInstitution>13</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>1</RecordCount>  </BatchFileHeader> <BenefitPurgeObject> <DetailRecordHeader>


</DetailRecordHeader> <CardNumber>6103200000000000</CardNumber> 

124


<HouseholdID>1234567</HouseholdID>  <UniqueBenefitID>3041</UniqueBenefitID>  <BenefitBeginDate>2014-08-21</BenefitBeginDate> <BenefitEndDate>2014-09-20</BenefitEndDate> <EffectiveDate>2014-09-20</EffectiveDate>  <UniquePurgeObject>

<CategoryCode>02</CategoryCode>  <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <SubcategoryCode>001</SubcategoryCode>  <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <BenefitQuantity>1.00</BenefitQuantity>  </UniquePurgeObject> <UniquePurgeObject>

<CategoryCode>03</CategoryCode>  <CategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <SubcategoryCode>001</SubcategoryCode>  <SubcategoryLongDescription xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <BenefitQuantity>2.00</BenefitQuantity> 

</UniquePurgeObject> </BenefitPurgeObject> </BatchFile>

F.2.9 Request ACH Payment <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9850</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion> 

125


<MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader> <RequestACHPayment> <DetailRecordHeader>


</DetailRecordHeader> <ActionCode>001</ActionCode>  <ACHReasonCode>P002</ACHReasonCode>  <VendorID>9999</VendorID>  <VendorCorporationID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />  <HierarchyCode>1</HierarchyCode>  <EffectiveDate>2014-08-19</EffectiveDate>  <PaymentAmount>4.10</PaymentAmount>  <SystemTraceAuditNumber>123</SystemTraceAuditNumber>  <BankName>Banks-r-Us</BankName>  <ABARoutingTransitNumber>000000000</ABARoutingTransitNumber>  <BankAccountNumber>000000000</BankAccountNumber>  <CardAcceptorIDCode>1</CardAcceptorIDCode>  <ReceivingInstitution>1</ReceivingInstitution>  </RequestACHPayment> <RequestACHPayment> <DetailRecordHeader>

126



</DetailRecordHeader> <ActionCode>001</ActionCode>  <ACHReasonCode>P001</ACHReasonCode>  <VendorID>9999</VendorID>  <VendorCorporationID>1</VendorCorporationID>  <HierarchyCode>2</HierarchyCode>  <EffectiveDate>2014-08-19</EffectiveDate>  <PaymentAmount>-7.34</PaymentAmount>  <SystemTraceAuditNumber>345</SystemTraceAuditNumber>  <BankName>Banks-r-Us</BankName>  <ABARoutingTransitNumber>000000000</ABARoutingTransitNumber>  <BankAccountNumber>000000000</BankAccountNumber>  <CardAcceptorIDCode>1</CardAcceptorIDCode>  <ReceivingInstitution>1</ReceivingInstitution>  </RequestACHPayment> </BatchFile>

F.2.10 Report Recoupment Requests <?xml version="1.0" encoding="utf-8"?> <BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9900</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>13</FileOriginator>  <ReceivingInstitution>3</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID> 

127


<FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader> <RecoupmentRequestObject> <DetailRecordHeader>


</DetailRecordHeader> <VendorID>123456</VendorID>  <ProcessingMonth>2014-05-01</ProcessingMonth>  <RecoupmentTypeCode>N</RecoupmentTypeCode>  <RecoupmentAmount>73.97</RecoupmentAmount>  </RecoupmentRequestObject> <RecoupmentRequestObject> <DetailRecordHeader>


</DetailRecordHeader> <VendorID>987654</VendorID>  <ProcessingMonth>2014-05-01</ProcessingMonth>  <RecoupmentTypeCode>D</RecoupmentTypeCode>  <RecoupmentAmount>0.13</RecoupmentAmount>  </RecoupmentRequestObject> </BatchFile>

F.2.11 Report Recoupment Status <?xml version="1.0" encoding="utf-8"?>

128


<BatchFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <BatchFileHeader> <MessageType>9901</MessageType>  <MessageVersion>ICD.2014.2.5</MessageVersion>  <MessageDatetime>2012-09-05T10:47:02.8207553-04:00</MessageDatetime>  <FileOriginator>3</FileOriginator>  <ReceivingInstitution>13</ReceivingInstitution>  <WICStateAgencyID>59</WICStateAgencyID>  <FileSequenceNumber>1</FileSequenceNumber>  <FileTypeCode>U</FileTypeCode>  <RecordCount>2</RecordCount>  </BatchFileHeader> <RecoupmentStatusObject> <DetailRecordHeader>


</DetailRecordHeader> <VendorID>123456</VendorID>  <ActivityDate>2014-05-02</ActivityDate>  <RecoupmentReasonCode>V006</RecoupmentReasonCode>  <RecoupmentAmountBeginning>0.00</RecoupmentAmountBeginning>  <RecoupmentAmountEnding>68.97</RecoupmentAmountEnding>  <RecoupmentAmountNew>73.97</RecoupmentAmountNew>  <RecoupmentAmountCredit>0.00</RecoupmentAmountCredit>  <RecoupmentAmountDebit>0.00</RecoupmentAmountDebit>  <RecoupmentAmountRecovered>10.00</RecoupmentAmountRecovered>  <RecoupmentAmountReversed>5.00</RecoupmentAmountReversed>  <RecoupmentAmountVariance>0.00</RecoupmentAmountVariance>  </RecoupmentStatusObject>

129


<RecoupmentStatusObject> <DetailRecordHeader>


</DetailRecordHeader> <VendorID>987654</VendorID>  <ActivityDate>2014-05-02</ActivityDate>  <RecoupmentReasonCode>V006</RecoupmentReasonCode>  <RecoupmentAmountBeginning>0.13</RecoupmentAmountBeginning>  <RecoupmentAmountEnding>0.00</RecoupmentAmountEnding>  <RecoupmentAmountNew>0.00</RecoupmentAmountNew>  <RecoupmentAmountCredit>0.00</RecoupmentAmountCredit>  <RecoupmentAmountDebit>0.13</RecoupmentAmountDebit>  <RecoupmentAmountRecovered>0.00</RecoupmentAmountRecovered>  <RecoupmentAmountReversed>0.00</RecoupmentAmountReversed>  <RecoupmentAmountVariance>0.00</RecoupmentAmountVariance>  </RecoupmentStatusObject> </BatchFile>

130


Appendix G - Date Field Considerations Many functions in this ICD include fields where a date value is expected. For batch files, a date is sent in the XML using CCYY-MM-DD as the format. For batch files, no time is specified. For the online methods, a time may be sent. This is due to a limitation in the .NET library where there is no “Date” data type available and the Processor must use “DateTime” as the object data type. The DateTime object accepts a time value. Because of how the .NET works with respect to web services, it is possible that an integrator can specify that the date/time is a local date/time. This means that an offset will be included in the underlying XML message. When the .NET library receives a local date and time from an integrator, it will translate the date and time to the date and time that is local to the eWIC server. In certain cases (such as if the integrator is in the Atlantic timezone), this could cause the date to be changed to a day earlier than intended. eWIC cannot easily infer the intended date based on the data available. Therefore, eWIC will now require that an integrator send an unspecified date/time value (i.e. a date/time that includes no offset information) for date fields in online methods.

131

Date post:	29-Mar-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

WIC Direct to MIS Interface Control Document · Cleaned up rules for managing the Status code field...

Documents