AP Technical Reference Manual for Processing Customers · September 2016 V1.5 Appendix A Added the...

AP Technical Reference Manual for Processing Customers

V1.5February 2017

TAPMP0217

Table of Contents

Chapter 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Cardholder Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Revision Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

What is AP Maintenance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

AP Maintenance Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

AP Batch Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15AP Batch Maintenance Message Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Balance Refresh Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Balance Refresh Message Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Online Host Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Online Host Maintenance Message Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

AP Online Screen Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20AP Online Screen Maintenance Message Flow . . . . . . . . . . . . . . . . . . . . . . . . . 21

AP Match and Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Match and Hold Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

AP Authorization Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23AP Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

AP Cooperative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

AP Configuration Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23AP Positive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

AP Positive with Balances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

AP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Copyright© 2017 FIS 15-February-17 Client Confidential 2

Account Detail Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Card Activation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Card Issuance and Management System (CIMS) Services . . . . . . . . . . . . . . . . 24

Scoring and Case Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Name Search Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 3

Using Batch Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

What is an AP Maintenance File? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Header Record and Trailer Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Header Record (Normal Transmission). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Trailer Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Interaction/Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Detail Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Segment Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Required Segment Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

How do I submit an initial load? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31File Transmission Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

How do I submit ongoing maintenance? . . . . . . . . . . . . . . . . . . . . . . . 32JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Hash Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Dummy Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Which detail records should I submit? . . . . . . . . . . . . . . . . . . . . . . . . . 35Deleting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Adding Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Updating Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Submitting Account Detail Information . . . . . . . . . . . . . . . . . . . . . . . . . 36Deleting Account Detail Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Adding Account Detail Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Updating Account Detail Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Submitting Cardholder Validation Information . . . . . . . . . . . . . . . . . . . 41Deleting Cardholder Validation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


Adding Cardholder Validation Information . . . . . . . . . . . . . . . . . . . . . . 42

Updating Cardholder Validation Information. . . . . . . . . . . . . . . . . . . . . 43

Submitting Card Issuance and Management Information . . . . . . . . . . 45Deleting CIMS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Adding CIMS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Updating CIMS Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Submitting Fraud Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Deleting Fraud Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Adding Fraud Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Updating Fraud Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Submitting Name Search Information . . . . . . . . . . . . . . . . . . . . . . . . . 56Deleting Name Search Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Adding Name Search Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Updating Name Search Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

AP Batch Load Exception Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60What segments do I resubmit if I have an error? . . . . . . . . . . . . . . . . . . . . . . . . 60

Report Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Multiple Product Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Deleting Multiple Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Adding Multiple Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Updating Multiple Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 4

Using Online Host Maintenance . . . . . . . . . . . . . . . . . . . . . . . 68

What is Online Host Maintenance? . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Submitting Online Host Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Maintenance Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Using Spaces and Asterisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

ISO Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Format 8 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73


Cardholder Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Account Detail Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 5

Using Balance Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

What is Balance Refresh? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Balance Refresh Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Balance Refresh and End-Of-Day. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Balance Refresh Record Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Header Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Detail Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Trailer Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Sending Records Using RJE or NJE . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Chapter 6

Using Match and Hold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

What is Match and Hold? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

How does AP match a hold? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Match and Hold Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Match and Hold for Pre-Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Match and Hold for Debit MasterCard® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Match and Hold for Visa Check™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Match and Hold Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104FIS Does Match and Hold For AP Complete . . . . . . . . . . . . . . . . . . . . . . . . . . 104

FIS Does Match and Hold For AP Cooperative. . . . . . . . . . . . . . . . . . . . . . . . . 104

Your Host Performs Match and Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

No Match and Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Does Match and Hold affect the cardholder’s balance? . . . . . . . . . . . 105Duplicating Holds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

AP Hold File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106


Raw Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Match and Hold Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108File Header Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109File Trailer Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Batch Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Batch Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Detail Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Entry Addendum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

AP Hold Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117AP Hold Detail Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

AP Hold Detail Report - With PAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Enhanced AP Hold Detail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123AP Hold Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Connex™ on HP NonStop® AP Parameters . . . . . . . . . . . . . . . . . . . 128Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Processing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Run Statement Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

IBM® Settlement Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Update Institution Entity Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131AP Hold Program Abend and Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Appendix A

AP Batch Record Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Key Field Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

CH01A - Cardholder Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

CH02A - Track 2 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

CH03A - Account Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

CH03B - Account Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

CH04A - Override Limits Information . . . . . . . . . . . . . . . . . . . . . . . . . 154


CH06A - Hold List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

CH08A - Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

CH09A - Override Expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

CH14A - Additional Card Information . . . . . . . . . . . . . . . . . . . . . . . . . 164

CH18A - Card Management Group Information. . . . . . . . . . . . . . . . . 166

CH18B - Card Management Group Information. . . . . . . . . . . . . . . . . 168

CH18C - Card Management Group Information. . . . . . . . . . . . . . . . . 171

CH18D - Card Management Group Information. . . . . . . . . . . . . . . . . 174

CH19A - Card Management Member Information . . . . . . . . . . . . . . . 175

Personix Card Collection Series. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

CH19B - Card Management Member Information . . . . . . . . . . . . . . . 181

CH22A - Card Validation Information . . . . . . . . . . . . . . . . . . . . . . . . . 184

CH22B - Card Validation Information . . . . . . . . . . . . . . . . . . . . . . . . . 187

CH23A - Fraud Control Information . . . . . . . . . . . . . . . . . . . . . . . . . . 191

CH50A - VAU/ABU Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

FR01A - Fraud Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

FR01B - Fraud Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

FR02A - Fraud Activity Information . . . . . . . . . . . . . . . . . . . . . . . . . . 202

FR02B - Fraud Activity Information . . . . . . . . . . . . . . . . . . . . . . . . . . 204

FR03A - Fraud Member Information. . . . . . . . . . . . . . . . . . . . . . . . . . 206

FR03B - Fraud Member Information. . . . . . . . . . . . . . . . . . . . . . . . . . 208

AD01A - Account Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

AD01B - Account Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

AD02A - Account Detail Overdraft Information. . . . . . . . . . . . . . . . . . 219

AD02B - Account Detail Overdraft Information. . . . . . . . . . . . . . . . . . 221

AD03A - Account Detail Hold List Information . . . . . . . . . . . . . . . . . . 223

AD03B - Account Detail Hold List. . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

AD06A - Additional Hold Information . . . . . . . . . . . . . . . . . . . . . . . . . 228

AD06B - Additional Hold Information . . . . . . . . . . . . . . . . . . . . . . . . . 231


AD06C - Additional Hold Information . . . . . . . . . . . . . . . . . . . . . . . . . 232

AD06D - Additional Hold Information . . . . . . . . . . . . . . . . . . . . . . . . . 234

AD08 - Host Balance Update Segment . . . . . . . . . . . . . . . . . . . . . . . 235

CH1AA - Consolidated AVS Group . . . . . . . . . . . . . . . . . . . . . . . . . . 237

CH1AB - Consolidated AVS Group . . . . . . . . . . . . . . . . . . . . . . . . . . 239

CH1AC - Consolidated AVS Group . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Appendix B

Error and Informational Messages . . . . . . . . . . . . . . . . . . . . 244

AP Message Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

AP Batch Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Balance Update Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Appendix C

APCOMP Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Removing Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Sample Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Appendix D

Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Reject Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Transaction Type Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Appendix E

Cardholder Maintenance Values . . . . . . . . . . . . . . . . . . . . . . 291

Card/Account Status Valid Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 291


Appendix F

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

State Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296


1
Introduction
The AP system authorizes EFT transaction requests by accessing files that are synchronized with the client’s internal application files. This manual describes the methods used to maintain the Authorization Processor (AP) system files using offline batch files, balance update files, hold files, or an online host connection.

Cardholder MaintenanceCardholder Maintenance is a Web-based application that operators can use to enter maintenance in the AP system files. The following documentation provides additional information related to Cardholder Maintenance:

AP Cardholder Maintenance User Manual AP Cardholder Maintenance Installation and Deployment Guide AP Cardholder Maintenance Quick Reference Guide Online help in the Cardholder Maintenance application

AudienceThe audience for this manual includes certification and database analysts, account management staff, customer support representatives, and processing customers of Fidelity Naional Information Services (FIS) who perform an initial install or submit maintenance files to AP.

Host operators responsible for sending and receiving batch maintenance information

EFT network operations staff responsible for running the network

EFT network and institution administrators


Revision Log

DateEffective w/Version Chapter Summary of Changes

February 2017 V1.5 Appendix A

Appendix B

Updated the Description/Usage of REAS-CODE, REV-CODE and CONV-CODE fields on page 195.

Updated the input sample for the CH50A - VAU/ABU Information segment on page 197

Renamed APB-160 VAU/ABU OLD/NEW TRK2 DATE REQUIRED to APB-160 VAU/ABU OLD TRK2 DATE REQUIRED.

Updated the description on APB-160 - VAU/ABU OLD TRK2 DATE REQUIRED

Added the following error messages: APB-161 VAU/ABU OLD PAN REQUIRED APB-162 VAU/ABU INVALID NEW TRK2

DATE APB-163 VAU/ABU OLD & NEW TRK2

SHOULD NOT BE THE SAME APB-164 VAU/ABU OLD & NEW PAN SHOULD

NOT BE THE SAME APB-165 VAU/ABU NEW TRK2 DATE

REQUIRED

January 2017 V1.5 All Updated instances of VRU with EIVR as appropriate.

Appendix A Added the value “V = Secure Code.” on page 189.

December 2016 V1.5 Appendix B Added the following AP Batch messages: APB-147 - PAN TOKENIZATION PADSS ERROR

CODE = XX APB-148 - FILE REGISTER PADSS ERROR CODE

= XXX APB-149 - FILE ENCRYPTION PADSS ERROR

CODE = XXX APB-150 - PAN DETOKENIZATION PADSS ERROR

CODE = XXX APB-151 - BATCH RECORDS OLDER THAN LAST

FILE UPDATE - SKIPPING APB-152 - INVALID MEDIA TYPE APB-153 - INVALID COMPANION MINI TYPE APB-154 - INVALID COMPANION MICRO TYPE APB-155 - INVALID COMPANION MOBILE TYPE


November 2016 V1.5 Appendix B Added the following AP Batch messages: APB-156 - VAU/ABU INDICATOR REQUIRED. APB-157 - VAU/ABU INVALID REASON CODE APB-158 VAU/ABU INVALID REVERSAL CODE APB-159 - VAU/ABU INVALID CONVERSION CODE APB-160 - VAU/ABU OLD TRK2 DATE REQUIRED.

September 2016 V1.5 Appendix A Added the following Cardholder Segment: “CH50A - VAU/ABU Information” on page 193.

May 2015 V1.5 Appendix A Updated the field length of the CARD-ACCESS field on page 138.

Appendix A Updated the description/usage of the CARD-TYPE field and the on page 165.

Appendix A Added the following fields: “MEDIA-TYPE” on page 165. “CARD-COMPANION-MINI” on page 166. “CARD-COMPANION-MICRO” on page 166. “CARD-COMPANION-MOBILE” on page 166.

Appendix A Updated the Note information on page 166.

Appendix A Updated the input sample for the CH14A - Additional Card Information segment on page 166.

July 2014 V1.5 Appendix A Added a Note and values supporting EMV categories on page 166.

June 2014 V1.5 2 Updated Discover Debit service in “Card Activation Services” on page 24.

December 2013 V1.5 All Miscellaneous text, screen, and report updates to make data representation more generic.

June 2013 V1.5 Appendix A Updated “CARD-TYPE” on page 165.

October 2012 V1.5 Appendix A CH19A - Card Management Member Information - Updated the Description/Usage for: “CARD-ORDER-STATUS-FLAG” on page 178.

CH19B - Card Management Member Information - Updated the Description/Usage for: “CARD-ISSUE-REASON-FLAG” on page 182.

September 2012 V1.5 3 Updated the Note information on page 25.

September, 2009 V1.5 Appendix B Updated the description for the following AP Batch Message: “APB-067 - INVALID CARD ISSUE REASON” on

page 252.



July, 2009 V1.5 Appendix A FR01A - Fraud Information - Renamed the following field from: LAST-STATEMENT to BLANK on page 199. EXTERNAL-SCORE to BLANK on page 199. DEBIT-BEREAU-SCORE to BLANK on page 199. APPLICATION SCORE to BLANK on page 199. LAST-MINBAL-DATE to BLANK on page 199. LAST-MINBAL-AMT to BLANK on page 199.

Appendix D Added the following Reject Reason Code: “FC” on page 274.

July, 2009 V1.5 Initial release of this manual for V1.5.



2
Overview
This chapter provides an overview of the Authorization Processor maintenance methods.

What is AP Maintenance?The Authorization Processor (AP) is an online EFT application that performs some or all of the authorization checks necessary to process EFT transactions. The two functions of the Authorization Processor include the authorization of financial requests and the maintenance of the files that AP uses during the authorization process. These maintenance files must be continually updated so that they are synchronized as closely as possible to your institution’s internal cardholder files.

AP Maintenance allows you to update the files used by the Authorization Processor so that requests are authorized using current and accurate cardholder, account, and fraud file information.

AP Maintenance allows you to select the authorization method and products that best suit your institution. Your institution can vary the processing functions it performs based on the availability of your host or usual processor and the type of transaction it receives.

AP Maintenance MethodsThe timely maintenance of your institution’s Cardholder File, Fraud File, and Account Detail File is critical to authorize or deny transaction requests accurately. The following are the AP Maintenance methods.

AP Batch Maintenance Balance Refresh Online Maintenance from the Host AP Match and Hold AP Online Screen Maintenance


AP Batch MaintenanceYour institution can submit a batch file to FIS containing AP Maintenance information as either an initial load or as ongoing maintenance. Maintenance information includes adding new cards, deleting old records, and changing the account access for a card.

AP Batch Maintenance Message FlowThe batch maintenance process begins when the host’s application program writes AP Maintenance information to a batch file and sends that file to FIS.

NOTE: Another form of AP Maintenance not covered in this manual is online screen maintenance. Information for performing online screen mainte-nance procedures can be found in the AP Maintenance User Manual.

Figure 1 AP Batch Maintenance Flow

CardholderFile

AccountDetail File

Log HoldingFile

AuthorizationProcessor

Maintenance

APMaintenance

Screen

AdministrativeTerminal

AP MaintenanceSystem

Online EFTSystem

HostComputer


ProcessorInterface

FileMaintenance

Routing(FMR)

DataCollectionMethod

1

2

3

4

5

6

7

8

9

10


1. A program generates data or a data entry operator enters maintenance to a host system application.

2. The host formats the AP batch records and writes the maintenance to a tape or disk file. The file’s information must be written in the format required by AP.

3. If the information is on tape, the tape is removed from the host. If the information is on disk, the data is transmitted electronically.

4. If the information is on tape, the tape is physically transported to the AP system, where a member of the operations staff loads it to the tape drive.

5. An AP program is called up to read the tape or disk file.

6. AP Maintenance writes the maintenance transaction to the Log Holding file.

7. File Maintenance Routing (FMR), an online EFT process, takes the maintenance transaction from the Log Holding file.

8. FMR sends it to the Logger, which writes it to a log file for settlement and auditing purposes.

9. Optionally, FMR routes the maintenance transaction to the appropriate Processor Interface to advise the host.

10. Optionally, the Processor Interface changes the maintenance transaction’s format to one compatible with the host, then sends an advice message to the host.

Balance Refresh MaintenanceYour institution can submit a balance file to FIS to update and coordinate balances with the host.


Balance Refresh Message FlowThe balance update process beings when the host’s application writes balance information to a batch file and sends that balance file to FIS.

1. At the end of the AP business day, an offline process sends its financial transactions to the host for batch posting. AP starts accumulating unposted amounts in the Account Detail file.

Using the AP financial transactions as input, a host application program writes the necessary balance information to a new host file. The file, on either tape or disk, must be in the required AP format.

2. If the file is on tape, it is removed from the host. If the file is on disk, the data is transmitted electronically.

Figure 2 Balance Refresh Message Flow

CardholderFile

AccountDetail File

Log HoldingFile

BalanceUpdateProcess

APMaintenance

Screen



Online EFTSystem

HostComputer

1

2

3

4

APMaintenance

Screen

OperationsTerminal

BalanceUpdate

File

5

6


3. If the file is on tape, it is physically transported to the AP system, where a member of the operations staff loads it to a tape drive. If more than one tape drive is available and the Balance Update files are set up to correspond with the Account Detail files, multiple reels can be processed at the same time.

4. Balance Refresh, a batch process, receives the host input file containing the current balance information.

5. Balance Refresh uses the host file to create a new Balance Update file. Account balances in the Account Detail file are not affected.

6. Balances in the Account Detail file are replaced only when AP wants current information. This is when a data entry operator accesses the cardholder’s record in AP Maintenance.

To calculate the cardholder’s new account balances, AP takes account balances in the Balance Update file and applies the unposted amounts AP has been accumulating. AP then writes the new balances to the Account Detail file and uses them when authorizing the cardholder’s requests.

Online Host MaintenanceYour institution can submit batch maintenance files to FIS online from your host. Maintenance information includes updating account balances, adding new cards, and changing account access for a card.


Online Host Maintenance Message FlowOnline maintenance from a host originates when the host’s terminal operator enters maintenance information from a terminal connected to the host and sends that information online to FIS.

1. An entity such as a data entry operator or a computer application supplies maintenance information.

2. A program on the host writes the maintenance to either an FIS ISO message or Format 8 message (I5X) required by AP and sends it to the Processor Interface.

3. AP receives the maintenance transaction, then sends the transaction to AP Maintenance.

4. AP Maintenance updates one of the AP files.

5. AP Maintenance writes the maintenance transaction to the Log Holding file (FMRHOLD).

Figure 3 Online Host Message Flow

CardholderFile

AccountDetail File

Log HoldingFile


Maintenance

APMaintenance

Screen



Online EFTSystem

HostComputer


ProcessorInterface

FileMaintenance

Routing(FMR)

DataCollectionMethod

1

234

5

6

7

89

10


6. You can display the updated file record on an Administrative Terminal screen.


8. FMR sends it to the Logger, which writes it to a log file for settlement and auditing purposes.

9. Optionally, FMR routes it to the appropriate Processor Interface to advise the host.


AP Online Screen MaintenanceYour institution can perform online maintenance from the Administrative Terminal or your personal computer allowing you to add, update, and delete information from your cardholder’s records immediately. See the AP Online Screen Maintenance User Manual for screens and procedures for completing AP Maintenance and Quick Maintenance.


AP Online Screen Maintenance Message FlowThe online maintenance process begins when you enter the maintenance information from your Administrative Terminal or personal computer and flows through the AP system.

1. First access the appropriate AP Maintenance screen. Enter the information and press the Update Function key. The AP Maintenance system updates one of the AP files.

2. The AP Maintenance system writes the maintenance transaction to the Log Holding file and displays a message on your screen.


4. FMR sends the maintenance transaction to the Logger, which writes it to a log file for settlement and auditing purposes.

Figure 4 Online Screen Maintenance Message Flow

CardholderFile

AccountDetail File

Log HoldingFile

APMaintenanceProcesses

APMaintenance

Screen



Online EFTSystem

HostComputer

1

2

3

4

5

6

ProcessorInterface

Logger

FileMaintenance

Routing(FMR)

7


5. Optionally, FMR routes the maintenance transaction to the appropriate Processor Interface.


AP Match and HoldAP Match and Hold is an optional feature of the Authorization Processor that places a hold against your cardholder’s account when a point-of-sale (POS), Debit MasterCard® or Visa Check™ debit transaction is pre-authorized online but is not settled. Holds are removed from the AP Hold File when the transactions are matched and settled, or when the hold expires.

AP creates the AP Hold File, which is used to automatically update account balances on your host system. This keeps AP and the host synchronized with a minimum amount of effort.

Match and Hold FlowWhen a card is used for a purchase, a merchant can verify that the cardholder is valid and has the available funds to complete the purchase. These items are eventually turned into online messages that are used to post and settle at the completion of the sale.

The first part of the match and hold flow is the transaction pre-authorization, which is a 100 level message.

The second part of the match and hold flow is the settled item, which is a 200 level message. (The standard at FIS is to expire holds that are not matched after three calendar days.)

Figure 5 Match and Hold Flow

Hold ExpiredAfter

3 Calendar Days

Match Holdwith

Settled ItemPre-Authorization

TransactionSent


AP Authorization MethodsThe following authorization methods are available to institutions using the FIS Authorization Processor.

AP CompleteThe AP Complete authorization method has the Authorization Processor perform all authorizations. A record of all accepted and rejected transactions can be written to a file and transmitted to the host processor.

AP CooperativeThe AP Cooperative authorization method uses a combination of authorization methods. When the host or usual processor is not available, AP performs any authorizations. When the host or usual processor is available, AP can perform some initial checks and then send the request to the cardholder’s processor, who can perform any final checks.

AP Configuration MethodsThe following authorization configuration methods are available to institutions using the FIS Authorization Processor.

AP PositiveThe AP Positive configuration method accesses information about every cardholder and every card issued to approve a transaction. A cardholder file exists that contains one record for each cardholder letting you place cardholders in different limit groups. A Positive File requires that you maintain account information and balance information, and provides information such as such as overdraft support and Open Account Relationships (OAR).

AP Positive with BalancesThe AP Positive with Balances configuration method accesses all of the same information as AP Positive as well as the cardholder’s actual balance file. This balance file contains information about all of your institution’s cardholders, the cardholder’s accounts, and the cardholder’s account balances, including balance refresh and current balance information. AP Positive with Balances also authorizes transactions based on credit line, card status information, and overdraft and hold information. AP Positive with Balances is the most secure authorization method.


AP ServicesThe following optional authorization services are available to institutions using the FIS Authorization Processor.

Account Detail ServicesAccount Detail services provides your institution with account level information about all of your cardholders, the cardholder’s accounts, and the cardholder’s account balances. This includes the cardholder’s balance refresh and current account balance information. The Account Detail File is used to authorize transactions based on balance, credit line and status information, as well as overdraft and hold information.

Card Activation ServicesThe Card Activation and Expiration Date Matching (CA/EDM) service provides your institution with information to validate the identity of your cardholder, the previous card expiration date, and previous card activation flag. This optional Visa Check™, Debit MasterCard® and Discover Debit service is available for newly issued or reissued cards.

Card Issuance and Management System (CIMS) ServicesCIMS service provides your institution with access to the FIS Card Issuance and Management System (CIMS). Your institution can use CIMS to issue, order, and maintain ATM debit cards online.

Scoring and Case ManagementScoring and Case Management for Visa Check™ and Debit MasterCard® is a comprehensive service that uses the Falcon™ Fraud Management system to identify suspicious transactions and provide quick action to review these transactions and stop the occurrence of future fraudulent transactions.

Name Search ServicesThe Name Search service allows your institution to directly access an AP Cardholder record using the cardholder’s PAN, Plastic Number, Account Number, or Cardholder Name. You can also access cardholder records by the name and primary or secondary deposit account numbers. If you choose to search by the cardholder name, the search is performed based on the exact spelling of the name entered.


3
Using Batch Maintenance
This chapter describes the procedures to follow when you submit an AP Batch Maintenance file. At the end of the chapter are frequently asked questions from customers with responses from the Technical Support at FIS.

What is an AP Maintenance File?An AP Maintenance File is a batch file that consists of a header record, the required AP Maintenance detail records, and a trailer record. The header and trailer records are at the institutional level, with all of the required and optional segments following the header record and preceding the trailer record specific to that institution. The detail record segments are used to add, update, or delete individual account, cardholder, and fraud information records stored in the Account Detail File, Cardholder File, and Fraud File of the Authorization Processor.

You can submit an AP batch file to FIS containing maintenance information as either an initial load or as ongoing AP Batch Maintenance.

NOTE: It is critical that you submit the required segments in the recom-mended sequence. If any of the required segments for a cardholder are not submitted or not submitted in the proper order, all segments for that cardholder are rejected, and AP will process the next card-holder record in the batch file. All AP batch errors are written to the AP Batch Maintenance Exception Report. Furthermore if any data in a segment is cannot be validated or is in error, all segments for that cardholder are rejected and AP will process the next cardholder record in the batch file.


Header Record and Trailer RecordsHeader and trailer records are required to ensure that all transmitted AP batch files are received by FIS. The key field in the header and trailer records is CONTROL-NBR. The control number field is the sequential numbering that tracks all AP files sent to FIS.

Every time you send in a file, increment by at least one the existing control number. Start with number 000 or 001 and continue through to 999. When your control number reaches 999, reset the control number to either 000 or 001. The control number in the header record must match the control number in the trailer record. Optionally, the batch control number can be set to any number greater than the last successfully completed batch number. At some point, the batch control number must be set to 999 so that it can roll back to either 000 or 001.

Header Record (Normal Transmission)

NOTE: If you re-send a file after your original file transmission fails, use the control number from the original or failed file. Do not increment the value in the CONTROL-NBR field by one as you would when sending an original file.

Number and Field Name Pos.

Len. Status

Field Attributes Description/Usage

1 BATCH-MSG-TYPE

1 2 Required Record IdentifierValue = HD

2 HOST-ID 3 10 Required Alpha Numeric

Originator identifier. FIS supplies this value. The field is left justified and blank filled.

3 CONTROL-NBR

13 3 Required Numeric This key field is the file sequence number. Value = 001 - 999Note: If the control override parameter is set to N, the control number must be incremented by 1 for each file transmission. If the control override parameter is set to U, the control number can be incremented by more than 1 for each file transmission.

4 DATE-JULIAN

16 5 Required Numeric The file date used for archiving in Julian format.Value = YYDDDYY = YearDDD = Julian Day


Header Record Sample

Trailer Record

5 NBR-RECORDS-TOTAL

21 11 Required Numeric System edit. Total number of detail records for the institution.Value = Actual number of records.Note: Does not include the Header record.

6 HASH-FLAG

32 1 Required AlphaNumeric

System edit.Value = Y (Yes)

7 FILLER 33 48 Required AlphaNumeric

Ensure 80 byte record.Value = Spaces

Number and Field Name Pos.

Len. Status


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y

Field Number and Name Pos. Len. Status


1 BATCH-MSG-TYPE

1 2 Optional Record identifier.Value = TR

2 HOST-ID 3 10 Required AlphaNumeric

Originator identifier. FIS supplies this value. The field is left justified and blank filled.

3 CONTROL-NBR

13 3 Required Numeric This key field must be incremented by at least one for each file transmission. File sequence ensures updates are applied in correct order. Values = 001 - 999

4 NBR-RECORDS-TOTAL

16 11 Required Numeric System edit. The total number of detail records for this institution. Value = Actual number of records.Note: Does not include the Trailer record.


Trailer Record Sample

Interaction/ProcessingIf CEDCOPT Verify-PIN-Option = 2 (AP provides this info) and CEDDES Quick-Kill = Yes, the AP PIN Fail Count is incremented with each bad PIN transaction because AP pro-vides the PIN offset to PMC to validate the PIN. The CEDDES Quick-Kill setting has no impact.

If CEDCOPT Verify-PIN-Option = 1 (Always validate the PIN) and CEDDES Quick-Kill = Yes, the AP PIN Fail Count is not incremented with each bad PIN transaction because PMC is validating the PIN, but not basing the validation on information provided by AP. Because the CEDDES Quick-Kill flag is turned on, AP is not aware that PMC denied the transaction for bad PIN.

5 HASH-TOTAL 27 10 Required Numeric System edit. The sum of the last 10 digits of the PAN in the CH records added to the last 10 digits of the account numbers in the AD01A and AD01B records. If that sum is greater than 10 positions, all left-most positions greater than 10 positions are truncated. If the account number is less than 10 digits, the field is right filled with zeros.Value = 9999999999

6 DATE-RECVD 37 5 Optional AlphaNumeric

The date file is received for archiving purposes. YY = Year, DDD = Julian DayValue = YYDDD

7 TIME-RECVD 42 6 Optional AlphaNumeric

The time file is received for archiving purposes.Value = 6 spaces

8 FILLER 48 33 Optional AlphaNumeric

Ensure 80-byte record.Value = 33 spaces



1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

TRLSBM 00299999999999888888888807929120000


Detail SegmentsAP Batch Maintenance allows you to send batch edit files containing account, limit, and cardholder information to maintain your cardholder, fraud, and account detail files to FIS. Each AP Batch Maintenance file consist of logical groupings called segments which consist of one or more detail records of related information. A standard AP batch record layout consists of a header record, various detail records, and a trailer record. The specific segments you are required to submit are defined in your AP parameter file.

Segment FieldsEach segment contains field information from the account detail, cardholder, and fraud files. Along with the standard fields, each segment contains one or more key fields. A segment’s key field information cannot be updated. If you want to update or change key field information, first submit a delete for that segment, and then submit an add for that segment with the updated key field information. The key fields for the cardholder and fraud segments include the PAN, PLASTIC-NBR and ACCT-NO and the key fields for the account detail segments include FI-ID, ACCT-TYPE, and ACCT-NO.

All fields are left justified with trailing blank spaces. You can enter special characters to clear or blank-out existing values. All alpha values are typed in upper case. The following table explains the rules that apply to AP Batch Maintenance fields:

Required Segment OrderWhen you submit an AP Batch Maintenance file, all of the segments within that file must be submitted in the required order. A base segment is required for each record, while other detail record segments are required or optional depending on the type of authorization method you use and how AP processes that segment information.

Organize the segments in your file in ascending numerical order according to record type. To prevent the duplication of cardholder, fraud, or account information, enter and submit all of your institution’s delete segments first, followed by your institution’s add segments, and finally your institution’s update segments.

If You Enter Then

Blank spaces You do not change the existing data.

Asterisks You blank out existing data. (Alpha or Alpha/Numeric fields only)

Zeros You reset the values to zero.

Any other characters You replace existing data with the new data.


Within the add, delete, and update segments, enter all of the cardholder segments in ascending numeric order, followed by the Scoring and Case Management segments in ascending numeric order, and finally the account detail segments in ascending numeric order.

The table below shows the order to follow when you submit your segment information.

Record Segment Segment Keyword

Cardholder Base BASE

CH01A Cardholder Information CARDINFO

CH02A Track II Information TRACK2

CH03A Account Information ACCTINFO

CH03B Account Information ACCTINFO

CH04A Override Limits OVERRIDE

CH06A Limit Hold Information HOLDLIST

CH08A Greeting Name Information NAMEINFO

CH09A Override Expire OVREXPR

CH14A Additional Card Info ADDLCRD

CH18A Cardholder Management Group Information

CARDMAN

CH18B Cardholder Management Group Information

CARDMAN

CH18C Cardholder Management Group Information

CARDMAN

CH18D Cardholder Management Group Information

CARDMAN

CH19A Cardholder Management Member Information

CARDMAN2

CH19B Cardholder Management Member Information

CARDMAN2

CH22A Card Validation Information VALIDATE

CH22B Card Activation Information VALIDATE

Scoring and Case Management

Base

FR01A Fraud Information FRINFO

FR02A Fraud Activity Information ACTIVITY


How do I submit an initial load?Submitting an initial load is the most effective maintenance method for adding a large number of records, but is not recommended for performing ongoing batch maintenance. When you submit AP Batch Maintenance files in an initial load, only basic editing of the input records is performed and the maintenance files are not logged for offline reporting.

An initial load should consist of all new cardholder and account detail records for your institution. All required segments must be included for AP to successfully process the batch. When FIS receives your transmission file, they create an initial input file from that transmission file.

FR02B Fraud Activity Information ACTIVITY

FR03A Fraud Member Information MEMBER

FR03B Fraud Member Information MEMBER

Account Detail Base BASE

AD01A Account Detail ACCTDTL

AD01B Account Detail ACCTDTL

AD02A Overdraft Information OVERDRFT

AD02B Overdraft Information OVERDRFT

AD03A Account Hold List ACCTHOLD

AD03B Account Hold List ACCTHOLD

AD06A Additional Account Hold Info ADDLHOLD

AD06B Additional Account Hold Info ADDLHOLD

AD06C Additional Account Hold Info ADDLHOLD

AD06D Additional Account Hold Info ADDLHOLD

Record Segment Segment Keyword

NOTE: If you submit an initial load for AP Batch Maintenance, you must send FIS a test file containing 10 to 20 cardholder records. After the test file is verified, you can send FIS a productive initial load file contain-ing your institution’s cardholder records.

The LIMIT-GROUP-ID field needs a value when doing the initial load via batch maintenance.


File Transmission FormatWhen you submit an initial load maintenance file, all fields are left justified and space filled to the right. Send your initial batch file transmission to FIS on a tape with the maintenance information and the Tape Information Form attached. (You can get a copy of the Tape Information Form from your Account Manager or Project Manager at FIS.) You can also send a diskette containing a flat file of your AP Maintenance information. The following tape and diskette characteristics are required to update AP’s files:

Tape File

ASCII format. Unlabeled. Record length = 80 bytes. Pad with spaces to the record’s end. Block size = A multiple of 80, up to 4080 characters. The block size is determined

by the network’s disk size.

Diskette File

Entry Sequence File. ASCII format. Record length = 80 bytes. Pad with spaces to the record’s end.

How do I submit ongoing maintenance?When you perform ongoing AP Batch Maintenance, you normally add new cardholder records, delete expired cardholder records, and update existing cardholder records. When you submit ongoing maintenance, your input records are edited and logged for offline reporting.

You choose a file transmission schedule that best suits your institution’s business requirements to submit your ongoing AP Batch Maintenance. Your institution can submit ongoing maintenance files daily, weekly, or bi-weekly.

NOTE: After loading the tape file or diskette, view the AP Batch Load Excep-tion Report to determine if any records have been rejected and the reject reason.

NOTE: If your institution uses any type of PIN change product (PIN change via ATM or PIN change via EIVR) through FIS, you CANNOT submit a full file replacement. A full file replacement will overwrite all the PIN offsets, including those previously changed by cardholders. Those cards will be denied for an incorrect PIN.

The LIMIT-GROUP-ID field can be blank when doing Ongoing batch maintenance.


JCLYou use an RJE, NJE, FTP, or a CONNECT:Direct™ connection to send your ongoing AP Batch Maintenance files to FIS. The JCL required to execute your maintenance files is provided by your Account Manager or Project Manager at FIS. Following is a sample of JCL you might receive from FIS.

Hash TotalsTo calculate hash totals for AP Batch Maintenance processing, take the last 10 digits of the PAN in the CH01A, CH02A, CH03A, CH03B records and add them to the last 10 digits of the account numbers in the AD01A and AD01B records. If that sum is greater than 10 positions, all left-most positions greater than 10 are truncated. If the account number is less than 10 digits, the field is right filled with zeros.

Dummy RecordsIf you do not have ongoing maintenance information to send to FIS on your scheduled maintenance day, you must send a dummy record with the properly formatted header and trailer records. You have the option of including a dummy record with any ongoing maintenance file you send to FIS. The data contained in the dummy record must be included in the hash total.

Card 1//EF………………………………………….Card 2//……………………………………………….Card 3/*ROUTE………………………………….Card 4//……………………………………………….Card 5//CREATE………………………………. file header record detail records file trailer recordCard 6Card 7/*……………………………………………….Card 8//……………………………………………….

Number and Field Name

Position

Length

Field Attribute Description/Usage

1 1 2 Value = Spaces

2 RECORD-NAME 3 2 Alpha/Numeric

Value = CH

3 SEG-ID 5 2 Numeric Value = 01


Dummy Record Sample

4 OCCURRENCE-SECTION

7 1 Alpha/Numeric

Value = A

5 FILE-UPDATE-CODE

8 1 Numeric Value = 8

6 PAN 9 19 Alpha/Numeric

Value = 9999999999999999999Note: Must be 19 number 9s.

7 PLASTIC NBR 28 5 Alpha/Numeric

Value = Spaces

8 FILLER 33 48 Alpha/Numeric

Value = Spaces

Number and Field Name

Position

Length

Field Attribute Description/Usage

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH01A89999999999999999999


Which detail records should I submit?This chapter provides a list of the segments that are required for the type of processing your institution performs and the products you use, as well as a sample of the segment’s input file.

If you do not submit all of the required segment records and information for a cardholder, AP detects the error and rejects the cardholder segments with the error, reports the error on the AP Batch Maintenance Exception Report, and continues to process the next cardholder in the AP batch file.

Deleting Information Only submit a delete if you are updating key field information or deleting a

cardholder. Submit an update to eliminate existing segment information.

Submit only segment CH01A to delete all cardholder information from the cardholder file.

If you use Scoring and Case Management and are deleting cardholder information, you must submit the FR01A segment to delete all of the cardholder’s fraud segments.

Submit an AD01A and AD01B to delete all account detail and balance information for a cardholder. If you only submit the AD01A, an error is reported and the account detail information is not deleted.

If you have multiple cardholders linked to one account, delete only the cardholder information for the cardholder. Do not delete the account detail information for a cardholder unless you are deleting all of the associated cardholders.

Adding Information Submit all the appropriate required and optional segments and the required

records for each segment.

Submit all of the required segments to add, update, and delete an individual cardholder before you submit the segments for the next cardholder.

NOTE: You must submit all segments required for the AP products used by your financial institution. This includes the individual CH segments plus their related A, B, C, and D records. All segments should contain blanks in Position 1 and 2 as segment data appears in Position 3.


Updating Information Enter all of the segments for the all of the products that were originally submitted

when you added the cardholder for a full replacement file. Be sure to include all of the segments for all of the cardholder’s products.

Enter only the field information that is being updated and blank fill the fields that are not being updated for an updated field AP Maintenance file.

Update the information in the specific fields you want to change and blank fill all other fields.

If you update a segment with multiple segment records (CH18A, CH18B, CH18C, and CH18D), you must submit all of the required segment records.

If you update key field information, submit a delete for the segment with the key field followed by an add for that segment. The add segment contains the updated key field information.

If you update an account number with multiple cardholders, first submit a delete with the CH03A and CH03B segments to eliminate any cardholders associated with that account. Next, submit the CH03A, CH03B, AD01A, and AD01B segments to add the new account number and all of the associated cardholders.

Submitting Account Detail InformationThe account detail file uses balance information about all cardholder accounts and cardholder account balances; any account information tied to the cardholder’s balance. The account detail file uses credit line and status information as well as overdraft and hold information to authorize transactions.

NOTE: If your institution uses any type of PIN change product (PIN change via ATM or PIN change via EIVR) through FIS, you CANNOT submit a full file replacement. A full file replacement will overwrite all the PIN offsets, including those previously changed by cardholders. Those cards will be denied for an incorrect PIN.


Deleting Account Detail InformationSubmit the following header, trailer, and detail records in the sequence listed below to delete account detail information. The account detail records delete all of the account information for the specified account.

Input Sample

Segment Name Segment Number Segment Status

Header Record Required

Detail Records Required

Cardholder Information CH01A Required

Account Detail AD01A Required

Account Detail AD01B Required

Trailer Record Required

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A61010000000000000001 1000000000 AD01A61010000000000000001DDA DDA-123456 AD01B61010000000000000001DDA DDA-123456 List Additional Cardholder Records Here TRLSBM 00299999999999888888888807929120000


Adding Account Detail InformationSubmit the following header, trailer, and detail records in the sequence listed below to add account detail information.

File Sample

Input Sample





Account Information CH03A Required

Account Information CH03B Required




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A53535000000000000060 1000004352 111111111 ABLG01 CH03A53535000000000000060 1000004352DDA DDA-1 DDA CH03B53535000000000000060 DDA-1 YYYYYYYYY NN AD01A51000004352DDA DDA-1 +010000000+010000000+000000000 AD01B51000004352DDA DDA-1 111111111

List Additional Cardholder Records Here TRLSBM 00299999999999888888888807929120000


Updating Account Detail InformationSubmit the following header, trailer, and detail records in the sequence listed below to update account detail information. You are required to submit only the segments you are updating; all other segments are optional. Enter only the specific field information that you are updating or changing for that segment. All other field information should be blank filled.

File Sample

NOTE: If you update segment information, you are required to send FIS only those segments you are updating and any related records for that segment. For example, if you update information in segment AD01A, send FIS an AP Batch Maintenance file with a FILE UPDATE CODE of eight for segments AD01A and AD01B.

To change an account number for an existing cardholder (financial institution is set up for Account Info only) when the account number is no longer valid: send a CH03A for the old account umber with a FILE UPDATE CODE of six (delete), followed by a CH03A and CH03B for the new account number with a FILE UPDATE CODE of five (add).

To change an account number for an existing cardholder (financial institution set up for Account Detail) when the account number is no longer valid: send a CH03A, CH03B, and AD01A for the old account number with a FILE UDPATE CODE of 6 (delete), followed by CH03A, CH03B, AD01A, and AD01B for the new account number with a FILE UPDATE CODE of five (add).



Detail Records Only those segments that are being updated are required

Cardholder Information CH01A Required if being updated

Account Information CH03A Required if this segment or CH03B is being updated

Account Information CH03B Required if this segment or CH03A is being updated


Full Replacement File Input Sample

A full replacement file contains all of the segments and field information originally submitted when the cardholder was added. The original add segments included in the full replacement update file are CH01A, CH03A, CH03B, AD01A, and AD01B.

Account Detail AD01A Required if this segment or AD01B is being updated

Account Detail AD01B Required if this segment or AD01A is being updated



1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A83535000000000000060 1000004352 111111111 ABLG01 CH03A83535000000000000060 1000004352DDA DDA-1 DDA CH03B83535000000000000060 DDA-1 YYYYYYYYY NN AD01A81000004352DDA DDA-1 +010000000+010000000+000000000 AD01B81000004352DDA DDA-1 111111111

List Additional Cardholder Records Here

TRLSBM 00299999999999888888888807929120000


Field Update File Input Sample

A file with updated account detail field information contains only the key field information and the updated field information. Enter the key field information and any updated field information, and blank fill the fields not being updated.

In the following example, the PURCHASES field (position 60) of segment CH03B is being changed from Yes to No. Submit segments CH03B and CH03A.

Submitting Cardholder Validation InformationThe cardholder validation information is used to validate the identity of your cardholder and activate cards using the previous card expiration date and previous card activation information.

Deleting Cardholder Validation InformationSubmit the following header, trailer, and detail records in the sequence listed below to delete cardholder validation or card activation information.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH03A83535000000000000060 CH03B83535000000000000060 N


TRLSBM 00299999999999888888888807929120000







Input Sample

Adding Cardholder Validation InformationSubmit the following header, trailer, and detail records in the sequence listed below to add cardholder validation or activation information.

File Sample

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A61010000000000000001 1000000000

List Additional Cardholder Records HereTRLSBM 00299999999999888888888807929120000





Track II Information CH02A Required

Card Validation CH22A Required

Card Validation CH22B Required



Input Sample

Updating Cardholder Validation InformationSubmit the following header, trailer, and detail records in the sequence listed below to update cardholder validation or card activation information. You are required to submit only the segments you are updating; all other segments are optional. Enter only the specific field information that you are updating or changing for that segment. All other field information should be blank filled.

File Sample


A full replacement file contains all of the field information and all of the segments that were originally submitted when you added the cardholder. The original add segments included in the full replacement update file are segments CH01A, CH02A, CH22A, and CH22B.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A53737000000000000060 1000004352 111111111 ABLG01 CH02A53737000000000000060 003160 4912 CH22A53737000000000000060 396860731FLAKE 41435274554149635611 CH22B53737000000000000060 USER DEFINED 1


Segment Name Segment Number Segment status


Detail Records Submit only the detail records that are being updated

Cardholder Information CH01A Required if being updated

Track II CH02A Required if being updated

Card Validation CH22A Required if being updated

Card Validation CH22B Required if being updated




A file with updated card validation field information contains only the key field information and the updated field information. Enter the key field information and any updated field information, and blank fill the fields not being updated.

In the following example, the USER DEFINED VALIDATION field (position 33) of segment CH22B is being changed from USER DEFINED to No Middle Initial. Submit segments CH22A and CH22B.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A83737000000000000060 1000004352 111111111 ABLG01 CH02A83737000000000000060 003160 4912 CH22A83737000000000000060 396860731FLAKE 41435274554149635611 CH22B83737000000000000060 USER DEFINED 1


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH22A83737000000000000060 CH22B83737000000000000060 No Middle Initial



Submitting Card Issuance and Management InformationThe Card Issuance and Management System (CIMS) information is used to issue and control the online ordering and maintenance of ATM debit cards. CIMS services include, flexible processing, personal identification number (PIN) handling, audit and security, reporting, and interfaces to leading embossing/encoding vendors.

Deleting CIMS InformationSubmit the following header, trailer, and detail records in the sequence listed below to delete CIMS information.

Input Sample

NOTE: Consolidated Address Verification System (AVS) records for custom-ers configured for CIMS are not used for the date fields on segment CH19 records. These fields are automatically populated with current maintenance dates.






1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999YY CH01A61010000000000000001 1000000000



Adding CIMS InformationSubmit the following header, trailer, and detail records in the sequence listed below to add CIMS information.

File Sample

NOTE: When adding a cardholder: Send both CH19A and B segments even if not ordering a card or

PIN for the cardholder. (See “CH19A - Card Management Member Information” on page 175 and “CH19B - Card Management Member Information” on page 181 for more information.)

Send the CH01 segment first (required for an add), followed by a CH04 for each override limit. (See “CH01A - Cardholder Information” on page 135 and “CH04A - Override Limits Information” on page 154 for more information.)





Track II CH02A Required



Card Management Group CH18A Required

Card Management Group CH18B Optional

Card Management Group CH18C Required

Card Management Group CH18D Required

Card Management Member CH19A Required

Card Management Member CH19B Required



Input Sample

Updating CIMS InformationSubmit the following header, trailer, and detail records in the sequence listed below to update CIMS information. You are required to submit only the segments you are updating; all other segments are optional. Enter only the specific field information that you are updating or changing for that segment. All other field information should be blank filled.

File Sample

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999YY CH01A53535000000000000060 1000004352 111111111 ABLG01 CH02A53535000000000000060 003160 4912 CH03A53535000000000000060 1000004352DDA DDA-1 DDA CH03B53535000000000000060 DDA-1 YYYYYYYYY NN CH18A53535000000000000060 392 PARK HILL DRIVE CH18B53535000000000000060 CH18C53535000000000000060 PEWAUKEE WI5307212340Y CH18D53535000000000000060 CH19A53535000000000000060 01PHYLISS XB0199610061003 CH19B53535000000000000060 0N1996100119961006


NOTE: If you update segment information, you are required to send FIS only those segments you are updating and any related records for that segment. For example, if you update information in segment CH18A, send FIS an AP Batch Maintenance file with a FILE UPDATE CODE of eight for segments CH18A, CH18C, and CH18D.



Detail Records Only those segments that are being updated are required.

Cardholder Information CH01A Not required

Track II CH02A Required if being updated



A full replacement file contains all of the segments and field information originally submitted when the cardholder was added. The original add segments included in the full replacement update file are CH01A, CH02A, CH03A, CH03B, CH18A, CH18B, CH18C, CH18D, CH19A, and CH19B.

Account Information CH03A Required if this segment or CH03B is being updated.

Account Information CH03B Required if this segment or CH03A is being updated.

Card Management Group CH18A Required if this segment or CH18B, CH18C, or CH18D are being updated.

Card Management Group CH18B Required if this segment is being updated.

Card Management Group CH18C Required if this segment or CH18A, CH18B, or CH18D are being updated.

Card Management Group CH18D Required if this segment or CH18A, CH18B, or CH18C are being updated.

Card Management Member

CH19A Required if this segment or CH19B is being updated.

Card Management Member

CH19B Required if this segment or CH19A is being updated.




Field Update Input Sample

A file with updated card issuance and management field information contains only the key field information and the updated field information. Enter the key field information and any updated field information, and blank fill the fields not being updated.

In the following example, the ADDRESS-1 field (position 33) of segment CH18A is being changed from 1123 ANYSTREET ST to 4455 NEWSTREET. Submit segments CH18A, CH18B, CH18C, and CH18D.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999YY CH01A81010000000000000001 1000000000 YYYYYNNNY ABLG01 CH02A81010000000000000001 006969 9912 CH03A81010000000000000001 1000000000DDA DDA-ABC-01-APB DDA CH03B81010000000000000001 CHECKING-1 YYYYYYYYY YY CH03A81010000000000000001 1000000000SAV SAV-ABC-01-APB SAV CH03B81010000000000000001 SAVINGS-1 YYYYYYYYY NN CH18A81010000000000000001 1123 ANYSTREET ST CH18B81010000000000000001 CH18C81010000000000000001 WASHINGTON DC4883794110Y CH18D81010000000000000001 SS123000000/BD062661 CH19A81010000000000000001 01JOHN Q PUBLIC C0 CH19B81010000000000000001 0N1999080819991012

Next Cardholder

CH01A81010000000000000002 1000000000 YYYYYNNNY ABLG01 CH02A81010000000000000002 007070 9912 CH03A81010000000000000002 1000000000DDA DDA-ABC-01-APB DDA CH03B81010000000000000002 CHECKING-1 YYYYYYYYY YY CH03A81010000000000000002 1000000000SAV SAV-ABC-01-APB SAV CH03B81010000000000000002 SAVINGS-1 YYYYYYYYY NN CH18A81010000000000000002 1123 CRABAPPLE CT CH18B81010000000000000002 CH18C81010000000000000002 WASHINGTON DC4883794110Y CH18D81010000000000000002 SS123000000/BD070445 CH19A81010000000000000002 01GEORGE WASHINGTON C0 CH19B81010000000000000002 0N1999080819991012


TRLSBM 00299999999999888888888807929120000


Submitting Fraud InformationThe fraud information is used for Scoring and Case Management. This information includes cardholder data to assist in fraud detection and in contacting the cardholder.

Deleting Fraud InformationSubmit the following header, trailer, and detail records in the sequence listed below to delete fraud information.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999YY CH18A81010000000000000001 4455 NEWSTREET ST CH18B81010000000000000001 CH18C81010000000000000001 CH18D81010000000000000001


TRLSBM 00299999999999888888888807929120000







Fraud Information FR01A Required



Input Sample

Adding Fraud InformationSubmit the following header, trailer, and detail records in the sequence listed below to add fraud information.

File Sample

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A61010000000000000001 AD01A61010000000000000001 AD01B61010000000000000001 FR01A61010000000000000001






Track II CH02A Required



Card Management Group CH18A Required

Card Management Group CH18B Optional

Card Management Group CH18C Required

Card Management Group CH18D Required

Card Management Member CH19A Required

Card Management Member CH19B Required

Card Validation CH22A Required

Card Validation CH22B Required

Account Detail AD01A Optional


Account Detail AD01B Optional

Fraud Information FR01A Required

Fraud Activity Information FR02A Conditional*

Fraud Activity Information FR02B Conditional*

Fraud Member Information FR03A Conditional*

Fraud Member Information FR03B Conditional*



* See the following AP batch layouts for information on when these fraud segments are required:“FR02A - Fraud Activity Information” on page 202“FR02B - Fraud Activity Information” on page 204“FR03A - Fraud Member Information” on page 206“FR03B - Fraud Member Information” on page 208


Input Sample

Updating Fraud InformationSubmit the following header, trailer, and detail records in the sequence listed below to update fraud information. You are required to submit only the segments you are updating; all other segments are optional. Enter only the specific field information that you are updating or changing for that segment. All other field information should be blank filled.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A53737000000000000060 1000004352 111111111 ABLG01 CH02A53737000000000000060 003160 4912 CH03A53737000000000000060 1000004352DDA DDA-1 DDA CH03B53737000000000000060 DDA-1 YYYYYYYYY NN CH18A53737000000000000060 392 PARK HILL DRIVE CH18B53737000000000000060 CH18C53737000000000000060 PEWAUKEE WI5307212340Y CH18D53737000000000000060 CH19A53737000000000000060 01PHYLISS FRAUD XB0199610061003 CH19B53737000000000000060 0N1996100119961006 CH22A53737000000000000060 396860731FLAKE 41435274554149635611 CH22B53737000000000000060 USER DEFINED 1 AD01A53737004352DDA DDA-1 +010000000+010000000+000000000 AD01B53737004352DDA DDA-1 111111111 FR01A53737000000000000060 1998010119980101999999999Y19980101000060000 FR02A53737000000000000060 200101011998010119980101000010000019980101 FR02B53737000000000000060 0000003300199801010000004400199801010000004400N FR03A53737000000000000060 02414341562219640926311760123SMITH FR03B53737000000000000060 USER DEFINED 3


NOTE: If you update segment information, you are required to send FIS only those segments you are updating and any related records for that segment. For example, if you update information in segment FR02A, send FIS an AP Batch Maintenance file with a File- Update-Code of eight for segments FR02A and FR02B.


File Sample


Header Record Required.

Detail Records Only those segments that are being updated are required.

Cardholder Information

CH01A Required if being updated.

Track II CH02A Required if being updated.



Card Management Group Information

CH18A Required if this segment or CH18B, CH18C, or CH18D are being updated.


CH18B Required if this segment is being updated, otherwise Optional.


CH18C Required if this segment or CH18A, CH18B, or CH18D are being updated.


CH18D Required if this segment or CH18A, CH18B, or CH18C are being updated.

Card Management Member Information


Card Management Member Information


Card Validation Information


Card Validation Information


Account Detail AD01A Required if this segment or AD01B is being updated.

Account Detail AD01B Required if this segment or AD01A is being updated.

Fraud Information FR01A Required if being updated

Fraud Activity Information

FR02A Required if this segment or FR02B is being updated.

Fraud Activity Information

FR02B Required if this segment or FR02A is being updated.



A full replacement file contains all of the segments and field information originally submitted when the cardholder was added. The original add segments included in the full replacement update file are CH01A, CH02A, CH03A, CH03B, CH18A, CH18B, CH18C, CH18D, CH19A, CH19B, CH22A, CH22B, AD01A, AD01B, FR01A, FR02A, FR02B, FR03A, and FR03B.

Fraud Member Information

FR03A Required if this segment or FR03B is being updated.

Fraud Member Information

FR03B Required if this segment or FR03A is being updated.



1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A83737000000000000060 1000004352 111111111 ABLG01 CH02A83737000000000000060 003160 4912 CH03A83737000000000000060 1000004352DDA DDA-1 DDA CH03B83737000000000000060 DDA-1 YYYYYYYYY NN AD01A83737004352DDA DDA-1 +010000000+010000000+000000000 AD01B83737004352DDA DDA-1 111111111 AD03A83737000233DDA 1237810001 00000000000100482700 V1 AD03B83737000233DDA 1237810001 000527 CH18A83737000000000000060 392 PARK HILL DRIVE CH18B83737000000000000060 CH18C83737000000000000060 PEWAUKEE WI5307212340Y CH18D83737000000000000060 CH19A83737000000000000060 01PHYLISS FRAUD XB0199610061003 CH19B83737000000000000060 0N1996100119961006 CH22A83737000000000000060 396860731FLAKE 41435274554149635611 CH22B83737000000000000060 USER DEFINED 1 FR01A83737000000000000060 1998010119980101999999999Y19980101000060000 FR02A83636000000000000060 200101011998010119980101000010000019980101 FR02B83636000000000000060 0000003300199801010000004400199801010000004400N FR03A83737000000000000060 02414341562219640926311760123SMITH FR03B83737000000000000060 USER DEFINED 3




A file with updated fraud field information contains only the key field information and the updated field information. Enter the key field information and any updated field information, and blank fill the fields not being updated.

In the following example, the USER DEFINED VALIDATION field (position 33) of segment FR03B is being changed from USER DEFINED to MIDDLE NAME JOHN. Submit segments FR03A and FR03B.

Submitting Name Search InformationThe name search information is used to access cardholder records by the cardholder’s name and primary or secondary deposit account numbers. This allows you direct access to an AP cardholder record using the PAN and plastic number, as well as the account number or cardholder name.

Deleting Name Search InformationSubmit the following header, trailer, and detail records in the sequence listed below to delete name search information.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y FR03A83737000000000000060 FR03B83737000000000000060 MIDDLE NAME JOHN








Input Sample

Adding Name Search InformationSubmit the following header, trailer, and detail records in the sequence listed below to add name search information. If you are adding any other product information for this cardholder, be sure to include the required segments for the additional products as well.

File Sample

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A61010000000000000001 1000000000








Greeting Name CH08A Required



Input Sample

Updating Name Search InformationSubmit the following header, trailer, and detail records in the sequence listed below to update name search segment information. You are required to submit only the segments you are updating; all other segments are optional. Enter only the specific field information that you are updating or changing for that segment. All other field information should be blank filled.

File Sample

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A53535000000000000060 1000004352 111111111 ABLG01 CH03A53535000000000000060 1000004352DDA DDA-1 DDA CH03B53535000000000000060 DDA-1 YYYYYYYYY NN CH08A53535000000000000060 FRANK/PHYLIIS//MR.


TRLSBM 00299999999999888888888807929120000

NOTE: If you update segment information, you are required to send FIS only those segments you are updating and any related records for that segment. For example, if you update information in segment CH03A, send FIS an AP Batch Maintenance file with a FILE UPDATE CODE of eight for segments CH03A and CH03B.


Header Record Required.

Detail Records Only those segments being updated are required.

Cardholder Information CH01A Required if being updated.



Full Replacement Input Sample

A full replacement file contains all of the segments and field information originally submitted when the cardholder was added. The original add segments included in the full replacement update file are CH01A, CH03A, CH03B, and CH08A.

Field Update Input Sample

A file with updated name search field information contains only the key field information and the updated field information. Enter the key field information and any updated field information, and blank fill the fields not being updated.

In the following example, the GREETING NAME field (position 33) of segment CH08A is being changed from FRANK/PHYLIIS//MR to FRANK/PHILIP//MR. Submit segment CH08A.


Greeting Name CH08A Required if being updated.

Trailer Record Required.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH01A83535000000000000060 1000004352 111111111 ABLG01 CH03A83535000000000000060 1000004352DDA DDA-1 DDA CH03B83535000000000000060 DDA-1 YYYYYYYYY NN CH08A83535000000000000060 FRANK/PHYLIIS//MR.


TRLSBM 00700000000009000001358497219140401


AP Batch Load Exception ReportAn Authorization Processor program maintains record statistics according to segment ID. If any required AP batch information is missing when AP is finished processing, AP detects the error and rejects the maintenance for the segment ID where the error is found. AP writes the error to a report, and then processes the next cardholder in the AP batch file.

After each batch file runs, AP produces a report that records the statistics for that batch file, and sorts the report by the segment ID. The statistics are then written to the AP Batch Load Exception Report. These statistics include the number of records that are read, rejected, added, deleted, and maintained. This report shows any records that are rejected by AP and the reason for the rejection. Contact your Account Manager or Customer Service Representative to request a copy of the AP Batch Load Exception Report.

What segments do I resubmit if I have an error? If you originally submitted a batch to add cardholder records and an error occurs,

you are required to resubmit all of the segments for that cardholder. AP will not process any of the segments for a cardholder if an error occurred within that cardholder’s maintenance file.

If you originally submitted a batch to update cardholder records and an error occurs, you are required to resubmit only those segments that had the error.

Report Samples

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

HDLSBM 0029933399999999999Y CH08A83535000000000000060 FRANK/PHILIP//MR.


TRLSBM 00700000000009000001358497219140401

NOTE: If an add already exists for an AD01 record, and another identical add is submitted, the incoming add will be considered a duplicate and reported on the AP Batch Exception Report as such.


AP Batch Load Exception Report – Page 1The following report sample shows an attempt to add a series of cards. One of the cards, 3333010000000000039, in the AP Batch Maintenance file had an Invalid Member Number error in segment CH19A of the input file. An asterisk (*) displays in line 0000016 to indicate that an error occurred and the maintenance was rejected for the cardholder with that segment ID.

You are required to correct the Invalid Member Number error and re-submit the maintenance for card 3333010000000000039. In the example shown below, all of the segments for this cardholder would be resubmitted because the original batch was to add this cardholder’s records.

SEQ # MESSAGE/INPUT RECORD DESCRIPTION------- ---------------------------------------------------------------------APB-001 APBATCH2 INITIATED 99/09/04 10:01:33

APB-063 INVALID MEMBER NUMBER

0000001 CH01A53333010000000000039 1000000330 111111111 GBLG030000002 CH02A53333010000000000039 006969 49120000003 CH03A53333010000000000039 1000000330DDA DDA-ABC-020000004 CH03B53333010000000000039 CHECKING-2 YYYYYYYYY MY0000005 CH03A53333010000000000039 1000000330SAV SAV-ABC-010000006 CH03B53333010000000000039 SAVINGS-1 YYYYYYYYY IN0000007 CH03A53333010000000000039 1000000330OTH OTH-ABC-01

0000008 CH03B53333010000000000039 OTHER-1 YYYYYYYYY MN0000009 CH03A53333010000000000039 1000000330CRD CRD-ABC-010000010 CH03B53333010000000000039 CREDIT-1 YYYYYYYYY IN0000011 CH08A53333010000000000039 PUBLIC/JOHN/Q0000012 CH18A53333010000000000039 1600 PENNSYLVANIA AVE0000013 CH18B533330100000000000390000014 CH18C53333010000000000039 ANYCITY WI5432112340Y0000015 CH18D53333010000000000039

0000016 * CH19A53333010000000000039 ZZABC1 COOPAVS1 XB019490

The asterisk * indicates that an error was found.

0000017 CH19B53333010000000000039 0N19960808199610120000018 CH19A53333010000000000039 02ABC2 COOPAVS2 XB0194900000019 CH19B53333010000000000039 0N19960808199610120000020 CH19A53333010000000000039 03ABC3 COOPAVS3 XB0194900000021 CH19B53333010000000000039 0N19960808199610120000022 CH19A53333010000000000039 04ABC4 COOPAVS4 XB0194900000023 CH19B53333010000000000039 0N19960808199610120000024 CH01A53333010000000000040 1000000330 111111111 GBLG03

0000050 CH01A53333010000000000041 1000000330 111111111 GBLG03


AP Batch Load Exception Report – Page 2The AP Batch Load Exception Report shows statistics for the input records that were read, rejected, added, deleted, updated, and created. It also displays the total number of input records read and how many of those records were valid.

RECORDS READ REJECTED ADDED DELETED UPDATED CREATED

------ ------- -------- ----- ------- ------- --------UNKNOWN 0 0 0 0 0 0AD 01 0 0 0 0 0 0AD 02 0 0 0 0 0 0AD 03 0 0 0 0 0 0AD 04 0 0 0 0 0 0AD 05 0 0 0 0 0 0CH 01 3 1 2 0 0 0CH 02 3 1 2 0 0 0CH 03 24 8 16 0 0 0CH 04 0 0 0 0 0 0CH 05 0 0 0 0 0 0CH 06 0 0 0 0 0 0CH 07 0 0 0 0 0 0CH 08 3 1 2 0 0 0CH 09 0 0 0 0 0 0CH 10 0 0 0 0 0 0CH 11 0 0 0 0 0 0CH 12 0 0 0 0 0 0CH 13 0 0 0 0 0 0CH 14 0 0 0 0 0 0CH 15 0 0 0 0 0 0CH 16 0 0 0 0 0 0CH 17 0 0 0 0 0 0CH 18 12 4 8 0 0 0CH 19 24 8 16 0 0 0CH 20 3 1 2 0 0 0 Total number of Toral number of records read valid records

TOTAL DETAIL READ : 72 TOTAL DETAIL GOOD : 48


Multiple Product LinesOrganize the segments in your AP batch maintenance file in ascending numerical order according to record type. To prevent the duplication of cardholder or account information, enter and submit all of your institution’s delete segments first, followed by your institution’s add segments, and finally your institution’s update segments. Within the delete, add, and update segments, you must enter all of the cardholder segments in ascending numeric order, followed by the Scoring and Case Management segments in ascending numeric order, and finally the account detail segments in ascending numeric order.

Deleting Multiple ProductsThe following table identifies the segments you are required to submit if you are deleting account detail, cardholder, or fraud information for specific products. Submit only those segments for the product information your institution is deleting. Submit the required segments in the recommended order.

Segment

Segment Name Balance

Card Activa-tion CIMS

Fraud Scoring

and Case

Manage-ment

Name Searc

hAccount Holds

CH01A Card-holder X X X X X X

AD01A Account Detail

X X

AD01B Account Detail

X X

FR01A Scoring and Case Management

X

NOTE: If you are deleting address information using the Consolidated Address Verification System (AVS), you are required to submit only the CH1AA record. Do not include the AVS segments in an AP Batch Maintenance file with any AP Maintenance segments.


Adding Multiple ProductsThe following table identifies the segments you are required to submit if you are adding account detail, cardholder, or fraud information for a specific product. Be sure to include all of the required segments for all of the products used by your institution. For example, if your customer has account detail and name search, you would submit segments CH01A, CH03A, CH03B, CH08A, AD01A, AD01B, AD03A, and AD03B (in that order). Submit all of the required segments in the recommended order.

Segment Segment Name Bal


Fraud Scoring

and Case Manage-

ment

Name Searc

hAcct

Holds

CH01A Cardholder Information

X X X X X X

CH02A Track II X X X

CH03A Account Information

X X X X X

CH03B Account Information

X X X X X

CH04A Override Limit

CH06A Limit Hold

CH08A Greeting Name X X

CH09A Override Expire

CH014A Additional CardInfo

CH18A Card Management Group

X X

CH18B Card Management Group

X

CH18C Card Management Group

X X

CH18D Card Management Group

X X

CH19A Card Management Member

X X X

CH19B Card Management Member

X X X


*

CH22A Card Activation X X

CH22B Card Activation X X

AD01A Account Detail X X

AD01B Account Detail X X

AD02A Overdraft Detail

AD02B Overdraft Detail

AD03A Account Hold X

AD03B Account Hold X

AD06A Additional Hold

AD06B Additional Hold

FR01A Scoring and Case Management Information

X

FR02A Fraud Activity Information

Used for Fraud*

FR02B Fraud Activity Information

Used for Fraud*

FR03A Fraud Member Information

Used for Fraud*

FR03B Fraud Member Information

Used for Fraud*

* See the following AP batch layouts for information on when these fraud segments are required:

“FR02A - Fraud Activity Information” on page 202 “FR02B - Fraud Activity Information” on page 204 “FR03A - Fraud Member Information” on page 206 “FR03B - Fraud Member Information” on page 208

Segment Segment Name Bal


Fraud Scoring

and Case Manage-

ment

Name Searc

hAcct

Holds


Updating Multiple ProductsTwo options are available to your institution when you update cardholder or account information, you can send in a full replacement maintenance file or an updated field maintenance file to the AP system.

A full replacement file for AP batch maintenance contains all of the segments for the all of the products that were originally submitted when you added the cardholder. All of the field information is entered in the replacement file. Be sure to include all of the segments for all of the products.

An updated field file for AP batch maintenance contains only those segments with field information that is being changed and any required segment records. Enter only the field information that is being updated and blank fill the fields that are not being updated.

To update a segment with multiple segment records, you must submit all of the required segment records for the updated segment. For example, if you update and submit Account Information segment CH03A for a cardholder, you must submit Account Information segment CH03B. You can submit a full replacement for segments CH03A and CH03B with all of the field information entered including the updated field information. Or, you can submit segments CH03A and CH03B with the key field and updated field information entered. These segments have multiple segment records:

Account Information segments (CH03A and CH03B) Card Management Group segments (CH18A, CH18B, CH18C, CH18D) Card Management Member segments (CH19A and CH19B) Card Activation segments (CH22A and CH22B) Fraud Activity Information segments (FR02A and FR02B) Fraud Member Information segments (FR03A and FR03B)

To update an account number with multiple cardholders, first submit a delete for that account number (segments CH03A and CH03B) to eliminate any cardholders associated with the account. Next, submit an add (segments CH03A, CH03B, AD01A, and AD01B) to add back the new account number and all of the associated cardholders.

Key field information cannot be updated. You must submit the segment you want to change as a delete (FILE UPDATE CODE 6) for that field, and then submit that segment as an add (FILE UPDATE CODE 5) with the new key field information.

NOTE: If you are adding address information using the Consolidated Address Verification System (AVS), you are required to submit the CH1AA, CH1AB, CH1AC records. Do not submit the AVS segments in an AP Batch Maintenance file with any AP Maintenance segments.


See “AP Batch Record Layouts” on page 135 for description and usage of specific segments and fields discussed in this chapter.

NOTE: If you are updating address information using Consolidated Address Verification System (AVS), you are required to submit the CH1AA, CH1AB, CH1AC records. Do not submit the AVS segments in an AP Batch Maintenance file with any AP Maintenance segments.


4
Using Online Host Maintenance
This chapter describes procedures for performing AP Maintenance that originates from an online host. For additional information about the Format 8 and ISO messages, see the FIS ISO 8583 Processor Interface Specifications Manual and the Format 8 Interface Specifications Manual.

What is Online Host Maintenance?Online host maintenance is AP Maintenance sent online from the host instead of in an AP Batch Maintenance file to the Authorization Processor. FIS suggests using online host maintenance for exception processing only.

Submitting Online Host MaintenanceTo use an online host to submit AP Maintenance, your institution’s host generates AP Maintenance information and sends it online to FIS to update your institution’s AP files. FIS does not recommend using online host maintenance to perform ongoing AP Maintenance. Not all of the AP Batch Maintenance segments can be sent using the online host maintenance method. The AP Maintenance procedures you can perform using an online host include the emergency hot-carding of a cardholder, or individual new card maintenance.

NOTE: Online host maintenance is intended for hot card status changes or exception processing that requires immediate.

CAUTION: Any errors that occur while your institution is performing online host maintenance display on the Network Monitoring System and wait for operator action. FIS recommends using AP Batch Maintenance or online screen maintenance for performing ongoing maintenance to the Authorization Processor files. See Chapter 3 “Using Batch Main-tenance” of this manual, and the AP Maintenance User Manual for complete instructions.


Unlike AP Batch Maintenance, each online host maintenance transaction updates a single AP segment. You must send a separate host maintenance transaction for each AP segment you want to update. If you want to add a new card for an AP positive with account detail, you must send a minimum of five separate transactions for each of the batch segments. For example, segments CH01, CH02, CH03 (A and B handled in a single message), CH08, and AD01 must all be sent in a separate transaction.

The same rules used for AP Batch Maintenance apply to online host maintenance. The following segments are supported by online host maintenance.

Maintenance MessagesThe following Format 8 and ISO message formats are used to transmit your AP Maintenance online from your host. For additional information about the Format 8 and ISO messages, see the FIS ISO 8583 Processor Interface Specifications Manual and the Format 8 Interface Specifications Manual.

Using Spaces and AsterisksAP reads the input data and changes the affected fields using the following update rules:

For Alpha fields: All spaces = No change All asterisks = Clear out All other characters = Replace with the input data

For Numeric fields: All spaces = No change

Segment Number Segment Name

CH01 Cardholder Information

CH02 Track 2 Information

CH03 Account Information

CH04 Override Limit Information

CH06 Hold List Transaction Information

CH08 Name Information Transaction

AD01 Account Detail Information

AD02 Overdraft Information

AD03 Account Detail Hold List Transaction


All zeroes = Reset to zero All other numbers = Replace with the input data

ISO MessageOnline host maintenance uses the following FIS ISO messages generated by the issuer or the Connex™ System.

Card Issuer File Update Request for ISO (0382)The 0382 Card Issuer File Update Request message contains instructions to add, change, or delete a record on the AP files. The expected response would be the 0392 Card Issuer File Update Response.

Message StructureFollowing is the structure of the 0382 Card Issuer File Update Request message.

CAUTION: When the Authorization Processor uses the I51 and 0382 online messages to update the AP files, spaces and asterisks have special meaning. Use any spaces and asterisks with caution.

Bit No.

Data Element Name Format

Attri-butes

Sta-tus Notes

___ Message Type nP 4 M Always 0382.

___ Bit Map, Primary b 64 M

001 Bit Map, Secondary b 64 M

007 Transmission Date and Time

MMDDhhmmss

nP 10 M

011 System Trace Audit Number

nP 6 M

053 Security Related Control Information

nP 16 C Required if using dual active encryption keys and message authentication (MACing) is being performed.

062 Issuer Transport Data

LLLVAR ans..100

O This data is echoed in the response. The length must be 26 or less.


064 Message Authentication Code

b 64 C This data element is required when MACing messages and no data element from 065-128 is present in the message.

091 File Update Code an 1 M Supports the following codes.1 = Add2 = Update3 = Delete

096 Message Security Code

b 64 M 8-byte character password assigned by the processor.

101 File Name LLVAR ans..17 M ValuesCHnn = Cardholder file maintenanceADnn = Account detail file maintenancenn = Segment ID being maintained

113 Authorizing Agent Institution ID Code

LLLVAR n..011 M Institution ID code of the institution that issued the card being maintained.

124 Info, Text LLLVAR ans..255

M Cardholder or account file maintenance data. See “Section 5. Data Element Definitions” of the FIS ISO 8583 PI Specifications Manual for layout information.

128 Message Authentication Code

b 64 C This data element is required when MACing messages and at least one of the data elements from 065-127 is present in the message.

Bit No.

Data Element Name Format

Attri-butes

Sta-tus Notes


Format 8 MessagesThe following 15x messages are used to maintain AP cardholder and account information.

Maintenance Request Message for Format 8 (I51)The I51 AP Maintenance Request message adds, deletes, or updates a segment of the Cardholder File or Account Detail File. The issuer generates the message and expects an I52 or I53 reply or response.

Maintenance Reply Accept Message for Format 8 (I52)The I52 AP Maintenance Reply Accept message acknowledges that the Connex™ System successfully processed the I51 request. Information for the I52 is copied from the I51 request. The expected response is a protocol acknowledgment from the issuer.

Maintenance Reply Reject Message for Format 8 (I53)The I53 AP Maintenance Reply Reject message indicates that the Connex System did not process the I51 request and maintenance was not performed. Information for the I53 is copied from the I51 request. The expected response is a protocol acknowledgment from the issuer.

Each file consists of one or more record segments. The I5x messages add, delete, or update one of the following Cardholder or Account Detail Record segments.

Segment ID Segment Description

Cardholder Record

01 Card Information

02 Track 2

03 Account Information

04 Override List

06 Hold List

08 Name Information

Account Detail Record

01 Account Detail

02 Overdraft Information

03 Account Hold Information


Message FormatFollowing is the format for the I5x AP Maintenance message.

ISO Number and Field Name

Pos.

Len. Status

Attri-butes Description/Usage

1 Message Code 1 4 Required Alpha-numeric

ValuesI51 = RequestI52 = Reply AcceptI53 = Reply Reject

2 Format Code 5 1 Required Numeric Value = 8

3 Date 6 6 Required Numeric Format = YYMMDD

4 Time 12 6 Required Numeric Format = HHMMSS

5 Processor Value 18 2 Required Alpha-numeric

Assigned by the system technical staff.

100 AP Response Code

20 2 Required Alpha-numeric

Code returned by AP Maintenance servers. Treated as filler field on request.

101 Update Code 22 1 Required Alpha-numeric

Indicates the type of maintenance being performed.

102 Record Name 23 2 Required Alpha-numeric

ValuesCH = Cardholder RecordAD = Account Detail Record

103 Segment ID 25 4 Required Alpha-numeric

Value for Cardholder Record or Account Detail segment is entered.

104 Originating Institution ID


Institution Identification Code of the endpoint that originated this transaction.

105 File Record Length


Length of the record that follows this field.

NOTE: The message formats vary at this point depending on the Record Name and Segment ID fields. The format for each type of segment is presented on the following pages, starting at the twelfth field in the message after the “File Record Length” field.

/b/b/b


Cardholder Record

Card Information


Pos.

Len. Status


23 Primary Account Number

42 19 Required Numeric Account number encoded on Track 2 of the access card.

92 Plastic Number 61 5 Optional Alpha-numeric

Member number or plastic number from Track 2 Discretionary Data.

106 Card Issuer Institution ID


Identification Code of the institution that issued the card.

107 Status 76 2 Optional Alpha-numeric

Code indicating the status of a cardholder's card.

108 Card Access Indicates the cardholder's ability to perform a type of transaction. Each type of card access (listed below) is one byte long.Note: At least one card access is required for all Add Codes 5.

108a Withdrawals 78 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108b Deposits 79 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108c Inquiries 80 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108d Payments To 81 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108e Payments From 82 1 Optional Alpha Values::Y = Add card accessN = Delete card access


108f Transfers To 83 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108g Transfers From 84 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108h Purchases 85 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108I Third Party Payment

86 1 Optional Alpha Values:Y = Add card accessN = Delete card access

108j Future Access Types

87 7 Optional Alpha Field is for future use.

109 Pin-Fail-Reset 94 1 Required Alpha-numeric

Indicate whether to reset the PIN fail count to prevent the account from being blocked when the value exceeds the limit. Values:Y = Reset PIN fail count to zero.Blank = No change.

110 Limit Group ID 95 6 Required Alpha-numeric

Limit group for this cardholder.

170 Fee Group 101 6 Optional Alpha-numeric

Fees to be charged to the cardholder. Note: Leave this field blank.

171 Card Activation 107 1 Required Alpha-numeric

Values:Blank = Card is active (Default)Y = Card is activeN = Card is not active


Pos.

Len. Status



Track 2


Pos.

Len. Status




92 Plastic Number 61 5 Required Alpha-numeric


110 PIN Authentication Flag

66 2 Conditional Alpha-numeric

Determine where the PIN offset resides. Values:00 = AP Holds the Offset01 = AP Does Not Hold Offset99 = PIN Offset Flagged ChangeNote: This field is required if you are adding this segment. Enter a value for this field whether you use the PIN-AUTH-VALUE or not.

111 PIN Authentication Value

68 16 Conditional Value used for PIN checking.Note: This field is required if the PIN Authentication Flag is 00 or if your institution uses CIMS for ordering cards.

112 Track 2 Date 84 4 Optional Numeric Card’s expiration date or the issued date using the YYMM format.Note: Required if AP card activation expiration date matching is used.


Account InformationAt least one account access is required for Add Code 5.


Pos.

Len. Status






113 Account Institution ID


Identification Code of the institution where the account is located.

114 Account Type 76 4 Required Alpha-numeric

Institution-assigned identifier that corresponds to the institution's host. For example, SNOW might correspond to the institution's Super-Now accounts.

115 Account Number


Number assigned to this account by the institution.

28 Account Qualifier #1


User-defined qualifier assigned by the system technical staff.

116 Open Account Relationship (OAR) Select Type

111 3 Conditional Value used to select accounts for the OAR display. Required for Update Code 5. DDA = CheckingSAV = SavingsCRD = CreditOTH = Other

117 Account Description


Description of the account. For example, VACATION FUND is used for OAR purposes to help the cardholder identify their accounts.


118 Account Access

Required for Add

Indicates the cardholder's ability to perform a type of transaction. Each type of account access (listed below) is one byte long.

118a With-drawals 134 1 Required Alpha Values:Y = Add account accessN = Delete account access

118b Deposits 135 1 Required Alpha Values:Y = Add account accessN = Delete account access

118c Inquiries 136 1 Required Alpha Values:Y = Add account accessN = Delete account access

118d Payments To 137 1 Required Alpha Values:Y = Add account accessN = Delete account access

118e Payments From

138 1 Required Alpha Values:Y = Add account accessN = Delete account access

118f Transfers To 139 1 Required Alpha Values:Y = Add account accessN = Delete account access

118g Transfers From 140 1 Required Alpha Values:Y = Add account accessN = Delete account access

118h Purchases 141 1 Required Alpha Values:Y = Add account accessN = Delete account access

118i Third Party Payment

142 1 Required Alpha Values:Y = Add account accessN = Delete account access


Pos.

Len. Status



Override


143 1 Required Alpha Field is for future use.

119 Primary Account Indicator

150 1 Required Alpha Values:Y = PrimaryN = Not Primary

120 Funding Account Indicator

151 1 Required Alpha Values:Y = FundingN = Not Funding

ISO Number and Field Name Pos. Len. Status




92 Plastic Number



121 Limit Type 66 6 Required Alpha-numeric

Limit being used, such as deposit, withdrawal, or transfer.

122 Limit Amount 72 10 Required Alpha-numeric

Overrides the cardholder's limit group amount.

123 Limit Uses 82 5 Required Numeric Overrides the cardholder's uses limit.

124 Increment Amount

87 10 Optional Alpha-numeric

Override increment amount to be used for this limit.

125 Minimum Amount


Override minimum amount.

125 Percent Deposit Available

10 3 Optional Numeric Percentage of deposits available for withdrawal.


Pos.

Len. Status



Hold List


Pos.

Len. Status



42 19 Required Numeric

Account number encoded on Track 2 of the access card.

92 Plastic Number



127 Match Data

Required The data that is used to match the hold.Pos. Description1-12 Last 12 digits of PAN13-27 Transaction ID28 Pre-authorization ID29-30 Transaction Code31-36 AP Approval Code

127a Primary Account Number


Used to match the hold with the settled transaction. Value = Last 12 non-blank characters of PANNote: You cannot update this key field.

127b Card Acceptor ID

78 15 Required Numeric

The first 8 digits of the transaction’s terminal reference number used as an ID for the party accepting the card and presenting transaction data to an acquirer.Note: You cannot update this key field.

127c Pre-Auth. Indicator

93 1 Required Alpha Match the hold with the settled transaction. Values:P = Pre-authorizedV = Visa Check™M = Debit MasterCard®Note: You cannot update this key field.

__ Filler 94 2 Required Alpha-numeric

Value = 2 spaces

127d Auth. Number


Authorization number of the transaction that caused the hold.


Value: 8 spaces


Name Information

128 Limit ID 110 6 Required Alpha-numeric

Identifies the limit being used.

129 Expiration Time Indicator


ValuesY = Reset the Expiration Time.N = Do not reset Expiration Time.


Value = 1 space

ISO Number and Field Name Pos.

Len. Status






130 Greeting Name 66 20 Required Alpha-numeric

Name displayed on the administrative terminal inquiry.


Pos.

Len. Status



Account Detail Records

Account Detail






114 Account Type 52 4 Required Alpha-numeric


115 Account Number



152 Ledger Balance


Amount used to store the ledger balance for an account.

153 Available Balance


Amount available for an account.

154 Credit Line Amount


Credit line amount associated with an account.

155 Account Status


Code indicating the status of an account.


ISO Number and Name Field Pos.

Len. Status


118 Account Access


Indicates the cardholder's ability to perform a type of transaction. Each type of account access (listed below) is one byte long. Note: One account access is required for a File Update Code of 5 for an Add.

118a With-drawals


Values:Y = Add account access N = Delete account access

118b Deposits 117 1 Required Alpha-numeric

Values:Y = Add account accessN = Delete account access

118c Inquiries 118 1 Required Alpha-numeric

Values:Y = Add Account accessN = Delete account access

118d Payments To



118e Payments From



118f Transfers To



118g Transfers From



118h Purchases 123 1 Required Alpha-numeric



Overdraft Information

118i Third Party Payment





Field is for future use.

156 Overdraft Amount


Amount the account is allowed to overdraw before going to an overdraft account or rejecting the transaction.

ISO Number and Field Name Pos.

Len. Status





114 Account Type



115 Account Number



157 Overdraft Institution ID

84 10 Required Identification Code of the institution where the overdraft account resides.

114 Account Type

94 4 Required Type of overdraft account assigned by the institution to correspond to the host's files.

115 Account Number

98 28 Required Account number of the overdraft account.

ISO Number and Name Field Pos.

Len. Status



Account Hold InformationYou can only update a Hold List transaction using on-line maintenance.



5 Fi-ID 9 10 Required Alpha-numeric

This key field is the routing and transit number of the institution issuing the card. Identifies the account holding financial institution.Value = 1NNNNNNNNCNote: You cannot update this key field.

6 Acct-Type 19 4 Required Alpha-numeric

Specify a valid account type The service line identifier. This number must match the ACCT-TYPE in CH03A. Samples include:DDA = CheckingSAV = SavingsCRD = Line of CreditNote: You cannot update this key field.

7 Acct-No 23 28 Required Alpha-numeric

This identifier is the cardholder’s account number and it must match the ACCT-NO field in CH03A. For a CU, this is the base account number with the account number suffix.Note: You cannot update this key field.

8 Primary-Account-Number


The last 12 digits of the PAN. Matches the hold with the settled transaction.


9 Card-Acceptor-ID



10 Preauth-Indicator


Match the hold with the settled transaction. Values:P = Pre-authorizedV = Visa Check™M = Debit MasterCard®Note: You cannot update this key field.

11 Terminal-Day


If your PREAUTH-INDICATOR is V or M, enter the number for the month’s day.Values = 01, 02, ...., 31Note: You cannot update this key field.




5
Using Balance Refresh
This chapter describes how to keep a cardholder’s balance information current and accurate using Balance Refresh.

What is Balance Refresh?The balance refresh process is used to update your cardholder’s account balance information in the AP Balance File. During this process, a host’s application program writes the balance information to a new host file using financial transactions from AP and an in-house system as input. This input file is submitted and current account balance information is applied to the cardholder’s existing account detail file.

To calculate a cardholder’s new available account balances, AP takes data from the Balance Refresh File and applies any of the unposted amounts to the new account balances in the cardholder’s Account Detail File. When a cardholder makes their first request of the business day or when a terminal operator inquires into the cardholder’s AP records, the cardholder’s current balance is available.

Balance Refresh Flow

NOTE: A Balance Refresh File is not a full replacement file. FIS stores only the most recent balance information received for the designated account. When you close an account, you must send FIS a zero bal-ance ($00.00) for that account as the final balance or AP will use the customer’s last balance to authorize the next transaction.

Balancesfrom the Host

BalanceFile

AP BalanceUpdate File


Balance Refresh and End-Of-DayYour institution’s AP end-of-day is set up to coincide with your settlement end-of-day to ensure that AP maintains all transactions that occur after your posting file is created. If your institution is scheduled to send your balance refresh file Monday through Friday between 9:00 p.m. and midnight, your AP end-of-day is 3:00 p.m. This is based on the assumption that your institution always posts that day’s transactions before sending FIS a new Balance Refresh file.

Your institution’s AP end-of-day should occur before every expected Balance Refresh File. The AP end-of-day flag remains on if a balance refresh is not submitted during the week.

If your institution sends two balance refresh files during a day, AP suspends the unposted transactions that occurred between the first and second file. The second balance refresh file will be applied to the cardholder accounts, but the transactions done between the two balance refresh files are not used.

As soon as the Balance Refresh File is received and logged, the AP end-of-day flag is turned off, releasing the unposted items. These unposted transactions are immediately subtracted from the cardholder’s new balance. When subsequent transactions occur, the newly calculated balance is used to authorize those transactions. AP end-of-day should always occur before each expected Balance Refresh File.


Balance Refresh Record LayoutTo ensure the integrity of the files, you are required to submit a header and trailer record with your Balance Refresh File. If you are sending multiple files for multiple institutions, use a header and trailer record to separate each file. Fill any fields that do not have data with blank spaces. The first record of the maintenance is a header that contains the logical name used to find the balance file.

Hash totals are calculated by taking the sum of the absolute values of all available balances. If that sum is greater than 10 position in length, all of the left most positions are truncated.

You can submit your initial Balance Refresh file to FIS on tape. Tape block size is limited to 20,480 bytes. A multi volume input is also supported. You can also submit your production balance refresh file using RJE, NJE, FTP, or CONNECT:Direct™. Use the JCL provided by FIS to wrap around the balance files you submit.

Header RecordThe header record is the Balance Refresh File.



1 INST-ID 1 10 Required Numeric Routing and Transit number.Value = 1NNNNNNNNCN = Routing and Transit NumberC = Check Digit

2 APPLIC-ID 11 4 Required Alpha-numeric

Value = ALLIf a separate file will be sent for each Service Line, this value must reflect that Service Line ID. If for COOP, value = COOP.

3 ACCT-NO 15 28 Required Alpha-numeric

Value = Header

4 NBR-RECORDS-TOTAL


Total number of detail records for this institution.

5 NBR-RECORDS-DDA


Total number of demand deposit detail records for this institution.


Input Sample

6 NBR-RECORDS-SAV


Total number of savings detail records for this institution.

7 NBR-RECORDS-CRED


Total number of credit detail records for this institution.

8 DATE-JULIAN

81 5 Required Numeric The file date in Julian format.Value = YYDDDYY = Year, DDD = Julian Day of the Year

9 HASH-FLAG


Value = Yes

10 CONTROL-NBR

87 3 Required Numeric This key field is the file sequence number. Value = 001 – 999Note: If the control override parameter is set to N, the control number must be incremented by 1 for each file transmission. If the control override parameter is set to U, the control number can be incremented by more than 1 for each file transmission.

11 FILLER 90 11 Required Alpha-numeric

Ensure 80 byte record.Value = Spaces



1 2 3 4 5 6 7 8 91234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567

1NNNNNNNNCALL HEADER 1111111111122222222233333333344444444499215Y 009


Detail RecordThe detail record for a Balance Refresh File.

Field Number and Name Pos.

Len. Status


1 INST-ID 1 10 Required Numeric Routing and Transit number.Value = 1NNNNNNNNCN = Routing and Transit NumberC = Check Digit

2 ACCT-TYPE


This file identifier is used if the clients requires separate cardholder files for each account service line. This field should be blank if the institution does not use balances. Example ValuesDDA = Checking Account (default)SAV = Savings AccountCRD = Line of CreditOVD = Overdraft AccountOTH = Other Account Spaces = No Account Detail exists.Blank = Institution does not use balances.Note: FIS recommends that you set up an overdraft account for a cardholder rather than include an overdraft amount in the cardholder’s available balance. The transaction is denied if the account isn’t found.


The cardholder’s account number assigned by the financial institution identifying the updated account. If alpha values are sent, they are entered as upper case.For CU, use the base account number plus the account suffix.

4 AVAIL-BAL

43 10 Required Numeric Available balance for this account. Value = S9999999V99


4a 43 1 Required Alpha Indicate the available balance as a positive or negative balance.S = sign (zero, +, -, or space)A positive balance is indicated by a zero, +, or space.Note: Zero is the preferred method to indicate a positive balance.For example, 0100000000 or +100000000 = positive 1,000,000.00

4b 44 9 Required Alpha-numeric

Available balance for this account. Value = 9999999V999 = Numeric ValueV = Implied Decimal

5 LED-BAL-1

53 10 Required Numeric Ledger balance for this account.Value = S9999999V99

5a 53 1 Alpha-numeric

Indicate the ledger balance as positive or negative.S = sign (zero, +, -, or space)A positive balance is indicated by a zero, +, or space.Note: Zero is the preferred method to indicate a positive balance.For example, 0100000000 or +100000000 = positive 1,000,000.00


Ledger balance for this account.Value = 9999999V99 9 = Numeric ValueV = Implied Decimal Point

6 CREDIT-LINE-AMNT-1

63 10 Required Numeric Credit line amount for this account.Value = S9999999V99


Len. Status



6a 63 1 Required Alpha-numeric

Indicate the credit line amount a as positive or negative balance.S = sign (zero, +, -, or space)A positive balance is indicated by a zero, +, or space.Note: Zero is the preferred method to indicate a positive balance.For example, 0100000000 or +100000000 = positive 1,000,000.00


Credit line amount for this account.Value = 9999999V99 9 = Numeric ValueV = Implied Decimal Point

7 ACCT-STATUS


Value = 2 SpacesYou can use ** to clear an existing status.

8 ACCT-ACCESS


Value = 9 Spaces

9 FUTURE 84 7 Optional Alpha-numeric

Value = 7 Spaces

10 OD-AMNT

91 10 Optional Numeric Amount the account can be overdrawn before going to the overdraft account or rejecting the withdrawal transaction.Value = S9999999V99

10a 91 1 Optional Alpha-numeric

Indicate the overdraft amount as a positive or negative balance.S = sign (zero, +, -, or space)A positive balance is indicated by a zero, +, or space.Note: Zero is the preferred method to indicate a positive balance.For example, 0100000000 or +100000000 = positive 1,000,000.00


Len. Status



Input Sample

10b 92 9 Optional Alpha-numeric

Amount the account can be overdrawn before going to the overdraft account or rejecting the withdrawal transaction.Value = 9999999V99 9 = Numeric ValueV = Implied Decimal Point


Len. Status


1 2 3 4 5 6 7 8 9 01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123

135764812COTH 555666777888999000 +100000000+100000000+100000000 +100000000


Trailer RecordThe trailer record for a Balance Refresh File.

Input Sample



1 INST-ID 1 10 Required Numeric Marker for End-of-File (EOF)Value = all 9s

2 APPLIC-ID 11 4 Required Numeric Marker for EOFValue = all 9s

3 ACCT-NO 15 28 Required Numeric Marker for EOFValue = all 9s

4 NBR-RECORDS-TOTAL

43 11 Required Numeric Total number of detail records for this institution.

5 HASH-TOTAL

54 10 Required Numeric The sum of the absolute values of all available balances, including cents. If that sum is greater than 10 position in length, all left-most positions greater than 10 are truncated.

6 CONTROL-NBR

64 3 Required Numeric File sequence number that is incremented by 1 with each file transmission. When you reach 999 start over with 001.Must match the control number in the header and footer.Values = 001 to 999

7 DATE-RECVD


Value = 5 Spaces

8 TIME-RECVD


Value = 6 Spaces

9 FILLER 78 23 Required Alpha-numeric

Ensure 80-byte record.Value = Spaces

1 2 3 4 5 6 7 8 9 01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123

999999999 9999 9999999999999999999999999999100000000000999215


Sending Records Using RJE or NJEIf a you send FIS a 100-byte record using RJE or NJE, you must divide the 100-byte record into two 80-byte records. The first segment of the 80-byte record is 72 bytes in length and the second segment is 28 bytes in length. If there is no data for the second segment of the first record or the first and second segments of the second record, blank fill those segments.

80-Byte Record

Samples

To send a 100-byte record as 80-byte punch data, break up the 100-byte record into two 80-byte records.

Record 1, Input Segment 1

NOTE: If your institution sends balance files to FIS using FTP or a CON-NECT:Direct™ file transmission, send a standard 100-byte record.


Len.

Short-Name Description/Usage

1 INPUT-RECORD-NUMBER

1 3 REC-NUMBER

Actual record number of the input record (reference only).Values = 001 – 999When you reach 999, reset the number of records to 001.

2 INPUT-RECORD-SEQUENCE-NUMBER

4 2 REC-SEQNUM

Number of the segment of the input record.

3 INPUT-RECORD-DATA-LENGTH

6 2 REC-LENGTH

Length of the data to follow.Values72 = First Segment28 = Second Segment

4 END-OF-RECORD-INDICATOR

8 1 END-OF-DATA

Indicates if this segment is the last segment.ValuesN = Not Last SegmentY = Last Segment

5 INPUT-RECORD-DATA-AREA

9 72 DATA-AREA-1orDATA-AREA-2

The actual balance file information.ValuesDATA-AREA-1 = First SegmentDATA-AREA-2 = Second Segment





001 01 72 N ((72 bytes of data))

001 02 28 Y ((28 bytes of data)) //// ((44 blank bytes))

002 01 72 N ((72 bytes of data))

002 02 28 Y ((28 bytes of data)) //// ((44 blank bytes))


6
Using Match and Hold
This chapter describes the optional AP match and hold feature available to Visa Check™ and Debit MasterCard® customers.

What is Match and Hold?Match and hold is an optional feature of AP that places a hold against your cardholder’s account when a point-of-sale (POS), Debit MasterCard®, or Visa Check™ debit transaction is pre-authorized online but has not yet settled. The amount of the transaction is applied as a memo post against the cardholder’s account balance until the transaction item is settled or expired. AP produces the AP Hold File that contains any holds against your cardholder’s accounts and uses this file information to approve or deny transactions.

If a matching force post settled transaction is found, the hold against the cardholder’s account is removed for that transaction. Holds are matched and removed from the AP Hold File when transactions are settled or expired. FIS standard product expires all unmatched holds after three calendar days.

FIS recommends using the optional match and hold feature for the following reasons.

You can use the optional AP Hold File to ensure that a cardholder has sufficient funds for teller activity and other transactions that are not routed through FIS.

You can use the information in the hold file or the AP Hold Report to determine if your institution’s holds have been matched.

NOTE: Because all holds are conditional, some are never matched. The set-tled items may not be processed or delivered for several days after the authorization message is sent and the holds for those transac-tions are never matched. Or, if the sale does not occur, the settled item is never generated and the hold for that transaction is never matched.


How does AP match a hold?AP matches holds based on conditions set up in your parameter file. The conditions for matching the holds vary depending on whether the transaction is a point-of-sale (POS) pre-authorization, Debit MasterCard®, or Visa Check™. The match and hold process will cycle through all of the holds until either a match is found or until all of the holds are checked and no match is found.

If the conditions to process the hold are met, the matching process is complete and the remaining steps are not performed. The AP system begins the match process for the next hold.

If no match is found, the hold remains against the account until it is expired. No match is performed because this POS pre-authorization type is only processed

after the hold has been expired.

Match and Hold CriteriaFIS uses the following transaction data elements to match hold transactions. A match on the PAN (card number) must be made to begin the match process.

Match Hold Authorization Network Card PIN Hold Data Elements

Expiration Hold Regional Network

ATMVisa Check™ Master-Card® Debit

Yes Minutes Last 12 digits of the PAN (card number)

Authorization Number Terminal Reference

Number


POS Pre-Authorization

Regional Network

ATMVisa Check Master-Card® Debit

Yes Minutes Last 12 digits of the PAN (card number)

Authorization Number Terminal Reference

Number

Authorization Visa® Card Visa Check

No 3 Calendar Days

Last 12 digits of the PAN (card number)

Visa Transaction Identifier (if present)

Authorization Number Acquirer Day, actual

Transaction Amount or Percent Deviation, and actual Terminal Date

Authorization Master- Card®

Master-Card Debit

No 3 Calendar Days

Last 12 digits of the PAN (card number)

Authorization Number Acquirer Day, actual

Transaction Amount or Percent Deviation, and actual Terminal Reference Number

Match Hold Authorization Network Card PIN Hold Data Elements


Match and Hold for Pre-AuthorizationAfter a match on the PAN is made, the diagram shows the match criteria used to match a hold for a Pre-Authorization transaction.

Figure 1 Match and Hold for Pre-Authorization

Is the Authorization Numberpresent in the transaction?

If an Authorization Numbermatch occurs, process the hold.

If no match occurs, is theTerminal Reference Numberpresent in the transaction?

If a Terminal Reference Numbermatch occurs, process the hold.

If no match occurs,continue with the next hold.

Yes

Yes

No

No


Match and Hold for Debit MasterCard®After a match on the PAN is made, the diagram shows the match criteria used to match a hold for a Debit MasterCard® transaction.

Figure 2 Match and Hold for Debit MasterCard® Transaction

Is the Authorization Numberpresent in the transaction?


If no match occurs, are the

Terminal ReferenceNumber present in the transaction?

Acquirer Day, the exact amount ofthe Percent Deviation or TransactionAmount, and

If the

Terminal ReferenceNumber all match, process the hold.

Acquirer Day, the exact amountof the Percent Deviation or TransactionAmount, and the


Yes

Yes

No

No


Match and Hold for Visa Check™After a match on the PAN is made, the diagram shows the match criteria used to match a hold for a Visa Check™ transaction.

Figure 3 Match and Hold for Visa Check™ Transaction

instruct=account-hold,odallow=y,balance=avail,account=fr, chktype=ALL,length=(4320,4320),odincr=0.01,preauth=V,instruct=match-account-hold,account=fr,balance=avail,chktype=forced, odallow=y,odincr=0.01,

Is the Visa TransactionIdentifier present in thetransaction?

If no match occurs, isthe Authorization Numberpresent in the transaction?

If a Visa Transaction Identifiermatch occurs, process the hold.



If no match occurs, are the

Terminal Reference Numberpresent in the transaction?

Acquirer Day, the exact amountof the Percent Deviation orTransaction Amount, and

If the

Terminal ReferenceNumber all match, process the hold.

Acquirer Day, the exact amountof the Percent Deviation or TransactionAmount, and the

Yes

Yes

Yes

No

No

No


Match and Hold OptionsThe following match and hold options are available to the processing customers at FIS.

FIS Does Match and Hold For AP CompleteFIS places a hold on an authorization transaction (100 message) and then releases the hold when the settled transaction (220 message) is received and the amount is posted to the cardholder’s account. (An expired hold is not posted to the cardholder’s account.) This hold on your cardholder’s account is for a predetermined amount that is either a percentage of or equal to the amount of the transaction.

If FIS performs the match and hold for your cardholder’s pre-authorized debit transactions, you are required to do the following.

Use the FIS Authorization Processor to authorize cardholder transactions.

Determine whether to use a percentage of the transaction or the total amount of the transaction to hold against the cardholder’s account.

Maintain a balance file for your cardholders.

FIS Does Match and Hold For AP CooperativeFIS places a hold on an authorization transaction (100 message) and then releases the hold when the settled transaction (220 message) is received and the amount is posted to the cardholder’s account. (An expired hold is not posted to the cardholder’s account.) This hold on your cardholder’s account is for a predetermined amount that is either a percentage of or equal to the amount of the transaction.

If FIS performs the match and hold for your cardholder’s pre-authorized debit transactions, you are required to do the following.

Use the FIS Authorization Processor to authorize cardholder transactions.

Determine whether to use a percentage of the transaction or the total amount of the transaction to hold against the cardholder’s account.

Maintain a balance file for your cardholders.

Receive balance information in the online message.

After an authorization is sent through AP and logged, it is passed online to your host for approval. The host then memo posts the authorization to the cardholders account for that day. When transactions come to FIS for approval, AP performs the necessary edits and logs the authorization or settled item to the appropriate file. The item then flows to the host for authorization or posting of the settled items.


Your Host Performs Match and HoldYour host places a hold against your cardholder’s available account balance from an authorization transaction (100 message), and then releases the hold when the settled item (220 message) is received and the amount is posted to the account or the hold is expired.

Your institution or your vendor is responsible for determining the criteria you use to match holds and when you expire holds. FIS is only responsible for sending the items online. FIS recommends that you or your vendor use the same criteria currently used by FIS to match holds.

Your host is also responsible for matching the authorization transaction to the settled item. The authorization or the advice of an authorization (when FIS stands in for the host) is sent online to the host. The settled items are sent online to your host for posting to the cardholder’s account. Your host is responsible for tracking and matching the authorizations to determine if they are matched to settled items or are expired.

No Match and HoldYour institution is at financial risk if you decide not to manage outstanding pre-authorizations. Because you are not required to maintain balances or account detail file information, unsettled funds are not reflected in your cardholder account balances. Under these circumstances, a cardholder is able to close an account or cash a check without settled items being posted to that account. FIS does not recommend using this option.

Does Match and Hold affect the cardholder’s balance?Holds have a direct relationship to the cardholder’s account balance. A hold always reads the balance information in the cardholder’s account detail file. That way, if a cardholder has more than one card tied to their account, AP always checks the account’s balance before authorizing a transaction of any amount.

The cardholder’s account balance is only decremented when the hold item is a settled transaction (220 message). The cardholder’s account balance is not decremented by the approved POS, Visa Check™, or Debit MasterCard® authorization transaction (100 message). If a cardholder performs a balance inquiry at an ATM, the hold is not reflected in the available balance or the ledger balance. AP does however take the hold into consideration before approving that transaction.

NOTE: AP tracks transactions for daily usage limits but does not hold or match any settled transactions. AP always checks your cardholder’s daily limit before authorizing a transaction.


If a cardholder has an available balance of $600 with a $500 hold against that account and the cardholder then attempts to make a $500 purchase, AP considers the $500 hold and denies the $500 purchase. However, the cardholder does not see their balance decremented by that $500 hold.

Duplicating HoldsTo prevent a hold from being duplicated, your host should not post any holds to a cardholder’s account until after the balance file has been sent to FIS. Because AP considers the amount of any outstanding holds when approving a transaction, you should not send FIS a cardholder balance that has already been reduced by the amount of a hold.

If you post the hold information from the AP Hold File to a cardholder’s balance and send that balance file to FIS, the amount of the hold is deducted twice, or duplicated, when AP attempts to authorize the hold. Your institution should only post authorization information from the AP Hold File after sending FIS a balance file.

AP Hold FileThe optional AP Hold File provides your institution with a complete list of all POS, Visa Check™, and Debit MasterCard® holds that are authorized but have not been settled. The hold file is only available if you are AP Complete or AP Cooperative, and FIS is performing the match and hold for your institution.

The AP Hold file is created daily and contains all outstanding or unexpired holds at the specified cutoff time. Although the balance seen by your cardholder does not reflect any of the outstanding holds, AP uses the hold information when determining if it will authorize the transaction. Holds are removed from the file when they are matched and settled or when the hold is expired from the file.

Raw Data FileThe raw data file provides you with any daily outstanding authorization data. If you or a software vendor are performing the match and hold for your institution, you receive the authorization data in an online host message. To extract information from the raw data file, use the “Detail Record” on page 113. Your institution can create reports or integrate the data into your teller system to indicate when a hold has been placed on an account.

NOTE: To prevent a hold from being duplicated or applied twice to a card-holder’s available balance, post the hold information from the AP Hold File after you have sent FIS your institution’s balance file.


Raw Data FileBelow is an example of a raw data file. Extract the data for your institution’s internal use.

Raw Data File with PANBelow is an example of a raw data file that includes the cardholder’s PAN. Extract the data for your institution’s internal use.

101 314970664 31497066499090312551094101SAMPLE SAVINGS BANK FSB 5200SAMPLESAVINGSBANK ACCOUNT P 999999999HLDATM TRANS 990903990903 1 0000001 6253149706640060270447 00000035009909022003555744390170252493 1 1 0000001 700 39017025249392450000 P 134213 0000001 6253149706642136041207 00000100009909022027244366784250039004 1 0000002 700 784250039004000741 P 136316 0000002 6253149706643112017706 00000035009909021742595744390180329794 1 1 0000003 700 39018032979492450000 P 123066 0000003 6253149706643175013261 00000035009909022007055744390180131679 1 1 0000004 700 39018013167992450000 P 134462 0000004 6253149706643800451902 00000050009909021834235744390180329950 1 1 0000005 700 390180329950065870 P 136942 0000005 82000000100157485330000000025500000000000000 314970664 0000001 5200SAMPLESAVINGS ACCOUNT V 999999999HLDATM TRANS 990903990903 1 0000002 6253149706640130160902 00000001009909042043164366784250004842 1 0000001 700 784250004842099245061921584V01187128 0000001 6253149706640130208602 00000014669909032256074366784250004404 1 0000002 700 784250004412089244141635597V31120902 0000002 6253149706640130231603 00000014299909051434074366784250004545 1 0000003 700 784250004545089245704444573V02126934 0000003 6253149706640130257700 00000037709909050040324366784250009338 1 0000004 700 784250009346089245204295204V02194471 0000004

Figure 4 Raw Data File Sample

. 101 121135045 12113504599090313441094101THE SAMPLE BANK THE SAMPLE BANK 5200THESAMPLEBANK ACCOUNT V 888888888HLDATM TRANS 990903990903 1 0000001 62512113504500001009035 0000001187990904204927 1 0000001 700 810018243113089245065645982V01185012 0000001 62512113504500001070794 0000007506990904125256 1 0000002 700 810014712491089244643721073V01105340 0000002 62512113504500001077508 0000004737990904194014 1 0000003 700 810018242800089245024118454V01478621 0000003 62512113504500001078252 0000007962990904171344 1 0000004 700 81001829448892444346 V01151429 0000004 62512113504500001201591 0000001543990905150549 1 0000005 700 810028968139009245723469243V02130634 0000005 62512113504500001201591 0000002885990905120750 1 0000006 700 810028968139099245616676224V02100839 0000006 62512113504500001205407 0000002277990905144129 1 0000007 700 810018244939019245708867618V02124213 0000007 62512113504500001208706 0000000750990904234925 1 0000008 700 81001824511841794170 V01215010 0000008 62512113504500001208706 0000001250990904151006 1 0000009 700 81001824511892440840 V01470866 0000009 62512113504500001212539 0000001448990905111042 1 0000010 700 81001807705700062524 V02091128 0000010

Figure 5 Raw Data File - PAN Sample


Match and Hold Record LayoutThe AP Hold File program contains hold information from the cardholder’s account holds.

The record layout for an AP Hold file includes:

File header File trailer Batch header Batch trailer Entry Detail Entry Addendum

FieldsThe following table explains the rules that apply to the fields in an AP batch maintenance file:

If You Enter Then

Blank spaces You space fill a field. Existing data does not change when you blank fill the spaces.

Alpha Values You type in uppercase.

All Field You left-justify and fill the field with trailing blanks.

Asterisks You blank out existing data. (Alpha or Alpha/Numeric fields only)

Zeros You reset values to zero.

Any other characters You replace existing data with the new data.


File Header RecordThis header record is for the entire batch file.

Field Pos.Len.

Attri-butes Description

Record Type Code 1 1 Numeric Value = 1

Priority Code 2 2 Numeric Value = 01

Immediate Destination 4 10 Numeric Issuer IID numberPosition 1 = blankPositions 2-9 = ABA Routing and Transit NumberPosition 10 = Check digit

Immediate Origination 14 10 Numeric Issuer IID numberPosition 1 = blankPositions 2-9 = ABA Routing and Transit NumberPosition 10 = Check digit

Transmission Date 24 6 Numeric File creation date (YYMMDD)

Transmission Time 30 4 Numeric File creation time (HHMM)

File ID Modifier 34 1 Numeric Value = 1

Record Size 35 3 Numeric Value = 094

Blocking Factor 38 2 Numeric Value = 10

Format Code 40 1 Numeric Value = 1

Destination Name 41 23 Alpha-numeric

Issuer institution name

Origination Name 64 23 Alpha-numeric

Connex on HP NonStop system name

Blanks 87 8 Alpha-numeric

Value = 8 spaces


File Trailer RecordThis trailer record is for the entire batch file.

Field Pos. Len.Attri-butes Description

Record Type Code 1 1 Numeric Value = 9

Batch Count 2 6 Numeric Number of batch header records in the file

Block Count 8 6 Numeric Number of physical blocks in the file, including file headers and file trailers divided by 10

Entry Addendum Count

14 8 Numeric Number of entry detail and entry addendum records processed in the file

Entry Hash 22 10 Numeric The routing and transit number with the check digit (the first 8 digits only) multiplied by the number of times the routing and transit number appears in the hold file. This is a 10-digits field. If the sum of the routing and transit numbers is longer than the available 10 positions, the left-most positions are truncated.

Total Debit Amount 32 12 Numeric Total debit entry amount in the file (two decimal digits)

Total Credit Amount

44 12 Numeric Total credit entry amount in the file (two decimal digits)Should always be zero


Value: 39 spaces


Batch HeaderThis header record is used to indicate the start of each institution’s batch file.

FieldPos. Len.


Record Type Code 1 1 Numeric Value: 5

Service Class Code 2 3 Numeric Value = 200

Company Name 5 16 Alpha-numeric

Issuer institution name

Hold Type 21 10 Alpha-numeric

Blank = UnspecifiedACCOUNT = account holds

Batch Type 31 10 Alpha-numeric

blank = all hold types togetherM = Debit MasterCard®P = POS Pre-authorizationV = Visa Check™

Destination FRDABA 41 10 Numeric Issuer FRDABA numberPosition 1 = blankPositions 2-9 = ABA Routing and Transit NumberPosition 10 = Check digit

Standard Entry Class 51 3 Alpha-numeric

Standard entry classDefault value will be ‘HLD’

Company Entry Description

54 10 Alpha-numeric

Standard entry description

Company Description Date

64 6 Numeric File creation date (YYMMDD)

Effective entry date 70 6 Numeric File creation date (YYMMDD)


Value: 3 spaces

Originator Status Code

79 1 Alpha-numeric

Value: 1


Value: 8 spaces

Batch Number 88 7 Numeric Assigned in ascending sequence


Batch TrailerThis trailer record is used to indicate the end of each institution’s batch file.

FieldPos.

Len.


Record Type Code 1 1 Numeric Value: 8

Service Class Code 2 3 Numeric Value: 200

Entry Addendum Count

5 6 Numeric Number of entry detail and entry addendum records processed in the batch

Entry Hash 11 10 Numeric The critical institution ID number is hashed to provide a check (entry addendum records are not hashed)

Total Debit Amount 21 12 Numeric Total debit entry amount in the file (two decimal digits)

Total Credit Amount 33 12 Numeric Total credit entry amount in the file (two decimal digits)Should always be zero

Destination FRDABA 45 10 Numeric Cardholder ID numberPosition 1 = blankPositions 2-9 = ABA Routing and Transit NumberPosition 10 = Check digit


Value: 33 spaces

Batch Number 88 7 Numeric Assigned in ascending sequence


Detail RecordThis is the detail record for an institution.

FieldPos.

Len.


Record Type Code 1 1 Numeric

Value: 6

Transaction Code 2 2 Numeric

Default is DDA. ACH type code:25 = DDA debit29 = DDA credit35 = SAV debit39 = SAV credit45 = OTH debit49 = OTH credit55 = CRD debit59 = CRD credit

Bank Identification 4 9 Numeric

Cardholder IID numberPositions 1-8 = ABA Routing and Transit NumberPosition 9 = Check digit

Account Number 13 24 Alpha-numeric

Cardholder account number

Amount 37 10 Numeric

Amount of hold (two decimal digits)

Expiration Date 47 6 Numeric

Hold expiration date (YYMMDD)

Expiration Time 53 6 Numeric

Hold expiration time (HHMMSS)

PAN 59 19 Alpha-numeric

This key field identifies the cardholder whose transaction placed the hold when more than one cardholder is linked to a card.

Plastic Number 78 5 Alpha-numeric

This key field number on Track II of the card’s magnetic stripe identifies the card that placed the hold if more than one card is issued with the same PAN. Not used for Visa Check™ or Debit MasterCard® cards.


Entry AddendumThis is the entry addendum for an institution.

Addendum Indicator

83 1 Numeric

Value: 1


Value: 4 blank spaces

Sequence Number 88 7 Numeric

Assigned in ascending sequence to entries in a batch.

FieldPos.

Len.


Field Pos.Len.


Record Type Code 1 1 Numeric

Value: 7

Addendum Type Code 2 2 Numeric

Value: 00

Blank 4 1 Alpha-numeric

Value: 1 space

Match Data Alpha-numeric

This data is used to match the clearing item with the pre-authorization held against either the cardholder’s limit or account balance. The field information varies based on the type of pre-authorization transaction. Select one of the following Match Data options.

Match Data for Pre-Auth

5 36 Alpha-numeric

Use this data to match the hold.

Pos. Description

1-12 Last 12 digits of the card number performing the transaction that placed the hold.

13-27

The Terminal Reference is the number from the terminal used in the transaction.

28 P (standard POS pre-authorization)


29-30

Blank Fill

31-36

The authorization number for the hold transaction. Use the AP or online host assigned authorization number.

Match Data for Debit MasterCard®

5 36 AlphaNumeric


Pos. Description


13-27

Terminal Reference is the number from the terminal used in the transaction.

28 M (Debit MasterCard® transaction)

29-30

Terminal Day is the 2-digit day of the month when the original transaction occurred.

31-36


Match Data for Visa Check with Transaction Identifier

5 36 Alpha-numeric


Pos. Description


13-27

The Visa® Transaction Identifier for this transaction.

28 V (Visa Check™ transaction)

29-30


Field Pos.Len.



31-36


Match data for visa check without transaction identifier

5 36 Alpha-numeric


Pos. Description

1 - 12

Last 12 digits of the card number performing the transaction that placed the hold.

13 - 20

The Terminal Reference number from the terminal used in the transaction.

21 - 27

Blank or Space fill


29 - 30


31 - 36


MERCHANT-NAME 37 25

HOLD-STATUS 62 1

MERCHANT-CODE 63 4

CREATE-TIME 67 12 Format: YYMMDDhhmmss

EXPR-USER-ID 79 5

Note: These fields are optional and may not be present.

Sequence Number 88 7 Numeric

Assigned in ascending sequence to entries in a batch.

Field Pos.Len.



AP Hold ReportThe optional AP Hold Report is a transaction level report that lists all holds currently placed against your cardholder’s accounts. Your institution can use this report to hand-post the holds if you do not receive the AP Hold File. (Memo posting the holds helps to prevent the double posting of settled items.)

AP Hold Detail ReportThe AP Hold Detail Report contains information you can use to match your pre-authorization hold transactions. The AP Hold Report is sorted by cardholder account number. If multiple cardholders are connected to the same account, all holds for all connected cardholders are listed for that account number.

Field Descriptions

PAN

This field is blank.

Plastic

The field is blank.

ENK COMM GROUP -000000259 SAMPLE INSTITUTION SETDATE 09/23/99 PAGE 1ENK COMM GROUP -INT025 AP HOLD DETAIL REPORT RUNDATE 09/23/99EF500191-RP01 RUNTIME 20:36:05

HOLD TYPE: ACCOUNT FILE ID: DEPSEF555 BATCH NUMBER: 1PAN PLASTIC ACCOUNT NUMBER EXP DATE EXP TIME TYPE ACCT LIMIT ID AMOUNT

66666609035 06/21/99 15:26:04 V DDA 96.57 MATCH DATA: 999999777712349169735712731V18132714 66666611704 06/19/99 18:09:28 V DDA 19.29 MATCH DATA: 999999777712349167833749556V16161038 66666674921 06/20/99 19:01:10 V DDA 41.62 MATCH DATA: 99999977771234690117 V17170220 66666674921 06/18/99 19:42:17 V DDA 75.05 MATCH DATA: 99999977771234130011 V15174327 66666677508 06/20/99 18:30:17 V DDA 15.22 MATCH DATA: 99999977771234690747 V17163130 66666678902 06/20/99 21:51:03 V DDA 61.50 MATCH DATA: 999999777712349169102690367V17195212 77777702509 06/20/99 14:17:33 V DDA 31.09 MATCH DATA: 999999777712349168694602531V17121843 77777719108 06/20/99 08:52:07 V DDA 1.00 MATCH DATA: 999999777712349168499331776V17065317

Figure 6 AP Hold Detail Report


Account Number

The hold is applied to this cardholder account number.

Exp Date

The date the hold expires if not matched.

Exp Time

The time the hold expires if not matched.

Type

The type of account that has the hold applied to it.Values:

Acct

The cardholder’s account number that has the hold applied to it.

Limit ID

FIS standard product does not support the use of this field.

Amount

The amount of the hold applied to the cardholder’s account.

Match Data

The data used to match the authorized item to the settled item.

Value Description

M Debit MasterCard®

V Visa Check™

P POS Pre-Authorizations



Debit MasterCard®

Visa Check™ with Transaction Identifiers

Pos. Description


13-27 The Terminal Reference is the number from the terminal used in the transaction.

28 P (standard POS pre-authorization).

29-30 Blank Fill

31-36 The authorization number for the hold transaction. Use the AP or online host assigned authorization number.

Pos. Description


13-27 Terminal Reference is the number from the terminal used in the transaction.

28 M (Debit MasterCard® transaction).

29-30 Terminal Day is the 2-digit day of the month when the original transaction occurred.


Pos. Description


13-27 The Visa® Transaction Identifier for this transaction.

28 V (Visa Check™ transaction).




Visa Check™ without Transaction Identifiers

AP Hold Detail Report - With PANThe match and hold information in the following AP Hold Report sample displays the cardholder account number and any cardholder PANs associated with that account number. The PAN on the detail record is not always the PAN that performed the pre-authorization transaction. Any PAN linked to the cardholder’s account can appear in the PAN column. The last 12 digit in the Match Data field are the last 12 digits of the PAN for that card that performed the transaction.

Pos. Description


13-20 The Terminal Reference number from the terminal used in the transaction.

21-27 Blank or Space fill

28 V (Visa Check transaction)




Field Descriptions

PAN

The PAN is the cardholder identifier and a key field.

Plastic

The card identifier used if more than one card is issued with the same PAN. This key field number is used on Track II of the card’s magnetic stripe. You cannot update this key field.

Account


Exp Date

The hold is expired on this date if it is not matched.

Exp Time

The hold is expired at this time if it is not matched.

PROCESSOR NAME -000000013 SETDATE 12/06/99 PAGE 1FINANCIAL INSTITUTION NAME -PRC097 AP HOLD DETAIL REPORT RUNDATE 12/07/99EF500670-RP01 RUNTIME 07:47:34

HOLD TYPE: ACCOUNT FILE ID: DDDXX001 BATCH NUMBER: 1 PAN PLASTIC ACCOUNT NUMBER EXP DATE EXP TIME TYPE ACCT LIMIT ID AMOUNT

5755550240325923 1 0003987567 06/18/99 18:11:10 P DDA 35.00 MATCH DATA: 99999977771234690000 P 116157 5755557777049560 1 3144019431 06/18/99 18:40:08 P DDA 35.00 MATCH DATA: 999999777712344120 P 136580 5755550180082732 1 3344002591 06/18/99 17:43:55 P DDA 35.00 MATCH DATA: 99999977771234690000 P 112724 5755550180173200 1 3800045811 06/18/99 20:24:55 P DDA 36.00 MATCH DATA: 99999977771234942022 P 134434 5755557777167487 1 3800083028 06/18/99 18:14:13 P DDA 35.00 MATCH DATA: 999999777712341690000 P 116570 5755557777068842 1 3800184362 06/18/99 19:01:31 P DDA 35.00 MATCH DATA: 999999777712341690000 P 122826 5755550240183439 1 3800249108 06/18/99 18:50:39 P DDA 35.00 MATCH DATA: 99999977771234690000 P 121399 5755550180269594 1 3800342101 06/18/99 18:17:24 P DDA 35.00 MATCH DATA: 99999977771234690000 P 116989

Figure 7 AP Hold Detail Report


Type


Acct

The cardholder’s account that has the hold applied to it.

Limit ID


Amount


Value Description


V Visa Check™



Enhanced AP Hold Detail ReportThis is the expanded version of the AP Hold Detail Report.

Field Descriptions

PAN

The PAN is the cardholder identifier and a key field.

Plastic

The card identifier used if more than one card is issued with the same PAN. This key field number is used on Track II of the card’s magnetic stripe. You cannot update this key field.

Account


Exp Date

The hold is expired on this date if it is not matched.

Exp Time

The hold is expired at this time if it is not matched.

SAMPLE BANK -101007041 SETDATE 05/24/05 PAGE 2MINIBANK AP PROCESSOR -PRCAPM AP HOLD DETAIL REPORT RUNDATE 05/27/05 EF500670-RP01 RUNTIME 13:33:01 HOLD TYPE: ACCOUNT FILE ID: CBDCI001 BATCH NUMBER: 2 PAN PLASTIC ACCOUNT NUMBER EXP DATE EXP TIME TYPE ACCT LIMIT ID AMOUNT MERCHANT NAME HOLD STATUS MERCHANT CD CREATE DATE CREATE TIME USER ID DDA-THR-01A 05/21/05 23:28:15 M DDA 20.00 FIS A 6011 05/11/05 23:24:12 MATCH DATA: 9999997777123410000 M11000013 DDA-THR-01A 05/21/05 23:28:23 M DDA 20.00 FIS A 6011 05/11/05 23:24:22 MATCH DATA: 9999997777123410000 M11000014 DDA-THR-01A 05/21/05 23:28:31 M DDA 20.00 FIS A 6011 05/11/05 23:24:47 MATCH DATA: 9999997777123410000 M11000015 DDA-THR-01A 05/21/05 23:28:38 M DDA 20.00 FIS A 6011 05/11/05 23:24:54 MATCH DATA: 9999997777123410000 M11000016

Figure 8 Enhanced AP Hold Detail Report


Type


Acct

The cardholder’s account that has the hold applied to it.

Limit ID


Amount


Merchant Name

Merchant name passed in the AP hold file, taken from the external network message.

Hold Status

Internal Merchant Hold status, normally A for active.

Merchant Code

Merchant code, either the ISO external (ISO field no 18) Merchant Category Code/SIC or an MCDP configured override.

Create Time

Format of YYMMDD, hhmmss - converted from HP NonStop Timestamp. The MCDP local system date and time that the hold was created.

Expr User ID

First 5 bytes of the 32 byte user ID field. Not normally seen. The user ID of the hold when manually expired by MSR.

Value Description


V Visa Check™



AP Hold Summary ReportThe AP Hold Summary Report shows the debit and credit amounts by file and batch.

Field Descriptions

Account Number

The cardholder’s account number.

Acct

The Automated Clearing House System account type code. Values are:

Amount

The dollar amount of the hold.

Batch or Batch Number

The number assigned to the batch.

ENK COMM GROUP -000000259 SAMPLE INSTITUTION SETDATE 09/23/99 PAGE 1ENK COMM GROUP -INT025 AP HOLD SUMMARY REPORT RUNDATE 09/23/99EF500191-RP01 RUNTIME 20:36:05

FILE BATCH ENTRIES DEBITS CREDITS APHOLD02 00001 2 101.98 .00 APHOLD02 00002 2 101.98 .00 APHOLD02 00003 4 203.96 .00 APHOLD02 00004 2 101.98 .00

*** TOTAL 10 509.90 .00

Figure 9 AP Hold Summary Report

Value Description

25 DDA debit

29 DDA credit

35 SAV debit

39 SAV credit

45 OTH debit

49 OTH credit

55 CRD debit

59 CRD credit


Credits

The total credit amount for the batch.

Debits

The total debit amount for the batch.

Entries

The total number of entry detail and entry addendum records in the file.

Exp Date

The date the hold expires if not matched.

Exp Time

The time the hold expires if not matched.

File or File ID

The file identifier.

Hold Type

The hold type. ACCOUNT = account holds

Limit ID


Match Data

The data used to match the authorized item to the settled item.


Pos. Description


13-27 The Terminal Reference is the number from the terminal used in the transaction.

28 P (standard POS pre-authorization)

29-30 Blank Fill



Debit MasterCard®

Visa Check with Transaction Identifiers

Visa Check without Transaction Identifiers

Pos. Description


13-27 Terminal Reference is the number from the terminal used in the transaction.

28 M (Debit MasterCard® transaction)



Pos. Description


13-27 The Visa® Transaction Identifier for this transaction.




Pos. Description


13-20 The Terminal Reference number from the terminal used in the transaction.

21-27 Blank or Space fill

28 V (Visa Check transaction)




PAN

The Primary Account Number.

Plastic

The card’s plastic number for accounts with multiple cardholders.

Total

The total number of entries, debits, and credits in the AP Hold File.

Total Records

The total number of records on the AP Hold Detail Report.

Type

The batch type. Values are:

Connex™ on HP NonStop® AP ParametersAP Match and Hold reads the AP file(s) and extracts the limit hold or account hold information to another file that are processed by an IBM® offline program into a file for a specific host. You must run AP Match and Hold as an offline batch job as close as possible after the client’s end-of-day cutoff for the most accurate hold information.

Installation ConsiderationsThis program uses APFILES, SWP45APF, and SWP45APS files along with the related AP cardholder and/or AP account detail files. Recompile APHLDEX, bind APHOLDEX, and install using standard installation procedures. The APHLDEX data file is created from the DFUP file.

Processing InformationYou can run this program two ways:

With run statement parameters With parameters

Value Description

blank all hold types together


P Pre-Authorizations

V Visa Check™


If you use both parameters and run statement parameters, the parameter values override the run statement parameters.

The general outline of the process for using this program is as follows:

Purge the data file contents Set the parameters Run the job Transmit the data file to the IBM® for more processing

Run Statement Parameters

1. When only AD03 (Account Hold) segment is configured.

Create a batch job (OBEY file) as follows:

fup purgedata $dddd.ssssssss.fffffff

clear all param

param evdb $usr1.v12evdb

run $dddd.ssssss.apholdex /in $dddd.ssssssss.fffffff,out $s.#xxxxxx/,nnnnnnnnnn,card

in $dddd.ssssssss.fffffff is the location of the file that will contain the extracted hold information

out $s.#xxxxxx is the report file for the job summary (see below for report content)

nnnnnnnnnn is the client’s FRDABA

If the Output type is card, a Card Group may be passed to create a file of only that Card Group’s holds. Should the option be chosen, create a batch job as follows:

fup purgedata $dddd.ssssssss.ffffff

clear all


run $dddd.ssssss.apholdex /in $dddd.ssssssss.ffffff,out $s.#xxxxxx/ ,nnnnnnnnnn,card, card group, $dddd.objectxx, $dddd.ssssssss.pwmsgsxx

Where card group is the six character card group

$dddd.objectxx is the object file location (volume and subvolume) for all AHLSR940 server

$dddd.ssssssss.pwmsgsxx is the fully qualified PWMSGS file location

2. When AD03 (Account Hold) and AD06 (Additional Account Hold) segments are configured.


Create a batch job (OBEY file) as follows:

fup purgedata $dddd.ssssssss.fffffff

clear all param


run $dddd.ssssss.apholdex /in $dddd.ssssssss.fffffff,out $s.#xxxxxx/

,nnnnnnnnnn,cden

$dddd.ssssssss.fffffff is the location of the file that will contain the extracted hold information

out $s.#xxxxxx is the report file for the job summary (see below for report content) nnnnnnnnnn is the client’s FRDABA

3. If the Output type is cden, a Card Group may be passed to create a file of only that Card Group’s holds. Should the option be chosen, create a batch job as follows:

fup purgedata $dddd.ssssssss.ffffff

clear all


run $dddd.ssssss.apholdex /in $dddd.ssssssss.ffffff,out $s.#xxxxxx/

,nnnnnnnnnn,cden, card group, $dddd.objectxx, $dddd.ssssssss.pwmsgsxx

Where card group is the six character card group

$dddd.objectxx is the object file location (volume and subvolume) for all

AHLSR940 server

$dddd.ssssssss.pwmsgsxx is the fully qualified PWMSGS file location

ParametersThe parameters are:

EVDB is the Connex™ Environmental Database location. FRDABA is the client's routing and transit number. OUTPUT is either CARD, ACCT, CDEN or ACEN.

Use the parameters in the order shown below for the run statement parameters. If using PARAM statements, these parameters can be in any order.

The OUTPUT type determines the type of processing to be done:

CARD loads the PAN (and PLASTIC # if available) and extracts the limit holds if there are no account detail records. If account detail holds are configured, then the account detail account holds are extracted.

ACCT reads the account detail file directly, but does not use the cardholder file and does not extract the PAN/PLASTIC information.


CDEN works only when AD06 (Additional Account Hold) segment is configured. CDEN loads the PAN (and PLASTIC # if available) and extracts the limit holds if there are no account detail records. If account detail holds are configured, then the account detail account holds are extracted.

ACEN works only when AD06 (Additional Account Hold) segment is configured. ACEN reads the account detail file directly, but does not use the cardholder file and does not extract the PAN/PLASTIC information.

If you optionally chose to pass a card group, these are the required parameters:

CARDGRP is the card group

OBJECT is the object file volume and subvolume for the AHLSR940 server

APBM is the fully qualified location of the PWMSGS file

The program does nowaited I/O to the data file being created with the extracted data. The program looks at the record size of the file and adjusts internal buffers to write that size record to the file. Your technical staff can experiment with various record sizes to find an optimal size for speed of processing; the record size must be an integer multiple of the base record size (currently 114 bytes).

A print file is created at the end of the job with the following information:

Processing FRDABA Start time Stop time CPU time used Number of detail records written to the Hold File

IBM® Settlement ParametersOffline IBM® settlement parameter maintenance information is for the staff responsible for updating the V3.00 settlement database.

Update Institution Entity RowPanel ID: EFEGI002Path: INST

Field ChangesSet the AP Match and Hold DDNAME field with the DDNAME to be used for AP Hold File creation. Add a distribution row with this DDNAME as the key. The distribution type is HOLDDIST.


Affected Reports/Files Setting the AP Match and Hold DDNAME field is required to activate an institution for AP Hold file processing. If an entry is not made and AP hold records are passed from HP NonStop online to offline, the AP Hold create program is not able to process those records.

Update Distribution Parameter RowPanel ID: EFEGZ030Path: INST/PARM-DD-DR(HOLDDIST)

Field ChangesAdd a distribution row for the DDNAME on 'AP Hold DDNAME' on the institution row (panel=EFEGI002). The type = 'HOLDDIST'. This entry should be set up in the same manner that a POSTDIST entry is set up. The output length should be 094. There are some settings required in the free-format Batch/EDC-Unique field.

Affected Reports/FilesThis distribution row (HOLDDIST) is required to activate an institution for AP Hold File processing. If an entry is not made and AP hold records are passed from HP NonStop® online to offline, the AP Hold create program will not be able to process those records.

Position Length Field

01 02 Batching OptionValues: Blank = All holds processed together (default)01 = Batch by hold type

03 11 Originating Institution Identifier (used on file header)

14 23 Originating Institution Name (used on file header)

37 03 Standard Entry Class (used on batch header)

40 10 Company Entry Description (used on batch header)


AP Hold Program Abend and Return Codes

EFVP0030 Abend Codes

EFVP0030 Return Code

EF500668 Abend Codes

EF500668 Return Code

Abend Codes Description

100 Processor not found on database

200 Network not found on database

300 Distribution row not found on database

400 No institutions set up for AP hold processing

841 Table overflow (see JOBAUDIT for table description)

1000 No data on db2extrf file

4095 Invalid setdate

Return Code Description

0 Successful completion


100 Institution not found on termerch

200 Processor not found on termerch

841 Table overflow (see JOBAUDIT for table description)

4000 Termerch open failure

4010 Termerch read failure

4090 Termerch close failure

4095 Invalid setdate




EF500670 Abend Codes

EF500670 Return Codes


100 No parmdata present or institution with hold data

200 Count on APHOLD trailer record does not match pgm cnt

300 Invalid APHOLD record type found

400 APHOLD record type out of sequence

500 Invalid return from i/o subsystem driver, ZZ200088

600 Invalid return from table sort subroutine, ZZ200080

700 No DDNAME(s) specified for redistribution

841 Table overflow (see JOBAUDIT for table information)

1000 Invalid parmdata input

4095 Invalid settlement date abend



4 No activity to report because no data was present or because no data matches the redistribution parameters


A
AP Batch Record Layouts
This appendix provides samples of the record layouts you need to submit for AP Batch Maintenance. The following record layouts provide a brief description of each segment and all of the fields within that segment. All fields are left-justified and padded on the right with spaces.

Key Field InformationYou cannot update a key field. Key fields for the cardholder segments include PAN and PLASTIC-NBR. Key fields for the account detail segments are FI-ID, ACCT-TYPE, and ACCT-NO. If you update a key field, you must send in a delete for that segment and then send in an add for that segment with the updated key field information.

CH01A - Cardholder InformationThis cardholder segment is required to add cardholders for an initial load and ongoing maintenance. (This segment is not required for updates.) All of the information in this segment is at the cardholder level. The CH01A segment is always the first segment submitted in an AP Batch II maintenance file. This segment stores the cardholder information including card access, card status, and PIN fail. The CARD-ACT (Card Activation) field was added to the Cardholder Information Transaction segment for card activation. The host uses this segment to update the corresponding fields in the Cardholder File.

NOTE: If your institution uses any type of PIN change product (PIN change via ATM or PIN change via EIVR) through FIS, you CANNOT submit a full file replacement. A full file replacement will overwrite all the PIN offsets, including those previously changed by cardholders. Those cards will then be denied for an incorrect PIN.


If you use AP screen maintenance, this segment information displays on the Cardholder Information Screen (APMSC022), the Account Detail Account Information Screen (APMSC51), and the AP Quick Maintenance Screen (APMSC003).

The identifiers for this group of fields are:

NOTE: Use segment CH01A to delete the cardholder record.

If you want to delete a cardholder’s account detail information or account, submit segments AD01A and AD01B. If you have multiple cardholders linked to one account, do not delete the account detail information for one cardholder unless you are deleting all of the cardholders associated with that account.

If your institution uses Scoring and Case Management, submit the FR01A, FR02A, FR02B, FR03A, and FR03B records to delete the fraud file information for the cardholder.

When adding a cardholder, segment CH01 must be sent followed by segment CH04A for each override limit.

Identifiers Fields

Segment ID 01

Segment Definition CARD INFO

Segment Description Cardholder Information

Field Number and Name Pos. Len. Status Attributes Description/Usage

1 RECORD-NAME 3 2 Required Alpha-numeric

File identifier.Value = CH

2 SEG-ID 5 2 Required Numeric Segment Identifier.Value = 01



Sub-segment identifier.Value = A

4 FILE-UPDATE-CODE 8 1 Required Numeric Action code.Values:5 = Add6 = Delete8 = Update


5 PAN 9 19 Required Numeric This key field identifies the cardholder. The last 10 non-space digits are used to determine hash field totals. Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.

6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. The key field number used on Track 2 of the card’s magnetic stripe.Format = 99999Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 ISSUING-FI-ID 33 10 Required Numeric Identifies the financial institution issuing the card.Format = 1NNNNNNNNCN = Routing & Transit numberC = Check Digit

8 CI-STATUS 43 2 Optional Alpha-numeric

Reject or capture card if hot- or warm-carding. You can use ** to clear an existing status.Values:Blank = Normal Card or No ChangeAK = Capture Hot CardNK = No Capture Hot Card Note: See “Reject Reason Codes” on page 271 in Appendix C for a complete list of reject reason code values.



9 CARD-ACCESS 45 9 Required Alpha-numeric

The next 9 bytes determine the type of transactions this card can be used for. Accept transaction and override transaction codes in AP parameter file. At least one access is required for an Add. Values:1 or Y = Access

9a WITHDRAWAL 45 1 Optional Alpha-numeric

Indicates if account is used for withdrawals. Values:1 or Y = Allow Withdrawal0 or N = No WithdrawalBlank = No Change

9b DEPOSIT 46 1 Optional Alpha-numeric

Indicates if account is used for deposits. Values:1 or Y = Allow Deposit0 or N = No DepositBlank = No Change

9c BAL INQUIRY 47 1 Optional Alpha-numeric

Indicates if cardholder can inquire about the account balance. Values:1 or Y = Allow Inquiry0 or N = No InquiryBlank = No Change

9d PAYMENT-TO 48 1 Optional Alpha-numeric

Indicates if this is the account to make payments to. Values:1 or Y = Allow Payment0 or N = No PaymentBlank = No Change

9e PAYMENT-FROM 49 1 Optional Alpha-numeric

Indicates if this is the account to make payments from. Values:1 or Y = Allow Payment0 or N = No PaymentBlank = No Change

9f TRANSFER-TO 50 1 Optional Alpha-numeric

Indicates if this is the account to transfer funds to. Values:1 or Y = Allow Transfer0 or N = No TransferBlank = No Change



9g TRANSFER-FROM 51 1 Optional Alpha-numeric

Indicates if this is the account to transfer funds from. Values:1 or Y = Allow Transfer0 or N = No TransferBlank = No Change

9h PURCHASE 52 1 Optional Alpha-numeric

Indicates if the account is used for purchases. Values:1 or Y = Allow Purchase0 or N = No PurchaseBlank = No Change

9i 3rd-PARTY PAYMENT 53 1 Optional Alpha-numeric

Indicates if this is the account to use for third-party payments.Values:1 or Y = Allow Payment0 or N = No PaymentBlank = No Change

10 Future 54 7 Optional Alpha-numeric

Not currently used. Value = Spaces

11 PIN-FAIL-CNT-RESET 61 1 Required Alpha-numeric

Indicates whether to reset the PIN fail count to prevent the account from being blocked when the value exceeds the limit.Values:Y = Reset PIN fail count to zeroBlank = No Change.

12 LIMIT-GROUP-ID 62 6 Required Alpha-numeric

Four-character, FIS-assigned ID used to determine the allowed transactions and limits for a cardholder group, followed by a two-digit group ID. This field must not be blank when doing the initial file loads via batch maintenance.Format = AAAA99, where:A = 4-character FIS ID9 = 2-digit numberNote: The same ATM cardbase could have identical or different limits, but each cardbase needs a different LIMIT-GROUP-ID.



Input Sample

13 FEE-GROUP 68 6 Optional Numeric Fees charged to cardholder for EFT transaction based on type and location. Do not use for Network members.Format = 999999

14 CARD-ACT 74 1 Required Alpha-numeric

Current card activation flag. Indicates if Card Activation should reject transactions for cards that are not activated. Values:Blank = Defaults to Y (Card Active)Y = Card ActiveN = Card Not Active (Rejects pinless transactions)Note: To use the new card activation enhancements, you must use and maintain this field. If CIMS is your card vendor, this field is automatically set to N.If card issuance is not done via CIMS and updated values for this field are sent, AP automatically moves the current value to the PREV-CRD-ACT field in segment “CH22B - Card Validation Information” on page 187.

15 BLANK 75 6 Required Alpha-numeric

Ensures 80-byte record.Value = Spaces


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH01A51010000000000000001 1000000000 YYYYYNNNY ABLG01


CH02A - Track 2 InformationThis optional cardholder segment stores the card’s Track 2 information and is required for an initial load if your institution uses the FIS Card Issuance and Management System (CIMS), cardholder validation, and card activation. The segment information includes, PIN offset value, status of the PIN offset value, current card expiration date, and Track 2 date information. The host uses this segment to update the corresponding fields in the Cardholder File.

If you use AP screen maintenance, this segment information displays on the Cardholder Information Screen (APMSC022) and the Account Detail Account Information Screen (APMSC051).


Identifiers Fields

Segment ID 02

Segment Definition TRACK2

Segment Description Track 2 Information




2 SEG-ID 5 2 Required Numeric Segment identifier.Value = 02



Sub-segment identifier. Value = A

4 FILE-UPDATE-CODE

8 1 Required Numeric Action code.Values:5 = Add6 = Delete8 = Update

5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits are used to determine hash field totals. Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.


6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. This key field number is used on Track 2 of the card’s magnetic stripe.Format = 99999Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 PIN-AUTH-FLAG 33 2 Conditional Numeric Indicates where the PIN offset resides.Values:00 = AP Holds the Offset01 = AP Does Not Hold Offset99 = PIN Offset Flagged ChangeNote: 99 enables a client PIN change and First PIN transaction is

approved/processed as a PIN change, but PIN is not validated.

New PIN offset is generated and used for all subsequent PIN transactions.

Field resets to 00.Requirement Notes:Enter a 00 if AP is validating the PIN. Leave this field blank if doing an Update.



8 PIN-AUTH-VALUE 35 16 Conditional Numeric PIN offset value stored in AP. Transactions that are not matched are refused. If AP holds the offset, enter the 4-digit PIN-AUTH-VALUE followed by 12 spaces.Values =NNNN_ _ _ _ _ _ _ _ _ _ _ _Where: N = 4-digit PIN Offset and _ = SpaceRequirement Notes:Note: This field is required if PIN AUTH FLAG is 00 or if your institution uses CIMS for ordering cards. 0000 (natural PIN) is used if

CIMS is used for card ordering.

If PIN change is done at ATM, this is a reissue/forced issue, and host does not hold the PIN offsets.



9 TRK2-DATE Conditional The current card expiration date or the card issue date used for expiration date checking, fraud scoring and case management matching. AP Parameter file determines the use.If card issuance is not done via CIMS and updated values are sent for this field, AP automatically moves the current expiration date to the PREV-TRK2-DT field in segment “CH22B - Card Validation Information” on page 187.Note: Do not use a non-expiring date for Visa Check™ or Debit MasterCard® cards.Requirements Notes: Required if using AP for card

activation expiration date or card issuance. Card reissue time is based on this expiration date. If date does not match the date of the CIMS card reissue cycle, a new date is calculated from the date in this field and the reissue cycle date.

Required for Scoring and Case Management.

9a YEAR 51 2 Optional Numeric The last two digits of the year the card expires.Value = 00 to 49

9b MONTH 53 2 Optional Numeric The last two digits of the month the card expires.Value = 01 to 12





Input Sample

CH03A - Account InformationThis cardholder segment stores cardholder account information and is required for the initial load and ongoing maintenance. This segment stores all account information at the cardholder level. The account information includes cardholder account numbers and account descriptions. As part of the cardholder record, this segment stores the Open Account Relationship information that links multiple cardholders to their accounts and multiple accounts to that cardholder.

If you use AP screen maintenance, this segment contains the account information that displays on the Account Information - Summary Screen (APMSC023) and the Account Information - Detail Screen (APMSC024).


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH02A51010000000000000001 006969 9912

NOTE: If you add or update an Account Information segment (CH03A or CH03B), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH03A, you must submit the CH03B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 03

Segment Definition ACCTINFO

Segment Description Account Information




2 SEG-ID 5 2 Required Numeric Segment identifier.Value=03





4 FILE-UPDATE-CODE 8 1 Required Numeric Action code.Values:5 = Add6 = Delete8 = UpdateNote: If adding an account to an existing cardholder, this field must contain a 5.

5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits used to determine hash field totals. Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.


7 ACCT-FI-ID 33 10 Required Alpha-numeric

Identifies the financial institution issuing the card. The institution routing/transit number (N) followed by the check digit (C).Format = 1NNNNNNNNCNote: You cannot update this key field.



8 ACCT-TYPE 43 4 Conditional

Alpha-numeric

The file identifier used if you require separate cardholder files for each OAR account service line. FIS recommends setting up an overdraft account for a cardholder rather than including an overdraft amount in the cardholder’s available balance. If an account is not found, the transaction is denied. Leave this field blank if you do not keep balances.Sample values:ALL = All Service LinesDDA = Checking Account (default)SAV = Savings AccountCRD = Line of CreditOVD = Overdraft AccountOTH = Other Account Blank = Institution does not use balances.Note: You cannot update this key field.Requirements Notes: Required for Balances or if

same account number is used across service lines.

If financial institution is set up for Account Info only and uses OAR, use DDA, SAV, or CRD for the service line. Use the same entry for the OAR-SELECT-TYPE.


The cardholder’s account number that displays on the OAR selection screen of the ATM. The suffix is assigned by the financial institution and varies by institution. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.



10 ACCT-QUALIFIER 75 3 Optional Alpha-numeric

The institution’s qualifying code that is determined by FIS and used in the FINIPC message format.

11 OAR-SELECT-TYPE 78 3 Required Alpha-numeric

Identifies the specific service line for this account. Applies to OAR cardholders with multiple accounts.Values:DDA = Demand Deposit AccountSAV = Savings AccountCRD = Credit AccountOVD = Overdraft AccountOTH = Other AccountLON = Loan AccountRCL = Revolving Credit LineINV = Investment AccountUNV = Universal AccountRequirements Notes:If financial institution is set up for Account Info only and uses OAR, use DDA, SAV, or CRD for the service line. Use the same entry for the ACCT-TYPE.



Input Sample

CH03B - Account InformationThis cardholder segment is required for an initial load and ongoing batch maintenance. This optional cardholder segment stores cardholder account information, including account descriptions, account access information, and primary account and funding account information. If you use account detail, this segment’s field information must remain identical to the field information in segment AD01B.

If you use AP screen maintenance, this segment displays on the Cardholder Account Information Summary Screen (APMSC023), the Cardholder Account Information Detail Screen (APMSC024), and the Account Detail Account Information Screen (APMSC051).


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH03A51010000000000000001 1000000000 98765432101 DDA CH03B51010000000000000001 PRIMARY SAVINGS YYYYYYYYY YN

NOTE: If you add or update an Account Information segment (CH03A and CH03B), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH03B, you must submit the CH03A record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 03

Segment Definition ACCTINFO

Segment Description Account Information








Sub-segment identifier.Value = B

4 FILE-UPDATE-CODE

8 1 Required Numeric Action code.Values:5 = Add6 = Delete8 = UpdateNote: If adding an account to an existing cardholder, this field must contain a 5.

5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits are used to determine hash field totals.Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.


7 ACCT-DESC 33 20 Optional Alpha-numeric

The cardholder’s alphabetic description of the account from segment CH03A. It displays on the OAR selection screen of the ATM and provides the cardholder with a listing of their available accounts.

8 ACCT-ACCESS 53 10 Required Alpha-numeric

The next 10 bytes define how the account can be accessed by the cardholder. Indicates if the transaction can override the transaction codes set up in the AP parameter file. You are required to select access type.Values:1 or Y = Access



8a WITHDRAWAL 53 1 Optional Alpha-numeric

Indicates if account is used for withdrawals.Values:1 or Y = Withdrawal Access0 or N = No Withdrawal AccessBlank = No change


Indicates if account is used for deposits.Values:1 or Y = Deposit Access0 or N = No Deposit AccessBlank = No Change

8c BAL INQUIRY 55 1 Optional Alpha-numeric

Indicates if the cardholder can inquire about the account balance. Values:1 or Y = Inquiry Access0 or N = No Inquiry AccessBlank = No Change

8d PAYMENTS-TO 56 1 Optional Alpha-numeric

Indicates if payments can be made to the account. Values:1 or Y = Payment Access0 or N = No Payment AccessBlank = No Change

8e PAYMENTS-FROM


Indicates if payments can be made from the account. Values:1 or Y = Payment Access0 or N = No Payment AccessBlank = No Change


Indicates if funds can be transferred to the account. Values:1 or Y = Transfer Access0 or N = No Transfer AccessBlank = No Change

8g TRANSFER-FROM


Indicates if funds can be transferred from the account. Values:1 or Y = Transfer Access0 or N = No Transfer Access Blank = No Change



8h PURCHASES 60 1 Optional Alpha-numeric

Indicates if purchases can be made from the account. Values:1 or Y = Purchase Access0 or N = No Purchase AccessBlank = No Change

8i 3rd-PARTY PAYMENT


Indicates if third-party payments can be made from the account. Values:1 or Y = Payment Access0 or N = No Payment AccessBlank = No Change

9 Future 62 7 Optional Alpha-numeric

Values = Spaces

10 PRIMARY-IND 69 1 Conditional

Alpha-numeric

Indicates the main or principal account the ATM should access for a cardholder with more than one account for a service line. Identifies a primary account for each service line when the cardholder has multiple accounts. For example, if the cardholder has more than one savings account, indicate the primary savings account. Values:Y = Primary N = Non-Primary I = Installment Account (LON service line only)M = Mortgage Account (LON service line only)Note: If a funding account is not specified, AP uses the cardholder’s primary demand deposit account. If a primary demand deposit account is not specified, AP uses the first demand deposit account logged to AP for that service line.Requirements Notes: Required for Add.



Input Sample

11 FUNDING-IND 70 1 Conditional

Alpha-numeric

Indicates the one account to access for deposits or withdrawals when a cardholder uses a Visa Check™ or Debit MasterCard® card. A funding account is required for all Visa Check or Debit MasterCard cardholders. Specify only one funding account. If you do not indicate a funding

account, AP uses the cardholder’s primary demand deposit account. If you do not indicate a primary demand deposit account, AP uses the first demand deposit account logged to AP for that service line. If you attempt to Add or Update a cardholder with more than one funding account, an error occurs.

If you do not indicate a funding account and no demand deposit account exists, AP uses the savings account marked for funding. If no funding account is indicated, no demand deposit account exists, and no savings account is marked for funding, the transaction is rejected.

Values:Y = Funding Account N = Not for FundingRequirements Notes: Required for Add.


Ensures 80-byte recordValue = Spaces


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH03A51010000000000000001 1000000000 98765432101 DDA CH03B51010000000000000001 PRIMARY SAVINGS YYYYYYYYY YN


CH04A - Override Limits InformationThis optional cardholder segment stores override limit information for cards specified in segment CH01. The segment’s information overrides the standard limits for a selected cardholder.

If you use AP screen maintenance, this segment contains the information that displays on the Override Limits Information Screen (APMSC025).


NOTE: You could opt for FIS to not check limits in Online mode, but still check them in Offline mode. If FIS is not holding balances, eliminating Offline limits is not recommended.

Identifiers Fields

Segment ID 04

Segment Definition OVERRIDE

Segment Description Override Limits








4 FILE-UPDATE-CODE




6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. This key field number is used on Track 2 of the card’s magnetic stripe. Format = 99999Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 LIMIT-TYPE 33 6 Conditional

Alpha-numeric

Overrides the specified limits for this transaction type. Must match the LIMIT-TYPE in the AP Parameter file. Identifies the limit type, such as withdrawal or deposit, for which limits are being established. Must be a valid limit type. Examples:WDR02 = WithdrawalsPRE020 = Purchase ReturnsPUR020 = PurchasesAVD020 = Available DepositsPPR220 = Pre-authorized PurchaseUAV020 = Unlimited AvailabilityRequirements Notes: Required for Update.

8 LIMIT-AMNT 39 10 Required Alpha-numeric

Overrides the specified maximum dollar amount for a transaction type within a business day. Required for file update. Format = S9999999V99S = sign (+, -, or space = positive)For example, "+100000000" = positive 1,000,000.009 = NumberV = Implied Decimal Point



9 LIMIT-USES 49 5 Required Alpha-numeric

Overrides the maximum number of times a cardholder can use their card within a business day for withdrawals, deposits, or purchases. Values:0 = Zero1 = One2 = Two

10 INCR-AMNT 54 10 Conditional

Alpha-numeric

Required for file update. Overrides the increment amount to be used by the limit. Use the following format. Format = S9999999V99.S = sign (+, -, or space = positive)For example, "+100000000" = positive 1,000,000.009 = NumberV = Implied Decimal PointRequirements Notes: Required for Add.

11 MIN-AMNT 64 10 Optional Alpha-numeric

The minimum amount for which a transaction can be approved when using this limit. Use the following format.Format = S9999999V99.S = sign (+, -, or space = positive)For example, "+100000000" = positive 1,000,000.009 = NumberV = Implied Decimal Point

12 PERCNT-DEP-AVAL

74 3 Optional Numeric Overrides the standard deposit percentage available. Limits amount withdrawn on a deposit at one time. Overrides the normal percentage of same day deposits used to calculate the available balance.Format = 999 (Percentage Number)





Input Sample

CH06A - Hold List InformationThis cardholder segment is used to store holds against a limit for the cardholder specified in segment CH01. This optional segment information is used for matching a pre-authorized purchase to a limit hold. Holds are expired three days after the hold is placed or when the settled transaction item is processed.

If you use AP screen maintenance, this segment contains the information that displays on the Hold List Information Screen (APMSC027).


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH04A51010000000000000001 SBAD 0000500000000010000000100075

NOTE: You can only use segment CH06A to delete limit hold information. Do not use this segment to add or update limit hold information; AP Batch Maintenance does not support those procedures.

Identifiers Fields

Segment ID 06

Segment Definition HOLDLIST

Segment Description Hold List









4 FILE-UPDATE-CODE

8 1 Required Numeric Action code. This segment can only be used to delete limit hold information.Value:6 = Delete


6 PLASTIC-NBR 28 5 Required Numeric Identifies the cardholder if more than one card is issued with the same PAN. This key field number is used on Track 2 of the card’s magnetic stripe.Format = 99999Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 PAN 33 12 Required Numeric Used to match a hold with the settled transaction. Value = Last 12 non-blank characters of PANNote: You cannot update this key field.

8 TERMINAL-REFERENCE


The first 8 digits of the transaction’s terminal reference number used as an ID by the party accepting the card and presenting transaction data to an acquirer.Note: You cannot update this key field.



Input Sample

9 PREAUTH-INDICATOR


Matches the hold with the settled transaction. Values:P = Pre-AuthorizedV = Visa Check™M = Debit MasterCard®Note: You cannot update this key field.

10 TERMINAL-DAY 61 2 Conditional Alpha-numeric

If the PREAUTH-INDICATOR is V or M, enter the day of the month number. Values = 01, 02, ...., 31Note: You cannot update this key field.Requirements Notes: Required for Add.

11 AUTH-NO 63 6 Required Alpha-numeric

The authorization number of the transaction that originated the hold. Match the hold with the settled transaction.Note: You cannot update this key field.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH06A65465123000000000001 00000000000100678000 M12000437


CH08A - Name InformationThis optional cardholder segment is used to store cardholder name information if your institution uses name search. Name search allows you to search for a cardholder’s record using the cardholder’s greeting name.

If your institution is not using name search, you can use this segment to store free form name information for your cardholders.

If you use AP screen maintenance, this segment contains the cardholder’s name that displays on the Cardholder Information Screen (APMSC022).


NOTE: If using Name Search, delimiters (/) are required between the last name, first name, middle initial, prefix (Mr., Mrs., Ms.), and suffix (Senior or Junior) of a greeting name. The delimiters are counted as part of the 20 byte greeting field. Also, you must type the GREET-ING-NAME in uppercase.

Identifiers Fields

Segment ID 08

Segment Definition NAMEINFO

Segment Description Name Information








4 FILE-UPDATE-CODE



5 PAN 9 19 Required Numeric This key field identifies the cardholder. The last 10 non-space digits used to determine hash field totals.Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.


7 GREETING-NAME


Name used to locate the cardholder’s record. If you do not use name search, this free-form field can be used to enter a cardholder name to display on the ATM screen.Format = LAST NAME/FIRST NAME/MI/TITLE/SUFFIX (Values must be in all uppercase letters.)Note: When using Name Search, you must include the delimiters when you enter the information in your maintenance file. If you do not use delimiters, you will encounter a processing error. Use one delimiter following the last name (example: smith/) if you only know the last name.





Input Sample

CH09A - Override ExpireThis optional cardholder segment stores a beginning and ending date for an override limit that may have been created for a card specified in segment CH04. The segment’s information specifies the time period during which the override limit should take effect. When a transaction takes place outside of this time period than the override limit will not be used, instead standard limits will apply.

This segment cannot be maintained via any APM screen.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH08A51010000000000000001 PUBLIC/JOHN/Q/MR

Identifiers Fields

Segment ID 09

Segment Definition OVREXPR

Segment Description Override Expire








4 FILE-UPDATE-CODE





7 LIMIT-TYPE 33 6 Required Alpha-numeric

Overrides the specified limits for this transaction type. Must match the LIMIT-TYPE in the AP Parameter file. Identifies the limit type, such as withdrawal or deposit, for which limits are being established. Must be a valid limit type.Examples:WDR02 = WithdrawalsPRE020 = Purchase ReturnsPUR020 = PurchasesAVD020 = Available DepositsPPR220 = Pre-authorized PurchaseUAV020 = Unlimited AvailabilityRequirements Notes:Required for Update.

8 BEGIN-TIME 39 8 Required on Add

Alpha-numeric

Specifies beginning effective date for the override limit.Value = YYYYMMDD

9 END-TIME 47 8 Required on Add

Alpha-numeric

Specifies ending effective date for the override limit.Value = YYYYMMDD





Input Sample

CH14A - Additional Card InformationThis optional cardholder segment stores additional card information associated with a PAN. It contains information relative to consecutive reject counts and card-type. This information is used both by the online transaction processing system and for AP extracts.

This segment cannot be maintained via any APM screen.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH09A51010000000000000001 SBAD 2005030420050406

Identifiers Fields

Segment ID 14

Segment Definition ADDLCARD

Segment Description Additional Card Info








4 FILE-UPDATE-CODE





7 CONSECUTIVE-REJECTS

33 2 Optional Numeric This value is a count of the number consecutive transactions that have been rejected.

8 PREV-CONSECUTIVE-REJECTS

35 2 Optional Numeric This value is the previous count of the number of consecutive transactions rejected

9 CARD-TYPE 37 2 Optional Alpha-numeric

Value indicating the type of card.Valid Values are:DR- Debit CR - CreditCH - Charge MU - Multi PP - Prepaid AD - Administrative.

10 MEDIA-TYPE 39 2 Optional Alpha-numeric

This value indicates the type of media.Values:MS - Mag Stripe Only IC - Mag Stripe, Contact Chip IP - Mag Stripe, Contact Chip & ContactlessIS - Mag Stripe, Contactless.



Input Sample

CH18A - Card Management Group InformationThis cardholder segment stores the cardholder’s address information. This optional segment is required during the initial load if your institution uses CIMS and any part of the cardholder’s address is being changed. The host uses this segment to update the corresponding fields in the Cardholder File.

If you use AP screen maintenance, the updated fields display on the Card Management Group Information Screen (APMSC040).

11 CARD-COMPANION-MINI


This value indicates the small cards or fobs that hang on a keyring and can be waved at a device.Value = Y/N.

12 CARD-COMPANION-MICRO


This value indicates the tags/stickers placed onto devices that can be waved at a device.Value = Y/N.

13 CARD-COMPANION-MOBILE


This value indicates that the cardholders have loaded the application onto their mobile device.Value = Y/N.

Note: Institutions using AP Batch II File and Issuing Chip Cards should activate the CH14A(Additional Card Information Record) and should populate the fields CARD TYPE, MEDIA TYPE, CARD-COMPANION-MINI, CARD-COMPANION-MICRO, and CARD-COMPANION-MOBILE with the appropriate values.




12345678901234567890123456789012345678901234567890123456789012345678901234567890

CH14A51010000000000000001 0000DRICNNY



NOTE: If you add or update a Card Management Group Information seg-ment (CH18A, CH18C, and CH18D), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH18A, you must submit the required CH18C and CH18D records. If any of the required records are not submitted, the update is rejected.

CH18B is an optional record and should only be submitted for an update if you submitted this record when the cardholder was origi-nally added.

Identifiers Fields

Segment ID 18

Segment Definition CARDMAN

Segment Description Card Management Group







Sub-segment identifier. Value = A

4 FILE-UPDATE-CODE




Input Sample

CH18B - Card Management Group InformationThis cardholder segment is used to store the cardholder’s second address. This optional segment is or during the initial load if your institution uses CIMS. Do not submit this segment for an add if the corresponding fields in the Cardholder File are blank.

If you use AP screen maintenance, this segment contains the information that displays on the Card Management Group Information Screen (APMSC040).


7 ADDRESS-1 33 30 Required Alpha-numeric

The cardholder’s mailing address. Used for card and case management.


Ensures 80-byte record. Value = Spaces


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH18A81010000000000000002 1123 CRABAPPLE CT CH18B81010000000000000002 CH18C81010000000000000002 WASHINGTON DC4883794110Y CH18D81010000000000000002 SS123000000/BD070445


The identifiers for this group of field are:

NOTE: If you add or update a Card Management Group Information seg-ment (CH18A, CH18C, and CH18), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH18A, you must submit the required CH18C and CH18D records. If any of the required information is not submitted, the update is rejected.


Identifiers Fields

Segment ID 18









Sub-segment identifier. Value = B

4 FILE-UPDATE-CODE




Input Sample


7 ADDRESS-2 33 30 Optional Alpha-numeric

The second line of the cardholder’s street address used for card or case management.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH18A81010000000000000002 1123 CRABAPPLE CT CH18B81010000000000000002 P. O. BOX 1234 CH18C81010000000000000002 WASHINGTON DC4883794110Y CH18D81010000000000000002 SS123000000/BD070445


CH18C - Card Management Group InformationThis cardholder segment stores cardholder address information and is required during the initial load if your institution uses CIMS. This optional segment’s information includes the cardholder’s city, state, or zip code. The host uses this information to update the corresponding fields in the Cardholder File.

If you use AP screen maintenance, this segment contains the information that displays on the Cardholder Management Group Information Screen (APMSC040).


NOTE: If you add or update a Card Management Group Information seg-ment (CH18A, CH18C, and CH18D), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH18A, you must submit the required CH18C and CH18D records. If any of the required records are not submitted, the update is rejected.


Identifiers Fields

Segment ID 18









Sub-segment identifier. Value = C

4 FILE-UPDATE-CODE





7 CITY 33 19 Required Alpha-numeric

The city portion of the cardholder’s address. Entry of this field is required if CIMS or AVS is being used.Note: This field is displayed only if the Card Management Group segment using this field is set up in the Parameter file.

8 STATE 52 2 Required Alpha-numeric

The state portion of the cardholder’s address. Entry of this field is required if CIMS or AVS is being used. Two asterisks (**) in this field indicates this is a non-U.S. address. (See the Zip Code description below for more information.) In the case of a non-U.S. address, the City field may be used to contain the country. For valid values, refer to Appendix D, “Abbreviations” on page 293.Note: This field displays only if the Card Management Group segment using this field is set up in the Parameter file.



Input Sample

9 ZIP-CODE 54 9 Conditional

Alpha-numeric

The cardholder's zip code (required if CIMS or AVS is being used). This field does not require an entry if the State field is filled with two asterisks (**).Note: This field is displayed only if the Card Management Group segment using this field is set up in the Parameter file.Requirements Notes: Required for US.

10 CARD-CONDITION-FLAG

63 1 Required Numeric Current card status.Values:0 = Normal1= Hot Card2 = Warm CardNote: AP processing does not distinguish between 1 and 2; only used for CIMS. Value here is not carried over to other segments, but maintained separately.

11 AUTO-ISSUE 64 1 Required Alpha-numeric

Indicates if the card is eligible for automatic reissue if the current card expires.Values:Y = Eligible for Automatic ReissueN = Not Eligible for Automatic ReissueNote: Use N to use CIMS for PIN mailer only.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890



CH18D - Card Management Group InformationThis cardholder segment is used to store cardholder comment information and is required during the initial load if your institution uses CIMS. The host uses this segment to update the corresponding fields in the Cardholder File.

If you use AP screen maintenance, this segment contains the information that displays on the Cardholder Management Group Information Screen (APMSC040).


NOTE: If you add or update a Card Management Group Information record (CH18A, CH18C, or CH18D) you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH18A, you must submit the required CH18C and CH18D records. If any of the required records are not submitted, the update is rejected.

CH18B is an optional records and should only be submitted for an update if you submitted this record when the cardholder was origi-nally added.

Identifiers Fields

Segment ID 18





File identifier. Value = CH

2 SEG-ID 5 2 Required Numeric Segment identifier. Value = 18



Sub-segment identifier.Value = D

4 FILE-UPDATE-CODE



Input Sample

CH19A - Card Management Member InformationThis cardholder segment stores card information and is required during the initial load if your institution uses CIMS and/or cardholder validation. This optional segment is used for card ordering, including the cardholder’s name, photo ID, and the Personix Card Collection Series styles. This segment is also used for card activation, specifically for calculating the number of days to activate the card. The host uses this segment to update the corresponding fields in the Cardholder File.

If you use AP screen maintenance, this information displays on the Card Management Member Information Screen (APMSC041).

5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits used to determine hash field totals.Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.


7 CARDHOLDER-COMMENTS


Reserved for comments about the cardholder.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890




NOTE: If you add or update a Card Management Member segment (CH19A or CH19B), you must submit all of the required records for that seg-ment even if you are not changing that record’s information. For example, if you update CH19A, you must submit the required CH19B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 19

Segment Definition CARDMAN2

Segment Description Card Management Member





3 OCCURENCE-SECTION



4 FILE-UPDATE-CODE




6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. This key field number is used on Track 2 of the card’s magnetic stripe. Format = 99999Note: You cannot update this key field. Do not use for Visa Check™ or Debit MasterCard® cards.

7 MEMBER- NUMBER

33 2 Required for CIMS

Alpha-numeric

Number used to identify multiple card recipients having the same PAN and plastic number.Values:01 = Primary02 = Secondary03 = Third04 = Fourth

8 CARDHOLDER- NAME-FIRST


Alpha-numeric

The cardholder’s first name embossed on the card.

9 CARDHOLDER- NAME-LAST


Alpha-numeric

The cardholder’s last name embossed on the card.

10 CARDHOLDER- NAME-MIDDLE INITIAL


The cardholder’s middle initial embossed on the card.

11 CARD-ORDER-TYPE-FLAG


Alpha-numeric

Indicates what is generated for the card order.Values:B = Card and PIN MailerC = Card Mailer OnlyP = PIN Mailer OnlyNote: Use B if not ordering a card or PIN.



12 CARD-ORDER-STATUS-FLAG


Alpha-numeric

Indicates status of the card order.Values:0 = Do Not Order1 = New Order2 = Reorder Pending3 = Order CreatedNote: This field does not control issuing a card. Use a 1, 2, 3 or 4 for position 33, CARD-ISSUE-REASON-FLAG in “CH19B - Card Management Member Information” on page 181 to order a card.Refer to the section CH19B for the explanation of values.

13 CARD-ORDER-STATUS UPDATE-DATE


Alpha-numeric

Date the card order was last updated.Format = YYYYMMDD (defaults to current date if left blank)Note: Use current date if not ordering a card or PIN.

14 PHOTO-CARD 75 1 Required for CIMS

Alpha-numeric

The PersonixSM Card Services photo ID card displays cardholder’s picture.Value:1 = Photo CardSpace = No Photo Card (default if left blank)Note: The social security number field in segment “CH22A - Card Validation Information” on page 184 is required if you select the photo ID card.

15 CARD COLLECTION


Alpha-numeric

Personix Card Services card styles that display on the card. Values:NNN = Style NumberSpace = Personix card style not used (default if left blank)Note: See “Personix Card Collection Series” on page 179.





Input Sample

Personix Card Collection SeriesThe table on the following pages lists the card styles available for each specific card type. None of the styles from the PersonixSM Card Collection Series are available with Photo Card for ATM cards. Before selecting the photo ID card or a Card Collection Series style, contact a representative from Personix Card Services at (800) 842-4712.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH19A53636000000000000001 01BRETT SMITH XB0199610061003

Available Card Types

Personix Card CollectionATM Card (No Photo)

Visa Check™

Visa Check Photo Card

Debit MasterCard®

MasterCard Photo Card

000 Eggplant Marble x x x

001 Beige Marble x x x x x

002 Green & Gold Marble x x x x x

003 Grey & White Marble x x x

004 Grey Marble x x x

005 Antique x x x

006 Mariner x x x

007 Gentry x x x

008 Great Forest x x x

009 Estate x x x

010 Flag x x x

011 Statue of Liberty x x x

012 Lighthouse x x x x x

013 Mountains x x x x x

014 Barn x x x

015 $20 Bills x x x x x

016 Money & Gears x x x


017 Cash & Coins x x x x x

018 Earth Globes x x x

019 Waves x x x

020 Fish x x x

021 Blue Marble x x x x x

022 Shoreline x x x

023 Tranquility x x x

024 Countryside x x x

025 Medallion x x x

026 Coronet x x x x x

027 Fresco x x x x x

028 Fleur-de-lis x x x x x

029 Currency x x x

030 Coronet Gold x x x

031 Coronet Platinum x x x

032 Fleu-de-Lis Gold x x x

033 Fleu-de-Lis Platinum x x x

034 Radiance x

035 Aurora x x x x x

036 Azure x

037 Portico x x x x x

038 Neptune x

Available Card Types

Personix Card CollectionATM Card (No Photo)

Visa Check™

Visa Check Photo Card

Debit MasterCard®

MasterCard Photo Card


CH19B - Card Management Member InformationThis cardholder segment stores card information and is required during the initial load if your institution uses CIMS and/or cardholder validation. This optional segment is used for card ordering, including card issue and card reissue information. This segment is also used for card activation, specifically for calculating the number of days to activate the card. The host uses this segment to update the corresponding fields in the Cardholder File.

If you use AP screen maintenance, this information displays on the Card Management Member Information Screen (APMSC041).


NOTE: If you add or update a Card Management Member segment (CH19A or CH19B), you must submit the required records for that segment even if you are not changing that record’s information. For example, if you update CH19A, you must submit the required CH19B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 19

Segment Definition CARDMAN2

Segment Description Card Management Member 2B








4 FILE-UPDATE-CODE





7 CARD-ISSUE-REASON-FLAG


Alpha-numeric

Action to take for the last card issued.Values:0 = Issue new card only if current card expired1 = Issue new card immediately2 = Reissue card immediately3 = Priority Issue/New immediately4 = Priority Reissue immediatelyNote: Priority coding will cause the card personalization vendor to expedite production (if they support it). For those vendors that do not support it at 3 will act like a 1 and a 4 will act like a 2. As of this printing only FIS Cardpro and FIS St Pete card production support this code.

8 CARD-REPLACEMNT-INDICATOR


Alpha-numeric

Action to take when an automatic reissue occurs.Values:Y = Generate a CardN = Do Not Generate a Card

9 DATE-CARD-ORIGINALLY-ISSUED


Alpha-numeric

The date the card was first issued.Format = YYYYMMDD (defaults to current date if left blank)



Input Sample

10 DATE-CARD-LAST-ISSUED

43 8 Conditional Alpha-numeric

Date the card was last issued. If using CIMS, this is a required field.If not using CIMS but using Card Activation, this field is required for calculating the number of days to activate the card.Format = YYYYMMDD (defaults to current date if left blank)Requirements Notes: Required for Scoring and

Case Management.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH19B53636000000000000001 0N1996100119961006


CH22A - Card Validation InformationThis cardholder segment stores cardholder validation or verification information, including social security number, mother’s maiden name, and home and business phone numbers. If your institution uses the validation information and this segment is not present, AP creates this segment when the cardholder activates their card.

If you use AP screen maintenance, this segment is on the Card Activation Screen (APMSC045).


NOTE: If you want to limit the number of days for a cardholder to activate their card, you must send both segments CH19A and CH19B.

If you add or update a Card Validation Information segment (CH22A or CH22B), you must submit all the required records for that segment even if you are not changing that record’s information. For example, if you update CH22A, you must submit the required CH22B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 22

Segment Definition VALIDATE

Segment Description Validation Information


1 RECORD-NAME 3 2 Required Character File identifier.Value = CH

2 SEG-ID 5 2 Required Character Segment identifier.Value = 22


7 1 Required Character Sub-segment identifier.Value = A

4 FILE-UPDATE-CODE



5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits used as the hash field.Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.

6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. This key field number is used on Track 2 of the card’s magnetic stripe.Format = 99999 Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 SOCIAL SECURITY NUMBER

33 9 Conditional Character The cardholder’s 9-digit social security number. Used for case management, card activation, and photo card.Note: For EIVR use and Scoring and Case Management. If populating only the last 4 digits of the SSN, use blanks before the last 4 digits (right justify, blank fill). For example, bbbbb####.Requirements Notes: Required for Scoring and

Case Management.

8 MOTHER’S MAIDEN NAME

42 17 Conditional Character The maiden name of the cardholder’s mother. Used for case management and card validation.Requirements Notes: Required for Scoring and

Case Management.



Input Sample

9 HOME PHONE 59 10 Conditional Character The cardholder’s home telephone number using the format AAANNNNNNN Where:A = Area CodeN = 7-digit Phone Number. Do not use hyphens.If no area code is available, enter 000 followed by the 7-digit phone number. Use for case management and card activation.Requirements Notes: Required for Scoring and

Case Management.

10 BUSINESS PHONE

69 10 Conditional Character The cardholder’s business telephone number using the format AAANNNNNNN Where:A = Area CodeN = 7-digit Phone Number. Do not use hyphens.If no area code is available, enter 000 followed by the 7-digit phone number. Use for case management and card validation.Requirements Notes: Required for Scoring and

Case Management.

11 BLANK 79 2 Required Character Ensures 80-byte record.Value = Spaces


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH22A53636000000000000001 396860731FLAKE 41435274554149635611


CH22B - Card Validation InformationThis optional cardholder segment stores cardholder validation or verification information, including date of birth, user defined information, and home phone information. This segment also stores card activation information including activation method, activation time stamp, and EIVR counter.

If you use AP screen maintenance, this information displays on the Card Activation Screen (APMSC045).


NOTE: If you want to limit the number of days for a cardholder to activate their card, you must send both segments CH19A and CH19B.

If you add or update a Card Validation Information segment (CH22A or CH22B), you must submit all the required records for that segment even if you are not changing that record’s information. For example, if you update CH22B, you must submit the required CH22A record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 22

Segment Definition VALIDATE

Segment Description Validation Information


1 RECORD-NAME 3 2 Required Character File segment identifier.Value = CH

2 SEG-ID 5 2 Required Character Segment identifier.Value = 22


7 1 Required Character Sub-segment identifier.Value = B

4 FILE-UPDATE-CODE

8 1 Required Numeric Action code. Values:5 = Add6 = Delete8 = Update


5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits used as the hash field.Format = 9999999999999999999Note: You cannot update a key field. Send in a Delete record followed by an Add.


7 USER DEFINED VALIDATION

33 25 Optional Character Validation information used for card activation. The secret code used by the EIVR for card activation.

8 VRU-COUNTER 58 1 Optional Character The number of attempts by the cardholder to activate a card using the EIVR. Cardholder is allowed three attempts.Value = 1, 2, or 3Note: If left blank for an Add, defaults to 0. No change is made for an Update.

9 DATE-OF-BIRTH 59 8 Conditional Character Validation information used for card activation.Format = YYYYMMDDRequirements Notes: Required for Scoring and

Case Management.



10 ACTIVATION-METHOD

67 1 Optional Character Method used to activate the card.Values when activated using:P = Pinned transactionO = Online AP maintenanceS = Screen AP maintenanceB = Batch II maintenanceValues when activated using EIVR:A = ANI (Automatic Number

Identification)Q = SSN (Social Security

Number) R = SSN (last 4 digits of SSN)D = DOB (mm/dd/yy)M = MMN (all of Mother’s

Maiden Name)N = MMN (first 6 digits of MMN)Z = Zip CodeC = Cardholder’s DDA/Share

Draft #U = User-Defined Validation InfoV = Secure Code.

11 ACTIVATION-TIME-STAMP

68 8 Optional Character The time and date the card was activated. (Internal use.) Value = Space

12 PREV-TRK2-DT 76 4 Optional Character The expiration date of the previously issued card. (Internal use only.)Value = SpaceNote: If new card issue is not done via CIMS, send the old card as an Add. This field updates with the expiration date of the old card when the new one is activated via EIVR.



Input Sample

13 PREV-CRD-ACT 80 1 Optional Character The activation status of the previously issued card. (Internal use only.)Value = SpaceNote: If new card issue is not done via CIMS, send the old card as an Add. This field is updated with N for the old card when the new one is activated via EIVR.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH22B53636000000000000001 USER DEFINED 1 12121955V 0208


CH23A - Fraud Control Information


NOTE: This segment is obsolete. The following information is provided for refer-ence purposes only.

Identifiers Fields

Segment ID 23

Segment Definition FRAUDCTL

Segment Description Fraud Control Information



File segment identifier.Value = CH





4 FILE-UPDATE-CODE





7 DO-NOT-DISTURB


The expiration date for a timeframe when a customer’s normal usage pattern changes and they should not be contacted by a fraud analyst. (Determined by fraud case management.)Format = CCYYMMDD

8 IN-AUTH-REVIEW 41 1 Optional Alpha-numeric

Indicates if the transaction is being reviewed by the fraud in-authorization process. (Set by the fraud post-authorization process. Internal use only.) Value:Y = YesN = No

9 POST-AUTH-EXCLUDE


Indicates which transactions are excluded from the fraud post-authorization process. (Internal use only.) Value:Y = YesN = No

10 IN-AUTH-EXCLUDE


Indicates which transactions are excluded from the fraud in-authorization process. (Internal use only.) Value:Y = YesN = No





Input Sample

CH50A - VAU/ABU InformationThis cardholder segment is used to provide data specific to the Visa Account Updater (VAU) and MasterCard Automatic Billing Updater (ABU) services.

The host uses this segment to provide the data as specified and required by Visa and/or MasterCard.

The data items are not stored in any AP files and are not available for display in any AP query applications (For example, Cardholder Maintenance). The data items are passed through to the Card Issuance and Management System (CIMS) for use by the CIMS batch programs that generate the VAU and ABU files for Visa and MasterCard.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH23A53636000000000000001 19980116NNN

S.No Identifiers Fields

1 Segment ID 50

2 Segment Definition Not Applicable for this segment. This value is only defined and used when data is stored in AP files. That is not the case with CH50 data.

3 Segment Description Visa Account Updater/Automatic Billing Updater Information.

Field Number and Field Name Pos. Len. Status Attribute Description/Usage

1 RECORD-NAME

3 2 Req AN File identifier. Value = CH

2 SEG-ID 5 2 Req NUM Segment Identifier. Value = 50


7 1 Req AN Sub-segment identifier. Value = A


4 FILE-UPDATE-CODE

8 1 Req NUM Action code.Values: 5 = Add 6 = Delete 8 = Update

5 PAN 9 19 Req NUM This key field identifies the cardholder. For VAU/ABU, this will be the “New PAN”, depending on the VAU/ABU maintenance scenario.

Last 10 non-space digits used to determine hash field totals.

Format = Left justify trailing spaces.

Note: You cannot update this key field. Send in a Delete record followed by an Add record.

6 PLASTIC-NBR 28 5 Opt NUM Identifies the cardholder if more than one card is issued with the same PAN.

Note: This field is not passed to CIMS as it is not relevant for VAU/ABU updates.

7 VAU-ABU-IND 33 3 Req AN This field is used to indicate whether this update is for VAU or ABU.

Must contain “VAU” for Visa cards or “ABU” for MasterCard cards.

8 NEW-TRK2-DATE

36 4 Opt* AN This field is used to provide the new expiration date, when the VAU/ABU maintenance scenario requires it.

Format = YYMM

Note: For hosts that make use of the card ordering feature of CIMS, and are configured for auto reissues, CIMS will be used to provide this data.Therefore, in that situation, those hosts do not need to supply this data item.



9 OLD-PAN 40 19 Opt* AN This field is used to provide the old PAN, when the VAU/ABU maintenance scenario requires it.

Format = Left justify trailing spaces.

10 OLD-TRK2-DATE

59 4 Opt* AN This field is used to provide the old expiration date, when the VAU/ABU maintenance scenario requires it.

Format = YYMM

Note: For hosts that make use of the card ordering feature of CIMS, and are configured for auto reissues, CIMS will be used to provide this data. Therefore, in that situation, those hosts do not need to supply this data item.

11 REAS-CODE 63 1 Req AN This field is used to provide the specific VAU or ABU reason code for the update.Valid values are defined by Visa and MC.If the VAU-ABU-IND is “VAU”, the values allowed are “A”, “C”, “E” or “Q”.

A = Account number (PAN) change. The account number or account number and expiration date are being updated.

C = Closed account advice. E = Expiration date change. Q = Contact cardholder advice.

The merchant should contact the cardholder for additional information on the account.



If the VAU-ABU-IND is "ABU", the valid values allowed are "E", "B", "P", "R", "X", "Y", "C", "O", "N".

E - Update Expiration Date.The Account Number remains unchanged and only the expiration date is updated. B - Brand Flip to MasterCard. Both

(Old and New Account) records are added to the database and the New Account is the current active card.

P - Portfolio Change. The new account is the current active card.

R- Card- Replacement. The New Account is the current active card.

X- Update New Account Information Only (Update Only). Both the New Account and New Expiration Date are updated.

Y- Update Old Account Information Only (Update Only). Both the Old Account and Old Expiration Date are updated.

C- Closed Account O- Override for Deletion N- New Account (not replacing

another account). This record is indicated that the first Active Account.



Input Sample

12 REV-CODE 64 1 Opt* AN Visa has identified a separate field to indicate that a recent issuer submission was sent in error. FIS will support this situation, if the issuer chooses to use it, by adding this field to the cardholder maintenance methods.

If the VAU-ABU-IND is “VAU”, the values allowed are space or “R” (reversal of previous upate).

If the VAU-ABU-IND is "ABU", the values allowed are spaces.

13 CONV-CODE 65 1 Opt* AN Visa has identified a separate field to indicate a portfolio conversion. FIS will support this situation, if the issuer chooses to use it, by adding this field to the cardholder maintenance methods.

If the VAU-ABU-IND is “VAU”, the values allowed are space, “V” (Visa portfolio conversion) or “M” (Non-Visa portfolio conversion).

If the VAU-ABU-IND is "ABU", the values allowed are spaces.

14 FILLER 66 15 Req AN


NOTE: The status of the optional fields is subject to the Visa and MasterCard specifica-tions for VAU and ABU, respectively.

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH50A54123450000000029 VAU19094123450000000029 1909C CH50A54123450000000037 VAU19094123450000000045 1705A CH50A54123450000000029 ABU24094123450000000066 1212B CH50A54123450000000037 ABU21894123450000000037 1819E


FR01A - Fraud InformationThis fraud segment is required if your institution uses Scoring and Case Management. Any information not included will reduce the effectiveness of this service. The Fraud Information records follow the Cardholder Information records.

If you use AP screen maintenance, this information displays on the Fraud Prevention Screen (APMSC402).


Identifiers Fields

Segment ID 01

Segment Definition FRINFO

Segment Description Fraud Information



File segment identifier.Value = FR

2 SEG-ID 5 2 Required Numeric Segment identifier.Value =01




4 FILE-UPDATE-CODE





7 CUST-SINCE 33 8 Required Alpha-numeric

The date the cardholder opened their first account. Format = YYYYMMDD

8 BLANK 41 8 Not Used Alpha-numeric

Space filled to ensure 80-byte record.







12 VIP-INDICATOR 58 1 Optional Alpha-numeric

This field accepts only "Y", "N", space or "*". You can use "*" to clear the existing value.





15 TRAVEL-INDICATOR


This field accepts only "Y", "N", space or "*". You can use "*" to clear the existing value.





Input Sample

FR01B - Fraud InformationThis fraud segment is used to include the Travel Start and End date if the cardholder is going to participate the travel program.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

FR01A53636000000000000002 1998010119980101999999999Y19980101+0006000000

NOTE: B is an optional occurrence in the FR01. If it is present for FR01 in the input record then it should be the consequent to occurrence A of FR01.

Identifiers Fields

Segment ID 01

Segment Definition FRINFO

Segment Description Fraud Information


1 RECORD-NAME 3 2 Required Alpha-numeric File segment identifier.Value = FR

2 SEG-ID 5 2 Required Numeric Segment identifier.Value =01

3 OCCURRENCESECTION

7 1 Required Alpha-numeric Sub-segment identifier.Value = B

4 FILE-UPDATECODE



Input Sample

5 PAN 9 19 Required This key field identifies thecardholder. Last 10 non-space digits used as the hash field. Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.

6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. This key field number is used on rack 2 of the card’s magnetic stripe. Format = 99999Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 TRAVEL-START-DATE

333 3

8 Required Alphanumeric Travel Start date. It should not be greater than the End date.It should not be blank if travel indicator flag is "Y" and it should be blank if travel indicator flag in "N".Format = YYYYMMDD

8 TRAVEL-END-DATE

3413 8 Required Alphanumeric Travel End date. It should not be less than the Current date.It should not be blank if travel indicator flag is "Y" and it should be blank if travel indicator flag in "N".Format = YYYYMMDD

9 BLANK 49 31 Required Alphanumeric Ensures 80-byte record.Value = Spaces


1 2 3 4 5 6 7 8 9

12345678901234567890123456789012345678901234567890123456789012345678901234567890

FR01B53636000000000000002 2008011020080510


FR02A - Fraud Activity InformationThis optional segment stores cardholder activity information, including the date of the last address change. This segment is used for Scoring and Case Management.

Some of the fields in this segment can also be maintained using AP screen maintenance. If you use AP screen maintenance, this information displays on the Fraud Prevention Screen (APMSC402).


NOTE: If you add or update this segment, you must also submit the FR02B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 02

Segment Definition ACTIVITY

Segment Description Fraud Activity Information








4 FILE-UPDATE-CODE




Input Sample


7 LAST-ADDR-CHG 33 8 Required for Falcon/Fraud

Alpha-numeric

The date of the last change of address.Format = YYYYMMDDNote: This field is updated by the system if you use the CH18 segment and CIMS for card ordering.

8 LAST-PIN-CHG 41 8 Requiredfor Falcon/Fraud

Alpha-numeric

The date of the last PIN change. Format = YYYYMMDDNote: This field is updated by the system if the AP PIN Change feature is used.

9 LAST-DEP-DATE 49 8 Not Used Alpha-numeric

Note: This field is updated by the system and is intended for informational purposes only.

10 LAST-DEP-AMT 57 10 Not Used Alpha-numeric


11 LAST-AMT-DATE 67 8 Not Used Alpha-numeric





1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

FR02A53636000000000000002 200101011998010119980101+00010000019980101


FR02B - Fraud Activity Information

Some of the fields in this segment can also be maintained using AP screen maintenance. If you use AP screen maintenance, this information displays on the Fraud Prevention Screen (APMSC402).


NOTE: This segment is no longer used by the system and is for informational purposes only. However, this segment is required if you add or update a Fraud Activity Information segment (FR02A). If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 02

Segment Definition ACTIVITY

Segment Description Fraud Activity Information








4 FILE-UPDATE-CODE





7 LAST-ATM-AMT 33 10 Not Used Alpha-numeric

Amount of last withdrawal.Format = S9999999V99Note: This field is updated by the system and is intended for informational purposes only.

8 LAST-PIN-DATE 43 8 Not Used Alpha-numeric

The date of the last PINNED transaction. Format = YYYYMMDDNote: This field is updated by the system and is intended for informational purposes only.

9 LAST-PIN-AMT 51 10 Not Used Alpha-numeric

The amount of the last PINNED transaction. Format = S9999999V99Note: This field is updated by the system and is intended for informational purposes only.

10 LAST-OFLN-DATE 61 8 Not Used Alpha-numeric

The date of the last offline debit transaction used for fraud scoring. Format = YYYYMMDDNote: This field is updated by the system and is intended for informational purposes only.

11 LAST-OFLN-AMT 69 10 Not Used Alpha-numeric

The amount of the last offline debit transaction used for fraud scoring. Format = S9999999V99Note: This field is updated by the system and is intended for informational purposes only.

12 SEND-TO-CASE 79 1 Not Used Alpha-numeric

Note: This field is blank.



Input Sample

FR03A - Fraud Member InformationThis fraud segment provides cardholder information used for Scoring and Case Management. This optional segment stores cardholder verification and contact information for cardholder Member Number 2 through Member Number 4. Any information you do not include will reduce the effectiveness of the Scoring and Case Management service.

If you use AP screen maintenance, this information displays on the Fraud Member Validation Screen (APMSC403).



Ensures 80-byte record.Value = Space


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

FR02B53636000000000000002 000000330019980101000000440019980101+000004400N

NOTE: If you add or update this segment, you must also submit the FR03B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 03

Segment Definition MEMBER

Segment Description Fraud Member Information









4 FILE-UPDATE-CODE 8 1 Required Numeric Action code.Values:5 = Add6 = Delete8 = Update



7 MEMBER-NUMBER 33 2 Conditional

Numeric Value for the member number. 01 = Primary02 = Secondary03 = Third04 = FourthRequirements Notes: Required for multiple

members.



Input Sample

FR03B - Fraud Member InformationThis fraud segment is not used, but is required if you add or update a Fraud Member Information segment (FR03A).


8 WORK-PHONE 35 10 Optional Alpha-numeric

The cardholder’s business telephone number using the format AAANNNNNNN Where:A = Area CodeN = 7-digit Phone Number. Do not use hyphens.If no area code is available, enter 000 followed by the 7-digit phone number. Use for case management and card activation.

9 DATE-OF-BIRTH 45 8 Optional Alpha-numeric

The birth date for member numbers 02, 03, and 04. Used for case management.Format = YYYYMMDD

10 SOCIAL-SECURITY-NUMBER

53 9 Optional Numeric The cardholder’s 9-digit social security number used for case management.Format = 999999999

11 MAIDEN-NAME 62 17 Optional Alpha-numeric

The maiden name for members 02, 03, and 04. Used for case management.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

FR03A523232323232323232396666604414555121219751221398765555WASHINGTON


Identifiers Fields

Segment ID 03

Segment Definition MEMBER

Segment Description Fraud Member Information








4 FILE-UPDATE-CODE



6 PLASTIC-NBR 28 5 Optional Numeric Identifies the cardholder if more than one card is issued with the same PAN. The number used on Track 2 of the card’s magnetic stripe.Format = 99999Note: You cannot update this key field. Send in a Delete record followed by an Add. Do not use for Visa Check™ or Debit MasterCard® cards.

7 USER-DEFINED VALIDATION

33 25 Not Used Alpha-numeric





Input Sample

AD01A - Account DetailThis account detail segment provides account and balance information at the account level. The account level information includes account balances, overdraft information, credit line, account status, and account level access. This segment is required for the initial load and ongoing maintenance if you maintain balances with AP, or use the account hold features but are not submitting a balance refresh file. The host uses this segment to update the corresponding fields in the Account Detail File.

FIS recommends setting up an overdraft account for the cardholder rather than including those funds in the cardholder’s available balance. FIS also suggests using the Balance Refresh File to update an account balance rather then sending in the account detail segments. For additional information, see Chapter 5, “Using Balance Refresh."

If you use AP screen maintenance, the updated fields display on the Account Detail Information screen (APMSC051).


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

FR03B5232323232323232323966666USER VALIDATION FIELD

NOTE: If you add or update an Account Detail Transaction segment (AD01A or AD01B), you must submit all or the required records for that seg-ment even if you are not changing that record’s information. For exam-ple, if you update AD01A, you must submit the required AD01B record. If any of the required records are not submitted, the update is rejected.

Identifiers Fields

Segment ID 01

Segment Definition ACCTDTL

Segment Description Account Detail Information



File segment identifier.Value = AD






4 FILE-UPDATE-CODE

8 1 Required Numeric Action codeValues:5 = Add6 = Delete8 = UpdateNote: If adding an account to an existing cardholder, this field must be set to 5 and segments CH03A/B sent.

5 FI-ID 9 10 Required Alpha-numeric

The routing/transit number of the institution issuing the card. Identifies the financial institution holding the account.Format = 1NNNNNNNNCNote: You cannot update this key field.

6 ACCNT-TYPE 19 4 Required Alpha-numeric

A valid account type for institutions maintaining account balances on AP or a dummy account type for institutions not keeping balances on AP. Must match the ACCT-TYPE field in segment “CH03A - Account Information” on page 145.Note: You cannot update this key field.


The cardholder’s account number. This account identifier must match the ACCT-NO in “CH03A - Account Information” on page 145. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.



8 LED-BAL-1 51 10 Optional Alpha-numeric

The ledger balance amount for this account. The balance after posted activity, used as specified in AP parameters. The right-most 2 digits are cents.Format = S9999999V99S = Sign (+, -, C = Credit, D = Debit, or space = positive)9 = NumberV = Decimal Point Note: FIS recommends setting up an overdraft account for a cardholder rather than including those funds in the cardholder’s available balance. FIS also suggests using the Balance Refresh file to update an account balance rather then sending in the account detail segments.+ or - sign is used to Replace the Balance. C or D sign is used to Update the Balance. If both the balances are updated ensure that C/D sign is used for both the balances.Do not use + or - sign for one Balance and C/D sign for another Balance since Balance update involves: First calculation of the Latest

Balance (for both Ledger & Available) including Balance from the Balance refresh file and posting of Unposted amounts to the Balance.

Performing the Credit/Debit to the Latest Balance.



9 AVAL-BAL-1 61 10 Optional Alpha-numeric

The available balance amount for this account. Balance after posted or unposted activity, used as specified in AP parameters. The right-most 2 digits are cents.Format = S9999999V99S = Sign (+, -, C = Credit, D = Debit, or space = positive)9 = NumberV = Decimal Point Note: FIS recommends setting up an overdraft account for a cardholder rather than including those funds in the cardholder’s available balance. FIS also suggests using the Balance Refresh file to update an account balance rather then sending in the account detail segments.+ or - sign is used to Replace the Balance. C or D sign is used to Update the Balance. If both the balances are updated ensure that C/D sign is used for both the balances.Do not use + or - sign for one Balance and C/D sign for another Balance since Balance update involves: First calculation of the Latest

Balance (for both Ledger & Available) including Balance from the Balance refresh file and posting of Unposted amounts to the Balance.

Performing the Credit/Debit to the Latest Balance.



Input Sample

AD01B - Account DetailThis account detail segment stores account restrictions and overdraft amount information at the account level. This segment is used if your institution maintains balances with AP, or if you use the account hold feature but do not submit a balance refresh file. An overdraft amount balance is not reflected in the available balance displayed at the terminal. The host uses this record layout to update the corresponding fields in the Account Detail file.

If your institution uses AP to perform daily balance updates, FIS suggests setting up an overdraft account for a cardholder rather than including those funds in the cardholder’s available balance. FIS also recommends using the Balance Refresh file to update an account balance rather then sending in the account detail segments. For additional information, see Chapter 5, “Using Balance Refresh."

10 CREDIT-LINE-AMNT-1


The credit line or overdraft amount for this account. The right-most 2 digits are cents.Format = S9999999V99S = Sign (+, -, or space = positive)9 = NumberV = Decimal Point Note: FIS recommends setting up an overdraft account for a cardholder rather than including those funds in the cardholder’s available balance. FIS also suggests using the Balance Refresh file to update an account balance rather then sending in the account detail segments.


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

AD01A51000004352DDA DDA-ACCNT-1 +010000000+010000000+000000000




NOTE: If you add or update an Account Detail Transaction segment (AD01A or AD01B), you must submit all of the required records for that seg-ment even if you are not changing that record’s information. For exam-ple, if you update AD01B, you must submit the required AD01A record. If any of the required records are not submitted, the update is rejected. Always submit the account detail segments after the cardholder seg-ments.

Identifiers Fields

Segment ID 01

Segment Definition ACCTDTL




File identifier.Value = AD





4 FILE-UPDATE-CODE

8 1 Required Numeric Action code.Values:5 = Add6 = Delete8 = UpdateNote: If adding an account to an existing cardholder, this field must contain a 5 and segments CH03A/B sent.





Identifies the service line that must match the ACCT-TYPE field in segment “CH03A - Account Information” on page 145.Note: You cannot update this key field.


The cardholder’s account number. This account identifier must match the ACCT-NO in “CH03A - Account Information” on page 145. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 ACCT-STATUS 51 2 Optional Alpha-numeric

Two-character reject reason code. See “Codes” on page 271 in Appendix C.

9 ACCT-ACCESS 53 10 Required Alpha-numeric

At least one access is required for an Add.Values:1 or Y = Access

9a WITH-DRAWAL 53 1 Optional Alpha-numeric

Indicates if account is used for withdrawals. Values:1 or Y = Withdrawal Access0 or N = No Withdrawal AccessBlank = No Change


Indicates if account is used for deposits. Values:1 or Y = Deposit Access0 or N = No Deposit AccessBlank = No Change



9c BAL-INQUIRY 55 1 Optional Alpha-numeric

Indicates if the cardholder can inquire about the account balance. Values:1 or Y = Inquiry Access0 or N = No Inquiry AccessBlank = No Change

9d PAYMENTS-TO 56 1 Optional Alpha-numeric

Indicates if payments can be made to the account. Values:1 or Y = Payment Access0 or N = No Payment AccessBlank = No Change

9e PAYMENTS-FROM


Indicates if payments can be made from the account. Values:1 or Y = Payment Access0 or N = No Payment AccessBlank = No Change


Indicates if funds can be transferred to the account. Values:1 or Y = Transfer Access0 or N = No Transfer AccessBlank = No Change

9g TRANSFER-FROM


Indicates if funds can be transferred from the account Values:1 or Y = Transfer Access0 or N = No Transfer AccessBlank = No Change

9h PURCHASE 60 1 Optional Alpha-numeric

Indicates if purchases can be made from this account. Values:1 or Y = Purchase Access0 or N = No Purchase AccessBlank = No Change

9I 3RD-PARTY PAYMENT

61 1 Optional Character Indicates if third-party payments can be made from the account.Values:1 or Y = Payment Access0 or N = No Payment AccessBlank = No Change

9j FUTURE 62 7 Optional Alpha-numeric

Value = 7 spaces



Input Sample

9k OD-AMNT 69 10 Optional Alpha-numeric

Amount the account can be overdrawn before going to the overdraft account or rejecting the transaction. The right-most 2 digits are cents.Format: - S9999999V99S = Sign (+, -, or space = positive)9 = NumberV = Decimal Point




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

AD01B51000004352SAV SAV-ACCNT-1A 111111111


AD02A - Account Detail Overdraft InformationThis overdraft segment stores the cardholder’s overdraft account information and is optional after the initial setup. The account information can be used by another service line and reside at another institution. The host uses this segment to update the corresponding fields in the Account Detail File.

If your institution uses AP to perform daily balance updates, FIS suggests setting up an overdraft account for a cardholder rather than including those funds in the cardholder’s available balance. FIS also recommends using the Balance Refresh file to update an account balance rather then sending in the account detail segments. For additional information, see Chapter 5, “Using Balance Refresh."



NOTE: If you add or update an Overdraft Information segment (AD02A or AD02B), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update AD02A, you must submit the required AD02B record. If any of the required records are not submitted, the update is rejected. Always submit the account detail segments after the cardholder seg-ments.

Identifiers Fields

Segment ID 02

Segment Definition OVERDRFT










4 FILE-UPDATE-CODE





The service line identifier that must match the ACCT-TYPE field in segment “CH03A - Account Information” on page 145.Note: You cannot update this key field.


The cardholder’s account number. This account identifier must match the ACCT-NO field in segment “CH03A - Account Information” on page 145. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 FI-ID 51 10 Conditional Alpha-numeric

The routing/transit number of the institution issuing the card.Requirements Notes: Required for Update.

9 ACCNT-TYPE 61 4 Conditional Alpha-numeric

An institution-assigned code that corresponds to the host’s file.Requirements Notes: Required for Update.

10 Blank 65 16 Required Alpha-numeric




Input Sample

AD02B - Account Detail Overdraft InformationThis overdraft segment stores overdraft account information and is optional after the initial setup. This account information can be used by another service line and reside at another institution. The host uses this segment to update the corresponding fields in the Account Detail file.

If your institution uses AP to perform daily balance updates, FIS suggests setting up an overdraft account for your cardholders rather than including those funds in the cardholder’s available balance. FIS recommends using the Balance Refresh file to update an account balance rather then sending in the account detail segments. For additional information, see Chapter 5, “Using Balance Refresh."



1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

AD02A51000004352DDA 12358671 1000004352SAV

NOTE: If you add or update an Overdraft Information segment (AD02A or AD02B), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update AD02B, you must submit the required AD02A record. If any of the required records are not submitted, the update is rejected. Always submit the account detail segments after the cardholder seg-ments.

Identifiers Fields

Segment ID 02

Segment Definition OVERDRFT










4 FILE-UPDATE-CODE



The routing and transit number of the institution issuing the card. Identifies the financial institution holding the account.Format = 1NNNNNNNNCNote: You cannot update this key field.

6 ACCT-TYPE 19 4 Required Alpha-numeric

Identifies the service line that must match the OAR SELECT-TYPE field in segment “CH03A - Account Information” on page 145.Note: You cannot update this key field.


The cardholder’s account number. This account identifier must match the ACCT-NO field from segment “CH03A - Account Information” on page 145. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.


Identifies the overdraft account number.

9 Blank 79 2 Required Alpha-numeric



Input Sample

AD03A - Account Detail Hold List InformationThis hold list segment stores any holds against the account specified in the segments AD01A and AD01B. These holds are matched when an item is settled, but can also expire automatically. The host uses this segment to update the corresponding fields in the Account Detail File.

If you use AP screen maintenance, the updated fields display on the Hold List Information screen (APMSC052).


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

AD02B51000004352DDA 12258671 10214567

NOTE: Segment AD03A is only used to delete account hold information. AP Batch Maintenance does not support adding or updating account hold information using segment AD03A. The only file update code available for AD03A is delete (6).

Identifiers Fields

Segment ID 03

Segment Definition ACCTHOLD










4 FILE-UPDATE-CODE 8 1 Required Numeric Action code.Value:6 = DeleteNote: You cannot add or update this segment.


This key field is the routing and transit number of the institution issuing the card. Identifies the financial institution holding the account.Format = 1NNNNNNNNCNote: You cannot update this key field.




This identifier is the cardholder’s account number and it must match the ACCT-NO field in segment “CH03A - Account Information” on page 145. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 PRIMARY-ACCOUNT-NUMBER



9 CARD-ACCEPTOR-ID 63 15 Required Alpha-numeric




10 PREAUTH-INDICATOR 78 1 Optional Alpha-numeric

Match the hold with the settled transaction.Values:P = Pre-AuthorizedV = Visa Check™M = Debit MasterCard®Note: You cannot update this key field.

11 TERMINAL-DAY 79 2 Required Alpha-numeric




Input Sample

AD03B - Account Detail Hold ListThis optional account detail segment is used to store any holds against the account specified in the AD01 segments. These holds are matched when an item is settled, but can also expire automatically. The host uses this segment to update the corresponding fields in the Account Detail File.

If you use AP screen maintenance, the updated fields display on the Hold List Information screen (APMSC052).


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

AD03A61000000233DDA 1237810001 00000000000100482700 V01

NOTE: Segment AD03A is only used to delete account hold information. AP Batch Maintenance does not support adding or updating account hold information using segment AD03A. The only file update code available for AD03B is delete (6).

Identifiers Fields

Segment ID 03

Segment Definition ACCTHOLD










Input Sample

4 FILE-UPDATE-CODE

8 1 Required Numeric Action code.Value:6 = Delete






The cardholder’s account number. This account identifier must match the ACCT-NO field in segment “CH03A - Account Information” on page 145. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 AUTH-NO 51 6 Optional Alpha-numeric

The FINIPC’s authorization number of the transaction that caused the hold. Match the hold with the settled transaction.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

AD03B61000000233DDA 1237810001 000527


AD06A - Additional Hold InformationThis optional segment stores additional information about a hold (AD03 record) against the account specified in the segments AD01A and AD01B. This AD06 record can be linked to a corresponding AD03 record via the 36 bytes of match data(i.e. all of AD06A and the first 6 bytes of AD06B). The AD06 segment has no purpose without a corresponding AD03 segment but is NOT required if AD03 is present.

There is no AP screen maintenance supported with this segment.


NOTE: Segment AD06A is only used to delete additional account hold informa-tion. AP Batch Maintenance does not support adding or updating addi-tional account hold information using segment AD06A. The only file update code available for AD06A is delete (6).

Identifiers Fields

Segment ID 06

Segment Definition ADDLHOLD

Segment Description Additional Hold Information








4 FILE-UPDATE-CODE 8 1 Required Numeric Action code.Value:6 = DeleteNote: You cannot add or update this segment.



This key field is the routing and transit number of the institution issuing the card. Identifies the financial institution holding the account.Format = 1NNNNNNNNCNote: You cannot update this key field.


The service line identifier that must match the ACCT-TYPE field in segment CH03A - Account Information.Note: You cannot update this key field.


This identifier is the cardholder’s account number and it must match the ACCT-NO field in segment CH30A - Account Information. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 PRIMARY-ACCOUNT-NUMBER





Input Sample

9 CARD-ACCEPTOR-ID 63 15 Required Alpha-numeric


10 PREAUTH-INDICATOR 78 1 Optional Alpha-numeric

Match the hold with the settled transaction.Values:P = Pre-AuthorizedV = Visa Check™M = Debit MasterCard®Note: You cannot update this key field.

11 TERMINAL-DAY 79 2 Required Alpha-numeric



1 2 3 4 5 6 7 8

12345678901234567890123456789012345678901234567890123456789012345678901234567890

AD06A61000000233DDA 1237810001 00000000000100482700 V01


AD06B - Additional Hold InformationThis optional account detail segment is used to store additional hold information against the account specified in the AD01 segments. These holds are matched when an item is settled, but can also expire automatically. The host uses this segment to update the corresponding fields in the Account Detail File.

There is no AP screen maintenance supported for this data.


NOTE: Segment AD06B is only used to delete account hold information. AP Batch Maintenance does not support adding or updating account hold information using segment AD06B. The only file update code available for AD06B is delete (6).

Identifiers Fields

Segment ID 06


Segment Description Additional Account Hold Information








4 FILE-UPDATE-CODE 8 1 Required Numeric Action code.Value:6 = Delete




Input Sample

AD06C - Additional Hold InformationThis optional account detail segment is used to store additional hold information against the account specified in the AD01 segments. This data is the merchant code and name associated with the account hold.




The cardholder’s account number. This account identifier must match the ACCT-NO field in segment CH03A - Account Information. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 AUTH-NO 51 6 Required Alpha-numeric

The FINIPC’s authorization number of the transaction that caused the hold. Match the hold with the settled transaction.

9 HOLD-STATUS 57 1 Optional Alpha-numeric

The current status of the holdA = activeE = expired

10 CREATE-TIME 58 8 Optional Alpha-numeric

Date the hold was created. In YYYYMMDD formatValue = YYYYMMDD


Ensures 80-byte recordValue = Spaces


1 2 3 4 5 6 7 8

12345678901234567890123456789012345678901234567890123456789012345678901234567890

AD06B61000000233DDA 1237810001 000527E20050412




NOTE: Segment AD06C is only used to delete account hold information. AP Batch Maintenance does not support adding or updating account hold information using segment AD06C. The only file update code available for AD06C is delete (6).

Identifiers Fields

Segment ID 06









Sub-segment identifier.Value = C

4 FILE-UPDATE-CODE

8 1 Required Numeric Action code.Value:6 = Delete






Input Sample

AD06D - Additional Hold InformationThis optional account detail segment is used to store additional hold information against the account specified in the AD01 segments. This data is user ID who expired hold (if the hold has been manually expired).




The cardholder’s account number. This account identifier must match the ACCT-NO field in segment CH03A - Account Information. Credit Unions use the base account number plus the account suffix.Note: You cannot update this key field.

8 MERCHANT-CODE


The merchant code (aka ‘SIC’) associated with the hold record.

9 MERCHANT-NAME


The merchant name associated with the hold record.




1 2 3 4 5 6 7 8

12345678901234567890123456789012345678901234567890123456789012345678901234567890

AD06C61000000233DDA 1237810001 6012JIM’s Bakery

NOTE: Segment AD06D is only used to delete account hold information. AP Batch Maintenance does not support adding or updating account hold information using segment AD06D. The only file update code available for AD06D is delete (6).


Input Sample

AD08 - Host Balance Update SegmentThis account detail segment stores host balance update information in the AD08 segments. The online uses of this segment is to calculate the hold amounts for balance calculation in the Account Detail File.


Identifiers Fields

Segment ID 06





2 SEG-ID 5 2 Required Numeric

3 OCCURRENCE-SECTION 7 1 Required Alpha-numeric

4 FILE-UPDATE-CODE 8 1 Required Numeric




8 USER-ID 51 30 Optional Alpha-numeric

1 2 3 4 5 6 7 8

12345678901234567890123456789012345678901234567890123456789012345678901234567890

AD06D61000000233DDA 1237810001 [email protected]

Identifiers Fields

Segment ID 08

Segment Definition HOSTBALU



Input Sample


1 RECORD-NAME 3 2 Required Alpha-numeric File segment identifier.Value = AD

2 SEG-ID 5 2 Required Numeric Segment Identifier.Value = 08

3 OCCURRENCE-SECTION 7 1 Required Alpha-numeric Sub-segment identifier.Value = A

4 FILE-UPDATE-CODE 8 1 Required Numeric Action code values.Value:6 = Delete

5 FI-ID 9 10 Required Alpha-numeric The routing and transit number of the FI issuing card.

6 ACCT-TYPE 19 4 Required Alpha-numeric The service line identifier. This number must match the ACCT-TYPE field in segment CH03A - Account Information.

7 ACCT-NO 23 28 Required Alpha-numeric The cardholder’s account number. This number must match the ACCT-NO field in segment CH03A - Account Information.

8 UPDATED-TIMESTAMP 51 8 Required Date This shows the account balance updated timestamp.

1 2 3 4 5 6 7 8

12345678901234567890123456789012345678901234567890123456789012345678901234567890

AD08A51101007041DDA DDA-THR-01a 20060830


CH1AA - Consolidated AVS GroupThe optional address verification segment is used to update the cardholder’s name and address information and is an alternative to the Card Management Group and Card Management Member Information segments, CH18 and CH19. Only institutions using AP exclusively for address verification should use the Consolidated AVS Group segments.

Do not send segment CH01 with the Consolidated AVS Group segments if the Create CH01 field in the header record is set to Yes.

Do not send segment CH08 with the Consolidated AVS Group segments if your institution uses name search.

Do not send a Consolidated AVS Group segment if your institution uses CIMS.


NOTE: If you add or update a Consolidated AVS Group segment (CH1AA or CH1AC), you must submit all of the required records for that segment even if you are not changing that record’s information. For example, if you update CH1AA, you must submit the required CH1AC record. If any of the required records are not submitted, the update is rejected.

CH1AB is an optional record and should only be submitted for an update if you submitted this record when the cardholder was origi-nally added.

Identifiers Fields

Segment ID 1A

Segment Description Address Verification Information




2 SEG-ID 5 2 Required Alpha-numeric

Segment identifier.Value = 1A





Input Sample

4 FILE-UPDATE-CODE




7 CARDHOLDER NAME-LAST


The cardholder’s last name. Updates the corresponding field in the cardholder file.


The cardholder’s street address. Updates the corresponding field in the cardholder file.


Ensures 80-byte record.Value = Space


1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH1AA5232323232323232323966666SMITH 1234 NORTH MAIN STREET


CH1AB - Consolidated AVS GroupThe optional address verification segment is used to update the cardholder’s name and address information and is an alternative to the Card Management Group and Card Management Member Information segments, CH18 and CH19. Only institutions using AP exclusively for address verification should use the Consolidated AVS Group segments.

Do not send segments CH01 or CH08 with the Consolidated AVS Group segments. Do not send a Consolidated AVS Group segment if your institution uses CIMS.


NOTE: If you add or update the Consolidated AVS Group segments (CH1AA or CH1AC), you must submit all of the records for that segment even if you are not changing that record’s information. For example, if you update CH1AA, you must submit the required CH1AC record. If any of the required records are not submitted, the update is rejected.

CH1AB is an optional record and should only be submitted for an update if you submitted this record when the cardholder was origi-nally added.

Identifiers Fields

Segment ID 1B










4 FILE-UPDATE-CODE



Input Sample

CH1AC - Consolidated AVS GroupThe optional address verification segment is used to update the cardholder’s name and address information and is an alternative to the Card Management Group and Card Management Member Information segments, CH18 and CH19. Only institutions using AP exclusively for address verification should use the Consolidated AVS Group segments.

Do not send segments CH01 or CH08 with the Consolidated AVS Group segments. Do not send a Consolidated AVS Group segment if you are using the Card

Issuance and Management System.

5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits used as the hash field. Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.



The cardholder’s street address. Updates the corresponding field in the cardholder file.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH1AB52323232323232323239666661234 NORTH MAIN STREET



NOTE: If you add or update the Consolidated AVS Group segments (CH1AA or CH1AC), you must submit all of the records for that segment even if you are not changing that record’s information. For example, if you update CH1AA, you must submit the required CH1AC record. If any of the required records are not submitted, the update is rejected.

CH1AB is an optional segment and should only be submitted for an update if you submitted this record when the cardholder was origi-nally added.

Identifiers Fields

Segment ID 1C









Sub-segment identifier.Value = C

4 FILE-UPDATE-CODE


5 PAN 9 19 Required Numeric This key field identifies the cardholder. Last 10 non-space digits used as the hash field. Format = 9999999999999999999Note: You cannot update this key field. Send in a Delete record followed by an Add.



7 CITY 33 19 Required Alpha-numeric

The name of the city where the cardholder resides. Updates corresponding field in the cardholder file. (If international, enter city and country.)

8 STATE 52 2 Required Alpha-numeric

The cardholder’s 2-character state code. Updates corresponding field in the cardholder file.** = International

9 ZIP-CODE 54 9 Conditional Alpha-numeric

The cardholder’s zip code. Requirements Notes: Required for USA residents.

10 CARDHOLDER NAME-FIRST


The cardholder’s first name.

11 CARDHOLDER NAME-MIDDLE INITIAL


The cardholder’s middle initial.



Input Sample

12 CI-STATUS 76 2 Optional Alpha-numeric

Reject or capture card if hot- or warm-carding.Values:Blank fill or * = Normal Card or No ChangeAK = Capture Hot CardNK = No Capture Hot CardNote: See “Reject Reason Codes” on page 271 in Appendix C for a complete list of reject reason code values.Additional Note:If an update changes the value from blank to NK (per CED setting), and a second update changes other fields but not this field, Visa and MasterCard would consider the second update one for an existing record.




1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

CH1AC5232323232323232323966666CITY ST999999999JOHN AK


B
Error and Informational Messages
This appendix contains error and informational messages that can occur while processing the maintenance.

AP Message TypesThe following messages and their prefixes are used for AP maintenance.

AP Batch Messages

APB-018 - AP DATABASE RECORD ALREADY EXISTS

This message indicates that the program attempted to add a new AP Cardholder or Account Detail record and the record already exists. The add was performed because the Segment ID and the file update code in the batch record required that the associated database record not exist. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-019 - EXCEEDED 100 OUTSTANDING FILE OPERATIONS

This message indicates that the program encountered an unrecoverable internal error in managing the paths to multiple AP database files. I/O operations that are initiated by the program are never completed by the program. The program will terminate after reporting the error.

Prefix Format Message Source Documented

AP### AP Compiler AP Parameters Reference Manual

AP## Network Monitor Network Messages Manual

APB### AP Batch Maintenance This appendix

APM### AP Maintenance System AP Maintenance User’s Manual

BU## Balance Update This appendix


APB-020 - INVALID RECORD NAME

This message indicates that a batch record contained a missing or invalid record name value. The valid values are CH or AD. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-021 - INVALID SEGMENT ID

This message indicates that a batch record contained a missing or invalid Segment ID value. The valid values are defined in the Batch Maintenance section of the AP Maintenance User’s Guide. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-022 - INVALID OR UNEXPECTED OCCURRENCE SECTION

This message indicates that a batch record contained a missing, invalid or unexpected (not in sequence) occurrence section value. The valid values are dependent on the specific segment and are defined in the Batch Maintenance section of the AP Maintenance User’s Guide. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-023 - INVALID FILE UPDATE CODE

This message indicates that a batch record contained a missing or invalid file update code value. The valid values are 5 (add), 6 (delete), and 8 (update). The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-024 - ADD OPERATION REQUIRES ADD FILE UPDATE CODE

This message indicates that a batch record with a file update code other than 5 (add) was encountered during the execution of the program in the initial mode. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-025 - INVALID PIN AUTHORIZATION FLAG

This message indicates that the PIN authorization flag value in a CH02 batch record was missing or invalid. The valid values are 00, 01, or 99. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-026 - INVALID LEDGER BALANCE

This message indicates that the ledger balance value in a AD01A batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-027 - INVALID AVAILABLE BALANCE

This message indicates that the available balance value in a AD01A batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-028 - INVALID CREDIT LINE AMOUNT

This message indicates that the credit line amount value in a AD01A batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-029 - INVALID OVERDRAFT AMOUNT

This message indicates that the overdraft amount value in a AD01B batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-030 - INVALID CARDHOLDER PAN/PLASTIC NUMBER

This message indicates that the Primary Message Control (PMC) Pathway server process was unable to derive the financial institution and AP card group from the Environmental Database given the PAN and plastic number in the CH batch record. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-031 - INVALID LIMIT AMOUNT

This message indicates that the limit amount value in a CH04 batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-032 - INVALID LIMIT USES

This message indicates that the limit uses value in a CH04 batch record was nonnumeric. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-033 - INVALID INCREMENT AMOUNT

This message indicates that the increment amount value in a CH04 batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-034 - INVALID MINIMUM AMOUNT

This message indicates that the minimum amount value in a CH04 batch record was invalid. The Batch Maintenance section of the AP Maintenance User’s Guide defines the acceptable format for amount values. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-035 - INVALID DEPOSIT PERCENTAGE

This message indicates that the deposit percentage value in a CH04 batch record was not a value between 0 and 100 inclusive. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-036 - EXCEEDED 200 BATCH RECORDS PER CH/AD RECORD

This message indicates that the program accumulated more than 200 batch records for a single cardholder/account. The accumulation occurs in a fixed table for the purpose of reporting all of the batch records that were rejected as a result of an error in processing the cardholder/account. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-037 - EXCEEDED 100 LOG RECORDS PER CH/AD RECORD

This message indicates that the program accumulated more than 100 log records containing before/after images of the database record that is currently being processed. The condition indicates that more than 100 segment occurrences were maintained for a given cardholder/account and most likely indicates a problem in the creation of the batch input file. The program will terminate after reporting the error.


APB-038 - FIRST RECORD IS NOT A SEGMENT 01 RECORD

This message indicates that the program is being executed in the initial mode and the first batch record encountered for a given cardholder/account was not a segment 01 record. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-039 - EXCEEDED 32000 EDIT TABLE ENTRIES

This message indicates that the program attempted to load more than 32000 AP Maintenance Edit (APME) records into a fixed extended memory table. The load process in invoked if the PARAM EDIT ON command is entered. The program will terminate after reporting the error.

APB-040 - OCCURRENCE DOES NOT EXIST

This message indicates that the program attempted to update or delete a non-existent AP Cardholder or Account Detail segment occurrence. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-041 - OCCURRENCE ALREADY EXISTS

This message indicates that the program attempted to add an AP Cardholder or Account Detail segment occurrence that already exists. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-042 - IDENTIFER DOES NOT EXIST (xxxxxxxxxx)

This message indicates that the specified identifier does not exist in the AP Maintenance Edit file, which is created by the AP Parameter Compiler (APPC) from the AP Parameter file. The program validates all AP Parameter defined identifiers if the PARAM EDIT ON command was entered. Examples of identifiers include financial institution ID, limit group, limit type ID, account type. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-043 - INVALID CARD/ACCOUNT STATUS CODE

This message indicates that the 2-byte status code value in a CH01 or AD01A batch record is either not alphanumeric or is an “**” (clear status) on an add operation. See Appendix C of the AP Parameter Reference Manual for definitions of all the valid status (reject reason) codes. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-044 - INVALID CARD/ACCOUNT ACCESS(ES)

This message indicates that one or more of the access types in a CH01, CH03B, or AD01B batch record is not valid. An access type is defined by a one-byte field, which can contain a blank, “0” (no), “1” (yes), “N” (no), or “Y” (yes) value. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-045 - CARD/ACCOUNT DOES NOT HAVE AN ACCESS

This message indicates that the cardholder/account will not have at least one access type bit set (yes) after the access types in the CH01, CH03B, or AD01B batch record are applied to the database record. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-046 - INVALID FINANCIAL INSTITUTION ID

This message indicates that a batch record is missing a financial institution ID. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-047 - INVALID ACCOUNT TYPE

This message indicates that a batch record is missing an account type. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-048 - INVALID ACCOUNT NUMBER

This message indicates that a batch record is missing an account number. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-049 - INVALID CARD/ACCOUNT HOLD MATCH DATA

This message indicates that a batch record is missing an card/account hold match data. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-050 - INVALID OAR SELECT TYPE

This message indicates that the OAR select type value in a CH03A batch record is not “CRD”, “DDA”, “OTH”, or “SAV”. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-051 - INVALID PRIMARY ACCOUNT INDICATOR

This message indicates that the primary account indicator in a CH03A batch record is not “Y” or “N.” The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-052 - INVALID FUNDING ACCOUNT INDICATOR

This message indicates that the funding account indicator in a CH03A batch record is not “Y” or “N.” The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-053 - INVALID ACCESS GROUP

This message indicates that the access group ID in a CH14 batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-054 - INVALID LIMIT GROUP ID

This message indicates that the limit group ID in a CH01 batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-055 - INVALID DATE FORMAT/VALUE (YYMM)

This message indicates that the year and/or month value in a CH02 batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-056 - INVALID LIMIT TYPE ID

This message indicates that the limit type ID value in a CH04 batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-057 - INVALID CARDHOLDER ADDRESS

This message indicates that the cardholder address in the CH18A batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-058 - INVALID CARDHOLDER CITY

This message indicates that the cardholder’s city in the CH18C batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-059 - INVALID CARDHOLDER STATE

This message indicates that the cardholder state code in the CH18C batch record is invalid or missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-060 - INVALID CARDHOLDER ZIP CODE

This message indicates that the CH18C batch record contains a non-numeric cardholder zip code. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-061 - INVALID CARD CONDITION STATUS

This message indicates that the card condition status in the CH18C batch record is not “0”, “1”, or “2”. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-062 - INVALID AUTOMATIC ISSUE INDICATOR

This message indicates that the automatic issue indicator in the CH18C batch record is not “Y” or “N” (upper or lower case). The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-063 - INVALID MEMBER NUMBER

This message indicates that the member number in the CH19A batch record is not 01, 02, 03, or 04. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-064 - INVALID CARDHOLDER NAME

This message indicates that the cardholder first and/or last name in the CH19A batch record is missing. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-065 - INVALID CARD ORDER TYPE

This message indicates that the card order type in the CH19A batch record is not any of the following values including B, C, P, G, H, V, or W. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-066 - INVALID CARD ORDER STATUS

This message indicates that the card order status in the CH19A batch record is not 0, 1, 2, 3, or 4. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-067 - INVALID CARD ISSUE REASON

This message indicates that the card issue reason in the CH19B batch record is not {0, 1, 2, 3, or 4}. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-068 - INVALID CARD REPLACEMENT INDICATOR

This message indicates that the card replacement indicator in the CH19B batch record is not “Y” or “N” (upper or lower case). The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-069 - INVALID CARDHOLDER SEX

This message indicates that the cardholder sex in the CH20 batch record is not “M” or “F” (upper or lower case). The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-070 - INVALID MARITAL STATUS

This message indicates that the cardholder marital status in the CH20 batch record is not D, M, S, or W (upper or lower case). The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-071 - INVALID EDUCATION LEVEL

This message indicates that the cardholder education level in the CH20 batch record is not 1, 2, 3, 4, or 5. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.


APB-072 - INVALID INCOME RANGE

This message indicates that the income range in the CH20 batch record is not included in the range of 1 to 10. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-073 - INVALID FAMILY SIZE

This message indicates that the cardholder family size in the CH20 batch record is non-numeric. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-074 - INVALID CARDHOLDER DISTANCE

This message indicates that the cardholder distance in the CH20 batch record is non-numeric. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-075 - INVALID RESIDENCE STATUS

This message indicates that the cardholder residence status in the CH20 batch record is not 0, 1, or 2. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-076 - INVALID EMPLOYMENT STATUS

This message indicates that the cardholder employment status in the CH20 batch record is not 0, 1, 2, 3, or 4. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-077 - INVALID DATE FORMAT/VALUE (YYYYMMDD)

This message indicates that the year, month, and or day value in the CH19A batch record is invalid. The program will reject and report all of the batch records associated with the cardholder/account and continue processing the next cardholder/account.

APB-078 - CONTROL NUMBER DOES NOT EXIST (AUTOMATIC FORCE)

This message indicates that the control number in the batch file header record does not exist. The program will automatically change the control option specified in the PARAM CONTROL TACL command to “FORCE.” This will cause the control number in the control/activity file (ASSIGN APBC file) to be replaced with blanks.


APB-079 - CONTROL NUMBER MISMATCH (PREVIOUS/CURRENT: ###/###)

This message indicates that the control number in the batch file header record is not “1” more than the control number in the control/activity file (ASSIGN APBC file) and the “CHECK” option was specified on the PARAM CONTROL TACL command. The program will terminate after reporting the error.

APB-080 - FAILED TO FIND INST/CARD GROUP

This message indicates that the FI and/or a card group are not found in the CED database. Verify the FI and the card group within CED.

APB-081 - FAILED TO FIND DEFAULT LMTGRP

This message indicates that a limit group cannot be found for this institution. Verify the limit group in the AP Parameter file.

APB-082 - INVALID CARD ACTIVATION

This message indicates that the card activation field in segment CH01A has not been set. Set the card activation field to Yes or No and resubmit.

APB-083 - ADA RECORD ALREADY EXISTS IN APADAA FILE

This message indicates that a CH08A or a CH03A record is processed with Alternate Database Access and the specified account number or cardholder name already exists in the APADAA File. Have operation must run the APADAJ Utility.

APB-084 - CARDHOLDER NAME NOT FORMATTED CORRECTLY

This message indicates that when AP Batch II processes a CH08 record and Cardholder Name access (ADATYPE=CN) is allowed, the CH08 records are required to be in a format using delimiters (“/”) for separating the name fields. The record is not formatted correctly.

APB-085 - CARDMAN=Y, CH1AA/AB/AC NOT PERMITTED

This message indicates that the AP Batch II input file contains the consolidated AVS group records for an institution using CIMS (i.e. CARDMAN=Y in the AP Parameter file). This is not permitted.

APB-086 - EXCEEDED 50 BALANCE UPDATE FILES

This message indicates that when AP Batch II processed this input file, the limit of 50 balance update files was exceeded. An AP Batch II input file cannot contain maintain records for a number of institutions whose sum total of balance update files would exceed 50. Divide the balance update files into more than one AP Batch II input file and resubmit.


APB-087 - FAILED TO APPLY BALANCE UPDATE RECORD

This message indicates that AP Batch II could not update the institution’s balance file with the account detail balance information. Escalate to Customer Support Representative.

APB-088 - ONLY ONE FUNDING ACCOUNT PER CARDHOLDER

This message indicates that when AP Batch II processed segment CH03A, more than one funding account was indicated. This is not permitted.

APB-094 - INVALID LAST-MIN-BAL-AMT

This message indicates that a non-numeric value exists in the FR01 segment of the AP Batch II input record. Change the data to a valid numeric value and resubmit the batch.

APB-095 - INVALID LAST-ADDR-CHG-DATE

This message indicates that an invalid date exists in the FR02 segment of the AP Batch II input record. Change the date to a valid value and resubmit the batch.

APB-096 - INVALID LAST-PIN-CHG-DATE


APB-097 - INVALID LAST-PIN-CHG-DATE


APB-098 - INVALID LAST-DEP-AMT

This message indicates that a non-numeric value exists in the FR02 segment of the AP Batch II input record. Change the data to a valid numeric value and resubmit the batch.

APB-099 - INVALID LAST-PIN-DATE

This message indicates that an invalid date exists in the FR02 segment of the AP Batch II input record. Change the data to a valid value and resubmit the batch.

APB-100 - INVALID LAST-DEP-DATE


APB-101 - INVALID LAST-ATM-DATE



APB-102 - INVALID LAST-AMT-AMT

This message indicates that non-numeric value exists in the FR02 segment of the AP Batch II input record. Change the data to a valid numeric value and resubmit the batch.

APB-103 - INVALID LAST-PIN-AMT


APB-104 - INVALID LAST-OFFLINE-DATE


APB-105 - INVALID LAST-OFFLINE-AMT


APB-106 - INVALID SEND-TO-CASE

This message indicates that a send-to-case field value does not exist in the FR02 segment of the AP Batch II input record. Change the send-to-case field to Y or N and resubmit the batch.

APB-107 - INVALID CUST-SINCE-DATE


APB-108 - INVALID LAST-STATEMENT-DATE

This message indicates that an invalid date exists in the FR01 APBATCH2 input record. Change the date to a valid value and resubmit the batch.

APB-109 - INVALID LAST-MINIBAL-DATE


APB-110 - INVALID LAST-DEP-DATE


APB-111 - INVALID DATE-OF-BIRTH



APB-112 - INVALID ACTIVATION-TIME-STAMP

This message indicates that an invalid timestamp exists in the CH22 segment of the AP Batch II input record. Change the timestamp to a valid value and resubmit the batch.

APB-113 - INVALID PREV-CRD-ACT

This message indicates that the Prev-Crd-Act value does not exist in the CH22 segment of the AP Batch II input record. Change the Prev-Crd-Act value to Y or N and resubmit the batch.

APB-114 - INVALID POST-AUTH-EXCLUDE

This message indicates that the Post-Auth-Exclude value does not exist in the CH23 segment of the AP Batch II input record. Change the Post-Auth-Exclude value to Y or N and resubmit the batch.

APB-115 - INVALID IN-AUTH-EXCLUDE

This message indicates that the In-Auth-Exclude value does not exist in the CH23 segment of the AP Batch II input record. Change the Invalid In-Auth-Exclude value to Y or N and resubmit the batch.

APB-116 - INVALID IN-AUTH-REVIEW

This message indicates that the In-Auth-Review value does not exist in the CH23 segment of the AP Batch II input record. Change the In-Auth-Review value to Y or N and resubmit the batch.

APB-117 - INVALID DO-NOT-DISTURB-DATE

This message indicates that an invalid date exist in the CH23 segment of the AP Batch II input record. Change the date to a valid value resubmit the batch.

APB-118 - FAILED UPDATE OF CH23 SEGMENT

This message indicates that the attempt to update the Ci-Status field for CH01 failed. AP Batch II cannot update the related fields in the CH23 segment of this input record. Verify that CH23 is properly configured for the institution and that no invalid data exists in this segment for this cardholder. Make the necessary changes and resubmit the batch.

APB-119 - FAILED UPDATE OF FR02 SEGMENT

This message indicates that the attempt to update the Address field in CH18, the Ci-Status field in CH01, and the PIN-Offset field in CH02 failed. AP Batch II cannot update the related fields in the FR02 input record. Verify that an APFRAUD file exists and FR02 is properly configured for this institution. Make the necessary changes and resubmit the batch.



This message indicates that the attempt to update the Card Activation field in CH01 failed. AP Batch II cannot update the related fields in CH22 input record. Verify that the CH22 segment is properly configured for this institution and that no invalid data is present for this cardholder. Make the necessary changes and resubmit the batch.


This message indicates that the attempt to update the Card Condition code field in CH18 failed. If an institution uses CIMS and attempts to add or remove a hot-card using a CH01 update, AP Batch II will also update the CH18 Card Condition Code field. This message indicates that the CH18 update failed. Verify that the CH18 segment is properly configured for this institution and that no invalid data is present for this cardholder. Make the necessary changes and resubmit the batch.

APB-128 - BEGIN TIMESTAMP MUST BE LESS THAN END TIMESTAMP

The CH09 segment requires the begin timestamp to be less than the end timestamp. Verify the timestamps, make the necessary changes, and resubmit the batch.

APB-129 - REQUIRED AD06 SEGMENT(S) MISSING

The AD06 has four segments AD06A, AD06B, AD06C, and AD06D and all four segments should be present. Verify which segment(s) are missing, make the necessary changes, and resubmit the batch.

APB-130 - INVALID CONSECUTIVE REJECT COUNTS

This message indicates the attempt was made to add/update the invalid consecutive reject count.

APB-131 - INVALID PREVIOUS CONSECUTIVE REJECT COUNTS

This message indicates the attempt was made to add/update the invalid previous consecutive reject count.

APB-132 - INVALID CARD TYPE

This message indicates the the attempt was made to add/update the invalid Card type.

APB-133 - REQUIRED AD03 SEGMENT (S) MISSING

This message indicates that some of the AD03 segment occurrence(s) were missing when the attempt was made to add/update the AD03 segment.


APB-134 - INVALID HOST ACCT BALANCE UPDATE DATE

This message indicates that the attempt was made to add/update the invalid host acct balance update date. The actual date format is YYYYMMDD.

APB-135 - FAILED UPDATE OF AD08 SEGMENT

This message indicates that the attempt made to update the AD08 segment failed.

APB-136 - INVALID TRAVEL INDICATOR

This message indicates that the attempt was made to add/update travel indicators in the Travel Indicator field, other than the following characters (Y, N, space and *).

APB-137 - INVALID VIP INDICATOR

This message indicates that the attempt was made to add/update VIP indicators in the VIP indicator field, other than the following characters (Y, N, space and *).

APB-138 - TRAVEL INDICATOR CAN NOT BE Y IF TRAVEL LEVEL N

This message indicates that the attempt was made to add/update the travel indicator as "Y" when the Travel-Level is "N" in the APPARAM file.

APB-139 - START & END DATE NOT ALLOWED IF TRAVEL INDICATOR N

This message indicates that the attempt was made to add/update the travel dates when the Travel indicator was "N".

APB-140 - START & END DATE SHOULD BE GIVEN IF TRAVEL INDICATOR Y

This message indicates that the attempt was made to add/update the travel dates as "Blank" when the Travel indicator was "Y". This is a warning message. In this case, the record will be added successfully.

APB-141 - TRAVEL START DATE REQUIRED

This message indicates that attempt was made to add/update the Travel Start Date field with "Blank" and the Travel End Date field with a date.

APB-142 - TRAVEL END DATE REQUIRED

This message indicates that the attempt was made to add/update the Travel End Date field with "Blank" and the Travel Start Date field with a date.

APB-143 - INVALID TRAVEL END DATE

This message indicates that the attempt was made to add/update the Travel End Date field with an invalid date. The actual date format is YYYYMMDD.


APB-144 - INVALID TRAVEL START DATE

This message indicates that the attempt was made to add/update the Travel Start Date field with an invalid date. The actual date format is YYYYMMDD.

APB-145 - END DATE IS LESS THAN TODAY’S DATE

This message indicates that the attempt was made to add/update the Travel End Date as lesser than the current date.

APB-146 - END DATE IS LESS THAN START DATE

This message indicates that the attempt was made to add/update the Travel End Date as lesser than the Travel Start Date.

APB-147 - PAN TOKENIZATION PADSS ERROR CODE = XX

This message indicates that error occured during PAN to PPAN conversion and the corresponding PADSS error code.

APB-148 - FILE REGISTER PADSS ERROR CODE = XXX

This message indicates that error occured during file register procedure (at present this is apbatch2 input file) for PADSS and the corresponding error code.

APB-149 - FILE ENCRYPTION PADSS ERROR CODE = XXX

This message indicates that error occured during File data (at present this is fmrhold file log data) encryption procedure for PADSS and the corresponding error code.

APB-150 - PAN DETOKENIZATION PADSS ERROR CODE = XXX

This message indicates that error occured during PPAN to PAN conversion and the corresponding PADSS error code.

APB-151 - BATCH RECORDS OLDER THAN LAST FILE UPDATE - SKIPPING

This message indicates that Batch input file is older than the last CH file update. CH00 record needs to have newer date than CH01 last maintained timestamp.

APB-152 - INVALID MEDIA TYPE

This message indicates that invalid media type values are present in Batch input file record CH14. Valid values are IC, IP, MS and IS.

APB-153 - INVALID COMPANION MINI TYPE

This message indicates that invalid companion mini type values are present in batch input file record CH14. Valid values are Y and N.


APB-154 - INVALID COMPANION MICRO TYPE

This message indicates that invalid companion micro type values are present in batch input file record CH14. Valid values are Y and N.

APB-155 - INVALID COMPANION MOBILE TYPE

This message indicates that invalid companion mobile type values are present in batch input file record CH14. Valid values are Y and N.

APB-156 - VAU/ABU INDICATOR REQUIRED

This message indicates that missing VAU/ABU required Indicator. Valid Values are "VAU" or "ABU".

APB-157 - VAU/ABU INVALID REASON CODE

This message indicates that VAU/ABU Reason Code is not valid.Valid Values are "A","C","E" or "Q".

APB-158 VAU/ABU INVALID REVERSAL CODE

This message indicates that VAU/ABU Reversal Code is not valid.Valid Values are space or "R".

APB-159 - VAU/ABU INVALID CONVERSION CODE

This message indicates that VAU/ABU Conversion Code is not valid.Valid Values are space,"V" or "M".

APB-160 - VAU/ABU OLD TRK2 DATE REQUIRED

This Indicator indicates OLD TRK2 DATE is missing to add/update the CH50 Segment for VAU/ABU information.

VAU - Reason code C and Q should not have Old Expiration Date whereas A and E should have old Expiration Date when add/update the CH50 Segment for VAU Information

ABU - Reason code E,B,P,R,X,Y should have Old Expiration Date whereas C,O,N may or may not have old Expiration Date when add/update the CH50 Segment for ABU Information.

APB-161 VAU/ABU OLD PAN REQUIRED

This Indicator indicates OLD PAN is missing to add/update the CH50 Segment for VAU/ABU information.

VAU - Reason code A should have OLD PAN whereas E,C,Q may or may not have OLD PAN when add/update the CH50 Segment for VAU Information.

ABU - Reason code B,P,R,X,Y should have OLD PAN whereas E,C,O,N may or may not have OLD PAN when add/update the CH50 Segment for ABU Information.


APB-162 VAU/ABU INVALID NEW TRK2 DATE

This Indicator indicates, when New trk2 date is not the future date.YY & MM should be the Future Date.

APB-163 VAU/ABU OLD & NEW TRK2 SHOULD NOT BE THE SAME

This Indicator indicates OLD TRK2 DATE & NEW TRK2 DATE should be Unique, when vau-abu-ind as "VAU" or "ABU" for the reason code "E".

APB-164 VAU/ABU OLD & NEW PAN SHOULD NOT BE THE SAME

This Indicator indicates OLD PAN & NEW PAN should be Unique, when vau-abu-ind as "ABU" for the reason code "B","P","R".

APB-165 VAU/ABU NEW TRK2 DATE REQUIRED

This Indicator indicates NEW TRK2 DATE is missing to add/update the CH50 Segment for VAU/ABU information.

VAU - Reason code A,C,E,Q should have New Expiration date when add/update the CH50 Segment for VAU Information.

ABU - Reason code E,B,P,R,X,Y,N should have New Expiration Date whereas C,O may or may not have the New Expiration Date when add/update the CH50 Segment for ABU Information.

Balance Update Messages

$xxxxx: I/O Error on $TAPE, ERROR = nnn

Each BU message indicating an I/O error is preceded by this message.

BU-01 $xxxxx: Cannot Open Maintenance Input; (full file name)

An I/O error occurred while trying to read the specified maintenance input.

BU-02 $xxxxx: Error Reading Data From Tape; (full name)

An I/O error occurred while trying to read the specified maintenance input. Look for an I/O error message and correct the error.

BU-03 $xxxxx: Cannot Open Control File; (full file name)

An I/O error occurred while trying to read the Control file. Look for an I/O error message and correct the error.

BU-04 $xxxxx: Cannot Find Control File; (full file name)

The Control file is not on the specified volume and subvolume. Check the output of the AP parameter compiler.


BU-05 $xxxxx: Cannot Find Status File; (full file name)

The Status file is not on the specified volume and subvolume. Check the File Locator file and allocate a Status file if necessary.

BU-06 $xxxxx: Cannot Open Status File; (full file name)

An I/O error occurred while trying to open the Status file. Look for an I/O error message and correct the error.

BU-07 $xxxxx: Error Reading Disc

An I/O error occurred while trying to read the specified maintenance input. Look for an I/O error message and correct the error.

BU-08 $xxxxx: Control Record Missing

APBFU input file requires a control header record. This control header record is missing from the input file.

BU-09 $xxxxx: Error Reading Control File; (full file name)

An I/O error occurred while trying to read the Control file. Look for an I/O error message and correct the error.

BU-10 $xxxxx: Error Opening Balance File; (full file name)

An I/O error occurred while trying to read the Balance Update file. Look for an I/O error message and correct the error.

BU-11 $xxxxx: File Name Not Valid; (full file name)

The Match-Merge mode was selected. However, the name of the alternate file or the Balance Update file is invalid or more than 7 characters. Correct the name.

BU-12 $xxxxx: Unrecognized Option In Start-Up

An override mode was specified in the start-up, but it is not MM, IN, or LO. Therefore, the mode is ignored and the Balance Update process will determine the most efficient update mode. No action is required.

BU-13 $xxxxx: Cannot Open COM MOM

An optional MOM was specified in the start-up. An I/O error message occurred while trying to open the optional MOM. Look for an I/O error message and correct the error.

BU-14 $xxxxx: Cannot Write To COM MOM

An I/O error occurred while trying to write to the Optional MOM. Look for an I/O error message and correct the error.


BU-15 $xxxxx: BFU Is Not Named; It Must Be

The override has been specified to do a Match-Merge or a Load process, but the AP balance was not named. Add a name parameter to the start-up.

BU-16 $xxxxx: Newprocess On FUP Failed; Error xxx

The Match-Merge or Load mode was selected. However, the HP NonStop File Utility Program failed to open when requested. Force Balance Update to fun In Place mode or contact your HP NonStop® representative about the error.

BU-17 $xxxxx: Cannot Open FUP

Either Match-Merge or Load mode was selected. However, the HP NonStop File Utility Program failed to open when requested. Force Balance Update to fun In Place mode or contact your HP NonStop® representative about the error.

BU-18 $xxxxx: Error Reading BAL File

An I/O error occurred while trying to read the Balance Update file. Look for an I/O error message and correct the error.

BU-19 $xxxxx: Cannot Open The ALT File; (full file name)

An I/O error occurred while trying to open the alternate Balance Update file. Look for an I/O error message and correct the error.

BU-20 $xxxxx: Cannot Rename File; (full file name)

An I/O error occurred while trying to rename one of the Balance Update file. Look for an I/O error message and correct the error.

BU-21 $xxxxx: Error Writing BAL File; (full file name)

An I/O error occurred while trying to write to the Balance Update file. Look for an I/O error message and correct the error.

BU-22 $xxxxx: Error Writing Stat File; (full file name)

An I/O error occurred while trying to write to the Status file. Look for an I/O error message and correct the error.

BU-23 $xxxxx: Balance Update Is Complete

Balance Update is finished. No action is required.

BU-24 $xxxxx: Maintenance File Is Empty

The specified maintenance file is empty. AP Balance Update abends.

BU-25 $xxxxx: Error On Alternate File; (full file name)

An I/O error occurred on the alternate Balance Update file. Look for an I/O error message and correct the error.


BU-26 $xxxxx: Error Reading Status File; (full file name)

An I/O error occurred while trying to read the Status file. Look for an I/O error message and correct the error.

BU-27 $xxxxx: Cannot Write To FUP

An I/O error occurred while trying to write to FUP. Look for an I/O error message and correct the error.

BU-28 $xxxxx: FUP Did Not Complete Normally; Update Not Complete

An I/O error occurred while trying to communicate with FUP. Look for an I/O error message and correct the error. Check for message BU-37.

BU-29 $xxxxx: Cannot Open File LOC File; (full file name)

An I/O error occurred while trying to open the File Locator file. Look for an I/O error message and correct the error.

BU-30 $xxxxx: Keyposition Failed On; (full file name)

An I/O error occurred while trying to keyposition on the specified file. Look for an I/O error message and correct the error.

BU-31 $xxxxx: Input Is Not Tape Or Disc

The input file specified for the maintenance input was not disc or tape and the Balance Update abends. Correct the error and resubmit the file.

BU-32 $xxxxx: Mode=xx(nn); (full file name)

This is an informational message.

xx = The mode used. Possible values are:

nn = The method of selection. Possible values are:

Value Description

IP In Place

MM Match-Merge

LO Load


No action is required.

BU-32 Time(sec)=yyyy,Maint=zzzzzz,File=rrrrrr,Rate=pppp

This is an informational message, where:

No action is required.

BU-33 $xxxxx: Counting The Number Of Records In The Balance File

The record that contains the record count on the Balance Update file is missing. AP Balance Update is counting the number of records on the file. There is a short delay and no action is required.

BU-34 $xxxxx: BFU Is Starting

AP Balance Update is starting. No action is required.

BU-35 $xxxxx: Tape Is Not Ready

The input tape is not ready. Ready the tape and respond to the message.

BU-36 $xxxxx: Mount Next Reel

The input reel is finished. Mount the next reel, ready the tape, and respond to the message.

Value Description

00 The name of the primary file is 8 characters and the files cannot be renamed.

01 The alternate file does not exist or cannot be used.

02 The mode override was entered in the RUN command.

03 Balance Update performed a calculation and determined the mode to use.

(full file name) The Balance Update file being created.

yyyy The number of seconds it took AP Balance Update to run.

zzzzzz The number of records in the maintenance input.

rrrrrr The resulting number of records in the new Balance Update file.

pppp The records processed per second.


BU-37 $xxxxx: MSG From FUP: (text)

A Match-Merge or a Load mode is being performed. If no errors have occurred, this is a count of the number of records loaded. Determine the corrective action from the message text.

BU-38 $xxxxx: Error Opening Config: (full file name)

An I/O error occurred while trying to open the Configuration file. Look for an I/O error message and correct the error.

BU-39 $xxxxx: Error Reading Config: (full file name)

An I/O error occurred while trying to read the Configuration file. Look for an I/O error message and correct the error.

BU-40 $xxxxx: Error Opening AP: $Name

An I/O error occurred while trying to communicate with an AP process. Look for an I/O error message and correct the error.


C
APCOMP Utility
APCOMP is a batch utility program that allows you to add/remove compromised flags.

The flag name should be 3 characters long. The first character should be alphabetic, the others can be alphabetic or numeric. USAA decides the name of the flags.

USAA sends the input file, and this reaches HP NonStop® through IBM®. The card numbers are sorted, and MMYY is removed from the input file name so that the input file name matches any one of the flags.

RUNAPCOM is configured in NetBatch to automatically run once the input file is placed in the input location. APCOMP uses the input file name as the current flag, and first removes the (old) occurrences of the flag in AP database using the work file (it remains in the history location).

In the second phase, APCOMP adds the flag to the card numbers given in the input file. If APCOMP is unable to add the flag, then it writes the card number in the Alert Update report with the reason. This report is sent to customer.

Removing FlagsTo remove flags from the AP database, create an empty input file for each flag. This removes the old occurrence of flags from the AP database.

ExampleTo remove the A01 flag from the AP database, create an empty input file in input location as A01 and run the RUNAPCOM, so that the old occurrence of A01 is removed.


RUNAPCOM

?tacl macro == Program to update the APFRAUD file for USAA ==################################################# == Batch RUNTACL Variables == Batch Parameters == LINES : Number of detail lines in report file == FLAG1 : Name of the Input-file (Flag) == FLAG2 : Name of the Input-file (Flag) == Flag3 : Name of the Input-file (Flag) == INPUT-LOC : Location where the input file should be == only volume and subvolume is enough == HISTORY-LOC : Location where the work file and other history files == should be == only volume and subvolume is enough == PATHWAY : Location where AHLSR940 is present. == EVDB : Location of the EVDB. == REPORT-TYPE : Type of the report file FILE or SPOOLER == == valid values: FILE - use ASSIGN *.REPORT-FILE , =cmrptse == SPOOLER - use ASSIGN *.REPORT-FILE , $S.#REPORT == == Batch Assigns == REPORT-FILE : This report will have the card numbers and the == reason why the batch program not able to add flag. == == REMOVE-REPORT-FILE : This report will have the card numbers and the == reason why the batch program not able to remove == the old occurrence of the flag. ==################################################# #frame CLEAR ALL ASSIGN *.REPORT-FILE, $PXD20.WR29234.REPO ASSIGN *.REMOVE-REPORT-FILE, $S.#REMOVE ==################################################# PARAM REPORT-TYPE SPOOLER PARAM LINES 20 PAAAM FLAG1 A01 PARAM FLAG2 B01 PARAM FLAG3 c01 PARAM INPUT-LOC $pxd20.WR29234 PARAM HISTORY-LOC $pxd20.WR29234O PARAM PATHWAY $S4AP PARAM EVDB $PXD06.SDC4EVDB ==################################################# [ RUN $pxd20.wr29234o.APCOMP / OUT $s.#ap.apcomp , cpu 3, PRI 110 / ] #unframe

Figure 1 RUNAPCOM


Sample Report

SAMPLE SAVINGS BANK-XXX -1314074269 SETDATE 07/06/06 PAGE 1 USAA - PRC020 ALERT UPDATE REPORT RUNDATE 07/07/06 APCOMP RUNTIME 09:04:47 ----------------------------Exception Reporting------------------------------ - Card Number Error Detail ----------------------------------------------------------------------------- <PAN> < Error Detail > <PAN> < Error Detail > Processing Summary ------ --------- -------- --------- Alert Read Success Failed ------ --------- -------- --------- A01 000000100 98 2

Figure 2 Sample Report - Alert Update Report


D
Codes
This appendix lists the reject reason codes and transaction type codes.

Reject Reason CodesFollowing is a list of the Reject Reason codes currently supported by FIS. The codes have several uses:

They are associated with RSNnn values in the REJRSN command defining how standard AP reject conditions are handled for each AP card group and online/offline/stand-alone condition.

They are used as negative status codes for both the Card Status field on the Cardholder Record and the Account Status field on the Account Detail Record.

They are displayed, along with other reject information, in the Reject Reason field on Customer Service Transaction List screens (APMSC081 and APMSC082).

Many institutions use only a small subset of the complete list.

CAUTION: Not all Connex™ applications support these codes. Contact your Account Manager or Customer Support Representative at FIS to verify your choices.

Format 8 Code

ISO Code Description

Settlement Description

_A 904 Invalid Format Inv Time

_B 904 Invalid Date Inv Date

_C 904 Invalid Processor Identification Inv Proc

_D 940 Invalid Security Code Inv Secur

_E 923 Transaction in Progress In Prgrss

_F 109 Invalid Merchant


_F 120 Transaction Not Permitted to Terminal

_F 905 Invalid Terminal Number Inv Term

_G 111 Invalid Cardholder Number

_H 201 Invalid Expiration Date (Capture Card) Inv Exp

_I 112 PIN Data Required

_I 117 Invalid PIN Inv PIN

_J 119 Invalid Transaction Type Inv Tran

_K 110 Invalid Amount Field Inv Amt

_L 904 Invalid Response Code Inv Resp

_M 906 Cutover in Progress

_M 910 Processor Not Logged On Not Sign ON

_N 907 Processor Option of Decline When Down Decline

_N 911 Card Issuer Timed Out

_N 912 Card Issuer Unavailable

_P 118 Cardholder Not on File Not On File

_P 125 Card Not Effective

_P 129 Suspected Counterfeit Card

_P 210 Suspected Counterfeit Card (Pick Up Card)

_Q 904 Invalid Reject Reason Inv Reject

_R 206 Excessive PIN Tries (Capture Card) PIN Tries

_S 114 No Account of Type Requested No DDA

_S 190 No Unspecified (Funding) Account Available

_S 193 No Checking Account Available

_T 192 No Savings Account Available

_U 121 Exceeded DDA Dollar Limit Dollar Lmt

_V 123 Exceeded DDA Number Limit Excess Use

_W 121 Exceeded SAV Dollar Limit Dollar Lmt

_X 123 Exceeded SAV Number Limit Excess Use

Format 8 Code




_Y 121 Exceeded CR Dollar Limit Dollar Lmt

_Z 123 Exceeded CR Number Limit Excess Use

AB 115 Access Requested Not Valid for Debit Card No Debit

AC 115 Access Requested Not Valid for Credit Card No Credit

AD 209 Lost/Stolen Card (Capture Card) Hot Card

AE 202 Fraud (Capture Card) Fraud

AF 908 Invalid Prefix Inv Prefix

AG 908 Invalid Institution Code Inv Inst

AH 100 Deposit Reversals Exceed Today’s Deposits Inv Rev

AI 100 Withdrawal Reversals Exceed Today’s Withdrawals

Inv Rev

AJ 907 Credit Floor Limit Exceeded/Processor Down Flr Limit

AJ 912 Card Issuer Unavailable

AK 204 Permanent Restraint (Capture Card) Perm Rest

AL 207 Bad Debt (Capture Card) Bad Debt

AM 308 Account Already on Negative File NegF Acct

AN 904 Field was Changed from Original Request 135 Bad

AP 122 Terminal Not Owned by Requester Inv Owner

AQ 909 File Full - Request Not Processed

AR 909 File Error - Request Not Processed

C0 902 CR-DDA Invalid Transaction Code or Type Inv Trans

C1 114 No CR-DDA Account No Acct

C2 100 CR-DDA MasterCard® and Account Number Do Not Agree

No Match

C3 183 CR-DDA Closed or Restricted for Closing Closed

C4 184 CR-DDA Dormant Dormant

C5 116 CR-DDA Non-Sufficient Funds NSF

C6 100 CR-DDA Deposit Reversals Exceed EFT Deposits Today

Inv Rev

Format 8 Code




C7 100 CR-DDA Withdrawal Reversals Exceed EFT Withdrawals Today

Inv Rev

D0 902 DDA Invalid Transaction Code or Type Inv Trans

D1 114 No DDA Account No Acct

D2 100 DDA MasterCard and Account Number Do Not Agree

No Match

D3 183 DDA Closed or Restricted for Closing Closed

D4 184 DDA Dormant Dormant

D5 116 DDA Non-Sufficient Funds NSF

D6 100 DDA Deposit Reversals Exceed EFT Deposits Today

Inv Rev

D7 100 DDA Withdrawal Reversals Exceed EFT Withdrawals Today

Inv Rev

FC A41 Reject/Block received from Compromise Manager

Comp Mgr Blk

ND 180 Lost/Stolen Card (Return Card) Hot Card

NE 102 Fraud (Return Card) Fraud

NH 101 Invalid Expiration Date (Return Card) Inv Exp

NK 104 Permanent Restraint (Return Card) Perm Rest

NL 185 Bad Debt (Return Card) Bad Debt

NR 106 Excessive PIN Tries (Return Card) PIN Tries

P0 114 DDA Account Not on File (Stand-In Authorization)

Not On File

P1 114 SAV Account Not on File (Stand-In Authorization)

Not On File

P2 116 CR Non-Sufficient Funds NSF Limit

P3 114 CR Account Not On File (Stand-In Authorization)

Not On File

P4 116 OTH Non-Sufficient Funds NSF Limit

P5 114 OTH Account Not on File (Stand -In Authorization)

Not On File

P6 183 CR Closed or Restricted for Closing Closed

Format 8 Code




P7 184 CR Dormant Dormant

P8 183 Closed Account

P9 184 Dormant Account

PC 194 No Credit Account Available

PD 123 Total Daily Uses Exceeded Excess Use

PE 115 Function Unavailable Not Avail

PF 118 Card Not on File (Stand-In Authorization) Not On File

PG 922 Invalid Sequence Number Inv Seq

PH 100 Total Daily Denials Exceeded Denial Exc

PI 123 Total Daily Withdrawal Uses Exceeded (Return Card)

Excess Use

PJ 280 Total Daily Withdrawal Uses Exceeded (Capture Card)

Excess Use

PK 123 DDA Daily Withdrawal Uses Exceeded Excess Use

PL 123 SAV Daily Withdrawal Uses Exceeded Excess Use

PM 123 CR Daily Withdrawal Uses Exceeded Excess Use

PN 121 DDA Daily Withdrawal Amount Exceeded Dollar Lmt

PP 121 SAV Daily Withdrawal Amount Exceeded Dollar Lmt

PQ 121 CR Daily Withdrawal Amount Exceeded Dollar Lmt

PR 121 Total Daily Withdrawal Amount Exceeded (Return Card)

Dollar Lmt

PS 281 Total Daily Withdrawal Amount Exceeded (Capture Card)

Dollar Lmt

PT 902 Transaction Not Allowed by Institution Inv Trans

PU 200 Hot Card for Transaction Denial Hot Card

PV 191 No Other Account Available

PW 123 OTH Daily Withdrawal Uses Exceeded (Return Card)

Excess Use

PX 280 OTH Daily Withdrawal Uses Exceeded (Capture Card)

Excess Use

Format 8 Code




PY 121 OTH Daily Withdrawal Amount Exceeded (Return Card)

Dollar Lmt

PZ 281 OTH Daily Withdrawal Amount Exceeded (Capture Card)

Dollar Lmt

Q1 100 General Denial Reject

Q1 186 Check Already Posted

Q1 187 Information Not on File

Q1 903 Re-enter Transaction

Q1 914 Not Able to Trace Back to Original Transaction

Q1 915 Reconciliation Cutover or Checkpoint Error

Q1 916 MAC Incorrect

Q1 917 MAC Key Sync Error

Q2 117 Bad PIN (Return Card) Inv PIN

Q3 208 Card Misplaced (Capture Card) Lost Card

Q4 200 No Account on File (Capture Card) No Acct

Q5 107 Card Acceptor-Call Issuer Not Avail



Q7 203 Card Acceptor Contact Acquirer (Pick Up Card)

Q8 115 Invalid Function Inv Funct

Q9 904 Invalid Message Format Inv Fmt

QA 101 Invalid Expiration Date Inv Exp

QB 126 Invalid PIN Block

QB 127 PIN Length Error

QB 128 Key Synchronization Error

QB 918 No Communication Keys Available for Use

QB 919 Key Synchronization Error Key Error

QB 920 Security Software/Hardware Error - Try Again

QB 921 Security Software/Hardware Error - No Action

Format 8 Code




QC 904 Invalid Service Type Inv Type

QD 904 Invalid Discretionary Data Inv Disc

QE 910 PMC Not Signed On PMC Not On

QF 105 Card Acceptor Call Acquirer’s Security Department

QF 205 PSI SI Wrap-Back Wrap Back

QG 109 Invalid Terminal FRD-ABA Number Inv Tinst

QG 120 Transaction Not Permitted to Terminal

QG 905 Acquirer Not Supported by Switch

QJ 188 Card Verification Value (CVV) Verification Failed (No Pickup)

QZ 119 Deposit Only Function Dep Only

RH 113 Unacceptable Transaction Fee Unacc Trn

RI 124 Violation of Law Violn Law

RJ 913 Duplicate Transaction Dupl Tran

RK 909 System Malfunction Sys Malfu

RL 181 Authorization Life Unacceptable Life Unac

RM 182 Authorization Life Cycle has Expired Life Exp

RY A10 Card Not Activated

S0 902 SAV Invalid Transaction Code or Type Inv Trans

S1 114 No SAV Account No Acct

S2 100 SAV MasterCard® and Account Number Do Not Agree

No Match

S3 183 SAV Acct Closed or Restricted for Closing Closed

S4 184 SAV Dormant Dormant

S5 116 SAV Non-Sufficient Funds NSF

S6 100 SAV Deposit Reversals Exceed EFT Deposits Today

Inv Rev

S7 100 SAV Withdrawal Reversals Exceed EFT Withdrawals Today

Inv Rev

Format 8 Code




UA 116 NSF on Withdrawal-Try Lesser Amount NSF Less

UB 116 No Funds in Account NSF

UC 185 From Account Bad Status Bad Stat

UD 185 To Account Bad Status Bad Stat

UE 116 NSF on Transfer-Try Lesser Amount NSF Less

UF 116 NSF on Payment-Try Lesser Amount NSF Less

UG 908 Bank Control Record Not Available No Bk Rec

UH 121 Daily Withdrawal Limit Reached Lmt Reach

UI 121 Would Cause Daily Limit to be Exceeded Exceed Lmt

UJ 183 ACM Account is Closed Closed

UK 114 Invalid From Account/Not Set up Inv From

UL 114 Invalid to Account/Not Set Up Inv To

UN 114 Invalid From Account/No Account No Fr Act

UO 114 Invalid To Account/No Account No To Act

UP 114 From Account Does Not Exist No Fr Act

UQ 114 To Account Does Not Exist No To Act

UR A09 Expiration Date Mismatch (Do not capture card)

US 282 Expiration Date Mismatch (Capture card)

UY A25 Invalid Secret PIN

UZ 128 PIN Key Synch Error

W0 902 WMC Invalid Transaction Code or Type Inv Trans

W1 185 WMC Account Statused Statused

W2 185 WMC Account Delinquent Delinq

W3 116 WMC Transaction Takes Customer Over Line Over Line

W4 100 WMC Number of Authorizations Exceeded Exc Auth

W5 123 WMC Number of Cash Advances Exceeded Exc Adv

W6 116 WMC Credit Rating Exceeded Exc Or Rat

Z0 101 Expired

Format 8 Code




Transaction Type CodesThe following transaction type codes are supported by the Authorization Processor System.

Z1 101 Expired

Z2 121 Exceeds Withdrawal Amount Limit

Z2 123 Exceeds Withdrawal Frequency Limit

Z3 902 Invalid Payment

1U 116 DDA or OTH Non-Sufficient Funds NSF Limit

1W 116 SAV Non-Sufficient Funds NSF Limit

1Y 116 CR Non-Sufficient Funds NSF Limit

7A 100 Invalid System Request Inv Reqst

7B 100 No Key Change in Progress No Keychg

7C 100 Key Change Already in Progress In Prgrss

Any Other N/A Unknown Unknown

NOTE: Refer to “Cardholder Maintenance Values” on page 291, for more infor-mation on valid values for cardholder maintenance.

Format 8 Code



Format 8 Code Description of Transaction

ISO Code

Pre-Auth Indicator

01 Payment from Demand to Other 402099 N

02 Payment from Savings to Other 401099 N

03 Payment from Credit to Other 403099 N

04 Payment from Other to Other 400999 N

05 Deferred Debit Purchase from Demand 182000192000

NN

06 Deferred Debit Purchase from Savings 181000191000

NN


07 Deferred Debit Purchase from Funding 180000190000

NN

08 Merchandise Return to Credit (memo) 200030 N

09 Pre-Authorized Purchase from Credit (memo) 003000093000113000

YYY

10 Purchase Authorization Funding (memo) 000000090000110000

NNN

11 Cash Withdrawal from Demand (settled) 012000 N

12 Cash Withdrawal from Credit (settled) 130000 N

13 Cash Withdrawal from Savings (settled) 011000 N

14 Cash Withdrawal from Other (settled) 010900 N

15 Check Verification 040000 N

16 Traveler's Check Withdrawal from Demand 062000 N

17 Traveler's Check Withdrawal from Credit 063000 N

18 Traveler's Check Withdrawal from Savings 061000 N

19 Traveler's Check Withdrawal from Other 060900 N

20 Check Guarantee 030000 N

21 Generic Balance Inquiry 390000 N

22 Balance Inquiry from Demand 312000 N

23 Balance Inquiry from Credit 313000 N

24 Balance Inquiry from Savings 311000 N

25 Balance Inquiry from Other 310900 N

26 Deposit to Commercial 290020 N

27 Deposit to Other 210009 N

28 Deposit to Demand 210020 N

29 Deposit to Savings 210010 N

30 Transfer from Demand to Demand 402020 N

31 Transfer from Demand to Savings 402010 N


ISO Code

Pre-Auth Indicator


32 Transfer from Demand to Other 402009 N

33 Payment from Demand to Credit 402030 N

34 Payment from Savings to Credit 401030 N

35 Transfer from Savings to Demand 401020 N

36 Transfer from Savings to Other 401009 N

37 Transfer from Other to Demand 400920 N

38 Transfer from Other to Savings 400910 N

39 Transfer from Other to Other 400909 N

40 Transfer from Savings to Savings 401010 N

41 Payment from Other to Credit 400930 N

42 Payment Enclosed 590800 N

43 Information Inquiry 910000 N

44 Payment to Credit 210030 N

45 Payment to Liability (Enclosed) from Demand 592000 N

46 Payment to Liability (Enclosed) from Savings 591000 N

47 Payment to Liability (Enclosed) from Other 590900 N

48 Payment to Liability (Enclosed) from Credit 593000 N

49 Notification to Bank 920000 N

50 Transfer from Credit to Demand 403020 N

51 Transfer from Credit to Savings 403010 N

52 Transfer from Credit to Other 403009 N

53 Payment from Credit to Credit 403030 N

54 Payment to Other 210099 N

55 Payment to Liability (Enclosed) from Funding 590000 N

56 Cash Withdrawal from Demand (memo) 012000 N

57 Cash Withdrawal from Credit (memo) 013000 N

58 Cash Withdrawal from Savings (memo) 011000 N

59 Cash Withdrawal from Other (memo) 010900 N


ISO Code

Pre-Auth Indicator


60 Merchandise Return to Credit (settled) 20030 N

61 Purchase from Credit (settled) 003000093000113000

NNN

62 Purchase Authorization Credit 003000093000113000

NNN

63 Traveler's Check Withdrawal from Funding 060000 N

64 Merchandise Return to Demand (settled) 200020 N

65 Merchandise Return to Savings (settled) 200010 N

66 Merchandise Return to Other (settled) 200009 N

67 Purchase from Demand (settled) 002000092000112000

NNN

68 Purchase from Savings (settled) 001000091000111000

NNN

69 Purchase from Other (settled) 000900090900110900

NNN

70 Payment to 3rd Party Liability from Demand 502000 N

71 Payment to 3rd Party Liability from Savings 501000 N

72 Payment to 3rd Party Liability from Credit 503000 N

73 Payment to 3rd Party Liability from Other 500900 N

74 Payment to 3rd Party Liability from Funding 500000 N

75 Cash Withdrawal from Funding (memo) 010000 N

76 Funds Available Inquiry from Funding 300000 N

77 Cash Withdrawal from Funding (settled) 010000 N

78 Balance Inquiry from Funding 310000 N

79 Purchase from Funding (settled) 000000090000110000

NNN

80 Merchandise Return to Funding (settled) 200000 N


ISO Code

Pre-Auth Indicator


81 Purchase Pre-Auth from Demand 002000092000112000

NNN

82 Purchase Pre-Auth from Savings 001000091000111000

NNN

83 Purchase Pre-Auth from Credit 003000093000113000

NNN

84 Purchase Pre-Auth from Other 000900090900110900

NNN

85 Purchase Pre-Auth from Funding 000000090000110000

NNN

86 Funds Available Inquiry from Demand 302000 N

87 Funds Available Inquiry from Credit 303000 N

88 Funds Available Inquiry from Savings 301000 N

89 Funds Available Inquiry from Other 300900 N

90 PIN Change Request 900000 N

91 Pre-Authorized Purchase from Demand 002000092000112000

YYY

92 Pre-Authorized Purchase from Savings 001000091000111000

YYY

93 Pre-Authorized Purchase from Credit 003000093000113000

YYY

94 Pre-Authorized Purchase from Other 000900090900110900

YYY

95 Pre-Authorized Purchase from Funding 000000090000110000

YYY

96 Merchandise Return to Funding (memo) 200000 N


ISO Code

Pre-Auth Indicator


AK Notification to Bank - Funding 092000 N

AN Stop Pay - Demand Deposit 922000 N

AX Statement (Online) from Demand Deposit 912000 N

AY Statement (Online) from Savings 911000 N

AZ Statement (Online) from Credit 913000 N

AO Deposit to Unspecified Account (memo) 210000 N

A8 Information Inquiry from Savings 911000 N

A9 Information Inquiry from Demand Deposit 912000 N

BA Statement (Online) from Other 910900 N

BB Statement (Online) from Funding 910000 N

BC Deposit to Funding 210000 N

BV Check Cashing from Savings 171000 N

BW Check Cashing from Demand Deposit 172000 N

BX Check Cashing from Other 170900 N

B1 Check Reorder for Demand Deposit 922000 N

B2 Statement (Mail) from All Accounts 929700 N

B3 Statement (Mail) from Savings 921000 N

B4 Statement (Mail) from Demand Deposit 922000 N

B5 Statement (Mail) from Credit 923000 N

B6 Statement (Online) from all Accounts 919700 N

B7 Statement (Mini) for last ATM Transaction from all Accounts

919700 N

B8 Item Inquiry From Demand Deposit for a specific check

912000 N

B9 Statement (Mail) from Other 920000 N

CU Purchase Authorization from Savings (memo) 001000091000111000

NNN

CV Purchase Authorization from Demand Deposit (memo)

002000092000112000

NNN


ISO Code

Pre-Auth Indicator


D1 Item Inquiry from Funding 910000 N

D2 Item Inquiry from Savings 911000 N

D3 Item Inquiry from Credit 913000 N

D4 Item Inquiry from Other 910900 N

EO Statement (Mini) for last Deposits to Savings 911000 N

EP Statement (Mini) for last Deposits to Demand Deposit

912000 N

EQ Statement (Mini) for last ATM Transactions against Credit

913000 N

ER Statement (Mini) for last ATM Transaction from Other 910900 N

ES Statement (Mini) for last ATM Transaction from Funding

910000 N

ET Information Inquiry - Other 910900 N

EU Information Inquiry - Funding 910000 N

EZ Item Inquiry (card or all accounts) 919700 N

GM Purchase of Quasi-Cash or Scrip from Default Account

110000 N

GR Purchase of Quasi-Cash or Scrip from Other Account

110900 N

GT Purchase of Quasi-Cash or Scrip from Savings Account

111000 N

GX Purchase of Quasi-Cash or Scrip from DDA Account 112000 N

H2 Purchase of Quasi-Cash or Scrip from Credit Account

113000 N

HI Balance Inquiry from Investment 315000 N

HJ Transfer from Funding to Funding 400000 N

HO Transfer from Universal to Other 404009 N

HP Balance Inquiry from Universal 314000 N

HQ Transfer from Savings to Universal 401040 N

HR Transfer from Savings to Investment 401050 N

HT Transfer from Checking to Investment 402050 N


ISO Code

Pre-Auth Indicator


HV Transfer from Credit to Universal 403040 N

HW Transfer from Credit to Investment 403050 N

HY Transfer from Universal to Savings 404010 N

HZ Transfer from Universal to Checking 404020 N

IK Transfer from Other to Universal 400940 N

IL Transfer from Other to Investment 400950 N

IM Transfer from Checking to Universal 402040 N

IN Transfer from Universal to Investment 404050 N

IQ Transfer from Investment to Other 405009 N

IR Transfer from Investment to Universal 405040 N

IS Transfer/Payment Investment to Other Loan 405099585099

NN

IT Payment to Third Party from Universal 504000 N

IU Payment to Third Party from Investment 505000 N

I1 Transfer/Payment Universal to Credit 404030584030

NN

I2 Transfer from Universal to Universal 404040 N

I3 Transfer from Investment to Savings 405010 N

I4 Transfer from Investment to Checking 405020 N

I5 Transfer/Payment from Investment to Credit 405030585030

NN

I6 Transfer from Investment to Investment 405050 N

J2 Balance Inquiry from Loan 319000 N

J3 Balance Inquiry from Mortgage Loan 319100 N

J4 Balance Inquiry from Installment Loan 319200 N

J5 Balance Inquiry from Other Loan 319900 N

JA Payment Return to Other 280009 N

JB Payment Return to Savings 280010 N

JC Payment Return to Checking 280020 N

JD Payment Return to Credit 280030 N


ISO Code

Pre-Auth Indicator


JE Payment Return to Universal 280040 N

JF Payment Return to Investment 280050 N

JG Transfer from Other to Loan 400990 N

JH Transfer from Other to Mortgage Loan 400991 N

JI Transfer from Other to Installment Loan 400992 N

JJ Transfer from Savings to Loan 401090 N

JK Transfer from Savings to Mortgage Loan 401091 N

JL Transfer from Savings to Installment Loan 401092 N

JM Transfer from Checking to Loan 402090 N

JN Transfer from Checking to Mortgage Loan 402091 N

JO Transfer from Checking to Installment Loan 402092 N

JP Transfer from Credit to Loan 403090 N

JQ Transfer from Credit to Mortgage Loan 403091 N

JR Transfer from Credit to Installment Loan 403092 N

JS Transfer from Universal to Loan 404090 N

JT Transfer from Universal to Mortgage Loan 404091 N

JU Transfer from Universal to Installment Loan 404092 N

JV Transfer from Investment to Loan 405090 N

JW Transfer from Investment to Mortgage Loan 405091 N

JX Transfer from Investment to Installment Loan 405092 N

JY Deposit/Payment to Loan 210090 N

JZ Deposit/Payment to Mortgage Loan 210091 N

KL Payment Return To Unspecified 280000 N

KM Transfer from Savings to Unspecified 401000 N

KN Transfer from Checking to Unspecified 402000 N

KO Transfer from Credit to Unspecified 403000 N

K1 Deposit/Payment to Installment Loan 210092 N

LN Check Cashing from Funding 170000 N


ISO Code

Pre-Auth Indicator


LO Deposit Check to Savings (memo) 240010 N

LP Deposit Check to Demand (memo) 240020 N

LQ Deposit Check to Other (memo) 240009 N

LR Deposit Check to Funding (memo) 240000 N

LS Deposit Check to Savings 240010 N

LT Deposit Check to Demand Deposit 240020 N

LU Deposit Check to Other 240009 N

LV Deposit Check to Funding 240000 N

M2 Check Deposit to Credit (memo) 240030 N

M3 Check Deposit to Credit 240030 N

MN Payment to 3rd Party from Funding (P2P) (memo) 540000 N

MO Payment to 3rd Party from Other (P2P) (memo) 540900 N

MP Payment to 3rd Party from Savings (P2P) (memo) 541000 N

MQ Payment to 3rd Party from Demand Deposit (P2P) (memo)

542000 N

MR Payment to 3rd Party from Credit (P2P) (memo) 543000 N

MS Account Verification from Funding 330000 N

MT Account Verification from Other 330900 N

MU Account Verification from Savings 331000 N

MV Account Verification from Demand Deposit 332000 N

MW Account Verification from Credit 333000 N

P1 Non-Cash Financial Instrument for Funding from Savings (settled)

101000 N

P2 Non-Cash Financial Instrument for Funding from Demand Deposit (memo)

102000 N

P3 Non-Cash Financial Instrument for Funding from Demand Deposit (settled)

102000 N

P4 Payment from 3rd Party to Funding (P2P) (settled) 560000 N

P6 Payment from 3rd Party to Other (P2P) (settled) 560009 N

P7 Payment from 3rd Party to Savings (P2P) (settled) 560010 N


ISO Code

Pre-Auth Indicator


P8 Payment from 3rd Party to Demand Deposit (P2P) (settled)

560020 N

P9 Payment from 3rd Party to Credit (P2P) (settled) 560030 N

PA Payment from 3rd Party to Credit (memo) 550030 N

PB Payment from 3rd Party to Demand Deposit (memo) 550020 N

PC Payment from 3rd Party to Credit (settled) 550030 N

PD Payment from 3rd Party to Demand Deposit (settled) 550020 N

PE Payment from 3rd Party to Funding (memo) 550000 N

PF Payment from 3rd Party to Funding (settled) 550000 N

PH Payment from 3rd Party to Savings (memo) 550010 N

PI Non-Cash Financial Instrument for Funding from Default Unspecified (settled)

100000 N

PJ Payment to 3rd Party from Funding (P2P) (settled) 540000 N

PK Payment to 3rd Party from Other (P2P) (settled) 540900 N

PL Payment to 3rd Party from Savings (P2P) (settled) 541000 N

PM Payment to 3rd Party from Demand Deposit (P2P) (settled)

542000 N

PN Payment to 3rd Party from Credit (P2P) (settled) 543000 N

PO Payment from 3rd Party to Other 550009 N

PP Non-Cash Financial Instrument for Funding from Default Unspecified (memo)

100000 N

PS Payment from 3rd Party to Savings (settled) 550010 N

PZ Non-Cash Financial Instrument for Funding from Savings (memo)

101000 N

W1 Funds Withdrawal for Electronic Purse from Demand Deposit to Purchase Electronic Card (settled)

132067 N

W2 Funds Withdrawal for Electronic Purse from Credit to Electronic Purse Card Account (settled)

133060 N

W3 Funds Withdrawal for Electronic Purse from Credit to Purchase Electronic Card (settled)

133067 N

W4 Funds Withdrawal for Electronic Purse from Universal to Electronic Purse Card Account (settled)

134060 N


ISO Code

Pre-Auth Indicator


W5 Funds Withdrawal for Electronic Purse from Universal to Purchase Electronic Card (settled)

134067 N

WL Funds Withdrawal for Electronic Purse from Funding to Electronic Purse Card Account (memo)

130060 N

WM Funds Withdrawal for Electronic Purse from Funding to Purchase Electronic Card (memo)

130067 N

WN Funds Withdrawal for Electronic Purse from Savings to Electronic Purse Card Account (memo)

131060 N

WO Funds Withdrawal for Electronic Purse from Savings to Purchase Electronic Card (memo)

131067 N

WP Funds Withdrawal for Electronic Purse from Demand Deposit to Electronic Purse Card Account (memo)

132060 N

WQ Funds Withdrawal for Electronic Purse from Demand Deposit to Purchase Electronic Card (memo)

132067 N

WR Funds Withdrawal for Electronic Purse from Credit to Electronic Purse Card Account (memo)

133060 N

WS Funds Withdrawal for Electronic Purse from Credit to Purchase Electronic Card (memo)

133067 N

WT Funds Withdrawal for Electronic Purse from Universal to Electronic Purse Card Account (memo)

134060 N

WU Funds Withdrawal for Electronic Purse from Universal to Purchase Electronic Card (memo)

134067 N

WV Funds Withdrawal for Electronic Purse from Funding to Electronic Purse Card Account (settled)

130060 N

WW Funds Withdrawal for Electronic Purse from Funding to Purchase Electronic Card (settled)

130067 N

WX Funds Withdrawal for Electronic Purse from Savings to Electronic Purse Card Account (settled)

131060 N

WY Funds Withdrawal for Electronic Purse from Savings to Purchase Electronic Card (settled)

131067 N

WZ Funds Withdrawal for Electronic Purse from Demand Deposit to Electronic Purse Card Account (settled)

132060 N


ISO Code

Pre-Auth Indicator


E
Cardholder Maintenance Values
This Appendix lists the valid values for the Account and Card Status.

Card/Account Status Valid ValuesThe Card/Account Status identifies the standing of the card or the current status of the account.

The following are the fields to flag a card as hot.

NOTE: If the Card/Account Status field appears as "Code Status Unknown-with the entered code" then field has been updated with a non-standard status code in the past. This mostly occurs through the batch maintenance functions and the only way to change them is to resubmit a batch maintenance update.

Format 8 Code



_N 907 Processor Option of Decline Decline

AD 209 Lost/Stolen Card (Card Capture) Hot Card

AE 202 Fraud (Card Capture) Fraud

AK 204 Permanent Restraint (Card Capture) Perm Rest

AL 207 Bad Debt (Card Capture) Bad Debt

C3 183 CR-DDA Restricted for Closing Closed

D3 183 DDA Restricted for Closing Closed

D4 184 DDA Dormant Dormant

ND 180 Lost/Stolen Card (Return Card) Hot Card

NE 102 Fraud (Return Card) Fraud


NK 104 Permanent Restraint (Return Card) Perm Rest

NL 185 Bad Debt (Return Capture) Bad Debt

PE 115 Function Unavailable Not Avail

Q3 208 Card Misplaced (Capture Card) Lost Card

RY A10 Card Not Activated

Format 8 Code




F
Abbreviations
State CodesThe following table lists the valid values that may be used in the State field.

Code Description

** Non-US

AA Armed Forces Americas

AE Armed Forces Africa, Canada, Europe, Middle East

AK Alaska

AL Alabama

AP Armed Forces Pacific

AR Arkansas

AS American Samoa

AZ Arizona

CA California

CO Colorado

CT Connecticut

DC District of Columbia

DE Delaware

FL Florida

FM Federated States of Micronesia

GA Georgia

GU Guam

HI Hawaii


IA Iowa

ID Idaho

IL Illinois

IN Indiana

KS Kansas

KY Kentucky

LA Louisiana

MA Massachusetts

MD Maryland

ME Maine

MH Marshall Islands

MI Michigan

MN Minnesota

MO Missouri

MP Northern Mariana Islands

MS Mississippi

MT Montana

NC North Carolina

ND North Dakota

NE Nebraska

NH New Hampshire

NJ New Jersey

NM New Mexico

NV Nevada

NY New York

OH Ohio

OK Oklahoma

OR Oregon

PA Pennsylvania

Code Description


PR Puerto Rico

PW Palau

RI Rhode Island

SC South Carolina

SD South Dakota

TN Tennessee

TX Texas

UT Utah

VA Virginia

VT Vermont

WA Washington

WI Wisconsin

WV West Virginia

WY Wyoming

Code Description


Index

Symbols$xxxxx: I/O Error on $TAPE, ERROR = nnn

262

Numerics100-byte records . . . . . . . . . . . . . . . . . 96

AAccount Detail

AD01A . . . . . . . . . . . . . . . . . . . . 210AD01B . . . . . . . . . . . . . . . . . . . . 214

Account Detail Hold ListAD03B . . . . . . . . . . . . . . . . . . . . 226

Account Detail Hold List InformationAD03A . . . . . . . . . . . . . . . . . . . . 223

account detail informationadding . . . . . . . . . . . . . . . . . . 35, 38deleting . . . . . . . . . . . . . . . . . . 35, 37updating . . . . . . . . . . . . . . . . . 36, 39

Account Detail Overdraft InformationAD02A . . . . . . . . . . . . . . . . . . . . 219AD02B . . . . . . . . . . . . . . . . . . . . 221

Account InformationCH03A . . . . . . . . . . . . . . . . . . . . 145CH03B . . . . . . . . . . . . . . . . . . . . 149

AD01A, Account Detail . . . . . . . . . . . 210

AD01B, Account Detail . . . . . . . . . . . 214

AD02A, Account Detail Overdraft Information . . . . . . . . . . . . . . . . . . . . . . . . . 219

AD02B, Account Detail Overdraft Information . . . . . . . . . . . . . . . . . . . . . . . . . 221

AD03A, Account Detail Hold List Information . . . . . . . . . . . . . . . . . . . . . . . . . 223

AD03B, Account Detail Hold List . 226, 234

AD06A - Additional Hold Information . . 228

AD06B - Account Detail Hold List . . . . 231

AD06C - Account Detail Hold List . . . . 232

AD06D - Account Detail Hold List . . . . 234

AD08 - host balance update segment . 235

adding . . . . . . . . . . . . . . . . . . . . . . . . 64account detail information . . . . . . . . 38cardholder validation information . . . 42CIMS information . . . . . . . . . . . . . . 46fraud information . . . . . . . . . . . . . . 51name search information . . . . . . . . . 57

adding account detail, cardholder and fraud information . . . . . . . . . . . . . . . . . . 35

adding informationmultiple products . . . . . . . . . . . . . . 64

AP batch file segments . . . . . . . . . . . . . 29

AP Batch Load Exception Report . . . . . 60

AP Completematch and hold . . . . . . . . . . . . . . 104

AP Cooperativematch and hold . . . . . . . . . . . . . . 104

AP Hold Detail Report . . . . . . . . . . . . 117with PAN . . . . . . . . . . . . . . . . . . . 120

AP Hold File . . . . . . . . . . . . . . . . . . . 106

AP hold program abend and return codesEF500668 abend codes . . . . . . . . 133EF500668 return code . . . . . . . . . 133EF500670 abend codes . . . . . . . . 134EF500670 return codes . . . . . . . . 134EFVP0030 abend codes . . . . . . . . 133EFVP0030 return code . . . . . . . . . 133

AP Hold Report . . . . . . . . . . . . . . . . . 117

AP Hold Summary Report . . . . . . . . . 125

AP maintenanceonline host . . . . . . . . . . . . . . . . . . . 68


AP Maintenance File . . . . . . . . . . . . . . 25

APB-018 - AP DATABASE RECORD ALREADY EXISTS . . . . . . . . . . . 244

APB-019 - EXCEEDED 100 OUTSTANDING FILE OPERATIONS . . . . . . . . . . 244

APB-020 - INVALID RECORD NAME . 245

APB-021 - INVALID SEGMENT ID . . . 245

APB-022 - INVALID OR UNEXPECTED OCCURRENCE SECTION . . . . . 245

APB-023 - INVALID FILE UPDATE CODE . 245

APB-024 - ADD OPERATION REQUIRES ADD FILE UPDATE CODE . . . . . 245

APB-025 - INVALID PIN AUTHORIZATION FLAG . . . . . . . . . . . . . . . . . . . . 245

APB-026 - INVALID LEDGER BALANCE . 246

APB-027 - INVALID AVAILABLE BALANCE 246

APB-028 - INVALID CREDIT LINE AMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . 246

APB-029 - INVALID OVERDRAFT AMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . 246

APB-030 - INVALID CARDHOLDER PAN/PLASTIC NUMBER . . . . . . . . . . 246

APB-031 - INVALID LIMIT AMOUNT . . 246

APB-032 - INVALID LIMIT USES . . . . 247

APB-033 - INVALID INCREMENT AMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . 247

APB-034 - INVALID MINIMUM AMOUNT . 247

APB-035 - INVALID DEPOSIT PERCENTAGE . . . . . . . . . . . . . 247

APB-036 - EXCEEDED 200 BATCH RECORDS PER CH/AD RECORD . . 247

APB-037 - EXCEEDED 100 LOG RECORDS PER CH/AD RECORD . . . . . . . . 247

APB-038 - FIRST RECORD IS NOT A SEGMENT 01 RECORD . . . . . . . 248

APB-039 - EXCEEDED 32000 EDIT TABLE ENTRIES . . . . . . . . . . . . . . . . . . 248

APB-040 - OCCURRENCE DOES NOT EXIST . . . . . . . . . . . . . . . . . . . . 248

APB-041 - OCCURRENCE ALREADY EXISTS . . . . . . . . . . . . . . . . . . . 248

APB-042 - IDENTIFER DOES NOT EXIST (xxxxxxxxxx) . . . . . . . . . . . . . . . 248

APB-043 - INVALID CARD/ACCOUNT STATUS CODE . . . . . . . . . . . . . 248

APB-044 - INVALID CARD/ACCOUNT ACCESS(ES) . . . . . . . . . . . . . . . 249

APB-045 - CARD/ACCOUNT DOES NOT HAVE AN ACCESS . . . . . . . . . . 249

APB-046 - INVALID FINANCIAL INSTITUTION ID . . . . . . . . . . . . 249

APB-047 - INVALID ACCOUNT TYPE . 249

APB-048 - INVALID ACCOUNT NUMBER .249

APB-049 - INVALID CARD/ACCOUNT HOLD MATCH DATA . . . . . . . . . . 249

APB-050 - INVALID OAR SELECT TYPE .249

APB-051 - INVALID PRIMARY ACCOUNT INDICATOR . . . . . . . . . . . . . . . . 250

APB-052 - INVALID FUNDING ACCOUNT INDICATOR . . . . . . . . . . . . . . . . 250

APB-053 - INVALID ACCESS GROUP 250

APB-054 - INVALID LIMIT GROUP ID . 250

APB-055 - INVALID DATE FORMAT/VALUE (YYMM) . . . . . . . . . . . . . . . . . . . 250

APB-056 - INVALID LIMIT TYPE ID . . . 250

APB-057 - INVALID CARDHOLDER ADDRESS . . . . . . . . . . . . . . . . . 250

APB-058 - INVALID CARDHOLDER CITY .251


APB-059 - INVALID CARDHOLDER STATE 251

APB-060 - INVALID CARDHOLDER ZIP CODE . . . . . . . . . . . . . . . . . . . . 251

APB-061 - INVALID CARD CONDITION STATUS . . . . . . . . . . . . . . . . . . 251

APB-062 - INVALID AUTOMATIC ISSUE INDICATOR . . . . . . . . . . . . . . . . 251

APB-063 - INVALID MEMBER NUMBER . 251

APB-064 - INVALID CARDHOLDER NAME 251

APB-065 - INVALID CARD ORDER TYPE 252

APB-066 - INVALID CARD ORDER STATUS . . . . . . . . . . . . . . . . . . . . . . . . . 252

APB-067 - INVALID CARD ISSUE REASON . . . . . . . . . . . . . . . . . . . . . . . . . 252

APB-068 - INVALID CARD REPLACEMENT INDICATOR . . . . . . . . . . . . . . . . 252

APB-069 - INVALID CARDHOLDER SEX . 252

APB-070 - INVALID MARITAL STATUS 252

APB-071 - INVALID EDUCATION LEVEL . 252

APB-072 - INVALID INCOME RANGE 253

APB-073 - INVALID FAMILY SIZE . . . . 253

APB-074 - INVALID CARDHOLDER DISTANCE . . . . . . . . . . . . . . . . 253

APB-075 - INVALID RESIDENCE STATUS 253

APB-076 - INVALID EMPLOYMENT STATUS . . . . . . . . . . . . . . . . . . . . . . . . . 253

APB-077 - INVALID DATE FORMAT/VALUE (YYYYMMDD) . . . . . . . . . . . . . . 253

APB-078 - CONTROL NUMBER DOES NOT EXIST (AUTOMATIC FORCE) . . 253

APB-079 - CONTROL NUMBER MISMATCH (PREVIOUS/CURRENT: ###/###) 254

APB-080 - FAILED TO FIND INST/CARD GROUP . . . . . . . . . . . . . . . . . . . 254

APB-081 - FAILED TO FIND DEFAULT LMTGRP . . . . . . . . . . . . . . . . . . 254

APB-082 - INVALID CARD ACTIVATION . .254

APB-083 - ADA RECORD ALREADY EXISTS IN APADAA FILE . . . . . . 254

APB-084 - CARDHOLDER NAME NOT FORMATTED CORRECTLY . . . . 254

APB-085 - CARDMAN=Y, CH1AA/AB/AC NOT PERMITTED . . . . . . . . . . . 254

APB-086 - EXCEEDED 50 BALANCE UPDATE FILES . . . . . . . . . . . . . 254

APB-087 - FAILED TO APPLY BALANCE UPDATE RECORD . . . . . . . . . . . 255

APB-088 - ONLY ONE FUNDING ACCOUNT PER CARDHOLDER . . . . . . . . . 255

APB-094 - Invalid Last-Min-Bal-Amt . . 255

APB-095 - Invalid Last-Addr-Chg-Date 255

APB-096 - Invalid Last-PIN-Chg-Date . 255

APB-097 - Invalid Last-PIN-Chg-Date . 255

APB-098 - Invalid Last-Dep-Amt . . . . . 255

APB-099 - Invalid Last-PIN-Date . . . . . 255

APB-100 - Invalid Last-Dep-Date . . . . 255

APB-101 - Invalid Last-ATM-Date . . . . 255

APB-102 - Invalid Last-Amt-Amt . . . . . 256

APB-103 - Invalid Last-PIN-Amt . . . . . 256

APB-104 - Invalid Last-Offline-Date . . . 256

APB-105 - Invalid Last-Offline-Amt . . . 256

APB-106 - Invalid Send-To-Case . . . . . 256

APB-107 - Invalid Cust-Since-Date . . . 256

APB-108 - Invalid Last-Statement-Date 256

APB-109 - Invalid Last-Minibal-Date . . 256

APB-110 - Invalid Last-Dep-Date . . . . 256

APB-111 - Invalid Date-of-Birth . . . . . . 256


APB-112 - Invalid Activation-Time-Stamp . 257

APB-113 - Invalid Prev-Crd-Act . . . . . 257

APB-114 - Invalid Post-Auth-Exclude . 257

APB-115 - Invalid In-Auth-Exclude . . . 257

APB-116 - Invalid In-Auth-Review . . . . 257

APB-117 - Invalid Do-Not-Disturb-Date 257

APB-118 - Failed Update of CH23 Segment 257

APB-119 - Failed Update of FR02 Segment 257



APB-128 - BEGIN TIMESTAMP MUST BE LESS THAN END TIMESTAMP . 258

APB-129 - REQUIRED AD06 SEGMENT(S) MISSING . . . . . . . . . . . . . . . . . 258

APB-130 - INVALID CONSECUTIVE REJECT COUNTS . . . . . . . . . . . 258

APB-131 - INVALID PREVIOUS CONSECUTIVE REJECT COUNTS . 258

APB-132 - INVALID CARD TYPE . . . . 258

APB-133 - REQUIRED AD03 SEGMENT (S) MISSING . . . . . . . . . . . . . . . . . 258

APB-134 - INVALID HOST ACCT BALANCE UPDATE DATE . . . . . . . . . . . . . 259

APB-135 - FAILED UPDATE OF AD08 SEGMENT . . . . . . . . . . . . . . . . 259

APB-136 - INVALID TRAVEL INDICATOR . 259

APB-137 - INVALID VIP INDICATOR . 259

APB-138 - TRAVEL INDICATOR CAN NOT BE Y IF TRAVEL LEVEL N . . . . . 259

APB-139 - START & END DATE NOT ALLOWED IF TRAVEL INDICATOR N 259

APB-140 - START & END DATE SHOULD BE GIVEN IF TRAVEL INDICATOR Y 259

APB-141 - TRAVEL START DATE REQUIRED . . . . . . . . . . . . . . . . 259

APB-142 - TRAVEL END DATE REQUIRED 259

APB-143 - INVALID TRAVEL END DATE . .259

APB-144 - INVALID TRAVEL START DATE 260

APB-145 - END DATE IS LESS THAN TODAY’S DATE . . . . . . . . . . . . . 260

APB-146 - END DATE IS LESS THAN START DATE . . . . . . . . . . . . . . . 260

APB-147 - PAN TOKENIZATION PADSS ERROR CODE = XX . . . . . . . . . 260

APB-148 - FILE REGISTER PADSS ERROR CODE = XXX . . . . . . . . . . . . . . . 260

APB-149 - FILE ENCRYPTION PADSS ERROR CODE = XXX . . . . . . . . 260

APB-150 - PAN DETOKENIZATION PADSS ERROR CODE = XXX . . . . . . . . 260

APB-151 - BATCH RECORDS OLDER THAN LAST FILE UPDATE - SKIPPING . . . . . . . . . . . . . . . . . . . . . . . . . 260

APB-152 - INVALID MEDIA TYPE . . . . 260

APB-153 - INVALID COMPANION MINI TYPE . . . . . . . . . . . . . . . . . . . . 260

APB-154 - INVALID COMPANION MICRO TYPE . . . . . . . . . . . . . . . . . . . . 261

APB-155 - INVALID COMPANION MOBILE TYPE . . . . . . . . . . . . . . . . . . . . 261

APB-156 - VAU/ABU INDICATOR REQUIRED . . . . . . . . . . . . . . . . 261

APB-157 - VAU/ABU INVALID REASON CODE . . . . . . . . . . . . . . . . . . . . 261

APB-158 VAU/ABU INVALID REVERSAL CODE . . . . . . . . . . . . . . . . . . . . 261


APB-159 - VAU/ABU INVALID CONVERSION CODE . . . . . . . . 261

APB-160 - VAU/ABU OLD TRK2 DATE REQUIRED . . . . . . . . . . . . . . . . 261

APB-161 VAU/ABU OLD PAN REQUIRED 261

APB-162 VAU/ABU INVALID NEW TRK2 DATE . . . . . . . . . . . . . . . . . . . . 262

APB-163 VAU/ABU OLD & NEW TRK2 SHOULD NOT BE THE SAME . . 262

APB-164 VAU/ABU OLD & NEW PAN SHOULD NOT BE THE SAME . . 262

APB-165 VAU/ABU NEW TRK2 DATE REQUIRED . . . . . . . . . . . . . . . . 262

APCOMP utilityremoving flags . . . . . . . . . . . . . . . 268

APCOMP utility-removing flagsample report . . . . . . . . . . . . . . . 270

APCOMP utility-removing flagsexample . . . . . . . . . . . . . . . . . . . 268

APCOMP utility-removing flags exampleRUNAPCOM . . . . . . . . . . . . . . . . 269

asterisks . . . . . . . . . . . . . . . . . . . . . . . 69

audience . . . . . . . . . . . . . . . . . . . . . . 10

Bbalanace update messages

BU-25 $xxxxx: Error On Alternate File (full file name) . . . . . . . . . . . . . . . 264

balance refresh . . . . . . . . . . . . . . . . . . 87100-byte records . . . . . . . . . . . . . . 96detail record . . . . . . . . . . . . . . . . . 91header record . . . . . . . . . . . . . . . . 89trailer record . . . . . . . . . . . . . . . . . 95

balance refresh flow . . . . . . . . . . . . . . 87

balance refresh record layout . . . . . . . . 89

balance update messages . . . . . . . . . 262$xxxxx: I/O Error on $TAPE, ERROR =

nnn . . . . . . . . . . . . . . . . . . . . . . . 262BU-01 $xxxxx: Cannot Open Maintenance Input (full file name) . 262BU-02 $xxxxx: Error Reading Data From Tape (full name) . . . . . . . . . . . . . . 262BU-03 $xxxxx: Cannot Open Control File (full file name) . . . . . . . . . . . . . . . 262BU-04 $xxxxx: Cannot Find Control File (full file name) . . . . . . . . . . . . . . . 262BU-05 $xxxxx: Cannot Find Status File (full file name) . . . . . . . . . . . . . . . 263BU-06 $xxxxx: Cannot Open Status File (full file name) . . . . . . . . . . . . . . . 263BU-07 $xxxxx: Error Reading Disc . 263BU-08 $xxxxx: Control Record Missing .263BU-09 $xxxxx: Error Reading Control File (full file name) . . . . . . . . . . . . . . . 263BU-10 $xxxxx: Error Opening Balance File (full file name) . . . . . . . . . . . . 263BU-11 $xxxxx: File Name Not Valid (full file name) . . . . . . . . . . . . . . . . . . 263BU-12 $xxxxx: Unrecognized Option In Start-Up . . . . . . . . . . . . . . . . . . . . 263BU-13 $xxxxx: Cannot Open COM MOM . . . . . . . . . . . . . . . . . . . . . . . . . . 263BU-14 $xxxxx: Cannot Write To COM MOM . . . . . . . . . . . . . . . . . . . . . . 263BU-15 $xxxxx: BFU Is Not Named It Must Be . . . . . . . . . . . . . . . . . . . . . . . . 264BU-16 $xxxxx: Newprocess On FUP Failed Error xxx . . . . . . . . . . . . . . 264BU-17 $xxxxx: Cannot Open FUP . 264BU-18 $xxxxx: Error Reading BAL File .264BU-19 $xxxxx: Cannot Open The ALT File (full file name) . . . . . . . . . . . . 264BU-20 $xxxxx: Cannot Rename File (full file name) . . . . . . . . . . . . . . . . . . 264BU-21 $xxxxx: Error Writing BAL File (full file name) . . . . . . . . . . . . . . . . . . 264BU-22 $xxxxx: Error Writing Stat File (full file name) . . . . . . . . . . . . . . . . . . 264BU-23 $xxxxx: Balance Update Is Complete . . . . . . . . . . . . . . . . . . . 264BU-24 $xxxxx: Maintenance File Is


Empty . . . . . . . . . . . . . . . . . . . . . 264BU-26 $xxxxx: Error Reading Status File (full file name) . . . . . . . . . . . . . . . 265BU-27 $xxxxx: Cannot Write To FUP . . 265BU-29 $xxxxx: Cannot Open File LOC File (full file name) . . . . . . . . . . . . 265BU-30 $xxxxx: Keyposition Failed On (full file name) . . . . . . . . . . . . . . . . . . 265BU-31 $xxxxx: Input Is Not Tape Or Disc 265BU-32 $xxxxx: Mode=xx(nn) (full file name) . . . . . . . . . . . . . . . . . . . . . 265BU-32 Time(sec)=yyyy,Maint=zzzzzz,File=rrrrrr,Rate=pppp . . . . . . . . . . . . . . . . . 266BU-33 $xxxxx: Counting The Number Of Records In The Balance File . . . . . 266BU-34 $xxxxx: BFU Is Starting . . . 266BU-35 $xxxxx: Tape Is Not Ready . 266BU-36 $xxxxx: Mount Next Reel . . 266BU-37 $xxxxx: MSG From FUP: (text) . 267BU-38 $xxxxx: Error Opening Config: (full file name) . . . . . . . . . . . . . . . . . . 267BU-39 $xxxxx: Error Reading Config: (full file name) . . . . . . . . . . . . . . . . . . 267BU-40 $xxxxx: Error Opening AP: $Name . . . . . . . . . . . . . . . . . . . . . . . . . . 267

batch headermatch and hold . . . . . . . . . . . . . . 111

batch maintenance file . . . . . . . . . . . . . 25

batch trailermatch and hold . . . . . . . . . . . . . . 112

BU-01 $xxxxx: Cannot Open Maintenance Input (full file name) . . . . . . . . . . 262

BU-02 $xxxxx: Error Reading Data From Tape (full name) . . . . . . . . . . . . . 262

BU-03 $xxxxx: Cannot Open Control File (full file name) . . . . . . . . . . . . . . . . . 262

BU-04 $xxxxx: Cannot Find Control File (full file name) . . . . . . . . . . . . . . . . . 262

BU-05 $xxxxx: Cannot Find Status File (full file name) . . . . . . . . . . . . . . . . . 263

BU-06 $xxxxx: Cannot Open Status File (full file name) . . . . . . . . . . . . . . . . . 263

BU-07 $xxxxx: Error Reading Disc . . . 263

BU-08 $xxxxx: Control Record Missing 263

BU-09 $xxxxx: Error Reading Control File (full file name) . . . . . . . . . . . . . . 263

BU-10 $xxxxx: Error Opening Balance File (full file name) . . . . . . . . . . . . . . 263

BU-11 $xxxxx: File Name Not Valid (full file name) . . . . . . . . . . . . . . . . . . . . 263

BU-12 $xxxxx: Unrecognized Option In Start-Up . . . . . . . . . . . . . . . . . . . . . . . 263

BU-13 $xxxxx: Cannot Open COM MOM . .263

BU-14 $xxxxx: Cannot Write To COM MOM 263

BU-15 $xxxxx: BFU Is Not Named It Must Be . . . . . . . . . . . . . . . . . . . . . . . . . 264

BU-16 $xxxxx: Newprocess On FUP Failed Error xxx . . . . . . . . . . . . . . . . . . 264

BU-17 $xxxxx: Cannot Open FUP . . . . 264

BU-18 $xxxxx: Error Reading BAL File 264

BU-19 $xxxxx: Cannot Open The ALT File (full file name) . . . . . . . . . . . . . . 264

BU-20 $xxxxx: Cannot Rename File (full file name) . . . . . . . . . . . . . . . . . . . . 264

BU-21 $xxxxx: Error Writing BAL File (full file name) . . . . . . . . . . . . . . . . . . . . 264

BU-22 $xxxxx: Error Writing Stat File (full file name) . . . . . . . . . . . . . . . . . . . . 264

BU-23 $xxxxx: Balance Update Is Complete 264

BU-24 $xxxxx: Maintenance File Is Empty .264

BU-25 $xxxxx: Error On Alternate File (full file name) . . . . . . . . . . . . . . . . . . . . 264

BU-26 $xxxxx: Error Reading Status File (full file name) . . . . . . . . . . . . . . . . . 265

BU-27 $xxxxx: Cannot Write To FUP . . 265


BU-29 $xxxxx: Cannot Open File LOC File (full file name) . . . . . . . . . . . . . . 265

BU-30 $xxxxx: Keyposition Failed On (full file name) . . . . . . . . . . . . . . . . . . . . 265

BU-31 $xxxxx: Input Is Not Tape Or Disc . . 265

BU-32 $xxxxx: Mode=xx(nn) (full file name) 265

BU-32 Time(sec)=yyyy,Maint=zzzzzz,File=rrrrrr,Rate=pppp . . . . . . . . . . . . . . . 266

BU-33 $xxxxx: Counting The Number Of Records In The Balance File . . . . 266

BU-34 $xxxxx: BFU Is Starting . . . . . . 266

BU-35 $xxxxx: Tape Is Not Ready . . . . 266

BU-36 $xxxxx: Mount Next Reel . . . . . 266

BU-37 $xxxxx: MSG From FUP: (text) . 267

BU-38 $xxxxx: Error Opening Config: (full file name) . . . . . . . . . . . . . . . . . . . . 267

BU-39 $xxxxx: Error Reading Config: (full file name) . . . . . . . . . . . . . . . . . . . . 267

BU-40 $xxxxx: Error Opening AP: $Name . 267

Ccard collection styles . . . . . . . . . . . . . 175

Card Issuer File Update Request for ISO (0382) . . . . . . . . . . . . . . . . . . . . . 70

Card Management Group InformationCH18A . . . . . . . . . . . . . . . . . . . . 166CH18B . . . . . . . . . . . . . . . . . . . . 168CH18C . . . . . . . . . . . . . . . . . . . . 171CH18D . . . . . . . . . . . . . . . . . . . . 174

Card Management Member InformationCH19A . . . . . . . . . . . . . . . . . . . . 175CH19B . . . . . . . . . . . . . . . . . . . . 181

Card Validation InformationCH22A . . . . . . . . . . . . . . . . . . . . 184CH22B . . . . . . . . . . . . . . . . . . . . 187

card/account status valid values . . . . . 291

Cardholder InformationCH01A . . . . . . . . . . . . . . . . . . . . 135

cardholder informationadding . . . . . . . . . . . . . . . . . . . . . . 35deleting . . . . . . . . . . . . . . . . . . . . . 35updating . . . . . . . . . . . . . . . . . . . . 36

Cardholder Maintenance . . . . . . . . . . . 10

cardholder validation informationadding . . . . . . . . . . . . . . . . . . . . . . 42deleting . . . . . . . . . . . . . . . . . . . . . 41updating . . . . . . . . . . . . . . . . . . . . 43

cardholder’s balancematch and hold . . . . . . . . . . . . . . 105

Cconnex™ on HP NonStop® AP parametersinstallation considerations . . . . . . . 128

CH01A, Cardholder Information . . . . . 135

CH02A, Track II Information . . . . . . . . 141

CH03A, Account Information . . . . . . . . 145

CH03B, Account Information . . . . . . . . 149

CH04A, Override Limits Information . . 154

CH06A, Hold List Information . . . . . . . 157

CH08A, Name Information . . . . . . . . . 160

CH09A - Override Expire . . . . . . . . . . 162

CH14A - Additional Card Information . . 164

CH18A, Card Management Group Information . . . . . . . . . . . . . . . . 166

CH18B, Card Management Group Information . . . . . . . . . . . . . . . . 168

CH18C, Card Management Group Information . . . . . . . . . . . . . . . . 171

CH18D, Card Management Group Information . . . . . . . . . . . . . . . . 174

CH19A, Card Management Member Information . . . . . . . . . . . . . . . . 175

CH19B, Card Management Member Information . . . . . . . . . . . . . . . . 181

CH1AA, Consolidated AVS Group . . . . 237


CH1AB, Consolidated AVS Group . . . 239

CH1AC, Consolidated AVS Group . . . 240

CH22A, Card Validation Information . . 184

CH22B, Card Validation Information . . 187

CH23A, Fraud Control Information . . . 191

CH50A, VAU/ABU Information . . . . . . 193

CIMS informationadding . . . . . . . . . . . . . . . . . . . . . 46deleting . . . . . . . . . . . . . . . . . . . . . 45updating . . . . . . . . . . . . . . . . . . . . 47

codesreject reason . . . . . . . . . . . . . . . . 271transaction type . . . . . . . . . . . . . . 279

Connex™ on HP NonStop® AP parameters 128

parameters . . . . . . . . . . . . . . . . . 130processing information . . . . . . . . . 128run statement parameters . . . . . . . 129

Consolidated AVS GroupCH1AA . . . . . . . . . . . . . . . . . . . . 237CH1AB . . . . . . . . . . . . . . . . . . . . 239CH1AC . . . . . . . . . . . . . . . . . . . . 240

control number . . . . . . . . . . . . . . . . . . 26

Ddeleting . . . . . . . . . . . . . . . . . . . . . . . 63

account detail information . . . . . . . . 37cardholder validation information . . . 41CIMS information . . . . . . . . . . . . . . 45fraud information . . . . . . . . . . . . . . 50name search information . . . . . . . . 56

deleting account detail, cardholder and fraud information . . . . . . . . . . . . . . . . . 35

deleting informationmultiple products . . . . . . . . . . . . . . 63

detail recordmatch and hold . . . . . . . . . . . . . . 113

detail records . . . . . . . . . . . . . . . . . . . 35

detail segments . . . . . . . . . . . . . . . . . . 29

diskette file format . . . . . . . . . . . . . . . . 32

dummy record sample . . . . . . . . . . . . . 35

dummy records . . . . . . . . . . . . . . . . . . 33

duplicating holds . . . . . . . . . . . . . . . . 106

Eend-of-day

balance refresh . . . . . . . . . . . . . . . 88

entry addendummatch and hold . . . . . . . . . . . . . . 114

errorresubmitting files . . . . . . . . . . . . . . 60

Ffile header record

match and hold . . . . . . . . . . . . . . 109

file trailer recordmatch and hold . . . . . . . . . . . . . . 110

file transmission formatfor initial load . . . . . . . . . . . . . . . . . 32

flowbalance refresh . . . . . . . . . . . . . . . 87

Format 8 Messages . . . . . . . . . . . . . . . 72

FR01A, Fraud Information . . . . . . . . . 198

FR01B, Fraud Information . . . . . . . . . 200

FR02A, Fraud Activity Information . . . . 202

FR02B, Fraud Activity Information . . . . 204

FR03A, Fraud Member Information . . . 206

FR03B, Fraud Member Information . . . 208

Fraud Activity InformationFR02A . . . . . . . . . . . . . . . . . . . . . 202FR02B . . . . . . . . . . . . . . . . . . . . . 204

Fraud Control InformationCH23A . . . . . . . . . . . . . . . . . . . . 191

Fraud InformationFR01A . . . . . . . . . . . . . . . . . . . . . 198


fraud informationadding . . . . . . . . . . . . . . . . . . 35, 51deleting . . . . . . . . . . . . . . . . . . 35, 50submitting . . . . . . . . . . . . . . . . . . . 50updating . . . . . . . . . . . . . . . . . 36, 53

Fraud Member InformationFR03A . . . . . . . . . . . . . . . . . . . . 206FR03B . . . . . . . . . . . . . . . . . . . . 208

Hhash totals . . . . . . . . . . . . . . . . . . . . . 33

header recordsample for normal transmission . . . . 26

header record samplenormal transmission . . . . . . . . . . . . 27

header records . . . . . . . . . . . . . . . . . . 26

Hold List InformationCH06A . . . . . . . . . . . . . . . . . . . . 157

IIBM® settlement parameters . . . . . . . 131

AP hold program abend and return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 133update institution entity row . . . . . 131

initial load . . . . . . . . . . . . . . . . . . . . . . 31

InternetCardholder Maintenance . . . . . . . . 10

ISO message . . . . . . . . . . . . . . . . . . . 70

JJCL . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Mmaintenance messages

APB-018 - AP DATABASE RECORD

ALREADY EXISTS . . . . . . . . . . . . 244APB-019 - EXCEEDED 100 OUTSTANDING FILE OPERATIONS . .244APB-020 - INVALID RECORD NAME . .245APB-021 - INVALID SEGMENT ID . 245APB-022 - INVALID OR UNEXPECTED OCCURRENCE SECTION . . . . . . 245APB-023 - INVALID FILE UPDATE CODE . . . . . . . . . . . . . . . . . . . . . 245APB-024 - ADD OPERATION REQUIRES ADD FILE UPDATE CODE 245APB-025 - INVALID PIN AUTHORIATION FLAG . . . . . . . . . . . . . . . . . . . . . 245APB-026 - INVALID LEDGER BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . 246APB-027 - INVALID AVAILABLE BALANCE . . . . . . . . . . . . . . . . . . 246APB-028 - INVALID CREDIT LINE AMOUNT . . . . . . . . . . . . . . . . . . . 246APB-029 - INVALID OVERDRAFT AMOUNT . . . . . . . . . . . . . . . . . . . 246APB-030 - INVALID CARDHOLDER PAN/PLASTIC NUMBER . . . . . . . . 246APB-031 - INVALID LIMIT AMOUNT . .246APB-032 - INVALID LIMIT USES . . 247APB-033 - INVALID INCREMENT AMOUNT . . . . . . . . . . . . . . . . . . . 247APB-034 - INVALID MINIMUM AMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . 247APB-035 - INVALID DEPOSIT PERCENTAGE . . . . . . . . . . . . . . . 247APB-036 - EXCEEDED 200 BATCH RECORDS PER CH/AD RECORD 247APB-037 - EXCEEDED 100 LOG RECORDS PER CH/AD RECORD 247APB-038 - FIRST RECORD IS NOT A SEGMENT 01 RECORD . . . . . . . . 248APB-039 - EXCEEDED 32000 EDIT TABLE ENTRIES . . . . . . . . . . . . . 248APB-040 - OCCURRENCE DOES NOT EXIST . . . . . . . . . . . . . . . . . . . . . 248APB-041 - OCCURRENCE ALREADY


EXISTS . . . . . . . . . . . . . . . . . . . . 248APB-042 - IDENTIFER DOES NOT EXIST (xxxxxxxxxx) . . . . . . . . . . . 248APB-043 - INVALID CARD/ACCOUNT STATUS CODE . . . . . . . . . . . . . . 248APB-044 - INVALID CARD/ACCOUNT ACCESS(ES) . . . . . . . . . . . . . . . 249APB-045 - CARD/ACCOUNT DOES NOT HAVE AN ACCESS . . . . . . . 249APB-046 - INVALID FINANCIAL INSTITUTION ID . . . . . . . . . . . . . 249APB-047 - INVALID ACCOUNT TYPE . 249APB-048 - INVALID ACCOUNT NUMBER . . . . . . . . . . . . . . . . . . 249APB-049 - INVALID CARD/ACCOUNT HOLD MATCH DATA . . . . . . . . . . 249APB-050 - INVALID OAR SELECT TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 249APB-051 - INVALID PRIMARY ACCOUNT INDICATOR . . . . . . . . 250APB-052 - INVALID FUNDING ACCOUNT INDICATOR . . . . . . . . 250APB-053 - INVALID ACCESS GROUP 250APB-054 - INVALID LIMIT GROUP ID . 250APB-055 - INVALID DATE FORMAT/VALUE (YYMM) . . . . . . . . . . . . . . 250APB-056 - INVALID LIMIT TYPE ID 250APB-057 - INVALID CARDHOLDER ADDRESS . . . . . . . . . . . . . . . . . 250APB-058 - INVALID CARDHOLDER CITY . . . . . . . . . . . . . . . . . . . . . . 251APB-059 - INVALID CARDHOLDER STATE . . . . . . . . . . . . . . . . . . . . . 251APB-060 - INVALID CARDHOLDER ZIP CODE . . . . . . . . . . . . . . . . . . . . . 251APB-061 - INVALID CARD CONDITION STATUS . . . . . . . . . . . . . . . . . . . 251APB-062 - INVALID AUTOMATIC ISSUE INDICATOR . . . . . . . . . . . . . . . . . 251APB-063 - INVALID MEMBER NUMBER . . . . . . . . . . . . . . . . . . . . . . . . . . 251APB-064 - INVALID CARDHOLDER NAME . . . . . . . . . . . . . . . . . . . . . 251APB-065 - INVALID CARD ORDER

TYPE . . . . . . . . . . . . . . . . . . . . . 252APB-066 - INVALID CARD ORDER STATUS . . . . . . . . . . . . . . . . . . . . 252APB-067 - INVALID CARD ISSUE REASON . . . . . . . . . . . . . . . . . . . 252APB-068 - INVALID CARD REPLACEMENT INDICATOR . . . . 252APB-069 - INVALID CARDHOLDER SEX . . . . . . . . . . . . . . . . . . . . . . . . . . 252APB-070 - INVALID MARITAL STATUS 252APB-071 - INVALID EDUCATION LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . 252APB-072 - INVALID INCOME RANGE .253APB-073 - INVALID FAMILY SIZE . 253APB-074 - INVALID CARDHOLDER DISTANCE . . . . . . . . . . . . . . . . . . 253APB-075 - INVALID RESIDENCE STATUS . . . . . . . . . . . . . . . . . . . . 253APB-076 - INVALID EMPLOYMENT STATUS . . . . . . . . . . . . . . . . . . . . 253APB-077 - INVALID DATE FORMAT/VALUE (YYYYMMDD) . . . . . . . . . 253APB-078 - CONTROL NUMBER DOES NOT EXIST (AUTOMATIC FORCE) 253APB-079 - CONTROL NUMBER MISMATCH (PREVIOUS/CURRENT: ###/###) . . . . . . . . . . . . . . . . . . . 254APB-080 - FAILED TO FIND INST/CARD GROUP . . . . . . . . . . . . . . . . . . . . 254APB-081 - FAILED TO FIND DEFAULT LMTGRP . . . . . . . . . . . . . . . . . . . 254APB-082 - INVALID CARD ACTIVATION 254APB-083 - ADA RECORD ALREADY EXISTS IN APADAA FILE . . . . . . . 254APB-084 - CARDHOLDER NAME NOT FORMATTED CORRECTLY . . . . . 254APB-085 - CARDMAN=Y, CH1AA/AB/AC NOT PERMITTED . . . . . . . . . . . . 254APB-086 - EXCEEDED 50 BALANCE UPDATE FILES . . . . . . . . . . . . . . 254APB-087 - FAILED TO APPLY BALANCE UPDATE RECORD . . . . . . . . . . . . 255APB-088 - ONLY ONE FUNDING


ACCOUNT PER CARDHOLDER . 255APB-094 - INVALID LAST-MIN-BAL-AMT . . . . . . . . . . . . . . . . . . . . . . . . . . 255APB-095 - INVALID LAST-ADDR-CHG-DATE . . . . . . . . . . . . . . . . . . . . . 255APB-096 - INVALID LAST-PIN-CHG-DATE . . . . . . . . . . . . . . . . . . . . . 255APB-097 - INVALID LAST-PIN-CHG-DATE . . . . . . . . . . . . . . . . . . . . . 255APB-098 - INVALID LAST-DEP-AMT . . 255APB-099 - INVALID LAST-PIN-DATE . . 255APB-100 - INVALID LAST-DEP-DATE . 255APB-101 - INVALID LAST-ATM-DATE . 255APB-102 - INVALID LAST-AMT-AMT . . 256APB-103 - INVALID LAST-PIN-AMT 256APB-104 - INVALID LAST-OFFLINE-DATE . . . . . . . . . . . . . . . . . . . . . 256APB-105 - INVALID LAST-OFFLINE-AMT . . . . . . . . . . . . . . . . . . . . . . 256APB-106 - INVALID SEND-TO-CASE . 256APB-107 - INVALID CUST-SINCE-DATE 256APB-108 - INVALID LAST-STATEMENT-DATE . . . . . . . . . . . . . . . . . . . . . 256APB-109 - INVALID LAST-MINIBAL-DATE . . . . . . . . . . . . . . . . . . . . . 256APB-110 - INVALID LAST-DEP-DATE . 256APB-111 - INVALID DATE-OF-BIRTH . 256APB-112 - INVALID ACTIVATION-TIME-STAMP . . . . . . . . . . . . . . . . . . . . 257APB-113 - INVALID PREV-CRD-ACT . 257APB-114 - INVALID POST-AUTH-EXCLUDE . . . . . . . . . . . . . . . . . . 257APB-115 - INVALID IN-AUTH-EXCLUDE

. . . . . . . . . . . . . . . . . . . . . . . . . . 257APB-116 - INVALID IN-AUTH-REVIEW 257APB-117 - INVALID DO-NOT-DISTURB-DATE . . . . . . . . . . . . . . . . . . . . . . 257APB-118 - FAILED UPDATE OF CH23 SEGMENT . . . . . . . . . . . . . . . . . . 257APB-119 - FAILED UPDATE OF FR02 SEGMENT . . . . . . . . . . . . . . . . . . 257APB-120 - FAILED UPDATE OF CH22 SEGMENT . . . . . . . . . . . . . . . . . . 258APB-121 - FAILED UPDATE OF CH18 SEGMENT . . . . . . . . . . . . . . . . . . 258

maintenance methodsonline host maintenance . . . . . . . . . 68

Maintenance Reply Accept Message for Format 8 (I52) . . . . . . . . . . . . . . . 72

Maintenance Reply Reject Message for Format 8 (I53) . . . . . . . . . . . . . . . 72

Maintenance Request Message for Format 8 (I51) . . . . . . . . . . . . . . . . . . . . . . 72

match and hold . . . . . . . . . . . . . . . . . . 98batch header . . . . . . . . . . . . . . . . 111batch trailer . . . . . . . . . . . . . . . . . 112cardholder’s balance . . . . . . . . . . . 105criteria . . . . . . . . . . . . . . . . . . . . . . 99detail record . . . . . . . . . . . . . . . . . 113duplicating holds . . . . . . . . . . . . . 106entry addendum . . . . . . . . . . . . . . 114file header record . . . . . . . . . . . . . 109file trailer record . . . . . . . . . . . . . . 110flow . . . . . . . . . . . . . . . . . . . . . . . . 22for Debit MasteCard . . . . . . . . . . . 102for pre-authorization . . . . . . . . . . . 101for Visa Check . . . . . . . . . . . . . . . 103host performs . . . . . . . . . . . . . . . . 105no match and hold . . . . . . . . . . . . 105options . . . . . . . . . . . . . . . . . . . . 104raw data file . . . . . . . . . . . . . . . . . 106raw data file sample . . . . . . . . . . . 107record layout . . . . . . . . . . . . . . . . 108


message formats . . . . . . . . . . . . . . . . 73account detail . . . . . . . . . . . . . . . . 82account hold information . . . . . . . . 85account information . . . . . . . . . . . . 77card information . . . . . . . . . . . . . . . 74hold list . . . . . . . . . . . . . . . . . . . . . 80name information . . . . . . . . . . . . . . 81overdraft information . . . . . . . . . . . 84override . . . . . . . . . . . . . . . . . . . . . 79track 2 . . . . . . . . . . . . . . . . . . . . . . 76

message typesAP## . . . . . . . . . . . . . . . . . . . . . 244AP### . . . . . . . . . . . . . . . . . . . . 244APB### . . . . . . . . . . . . . . . . . . . 244APM### . . . . . . . . . . . . . . . . . . . 244Authorization Processor . . . . . . . . 244BU## . . . . . . . . . . . . . . . . . . . . . 244

messages$xxxxx: I/O Error on $TAPE, ERROR = nnn . . . . . . . . . . . . . . . . . . . . . . . 262AP Batch . . . . . . . . . . . . . . . . . . . 244APB-018 - AP DATABASE RECORD ALREADY EXISTS . . . . . . . . . . . . 244APB-019 - EXCEEDED 100 OUTSTANDING FILE OPERATIONS . . 244APB-020 - INVALID RECORD NAME . 245APB-021 - INVALID SEGMENT ID 245APB-022 - INVALID OR UNEXPECTED OCCURRENCE SECTION . . . . . . 245APB-023 - INVALID FILE UPDATE CODE . . . . . . . . . . . . . . . . . . . . . 245APB-024 - ADD OPERATION REQUIRES ADD FILE UPDATE CODE 245APB-025 - INVALID PIN AUTHORIATION FLAG . . . . . . . . . . . . . . . . . . . . . 245APB-026 - INVALID LEDGER BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . 246APB-027 - INVALID AVAILABLE BALANCE . . . . . . . . . . . . . . . . . . 246APB-028 - INVALID CREDIT LINE AMOUNT . . . . . . . . . . . . . . . . . . 246APB-029 - INVALID OVERDRAFT

AMOUNT . . . . . . . . . . . . . . . . . . . 246APB-030 - INVALID CARDHOLDER PAN/PLASTIC NUMBER . . . . . . . . 246APB-031 - INVALID LIMIT AMOUNT . .246APB-032 - INVALID LIMIT USES . . 247APB-033 - INVALID INCREMENT AMOUNT . . . . . . . . . . . . . . . . . . . 247APB-034 - INVALID MINIMUM AMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . 247APB-035 - INVALID DEPOSIT PERCENTAGE . . . . . . . . . . . . . . . 247APB-036 - EXCEEDED 200 BATCH RECORDS PER CH/AD RECORD 247APB-037 - EXCEEDED 100 LOG RECORDS PER CH/AD RECORD 247APB-038 - FIRST RECORD IS NOT A SEGMENT 01 RECORD . . . . . . . . 248APB-039 - EXCEEDED 32000 EDIT TABLE ENTRIES . . . . . . . . . . . . . 248APB-040 - OCCURRENCE DOES NOT EXIST . . . . . . . . . . . . . . . . . . . . . 248APB-041 - OCCURRENCE ALREADY EXISTS . . . . . . . . . . . . . . . . . . . . 248APB-042 - IDENTIFER DOES NOT EXIST (xxxxxxxxxx) . . . . . . . . . . . 248APB-043 - INVALID CARD/ACCOUNT STATUS CODE . . . . . . . . . . . . . . 248APB-046 - INVALID FINANCIAL INSTITUTION ID . . . . . . . . . . . . . 249APB-047 - INVALID ACCOUNT TYPE .249APB-048 - INVALID ACCOUNT NUMBER . . . . . . . . . . . . . . . . . . . 249APB-049 - INVALID CARD/ACCOUNT HOLD MATCH DATA . . . . . . . . . . . 249APB-050 - INVALID OAR SELECT TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 249APB-051 - INVALID PRIMARY ACCOUNT INDICATOR . . . . . . . . 250APB-052 - INVALID FUNDING ACCOUNT INDICATOR . . . . . . . . 250APB-053 - INVALID ACCESS GROUP .250APB-054 - INVALID LIMIT GROUP ID .250APB-055 - INVALID DATE FORMAT/


VALUE (YYMM) . . . . . . . . . . . . . . 250APB-056 - INVALID LIMIT TYPE ID 250APB-057 - INVALID CARDHOLDER ADDRESS . . . . . . . . . . . . . . . . . 250APB-058 - INVALID CARDHOLDER CITY . . . . . . . . . . . . . . . . . . . . . . 251APB-059 - INVALID CARDHOLDER STATE . . . . . . . . . . . . . . . . . . . . . 251APB-060 - INVALID CARDHOLDER ZIP CODE . . . . . . . . . . . . . . . . . . . . . 251APB-061 - INVALID CARD CONDITION STATUS . . . . . . . . . . . . . . . . . . . 251APB-062 - INVALID AUTOMATIC ISSUE INDICATOR . . . . . . . . . . . . . . . . . 251APB-063 - INVALID MEMBER NUMBER . . . . . . . . . . . . . . . . . . . . . . . . . . 251APB-064 - INVALID CARDHOLDER NAME . . . . . . . . . . . . . . . . . . . . . 251APB-065 - INVALID CARD ORDER TYPE . . . . . . . . . . . . . . . . . . . . . 252APB-067 - INVALID CARD ISSUE REASON . . . . . . . . . . . . . . . . . . 252APB-068 - INVALID CARD REPLACEMENT INDICATOR . . . . 252APB-069 - INVALID CARDHOLDER SEX . . . . . . . . . . . . . . . . . . . . . . . . . . 252APB-070 - INVALID MARITAL STATUS 252APB-071 - INVALID EDUCATION LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . 252APB-072 - INVALID INCOME RANGE . 253APB-073 - INVALID FAMILY SIZE . 253APB-074 - INVALID CARDHOLDER DISTANCE . . . . . . . . . . . . . . . . . 253APB-075 - INVALID RESIDENCE STATUS . . . . . . . . . . . . . . . . . . . 253APB-076 - INVALID EMPLOYMENT STATUS . . . . . . . . . . . . . . . . . . . 253APB-077 - INVALID DATE FORMAT/VALUE (YYYYMMDD) . . . . . . . . . 253APB-078 - CONTROL NUMBER DOES NOT EXIST (AUTOMATIC FORCE) 253APB-079 - CONTROL NUMBER MISMATCH (PREVIOUS/CURRENT: ###/###) . . . . . . . . . . . . . . . . . . . 254APB-080 - FAILED TO FIND INST/CARD

GROUP . . . . . . . . . . . . . . . . . . . . 254APB-081 - FAILED TO FIND DEFAULT LMTGRP . . . . . . . . . . . . . . . . . . . 254APB-082 - INVALID CARD ACTIVATION 254APB-083 - ADA RECORD ALREADY EXISTS IN APADAA FILE . . . . . . . 254APB-084 - CARDHOLDER NAME NOT FORMATTED CORRECTLY . . . . . 254APB-085 - CARDMAN=Y, CH1AA/AB/AC NOT PERMITTED . . . . . . . . . . . . 254APB-086 - EXCEEDED 50 BALANCE UPDATE FILES . . . . . . . . . . . . . . 254APB-087 - FAILED TO APPLY BALANCE UPDATE RECORD . . . . . . . . . . . . 255APB-088 - ONLY ONE FUNDING ACCOUNT PER CARDHOLDER . . 255APB-094 - INVALID LAST-MIN-BAL-AMT . . . . . . . . . . . . . . . . . . . . . . . . . . 255APB-095 - INVALID LAST-ADDR-CHG-DATE . . . . . . . . . . . . . . . . . . . . . . 255APB-096 - INVALID LAST-PIN-CHG-DATE . . . . . . . . . . . . . . . . . . . . . . 255APB-097 - INVALID LAST-PIN-CHG-DATE . . . . . . . . . . . . . . . . . . . . . . 255APB-098 - INVALID LAST-DEP-AMT . .255APB-099 - INVALID LAST-PIN-DATE . .255APB-100 - INVALID LAST-DEP-DATE .255APB-101 - INVALID LAST-ATM-DATE . .255APB-102 - INVALID LAST-AMT-AMT . .256APB-103 - INVALID LAST-PIN-AMT 256APB-104 - INVALID LAST-OFFLINE-DATE . . . . . . . . . . . . . . . . . . . . . . 256APB-105 - INVALID LAST-OFFLINE-AMT . . . . . . . . . . . . . . . . . . . . . . 256APB-106 - INVALID SEND-TO-CASE . .256APB-107 - INVALID CUST-SINCE-DATE 256APB-108 - INVALID LAST-STATEMENT-DATE . . . . . . . . . . . . . . . . . . . . . . 256APB-109 - INVALID LAST-MINIBAL-


DATE . . . . . . . . . . . . . . . . . . . . . 256APB-110 - INVALID LAST-DEP-DATE . 256APB-111 - INVALID DATE-OF-BIRTH . 256APB-112 - INVALID ACTIVATION-TIME-STAMP . . . . . . . . . . . . . . . . . . . . 257APB-113 - INVALID PREV-CRD-ACT . 257APB-114 - INVALID POST-AUTH-EXCLUDE . . . . . . . . . . . . . . . . . . 257APB-115 - INVALID IN-AUTH-EXCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . 257APB-116 - INVALID IN-AUTH-REVIEW 257APB-117 - INVALID DO-NOT-DISTURB-DATE . . . . . . . . . . . . . . . . . . . . . 257APB-118 - FAILED UPDATE OF CH23 SEGMENT . . . . . . . . . . . . . . . . . 257APB-119 - FAILED UPDATE OF FR02 SEGMENT . . . . . . . . . . . . . . . . . 257APB-120 - FAILED UPDATE OF CH22 SEGMENT . . . . . . . . . . . . . . . . . 258APB-121 - FAILED UPDATE OF CH18 SEGMENT . . . . . . . . . . . . . . . . . 258balance update . . . . . . . . . . . . . . 262BU-01 $xxxxx: Cannot Open Maintenance Input (full file name) . 262BU-02 $xxxxx: Error Reading Data From Tape (full name) . . . . . . . . . . . . . . 262BU-03 $xxxxx: Cannot Open Control File (full file name) . . . . . . . . . . . . . . . 262BU-04 $xxxxx: Cannot Find Control File (full file name) . . . . . . . . . . . . . . . 262BU-05 $xxxxx: Cannot Find Status File (full file name) . . . . . . . . . . . . . . . 263BU-07 $xxxxx: Error Reading Disc 263BU-08 $xxxxx: Control Record Missing 263BU-09 $xxxxx: Error Reading Control File (full file name) . . . . . . . . . . . . . . . 263BU-10 $xxxxx: Error Opening Balance File (full file name) . . . . . . . . . . . . 263BU-11 $xxxxx: File Name Not Valid (full file name) . . . . . . . . . . . . . . . . . . 263BU-12 $xxxxx: Unrecognized Option In

Start-Up . . . . . . . . . . . . . . . . . . . . 263BU-13 $xxxxx: Cannot Open COM MOM . . . . . . . . . . . . . . . . . . . . . . . . . . 263BU-14 $xxxxx: Cannot Write To COM MOM . . . . . . . . . . . . . . . . . . . . . . 263BU-15 $xxxxx: BFU Is Not Named It Must Be . . . . . . . . . . . . . . . . . . . . . . . . 264BU-16 $xxxxx: Newprocess On FUP Failed Error xxx . . . . . . . . . . . . . . 264BU-17 $xxxxx: Cannot Open FUP . 264BU-19 $xxxxx: Cannot Open The ALT File (full file name) . . . . . . . . . . . . 264BU-20 $xxxxx: Cannot Rename File (full file name) . . . . . . . . . . . . . . . . . . 264BU-21 $xxxxx: Error Writing BAL File (full file name) . . . . . . . . . . . . . . . . . . 264BU-22 $xxxxx: Error Writing Stat File (full file name) . . . . . . . . . . . . . . . . . . 264BU-23 $xxxxx: Balance Update Is Complete . . . . . . . . . . . . . . . . . . . 264BU-24 $xxxxx: Maintenance File Is Empty . . . . . . . . . . . . . . . . . . . . . 264BU-25 $xxxxx: Error On Alternate File (full file name) . . . . . . . . . . . . . . . 264BU-26 $xxxxx: Error Reading Status File (full file name) . . . . . . . . . . . . . . . 265BU-27 $xxxxx: Cannot Write To FUP . .265BU-29 $xxxxx: Cannot Open File LOC File (full file name) . . . . . . . . . . . . 265BU-30 $xxxxx: Keyposition Failed On (full file name) . . . . . . . . . . . . . . . . . . 265BU-31 $xxxxx: Input Is Not Tape Or Disc 265BU-32 $xxxxx: Mode=xx(nn) (full file name) . . . . . . . . . . . . . . . . . . . . . 265BU-32 Time(sec)=yyyy,Maint=zzzzzz,File=rrrrrr,Rate=pppp . . . . . . . . . . . . . . . . . . 266BU-33 $xxxxx: Counting The Number Of Records In The Balance File . . . . . 266BU-34 $xxxxx: BFU Is Starting . . . 266BU-35 $xxxxx: Tape Is Not Ready . 266BU-36 $xxxxx: Mount Next Reel . . 266BU-37 $xxxxx: MSG From FUP: (text) .267BU-38 $xxxxx: Error Opening Config: (full


file name) . . . . . . . . . . . . . . . . . . 267BU-39 $xxxxx: Error Reading Config: (full file name) . . . . . . . . . . . . . . . . . . 267BU-40 $xxxxx: Error Opening AP: $Name . . . . . . . . . . . . . . . . . . . . . . . . . . 267

NName Information

CH08A . . . . . . . . . . . . . . . . . . . . 160

Name Searchupdating . . . . . . . . . . . . . . . . . . . . 58

name search informationadding . . . . . . . . . . . . . . . . . . . . . 57deleting . . . . . . . . . . . . . . . . . . . . . 56submitting . . . . . . . . . . . . . . . . . . . 56

NJEsending records . . . . . . . . . . . . . . . 96

Oongoing maintenance

submitting . . . . . . . . . . . . . . . . . . . 32

online host maintenance . . . . . . . . . . . 68

optional featuresmatch and hold . . . . . . . . . . . . . . . 98

Overdraft InformationAD02A . . . . . . . . . . . . . . . . . . . . 219AD02B . . . . . . . . . . . . . . . . . . . . 221

Override Limits InformationCH04A . . . . . . . . . . . . . . . . . . . . 154

PPersonix Card Collection Series . . . . . 179

photo ID . . . . . . . . . . . . . . . . . . . . . . 175

Rraw data file . . . . . . . . . . . . . . . . . . . . 106

record layoutbalance refresh . . . . . . . . . . . . . . . 89match and hold . . . . . . . . . . . . . . 108

reject reason codes . . . . . . . . . . . . . . 271

report samples . . . . . . . . . . . . . . . . . . 61AP Batch Load Exception Report . . . 60

reportsAP Batch Load Exception . . . . . . . . 60AP Hold Detail Report . . . . . . . . . . 117AP Hold Detail Report with PAN . . 120AP Hold Summary Report . . . . . . . 125

resubmitting files . . . . . . . . . . . . . . . . . 60

RJEsending records . . . . . . . . . . . . . . . 96

Ssegment fields

AP . . . . . . . . . . . . . . . . . . . . . . . . . 29

segmentsdetail . . . . . . . . . . . . . . . . . . . . . . . 29required order . . . . . . . . . . . . . . . . 29

sending recordsNJE . . . . . . . . . . . . . . . . . . . . . . . . 96RJE . . . . . . . . . . . . . . . . . . . . . . . . 96

spaces . . . . . . . . . . . . . . . . . . . . . . . . 69

submittingfraud information . . . . . . . . . . . . . . 50online host maintenance . . . . . . . . . 68

submitting account detail information . . . 36

submitting an initial load . . . . . . . . . . . . 31

submitting cardholder validation information 41

submitting CIMS information . . . . . . . . . 45

submitting detail records . . . . . . . . . . . . 35

submitting name search information . . . 56


submitting ongoing maintenance . . . . . 32

Ttape file format . . . . . . . . . . . . . . . . . . 32

Track II InformationCH02A . . . . . . . . . . . . . . . . . . . . 141

trailer record . . . . . . . . . . . . . . . . . . . . 27

trailer record sample . . . . . . . . . . . . . . 28

trailer records . . . . . . . . . . . . . . . . . . . 26

transaction type codes . . . . . . . . . . . . 279

Uupdate institution entity row

affected reports/files . . . . . . . . . . . 132field changes . . . . . . . . . . . . 131, 132update distribution parameter row . 132

updating . . . . . . . . . . . . . . . . . . . . . . . 66account detail information . . . . . . . . 39cardholder validation information . . . 43CIMS information . . . . . . . . . . . . . . 47fraud information . . . . . . . . . . . . . . 53

updating account detail, cardholder and fraud information . . . . . . . . . . . . . 36

updating informationmultiple products . . . . . . . . . . . . . . 66

using spaces and asterisks . . . . . . . . . . 69

WWeb

Cardholder Maintenance . . . . . . . . . 10



Statement of Confidentiality

The information contained in or supplied with this document is submitted solely for the purpose ofevaluating the products and services of FIS, and/or its affiliates and subsidiaries. The informationcontained in or supplied with this document, in its entirety, is the confidential and proprietary infor-mation of FIS, and it may not be copied by or disclosed to any person or entity (other than to theintended recipient), without the prior written consent of FIS. With or without FIS’ prior written con-sent, FIS accepts no liability whatsoever for any consequences arising from the reproduction ofthe information contained in or supplied with this document, or from its disclosure to any personor entity, including to the intended recipient. FIS additionally accepts no liability for the use of theinformation contained in, or supplied with this document, by the intended recipient, or by anyother person or entity, with or without FIS’ express prior consent. The intended recipient shall notuse any part of the information contained in, or supplied with this document, in any way to thecompetitive disadvantage of FIS, and will take all steps designed to assure its compliance withthis provision.

This proposal is neither an offer nor intended by FIS, upon acceptance by the intended recipient,or otherwise, to create a binding agreement with FIS. Such an agreement shall be reflected onlyby a definitive contract, executed by both parties.

Trademarks

All other trademarks are the property of their owners.

Company, product, and service names used by FIS within, or supplied with this document maybe trademarks or service marks of other persons or entities.

Copyright

Copyright© 2017 FIS.All Rights Reserved.

AP Technical Reference Manual for Processing Customers · September 2016 V1.5 Appendix A Added the...

Documents

Transcript of AP Technical Reference Manual for Processing Customers · September 2016 V1.5 Appendix A Added the...