Ifx 1.7 - BMS

Interactive Financial Exchange
Version 1.7
Business Message Specification
2000, 2001, 2002, 2003, 2004, 2005 IFX Forum, Inc. All rights reserved.
Interactive Financial Exchange Business Message Specification
Disclaimer
The IFX Forum makes no warranties whatsoever with respect to the contents of this specification. Without limitation, the IFX Forum makes no warranty (i) that the information contained in the specification is accurate, error-free or describes a practically realizable product or service, or (ii) that the product or service described in the specification can be produced or provided without infringing third-party rights or violating applicable laws or regulations. RESERVATION OF RIGHTS: The contents of this specification are protected by copyright and other intellectual property laws. The IFX Forum expressly reserves all rights in such content.
Version 1.7
April 2005
Table of Contents
1 OVERVIEW.................................................................................................................................1
1.1 INTRODUCTION..................................................................................................................................................1 1.1.1 The IFX Business Message Specification..............................................................................................1 1.1.2 IFX Implementation Specifications.......................................................................................................1 1.2 DESIGN PRINCIPLES...........................................................................................................................................1 1.3 BENEFITS TO FINANCIAL INSTITUTIONS AND SERVICE PROVIDERS.............................................................................3 1.4 BENEFITS TO CONSUMERS AND BUSINESSES...........................................................................................................3
2 STRUCTURE...............................................................................................................................1
2.1 DEFINITIONS.....................................................................................................................................................1 2.1.1 Biller......................................................................................................................................................1 2.1.2 Biller Payment Provider (BPP).............................................................................................................1 2.1.3 Biller Service Provider (BSP)...............................................................................................................1 2.1.4 Client.....................................................................................................................................................1 2.1.5 Customer................................................................................................................................................1 2.1.6 Customer Payment Provider (CPP)......................................................................................................1 2.1.7 Customer Service Provider (CSP).........................................................................................................1 2.1.8 Financial Institution (FI).......................................................................................................................1 2.1.9 Provider.................................................................................................................................................2 2.1.10 Server...................................................................................................................................................2 2.1.11 Service.................................................................................................................................................2 2.1.12 Service Provider (SP)..........................................................................................................................2 2.1.13 May, Should, and Must........................................................................................................................2 2.2 DOCUMENTATION CONVENTIONS..........................................................................................................................3 2.3 DATA TYPES....................................................................................................................................................5 2.3.1 Character...............................................................................................................................................5 2.3.2 Narrow Character.................................................................................................................................5 2.3.3 Binary....................................................................................................................................................5 2.3.4 Boolean..................................................................................................................................................6 2.3.5 YrMon, Date, Time, DateTime, and Timestamp....................................................................................6 2.3.6 Phone Number.....................................................................................................................................10 2.3.7 Decimal................................................................................................................................................10 2.3.8 Long.....................................................................................................................................................11 2.3.9 Currency Amount.................................................................................................................................11 2.3.10 Enum..................................................................................................................................................12 2.3.11 Identifier............................................................................................................................................12 2.3.12 Universally Unique Identifier (UUID)..............................................................................................12 2.3.13 URL....................................................................................................................................................13 2.3.14 HexBin...............................................................................................................................................13 2.4 BUILDING BLOCKS...........................................................................................................................................13 2.4.1 Element................................................................................................................................................14 2.4.2 Aggregate............................................................................................................................................14 2.4.3 Message...............................................................................................................................................14 2.4.4 Service.................................................................................................................................................21 2.4.5 Document.............................................................................................................................................22 2.4.6 Order...................................................................................................................................................23 2.5 NAMING CONVENTION.....................................................................................................................................23 2.5.1 Rules for Naming in the IFX Specification..........................................................................................23 2.6 INTERNATIONAL SUPPORT.................................................................................................................................24 2.6.1 Country Codes.....................................................................................................................................24 2.6.2 Character Sets.....................................................................................................................................24 2.6.3 Reporting Foreign Exchange Transactions.........................................................................................24
ii
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification 2.6.4 Languages and Dialects......................................................................................................................25 2.6.5 Times and Time Zones.........................................................................................................................25 2.6.6 Country-Specific Tags.........................................................................................................................25 2.7 VERSIONING AND SPECIFICATION EVOLUTION......................................................................................................25 2.7.1 Extension and Customization..............................................................................................................25 2.7.2 Mandatory and Optional Elements.....................................................................................................26
3 COMMON ELEMENTS AND AGGREGATES.........................................................................................1

3.1 COMMON ELEMENTS..........................................................................................................................................1 3.1.1 Edit Masks ............................................................................................................................................1 3.1.2 Customer Identifiers..............................................................................................................................2 3.1.3 Request Identifier <RqUID>.................................................................................................................2 3.1.4 Service Provider Reference Identifiers..................................................................................................2 3.1.5 Service Provider Name <SPName>......................................................................................................3 3.1.6 Organization <Org>.............................................................................................................................3 3.1.7 Token <Token>.....................................................................................................................................3 3.1.8 Reversal Reason Code <RevReasonCode>..........................................................................................4 3.2 COMMON AGGREGATES......................................................................................................................................4 3.2.1 Message Headers...................................................................................................................................4 3.2.2 Europay, MasterCard, Visa (EMV) Data..............................................................................................5 3.2.3 Customer Data.....................................................................................................................................14 3.2.4 Person Data.........................................................................................................................................19 3.2.5 Organization Data...............................................................................................................................22 3.2.6 Biller Data...........................................................................................................................................23 3.2.7 Account Data.......................................................................................................................................24 3.2.8 Account Balances................................................................................................................................32 3.2.9 Term Data............................................................................................................................................34 3.2.10 Selection Criteria...............................................................................................................................35 3.2.11 Recurring Model Data.......................................................................................................................36 3.2.12 System Message Data........................................................................................................................37 3.2.13 Industry Identifier Aggregate <IndustId>........................................................................................41 3.2.14 Secrets Aggregates............................................................................................................................41 3.2.15 Payment Instrument Aggregate <PmtInst>......................................................................................42 3.2.16 Fees and Amounts..............................................................................................................................44 3.2.17 Reference Information <RefInfo>.....................................................................................................47 3.2.18 Network Transaction Information Aggregate <NetworkTrnInfo> ..................................................47 3.2.19 Identifier Characteristics Data Aggregate <IdentCharacterData>.................................................48 3.2.20 Point of Service Security Aggregate <POSSecurity>.......................................................................49 3.2.21 Point of Service Capabilities Aggregate <POSCapabilities>..........................................................50 3.2.22 Point of Service Agent Aggregate <POSAgent>..............................................................................50 3.2.23 Point of Service Data Aggregate <PointOfServiceData>................................................................51 3.2.24 Card Logical Data Aggregate <CardLogicalData>........................................................................51 3.2.25 Passport.............................................................................................................................................52 3.2.26 Passbook Acceptance Data <PassbkAcceptData>...........................................................................53 3.2.27 Personal Identification <PersonalIdent>.........................................................................................53 3.2.28 GovIssueIdent....................................................................................................................................54 3.2.29 EmploymentData...............................................................................................................................54 3.2.30 EmployeeIdent...................................................................................................................................55 3.2.31 OtherIdentDoc..................................................................................................................................55
4 SECURITY..................................................................................................................................1
4.1 CHANNEL LEVEL SECURITY VS. APPLICATION LEVEL SECURITY...............................................................................1 4.2 APPLICATION LEVEL SECURITY IN THE IFX SPECIFICATION.....................................................................................1 4.3 SECURITY COMMON ELEMENTS AND AGGREGATES.................................................................................................1 4.3.1 Customer Password Aggregate <CustPswd>.......................................................................................1 4.3.2 Signon Password Aggregate <SignonPswd>.......................................................................................2
Version 1.7
April 2005
iii
Interactive Financial Exchange Business Message Specification 4.3.3 Signon Certificate Aggregate <SignonCert>........................................................................................2 4.3.4 Signon Transport Aggregate <SignonTransport>................................................................................2 4.3.5 Signon Magnetic Stripe/PIN Aggregate <SignonMagPIN>.................................................................3 4.3.6 Session Key <SessKey>........................................................................................................................3 4.4 AUTHENTICATION..............................................................................................................................................4 4.4.1 Description............................................................................................................................................4 4.4.2 Signon....................................................................................................................................................4 4.4.3 Signoff....................................................................................................................................................7
5 THE BASE SERVICE <BASESVC>.................................................................................................1

5.1 BASE SERVICE MESSAGE SUMMARY....................................................................................................................1 5.2 BASE SERVICE COMMON ELEMENTS AND AGGREGATES..........................................................................................5 5.2.1 Service Profile Common Elements........................................................................................................5 5.2.2 Service Profile Common Aggregates.....................................................................................................6 5.2.3 Customer Profile Common Aggregates.................................................................................................8 5.2.4 Party Account Relationship Info <PartyAcctRelInfo>.......................................................................14 5.2.5 Card Preference Record Aggregate <CardPrefRec>.........................................................................16 5.2.6 Card Preference Status Aggregate <CardPrefStatus>.......................................................................17 5.2.7 Card Preference Information Aggregate <CardPrefInfo>.................................................................17 5.2.8 Card Preference Aggregate <CardPref>...........................................................................................17 5.2.9 Card Preference Withdrawal Aggregate <CardPrefMisc>...............................................................17 5.2.10 Card Preference Withdrawal Aggregate <CardPrefWithdrawal>..................................................18 5.2.11 Card Preference Deposit Aggregate <CardPrefDeposit>...............................................................18 5.2.12 Card Preference Message Request Information Aggregate <CardPrefMsgRqInfo>.......................19 5.2.13 Card Preference Message Record Aggregate <CardPrefMsgRec>.................................................19 5.2.14 Posting Session Record Aggregate <PostingSessionRec>...............................................................20 5.2.15 Session Totals Record Aggregate <SessionTotalsRec>...................................................................21 5.3 SERVICE PROFILE............................................................................................................................................22 5.3.1 Description..........................................................................................................................................22 5.3.2 Service Profile Inquiry Message.........................................................................................................22 5.3.3 Holiday Inquiry Message....................................................................................................................24 5.4 CUSTOMER PROFILE.........................................................................................................................................25 5.4.1 Description..........................................................................................................................................25 5.4.2 Customer..............................................................................................................................................28 5.4.3 Customer/Service Link.........................................................................................................................44 5.4.4 Service/Account Link...........................................................................................................................53 5.4.5 Disclosure............................................................................................................................................70 5.4.6 Customer/Disclosure Link...................................................................................................................71 5.5 SECURITY OBJECT...........................................................................................................................................74 5.5.1 Security Object Add.............................................................................................................................74 5.5.2 Security Object Modify........................................................................................................................75 5.5.3 Security Object Inquiry........................................................................................................................76 5.5.4 Security Object Delete.........................................................................................................................77 5.5.5 Security Object Advise.........................................................................................................................78 5.5.6 Security Object Sync............................................................................................................................79 5.6 PARTY TO ACCOUNT RELATIONSHIP ..................................................................................................................80 5.6.1 Party to Account Relationship Add.....................................................................................................80 5.6.2 Party to Account Relationship Delete.................................................................................................82 5.6.3 Party to Account Relationship Inquiry................................................................................................83 5.6.4 Party to Account Relationship Modify................................................................................................85 5.7 EMV CARD OBJECT.......................................................................................................................................87 5.7.1 EMV Card Record Aggregate <EMVCardRec>.................................................................................87 5.7.2 EMV Card Info Aggregate <EMVCardInfo>.....................................................................................87 5.7.3 EMV Card Advice Request <EMVCardAdviseRq>............................................................................87 5.7.4 EMV Card Advise Response <EMVCardAdviseRs>..........................................................................88 5.8 CARD PREFERENCE..........................................................................................................................................88
iv
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification 5.8.1 Card Preference Add Message............................................................................................................88 5.8.2 Card Preference Modify Message.......................................................................................................89 5.8.3 Card Preference Inquiry Message.......................................................................................................91 5.8.4 Card Preference Delete Message........................................................................................................93 5.8.5 Card Preference Audit Message..........................................................................................................94 5.8.6 Card Preference Sync Message...........................................................................................................95 5.8.7 Card Preference Reversal Message....................................................................................................97 5.8.8 Card Preference Status Modify Message............................................................................................99 5.9 POSTING SESSION..........................................................................................................................................100 5.9.2 Posting Session Add..........................................................................................................................101 5.9.3 Posting Session Modify......................................................................................................................102 5.9.4 Posting Session Inquiry.....................................................................................................................104 5.9.5 Posting Session Audit........................................................................................................................105 5.9.6 Posting Session Status Modify...........................................................................................................107 5.9.7 Session Totals Inquiry.......................................................................................................................108 5.10 BASE SERVICE PROFILE <BASESVCPROFINFO>...............................................................................................110 5.10.1 Signon Information Aggregate <SignonInfo>................................................................................111 5.10.2 Enroll Profile Aggregate <EnrollProf>.........................................................................................111
6 THE BANKING SERVICE <BANKSVC>...........................................................................................1

6.1 DESCRIPTION....................................................................................................................................................1 6.1.1 Accounts................................................................................................................................................1 6.1.2 Client-Initiated Actions.........................................................................................................................1 6.2 BANKING SERVICE MESSAGE SUMMARY...............................................................................................................2 6.3 BANKING SERVICE COMMON AGGREGATES.........................................................................................................14 6.3.1 Bank Service Checksum Record Aggregate <BankSvcChkSumRec>.................................................14 6.3.2 Credit Record Aggregate <CreditRec>..............................................................................................15 6.3.3 Credit Status Aggregate <CreditStatus>............................................................................................16 6.3.4 Credit Media Item Aggregate <CreditMediaItem>............................................................................16 6.3.5 Credit Media Cash Information Aggregate <CreditMediaCashInfo>...............................................16 6.3.6 Credit Media Check Information Aggregate <CreditMediaChkInfo>...............................................17 6.3.7 Deposit Account Record Aggregate <DepAcctRec>..........................................................................17 6.3.8 Credit Card Account Record Aggregate <CCAcctRec>....................................................................18 6.3.9 Common Loan and LOC Account Aggregate <LoanInfoCommon>..................................................18 6.3.10 Loan Account Record Aggregate <LoanAcctRec>...........................................................................18 6.3.11 Line of Credit Account Record Aggregate <LOCAcctRec>.............................................................19 6.3.12 Mortgage Account Record Aggregate <MortAcctRec>...................................................................19 6.3.13 Bank Account Transaction Record Aggregate <BankAcctTrnRec>.................................................19 6.3.14 Deposit Account Transaction Record Aggregate <DepAcctTrnRec>..............................................21 6.3.15 Credit Card Account Transaction Record Aggregate <CCAcctTrnRec>........................................23 6.3.16 Selection Range Check Number Aggregate <ChkRange>................................................................23 6.3.17 Stop Check Record Aggregate <StopChkRec>.................................................................................23 6.3.18 Foreign Exchange Rate Information Aggregate <ForExRateInfo>.................................................24 6.3.19 Transfer Record Aggregate <XferRec>............................................................................................25 6.3.20 Check Order Record Aggregate <ChkOrdRec>...............................................................................27 6.3.21 Recurring Check Order Record Aggregate <RecChkOrdRec>........................................................29 6.3.22 Check Order Detail Aggregate <ChkOrdDetail>............................................................................30 6.3.23 Deposit Book Order Record Aggregate <DepBkOrdRec>...............................................................31 6.3.24 Transfer Profile Aggregate <XferProf>...........................................................................................32 6.3.25 Debit Record Aggregate <DebitRec>...............................................................................................33 6.3.26 Debit Authorization Record Aggregate <DebitAuthRec>................................................................33 6.3.27 Debit Information Aggregate <DebitInfo>.......................................................................................35 6.3.28 Credit Authorization Record Aggregate <CreditAuthRec>.............................................................36 6.3.29 Credit Information Aggregate <CreditInfo>....................................................................................37 6.3.30 Deposit Application Information Aggregate <DepAppInfo>...........................................................39 6.3.31 Deposit Application Record Aggregate <DepAppRec>...................................................................40
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification 6.3.32 Payment Enclosed Information Aggregate <PmtEnclInfo>.............................................................41 6.3.33 Deposit Account Statement Record <DepAcctStmtRec>..................................................................43 6.3.34 Check Issue Information Aggregate <ChkIssueInfo>.......................................................................44 6.3.35 Check Accept Record Aggregate <ChkAcceptRec>.........................................................................46 6.3.36 Check Accept Image Aggregate <ChkImg> ....................................................................................47 6.3.37 Check Detail Aggregate <ChkDetail>..............................................................................................48 6.3.38 Selection Range Check Number Aggregate <SelRangeChkNum>...................................................48 6.3.39 Base Environment Aggregate <BaseEnvr>......................................................................................49 6.3.40 Passbook Record Aggregate <PassbkRec>......................................................................................49 6.3.41 Passbook Item Record Aggregate <PassbkItemRec>.......................................................................51 6.3.42 Transaction Count Limit Aggregate <TrnCountLimit>...................................................................53 6.4 STATEMENT AND ACCOUNT INQUIRY..................................................................................................................54 6.4.1 Balance Inquiry...................................................................................................................................54 6.4.2 Balance Reversal.................................................................................................................................55 6.4.3 Account Inquiry...................................................................................................................................57 6.4.4 Account Reversal.................................................................................................................................59 6.4.5 Deposit Account Statement Inquiry.....................................................................................................60 6.4.6 Deposit Account Statement Reversal...................................................................................................63 6.4.7 Deposit Account Statement Advise......................................................................................................64 6.4.8 Credit Card Statement Inquiry............................................................................................................65 6.4.9 Credit Card Statement Inquiry Reversal ............................................................................................68 6.4.10 Deposit Account Transaction Inquiry...............................................................................................69 6.4.11 Deposit Account Transaction Advise.................................................................................................72 6.4.12 Deposit Account Transaction Reversal.............................................................................................73 6.4.13 Credit Card Account Transaction Inquiry........................................................................................75 6.4.14 Credit Card Account Transaction Reversal......................................................................................77 6.4.15 Bank Account Transaction Image Inquiry.........................................................................................78 6.4.16 Bank Account Transaction Image Reversal......................................................................................82 6.4.17 Interest Rate Inquiry..........................................................................................................................83 6.4.18 Interest Rate Inquiry Reversal...........................................................................................................85 6.4.19 Bank Account Taxation Inquiry.........................................................................................................86 6.4.20 Foreign Exchange Rate Inquiry........................................................................................................88 6.4.21 Foreign Exchange Rate Reversal......................................................................................................92 6.5 FOREIGN EXCHANGE DEAL ELEMENTS..............................................................................................................93 6.5.1 Foreign Exchange Deal Record Aggregate <ForExDealRec>.........................................................93 6.5.2 Foreign Exchange Deal Add..............................................................................................................95 6.5.3 Foreign Exchange Deal Modify..........................................................................................................96 6.5.4 Foreign Exchange Deal Inquiry..........................................................................................................97 6.5.5 Foreign Exchange Deal Cancel.........................................................................................................99 6.5.6 Foreign Exchange Deal Audit...........................................................................................................100 6.5.7 Foreign Exchange Deal Sync............................................................................................................102 6.5.8 Foreign Exchange Deal Reversal....................................................................................................104 6.5.9 Foreign Exchange Deal Status Modify.............................................................................................106 6.5.10 Foreign Exchange Deal Status Inquiry...........................................................................................107 6.5.11 Foreign Exchange Deal Advise.......................................................................................................109 6.6 STOP CHECK................................................................................................................................................110 6.6.1 Stop Check Add..................................................................................................................................110 6.6.2 Stop Check Cancel.............................................................................................................................112 6.6.3 Stop Check Inquiry............................................................................................................................113 6.6.4 Stop Check Audit...............................................................................................................................116 6.6.5 Stop Check Sync................................................................................................................................118 6.6.6 Stop Check Advise.............................................................................................................................119 6.6.7 Stop Check Reversal..........................................................................................................................120 6.7 FUNDS TRANSFER..........................................................................................................................................122 6.7.1 Funds Transfer Add...........................................................................................................................122 6.7.2 Funds Transfer Modify......................................................................................................................123
vi
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification 6.7.3 Funds Transfer Status Modify...........................................................................................................125 6.7.4 Funds Transfer Cancel......................................................................................................................126 6.7.5 Funds Transfer Inquiry......................................................................................................................128 6.7.6 Funds Transfer Audit.........................................................................................................................131 6.7.7 Funds Transfer Sync..........................................................................................................................133 6.7.8 Funds Transfer Advise.......................................................................................................................135 6.7.9 Funds Transfer Reversal...................................................................................................................136 6.8 RECURRING TRANSFER MODEL.......................................................................................................................138 6.8.1 Recurring Transfer Model Add.........................................................................................................138 6.8.2 Recurring Transfer Model Modify.....................................................................................................139 6.8.3 Recurring Transfer Model Cancel.....................................................................................................141 6.8.4 Recurring Transfer Model Inquiry....................................................................................................142 6.8.5 Recurring Transfer Model Audit.......................................................................................................144 6.8.6 Recurring Transfer Model Sync........................................................................................................146 6.8.7 Recurring Transfer Reversal.............................................................................................................148 6.9 CUSTOMER COMMUNICATIONS.........................................................................................................................150 6.9.1 Check Order......................................................................................................................................150 6.9.2 Recurring Check Order.....................................................................................................................162 6.9.3 Deposit Book Order Add...................................................................................................................173 6.9.4 Deposit Book Order Add...................................................................................................................175 6.9.5 Deposit Book Order Reversal............................................................................................................176 6.10 DEBIT AND CREDIT......................................................................................................................................177 6.10.1 Debit Messages................................................................................................................................177 6.10.2 Credit Messages..............................................................................................................................204 6.11 DEPOSIT APPLICATION.................................................................................................................................232 6.11.1 Deposit Application Add..................................................................................................................232 6.11.2 Deposit Application Modification...................................................................................................233 6.11.3 Deposit Application Cancel.............................................................................................................235 6.11.4 Deposit Application Inquiry............................................................................................................236 6.11.5 Deposit Application Audit...............................................................................................................237 6.11.7 Deposit Application Sync................................................................................................................239 6.12 BANK ACCOUNT STATEMENT IMAGE INQUIRY.................................................................................................241 6.12.2 Bank Account Statement Image Reversal........................................................................................244 6.13 PAYMENT ENCLOSED...................................................................................................................................245 6.13.1 Payment Enclosed Add ...................................................................................................................245 6.13.2 Payment Enclosed Modify...............................................................................................................247 6.13.3 Payment Enclosed Inquiry...............................................................................................................248 6.13.4 Payment Enclosed Cancel...............................................................................................................250 6.13.5 Payment Enclosed Audit..................................................................................................................251 6.13.6 Payment Enclosed Status Modify....................................................................................................253 6.13.7 Payment Enclosed Advise................................................................................................................255 6.13.8 Payment Enclosed Reversal............................................................................................................256 6.14 CHECK ISSUE .............................................................................................................................................258 6.14.1 Check Issue Add..............................................................................................................................258 6.14.2 Check Issue Modification................................................................................................................260 6.14.3 Check Issue Status Modification.....................................................................................................261 6.14.4 Check Issue Delete..........................................................................................................................263 6.14.5 Check Issue Inquiry.........................................................................................................................264 6.14.6 Check Issue Audit............................................................................................................................267 6.14.7 Check Issue Sync.............................................................................................................................268 6.14.8 Check Issue Advise..........................................................................................................................270 6.15 BANK SERVICE CHECKSUM ..........................................................................................................................271 6.15.1 Bank Service Checksum Add...........................................................................................................271 6.15.2 Bank Service Checksum Modify......................................................................................................273 6.15.3 Bank Service Checksum Status Modify............................................................................................274 6.15.4 Bank Service Checksum Delete.......................................................................................................275
Version 1.7
April 2005
vii
Interactive Financial Exchange Business Message Specification 6.15.5 Bank Service Checksum Inquiry......................................................................................................277 6.15.6 Bank Service Checksum Audit.........................................................................................................278 6.15.7 Bank Service Checksum Synchronization........................................................................................280 6.16 CHECK ACCEPT ..........................................................................................................................................282 6.16.1 Check Accept Add............................................................................................................................282 6.16.2 Check Accept Modify.......................................................................................................................283 6.16.3 Check Accept Inquiry......................................................................................................................284 6.16.4 Check Accept Cancel.......................................................................................................................286 6.16.5 Check Accept Audit..........................................................................................................................287 6.16.6 Check Accept Sync...........................................................................................................................289 6.16.7 Check Accept Reversal....................................................................................................................291 6.16.8 Check Accept Status Modify............................................................................................................294 6.17 PASSBOOK..................................................................................................................................................295 6.17.1 Passbook Add..................................................................................................................................296 6.17.2 Passbook Modify.............................................................................................................................297 6.17.3 Passbook Inquiry.............................................................................................................................298 6.17.4 Passbook Delete..............................................................................................................................301 6.17.5 Passbook Audit................................................................................................................................302 6.17.6 Passbook Sync.................................................................................................................................304 6.17.7 Passbook Reversal...........................................................................................................................306 6.17.8 Passbook Status Modify...................................................................................................................309 6.17.9 Passbook Status Inquiry..................................................................................................................310 6.17.10 Passbook Item Add........................................................................................................................311 6.17.11 Passbook Item Modify...................................................................................................................312 6.17.12 Passbook Item Inquiry...................................................................................................................314 6.17.13 Passbook Item Delete....................................................................................................................316 6.17.14 Passbook Item Audit......................................................................................................................317 6.17.15 Passbook Item Sync.......................................................................................................................320 6.17.16 Passbook Item Reversal.................................................................................................................321 6.17.17 Passbook Item Status Modify.........................................................................................................324 6.17.18 Passbook Item Status Inquiry........................................................................................................325 6.18 BANKING SERVICE PROFILE <BANKSVCPROFINFO>........................................................................................327 6.18.1 Stop Check Profile Aggregate <StopChkProf>..............................................................................328 6.18.2 Interbank Transfer Profile Aggregate <IntXferProf>....................................................................329 6.18.3 ACH Profile Aggregate <USA.ACHProf>.....................................................................................329
7 THE PAY SERVICE <PAYSVC>......................................................................................................1

7.1 DESCRIPTION....................................................................................................................................................1 7.1.1 Payees....................................................................................................................................................1 7.1.2 Payments................................................................................................................................................3 7.2 PAY SERVICE MESSAGE SUMMARY......................................................................................................................7 7.3 PAY SERVICE COMMON AGGREGATES................................................................................................................12 7.3.1 Standard Payee Record <StdPayeeRec>............................................................................................12 7.3.2 Customer Payee Record Aggregate <CustPayeeRec>.......................................................................12 7.3.3 Payment Record Aggregate <PmtRec>..............................................................................................15 7.3.4 Payment Remittance Information <PmtRemitInfo>...........................................................................17 7.3.5 Payment Authorization Record Aggregate <PmtAuthRec>...............................................................20 7.3.6 Remittance Record Aggregate <RemitRec>.......................................................................................21 7.3.7 Invoice Information Aggregate <InvoiceInfo>...................................................................................27 7.3.8 Invoice Adjustment Aggregate <InvoiceAdj>.....................................................................................28 7.3.9 Invoice Line Item Aggregate <InvoiceLineItem>...............................................................................28 7.3.10 Checksum Record Aggregate <ChksumRec>...................................................................................29 7.3.11 Comprehensible Remittance Statement Record Aggregate <CompRemitStmtRec>........................30 7.3.12 Payment Status Record Aggregate <PmtStatusRec>.......................................................................32 7.3.13 Payment Acknowledgement Record Aggregate <PmtAckRec>........................................................32 7.3.14 pain.001.001.01 <pain.001.001.01>................................................................................................33
viii
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification 7.3.15 pain.002.001.01 <pain.002.001.01>................................................................................................34 7.3.16 pain.003.001.01 <pain.003.001.01>................................................................................................34 7.3.17 pain.004.001.01 <pain.004.001.01>................................................................................................34 7.3.18 PmtBatch Record Aggregate <PmtBatchRec>.................................................................................35 7.4 STANDARD PAYEE...........................................................................................................................................35 7.4.1 Standard Payee Inquiry.......................................................................................................................35 7.4.2 Standard Payee Reversal.....................................................................................................................38 7.5 CUSTOMER PAYEE...........................................................................................................................................39 7.5.1 Customer Payee Add...........................................................................................................................39 7.5.2 Customer Payee Modify......................................................................................................................40 7.5.3 Customer Payee Type Modify..............................................................................................................42 7.5.4 Customer Payee Delete.......................................................................................................................43 7.5.5 Customer Payee Inquiry......................................................................................................................45 7.5.6 Customer Payee Audit.........................................................................................................................47 7.5.7 Customer Payee Synchronization........................................................................................................49 7.6 SINGLE PAYMENT............................................................................................................................................50 7.6.1 Payment Add........................................................................................................................................50 7.6.2 Payment Modify...................................................................................................................................52 7.6.3 Payment Status Modify........................................................................................................................54 7.6.4 Payment Status Advise.........................................................................................................................55 7.6.5 Payment Cancel...................................................................................................................................56 7.6.6 Payment Inquiry..................................................................................................................................58 7.6.7 Payment Reversal................................................................................................................................63 7.6.8 Payment Status Inquiry........................................................................................................................64 7.6.9 Payment Audit.....................................................................................................................................68 7.6.10 Payment Synchronization..................................................................................................................70 7.7 PAYMENT AUTHORIZATION...............................................................................................................................72 7.7.1 Payment Authorization Add.................................................................................................................72 7.7.2 Payment Authorization Modify............................................................................................................73 7.7.3 Payment Authorization Cancel............................................................................................................74 7.7.4 Payment Authorization Inquiry...........................................................................................................76 7.7.5 Payment Authorization Audit..............................................................................................................77 7.7.6 Payment Authorization Synchronization.............................................................................................79 7.7.7 Payment Authorization Reversal.........................................................................................................81 7.8 REMITTANCE...................................................................................................................................................82 7.8.1 Remittance Add....................................................................................................................................82 7.8.2 Remittance Modify...............................................................................................................................84 7.8.3 Remittance Status Modify....................................................................................................................85 7.8.4 Remittance Delete................................................................................................................................87 7.8.5 Remittance Inquiry..............................................................................................................................88 7.8.6 Remittance Audit.................................................................................................................................89 7.8.7 Remittance Synchronization................................................................................................................91 7.8.8 Remittance Reversal............................................................................................................................93 7.9 RECURRING PAYMENT MODEL..........................................................................................................................95 7.9.1 Recurring Payment Model Add...........................................................................................................95 7.9.2 Recurring Payment Instance Add........................................................................................................96 7.9.3 Recurring Payment Model Modify......................................................................................................98 7.9.4 Recurring Payment Model Cancel......................................................................................................99 7.9.5 Recurring Payment Model Inquiry....................................................................................................101 7.9.6 Recurring Payment Model Audit.......................................................................................................104 7.9.7 Recurring Payment Model Sync........................................................................................................105 7.9.8 Recurring Payment Model Reversal..................................................................................................107 7.10 PAYMENT ACKNOWLEDGEMENT.....................................................................................................................109 7.10.1 Payment Acknowledgment Inquiry..................................................................................................110 7.10.2 Payment Acknowledgment Reversal................................................................................................111 7.10.3 Payment Acknowledgment Advise...................................................................................................113
Version 1.7
April 2005
ix
Interactive Financial Exchange Business Message Specification 7.11 BATCH CHECKSUM......................................................................................................................................114 7.11.1 Checksum Add.................................................................................................................................114 7.11.2 Checksum Modify............................................................................................................................115 7.11.3 Checksum Status Modify..................................................................................................................117 7.11.4 Checksum Delete.............................................................................................................................118 7.11.5 Checksum Inquiry............................................................................................................................119 7.11.6 Checksum Audit...............................................................................................................................121 7.11.7 Checksum Synchronization..............................................................................................................122 7.11.8 Checksum Advise.............................................................................................................................124 7.12 COMPREHENSIBLE REMITTANCE.....................................................................................................................125 7.12.1 Comprehensible Remittance Statement Add....................................................................................126 7.12.2 Comprehensible Remittance Statement Inquiry..............................................................................128 7.12.3 Comprehensible Remittance Statement Audit.................................................................................130 7.12.4 Comprehensible Remittance Statement Synchronization................................................................131 7.13 PAY SERVICE PROFILE <PAYSVCPROFINFO>..................................................................................................133 7.13.1 Recurring Payment Profile Aggregate <RecPmtProf>..................................................................135 7.14 PAYMENT BATCH .......................................................................................................................................135 7.14.1 PmtBatch Add..................................................................................................................................135 7.14.2 PmtBatch Cancel.............................................................................................................................137 7.14.3 PmtBatch Status Inquiry..................................................................................................................138 7.14.4 PmtBatch Status Advise...................................................................................................................141
8 THE BILL PRESENTMENT SERVICE <PRESSVC>..............................................................................1

8.1 DESCRIPTION....................................................................................................................................................1 8.1.1 Biller Inquiry.........................................................................................................................................1 8.1.2 Activate Bill Delivery............................................................................................................................2 8.1.3 Account Inquiry.....................................................................................................................................2 8.1.4 Bill Presentment....................................................................................................................................2 8.1.5 Bill Payment..........................................................................................................................................5 8.2 BILL PRESENTMENT SERVICE MESSAGE SUMMARY................................................................................................6 8.3 PRESENTMENT SERVICE COMMON AGGREGATES....................................................................................................6 8.3.1 Biller Record Aggregate <BillerRec>..................................................................................................6 8.3.2 Biller Account Identification Information Aggregate <BillerAcctIdInfo>...........................................9 8.3.3 Bill Record <BillRec>.........................................................................................................................10 8.4 PRESENTMENT SERVICE MESSAGE DETAIL..........................................................................................................14 8.4.1 Biller Inquiry.......................................................................................................................................14 8.4.2 Biller Inquiry Reversal........................................................................................................................17 8.4.3 Bill Inquiry...........................................................................................................................................18 8.4.4 Bill Reversal........................................................................................................................................21 8.4.5 Bill Status Modify................................................................................................................................23 8.5 BILL PRESENTMENT SERVICE PROFILE <PRESSVCPROFINFO>...............................................................................25
9 THE VALUABLE MEDIA SERVICE <MEDIASVC>..............................................................................1

9.1 DESCRIPTION....................................................................................................................................................1 9.2 VALUABLE MEDIA SERVICE MESSAGE SUMMARY..................................................................................................2 9.3 VALUABLE MEDIA SERVICE COMMON AGGREGATES..............................................................................................2 9.3.1 Media Item <MediaItem>.....................................................................................................................2 9.3.2 Media Account Record Aggregate <MediaAcctAdjRec>.....................................................................4 9.4 MEDIA ACCOUNT ADJUST..................................................................................................................................6 9.4.1 Media Account Adjust Add....................................................................................................................6 9.4.2 Media Account Adjust Inquiry...............................................................................................................7 9.4.3 Media Account Adjust Audit..................................................................................................................9 9.4.4 Media Account Adjust Synchronization...............................................................................................11 9.4.5 Media Account Adjust Reversal...........................................................................................................12 9.5 MEDIA ACCOUNT INVENTORY...........................................................................................................................14 9.5.1 Media Account Inventory Inquiry........................................................................................................14
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification 9.5.2 Media Account Inventory Reversal.....................................................................................................15 9.6 VALUABLE MEDIA SERVICE PROFILE <MEDIASVCPROFINFO>..............................................................................16
10 ROOT SERVICE <ROOTSVC>.....................................................................................................1

10.1 DESCRIPTION..................................................................................................................................................1 10.2 ROOT SERVICE MESSAGE SUMMARY..................................................................................................................2 10.3 ROOT SERVICE COMMON AGGREGATES..............................................................................................................3 10.3.1 Terminal Object Record Aggregate <TerminalObjRec>...................................................................3 10.3.2 Terminal Service Provider Object Record Aggregate <TerminalSPObjRec>...................................4 10.3.3 Device Record Aggregate <DevRec>.................................................................................................5 10.4 TERMINAL OBJECT........................................................................................................................................23 10.4.1 Terminal Object Add Message..........................................................................................................23 10.4.2 Terminal Object Modify....................................................................................................................24 10.4.3 Terminal Object Inquiry....................................................................................................................25 10.4.4 Terminal Object Delete.....................................................................................................................25 10.4.5 Terminal Object Audit.......................................................................................................................26 10.4.6 Terminal Object Status Modify..........................................................................................................28 10.4.7 Terminal Object Advise.....................................................................................................................29 10.5 TERMINAL SERVICE PROVIDER OBJECT ............................................................................................................30 10.5.1 Terminal Service Provider Object Add Message..............................................................................30 10.5.2 Terminal Service Provider Object Modify........................................................................................31 10.5.3 Terminal Service Provider Object Inquiry........................................................................................32 10.5.4 Terminal Service Provider Object Delete.........................................................................................34 10.5.5 Terminal Service Provider Object Audit...........................................................................................34 10.5.6 Terminal Service Provider Object Advise.........................................................................................36 10.6 DEVICE MESSAGES........................................................................................................................................37 10.6.1 Device Inquiry...................................................................................................................................37 10.6.2 Device Advise....................................................................................................................................39 10.7 ROOT SERVICE PROFILE INFORMATION <ROOTSVCPROFINFO>............................................................................40
A RESPONSE STATUS CODES...........................................................................................................1

A.1 ALL MESSAGES..............................................................................................................................................12 A.2 SECURITY MESSAGES......................................................................................................................................14 A.2.1 Signon (Signon)...................................................................................................................................14 A.2.2 Signoff (Signoff)..................................................................................................................................15 A.3 BASE SERVICE...............................................................................................................................................15 A.3.1 Service Profile Inquiry (SvcProfInq)..................................................................................................15 A.3.2 Holiday Inquiry (HolInq)....................................................................................................................15 A.3.3 Customer Password Modify (CustPswdMod).....................................................................................15 A.3.4 Customer Add (CustAdd)....................................................................................................................15 A.3.5 Customer Modify (CustMod)..............................................................................................................16 A.3.6 Customer Status Modify (CustStatusMod)..........................................................................................16 A.3.7 Customer Inquiry (CustInq)................................................................................................................16 A.3.8 Customer Synchronization (CustSync)................................................................................................16 A.3.9 Customer/Service Link Add (CustSvcAdd)..........................................................................................16 A.3.10 Customer/Service Link Modify (CustSvcMod)..................................................................................17 A.3.11 Customer/Service Link Status Modify (CustSvcStatusMod).............................................................17 A.3.12 Customer/Service Link Delete (CustSvcDel)....................................................................................17 A.3.13 Customer/Service Link Audit (CustSvcAud).....................................................................................18 A.3.14 Customer/Service Link Synchronization (CustSvcSync)...................................................................18 A.3.15 Service/Account Link Add (SvcAcctAdd)..........................................................................................18 A.3.16 Service/Account Link Modify (SvcAcctMod).....................................................................................18 A.3.17 Service/Account Link Status Modify (SvcAcctStatusMod)................................................................19 A.3.18 Service/Account Link Identifier Modify (SvcAcctIdMod).................................................................19 A.3.19 Service/Account Link Delete (SvcAcctDel).......................................................................................19 A.3.20 Service/Account Link Inquiry (SvcAcctInq)......................................................................................19
Version 1.7
April 2005
xi
Interactive Financial Exchange Business Message Specification A.3.21 Service/Account Link Audit (SvcAcctAud)........................................................................................20 A.3.22 Service/Account Link Synchronization (SvcAcctSync)......................................................................20 A.3.23 Service/Account Link Reversal (SvcAcctRev)...................................................................................20 A.3.24 Disclosure Inquiry (DiscInq)............................................................................................................20 A.3.25 Customer/Disclosure Link Status Modify (CustDiscStatusMod)......................................................20 A.3.26 Customer/Disclosure Link Inquiry (CustDiscInq)............................................................................21 A.3.27 Customer Identifier Inquiry (CustIdInq)...........................................................................................21 A.3.28 Customer Status Modify (CustStatusMod)........................................................................................21 A.3.29 Customer Authorization Modify (CustAuthMod)..............................................................................21 A.3.30 Security Object Add (SecObjAdd).....................................................................................................21 A.3.31 Security Object Modify (SecObjMod)...............................................................................................22 A.3.32 Security Object Inquiry (SecObjInq).................................................................................................22 A.3.33 Security Object Delete (SecObjDel).................................................................................................22 A.3.34 Security Object Advise (SecObjAdvise)............................................................................................22 A.3.35 Security Object Sync (SecObjSync)...................................................................................................22 A.3.36 Party Account Relationship Add (PartyAcctRelAdd)........................................................................23 A.3.37 Party Account Relationship Modify (PartyAcctRelMod)..................................................................23 A.3.38 Party Account Relationship Delete (PartyAcctRelDel)....................................................................23 A.3.39 Party Account Relationship Inquiry (PartyAcctRelInq)...................................................................23 A.3.40 Card Preferences Add (CardPrefAdd)..............................................................................................23 A.3.41 Card Preference Modify (CardPrefMod).........................................................................................24 A.3.42 Card Preference Inquiry (CardPrefInq)...........................................................................................25 A.3.43 Card Preference Delete (CardPrefDel)............................................................................................25 A.3.44 Card Preference Audit (CardPrefAud).............................................................................................25 A.3.45 Card Preference Sync (CardPrefSync).............................................................................................26 A.3.46 Card Preference Reversal (CardPrefRev)........................................................................................26 A.3.47 Card Preference Status Modify (CardPrefStatusMod).....................................................................26 A.3.48 Posting Session Add (PostingSessionAdd)........................................................................................26 A.3.49 Posting Session Modify (PostingSessionMod)..................................................................................27 A.3.50 Posting Session Inquiry (PostingSessionInq)...................................................................................27 A.3.51 Posting Session Status Modify (PostingSessionStatusMod).............................................................27 A.3.52 Session Totals Inquiry (SessionTotalsInq)........................................................................................27 A.4 BANKING SERVICE..........................................................................................................................................27 A.4.1 Balance Inquiry (BalInq)....................................................................................................................27 A.4.2 Balance Reversal (BalRev).................................................................................................................28 A.4.3 Account Inquiry (AcctInq)...................................................................................................................28 A.4.4 Account Reversal (AcctRev)................................................................................................................29 A.4.5 Deposit Account Statement Inquiry (DepAcctStmtInq).......................................................................29 A.4.6 Credit Card Statement Inquiry (CCAcctStmtInq)...............................................................................30 A.4.7 Credit Card Statement Reversal (CCAcctStmtRev)............................................................................30 A.4.8 Deposit Account Transaction Inquiry (DepAcctTrnInq)....................................................................31 A.4.9 Deposit Account Transaction Reversal (DepAcctTrnRev)..................................................................31 A.4.10 Credit Card Account Transaction Inquiry (CCAcctTrnInq).............................................................32 A.4.11 Credit Card Account Transaction Reversal (CCAcctTrnRev)..........................................................32 A.4.12 Interest Rate Inquiry (IntRateInq).....................................................................................................33 A.4.13 Interest Rate Rev (IntRateRev)..........................................................................................................33 A.4.14 Bank Account Taxation Inquiry (BankAcctTaxInq)..........................................................................33 A.4.15 Foreign Exchange Rate Inquiry (ForExRateInq).............................................................................34 A.4.16 Foreign Exchange Rate Reversal (ForExRateRev)..........................................................................34 A.4.17 ForExDealAdd..................................................................................................................................34 A.4.18 ForExDealMod.................................................................................................................................35 A.4.19 ForExDealInq...................................................................................................................................35 A.4.20 ForExDealCan..................................................................................................................................35 A.4.21 ForExDealAud..................................................................................................................................35 A.4.22 ForExDealSync.................................................................................................................................35 A.4.23 ForExDealRev...................................................................................................................................35
xii
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification A.4.24 A.4.25 A.4.26 A.4.27 A.4.28 A.4.29 A.4.30 A.4.31 A.4.32 A.4.33 A.4.34 A.4.35 A.4.36 A.4.37 A.4.38 A.4.39 A.4.40 A.4.41 A.4.42 A.4.43 A.4.44 A.4.45 A.4.46 A.4.47 A.4.48 A.4.49 A.4.50 A.4.51 A.4.52 A.4.53 A.4.54 A.4.55 A.4.56 A.4.57 A.4.58 A.4.59 A.4.60 A.4.61 A.4.62 A.4.63 A.4.64 A.4.65 A.4.66 A.4.67 A.4.68 A.4.69 A.4.70 A.4.71 A.4.72 A.4.73 A.4.74 A.4.75 A.4.76 A.4.77 A.4.78 A.4.79 ForExDealStatusMod........................................................................................................................35 ForExDealStatusInq..........................................................................................................................35 ForExDealAdvise..............................................................................................................................36 Stop Check Add (StopChkAdd).........................................................................................................36 Stop Check Cancel (StopChkCan)....................................................................................................37 Stop Check Inquiry (StopChkInq).....................................................................................................37 Stop Check Audit (StopChkAud).......................................................................................................38 Stop Check Synchronization (StopChkSync).....................................................................................39 Stop Check Reversal (StopChkRev)..................................................................................................39 Funds Transfer Add (XferAdd).........................................................................................................39 Funds Transfer Modify (XferMod)....................................................................................................41 Funds Transfer Status Modify (XferStatusMod)...............................................................................42 Funds Transfer Cancel (XferCan)....................................................................................................42 Funds Transfer Inquiry (XferInq).....................................................................................................42 Funds Transfer Audit (XferAud).......................................................................................................43 Funds Transfer Synchronization (XferSync).....................................................................................44 Funds Transfer Reversal (XferRev)..................................................................................................44 Recurring Funds Transfer Model Add (RecXferAdd).......................................................................44 Recurring Funds Transfer Instance Add (RecXferInstAdd)..............................................................45 Recurring Funds Transfer Model Modify (RecXferMod).................................................................47 Recurring Funds Transfer Model Cancel (RecXferCan)..................................................................48 Recurring Funds Transfer Model Inquiry (RecXferInq)...................................................................48 Recurring Funds Transfer Model Audit (RecXferAud).....................................................................49 Recurring Funds Transfer Synchronization (RecXferSync)..............................................................49 Records Funds Transfer Model Reversal (RecXferRev)...................................................................50 Bank Account Transaction Image Inquiry (BankAcctTrnImgInq)....................................................50 Bank Account Transaction Image Inquiry Reversal (BankAcctTrnImgRev)....................................51 Check Order (ChkOrdAdd)...............................................................................................................51 Check Order Reversal (ChkOrdRev)................................................................................................52 Recurring Check Order Add (RecChkOrdAdd)................................................................................52 Recurring Check Order Modify (RecChkOrdMod)..........................................................................52 Deposit Book Order (DepBkOrdAdd)...............................................................................................52 Deposit Book Order Reversal (DepBkOrdRev)................................................................................53 Debit Authorization Add (DebitAuthAdd).........................................................................................53 Debit Authorization Modify (DebitAuthMod)...................................................................................54 Debit Authorization Cancel (DebitAuthCan)....................................................................................54 Debit Authorization Inquiry (DebitAuthInq).....................................................................................55 Debit Authorization Audit (DebitAuthAud).......................................................................................55 Debit Authorization Sync (DebitAuthSync).......................................................................................56 Debit Authorization Status Modify (DebitAuthStatusMod)..............................................................56 Debit Authorization Reversal (DebitAuthRev)..................................................................................56 Debit Add (DebitAdd).......................................................................................................................57 Debit Modify (DebitMod)..................................................................................................................58 Debit Cancel (DebitCan)..................................................................................................................58 Debit Inquiry (DebitInq)...................................................................................................................58 Debit Audit (DebitAud).....................................................................................................................59 Debit Sync (DebitSync).....................................................................................................................59 Debit Status Modify (DebitStatusMod).............................................................................................60 Debit Reversal (DebitRev)................................................................................................................60 Credit Authorization Add (CreditAuthAdd)......................................................................................60 Credit Authorization Modify (CreditAuthMod)................................................................................61 Credit Authorization Cancel (CreditAuthCan).................................................................................62 Credit Authorization Inquiry (CreditAuthInq)..................................................................................62 Credit Authorization Audit (CreditAuthAud)....................................................................................63 Credit Authorization Sync (CreditAuthSync)....................................................................................63 Credit Authorization Status Modify (CreditAuthStatusMod)............................................................64
Version 1.7
April 2005
xiii
Interactive Financial Exchange Business Message Specification A.4.80 Credit Authorization Reversal (CreditAuthRev)...............................................................................64 A.4.81 Credit Add (CreditAdd).....................................................................................................................64 A.4.82 Credit Modify (CreditMod)...............................................................................................................65 A.4.83 Credit Cancel (CreditCan)................................................................................................................66 A.4.84 Credit Inquiry (CreditInq)................................................................................................................66 A.4.85 Credit Audit (CreditAud)..................................................................................................................67 A.4.86 Credit Sync (CreditSync)..................................................................................................................67 A.4.87 Credit Status Modify (CreditStatusMod)..........................................................................................67 A.4.88 Credit Reversal (CreditRev)..............................................................................................................68 A.4.89 Bank Account Statement Image Inquiry (BankAcctStmtImgInq)......................................................68 A.4.90 Bank Account Statement Image Reversal (BankAcctStmtImgRev)...................................................69 A.4.91 Payment Enclosed Reversal (PmtEnclRev).......................................................................................69 A.4.92 Check Issue Add (ChkIssueAdd).......................................................................................................69 A.4.93 Check Issue Modify (ChkIssueMod).................................................................................................69 A.4.94 Check Issue Status Modify (ChkIssueStatusMod).............................................................................70 A.4.95 Check Issue Delete (ChkIssueDel)....................................................................................................70 A.4.96 Check Issue Inquiry (ChkIssueInq)...................................................................................................70 A.4.97 Check Issue Status Inquiry (ChkIssueStatusInq)..............................................................................71 A.4.98 Check Issue Audit (ChkIssueAud).....................................................................................................71 A.4.99 Check Issue Synchronization (ChkIssueSync)...................................................................................72 A.4.100 Bank Service Checksum Add (BankSvcChkSumAdd)......................................................................72 A.4.101 Bank Service Checksum Modify (BankSvcChkSumMod)................................................................72 A.4.102 Bank Service Checksum Status Modify (BankSvcChkSumStatusMod)...........................................73 A.4.103 Bank Service Checksum Delete (BankSvcChkSumDel)..................................................................73 A.4.104 Bank Service Checksum Inquiry (BankSvcChkSumInq).................................................................73 A.4.105 Bank Service Checksum Audit (BankSvcChkSumAud)...................................................................74 A.4.106 Bank Service Checksum Synchronization (BankSvcChkSumSync).................................................74 A.4.107 Check Accept Add (ChkAcceptAdd)................................................................................................74 A.4.108 Check Accept Modify (ChkAcceptMod)..........................................................................................75 A.4.109 Check Accept Inquiry (ChkAcceptInq)............................................................................................75 A.4.110 Check Accept Cancel (ChkAcceptCan)...........................................................................................76 A.4.111 Check Accept Audit (ChkAcceptAud)..............................................................................................76 A.4.112 Check Accept Syncronization (ChkAcceptSync).............................................................................77 A.4.113 Check Accept Reversal (ChkAcceptRev).........................................................................................77 A.4.114 Check Accept Status Modify (ChkAcceptStatusMod)......................................................................77 A.4.115 Media Account Adjustment Add (MediaAcctAdjAdd).....................................................................78 A.4.116 Media Account Adjustment Modify (MediaAcctAdjMod)...............................................................78 A.4.117 Media Account Adjust Inquiry (MediaAcctAdjInq)........................................................................78 A.4.118 Media Account Inventory Inquiry (MediaAcctInventoryInq)..........................................................78 A.4.119 Passbook Add (PassbkAdd)...........................................................................................................78 A.4.120 Passbook Mod (PassbkMod)...........................................................................................................79 A.4.121 Passbook Inquiry (PassbkInq)........................................................................................................79 A.4.122 Passbook Delete (PassbkDel).........................................................................................................80 A.4.123 Passbook Audit (PassbkAud)..........................................................................................................80 A.4.124 Passbook Sync (PassbkSync)..........................................................................................................80 A.4.125 Passbook Reversal (PassbkRev).....................................................................................................81 A.4.126 Passbook Status Modify (PassbkStatusMod)..................................................................................81 A.4.127 Passbook Status Inquiry (PassbkStatusInq)....................................................................................81 A.4.128 Passbook Item Add (PassbkItemAdd).............................................................................................81 A.4.129 Passbook Item Modify (PassbkItemMod).......................................................................................82 A.4.130 Passbook Item Inquiry (PassbkItemInq).........................................................................................82 A.4.131 Passbook Item Delete (PassbkItemDel)..........................................................................................83 A.4.132 Passbook Item Audit (PassbkItemAud)...........................................................................................83 A.4.133 Passbook Item Sync (PassbkItemSync)...........................................................................................83 A.4.134 Passbook Item Reversal (PassbkItemRev)......................................................................................83 A.4.135 Passbook Item Status Modify (PassbkItemStatusMod)...................................................................84
xiv
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification A.4.136 Passbook Item Status Inquiry (PassbkItemStatusInq)....................................................................84 A.5 PAY SERVICE.................................................................................................................................................85 A.5.1 Standard Payee Inquiry (StdPayeeInq)...............................................................................................85 A.5.2 Standard Payee Reversal (StdPayeeRev)............................................................................................85 A.5.3 Customer Payee Add (CustPayeeAdd)................................................................................................85 A.5.4 Customer Payee Modify (CustPayeeMod)..........................................................................................85 A.5.5 Customer Payee Delete (CustPayeeDel)............................................................................................86 A.5.6 Customer Payee Inquiry (CustPayeeInq)...........................................................................................86 A.5.7 Customer Payee Audit (CustPayeeAud).............................................................................................86 A.5.8 Customer Payee Synchronization (CustPayeeSync)...........................................................................87 A.5.9 Payment Add (PmtAdd).......................................................................................................................87 A.5.10 Payment Modify (PmtMod)...............................................................................................................88 A.5.11 Payment Status Modify (PmtStatusMod)..........................................................................................89 A.5.12 Payment Cancel (PmtCan)................................................................................................................89 A.5.13 Payment Inquiry (PmtInq)................................................................................................................89 A.5.14 Payment Enclosed Add (PmtEnclAdd)..............................................................................................90 A.5.15 Payment Enclosed Modify (PmtEnclMod) .......................................................................................91 A.5.16 Payment Enclosed Cancel (PmtEnclCan) ........................................................................................91 A.5.17 Payment Enclosed Inquiry (PmtEnclInq) ........................................................................................91 A.5.18 Payment Enclosed Audit (PmtEnclAud) ..........................................................................................92 A.5.19 Payment Enclosed Status Modify (PmtEnclStatusMod) ..................................................................92 A.5.20 Payment Status Inquiry (PmtStatusInq)............................................................................................92 A.5.21 Payment Audit (PmtAud)..................................................................................................................93 A.5.22 Payment Synchronization (PmtSync)................................................................................................93 A.5.23 Payment Reversal (PmtRev)..............................................................................................................94 A.5.24 Payment Authorization Add (PmtAuthAdd)......................................................................................94 A.5.25 Payment Authorization Modify (PmtAuthMod)................................................................................94 A.5.26 Payment Authorization Cancel (PmtAuthCan).................................................................................95 A.5.27 Payment Authorization Inquiry (PmtAuthInq)..................................................................................95 A.5.28 Payment Authorization Audit (PmtAuthAud)....................................................................................95 A.5.29 Payment Authorization Synchronization (PmtAuthSync).................................................................96 A.5.30 Payment Authorization Reversal (PmtAuthRev)...............................................................................96 A.5.31 Remittance Add (RemitAdd)..............................................................................................................96 A.5.32 Remittance Modify (RemitMod)........................................................................................................96 A.5.33 Remittance Status Modify (RemitStatusMod)...................................................................................97 A.5.34 Remittance Delete (RemitDel)..........................................................................................................97 A.5.35 Remittance Inquiry (RemitInq)..........................................................................................................97 A.5.36 Remittance Audit (RemitAud)............................................................................................................98 A.5.37 Remittance Synchronization (RemitSync).........................................................................................98 A.5.38 Remit Reversal (RemitRev)...............................................................................................................98 A.5.39 Recurring Payment Model Add (RecPmtAdd)..................................................................................98 A.5.40 Recurring Payment Instance Add (RecPmtInstAdd).........................................................................99 A.5.41 Recurring Payment Model Modify (RecPmtMod)..........................................................................100 A.5.42 Recurring Payment Model Cancel (RecPmtCan)...........................................................................101 A.5.43 Recurring Payment Model Inquiry (RecPmtInq)............................................................................101 A.5.44 Recurring Payment Model Audit (RecPmtAud)..............................................................................102 A.5.45 Recurring Payment Model Synchronization (RecPmtSync)............................................................102 A.5.46 Payment Acknowledgment Inquiry (PmtAckInq)............................................................................102 A.5.47 Payment Acknowledgement Reversal (PmtAckRev).......................................................................103 A.5.48 Checksum Add (ChksumAdd)..........................................................................................................103 A.5.49 Checksum Modify (ChksumMod)....................................................................................................103 A.5.50 Checksum Status Modify (ChksumStatusMod)...............................................................................104 A.5.51 Checksum Cancel (ChksumCan).....................................................................................................104 A.5.52 Checksum Inquiry (ChksumInq)......................................................................................................104 A.5.53 Checksum Audit (ChksumAud)........................................................................................................104 A.5.54 Checksum Synchronization (ChksumSync).....................................................................................105
Version 1.7
April 2005
xv
Interactive Financial Exchange Business Message Specification A.5.55 Comprehensible Remittance Statement Add (CompRemitStmtAdd)...............................................105 A.5.56 Comprehensible Remittance Statement Inq (CompRemitStmtInq).................................................105 A.5.57 Comprehensible Remittance Statement Audit (CompRemitStmtAud).............................................106 A.5.58 Comprehenesible Remittance Statement Synchronization (ComprRemitStmtSync).......................106 A.5.59 Payment Batch Add (PmtBatchAdd)...............................................................................................107 A.5.60 Payment Batch Cancel (PmtBatchCan)..........................................................................................107 A.5.61 Payment Batch Status Inquiry (PmtBatchStatusInq)......................................................................107 A.6 BILL PRESENTMENT SERVICE.........................................................................................................................108 A.6.1 Biller Inquiry (BillerInq)...................................................................................................................108 A.6.2 Biller Reversal (BillerRev)................................................................................................................109 A.6.3 Bill Inquiry (BillInq).........................................................................................................................109 A.6.4 Bill Status Modification (BillStatusMod)..........................................................................................109 A.6.5 Bill Reversal (BillRev)......................................................................................................................109 A.7 ROOT SERVICES...........................................................................................................................................110 A.7.1 Terminal Object Add (TerminalObjAdd)..........................................................................................110 A.7.2 Terminal Object Modify (TerminalObjMod)....................................................................................110 A.7.3 Terminal Object Inquiry (TerminalObjInq)......................................................................................110 A.7.4 Terminal Object Delete (TerminalObjDel).......................................................................................110 A.7.5 Terminal Object Audit (TerminalObjAud)........................................................................................110 A.7.6 Terminal Object Status Modify (TerminalObjStatusMod)................................................................111 A.7.7 Terminal Service Provider Object Add (TerminalSPObjAdd)..........................................................111 A.7.8 Terminal Service Provider Object Modify (TerminalSPObjMod)....................................................111 A.7.9 Terminal Service Provider Object Inquiry (TerminalSPObjInq).....................................................111 A.7.10 Terminal Service Provider Object Delete (TerminalSPObjDel)....................................................112 A.7.11 Terminal Server Provider Object Audit (TerminalSPObjAud).......................................................112 A.7.12 Device Inquiry (DevInq).................................................................................................................112
B COMPATIBILITY POLICY...............................................................................................................1
B.1 INTRODUCTION.................................................................................................................................................1 B.2 DEFINITIONS....................................................................................................................................................1 B.2.1 Compatibility .......................................................................................................................................1 B.2.2 Change Levels.......................................................................................................................................1 B.3 COMPATIBILITY RULES......................................................................................................................................1 B.3.1 Policy Guidelines..................................................................................................................................2 B.4 EFFECTIVE START TIME ....................................................................................................................................2 B.5 MANAGING CHANGE FOR MIGRATIONAL EASE......................................................................................................2 B.5.1 Deprecation List....................................................................................................................................2
C INDEX......................................................................................................................................1
xvi
April 2005
Version 1.7
1 Overview
1.1Introduction
The Interactive Financial Exchange (IFX) Specification provides a robust and scalable framework for the exchange of financial data and instructions independent of a particular network technology or computing platform. The information-sharing potential of IFX has been designed to support communication not only between a Financial Institution and its customers, but also between a Financial Institution and its Service Providers, between Financial Institutions, and eventually directly between customers (e.g., electronic wallet). This specification supports existing and emerging financial services and is extensible and customizable for future growth. The IFX Specification has been developed as a cooperative industry effort among major Financial Institutions, Service Providers, and information technology vendors to these institutions and their customers in the small business and consumer markets. This specification builds on previous industry experience, including the OFX and Gold specifications that are currently implemented by major Financial Institutions and Service Providers to enable the electronic exchange of financial data between them and their customers. The IFX Specification provides a comprehensive specification for new financial industry services and software while providing a common strategic direction for the evolution of existing products and services. The IFX Specification provides Financial Institutions, their Service Provider vendors, and financial software developers for the small business and consumer markets with a generalized model for financial industry data communications. This generalized model consists of two parts: 1. A business-level Message Specification and its associated Data Dictionary, which are contained in Volumes 1 and 2, and 2. Implementation specifications, which are available separately at the IFX Forum website.
1.1.1The IFX Business Message Specification

This document provides the financial services industry with a common set of Business Messages that may be used to provide message-processing services across multiple organizations and networks. This document defines the information that must be sent in a message request and in a message response from a business perspective and provides message semantics for each request and response pair. This document provides the basis for business-level information flow between Financial Institutions, their customers, and third-party Service Providers. For example, an individual account holder may bank from home using a secure connection over the public Internet to connect to their Financial Institution. The same request message sent from the personal computer in the home may enter the Financial Institutions private data network for processing or be routed to a third-party Service Provider that processes that message on behalf of the Financial Institution. Regardless of the organization that actually processes the message or what computing and network architecture that organization has installed, the customer receives a response message with standard semantics.
1.1.2IFX Implementation Specifications

Complementary documents called Interactive Financial Exchange Implementation Specifications are expected to provide additional detail on how the business messages defined in this document may be physically represented. Each IFX Implementation Specification is an agreement between vendors and the financial services industry on how to implement the business messages defined in this document. IFX Implementation Specifications also provide the basis for interworking among products and services from various vendors and custom software developed by Financial Institutions and Service Providers.
1.2Design Principles
The IFX Specification has been designed to meet the following principles: Version 1.7 April 2005 1
Interactive Financial Exchange Business Message Specification Support a Broad Range of Financial ActivitiesThe IFX Specification is envisioned to incorporate the broad feature sets of the existing OFX and Gold specifications. Version 1.0 provides the following functions: Bank account balances, account information, statement download for deposit and loan accounts; Credit card statement download; Funds transfers, including recurring transfers; Consumer payments, including recurring payments; Business payments, including recurring payments; Bill presentment; and
Customer service. Support Financial Communications Among a Broad Range of PartiesThe IFX Specification supports financial communications among: Banks Brokerage houses (future) Service Providers Financial advisors (future) Small businesses
Consumers Support a Broad Range of Client DevicesThe IFX Specification allows Financial Institutions to support customers using a broad range of client devices, including, but not limited to: World Wide Web access using any standard Web Browser software, Personal Computers with Personal Financial Manager (PFM) software, Voice Response Units (VRUs) that provide Bank by Phone services, Automated Teller Machines (ATMs), and
Consumer Handheld Devices such as Personal Digital Assistants (PDAs) or Mobile Telephones with data capabilities. Support Customers Using Multiple Client DevicesThe IFX Specification allows a customer to use multiple client devices to interact with a Financial Institution. All devices get the same data for that customer and provide the customer with a consistent experience. The IFX Specification contains requests, which allow an intelligent client to discover what messages the customer has performed using other client devices. FlexibleThe IFX Specification is designed to provide Financial Institutions and Service Providers with the flexibility they need to rapidly develop, test, and deploy new services. The specification is intended to specify the minimum necessary functionality to provide reliable interactions between systems owned and maintained by customers, their Financial Institutions, and their Service Providers. CustomizableThe IFX Specification allows Financial Institutions and Service Providers to add custom elements, aggregates, or entire messages to rapidly deploy new services or add functionality to existing services. Custom elements, aggregates, and messages should be registered with the IFX Specification governance organization to protect against name collisions. However, registration of custom objects does not obligate any organization to use them in order to be in compliance with the specification. ExtensibleThe IFX Specification has been designed to allow for constant evolution through the addition of standardized services that may be easily implemented by Financial Institutions and their customers. OpenThe IFX Specification is publicly available. Solutions for financial communications based on the specification may be built by anyone, independent of any specific technology, vendor, or Financial Institution. IFX is currently maintained through cooperative industry effort and will be evolved into a formal standard over time.
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification RobustThe IFX Specification is used for the execution of important financial messages and the communication of sensitive financial data. The specification provides customers with confirmation that messages have occurred as planned and notification when scheduled messages fail. SecureThe IFX Specification provides a secure framework for the development of secure online financial services. IFX relies on industry standard mechanisms to provide secure channels between client and server and provides application-level authentication of customers and Financial Institution and Service Provider staff. Note that application-level authentication between different Service Providers for Electronic Bill Presentment and Payment may be provided through alternate means. Support Batch and Interactive SessionsThe IFX Specification may be implemented using either batch or interactive session management. The business-level messages are not biased towards either batch or interactive sessions. International SupportThe IFX Specification incorporates significant features for international support, including multiple currencies, and languages. Additional requirements for international support will be addressed as the specification evolves and international requirements are identified. Platform IndependentThe IFX Specification makes no assumptions about the hardware or software available as a client or server. IFX may be implemented on any computing platform. Transport IndependentThe IFX Specification makes no assumptions about the network used for the transport of business-level messages. IFX Implementation Specifications provide details on transport for a specific type of network.
1.3Benefits to Financial Institutions and Service Providers

Customer Acquisition and RetentionStandardization of message sets for financial message processing will remove technical barriers that currently limit an FIs ability to acquire customers for online banking services. These standards will level the competitive playing field for electronic delivery of financial services and allow Financial Institutions to serve new customers for whom appropriate channels have not previously existed. Broader vendor support for these message sets and the associated implementation specifications will stimulate end user adoption of online banking through the availability of a diverse set of client applications that interoperate with any FI that adopts this specification. FlexibilityBecause the semantics and syntax for the request and response message pair are defined end-to-end in IFX and the same message is passed regardless of the network technology, Financial Institutions and Service Providers are not locked into a single vendor or technology. They may find other ways to meet their business objectives if their service is not well supported by a vendor or network provider. ManageabilityStandardization of message sets for financial message processing will remove technical barriers that currently limit an FIs ability to acquire customers for online banking services. This common framework will provide Financial Institutions and their outsourced Service Providers with significant benefits in terms of their ability to manage the development and operation of a portfolio of services for their customers. Cost SavingsThe increased flexibility and manageability of solutions based on the IFX Specification will directly affect the profitability of an online financial service. Financial Institutions and Service Providers that invest in solutions based on IFX will see their investments returned quickly through operational cost savings.
1.4Benefits to Consumers and Businesses

Reliability and PerformanceIndividual consumers and small businesses will receive benefits in reliability and performance through the increased integration of their software with a Financial Institutions systems and networks. The IFX Specification is the product of an unprecedented level of cooperation between developers of consumer and small business financial applications and financial industry high-volume message processing experts.
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification Consistency of Experience with a Financial InstitutionConsumers of online financial services will notice significant improvements in the consistency of their interactions with the Financial Institution through multiple channels as the organizations take advantage of the improved service manageability and flexibility enabled by use of the IFX. Common Standard Across all Financial InstitutionsBusinesses and Consumers will also benefit from increased financial industry use of the IFX by their increased ability to manage their relationships with Financial Institutions using off-the-shelf software.
April 2005
Version 1.7
2 Structure
This section describes a number of important foundations of the IFX Specification, including terminology, data types, elements, aggregates, messages, services, authentication realms, naming conventions, versioning and governance, usage rules, and documentation conventions.
2.1Definitions
The following terms are used extensively in IFX Specification documentation and may have very specific meanings within this context.
2.1.1Biller
A Biller is a company or organization that sends a Bill or Statement to a customer, usually a request for payment for a product or service.
2.1.2Biller Payment Provider (BPP)

A Biller Payment Provider (or BPP) is an agent (usually a financial institution) of the Biller that originates and accepts payments on behalf of the Biller.
2.1.3Biller Service Provider (BSP)

A Biller Service Provider (or BSP) is an agent of the Biller that provides an electronic bill presentment and payment service for the Biller
2.1.4Client
Client refers to the sender of an IFX Request Message. The client may be a computer system that a Customer is logged into, or it may be some kind of proxy device that is making IFX Requests on behalf of the Customer. This scenario is typical in the case of a Customer using a Web browser to perform financial messages. The Web server may be communicating using IFX Messages to some back end system. In this case, the Web server is considered a proxy client and the back end system is the server. It should be noted that clients might also be Service Providers for certain messages, such as the Pay/No-Pay message and Reverse Pay Decision message.
2.1.5Customer
A Customer is an individual or small business that is a consumer of financial services provided by a Financial Institution.
2.1.6Customer Payment Provider (CPP)

A Customer Payment Provider (or CPP) is an agent (usually a financial institution) of the Customer that originates payments on behalf of the Customer.
2.1.7Customer Service Provider (CSP)

A Customer Service Provider (or CSP) is an agent of the Customer that provides an interface directly to customers, businesses, or others for bill presentment. A CSP enrolls customers, enables presentment, and provides customer care, among other functions.
2.1.8Financial Institution (FI)

A Financial Institution (or FI) is an organization that provides branded financial services to customers. Financial Institutions develop and market financial services to individual and small business customers. Financial Institutions may serve as the processor for their own services or may choose to outsource processing
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification to a Service Provider. In an effort to group the services different providers provide, the Financial Institution is also referred to as a Financial Institution in this document.
2.1.9Provider
When the term provider is used generically, typically qualified by a service name (e.g., Pay provider), it refers to an organization that processes messages that support financial services provided to individual and small business customers. A provider may be either of the following: A Financial Institution that has chosen to perform its own message processing in support of its services or A Service Provider that performs message processing on behalf of a Financial Institution that has decided to outsource this function.
2.1.10
Server
Server refers to a system that receives IFX Request Messages and responds with IFX Response Messages. For clarity in the documentation, the server is assumed to be an endpoint that composes the entire response message and sends it back to the client. In the real world, systems may be implemented with multiple stages of message processing that are transparent to the client. As long as the complete response message is delivered to the client, the protocol will work as designed.
2.1.11
Service
Service specifically refers to a collection of related messages. For example, the Bank service encompasses banking messages such as requesting bank statement, initiating stop checks, etc. This definition correlates to an application-level concept of service that refers to a single function or a collection of similar functions that are branded and marketed to individuals and small businesses by a Financial Institution or Service Provider. Within this specification, each SP maintains a list of the services it supports. Services that are currently defined in this specification are Banking (Bank), Payment (Pay), Presentment (Pres), Valuable Media (Media), and Root (Root). Customer Service and a few other functions including Service Profile are grouped together in a chapter called Base Service (Base). Additional services may be defined and implemented by Financial Institutions or Service Providers as extensions to this specification.
2.1.12
Service Provider (SP)
A Service Provider (or SP) is an organization that provides services to an individual or to other organizations. An example of a Service Provider is a message processor for a Financial Institution that has chosen to outsource its message processing for a particular service. Service Providers typically provide services for multiple individuals or organizations. A Biller may be considered a Service Provider; however, in this document the term Service Provider is used to refer generically to an FI, CSP, CPP, BSP and/or BPP. Organizations that provide services to end user customers are referred to specifically as Financial Institutions or CSPs where possible. Note: The labels CSP, CPP, BSP and BPP are used to define a collection of functions and responsibilities. They do not necessarily refer to specific physical or business entities. Any entity wishing to perform a particular role needs to address the issues and responsibilities defined for that role. It is also understood that one entity may perform more than one role, or that an entity may wish to outsource one or more functions of a role to other entities. For example, some Billers may serve as their own BSPs, some Financial Institutions may perform the role of both CSP and CPP, and some CSPs may outsource functions such as customer care to other service providers. For more information about the responsibilities of the various roles, see the Electronic Bill Presentment and Payment Business Practices at http://www.nacha.org/billpay/businesspractices.htm.
2.1.13
May, Should, and Must
The terms may, should, and must are used frequently within this specification.
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification May indicates that the described behavior is not required for IFX compliance, nor is there any preferred behavior. Generally, the behavior is described to inform of possible behaviors of which client or server designers and developers should be aware. Should indicates that, while the described behavior is not required for IFX compliance, it is preferred. Generally, the behavior is described to provide a better experience for the communicating parties. Must indicates that the described behavior is required for IFX compliance.
2.2Documentation Conventions
Documentation conventions in the specification include: o All documentation is written and maintained in US English. Required elements and aggregates have Required in the Usage column. In a request message, Required means that the client must include the element.
o In a response message, Required means that the server must return the element if the message is successful, with the exception of <CustId> and <RqUID>, which must always be returned. There are exceptions to the <CustId> requirement; those are explicitly called out in the message definitions within this specification. Optional elements and aggregates have Optional in the Usage column. If there are specific cases where an optional element or aggregate may be required, it is noted by but see Description in the Usage column, to call attention to this condition. For successful synchronous messages (i.e., responses with a <Status> <Severity> of Info or Warn) in a session where the client did not request suppression of echo (via <SuppressEcho> = True, see section 4.4.2.1) or the server does not support echo suppression, a server must echo all fields provided in the request that are indicated in the response by Echoed in the Usage column. For unsuccessful messages (i.e., responses with a <Status> <Severity> of Error), successful messages in a session where the client requested to suppress echo (via <SuppressEcho> = True, see section 4.4.2.1), or asynchronous responses, a server must echo <RqUID>, and, if present in the request, <AsyncRqUID> and <CustId>. For more information about synchronous responses and echoes, see section 3.2.12.1. Some elements and aggregates are required only if the Service Provider indicates this through the Service Profile for the service. These elements and aggregates have Profiled requirement in the Usage column. Some elements have valid values defined by the Service Profile. These elements have Profiled values in the Usage column. Some elements and aggregates are only valid if support for them is indicated in the Service Profile. These elements have Profiled support in the Usage column. Repeating elements and aggregates may appear more than once, and are indicated by Repeating in the Usage column. An inclusive or condition requires at least one of the members of the group to be present, and is indicated with OR in the Usage column. A thin dashed line separates the members of the OR, while a thicker dotted line indicates the boundaries of the entire OR group. An exclusive or condition requires one, and only one, of the members of the group to be present, and is indicated with XOR in the Usage column. A thin dashed line separates the members of the XOR, while a thicker dotted line indicates the boundaries of the entire XOR group. An and condition requires all or none of the members of the group to be present, and is indicated with a AND in the Usage column. A thin dashed line separates the members of the AND, while a thicker dotted line indicates the boundaries of the entire AND group. Indentation indicates that the indented element or aggregate is contained in the most recent aggregate that has one less indentation.
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification 1.x+ = The noted element or aggregate is the preferred element or aggregate for implementations utilizing the specification cited. The usage signifies that the XORd item will be deprecated in the next major release.
Tag <Element1>
Type
C-12
Usage
Required
Description
Required Element. Occurs exactly once in each Request, or exactly once in each successful Response.
<Element1>
C-36
Optional
Optional Element. Occurs zero or one times.
<Element1>
C-12
Optional Repeating Optional Profiled support Optional Repeating Profiled values Optional Echoed
Optional Repeating Element. Occurs zero or more times. Profiled Aggregate. Occurs zero or one times. Usage is controlled by an entry in the Service Profile. Profiled Open Enum. Occurs zero or more times. Supported values are controlled by an entry in the Service Profile. Echo Aggregate. Occurs zero or one times. Must be included in the response message if it was received in the request. Optional and. Two valid cases (1) both <Element1> and <Element2>, (2) neither. Inclusive or. Three valid cases (1) <Element1>, (2) <Element2>, (3) both <Element1> and <Element2>. Optional exclusive or. Three valid cases: (1) neither <Element1> nor <Element2>. (2) <Element1>, but not <Element2>. (3) <Element2>, but not <Element1>. Required Exclusive or. Two valid cases: (1) <Element1>, but not <Element2>. (2) <Element2>, but not <Element1>. Required Exclusive or. Two valid cases: (1) <Element1>, but neither <Element2> nor <Element3>. (2) <Element2> and <Element3>, but not <Element1>.
<Aggregate1>
Aggregate
<Element1>
Open Enum
<Aggregate1>
Aggregate
<Element1> <Element2> <Element1> <Element2> <Element1> <Element2>
Long Decimal Long Decimal Long Decimal
Optional AND Optional AND Required OR Required OR Optional XOR Optional XOR Required XOR Required XOR Required XOR Required XOR Required Required XOR Required XOR
<Element1> <Element2> <Element1> <Element2>
Long Decimal Long Decimal
<Element3> <Element1> <Element2>
C-10 Long Decimal
Required Exclusive or. Three valid cases: (1) <Element1>, but neither <Element2> nor <Element3>. (2) <Element2> and <Element3>, but not <Element1>. (3) <Element2>, but neither <Element1> nor <Element3>.
April 2005
Version 1.7
Tag <Element3>
Type
C-10
Usage
Optional
Description
2.3Data Types
The IFX Specification is designed around a small number of data types that are used to represent all data passed between clients and servers using the messages defined in this specification. All information elements are based on these data types. Supported data types are: Character Narrow Character Binary Boolean YrMon, Date, Time, DateTime, and Timestamp Decimal Currency Amount HexBin IFX defines the semantics and logical attributes of each data type. The physical representations are defined within the implementation specifications. Closed Enum Open Enum Long Identifier Phone Number Universally Unique Identifier (UUID) URL
2.3.1Character
Character indicates an element that allows character data up to a maximum number of characters, regardless of the number of bytes required to represent each character. The number after the hyphen specifies the maximum number of characters. For example, C-12 specifies an element of characters with maximum length 12 characters. C- indicates an element with no maximum length. It is expected that character type elements may contain multibyte representations of characters in some implementations, depending on the allowable character sets.
2.3.2Narrow Character
Elements of type Narrow Character are elements of character data type with the additional restriction that the only allowable characters are those contained within the ISO Latin-1 character set (http://www.htmlhelp.com/reference/charset/). The Narrow Character set limits the characters to accommodate interfacing to existing standards such as the ABA standard for card track 2 mag stripe data.
2.3.3Binary
The Binary data type is a compound type consisting of three logical elements:
Tag
<ContentType> <BinLength> <BinData>
Type
Open Enum Long Raw Binary Data
Usage
Optional Required Required
Description
Specified in IETF RFC 2046. Identifies the size of the binary data in number of bytes. Binary data.
Version 1.7
April 2005
2.3.4Boolean
Boolean indicates a logical True or False condition. The physical representation of Boolean data is specified by each implementation specification corresponding to this message specification.
2.3.4.1 Boolean Conventions and Selection Criteria

The general usage of Booleans within the IFX specification is: <TagName> (optional) If True, then If False or omitted, then This usage of Booleans in IFX allows optional Booleans to be added in future revisions while maintaining upward compatibility. There are instances where it is considered too error prone to allow a default of False. In these cases the Boolean is required. The convention for the use of selection criteria for read messages is: For Booleans: <TagName> (optional) True. False. If True, then the selected set must include at least those items where the condition is If False, then the selected set must include at least those items where the condition is
If omitted, then this item is ignored as a selection criterion. Usage notes specify when a Boolean is used as a selection criterion. For others: <TagName> (optional) If present, the selected set must include at least those items where the value in the request matches a value for the corresponding tag in the searched region. If absent, the selected set must include items with any value, including NULL, for the corresponding tag in the searched region.
2.3.5YrMon, Date, Time, DateTime, and Timestamp

The IFX Specification includes five time-related compound data types: YrMon, Date, Time, DateTime, and Timestamp. In all types that describe Date information, IFX 1.0.1 uses the Gregorian calendar. Other calendars may be considered for future versions as requirements are identified. Data types including time information refer to a 24-hour clock. All date and time types include (with the largest units given first): year, month, day, hour, minute, second, and fractions of a second. Any particular type may include a subset of these possible values. Types including time information (hour, minute, etc.) may also include an offset from Coordinated Universal Time (UTC). Note: In a DateTime element, specifying a date without a time or time zone will result in a time of midnight, UTC. This will result in the previous date appearing for all time zones in the western hemisphere. For example, October 5, 2002, without a specified time zone offset, will appear to be October 5, 2002, for the eastern hemisphere, but October 4, 2002, for the western hemisphere. Therefore, for DateTime elements where a single date is desired
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification worldwide, the time must be included, and it must result in noon, UTC (e.g., 12:00:00 or 09:00:00-03:00). Note: IFX does not require servers or clients to use the full precision specified. However, they are required to accept any of these forms without complaint. As a general rule for date and time compound data types, values may be entered that omit the smallest logical elements. In every case, the value is taken to mean the same thing as if the minimum values (such as zeroes) were included. (The default is always the start of an otherwise ambiguous range for types other than YrMon.) For example, a DateTime value omitting the time portion means the start of the day (12:00 midnight). Note that time zone qualifiers (in time and DateTime values) are an exception to this rule, as they may be included even if times are not specified to the millisecond. The logical elements appearing in each of these compound data types are summarized below. Required means that the element must occur in all instances of the data type. Recommended means that the element should be included in all instances of the data type. Optional elements may be omitted from an instance of the data type. Optional elements must be included if smaller elements are to be included. For example, month must not be omitted from a date value if day is included.
Contains
Year YYYY 0000-9999 Month MM 1-12 Day DD 1-31 Hours HH 0-23 Minutes MM 0-59 Seconds SS 0-60 Fractional Seconds XXX (minimum) Precision is determined by the implementation HH 0-23 MM 0-59 N/A N/A Recommended Recommended Recommended N/A N/A Recommended Recommended Recommended N/A N/A Optional Optional Optional N/A N/A Optional Optional Required N/A N/A Optional Optional Required N/A N/A Required Optional Required N/A Optional N/A Required Required Required Optional N/A Required Required
YrMon
Required
Date
Required
Time
N/A
DateTime
Required
Timestamp
Required
UTC offset Hours UTC offset Minutes (time zone indication)
2.3.5.1 YrMon
Elements of data type YrMon contain an indication of a particular month. This data type describes a unique period of time (not a repeating portion of every year). This may (for example) be used to describe an expiration date for a credit card. In that case, the period represented is actually a shorthand for the last day (or millisecond or whatever minimum interval) of the month described. Logically, the YrMon data type must contain a month and 4-digit year. Unlike the other date and type types, values of this type must not be shortened by any omission of its portions: Both the year and month are required.
Version 1.7
April 2005
YrMon Data type

Year Month
Type
Long Long
Usage
Required Required
Description
4-digit year value. Number of the represented month. Value must be within the range 1 through 12.
2.3.5.2 Date
Elements of data type Date contain an indication of a particular day. This data type describes a unique period of time, normally 24 hours (not a repeating portion of every year). Logically, this data type must contain a 4-digit year, and may contain a month number, and day number.
Date Data type
Year Month
Type
Long Long
Usage
Required Optional but see Description
Description
4-digit year value. Number of the represented month. Value must be within the range 1 through 12. Must be included if <Day> is included. If absent, the value is assumed to be 1 (January). Number of the represented day. Value must be within the range 1 through 31. If absent, the value is assumed to be 1.
Day
Long
Optional
2.3.5.3 Time
Elements of data type Time contain an indication of a particular time during a date. This data type describes a repeating portion of a day. That is, each time described (ignoring leap seconds) occurs once per calendar date. In the IFX specification, it is required that a time data type be able to represent a specific period with indefinite precision. Milliseconds are the minimum required precision of the time data type. A time represented using this data type must not be ambiguous with respect to morning and afternoon. That is, the time must occur once and only once each 24-hour period. In addition, the Time data type must not be ambiguous with respect to location at which the time occurs. If unspecified, the time zone defaults to Coordinated Universal Time (UTC). Generally, use of a specific time zone in the representation is preferred. The time zone should always be specified to avoid ambiguous communication between clients and servers.
Time Data type

Hour Minute
Type
Long Long
Usage
Description
Number of the represented hour. Value must be within the range 0 through 23. Number of the represented minute. Value must be within the range 0 through 59. Must be included if <Second> is included. If absent, the value defaults to 0. Number of the represented second. Value must be within the range 0 through 60. The value 60 is used only to represent leap seconds. Must be included if <Fraction> is included. If absent, the value defaults to 0.
Second
Long
Optional but see Description
April 2005
Version 1.7
Time Data type

Fraction
Type
Long
Usage
Optional
Description
Number of represented microseconds. Value must be within the range 0 through 999,999. Particular implementations may choose to allow representations of smaller fractions. If absent, the value defaults to 0.
UTCOffsetHour
Long
Optional
Offset from UTC in hours. Value must be within the range of 0 thorugh 23. Must be included if <UTCOffsetMinute> is included. If absent, the value defaults to 0.
UTCOffsetMinute
Long
Optional
Offset from UTC in minutes. Value must be within the range of 0 through 59.
2.3.5.4 DateTime
Elements of data type DateTime contain all of the information expressed by the date and time data types. All ambiguities mentioned with Date and Time (see Sections 2.3.5.2 and 2.3.5.3) should be resolved in a similar fashion here.
DateTime Data type
Year Month Day Hour
Type
Long Long Long Long
Usage
Required Required Required Optional but see Description
Description
4-digit year value. Number of the represented month. Value must be within the range 1 through 12. Number of the represented day. Value must be within the range 1 through 31. Number of the represented hour. Value must be within the range 0 through 23. Must be included if <Minute> is included. If absent, the value defaults to 0. Number of the represented minute. Value must be within the range 0 through 59. Must be included if <Second> is included. If absent, the value defaults to 0. Number of the represented second. Value must be within the range 0 through 60. The value 60 is used only to represent leap seconds. Must be included if <Fraction> is included. If absent, the value defaults to 0.
Minute
Long
Second
Long
Fraction
Long
Optional
Number of represented microseconds. Value must be within the range 0 through 999,999. Particular implementations may choose to allow representations of smaller fractions. If absent, the value defaults to 0.
UTCOffsetHour
Long
Optional
Offset from UTC in hours. Value must be within the range of 0 thorugh 23. Must be included if <UTCOffsetMinute> is included. If absent, the value defaults to 0.
UTCOffsetMinute
Long
Optional
Version 1.7
April 2005
2.3.5.5 Timestamp
Elements of data type Timestamp contain the same information as DateTime values. Unlike that data type, Timestamp information is not intended to have meaning at the other end of the communication. In addition, microseconds are the minimum required precision of the time portion of this data type. The intent here is to describe a type identical to DateTime but without semantic meaning between two machines. The general DateTime data type has meaning on both ends of the protocol (even though time synchronization is not required by this specification). Timestamp indicates an exact point in time with respect to the generating application. For example, a Timestamp value may be generated at a server when creating an audit response. The client application may return that value to the server in later requests, but the client software should not interpret the information.
Timestamp Data type
Year Month Day Hour Minute Second
Type
Long Long Long Long Long Long
Usage
Required Required Required Required Required Required
Description
4-digit year value. Number of the represented month. Value must be within the range 1 through 12. Number of the represented day. Value must be within the range 1 through 31. Number of the represented hour. Value must be within the range 0 through 23. Number of the represented minute. Value must be within the range 0 through 59. Number of the represented second. Value must be within the range 0 through 60. The value 60 is used only to represent leap seconds. Number of represented microseconds. Value must be within the range 0 through 999,999. Particular implementations may choose to allow representations of smaller fractions. Offset from UTC in hours. Value must be within the range of 0 thorugh 23. Must be included if <UTCOffsetMinute> is included. If absent, the value defaults to 0.
Fraction
Long
Required
UTCOffsetHour
Long
Optional
UTCOffsetMinute
Long
Optional
2.3.6Phone Number
Phone Number indicates a string of up to 32 narrow characters in length (NC-32). It must begin with a plus sign + followed by country code, a hyphen, city/area code, another hyphen, then the local phone number. If a PBX extension is to be included, it must appear at the end of the field, separated from the rest of the telephone number by a plus sign. For example, +1-800-5551212+739 indicates PBX extension 739 at phone number 5551212 within area code 800 of North America (country code 1).
2.3.7Decimal
Decimal indicates a numeric value that meets the following rules: The value is up to fifteen (15) decimal digits in length. The value is not restricted to integer values and has a decimal point that may be placed anywhere from the left of the leftmost digit to the right of the rightmost digit (e.g., +.12345678901234 is acceptable while 12345678901234567 is not).
10
April 2005
Version 1.7
The sign is always optional. If it is absent, the value is assumed to be positive.
2.3.8Long
Long is an integer value, which may be positive, negative, or zero, with values ranging from 2147483648 to 2147483647.
2.3.9Currency Amount
A Currency Amount is a compound data type consisting of four logical elements:
Tag
<Amt> <CurCode>
Type
Decimal NC-3
Usage
Required Optional but see Description Optional AND
Description
Amount. Currency code. Required if <CurRate> is specified.
<CurRate>
Decimal
Exchange rate. The ratio of the foreign currency and the currency of the account. The <CurConvertRule> specifies which amount is the numerator and which is the denominator. Currency Conversion Indicator. Valid values are Direct and Indirect. See below for more information.
<CurConvertRule>
Closed Enum
Optional AND
All monetary amounts in the IFX Specification are handled with the Currency Amount data type. When included, this data type contains a decimal value for the amount, an optional three-letter currency code defined in ISO-4217, an optional currency rate, and an optional exchange rate indicator. When Currency Code is not included, Amount is assumed to represent the currency of the account (in particular the from account in the case of a transfer or payment). The valid values for the exchange rate indicator are Direct and Indirect. The indirect rate is the amount of foreign currency per unit of base currency. The direct rate is the amount of base currency per unit of foreign currency. If the exchange rate is present, the currency indicator must be specified. The currency indicator identifies the way in which the rate is calculated. Derive domestic equivalent from a specified foreign amount: If the rate is Indirect, divide the foreign amount by the rate, If the rate is Direct, multiply the foreign amount by the rate. Derive foreign amount from a specified domestic amount: If the rate is Indirect, multiply the domestic amount by the rate, If the rate is Direct, divide the domestic amount by the rate. Examples (USD is the base): USDGBP USDDEM Indirect = .6037 Indirect = 1.6866 Direct = 1.6590 Direct = .5929
The following table is intended to illustrate when the elements within the Currency Amount data type are used.
Use Cases
Initiating a transaction In the currency of the FROM account In a currency different than the FROM account Required Required Required Only used when a pre-committed exchange rate is used, see the Foreign Exchange Rate message
<Amt>
<CurCode >
<CurRate> and <CurConvertRule>
Version 1.7
April 2005
11
Reporting a transaction e.g. within a statement In the currency of the account. Originating in a currency different from the currency of the account. Required Required Required Required
2.3.10
Enum
Enum is a Narrow Character type that has a limited number of specified valid values, each of which is represented by a tag of up to 80 characters each. The Enum data type is either a Closed Enum or an Open Enum. Adding a value to a Closed Enum requires a spec update, while adding a value to an Open Enum only requires out-of-band agreement by the end points.
2.3.10.1 Closed Enum

A Closed Enum is an element where a number of valid values are defined within this specification. All other values should be rejected as invalid.
2.3.10.2 Open Enum

An Open Enum is an element where a number of valid values are defined within this specification, but other values should not be rejected as invalid by any system other than the final message destination. Open Enums provide a mechanism for a client and final destination server to communicate with values that may be known to both endpoints but not to all intermediate servers that route the message. If the client sends a value that was not listed in the Service Profile as being a supported value in a Profiled Values element, the server must respond with the most specific response code possible (for example, Frequency not supported). Otherwise, if the client or server receives a value that it does not recognize, it must be treated as the type other. Open Enums are typically used for elements related to system message processing and have been defined as open to support extensibility and customization of the specification.
2.3.11
Identifier
Object identifiers in the IFX Specification are of the data type Identifier. This is a Narrow Character data type with a maximum length of 36.
2.3.12
Universally Unique Identifier (UUID)
UUID elements are Narrow Character with a maximum length of 36. A UUID is an identifier that is unique across both space and time, with respect to the space of all UUIDs. To be precise, the UUID consists of a finite bit space. Thus, the time value used for constructing a UUID is limited and will roll over in the future (approximately at A.D. 3400, based on the specified algorithm). A UUID may be used for multiple purposes, from tagging objects with an extremely short lifetime to reliably identifying very persistent objects across a network. The following information on UUID is based on Internet-Draft <leachuuids-uuids-01.txt>: The generation of UUIDs does not require that a registration authority be contacted for each identifier. Instead, it requires a unique value over space for each UUID generator. This spatially unique value is specified as an IEEE 802 address, which is usually already available to network-connected systems. This 48-bit address may be assigned based on an address block obtained through the IEEE registration authority. This section of the UUID specification assumes the availability of an IEEE 802 address to a system desiring to generate a UUID, but if one is not available, section 4 specifies a way to generate a probabilistically unique one that cannot conflict with any properly assigned IEEE 802 address.3.1 Format. In its most general form, all that may be said of the UUID format is that a UUID is 16 octets, and that some bits of octet 8 of the UUID called the variant field (specified in the next section) determine finer structure.
12
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification For use in human-readable text, a UUID string representation is specified as a sequence of fields, some of which are separated by single dashes. Each field is treated as an integer and has its value printed as a zero-filled hexadecimal digit string with the most significant digit first. The hexadecimal values a to f inclusive are output as lower case characters, and are case insensitive on input. The sequence is the same as the UUID constructed type. The formal definition of the UUID string representation is provided by the following extended BNF:
UUID time_low time_mid time_high_and_version clock_seq_and_reserve d clock_seq_low node hexOctet hexDigit <time_low> - <time_mid> - <time_high_and_version> - <clock_seq_and_reserved> <clock_seq_low> - <node> 4*<hexOctet> 2*<hexOctet> 2*<hexOctet> <hexOctet> <hexOctet> 6*<hexOctet <hexDigit> <hexDigit> zero | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9| a | b | c | d | e | f | A | B | C | D | E | F
The following is an example of the string representation of a UUID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6
2.3.13
URL
An element of the Uniform Resource Locator URL data type specifies the URL where a customer may access information. A URL is of the Narrow Character data type with a length of 1024 Characters (NC-1024). The format of a URL begins with a string that identifies which protocol is to be used to access the information, such as http://.
2.3.14
HexBin
Each HexBin character will define the 4-bit nibble of the 8-bit byte transformed into a hex character, with the maximum length (n) of the transformation specified. The HexBin represents arbitrary hex-encoded binary data. The value space of HexBin is the set of finite-length sequences of binary octets. Each binary octet is encoded as a character tuple, consisting of two hexadecimal digits ([0-9, A-F]) representing the octet code. For example, "0FB7" is the hex encoding for the 16-bit integer 4023 (whose binary representation is 111110110111).
2.4Building Blocks
The IFX Specification is constructed using the following building blocks:
Element Aggregate Message Service Document The most basic unit of data in the IFX Specification to define a single piece of information (of a specific data type) that is passed between the client and the server. A group of related elements to provide a mechanism for coding logic rules and a convenient method to refer to related information using a single name. A collection of elements and/or aggregates to be passed from the client to the server (Request Message) or from the server to the client (Response Message). A single function or a collection of similar functions that are branded and marketed to individuals and small businesses by a financial institution. A collection of services and messages sent as a single unit between client and server.
Version 1.7
April 2005
13
2.4.1Element
An Element is the most basic unit of data in the IFX Specification. An element is defined based on one of the supported data types to define a single piece of information that is passed between the client and server. An element is named according to specific rules and has a definition associated with it to provide additional information on what it contains. An element may also have some usage rules associated with it, which describe how the client and server interact with the element. For example, the <ChkNum> element is based on the Character data type with a maximum of 12 characters and specifies a Check Number. Depending on where it is used in the specification, it may be provided by the client or the server.
2.4.2Aggregate
A number of related elements may be grouped together into an Aggregate. An aggregate provides a mechanism for coding logic rules (element 1 or element 2 must be provided) and also provides a convenient way for programmers to specify all of the related information by using a single name. Note that multiple aggregates may use the same structure. This may occur to allow use of a more descriptive name, e.g., <BillingAddr> in the <PresAcctId> aggregate has the same structure as the <PostAddr> aggregate. This may also occur when a unique name must be used due to the same aggregate being used more than once within a request/response message, e.g. TO/FROM account within a transfer message.
2.4.2.1 External Aggregate

An external aggregate is an aggregate (section 2.4.2) that is defined and maintained by an external authority. Typically, an external aggregate will embed data defined by another standards organization or authoritative body. The IFX Data Dictionary entry will contain a reference to the defining organization and will indicate where to obtain an authoritative definition of the aggregate. The requirements for, and use of, an external aggregate is defined by IFX in this document. The external authority responsible for the aggregate defines the requirements for, and use of, the contents of that aggregate. This data type is not intended to support customization of the IFX standard; rather, it is intended to support interoperability between related standards as deemed appropriate by the IFX Forum. Inclusion of an external aggregate does not ensure that the external aggregate will adhere to BMS-specified rules for maintenance and data formatting. In particular, compatibility rules between IFX releases may not be applicable to IFX messages that contain external aggregates nor can IFX data-typing rules be assumed (i.e., date formats, field sizes, required contents, etc.). When dealing with external aggregates a processing application must be able to separate the handling of IFX data from that of the external data and apply appropriate processing and formatting rules.
2.4.3Message
A Message is a collection of elements and/or aggregates, which is passed from the client to the server (Request Message) or from the server to the client (Response Message). A response message is typically a superset of the request that echoes back the information included in the request and adds new information as appropriate to the message being conducted. All requests are sent from client to server and all responses are sent from server to client. IFX uses several common message types to perform specific functions. Within IFX, the following naming conventions are used, where the messages associated with objects of type xxx include: Add request <xxxAddRq> and response <xxxAddRs> Modify request <xxxModRq> and response <xxxModRs> Delete request <xxxDelRq> and response <xxxDelRs> Cancel request <xxxCanRq> and response <xxxCanRs> Inquiry request <xxxInqRq> and response <xxxInqRs>
14
April 2005
Version 1.7
Audit request <xxxAudRq> and response <xxxAudRs> Synchronize request <xxxSyncRq> and response <xxxSyncRs> Advise request <xxxAdviseRq> and response <xxxAdviseRs> Reversal request <xxxRevRq> and response <xxxRevRs>
2.4.3.1 Add Message

The Add IFX message has a name structure of <xxxAddRq>/<xxxAddRs>. It is used to create a new instance of object xxx (such as creating a new payment using <PmtAddRq>).
2.4.3.2 Modify Message

The modify IFX message has a name structure of <xxxModRq>/<xxxModRs>. It is used to modify an existing instance of object xxx (such as modifying an existing payment using <PmtModRq>. A client modifies a record on the server using the appropriate Modify request message and replaces the entire existing object (all properties) with the newly submitted object. Therefore, within a modify request message, all properties of the object that are intended to be stored must be included, even if the values are not modified. The complete replacement requirement for specific objects can be adjusted to meet the needs of specific applications. This adjustment is intended to support data within an object that cannot be modified (i.e., the create date). The fields affected by this adjustment must be established out of band, often through an application specific implementation guide.
2.4.3.3 Delete and Cancel Messages

The delete and cancel IFX messages have a name structure of <xxxDelRq>/<xxxDelRs> and <xxxCanRq>/<xxxCanRs>, respectively. They are used to delete an existing instance of object xxx (such as deleting a payee from the customer payee list using <CustPayeeDelRq>), or to cancel an existing scheduled object (such as canceling a pending payment using <PmtCanRq>.
2.4.3.3.1 Cascading Deletes

The following objects are considered related (the leftmost object cascades into the object on the right of the colon): Presentment service: Bill Presentment Accounts Payment service: Payment Service Accounts, Pending payments (that are not yet in process or processed), Recurring payment models, Customer payees Payment Service Accounts: Pending Payments (that are not yet in process or processed), Recurring Payment models. While Customer payees are not truly related objects to accounts, a customer payee object may contain default payment information <DfltPmtInfo> with a <DepAcctIdFrom> or <CardAcctIdFrom>. If the Account being deactivated is listed as a default payment funding account for any customer payee, the customer payee object should be updated to remove the reference to the deactivated account. Since default payment information accounts are optional, this will not present any data integrity problems. Banking Service: Banking Service Accounts, Pending Transfers (that are not yet in process or processed), Recurring transfer models Banking Service Accounts: Pending Transfers (that are not yet in process or processed), Recurring transfer models o Bill Presentment Accounts: Bills (Conditional) New, Delivered or Viewed bills must be deleted.
o Retired, Withdrawn or Undeliverable bill summaries should remain at the CSP/BSP. The CSP/BSP is responsible for allowing continued customer access to those bill summaries.
Version 1.7
April 2005
15
Interactive Financial Exchange Business Message Specification Customer Payees: Pending payments (that are not yet in process or processed), Recurring payment models Pending Payments: none Recurring Payment Models: Pending payments (that are not yet in process or processed) Pending Transfers: none Recurring Transfer Models: Pending transfers (that are not yet in process or processed)
Payment Service
Payment Account
Payment Account
Customer Payee
Pending Payment
Recurring Payment Model
Pending Payment
16
April 2005
Version 1.7
Banking Service
Banking Account
Banking Account
Banking Account
Pending Transfer
Recurring Transfer Model
Pending Transfer
Presentment Service
Presentment Account
Presentment Account
Presentment Account
Bill
Each object defined above is represented in the hierarchy. Whenever an object is disabled/deactivated/deleted, all the objects below that are also deleted if <CascadeDel> = True. If related objects are deleted as part of a cascade delete, <xxxDelRs> and <xxxCanRs> messages must be placed in appropriate Audits and Syncs to properly communicate what was removed as part of the cascade delete. The sole exception to this is when an entire service is removed. If the service removal is successful, only the service Rs is required in the Audit or Sync. Cascade Delete should not apply to completed/processed payments or retired/withdrawn/undelivered bills. It is expected that the service will denormalize the payment-payee-account data for a processed payment such that the record of the payment (and all its related data) is self-contained. It is also expected that a service will denormalize the biller-billing account-bill data for a retired/withdraw/undelivered bill such that a record of the bill is self-contained.
Version 1.7
April 2005
17
Interactive Financial Exchange Business Message Specification A <BillStatusModRq> should be issued when a payment related to a bill is deleted as a result of a cascade from a higher-level object delete. The <BillStatusModRq> must include a <BillPmtStatus> aggregate with the <BillPmtStatusCode> supplied with a value of Cancelled. The specification provides for supplying a bill identifier when adding/modifying a payment to establish this relationship. If a server is unable to remove the entire dependent object tree during a cascade delete, then all of them must remain and the request must respond with a code of 1300.
2.4.3.4 Inquiry Message

The inquiry IFX message has a name structure of <xxxInqRq>/<xxxInqRs>. It is used to search for and/or gain information about the current state of existing objects xxx (such as finding one or more existing payments using <PmtInqRq>). Inquiry messages limit the response set to records matching the selection criteria used in the request. Selection criterion elements in the request are sometimes repeating elements; where more than one value is given for a particular element (i.e., a repeating element), the query ORs those values. Where selection criteria across multiple different elements are provided, the query ANDs those values. Where an element is absent, the query is not filtering on that element. Several <Status> codes are available to help the client understand the results of an Inquiry Message: 1120 indicates that all of the search criteria that the server was aware of were applied, and no records that matched the search criteria were found. 1140 indicates that some, but not all, of the search criteria that the server was aware of were applied, and records were found that matched the search criteria used. 1160 indicates that none of the search criteria that the server was aware of were applied, and an unfiltered set of records were found for the implicit search criteria, e.g. <CustId>. The phrase that the server was aware of is used to recognize the situation that a client is implemented using a more recent level of the IFX spec than the server has implemented. If the later version added optional search criteria, the server wont be aware of them. The client may test the <Version> value within the <SvcCore> aggregate to determine if the server is implemented to an older version of IFX. The client may use this knowledge to better interpret the <Status> code values. Note: A server is not obligated to support filtering on all selection criterion elements. If a server chooses not to support a particular element as a selection criterion, it must treat that element as if it were not present in the request. That is, the server must return the appropriate record set for the elements on which it does support filtering. As a result, clients should be prepared to receive records outside the scope of the selection criteria submitted in the request.
2.4.3.5 Audit and Synchronization Messages

This section introduces the concepts of message auditing and data synchronization as used in the IFX Specification. As its name implies, message auditing is a server function that records all message activity (i.e., creates and stores records for audit trail purposes) affecting the state of IFX defined objects. Examples of such objects are transfers, payees, and payments. The specific audit messages provide a user (typically a customer service representative [CSR]) the capability to retrieve a time-sequenced listing of message responses that added, modified or deleted a users objects. Informational messages like inquiries do not affect the state of the business objects, and therefore are not recorded in the audit logs. Data Synchronization is a server function providing clients that store their object data locally (e.g., personal finance managers [PFMs]) a means to update the state of their local data by requesting and comparing data from the server. This allows the client to learn about data resulting from actions that occurred at the server but are unknown to the client. For example, a user may have multiple PFM clients or employ other channel devices, such as telephones or web browsers, to submit requests to the server that changes the state of their business object data.
18
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification The IFX audit and synchronization messages are similar in that their responses contain a list of add, modify or delete records. As described above, the difference between audit and synchronize is in their intended use, which is manifested in their message requests as differences in the selection criteria. The sync messages are specifically tailored for PFM-like clients (i.e., clients that keep local state). The only selection criterion for the synchronization requests is the <Token>, which, by standard convention, is the value that determines the starting point for the synchronization. The server assigns the <Token> value, except when the client sets the token to zero to request the first synchronization or to request a refresh. In the synchronization response, the server must return an updated <NewToken> that the client should save for use in its next synchronization request. A more detailed description of the token is provided in Section 3.1.7. Audit messages are used (typically by CSRs) to trace the sequence of messages that users may have issued during a certain timeframe that affected the state of their objects. The audit requests contain optional selection criteria specifically defined for flexible and effective tracing of user message activity. For example, a CSR may want to resolve a payment dispute, by verifying that a change to a scheduled payment had been made prior to the payment being processed. Via the payment audit message, the CSR can request from the server all modifications made to a scheduled payment that occurred before it was processed. As in the case of user or CSR initiated actions (i.e., adds, mods or deletes), server-initiated actions for spawning instances from recurring models should also create and log audit records (i.e., adds) for these instances. In addition, whenever the server spawns a skipped instance, it should create and log an add audit record for the skipped instance, and must create and log a mod audit record for the model to account for the skip count adjustment made to the model. The mod audit record for the model is required because the user randomly may initiate the skip function any time after the model has been created. However, normal model status changes (e.g., number of remaining instances) do not require any model mod audit records, since these changes are predictable from the definition of the model.
2.4.3.5.1 Audit Message

The IFX audit message has a name structure of <xxxAudRq>/<xxxAudRs>. Audit in the IFX Specification refers to those messages that allow clients to receive specific message responses that change the state of an object, or class of objects, stored on the server since some past point in time. This past point in time is either identified by customer-specified audit selection criteria, including a DateTime range. Clients initiate audits to find out what messages were executed that caused the server to get to the current state. Clients initiate inquiry messages to view the current state of an object, or class of objects. Thin (stateless) clients also use audit messages to allow a customer or CSR to receive a change history of an object, such as a payment, typically to assist in problem resolution. The server should return as many state changes as are practical in response to an audit request. The specific type of object determines state changes. Most objects have a clear life cycle, from creation to deletion. Each status change must be reported using the appropriate add, modify, delete/cancel message response. The life cycle of some objects, e.g. a payment, is more complex. Information about a payment may change after it moves from a pending state to a processed state. The state change from pending to processed, and any subsequent changes must be included in the Audit response as modification response messages. Audit must contain all messages where the <Severity> within <Status> is Info or Warn. Audit may contain messages where the <Severity> is Error, at server discretion.
2.4.3.5.2 Synchronization Message

The IFX synchronization message has a name structure of <xxxSyncRq>/<xxxSyncRs>. Synchronization in the IFX Specification refers to those messages that allow clients to receive specific message responses that change the state of an object, or class of objects, stored on the server since some past point in time. This past point in time is identified by a server-assigned token. The server-assigned token is only meaningful to the server that assigned it.
Version 1.7
April 2005
19
Interactive Financial Exchange Business Message Specification Thick (stateful) clients send synchronization requests to find out what messages were executed that caused the server to get to the current state, so as to synchronize their local data with the server (system of record). Clients send inquiry requests to view the current state of an object, or class of objects. The server should return state changes using the same rules as Audit. However, at server discretion, multiple messages in a Sync may be collapsed into a single message. The resultant collapsed message must provide information sufficient to bring the client up to date. For example, if an object has been modified several times, then deleted, it is sufficient for the server to return only the <xxxDelRs> response in a Sync. The Sync response includes a playback of messages for a single customer. In it, the messages that affect a specific object must be returned in the order that that server processed then, i.e. ascending by <EffDt>. Examples of objects that the Sync refers to are a payment, in the case of <PmtSyncRq>. A client that maintains local data, sometimes referred to as thick or stateful client, should apply the changes in the order received to synchronize its local data with that maintained by the server (system of record). The server may, at server discretion, not maintain sufficient history to reliably update the client to be consistent with the current data at the server. The server must detect this condition by checking the <Token> supplied by the client in the Sync request versus the oldest <Token> maintained by the server. When the <Token> supplied by the client is older than the history maintained by the server, the server must return <Status> with <Severity>Error. The server must not return any message records within the response. The typical client error recovery should be to issue an inquiry message to receive the current status of the object class, e.g. payments, intrabank transfers, etc.; and use it to synchronize its local database.
2.4.3.6 Advise Message

The IFX advise message set has a name structure of <xxxAdviseRq>/<xxxAdviseRs>. Advise in the IFX specification refers to those messages that allow an entity to advise another entity of an object or a property of an object. The Advise message set does not imply any action to take such as add, or update. It is up to the receiving entity to decided what action to take based on the contents of the Advise message. The <xxxAdviseRq> message contains the object record information or object id and property. The <xxxAdviseRs> messages allow a status to be returned acknowledging receipt of the request. A likely scenario for this message type is an entity, who has the ability to receive <xxxAdviseRq> messages, wishes to be advised on the status of an object, e.g. a payment previously added. This entity is interested in being updated as the payment goes through its life cycle from pending to processed, and any other events related to the payment. In this scenario, as the payment status gets updated, a <PmtStatusAdviseRq> would be sent to advise the entity of the payment status change. Advise messages may also be used to notify an interested party of an object that was created or modified on behalf of the party. This use is intended to support business relationships where one party has the legal authority to stand in for or operate on behalf of the other party. In this case the business relationship dictates the processing that the receiving party must perform on receipt of the Advise message. In this context the Advise message is similar to an Add except that the receiver is expected to accept the message. Unlike the Add, the Advise message does not imply the transfer of the owner of record. The sender continues to be the owner of record of the object. Although the Advise message usually implies the existence of an IFX object (i.e., the Add method succeeded) there are situations where the Advise message must be used to notify interested parties that a method failed. This is particularly true of attempts to create or modify objects that represent financial transactions. In this case the status aggregate in the object status segment (i.e., DebitStatus) must indicate the error condition that prevented the method from succeeding. This along with the object status code should provide the information required by the receiver to determine the current state of the object.
2.4.3.7 Reversal Message

The Reversal IFX message has a name structure of <xxxRevRq>/<xxxRevRs>. It is used to reverse the effect of a message. This may be on an existing instance of an object xxx (such as reversing an existing debit using <DebitRevRq>) or a message that is not based on any object (such as reversing a balance inquiry using <BalRevRq>). This is a message based reversal that is used when the original message was not based on an object (such as a BalInqRq) or the effect of the original message on its object is unknown by the application generating the reversal (such as reversing a <DebitAddRq> when the <DebitAddRs> has not been received and
20
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification its status is unknown). The Reversal message should be used when the object identifier or the state of the object is not known. The Reversal message can be useful in situations when an IFX client experiences unusual delays in receiving IFX responses, or for situations where the Customer who initiated a transaction cancels or walks-away from an ATM/POS terminal before their transaction completed. In general, the Reversal message provides the capability to "undo" a previous request. For example, performing a reversal on a modify request would place that object back to the state it was in prior to the modify. Unlike the use of a Delete or Cancel message, if the IFX client uses a Reversal message not only would the prior request be reversed but also any implications related to back-end processes or fees would also be reversed. If a DebitAddRq was sent and is successful and a DebitRevRq was sent, the system would be put back to the logical state before the object was added. For a client to be able to send a reversal message request, it must be capable of saving or recreating the original request message that is being reversed. Also, a reversal message cannot be reversed. A request to reverse a message is not guaranteed to be successful. The reversal of the last operation on an object (O-1) is most likely to be successful. The reversal of an operation prior to the most recent one on an object (O2, O-3, etc.) is not as likely to be successful. (Example 1 If an object add was followed by an object modify, it is likely an object modify reversal will cause the object to be back to the original object add state. Example 2 If an object add was followed by an object modify #1 then an object modify #2, an object modify #1 reversal would not likely be successful however an object modify #2 reversal would have a good chance of being successful.).
2.4.4Service
A Service is a collection of related messages. Service wrappers are aggregates containing one or more IFX messages of the same service. Except for Signon and Signoff, all IFX messages have a service associated with them, and must be contained in a service wrapper. <xxxSvcRq> is used in requests, where xxx is the name of the service (e.g., Pay, Bank, Base). <xxxSvcRs> is used in corresponding responses. Within a service wrapper is an optional <SPName> element. The client must provide this value in cases where the destination service provider is ambiguous. One example of such a scenario is where there are multiple service providers for a given service, supporting the same messages. The service response wrapper also contains an optional <Status>. If the associated service provider returns an error to the CSP, or the CSP is unable to forward the messages to the associated service provider, the <Status> in the service response wrapper is used to communicate this failure to the client. A service wrapper for a particular service may repeat. One possible use for this is a case where one SP supports different messages than another. In such a situation, the client may use one SP for some messages, and another SP for others. This also makes it possible for a single SP to route internally using the service wrapper, simply by giving each destination a different <SPName> in the Service Profile.
Version 1.7
April 2005
21
2.4.4.1 Request <xxxSvcRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 UUID
Usage
Required Optional
Description
Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. For more information, see section 3.2.12.1.
<SPName>
Identifier
Optional
Service provider name. May be provided by the client to clearly identify which service provider is the intended destination for this collection of messages. It is required in instances where the destination would otherwise be ambiguous. A collection of various requests associated with the service named in the service wrapper.
<xxxRq>
Message
Optional Repeating
2.4.4.2 Response <xxxSvcRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID
Usage
Optional
Description
Response status.
<RqUID> <MsgRqHdr>
Required Echoed Optional Echoed Optional
Request Identifier. Message Request Header aggregate.
<MsgRsHdr>
Message Response Header aggregate.
<AsyncRqUID>
Optional Echoed
<SPName>
Identifier
Optional Echoed
Service provider name. May be provided by the client to clearly identify which service provider is the intended destination for this collection of messages. It is required in instances where the destination would otherwise be ambiguous. A collection of various responses associated with the service named in the service wrapper.
<xxxRs>
Message
Optional Repeating
2.4.5Document
An IFX Document is a collection of services and messages sent as a single unit between client and server. Note: both the request document and the response document share the <IFX> tag name.
2.4.5.1 Request <IFX>

An IFX request document must contain at least a Signon request.
22
April 2005
Version 1.7
Tag
<SignonRq> <xxxSvcRq> <SignoffRq>
Type
Message Service Message
Usage
Required Optional Repeating Optional
Description
Signon Request Message. Service Request Wrapper. Signoff Request Message.
2.4.5.2 Response <IFX>

An IFX response document varies, depending on the validity of the associated IFX request document.
Tag
<Status>
Type
Aggregate see section 3.2.12.1 Message
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). If this aggregate is absent, <StatusCode> defaults to 0 (zero). Signon Response Message. Must be provided in cases where the IFX request document was valid. Service Response Wrapper. Must be provided for each <xxxSvcRq> provided in the request document.
<SignonRs>
Optional but see Description Optional Repeating but see Description Optional but see Description
<xxxSvcRs>
Service
<SignoffRs>
Message
Signoff Response Message. Must be provided if <SignoffRq> was provided in the request document.
2.4.6Order
IFX has the following rules related to order: Within an IFX document, the signon message must come before any service wrapper or signoff message. Within an IFX document, the signon message must be processed before any service wrappers or the signoff message. Within an IFX document, the order of service wrappers is not defined. Within an IFX document, the processing order of service wrappers is not defined.
Within an IFX document, the signoff message must come after the signon message and any service wrappers. Within an IFX document and if present, the signoff message must be processed after the signon message and after any service wrappers. Within a service wrapper, the order of messages is not defined. Within a service wrapper, the processing order of the messages is sequential based on the message order submitted by the requestor. Within a message, the business message specifiction defines the element and aggregate order for that message.
2.5Naming Convention
Naming in the IFX Specification follows a convention based on a small set of rules and a set of standard abbreviations. These rules and abbreviations apply to names of elements, aggregates, messages, messages, and services.
2.5.1Rules for Naming in the IFX Specification

Names should be designed for clarity of semantic meaning.
Version 1.7
April 2005
23
Names are case-sensitive. Within an aggregate, the sequence of fields matters. Names must follow standard abbreviations when possible.
The letters Rq and Rs must only appear as the final two letters of a name if it is a Request message, Response message, Request Service Wrapper, or Response Service Wrapper. Message names must follow Class, Object, Property, Method, Direction order; e.g., <PmtAddRq>. All custom values for Open Enum elements must be based on the established naming conventions and must use a name to designate the organization that developed the extension. All custom tags must have a prefix and a suffix. The delimiter between the prefix and the suffix may be specific to the implementation. For example all extensions developed by ABC Corporation must use the syntax <com.abccorp:Something> when : is specified as the delimiter. The governance process will support the registration of prefixes.
2.6International Support
2.6.1Country Codes
All representations of countries in the IFX Specification are the three-character codes for countries that are defined in ISO-3166. These country codes are used in this specification for the following purposes: In postal addresses, With language codes to specify a dialect of a language used in multiple countries, and
To identify country-specific tags that may be used to pass and store data relevant only in a single country.
2.6.2Character Sets
The IFX Specification defines two data types to represent character data. The most general data type used for the representation of most character data is called Character. The IFX Specification places no restrictions on the character sets used to represent elements based on the Character data type. The Character data type is intended to allow data in either single or multi-byte character sets to be passed between client and server and stored on the server to facilitate implementation in the broadest possible number of countries. It is expected, but not required, that multi-byte implementations be based on the UTF representation of Unicode. The other data type used for representation of character data is called Narrow Character. This data type is used in the IFX Specification to restrict some elements to single-byte characters so that implementation may be simplified. These elements tend to be related to system functions and should not interfere with the ability of an implementation to support multiple-byte character sets for most character data.
2.6.3Reporting Foreign Exchange Transactions

Messages that allow a customer to execute or schedule a financial transaction allow the customer to optionally specify the currency for the message. The SP may refuse to honor the message in the requested currency. The client may use the Deposit Account Transaction Inquiry or similar messages for other services to retrieve financial transaction detail. The detail available for a message that was executed with an amount in a foreign currency must include the original financial transaction amount in the requested currency with the actual exchange rate applied against the customers account for the financial transaction and the rate indicator. The converted amount in the account currency is also explicitly provided with the financial transaction detail. The <EU.Cur> element in the Signon message supports the new laws governing the use of the euro in Europe. This allows the client to specify whether they want to see financial amounts in euros or the currency of the local country.
24
April 2005
Version 1.7
2.6.4Languages and Dialects

Whenever languages are specified in the IFX Specification, they use the RFC-1766 standard, which uses the ISO-639 international standard for two-letter language codes. Languages also include an optional ISO-3166 two-letter country code to account for differences in dialect when the same language is used in multiple countries. Note: this is different from the use of country codes elsewhere in the specification, where threeletter codes are used. Two-letter codes are used here because RFC-1766 did not have a provision for a standard use of three-letter codes for language definitions. The customer may, in the <SignonRq>, specify a preferred language and dialect from the list provided by the server in <BaseSvcProfInfo>. If the client has not yet obtained a list of languages from the server, the customer may choose any language, but the server may default to a particular language if the preferred language is not among those supported.
2.6.5Times and Time Zones

Whenever times are specified in the IFX Specification, they are specified with an offset from Coordinated Universal Time (UTC). This specificity allows clients and servers in different time zones to communicate without ambiguity.
2.6.6Country-Specific Tags
To accommodate differences in financial regulations and practices in different countries, the IFX Specification allows extensions to be created that allow additional information to be passed between clients and servers that implement messages under an individual countrys regulations. Elements, Aggregates, or Messages that are added to the IFX Specification to support the needs of a single country should use custom tag names with a prefix that is the ISO-3166 three-letter country code. All three-letter tag name prefixes in the IFX Specification are reserved for country-specific tag names. In addition, the two-character prefix EU has been reserved for use by the European Union.
2.7Versioning and Specification Evolution

The IFX Specification has been designed to support two separate but related mechanisms for evolution. The specification evolves formally through an open governance process that provides a mechanism for features that are widely useful to be incorporated into the core specification, which is defined in this document, and the associated IFX implementation specifications. In addition, individual Financial Institutions or Service Providers may design their own custom extensions to the current version of the specification to quickly add needed functionality. Through this process, new custom elements or custom aggregates may be added to existing messages, custom messages and custom profile options may be added to existing services, and entirely new custom services may be developed.
2.7.1Extension and Customization

Since all tag names in the IFX Specification follow the same naming conventions, it is relatively easy for a Financial Institution or Service Provider to design customized extensions. All custom tag names and custom values for Open Enum elements must be based on the established naming conventions and must use a name to designate the organization that developed the extension. All custom names and values have a prefix and a suffix. The delimiter between the prefix and the suffix may be specific to the implementation. For example, all extensions developed by ABC Corporation must use the syntax com.abccorp:Something, where : is specified as the delimiter. To avoid clashes, all organizations using custom tags must either register their prefix with IFX Forum or follow the convention described below to name their prefixes:
Version 1.7
April 2005
25
Interactive Financial Exchange Business Message Specification Use the organization's fully qualified Internet domain name, reverse the order, with the top level domain first, e.g. org.ifxforum for IFX Forum (with a domain name of ifxforum.org) If the organization wants to have multiple prefixes for different services or different versions of customization, it may attach a sub-domain name, e.g. org.ifxforum.banking or org.ifxforum.v2 The prefix must consist only of lower-case alphanumeric characters or dash ('-') Note: the maximum length of a custom value is 80 characters. The governance process will support the registration of prefixes. All ISO country-specific values are reserved and assigned country specific prefixes. Therefore, it is required to reserve three-letter prefixes for such use. Unreserved values for private tags (i.e. ones that may be registered with the IFX Forum) are four or more positions in length.
2.7.2Mandatory and Optional Elements

The IFX Specification documentation conveys a number of rules for usage of elements and aggregates. This section provides a general taxonomy of rules for mandatory and optional elements and aggregates. For documentation conventions, see Section 2.2. These rules may be categorized as follows: Required messages within a serviceEach chapter that defines messages contains a table (normally section x.2, where x is the chapter number) that includes a column labeled Req. Yes in this column indicates that a server supporting the service that the chapter is part of must support this message if it supports the service. The server indicates support for optional messages (i.e., those with blank in the Req. column) using <MsgSupt> in the section of the Service Profile that corresponds to that service. (The Service Profile section for each service is typically documented at the end of each chapter.) Message Level Required Element or AggregateWithin each message, the elements and aggregates that appear at the highest level (as opposed to within nested aggregates) and that are required are marked. The meaning of required is slightly different for request and response messages. o In a request message, an element or aggregate that is marked as required must be included. o In a response message, an element or aggregate that is marked as required must be included in every successful response, but need not be included in failed responses. In addition, whether the message succeeds or fails, every response must contain a Request Unique ID <RqUID>, a Response Status aggregate <Status>, and a Customer Identification aggregate <CustId> if it was provided in the request. Elements and Aggregates Within a Higher Level AggregateWithin an aggregate, elements and aggregates are marked in the same way that they are at the message level. When an element or aggregate is marked required within the context of a higher-level aggregate that is optional, there is an implied required if the aggregate is included. Or and Exclusive Or ConditionsThere are places in the specification where one or more elements or aggregates from a list must be included. Where exactly one item must be included it is marked as an Exclusive Or or XOR condition. Where one or more items must be included it is marked as an OR condition. Required by Service ProfileSome but not all Financial Institutions or Service Providers may require many elements and aggregates. Each FI or SP must indicate to the client through the Service Profile for the service whether or not these elements and aggregates are required. Required by Biller DirectorySome but not all Billers may require some elements and aggregates. Each Biller must indicate to the client through their entry in the Biller Directory whether or not these elements and aggregates are required. Note that the Biller Service Provider (BSP) may actually create/maintain the directory entry for each Biller that it supports.
26
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification Complex Usage RulesSome elements and aggregates have usage rules that are more complex than the conditions described above. Where this is the case, these conditions are described in text in the Description column. Definition of optionalA client or server may include optional fields within a message. There is no requirement that the receiver process optional fields. In order to maintain upward compatibility, the receiver of a message must ignore tags that it does not support. Note that it is not unusual for an optional field to be required based on the context. This condition is documented by the words but see Description in the Usage column.
Version 1.7
April 2005
27
3 Common Elements and Aggregates

3.1Common Elements
A number of elements are used throughout the IFX Specification.
3.1.1Edit Masks
Edit masks are elements that provide a way for a user interface to determine and check what type or actual value must be in each character position of a particular related element. For example, edit mask is used in <AcctMask> in the <BillerAcctIdInfo> Aggregate to provide a way to determine whether the number entered by the user for <BillingAcct> in <PresAcctId> is a valid billing account number for that biller. Edit mask is used by <SecretMask> in <SecretPrompt> to check the characters input by the user for <Secret>. Multiple edit masks may exist for the customer accounts at each biller, as identified by a unique <BillerNum>. In this case, the client may apply one rule at a time until one succeeds. If all edit masks fail for the account number given, the client should consider the account number as invalid. Clients are not required to support this function; instead, they may rely on the presentment service provider to do it for them. Clients may wish to support this checking for performance reasons. The table below identifies the characters that may be in the mask and what they mean.
Mask Position Contains
a b c i n X A through Z 0 through 9 Special Characters/ * $ # ,@
Position in Account Number Must Contain

Alpha characters A through Z Space (blank) Alphanumeric characters, no space Ignore Digits 0 through 9 Alphanumeric characters, space allowed That exact character That exact number The specified character
Explanation
A lowercase a means an alpha character A through Z must appear in that position. A space must appear in that position. An alpha character, A through Z or a through z, or a number, 0 through 9, must appear in that position. Ignore this position. Do not check for any characters presence or absence. A numeric character from 0 through 9 must appear in that position An alpha character, A through Z or a through z, a number, 0 through 9, or a space must appear in that position. An upper case letter means that that alpha character must appear in that position. A number means that that specific number must appear in that position. A special character means that that exact special character must appear in that position in the account number.
Note: <AcctMask> is only 32 characters long, while the <SecretMask> is 80 characters long. The length of the edit mask element matches the length of the element being masked.
3.1.1.1 Account Mask <AcctMask>

Tag
<AcctMask>
Type
NC-32
Usage
Description
Account Mask. String describing the valid values to be checked against values input by the user.
Version 1.7
April 2005
3.1.1.2 Secret Mask <SecretMask>

Tag
<SecretMask>
Type
NC-80
Usage
Description
Secret Mask. String describing the valid values to be checked against values input by the user.
3.1.2Customer Identifiers
The IFX Specification uses two different identifiers for customers. The first, Customer Login ID <CustLoginId>, is a user-friendly name or number (such as tax id) that is used with a password for customer authentication. The second identifier, Customer Permanent ID <CustPermId>, is a unique permanent id used by the SP as a database key and is not typically known by the customer. The <CustPermId> is used by the CSP to identify the Customer in messages to other service providers. When the <CustPermId> is used outside of the entity that assigned it, further qualification may be required. See Section 3.2.3.1 for more information. Clients do not typically need to use <CustPermId>. When <CustPermId> is used, it is returned as part of the Signon Response and added to each subsequent message by an intermediate server prior to the message being delivered to the SP. Both IDs may appear together in the <CustId> aggregate (See Section 3.2.3.1).
3.1.2.1 Customer Login ID <CustLoginId>

Tag
<CustLoginId>
Type
NC-32
Usage
Description
Customer Login ID. Used as a user-friendly name for the customer for authentication purposes. Some implementations may allow a user to change his or her Login ID.
3.1.2.2 Customer Permanent ID <CustPermId>

Tag
<CustPermId>
Type
NC-32
Usage
Description
Customer Permanent ID. Used as a database key to uniquely identify an FI or CSP customer. Cannot be changed by the customer.
3.1.3Request Identifier <RqUID>

A client uses <RqUID> to uniquely identify a request message. It is a universally unique ID (UUID) that is generated according to an algorithm specified by the Open Software Foundation Distributed Computing Environment (OSF/DCE) standards to produce a 36-character hexadecimal encoding of a 128-bit number. A Request Identifier <RqUID> is included in request messages. A server must echo the received <RqUID> in the response message it generates. The server must store the <RqUID> for as long as the server stores the audit/sync log. The client may then correlate the asynchronous response with the request when the response is not immediate.
Tag
<RqUID>
Type
UUID
Usage
Description
Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests.
3.1.4Service Provider Reference Identifiers

Customer Service Provider Reference Identifier <CSPRefId> and Service Provider Reference Identifier <SPRefId> are typically optional elements that allow both the CSP and SP to return message reference numbers for a message. These identifiers provide permanent reference for the message and may be used by the customer in reporting problems to Customer Service.
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification The reference identifiers may be different for different methods applied to a given object. For example, the reference identifier in the <PmtAddRs> may be different from the reference identifier in a subsequent <PmtModRs> applied to the same payment. Therefore, it is not safe to assume that the reference identifiers may be used to uniquely identify a particular instance of an object (such as a payment).
3.1.4.1 Customer Service Provider Reference Identifier <CSPRefId>

Tag
<CSPRefId>
Type
Identifier
Usage
Description
Customer Service Provider Reference Identifier.
3.1.4.2 Service Provider Reference Identifier <SPRefId>

Tag
<SPRefId>
Type
Identifier
Usage
Description
Service Provider Reference Identifier.
3.1.5Service Provider Name <SPName>

The Service Provider Name element is a globally unique identifier for a service provider, e.g., the domain name of the SP. <SPName> is used for 2 distinct purposes. To specify the destination of a message, when multiple service providers provide the same service, e.g. a CSP interacts with multiple BSPs to implement Bill Presentment. To qualify the id of an object that it owns, e.g. <BillerId>, <PmtId>, <XferId>. There are cases where different <SPName>s may be used in the same message, e.g. the BSPs <SPName> is used to qualify the <BillerId> in a message that is sent to the CPP. To ensure uniqueness, <SPName> must be an Internet domain name registered to the SP. For example, the Bankers Roundtable would use org.bankersround as the value for <SPName>.
Tag
<SPName>
Type
Identifier
Usage
Description
Service Provider Name. To ensure uniqueness, a <SPName> should be an Internet domain name.
3.1.6Organization <Org>
The Organization <Org> element is used where information must be qualified by the organization that assigned it. For example, a tax authority assigns the tax type in the <BankAcctTaxInqRq>, so <Org> is used to identify the state or country tax authority. In general, <Org> is used to make identifiers globally unique in cases where there is no existing real-world globally unique identifier. An organization may register a globally unique value of <Org> through the IFX Governance Process to avoid conflicts with other organizations with similar names. The value of <Org>, like <SPName>, may also be an Internet domain name registered to the Organization defining that name space.
Tag
<Org>
Type
Identifier
Usage
Description
Organization. Organization defining this name space.
3.1.7Token <Token>
The IFX Specification allows clients to perform synchronization of data with servers using a server-assigned <Token>. This synchronization is performed using synchronization messages, where the client inserts a <Token> it has previously received from the server as an indication of the point in history from which the synchronization should occur. The server must return all messages that are relevant to the type of object being synchronized and have occurred since the <Token> was originally sent to the client. A client may also include <Token>0 in a Sync request, which results in the server returning all known messages of the relevant type.
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification The assignor determines the scope of uniqueness. The scope may either be globally across all customers known to the assignor or specific to a customer. The server must echo the <Token> in the response and also generate and return a new token <NewToken>, which may be used by the client in the future to specify the current point in history. See Section 2.4.3.5.2 for information regarding synchronization message definition.
Tag
<Token>
Type
Identifier
Usage
Description
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first-time requests.
3.1.8Reversal Reason Code <RevReasonCode>

Tag
<RevReasonCode>
Type
Open Enum
Usage
Description
Reversal reason code. The reason why the client is requesting a reversal. Defined values: CustomerCancellation, UnspecifiedNoActionTaken, SuspectedMalfunction, FormatErrorNoActionTaken, CompletedPartially, OriginalAmountIncorrect, ResponseReceivedTooLate, CardAcceptorDeviceUnableToCompleteTransaction, DepositOutOfBalance, NoCheckInEnvelope, PaymentOutOfBalance, DepositOutOfBalanceAppliedContents, PaymentOutOfBalance-AppliedContents, UnableToDeliverMessageToPointOfService, SuspectedMalfunction-CardRetained, SuspectedMalfunctionCardReturned, SuspectedMalfunction-Track3NotUpdated, SuspectedMalfunction-NoCashDispensed, TimedOutAtTakingMoney-NoCashDispensed, TimedOutAtTakingCard-CardRetainedAndNoCashDispensed, InvalidResponse-NoActionTaken, TimeoutWaitingForResponse (reference ISO 8583:1993 Annex A.11)
3.2Common Aggregates
3.2.1Message Headers
3.2.1.1 Message Request Header <MsgRqHdr>
The message header request aggregate contains common information for all request messages.
Tag
<EMVRqData>
Type
Aggregate see section 3.2.2.1 Aggregate see section 3.2.18
Usage
Optional
Description
EMV Request Data Aggregate.
<NetworkTrnInfo>
Optional
Network Transaction Information. Identification and location of the terminal from which the message originates.
April 2005
Version 1.7
Tag
<EMVRqData>
Type
Aggregate see section 3.2.2.1 Identifier
Usage
Optional
Description
EMV Request Data Aggregate.
<ClientTerminalSeqId>
Optional
Client Terminal Sequence Identifier. A sequence identifier generated by the client terminal in a Branch/CallCenter/ Teller environment. Note: Required if transaction is initiated by a Branch/Call Center/Teller application.
<PointOfServiceData>
Aggregate see section 3.2.23 Aggregate see section 3.2.1.3
Optional
The Point of Service Data. This aggregate contains information about the environment in which this message originated. Message Authentication Code (MAC) aggregate, used by the receiver of this message to verify the senders identity and authenticate the message contents.
<MsgAuthCode>
Optional
3.2.1.2 Message Response Header <MsgRsHdr>

The message header response aggregate contains common information for all response messages.
Tag
<EMVRsData>
Type
Usage
Optional
Description
EMV Response Data Aggregate.
<ServerTerminalSeqId>
Optional
Server Terminal Sequence Identifier. A terminal sequence identifier generated by the server (CSP) in an ATM or POS environment. Message Authentication Code (MAC) aggregate, used by the receiver of this message to verify the senders identity and authenticate the message contents.
<MsgAuthCode>
Aggregate see section 3.2.1.3
Optional
3.2.1.3 Message Authentication Code Aggregate <MsgAuthCode>

Tag
<MacValue>
Type
HexBin-
Usage
Required
Description
The Message Authentication Code value. Calculated using an encryption key shared by both endpoints according to a previously agreed algorithm such as ANSI X9.9/FIPS113 or ANSI X9.71/FIPS198. The Message Authentication Variant value. This field is used to ensure that MAC values will not be repeatable. When used, this value will be generated randomly before the MacValue is calculated. Mac variants cannot be retransmitted. The Security Object ID of the encryption key used to calculate the MAC Value. Used in lieu of check digits to help identify key synchronization errors.*
<MacVariant>
HexBin-8
Optional
<SecObjId>
Identifier
Optional
3.2.2Europay, MasterCard, Visa (EMV) Data

Europay, MasterCard, and Visa (EMV) have published jointly-developed specifications on how smart cards can be used for improved fraud reduction for transactions that the service providers choose to be more secure. This
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification joint effort is handled by mutually agreed upon smart card standards organization, called EMV Co. EMV specifications allow the clients and servers to utilize the Integrated Circuit Card (ICC) technology, which is also commonly called smart card, for better fraud risk management. The EMV specifications define a set of requirements that ensure interoperability for credit and debit payment applications between smart cards and terminals on a global basis, regardless of where the card is used. This version is compatible with the EMV standard up to version 4.1. For more information about the EMV, refer to their website at http://www.emvco.com.
3.2.2.1 EMV Request Data Aggregate <EMVRqData>

This aggregate contains the EMV request data that is sent by the device, which supports EMV functionality, to the acquirer host in an EMV transaction authorization request message. The current EMV specification contains many more elements (for EMV supported transaction requests) than those specified here. The EMV data elements that are specified here are the common sub-set of the current EMV implementation by the device vendors who have chosen to support the EMV functionality. The usage of all EMV data elements that are specified here is intentionally specified as Optional, although some data elements are required in order to verify the EMV support for a transaction request (and the usage column for these elements have the but see Description comments specified). The reasons for this is: The relationship between different device vendors and acquiring hosts might dictate different EMV data element requirements, and If a Required EMV data element is not present in a transaction request, then the acquiring host might want to fall-back on the alternate method of authorizing the transaction request. Therefore it is better that the decision to either proceed with the transaction request processing, using the alternate method of verification/authorization, or to decline the transaction request is left with the acquiring host.
Type
HexBin-16
Tag
<AppId>
Usage
Optional
Description
Application Identifier (AID). It is also referred to as the Application Definition File Name (ADF Name) and Dedicated File Name (DF Name) in the context of the applications supported by an Integrated Circuit Card (ICC). The data value contained by this element is in hexadecimal characters, e.g., Hex 4F value is specified in two characters as 4 & F. The AID consists of two parts: A Registered Application Provider Identifier (RID) of 5 bytes, unique to an application provider and assigned according to ISO/IEC 7816-5. An optional field assigned by the application provider of up to 11 bytes. This field is known as a Proprietary Application Identifier Extension (PIX) and may contain any 0-11 byte value specified by the provider. The meaning of this field is defined only for the specific RID and need not be unique across different RIDs.
April 2005
Version 1.7
Tag
<Trk2EquivData>
Type
HexBin-20
Usage
Optional
Description
Track 2 Equivalent Data. Indicates the Track 2 Data as read from the Integrated Circuit Card (ICC). The format of this data is according to ISO/IEC 7813 standards, excluding start sentinel, end sentinel, and LRC. It includes the following data elements: Primary account Number (PAN), a variable length numeric character string of up to 19 characters; Field Separator (hex D value); Expiration Date in YYMM format, a 4-character numeric string; Service Code, a 3-character string; Discretionary Data (define by individual payment systems), a variable length character string of up to 12 characters; and the last character is padded with hex. F, if needed to ensure whole bytes. The data associated with this element is not needed if the Track 2 data already contains this information elsewhere in the transaction message.
<AppPan>
HexBin-16
Optional
Application Primary Account Number (PAN). Indicates the valid cardholder account number, padded to the right with hex F values. The data value contained by this element is in hexadecimal characters. The data associated with this element is not needed if the <Trk2EquivData> already contains this information and is equivalent.
<AppPanSeq>
HexBin-1
Optional
Application PAN Sequence Number. Sometimes, also referred to as the Member Number. Identifies and differentiates cards with the same PAN (e.g., cards with the same PAN for different family members). The data value contained by this element is in hexadecimal characters. Cryptogram Information Data. It indicates the type of cryptogram returned (approved, online, or denied) by the card and the actions to be performed by the terminal (advice or not, reason for advice). The data value contained by this element is in hexadecimal characters. For exact values based on the bit positions (the data is in hex), refer to the EMV Integrated Circuit Card Specification for Payment Systems Version 4.1 (Book 3, table 12). Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<CryptoInfoData>
HexBin-1
<AuthRqCrypto>
HexBin-8
Authorization Request Cryptogram (ARQC). Cryptogram returned by the ICC in response to the GENERATE AC command. The data value contained by this element is in hexadecimal characters. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
Version 1.7
April 2005
Tag
<IssAppData>
Type
HexBin-32
Usage
Description
Issuer Application Data (IAD). Indicates the proprietary application data for transmission to the issuer in an online transaction. It also provides the data elements that the Issuer has elected to have in the authorization message. For example, derivation key index and algorithm version numbers. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<AppICProf>
HexBin-2
Application Interchange Profile (AIP). It contains the capabilities of the card to support specific functions in the application, as defined in the AIP table. The data value contained by this element is in hexadecimal characters. For exact values based on bit positions (the data is in hex), refer to the EMV EMV Integrated Circuit Card Specification for Payment Systems Version 4.1 (Book 3, table 37). Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<AppTrnCounter>
HexBin-4
Application Transaction Counter (ATC). A counter maintained by the application in the Integrated Circuit Card (ICC). It indicates sequential order of the transaction performed by the application. Incrementing of the ATC is managed by the ICC. The data value contained by this element is in hexadecimal characters. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<AuthAmt>
Currency Amount
Authorization Amount. It contains the transaction amount, excluding any adjustments, that needs to be authorized. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<SecAmt>
Currency Amount
Secondary Amount. It contains the secondary (or other) amount of the transaction. It contains any secondary amount that transaction might have. E.g., Cashback amount. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<TerminalCountryCode>
NC-3
Terminal Country Code. Indicates the country code of the merchant or terminal associated with the transaction. This is the ISO country code based on ISO-3166. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
April 2005
Version 1.7
Tag
<TerminalVrfyRslt>
Type
HexBin-5
Usage
Description
Terminal Verification Results (TVR). It defines the status of different functions as seen from the terminal. The data value contained by this element is in hexadecimal characters. For exact values based on the bit positions (the data is in hex), refer to the EMV Integrated Circuit Card Specification for Payment Systems Version 4.1 (Book 3, table 42). Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<CurCode>
NC-3
Currency Code. Indicates the currency code associated with the transaction amount. This is the ISO currency code based on ISO-4217. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<TrnDt>
Date
Transaction Date. Indicates the local date the transaction was authorized. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request. Transaction Type. Indicates the type (code) of the transaction, represented by the first two digits the ISO 8583 (1987) Processing Code. Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
<EMVTrnType>
NC-2
<UnpredictNum>
HexBin-4
Unpredictable Number. An unpredictable number, generated by the terminal, which may be used for input to the application cryptogram algorithm to ensure the unpredictability of data input to this calculation or for random transaction selection for terminal risk management. It contains the value to provide variability and uniqueness to the generation of the application cryptogram in order to reduce fraud risk. The data value contained by this element is in hexadecimal characters. An unpredictable number shall be generated in accordance with an individual payment systems specifications. One example of a method for generating the Unpredictable Number is performing an exclusive-OR operation on all the previous Authorization Request Cryptograms (ARQCs), Transaction Certificates (TCs), Application Authentication Cryptograms (AACs), and Application Authorization Referrals (AARs). Required if the online EMV support is needed for this transaction, and the user does not intend to fall back on the alternative method of authorizing the transaction request.
Version 1.7
April 2005
Tag
<TerminalCaps>
Type
HexBin-3
Usage
Optional
Description
Terminal Capabilities. Indicates the card data input, cardholder verification method (CVM), and security capabilities of the terminal. The data value contained by this element is in hexadecimal characters. Cardholder Verification Method (CVM) Results. Indicates the results of the last cardholder verification method (CVM) performed. The data value contained by this element is in hexadecimal characters. Transaction Status Information. Indicates the functions performed in a transaction. The data value contained by this element is in hexadecimal characters. Application Version Number. The version number of the application assigned by the payment system. Issuer Script Result. Contains the results of executing Issuer Scripts received in a previous EMVRsData aggregate. Required if the previous <EMVRsData> aggregate contained <IssScriptData>. Application Effective Date. Date from which the application may be used Application Expiry Date. Date after which the application expires Issuer Country Code. Indicates the country of the issuer according to ISO 3166 Issuer Action Code Default. Specifies the issuers conditions that cause a transaction to be rejected if it might have been approved online, but the terminal is unable to process the transaction online Issuer Action Code Denial. Specifies the issuers conditions that cause the denial of a transaction without attempt to go online. Issuer Action Code Online. Specifies the issuers conditions that cause a transaction to be transmitted online. Card Risk Management Data Object List 1. List of data objects (tag and length) passed to the ICC in the first GENERATE AC command. Card Risk Management Data Object List 2. List of data objects (tag and length) passed to the ICC in the second GENERATE AC command. Transaction Certificate Data Object List. List of data objects (tag and length) used by the terminal in generating the TC Hash Value. Transaction Certificate Hash Value. Result of a hash function specified in EMV Integrated Circuit Card Specification for Payment Systems Version 4.1 (Book 2, Annex B3.1). Processing Options Data Object List. Contains a list of terminal resident data objects (tags and lengths) used by the ICC in processing the GET PROCESSING OPTIONS command. Transaction Sequence Counter. Counter maintained by the terminal that is incremented by one for each transaction.
<CVMRslts>
HexBin-3
Optional
<TrnStatInfo>
HexBin-2
Optional
<AppVersionNum> <IssScriptResultData>
HexBin-2 Aggregate see section 3.2.2.6
Optional Optional Repeating
but see Description

Optional Optional Optional Optional XOR
<AppEffDt> <AppExpDt> <IssCountryCode> <IssActionCodeDefault>
Date Date NC-3 HexBin-5
<IssActionCodeDenial>
HexBin-5
Optional XOR Optional XOR Optional
<IssActionCodeOnline>
HexBin-5
<CDOL1>
HexBin-252
<CDOL2>
HexBin-252
Optional
<TDOL>
HexBin-252
Optional
<TCHash>
HexBin-20
Optional
<PDOL>
HexBin-252
Optional
<TrnSeqCntr>
NC-8
Optional
10
April 2005
Version 1.7
Tag
<IssDiscData> <TrnCategory> <CVMList>
Type
HexBin-222 NC-1 Aggregate see section 3.2.2.7
Usage
Optional Optional Optional
Description
File Control Information (FCI) Issuer Discretionary Data. Issuer discretionary part of the FCI. Transaction Category. Transaction Category Code as defined by Mastercard. List of Cardholder Verification Methods. Contains the list of rules for cardholder verification.
3.2.2.2 EMV Response Data Aggregate <EMVRsData>

This aggregate contains the EMV response data that is returned by the acquirer host to the device, which supports EMV functionality, in an EMV transaction authorization response message. The EMV data elements that are specified here are the common super set of the current EMV implementation by the device vendors who have chosen to support the EMV functionality.
Tag
<AuthRsCode>
Type
C-2
Usage
Required
Description
Authorization Response Code. A code that defines the disposition of an EMV response message. As a minimum, the codes reflecting the following responses should be defined in the response messages from the Issuer to the terminal: Online Approval, Online Decline, Referral (initiated by Issuer), and Capture Card. In addition, the terminal shall be able to generate (and transmit to the ICC) the codes reflecting the following new responses when transactions are not authorized online: Unable to go Online, Offline Approved; Unable to go Online, Offline Declined; Offline Approved; Offline Declined; Approval (after card-initiated referral); and Decline (after card-initiated referral). The codes are to be set by the individual payment systems. The terminal shall never modify the Authorization Response Code returned in the response message. The cards final decision is reflected in the Cryptogram Information Data and not in the authorization Response Code.
<AuthCode>
HexBin-6
Optional
Authorisation Code. Value generated by the authorisation authority for an approved transaction. Details are Issuer specific. Issuer Authentication Data. Contains the data sent to the ICC for online issuer authentication. If present, the value contained by this element is at least 16 characters long, and it contains the Application Response Cryptogram. The data value is in hexadecimal characters. Required if the online EMV support is needed for this transaction, and the original request contained the EMV support data (the user did not fall back on the alternative method of authorizing the transaction request).
<IssAuthData>
HexBin-32
<IssScriptData>
Optional
Issuer Script Data Aggregate. If omitted, the issuer does not intend to send any Script Data (commands) to the terminal for further passing on to the ICC (chip card).
Version 1.7
April 2005
11
3.2.2.3 Issuer Script Data Aggregate <IssScriptData>

The <IssScriptData> aggregate specifies the format for Issuer Script Commands for transmission to the card for processing by the card application. These commands are issued by the terminal, in the order specified in this aggregate, to the ICC (chip card) for processing. The issuer script commands include both types of commands that are issues by the terminal before (<IssPreScriptData>) and after (<IssPostScriptData>) issuing the final EMV GENERATE AC command.
Tag
<IssPreScriptData>
Type
Aggregate see section 3.2.2.4 Aggregate see section 3.2.2.5
Usage
Optional Repeating Optional Repeating
Description
Issuer Pre Script Data (commands issued by the terminal before the final EMV GENERATE AC command). Issuer Post Script Data (commands issued by the terminal after the final EMV GENERATE AC command).
<IssPostScriptData>
3.2.2.4 Issuer Script Data Aggregate <IssPreScriptData>

Tag
<IssScriptId>
Type
HexBin-4
Usage
Description
Issuer Script Identification. Uniquely identifies the pre script command. Required if the <IssPreScriptData> occurs more than once (multiple pre script commands are present). Issuer Script Command. Contains an Issuer Pre Script Command to be processed by the ICC card at the terminal. If multiple Issuer Pre Script Commands are present here, then the terminal must process them in the sequence they are listed here.
<IssScriptCmd>
HexBin-124
Required Repeating
3.2.2.5 Issuer Script Data Aggregate <IssPostScriptData>

Tag
<IssScriptId>
Type
HexBin-4
Usage
Description
Issuer Script Identification. Uniquely identifies the post script command. Required if the <IssPostScriptData> occurs more than once (multiple post script commands are present). Issuer Script Command. Contains an Issuer Post Script Command to be processed by the ICC card at the terminal. If multiple Issuer Post Script Commands are present here, then the terminal must process them in the sequence they are listed here.
<IssScriptCmd>
HexBin-124
Required Repeating
3.2.2.6 Issuer Script Result Data Aggregate <IssScriptResultData>

Tag
<IssScriptResult>
Type
HexBin-1
Usage
Required
Description Issuer Script Result. The result of executing the Issuer Script. In the event of an error, this includes the sequence number of the failed Script Command in the order it appears in the issuer script.
Valid values are defined in EMV Integrated Circuit Card Specification for Payment Systems Version 4.1 (Book 4, table 33).
12
April 2005
Version 1.7
Tag
<IssScriptId>
Type
HexBin-4
Usage
Description
Issuer Script Identification. Uniquely identifies the script command for which this is the response. Required if multiple scripts send to the terminal were identified by <IssScriptId>s.
3.2.2.7 Cardholder Verification Methods List Aggregate <CVMList>

Tag
<AmtX> <AmtY> <CVMRule>
Type
Currency Amount Currency Amount HexBin-2
Usage
Required Required Required Repeating
Description
Amount referred to as Amount X in the CVM Rule definition. Amount referred to as Amount Y in the CVM Rule definition. Cardholder Verification Rule. For exact values based on the bit positions (the data is in hex), refer to the EMV Integrated Circuit Card Specification for Payment Systems Version 4.1 (Book 3, tables 39 and 40).
3.2.2.8 Signon Integrated Chip Card Aggregate <SignonICC>

Tag
<AppPan>
Type
HexBin-16
Usage
Required
Description
Application Primary Account Number (PAN). Indicates the valid cardholder account number, padded to the right with hex F values. The data value contained by this element is in hexadecimal characters. Application PAN Sequence Number. Sometimes, also referred to as the Member Number. Identifies and differentiates cards with the same PAN (e.g., cards with the same PAN for different family members). The data value contained by this element is in hexadecimal characters. Application Identifier (AID). It is also referred to as the Application Definition File Name (ADF Name) and Dedicated File Name (DF Name) in the context of the applications supported by an Integrated Circuit Card (ICC). The data value contained by this element is in hexadecimal characters, e.g., Hex 4F value is specified in two characters as 4 & F. The AID consists of two parts: A Registered Application Provider Identifier (RID) of 5 bytes, unique to an application provider and assigned according to ISO/IEC 7816-5. An optional field assigned by the application provider of up to 11 bytes. This field is known as a Proprietary Application Identifier Extension (PIX) and may contain any 0-11 byte value specified by the provider. The meaning of this field is defined only for the specific RID and need not be unique across different RIDs.
<AppPanSeq>
HexBin-1
Optional
<AppId>
HexBin-16
Optional
Version 1.7
April 2005
13
Tag
<PINBlock>
Type
NC-32
Usage
Description
PIN pad data. The Pin pad data is required for on-line transactions, where the Pin is verified by the server. For off-line Pin verification, where the IC Card verifies the PIN and authorizes the transaction, the Pin pad data is optional. Note that in both cases additional transaction and security relate data is contained in the <EMVRqData> element of the <MsgRqHdr>. Session Key Requested Indicator. True indicates that the client is requesting a Session Key in the response. False or absent indicates that the client is not requesting a Session Key in the response.
<GenSessKey>
Boolean
Optional
3.2.3Customer Data
3.2.3.1 Customer Identification Aggregate <CustId>
The <CustId> aggregate is used to uniquely identify the customer who submits a request. Its use is optional when the customer ID may be inferred from the session (i.e., when it matches the <CustId> in the <SignonRq>). When the <CustId> is used in messages between a Customer and CSP, the <CustPermId> element is an optional element and the <CustLoginId> is a required element. This is because the CSP server assigns the <CustPermId>, and the client may not know this ID the first time it logs in. When <CustId> is used in messages between CSP and BSP or other service provider, <CustPermId> may be required with <CustLoginId> optional. The <SPName> indicates the CSP that issued the customer permanent id. Because the <CustPermId> is used as a key field with many SPs, the <CustPermId> must not be changed once assigned. Future versions of IFX may permit this identifier to be changed by providing messages to communicate these changes to other SPs.
Tag
<SPName> <CustPermId>
Type
Identifier Identifier
Usage
Required Required OR
Description
Service Provider Name. The SP that assigned the <CustPermId>. Customer Permanent ID. Used as a database key to uniquely identify an FI or CSP customer. Cannot be changed by the customer. When <CustId> is used in messages between CSP and BSP or other service provider, <CustPermId> may be required with <CustLoginId> optional.
<CustLoginId>
Identifier
Required OR
Customer Login ID. Used as a user-friendly name for the customer for authentication purposes. Maps directly to Customer Permanent ID. Some implementations may allow a user to change his or her Login ID. When the <CustId> is used in messages between a Customer and CSP, the <CustPermId> element is an optional element and the <CustLoginId> is a required element.
<CardMagData>
Aggregate see section 3.2.7.2.4.1 Aggregate see section 3.2.24
Required OR Required Repeating OR
Card Magnetic Stripe Data
<CardLogicalData>
Logical Data That Represents the Card.
14
April 2005
Version 1.7
Tag
<PassbkAcceptData>
Type
Aggregate see section 3.2.26 Aggregate see section 3.2.27
Usage
Required Repeating OR Required Repeating OR
Description
Data that represents the passbook
<PersonalIdent>
Personal identification. The identification presented by the customer.
3.2.3.2 Customer Name Aggregate <CustName>

The <CustName> aggregate is used to specify a customers name and, optionally, nickname. This aggregate will be deprecated in IFX 2.0, replaced by <PersonName>.
Tag
<LastName> <FirstName> <MiddleName> <TitlePrefix> <NameSuffix> <Nickname> <LegalName>
Type
C-40 C-40 C-40 C-8 C-40 C-40 C-96
Usage
Required Repeating Required Repeating Optional Repeating Optional Optional Optional Optional
Description
Customer Last Name. Customer First Name. Customer Middle Name. Customer Title Prefix. For example, Ms., or Dr. Customer Name Suffix. For example, MD or Jr. Customer Nickname. Assigned by customer if desired. Used by entities like trusts, or businesses in the case where an individual is doing business as a company. Organizations and companies will be supported more fully in future versions of IFX.
3.2.3.3 Customer Contact Aggregate <CustContact>

The <CustContact> aggregate appears wherever the customers contact information is needed. The customer provides this information to the SP regarding how and when to contact him or her. This aggregate is most commonly used to allow the customer to override the default customer contact information stored as part of the Customer Profile. This aggregate will be deprecated in IFX 2.0, replaced by <ContactInfo>.
Tag
<CustContactPref>
Type
Open Enum
Usage
Optional
Description
Customer Contact Preference. This is a customer-provided preference for contact by FI and SP staff. Defined values: DayPhone, EvePhone, DayFax, EveFax, Email, Post.
<PrefTimeStart> <PrefTimeEnd> <DayPhone>
Time Time Phone Number Phone Number
Optional Optional Optional but see Description Optional but see Description
Preferred Customer Contact Start Time. This is a customerprovided start time preference for contact by SP staff. Preferred Customer Contact End Time. This is a customerprovided end time preference for contact by SP staff. Customer Daytime Telephone Number. Required if <CustContactPref> = DayPhone. Customer Evening Telephone Number. Required if <CustContactPref> = EvePhone.
<EvePhone>
Version 1.7
April 2005
15
Tag
<DayFax>
Type
Phone Number Phone Number NC-128
Usage
Optional but see Description Optional but see Description Optional but see Description
Description
Customer Daytime Fax Number. Required if <CustContactPref> = DayFax. Customer Evening Fax Number. Required if <CustContactPref> = EveFax. Customer Email Address. Required if <CustContactPref> = Email.
<EveFax>
<EmailAddr>
3.2.3.4 Customer Name/Address Aggregate <CustNameAddr>

This aggregate will be deprecated in IFX 2.0, to be replaced by <PersonInfo>.
Tag
<NameAddrType>
Type
Open Enum
Usage
Required
Description
Name/Address type. Defined values: Billing, Delivery, Customer
<FullName>
C-96
Required XOR Repeating Required XOR Required XOR Required
Concatenated customer name associated with the address.
<CustName>
Aggregate see section 3.2.3.2 Aggregate see section 3.2.4.1.1 Aggregate see section 3.2.3.10.1 Aggregate see section 3.2.3.3 Aggregate see section 3.2.3.9
Customer name. The customer name associated with the address. Person name.
<PersonName>
<PostAddr>
Postal address.
<CustContact>
Optional XOR Optional XOR
Customer contact aggregate.
<ContactInfo>
Contact Information Aggregate.
3.2.3.5 Customer Preference Aggregate <CustPref>

The <CustPref> aggregate is used to specify a customers preferences or for the service provider to store values that are specific to a customer. Applications can use the values stored in this aggregate to tailor the customers experience during an interaction with a service.
Tag
<Language>
Type
NC-17
Usage
Optional
Description
Language. This element contains the customers preferred language of communication. See section 2.6.4 for more information on the format of this element.
<MktgInfo> <CustBankSvcPref>
C-255 Aggregate see section 3.2.3.6
Optional Optional
Marketing Information. Customer Banking Service Preferences
16
April 2005
Version 1.7
3.2.3.6 Customer Bank Service Preference Aggregate <CustBankSvcPref>

Tag
<CustWithdrawalPref>
Type
Usage
Optional
Description
Customer Withdrawal Preferences. Used to store the customers preferred withdrawal parameters for fast cash ATM withdrawals.
3.2.3.7 Customer Withdrawal Preference Aggregate <CustWithdrawalPref>

Tag
<CurAmt> <DepAcctId>
Type
Currency Amount Aggregate see section 3.2.7.2.2
Usage
Required Optional
Description
Currency Amount. Identifies the customers preferred amount to be withdrawn. Deposit Account Identifier. This is the customers preferred deposit account identifier. If absent, the value defaults to the primary account for the customer (usually a checking account).
3.2.3.8 Composite Contact Information Aggregate <CompositeContactInfo>

Tag
<ContactInfoType>
Type
Open Enum
Usage
Required
Description
Contact Information Type. The specific type of the contact referenced in the <ContactInfo> aggregate. Defined values: CustServ, LostCard, GeneralInfo
<ContactInfo>
Required
Contact Information.
3.2.3.9 Contact Information Aggregate <ContactInfo>

The <ContactInfo> aggregate appears wherever a persons or organizations contact information is needed. It is used in IFX 1.1 and later versions as a replacement for the <CustContact> and <OrgContact> aggregates that will be deprecated in IFX 2.0.
Tag
<ContactPref>
Type
Open Enum
Usage
Optional
Description
Contact Preference. This is the preferred method to reach the entity to whom the <ContactInfo> refers. Defined values: DayPhone, EvePhone, DayFax, EveFax, Email, Post.
<PrefTimeStart> <PrefTimeEnd>
Time Time
Optional Optional
Preferred Contact Start Time. This is the beginning of the window of time within which contact is preferred. Preferred Contact End Time. This is the end of the window of time within which contact is preferred.
Version 1.7
April 2005
17
Tag
<PhoneNum>
Type
Aggregate see section 3.2.3.10 C-40
Usage
Optional Repeating but see Description Optional
Description
Phone number aggregate. Required if <ContactPref> = DayPhone, EvePhone, DayFax, or EveFax.
<ContactName>
Name. Name of the person associated with the contact information. Typically, this is the name of the person within the business that the phone number, email address, and/or address is associated with. Email Address. Required if <ContactPref> = Email. Web Site Address. Postal Address. Required if <ContactPref> = Post
<EmailAddr>
NC-128
Optional but see Description Optional Optional Repeating but see Description
<URL> <PostAddr>
URL Aggregate see section 3.2.3.10.1
3.2.3.10 Phone Number Aggregate <PhoneNum>

Tag
<PhoneType>
Type
Open Enum
Usage
Required
Description
Phone number type. Defined values: DayPhone, EvePhone, DayFax, EveFax
<Phone>
Phone Number
Required
Phone Number.
3.2.3.10.1 Postal Address Aggregates <PostAddr>, <BillingAddr>, <BillRetAddr>, <RemitAddr>

The <PostAddr> aggregate is used wherever a postal address is needed. There are some cases where a synonym is used to distinguish the aggregate from another of the same structure in the same aggregate (e.g., the Billing Address <BillingAddr>, where more than one postal address is present).
Tag
<Addr1> <Addr2>
Type
C-64 C-64
Usage
Required Optional but see Description Optional but see Description Optional Optional Optional Optional Required
Description
Address Line 1. Address Line 2. Required if <Addr3> is present. Address Line 3. Required if <Addr4> is present. Address Line 4. City. State or Province. Postal Code. Country. Values are defined by ISO-3166 3-letter codes.
<Addr3>
C-64
<Addr4> <City> <StateProv> <PostalCode> <Country>
C-64 C-32 C-32 C-11 NC-3
18
April 2005
Version 1.7
Tag
<AddrType>
Type
Open Enum
Usage
Optional
Description
Address Type. Defined values: Seasonal, Primay, Secondary, Business, Home
<StartDt> <EndDt>
DateTime DateTime
Optional Optional
Start Date. Effective start date for this address. End Date. Effective end date for this address. Address is current if <EndDt> is not present.
3.2.4Person Data
3.2.4.1 Person Information Aggregate <PersonInfo>
The <PersonInfo> aggregate is used to specify the details about a person. It is used in IFX 1.1 and later versions as a replacement for the <CustNameAddr> aggregate that will be deprecated in IFX 2.0.
Tag
<NameAddrType>
Type
Open Enum
Usage
Required
Description
Name/Address type. Defined values: Billing, Delivery, Customer
<FullName> <PersonName>
C-96 Aggregate see section 3.2.4.1.1 Aggregate see section 3.2.3.9 Aggregate see section 3.2.4.1.3 Date Aggregate see section 3.2.4.1.2 C-40 C-40 Aggregate see section 3.2.4.1.4 Aggregate see section 2.2.6 Open Enum Open Enum
Required XOR Required XOR Optional
Concatenated person name. Person name.
<ContactInfo>
Contact information aggregate.
<TINInfo>
Optional
Customer Tax Identifier Number aggregate.
<BirthDt> <DriversLicense>
Optional Optional
Date of Birth. Drivers License aggregate. This will become a subaggregate of GovIssueIdent in IFX 2.0 Mothers Maiden Name. Spouses Name. Employment History Aggregate. This will become a subaggregate of Employment Data in IFX 2.0. Employment Data Aggregate. Contains Employment History and employee identification data.
<MotherMaidenName> <SpouseName> <EmploymentHistory>
Optional Optional Optional XOR Repeating Optional XOR Repeating
<EmploymentData>
<Gender> <MaritalStatus>
Optional
Marital Status. Defined values: Married, Single, Divorced, Widow
<USA.MilitaryRank> <Dependents>
C-32 Long
Optional Optional
Military Rank. This element will be deprecated in IFX 2.0 and replaced by <MiscGovIssueIdent>. Number of Dependents.
Version 1.7
April 2005
19
Tag
<Passport>
Type
Aggregate See section 2.2.1 C-32 NC-3 Open Enum
Usage
Optional XOR Optional XOR Optional XOR Optional
Description
This passport provides further passport information. It will replace <PassportNumber> and <PassportCountry> in IFX 2.0. Passport Number. This element will be deprecated in IFX 2.0. and replaced by <Passport> Passport Country. This element will be deprecated in IFX 2.0. and replaced by <Passport> Officer, Employee, Director Code. Defined values: Officer, Director, Employee
<PassportNumber> <PassportCountry> <OEDCode>
<OEDInstitution>
Open Enum
Optional
OED Institution. Defined values: Unknown, Affiliate Financial Institution, Holding Company, Other Financial Institution, This Financial Institution
<GovIssueIdent>
Aggregate see section 2.2.4
Optional
Government Issued Identification. Used if IdentVerifyType is GovIssuedId. This would be used if the ID presented is DriversLicense BirthCertificate HealthCard MilitaryIdent PermResIdent GovEmpIdent RetirementIdent VoterRegIdent
<OtherIdentDoc>
Optional
Other Identification Document.
3.2.4.1.1 Person Name Aggregate <PersonName>

The <PersonName> aggregate is used to specify a persons name and, optionally, nickname. It is used in IFX 1.1 and later versions as a replacement for the <CustName> aggregate that will be deprecated in IFX 2.0.
Tag
<LastName> <FirstName> <MiddleName> <TitlePrefix> <NameSuffix> <Nickname>
Type
C-40 C-40 C-40 C-8 C-40 C-40
Usage
Required Repeating Required Optional Repeating Optional Optional Optional
Description
Customer Last Name. Customer First Name. Customer Middle Name. Customer Title Prefix. For example, Ms., or Dr. Customer Name Suffix. For example, MD or Jr. Customer Nickname. Assigned by customer if desired.
20
April 2005
Version 1.7
Tag
<LegalName>
Type
C-96
Usage
Optional
Description
Used by entities like trusts, or businesses in the case where an individual is doing business as a company. Organizations and companies will be supported more fully in future versions of IFX.
3.2.4.1.2 Drivers License Aggregate <DriversLicense>

Drivers license.
Tag
<LicenseNum> <StateProv> <Country>
Type
C-32 C-32 NC-3
Usage
Required Optional Optional
Description
Drivers License Number. Drivers License State/Province. Drivers License Country.
3.2.4.1.3 Tax Identification Number Aggregate <TINInfo>

Tax identification number aggregate.
Tag
<TINType>
Type
Open Enum
Usage
Optional
Description
TIN Code Type. Defined values: EIN (Business TIN), SSN (Personal TIN), NRA Business, NRA Personal.
<TaxId> <CertCode>
NC-12 Open Enum
Required Optional
Tax Identifier. Certification Code for the Tax ID. Defined values: Certification Not on File, Certification on File, Account Opened After 1987, Account Opened 1984-1987, Account Open Before 1984, Certified, Uncertified, Notice 1, Notice 2, Cert Not Required
3.2.4.1.4 Employment History Aggregate <EmploymentHistory>

Employment history aggregate.
Tag
<EmploymentStatus>
Type
Open Enum
Usage
Optional
Description
Employment Status. Defined values: Current, Previous
<OrgInfo>
Aggregate see section 3.2.5.1.2 C-50 Currency Amount C-32 DateTime DateTime
Optional
Employer Organization Information.
<Occupation> <Income> <JobTitle> <StartDt> <EndDt>
Required Optional Optional Optional Optional
Occupation Income Amount Job Title. Employment Start Date. Employment End Date.
Version 1.7
April 2005
21
3.2.5Organization Data
3.2.5.1 Organization Record <OrgRec>
Tag
<OrgId>
Type
Aggregate see section 3.2.5.1.1 Aggregate see section 3.2.5.1.2
Usage
Optional Repeating Required
Description
Organization Identifier
<OrgInfo>
Organization Information.
3.2.5.1.1 Organization Information <OrgId>

Tag
<OrgIdType>
Type
Open Enum
Usage
Required
Description
Organization Identifier Type. Defined Values: DunAndBradstreet, USA.TaxId, OrgSpecific
<OrgIdNum>
Identifier
Required
Organization Identifier Number
3.2.5.1.2 Organization Information <OrgInfo>

Tag
<IndustId>
Type
Aggregate see section 3.2.13 C-40 C-96 Aggregate see section 3.2.3.8 Aggregate see section 3.2.4.1.3 Date Long
Usage
Optional
Description
Industry Identifier. The identifier of the industry in which the organization does business. Name. The name of the organization. Legal Name. The legal name of the organization. Composite Contact Information Aggregate.
<Name> <LegalName> <CompositeContactInfo>
Optional Optional Optional Repeating Optional
<TINInfo>
Tax Identifier Number Aggregate.
<EstablishDt> <NumEmployees>
Optional Optional
Date Established. Number of Employees.
3.2.5.2 Organization Contact Aggregate <OrgContact>

The <OrgContact> aggregate appears wherever contact information for an organization is needed. Contact type indicates the function of the contact. This aggregate will be deprecated in IFX 2.0, replaced by <ContactInfo>.
Tag
<ContactType>
Type
Open Enum
Usage
Required
Description
Contact Type. Defined values: CustSvc, Enroll, Tech, Personal
<Desc>
C-80
Optional
Description. Text describing the purpose of the group providing contact information is provided.
22
April 2005
Version 1.7
Tag
<Phone> <Fax> <EmailAddr> <URL>
Type
Phone Number Phone Number NC-128 URL
Usage
Optional Optional Optional Optional
Description
Telephone Number. Fax Number. Email Address. Web Site Address.
3.2.6Biller Data
3.2.6.1 Biller Contact Aggregate <BillerContact>
The <BillerContact> aggregate is used to provide complete information about a Biller.
Tag
<LegalName> <Name> <PostAddr>
Type
C-96 C-40 Aggregate see section 3.2.3.10.1 Aggregate see section 3.2.3.10.1
Usage
Description
Biller Legal Name. Assigned by the service provider. Cannot be changed by the client. Biller Business Name. Assigned by the service provider. Cannot be changed by the client. Biller Address Aggregate. Assigned by the service provider. Cannot be changed by the customer.
<BillRetAddr>
Optional
Bill Return Address Aggregate. Uses the same structure as <PostAddr>. Assigned by the service provider. Cannot be changed by the customer.
<RemitName>
C-40
Optional
Remittance Name. Uses the same structure as <PostAddr>. Assigned by the service provider. Cannot be changed by the customer.
<RemitAddr>
Aggregate
Optional
Remittance Address Aggregate. Uses the same structure as <PostAddr>. Assigned by the service provider. Cannot be changed by the customer.
<OrgContact>
Optional XOR Repeating Optional XOR Repeating
Support Contact Detail Aggregate.
<ContactInfo>
3.2.6.2 Biller Pay Information Aggregate <BillerPayInfo>

The <BillerPayInfo> identifies payment information associated with a Biller.
Version 1.7
April 2005
23
Tag
<PmtInst>
Type
Usage
Optional Repeating Profiled values
Description
Payment Instrument Aggregate. Types of payment that the biller accepts via the Pay provider. This is used to restrict the methods by which the customer may pay for the bill. The Service Provider indicates which Payment Instruments are supported via profile. The Biller may choose to override this list by including <PmtInst> in the Bill Summary <BillRec>. Days to post an electronic payment. The maximum days between receipt of an electronic payment by the biller or BPP and posting to the customers account. Pre-Note Required. If set to True, the Biller requires prenoting by the Service Provider.
<DaysToEPost>
Long
Optional
<PrenoteReqd>
Boolean
Optional
Note: Pre-noting is the transmission of a zero dollar message to verify consumer information, usually the payee account information.
3.2.7Account Data
3.2.7.1 Bank Account Record Aggregate <BankAcctRec>
The <BankAcctRec> aggregate provides information about a customer banking account.
Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.7.2.6 Aggregate see section 3.2.7.2.7 Open Enum
Usage
Required XOR Required XOR Required XOR Required
Description
Deposit Account Identification Aggregate.
<CardAcctId>
Card Account Identification Aggregate.
<LoanAcctId>
Loan Account Identification Aggregate.
<BankAcctInfo>
Bank Accont Information Aggregate
<BankAcctStatus>
Optional
Bank Account Status Aggregate
<AcctTaxType>
Optional
Account Tax Type. Defined values: TaxDeferred, Standard.
<XferFromSupt>
Optional
Transfer From Supported Aggregate. If present, indicates that this account is a valid source account for a transfer. This aggregate will be deprecated in IFX 2.0, to be replaced by <BankAcctFeatSupt>.
<XferToSupt>
Optional
Transfer To Supported Aggregate. If present, indicates that this account is a valid target account for a transfer. This aggregate will be deprecated in IFX 2.0, to be replaced by <BankAcctFeatSupt>.
<PaySupt>
Optional
Payment Supported Aggregate. If present, indicates that this account is a valid source account for payment. This aggregate will be deprecated in IFX 2.0, to be replaced by <BankAcctFeatSupt>.
24
April 2005
Version 1.7
Tag
<BankAcctFeatSupt>
Type
Aggregate see section 3.2.7.2.8 Aggregate see section 3.2.8.1
Usage
Description
Supported Bank Account Features Aggregate. If present, indicates the various features supported for this Bank Account Account Balance Aggregate. Repeated for each balance to be included for this account.
<AcctBal>
3.2.7.2 Bank Account Record Support Aggregate <XferFromSupt>, <XferToSupt>, <PaySupt>

Tag
<MinCurAmt> <MaxCurAmt>
Type
Currency Amount Currency Amount
Usage
Optional Optional
Description
Minimum amount that may be transferred from the account, if applicable. Maximum amount that may be transferred from the account, if applicable.
3.2.7.2.1 Bank Information Aggregate <BankInfo>

The Bank Information aggregate contains additional information used to identify a bank. Sufficient information must be provided within this aggregate to uniquely identify the bank at which the account is held. Failure to do so will result in an error being returned from the server.
Tag
<BankIdType>
Type
Open Enum
Usage
Optional
Description
Bank Identifier Type. Type of bank identifier. Defined Values: SWIFT, ABA, FedWire, CHIP, CHAP, SortCode. Default value is ABA.
<BankId>
NC-34
Optional
Bank Identifier. Qualifies account number if known by the customer/client. Usage is expected to be routing and transit number in the US or the equivalent in an international implementation. This is required in USA. Additional Reference information to uniquely identify the bank. Defined values for contained <RefType>: CountrySpecific, BankSpecific
<RefInfo>
Optional Repeating
<Name>
C-40
Optional but see Description Optional
Bank name, required in CHE, DEU, and ITA.
<BranchId>
NC-22
Branch Identifier. Qualifies account number if known by the customer/client. Used to indicate which branch the account is with. Usage is expected to be primarily in countries where regulations require an account to be assigned to a branch office, but a US-based FI may also require this field for operational reasons. Bank branch name, required in ITA.
<BranchName>
C-40
Version 1.7
April 2005
25
Tag
<PostAddr>
Type
Aggregate see section 3.2.3.10.1 C-32
Usage
Optional XOR Optional XOR but see Description Optional but see Description Optional but see Description Optional but see Description
Description
Bank Postal Address. Either <PostAddr> or broken-out <City>, <StateProv>, <PostalCode>, and/or <Country> may be used, but not both. Bank Branch City. Required in CHE. Either <PostAddr> or broken-out <City>, <StateProv>, <PostalCode>, and/or <Country> may be used, but not both. Bank Branch State or Province. Either <PostAddr> or broken-out <City>, <StateProv>, <PostalCode>, and/or <Country> may be used, but not both. Bank Branch Postal Code. Required in CHE. Either <PostAddr> or broken-out <City>, <StateProv>,<PostalCode>, and/or <Country> may be used, but not both. Country. Bank Branch Country Code. Either <PostAddr> or broken-out <City>, <StateProv>, <PostalCode>, and/or <Country> may be used, but not both.
<City>
<StateProv>
C-32
<PostalCode>
C-11
<Country>
NC-3
3.2.7.2.2 Deposit Account Identifier Aggregates <DepAcctId> <DepAcctIdFrom> <DepAcctIdTo>

The <DepAcctId> aggregate is used to uniquely identify a deposit-type account. When a single account is specified in a message or aggregate, it is referred to as <DepAcctId>. When multiple accounts appear in a message or aggregate, the <DepAcctIdFrom> and <DepAcctIdTo> aggregates are used for clarity. The <DepAcctIdFrom> and <DepAcctIdTo> aggregates have the same structure as the <DepAcctId> aggregate.
Tag
<AcctId>
Type
C-32
Usage
Required
Description
Account Identifier. Sometimes known as account number, but not restricted to numeric characters.
Note: An International Bank Account Number (IBAN) can be used here to replace the domestic account number.
<AcctType> Open Enum Required Account Type. See Data Dictionary for details. Defined values: DDA, SDA, CDA, MMA, CMA.
Note: An Open Enum data type permits the addition of account types specific to an FI, country, etc.
<AcctKey> <AcctCur> NC-22 NC-22 Optional Optional Account Key. Checksum for international banks. Account Currency. Currency of the account. This may be necessary to uniquely identify the account, as many countries allow for a single account to contain multiple subaccounts, each in a different currency. Bank Information aggregate.
<BankInfo>
Aggregate see section 3.2.7.2.1
Required
3.2.7.2.2.1 Intermediary Deposit Account Aggregate <IntermediaryDepAcct>

The Intermediary Bank Account aggregate is used to identify all intermediary bank accounts in a bank chain. This aggregate is used within the payment instruction to identify all banks that route the payment from the originating bank or <DepAcctIdFrom> to the receiving bank or <DepAcctIdTo>.
26
April 2005
Version 1.7
Tag
<SeqNum> <DepAcctId>
Type
Long Aggregate see section 3.2.7.2.2
Usage
Required Required
Description
Sequence number of the Intermediary bank in a bank chain. Deposit Account Identification Aggregate for the intermediary bank.
3.2.7.2.3 Card Account Identifier Aggregates <CardAcctId> <CardAcctIdFrom> <CardAcctIdTo>

The <CardAcctId> aggregate is used to uniquely identify a card-type account, such as credit card or debit card. When a single account is specified in a message or aggregate, it is referred to as <CardAcctId>. When multiple accounts appear in a message or aggregate, the <CardAcctIdFrom> and <CardAcctIdTo> aggregates are used for clarity. The <CardAcctIdFrom> and <CardAcctIdTo> aggregates have the same structure as the <CardAcctId> aggregate.
Tag
<AcctId> <CardMagData>
Type
NC-32 Aggregate see section 3.2.7.2.4.1 Open Enum
Usage
Required XOR Required XOR Required
Description
Account Identifier. Sometimes known as account number, but not restricted to numeric characters. Card Magnetic Stripe Data
<AcctType>
Account Selection Type. See Data Dictionary for details. Defined values: CCA, DDA, SDA, Default, Unknown, DesignatedOther
<CCMotoAcct>
Optional
Credit Mail Order/Telephone Order Account Aggregate. Used for defining additional Credit Card data when required for card not present transactions, such as when activating a Credit Card as a funding account for payment.
3.2.7.2.4 Credit Card Mail Order/Telephone Aggregate <CCMotoAcct>

Tag
<ExpDt>
Type
DateTime
Usage
Required
Description
Expiration date for card. If the card has only month and year expiration, the last day of the month must be specified here. Card verification data. This field contains data printed on the card that is manually entered. This is data that cannot be automatically read from a card as it is used. This data is used to ensure the physical presence of the actual card. Customer Name. Name on the front of this card (exactly as name appears on the card). Customer Address Aggregate. Customer address associated with this card. Customer Postal Code. The postal code associated with this card. Customer phone number associated with this card.
<CardVrfyData>
C-16
Optional
<Name> <PostAddr>
C-40 Aggregate see section 3.2.3.10.1 C-11 Phone Number
Optional Optional XOR Optional XOR Optional
<PostalCode> <Phone>
Version 1.7
April 2005
27
Tag
<Brand>
Type
Open Enum
Usage
Optional
Description
Type of credit card (VISA, AMEX, etc.). This is just a check against the information provided by the account number. Defined values: AmEx, CarteBlanche, DinersClub, Discover, Europay, JCB, MasterCard.
3.2.7.2.4.1 Card Magnetic Stripe Data <CardMagData>

Tag
<MagData1> <MagData2> <MagData3>
Type
NC-79 NC-40 NC-107
Usage
Required OR Required OR Required OR
Description
Track 1 data Track 2 data Track 3 data
3.2.7.2.5 Loan Account Identifier Aggregates <LoanAcctId> <LoanAcctIdFrom> <LoanAcctIdTo>

The <LoanAcctId> aggregate is used to uniquely identify a loan-type account. When a single account is specified in a message or aggregate, it is referred to as <LoanAcctId>. When multiple accounts appear in a message or aggregate, the <LoanAcctIdFrom> and <LoanAcctIdTo> aggregates are used for clarity. The <LoanAcctIdFrom> and <LoanAcctIdTo> aggregates have the same structure as the <LoanAcctId> aggregate.
Tag
<AcctId> <AcctType>
Type
NC-32 Open Enum
Usage
Required Required
Description
Account Identifier. Sometimes known as account number, but not restricted to numeric characters. Account Type. See Data Dictionary for details. Defined values: MLA, ILA, LOC, EQU, CLA.
<BankInfo> Aggregate see section 3.2.7.2.1 Required Bank Information aggregate.
3.2.7.2.6 Bank Account Information Aggregate <BankAcctInfo>

Tag
<CurCode> <Desc> <CustName>
Type
NC-3 C-80 Aggregate see section 3.2.3.2 Aggregate see section 3.2.4.1.1 Aggregate see section 3.2.5.2
Usage
Required Optional Optional XOR Optional XOR Optional XOR
Description
Currency Code. As defined by ISO-4217. Account Description. Assigned by the Financial Institution. Typically product name. Does not include account number. Customer Name in which this account is held.
<PersonName>
Person Name.
<OrgContact>
FI Customer Service Contact Information.
28
April 2005
Version 1.7
Tag
<ContactInfo>
Type
Aggregate see section 3.2.3.9 Open Enum
Usage
Optional XOR Optional
Description
<CustAcctUse>
Customer Account Use. Defined values: Retail, Business.
<PrimaryAcct>
Boolean
Optional
Primary Account Indicator. If True, used as default account for a class of accounts (i.e., checking). Typically used in ATM networks. May be used for other applications by some FIs. Term Aggregate.
<Term>
Aggregate see section 3.2.9.1 Aggregate see section 6.3.30.4 Boolean NC-3 C-32 C-42 C-42 Currency Amount
Optional
<IntRateInfo>
Optional
Interest Rate Information Aggregate.
<BackupWithholding> <TaxCountry> <TaxProvince> <Ownership> <ProductId> <InitialDeposit>
Optional Optional Optional Optional Optional Optional
Backup Withholding Indicator. Tax Country. Tax Province. Ownership Identifier. Product Identifier. Initial Deposit Amount.
3.2.7.2.7 Bank Account Status <BankAcctStatus>

Tag
<BankAcctStatusCode>
Type
Closed Enum C-255 DateTime Open Enum
Usage
Required
Description
Account Status. Valid values: Open, Closed, Inactive, NotAvail
<StatusDesc> <EffDt> <StatusModBy>
Status Description. Explanatory text associated with this bank account status. Effective Date/Time. The date/time the <BankAcctStatusCode> took effect. Status Modified By. If present, indicates who modified the Bank Status Code. Defined values: Customer, FI, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
3.2.7.2.8 Bank Account Feature Support <BankAcctFeatSupt>

The <BankAcctFeatSupt> aggregate provides information about various features supported by a customer banking account. This aggregate contains two <TrnSrc> elements. The first <TrnSrc> element (contained within <BankAcctFeatLimit>) indicates features supported by the transaction source. The second <TrnSrc> indicates the transaction source that has a limit.
Version 1.7
April 2005
29
Tag
<BankAcctFeatType>
Type
Open Enum
Usage
Required
Description
Bank Account Feature Type. Indicates the type of feature supported. Defined Values: XferFrom, XferTo, Pay, Debit, Credit, ChkDeposit,ChkCashing,CashDeposit
<TrnSrc>
Open Enum
Optional Repeating
Transaction Source. Indicates the transaction source for which this feature is supported (absence indicates all sources). This is used to indicate features supported by transaction source regardless of specific limits. Defined values: ATM, Teller, POS, VRU, HomeBank, ACH
<BankAcctFeatLimitType>
Open Enum
Required
Bank Account Feature Limit Type. Indicates the type of limit. Defined Values: Min, Max, DailyMin, DailyMax, WeeklyMin, WeeklyMax, MonthlyMin, MonthlyMax
3.2.7.2.9 Bank Account Feature Limit Aggregate <BankAcctFeatLimit>

Tag
<TrnSrc>
Type
Open Enum
Usage
Optional
Description
Transaction Source. Indicates the transaction source for which this limit applies (absence indicates that the limit applies to all sources). This is used if the limits are different for different transaction sources. Defined values: ATM, Teller, POS, VRU, HomeBank, ACH
<CurAmt>
Currency Amount
Required
Currency Amount. The amount of the limit.
3.2.7.3 Presentment Account Record Aggregate <PresAcctRec>

Tag
<PresAcctId>
Type
Aggregate see section 3.2.7.3.1 Aggregate see section 3.2.7.3.2 Aggregate see section 3.2.7.3.3
Usage
Required
Description
Presentment Account Identification Aggregate
<PresAcctInfo>
Required
Presentment Account Information Aggregate
<PresAcctStatus>
Optional
Presentment Account Status Aggregate
3.2.7.3.1 Presentment Account Identification <PresAcctId>
30
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification The <PresAcctId> aggregate uniquely identifies a customers account with a biller by the combination of BSP <Org>, biller identifier <BillerNum>, and account number <BillingAcct>. <BillerNum>s must be unique within a BSP. Upon account activation, the <CustNameAddr> (billing account information) has to be correlated to the <CustPermId> from the CSPs records by either or both the CSP and the BSP to ensure that the Customers identification as known to the CSP is properly matched to the Customers identification as known to the Biller. For account activation, this aggregate also provides the CSP with the ability to send the BSP the <StdPayeeId> or the <CustPayeeId> that is associated with this biller at the appropriate CPP. If the BSP stores these data, they must be returned in any inquiry response that includes <PresAcctId> (e.g. <BillInqRs>).
Tag
<BillingAcct> <BillerId>
Type
Usage
Required Required
Description
Customer account with the Biller. Biller Identifier Aggregate. This is an identifier created by the Biller or BSP.
3.2.7.3.2 Presentment Account Information Aggregate <PresAcctInfo>

Tag
<StdPayeeId>
Type
Usage
Optional XOR
Description
Standard Payee Identifier. The identification for this biller at the CPP. When sent in account activation, it is intended for storage on the BSP database, such that it may be returned in subsequent inquiries utilizing this aggregate. This may be used by the CSP to help match the BSPs Biller ID to the Standard Payee ID as known to the CPP. Customer Payee Identifier. The identification for this biller at the CPP. When sent in account activation, it is intended for storage on the BSP database, such that it may be returned in subsequent inquiries utilizing this pair of elements. This may be used by the CSP to help match the BSPs Biller ID to the Standard Payee ID as known to the CPP. Service Provider Name. Used to scope <CustPayeeId>.
<CustPayeeId>
Identifier
Optional XOR
<SPName>
Identifier
Required
3.2.7.3.3 Presentment Account Status <PresAcctStatus>

The <PresAcctStatus> aggregate describes the status of the customers account with a biller.
Tag
<PresAcctStatusCode>
Type
Usage
Required
Description
Account Status. Valid values: Open, Closed, Inactive, NotAvail
Status Description. Explanatory text associated with this presentment account status. Effective Date/Time. The date/time the <BankAcctStatusCode> took effect. Status Modified By. If present, indicates who modified the status. Defined values: Customer, FI, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
Version 1.7
April 2005
31
3.2.8Account Balances
The following tables identify the account balances applicable to a specific account type. The first table identifies the association between the account type and the specific account classification <DepAcctId>, <CardAcctId> and <LoanAcctId>. The second table identifies the relationship between account classification and balance types. All account types use the balances associated with their account classification. The <EffDt> associated with each balance indicates the time and date as of which the balance is current. The frequency of changing this date depends on how often the FI/SP refreshes the balances for a specific account type. This time and date might be updated by every update message in an on-line bank or be refreshed once a day by a strip file implementation. Even within a single FI/SP, the Demand Deposit (Checking) Account (DDA) might be online, while Savings (SDA) or Certificates of Deposit (CDA) might be updated overnight.
3.2.8.1 Account Balance Aggregate <AcctBal>

The <AcctBal> aggregate is used to express an account balance. The balance being specified is identified in <BalType>, which is an Open Enum. When <AcctBal> is used, it may repeat, to allow multiple balances to be specified for the given account.
Tag
<BalType>
Type
Open Enum
Usage
Required
Description
Balance Type. Defined Values: Ledger, OpeningLedger, ClosingLedger, MinLedger, AvgLedger, Avail, Current, Outstanding, OpeningOutstanding, ClosingOutstanding, AvailCredit, CreditLimit, PayoffAmt, Principal, Escrow, CreditHeld, DebitHeld, TotalHeld, BAI:xxx or TMA:xxx (Reference BAI Code List at http://www.bai.org/operations/bai_codes.html, or TMA Code List at http://www.AFPonline.org/Information_Center/Publications/ Bookstore/afpbooks/afpbooks.html as maintained by Association of Financial Professionals (AFP)) Example: BAI:010 (Beginning Ledger Balance), BAI:140 (ACH Credits), etc.
<CurAmt> <EffDt> <ExpDt> <Desc>
Currency Amount DateTime DateTime C-80
Required Optional Optional Optional
Currency Amount. This currency amount references the Balance Amount. Effective DateTime. Expiration DateTime. Expiration Date of the Balance. For example, a payoff amount expiration date. Description.
3.2.8.1.1 Balance Type and Classification Association

Account Classification Balance Type
Ledger OpeningLedger ClosingLedger MinLedger AvgLedger Avail
Deposit (Asset)

Loan (Liability)
Card (Asset or Liability)

32
April 2005
Version 1.7
Current Outstanding OpeningOutstanding ClosingOutstanding AvailCredit CreditLimit PayoffAmt Principal Escrow
3.2.8.2 Extended Account Balance Aggregate <ExtAcctBal>

The <ExtAcctBal> aggregate is used to express an extended account balance. The balance being specified is identified in <ExtBalType>, which is an Open Enum. When <ExtAcctBal> is used, it may repeat, to allow multiple balances to be specified for the given account.
Tag
<ExtBalType>
Type
Open Enum
Usage
Required
Description
Balance Type. Defined Values: PrepayPenalty, Orig, UnpaidAccruedInt, Redemption, YTDWithhold, LastYrWithhold, Overdraft, Overlimit, PastDue, CashLine, OutstandingCashAdv, CashAvail, PendAuthAmt, LastStmtBal, YTDInterest, LastYrInt, YTDFees, PeriodFees, LastYrFees, CashDepositAvail. Balance Amount. Balance DateTime. Expiration Date of the Balance. For example, a payoff amount expiration date. Description.
<CurAmt> <EffDt> <ExpDt> <Desc>
Currency Amount DateTime DateTime C-80
Required Required Optional Optional
3.2.8.2.1 Extended Balance Type and Classification Association

Account Classification Extended Balance Type
Orig UnpaidAccruedInt Redemption YTDWithhold LastYrWithhold Overdraft Overlimit PastDue CashLine OutstandingCashAdv
Deposit (Asset)
Loan (Liability)

Version 1.7
April 2005
33
CashAvail PendAuthAmt LastStmtBal YTDInterest LastYrInt YTDFees PeriodFees LastYrFees
3.2.8.3 Account Type and Classification Association

Account Classification <AcctType>
CCACredit Card Account CDACertificate of Deposit CLACommercial Loan Account CMACash Management Account DDADemand Deposit Account EQUHome Equity Loan ILAInstallment Loan Account LOCConsumer Line of Credit MLAMortgage Loan Account MMAMoney Market Account SDASavings Account
Deposit (Asset)
Loan (Liability)
The sign of account balances are stated as positive values when greater than zero (outstanding balance due on a customers liability account and positive balance in a customers asset account) and negative numbers when less than zero (credit balance in a customers liability account and overdrawn balance in a customers asset account). For a Card Account, the <AcctType> is used to indicate whether the account is an asset or liability account.
3.2.9Term Data
3.2.9.1 Deposit Term Aggregate <Term>
The <Term> aggregate contains details of the term of a deposit or a loan.
Tag
<Count>
Type
Long
Usage
Required
Description
Count. In this context, <Count> is the number of <TermUnits> for which a term deposit is effective. At the end of this period, the Term Deposit ceases to exist.
Note: If <TermUnits>=Days, this is the number of calendar days, not business days.
<TermUnits> Closed Enum C-80 Required Term Units. Units in which the Term Deposit is measured. Defined values: Days, Weeks, Months, Years, Indefinite Optional Short Description.
<Desc>
34
April 2005
Version 1.7
Tag
<DaysCall>
Type
Long
Usage
Description
Days Call. The number of business days notice required for withdrawal. Required if <TermUnits>=Indefinite.
3.2.10
Selection Criteria
3.2.10.1 Selection Range Date Aggregates <SelRangeDt>, <SelRangeDueDt>, <SelRangePrcDt>

The <SelRangeDt> aggregate identifies the start date and/or the end date as a selection criterion. The Selection Range Due Date <SelRangeDueDt> and Selection Range Processing Date <SelRangePrcDt> have the same structure as the <SelRangeDt>. The <SelRangeDt> aggregate contains two optional fields: <StartDt> and <EndDt>. The following rules are established for the <StartDt> and <EndDt> fields: If <StartDt> but not <EndDt> is supplied, then the search must match dates that are later than or equal to <StartDt>. If <EndDt> is supplied but not <StartDt>, then the search must match dates that are earlier than or equal to the <EndDt>. If both dates are supplied, then the search must match dates that are between or equal to the two dates supplied. If a client wishes to search for a specific date, then both <StartDt> and <EndDt> should be supplied and set to the same date, with <EndDt> set for 23:59:59. If <StartDt> and <EndDt> both have no times included, the semantic intent of the request is to search for items that occurred precisely at midnight on the specified date. Note: <StartDt> and <EndDt> are date fields typically entered by a consumer and are not timestamp fields. <UpDt>, on the other hand, is a timestamp (date and time) field found in many <xxxInqRq> messages. A client uses this timestamp to ask for any xxx updates created on the server after the value of <UpDt>. Along with any updates, the server returns <NewUpDt>, also a timestamp, that is the time that the last update was made on the server. The client may use <NewUpDt> as the value of <UpDt> in a subsequent <xxxInqRq>.
Type
DateTime DateTime
Tag
<StartDt> <EndDt>
Usage
Required OR Required OR
Description
Selection Start Date. Selection End Date.
3.2.10.2 Selection Range Currency Amount Aggregate <SelRangeCurAmt>

The <SelRangeCurAmt> aggregate contains two optional fields: <LowCurAmt> and <HighCurAmt>. The following rules are established for these fields: If <LowCurAmt> but not <HighCurAmt> is supplied, then the search must match amounts that are greater than or equal to <LowCurAmt>. If <HighCurAmt> is supplied but not <LowCurAmt>, then the search must match amounts that are smaller than or equal to the <HighCurAmt>.
Version 1.7
April 2005
35
Interactive Financial Exchange Business Message Specification If both amounts are supplied, then the search must match amounts that are between or equal to the two amounts supplied. If a client wishes to search for a specific amount, then both <LowCurAmt> and <HighCurAmt> should be supplied and set to the same value.
Tag
<LowCurAmt> <HighCurAmt>
Both amounts must be of the same currency.

Type
Currency Amount Currency Amount
Usage
Description
Selection Low Amount. Selection End Amount.
3.2.11
Tag
<Freq>
Recurring Model Data

Type
Open Enum
3.2.11.1 Recurring Model Information Aggregate <RecModelInfo>

Usage
Required
Description
Recurring Model Frequency. Defined values: Daily, Weekly, Biweekly, TwiceMonthly, Monthly, EndOfMonth, FourWeeks, BiMonthly, Quarterly, SemiAnnually, Annually, Manually.
<NumInsts>
Long
Optional XOR Profiled support Optional XOR Profiled support
Recurring Model Total Instances. If none of <NumInsts>, <FinalPrcDt>, or <FinalDueDt> is provided, the model is open-ended. Final Processing Date. Subject to server support for Processing Date Model in profile. Only payments allow the option of processing date. All transfers must use due date. If none of <NumInsts>, <FinalPrcDt>, or <FinalDueDt> is provided, the model is open-ended.
<FinalPrcDt>
Date
<FinalDueDt>
Date
Optional XOR Profiled support Optional Profiled support Optional Profiled support Optional Profiled support
Final Due Date. Subject to server support for Due Date Model in profile. If none of <NumInsts>, <FinalPrcDt>, or <FinalDueDt> is provided, the model is open-ended. Recurring Model Initial Amount. May be different from nominal instance amount. If omitted, the default instance amount is used for the initial transfer or payment. Recurring Model Final Amount. May be different from nominal instance amount. If omitted, the default instance amount is used for the final transfer or payment. Nickname. Optionally assigned by the customer. Pay provider may indicate support for longer-term storage of nicknames in the Service Profile. May be modified by the client.
<InitialCurAmt>
Currency Amount Currency Amount C-40
<FinalCurAmt>
<Nickname>
36
April 2005
Version 1.7
Tag
<SkipNextN>
Type
Long
Usage
Optional Profiled support
Description
Skip Next N Instances. A non-zero value indicates that the next N transaction instances are to be skipped. Subject to server support in Service Profile.
Note: The server must decrement the Skip Next N count and generate the instance with a processing status code of Skipped, based on the timing of the recurring model. The server must handle the skipped instance like any other instance, except that the server does not execute the instance for fulfillment purposes, including creating audit and sync records for the instance addition, and for the recurring model status changes. Therefore, each decrement must be reflected as a separate <RecXferModRs> within audits and syncs, and each status change to the specific instances of the transfers must be reflected as a separate <XferModRs>. The same behavior applies to <RecChkOrdModRs> and <ChkOrdModRs>
3.2.12
System Message Data
3.2.12.1 Response Status Aggregate <Status>

The <Status> aggregate is used in each response to indicate the status of the message. See Appendix A for information on Response Status Codes. When <Severity> = Info or Warn and the server is responding synchronously (i.e., not requiring the client to pick up the response at a later time, as described below), the server must generate the complete response message. When <Severity> = Error, the server is only expected to include the <Status> aggregate (required), the <MsgRsHdr> aggregate (optional), and echo the <RqUID>, <AsyncRqUID>, and <CustId> fields. The server must include these fields unless a system error prevents the server from reading the request message contents. In the latter situation, it may only be possible for the server to generate a response message containing the <Status> aggregate by itself. Other actions to be taken in the case of severe errors are specified for each implementation. Note: The explanatory text provided in the <StatusDesc> is freeform text that is not strictly dictated by the status code. Appendix A provides default <StatusDesc> text, but this text may be replaced or enhanced by particular implementations. The Asynchronous Response Information Aggregate <AsyncRsInfo> is used when the server cannot generate a complete response in a reasonable time (such as less than five minutes). In such a case, the server may return a <StatusCode> of 900 and <Severity> of Warn, with an <AsyncRsInfo> aggregate optionally containing an Available Date <AvailDt> and/or Expiration Date <ExpDt>. These two elements indicate to the client the window of time at which the response data is expected to be available. If the server does provide an asynchronous response, the client must send the exact same request, but with a new <RqUID>, providing the <RqUID> from the original request in the <AsyncRqUID> element, at a later time (generally within the availability window). The server then must respond with either the cached and built response, or another <AsyncRsInfo> indicating a new projected availability time. The server may choose to reject, with a <StatusCode> of 910 and <Severity> of Error, a subsequent asynchronous request if the elements provided by the client dont match the corresponding elements from the original request. Info status means that this status did not prevent the server from accepting message, service, or document. The status provided additional information related to the message, service, or document. Warn status means that this status did not prevent the server from accepting the message, service, or document; however, not all information may have been returned to the client. For example, too many records requested.
Version 1.7
April 2005
37
Interactive Financial Exchange Business Message Specification Error status means that the server declined the message, service, or document. The server may return a SPRefId and/or a CSPRefId, where present, for tracking purposes; however, the return of these elements are not guaranteed.
Tag
<StatusCode> <ServerStatusCode>
Type
Long C-20
Usage
Required Optional
Description
Response Status Code. Valid values depend on context. See Appendix A. Server Status Code. The value placed here is used to allow the client to display the status code to the user. This allows the user to read the code to a customer service representative for debugging purposes. Severity. Valid values: Error, Warn, Info
<Severity>
Closed Enum C-255
Required
<StatusDesc>
Optional
Status Description. Explanatory text associated with the status code. The Status Description may be default text or Service Provider specific. Additional statuses. The <StatusCode> above must contain the primary response code. This aggregate may appear once for each additional status that the server intends to provide. For example, if both an account number and a date are invalid, the <StatusCode> above may contain one of the two errors, and this aggregate may contain the other. Asynchronous Response Information.
<AdditionalStatus>
Optional Repeating
<AsyncRsInfo>
Optional
3.2.12.2 Additional Status Aggregate <AdditionalStatus>

Tag
<StatusCode> <ServerStatusCode>
Type
Long C-20
Usage
Optional Optional
Description
Response Status Code. Valid values depend on context. See Appendix A. Server Status Code. The value placed here is used to allow the client to display the status code to the user. This allows the user to read the code to a customer service representative for debugging purposes. Severity. Valid values: Error, Warn, Info
<Severity>
Closed Enum C-255
Required
<StatusDesc>
Optional
Status Description. Explanatory text associated with the status code. The Status Description may be default text or Service Provider specific.
3.2.12.3 Asynchronous Response Information Aggregate <AsyncRsInfo>

Tag
<AvailDt> <ExpDt>
Type
DateTime DateTime
Usage
Optional Optional
Description
Available DateTime. The projected time at which the response will be available. Expiration DateTime. The time at which the cached response will be purged at the server.
38
April 2005
Version 1.7
3.2.12.4 Records Control

Some response messages, typically associated with the inquiry/audit/sync request messages, may be quite large. The size of the response message may create problems for both the client and server. The problems are specific to the implementation. Some examples of these problems are: The client may not be able to allocate enough storage for the entire response. A network timeout may occur due to the time to return the complete HTTP response.
Mixing very large with small messages within the message manager (OLTP) middleware may create serious performance problems for the small messages. In order to address these potential problems, IFX allows either the client or server to constrain the size of a response message. The client initiates all IFX messages, so the server cannot push the additional information to the client. A mechanism is provided for the server to indicate that additional information is available and for the client to request the additional information The Record Control value within <OptSupt> in the Service Profile indicates whether a server supports this capability.
3.2.12.4.1 Records Control Input <RecCtrlIn>

The <RecCtrlIn> aggregate is used in inquiry/audit/sync request messages to allow the client to specify a maximum number of records that it is capable of processing within a single response. The initial request omits the <Cursor> element. Subsequent requests set the <Cursor> to the value returned by the server in the previous response (Rs) message. The <Cursor> value is meaningful to the server and opaque to the client. The <Cursor> is intended to be a pointer to a position within the answer set for the inquiry/audit/sync request. The client should send the same selection criteria in the initial and subsequent requests. The server may verify that the cursor returned is valid by comparing the search criteria on subsequent requests with the search criteria on the initial request. If they differ, the cursor may be considered invalid and an error returned. Similarly, if the time between the initial and subsequent requests is too long, the cursor may be rejected on the subsequent request. In this situation, the client may reinitiate the initial request.
Tag
<MaxRec> <Cursor>
Type
Long Binary
Usage
Description
Maximum Records Requested. Cursor Handle. Must be omitted in initial request. May be included in subsequent requests if server provided as a pointer to more records in previous <RecCtrlOut> in response.
3.2.12.4.2 Records Control Output <RecCtrlOut>

The <RecCtrlOut> aggregate is used in inquiry/audit/sync responses to provide a client that used the <RecCtrlIn> aggregate in the request with information it needs to retrieve the rest of the records that matched the specified selection criteria. The <RecCtrlOut> aggregate must be sent as part of the Rs if the server indicated support for Records Control in the Service Profile by setting <OptSupt> = RecCtrl and one or both of the following are true: The Rq contains an <RecCtrlIn> aggregate or The server is returning a subset of the available output records in an Rs.
Version 1.7
April 2005
39
Tag
<MatchedRec> <SentRec> <Cursor>
Type
Long Long Binary
Usage
Required Required Optional but see Description
Description
Matched Records. Total number of records matching the selection criteria. Sent Records. Number of records matching the selection criteria that are included in this message. Cursor. Included in the response only if additional records are available. When <Cursor> is present in the response, the Status code 1110 must be sent. Assume server retains cursor of matching records for some time in case client requests more. Used to allow the client to issue another request to fetch more matching records.
3.2.12.4.3 Example
Assume: The server sets <OptSupt>=RecCtrl in Banking section of Service Profile. The client issues an Account History message.
The client is capable of processing only process 10 records (history messages) within a single Rs. There are 25 messages in the answer set. Initial request from client:
<MaxRec>=10
Note that the <Cursor> element is omitted. Initial response:

<MatchedRec>=25 <SentRec>=10 <Cursor>=binary_value_1
Second request:
<MaxRec>=10 <Cursor>=binary_value_1
Second response:
<MatchedRec>=25 <SentRec>=10 <Cursor>=binary_value_2
Third request:
<MaxRec>=10 <Cursor>=binary_value_2
Third response:
<MatchedRec>=25 <SentRec>=5
<Cursor> element is omitted
3.2.12.5 Client Application <ClientApp> and Proxy Client <ProxyClient>

The primary use of the <ClientApp> aggregate is to inform a customer service representative about what software was used to create or change an object. <ClientApp> conveys the application that is acting as the client endpoint of the IFX message. This may be an application on the customers PC if it is aware of Interactive Financial Exchange, or it may be an intermediate server that is composing IFX requests on behalf of a client that has connected to it using some other protocol (e.g., HTTP).
40
April 2005
Version 1.7
Tag
<Org> <Name> <Version>
Type
Identifier C-40 NC-12
Usage
Required Required Required
Description
Organization. This identifies the client application manufacturer. Client Application Name. Client Application Version.
3.2.13
Industry Identifier Aggregate <IndustId>
The <IndustId> aggregate provides standard codes by which industries are classified. <IndustId> is used in payments and other messages as information for reporting and accounting by industry code.
Tag
<Org>
Type
Identifier
Usage
Required
Description
Organization. Identifies the organization assigning numbers to different industries. SIC identifies Standard Industrial Codes. NAICS identifies North American Industrial Code System.
<IndustNum>
NC-6
Required
Number identifying the industry.
3.2.14
Secrets Aggregates
3.2.14.1 Secret Prompt Aggregate <SecretPrompt>

The <SecretPrompt> aggregate is used to provide enough information to prompt a user for secrets used for initial authentication. For example, the server may request the users tax ID, mothers maiden name or some other secret already shared between the user and the service provider operating the server. The <SecretPrompt> may be used by CSPs during enrollment of customers for a specific service such as Bill Presentment. For example, a customer new to a specific biller may be authenticated against existing customer records at the biller. If omitted, the biller does not require the customer to enter any secrets for client enrollment. Another use is to prompt for a security token or password that has been provided to the customer by some other means, possibly during an interactive identity verification session with the customer.
Tag
<SecretId> <Prompt>
Type
Identifier C-20
Usage
Required Required
Description
The ID of this secret. The client must return the ID along with the secret itself in <SecretList>. Prompt. The short prompt to be displayed to the user, explaining the value to be returned in <SecretList> for this secret. Memo. This is a longer description of the meaning of <Prompt> above. This may be displayed to the user if the user requests more information regarding the intended meaning of <Prompt>. If True, the secret does not need to be provided in the <SecretList> sent to the server in order for the server to process the requested message. If False or omitted, the secret does need to be provided in the <SecretList> sent to the server in order for the server to process the requested message.
<Memo>
C-255
Optional
<SecretOptional>
Boolean
Optional
Version 1.7
April 2005
41
Tag
<SecretFormat>
Type
NC-1024
Usage
Optional
Description
Secret Format. Regular expression describing the secret format. The definition and behavior of Regular Expression is per IEEE Std 1003.2-1992 (POSIX.2). General definition may be found at http://www.ciser.cornell.edu/info/regex.html
<SecretMask>
C-80
Optional
Secret Mask. Edit Mask for the user input for <Secret> in <SecretList>. EditMask, in Section 3.1.1,specifies the format for <SecretMask>.
3.2.14.2 Secret List Aggregate <SecretList>

The <SecretList> aggregate provides a way for users to input shared secrets in response to a <SecretPrompt>.
Tag
<SecretId> <CryptType>
Type
Identifier Open Enum
Usage
Required Required Profiled values
Description
ID of Secret. The client must use the value of <SecretId> sent by the server in <SecretPrompt>. Encryption Type. Defined values: None, PKCS#1 , PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Must be supported in list of encryption types in the SPs Service Profile.
<SecObjId>
Identifier
Optional Repeating but see Description
Identifier of Security Object on which the <CryptSecret> is encrypted Note: If security objects are managed in band, this element should be included in order to know how to decrypt <CryptSecret> Secret. The secret itself as entered by the user in response to the <Prompt> and/or <Memo> displayed in <SecretPrompt>. <Secret> is used when <CryptType> = None
<Secret>
C-80
Required XOR
<CryptSecret>
Binary, 128
Required XOR
Encrypted Secret. Positional list of customer-entered data corresponding to each secret prompt provided through the <BillerRec> aggregate. Typical uses are mothers maiden name, tax id, etc. <CryptSecret> is used when <CryptType> None
3.2.15
Payment Instrument Aggregate <PmtInst>
The <PmtInst> aggregate is used to communicate the types of payment that the biller is capable of accepting via the Pay provider. This is used to restrict the methods by which the customer may pay for the bill. The Service Provider indicates which Payment Instruments are supported via the Biller profile in <BillerPayInfo>. The Biller may use the <PmtInst> in <BillRec> to provide a subset of the types of payments the Biller accepts for a particular bill. Note that errors may occur if this aggregate contains types of payments different from those communicated through the Biller Profile.
Tag
<PmtInstType>
Type
Closed Enum
Usage
Required
Description
Payment type. Specifies the type of payment instruments that the biller is capable of accepting for electronic payment. Valid values: CheckAcct, CreditCard, ElectronicCash
42
April 2005
Version 1.7
Tag
<Brand>
Type
Open Enum
Usage
Optional
Description
Accepted brand for a given payment type. If not specified, the client assumes that all brands of the given <PmtInstType> are acceptable. Defined values: AmEx, CarteBlanche, DinersClub, Discover, Europay, JCB, MasterCard.
<SettlementInfo>
Optional Repeating
Settlement Information. May contain complete or partial information for use by the CPP in transferring funds to the Biller or BPP. One or more options may be supported for each Payment instrument and brand.
3.2.15.1 Settlement Information <SettlementInfo>

The <SettlementInfo> aggregate is used to communicate the settlement instruction of payment to the CPP. This aggregate may contain complete or partial information for use by the CPP in transferring funds to the Biller or BPP.
Tag
<SettlementMethod>
Type
Open Enum
Usage
Required
Description
Settlement Method. Either the method accepted by the Biller or BPP for settling payments, or the payment/settlement method, provided as the general method for settling payment. Defined values: RPS, EPay, ACH, Concentrator, FedNet, SWIFT, CHIPS, CHAPS, BookEntry, Draft, OutsourcedCheck, DirDebACH
<DepAcctId>
Aggregate see section 3.2.7.2.2 C-20 Aggregate see section 3.2.5.2 Aggregate see section 3.2.3.9 C-255 Aggregate see section 3.2.15.2
Required OR Required OR Required OR
<SettlementId> <OrgContact>
Settlement Identification. May contain the RPS or Epay ID as applicable, depending on the Settlement Type. Organization Contact. The Billers Concentrators contact name and telephone number for the CPP to find out additional information needed to complete payments or for clarification. Contact Information Aggregate.
<ContactInfo>
Required OR Required OR Optional
<Memo> <PmtInstruction>
Additional human-readable information that may be needed to complete payments or for clarification. Detail payment and settlement instruction.
3.2.15.2 Payment and Settlement Instruction Aggregate <PmtInstruction>

Tag
<Country>
Type
NC-3
Usage
Optional
Description
Country. Country of the payment system in which the payment is processed.
Version 1.7
April 2005
43
Tag
<PmtFormat>
Type
Open Enum
Usage
Optional
Description
Payment format. Payment format for the specified payment method above. For example, in ACH electronic transfer, the format can be CTX, CCD, CCD+, PPD, etc. Reference information associated with payment information. Intermediary deposit account. Used to identify deposit accounts for intermediary banks that route the payment. Bank Fee Charge Allocation. Used to communicate the fee charges on the payment by the CPP. This specifies who and how the fee is being distributed between the Payer and the Payee.
<RefInfo>
Aggregate see section 3.2.17 Aggregate see section 3.2.7.2.2.1 Aggregate see section 3.2.15.3
Optional Repeating Optional Repeating Optional
<IntermediaryDepAcct>
<FeeChargeAlloc>
3.2.15.3 Fee Charge Allocation Aggregate <FeeChargeAlloc>

Tag
<ChargeRegulation>
Type
Open Enum
Usage
Required
Description
Specify how the fee is distributed. Defined Values: Payer, Payee, Share Equally.
<Fee>
Aggregate see section 3.2.16.2 Aggregate see section 3.2.7.2.2
Required
Fee Charge info and amount.
<DepAcctId>
Optional
Account from which the bank fee is drawn.
3.2.16
Fees and Amounts
Up to and including IFX 1.1, a fee was only allowed to be a currency amount. This is adequate for fees that are a fixed amount (e.g. surcharge fee of $1.50). For some transactions the associated fee is based on a percentage of the transaction amount or a combination of a fixed amount and a percentage. The following are some fee scenarios: fee is a fixed currency amount (e.g. surcharge fee of $1.50) fee is a percentage of the transaction amount (e.g. check cashing fee of 1% of the check amount) fee is a percentage of the transaction amount with a minimum (e.g. check cashing fee of 1% of the check amount, with a minimum fee of $2.00) fee is a percentage of the transaction amount with a maximum (e.g. check cashing fee of 1% of the check amount, with a maximum fee of $5.00) fee is a percentage of the transaction amount with a minimum and maximum (e.g. check cashing fee of 1% of the check amount, with a minimum fee of $2.00 and maximum fee of $5.00) fee is a fixed currency amount plus a percentage of the transaction amount (e.g. a $1.00 fee to cash a check plus 2% of the check amount) IFX 1.1 and earlier only allowed the first scenario. Starting with IFX 1.2, fees are permitted to be any of the five. Following are descriptions of which fields are necessary to describe each of those scenarios: fee is a fixed currency amount (e.g. surcharge fee of $1.50)
44
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification <CurAmt> = 1.50 fee is a percentage of the transaction amount (e.g. check cashing fee of 1% of the check amount) <Rate> = 1.00 fee is a percentage of the transaction amount with a minimum (e.g. check cashing fee of 1% of the check amount, with a minimum fee of $2.00) <Rate> = 1.00 <MinCurAmt> = 2.00 fee is a percentage of the transaction amount with a maximum (e.g. check cashing fee of 1% of the check amount, with a maximum fee of $5.00) <Rate> = 1.00 <MaxCurAmt> = 5.00 fee is a percentage of the transaction amount with a minimum and maximum (e.g. check cashing fee of 1% of the check amount, with a minimum fee of $2.00 and maximum fee of $5.00) <Rate> = 1.00 <MinCurAmt> = 2.00 <MaxCurAmt> = 5.00 fee is a fixed currency amount plus a percentage of the transaction amount (e.g. a $1.00 fee to cash a check plus 2% of the check amount) <CurAmt> = 1.00 <Rate> = 2.00
3.2.16.1 Composite Currency Amount <CompositeCurAmt>

The Composite Currency Amount aggregate <CompositeCurAmt> contains information about the amount and timing of float availability of funds for a single transaction. This aggregate is also used (usually repeating) where a currency amount identified in a message consists of multiple composites, e.g. a debit message which identifies both the customer requested debit amount plus one or more fees to be debited. The composite currency amount aggregate can also be used within a <DebitAdd> or <ChkAcceptAdd> to charge a fee (e.g. for a printed statement). The <CompositeCurAmtId> is used to identify a specific component of a currency amount in communications between client and server (e.g. to override a specific Fee component).
Tag
<CompositeCurAmtId>
Type
Identifier
Usage
Optional but see Description Required
Description
Composite Currency Amount Id. Required if the aggregate is repeating within a debit or credit message. Composite Currency Amount Type. Description of Float Category or Currency Amount Type. Defined Values: Immediate, 1DayFloat, 2DayFloat, 3DayFloat, 4DayFloat, 5DayFloat, 6DayFloat, OnePlusDay, TwoPlusDay, ThreePlusDay, Standard, Debit, Credit, ForExFee, StopChkFee, LateFee, TransactionFee, InterchangeFee, Surcharge, StatementFee, Tax, MerchandisePurchase, MerchandiseReturn, CheckFee, PmtEnclosed, CashBack, CreditHeld.
<CompositeCurAmtType>
Open Enum
Version 1.7
April 2005
45
Tag
<CurAmt>
Type
Currency Amount
Usage
Required OR
Description
Currency Amount. When used for float, the fractional amount of the transaction amount assigned to this float category. When used for a fixed amount fee, this is the fixed amount that will be charged. For fees that are calculated as a fixed amount plus a percentage of the transaction, this is the fixed amount and the percentage is in Rate. Fee Rate. Usage is a percentage (e.g. a value of 2.5 = 2.5%). Minimum Currency Amount. The minimum amount to charge for this fee. Maximum Currency Amount. The maximum amount to charge for this fee. Special Handling requests. Defined Values: ClientOverride
<Rate>
Decimal
Required OR 1.2+ Optional Optional Optional
<MinCurAmt> <MaxCurAmt> <SpecialHandling>
Currency Amount Currency Amount Open Enum
<Memo>
C-255
Optional
Memo. Additional information about the transaction (e.g. reason for modifying the fees)
3.2.16.2 Fee <Fee>

The <Fee> aggregate identifies the type and amount of fee being charged.
Tag
<FeeType>
Type
Open Enum
Usage
Required
Description
Fee Type. Defined values: ForEx, StopChk, Late, Transaction, Interchange, Surcharge
<CurAmt>
Currency Amount
Required OR
Currency Amount. When used for a fixed amount fee, this is the fixed amount that will be charged. For fees that are calculated as a fixed amount plus a percentage of the transaction, this is the fixed amount and the percentage is in Rate. Fee Rate. Usage is a percentage (e.g. a value of 2.5 = 2.5%). Minimum Currency Amount. The minimum amount to charge for this fee. Maximum Currency Amount. The maximum amount to charge for this fee.
<Rate> <MinCurAmt> <MaxCurAmt>
Decimal Currency Amount Currency Amount
Required OR Optional Optional
3.2.16.3 Tax Information <TaxInfo>

The <TaxInfo> aggregate identifies a levied tax.
Tag
<Org> <TaxType>
Type
Usage
Required Required
Description
Organization. Organization defining this name space. Usage is Tax Authority (e.g., state or country). Tax Type. Qualified by <Org>. Defined values: WithHoldingTax, DebitsTax, FIDuty
<CurAmt> <Rate>
Currency Amount Decimal
Tax Amount (+ paid by customer, earned by customer). Tax Rate. Usage is a percentage (e.g., a value of 5.2 = 5.2%). (+ paid by customer, earned by customer)
46
April 2005
Version 1.7
3.2.17
Reference Information <RefInfo>
The <RefInfo> aggregate provides information typically related to an IFX object. It is generally expected that the reference information is to be used by the message recipient to relate information within the associated IFX object with other data obtained via a different channel.
Tag
<RefType> <RefId>
Type
Open Enum Identifier
Usage
Required Required
Description
Reference Type. Description of the type of Reference Id. Defined Values depend on the specific usage. Reference Identifier.
3.2.18
Network Transaction Information Aggregate <NetworkTrnInfo>
The Network Transaction Information aggregate <NetworkTrnInfo> contains information regarding the network processing the transaction, i.e., owner, location, bank ID and reference number assigned by the network when processing the transaction. Information in this aggregate is also used for providing the physical location of an automated terminal at which a customer conducts a transaction. The physical location information may be required to be printed on statements and receipts for regulatory purposes. Note: This aggregate is used in IFX 1.1 and later versions as a replacement for the <ATMTrnInfo> and <USA.ACHTrnInfo> aggregates within the <DepAcctTrnRec> aggregate. The <ATMTrnInfo> and <USA.ACHTrnInfo> aggregates will be deprecated in IFX 2.0.
Tag
<NetworkOwner>
Type
Open Enum
Usage
Required
Description
Network Owner. The name of the individual or organization that owns the source network. Defined Values: ATM, POS, ACH, FedNet, SWIFT, Branch, CallCenter, Other
<OriginatorName> <OriginatorType>
C-40 Long
Optional Optional
Name. Name of originator of the Message. The type of organization that the originator represents. This is usually a coded value representing the industry that the organization operates in. It contains the SIC code or other nationally defined industry value. Terminal Identifier. Identification of terminal, such as terminal code or terminal number of ATM. Required if <NetworkOwner> is ATM. Defined values: AdminTerm, ATM, POS, CustomerDevice, ECR, DialCash, TravelerCheckDispenser, FuelPump, ScripTerm, CouponTerm, TicketTerm, POBTerm, Teller, Utility, Vending, Payment, VRU Postal Address. Physical Address of the terminal. At least one of <PostAddr>, <Desc> and <Name> is required if <NetworkOwner> is ATM. Description. A generally accepted name for the location of the terminal. At least one of <PostAddr>, <Desc> and <Name> is required if <NetworkOwner> is ATM. Name. Name of the owner or operator of the terminal. At least one of <PostAddr>, <Desc> and <Name> is required if <NetworkOwner> is ATM.
<TerminalId>
Identifier
<TerminalType>
Open Enum
<PostAddr>
Optional OR but see Description Optional OR
<Desc>
but see Description

<Name> C-40 Optional OR but see Description
Version 1.7
April 2005
47
Tag
<BankIdType>
Type
Open Enum
Usage
Optional
Description
Bank Identifier Type. Type of bank identifier. Defined Values: SWIFT, ABA, FedWire, CHIP, CHAP, SortCode. Default value is ABA.
<BankId>
NC-34
Bank Identifier. Qualifies account number if known by the customer/client. Usage is expected to be routing and transit number in the US or the equivalent in an international implementation. This is required in USA when <NetworkOwner> is ACH. Network Reference Identifier. Reference number assigned by network due to the processing of a message at the respective network. Example: Federal Reserve wire network assigns a Fed Reference Number or ACH trace number. or an ISO retrieval reference number.
<NetworkRefId>
Identifier
Optional
3.2.19
Identifier Characteristics Data Aggregate <IdentCharacterData>
The Identifier Characteristics Data aggregate describes the identification device that the customer presented to the transaction acquirer. The identification device typically will be a card or similar device that represents one or more of the customers accounts.
Tag
<IdentType>
Type
Open Enum
Usage
Required
Description
The type of identification presented or inferred by the customer. Unknown, MagStripeCard, ICCCard
<ExpDt>
DateTime
Optional
The date/time that the identification device will expire or otherwise become ineffective. Use of the identification device after this date/time will normally not be allowed. The date/time that the identification device became or will become effective. Use of the identification device before this date/time will normally not be allowed. The date/time that identification was first issued to the customer that is presenting this device. This will normally represent a customer since or similar concept. The identifier of the program that the identification device belongs to. This is a detailed classification of the identification by line of business. It is intended to support special processing of specific customer classes. Servers should ignore this field unless they have a specific agreement with the identification device acceptor that specifies special processing. The actual method used to read the customers identification device. Valid values: Manual, BarCode, MagStripe, OCR, ICC, Customer.
<StartDt>
DateTime
Optional
<OrigIssueDt>
DateTime
Optional
<IdentProgramId>
Identifier
Optional
<IdentReadMethod>
Open Enum
Optional Repeating
48
April 2005
Version 1.7
Tag
<IdentPrevReadMethod>
Type
Open Enum
Usage
Optional Repeating
Description
The actual method used by the device to read the previously used customers identification device (card). The IFX client should be able to keep track of the previous read method in order to support this functionality. Valid values: Manual, BarCode, MagStripe, OCR, ICC, Customer.
<IdentServiceCode>
C-3
Optional
The Service Code read from the customers identification device, as defined by ISO 7813. This Service Code comes from the chip (Integrated Circuit - IC) on the card, if the chip is present on the card and it could be successfully read; otherwise, this Service Code will come from the magnetic stripe present on the card.
<IdentPrevServiceCode>
C-3
Optional
The Service Code read from the previously used customers identification device, as defined by ISO 7813. The IFX client should be able to keep track of the previous service code in order to support this functionality. This Service Code comes from the chip (Integrated Circuit - IC) on the card, if the chip is present on the card and it could be successfully read; otherwise, this Service Code will come from the magnetic stripe present on the card.
<IdentVerifyMethod>
Open Enum
Optional Repeating
The actual method used to verify the customers authority to use the presented identification device. Valid values: Unknown, None, Signature, PictureID, OnlinePIN, OfflinePIN, DigitizedSignature, Biometrics, ICCSignature, Certificate, AddressVerification, TelephoneNumberVerification, PersonalInfoVerification.
<IdentVerifyEntity>
Open Enum
Optional Repeating
The entity that verified the customers authority to use the presented identification device. Valid values: Unknown, NotAuthenticated, Acceptor, Intermediary, Authorizer, ICC, CAD
<IdentConditions>
Open Enum
Optional Repeating
Any identified conditions detected by the transaction acquirer related to the customers presentation of the identification device. Valid values: None, CustomerNotPresent, CardNotPresent, PreauthorizedTransaction, Telephone, MailOrder, IdentVerifyUnavailable, SecurityAlert, MerchantSuspicious, SuspectedFraud
<IdentVerifyResults>
Open Enum
Optional Repeating
The results of the application of the identity verify method(s). Valid values: CVVValid, CVVInvalid, PINValid, PINInvalid, SignatureValid, SignatureInvalid,
3.2.20
Point of Service Security Aggregate <POSSecurity>
The Point of Service Security aggregate provides information about the security policies imposed by the transaction acquirer. An account owner or intermediary can use the security policies can be used to judge the likelihood that a transaction has been compromised.
Version 1.7
April 2005
49
Tag
<PSSNetworkType>
Type
Open Enum
Usage
Optional
Description
The type of network that the document passed through between the transaction initiator and the account owner. When a document passes through several networks this field should reflect the most exposed (least private) communication segment. Valid values: Unknown, Private, VirtualPrivate, SemiPublic, Public Default value: Private
<PSSMsgMAC>
Open Enum
The type of MAC processing performed on the document. Valid values: None, Channel, PassThrough The type of encryption performed on the document. Valid values: None, Channel, EndToEnd The CAT security level defines the security level of a CAT (cardholder activated terminal) device. Valid values: PIN, SST, LMT, IFC
<PSSMsgEncryption>
Open Enum
<PSSCATSecLevel>
Open Enum
3.2.21
Point of Service Capabilities Aggregate <POSCapabilities>
The Point of Service Capabilities aggregate provides information about the transaction processing capabilities of the transaction acquirer.
Tag
<POSAttended> <POSOperation> <POSEntryCapability> <POSCaptureCapability> <POSVerifyCapability>
Type
Boolean Open Enum Open Enum Boolean Open Enum
Usage
Optional Optional Repeating Optional Repeating Optional Optional Repeating
Description
An agent of the card acceptor attends the service device. Default is false. Valid values: CustomerOperated, AcceptorOperated, AdministratorOperated, ScheduleOperated Valid values: Unknown, Manual, MagStripe, BarCode, OCR, ICC, Customer. The service provider can capture the identification device. Default is false. Valid values: Unknown, None, Signature, PictureID, OnlinePIN, OfflinePIN, DigitizedSignature, Biometrics, ICCSignature, Certificate, AddressVerification, TelephoneNumberVerification, PersonalInfoVerification. Valid values: None, TrackRewrite, ICCUpdate
<POSOutCapabilities>
Open Enum
Optional Repeating
3.2.22
Point of Service Agent Aggregate <POSAgent>
The Point of Service Agent aggregate provides information about the agent or employee of the transaction acquirer that assisted the customer in processing the transaction. This aggregate is used for acceptor operated devices.
50
April 2005
Version 1.7
Tag
<AgentType>
Type
Open Enum
Usage
Optional
Description
The type of agent that assisted the customer creating this message. Valid values: Unknown, Clerk, Manager, IndependentAgent, AuthorizedAgent Default value: Clerk
<AgentId>
Identifier
Optional
The identification of the agent of the card acceptor that attended the service device while this message was created. This will usually be the Id of a clerk or similar employee of the card acceptor.
3.2.23
Point of Service Data Aggregate <PointOfServiceData>
The Point of Service Data aggregate provides information about the environment, capabilities and policies of the transaction acquirer. An account owner or intermediary can use the information in this aggregate to determine the type of transaction the customer is trying to perform and the environment it is being performed under. It also contains conditions that the transaction acquirer detected concerting the customers use of its facilities.
Tag
<Environment>
Type
Open Enum
Usage
Required
Description
The environment that this customer interaction occurred under. Valid values: Unknown, Mail, Telephone, ECommerce, MCommerce, Recurring, StoredData, POS, CAT, ATM, Deferred, Installment
<POSCapabilities>
Aggregate see section 3.2.21 Aggregate see section 3.2.20 Aggregate see section 3.2.22 Aggregate see section 3.2.19 Open Enum Identifier
Optional
Transaction acceptor point of service capabilities.
<POSSecurity>
Optional
Transaction acceptor point of service security features.
<POSAgent>
Optional
Transaction acceptor agent (clerk) information.
<IdentCharacterData>
Optional
Customer identification device characteristics.
<POSLocation> <PostingSessionId>
Optional Optional
Valid values: Unknown, OnPremise, OffPremise, Retail, Customer, Agent, Branch, CallCenter Posting Session Identifier. Unique identifier on the server indicating which posting session parameters should be used for this transaction and where any server-maintained session totals should be updated.
3.2.24
Tag
Card Logical Data Aggregate <CardLogicalData>

Type
NC-64
Usage
Required
Description
The primary card number or PAN number. The account or card number embossed on the card.
<CardEmbossNum>
Version 1.7
April 2005
51
Tag
<CardSeqNum> <Brand>
Type
NC-16 Open Enum
Usage
Optional Optional
Description
The sequence (plastic) number of this card. The number further qualifies the embossed number to distinguish cards with a common account relationship. The name that identifies the type of card presented. It will typically be the name of the association or company that authorized the issuance of the card. Defined Values: AmEx The American Express Company, CarteBlanche Carte Blanche, CarteBancaire Carte Bancaire, DinersClub Diners Club International, Discover Dean Witter, Discover & Co, Europay (formerly Eurocheque International), JCB JCB International, MasterCard MasterCard International, VISA VISA USA or VISA International
<IssuerName> <Technology>
C-80 Open Enum
Optional Optional
Description. The name of the card. eg., Sears, Hudsons Bay Co. The type of card presented or inferred by the customer. Valid values: MagStripeCard, ICCCard
<IssDt>
Date
Optional
Card Issue Date for non FI issued cards only. If it is an FI issued card, this information should be included in the <IdentCharacterData>. Expiration date for card. If the card has only month and year expiration, the last day of the month must be specified here. Card verification data. This field contains data printed on the card that is manually entered. This is data that cannot be automatically read from a card as it is used. This data is used to ensure the physical presence of the actual card. Customer Name. Name on the front of this card (exactly as name appears on the card). Card (customer) service phone number.
<ExpDt>
DateTime
Optional
<CardVrfyData>
C-16
Optional
<Name> <CSPhoneNum>
C-40 Phone Number
Optional Optional
3.2.25
Tag
Passport
Type
C-32 NC-3 C-18 Datetime Datetime
This aggregate will support all passport information.

Usage
Required Required Optional Optional Optional
Description
The serial number of the identification provided by the customer. The 3 character ISO code for the country where the passport was issued. Passport issue location. This may be a foreign embassy. Passport issue date. Passport expiry date.
<Passport Number> <Passport Country> <IssueLoc> <IssDt> <ExpDt>
52
April 2005
Version 1.7
3.2.26
Tag
Passbook Acceptance Data <PassbkAcceptData>

Type
Identifier Aggregate see section 6.3.40.3
This aggregate will support all passbooks issued by a financial institution.

Usage
Required XOR Required XOR
Description
Passbook Identifier Passbook Information Aggregate
<PassbkId> <PassbkInfo>
3.2.27
Personal Identification <PersonalIdent>
This aggregate will support all personal identification that is recorded as part of the identification process.
Tag
<AccountHolder>
Type
Boolean
Usage
Required
Description
True customer has one or more accounts with this FI. False customer does not have any accounts with this FI.
<PersonVerifyType>
Open Enum
Required XOR
Personal Verify Type. This element will contain the type of information that was used to authenticate the customer. It will be used if the customer was verified, by the teller, through private information that is stored on the database or if the identification presented to the teller was viewed but not recorded. Valid values: PrivateInfo, TINInfo, EmploymentData, Passport, GovIssueData, OtherIdent
<PersonInfo>
Required XOR
Person Information Aggregate. This element will be used if the details of the piece of identification, used to authenticate the customer, need to be recorded.
Version 1.7
April 2005
53
3.2.28
Tag
GovIssueIdent
Type
Open Enum
Usage
Required
Description
Government Issued Identification.Valid Values: DriversLicense BirthCertificate HealthCard MilitaryIdent PermResIdent GovEmpIdent RetirementIdent VoterRegIdent
<GovIssueIdentType>
<IdentSerialNum> <GovOrg>
NC-32 Open Enum
Required Required
Identification serial number The level of government that issued the identification. Valid values: Country, State, Province, Municipal, County
<GovOrgName>
C-80
Optional
The name of the government organization that issued the identification, e.g., Air Force, Army, Health Ministry, Motor Vehicle. Government Rank. Used if type is Military. State/Province. The State or Province the Id was issued. Country. The Country the Id was issued. A description of the identification if it is not clear by the IdentVerifyType. Identification issue date. Identification expiry date.
<GovRank> <StateProv> <Country> <Desc> <IssDt> <ExpDt>
C-32 C-32 NC-3 C-80 Datetime Datetime
Optional Optional Optional Optional Optional Optional
3.2.29
Tag
EmploymentData
Type
Aggregate see section 2.2.6 Aggregate see section 3.2.4.1.4
Usage
Optional
Description
Employer Identification. This aggregate includes the Employer Name and the Employee Id. It is used for identifciation purposes. Employment History Aggregate. This will become a subaggregate of Employment Data in IFX 2.0.
<EmployeeIdent>
<EmploymentHistory>
Optional XOR Repeating
54
April 2005
Version 1.7
3.2.30
Tag
EmployeeIdent
Type
C-80 C-80 NC-32 C-80 Datetime Datetime
Usage
Optional Optional Required Optional Optional Optional
Description
Employer Name. A description of the type of identification. eg. Picture ID employee card. Employee identification number The location where the identification was issued. Identification issue date Identification expiry date
<EmployerName> <Desc> <EmployeeIdentlNum> <IssueLoc> <IssDt> <ExpDt>
3.2.31
Tag
<Desc>
OtherIdentDoc
Type
C-80 NC-32 NC-32 C-80 Datetime Datetime
Usage
Required Required Required Optional Optional Optional
Description
A description of the identification Identification serial number The name of the identification issuer The location where the identification was issued. Identification issue date Identification expiry date
<IdentSerialNum> <Issuer> <IssueLoc> <IssDt> <ExpDt>
Version 1.7
April 2005
55
4 Security
4.1Channel Level Security vs. Application Level Security
The IFX Specification is designed to provide messages and data elements necessary to provide Application Level Security on top of an existing secure communications channel between the client and server. This Channel Level Security is not specified in this document, which is intentionally transport-independent. The mechanism used to provide this secure communications channel will be specified in each of the IFX Implementation Specifications associated with this document.
4.2Application Level Security in the IFX Specification

The IFX Specification supports a Customer Login ID and Password for each Signon Realm that the customer must access for their services. Each Signon Realm may have different rules regarding Customer Password length and composition; the rules may be found in the <SignonInfo> aggregate returned to the client in the <xxxSvcProfInfo>. Each CSP may also independently set its requirements for Customer Password Encryption. Note: At present, The IFX Specification supports several values for encryption of passwords and other authentication information. The first defined value is NONE, which relies entirely on channel level security and sends passwords as clear text. The other defined values enable a password or similar authentication information (up to 117 bytes) to be encrypted by the client or server and passed as a 128-byte binary element that may be decrypted by the receiver. Encryption keys can be generated with a 1024-bit modulus and distributed in an "out of band" process. Alternatively, with the use of the Security Object, encryption keys can be generated and distributed in an "in-band" process. Once a client authenticates with a CSP, the client may perform messages for any of the Services enabled by the CSP. If the client wishes to perform a message from a Service that has not been enabled for the current CSP, the client must authenticate with the CSP for which the desired Service has been enabled.
4.3Security Common Elements and Aggregates

4.3.1Customer Password Aggregate <CustPswd>
Tag
<CryptType>
Type
Open Enum
Usage
Required Profiled values
Description
Encryption Type. Defined values: None, PKCS#1. , PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Must be supported in list of encryption types in <SignonInfo> in the CSPs Service Profile.
<SecObjId>
Identifier
Identifier of Security Object on which the <CryptPswd> is encrypted Note: If security objects are managed in band, this element should be included in order to know how to decrypt <CryptPswd> Clear text Password. Used only when <CryptType> = None
<Pswd>
C-32
Required XOR
Version 1.7
April 2005
Tag
<CryptPswd>
Type
Binary, 128
Usage
Required XOR
Description
Encrypted Password. Used when <CryptType> None.
4.3.2Signon Password Aggregate <SignonPswd>

Tag
<SignonRole>
Type
Open Enum
Usage
Optional
Description
Signon role. Defined values: Customer, CSR, Agent, Teller Default value is Customer
<CustId>
Aggregate see section 3.2.3.1 Aggregate see section 4.3.1 Boolean
Required
Customer Identification Aggregate. This is the identifier of the user signing on. Customer Password Aggregate.
<CustPswd>
Required
<GenSessKey>
Optional
Session Key Requested Indicator. True indicates that the client is requesting a Session Key in the response. False or absent indicates that the client is not requesting a Session Key in the response.
4.3.3Signon Certificate Aggregate <SignonCert>

Tag
<SignonRole>
Type
Open Enum
Usage
Optional
Description
<CustId>
Aggregate see section 3.2.3.1 Binary Boolean
Required
Customer Identification Aggregate. This is the identifier of the user signing on.
<Certificate> <GenSessKey>
Required Optional Session Key Requested Indicator. True indicates that the client is requesting a Session Key in the response. False or absent indicates that the client is not requesting a Session Key in the response.
4.3.4Signon Transport Aggregate <SignonTransport>

Tag
<SignonRole>
Type
Open Enum
Usage
Optional
Description
<CustId>
Required
Customer Identification Aggregate. This is the identifier of the user signing on.
April 2005
Version 1.7
Tag
<GenSessKey>
Type
Boolean
Usage
Optional
Description
Session Key Requested Indicator. True indicates that the client is requesting a Session Key in the response. False or absent indicates that the client is not requesting a Session Key in the response.
4.3.5Signon Magnetic Stripe/PIN Aggregate <SignonMagPIN>

Tag
<SignonRole>
Type
Open Enum
Usage
Optional
Description
<CardMagData>
Aggregate see section 3.2.7.2.4.1 Open Enum
Required
Card Magnetic Stripe Data
<CryptType>
Encryption Type. <CryptType> will be required in IFX 2.0. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Must be supported in list of encryption types in <SignonInfo> in the CSPs Service Profile. Note: If security objects are managed in band, this element should be included in order to know how to decrypt <PINBlock>
<PINBlock> <SecObjId>
NC-32 Identifier
Required Optional Repeating but see Description
PIN pad data Identifier of Security Object on which the <PINBlock> is encrypted. <SecObjId> will be required in IFX 2.0 Note: If security objects are managed in band, this element should be included in order to know how to decrypt <PINBlock> Session Key Requested Indicator. True indicates that the client is requesting a Session Key in the response. False or absent indicates that the client is not requesting a Session Key in the response.
<GenSessKey>
Boolean
Optional
4.3.6Session Key <SessKey>

As an option, a client may request that the server generate and return a Session Key <SessKey> during a <SignonRq>. A Session Key may have an associated Expiration DateTime, after which it may not be used. If a client has a Session Key that has not expired, it may use the <SessKey> in subsequent <SignonRq>s. This mechanism addresses several requirements: It allows a server to efficiently process multiple <SignonRq>s from the same client over a relatively short time period. A batch-oriented client may group messages into a number of batches so that the results of the preceding batch are known when the next is submitted. The <SignonRq> in the first batch must contain a <CustId> and/or any other required authentication information. The <SignonRq> within subsequent batches may then contain the <SessKey> returned by the first <SignonRs>, in lieu of other authentication mechanisms. It allows a server to efficiently process multiple <SignonRq>s for the same user, but not necessarily the same client, over a short period of time. For example, a PFM client may invoke a web browser to support a CSP function that is not directly supported by the PFM client. The PFM
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification client may use the <SessKey> obtained from the <SignonRs> to issue a <SignonRq> for the web browser session. A batch or interactive client may process multiple Services with different Service Providers; e.g., VRU sends Pay messages to a different SP than Banking. The CSP and other SPs have a shared authentication mechanism. The client may use the <SessKey> obtained from the <SignonRs> from the CSP as part of the <SignonRq> to the other SPs, rather than having to either store the user password or prompt the user to enter his/her password a second time. A Session Key does not include the credentials of the entity specified in the <SignonOverride> aggregate.
Tag
<SessKey>
Type
NC-64
Usage
Description
Session Key.
4.4Authentication
4.4.1Description
Customer Authentication Messages are used to authenticate customers and address security at the application level. The Authentication messages are the only IFX messages without <RqUID>s, as there may be only one per IFX document.
4.4.2Signon
The Signon message is used to authenticate an IFX client. Unlike other IFX messages, the <SignonRs> does not echo all elements of the request, for security reasons. Also, because there must be only one <SignonRq> per IFX block, there is no <RqUID> in either the request or the response. If none of the optional signon methods are provided, the signon is anonymous. Customer authentication is between the IFX client and the IFX server. Other providers behind the IFX server are expected to rely on the authentication performed by the initial IFX server (note this does not apply if the client is redirected, or handed off, to another CSP). Intermediate elements, such as HTTP proxies, do not participate in the customer authentication exchange. The IFX server may rely on a different server to actually verify the customer password, but this is a local matter. Note: Signon and Signoff are the only two messages to occur at the top level of IFX, rather than being contained within a service wrapper.
4.4.2.1 Request <SignonRq>

Tag
<SignonPswd>
Type
Aggregate see section 4.3.2 Aggregate see section 4.3.3 Aggregate see section 4.3.4 Aggregate see section 4.3.5
Usage
Optional XOR Optional XOR Optional XOR Optional XOR
Description
Signon with <CustId>/<CustPswd> authentication method.
<SignonCert>
Signon with embedded certificate.
<SignonTransport>
Signon with transport certificate (i.e., SSL) authentication method. Signon with a magnetic stripe card and a PIN pad
<SignonMagPIN>
April 2005
Version 1.7
Tag
<SignonICC>
Type
Usage
Optional XOR
Description
Signon with an Integrated Circuit Card, where the card does not contain a magnetic stripe or where the primary account number from the chip rather than the magnetic stripe is used for calculating the PINBlock or where the card verifies the PINBlock. Authentication Key. Issued previously based on Password. Valid only for a fixed interval, as set by the server. Signon with a magnetic stripe card and a PIN pad
<SessKey> <SignonMagPIN>
NC-64 Aggregate see section 4.3.5 Aggregate see section 3.2.2.8
Optional XOR Optional XOR Optional XOR
<SignonICC>
Signon with an Integrated Circuit Card, where the card does not contain a magnetic stripe or where the primary account number from the chip rather than the magnetic stripe is used for calculating the PINBlock or where the card verifies the PINBlock. Authentication Key. Issued previously based on Password. Valid only for a fixed interval, as set by the server. Signon with a magnetic stripe card and a PIN pad
<SessKey> <SignonMagPIN>
NC-64 Aggregate see section 4.3.5 NC-64 Aggregate see section 4.4.2.1.1 DateTime
<SessKey> <SignonOverride>
Authentication Key. Issued previously based on Password. Valid only for a fixed interval, as set by the server. Authentication used for overriding functions that could not normally be performed by the signed on user. Client DateTime. Time according to the client.
<ClientDt>
Required
Note: This is typically used by customer service to resolve problems regarding cut-off time or timeliness of customer messages. It may be compared with the server time to determine whether there is a discrepancy.
<CustLangPref> NC-17 Required Profiled values The Client Language Preference has the same valid values as all other language elements. See section 2.6.4 for more information on the format of this element. Must be one of those supported in the Service Profile. <ClientApp> Aggregate see section 3.2.12.5 Aggregate see section 3.2.12.5 Required Client Application Aggregate. Manufacture, name, and version of the client endpoint of the IFX message. Proxy Client Aggregate. In the case where the IFX client is composing requests for some other application that the user is running (e.g., a Web browser), the details of the customers interface application should be included here. It has the same structure as the <ClientApp> aggregate. Euro currency selection. Used only in countries supporting the euro currency. Valid Values: Local, Euro. <SuppressEcho> Boolean Optional Profiled support If True, the client requests echoed fields to not appear in responses. If False or absent, the client requests echoed fields to appear in responses. The SP may choose to not honor the request and therefore send echoed fields in responses.
<ProxyClient>
Optional
<EU.Cur>
Closed Enum
Optional
Version 1.7
April 2005
4.4.2.1.1 SignonOverride <SignonOverride>

Tag
<OverrideType>
Type
Open Enum
Usage
Required
Description
Type of override being performed. Defined values: Clerk, Agent, Teller, Supervisor, Manager
<SignonPswd>
Aggregate see section 4.3.2 Aggregate see section 4.3.3 Aggregate see section 4.3.5
Required XOR Required XOR Required XOR
Signon with <CustId>/<CustPswd> authentication method.
<SignonCert>
Signon with embedded certificate.
<SignonMagPIN>
Signon with a magnetic stripe card and a PIN block.
4.4.2.2 Response <SignonRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 Open Enum Aggregate see section 3.2.3.1
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Signon role. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued.
<SignonRole> <CustId>
Optional Echoed Optional Echoed
Note: In cases where <Status> <Severity> is Error, echoing <CustId> is optional.

<GenSessKey> <ClientDt> <CustLangPref> <ClientApp> Boolean DateTime NC-17 Aggregate see section 3.2.12.5 Aggregate see section 3.2.12.5 Closed Enum DateTime NC-64 Optional Echoed Required Echoed Required Echoed Required Echoed Optional Echoed Optional Echoed Required Optional User Key Requested Indicator. Client DateTime. Customer Language Preference Aggregate. Client Application Aggregate.
<ProxyClient>
Proxy Client Aggregate.
<EU.Cur> <ServerDt> <SessKey>
Euro Currency Selection. Server DateTime. System time according to the server. Session Key. Included only at client request in <SignonRq>.
<ExpDt>
DateTime
Optional
Session Key Expiration DateTime. Included only if <SessKey> is returned.
April 2005
Version 1.7
Tag
<Language>
Type
NC-17
Usage
Required
Description
Language. See section 2.6.4 for more information on the format of this element. May or may not be the same as the Customer Preferred Language in <SignonRq>.
4.4.3Signoff
A client that has no further messages to perform should send a <SignoffRq> to indicate to the CSP that no more messages will be sent in this session and server resources may be freed and reallocated to other customers. The client may begin another session whenever it has new messages to perform by using the <SignonRq>. Because there may be only one <SignoffRq> per IFX block, there is no <RqUID> in either the request or the response. Note: Signon and Signoff are the only two messages to occur at the top level of IFX, rather than being contained within a service wrapper.
4.4.3.1 Request <SignoffRq>

Tag
<CustId>
Type
Usage
Optional
Description
Customer ID. Provided only in the case where a CSR is forcing a Signoff of a customer.
4.4.3.2 Response <SignoffRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Customer ID.
<CustId>
Optional Echoed
Version 1.7
April 2005
5 The Base Service <BaseSvc>

The Base Service in IFX includes messages that perform basic communication functions that must take place between parties (client and server or between different service providers). These messages are grouped into functions including Service Profile, Customer Authentication, Customer Profile, General Email, and Customer Service. IFX uses Service Profile messages to communicate information about a Service Providers services and configuration to a client. Customer Profile Messages provide for the registration of Customers with Service Providers, and the maintenance of that information. Customer Service messages provide administrative functions to assist Customer Service Representatives in serving customers.
5.1Base Service Message Summary

Function / Message Name Service Profile Inquiry
<SvcProfInqRq> <SvcProfInqRs>
Requi red
Yes
Comments
Allows the client to retrieve a current view of the services supported by the SP, the Authentication Realms that must be used for authentication, and basic information about the SP. Allows a client to retrieve a list of Bank Holidays observed by the Service Provider.
Holiday Inquiry
<HolInqRq> <HolInqRs>
Customer Add
<CustAddRq> <CustAddRs>
Allows client to provide customer personal details and indicate desire to use IFX Specification to communicate with a Financial Institution. SP may respond with Customer Login ID and Password or may provide these to the customer through another channel. Allows client to modify previously provided customer name, address, and contact information.
Customer Modify
<CustModRq> <CustModRs>
Customer Password Modify

<CustPswdModRq> <CustPswdModRs>
Allows a client to modify a Customer Password.
Note: this message will be deprecated in IFX 2.0, replaced by the Customer Authentication Modify message.
Allows a client to modify a customers authentication credentials.
Customer Authentication Modify

<CustAuthModRq> <CustAuthModRs>
Note: this message replaces the Customer Password Modify message, which will be deprecated in IFX 2.0
Allows a client to reverse a previous customer authentication modification The Customer Status Modify Message is used primarily by CSRs to reset the status and counters that were set when a user exceeded the invalid password threshold. Allows client to unenroll, deleting previously provided customer name, address, and contact information.
Customer Authentication Reversal

<CustAuthRev>
Customer Status Modify

<CustStatusModRq> <CustStatusModRs>
Customer Delete
<CustDelRq> <CustDelRs>
Version 1.7
April 2005
Function / Message Name Customer Inquiry

<CustInqRq> <CustInqRs>
Requi red
Comments
Allows client to retrieve current customer profile, including customer name, address, and contact information.
Customer Identifier Inquiry

<CustIdInqRq> <CustIdInqRs>
Allows client to retrieve either the login id corresponding to a permanent id, or the permanent id corresponding to a login id. Allows client to audit Customer messages associated with the current customer.
Customer Audit
<CustAudRq> <CustAudRs>
Customer Synchronize
<CustSyncRq> <CustSyncRs>
Allows client to synchronize Customer messages associated with the current customer.
Customer/Service Link Add

<CustSvcAddRq> <CustSvcAddRs>
Allows client to request the enabling of a service for a customer. Optionally allows an SP to return terms and conditions to the customer for acceptance. Allows the client to modify the fee account for a service.
Customer/Service Link Modify

<CustSvcModRq> <CustSvcModRs>
Customer/Service Link Status Modify

<CustSvcStatusModRq> <CustSvcStatusModRs>
Allows the client to modify the customer/service link status.
Customer/Service Link Delete

<CustSvcDelRq> <CustSvcDelRs>
Allows client to request the disabling of a service for the customer.
Customer/Service Link Audit

<CustSvcAudRq> <CustSvcAudRs>
Allows client to audit Service Enable and Disable messages associated with the current customer.
Customer/Service Link Synchronize

<CustSvcSyncRq> <CustSvcSyncRs>
Allows client to synchronize Service Enable and Disable messages associated with the current customer.
Service/Account Link Add

<SvcAcctAddRq> <SvcAcctAddRs>
Allows client to request activation of an account for one of the customers services. Optionally allows an SP to return terms and conditions to the customer for acceptance.
ServiceAccount Link Modify

<SvcAcctModRq> <SvcAcctModRs>
Allows client to request modification of an account for one of the customers services. Optionally allows an SP to return terms and conditions to the customer for acceptance. Allows client to request modification of the status of an account for one of the customers services.
ServiceAccount Link Status Modify

<SvcAcctStatusModRq> <SvcAcctStatusModRs>
Service Account Reversal

<SvcAcctRev>
Allows a client to reverse a previous service account request message.
April 2005
Version 1.7
Function / Message Name ServiceAccount Identifier Link Modify

<SvcAcctIdModRq> <SvcAcctIdModRs>
Requi red
Comments
Allows client to request replacement of one account for another within one of the customers services.
Service/Account Link Delete

<SvcAcctDelRq> <SvcAcctDelRs>
Allows client to request deactivation of an account for one of the customers services.
Service/Account Link Inquiry

<SvcAcctInqRq> <SvcAcctInqRs>
Allows client to retrieve account and service current state, and account balances.
Service/Account Link Audit

<SvcAcctAudRq> <SvcAcctAudRs>
Allows client to audit Account Activation and Deactivation messages associated with the current customer.
Service/Account Link Synchronize

<SvcAcctSyncRq> <SvcAcctSyncRs>
Allows client to synchronize Account Activation and Deactivation messages associated with the current customer. Allows client to retrieve disclosures.
Disclosure Inquiry
<DiscInqRq> <DiscInqRs>
Customer/Disclosure Link Status Modify

<CustDiscStatusModRq> <CustDiscStatusModRs>
Allows client to accept a disclosure received as part of the service enable/disable/modification and account activation/deactivation/modification process. Allows a customer to inquire about his/her associated disclosures for accounts or services.
Customer/Disclosure Link Inquiry

<CustDiscInqRq> <CustDiscInqRs>
Security Object Add

<SecObjAddRq> <SecObjAddRs>
Allows a client to create a security object. A security object is used for distributing encryption keys with IFX business messages using an "in-band" process. Allows a client to modify a security object.
Security Object Modify

<SecObjModRq> <SecObjModRs>
Secuity Object Inquiry

<SecObjInqRq> <SecObjInqRs>
Allows a client to inquiry on a security object.
Security Object Delete

<SecObjDelRq> <SecObjDelRs>
Allows a client to delete an instance of a security object.
Security Object Advise

<SecObjAdviseRq> <SecObjAdviseRs>
This message is sent to a terminal (e.g. ATM or POS) to trigger a remote key load process. This message can also be sent by a terminal to provide information on a security object that was loaded using an "out-of-band" process (e.g. manually loaded, injected from another system, etc.).
Version 1.7
April 2005
Function / Message Name Security Object Synchronize

<SecObjSyncRq> <SecObjSyncRs> Party to Account Relationship Add <PartyAcctRelAddRq> <PartyAcctRelAddRs> Party to Account Relationship Delete <PartyAcctRelDelRq> <PartyAcctRelDelRs> Party to Account Relationship Inquiry <PartyAcctRelInqRq> <PartyAcctRelInqRs>
Requi red
Comments
Allows a client a means to synchronize the security objects known by both the client and server.
The Party Account Relationship Add function relates parties to accounts with relationship types. This function will also be used to add parties, owners and non-owners, to existing accounts that already have at least one party to account relationship. The Party Account Relationship Delete Function will delete related parties from a specific account.
The Party Account Relationship Inquiry function returns parties related to a specific account, and can also be used to return the account associated with a particular party. This function will return base account ownership information such as Relationship Type, Primary Contact, and Tax Responsible Indicators. In addition, limited high level account information such as Account Status and Product will be returned. The Party Account Relationship Modify function is used to modify the relationship a party has with an account.
Party to Account Relationship Modify <PartyAcctRelModRq> <PartyAcctRelModRs>
CardPref Add
<CardPrefAddRq> <CardPrefAddRs>
Used to add a card preference. This is not used if a card preference relationship has already been established between a card and a business function. Used to modify a card preference object to alter the preferred account type, amount, or receipt printing option.
CardPref Modify
<CardPrefModRq> <CardPrefModRs>
CardPref Inquiry
<CardPrefInqRq> <CardPrefInqRs>
Used to inquire on a card preference object.
CardPref Cancel
<CardPrefCanRq> <CardPrefCanRs>
Not to be defined.
CardPref Delete
<CardPrefDelRq> <CardPrefDelRs>
Used to delete a card preference object.
CardPref Audit
<CardPrefAudRq> <CardPrefAudRs>
Used to audit changes to a card preference object.
CardPref Sync
<CardPrefSyncRq> <CardPrefSyncRs>
Used to synchronize changes to a card preference object.
CardPref Reversal
<CardPrefRevRq> <CardPrefRevRs>
Used to reverse an operation on a card preference object.
April 2005
Version 1.7
Function / Message Name CardPref Advise

<CardPrefAdviseRq> <CardPrefAdviseRs>
Requi red
Comments
Not to be defined.
CardPref Status Modify

<CardPrefStatusModRq> <CardPrefStatusModRs>
Used to update the status of a card preference object.
CardPref Status Inquiry

<CardPrefStatusInqRq> <CardPrefStatusInqRs>
Not to be defined
Posting Session Add

<PostingSessionAddRq> <PostingSessionAddRs>
Allows an individual (eg. teller, CSR, or operator) or a device (eg. kiosk) to start a session with the server and establish session parameters. Allows an individual (eg. teller, CSR, or operator) or a device (eg. kiosk) to modify a previously established session with the server without having to undergo full session verification. Allows an individual (eg. teller, CSR, or operator) or a device (eg. kiosk) to inquire on session parameters.
Posting Session Modify

<PostingSessionModRq> <PostingSessionModRs>
Posting Session Inquiry

<PostingSessionInqRq> <PostingSessionInqRs>
Posting Session Audit

<PostingSessionAudRq> <PostingSessionAudRs>
Allows a client to audit Posting Session Add/Modify/StatusMod messages.
Posting Session Status Modify

<PostingSessionStatusModRq> <PostingSessionStatusModRs>
Allows a teller, CSR or operator to modify a Posting Session status
Session Total Inq

<SessionTotalInqRq> <SessionTotalInqRs>
Allows for inquiry of an indicated session or for all sessions for a teller, CSR, customer or POS device.
5.2Base Service Common Elements and Aggregates

5.2.1Service Profile Common Elements
5.2.1.1 Messages Supported Element <MsgSupt>
The <MsgSupt> element is included in the Service Profile for each service. It provides the client with a list of supported messages for that service.
Tag
<MsgSupt>
Type
Open Enum
Usage
Description
Supported Messages. This is a list of messages that are supported for the current service. The convention is to use the name of the message without the Rq or Rs so that each message is only listed once.
Version 1.7
April 2005
5.2.1.2 Options Supported Element <OptSupt>

The <OptSupt> element is included in each Service Profile where there are options that the client should know are supported or not supported by the server.
Tag
<OptSupt>
Type
Open Enum
Usage
Description
Options Supported. Defined values: AcctNickname, BillerPayee, BillStatus, CustPayeeNickname, ForEx, ForExCommit, FSPayee, ImmediateXfer, LineItem, RecCtrl, RecFinalCurAmt, RecInitialCurAmt, RecPend, SchedXfer, SkipInst, StopChkRangeSC, SuppressEcho, XferPayee
The following table identifies the services that use each option support value.
<OptSupt> value
AcctNickname BillerPayee BillStatus CustPayee CustPayeeNickname ForEx ForExCommit FSPayee ImmediateXfer LineItem RecCtrl RecFinalCurAmt RecInitialCurAmt SchedXfer SkipInst StopChkRangeSC XferPayee
Base
Bank
Pay

Pres
5.2.2Service Profile Common Aggregates

5.2.2.1 Service Core Aggregate <SvcCore>
The <SvcCore> aggregate provides information about the service that is critical for the correct processing of that service.
Tag
<Version>
Type
NC-12
Usage
Required
Description
The version of IFX that the server supports. May be used by the server to infer that any tags added beyond this level are not supported. Service Provider Name. SP Legal Name. SP Nickname.
<SPName> <LegalName> <Nickname>
Identifier C-96 C-40
Required Required Optional
April 2005
Version 1.7
Tag
<HoldCoId>
Type
Identifier
Usage
Optional
Description
SP Holding Company Identifier. A unique identifier assigned by a service provider to identify the holding company that owns the SP branding company. Routing and Transit Number. This is the default RTN for a customer account associated with the SPName above. Service Provider Contact Aggregate. Usage is contact information for reaching relevant organizations at the SP (for example, the customer services area). Contact Information Aggregate.
<USA.RTN> <OrgContact>
NC-9 Aggregate see section 3.2.5.2
Optional Required XOR Repeating
<ContactInfo>
Aggregate see section 3.2.3.9 NC-17
Required XOR Repeating Required Repeating
<Language>
Language. See section 2.6.4 for more information on the format of this element. If the server supports more than one language for this service, multiple Language aggregates may be listed.
<URL>
URL
Optional
URL. <URL> identifies where the client should send the request for that service.
5.2.2.2 Service Profile Information Aggregate (xxxSvcProfInfo)

The Service Profile Information aggregate is used to express profile options for particular services. A list of these aggregates comprises part of the Service Profile Inquiry Response message <SvcProfInqRs> that is used to communicate server capabilities to a client.
Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service. Other elements and aggregates as appropriate for profiling options for the specific service.
Service specific elements and aggregates
The definition of this aggregate is in the last section of each service chapter.
5.2.2.3 Processing Schedule Aggregate <PrcSched>

The <PrcSched> aggregate appears wherever information about a Service Providers processing schedule is needed. Note that this aggregate does not take holidays into account.
Tag
<PrcDaysOff>
Type
Closed Enum
Usage
Optional Repeating
Description
Processing Days Off. Days of the week on which no processing occurs. Valid values: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday, Holiday
<CutoffTm> <PrcDtAdj>
Time Open Enum
Required Required
Cutoff Time for Daily Processing. This is the latest time a customer may submit a request for processing today. Processing Date Adjustment. Algorithm used for adjustment of processing for requests that fall on non-processing days or holidays. Defined values: Earlier, Later.
Version 1.7
April 2005
5.2.3Customer Profile Common Aggregates

5.2.3.1 Customer Record Aggregate <CustRec>
Tag
<CustId>
Type
Usage
Required
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer Information Aggregate.
<CustInfo>
Aggregate see section 5.2.3.1.1 Aggregate see section 5.2.3.1.2 Timestamp
Optional
<CustStatus>
Required
Customer Status Aggregate.
<UpDt>
Optional
Customer Record Update DateTime. The value is for the last update to <CustInfo> on the server.
5.2.3.1.1 Customer Information Aggregate <CustInfo>

The Customer Information aggregate <CustInfo> contains information about the customer, such as name, address, and contact information.
Tag
<CustName>
Type
Aggregate see section 3.2.3.2 Aggregate see section 3.2.3.10.1 Aggregate see section 3.2.3.3 Aggregate see section 3.2.3.9 Aggregate see section 3.2.3.5 Open Enum
Usage
Required XOR Optional Profiled requirement Optional Profiled requirement Optional
Description
Customer Name Aggregate.
<PostAddr>
Customer Postal Address Aggregate.
<CustContact>
Customer Contact Aggregate.
<ContactInfo>
<CustPref>
Optional
Customer Preference Aggregate. An aggregate used to store preferences the customer has selected or for the service provider to store values to be used specifically for this customer. Customer Type. The type of relationship established between the CSP and the customer. Valid values: Retail, Business.
<CustType>
Optional
<PersonInfo>
Required XOR 1.1+ Required XOR 1.1+
Person Information Aggregate
<OrgInfo>
Organization Information Aggregate
5.2.3.1.2 Customer Status Aggregate <CustStatus>
April 2005
Version 1.7
Tag
<CustStatusCode>
Type
Open Enum
Usage
Required
Description
Customer Status Code. Defined values: Enrolled, EnrollPend, Suspended, UnenrollPend, Unenrolled
C-255 DateTime Open Enum
Status Description. Explanatory text associated with this service status. Effective Date/Time. The date/time the <CustStatusCode> took effect. Status Modified By. If present, indicates who modified the Customer Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<ResolvePendingDt>
Date
Optional
Resolve Pending Date. The date that the xxxPend status in <CustStatusCode> is expected to change to a final status; e.g., Enrolled, Unenrolled. This date should be returned when the <CustStatusCode> is set to xxxPend.
5.2.3.2 Disclosure Record Aggregate <DiscRec>

The <DiscRec> aggregate allows the CSP/SP to send Terms and Conditions, related to the IFX Service, to the customer. The CSP/SP may optionally require acceptance of these terms and conditions prior to enabling a service or activating/modifying an account for a service. Note: Customer acceptance of a disclosure is associated with the Disclosure Identifier <DiscId> for that disclosure. If it is necessary to track the version of a disclosure that a customer has accepted, it is recommended that a service provider use a new <DiscId> any time that they modify their disclosure. The <DiscId> itself is the versioning mechanism for disclosures within IFX (see Section 5.4.1.2 for additional information on Disclosures).
Type
UUID Aggregate see section 5.2.3.2.1
Tag
<DiscId> <DiscInfo>
Usage
Required Required
Description
Disclosure Identifier Disclosure Information
5.2.3.2.1 Disclosure Information Aggregate <DiscInfo>

Tag
<LongText> <DiscURL> <AcceptReqd>
Type
C- URL Boolean
Usage
Description
Disclosure Text. Disclosure URL. The address for obtaining human-readable disclosure information. Disclosure Accept RequiredThe server indicates whether the acceptance of this disclosure is required to proceed. If set to True, acceptance is required.
Version 1.7
April 2005
5.2.3.3 Customer/Disclosure Link Record Aggregate <CustDiscRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 UUID Aggregate see section 5.2.3.2.1 Aggregate see section 5.2.3.3.1
Usage
Required
Description
Customer Identifier
<DiscId> <DiscInfo>
Required Optional
Disclosure Identifier Disclosure Information. Provided if requested by the client.
<CustDiscStatus>
Required
Customer/Disclosure Link Status
5.2.3.3.1 Customer/Disclosure Link Status Aggregate <CustDiscStatus>

Tag
<CustDiscStatusCode>
Type
Usage
Required
Description
Customer/Disclosure Link Status Code Valid values: None, Accepted, Rejected, Viewed.
Status Description. Explanatory text associated with this customer/disclosure link status. Effective Date/Time. The date/time the <CustDiscStatusCode> took effect. Status Modified By. If present, indicates who modified the Status Code. Defined values: Customer, FI, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
5.2.3.4 Customer/Service Link Record Aggregate <CustSvcRec>

Tag
<CustSvcId>
Type
Usage
Required
Description
Customer/Service Link Identification Aggregate.
<CustSvcInfo>
Required
Customer/Service Link Information Aggregate.
<CustSvcStatus>
Required
Customer/Service Status Aggregate.
5.2.3.4.1 Customer/Service Link Identification Aggregate <CustSvcId>

Tag
<SvcName>
Type
Open Enum
Usage
Required
Description
Service Name. Defined values: Bank, Pay, Pres
<SPName>
Identifier
Required
Service Provider Name.
5.2.3.4.2 Customer/Service Link Information Aggregate <CustSvcInfo>

10 April 2005 Version 1.7
Tag
<DepAcctId>
Type
Usage
Description
Deposit Account Aggregate. Used to specify a deposit account to be used for charging fees for the service. Card Account Identifier Aggregate. Used to specify a card account to be used for charging fees for the service.
<CardAcctId>
5.2.3.4.3 Customer/Service Link Status Aggregate <CustSvcStatus>

Tag
<CustSvcStatusCode>
Type
Closed Enum
Usage
Required
Description
Customer/Service Status Code. Valid values: Enabled, EnablePend, Disabled, DisablePend, Rejected
<StatusDesc>
C-255
Optional but see Description Optional Optional
Status Description. Explanatory text associated with this customer/service link status. Required if service change is rejected. Effective Date/Time. The date/time the <CustSvcStatusCode> took effect. Status Modified By. If present, indicates who modified the Status Code. Defined values: Customer, FI, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<EffDt> <StatusModBy>
DateTime Open Enum
<ResolvePendingDt>
Date
Optional
Resolve Pending Date. The date that the xxxPend status in <CustSvcStatusCode> is expected to change to a final status; e.g., Enabled, Rejected. This date should be returned when the <CustSvcStatusCode> is set to xxxPend.
5.2.3.5 Service/Account Link Record Aggregate <SvcAcctRec>

Tag
<SvcAcctId>
Type
Aggregate see section 5.2.3.5.1 Aggregate see section 5.2.3.5.2 Aggregate see section 5.2.3.5.3 DateTime
Usage
Required
Description
Service/Account Link Identifier Aggregate.
<SvcAcctInfo>
Required
Service/Account Link Information Aggregate.
<SvcAcctStatus>
Required
Service/Account Status Aggregate.
<EffDt>
Optional
Effective Date. The date that the first account information (i.e. statement, bill, etc.) is expected to be available. This date should be returned when the <SvcAcctStatusCode> for an account is set to Activated. For billing accounts, this is the date of the first available bill. If absent, the semantic meaning is that information is available immediately.
5.2.3.5.1 Service/Account Link Identification Aggregate <SvcAcctId>
Version 1.7
April 2005
11
Tag
<CustSvcId>
Type
Aggregate see section 5.2.3.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.7.3.1 Aggregate see section 3.2.7.3.2
Usage
Required
Description
Customer/Service Link Identifier Aggregate.
<DepAcctId>
Required XOR Required XOR Required XOR Required XOR Required
Deposit Account Identifier Aggregate.
<CardAcctId>
Card Account Identifier Aggregate.
<LoanAcctId>
Loan Account Identifier Aggregate.
<PresAcctId>
Presentment Account Identifier Aggregate.
<PresAcctInfo>
Presentment Account Information Aggregate.
5.2.3.5.2 Service/Account Link Information Aggregate <SvcAcctInfo>

Tag
<Nickname>
Type
C-40
Usage
Optional
Description
Account Nickname, as held by the Service Provider.
5.2.3.5.3 Service/Account Link Status Aggregate <SvcAcctStatus>

Tag
<SvcAcctStatusCode>
Type
Closed Enum
Usage
Required
Description
Service/Account Status Code. Valid values: Activated, ActivatePend, Deactivated, DeactivatePend, Rejected, Suspended
<StatusDesc>
C-255
Optional but see Description Optional Optional
Status Description. Explanatory text associated with this customer/service link status. Required if service change is rejected. Effective Date/Time. The date/time the <SvcAcctStatusCode> took effect. Status Modified By. Defined values: CSP, CPP, BSP, BPP, FI
DateTime Open Enum
<ResolvePendingDt>
Date
Optional
Resolve Pending Date. The date that the xxxPend value in <SvcAcctStatusCode> is expected to change to a final status; e.g., Activated, Rejected. This date should be returned when the <SvcAcctStatusCode> is set to xxxPend.
5.2.3.6 Security Object Record Aggregate <SecObjRec>

Note: For security reasons, <SecObjValue> is not to be included in the Security Object Record Aggregate unless the object is not of sensitive nature.
12
April 2005
Version 1.7
Tag
<SecObjId> <SecObjKeyChkValue> <SecObjName>
Type
Identifier HexBin- C-64
Usage
Required Optional Optional but see Description Optional
Description
Security Object Identifier used to reference this security object in future request Key Check value for those protocols that can generate a key Check value (i.e. DEA, AES) Human readable object description. If there are two or more Security Objects of with the same <SecObjType>/<SecObjPurpose>, then this field is required in order to differentiate between the usages of the key. Type of Security Object. Valid Value: 1KeyDES, 2KeyDES, 3KeyDES, 128BitAES, 192BitAES, 256BitAES, DigitalCertificate, PublicKey, RandomNumber, ModuleID
<SecObjType>
Open Enum
<SecObjPurpose>
Open Enum
Optional
Purpose (use) of the Security Object Note: The Algorithm that employs this key is agreed to out of band. Valid Values: PINEncryptingKey, KeyEncryptingKey, PasswordEncryptingKey, DataEncryptingKey, Identification, MAC, Uniqueness, VISAPINVerification
<CryptType>
Open Enum
Optional
Type of encryption used to encrypt <SecObjValue>. Depending on the Security Object, this represents how the <SecObjValue> data is formatted. Note, must be present is <SecObjValue> is present.
The only <CryptType> values that make logical sense for use within the <SecObjRec> are the following:
Valid Values: PKCS#1, PKCS#7, PKCS#10, None <SecObjValue> HexBin- Optional For an Inquiry message, the security object is returned in the case of a digital signature or public key since there are not security concerns associated with transporting this key For an add message in which the KeyEncryptingKey is loaded via asymmetric cryptography, this is the ATM verification of the key load (Host Random Number, ATM Random Number signed by ATM Identification Key <SecObjStatus> Aggregate see section 5.2.3.6.2 Required Security Object Status
5.2.3.6.1 Security Object Information Aggregate <SecObjInfo>

Tag
<SecObjName>
Type
C-64
Usage
Description
Human readable object description. If there are two or more Security Objects of with the same <SecObjType>/<SecObjPurpose>, then this field is required in order to differentiate between the usages of the key. Type of Security Object. Valid Value: 1KeyDES, 2KeyDES, 3KeyDES, 128BitAES, 192BitAES, 256BitAES, DigitalCertificate, PublicKey, RandomNumber. ModuleID
<SecObjType>
Open Enum
Version 1.7
April 2005
13
Tag
<SecObjName>
Type
C-64
Usage
Description
Human readable object description. If there are two or more Security Objects of with the same <SecObjType>/<SecObjPurpose>, then this field is required in order to differentiate between the usages of the key. Purpose (use) of the Security Object Note: The Algorithm that employs this key is agreed to out of band. Valid Values: PINEncryptingKey, KeyEncryptingKey, PasswordEncryptingKey, DataEncryptingKey, Identification, MAC, Uniqueness, VISAPINVerification
<SecObjPurpose>
Open Enum
<CryptType>
Open Enum
Required
Type of encryption used to encrypt <SecObjValue>. Depending on the Security Object, this represents how the <SecObjValue> data is formatted Valid Values: PKCS#1, PKCS#7, PKCS#10, RSA#1, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM, None
<SecEncryptId>
Identifier
Optional but see Description Optional but see Description Required
Identifier of Security Object on which the <SecObjValue> is encrypted. <SecEncryptId> is required if <SecObjValue> is encrypted. Identifier of Security Object on which the <SecObjValue> is Signed. <SecSignId> is required if <SecObjValue> is cryptographically signed. Actual Security Object being transported (encryption key, digital certificate, etc.)
<SecSignId>
Identifier
<SecObjValue>
HexBin-
5.2.3.6.2 Security Object Status <SecObjStatus>

Tag
<SecObjStatusCode>
Type
Closed Enum
Usage
Required
Description
Security Object Status Code. This identifies the security object status. Valid Values: Active, Inactive, Expired, OutOfSync
Status Description. Explanatory text associated with this status Security Object Status date. The date associated with the state change to the current status Indicates the entity to last modify the object status Valid Values: Host, Terminal, Maintenance
5.2.4Party Account Relationship Info <PartyAcctRelInfo>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3
Usage
Optional
Description
Customer Identification Aggregate.
<DepAcctId>
<CardAcctId>
14
April 2005
Version 1.7
Tag
<LoanAcctId>
Type
Aggregate see section 3.2.7.2.5 Aggregate see section 5.2.4.3 Decimal
Usage
Required XOR Required Repeating Optional
Description
<PartyAcctRel>
Party to account relationship aggregate.
<OwnerPercent>
Percentage of account ownership. Used primarily for Loan Accounts. Usage is a percentage. (e.g. a value of 5.2 = 5.2%)
5.2.4.1 Party Account Relationship Record <PartyAcctRelRec>

Tag <PartyAcctRelId> <PartyAcctRelInfo>
Type
Identifier Aggregate see section 5.2.4 C-96 Aggregate see section 3.2.4.1.3 Boolean Aggregate see section 3.2.7.2.7 Date Date Boolean
Usage
Required Required
Description
Party Account Relationship Identifier. Party Account Relationship Info Aggregate.
<FullName> <TINInfo>
Optional Optional
Full name of the person or business. Tax Identifier Number aggregate.
<OwnerInd> <BankAcctStatus>
Optional Optional
Indicates if the relationship is of the owner or non-owner type. Bank Account Status Aggregate. Intended use within the PartyAcctRelRec is when the accounts associated with a customer are being returned for the PartyAcctRelInqRs. Indicates the date the account opened. Indicates the date the account closed Primary Account Indicator. If True, used as default account for a class of accounts (i.e., checking). Typically used in ATM networks. May be used for other applications by some FIs. Used to represent an account nickname applied by the customer of FI. Account balance aggregate.
<OpenDt> <ClosedDt> <PrimaryAcct>
<NickName> <AcctBal>
C-40 Aggregate see section 3.2.8.1 Aggregate see section 5.2.4.2
Optional Optional Repeating Optional
<PartyAcctRelStatus>
Party Account Relationship Status.
5.2.4.2 Party Account Relationship Status <PartyAcctRelStatus>

Tag <PartyAcctRelStatusCode>
Type
Closed Enum C-255
Usage
Required
Description
Party/Account Status Code. Valid values: Active, InActive, PendDelete
<StatusDesc>
Optional but see Descriptio n
Status Description. Explanatory text associated with this party/account link status. Required if service change is rejected.
Version 1.7
April 2005
15
Tag <EffDt> <StatusModBy>
Type
DateTime Open Enum
Usage
Optional Optional
Description
Effective Date/Time. The date/time the <PartyAcctStatusCode> took effect. Status Modified By. Defined values: CSP, CPP, BSP, BPP, FI
5.2.4.3 Party Account Relationship <PartyAcctRel>

Tag <PartyAcctRelType>
Type
Open Enum
Usage
Required Repeating
Description
Party Account Relationship Type. Defined values are: Tax Responsible Primary Contact Doing Business As Individual Individual with Rights Joint Tenancy Joint Tenants in Common Joint with Rights Multiple Signer Custodian Guardian Executor Administrator Guarantor Comaker Trustee Payee Power of Attorney Pay On Death
<PartyAcctRelDesc>
C-80
Optional
Party Account Relationship Description.
5.2.5Card Preference Record Aggregate <CardPrefRec>

Tag
<CardPrefId> <CardPrefInfo>
Type
Identifier Aggregate see section 5.2.7 Aggregate see section 5.2.6
Usage
Required Required
Description
Card Preference Identifier Card Preferences Information Aggregate
<CardPrefStatus>
Required
Card Preference Status Aggregate
16
April 2005
Version 1.7
5.2.6Card Preference Status Aggregate <CardPrefStatus>

Tag
<CardPrefStatusCode>
Type
Open Enum
Usage
Required
Description
The current status of the Card Preference object. Defined Values: Active, Inactive
<StatusDesc> <EffDt> <ApprovalId> <StatusModBy>
C-255 DateTime Identifier Open Enum
Status Description. Explanatory text associated with the current state of the object. Effective Date/Time. The date the <CardPrefStatusCode> took effect. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
5.2.7Card Preference Information Aggregate <CardPrefInfo>

Tag
<CardLogicalData>
Type
Usage
Required
Description
Logical Data That Represents the Card.
<CardPref>
Required
Card Preferences Aggregate. This contains an individual preference for the cardholder. Base Environment aggregate
<BaseEnvr>
Optional
5.2.8Card Preference Aggregate <CardPref>

Tag
<CardPrefMisc>
Type
Usage
Description
Miscellaneous preferences related to this card
<CardPrefWithdrawal>
Card Preferences for Withdrawal Business Function
<CardPrefDeposit>
Card Preferences for Deposit Business Function
5.2.9Card Preference Withdrawal Aggregate <CardPrefMisc>

Tag
<Language>
Type
NC-17
Usage
Optional
Description
Language. This element contains the customers preferred language of communication. See section 2.6.4 for more information on the format of this element.
Version 1.7
April 2005
17
5.2.10
Card Preference Withdrawal Aggregate <CardPrefWithdrawal>
Preferences for Cash Withdrawal and Cash Advances. Note that existing values for AcctType may include Other based on outstanding proposals.
Tag
<CurAmt> <AcctType>
Type
Currency Amount Open Enum
Usage
Optional Optional XOR
Description
Currency Amount. Identifies the customers preferred withdrawal amount. Account Type. The card-based account this cardholder has pre-selected for this transaction based on the current card. See Data Dictionary for details. Defined values: DDA, SDA, CDA, MMA, CMA.
<DepAcctId> Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Boolean Optional XOR Optional XOR Optional XOR Optional Deposit Account Identification Aggregate.
<CardAcctId>
<LoanAcctId>
<PrintReceipt>
Identifies the cardholders preference for printing receipts. If this value is not specified, the cardholder should be prompted for the
5.2.11
Card Preference Deposit Aggregate <CardPrefDeposit>

Type
Currency Amount Open Enum
Note that existing values for AcctType may include Other based on outstanding proposals.
Tag
<CurAmt> <AcctType>
Usage
Description
Currency Amount. Identifies the customers preferred deposit amount. Account Type. The card-based account this cardholder has pre-selected for this transaction based on the current card. See Data Dictionary for details. Defined values: DDA, SDA, CDA, MMA, CMA.
<DepAcctId> Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Optional XOR Optional XOR Deposit Account Identification Aggregate.
<CardAcctId>
18
April 2005
Version 1.7
Tag
<LoanAcctId>
Type
Aggregate see section 3.2.7.2.5 Boolean
Usage
Description
<PrintReceipt>
Identifies the cardholders preference for printing receipts.
5.2.12
Card Preference Message Request Information Aggregate <CardPrefMsgRqInfo>

Type
Aggregate see section 5.8.1.1 Aggregate see section 5.8.2.1 Aggregate see section 5.8.4.1 Aggregate see section 5.8.3.1 Aggregate see section 5.8.5.1 Aggregate see section 5.8.6.1 Aggregate see section 5.8.8.1
This aggregate is used for Reversal messages

Tag
<CardPrefAddRq>
Usage
Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR
Description
Card Preference Add Request Message Aggregate.
<CardPrefModRq>
Card Preference Modify Request Message Aggregate.
<CardPrefDelRq>
Card Preference Delete Request Message Aggregate.
<CardPrefInqRq>
Card Preference Inquiry Request Message Aggregate.
<CardPrefAudRq>
Card Preference Audit Request Message Aggregate.
<CardPrefSyncRq>
Card Preference Sync Request Message Aggregate.
<CardPrefStatusModRq>
Card Preference Status Modify Request Message Aggregate.
5.2.13
Card Preference Message Record Aggregate <CardPrefMsgRec>

Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 5.8.1.2 Aggregate see section 5.8.2.2
This aggregate is used for the Audit messages

Tag
<CustId>
Usage
Optional
Description
<MsgRecDt> <CardPrefAddRs>
Optional Required XOR Required XOR
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Card Preference Add Response Message Aggregate.
<CardPrefModRs>
Card Preference Modify Response Message Aggregate.
Version 1.7
April 2005
19
Tag
<CardPrefDelRs>
Type
Aggregate see section 5.8.4.2 Aggregate see section 5.8.7.2 Aggregate see section 5.8.8.2
Usage
Description
Card Preference Delete Response Message Aggregate.
<CardPrefRevRs>
Card Preference Reversal Response Message Aggregate.
<CardPrefStatusModRs>
Card Preference Status Modify Response Message Aggregate.
5.2.14
Tag
Posting Session Record Aggregate <PostingSessionRec>

Type
Identifier Aggregate see section 5.2.14.2 Aggregate see section 5.2.14.1
Usage
Required Required
Description
Session Identifier. Assigned by the server at the time the session is first added. Cannot be changed by the client. Session Information aggregate.
<PostingSessionId> <PostingSessionInfo>
<PostingSessionStatus>
Required
Session status aggregate.
5.2.14.1 Posting Session Status Aggregate <PostingSessionStatus>

The <PostingSessionStatus> is returned in responses to Add or Modify Posting Session model. Note that all elements within this aggregate are assigned by the server and cannot be assigned or modified by the client.
Tag
<PostingSessionStatusCode>
Type
Open Enum
Usage
Required
Description
Session Status Code. This identifies the Posting Session processing status. Valid values: Active, Inactive, Expired, Closed, ClosedFinal
Status Description. Explanatory text associated with this status. Session Status Date. The date associated with the state change to the current state. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSR, Teller, FI
5.2.14.2 Posting Session Information Aggregate <PostingSessionInfo>

The <PostingSessionInfo> aggregate is used in messages related to Posting Sessions. It is generally used in the request messages. It contains the Posting Session parameters that are to be stored on the server for subsequent teller transaction processing.
20
April 2005
Version 1.7
Tag
<SessionLoginId>
Type
Identifier
Usage
Required
Description
Session login id. This may or may not be the same as the teller, CSR or operator permanent identification maintained in the CustId. Session Date. The calendar date the session was established. Session posting date. The posting date for all transactions initiated by the teller, CSR or operator during the session.
<SessionDt> <SessionPostingDt>
DateTime Date
Required Required
Note: This is typically entered by the teller, CSR or operator. for example, the operator might be logging in to process prior day/future day work. It may be adjusted by the server to reflect the appropriate business date.
<PhysicalLocId> NC-36 Optional The physical location of the teller, CSR or operator. This may or may not be the same as the <SessionLocId>. An example is an operator at a central operations center logging on as if they were an operator located at a specific branch. If this element is not included, the assumption is that totals move with the teller, regardless of location. Physical Location Name. The session location of the teller, CSR or operator. This is the branch transit for which the teller/CSR/operator will be doing transactions and under which the transactions will be posted. The <SessionLocId> should only be included if it is different than the <PhysicalLocId> <SessionLocName> <ExpDt> C-40 DateTime Optional Optional Session Location Name. The date/time that the posting session will expire or otherwise become ineffective. Use of the posting session after this date/time will not be allowed. Base Environment aggregate
<PhysicalLocName> <SessionLocId>
C-40 NC-36
Optional Optional
<BaseEnvr>
Optional
5.2.15
Tag
Session Totals Record Aggregate <SessionTotalsRec>

Type
Currency Amount Aggregate see section 5.2.15.1
Usage
Required
Description
The net value of all totals within the specified session. For example, this could be the net amount of the Debit and Credit Session Balances. Session balances. Contains the denomination and different balances/totals for this session.
<NetCurAmt>
<SessionBal>
Required Repeating
5.2.15.1 Session Balances Aggregate <SessionBal>

Contains the denomination and different balances/totals for this session.
Tag
<PostingTotalType>
Type
Open Enum
Usage
Required
Description
Total type. Used to further clarify a session balance amount. Defined values: Debit, Credit
<Count>
Long
Optional
A count of the number of items in this aggregate.
Version 1.7
April 2005
21
Tag
<TotalCurAmt>
Type
Currency Amount
Usage
Required
Description
The total currency value of the <PostingTotalType>.
5.3Service Profile
5.3.1Description
The Service Profile has two messages, a Service Profile Inquiry message, and a Holiday Inquiry message. The Holiday Inquiry Message allows a client to retrieve a list of Bank Holidays observed by a Financial Institution or Service Provider. The Service Profile Inquiry Message allows a client to retrieve the Service Profile from a Financial Institution, CSP, or other Service Provider. The Service Profile contains the following information about the Customers Service Provider: Services SupportedServices are collections of messages that are functionally related. Each Service is designed with a corresponding section in the Service Profile to allow each Service Provider to inform clients as to which messages, functions, and options of the service supported. Signon RealmsSignon Realms provide a mechanism for a Service Provider to manage customer authentication across services. Service Providers may choose not to support IFX authentication when communicating to other service providers. Server-to-server authentication may take place in some other way. Service Provider InformationProvides the legal name of the SP, the SP address, the SPs Customer Service telephone number, and other useful information for that service provider. Each time a client authenticates with a Signon Realm, the time and date of the current Service Profile is returned by the server. If the client does not have a copy of the current Service Profile, it should perform a Service Profile Inquiry message to retrieve the current Service Profile. This mechanism is used to inform clients of changes in server capabilities. Note: All IFX servers must support the Service Profile Inquiry message.
5.3.2Service Profile Inquiry Message

5.3.2.1 Request <SvcProfInqRq>
The client submits a <SvcProfInqRq> that optionally includes a Timestamp value <UpDt> for the last Service Profile received from the server. <UpDt> indicates when the Service Profile was last updated on the server. If <CustId> is not available (because of an anonymous login, for example), a generic profile must be returned. If <CustId> is available, then a custom profile for that customer may be returned. This capability allows the SP to support capabilities such as: (1) providing different contact information for preferred customers or (2) providing information specific to service providers for this particular customer when the SP has relationships with multiple service providers for the same service.
Tag <RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
22
April 2005
Version 1.7
Tag <AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Delivery Method. Default is Channel. Value must be supported in Service Profile. Timestamp when the Service Profile was Last Updated on the Server. This is the timestamp of the last Service Profile received from the server.
<DeliveryMethod>
Open Enum
Optional Profiled values Optional
<UpDt>
Timestamp
5.3.2.2 Response <SvcProfInqRs>

The Service Profile Inquiry Response Message returns the following information in the following order: Sections for each service that the SP supports, including the parameters for that service, and the associated signon realm; Information about the SP, e.g. name, address, contact information, is included in <SvcCore> for the Base service, and Information about the signon realms. If there have been no updates to the Service profile, the server should return <StatusCode> 1 to indicate that the client has the most current Service Profile. In this case, the server should not return the <xxxSvcProfInfo> aggregates.
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Message Request Header aggregate.
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID> <CustId>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued.
Version 1.7
April 2005
23
Tag
<DeliveryMethod> <UpDt>
Type
Open Enum Timestamp
Usage
Description
Delivery Method. Timestamp when the Service Profile was Last Updated on the Server. The last timestamp received by the client.
<NewUpDt>
Timestamp
Required
New Service Profile Update Date Time. The value is for the last update to the most recent <xxxSvcProfInfo> on the Server. Service Profile Information Aggregate. At least one per service supported.
<xxxSvcProfInfo>
Aggregate
Optional Repeating
5.3.3Holiday Inquiry Message

The Holiday Inquiry message allows a client to retrieve a list of Bank Holidays observed by the Service Provider. The list of holidays is typically used to adjust the processing date for a scheduled payment or transfer.
5.3.3.1 Request <HolInqRq>

The client submits a <HolInqRq> in order to request a list of the Service Providers observed holidays.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 UUID
Optional
<AsyncRqUID>
Optional
<SPName>
Identifier
Optional but see Description Optional but see Description
Service Provider Name. If omitted, the receiver of the message must determine (1) that the message is unambiguous and provide a successful response or (2) that it is ambiguous and provide an error response. Service Name. If omitted, the server must determine (1) that the message is unambiguous and provide a successful response or (2) that it is ambiguous and provide an error response. Defined values: Bank, Pay, Pres.
<SvcName>
Open Enum
<DeliveryMethod>
Open Enum
Optional Profiled values
Delivery Method. Default is Channel. Value must be supported in Service Profile.
5.3.3.2 Response <HolInqRs>

The server at the Financial Institution or Service Provider responds with a list of observed Bank Holidays if available.
24
April 2005
Version 1.7
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Identifier Open Enum
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID> <SPName> <SvcName>
Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
Asynchronous Request Identifier. Service Provider Name. Service Name. Defined values: Bank, Pay, Pres Delivery Method. Holiday Information Aggregate.
<DeliveryMethod> <HolInfo>
Open Enum Aggregate see section 5.3.3.2.1
5.3.3.2.1 Holiday Information Aggregate <HolInfo>

Tag
<Name> <HolDt>
Type
C-40 Date
Usage
Required Required
Description
Holiday Name. Holiday Date.
5.4Customer Profile
5.4.1Description
Customer Profile Messages provide the following functions: Enrollment and Acquisition of Login ID and Password. An Enrollment message that allows an individual to submit enough personal information to be identified to a Service Provider is provided. If the SP supports customer self-enrollment using the IFX Specification, it may elect to return a login ID and password to the customer. Alternately, the SP may collect the customers information and use a separate process (possibly a mailing or a customer service telephone call) to provide the customer with a login and password. Updating of Customer Name, Address, and Contact Information. After the customer initially provides his or her personal information through the enrollment process, he or she may need to update this information periodically. The Modify Customer Information message is provided for this purpose. Customer Profile. The Customer Profile message provides a current view of the customers information, accounts balances, and services. It is useful both in initial setup and on an ongoing basis.
Version 1.7
April 2005
25
Interactive Financial Exchange Business Message Specification Service Enabling and Disabling. Services may be enabled for a customer, independently of any account. The customer and CSP may use the Customer/Service Link Add and Customer/Service Link Delete messages to manage which services are currently activated for the customer. A fee account may optionally be specified. Any fees attributable to the use of the service are charged to the fee account. Service Modification. The Customer/Service Link Modify message is used to change the fee account. Account Activation and Deactivation. Accounts may be activated for use by a specific service. The customer and CSP may use the Service/Account Add and Service/Account Delete messages to manage which accounts are currently activated for each service. Account Modification. The Service/Account Modify message is used to modify a funding account for the Pay service, or to change an account nickname.
5.4.1.1 Account Activation and Deactivation

Accounts are established with an SP and may be used electronically if activated for a service; e.g., a checking account may be activated for electronic banking (Bank service). Another CSP/ SP may reference the account; e.g., the Pay service provider may use it as a funding account. Thus, the meaning of activating an account for a service is specific to the service. The use of an account may be constrained based on a combination of the type of account, its tax status, and CSP/SP policy. For example: A certificate of deposit (CD) account may not be a funding or fee account for Pay. A CSP might not allow interbank transfers from a savings (SDA) account. The allowable usage for a bank account is specified by a series of aggregates <XferFromSupt>, <XferToSupt>, and <PaySupt> within the Bank Account Information Aggregate <BankAcctRec>. These tags are sometimes referred to as the accounts message authority. The following table defines the meaning of activating an account for a service.
Servic e
Base Bank Pay Pres
Activation Means
Not applicable Banking Accounts Funding Accounts Biller Accounts
Comments
Allows all banking services subject to message authority.
Customers account at the biller.
Services that normally require an account to be associated with them may remain enabled even when no account is activated. These situations are typically temporary conditions. For example, a customers checkbook for the sole Pay funding account may be stolen. The checking account is closed immediately to reduce the risk of loss, and there is a processing delay while a replacement account number is assigned. The Pay service must remain enabled during the processing delay, even though there was no funding account specified, in order to maintain the customer payee list, pending payments, and payment models that are defined. The Modify Account message is used to replace an existing account (e.g., change a funding account for Pay), change information for a Bill Presentment account, and modify the account nickname Note: The Customer/Service Link and Service/Account Link messages are intentionally limited to a single link per message to simplify error reporting when the request is rejected by the SP.
5.4.1.2 Disclosures
IFX Services may have terms and conditions associated with them. These terms and conditions may be a combination of fees, terms mandated by statute, and terms required by the SP. Banking regulations and contract law may restrict the acceptable means of notification; e.g., US Mail to the address of record in the US.
26
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification Some services, notably Bill Presentment, may require disclosures at the account level. In Bill Presentment, for example, individual Billers may need to disclose their specific terms and conditions for the Bill Presentment Service. Thus, disclosures may be associated with account-level messages as well as with service-level messages. Note that the disclosure-related structures within IFX were intended for exchange of disclosures related to the electronic service being facilitated by IFX (e.g., online banking, bill payment service, bill presentment service). Disclosures that relate to the underlying product or service, which is being billed in bill presentment, for example, are likely to be customer specific and can be delivered within a bill summary with <BillType> = Notice, using the <Memo> field, or can be displayed within the bill detail. An example would be a gas and electric company who must send notification of rate changes related to gas service. They would use the Bill Summary structure within IFX to send this notification, rather than the Disclosure structure. Disclosures are presented when a service is enabled or an account is activated, and can be obtained in advance using a disclosure inquiry (typically used by an SP to query another SP). Changes to the terms and conditions that were presented to the customer may also need to be presented. These may be considered to be serverinitiated changes and are conveyed to the client through standard IFX mechanisms described below. Disclosures are sent to the client as part of <DiscInqRs>, <CustSvcAddRs>, <CustSvcModRs>, <SvcAcctAddRs>, or <SvcAcctModRs>, and the client sends confirmations using <CustDiscStatusModRq>. The SP must indicate in the appropriate Rs message whether a disclosure should be presented to the customer for information only or whether it requires a confirmation. Note: Customer acceptance of a disclosure is associated with the Disclosure Identifier <DiscId> for that disclosure. If it is necessary to track the version of a disclosure that a customer has accepted, it is recommended that a service provider use a new <DiscId> any time that they modify their disclosure. The <DiscId> itself is the versioning mechanism for disclosures within IFX. Within the Bill Presentment Service, in the event that a Biller needs to republish disclosure information after the initial Bill Presentment account activation, they may choose to send a Bill Summary with the <BillType>=Notice. The Notice provides the ability to send any type of notification information to a customer using the <Memo> field. For disclosure-type notices, the <Memo> field may contain the disclosure text or may give instructions for accessing a URL. Note that this process of utilizing the Bill Summary for the delivery of disclosure information does not provide the Biller with the ability to receive a customer acceptance response. See Section Error: Reference source not found for additional information.
5.4.1.3 Customer Profile Retrieval via Service/Account Link

IFX allows a Service Provider to generate a customer profile, containing a list of the services for which the customer has access and a list of accounts associated with those services, for each customer who identifies himself or herself through an enrollment process. Once a customer is identified, the profile may be automatically generated to include information about the customer and his or her accounts. The Service/Account Link Inquiry message provides an efficient mechanism for client software to determine the current state of the customers accounts and what services are activated. This capability is especially important for customers who use multiple channels or multiple software clients to interact with an SP. The format of the response to a Service/Account Link Inquiry is constant regardless of which SP generates it; however, the content may differ. For example, a CSP may return information about all of the checking accounts for a customer, while the Pay Service Provider may choose to return only the identifiers of the checking accounts that have been identified to it as funding accounts.
5.4.1.4 Using the Customer Profile

A list of available accounts and services is often displayed to the end user so that he or she may select from them. This technique is preferred over asking the user to enter the information since it eliminates the possibility of errors when the user keys in account identifiers; e.g., account number, account type, routing and transit numbers.
Version 1.7
April 2005
27
Interactive Financial Exchange Business Message Specification The list of services available to the customer, or being used by the customer, is contained within <CustSvcRec>. A service is Available if the SP offers the service and the specific customer may enable it. The list of available accounts is contained within <SvcAcctRec>. This aggregate may be used for displaying appropriate candidates for use within a specific service.
5.4.2Customer
5.4.2.1 Customer Add Message
The Customer Add message is used to add a Customer record at a Service Provider. It also allows an individual to submit enough personal information to be identified to a Customer Service Provider. If the CSP supports customer self-enrollment using IFX, it may elect to return a login ID and password to the customer. Alternatively, the CSP may collect the customers information and use a separate process (possibly a mailing or a customer service telephone call) to provide the customer with a login and password. A CSP may choose not to support the Customer Add functionality defined in IFX for enrollment, and may provide a customized World Wide Web (WWW) page or some other means to support its own enrollment process. In this case, the CSP may communicate the URL for this page in the Service Profile. A short note about an alternative enrollment process may also be provided to the client through the Service Profile.
5.4.2.1.1 Request <CustAddRq>

If the CSP supports customer self-enrollment using this message, the CSP may specify what information it must receive to authenticate the customer using the <SecretPrompt> aggregate within the <EnrollProf> aggregate in the Service Profile. Information requested through this mechanism typically includes things like Tax ID, Date of Birth, or Mothers Maiden Name. The customer must provide this information in the <CustAddRq> to prove that the enrollment is valid against existing customer information stored in the SP customer database. The secret list is provided so that a customer new to this channel may be authenticated against existing customer records at the SP. Note that this is a variable-length list, depending on the requirements of the SP as expressed in <SecretPrompt> in the Service Profile. The client should display each <SecretPrompt> and collect customer input. This information is returned in the <SecretList> either in clear text (relying on channel security) or encrypted. Note: The Customer Add message requires special handling because it does not assume that a client is authenticated. By definition, a client that is performing an enrollment using the Customer Add message does not have a Customer Login ID or Password. Therefore, the Signon is likely anonymous under these circumstances.
Type
UUID
Tag
<RqUID>
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustInfo>
Optional Profiled requirement Optional Repeating AND
Customer Information Aggregate.
<SecretList>
Secret List. This aggregate is for a customer to input the secret required for client enrollment.
28
April 2005
Version 1.7
Tag
<CryptType>
Type
Open Enum
Usage
Optional AND Profiled values
Description
Encryption Type. Indicates the encryption algorithm used for the secrets within the <SecretList>. Must be one of the supported types such as the ones defined in the <EnrollProf> aggregate in <BaseSvcProfInfo>. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM
<SecObjId>
Identifier
Optional Repeating AND
Identifier of Security Object on which the <SecretList> is encrypted Note: If security objects are managed in band, this element should be included in order to know how to decrypt <SecretList> Customer ID. Usage is actual <CustId> if preassigned, or preference for SPs that allow customer to pick. Authentication Information. The client may provide information within this aggregate to send to the server the authentication tokens (such as password; other mechanisms will be defined in future releases of IFX) that may be used in future communications with the server.
<CustId>
Aggregate see section 3.2.3.1 Aggregate see section 5.4.2.1.1.1
Optional
<AuthInfo>
Optional
5.4.2.1.1.1 Authentication Information <AuthInfo>

Tag
<CustPswd>
Type
Usage
Optional
Description
Customer Password Aggregate.
5.4.2.1.2 Response <CustAddRs>

The <CustAddRs> message acknowledges the clients Enroll request. If the SP chooses to deliver a Customer Login ID and a password in the response, they are also included. Otherwise, the SP may provide the Customer Login ID and password through the postal mail, electronic mail, or over the telephone. Note: When the <CustAddRs> message is returned in an Audit Response <CustAudRs> or Sync Response <CustSyncRs>, <CryptType> and <PswdDelivery> may not be included, for security reasons.
Type
Tag
<Status>
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Optionally sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier.
Version 1.7
April 2005
29
Tag
<CustInfo>
Type
Aggregate see section 5.2.3.1.1 Aggregate see section 3.2.3.1 Aggregate see section 5.2.3.1 Aggregate see section 5.4.2.1.2.1 Identifier
Usage
Optional Echoed Optional Echoed Required
Description
<CustId>
Customer Login ID.
<CustRec>
Customer Record Aggregate.
<PswdDelivery>
Optional
Password Delivery Aggregate.
<SPRefId>
Optional
5.4.2.1.2.1 Password Delivery Aggregate <PswdDelivery>

Tag
<CustPswd>
Type
Aggregate see section 4.3.1 DateTime
Usage
Required
Description
<ExpDt>
Optional
Password Expiration date and time. If absent, the password never expires.
5.4.2.2 Customer Modify Message

A client may use the Customer Modify message to update his or her name, address, or contact details in the SPs records. For information on Conventions for Modification of Server-Based Data, see Section 2.4.3.2.
5.4.2.2.1 Request <CustModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier. Optionally sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer ID.
<CustInfo>
Required
5.4.2.2.2 Response <CustModRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero).
30
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 5.2.3.1.1 Aggregate see section 5.2.3.1 Identifier
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Required
Asynchronous Request Identifier. Customer ID.
<CustInfo>
<CustRec>
<SPRefId>
Optional
5.4.2.3 Customer Password Modify Message

A client may use the Modify Customer Password message to change the password. The new Customer Password must follow the password rules established in the <SignonInfo> aggregate, and must be encrypted if the Signon Realm requires it. Note: This message will be deprecated in IFX 2.0, replaced by the Customer Authentication Modify (CustAuthMod) message.
5.4.2.3.1 Request <CustPswdModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer ID.
<CustPswd>
Required
5.4.2.3.2 Response <CustPswdModRs>
Version 1.7
April 2005
31
Interactive Financial Exchange Business Message Specification The <CustPswdModRs> message provides the client with an acknowledgement that the Customer Password has been changed. If an error causes a client not to receive a response for a Modify Customer Password message, the server is in an indeterminate state and the client should attempt to establish a session with the new Customer Password. If that attempt fails, the client should attempt to establish a session with the old Customer Password.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 DateTime Identifier
Optional Echoed Optional
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Optional
<ExpDt> <SPRefId>
Password Expiration date and time. If absent, the password never expires. Service Provider Reference Identifier.
5.4.2.4 Customer Authentication Modify Message

A client may use the Customer Authentication Modify message to change the authentication value (e.g. password, certificate, PIN). This may occur with a customer login or a CSR login, as a CSR may need to change the customers password (e.g., when the customer has forgotten the password). Note: This message replaces Customer Password Modify (CustPswdMod), which will be deprecated in IFX 2.0.
5.4.2.4.1 Request <CustAuthModRq>
32
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer Password Aggregate
<CustPswd>
Aggregate see section 4.3.1 Binary NC-32 Open Enum
Required XOR Required XOR Required XOR Optional but see Description
<Certificate> <PINBlock> <CryptType>
Certificate New PIN pad data Encryption Type. <CryptType> will be required in IFX 2.0. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Must be supported in list of encryption types in <SignonInfo> in the CSPs Service Profile. Note: If security objects are managed in band, this element should be included in order to know how to decrypt <PINBlock>
<SecObjId>
Identifier
Identifier of Security Object on which the <PINBlock> is encrypted. <SecObjId> will be required in IFX 2.0 Note: If security objects are managed in band, this element should be included in order to know how to decrypt <PINBlock>
5.4.2.4.2 Response <CustAuthModRs>

The <CustAuthModRs> message provides the client with an acknowledgement that the authentication has been changed. If an error causes a client not to receive a response for a Customer Authentication Modify message, the server is in an indeterminate state and the client should attempt to establish a session with the new authentication value. If that attempt fails, the client should attempt to establish a session with the old authentication value. Note: The authentication credentials are not echoed in this message response in order to reduce the potential for authentication credentials to be stolen.
Version 1.7
April 2005
33
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 DateTime Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Optional
<ExpDt> <SPRefId>
Customer Authentication Expiration date and time. If absent, the authentication value never expires. Service Provider Reference Identifier.
5.4.2.5 Customer Authentication Reversal Message

5.4.2.5.1 Request <CustAuthRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Customer Authentication Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <CustAuthMsgRqInfo>
C-80 Aggregate
Optional Required
34
April 2005
Version 1.7
5.4.2.5.1.1 Customer Authentication Message Request Information Aggregate <CustAuthMsgRqInfo>

Tag
<CustAuthModRq>
Type
Usage
Optional
Description
Customer Authentication Modify Request Message Aggregate.
5.4.2.5.2 Response <CustAuthRevRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Optional Echoed Required Echoed
Asynchronous Request Identifier. Customer Identification Aggregate.
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Customer Authentication Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <CustAuthMsgRqInfo>
C-80 Aggregate
<CSPRefId> <SPRefId>
Optional Optional
5.4.2.6 Customer Status Modify Message

The Customer Status Modify Message may be used to modify the status.
5.4.2.6.1 Request <CustStatusModRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1
Usage
Required Optional
Description
Version 1.7
April 2005
35
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. This is the identifier of the customer whose status is being modified. Customer Status Aggregate.
<CustStatus>
Required
5.4.2.6.2 Response <CustStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer Status Aggregate.
<CustStatus>
Required Echoed Required
<CustRec>
5.4.2.7 Customer Delete Message

A client may use the Customer Delete message to unenroll.
5.4.2.7.1 Request <CustDelRq>
36
April 2005
Version 1.7
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Aggregate see section 3.2.3.1 Boolean
Optional
Customer ID.
<CascadeDel>
Optional
Cascade Delete. If True, server must delete all dependent objects when this object is deleted. If False or omitted, the customer/service link must not be deleted if dependent objects exist. For a service, a dependent object is a service/account link, pending transactions (transfers or payments), recurring models, bills or payees, depending on the service.
5.4.2.7.2 Response <CustDelRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Boolean Aggregate see section 5.2.3.1
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Optional XOR
<CascadeDel> <CustRec>
Cascade Delete. Customer Record Aggregate. This aggregate is provided in cases where the server keeps the customers record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Unenrolled. Dependent object type that exists for the customer/service link. One element must be returned for each dependent. Defined values: CustSvc Service Provider Reference Identifier.
<DependentType>
Open Enum
Optional XOR Repeating Optional
<SPRefId>
Identifier
Version 1.7
April 2005
37
5.4.2.8 Customer Inquiry Message

If <UpDt> is equal the servers date of last update, a <Status> code of 1 is returned, and the profile is not returned in the response. This is the newest <CustRec> <UpDt> received by the client. If this information is absent, or does not match the servers date of last update, the server must send all data in the response.
5.4.2.8.1 Request <CustInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 UUID Aggregate see section 3.2.3.1
Optional
Optional Echoed Optional Repeating
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Magnetic Stripe Data aggregate. This is the card data identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if an ATM issues the request on behalf of the user, then <CardMagData> is required, and must contain the value of the user whose request is being issued. Delivery Method. Default is Channel. Value must be supported in Service Profile. Customer Record Update DateTime. The value is for the last update to <CustRec> on the server that is known to the client. Include Token. If True, a <Token> should be included in the response to set a base for future Service/Account Sync messages. If False or omitted, no <Token> is returned.
<CardMagData>
Aggregate see section 3.2.7.2.4.1
Optional Repeating
<DeliveryMethod>
Open Enum
<UpDt>
Timestamp
<IncToken>
Boolean
Optional
5.4.2.8.2 Response <CustInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed Optional Echoed
<MsgRqHdr>
38
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
Optional Echoed Optional Repeating Echoed
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Magnetic Stripe Data aggregate.
<CardMagData>
Aggregate see section 3.2.7.2.4.1 Open Enum Timestamp Boolean
Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Required Optional Repeating Optional
<DeliveryMethod> <UpDt> <IncToken>
Delivery Method. Customer Record Update DateTime. Include Token. If True, a <Token> should be included in the response to set a base for future Service/Account Sync messages. If False or omitted, no <Token> is returned. New Customer Record Update Date Time. The value is for the last update to <CustRec> on the Server. Customer Record Aggregate. One record is returned for each customer matching the selection criteria in the request. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it.
<NewUpDt> <CustRec>
Timestamp Aggregate see section 5.2.3.1 Identifier
<Token>
5.4.2.9 Customer Identifier Inquiry Message

A client, typically a CSR, may send a request to the Server to retrieve either the Login Id corresponding to a Permanent Id, or the Permanent Id corresponding to a Login Id.
5.4.2.9.1 Request <CustIdInqRq>

The client must specify either the Customer Permanent identifier, or the Customer Login identifier.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
39
Tag
<CustPermId>
Type
Identifier
Usage
Description
Customer Permanent ID. Used as a database key to uniquely identify a Service Providers customer. Cannot be changed by the customer. Customer Login ID. Used as a user-friendly name for the customer for authentication purposes. Maps directly to Customer Permanent ID. Some implementations may allow a user to change his or her Login ID.
<CustLoginId>
Identifier
5.4.2.9.2 Response <CustIdInqRs>

The SP Server responds with a code indicating the processing status and the client identifiers.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1
<MsgRsHdr>
Optional Echoed Required
Note: in cases where there is a <Status> <Severity> of Error, <CustId> is not required in the response. This allows for graceful failures.
5.4.2.10 Customer Audit Message

The Customer Audit Message allows the client to audit Customer Add/Modify/Delete messages. When the Cust object changes, the server must generate an Rs message to the Rq that created the pending state.
5.4.2.10.1 Request <CustAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
40
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional Repeating
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Provider Name. Records Control Input Aggregate.
<SPName> <RecCtrlIn>
Identifier Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.10.1 Closed Enum
Optional Optional
<SelRangeDt>
Optional
Selection Range Date Time Aggregate.
<Method>
Optional Repeating
Customer/Service Link Method. This field is used as a selection criterion. Valid values: Add, Mod, Del.
5.4.2.10.2 Response <CustAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Provider Name. Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and the server supports Records Control.
<SPName> <RecCtrlOut>
Identifier Aggregate see section 3.2.12.4.2
Optional Echoed Optional but see Description
Version 1.7
April 2005
41
Tag
<SelRangeDt>
Type
Aggregate see section 3.2.10.1 Closed Enum Aggregate see section 5.4.2.10.2. 1
Usage
Optional Echoed Optional Repeating Echoed Optional Repeating
Description
Selection Range Date Aggregate.
<Method>
Customer/Service Link Method. This field is used as a selection criterion. Customer Message Record
<CustMsgRec>
5.4.2.10.2.1
Tag
<CustId>
Customer Message Record <CustMsgRec>

Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Customer Add Response Record Aggregate. One record is returned for each Customer Add message for this customer, subject to selection criteria or token. Customer Modify Response Record Aggregate. One record is returned for each Customer Modify message for this customer, subject to selection criteria or token. Customer Status Modify Response Record Aggregate. One record is returned for each Customer Status Modify message for this customer, subject to selection criteria or token. Customer Delete Response Record Aggregate. One record is returned for each Customer Delete message for this customer, subject to selection criteria or token.
<MsgRecDt> <CustAddRs>
Timestamp Aggregate see section 5.4.2.1.2 Aggregate see section 5.4.2.2.2 Aggregate see section 5.4.2.6.2 Aggregate see section 5.4.2.7.2
Optional Required XOR Required XOR Required XOR Required XOR
<CustModRs>
<CustStatusModRs>
<CustDelRs>
5.4.2.11 Customer Sync Message

The Customer Sync Message allows the client to synchronize on Customer Add/Modify/Delete messages. When the Cust object changes, the server must generate an Rs message to the Rq that created the pending state.
5.4.2.11.1 Request <CustSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
42
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Input Aggregate.
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Identifier
Optional
<Token>
Required
Token. Server assigned. Client should make no assumptions about the value of this token relative to others it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
5.4.2.11.2 Response <CustSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required
<MsgRqHdr>
<MsgRsHdr>
Optional Optional Echoed
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and server supports Records Control. Token.
<RecCtrlOut>
Optional but see Description Required Echoed
<Token>
Version 1.7
April 2005
43
Tag
<NewToken>
Type
Identifier
Usage
Required
Description
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others it may have received. The token is only significant to the server that originally assigned it. Customer Message Record
<CustMsgRec>
Aggregate see section 5.4.2.10.2. 1
Optional Repeating
5.4.3Customer/Service Link
5.4.3.1 Customer/Service Link Add
5.4.3.1.1 Request <CustSvcAddRq>
A client uses the <CustSvcAddRq> message to request that a service be enabled. If the <SvcName> value is Pay, then this message indicates enabling the Pay service, and should be sent from the CSP to the CPP; likewise, if the <SvcName> is Pres, then it should be sent to a BSP. The fee account should be passed to Service Providers who are actually charging for the service.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer/Service Link Identification Aggregate
<CustSvcId>
Required
<CustSvcInfo>
Required
Customer/Service Link Information Aggregate
5.4.3.1.2 Response <CustSvcAddRs>

The Customer/Service Link Add Response Message acknowledges receipt of the enabling request. It also optionally allows the SP to return disclosures associated with the activation request. Note: <CustSvcAddRs> may be returned before enabling a service if several steps must be performed in enabling a service. Therefore, a <CustSvcStatusCode> of xxxPending and the Resolve Pending Date may be returned to the CSP and/or Customer to provide an
44
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification estimated date for completion of the request. This may be used, for example, when a CPP does a prenotification for a fee account, since it might take several days to obtain results.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer/Service Link Identification Aggregate.
<CustSvcId>
Aggregate see section 5.2.3.4.1 Aggregate see section 5.2.3.4.2 Aggregate see section 5.2.3.4 Aggregate see section 5.2.3.2 Identifier Identifier
Required Echoed Required Echoed Required
<CustSvcInfo>
<CustSvcRec>
Customer/Service Record Aggregate
<DiscRec>
Optional Repeating Optional Optional
Disclosure Record Aggregate.
Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
5.4.3.2 Customer/Service Link Modify

The <CustSvcModRq> allows a customer to modify specific information about a customer/service link. This capability is currently limited to modifying the fee account.
5.4.3.2.1 Request <CustSvcModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
45
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer/Service Link Identification Aggregate.
<CustSvcId>
Required
<CustSvcInfo>
Required
Customer/Service Link Information Aggregate
5.4.3.2.2 Response <CustSvcModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<CustSvcId>
Aggregate see section 5.2.3.4.1 Aggregate see section 5.2.3.4.2 Aggregate see section 5.2.3.4 Aggregate see section 5.2.3.2
<CustSvcInfo>
<CustSvcRec>
Customer/Service Link Record Aggregate
<DiscRec>
Optional Repeating
46
April 2005
Version 1.7
Tag
Type
Usage
Optional Optional
Description
5.4.3.3 Customer/Service Link Status Modify

The <CustSvcStatusModRq> allows a Service Provider to temporarily change the customers service status. For example, this function is used in the Presentment Service to notify a BSP that the CSP is unable to deliver bills or other material to a customer and to notify the BSP that reverse sthe notification. This may occur when there is a potential security/fraud problem or when a technical problem precludes the customers access to his/her account with the CSP. The BSP may need to notify the Biller to send paper bills, depending on regulatory or business practices, to ensure the customers billing is not interrupted.
5.4.3.3.1 Request <CustSvcStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer/Service Link Identification Aggregate
<CustSvcId>
Required
<CustSvcStatus>
Required
Customer/Service Link Status Aggregate
5.4.3.3.2 Response <CustSvcStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
Version 1.7
April 2005
47
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
<CustSvcId>
Aggregate see section 5.2.3.4.1 Aggregate see section 5.2.3.4.3 Aggregate see section 5.2.3.4 Identifier Identifier
<CustSvcStatus>
Customer/Service Link Status Aggregate
<CustSvcRec>
Customer/Service Link Record Aggregate
Optional Optional
5.4.3.4 Customer/Service Link Delete

5.4.3.4.1 Request <CustSvcDelRq>
The <CustSvcDelRq> allows a customer to disable a service offered by a specified service provider. A customer may initiate the process by sending the <CustSvcDelRq> to the CSP. The CSP may then send a <CustSvcDelRq> message to a BSP to disable, for example, Bill Presentment Service for a particular customer at the BSP.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued.
48
April 2005
Version 1.7
Tag
<CustSvcId>
Type
Usage
Required
Description
Customer/Service Identification Aggregate
<CascadeDel>
Optional
Cascade Delete. If True, server must delete all dependent objects when this object is deleted. If False or omitted, the customer/service link must not be deleted if dependent objects exist. For a service, a dependent object is a service/account link, pending transactions (transfers or payments), recurring models, bills or payees, depending on the service.
5.4.3.4.2 Response <CustSvcDelRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer/Service Identification Aggregate
<CustSvcId>
Aggregate see section 5.2.3.4.1 Boolean Aggregate see section 5.2.3.4
Required Echoed Optional Echoed Optional XOR
<CascadeDel> <CustSvcRec>
Cascade Delete. Customer/Service Link Record Aggregate. This aggregate is provided in cases where the server keeps the customer/service links record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Disabled. Dependent object type that exists for the customer/service link. One element must be returned for each dependent. Defined values: SvcAcct, Bill, CustPayee, Pmt, RecPmt, RecXfer, Xfer Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<DependentType>
Open Enum
Optional Optional
Version 1.7
April 2005
49
5.4.3.5 Customer/Service Link Audit

Allows client to audit Customer/Service Link Add/Modify/Delete messages associated with the current customer. When the <CustSvcStatus> changes, the server must generate an Rs message corresponding to the Rq that created the pending state. The <Status> <Severity> must always be Info. The <StatusDesc> is used to supply the details of a rejection.
5.4.3.5.1 Request <CustSvcAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional Repeating
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.10.1 Closed Enum
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Customer/Service Link Method. This field is used as a selection criterion. Valid values: Add, Mod, Del.
<SvcName>
Open Enum
Service Name Valid values: Bank, Pay, Pres. Service Provider Name.
<SPName>
Identifier
5.4.3.5.2 Response <CustSvcAudRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests.
<RqUID>
Required Echoed
50
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Description
Message Request Header aggregate.
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Open Enum
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
<SelRangeDt>
<Method>
Customer/Service Link Action. Valid values: Add, Mod, Del Service Name Valid values: Bank, Pay, Pres Service Provider Name.
<SvcName>
<SPName>
Identifier
<CustSvcMsgRec>
Customer/Service Message Record.
5.4.3.5.2.1 Customer/Service Message Record Aggregate <CustSvcMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Customer/Service Link Add Response Record Aggregate. One record is returned for each Customer/Service Link Add message for this customer, subject to selection criteria or token. Customer/Service Link Modify Response Record Aggregate. One record is returned for each Customer/Service Link Modify message for this customer, subject to selection criteria or token.
<MsgRecDt>
Timestamp
Optional
<CustSvcAddRs>
Required XOR
<CustSvcModRs>
Required XOR
Version 1.7
April 2005
51
Tag
<CustSvcStatusModRs>
Type
Usage
Required XOR
Description
Customer/Service Link Status Modify Response Record Aggregate. One record is returned for each Customer/Service Link Status Modify message for this customer, subject to selection criteria or token. Customer/Service Link Delete Response Record Aggregate. One record is returned for each Customer/Service Link Delete message for this customer, subject to selection criteria or token.
<CustSvcDelRs>
Required XOR
5.4.3.6 Customer/Service Link Sync

Allows client to synchronize Customer/Service Link Add/Modify/Delete messages associated with the current customer. When the <CustSvcStatus> changes, the server must generate an Rs message corresponding to the Rq that created the pending state. The <Status> <Severity> must always be Info. The <StatusDesc> is used to supply the details of a rejection.
5.4.3.6.1 Request <CustSvcSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
5.4.3.6.2 Response <CustSvcSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
52
April 2005
Version 1.7
Tag
<RqUID>
Type
UUID
Usage
Description
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and server supports Records Control. Token. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others it may have received. The token is only significant to the server that originally assigned it. Customer/Service Message Record.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Identifier Identifier
Optional but see Description Required Echoed Required
<Token> <NewToken>
<CustSvcMsgRec>
Optional Repeating
5.4.4Service/Account Link
5.4.4.1 Bill Presentment
When activating an account for Bill Presentment Service, the customer and/or CSP must send secrets as requested by the Biller, names and addresses as known to the Biller to be associated with the account, and the customer account with the Biller <BillingAcct>, in order for a BSP or a Biller to correctly identify which customer and account to activate. The Customer name and address at the CSP may be used to assist a BSP or Biller in matching the correct customer with the account to be activated.
5.4.4.2 Account specific disclosures

Note that if the Service Provider (e.g., CSP, CPP, or BSP) has account-specific disclosures that were not displayed in the service activation process, the Service Provider must send disclosure text with the <SvcAcctAddRs> when an account is being activated. If presentation of terms and conditions is required prior to account activation, Disclosure Record Aggregates must be returned in the response. If acceptance is required, and the customer does not accept, the account
Version 1.7
April 2005
53
Interactive Financial Exchange Business Message Specification activation may not be sent to the BSP. If the customer does accept, the client may use <CustDiscStatusModRq>.
5.4.4.3 Service/Account Link Add Message

5.4.4.3.1 Request <SvcAcctAddRq>
A client uses the <SvcAcctAddRq> message to request that a particular account be activated for an enabled service, e.g., a long distance telephone account for a bill presentment service. Multiple accounts may be activated by sending a separate <SvcAcctAddRq> for each account to be activated.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service/Account Link Identification Aggregate
<SvcAcctId>
Aggregate see section 5.2.3.5.1 Aggregate see section 5.2.3.5.2 Aggregate see section 3.2.14.2 Open Enum
Required
<SvcAcctInfo>
Required
Service/Account Link Information Aggregate
<SecretList>
Optional Repeating AND Optional Profiled values AND
Secret List. This is the list of responses to <SecretPrompt> provided for account activation in aggregates such as <BillerRec>in Bill Presentment service. Encryption Type. Indicates the encryption algorithm used for the secrets within the <SecretList>. Must be one of the supported types such as the ones defined in the Biller directory entry <BillerRec> for Bill Presentment service. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM
<CryptType>
<SecObjId>
Identifier
Identifier of Security Object on which the <SecretList> is encrypted Note: If security objects are managed in band, this element should be included in order to know how to decrypt <SecretList> Customer Name/Address aggregate. This may be required for account activation, such as when adding a presentment account.
<CustNameAddr>
54
April 2005
Version 1.7
Tag
<PersonInfo>
Type
Usage
Description
Person Information Aggregate.
5.4.4.3.2 Response <SvcAcctAddRs>

The Activate Account Response Message acknowledges receipt of the activate request and contains as much status information as is available. Note: When a CSP activates an account on behalf of a customer, the xSP may return a status description of PendAdd. Upon subsequent Service/Account Link Audit Requests <SvcAcctAudRq> and Service/Account Link Sync Requests <SvcAcctSyncRq>, the Effective Date may be filled in when the account is activated. The <EffDt> is advisory information coming from the xSP.
Type
Tag
<Status>
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service/Account Link Identification Aggregate.
<SvcAcctId>
<SvcAcctInfo>
<SvcAcctRec>
Service/Account Record Aggregate.
<DiscRec>
Version 1.7
April 2005
55
5.4.4.4 Service/Account Link Modify Message

5.4.4.4.1 Request <SvcAcctModRq>
The <SvcAcctModRq> allows a customer to modify specific information about an account. This message is currently limited to modifying (1) a Pay funding account, and (2) the account Nickname.
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service/Account Link Identifier.
<SvcAcctId>
Aggregate see section 5.2.3.5.1 Aggregate see section 5.2.3.5.2 Aggregate see section 3.2.14.2 Open Enum
Required
<SvcAcctInfo>
Required
<SecretList>
Optional Repeating AND Optional Profiled values AND
Secret List. This is the list of responses to <SecretPrompt> provided for account activation in aggregates such as <BillerRec>in Bill Presentment service. Encryption Type. Indicates the encryption algorithm used for the secrets within the <SecretList>. Must be one of the supported types such as the ones defined in the Biller directory entry <BillerRec> for Bill Presentment service. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM
<CryptType>
<SecObjId>
Identifier
Identifier of Security Object on which the <SecretList> is encrypted Note: If security objects are managed in band, this element should be included in order to know how to decrypt <SecretList> Customer Name/Address aggregate. This may be required for account modification, such as with a presentment account. Person Information Aggregate.
<CustNameAddr>
Optional XOR Repeating Optional XOR Repeating
<PersonInfo>
5.4.4.4.2 Response <SvcAcctModRs>
56
April 2005
Version 1.7
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<SvcAcctId>
<SvcAcctInfo>
<SvcAcctRec>
Service/Account Record Aggregate.
<CustDiscRec>
Financial Institution Reference Number. Service Provider Reference Number.
5.4.4.5 Service/Account Link Status Modify

The <SvcAcctStatusModRq> allows a Service Provider to temporarily change the customers service/account link status.
5.4.4.5.1 Request <SvcAcctStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
57
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<SvcAcctId>
Required
<SvcAcctStatus>
Required
Service/Account Link Status Aggregate
5.4.4.5.2 Response <SvcAcctStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<SvcAcctId>
Aggregate see section 5.2.3.5.1 Aggregate see section 5.2.3.5.3 Aggregate see section 5.2.3.5 Identifier Identifier
<SvcAcctStatus>
Service/Account Link Status Aggregate
<SvcAcctRec>
Service/Account Link Record Aggregate
Optional Optional
58
April 2005
Version 1.7
5.4.4.6 Service/Account Link Identifier Modify Message

5.4.4.6.1 Request <SvcAcctIdModRq>
The <SvcAcctIdModRq> allows a customer or CSP to change the identifier associated with a particular Service Account Link. For example, in the Pay service, the <SvcAcctIdModRq> would change all pending payments against a particular funding account to be applied against a new funding account.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service/Account Link Identifier. This is the identifier of the currently linked account to the service. Deposit Account Identifier. This is the identifier of the new account to be linked. Card Account Identifier. This is the identifier of the new account to be linked. Loan Account Identifier. This is the identifier of the new account to be linked. Presentment Account Identifier. This is the identifier of the new account to be linked. Presentment Account Information.
<SvcAcctId>
Required
<DepAcctId>
Required XOR Required XOR Required XOR Required XOR Optional
<CardAcctId>
<LoanAcctId>
<PresAcctId>
<PresAcctInfo>
5.4.4.6.2 Response <SvcAcctIdModRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate.
Version 1.7
April 2005
59
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 5.2.3.5.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.7.3.1 Aggregate see section 3.2.7.3.2 Aggregate see section 5.2.3.5
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Required XOR Echoed Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Echoed Required
<SvcAcctId>
Service/Account Link Identifier.
<DepAcctId>
Deposit Account Identifier.
<CardAcctId>
Card Account Identifier.
<LoanAcctId>
Loan Account Identifier.
<PresAcctId>
Presentment Account Identifier.
<PresAcctInfo>
Presentment Account Information.
<SvcAcctRec>
Service/Account Link Record.
5.4.4.7 Service/Account Link Delete Message

5.4.4.7.1 Request <SvcAcctDelRq>
The <SvcAcctDelRq> allows a customer or CSP to deactivate a specific account for the specified service. Note that deactivating an account in IFX refers to a service provider removing the linkage between the account and the service, and does not impact the status of the actual account, e.g. suspending an electronic billing account should not be confused with halting the actual service, such as turning off the electricity.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
60
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<SvcAcctId>
Required
<CascadeDel>
Optional
Cascade Delete. If True, server must delete all dependent objects when this object is deleted. If False or omitted, the service/account link must not be deleted if dependent objects exist. For a service/account link, a dependent object is pending transactions (transfers or payments), recurring models, bills or payees, depending on the service.
5.4.4.7.2 Response <SvcAcctDelRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<SvcAcctId>
<CascadeDel>
Cascade Delete.
Version 1.7
April 2005
61
Tag
<SvcAcctRec>
Type
Usage
Optional XOR
Description
Service/Account Link Record Aggregate. This aggregate is provided in cases where the server keeps the service/account links record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Deactivated. Dependent object type that exists for the customer/service link. One element must be returned for each dependent. Defined values: SvcAcct, Bill, CustPayee, Pmt, RecPmt, RecXfer, Xfer Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<DependentType>
Open Enum
Optional Optional
5.4.4.8 Service/Account Link Inquiry Message

If <UpDt> is equal the servers date of last update, a <Status> code of 1 is returned, and the profile is not returned in the response. This is the last <NewUpDt> received by the client. If this information is absent, or does not match the servers date of last update, the server must send all data in the response.
5.4.4.8.1 Request <SvcAcctInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Magnetic Stripe Data aggregate. This is the card data identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if an ATM issues the request on behalf of the user, then <CardMagData> is required, and must contain the value of the user whose request is being issued. Records Control Input Aggregate.
<CardMagData>
Optional
<RecCtrlIn>
Optional
62
April 2005
Version 1.7
Tag
<SvcName>
Type
Open Enum
Usage
Optional Repeating
Description
Service Name. This field identifies the specific set of services for which the server should provide customer profile information. This allows the client to scope the profile request to provide account information only for a specific set of services. Defined values: Bank, Pay, Pres
<IncDetail>
Boolean
Optional
Include Detail Indicator. If True, the response should include the detail account records, <xxxAcctRec>, in the aggregates returned. If False, or omitted, the detail account records should not be included. Include Balances Indicator. If True, the <AcctBal> aggregate within <BankAcctRec> is being requested. If False or omitted, the <AcctBal> aggregate within <BankAcctRec> is not being requested. This indicator is only meaningful whenever <IncDetail> is True. Include Token. If True, a <Token> should be included in the response to set a base for future Service/Account Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Default is Channel. Value must be supported in Service Profile. Service/Account Information Update Timestamp. The value is for the last (i.e., latest) update made to either <CustSvcRec>or <SvcAcctRec> on the server that is known to the client.
<IncBal>
Boolean
Optional
<IncToken>
Boolean
Optional
<DeliveryMethod>
Open Enum
<UpDt>
Timestamp
5.4.4.8.2 Response <SvcAcctInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Magnetic Stripe Data aggregate.
<CardMagData>
Optional Echoed
Version 1.7
April 2005
63
Tag
<RecCtrlOut>
Type
Aggregate see section 3.2.12.4.2 Open Enum
Usage
Optional but see Description Optional Repeating Echoed Optional Echoed
Description
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Service Name. Defined values: Bank, Pay, Pres Include Detail Indicator. If True, the response should include the detail account records, <xxxAcctRec>, in the aggregates returned. If False, or omitted, the detail account records should not be included. Include Balances Indicator. If True, the <AcctBal> aggregate within <BankAcctRec> is being requested. If False or omitted, the <AcctBal> aggregate within <BankAcctRec> is not being requested. Include Token. If True, a <Token> should be included in the response to set a base for future Service/Account Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Service Information Update DateTime. New Service/Account Link Update DateTime. The value is for the last (i.e., latest) update made to either <CustSvcRec>or <SvcAcctRec> on the server. Various Account Record Aggregates, as defined in Section 3.2.7. (e.g., <BankAcctRec> and/or <PresAcctRec>) Customer/Service Link Record Aggregate. This aggregate contains the status of a specific service and, if applicable, fee account information associated with the service. Service/ Account Link Record Aggregate. This aggregate identifies an account and its status with respect to a specific service. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it.
<SvcName>
<IncDetail>
Boolean
<IncBal>
Boolean
Optional Echoed
<IncToken>
Boolean
Optional Echoed Optional Echoed Optional Echoed Required
<DeliveryMethod> <UpDt> <NewUpDt>
Open Enum Timestamp Timestamp
<xxxAcctRec> <CustSvcRec>
Aggregate Aggregate see section 5.2.3.4 Aggregate see section 5.2.3.5 Identifier
Optional Repeating Optional Repeating Optional Repeating Optional
<SvcAcctRec>
<Token>
5.4.4.9 Service/Account Link Audit Message

Allows client to audit Service/Account Link Add/Modify/Delete messages associated with the current customer and the current customers accounts. When the <SvcAcctStatus> changes, the server must generate an Rs message corresponding to the Rq that created the pending state. The <Status> <Severity> must always be Info. The <StatusDesc> is used to supply the details of a rejection.
5.4.4.9.1 Request <SvcAcctAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
64
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Service/Account Link Method.This field is used as a selection criterion. Valid values: Add, Mod, StatusMod, Del
5.4.4.9.2 Response <SvcAcctAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
Optional but see Description Optional Echoed
<SelRangeDt>
Version 1.7
April 2005
65
Tag
<Method>
Type
Closed Enum Aggregate see section 5.4.4.9.2.1
Usage
Optional Repeating Echoed Optional Repeating
Description
Service/Account Link Method.
<SvcAcctMsgRec>
Service/Account Link Message Record.
5.4.4.9.2.1 Service Account Message Record <SvcAcctMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Service/Account Link Add Response Record Aggregate. One record is returned for each Service/Account Link Add message for this customer, subject to selection criteria or token. Service/Account Link Modify Response Record Aggregate. One record is returned for each Service/Account Link Modify message for this customer, subject to selection criteria or token. Service/Account Link Status Modify Response Record Aggregate. One record is returned for each Service/Account Link Status Modify message for this customer, subject to selection criteria or token. Service/Account Link Identifier Modify Response Record Aggregate. One record is returned for each Service/Account Link Identifier Modify message for this customer, subject to selection criteria or token. Service/Account Link Delete Response Record Aggregate. One record is returned for each Service/Account Link Delete message for this customer, subject to selection criteria or token. Service/Account Link Reveral Response Record Aggregate. One record is returned for each Service/Account Link Reversal message for this customer, subject to selection criteria or token.
<MsgRecDt>
Timestamp
Optional
<SvcAcctAddRs>
Required XOR
<SvcAcctModRs>
Required XOR
<SvcAcctStatusModRs>
Required XOR
<SvcAcctIdModRs>
Required XOR 1.1+
<SvcAcctDelRs>
Required XOR
<SvcAcctRevRs>
Required XOR
5.4.4.10 Service/Account Link Sync Message

Allows client to synchronize Service/Account Link Add/Modify/Delete messages associated with the current customer and the current customers accounts. When the <SvcAcctStatus> changes, the server must generate an Rs message to the Rq that created the pending state. The <Status> <Severity> must be Info. The <StatusDesc> is used to supply the details of a rejection.
5.4.4.10.1 Request <SvcAcctSyncRq>
66
April 2005
Version 1.7
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
5.4.4.10.2 Response <SvcAcctSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
67
Tag
<RecCtrlOut>
Type
Usage
Description
Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and server supports Records Control. Token. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others it may have received. The token is only significant to the server that originally assigned it.
<Token> <NewToken>
<SvcAcctMsgRec>
Optional Repeating
5.4.4.11 Service Account Reversal

5.4.4.11.1 Request <SvcAcctRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Service Account Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <SvcAcctMsgRqInfo>
C-80 Aggregate see section 5.4.4.11.1. 1
Optional Required
5.4.4.11.1.1 Service Account Message Request Information Aggregate <SvcAcctMsgRqInfo>

Tag
<SvcAcctAddRq>
Type
Usage
Required XOR
Description
Service Account Add Request Message Aggregate.
68
April 2005
Version 1.7
Tag
<SvcAcctModRq>
Type
Usage
Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR
Description
Service Account Modify Request Message Aggregate.
<SvcAcctStatusModRq>
Service Account Stautus Modify Request Message Aggregate. Service Account Delete Request Message Aggregate.
<SvcAcctDelRq>
<SvcAcctInqRq>
Service Account Inquiry Request Message Aggregate.
<SvcAcctAudRq>
Service Account Audit Request Message Aggregate.
<SvcAcctSyncRq>
Service Account Synchronization Request Message Aggregate.
5.4.4.11.2 Response <SvcAcctRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Service Account Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <SvcAcctMsgRqInfo>
C-80 Aggregate see section 5.4.4.11.1. 1 Identifier Identifier
Optional Optional
Version 1.7
April 2005
69
5.4.5Disclosure
5.4.5.1 Disclosure Inquiry Message
A customer or CSP may make a query about disclosure terms and conditions for a given service.
5.4.5.1.1 Request <DiscInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Name. Defined values: Bank, Pay, Pres This element is used as a selection criterion.
<SvcName>
Open Enum
Optional Repeating
<DiscId> <DeliveryMethod>
UUID Open Enum
Optional Repeating Optional Profiled values Optional
Disclosure ID. This element is used as a selection criterion. Delivery Method. Default is Channel. Value must be supported in Service Profile. Timestamp when the Disclosure list was Last Updated on the Server. This is the timestamp of the last Disclosure list received from the server.
<UpDt>
Timestamp
5.4.5.1.2 Response <DiscInqRs>

The SP Server responds with disclosure details.
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
70
April 2005
Version 1.7
Tag
Type
Usage
Description
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Name.
<SvcName>
Open Enum
Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed
<DiscId>
UUID
Disclosure ID. This element is used as a selection criterion.
<DeliveryMethod> <UpDt>
Open Enum Timestamp
Delivery Method. Timestamp when the Disclosure list was last updated on the Server. The last timestamp received by the client.
<NewUpDt> <DiscRec>
Timestamp Aggregate see section 5.2.3.2
Required Optional Repeating
New Disclosure list update timestamp. The value is for the last update to the most recent <DiscRec> on the Server. Disclosure Record Aggregate. One aggregate is returned for each record matching the selection criteria in the request.
5.4.6Customer/Disclosure Link
5.4.6.1 Customer/Disclosure Link Status Modify Message
A customer uses the Customer/Disclosure Link Status Modify Message to accept or reject a disclosure received via various messages.
5.4.6.1.1 Request <CustDiscStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
71
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Disclosure Identifier. Customer/Disclosure Link Status Code Valid values: None, Accepted, Rejected, Viewed
<DiscId> <CustDiscStatusCode>
UUID Closed Enum
Required Required
5.4.6.1.2 Response <CustDiscStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Disclosure Identifier. Customer/Disclosure Link Status Code Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<DiscId> <CustDiscStatusCode> <CSPRefId> <SPRefId>
UUID Closed Enum Identifier Identifier
Required Echoed Required Echoed Optional Optional
5.4.6.2 Customer/Disclosure Link Inquiry Message

A customer or CSP may make a query about the status of a disclosure for a given consumer, and optionally include the associated disclosure itself.
5.4.6.2.1 Request <CustDiscInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier.
72
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Name. Defined values: Bank, Pay, Pres
<SvcName>
Open Enum
Required
<DiscId> <CustDiscStatusCode>
UUID Closed Enum
Optional Optional
Disclosure ID. This element is used as a selection criterion. Customer/Disclosure Link Status Code. This element is used as a selection criterion Valid values: None, Accepted, Rejected, Viewed
<IncDisc>
Boolean
Optional
Include Disclosure Boolean. If True, the client is requesting that <DiscInfo> be included with each record in the response. If False or omitted, the client is requesting that <DiscInfo> not be included with each record in the response. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<DeliveryMethod>
Open Enum
5.4.6.2.2 Response <CustDiscInqRs>

The SP Server responds with disclosure details.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
73
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Name. Disclosure ID. This element is used as a selection criterion. Customer/Disclosure Link Status Code. Include Disclosure Boolean. Delivery Method. Customer/Disclosure Record Aggregate. One aggregate is returned for each record matching the selection criteria in the request. <CustDiscRec> <DiscInfo> may also be returned if <IncDisc> is True.
<SvcName> <DiscId> <CustDiscStatusCode> <IncDisc> <DeliveryMethod> <CustDiscRec>
Open Enum UUID Closed Enum Boolean Open Enum Aggregate see section 5.2.3.3
Required Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
5.5Security Object
The Security Object messages are intended to allow security objects to be transported for use within IFX transactions. Security objects include items such as DES/3DES keys used for PIN encryption, Digital Certificates used for identification and public keys used for data encryption using asynchronous encryption techniques. A unique feature of the security object is the requirement for the object to physically exist at each end-point involved in the encryption process. Unlike a transaction (withdrawal, bill pay, etc) or customer information for which the system of record is in a single location, security objects must exist and be tracked in more than one location and be kept in sync. Note: None of the security object messages contain any of the IFX asynchronous element (AsyncRqUID). This is due to the fact that the exchange of security object information is expected to occur in a synchronous manner.
5.5.1Security Object Add

The Security Object Add message is used to create an instance of a security object.
5.5.1.1 Request <SecObjAddRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 5.2.3.6.1
Usage
Required Optional
Description
Request Identifier. Message Request Header Aggregate
<SecObjInfo>
Required
Security Object Information Aggregate
74
April 2005
Version 1.7
5.5.1.2 Response <SecObjAddRs>

Note:
Tag
<Status>
The encryption keys located in <SecObjInfo> are not echoed in this message response in order to reduce the potential for the encryption keys to be stolen.
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 5.2.3.6.1 Aggregate see section 5.2.3.6 Identifier Identifier
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Message Request Header Aggregate
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Message Response Header Aggregate
<SecObjInfo>
<SecObjRec>
Security Object Record Aggregate
Optional Optional
Customer Service Provider Reference Identifier of the object information is requested on Service Provider Reference Identifier of the object information is requested on.
5.5.2Security Object Modify

The Security Object Modify message provides a mechanism to modify a particular instance of a security object.
5.5.2.1 Request <SecObjModRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Identifier Aggregate see section 5.2.3.6.1
Usage
Required Optional
Description
<SecObjId> <SecObjInfo>
Required Required
Security Object Identifier of security object to be modified Security Object Information Aggregate
5.5.2.2 Response <SecObjModRs>

Note:
Tag
<Status>
The encryption keys located in <SecObjInfo> are not echoed in this message response in order to reduce the potential for the encryption keys to be stolen.
Type
Usage
Optional
Description
Version 1.7
April 2005
75
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 5.2.3.6.1 Aggregate see section 5.2.3.6 Identifier Identifier
Usage
Description
<MsgRsHdr>
<SecObjInfo>
<SecObjRec>
Optional Optional
Customer Service Provider Reference Identifier Service Provider Reference Identifier
5.5.3Security Object Inquiry

This message is sent to request information on a particular security object. Information returned is based on thetype of security object. For symmetric keys, the Key Check information is returned. For Public Keys or Digital certificate, the actual Public Key or Digital Certificate is returned.
5.5.3.1 Request <SecObjInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Identifier C-64 Open Enum
Usage
Required Optional
Description
<SecObjId> <SecObjName> <SecObjPurpose>
Security Object Identifier of security object information is requested on. Security Object Identifier used to reference this security object in future request Purpose (use) of the Security Object Note: The Algorithm that employs this key is agreed to out of band. Valid Values: PINEncryptingKey, KeyEncryptingKey, PasswordEncryptingKey, DataEncryptingKey, Identification, MAC, Uniqueness, VISAPINVerification
<SecObjType>
Open Enum
Optional
Type of Security Object. Valid Value: 1KeyDES, 2KeyDES, 3KeyDES, 128BitAES, 192BitAES, 256BitAES, DigitalCertificate, PublicKey, RandomNumber, ModuleID
Optional Optional
76
April 2005
Version 1.7
Tag
<RecCtrlIn>
Type
Aggregate see section 3.2.12.4.1 Closed Enum
Usage
Optional
Description
Record control input aggregate
<SecObjStatusCode>
Optional Repeating
Returns all security objects that match the status Valid Values: Active, Inactive, Expired, OutofSync
5.5.3.2 Response <SecObjInqRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 5.2.3.6 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<SecObjRec>
Required Repeating Optional Echoed Optional Echoed
5.5.4Security Object Delete

This message is sent to delete a particular instance of a security object.
5.5.4.1 Request <SecObjDelRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Identifier
Usage
Required Optional
Description
<SecObjId>
Required
Security Object Identifier of security object to be modified
5.5.4.2 Response <SecObjDelRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier.
<RqUID>
Required Echoed
Version 1.7
April 2005
77
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Identifier
Usage
Description
Message Request Header Aggregate
<MsgRsHdr>
5.5.5Security Object Advise

The Advise method can be used as a means of either triggering the remote key load process in an ATM or POS System or as a means of providing the server with information on a security object that was loaded into the client via an out of band method (manually loaded, injected from another system, etc.). This method is sent from the Server to the ATM with the <SecObjInitRemKey> tag set to True to request the client to initiate the Remote Key Load process. If the ATM is in a state that would allow it to initiate a remote key load process, the Advise will be responded to with a status code of 0 (OK). If the device is not in a state to initiate a remote key load process, then the Advise will be responded to with an information status code of 3760 and will initiate Remote Key Load process as soon as the state of the device will allow. If the device does not support Remote Key Load, then an error code of 3770 will be returned. If a security object is loaded into the client via an out-of-band method, the client can notify the server of the security objects <SecObjId> as well as the objects characteristics via the inclusion of the <SecObjRec> aggregate.
5.5.5.1 Request <SecObjAdviseRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 5.2.3.6 Boolean
Usage
Required Optional
Description
<SecObjRec>
Information on security object applied to message initiator out-of-band Request for recipient to initiate a Remote Key Load session Valid Values: True, False
<SecObjInitRemKey>
5.5.5.2 Response <SecObjAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
78
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Aggregate see section 3.2.1.2 Aggregate see section 5.2.3.6 Boolean
Usage
Optional
Description
<SecObjRec>
Required XOR Echoed Required XOR Echoed
Information on security object applied to message initiator out-of-band Request for recipient to initiate a Remote Key Load session Valid Values: True, False
<SecObjInitRemKey>
5.5.6Security Object Sync

The sync method can be used as a means of synchronization of the security objects known by either party. Note that actual security objects are not sent as part of this exchange unless the security object is not of a sensitive nature (Module ID, Public Key, etc.). If during this process, it is discovered that one party is missing a security object, an appropriate Security Object Add request should be issued.
5.5.6.1 Request <SecObjSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header Aggregate
<MsgRqHdr>
Optional
<SecObjId>
Optional Repeating Optional
Optional list of security IDs that the issuer is aware of Note: This is not a section criteria for the synchronization Records Control Input Aggregate.
<RecCtrlIn>
<Token>
Required
5.5.6.2 Response <SecObjSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header Aggregate
<RqUID>
<MsgRqHdr>
Version 1.7
April 2005
79
Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Response Header Aggregate
<RqUID>
Required Echoed Optional
<MsgRsHdr>
<SecObjId>
Optional Repeating Echoed Optional but see Description Required Echoed Required
Optional list of security IDs that the issuer is aware of Note: This is not a section criteria for the synchronization Records Control Output Aggregate. Required if client included <RecCtrlIn> in request and server supports Records Control. Token. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others it may have received. The token is only significant to the server that originally assigned it. Optional security object record that contains information on security objects that the server is aware of
<RecCtrlOut>
<Token> <NewToken>
<SecObjRec>
Optional Repeating
5.6Party to Account Relationship

The party to account relationship messages are used to associate a party (i.e., customer, prospect) to and account. This association could be as an owner or non-owner, and is also used to indicate the primary contact and tax responsible parties.
5.6.1Party to Account Relationship Add

This message is used to add a relationship between a pre-existing party (i.e., customer or prospect) and a preexisting account. This message may be used to add additional owners to an account to satisfy the requirements of a legal decision (power of attorney), or to instantiate a new joint owner to an account that has been modified to allow joint accounts.
5.6.1.1 Request <PartyAcctRelAddRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously.
80
April 2005
Version 1.7
Tag
<RqUID> <CustId>
Type
Usage
Required Optional
Description
Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Account Identification Aggregate.
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 5.2.4
Required XOR Required XOR Required XOR Required Repeating
<CardAcctId>
<LoanAcctId>
<PartyAcctRelInfo>
Party to Account Relationship Aggregate.
5.6.1.2 Response <PartyAcctRelAddRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Account Identification Aggregate.
<DepAcctId>
Required XOR Echoed Required XOR Echoed
<CardAcctId>
Version 1.7
April 2005
81
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.7.2.5 Aggregate see section 5.2.4 Aggregate see section 5.2.4.1 Identifier Identifier
Usage
Optional
Description
Status Aggregate
<RqUID> <LoanAcctId>
Required Echoed Required XOR Echoed Required Repeating Echoed Required Repeating Optional Optional
Request Identifier. Loan Account Identification Aggregate.
<PartyAcctRelInfo>
Party to Account Relationship Information Aggregate.
<PartyAcctRelRec>
Party to Account Relationship Record Aggregate
5.6.2Party to Account Relationship Delete

The PartyAcctRelDel will delete the relationship between the party and the account. This will not delete either the party or the account from the system. Under no circumstances will the deletion request delete the last party to account relationship.
5.6.2.1 Request <PartyAcctRelDelRq>

Tag <RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date this activity will take effect. Party to Account Relationship Id.
<EffDt> <PartyAcctRelId>
DateTime Aggregate
Optional Required Repeating
82
April 2005
Version 1.7
5.6.2.2 Response <PartyAcctRelDelRs>

Tag <Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Message Respnse Header Aggregate
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date this activity will take effect. Party to Account Relationship Information Aggregate.
<EffDt> <PartyAcctRelId>
DateTime Aggregate
Optional Echoed Required Repeating Echoed Optional Repeating Optional Optional
<PartyAcctRelRec>
Aggregate see section 5.2.4.1 Identifier Identifier
Party to Account Relationship Record Aggregate
5.6.3Party to Account Relationship Inquiry

The PartyAcctRelInq will inquire on all parties related to a specific account, or inquire on all accounts related to a specific party. If the <DepAcctId>, <CardAcctId>, or the <LoanAcctId> is used in the request, the return base will be all the relationships associated to the account. If none of these three aggregates are present, the return base will be all the accounts related to the party represented within the <CustId>. If both are present, the only search criteria used will be the account information, and the customer Id will represent the customer the request is being acted on behalf of.
5.6.3.1 Request <PartyAcctRelInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
Version 1.7
April 2005
83
Tag
<RqUID> <AsyncRqUID>
Type
UUID UUID
Usage
Required Optional
Description
Request Identifier. Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. For more information, see section 3.2.12.1.
<CustId>
Optional
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.1 Aggregate see section 3.2.12.4.1 Boolean
<CardAcctId>
<LoanAcctId>
<SelRangeDt>
<RecCtrlIn>
Optional
Records Control Input Aggregate.
<OpenAcctInd>
Optional
Option for returning only Open Accounts. If Open Account Indicator = True, only return open accounts.
5.6.3.2 Response <PartyAcctRelInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
84
April 2005
Version 1.7
Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID> <CustId>
Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Account Identification Aggregate.
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.12.4.2 Boolean
Optional XOR Echoed Optional XOR Echoed Optional XOR Echoed Optional but see Description Optional Echoed Required Repeating Optional Optional
<CardAcctId>
<LoanAcctId>
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Option for returning only Open Accounts. If Open Account Indicator =1, only return account with account status =Open Default is 0(No) Party to Account Relationship Record Aggregate.
<OpenAcctInd>
<PartyAcctRelRec>
5.6.4Party to Account Relationship Modify

The PartyAcctRelMod will modify existing relationships, but not add or delete relationships, associated with a specific account. Multiple relationships for one party may be modified with one PartyAcctRelMod message. However, in order to modify relationships for multiple parties, one PartyAcctRelMod message will need to be sent for each party.
5.6.4.1 Request <PartyAcctRelModRq>

Tag <RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
Version 1.7
April 2005
85
Tag <RqUID> <AsyncRqUID>
Type
UUID UUID
Usage
Required Optional
Description
Request Identifier. Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. For more information, see section 3.2.12.1.
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date this activity will take effect. Party Account Relationship Identifier. Party to Account Relationship Aggregate.
<EffDt> <PartyAcctRelId> <PartyAcctRelInfo>
DateTime Aggregate Aggregate see section 5.2.4
Optional Required Required
5.6.4.2 Response <PartyAcctRelModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date this activity will take effect. Party Account Relationship Identifier. Party to Account Relationship Information Aggregate.
<EffDt> <PartyAcctRelId> <PartyAcctRelInfo>
DateTime Aggregate Aggregate see section 5.2.4
Optional Echoed Required Echoed Required Echoed
86
April 2005
Version 1.7
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 5.2.4.1 Identifier Identifier
Usage
Optional
Description
Status Aggregate
<RqUID> <PartyAcctRelRec>
Request Identifier. Party to Account Relationship Record Aggregate
Optional Optional
5.7EMV Card Object

This is a transient object, which only exists temporarily at a terminal while an Integrated Circuit Card is used at the terminal to authorize transactions. The object is created implicitly and destroyed at the end of the transaction or sequence of transactions. This object holds the Data associated with the card and is used to advise the card issuer of changes to the card related data. The primary purpose of this object is to advise a card issuer of Issuer Script Results and Cryptogram Information Data after a transaction has been successfully concluded.
5.7.1EMV Card Record Aggregate <EMVCardRec>

Tag
<EMVCardId> <EMVCardInfo>
Type
Identifier Aggregate see section 5.7.2
Usage
Required Required
Description
EMV Card Identifier. EMV Card Information aggregate
5.7.2EMV Card Info Aggregate <EMVCardInfo>

Tag
<TrnRqUID>
Type
UUID
Usage
Required
Description
Request Identifier of the transaction request / response message pair, in which the associated issuer scripts were received. EMV Request data aggregate
<EMVRqData>
Required
5.7.3EMV Card Advice Request <EMVCardAdviseRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
Version 1.7
April 2005
87
Tag
<EMVCardRec>
Type
Usage
Required
Description
EMV Card Information
Note that in an EMVCardAdviseRq message, it is not necessary to include the (optional) <EMVRqData> in the <MsgRqHdr>, since the same aggregate is contained in the <EMVCardRec>.
5.7.4EMV Card Advise Response <EMVCardAdviseRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 5.7.1
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<EMVCardRec>
Required Echoed
EMV Card Information
Note that the StatusCode of an EMVCardAdviseRs must always be 0. If echoing is disabled, then this message can be empty, as it merely acknowledges receipt of the <EMVCardAdviseRq>.
5.8Card Preference
5.8.1Card Preference Add Message
The Card Preference Add message is used to add a card preference object. This is not used if a card preference relationship has already been established between a card and a business function.
5.8.1.1 Request <CardPrefAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header Aggregate.
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
88
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Information Aggregate.
<CardPrefInfo>
Required
5.8.1.2 Response <CardPrefAddRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Message Response Header Aggregate.
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Information Aggregate.
<CustId>
Optional Echoed
<CardPrefInfo>
Aggregate see section 5.2.7 Aggregate see section 5.2.5 Identifier Identifier
<CardPrefRec>
Card Preference Record Aggregate.
Optional Optional
5.8.2Card Preference Modify Message

The Card Preference Modify message is used to modify a card preference object to alter the preferred account type, amount, or receipt printing option.
Version 1.7
April 2005
89
5.8.2.1 Request <CardPrefModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Identifier. Card Preference Information Aggregate.
<CustId>
Optional
<CardPrefId> <CardPrefInfo>
Required Required
5.8.2.2 Response <CardPrefModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Identifier.
<CustId>
Optional Echoed
<CardPrefId>
Identifier
Required Echoed
90
April 2005
Version 1.7
Tag
<CardPrefInfo>
Type
Usage
Description
Card Preference Information Aggregate.
<CardPrefRec>
Card Preference Record Aggregate.
Optional Optional
5.8.3Card Preference Inquiry Message

The Card Preference Inquiry message is used to inquire on a Card Preference object.
5.8.3.1 Request <CardPrefInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Identifier. This field is used as a selection criterion. Logical Data That Represents the Card. Only fields present in this selection criterion aggregate will be used in the filter comparison. For example, if <CardEmbossNum> is specified but <CardSeqNum> is NOT specified in this aggregate, the inquiry will return any <CardLogicalData> with the same <CardEmbossNum> regardless of the <CardSeqNum> listed on the database. This field is used as a selection criterion.
<CustId>
Optional
<CardPrefId>
Identifier
<CardLogicalData>
Version 1.7
April 2005
91
Tag
<CardPrefType>
Type
Open Enum
Usage
Optional Repeating
Description
Card Preference Types to return (i.e. as defined by the <CardPrefXxx> Aggregate within the <CardPref> Aggregate). For example if two CardPrefType values are included in this inquiry with values of Withdrawal and Deposit, the devices are filtered to only return preferences that contain <CardPrefWithdrawal> and <CardPrefDeposit> aggregates. Defined values: Misc, Withdrawal, Deposit This field is used as a selection criterion.
5.8.3.2 Response <CardPrefInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Identifier. This field is used as a selection criterion. Logical Data That Represents the Card. Only fields present in this selection criterion aggregate will be used in the filter comparison. This field is used as a selection criterion.
<CustId>
Optional Echoed
<CardPrefId>
Identifier
Optional Repeating Echoed Optional Repeating Echoed
<CardLogicalData>
<CardPrefType>
Open Enum
Optional Repeating Echoed
Card Preference Types to return (i.e. as defined by the <CardPrefXxx> Aggregate within the <CardPref> Aggregate). For example if two CardPrefType values are included in this inquiry with values of Withdrawal and Deposit, the devices are filtered to only return preferences that contain <CardPrefWithdrawal> and <CardPrefDeposit> aggregates. Defined values: Misc, Withdrawal, Deposit This field is used as a selection criterion.
92
April 2005
Version 1.7
Tag
<CardPrefRec>
Type
Usage
Optional Repeating
Description
Card Preference Record Aggregate. One record is returned for each preference type specified for which a preference was found.
5.8.4Card Preference Delete Message

The Card Preference Delete message is used to delete a Card Preference object.
5.8.4.1 Request <CardPrefDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<CardPrefId>
Identifier
Required
5.8.4.2 Response <CardPrefDelRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
93
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Identifier. Card Preference Record Aggregate.
<CardPrefId> <CardPrefRec>
Identifier Aggregate see section 5.2.5 Identifier Identifier
Optional Optional
5.8.5Card Preference Audit Message

The Card Preference Audit message is used to audit changes made to a Card Preference object.
5.8.5.1 Request <CardPrefAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Provider Name. Records Control Input Aggregate.
<CustId>
Optional
Optional Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). Valid values: Add, Mod, Can This field is used as a selection criterion.
<CardPrefId>
Identifier
Required Repeating
Card Preference Identifier.
94
April 2005
Version 1.7
5.8.5.2 Response <CardPrefAudRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<CustId>
Optional Echoed
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Required Repeating Echoed Optional Repeating
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Card Preference Identifier.
<CardPrefId>
Identifier
<CardPrefMsgRec>
Card Preference Message Record.
5.8.6Card Preference Sync Message

The Card Preference Sync message is used to synchronize changes made to a Card Preference object.
5.8.6.1 Request <CardPrefSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Version 1.7
April 2005
95
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
Message Request Header Aggregate.
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Input Aggregate.
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<CardPrefId>
Identifier
Required Repeating
Card Preference Identifier.
5.8.6.2 Response <CardPrefSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to buil and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issues. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued.
<CustId>
Optional Echoed
96
April 2005
Version 1.7
Tag
<RecCtrlOut>
Type
Usage
Description
Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Card Preference Identifier.
<CardPrefId>
Identifier
Required Repeating Echoed Optional Repeating
<CardPrefMsgRec>
Card Preference Message Record.
5.8.7Card Preference Reversal Message

The Card Preference Reversal message is used to reverse on operation performed on a Card Preference object.
5.8.7.1 Request <CardPrefRevRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued.
<CustId>
Optional
Version 1.7
April 2005
97
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required
Description
<Desc> <CardPrefMsgRqInfo>
C-80 Aggregate see section 5.2.12
Optional Required
Description, text describing the reason for the reversal. Object Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
5.8.7.2 Response <CardPrefRevRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
98
April 2005
Version 1.7
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required Echoed
Description
<Desc> <CardPrefMsgRqInfo>
C-80 Aggregate see section 5.2.12 Identifier Identifier
Optional Echoed Required Echoed
Description, text describing the reason for the reversal. Object Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
5.8.8Card Preference Status Modify Message

The Card Preference Status Modify message is used to update the status of the Card Preference object.
5.8.8.1 Request <CardPrefStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<CardPrefId>
Identifier
Required
Version 1.7
April 2005
99
Tag
<CardPrefStatus>
Type
Usage
Required
Description
Card Preference Status aggregate.
5.8.8.2 Response <CardPrefStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Card Preference Identifier. Card Preference Status aggregate.
<CustId>
Optional Echoed
<CardPrefId> <CardPrefStatus>
5.9Posting Session
The Posting Session messages are used to control the session parameters for a branch teller, CSR or operator. Once a session is established, the teller, CSR or operator will continue to have a valid session until a Posting Session Status Modification has changed the status to Closed Final. A session may optionally be closed and reestablished with a PostingSessionStatusMod any number of times, until a PostingSessionStatusMod has been sent with a PostingSessionStatusCode of CloseFinal. The implementation of the PostingSessionModRq at the server may control if certain parameters cannot be different than the original parameters and may decline the modification if this is the case. A Posting Session will be considered Closed when either the posting session status is updated to Closed or to Closed Final. Updating the session status to Closed will limit transactions for that session to inquiries only. Changing the status to Closed Final will permanently lock the record and no further updates will be allowed. The session details will be contained in the PostingSessionInfo aggregate.
100
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification A server may optionally retain session totals for the Posting Sessions. The Session Totals inquiry will obtain the totals for either all existing sessions or for a given session. These inquiry messages are being proposed in such a manner as to allow the reuse for other session types beyond posting sessions. These messages are intended to be used within the Bank Services. A posting session identifier may be sent with each teller, CSR or operator transaction to associate the transaction with the given session on the server. This posting session identifier will be contained in the MsgRqHdr. The assumption in these messages is that the person performing the transaction (whether an operator, supervisor, teller) will be identified in the SignOnRq that accompanies the message. If the person performing the transaction differs from the operator to which the posting session is attached, the operator id will be included with the transaction message as the CustId. Eg., If the supervisor is signing on, on behalf of the teller, then the supervisor logon id would be in the SignOnRq while the teller logon id would be in the CustId of the transaction message. Note: reversals of a posting session add, modify, modify status or cancel are not supported.
5.9.1.1 Posting Session Message Record Aggregate <PostingSessionMsgRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp
Usage
Optional
Description
<MsgRecDt>
Optional
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Posting Session Add Response Message Aggregate.
<PostingSessionAddRs>
<PostingSessionModRs>
Posting Session Modify Response Message Aggregate. Posting Session Status Modify Response Message Aggregate.
<PostingSessionStatusModRs>
5.9.2Posting Session Add

The Posting Session Add message is used to establish a Posting Session on the server. The Posting Session Add will not have any effect on any Posting Session totals kept at the server.
5.9.2.1 Request <PostingSessionAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
101
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Session parameters aggregate.
<PostingSessionInfo>
Required
5.9.2.2 Response <PostingSessionAddRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 5.2.14.2 Aggregate see section 5.2.14 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<PostingSessionInfo>
Session parameters aggregate.
<PostingSessionRec>
Session Record aggregate.
Optional Optional
5.9.3Posting Session Modify

The Posting Session Modify message is used to modify an existing Posting Sessions parameters. The Posting Session Mod will not have any effect on any Posting Session totals kept on the server.
5.9.3.1 Request <PostingSessionModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
102
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Posting Session Identifier Session parameters aggregate.
<CustId>
Optional
Required Required
5.9.3.2 Response <PostingSessionModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Posting Session Identifier. Posting Session Information Aggregate.
<CustId>
Optional Echoed
Identifier Aggregate see section 5.2.14.2 Aggregate see section 5.2.14 Identifier Identifier
<PostingSessionRec>
Posting Session Record Aggregate.
Optional Optional
Version 1.7
April 2005
103
5.9.4Posting Session Inquiry

The Posting Session Inquiry messages will return the current session parameters on the server.
5.9.4.1 Request <PostingSessionInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<PostingSessionId>
Posting Session Selection. This field is used as a selection criterion. Posting Session Status. Posting Sessions returned should contain one of PostingSessionStatusCode values included in this request. For example if two PostingSessionStatusCode values are included in this inquiry with values of Active and Inactive, the posting sessions are filtered to only return posting sessions with a status of Active and Inactive. Valid values: Active, Inactive, Expired, Closed, ClosedFinal This field is used as a selection criterion.
Open Enum
<SelRangeDt>
Optional
Selection Range Date Aggregate. Returns all sessions with the <SessionDt> in this range.
5.9.4.2 Response <PostingSessionInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
Required Echoed
104
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Description
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Posting Session Selection. This field is used as a selection criterion.
<CustId>
Optional Echoed
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed
<PostingSessionId>
Open Enum
Posting Session Status. Posting Sessions returned should contain one of PostingSessionStatusCode values included in this request. For example if two PostingSessionStatusCode values are included in this inquiry with values of Active and Inactive, the posting sessions are filtered to only return posting sessions with a status of Active and Inactive. Valid values: Active, Inactive, Expired, Closed, ClosedFinal This field is used as a selection criterion.
<SelRangeDt>
Selection Range Date Aggregate. Returns all sessions with the session date in this range. Posting Session Record Aggregate.
<PostingSessionRec>
5.9.5Posting Session Audit

The Posting Session Audit Message allows the client to audit Posting Session Add/Modify/StatusMod messages.
Version 1.7
April 2005
105
5.9.5.1 Request <PostingSessionAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Provider Name. Records Control Input Aggregate.
Optional Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Customer/Service Link Method. This field is used as a selection criterion. Valid values: Add, Mod, StatusMod
<PostingSessionId>
Identifier
Required
Posting Session Identifier
5.9.5.2 Response <PostingSessionAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
106
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Time Aggregate.
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Required Echoed Optional Repeating
<SelRangeDt>
<Method>
Customer/Service Link Method. This field is used as a selection criterion. Valid values: Add, Mod, StatusMod Posting Session Identifier Posting Session Message Record Aggregate.
<PostingSessionId> <PostingSessionMsgRec>
5.9.6Posting Session Status Modify

The Posting Session Status Modify messages will modify the status of a particular session. A teller, CSR or operator may want to perform this when they want to temporarily suspend the session if they are leaving the workstation. Similarly, they may want to reactivate the session when they want to continue the session upon their return. This could be done by setting PostingSessionStatusModCode to
5.9.6.1 Request <PostingSessionStatusModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
Request Identifier. Message Request Header Aggregate.
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Posting Session Identifier.
<PostingSessionId>
Identifier
Required
Version 1.7
April 2005
107
Tag
<PostingSessionStatus>
Type
Usage
Required
Description
Posting Session Status Aggregate.
5.9.6.2 Response <PostingSessionStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Message Request Header Aggregate.
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Posting Session Identifier. Posting Session Status
<PostingSessionId> <PostingSessionStatus>
Identifier Aggregate see section 5.2.14.1 Identifier Identifier
Customer Service Reference Identifier. Service Provider Reference Identifier.
5.9.7Session Totals Inquiry

The Session Totals Inquiry will return information on a specific session type. If a session identifier is provided, the totals returned will be for the given session only. If no session identifier is provided, the totals returned will be for all sessions on the server.
5.9.7.1 Request <SessionTotalsInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier. Sent by the client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<MsgRqHdr>
Optional
108
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Customer Identification aggregate. This is the identification of the client device for which the request is being issued. This element is required if the owner of the object(s) specified in this request is not the user specified in <SignonRq>. Session Type. This is used to distinguish between different session types that a financial institution may support. Valid values: Customer, Teller, CSR, Operator
<SessionType>
Open Enum
Required
<SessionId>
Identifier
Optional
Session Identifier. This uniquely identifies a session on the server. If thes tag is not present, it is assumed the client is asking for the totals for all existing sessions on the server. This is the selection criterion.
5.9.7.2 Response <SessionTotalsInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by the client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Customer Identification aggregate.
<SessionType>
Session Type. This identifies the type of session. The valid values are: Customer, Teller, CSR, Operator, or POS. Session Identifier. Net Session Totals. The total value of one or more sessions <NetCurAmt> returned in <SessionTotalsRec>
<SessionId> <NetSessionTotals>
Identifier Currency Amount
Version 1.7
April 2005
109
Tag
<SessionTotalsRec>
Type
Usage
Required Repeating
Description
Session totals aggregate. This aggregate will repeat for every session for which totals were returned.
5.10
Base Service Profile <BaseSvcProfInfo>
The Base Service Profile functions the same way as all other services; therefore, it contains a Profile description for that service. Profiles for other services may be found at the end of each chapter of this document. A SP must return a complete set of Profiles for the services that it supports in response to a customer-initiated Service Profile Inquiry <SvcProfInqRq>. The Base Service Profile is defined below. This information is returned to the client in the Service Profile Inquiry message and provides information on how the client should use the Base Service.
Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service. MessagesSupported. Defined values: SvcProfInq, HolInq, CustAdd, CustMod, CustPswdMod, CustAuthMod, CustStatusMod, CustDel, CustInq, CustIdInq, CustAud, CustSync, CustSvcAdd, CustSvcMod, CustSvcStatusMod, CustSvcDel, CustSvcAud, CustSvcSync, SvcAcctAdd, SvcAcctMod, SvcAcctStatusMod, SvcAcctIdMod, SvcAcctDel, SvcAcctInq, SvcAcctAud, SvcAcctSync, CustDiscStatusMod, CustDiscInq, SvcAcctStatusMod, DiscInq, SecObjAdd, SecObjMod, SecObjInq, SecObjAdvise, SecObjDel, SecObjSync, PartyAcctRelAdd, PartyAcctRelDel, PartyAcctRelInq, PartyAcctRelMod, EMVCardAdvise, CardPrefAdd, CardPrefMod, CardPrefInq, CardPrefDel, CardPrefAud, CardPrefSync, CardPrefRev, CardPrefStatusMod, PostingSessionAdd, PostingSessionMod, PostingSessionInq, PostingSessionAud, PostingSessionAud, PostingSessionStatusMod, SessionTotalInq Reversal Options Supported. This is a list of reversal messages supported for the Base Service. The convention is to use the name of the message without the Rq or Rs so that each message is only listed once. Defined values: CardPrefAdd, CardPrefMod, CardPrefDel, CardPrefAud, CardPrefSync, CardPrefStatusMod
<MsgSupt>
Required Repeating
<RevOptSupt>
Open Enum
Optional Repeating
<OptSupt>
Open Enum
Optional Repeating
Options Supported. Defined values: RecCtrl, SuppressEcho, AddReadOnlyAllowed
<SignonInfo>
Required
<EnrollProf>
Optional
Enroll Profile Aggregate.
110
April 2005
Version 1.7
5.10.1
Tag
Signon Information Aggregate <SignonInfo>

Type
Open Enum
Usage
Optional Repeating
Description
Authentication methods supported. Defined values: Password, EmbedCert, TranspCert, MagPIN, SessKey Encryption Type. Required if <AuthSupt> has a value of Password. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Password Modification Required First. If set to True, indicates server requires customer to perform Modify Password message prior to executing any messages other than signon in the first session.
<AuthSupt>
<CryptType>
Open Enum
<ModPswdFirst>
Boolean
Optional
The following five elements provide options of allowable password characters. They are provided to allow the client to validate a customer-entered password during password creation
<Min> <Max> <CharType> Long Long Open Enum Optional Optional Optional Minimum Number of Password Characters. Maximum Number of Password Characters. Character Type Code. Defined values: AlphaOnly, NumericOnly, AlphaOrNumeric, AlphaAndNumeric, Special <CaseSen> <SpaceAlwd> <Memo> Boolean Boolean C-255 Optional Optional Optional Case Sensitive Flag. If set to True, indicates that the password is case-sensitive. Spaces Allowed. If set to True, indicates that the password allows spaces. Memo Text. The text to be displayed to the user to indicate password-formatting rules.
5.10.2
Tag
Enroll Profile Aggregate <EnrollProf>

Type
URL C-255
Usage
Optional Optional
Description
Web URL to start Enrollment Process in lieu of using the <CustAddRq> message. Enrollment Description. Instructions to customer for other enrollment process. For example, the customer services telephone number. Encryption Type. Indicates which encryption types are supported for the secret list in the Enroll message. Defined values: None, PKCS#1 , PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Required if IFX in-band enrollment is supported.
<WebEnrollURL> <EnrollDesc>
<CryptType>
Open Enum
<SecretPrompt>
Optional Repeating
Secret Prompt. If omitted, the SP does not require the customer to enter any secrets for client enrollment. Customer Name Required Indicator. If set to True, SP requires that <CustName> or <PersonName> be included in <CustAddRq>.
<CustNameReqd>
Optional
Version 1.7
April 2005
111
Tag
<PostAddrReqd>
Type
Boolean
Usage
Optional
Description
Customer Postal Address Required Indicator. If set to True, SP requires that <PostAddr> be included in <CustAddRq>.
112
April 2005
Version 1.7
6 The Banking Service <BankSvc>

The IFX Specification provides core-banking capabilities through the Banking Service. The Banking Service includes functions such as Statements and Account Inquiries, Transfers, Recurring Transfers, Customer Communications, and Bank Mail. These banking functions may be applied to either deposit accounts, loan accounts, or credit card accounts.
6.1Description
The Banking Service allows clients to perform the following functions: Statements and Account Inquiries, including Account Balances, Account Detail Inquiry, Account Closing Statement, Account History, and Interest Rate, Account Taxation and Exchange Rate Inquiries. Add, Modify and Delete a Stop Check Add, Modify, and Delete and Interbank Transfers (may be immediate or scheduled), and request Line of Credit Advance and loan repayment Add, Modify and Delete Recurring and Interbank Transfer Models for scheduled recurring transfers Customer Communications such as order a copy of a statement, order check copies, reorder checkbooks, open a term deposit account, order a deposit book, report a lost card, request a copy of a credit card sales slip, report a credit card dispute, report a lost credit card, change the credit limit on a credit card, and send and retrieve banking Email. Debits and Credits with the use of the Add, Modify, Delete a Debit Authorization, and Add Debit. Add, Modify, Delete a Credit Authorization, and Add a Credit.
6.1.1Accounts
The Banking Service specifies accounts using the Account Identification aggregates <DepAcctId>, <LoanAcctId>, and <CardAcctId>
6.1.2Client-Initiated Actions
6.1.2.1 Account Inquiries
The Banking Service provides messages that allow a client to retrieve detailed information about bank accounts, such as balances or previously initiated transactions.
6.1.2.2 Bank Statement View

The Banking Service provides messages that allow a client to retrieve Bank Account Statements for one or more given periods, comparable to traditional paper statements. The Statement includes various balances, and optionally the transaction detail for the statement period.
6.1.2.3 Stop Checks

The Banking Service provides messages that allow a client to stop payment on a check. Messages are also provided to inquire about stopped checks and to play back messages associated with stopped checks.
6.1.2.4 Order Checks

A customer may use the Check order messages to request that an order of checks be sent. The customer may specify the total quantity of checks to be sent, starting number of the checks, and style of the checks. The customer can also issue messages to establish recurring check orders.
Version 1.7
April 2005
6.1.2.5 Order Deposit Books

A customer may use the Deposit Book Order message to request that deposit book be sent.
6.1.2.6 Retrieve Interest Rates

A customer may request quotes on interest rates for a variety of financial products using the Interest Rate Inquiry message. The customer enters the Account Type, Tax Status, Amount, and Term, and the message returns the current interest rates.
6.1.2.7 Add, Modify, and Delete Transfers

A customer may add, modify, or delete a non-recurring funds transfer.
6.1.2.8 Add, Modify and Delete Recurring Transfer Models

Messages are also provided in the Banking Service to allow a client to manage models for fixed amount recurring funds transfers. The customer enters parameters, such as the transfer amount, the date of the first transfer, the frequency of the transfers, and the term of the model, and the Financial Institution automatically generates transfers based on this model at the requested frequency for the model term. Recurring transfer models may be closed-ended or open-ended (if no term is provided).
6.1.2.9 Credit Card Messages

The Banking Service provides customer service messages related to credit card accounts, including client request for a sales slip copy or report of a credit card dispute.
6.1.2.10 Debit and Credit Messages

The Banking Service provides debit messages to allow cash withdrawals, stamp dispensing, point-of-sale purchases, and similar transactions that incur a debit to an account. Credit messages are provided for cash and check deposits, which involve a credit to an account.
6.1.2.11 Deposit Account Application

A customer may use the Deposit Account Application messages to apply for a deposit account with a financial institution.
6.2Banking Service Message Summary

Required
Yes
Comments
Allows the client to retrieve a current view of the services supported by the SP, the Authentication Realms that must be used for authentication, and basic information about the SP. Allows client to retrieve appropriate balances as of the time the message is executed based on the type of Banking Account. Allows a client to reverse a previous request for a balance inquiry.
Balance Inquiry
<BalInqRq> <BalInqRs>
Balance Reversal
<BalRevRq> <BalRevRs>
Account Inquiry
<AcctInqRq> <AcctInqRs>
Allows client to retrieve current information about the Account that varies by account type. This inquiry includes balances, but does not include message detail.
April 2005
Version 1.7
Function / Message Name Account Reversal

<AcctRevRq> <AcctRevRs>
Required
Comments
Allows a client to reverse a previous request for an account inquiry.
Deposit Account Statement Inquiry

<DepAcctStmtInqRq> <DepAcctStmtInqRs>
Allows client to retrieve a Deposit Account Closing Statement for one or more given periods, comparable to a traditional paper statement. The Closing Statement includes Opening, Closing, and Minimum Ledger Balances and optionally the messages detail for the statement period Allows a client to reverse a previous request for a deposit account statement inquiry.
Deposit Account Statement Reversal

<DepAcctStmtRevRq> <DepAcctStmtRevRs>
Deposit Account Statement Advise
Allows a client to advise an entity of account information for a statement period.
<DepAcctStmtAdviseRq> <DepAcctStmtAdviseRs>
Credit Card Statement Inquiry

<CCAcctStmtInqRq> <CCAcctStmtInqRs>
Allows client to retrieve a Credit Card Account Closing Statement for one or more given periods, comparable to a traditional paper statement. The Closing Statement includes Opening and Closing Credit Card Balances, as well as Date Due and a number of summary level amounts and optionally the messages detail for the statement period Allows a client to reverse a previous request for a credit card statement inquiry.
Credit Card Statement Reversal

<CCAcctStmtRevRq> <CCAcctStmtRevRs>
Deposit Account Transaction Inquiry

<DepAcctTrnInqRq> <DepAcctTrnInqRs>
Allows client to retrieve the financial messages posted against an account over a specified time period.
Deposit Account Transaction Reversal

<DepAcctTrnRevRq> <DepAcctTrnRevRs>
Allows a client to reverse a previous request for a deposit account transaction inquiry.
Card Account Transaction Inquiry

<CCAcctTrnInqRq> <CCAcctTrnInqRs>
Allows a client to retrieve the financial messages posted against an account over a specified time period.
Card Account Transaction Reversal

<CCAcctTrnRevRq> <CCAcctTrnRevRs>
Allows a client to reverse a previous request for a card account transaction inquiry.
Bank Account Transaction Image Inquiry

<BankAcctTrnImgInqRq> <BankAcctTrnImgInqRs>
Allows a client to request a copy of a check or sales slip.
Bank Account Transaction Image Reversal

<BankAcctTrnImgRevRq> <BankAcctTrnImgRevRs>
Allows a client to reverse a previous request for a bank account transaction image inquiry.
Version 1.7
April 2005
Function / Message Name Interest Rate Inquiry

<IntRateInqRq> <IntRateInqRs>
Required
Comments
Allows client to retrieve a list of financial products and their associated interest rates.
Interest Rate Reversal

<IntRateRevRq> <IntRateRevRs>
Allows a client to reverse a previous request for an interest rate inquiry.
Bank Account Taxation Inquiry

<BankAcctTaxInqRq> <BankAcctTaxInqRs>
Allows client to request details of taxation on a specific bank account.
Foreign Exchange Rate Inquiry

<ForExRateInqRq> <ForExRateInqRs>
Allows client to inquire about an exchange rate from a Financial Institution, and to optionally request an exchange rate commitment Allows a client to reverse a previous request for a foreign exchange rate inquiry.
Foreign Exchange Rate Reversal

<ForExRateRevRq> <ForExRateRevRs>
Stop Check Add

<StopChkAddRq> <StopChkAddRs>
Allows a client to stop a check or a range of checks.
Stop Check Cancel

<StopChkCanRq> <StopChkCanRs>
Allows client to cancel a previous Stop Check request with a Financial Institution.
Stop Check Inquiry

<StopChkInqRq> <StopChkInqRs>
Allows client to view current Stopped Check records.
Stop Check Audit

<StopChkAudRq> <StopChkAudRs>
Allows client to play back Stopped Check messages associated with the current customer since some past point in time. Allows client to play back Stopped Check messages associated with the current customer since some past point in time.
Stop Check Synchronization

<StopChkSyncRq> <StopChkSyncRs>
StopChk Advise
<StopChkAdviseRq> <StopChkAdviseRs>
Stop Check Reveresal

<StopChkRevRq> <StopChkRevRs>
Allows a client to reverse a previous stop check request message.
Funds Transfer Add

<XferAddRq> <XferAddRs>
Allows client to schedule a Funds Transfer. Includes immediate transfer.
April 2005
Version 1.7
Function / Message Name Funds Transfer Modify

<XferModRq> <XferModRs>
Required
Comments
Allows client to modify a pending Transfer.
Funds Transfer Status Modify

<XferStatusModRq> <XferStatusModRs>
Allows client to modify Funds Transfer Status.
Funds Transfer Cancel

<XferCanRq> <XferCanRs>
Allows client to cancel a pending Funds Transfer.
Funds Transfer Inquiry

<XferInqRq> <XferInqRs>
Allows client to view Funds Transfer records.
Funds Transfer Audit

<XferAudRq> <XferAudRs>
Allows client to play back the Funds Transfer messages associated with the current customer since some past point in time.
Xfer Advise
<XferAdviseRq> <XferAdviseRs>
Funds Transfer Reversal

<XferRevRq> <XferRevRs>
Allows a client to reverse a previous funds transfer request message.
Funds Transfer Synchronization

<XferSyncRq> <XferSyncRs>
Allows client to play back the Funds Transfer messages associated with the current customer since some past point in time. Allows client to create a Recurring Transfer Model.
Recurring Transfer Model Add

<RecXferAddRq> <RecXferAddRs>
Recurring Transfer Model Modify

<RecXferModRq> <RecXferModRs>
Allows client to modify an existing Recurring Transfer Model.
Recurring Transfer Model Cancel

<RecXferCanRq> <RecXferCanRs>
Allows client to cancel an existing Recurring Transfer Model.
Recurring Transfer Model Inquiry

<RecXferInqRq> <RecXferInqRs>
Allows client to retrieve current Recurring Transfer Model records.
Recurring Transfer Model Audit

<RecXferAudRq> <RecXferAudRs>
Allows client to play back the messages associated with the model itself, as opposed to messages that are created by it, for the current customer since some past point in time.
Version 1.7
April 2005
Function / Message Name Recurring Transfer Model Synchronization

<RecXferSyncRq> <RecXferSyncRs>
Required
Comments
Allows client to play back the messages associated with the model itself, as opposed to messages that are created by it, for the current customer since some past point in time. Allows a client to reverse a previous recurring transfer model request message.
Recurring Transfer Model Reversal
<RecXferRevRq> <RecXferRevRs>
Check Order Add

<ChkOrdAddRq> <ChkOrdAddRs>
Allows client to reorder checks.
Check Order Modify

<ChkOrdModRq> <ChkOrdModRs>
Allows client to modify an existing check order.
Check Order Cancel

<ChkOrdCanRq> <ChkOrdCanRs>
Allows client to cancel an existing check order.
Check Order Inquiry

<ChkOrdInqRq> <ChkOrdInqRs>
Allows client to retrieve current check order records.
Check Order Audit

<ChkOrdAudRq> <ChkOrdAudRs>
Allows client to play back the Check Order messages associated with the current customer since some past point in time. Allows client to play back the Check Order messages associated with the current customer since some past point in time.
Check Order Synchronization

<ChkOrdSyncRq> <ChkOrdSyncRs>
ChkOrd Advise
<ChkOrdAdviseRq> <ChkOrdAdviseRs>
Check Order Reversal

<ChkOrdRevRq> <ChkOrdRevRs>
Allows a client to reverse a previous check order request message.
Recurring Check Order Add

<RecChkOrdAddRq> <RecChkOrdAddRs>
Allows client to create a Recurring Check Order Model.
Recurring Check Order Model Modify

<RecChkOrdModRq> <RecChkOrdModRs>
Allows client to modify an existing Recurring Check Order Model.
Recurring Check Order Model Cancel

<RecChkOrdCanRq> <RecChkOrdCanRs>
Allows client to cancel an existing Recurring Check Order Model.
April 2005
Version 1.7
Function / Message Name Recurring Check Order Model Inquiry

<RecChkOrdInqRq> <RecChkOrdInqRs>
Required
Comments
Allows client to retrieve current Recurring Check Order Model records.
Recurring Check Order Model Audit

<RecChkOrdAudRq> <RecChkOrdAudRs>
Allows client to play back the messages associated with the model itself, as opposed to messages that are created by it, for the current customer since some past point in time. Allows client to play back the messages associated with the model itself, as opposed to messages that are created by it, for the current customer since some past point in time. Allows a client to request a one-off instance of a recurring check order.
Recurring Check Order Model Synchronization

<RecChkOrdSyncRq> <RecChkOrdSyncRs>
Recurring Check Order Instance Add

<RecChkOrdInstAddRq> <RecChkOrdInstAddRs>
Deposit Book Order Add

<DepBkOrdAddRq> <DepBkOrdAddRs>
Allows client to order a Deposit Book from a Financial Institution.
DepBkOrd Advise
<DepBkOrdAdviseRq> <DepBkOrdAdviseRs>
Deposit Book Order Reversal

<DepBkOrdRevRq> <DepBkOrdRevRs>
Allows a client to reverse a previous deposit book order request message.
Debit Authorization Add

<DebitAuthAddRq> <DebitAuthAddRs>
Allows a client to request authorization for a debit to a specified account.
Debit Authorization Modify

<DebitAuthModRq> <DebitAuthModRs>
Allows a client to modify the details of a debit authorization
Debit Authorization Status Modify <DebitAuthStatusModRevRq> <DebitAuthStatusModRevRs> Debit Authorization Cancel

<DebitAuthCanRq> <DebitAuthCanRs>
Allows a client to change the status of a debit authorization.
Allows a client to cancel a debit authorization.
Debit Authorization Inquiry

<DebitAuthInqRq> <DebitAuthInqRs>
Allows a client to view debit authorization records.
Debit Authorization Audit

<DebitAuthAudRq> <DebitAuthAudRs>
Allows a client to play back the Debit authorization messages associated with the current customer since some past point in time.
DebitAuth Advise
<DebitAuthAdviseRq> <DebitAuthAdviseRs>
Version 1.7
April 2005
Function / Message Name Debit Authorization Reversal

<DebitAuthRevRq> <DebitAuthRevRs>
Required
Comments
Allows a client to reverse a previous debit authorization request message.
Debit Authorization Synchronization

<DebitAuthSyncRq> <DebitAuthSyncRs>
Allows a client to synchronize the Debit authorization messages associated with the current customer since some past point in time. Allows a client to debit a specified account.
Debit Add
<DebitAddRq> <DebitAddRs>
Debit Reversal
<DebitRevRq> <DebitRevRs>
Allows a client to reverse a previous debit request message.
Debit Modify
<DebitModRq> <DebitModRs>
Allows a client to modify the details of a debit.
Debit Cancel
<DebitCanRq> <DebitCanRs>
Allows a client to cancel a debit.
Debit Inquiry
<DebitInqRq> <DebitInqRs>
Allows a client to retrieve debit records.
Debit Audit
<DebitAudRq> <DebitAudRs>
Allows a client to play back the debit messages associated with the current customer since some past point in time. Allows a client to synchronize the debit messages associated with the current customer since some past point in time.
Debit Synchronize
<DebitSyncRq> <DebitSyncRs>
Debit Advise
<DebitAdviseRq> <DebitAdviseRs>
Debit Status Modify

<DebitStatusModRq> <DebitStatusModRs>
Allows a client to change the status of a debit.
Credit Authorization Add

<CreditAuthAddRq> <CreditAuthAddRs>
Allows a client to request authorization for a credit to a specified account.
Credit Authorization Modify

<CreditAuthModRq> <CreditAuthModRs>
Allows a client to modify the details of a credit authorization
April 2005
Version 1.7
Function / Message Name Credit Authorization Cancel

<CreditAuthCanRq> <CreditAuthCanRs>
Required
Comments
Allows a client to cancel a credit authorization
Credit Authorization Inquiry

<CreditAuthInqRq> <CreditAuthInqRs>
Allows a client to view credit authorization records
Credit Authorization Audit

<CreditAuthAudRq> <CreditAuthAudRs>
Allows a client to play back the credit authorization messages associated with the current customer since some past point in time. Allows a client to synchronize the credit authorization messages associated with the current customer since some past point in time.
Credit Authorization Synchronization

<CreditAuthSyncRq> <CreditAuthSyncRs>
CreditAuth Advise
<CreditAuthAdviseRq> <CreditAuthAdviseRs>
Credit Authorization Reversal

<CreditAuthRevRq> <CreditAuthRevRs>
Allows a client to reverse a previous credit authorization request message.
Credit Authorization Status Modify

<CreditAuthStatusModRq> <CreditAuthStatusModRs>
Allows a client to change the status of a credit authorization.
Credit Add
<CreditAddRq> <CreditAddRs>
Allows a client to credit a specified account.
Credit Modify
<CreditModRq> <CreditModRs>
Allows a client to modify the details of a credit.
Credit Cancel
<CreditCanRq> <CreditCanRs>
Allows a client to cancel a credit.
Credit Inquiry
<CreditInqRq> <CreditInqRs>
Allows a client to retrieve credit records.
Credit Audit
<CreditAudRq> <CreditAudRs>
Allows a client to play back the credit messages associated with the current customer since some past point in time. Allows a client to synchronize the credit messages associated with the current customer since some past point in time.
Credit Synchronize
<CreditSyncRq> <CreditSyncRs>
Version 1.7
April 2005
Function / Message Name Credit Status Modify

<CreditStatusModRq> <CreditStatusModRs>
Required
Comments
Allows a client to change the status of a credit.
Credit Advise
<CreditAdviseRq> <CreditAdviseRs>
Credit Reversal
<CreditRevRq> <CreditRevRs>
Allows a client to reverse a previous credit request message.
Deposit Account Application Add

<DepAppAddRq> <DepAppAddRs>
Allows client to apply for a Deposit Account.
Deposit Account Application Modify

<DepAppModRq> <DepAppModRs>
Allows client to modify a pending Deposit Account Application.
Deposit Account Application Cancel

<DepAppCanRq> <DepAppCanRs>
Allows client to cancel a pending Deposit Account Application.
Deposit Account Application Inquiry

<DepAppInqRq> <DepAppInqRs>
Allows client to view Deposit Account Application records.
Deposit Account Application Audit

<DepAppAudRq> <DepAppAudRs>
Allows client to play back the Deposit Account Application messages associated with the current customer since some past point in time. Allows client to play back the Deposit Account Application messages associated with the current customer since some past point in time.
Deposit Account Application Synchronization

<DepAppSyncRq> <DepAppSyncRs>
Bank Account Statement Image Inquiry

<BankAcctStmtImgInqRq> <BankAcctStmtImginqRs>
Allows a client to retrieve pre-rendered bank account statements.
Bank Account Statement Image Reversal

<BankAcctStmtImgRevRq> <BankAcctStmtImgRevRs>
Allows a client to reverse a previous request for a bank account statement image.
Payment Enclosed Add

<PmtEnclAddRq> <PmtEnclAddRs>
Allows a client to make a payment towards an outstanding debt. The payment may be in an envelope or the payment and remittance slip may be scanned. Allows a client to modify a payment enclosed.
Payment Enclosed Modify

<PmtEnclModRq> <PmtEnclModRs>
10
April 2005
Version 1.7
Function / Message Name Payment Enclosed Inquiry

<PmtEnclInqRq> <PmtEnclInqRs>
Required
Comments
Allows a client to retrieve payment enclosed records.
Payment Enclosed Cancel

<PmtEnclCanRq> <PmtEnclCanRs>
Allows a client to cancel a payment enclosed.
PmtEncl Advise
<PmtEnclAdviseRq> <PmtEnclAdviseRs>
Payment Enclosed Reversal

<PmtEnclRevRq> <PmtEnclRevRs>
Allows a client to reverse a previous payment enclosed request message.
Payment Enclosed Status Modify

<PmtEnclStatusModRq> <PmtEnclStatusModRs>
Allows a client to modify a payment enclosed status.
Check Issue Add

<ChkIssueAddRq> <ChkIssueAddRs>
Allows a client to request check issue information to be added.
Chieck Issue Modify

<ChkIssueModR> <ChkIssueModRs>
Allows a client to modify the details of check issue information.
Check Issue Status Modify

<ChkIssueStatusModRq> <ChkIssueStatusModRs>
Allows a client to modify the status of the details of check issue information.
Check Issues Delete

<ChkIssueDelRq> <ChkIssueDelRs>
Allows a client to delete the details of check issue information.
Check Issue Inquiry

<ChkIssueInqRq> <ChkIssueInqRs>
Allows a client to view the details of check issue information.
Check Issue Audit

<ChkIssueAudRq> <ChkIssueAudRs>
Allows a client to play back the check issue messages associated with the current customer since some past point in time. Allows a client to synchronize the check issue messages associated with the current customer since some past point in time. Allows a client to request bank service Checksum information to be added.
Check Issue Sync

<ChkIssueSyncRq> <ChkIssueSyncRs>
Bank Service Checksum Add

<BankSvcChkSumAddRq> <BankSvcChkSumAddRs>
Version 1.7
April 2005
11
Function / Message Name Bank Service Checksum Modify

<BankSvcChkSumModRq> <BankSvcChkSumModRs>
Required
Comments
Allows a client to modify bank service Checksum information.
Bank Serice Checksum Status Modify

<BankSvcChkSumStatusModRq> <BankSvcChkSumStatusModRs> Bank Service Checksum Delete <BankSvcChkSumDelRq> <BankSvcChkSumDelRs>
Allows a client to modify the status of bank service Checksum information.
Allows a client to delete bank service Checksum information.
Bank Service Checksum Inquiry

<BankSvcChkSumInqRq> <BankSvcChkSumInqRs>
Allows a client to view the bank service Checksum information.
Bank Service Checksum Audit

<BankSvcChkSumAudRq> <BankSvcChkSumAudRs>
Allows a client to play back the bank service Checksum messages associated with the current customer since some past point in time. Allows a client to synchronize the bank service Checksum messages associated with the current customer since some past point in time. Allow a client to accept a check and send it to a check issuer to verify the check is good.
Bank Service Checksum Synchronize

<BankSvcChkSumSyncRq> <BankSvcChkSumSyncRs>
Check Accept Add

<ChkAcceptAddRq> <ChkAcceptAddRs>
Check Accept Modify

<ChkAcceptModRq> <ChkAcceptModRs>
Allows a client to modify the details of a Check Accept object.
Check Accept Inquiry

<ChkAcceptInqRq> <ChkAcceptInqRs>
Allows a client to inquire on the details of a Check Accept object.
Check Accept Cancel

<ChkAcceptCanRq> <ChkAcceptCanRs>
Allows a client to cancel a previous Check Accept object.
Check Accept Audit

<ChkAcceptAudRq> <ChkAcceptAudRs>
Allows a client to play back the Check Accept messages associated with the current customer since some past point in time. Allows a client to synchronize the Check Accept messages associated with the current customer since some past point in time. Allows a client to reverse a previous Check Accept message.
Check Accept Sync

<ChkAcceptSyncRq> <ChkAcceptSyncRs>
Check Accept Reversal

<ChkAcceptRevRq> <ChkAcceptRevRs>
Check Accept Status Modify

<ChkAcceptStatusModRq> <ChkAcceptStatusModRs>
Allows a client to change the status of an Check Accept Object.
12
April 2005
Version 1.7
Function / Message Name Passbook Add

<PassbkAddRq> <PassbkAddRs>
Required
Comments
Used to add a logical passbook to an account. This is not used if a passbook relationship has already been established for an account. Used to modify the passbook object most likely to set the Id of the last printed Item, and the next line at which printing should begin. Used to inquire on a passbook object.
Passbook Modify
<PassbkModRq> <PassbkModRs>
Passbook Inquiry
<PassbkInqRq> <PassbkInqRs>
Passbook Delete
<PassbkDelRq> <PassbkDelRs>
Used to delete a logical passbook from an account.
Passbook Audit
<PassbkAudRq> <PassbkAudRs>
To audit changes to a Passbook object.
Passbook Sync
<PassbkSyncRq> <PassbkSyncRs>
To synchronize changes to a Passbook object.
Passbook Reversal
<PassbkRevRq> <PassbkRevRs>
Used to reverse an operation on the Passbook object.
Passbook Status Modify

<PassbkStatusModRq> <PassbkStatusModRs>
Used to update the status of a passbook.
Passbook Item Add

<PassbkItemAddRq> <PassbkItemAddRs>
Used to add a line into a passbook. Standard transactions are considered to be added automatically (through back-end processing). Used to modify an item in the passbook. Although this message may be defined, in all practical situations no passbook holder or bank staff would likely have permission to use this message. Used to inquire on PassbkItems for a specific passbook given the Passbook Id. This is the main message used when performing a Passbook update. Used to delete a line from a passbook. Although this message may be defined, in all practical situations no passbook holder or bank staff would likely have permission to use this message. Used to Audit the Passbook Item object.
Passbook Item Modify

<PassbkItemModRq> <PassbkItemModRs>
Passbook Item Inquiry

<PassbkItemInqRq> <PassbkItemInqRs>
Passbook Item Delete

<PassbkItemDelRq> <PassbkItemDelRs>
Passbook Item Audit

<PassbkItemAudRq> <PassbkItemAudRs>
Passbook Item Sync

<PassbkItemSyncRq> <PassbkItemSyncRs>
Used to synchronize the Passbook Item object.
Passbook Item Reversal

<PassbkItemRevRq> <PassbkItemRevRs>
Used to reverse a Passbook Item operation.
Version 1.7
April 2005
13
Function / Message Name Passbook Item Status Modify

<PassbkItemStatusModRq> <PassbkItemStatusModRs>
Required
Comments
Used to update the Status of the Passbook Item.
6.3Banking Service Common Aggregates

6.3.1Bank Service Checksum Record Aggregate <BankSvcChkSumRec>
Tag
<BankSvcChkSumId> <BankSvcChkSumInfo>
Type
Usage
Required Required
Description
Bank Service Checksum Identifier. Assigned by the server at the time the bank service Checksum is first added. Bank Service Checksum Information Aggregate.
<BankSvcChkSumStatus>
Required
Bank Service Checksum Status Aggregate.
6.3.1.1 Bank Service Checksum Information Aggregate <BankSvcChkSumInfo>

The Bank Service Checksum Information <BankSvcChkSumInfo> aggregate provides information about the check file and its summary control totals. These control totals provide information necessary for the server to verify the data contained in a Pay Service Request <PaySvcRq>.
Tag
<RefInfo>
Type
Aggregate see section 3.2.17 Open Enum
Usage
Optional
Description
Issuance transaction reference Identifier number. Identifier for the transaction file generated by the client. Bank Service Checksum Message Type. Message type of transaction being calculated for the Bank Service Checksum. Defined values: All IFX Add and Mod Messages in Banking Services. Example: XferModRq, StopChkAddRq, etc.
<MsgType>
Required
<Count>
Long
Required
Transaction count. This count indicates how many request messages should be contained in the file or <BankSvcRq>. Bank Service Checksum Aggregate. Defines different types of Checksum and values for verification of control Checksum totals with file transactions. Example: transaction amount sum, account Id sum or bank Id sum (foreign payment transactions).
<BankSvcChkSum>
Optional Repeating
6.3.1.1.1 Bank Service Checksum Aggregate <BankSvcChkSum>
14
April 2005
Version 1.7
Tag
<BankSvcChkSumType>
Type
Open Enum
Usage
Required
Description
Bank Service Checksum Type. Identifies the type of Checksum that is contained in <BankSvcChkSumValue>. Defined values: Sum, Hash, AcctId, BankId
<BankSvcChkSumValue>
Decimal
Required
Bank Service Checksum Value. Value of Bank Service Checksum type <BankSvcChkSumType>. Example, if used for the sum, <BankSvcChkSumValue> contains the total amount of all transactions of the file, without currency implication. Thus it contains the total of all <CurAmt>s in all <RemitInfo>s of the associated <BankSvcRq>, reflecting all items in the file.
6.3.1.2 Bank Service Checksum Status Aggregate <BankSvcChkSumStatus>

The Bank Service Checksum Status <BankSvcChkSumStatus> is returned in responses to Add or Modify BankSvcChkSum.
Tag
<BankSvcChkSumStatusCode>
Type
Open Enum
Usage
Required
Description
Bank Service Checksum Status Code. This identifies the Bank Service Checksum status. Defined values: Pending, Posted, Refused, Rejected, Returned, DelPend, Deleted
Optional Required Optional
Status Description. Explanatory text associated with this status. Effective Date. The date associated with the change to the current status. Status Modified By. If present, indicates who modified the Bank Service Checksum Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<Memo>
C-255
Optional
Memo. Intended to be optionally used by a BPP to store any necessary text associated with the Bank Service Checksum Control status.
6.3.2Credit Record Aggregate <CreditRec>

The <CreditRec> aggregate contains the credit record.
Tag
<CreditId> <CreditInfo>
Type
Identifier Aggregate see section 6.3.29 Aggregate see section 6.3.3
Usage
Required Required
Description
Credit Identifier. Assigned by the server at the time the Credit is first added. Cannot be changed by the client. Credit Information aggregate.
<CreditStatus>
Required
Credit Status aggregate.
Version 1.7
April 2005
15
6.3.3Credit Status Aggregate <CreditStatus>

The <CreditStatus> aggregate contains details of the status of a credit object.
Tag
<CreditStatusCode>
Type
Open Enum
Usage
Required
Description
The current status of the credit object. Defined Values: Authorized, Rejected, Posted, Held
DateTime Open Enum
Required Optional
Credit Status Date. The date associated with the state change to the current state. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<CreditHeldAmtExpDt>
DateTime
Optional
but see Description
Credit/Deposit Hold Expiry Date. The date that the current deposit held amount of this transaction would expire. The current held amount of this deposit transaction would become available on this date. NOTE: This date applies only to the portion of the deposit, which is held (and the credit status is Authorized), and it does not apply to the entire deposit (when the credit status is Held). If this element is present then one of the <CompositeCurAmtType> entries must be CreditHeld.
<Status>
Optional
Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the CreditStatusCode is Rejected or Held.
6.3.4Credit Media Item Aggregate <CreditMediaItem>

The <CreditMediaItem> aggregate contains details of the media item (e.g. check, cash) being deposited.
Tag
<CreditMediaItemId>
Type
Identifier
Usage
Optional but see Description Required XOR Required XOR
Description
Credit Media Item Identifier. If more than one <CreditMediaItem> aggregate is exists then the <CreditMediaItemId> is required. Credit Media Cash Information aggregate. This aggregate contains details about cash being deposited. Credit Media Check Information aggregate. This aggregate contains details about the check being deposited.
<CreditMediaCashInfo>
<CreditMediaChkInfo>
6.3.5Credit Media Cash Information Aggregate <CreditMediaCashInfo>

The <CreditMediaCashInfo> aggregate contains details about a cash media item being deposited.
Tag
<CashAmt>
Type
Currency Amount
Usage
Required
Description
Cash Amount. The cash denomination being deposited.
16
April 2005
Version 1.7
Tag
<CashValidity>
Type
Open Enum
Usage
Optional
Description
Cash Validity. The validity of the cash being deposited. Defined Values: Genuine, Counterfeit, Suspect
<CashQuality>
Open Enum
Optional
Cash Quality. The quality of the cash being deposited. Defined Values: Fit, Unfit
6.3.6Credit Media Check Information Aggregate <CreditMediaChkInfo>

The <CreditMediaChkInfo> aggregate contains details about a check media item being deposited cashed or used for payment.
Tag
<ChkEnteredAmt> <ChkCourtesyAmt> <MicrReadIntegrity>
Type
Currency Amount Currency Amount Open Enum
Usage
Description
Check Entered Amount. The amount the customer entered as the check amount being deposited or cashed. Check Courtesy Amount. The amount read from the courtesy amount of the check being deposited or cashed. MICR Read Integrity. The integrity of the MICR data read from the check being deposited or cashed. Defined Values: Good, Partial, Bad
<MicrUnformatted> <ChkImg>
C-64 Aggregate see section 6.3.36 Aggregate see section 6.3.37 Aggregate see section 3.2.4.1 Identifier
Optional Optional
MICR Unformatted. The unformatted MICR data read from the check being deposited or cashed. Check Images
<ChkDetail>
Optional
Check Detail
<PersonInfo>
Optional
Drawee information such as driver license number and birth date used by some network authorizers.
<ChkAcceptId>
Optional
Check Accept Identifier. The identifier from the Check Accept add request message that can be used to find the original Check Accept info.
6.3.7Deposit Account Record Aggregate <DepAcctRec>

Tag
<StopCount> <HoldCount> <LastDepDt> <LastDepCurAmt> <DepMatureDt>
Type
Long Long Date Currency Amount Date
Usage
Optional Optional Optional Optional Optional
Description
Number of Stopped Payments. Number of Holds outstanding. Last Deposit Date. Last Deposit Amount. Deposit Maturity Date.
Version 1.7
April 2005
17
6.3.8Credit Card Account Record Aggregate <CCAcctRec>

Tag
<DueDt> <ExpDt>
Type
Date DateTime
Usage
Optional Optional
Description
Payment Due Date. Expiration date for card. If the card has only month and year expiration, the last day of the month must be specified here. Last Payment Date. Last Payment Amount.
<LastPmtDt> <LastPmtCurAmt>
Date Currency Amount
Optional Optional
6.3.9Common Loan and LOC Account Aggregate <LoanInfoCommon>

This aggregate contains information that is common to both the <LoanInfo> and <LocInfo> aggregates.
Tag
<OrigDt> <Freq> <RemainingPmtCount> <PurposeDesc> <CollateralDesc> <CompletedPmtCount> <RegPmtCurAmt> <DueDt> <NextPmtCurAmt>
Type
Date Open Enum Long C-80 C-80 Long Currency Amount Date Currency Amount
Usage
Optional Optional Optional Optional Optional Optional Optional Optional Optional
Description
Original Date. Frequency. Repayment Frequency. Number of Payments Remaining. Purpose DescriptionPurpose for Loan or LOC Collateral Description. Number of Payments Completed. Regular Payment Amount Date Next Payment Due. Next Payment Amount, including any past due amounts that are now due. A first or last payment may also differ from the regular payment amount, even if there is no past due amount. Last Payment Date. Last Payment Amount. Number of Past Due Payments. Prepay Penalty. Amount charged for paying off a loan prior to the specified term.
<LastPmtDt> <LastPmtCurAmt> <PastDuePmtCount> <PrepayPenalty>
Date Currency Amount Long Currency Amount
6.3.10
Tag
<Term>
Loan Account Record Aggregate <LoanAcctRec>

Type
Aggregate see section 3.2.9.1 Date Aggregate see section 6.3.9
Usage
Optional
Description
Term Aggregate.
<MatDt> <LoanInfoCommon>
Optional Optional
Loan Maturity Date. Loan and LOC common information aggregate
18
April 2005
Version 1.7
6.3.11
Tag
Line of Credit Account Record Aggregate <LOCAcctRec>

Type
Currency Amount Currency Amount DateTime Aggregate see section 6.3.9
Usage
Description
LOC LimitThe maximum authorized amount for the line of credit. Minimum Payment Amount. Expiration Date. If omitted, the LOC is open ended. Loan and LOC common information aggregate
<LOCLimit> <MinPmtCurAmt> <ExpDt> <LoanInfoCommon>
6.3.12
Tag
<OrigDt>
Mortgage Account Record Aggregate <MortAcctRec>

Type
Date Aggregate see section 6.3.9 Date Date Currency Amount Date Currency Amount Date Currency Amount Date Currency Amount
Usage
Optional Optional
Description
Origination Date. Loan Information.
<LoanInfoCommon>
<LastPmtDt> <TaxPaidDt> <TaxPaidCurAmt> <LastYrTaxPaidDt> <LastYrTaxPaidCurAmt> <InsPaidDt> <InsPaidCurAmt> <LastYrInsPaidDt> <LastYrInsPaidCurAmt>
Optional Optional Optional Optional Optional Optional Optional Optional Optional
Last Payment Date. Tax Paid Date. Tax Paid Amount. Last Year Tax Paid Date. Last Year Tax Paid Amount. Mortgage Insurance Paid Date. Mortgage Insurance Paid Amount. Mortgage Last Year Insurance Paid Date. Mortgage Last Year Insurance Paid Amount.
6.3.13
Bank Account Transaction Record Aggregate <BankAcctTrnRec>
The <BankAcctTrnRec> aggregate describes the data common to all banking account transaction types.
Version 1.7
April 2005
19
Tag
<TrnType>
Type
Open Enum
Usage
Optional
Description
Transaction Type. Defined values: Debit, Credit, Withdrawal, Check, Deposit, Transfer, Payment, Interest, Dividend, DirectDeposit, DirectDebit, RepeatPayment, Fee, ServiceCharge, Adjustment, BAI:xxx or TMA:xxx (Reference BAI Code List at http://www.bai.org/operations/bai_codes.html, or TMA Code List at http://www.AFPonline.org/Information_Center/Publications/ Bookstore/afpbooks/afpbooks.html as maintained by Association of Financial Professionals (AFP)) Example: BAI:010 (Beginning Ledger Balance), BAI:140 (ACH Credits), etc.
<TrnSrc>
Open Enum
Optional
Transaction Source. See Data Dictionary for details. Defined values: ATM, Teller, POS, ARU, HomeBank, ACH.
<PostedDt>
Date
Required
Posted Date. For banking, the date on which the transaction was recorded against the account. For transfers, the date on which the entries were made on the books of the receiving Financial Institution. Origination Date. The date on which the customer originated the transaction. Effective Date. Bank offset date for a correcting transaction; date of previous transaction Currency Amount. Always in the currency of the account. Original Currency Amount. Indicates the transaction was initiated in a currency other than the default for the account (funding account in the case of transfers or payments). The currency rate, if provided, must be included here. Composite Currency Amount Aggregate. Bank charges on transaction. Standard Industrial ID Aggregate. For categorization purposes. Memo. Additional information about the transaction. Name of payee or merchant. Counterparty Information Aggregate
<OrigDt> <EffDt> <CurAmt> <OrigCurAmt>
Date DateTime Currency Amount Currency Amount
Optional Optional Required Optional
<CompositeCurAmt>
Aggregate see section 3.2.16.1 Aggregate see section 3.2.13 C-255 C-40 Aggregate see section 7.3.9.1 Aggregate see section 3.2.17 NC-80
Optional
<IndustId>
Optional
<Memo> <Name> <CounterpartyInfo>
<RefInfo>
Optional Repeating
Reference Information Aggregate. Identification information, typically supplied by the customer, used to correlate the bank account transaction to an associated <XferInfo> or <RemitInfo> sent by the client. Biller Reference Information. Biller-defined text from <BillRec>, for the billers Accounts Receivable reconciliation. Depending on the Payment Provider and the payment network and message used to make the payment, <BillRefInfo> may be truncated to 22 characters.
<BillRefInfo>
Optional
<RemitAdviceRefId>
Identifier
Optional
Remittance Advice Reference Identification. Remit advice identification for reconciliation process to link payments and remittance advice. This is also used to reconcile two information streams when remittance and payment travel separately.
20
April 2005
Version 1.7
Tag
<CustPayeeInfo>
Type
Aggregate see section 7.3.2.1 Aggregate see section 7.3.7 Identifier Identifier Aggregate see section 6.3.13.1
Usage
Optional
Description
Customer Payee Information Aggregate.
<InvoiceInfo>
Optional
Invoice Information Aggregate. Structured advice information on the transaction CSP Reference Identifier. Service Provider Reference Identifier. SP Reference Identifier Correction. Either replaces or deletes a previous transaction depending on the value of <CorrectAction>.
<CSPRefId> <SPRefId> <SPRefIdCorrect>
6.3.13.1 SP Reference Identifier Correction <SPRefIdCorrect>

The <BankAcctTrnRec> aggregate describes the data common to all banking account transaction types.
Tag
<SPRefId> <CorrectAction>
Type
Identifier Closed Enum
Usage
Required Required
Description
Old Message Identifier. This is the <SPRefId> of the transaction that is being replaced or deleted. Correction Action.
6.3.14
Deposit Account Transaction Record Aggregate <DepAcctTrnRec>
The <DepAcctTrnRec> aggregate describes a single transaction posted against a Deposit Account. It is used in messages that provide transaction detail. The sign convention for the statement message aggregate is as follows: a positive <CurAmt> is added to the account balance and a negative <CurAmt> is subtracted from the account balance
Sign of <CurAmt> Positive Negative Meaning Increase customer asset. Decrease customer asset.
Tag
<BankAcctTrnRec>
Type
Aggregate see section 6.3.13 Currency Amount Date Aggregate see section 3.2.16.1 NC-12
Usage
Required
Description
Banking Transaction Record.
<StmtRunningBal>
Optional
Statement Running Balance. Indicates the running total/balance, to be displayed on statements, as a result of this transaction. Available Date. The date on which funds are available. Composite Currency Amount Aggregate. This aggregate is generally used here to contain float amounts. Check Number.
<AvailDt> <CompositeCurAmt>
<ChkNum>
Version 1.7
April 2005
21
Tag
<XferId>
Type
Identifier
Usage
Optional
Description
Funds Transfer Identifier. Assigned by the server at the time the Funds Transfer is first added. Cannot be changed by the client. Payment Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client. Deposit Account Detail. Used for transfer messages. Card Account Detail. Used for transfer messages. Loan Account Detail. Used for transfer messages. Network Transaction Information Aggregate. Contains information regarding the network that processed the transaction. This aggregate replaces <ATMTrnInfo> and <USA.ACHTrnInfo>, both of which will be deprecated in IFX 2.0.
<PmtId> <DepAcctIdTo> <CardAcctIdTo> <LoanAcctIdTo> <NetworkTrnInfo>
Identifier Aggregate Aggregate Aggregate Aggregate see section 3.2.18
Optional Optional XOR Optional XOR Optional XOR Optional XOR 1.1+
<ATMTrnInfo>
Optional XOR
ATM (Automated Teller Machine) Message Information. This aggregate will be deprecated in IFX 2.0, being replaced by <NetworkTrnInfo> ACH Message Information Aggregate. This aggregate will be deprecated in IFX 2.0, being replaced by <NetworkTrnInfo>
<USA.ACHTrnInfo>
Optional
6.3.14.1 ATM Message Information <ATMTrnInfo>

Tag
<ATMOwner> <ATMLocation> <ATMCityState>
Type
C-14 C-18 C-15
Usage
Description
The name of the individual or organization which owns the ATM. Alphanumeric string assigned by the ATM owner that specifies the ATM location. Alphanumeric string assigned by the ATM owner that specifies the ATM city and state or province.
6.3.14.2 ACH Message Information Aggregate <USA.ACHTrnInfo>

Tag
<OriginatorName> <USA.RTN>
Type
C-40 NC-9
Usage
Required Optional
Description
Name of originator of the ACH Message. Transit Routing Number. A number uniquely identifying an organization providing products and services of a monetary or financial nature within the United States.
22
April 2005
Version 1.7
6.3.15
Credit Card Account Transaction Record Aggregate <CCAcctTrnRec>
The sign convention for the statement transaction aggregate is as follows: a positive <CurAmt> is added to the account balance and a negative <CurAmt> is subtracted from the account balance.
Sign of <CurAmt>
Positive Negative
Meaning
Increase customer liability. Decrease customer liability.
Tag
<BankAcctTrnRec>
Type
Aggregate see section 6.3.13 NC-23 C-255
Usage
Required
Description
Banking Transaction Record.
<SalesSlipRefNum> <Memo>
Required Optional
Sales Slip Reference Number. Memo. Additional information about the message.
6.3.16
Tag
Selection Range Check Number Aggregate <ChkRange>

Type
NC-12 NC-12
Usage
Description
Selection Low Check Number. Selection High Check Number.
<ChkNumStart> <ChkNumEnd>
6.3.17
Tag
Stop Check Record Aggregate <StopChkRec>

Type
Aggregate see section 6.3.17.1 Date Closed Enum
The <StopChkRec> aggregate is generally used in response messages related to Stopped Checks.
Usage
Required
Description
Stop Check Information.
<StopChkInfo>
<PostedDt> <StopChkStatusCode>
Optional Required
Check Posting Date. The date on which the check is posted against the customers account. Stop Check Status Code. The status of a Stop Check request that is returned as part of a Stop Check inquiry. Valid values: Pending, Stopped, Returned, Cleared, Rejected, Cancelled, Held
<StatusDesc> <Status>
C-255 Aggregate see section 3.2.12.1 Identifier
Optional Optional
Check Error Description. Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the ChkOrdEnclStatusCode is Rejected or Held. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server.
<ApprovalId>
Optional
Version 1.7
April 2005
23
6.3.17.1 Stop Check Information Aggregate <StopChkInfo>

The <StopChkInfo> aggregate is used in messages related to Stop Checks. It is generally used in the request messages.
Tag
<ChkNum> <Name> <CurAmt> <OrigDt> <Desc> <BaseEnvr>
Type
NC-12 C-40 Currency Amount Date C-80 Aggregate see section 6.3.39
Usage
Required Optional Optional Optional Optional Optional
Description
Check Number. Check Pay-To Name. Check Currency Amount. Check Origination Date. The date on which the customer originates the check. Description. Additional information, such as why the check is being stopped. Base Environment aggregate
6.3.18
Foreign Exchange Rate Information Aggregate <ForExRateInfo>
A customer may request a foreign exchange rate commitment from a Financial Institution using the Foreign Exchange Rate Message. This commitment may be stored by the client and may be referenced by an Intra- or Interbank transfer until the expiration date/time.
Tag
<CurAmt>
Type
Currency Amount
Usage
Description
Message Amount. This is the amount in the TO currency at the quoted exchange rate. Must be included when the Financial Institution quotes the commitment in the Foreign Exchange Response Message. Included by the client in a subsequent transfer request only if the transfer amount = the commitment amount. Exchange Rate. Currency Conversion Indicator. Valid values: Direct, Indirect. See Section 2.3.8 for more information.
<CurRate> <CurConvertRule>
Decimal Closed Enum
Required Required
<Fee>
Aggregate see section 3.2.16.2 DateTime
Optional Repeating Optional but see Description
Fee. The fee(s) required to execute the exchange may be provided to the customer for informational purposes. Expiration Date/Time. Required if it is a committed rate. Explicit commitment expiration date and time. After the date/time specified in this field, the Financial Institution is under no obligation to honor the rate returned.
<ExpDt>
Optional Optional
24
April 2005
Version 1.7
6.3.19
Tag
<XferId>
Transfer Record Aggregate <XferRec>

Type
Usage
Required Optional
Description
Transfer Identifier. Assigned by the server at the time the Transfer is first added. Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client. Included only if the Banking provider generated the transfer instance from a recurring model.
<RecXferId>
<RecXferMod>
Boolean
Recurring Transfer Modified Indicator. Required if <XferModRq> has subsequently modified a transfer generated from a Recurring Transfer Model so it no longer matches the Recurring Transfer Model. This may be supplied only for recurring transfer instances. Transfer Information Aggregate.
<XferInfo>
Required
<XferStatus>
Required
Transfer Status.
6.3.19.1 Recurring Transfer Record Aggregate <RecXferRec>

Tag
<RecXferId>
Type
Identifier
Usage
Required
Description
Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client. Transfer Information Aggregate.
<XferInfo>
Aggregate see section 6.3.19.2 Aggregate see section 3.2.11.1 Long
Required
<RecModelInfo>
Required
Recurring Model Information Aggregate.
<RemainingInsts>
Required
Remaining Instance Count. The server must calculate this number as the number of actual payments to be made plus the number of instances to skip. Server must calculate on <RecXferAddRq> and return in response. Server must recalculate in case of an <RecXferModRq> that changes <RecSeriesEnd> or when a payment is spawned.
6.3.19.2 Transfer Information Aggregate <XferInfo>

The <XferInfo> aggregate is used in messages related to Transfers, Interbank Transfers, and Recurring Transfer Models for Funds Transfers. Transfers may be single currency transfers, (i.e. the source and target amount is the same) or may be foreign exchange transfer (i.e. source and target amounts have different ISO currency code). The Financial Institution indicates support of foreign exchange transfers by specifying ForEx within <OptSupt> within <XferProf> in the Banking Profile In some cases, a customer may not be able to specify the exchange rate for a foreign exchange transfer Typically, the Financial Institution makes the transfer at the prevailing exchange rate at the time of the transfer, often considering such factors as the amount of transfer and the customer relationship with the Financial
Version 1.7
April 2005
25
Interactive Financial Exchange Business Message Specification Institution, in addition to the interbank exchange rate. Some Financial Institutions make exchange rate commitments (see Exchange Rate message). Usually, these commitments expire after a short period of time. In this case, the customer may specify the exchange rate and reference the <CSPRefId> returned within the Exchange Rate Rs. Where a specific foreign exchange contract is referred to, the <ForExDealId> is used instead of the <ForExInfo> aggregate.
Tag
<DepAcctIdFrom>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate
Usage
Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR Required Optional Optional Optional Profiled support Optional XOR Optional XOR
Description
Deposit Account Identification Aggregate. Usage is transfer source account. Card Account Identification Aggregate. Usage is transfer source account. Loan Account Identification Aggregate. Usage is transfer source account. Deposit Account Identification Aggregate. Usage is transfer destination account. Card Account Identification Aggregate. Usage is transfer destination account. Loan Account Identification Aggregate. Usage is transfer destination account. Currency Amount. Due Date. If not specified, the transfer is to be scheduled as soon as possible. Category for this message, modified by the client. Immediate Transfer Indicator. If set to True, the transfer should be executed immediately, and not at end of day. Subject to support in Service Profile. Foreign Exchange Rate Information Aggregate.
<CardAcctIdFrom>
<LoanAcctIdFrom>
<DepAcctIdTo>
<CardAcctIdTo>
Aggregate
<LoanAcctIdTo>
Aggregate
<CurAmt> <DueDt> <Category> <ImmediateXfer>
Currency Amount Date C-40 Boolean
<ForExRateInfo>
Aggregate see section 6.3.18 Identifier
<ForExDealId>
Foreign Exchange Deal Identifier (Committed deals). Where a specific foreign exchange contract is referred to, the <ForExDealId> is used instead of the <ForExInfo> aggregate Reference Information Aggregate. Identification information, used to correlate to transactions provided in bank statements. Base Environment aggregate
<RefInfo>
<BaseEnvr>
6.3.19.3 Transfer Status Aggregate <XferStatus>

The <XferStatus> is returned in responses to Add or Modify Transfer and Add or Modify Recurring Transfer Model. Note that all elements within this aggregate are assigned by the server and cannot be assigned or modified by the client.
26
April 2005
Version 1.7
Tag
<XferStatusCode>
Type
Closed Enum
Usage
Required
Description
Transfer Status Code. This identifies the payment processing status. Valid values: Scheduled, Cancelled, FIHeld, RejNoFund, RejInactive, RejClosed, Returned, Failed, Processed, Posted, Cleared, Skipped, Rejected, Held
Status Description. Explanatory text associated with this status. Transfer Status Date. The date associated with the state change to the current state. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<Status>
Optional
Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code.
6.3.20
Tag
Check Order Record Aggregate <ChkOrdRec>

Type
Usage
Required Required
Description
Check Order Identifier. Assigned by the server at the time the Check Order is first added. Check Order Information Aggregate.
<ChkOrdId> <ChkOrdInfo>
<ChkOrdStatus>
Required
Check Order Status.
6.3.20.1 Check Order Information Aggregate <ChkOrdInfo>

Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.20.1.1 C-80
Usage
Required XOR Required XOR Required XOR Optional XOR Optional XOR Repeating Optional Repeating XOR
Description
<CardAcctId>
<LoanAcctId>
<ChkPrint>
Check Print Aggregate.
<ChkText>
Freeform Check Text.
<CustNameAddr>
Customer Name/Address Aggregate. Within this aggregate, <NameAddrType> is most likely set to Delivery.
Version 1.7
April 2005
27
Tag
<PersonInfo>
Type
Usage
Optional Repeating XOR Optional
Description
Person Information Aggregate.
<DeliveryDestination>
Delivery destination. Specifies where to deliver the checks, such as Branch, Consumer, Alternate Address Default value: Consumer
<Count> <ChkNumPrefix> <ChkNumStart> <ChkNumSuffix> <ChkBkStyleId> <DeliveryMethod>
Long C-2 NC-12 C-2 Identifier Open Enum
Optional Optional Optional Optional Optional Optional Profiled values Optional
Number of Checks. If this is missing, the number used for the previous order must be used. Check Number Prefix. Two characters printed immediately before the check number. Starting Check Number of the Order. Check Number Suffix. Two characters printed immediately after the check number. Checkbook Style Identifier. Service Provider assigns defined values. This field indicates customers choice. Delivery Method. Default is Post. Value must be supported in Service Profile. Standard and Non-Standard billing methods for product(s) ordered. Valid Values: Customer, Institution, CheckPrinter
<BillingMethod>
Closed Enum
<CoverMngrm> <CoverStyleId> <ArtWorkId> <IncEndrsmntStmp>
C-3 Identifier Identifier Boolean
Cover Monogram. Up to 3 characters affixed to the covers ordered. Cover Style. Checkbook cover style. For valid cuts and pridemarks. This is dependent on <ChkBkStyleId>. Endorsement Stamp. If True an endorsement stamp is included with the check order. If False, no endorsement stamp is included with the product. Font Type. The type of font used for the check personalization. Over Signature Text. Printed information residing above the signature line. Secondary Signature Line. If True, a second signature line is printed below the first. If False, no secondary signature line is added. Identifier for bank club program discounts or special promotioins. Voucher Code. Indicates the voucher apron type included with the order. Base Environment aggregate
<FontId> <OvrSigText> <IncSecSigLine>
Identifier C-40 Boolean
<ClubAcctId> <VoucherTypeId> <BaseEnvr>
Identifier Identifier Aggregate see section 6.3.39
6.3.20.1.1 Check Print Aggregate <ChkPrint>
28
April 2005
Version 1.7
Tag
<CustName>
Type
Aggregate see section 3.2.3.2 Aggregate see section 3.2.4.1.1 Aggregate see section 3.2.3.10.1 Phone Number C-80
Usage
Required XOR Repeating Required XOR Repeating Required
Description
Customer Name Aggregate.
<PersonName>
Person Name Aggregate.
<PostAddr>
Customer Address Aggregate.
<Phone> <Desc>
Optional Optional
Telephone Number. Provided if it is to be printed on checks. Additional Information to be printed on checks.
6.3.20.2 Check Order Status Aggregate <ChkOrdStatus>

Tag
<ChkOrdStatusCode>
Type
Open Enum
Usage
Required
Description
Check Order Status Code. Defined values: Accepted, Processed, Sent, Pending, Rejected, Cancelled, Held
Optional Required Optional Optional
Status Description. Explanatory text associated with this status. Check Order Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<ResolvePendingDt>
Date
Optional
Resolve Pending Date. The date that the Pending status in <ChkOrdStatusCode> is expected to change to a final status; e.g., Sent or Cancelled. This date should be returned when the <ChkOrdStatusCode> is set to Pending. Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the ChkOrdEnclStatusCode is Rejected or Held.
<Status>
Optional
6.3.21
Tag
Recurring Check Order Record Aggregate <RecChkOrdRec>

Type
Usage
Required Required
Description
Recurring Check Order Identifier. Assigned by the server at the time the Recurring Check Order is first added. Check Order Information Aggregate.
<RecChkOrdId> <ChkOrdInfo>
<RecModelInfo>
Required
Version 1.7
April 2005
29
Tag
<RemainingInsts>
Type
Long
Usage
Optional
Description
Remaining Instance Count. The server must calculate this number as the number of actual check orders to be made plus the number of instances to skip based on the customerentered <RecSeriesEnd>. Server must calculate on <RecChkOrdAddRq> and return in response. Server must recalculate in case of an <RecChkOrdModRq> that changes <RecSeriesEnd> or when a payment is spawned.
6.3.22
Tag
Check Order Detail Aggregate <ChkOrdDetail>

Type
Identifier Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.20.1.1 C-80
Usage
Optional XOR Optional XOR Optional XOR Optional XOR Optional XOR Repeating Optional XOR Repeating Optional Repeating XOR Optional
Description
Deposit Account Identification Aggregate Credit Account Identification Aggregate.
<DepAcctId> <CardAcctId>
<LoanAcctId>
<ChkPrint>
Check Print Aggregate
<ChkText>
Freeform Check Text.
<CustNameAddr>
Aggregate see section 3.2.3.4 Aggregate see section 3.2.4.1 Open Enum
Customer Name/Address Aggregate. Within this aggregate, <NameAddrType> is most likely set to Delivery. Contains the address for check order delivery. Person Information Aggregate.
<PersonInfo>
<DeliveryDestination>
Delivery destination. Specifies where to deliver the checks, such as Branch, Consumer, Alternate Address, etc. Defined values: Branch, Consumer, Alternate Address Default value: Consumer
<Count> <ChkNumPrefix> <ChkNumStart> <ChkNumSuffix> <ChkBkStyleId> <DeliveryMethod>
Long C-2 NC-12 C-2 Identifier Open Enum
Optional Optional Optional Optional Optional Optional Profiled values
Number of checks. If omitted, the number from the previous order is used. Check Number Prefix. Two characters printed immediately before the check number. Starting Check Number of the Order. Check Number Suffix. Two characters printed immediately after the check number. Checkbook Style Identifier. Service Provider assigns defined values. This field indicates customers choice. Delivery Method. Default is Post. Value must be supported in Service Profile.
30
April 2005
Version 1.7
Tag
<BillingMethod>
Type
Closed Enum
Usage
Optional
Description
Standard and Non-Standard billing methods for product(s) ordered. Valid Values: Customer, Institution, CheckPrinter
<CoverMngrm> <CoverStyleId> <ArtWorkId> <IncEndrsmntStmp>
C-3 Identifier Identifier Boolean
Cover Monogram. Up to 3 characters affixed to the covers ordered. Cover Style. Checkbook cover style. For valid cuts and pridemarks. This is dependent on <ChkBkStyleId>. Endorsement Stamp. If True an endorsement stamp is included with the check order. If False, no endorsement stamp is included with the product. Font Type. The type of font used for the check personalization. Over Signature Text. Printed information residing above the signature line. Secondary Signature Line. If True, a second signature line is printed below the first. If False, no secondary signature line is added. Identifier for bank club program discounts or special promotioins. Voucher Code. Indicates the voucher apron type included with the order.
<FontId> <OvrSigText> <IncSecSigLine>
Identifier C-40 Boolean
<ClubAcctId> <VoucherTypeId>
Optional Optional
6.3.23
Tag
Deposit Book Order Record Aggregate <DepBkOrdRec>

Type
Usage
Required Required
Description
Deposit Book Order Identifier. Assigned by the server at the time the Deposit Book Order is first added. Deposit Book Order Information Aggregate.
<DepBkOrdId> <DepBkOrdInfo>
<DepBkOrdStatus>
Required
Deposit Book Order Status.
6.3.23.1 Deposit Book Order Information Aggregate <DepBkOrdInfo>

Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Long Identifier
Usage
Required
Description
<Count> <DepBkStyleId>
Optional Optional
Number of Deposit Slips. If omitted, the number used for the previous order must be used. Style of Deposit Book.
Version 1.7
April 2005
31
Tag
<DeliveryMethod>
Type
Open Enum
Usage
Description
Delivery Method. Used to request the delivery channel for requested information. See Data Dictionary for details. Default is Post. Value selected must be supported in Service profile.
<BaseEnvr>
Optional
Base Environment aggregate
6.3.23.2 Deposit Book Order Status Aggregate <DepBkOrdStatus>

Tag
<DepBkOrdStatusCode>
Type
Open Enum
Usage
Required
Description
Deposit Book Order Status Code. Defined values: Accepted, Processed, Sent, Pending, Rejected, Cancelled, Held
Optional Required Optional Optional
Status Description. Explanatory text associated with this status. Deposit Book Order Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<Status>
Optional
Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the DepBkOrdEnclStatusCode is Rejected or Held.
6.3.24
Tag
<OptSupt>
Transfer Profile Aggregate <XferProf>

Type
Open Enum
The Transfer Profile Aggregate is used to convey information on the transfer.

Usage
Optional Repeating
Description
Options Supported. Defined values: ForEx, ImmediateXfer, RecCtrl, RecFinalAmt, RecInitialAmt, RecModelNickname, Skip, SchedXfer. Processing Schedule Aggregate. If omitted, the default processing schedule is assumed. Recurring Transfer Profile Aggregate.
<PrcSched>
Optional
<RecXferProf>
Optional
32
April 2005
Version 1.7
6.3.24.1 Recurring Transfer Profile Aggregate <RecXferProf>

Tag
<Freq>
Type
Open Enum
Usage
Required Repeating
Description
Recurring Model Frequency. Usage is a list of supported frequencies. Defined values: Daily, Weekly, Biweekly, TwiceMonthly, Monthly, EndOfMonth, FourWeeks, BiMonthly, Quarterly, SemiAnnually, Annually
<ModPendingType>
Closed Enum
Required
Client Modify Pending Type. Valid values: Always, Never, IfRequested
6.3.25
Tag
<DebitId>
Debit Record Aggregate <DebitRec>

Type
Identifier Aggregate see section 6.3.27 Aggregate see section 6.3.25.1
The <DebitRec> aggregate contains the debit record.

Usage
Required Required
Description
Debit Identifier. Assigned by the server at the time the Debit is first added. Cannot be changed by the client. Debit Information aggregate.
<DebitInfo>
<DebitStatus>
Required
Debit Status aggregate.
6.3.25.1 Debit Status Aggregate <DebitStatus>

The <DebitStatus> aggregate contains details of the status of a debit object.
Tag
<DebitStatusCode>
Type
Open Enum
Usage
Required
Description
The current status of the debit object. Defined Values: Authorized, Rejected, Posted, Held
DateTime Open Enum
Required Optional
Debit Status Date. The date associated with the state change to the current state. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<ApprovalId> <Status>
Optional Optional
Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the DebitStatusCode is Rejected or Held.
6.3.26
Debit Authorization Record Aggregate <DebitAuthRec>
The <DebitAuthRec> aggregate contains the debit authorization record.
Version 1.7
April 2005
33
Tag
<DebitAuthId>
Type
Identifier
Usage
Required
Description
Debit Authorization Identifier. Assigned by the server at the time the Debit Authorization is first added. Cannot be changed by the client. Debit Authorization Information aggregate.
<DebitAuthInfo>
Required
<DebitAuthStatus>
Required
Debit Authorization Status aggregate.
6.3.26.1 Debit Authorization Information Aggregate <DebitAuthInfo>

The <DebitAuthInfo> aggregate is used in messages related to debit authorizations. It is generally used in the request messages.
Tag
<DebitAuthType>
Type
Open Enum
Usage
Required
Description
The type of the debit authorization. Defined Values: CashWithdrawal, StampDispense, TicketDispense, ValueCouponDispense, CreditCardAdvance, MerchandisePurchase.
<CompositeCurAmt>
Aggregate see section 3.2.16.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 6.3.39
Required Repeating Required XOR Required XOR Optional
The amounts of the debit transaction and appropriate fees.
<DepAcctId>
<CardAcctId>
<BaseEnvr>
6.3.26.2 Debit Authorization Status Aggregate <DebitAuthStatus>

The <DebitStatus> aggregate contains details of the status of a debit authorization object.
Tag
<DebitStatusCode>
Type
Open Enum
Usage
Required
Description
The current status of the debit authorization object. Defined Values: Authorized, Rejected, Posted, Held
<EffDt> <ApprovalId> <StatusModBy>
DateTime Identifier Open Enum
Debit Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
34
April 2005
Version 1.7
Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the DebitStatusCode is Rejected or Held.
6.3.27
Tag
Debit Information Aggregate <DebitInfo>

Type
Open Enum
The <DebitInfo> aggregate is used in messages related to debits. It is generally used in the request messages.
Usage
Required
Description
The type of the debit authorization transaction. Defined Values: CashWithdrawal, StampDispense, TicketDispense, ValueCouponDispense, CreditCardAdvance, MerchandisePurchase, , MerchandisePurchaseCashBack TransactionFee, CardVerification. This element will be deprecated from the DebitInfo aggregate in IFX 2.0. The replacement is to use the DebitType element.
<DebitAuthType>
<DebitType>
Open Enum
The type of the debit transaction. Defined Values: CashWithdrawal, StampDispense, TicketDispense, ValueCouponDispense, CreditCardAdvance, CardVerification, TransactionFee, MerchandisePurchase, MerchandisePurchaseCashBack. Since this element will be replacing DebitAuthType in the DebitInfo aggregate, this element will be required in IFX 2.0.
<CompositeCurAmt>
Aggregate see section 3.2.16.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Identifier
Required Repeating Required XOR Required XOR Optional
The amounts of the debit transaction and appropriate fees.
<DepAcctId>
<CardAcctId>
<DebitAuthId>
Debit Authorization Identifier. Assigned by the server at the time the Debit Authorization is first added. This is used to relate a debit to a previously authorized debit authorization object Transaction RqUID. If this debit is used as a fee for a transaction (e.g. fee for a balance inquiry) then this element will contain the RqUID of the transaction (e.g. the balance inquiry). If this debit is used as a cash withdrawal for a deposit transaction such as deposit with cash back then this element will contain the RqUID of credit message/deposit transaction.
<TrnRqUID>
UUID
Optional
Version 1.7
April 2005
35
Tag
<ClientChgCode>
Type
Open Enum
Usage
Optional
Description
Client Change Code. This indicates the reason why a Debit was for a different amount from the original authorization for the debit. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, PurchaseAdjustment, ConsumerDeclined, ConsumerTimeout
<NetworkTrnInfo>
Optional
Network Transaction Information. Identification and location of the terminal from which the message originates. This aggregate will be removed from the DebitInfo aggregate in IFX 2.0. With IFX 1.4+, the <NetworkTrnInfo> aggregate is available in the <MsgRqHdr> aggregate.
<BaseEnvr>
Optional
6.3.28
Credit Authorization Record Aggregate <CreditAuthRec>

Type
Identifier
The <CreditAuthRec> aggregate contains the credit authorization record.

Tag
<CreditAuthId>
Usage
Required
Description
Credit Authorization Identifier. Assigned by the server at the time the Credit Authorization is first added. Cannot be changed by the client. Credit Authorization Information aggregate.
<CreditAuthInfo>
Required
<CreditAuthStatus>
Required
Credit Authorization Status aggregate.
6.3.28.1 Credit Authorization Information Aggregate <CreditAuthInfo>

The <CreditAuthInfo> aggregate is used in messages related to credit authorizations. It is generally used in the request messages.
Tag
<CreditAuthType>
Type
Open Enum
Usage
Required
Description
The type of the credit authorization. Defined Values: UnverifiedCashDeposit, VerifiedCashDeposit, UnverifiedCheckDeposit, VerifiedCheckDeposit, EnvelopeDeposit, MultiDeposit, MerchandiseReturn.
<CompositeCurAmt>
Required Repeating Required XOR
The amounts of the credit transaction and appropriate fees.
<DepAcctId>
36
April 2005
Version 1.7
Tag
<CardAcctId>
Type
Aggregate see section 3.2.7.2.3 Aggregate see section 6.3.39
Usage
Required XOR Optional
Description
<BaseEnvr>
6.3.28.2 Credit Authorization Status Aggregate <CreditAuthStatus>

The <CreditAuthStatus> aggregate contains details of the status of a credit authorization object.
Tag
<CreditStatusCode>
Type
Open Enum
Usage
Required
Description
The current status of the credit authorization object. Defined Values: Authorized, Rejected, Posted, Held
<EffDt> <ApprovalId> <StatusModBy>
DateTime Identifier Open Enum
Credit Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<Status>
Optional
Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the CreditStatusCode is Rejected or Held.
6.3.29
Tag
Credit Information Aggregate <CreditInfo>

Type
Open Enum
The <CreditInfo> aggregate is used in messages related to credits. It is generally used in the request messages.
Usage
Required
Description
The type of the credit authorization transaction. Defined Values: UnverifiedCashDeposit, VerifiedCashDeposit, UnverifiedCheckDeposit, VerifiedCheckDeposit, EnvelopeDeposit, MultiDeposit, MerchandiseReturn, ChkPayment,ChkCash
<CreditAuthType>
This element will be deprecated from the CreditInfo aggregate in IFX 2.0. The replacement is to use the CreditType element.
Version 1.7
April 2005
37
Tag
<CreditType>
Type
Open Enum
Usage
Description
The type of the credit transaction. Defined Values: UnverifiedCashDeposit, VerifiedCashDeposit, UnverifiedCheckDeposit, VerifiedCheckDeposit, EnvelopeDeposit, MultiDeposit, MerchandiseReturn, ChkPayment,ChkCash. Since this element will be replacing CreditAuthType in the CreditInfo aggregate, this element will be required in IFX 2.0.
<CompositeCurAmt>
Aggregate see section 3.2.16.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.3.1 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.7.2.3 Identifier
Required Repeating Required XOR Required XOR Required XOR
The amounts of the credit transaction and appropriate fees.
<DepAcctId>
<PresAcctId>
Bill Presentment Account Identification Aggregate. Used for check payment. Loan Account Identification Aggregate. Used for check payment.
<LoanAcctId>
<CardAcctId>
Required XOR
Card Account Identification Aggregate. Used for check payment.
<CreditAuthId>
Optional
Credit Authorization Identifier. Assigned by the server at the time the Credit Authorization is first added. This is used to relate a credit to a previously authorized credit authorization object Credit Identifier. If this credit is used for a split deposit transaction then this element will contain the credit identifier assigned by the server of the previous credit transaction to link the credit messages together. Client Change Code. This indicates the reason why a Credit was for a different amount from the original authorization for the credit. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout
<CreditId>
Identifier
Optional
<ClientChgCode>
Open Enum
Optional
<CreditMediaItem>
Credit Media Item aggregate. This aggregate contains details pertaining to the individual items in the deposit (e.g. check, cash). Network Transaction Information. Identification and location of the terminal from which the message originates. This aggregate will be removed from the CreditInfo aggregate in IFX 2.0. With IFX 1.4+, the <NetworkTrnInfo> aggregate is available in the <MsgRqHdr> aggregate.
<NetworkTrnInfo>
38
April 2005
Version 1.7
Tag
<BaseEnvr>
Type
Usage
Optional
Description
6.3.30
Deposit Application Information Aggregate <DepAppInfo>

Type
Aggregate see section 6.3.30.2 Aggregate see section 6.3.30.1 Aggregate see section 3.2.7.2.6 Open Enum
The <DepAppInfo> aggregate contains information about a deposit application.

Tag
<DepApplicant>
Usage
Required Repeating Required
Description
Deposit Applicant Aggregate.
<DepAppAcctId>
<BankAcctInfo>
Required
Bank Account Aggregate.
<CardType>
Optional
Card Type. Defined value: ATM, Debit
<OverdraftFunding>
Overdraft Funding Aggregate.
<CreatedDt>
Application Creation Date.
6.3.30.1 Deposit Application Account Id Aggregate <DepAppAcctId>

The <DepAppAcctId> aggregate contains data about the assigned account number for the deposit application. The <DepAppAddRq> message may send an account number in this aggregate indicating that an account starter kit was issued, or the <DepAppAddRs> message may send an account number for the pending account.
Tag
<AcctId>
Type
Identifier
Usage
Optional
Description
Account Identifier. Sometimes known as account number but not restricted to numeric characters.
<AcctType> Open Enum Required Account Type. See Data Dictionary for details. Defined values: DDA, SDA, CDA, MMA, CMA <AcctKey> <AcctCur> NC-22 NC-22 Optional Optional Account Key. Checksum for international banks. Account Currency. Currency of the account. This may be necessary to uniquely identify the account, as many countries allow for a single account containing multiple subaccounts, each in a different currency. Bank Information aggregate.
<BankInfo>
Optional
6.3.30.2 Deposit Applicant Aggregate <DepApplicant>

Information about the applicant applying for a a deposit account.
Version 1.7
April 2005
39
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Aggregate see section 5.2.3.1.1 Open Enum
Usage
Optional
Description
Customer Identification Aggregate. Use this ID if the applicant is an existing bank customer. This information supersedes the CustId located in the message header. Customer Information Aggregate.
<CustInfo>
Optional
<DepApplicantAcctRel>
Optional Repeating
Deposit Applicant Account Relationship. Relationship the applicant has the the account. Defined values: Primary, Secondary, Tax Responsible, Statement Mailing, Phone Contact, Custodial, Trust, Doing Business As.
6.3.30.3 Overdraft Funding Aggregate <OverdraftFunding>

Funding account used for overdraft protection.
Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.5 NC-3
Usage
Description
<LoanAcctId>
<FundingPriority>
Funding Priority. Funding Priority for the account.
6.3.30.4 Interest Rate Information Aggregate <IntRateInfo>

Interest rate information.
Tag
<Rate> <Desc> <IntAPY> <Term>
Type
Decimal C-80 Decimal Aggregate see section 3.2.9.1 Currency Amount Currency Amount
Usage
Description
Interest Rate. Usage is a percentage. (e.g. a value of 5.2 = 5.2%) Short Description. Explanatory text associated with the interest rate code. Assigned by the financial institution. Annual Percentage Yield. Usage is a percentage of yield on an annualized basis. Term Aggregate
<LowCurAmt> <HighCurAmt>
Optional Optional
Interest Rate Low Amount. Interest Rate High Amount.
6.3.31
Deposit Application Record Aggregate <DepAppRec>
The <DepAppRec> aggregate contains the deposit application record.
40
April 2005
Version 1.7
Tag
<DepAppId> <DepAppInfo>
Type
Usage
Required Required
Description
Deposit Application Identifier. Assigned by the server at the time the application is added. Deposit Application Information Aggregate.
<DepAppStatus>
Optional
Deposit Application Status Aggregagte.
6.3.31.1 Deposit Application Status <DepAppStatus>

The <DepAppStatus> contains the status of the Deposit Application Record.
Tag
<DepAppStatusCode>
Type
Closed Enum
Usage
Required
Description
Deposit Application Status Code. Valid values: Pending, Complete, Cancelled, Feature Pending, In Work, Incomplete, New Customer Pending, Post Failed, Transmitting
Status Description. Explanatory text associated with this status. Deposit Application Status Date. The date associated with the state change to the current state. Status Mod By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
6.3.32
Payment Enclosed Information Aggregate <PmtEnclInfo>
The <PmtEnclInfo> aggregate is used in Payment Enclosed transaction messages. It is generally used in the request messages.
Tag
<PmtEnclType>
Type
Open Enum
Usage
Required
Description
The type of the Payment Enclosed transaction. Defined Values: UnverifiedCashDeposit, VerifiedCashDeposit, UnverifiedCheckDeposit, VerifiedCheckDeposit, EnvelopeDeposit, MultiDeposit
<PmtEnclPayeeInfo>
Aggregate see section 6.3.32.1 Aggregate see section 6.3.4 Aggregate see section 3.2.16.1 C-40
Optional but see Description Optional Repeating
Payment Enclosed Payee Information Aggregate. This aggregate is required if the <PmtEnclType> is other than EnvelopeDeposit. Credit Media Item aggregate. This aggregate contains details pertaining to the individual items in the enclosed payment (e.g. check, cash). The amounts of the Payment Enclosed transaction and any appropriate fees. Payment Category. The payment category selected by the customer.
<CreditMediaItem>
<CompositeCurAmt>
Required Repeating Optional
<Category>
Version 1.7
April 2005
41
Tag
<PrcDt>
Type
Date
Usage
Optional XOR Profiled support Optional XOR Profiled support Optional
Description
Payment Processing Date. The customer enters this date as the original requested processing date, not corrected for holidays and non-processing days. May be modified by the customer. Payment Due Date. The customer enters this date to represent the date the payment is due to arrive at the payee. May be modified by the customer. Base Environment aggregate
<DueDt>
Date
<BaseEnvr>
6.3.32.1 Payment Enclosed Payee Information Aggregate <PmtEnclPayeeInfo>

The <PmtEnclPayeeInfo> aggregate is used in <PmtEnclInfo> aggregate to identify the payee (when the <PmtEnclType> is other than EnvelopeDeposit).
Tag
<StdPayeeId>
Type
Aggregate see section 7.3.1.1 Aggregate see section 6.3.32.1.1 Aggregate see section 3.2.13
Usage
Description
Customers Payee Identifier. The Standard Payee as known to the CPP. Payees Name and Address Aggregate.
<PmtEnclPayee>
<IndustId>
Industry Identifier. It provides standard codes by which industries are classified.
6.3.32.1.1 Payees Name and Address Aggregate <PmtEnclPayee>

Tag
<Name> <PostAddr>
Type
C-40 Aggregate see section 3.2.3.10.1
Usage
Required Required
Description
Payee Name. Payee Address Aggregate.
6.3.32.2 Payment Enclosed Record Aggregate <PmtEnclRec>

The <PmtEnclRec> aggregate is used in Payment Enclosed transaction messages. It is generally used in the response messages.
Tag
<PmtEnclId> <PmtEnclInfo>
Type
Usage
Required Required
Description
Payment Enclosed Identifier. Assigned by the server at the time the Payment Enclosed is first added. Payment Enclosed Information aggregate.
<PmtEnclStatus>
Required
Payment Enclosed status aggregate.
42
April 2005
Version 1.7
6.3.32.3 Payment Enclosed Status Aggregate <PmtEnclStatus>

The <PmtEnclStatus> is returned in responses to Add or Modify Payment Enclosed Model. Note that all elements within this aggregate are assigned by the server and cannot be assigned or modified by the client.
Tag
<PmtEnclStatusCode>
Type
Closed Enum
Usage
Required
Description
Payment Enclosed Status Code. This identifies the payment enclosed processing status. Valid values: Cancelled, Failed, AcceptedToVerify, Verified, Rejected, Held
Status Description. Explanatory text associated with this status. Payment Enclosed Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
<Status>
Optional
Status Aggregate. This aggregate can be supplied when it is necessary to record the reason for the current status code. In particular, this aggregate is used to explain why the PmtEnclStatusCode is Failed, Rejected or Held.
6.3.33
Deposit Account Statement Record <DepAcctStmtRec>

Type
Identifier
The <DepAcctStmtRec> contains deposit account statement information.

Tag
<SPRefId>
Usage
Optional
Description
Service Provider Reference Identifier. This is a reference number for the statement.
<DepAcctId>
Optional
Deposit Account Identification Aggregate. This aggregate refers to an account that is a child of the account referenced in the request. Deposit Account Statement Identifier. Statement number; unique number assigned to a statement per account per customer. Effective Date. Date of statement; date when statement was generated. Next Closing DateTime. Account Balance Aggregate. If the <StmtType> is Legal, then this element is Required. May be used to provide the opening, closing and minimum ledger balance and any other balances to be provided on the statement. The ClosingLedger must be included. Statement Summary Amount Aggregate. Used to return all the statement summary totals for this closing statement period. Selection Start Date for this statement period..
<DepAcctStmtId>
Optional
<EffDt> <NextDt> <AcctBal>
DateTime DateTime Aggregate see section 3.2.8.1
Optional Optional Optional Repeating but see Description
<StmtSummAmt>
Optional Repeating Required
<StartDt>
Version 1.7
April 2005
43
Tag
<EndDt> <MktgInfo> <URL> <DepAcctTrnRec>
Type
DateTime C-255 URL Aggregate see section 6.3.14
Usage
Required Optional Optional Optional Repeating
Description
End date for this statement period.. Marketing Information. Contains bank-rendered statement copy. Deposit Account Transaction Record aggregate. Included if the <IncDetail> Boolean is set to True in the request. One record per message for this statement period.
6.3.33.1 Statement Summary Amount Aggregate <StmtSummAmt>

Tag
<StmtSummType>
Type
Open Enum
Usage
Required
Description
Summary Types. Used to identify the type of summary data. Defined Values: Deposits, OthCredits, Checks, OthDebits, Fees, IntCharged, IntEarned, ATM, Electronic, CreditsOnly, DebitsOnly, BAI:xxx or TMA:xxx (Reference BAI Code List at http://www.bai.org/operations/bai_codes.html, or TMA Code List at http://www.AFPonline.org/Information_Center/Publications/ Bookstore/afpbooks/afpbooks.html as maintained by Association of Financial Professionals (AFP)) Example: BAI:010 (Beginning Ledger Balance), BAI:140 (ACH Credits), etc.
<CurAmt> <Count>
Currency Amount Long
Required Optional
Summary Amount. Count. Summary Item Count. Example: This count would indicate how many checks should be contained in the detail record <DepAcctTrnRec>.
6.3.34
Tag
Check Issue Information Aggregate <ChkIssueInfo>

Type
Aggregate see section 3.2.7.2.2 DateTime Aggregate see section 3.2.17
The <ChkIssueInfo> aggregate contains the details of an issued check.

Usage
Required
Description
<DepAcctId>
<EffDt> <RefInfo>
Effective Date. The date associated with the origination of the Check Issue file. Additional Reference information to uniquely identify the bank. Defined values for contained <RefType>: CountrySpecific, BankSpecific
<ChkInfo>
Aggregate see section 6.3.34.1 Currency Amount Date Date
Optional
Check information.
<CurAmt> <DueDt> <PaidDt>
Currency Amount. Check currency amount Check Due Date. The date on which the check is due to pay. Check Origination Date. The date on which the customer originates the check.
44
April 2005
Version 1.7
Tag
<ImageURL>
Type
URL
Usage
Optional
Description
URL address for retrieving an image of the Compositelete bill encoded as HTML. This may be cached by the client for later display, or it may be viewed live directly from the Web.
6.3.34.1 Check Information Aggregate <ChkInfo>

Tag
<ChkNum> <OrigDt> <Name>
Type
NC-12 Date C-40
Usage
Description
Check number. Assigned by the Payer or CSP or CPP if payment is by paper check. Check origination date. The date on which the check is originated. Name of payer to appear on check (as originator). This can be Paying organization (Payer or Invoice Receiver) or check originator (CSP or CPP). Postal address of the Compositeany to appear on check (as originator). This can be Paying Compositeany (Payer or Invoice Receiver) or check originator (CSP or CPP) postal address. Phone number of the organization to appear on check (as originator). This can be Paying organization (Payer or Invoice Receiver) or check originator (CSP or CPP) phone number. Text description on the check.
<PostAddr>
Aggregate see section 3.2.3.10.1 Phone Number
Optional
<OrgPhone>
Optional
<Memo>
C-255
Optional
6.3.34.2 Check Issue Status Code Aggregate <ChkIssueStatus>

Tag
<ChkIssueStatusCode>
Type
Closed Enum
Usage
Required
Description
Check Issue Status Code. Values: Pending, Paid, Rejected, Pay, NoPay
Status Description. Explanatory text associated with this check issue status. Effective Date/Time. The date/time the <ChkIssueStatusCode> took effect. Status Mod By. If present, indicates who modified the Check Issue Status Code. Values: CSP, FI
6.3.34.3 Check Issue Record Aggregate <ChkIssueRec>

Tag
<ChkIssueId>
Type
Usage
Required
Description
Check Issue Identifier. Typically a combination of the deposit account ID and the check number. Check Issue Information Aggregate
<ChkIssueInfo>
Required
Version 1.7
April 2005
45
Tag
<ChkIssueStatus>
Type
Usage
Required
Description
Check Issue Status Aggregate
6.3.34.4 Check Issue Identifier Aggregate <ChkIssueId>

Tag
<ChkNum> <OrigDt> <AcctId>
Type
C-40 Date Identifier
Usage
Description
Check number. Assigned by the Payer or CSP or CPP if payment is by paper check. Check origination date. The date on which the check is originated. Account Identifier. Sometimes known as account number, but not restricted to numeric characters.
6.3.35
Tag
Check Accept Record Aggregate <ChkAcceptRec>

Type
Identifier
The <ChkAcceptRec> aggregate contains the check accept record.

Usage
Required
Description
Check Accept Identifier. Assigned by the server at the time the Check Accept is first added. Cannot be changed by the client. Check Accept Information aggregate.
<ChkAcceptId>
<ChkAcceptInfo>
Required
<ChkAcceptStatus>
Required
Check Accept Status aggregate.
6.3.35.1 Check Accept Status Aggregate <ChkAcceptStatus>

The <ChkAcceptStatus> aggregate contains details of the status of a Check Accept object.
Tag
<ChkAcceptStatusCode>
Type
Open Enum
Usage
Required
Description
The current status of the Check Accept object. Defined Values: Authorized, Rejected, Posted, Held
<EffDt>
DateTime
Required
Check Accept Status Date. The date associated with the state change to the current state.
6.3.35.2 Check Accept Information Aggregate <ChkAcceptInfo>

The <ChkAcceptInfo> aggregate is used in check accept messages. It is generally used in the request messages.
46
April 2005
Version 1.7
Tag
<ChkAcceptType>
Type
Open Enum
Usage
Required
Description
The type of the Check Accept transaction. Defined Values: ChkVerify, ChkGuarantee, ChkDeposit, ChkCash, ChkConvert, ChkVerifyConvert, ChkGuaranteeConvert,ChkPayment.
<CompositeCurAmt>
The amounts of the check transaction and appropriate fees. Credit Identifier. Use to link together items being cashed or deposited. This is returned from the server on the credit message. And presented back to the server on subsequent request messages.
<CreditId>
<SettleInd>
Boolean
Optional
Settle Indicator. Use by client to request the server treat the transaction as settled. Instead of creating a <CheckAcceptAuth> message this indicator can be used to accomplish the same concept. The server should consider setting the truncated indicator if the check is settled. Truncated Check Indicator is returned from the server and indicates the check was truncated. False indicates the check is not truncated. ATM could use this indicator to place the truncated checks in a specific bin to isolate truncated checks for servicing.
<TruncatedInd>
Boolean
Optional
<CreditMediaChkAcceptInfo>
Aggregate
Required
Credit Media Check Information aggregate. This aggregate contains check details pertaining to the individual items in the deposit or cashed check.
6.3.36
Tag
Check Accept Image Aggregate <ChkImg>

Type
Open Enum
This aggregate specifies the check image data.

Usage
Required Profiled values
Description
Encryption Type. Defined values: None, PKCS#1 , PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM Must be supported in list of encryption types in the SPs Service Profile.
<CryptType>
<SecObjId>
Identifier
Optional
Identifier of Security Object on which the <ChkImgFront> and <ChkImgBack> is encrypted. Note: If security objects are managed in band, this element should be included in order to know how to decrypt <ChkImgFront> and <ChkImgBack>.
<ChkImgFront>
Binary
Required
Front of check image. There must be agreement between two parties on the format of the image. Back of check image. There must be agreement between two parties on the format of the image.
<ChkImgBack>
Binary
Optional
Version 1.7
April 2005
47
6.3.37
Tag
Check Detail Aggregate <ChkDetail>

Type
Boolean
This aggregate specifies the check detail.

Usage
Optional
Description
ManualMicr. Use this to indicate the MICR has been keyed in manually. True indicates the MICR has been manually keyed. Bank Identifier. Qualifies account number if known by the customer/client. Usage is expected to be routing and transit number in the US or the equivalent in an international implementation. This is required in USA. Account number Process Control Check number. Assigned by the Payer or CSP or CPP if payment is by paper check. Check origination date. The date on which the check is originated. Name of payer to appear on check (as originator). This can be Paying organization (Payer or Invoice Receiver) or check originator (CSP or CPP). Postal address of the Compositeany to appear on check (as originator). This can be Paying Compositeany (Payer or Invoice Receiver) or check originator (CSP or CPP) postal address. Phone number of the organization to appear on check (as originator). This can be Paying organization (Payer or Invoice Receiver) or check originator (CSP or CPP) phone number. Text description on the check.
<ManualMicr>
<BankId>
NC-34
Optional
<AcctId> <ProcessControl> <ChkNum> <OrigDt> <Name>
C-18 C-6 NC-12 Date C-40
Optional Optional Optional Optional Optional
<PostAddr>
Optional
<OrgPhone>
Optional
<Memo>
C-255
Optional
6.3.38
Selection Range Check Number Aggregate <SelRangeChkNum>
The <SelRangeChkNum> aggregate contains two optional fields: <LowChkNum> and <HighChkNum>. The following rules are established for these fields: If <LowChkNum> but not <HighChkNum> is supplied, then the search must match check numbers that are greater than or equal to <LowChkNum>. If <HighChkNum> is supplied but not <LowChkNum>, then the search must match check numbers that are smaller than or equal to the <HighChkNum>. If both fields are supplied, then the search must match check numbers that are between or equal to the two values supplied. If a client wishes to search for a specific check number, then both <LowChkNum> and <HighChkNum> should be supplied and set to the same value.
Tag
<LowChkNum> <HighChkNum>
Type
NC-12 NC-12
Usage
Description
Selection Low Check Serial Number. Selection High Check Serial Number
48
April 2005
Version 1.7
6.3.39
Base Environment Aggregate <BaseEnvr>
The BaseEnvr aggregate contains data about the environment in which the object was created. This data will usually be established when the object is created and not modified during normal processing. The server typically manages this data.
Tag
<CreatedDt> <CreateRefId>
Type
DateTime Identifier
Usage
Required Optional
Description
Created Date/Time. The date/time the object was created. An identifier used to uniquely identify the creation of this object to the system that created the object. This will usually be a link to reference information used in creating the object. The created date/time as reported by the client. This can vary from the object creation date/time due to time zone differences, communication delays, etc. The date/time that the client recorded this object for operational purposes. This date/time will often be used to manage the availability of information or funds. Customer Identification Aggregate.
<ClientCreateDt>
DateTime
Optional
<ClientBusinessDt>
DateTime
Optional
<CustId>
Aggregate see section 3.2.3.1 Aggregate see section 3.2.18 Identifier
Optional
<NetworkTrnInfo>
Optional
Network Transaction Information. Identification and location of the terminal from which the message originates. Server Terminal Sequence Identifier. A terminal sequence identifier generated by the ATM/POS driving server (CSP) in an ATM or POS environment. The Point of Service Data. This aggregate contains information about the environment in which this message originated. Client Terminal Sequence Identifier. A sequence identifier generated by the client terminal in a Branch/CallCenter/Teller environment. Note: Required if transaction is initiated by a Branch/Call Center/Teller application.
<ServerTerminalSeqId>
Optional
<PointOfServiceData>
Optional
<ClientTerminalSeqId>
Optional
6.3.40
Tag
Passbook Record Aggregate <PassbkRec>

Type
Usage
Required Required
Description
Passbook Identifier Passbook Information Aggregate
<PassbkStatus>
Required
Passbook Status Aggregate
Version 1.7
April 2005
49
6.3.40.1 Passbook Status Record Aggregate <PassbkStatusRec>

Tag
<PassbkId> <PassbkStatus>
Type
Usage
Required Required
Description
Passbook Identifier Passbook Status Aggregate
6.3.40.2 Passbook Status Aggregate <PassbkStatus>

Tag
<PassbkStatusCode>
Type
Closed Enum
Usage
Required
Description
The current status of the Passbook object. Defined Values: UpToDate All items in the Passbook object have been printed in the passbook media. NewItems The Passbook object has new items which have not been printed in the passbook media. Automated or Teller passbook updates are possible. MediaError Passbook media may not be in sync with the Passbook object (i.e. an error occurred during printing, and the last successful line is not known). Manual intervention (e.g. from a Teller) is required in order to resynchronize the passbook media and object.
<PassbkNew ItemsToPrint>
Long
Optional
This field indicates the number of passbook items still to be printed in the passbook media. If this data is available, this field should be recalculated each time a new Passbook Item is added to the passbook. Status Description. Explanatory text associated with the current state of the object. Passbook Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
6.3.40.3 Passbook Information Aggregate <PassbkInfo>

Tag
<DepAcctId>
Type
Usage
Description
<CardAcctId>
<LoanAcctId>
50
April 2005
Version 1.7
Tag
<Name>
Type
C-40
Usage
Optional
Description
A short customer-provided name (or identifier) that differentiates one passbook from another. It would be assumed that this name could be entered or selected by an account holder, and is used to identify which passbook is being updated. This would likely only be necessary in an environment where multiple passbooks could be attached to the same account. The Id of the last successful PassbkItem that has been printed in the Passbook media. The last balance printed in the passbook media. Typical usage would only consider the <Amt> field in the currency amount type. If this value is unknown, the field is omitted. The line number on which to start printing. This should always be updated to the last line number printed+1 or reset to 1 if the next line to print is on a new page. This number is one-based, so a value of 1 means to print at the top of the page. A value of zero or negative values are reserved, and should not be used. If this value is unknown, the field is omitted. The page number on which to start printing. This number is one-based, so a value of 1 means to print on the first page of the Passbook. A value of zero or negative values are reserved, and should not be used. If this value is unknown, the field is omitted. Information on the format or layout of the associated passbook. This value is implementation specific (for example in an XFS implementation, could refer to the form to use when printing the passbook). If this field is blank or not present, this indicates to use the default format configured at the client. The number of lines on each passbook page for the physical media associated to this Passbook object. The number of pages in the passbook in the physical media associated to this Passbook object. Client Change Code. The reason the Passbook information was modified due to an unexpected situation. This field is not used when updating the server in the case where the lines have printed correctly. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountUnknown, ConsumerExceptionAmountUnknown, ConsumerTimeout
<PassbkLastItemPrinted> <PassbkLastBalPrinted>
Identifier Currency Amount
Optional Optional
<PassbkNextLine>
Long
Optional
<PassbkNextPage>
Long
Optional
<PassbkFormat>
C-40
Optional
<PassbkLinesPerPage> <PassbkPagesPerBook> <ClientChgCode>
Long Long Open Enum
<BaseEnvr>
Optional
6.3.41
Tag
Passbook Item Record Aggregate <PassbkItemRec>

Type
Identifier
Usage
Required
Description
Passbook Item Identifier
<PassbkItemId>
Version 1.7
April 2005
51
Tag
<PassbkItemInfo>
Type
Usage
Required
Description
Passbook Item Information Aggregate
<PassbkItemStatus>
Required
Passbook Item Status Aggregate
6.3.41.1 Passbook Item Status Record Aggregate <PassbkItemStatusRec>

Tag
<PassbkItemId> <PassbkItemStatus>
Type
Usage
Required Required
Description
Passbook Item Identifier Passbook Item Status Aggregate
6.3.41.2 6.3.41.3 Passbook Item Status Aggregate <PassbkItemStatus>

Tag
<PassbkItemStatusCod e>
Type
Closed Enum
Usage
Required
Description
The current status of the Passbook Item object. Defined Values: NotPrinted The Item has not yet been printed Printed The Item has been printed Unknown It is not known whether or not the item has been printed
Status Description. Explanatory text associated with the current state of the object. Passbook Item Status Date. The date associated with the state change to the current state. Approval Identifier. This is an identifier that refers to an approval event that occurred at the authorizing server. Status Modified By. Defined values: BPP, BPPSR, BSP, BSPSR, CPP, CSP, CSPSR, Customer, FI
6.3.41.4 Passbook Item Information Aggregate <PassbkItemInfo>

Tag
<PassbkId> <PassbkItemDetail>
Type
Identifier Aggregate see section 6.3.41.5 Aggregate see section 6.3.39
Usage
Required Required
Description
The Passbook Object this specific item is associated with. Details (e.g. line information) for this passbook item.
<BaseEnvr>
Optional
52
April 2005
Version 1.7
6.3.41.5 Passbook Item Detail Aggregate <PassbkItemDetail>

Tag
<PostedDt>
Type
Date
Usage
Optional
Description
Posted Date. For banking, the date on which the transaction was recorded against the account. For transfers, the date on which the entries were made on the books of the receiving Financial Institution. Transaction Type. Defined values: Debit, Credit, Withdrawal, Check, Deposit, Transfer, Payment, Interest, Dividend, DirectDeposit, DirectDebit, RepeatPayment, Fee, ServiceCharge, Adjustment, BAI:xxx or TMA:xxx (Reference BAI Code List at http://www.bai.org/operations/bai_codes.html, or TMA Code List at http://www.AFPonline.org/Information_Center/Publications/ Bookstore/afpbooks/afpbooks.html as maintained by Association of Financial Professionals (AFP)) Example: BAI:010 (Beginning Ledger Balance), BAI:140 (ACH Credits), etc.
<TrnType>
Open Enum
Optional
<CompositeCurAmt>
Aggregate see section 3.2.16.1 Currency Amount C-255
Optional Repeating Optional Optional Repeating
The amount for the specific transaction this Passbook Item Detail represents. The account balance after the processing of this item, prior to the processing of subsequent items Description of this item. The size of the passbook printable area should not be inferred from the size of this field, as it would likely be smaller.
<BalAmt> <Memo>
6.3.42
Transaction Count Limit Aggregate <TrnCountLimit>
The <TrnCountLimit> aggregate is used as selection criteria in the partial/interim/mini statement inquiry requests messages to specify the top or bottom number of desired records, or by default (when this aggregate is not present) all records, based on the specified selection criteria, from the server. Specifies options that relate to how the inquirys query should be performed. E.g., in a transaction set of 10 records, the top 5 will be the transactions numbered 1 through 5, and the bottom 5 will be the transactions numbered 6 through 10.
Tag
<LimitPosition>
Type
Closed Enum
Usage
Required
Description
Limit Position. This element specifies the start location of the selected transaction records with only two possible values: Top or Bottom. Top specifies the first <Count> records from the transaction set should be selected, and bottom specifies that the last <Count> records from the transaction set should be selected. Valid Values: Top, Bottom
<Count>
Long
Required
Count of items (transactions) from the list of available transaction history, based on the selection order specified earlier in this aggregate. Note that this number represents the number of client-requested transaction history records matching the selection criteria. The actual number of transaction records returned from the server could be less than this, depending on the number of available transaction records qualifying the selection criteria.
Version 1.7
April 2005
53
6.4Statement and Account Inquiry

6.4.1Balance Inquiry
A client may use the <BalInqRq> message to retrieve account balances without requesting message detail or a statement.
6.4.1.1 Request <BalInqRq>

The client specifies only the account for which to retrieve balances.
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Boolean
Required XOR Required XOR Required XOR Optional
<CardAcctId>
<LoanAcctId>
<IncExtBal>
Include Extended Balances Indicator. If True, the response should also include the <ExtAcctBal> aggregate and return all available balances for the type of account. If False or omitted, the response should only include the standard balances for the account in <AcctBal>. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<DeliveryMethod>
Open Enum
6.4.1.2 Response <BalInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
54
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Account Identification Aggregate.
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Boolean Open Enum Aggregate see section 3.2.8.1 Aggregate see section 3.2.8.2 C-255
Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Echoed Optional Echoed Required Repeating Optional Repeating Optional
<CardAcctId>
<LoanAcctId>
<IncExtBal> <DeliveryMethod> <AcctBal>
Include Extended Balances Indicator. Delivery Method. Account Balance Aggregate.
<ExtAcctBal>
Extended Account Balance Aggregate.
<MktgInfo>
Marketing Information.
6.4.2Balance Reversal
6.4.2.1 Request <BalRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Version 1.7
April 2005
55
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Balance Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <BalMsgRqInfo>
Optional Required
6.4.2.1.1 Balance Message Request Information Aggregate <BalMsgRqInfo>

Tag
<BalInqRq>
Type
Usage
Optional
Description
Balance Inquiry Request Message Aggregate.
6.4.2.2 Response <BalRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Balance Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier.
<Desc> <BalMsgRqInfo>
C-80 Aggregate see section 6.4.2.1.1 Identifier
<CSPRefId>
Optional
56
April 2005
Version 1.7
Tag
<SPRefId>
Type
Identifier
Usage
Optional
Description
6.4.3Account Inquiry
A client uses the Account Inquiry Message to retrieve more detailed information about a bank account than that provided by the Balance Inquiry Message. Much of the information is returned in an aggregate that is specific to each Account Type.
6.4.3.1 Request <AcctInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Boolean
<CardAcctId>
<LoanAcctId>
<IncExtBal>
Include Extended Balances Indicator. If True, the response should include the <ExtAcctBal> aggregate and return all available balances for the type of account. If False or omitted, the response should not include balances. Include Balances Indicator. If True, the response should include the <AcctBal> and <ExtAcctBal> aggregate and return all available balances for the type of account. If False or omitted, the response should not include balances. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<IncBal>
Boolean
Optional
<DeliveryMethod>
Open Enum
Version 1.7
April 2005
57
6.4.3.2 Response <AcctInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Boolean Boolean Open Enum Timestamp Date Date Aggregate see section 3.2.8.1 Aggregate see section 3.2.8.2 Aggregate see section 6.3.7 Aggregate see section 6.3.8
Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Echoed Optional Echoed Optional Echoed Required Optional Optional Optional Repeating Optional Repeating Optional XOR Optional XOR
<CardAcctId>
<LoanAcctId>
<IncExtBal> <IncBal> <DeliveryMethod> <UpDt> <LastTrnDt> <LastStmtDt> <AcctBal>
Include Extended Balances Indicator. Include Balances Indicator. Delivery Method. Account Update Timestamp. Last Transaction Date. Last Statement Cycle Date. Account Balance Aggregate
<ExtAcctBal>
Extended Account Balance Aggregate.
<DepAcctRec>
Deposit Account Record Aggregate.
<CCAcctRec>
Credit Card Account Record Aggregate.
58
April 2005
Version 1.7
Tag
<LoanAcctRec>
Type
Usage
Description
Loan Account Record Aggregate.
<LOCAcctRec>
Line of Credit Account Record Aggregate.
<MortAcctRec>
Mortgage Account Record Aggregate.
6.4.4Account Reversal
6.4.4.1 Request <AcctRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8
<RevReasonCode>
Open Enum
Required
<Desc> <AcctMsgRqInfo>
Optional Required
Description, text describing the reason for the reversal. Account Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
6.4.4.1.1 Account Message Request Information Aggregate <AcctMsgRqInfo>

Tag
<AcctInqRq>
Type
Usage
Optional
Description
Account Inquiry Request Message Aggregate.
Version 1.7
April 2005
59
6.4.4.2 Response <AcctRevRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate see section 6.4.4.1.1 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <AcctMsgRqInfo>
Reversal reason code. Description, text describing the reason for the reversal. Account Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
6.4.5Deposit Account Statement Inquiry

A client may use <DepAcctStmtInqRq> to retrieve account information for: a statement period, multiple statement periods, or a partial statement period. A client may optionally provide a date range or transaction inquiry options to limit the number of Account Statement aggregates that are returned in the response. Note that the returned statement records are either based on the normal cutoff cycles and the date range will return statements that ended (cutoff or cycled) during the specified range, or the specified number of statement records from either the top or bottom of the stack of available records, based on the specified criteria. The client may specify a date range or an inquiry options aggregate that results in no statement, because either there were no statement end cutoffs within the range or there are no statement records in the current partial statement cycle. If the client does not specify a date range or an inquiry options aggregate, the server returns as many statements as possible, but up to the maximum number of statement records available in the specified or current partial statement cycle. The client may request the detail messages associated with each returned Closing Statement or the current partial statement cycle by specifying True in the <IncDetail> Boolean.
6.4.5.1 Request <DepAcctStmtInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
60
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<TrnCountLimit>
Optional
Transaction Count Limit Aggregate. This aggregate is used as selection criteria in the transaction inquiry request messages to specify the top or bottom number of desired records, or by default (when this aggregate is not present) all records, based on the specified selection criteria, from the server. It specifies options that relate to how the inquirys query should be performed. E.g., in a transaction set of 10 records the top 5 will be the transactions numbered 1 through 5, and the bottom 5 will be the transactions numbered 6 through 10. This aggregate can only be used as a selection criterion when the <StmtType> is Partial (Interim), and it limits the number of transaction records (<DepAcctTrnRec>) within the returned <DepAcctStmtRec> aggregate.
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Boolean
<CardAcctId>
<SelRangeDt>
<IncDetail>
Optional
Include Detail Indicator. If True, the response should include the detail statement messages <DepAcctTrnRec> for the statements returned (in <DepAcctStmtRec>). If False or omitted, the detail messages should not be included. Delivery Method. Default is Channel. Value must be supported in Service Profile. Statement type Defined values: Partial, Legal
<DeliveryMethod>
Open Enum
<StmtType>
Open Enum
Version 1.7
April 2005
61
6.4.5.2 Response <DepAcctStmtInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Transaction Count Limit Aggregate. This aggregate is used as selection criteria in the transaction inquiry request messages to specify the top or bottom number of desired records, or by default (when this aggregate is not present) all records, based on the specified selection criteria, from the server. It specifies options that relate to how the inquirys query should be performed. E.g., in a transaction set of 10 records the top 5 will be the transactions numbered 1 through 5, and the bottom 5 will be the transactions numbered 6 through 10. This aggregate can only be used as a selection criterion when the <StmtType> is Partial (Interim), and it limits the number of transaction records (<DepAcctTrnRec>) within the returned <DepAcctStmtRec> aggregate.
<RecCtrlOut>
<TrnCountLimit>
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Boolean Open Enum Open Enum
Required XOR Echoed Required XOR Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed
<CardAcctId>
<SelRangeDt>
<IncDetail> <StmtType> <DeliveryMethod>
Include Detail Indicator. Statement type Delivery Method.
62
April 2005
Version 1.7
Tag
<Fee>
Type
Usage
Description
The fees charged for this transaction.
<DepAcctStmtRec>
Deposit Account Statement Record(s).
6.4.6Deposit Account Statement Reversal

6.4.6.1 Request <DepAcctStmtRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Deposit Account Statement Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <DepAcctStmtMsgRqInfo>
C-80 Aggregate
Optional Required
6.4.6.1.1 Deposit Account Statement Message Request Information Aggregate <DepAcctStmtMsgRqInfo>

Tag
<DepAcctStmtInqRq>
Type
Usage
Optional
Description
Deposit Account Statement Inquiry Request Message Aggregate.
6.4.6.2 Response <DepAcctStmtRevRs>

Tag
<Status>
Type
Aggregate
Usage
Optional
Description
Response Status Aggregate. If this aggregate is
Version 1.7
April 2005
63
Tag
Type see section 3.2.12.1
Usage
Description
absent, <StatusCode> defaults to 0 (zero).
<RqUID> <MsgRqHdr>
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Deposit Account Statement Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <DepAcctStmtMsgRqInfo>
C-80 Aggregate
Optional Optional
6.4.7Deposit Account Statement Advise

DepAcctStmtAdvise message is used to advise an entity of account information for a statement period.
6.4.7.1 Request <DepAcctStmtAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Account Statement Record.
<DepAcctStmtRec>
Optional Repeating
64
April 2005
Version 1.7
6.4.7.2 Response <DepAcctStmtAdviseRs>

Tag
<Status>
Type
Usage
Required
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header Aggregate.
<RqUID>
Required Echoed Optional Echoed Optional Echoed
<MsgRqHdr>
<CustId>
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Account Statement Record.
<DepAcctStmtRec>
Required Echoed Optional Repeating
<CSPRefId>
Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a payment corresponding to a confirmation number that was returned to the client when the payment was added or modified. When a payment has been modified, only the <CSPRefId> received in the most recent <DepAcctStmtAdvise> is valid. Service Provider Reference Identifier. Same usage as <CSPRefId>.
<SPRefId>
Identifier
Optional Repeating
6.4.8Credit Card Statement Inquiry

A client may use <CCAcctStmtInqRq> to retrieve account information for a statement period or multiple statement periods. A client may optionally provide a date range to limit the number of Account Statement aggregates that are returned in the response. Note that the statement is based on the normal cutoff cycles and the date range must return statements that ended (cutoff or cycled) during the specified range. The client may specify a date range that results in no statement, because there were no statement end cutoffs within the range. If the client does not specify a date range, the server returns as many statements as possible. The client may request the detail messages associated with each returned Statement by specifying True in the <IncDetail> Boolean.
6.4.8.1 Request <CCAcctStmtInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Version 1.7
April 2005
65
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Boolean
Optional
<CardAcctId>
Required
<SelRangeDt>
Optional
<IncDetail>
Optional
Include Detail Indicator. If True, the response should include the detail statement messages <CCAcctTrnRec> for the statements returned. If False or omitted, the detail messages should not be included. Delivery Method. Default is Channel. Value must be supported in Service Profile. Statement type Defined values: Partial, Legal
<DeliveryMethod>
Open Enum
<StmtType>
Open Enum
6.4.8.2 Response <CCAcctStmtInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control.
<RecCtrlOut>
66
April 2005
Version 1.7
Tag
<CardAcctId>
Type
Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Boolean Open Enum Open Enum Aggregate see section 6.4.8.2.1
Usage
Required Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
Description
<SelRangeDt>
<IncDetail> <StmtType> <DeliveryMethod> <CCAcctStmtRec>
Include Detail Indicator. Statement type Delivery Method. Credit Card Account Statement Record
6.4.8.2.1 Credit Card Account Statement Record <CCAcctStmtRec>

Tag
<SPRefId> <NextDt> <AcctBal>
Type
Identifier DateTime Aggregate see section 3.2.8.1 Aggregate see section 3.2.8.2 Date Currency Amount Aggregate see section 6.3.33.1 Aggregate see section 6.4.8.2.1.1 DateTime
Usage
Optional Optional Required Repeating Optional Repeating
Description
Service Provider Reference Identifier. Next Closing DateTime. Account Balance Aggregate. The ClosingOutstanding balance is required. Extended Account Balance Aggregate. Used to report other balances for this statement end, such as Period Fee, Cashline, Outstanding Cash Advance Total, Cash Available, and Over Limit Amount Payment Due Date. Minimum Payment Due. Statement Summary Amount Aggregate. Used to return all the statement summary totals for this closing statement period. Delinquency Aging Aggregate.
<ExtAcctBal>
<DueDt> <MinAmtDue> <StmtSummAmt>
Optional Optional Optional Repeating Optional Repeating Required
<DelinqAging>
<StartDt>
Selection Start DateTime Provided to allow client to use these dates to retrieve message detail corresponding to this statement. End DateTime. Provided to allow client to use these dates to retrieve message detail corresponding to this statement. Marketing Information. Contains bank-rendered statement copy. Credit Card Transaction Record Aggregate. Included if the <IncDetail> Boolean is set to True in the request.
<EndDt> <MktgInfo> <URL> <CCAcctTrnRec>
DateTime C-255 URL Aggregate see section 6.3.15
Required Optional Repeating Optional Optional Repeating
Version 1.7
April 2005
67
6.4.8.2.1.1 Delinquency Aging Aggregate <DelinqAging>

Tag
<Aging>
Type
Open Enum
Usage
Required
Description
Number of Days Delinquent. Defined values: 0-30, 31-60, 61-90, 91-120, Over121.
<CurAmt>
Currency Amount
Required
Amount Delinquent.
6.4.9Credit Card Statement Inquiry Reversal

6.4.9.1 Request <CCAcctStmtRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Card Statement Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <CCAcctStmtMsgRqInfo>
C-80 Aggregate
Optional Required
6.4.9.1.1 Credit Card Statement Message Request Information Aggregate <CCAcctStmtMsgRqInfo>

Tag
<CCAcctStmtInqRq>
Type
Usage
Optional
Description
Credit Card Statement Inquiry Request Message Aggregate.
68
April 2005
Version 1.7
6.4.9.2 Response <CCAcctStmtRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Card Statement Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <CCAcctStmtMsgRqInfo>
C-80 Aggregate
Optional Optional
6.4.10
Deposit Account Transaction Inquiry
A client uses the Deposit Account Transaction Inquiry to retrieve transaction detail for a given account. A variety of selection criteria are supported.
6.4.10.1 Request <DepAcctTrnInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Version 1.7
April 2005
69
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 6.3.16 Aggregate see section 6.3.42
Optional
<DepAcctId>
<CardAcctId>
<SelRangeDt>
Selection Range Date Aggregate. Selection criteria are based upon message posting date. Selection Range Amount Aggregate.
<SelRangeCurAmt>
Optional
<ChkRange>
Optional
Selection Range Check Number Aggregate.
<TrnCountLimit>
Optional
Transaction Count Limit Aggregate. This aggregate is used as selection criteria in the transaction inquiry request messages to specify the top or bottom number of desired records, or by default (when this aggregate is not present) all records, based on the specified selection criteria, from the server. It specifies options that relate to how the inquirys query should be performed. E.g., in a transaction set of 10 records the top 5 will be the transactions numbered 1 through 5, and the bottom 5 will be the transactions numbered 6 through 10. If this aggregate is not present, then the default is all transactions that qualify the specified selection criteria. Transaction Type. Defined values: Debit, Credit, Withdrawal, Check, Deposit, Transfer, Payment, Interest, Dividend, DirectDeposit, DirectDebit, RepeatPayment, Fee, ServiceCharge Transaction Source. Defined values: ATM, Teller, POS, VRU, HomeBank, ACH Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<TrnType>
Open Enum
Optional Repeating
<TrnSrc>
Open Enum
Optional Repeating Optional Repeating Optional Repeating Optional Profiled values
<CSPRefId>
Identifier
<SPRefId>
Identifier
<DeliveryMethod>
Open Enum
70
April 2005
Version 1.7
6.4.10.2 Response <DepAcctTrnInqRs>

The Deposit Account Transaction Inquiry Response message contains a list of Deposit Account Transaction Records for those transactions that meet the selection criteria in the request.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Deposit Account Identification Aggregate.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 6.3.16 Open Enum
Optional but see Description Required XOR Echoed Required XOR Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating Echoed
<DepAcctId>
<CardAcctId>
<SelRangeDt>
<SelRangeCurAmt>
Selection Range Amount Aggregate.
<ChkRange>
<TrnType>
Transaction Type.
Version 1.7
April 2005
71
Tag
<TrnCountLimit>
Type Aggregate see section 6.3.42
Usage
Optional Echoed
Description
Transaction Count Limit Aggregate. This aggregate is used as selection criteria in the transaction inquiry request messages to specify the top or bottom number of desired records, or by default (when this aggregate is not present) all records, based on the specified selection criteria, from the server. It specifies options that relate to how the inquirys query should be performed. E.g., in a transaction set of 10 records the top 5 will be the transactions numbered 1 through 5, and the bottom 5 will be the transactions numbered 6 through 10. If this aggregate is not present, then the default is all transactions that qualify the specified selection criteria. Transaction Source.
<TrnSrc>
Open Enum
Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Optional Repeating Optional Repeating
<CSPRefId>
Identifier
<SPRefId>
Identifier
<DeliveryMethod> <MktgInfo> <Fee>
Open Enum C-255 Aggregate see section 3.2.16.2 Aggregate see section 6.3.14
Delivery Method. Marketing Information. The fees charged for this transaction.
<DepAcctTrnRec>
Deposit Message Record Aggregate. One record per message subject to selection criteria and message records control.
6.4.11
Deposit Account Transaction Advise
6.4.11.1 Request <DepAcctTrnAdviseRq>

A server uses the Deposit Account Transaction Advise Request to notify a client of a new transaction detail for a given account. It allows for one or more transactions to be pushed to the client.
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.3.1
Usage
Required Optional
Description
<CustId>
Optional
<DepAcctId>
Required XOR
72
April 2005
Version 1.7
Tag
<CardAcctId>
Type
Usage
Required XOR Required Repeating
Description
<DepAcctTrnRec>
Deposit Message Record Aggregate.
6.4.11.2 Response <DepAcctTrnAdviseRs>

The Deposit Account Transaction Advise Response message indicates that the client received and processed the Advise Request.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<CustId>
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 6.3.14 Identifier
Required XOR Echoed Required XOR Echoed Optional Repeating Echoed Optional Repeating Optional Repeating
<CardAcctId>
<DepAcctTrnRec>
Deposit Message Record Aggregate. One record per message subject to selection criteria and message records control. Customer Service Provider Reference Identifier.
<CSPRefId>
<SPRefId>
Identifier
6.4.12
Tag
<RqUID>
Deposit Account Transaction Reversal

Type
UUID
6.4.12.1 Request <DepAcctTrnRevRq>

Usage
Required
Description
Request Identifier.
Version 1.7
April 2005
73
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Deposit Account Transaction Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <DepAcctTrnMsgRqInfo>
C-80 Aggregate
Optional Required
6.4.12.1.1 Deposit Account Transaction Message Request Information Aggregate <DepAcctTrnMsgRqInfo>

Tag
<DepAcctTrnInqRq>
Type
Usage
Optional
Description
Deposit Account Transaction Inquiry Request Message Aggregate.
6.4.12.2 Response <DepAcctTrnRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
74
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed Required Echoed Optional Echoed Required Echoed
Description
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Deposit Account Transaction Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <DepAcctTrnMsgRqInfo>
C-80 Aggregate
Optional Optional
6.4.13
Credit Card Account Transaction Inquiry
A client uses the Credit Card Account Transaction Inquiry to retrieve transaction detail for a given account. A variety of selection criteria are supported.
6.4.13.1 Request <CCAcctTrnInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2
Optional
<CardAcctId>
Required
<SelRangeDt>
Optional
Selection Range DateTime Aggregate.
<SelRangeCurAmt>
Optional
Version 1.7
April 2005
75
Tag
<TrnType>
Type
Open Enum
Usage
Optional Repeating
Description
Transaction Type. See Data Dictionary for details. This field is used as a selection criterion. Defined values: Debit, Credit, Withdrawal, Check, Deposit, Transfer, Payment, Interest, Dividend, DirectDeposit, DirectDebit, RepeatPayment, Fee, ServiceCharge, Adjustment
<TrnSrc>
Open Enum
Optional Repeating
Message Source. Defined values: ATM, Teller, POS, VRU, HomeBank, ACH This field is used as a selection criterion.
<CSPRefId> <SPRefId> <DeliveryMethod>
Identifier Identifier Open Enum
Optional Repeating Optional Repeating Optional Profiled values
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Delivery Method. Default is Channel. Value must be supported in Service Profile.
6.4.13.2 Response <CCAcctTrnInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request, and the server supports Records Control. Card Account Identifier Aggregate.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.10.1
Optional but see Description Required Echoed Optional Echoed
<CardAcctId>
<SelRangeDt>
Selection Range DateTime Aggregate.
76
April 2005
Version 1.7
Tag
<SelRangeCurAmt>
Type
Usage
Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Optional Repeating
Description
<TrnType>
Message Type.
<TrnSrc>
Open Enum
Message Source.
<CSPRefId>
Identifier
<SPRefId>
Identifier
Service Provider Reference Identifier. This field is used as a selection criterion. Delivery Method. Marketing Information. Credit Card Transaction Record Aggregate. One record per message subject to selection criteria and message records control.
<DeliveryMethod> <MktgInfo> <CCAcctTrnRec>
Open Enum C-255 Aggregate see section 6.3.15
6.4.14
Tag
<RqUID>
Credit Card Account Transaction Reversal

Type
6.4.14.1 Request <CCAcctTrnRevRq>

Usage
Required Optional
Description
<MsgRqHdr>
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Card Account Transaction Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <CCAcctTrnMsgRqInfo>
C-80 Aggregate
Optional Required
Version 1.7
April 2005
77
6.4.14.1.1 Credit Card Account Transaction Message Request Information Aggregate <CCAcctTrnMsgRqInfo>
Tag
<CCAcctTrnInqRq>
Type
Usage
Optional
Description
Credit Card Account Transaction Inquiry Request Message Aggregate.
6.4.14.2 Response <CCAcctTrnRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Card Account Transaction Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <CCAcctTrnMsgRqInfo>
C-80 Aggregate
Optional Optional
6.4.15
Note:
Bank Account Transaction Image Inquiry

The client may specify a delivery method picked from those supported in the Service Profile.
The Bank Account Transaction Image Order Message allows a client to request a copy of a check or sales slip.
78
April 2005
Version 1.7
6.4.15.1 Request <BankAcctTrnImgInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<DeliveryMethod>
Delivery Method. Used to request the delivery channel for requested information. Defined values: Channel, Courier, Email, Fax, HomeBank, InBand, Overnight, Post, TwoDay, UPS. Value selected must be supported in Service Profile.
<DeliveryMedia>
Open Enum
Optional
Delivery Media Defined values: CD, Diskette, DVD, Paper. Default value is Paper. Note: If media is specified, <DeliveryMethod> should be a physical method (i.e. Post, UPS)
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.17.1
Required XOR Required XOR Required XOR Optional Repeating XOR
<CardAcctId>
<LoanAcctId>
<StopChkInfo>
Check Description Aggregate. This field is used as a selection criterion.
Note: This aggregate will be deprecated from this message in IFX 2.0, to be replaced by <ChkNum>.
<ChkNum> NC-12 Optional Repeating XOR 1.2+ Optional Check Number. This field is used as a selection criterion.
<SelRangeCurAmt>
Selection Range Currency Amount. This field is used as a selection criterion.
Version 1.7
April 2005
79
Tag
<SelRangeChkNum>
Type
Aggregate see section 6.3.38 Aggregate see section 3.2.10.1 Open Enum Boolean
Usage
Optional
Description
Selection Range Check Number. This field is used as a selection criterion. Selection Range Date. This field is used as a selection criterion. Transaction Type. See Data Dictionary for details. This field is used as a selection criterion. Indicate whether all items should be included in a deposit request. If set to true, all items will be included with a deposit copy request. If false or omitted, include only the deposit image.
<SelRangeDt>
Optional
<TrnType> <IncAllItems>
<IncRefInfo>
Boolean
Optional
Include Reference Info. This field is used to signal that reference information requested to get the image. If set to true then RefInfo will be included with the response. Reference Information returned on a <BankAcctTrnImgIngRs> that is used to retrieve the image. Customer Contact Aggregate.
<RefInfo>
Aggregate see section 3.2.17 Aggregate see section 3.2.3.3 Aggregate see section 3.2.3.9
Optional
<CustContact>
Optional XOR Optional XOR 1.1+
<ContactInfo>
6.4.15.2 Response <BankAcctTrnImgInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
80
April 2005
Version 1.7
Tag
<DeliveryMethod>
Type
Open Enum
Usage
Optional Profiled values Echoed Optional Echoed Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Repeating XOR Echoed Optional Repeating XOR Echoed 1.2+ Optional Echoed Optional Echoed Optional Echoed Optional Repeating Echoed Optional Echoed
Description
Delivery Method.
<DeliveryMedia>
Open Enum
Delivery Media
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.17.1 NC-12
<CardAcctId>
<LoanAcctId>
<StopChkInfo>
Check Description Aggregate.
<ChkNum>
Check Number.
<SelRangeCurAmt>
Aggregate see section 3.2.10.2 Aggregate see section 3.2.10.1 Aggregate see section 6.3.38 Open Enum
Selection Range Currency Amount.
<SelRangeDt>
Selection Range Date.
<SelRangeChkNum>
Selection Range Check Number.
<TrnType>
Transaction Type. See Data Dictionary for details.
<IncAllItems>
Boolean
Indicate whether all items should be included in a deposit request. If set to true, all items will be included with a deposit copy request. If false or omitted, include only the deposit image.
<CustContact>
Aggregate see section 3.2.3.3 Aggregate see section 3.2.3.9 Aggregate see section 6.4.15.2.1 Identifier Identifier
Optional XOR Echoed Optional XOR Echoed 1.1+ Optional Repeating Optional Optional
Customer Contact Aggregate.
<ContactInfo>
<BankAcctTrnImgRec>
Bank Account Transaction Image Record Aggregate. One aggregate is returned for each record matching the selection criteria, if the <DeliveryMethod> is InBand. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Version 1.7
April 2005
81
6.4.15.2.1 Bank Account Transaction Image Record Aggregate <BankAcctTrnImgRec>

Tag
<TrnType> <CurAmt> <ChkNum> <RefInfo>
Type
Open Enum Currency Amount NC-12 Aggregate see section 3.2.17 Date Binary URL Aggregate see section 6.3.36
Usage
Description
Transaction Type. Currency Amount. The amount of the transaction. Check Number. Reference Information to retrieve an Image.
<PrcDt> <TrnImg> <ImageURL> <ChkImg>
Optional Optional OR Optional OR Optional OR
Transaction Processing Date. Transaction Image. URL for retrieving an image of the requested transaction. Check Images.
6.4.16
Tag
<RqUID>
Bank Account Transaction Image Reversal

Type
6.4.16.1 Request <BankAcctTrnImgRevRq>

Usage
Required Optional
Description
<MsgRqHdr>
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Bank Account Transaction Image Reversal Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <BankAcctTrnImgMsgRqInfo>
C-80 Aggregate
Optional Required
82
April 2005
Version 1.7
6.4.16.1.1 Bank Account Transaction Image Message Request Information Aggregate <BankAcctTrnImgMsgRqInfo>
Tag
<BankAcctTrnImgInqRq>
Type
Usage
Optional
Description
Bank Account Transaction Image Reversal Request Message Aggregate.
6.4.16.2 Response <BankAcctTrnImgRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Bank Account Transaction Image Reversal Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <BankAcctTrnImgMsgRqInfo>
C-80 Aggregate
Optional Optional
6.4.17
Note:
Interest Rate Inquiry

This is not used to obtain interest rates on open accounts, but rather for possible new accounts.
The Interest Rate Inquiry is used to retrieve current interest rates on various account types of particular balances.
6.4.17.1 Request <IntRateInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier.
Version 1.7
April 2005
83
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<AcctType>
Required
Account Type. Defined values: DDA, SDA, CCA, ILA, CLA, CDA, LOC, MLA, MMA, CMA
<AcctTaxStatus>
Open Enum
Optional
Account Tax Status. Defined values: TaxDeferred, Standard
<CurAmt> <Term>
Currency Amount Aggregate see section 3.2.9.1 Open Enum
Optional Optional
Currency Amount. Term Aggregate.
<DeliveryMethod>
6.4.17.2 Response <IntRateInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
84
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Account Type. Account Tax Status. Currency Amount. Term Aggregate. Echo of request.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Open Enum Open Enum Currency Amount Aggregate see section 3.2.9.1 Open Enum Aggregate see section 6.3.30.4
Optional but see Description Required Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
<AcctType> <AcctTaxStatus> <CurAmt> <Term>
<DeliveryMethod> <IntRateInfo>
Delivery Method. Interest Rate Aggregate.
6.4.18
Tag
<RqUID>
Interest Rate Inquiry Reversal

Type
6.4.18.1 Request <IntRateRevRq>

Usage
Required Optional
Description
<MsgRqHdr>
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal.
<RevReasonCode>
Open Enum
Required
<Desc>
C-80
Optional
Version 1.7
April 2005
85
Tag
<IntRateMsgRqInfo>
Type
Usage
Required
Description
Interest Rate Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
6.4.18.1.1 Interest Rate Message Request Information Aggregate <IntRateMsgRqInfo>

Tag
<IntRateInqRq>
Type
Usage
Optional
Description
Interst Rate Inquiry Request Message Aggregate.
6.4.18.2 Response <IntRateRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Interst Rate Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <IntRateMsgRqInfo>
C-80 Aggregate see section 6.4.18.1.1 Identifier Identifier
Optional Optional
6.4.19
Bank Account Taxation Inquiry
6.4.19.1 Request <BankAcctTaxInqRq>

The client must specify a client identifier, the account identifier, and tax details.
86
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Long Open Enum
Required XOR Required XOR Required XOR Required Optional Profiled values
<CardAcctId>
<LoanAcctId>
<TaxYear> <DeliveryMethod>
Tax year. Delivery Method. Default is Channel. Value must be supported in Service Profile.
6.4.19.2 Response <BankAcctTaxInqRs>

If research is required, requests for years other than current and prior years may require <Status> to say that it is accepted for asynchronous processing.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
87
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Long Open Enum NC-12 Aggregate see section 6.4.19.2.1
Required XOR Echoed Required XOR Echoed Required XOR Echoed Required Echoed Optional Echoed Required Optional Repeating
<CardAcctId>
<LoanAcctId>
<TaxYear> <DeliveryMethod> <TaxId> <AcctTaxInfo>
Tax year. Delivery Method. Customer Tax Identifier. Account Tax Information Aggregate.
6.4.19.2.1 Account Tax Information Aggregate <AcctTaxInfo>

Tag
<Org> <TaxType>
Type
Usage
Required Optional
Description
Organization. Organization defining this name space. Usage is Tax Authority (e.g., state or country). Tax Type. Qualified by <Org>. Defined values: WithHoldingTax, DebitsTax, FIDuty
<CurAmt> <PrevYrCurAmt> <Rate>
Currency Amount Currency Amount Decimal
Tax Amount (+ paid by customer, earned by customer). Previous Year Tax Amount (+ paid by customer, earned by customer). Tax Rate. Usage is a percentage (e.g., a value of 5.2 = 5.2%). (+ paid by customer, earned by customer)
6.4.20
Foreign Exchange Rate Inquiry
A client may request an exchange rate or a committed exchange rate for a future message. The Financial Institution may quote the current rate or may commit a rate for some time period. If a commitment is made to honor a rate until a future date, the Financial Institution must return a commitment identifier, which is provided in the <ForExRateId> in the <ForExRateRec>. In foreign exchange transactions, the trader provides the following information: The from and to currency codes, an amount, which is either the amount they wish to buy or the amount they wish to sell, and a Buy/Sell indicator, which applies to the amount provided. In all cases, a trader is actually trading, i.e. both buying one currency and selling another currency. The ForExRate messages must handle both scenarios 1) the buy
88
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification amount is provided, or 2) the sell amount is provided. The table below lists the scenarios, using USD and EUR, and states the convention of how the amount/currency elements for each will be conveyed in the ForExRate and ForExDeal messages:
FROM Scenario <CurAmt> <Amt> <CurCode> Selling exactly 1000 USD for unknown amount of EUR. Purchase exactly 1000 EUR with unknown amount of USD Selling exactly 1000 EUR for unknown amount of USD. Purchase exactly 1000 USD with unknown amount of EUR 1000.00 USD 1000.00 EUR 1000.00 EUR 1000.00 USD
TO <CurCode> <ForExRateDealType>
EUR
Sell
USD
Buy
USD
Sell
EUR
Buy
6.4.20.1 Request <ForExRateInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Currency Amount
Optional XOR Optional XOR Required
<CardAcctId>
<CurAmt>
The currency amount; which includes both a value (amount) and its associated currency code. Refer to the table above for the usage scenarios.
Version 1.7
April 2005
89
Tag
<CurCode>
Type
NC-3
Usage
Required
Description
The Currency Code of the from or to amount, depending on what the <CurAmt> above represents Refer to the table above for usage scenarios. Requested Rate Type. Valid values: Indicated, Committed
<ForExRateType>
Closed Enum Closed Enum
Optional
<ForExRateDealType>
Optional
Requested Deal Type. Valid values: Buy, Sell If not present, the default value is Buy. Refer to the table above for usage scenarios.
<ForExValDtType>
Closed Enum DateTime
Optional
Value date type of the rate. Valid values: Spot, Future
<ForExValDt>
Optional XOR but see Description Optional XOR
The requested Value date. Used for Future type deals. Required if the <ForExValDtType> is Future.
<StartDt>
DateTime
but see Description

<EndDt> DateTime Required
The requested Start date. Required if the <ForExValDtType> is Window. The <StartDt>and <EndDt> are a pair and both are required if either is present. The requested End date. Required if the <ForExValDtType> is Window. The <StartDt> and <EndDt> are a pair and both are required if either is present. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<DeliveryMethod>
Open Enum
6.4.20.2 Response <ForExRateInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
90
April 2005
Version 1.7
Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Currency Amount NC-3
Usage
Optional XOR Echoed Optional XOR Echoed Required Echoed Required Echoed
Description
Deposit Account Identification.
<CardAcctId> <CurAmt>
The currency amount; which includes both a value (amount) and its associated currency code. Refer to the table above for the usage scenarios. The Currency Code of the from or to amount, depending on what the <CurAmt> above represents Refer to the table above for usage scenarios.
<CurCode>
<ForExRateType>
Closed Enum Closed Enum Closed Enum DateTime
Optional Echoed Optional Echoed Optional Echoed Optional XOR but see Description Optional XOR but see Description Required
Requested Rate Type. Valid values: Indicated, Committed, Requested Deal Type. Valid values: Buy, Sell Value date type of the rate. Valid values: Spot, Future The requested Value date. Used for Future type deals.
<ForExRateDealType>
<ForExValDtType>
<ForExValDt>
<StartDt>
DateTime
The requested Start date. Required if the <ForExValDtType> is Window. The <StartDt>and <EndDt> are a pair and both are required if either is present. The requested End date. Required if the <ForExValDtType> is Window. The <StartDt> and <EndDt> are a pair and both are required if either is present. Delivery Method. Foreign Exchange Rate Record Aggregate
<EndDt>
DateTime
<DeliveryMethod> <ForExRateRec>
Open Enum Aggregate see section 6.4.20.2.1
6.4.20.2.1 Foreign Exchange Rate Record Aggregate <ForExRateRec>

Tag
<ForExRateId>
Type
Identifier
Usage
Description
Foreign Exchange Rate Identifier. This is required if the server is committing to an exchange rate. Foreign Exchange Rate Information Aggregate. This aggregate provides a Financial Institution commitment to honor this rate for the period of time specified. Value date type of the rate. Valid values: Spot, Future
<ForExRateInfo>
Aggregate see section 6.3.18 Closed Enum
<ForExValDtType>
Optional Echoed
Version 1.7
April 2005
91
6.4.21
Tag
<RqUID>
Foreign Exchange Rate Reversal

Type
6.4.21.1 Request <ForExRateRevRq>

Usage
Required Optional
Description
<MsgRqHdr>
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Foreign Exchange Rate Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <ForExRateMsgRqInfo>
C-80 Aggregate
Optional Required
6.4.21.1.1 Foreign Exchange Rate Message Request Information Aggregate <ForExRateMsgRqInfo>

Tag
<ForExRateInqRq>
Type
Usage
Optional
Description
Foreign Exchange Rate Inquiry Request Message Aggregate.
6.4.21.2 Response <ForExRateRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
92
April 2005
Version 1.7
Tag
Type
UUID Aggregate see section 3.2.3.1 Open Enum
Usage
Description
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Foreign Exchange Rate Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <ForExRateMsgRqInfo>
C-80 Aggregate
Optional Optional
6.5
6.5.1
Tag
Foreign Exchange Deal Elements

Foreign Exchange Deal Record Aggregate <ForExDealRec>
Type
Usage
Required Required
Description
Foreign Exchange Deal Identifier (Committed deals). Foreign Exchange Deal Information Aggregate
<ForExDealId> <ForExDealInfo>
<ForExDealStatus>
Optional
Foreign Exchange Deal Status Aggregate
Version 1.7
April 2005
93
6.5.1.1
Tag
Foreign Exchange Deal Information <ForExDealInfo>

Type
Closed Enum
Usage
Optional
Description
Requested Deal Type. Valid values: Buy, Sell If not present, the default value is Buy.
<ForExRateDealType>
<ForExValDtType>
Closed Enum DateTime
Optional
Value date type of the rate. Valid values: Spot, Future, Cash, Tom, Window
<ForExValDt>
Optional XOR but see Description Optional XOR but see Description Required
The requested Value date. Used for Future type deals.
<StartDt>
DateTime
The requested Start date. Required if the <ForExValDtType> is Window. The <StartDt> and <EndDt> are a pair and both are required if either is present. The requested End date. Required if the <ForExValDtType> is Window. The <StartDt> and <EndDt> are a pair and both are required if either is present. When part of <ForExDealAddRq>, it is an echo of the expiry date/time quoted by financial institution for the rate offer. When part of <ForExDealAddrs>, it is the date/time before which all payments or funds transfers referencing this deal must be completed.
<EndDt>
DateTime
<ExpDt>
DateTime
Optional
<CurAmt>
Currency Amount
Optional XOR
The currency amount; which includes both a value (amount) and its associated currency code. Refer to the table above for the usage scenarios The Currency Code of the from or to amount, depending on what the <CurAmt> above represents Refer to the table above for usage scenarios.
<CurCode>
NC-3
Optional XOR
<SPRefId>
Identifier
Optional XOR
Service Provider Reference Identifier. In the usage of this message, it is the unique Id assigned to the Foreign exchange deal quote.
6.5.1.2
Tag
Foreign Exchange Deal Status Aggregate <ForExDealStatus>

Type
Usage
Required
Description
Foreign Exchange Deal Status Code. Valid values: Pending, Rejected, Completed
<ForExDealStatusCode>
Status Description. Explanatory text associated with this customer/disclosure link status. Effective Date/Time. The date/time the <ForExDealStatusCode> took effect. Status Modified By. If present, indicates who modified the Status Code. Defined values: Customer, FI, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
94
April 2005
Version 1.7
6.5.2
Foreign Exchange Deal Add
A client may purchase foreign exchange currency using the <ForExDealAddRq> and later make a single or installment payment on this purchase using the associated <SPRefId> or <ForExDealId> as a reference identifier in a payment or funds transfer message.
6.5.2.1
Tag
<RqUID>
Request <ForExDealAddRq>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal information aggregate.
<CustId>
Optional
<ForExDealInfo>
Required
6.5.2.2
Tag
<Status>
Response <ForExDealAddRs>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Version 1.7
April 2005
95
Tag
<ForExDealInfo>
Type
Aggregate see section 6.5.1.1 Aggregate see section 6.5.1 Identifier Identifier
Usage
Description
Foreign Exchange Deal information aggregate.
<ForExDealRec>
Foreign Exchange Deal Record Aggregate.
Optional Optional
6.5.3Foreign Exchange Deal Modify

The Foreign Exchange Deal Modify messages provide support to modify a particular Foreign Exchange Deal.
6.5.3.1
Tag
<RqUID>
Request <ForExDealModRq>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier. Foreign Exchange Deal Information aggregate.
<CustId>
Optional
Required Required
6.5.3.2 Response <ForExDealModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
96
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier. Foreign Exchange Deal information aggregate.
<CustId>
Optional Echoed
<ForExDealRec>
Foreign Exchange Deal Record Aggregate.
Optional Optional
6.5.4Foreign Exchange Deal Inquiry

The Foreign Exchange Deal Inquiry allows for a client to inquire on foreign exchange deal(s) based upon the supplied search criteria.
Version 1.7
April 2005
97
6.5.4.1
Tag
<RqUID>
Request <ForExDealInqRq>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. ForExDeal Identifier. Service Provider Reference Identifier Requested Deal Type. Valid values: Buy, Sell If not present, the default value is Buy.
<CustId>
Optional
<ForExDealId> <SPRefId> <ForExRateDealType>
Identifier Identifier Closed Enum
Optional Repeating Optional Repeating Optional Repeating
98
April 2005
Version 1.7
6.5.4.2
Tag
<Status>
Response <ForExDealInqRs>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. ForExDeal Identifier.
<CustId>
Optional Echoed
<ForExDealId>
Identifier
Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
<SPRefId>
Identifier
Service Provider Reference Identifier
<ForExRateDealType>
Closed Enum
Requested Deal Type. Valid values: Buy, Sell If not present, the default value is Buy.
<ForExDealRec>
ForExDeal Record Aggregate.
6.5.5
6.5.5.1
Tag
<RqUID>
Foreign Exchange Deal Cancel

Request <ForExDealCanRq>
Type
UUID
The Foreign Exchange Deal Cancel message will cancel an existing pending deal.
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
99
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier.
<CustId>
Optional
<ForExDealId>
Identifier
Required
6.5.5.2
Tag
<Status>
Response <ForExDealCanRs>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier. Foreign Exchange Deal Record Aggregate.
<CustId>
Optional Echoed
<ForExDealId> <ForExDealRec>
Optional Optional
6.5.6Foreign Exchange Deal Audit

The Foreign Exchange Deal Audit message supports the ability for the client to trace the message history for all changes impacting the specified foreign exchange deal.
100
April 2005
Version 1.7
6.5.6.1
Tag
<RqUID>
Request <ForExDealAudRq>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<ForExDealId>
Identifier
Required Repeating
Foreign Exchange Deal Identifier.
6.5.6.2
Tag
<Status>
Response <ForExDealAudRs>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
101
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Foreign Exchange Deal Identifier.
<ForExDealId>
Identifier
<ForExDealMsgRec>
Message Record Aggregate.
6.5.6.2.1 Foreign Exchange Deal Message Record Aggregate <ForExDealMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Foreign Exchange Deal Add Response Message Aggregate.
<MsgRecDt> <ForExDealAddRs>
Timestamp Aggregate see section 6.5.2.2 Aggregate see section 6.5.3.2 Aggregate see section 6.5.5.2
Optional Required XOR Required XOR Required XOR
<ForExDealModRs>
Foreign Exchange Deal Modify Response Message Aggregate. Foreign Exchange Deal Cancel Response Message Aggregate.
<ForExDealCanRs>
6.5.7Foreign Exchange Deal Sync

The Foreign Exchange Deal Sync messages provide the ability for a client device to be brought up to date on changes made to the specified Foreign Exchange Deal object.
102
April 2005
Version 1.7
6.5.7.1
Tag
<RqUID>
Request <ForExDealSyncRq>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required Echoed
<ForExDealId>
Identifier
Required Repeating
Foreign Exchange Deal Identifier.
6.5.7.2
Tag
<Status>
Response <ForExDealSyncRs>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
103
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<RecCtrlOut>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Foreign Exchange Deal Identifier.
<ForExDealId>
Identifier
Required Repeating Echoed Optional Repeating Optional Optional
<ForExDealMsgRec>
Foreign Exchange Deal Message Record Aggregate.
6.5.8
6.5.8.1
Tag
<RqUID>
Foreign Exchange Deal Reversal

Request <ForExDealRevRq>
Type
UUID
The Foreign Exchange Deal Reversal message supports only a reversal on a <ForExDealAddRq> message.
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
104
April 2005
Version 1.7
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required
Description
<Desc> <ForExDealMsgRqInfo>
C-80 Aggregate
Optional Required
6.5.8.1.1 Foreign Exchange Deal Message Request Information Aggregate <ForExDealMsgRqInfo>

Tag
<ForExDealAddRq>
Type
Usage
Required
Description
Foreign Exchange Deal Add Request Message Aggregate.
6.5.8.2 Response <ForExDealRevRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
105
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Defined values: CustomerCancellation, UnspecifiedNoActionTaken, SuspectedMalfunction, FormatErrorNoActionTaken, CompletedPartially, OriginalAmountIncorrect, ResponseReceivedTooLate, CardAcceptorDeviceUnableToCompleteTransaction, DepositOutOfBalance, NoCheckInEnvelope, PaymentOutOfBalance, DepositOutOfBalanceAppliedContents, PaymentOutOfBalance-AppliedContents, UnableToDeliverMessageToPointOfService, SuspectedMalfunction-CardRetained, SuspectedMalfunctionCardReturned, SuspectedMalfunction-Track3NotUpdated, SuspectedMalfunction-NoCashDispensed, TimedOutAtTakingMoney-NoCashDispensed, TimedOutAtTakingCard-CardRetainedAndNoCashDispensed, InvalidResponse-NoActionTaken, TimeoutWaitingForResponse (reference ISO 8583:1993 Annex A.11)
<RevReasonCode>
Open Enum
Required Echoed
<Desc> <ForExDealMsgRqInfo>
C-80 Aggregate
Optional Optional
6.5.9
Foreign Exchange Deal Status Modify
The Foreign Exchange Deal Status Modify message allows for the modification of the status of a Foreign Exchange Deal.
6.5.9.1
Tag
<RqUID>
Request <ForExDealStatusModRq>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
106
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier. Foreign Exchange Deal Status aggregate.
<ForExDealId> <ForExDealStatus>
Required Required
6.5.9.2 Response <ForExDealStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier. Foreign Exchange Deal Status aggregate.
<CustId>
Optional Echoed
6.5.10
Foreign Exchange Deal Status Inquiry
The Foreign Exchange Deal Status Inquiry allows a user to inquire on Foreign Exchange Deal status.
Version 1.7
April 2005
107
6.5.10.1 Request <ForExDealStatusInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier
<CustId>
Optional
<ForExDealId>
Identifier
Required
6.5.10.2 Response <ForExDealStatusInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier Foreign Exchange Deal Status aggregate.
<CustId>
Optional Echoed
Optional Optional
108
April 2005
Version 1.7
6.5.11
Foreign Exchange Deal Advise
The Foreign Exchange Deal Advise message advises a recipient of the deal or the deal status.
6.5.11.1 Request <ForExDealAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<MsgRsHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Record Aggregate.
<CustId>
Optional
<ForExDealRec>
Aggregate see section 6.5.1 Identifier Aggregate see section 6.5.1.2
Foreign Exchange Deal Identifier Foreign Exchange Deal Status aggregate.
6.5.11.2 Response <ForExDealAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
Required
<MsgRqHdr>
Optional
<MsgRsHdr>
Optional
Version 1.7
April 2005
109
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Foreign Exchange Deal Identifier
<CustId>
Optional
<ForExDealRec>
Aggregate see section 6.5.1 Identifier Aggregate see section 6.5.1.2 Identifier Identifier
Foreign Exchange Deal Status aggregate. Foreign Exchange Deal Record Aggregate.
Optional Optional
6.6Stop Check
6.6.1Stop Check Add
The client sends a <StopChkAddRq> message to request that a check be stopped. The minimum function server must support identification of the check via check number <ChkNum> within <StopChkInfo>. The server stores the additional data elements within <StopChkInfo> (payee name and amount) to help identify the stop check request for future reference. They are not used to identify the check to be stopped.
6.6.1.1 Request <StopChkAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
110
April 2005
Version 1.7
Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.16 Aggregate see section 6.3.17.1
Usage
Required XOR Required XOR Required XOR Required XOR Required XOR
Description
<CardAcctId>
<LoanAcctId>
<ChkRange>
Selection RangeCheck Number Aggregate. <ChkRange> or <StopChkInfo>, but not both. Check Description Aggregate. This field is used as a selection criterion.
<StopChkInfo>
6.6.1.2 Response <StopChkAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.16
Required XOR Echoed Required XOR Echoed Required XOR Echoed Required XOR Echoed
<CardAcctId>
<LoanAcctId>
<ChkRange>
Selection RangeCheck Number Aggregate.
Version 1.7
April 2005
111
Tag
<StopChkInfo>
Type
Usage
Required XOR Echoed Required Repeating Optional Optional
Description
Stop Check Information Aggregate.
<StopChkRec>
Stop Check Record. This aggregate contains information about the server-stored stop check information and status. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
6.6.2Stop Check Cancel

A client may cancel a Stop Check Payment Request with a Financial Institution.
6.6.2.1 Request <StopChkCanRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.16 Aggregate see section 6.3.17.1
<CardAcctId>
<LoanAcctId>
<ChkRange>
<StopChkInfo>
Check Description Aggregate. Usage is selection criteria.
112
April 2005
Version 1.7
6.6.2.2 Response <StopChkCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.16 Aggregate see section 6.3.17.1 Aggregate see section 6.3.17 Identifier
Required XOR Echoed Required XOR Echoed Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Repeating Optional
<CardAcctId>
<LoanAcctId>
<ChkRange>
<StopChkInfo>
Stop Check Information Aggregate.
<StopChkRec>
Stop Check Record. This aggregate is provided to list all check stop payments that apply to the cancellation. Customer Service Provider Reference Identifier. This is the <CSPRefId> for this Cancel Stop Check message.
<CSPRefId>
<SPRefId>
Identifier
Optional
Service Provider Reference Identifier. This is the <SPRefId> for this Cancel Stop Check message.
6.6.3Stop Check Inquiry

The Stop Check Inquiry message allows a client to retrieve records of both current and completed stopped checks. Since volume of stopped checks is expected to be relatively low on a per-customer basis, there is not a separate Stop Check History Inquiry.
Version 1.7
April 2005
113
6.6.3.1 Request <StopChkInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.16 Aggregate see section 6.3.17.1 Aggregate see section 3.2.10.1 Boolean
Optional
<DepAcctId>
Required XOR Required XOR Required XOR Optional XOR Optional Repeating XOR Optional XOR Optional
Deposit Account Detail Aggregate.
<CardAcctId>
<LoanAcctId>
<ChkRange>
<StopChkInfo>
Check Description Aggregate. This field is used as a selection criterion. Selection Range Date Aggregate. Returns all stop check requests originated in this date range. Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<SelRangeDt>
<IncToken>
<DeliveryMethod>
Open Enum
6.6.3.2 Response <StopChkInqRs>

Tag
<Status>
Type
Usage
Optional
Description
114
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Deposit Account Detail Aggregate.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 6.3.16 Aggregate see section 6.3.17.1 Aggregate see section 3.2.10.1 Open Enum Aggregate see section 6.3.17 Identifier
Optional but see Description Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional XOR Echoed Optional XOR Repeating Echoed Optional XOR Echoed Optional Echoed Optional Repeating
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<ChkRange>
<StopChkInfo>
Stopped Check Information Aggregate.
<SelRangeDt>
<DeliveryMethod> <StopChkRec>
Delivery Method. Stopped Check Record Aggregate. One record is returned for each stopped check subject to selection criteria. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
Optional
Version 1.7
April 2005
115
6.6.4Stop Check Audit

6.6.4.1 Request <StopChkAudRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.1 Aggregate see section 6.3.16
Optional
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<SelRangeDt>
Selection Range Date Aggregate. Date of the Stop Check request. Selection RangeCheck Number Aggregate.
<ChkRange>
Optional
6.6.4.2 Response <StopChkAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
116
April 2005
Version 1.7
Tag
Type
Usage
Description
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.1 Aggregate see section 6.3.16 Aggregate see section 6.6.4.2.1
Optional but see Description Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Echoed Optional Echoed Optional Repeating
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<SelRangeDt>
Stop Check Audit Selection Criteria Aggregate.
<ChkRange>
<StopChkMsgRec>
Stop Check Message Record Aggregate.
6.6.4.2.1 Stop Check Message Record Aggregate <StopChkMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Stop Check Response Message Aggregate. One record is returned for each Stop Check message, which meets the selection criteria specified in the request. Cancel Stop Check Response Message Aggregate. One record is returned for each Cancel Stop Check message, which meets the selection criteria specified in the request. Cancel Stop Check Response Message Aggregate. One record is returned for each Reversal Stop Check message, which meets the selection criteria specified in the request.
<MsgRecDt> <StopChkAddRs>
Timestamp Aggregate see section 6.6.1.2 Aggregate see section 6.6.2.2 Aggregate see section 6.6.7.2
<StopChkCanRs>
<StopChkRevRs>
Version 1.7
April 2005
117
6.6.5Stop Check Sync

6.6.5.1 Request <StopChkSyncRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Identifier
Optional
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<Token>
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
6.6.5.2 Response <StopChkSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
118
April 2005
Version 1.7
Tag
Type
Usage
Description
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Identifier Identifier
Optional but see Description Required XOR Echoed Required XOR Echoed Required XOR Echoed Required Echoed Required
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<Token> <NewToken>
Stop Check Synchronization Aggregate. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Stop Check Message Record Aggregate.
<StopChkMsgRec>
Optional Repeating
6.6.6Stop Check Advise

The StopChk Advise message is used to notify interested parties that a StopChk object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.6.6.1 Request <StopChkAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Version 1.7
April 2005
119
Tag
<StopChkRec>
Type
Aggregate see section 6.3.17 Identifier Aggregate
Usage
Description
StopChk Record Aggregate
<StopChkId> <StopChkStatus>
StopChk Identifier.
6.6.6.2 Response <StopChkAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. StopChk Record Aggregate.
<StopChkRec>
Required XOR Echoed Required XOR Echoed Required Echoed Optional Optional
<StopChkId>
StopChk Identifier.
<StopChkStatus> <CSPRefId> <SPRefId>
Aggregate Identifier Identifier
Customer Service Provider Reference Id. Service Provider Reference Id.
6.6.7Stop Check Reversal

6.6.7.1 Request <StopChkRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
120
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Stop Check Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <StopChkMsgRqInfo>
Optional Required
6.6.7.1.1 Stop Check Message Request Information Aggregate <StopChkMsgRqInfo>

Tag
<StopChkAddRq>
Type
Aggregate see section 6.6.1.1 Aggregate see section 6.6.2.1 Aggregate see section 6.6.3.1 Aggregate see section 6.6.4.1 Aggregate see section 6.6.5.1
Usage
Description
Stop Check Add Request Message Aggregate.
<StopChkCanRq>
Stop Check Cancel Request Message Aggregate.
<StopChkInqRq>
Stop Check Inquiry Request Message Aggregate.
<StopChkAudRq>
Stop Check Audit Request Message Aggregate.
<StopChkSyncRq>
Stop Check Synchronization Request Message Aggregate.
6.6.7.2 Response <StopChkRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
Version 1.7
April 2005
121
Tag
<MsgRsHdr>
Type
Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum
Usage
Optional
Description
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Stop Check Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <StopChkMsgRqInfo>
Optional Optional
6.7Funds Transfer
This section contains messages for transferring money between accounts within one Financial Institution, or among service providers.
6.7.1Funds Transfer Add

6.7.1.1 Request <XferAddRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Information Aggregate.
<XferInfo>
Required
122
April 2005
Version 1.7
Tag
<DupChkOverride>
Type
Boolean
Usage
Optional
Description
Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new transfer being added.
6.7.1.2 Response <XferAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Information Aggregate.
<XferInfo>
Aggregate see section 6.3.19.2 Boolean Aggregate see section 6.3.19 Identifier Identifier
Required Echoed Optional Echoed Required
<DupChkOverride> <XferRec>
Duplicate Check Override Flag. Transfer Record Aggregate.
Optional Optional
6.7.2Funds Transfer Modify

6.7.2.1 Request <XferModRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
123
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Identifier. Assigned by the server at the time the Transfer is first added. Cannot be changed by the client. Transfer Information Aggregate.
<XferId> <XferInfo>
Identifier Aggregate see section 6.3.19.2 Boolean
Required Required
<DupChkOverride>
Optional
<ClientChgCode>
Open Enum
Optional
Client Change Code. This indicates the reason why an Authorization was cancelled or modified by the client, or why the fulfillment amount differed from the authorized amount. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout
6.7.2.2 Response <XferModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
124
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Identifier. Transfer Information Aggregate.
<XferId> <XferInfo>
Identifier Aggregate see section 6.3.19.2 Boolean
Required Echoed Required Echoed Optional Echoed
<DupChkOverride>
Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new transfer being added. Transfer Record Aggregate.
<XferRec>
Aggregate see section 6.3.19 Identifier Identifier Open Enum
Required
<CSPRefId> <SPRefId> <ClientChgCode>
Optional Optional Optional Echoed
Customer Service Provider Reference Identifier. Service Provider Reference Identifier. Client Change Code. This indicates the reason why an Authorization was cancelled or modified by the client, or why the fulfillment amount differed from the authorized amount. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout
6.7.3Funds Transfer Status Modify

6.7.3.1 Request <XferStatusModRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Version 1.7
April 2005
125
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Identifier. Transfer Status Aggregate.
<XferId> <XferStatus>
Required Required
6.7.3.2 Response <XferStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Identifier. Transfer Status Aggregate.
UUID Aggregate see section 6.3.19.3 Identifier Identifier
Financial Institute Reference Identifier. Service Provider Reference Identifier.
6.7.4Funds Transfer Cancel

6.7.4.1 Request <XferCanRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
126
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Identifier. Assigned by the server at the time the Transfer is first added. Cannot be changed by the client.
<XferId>
Identifier
Required
6.7.4.2 Response <XferCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Identifier. Transfer Record Aggregate. This aggregate is provided in cases where the server keeps the transfers record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Cancelled. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<XferId> <XferRec>
Optional Optional
Version 1.7
April 2005
127
6.7.5Funds Transfer Inquiry

6.7.5.1 Request <XferInqRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<XferId> <RecXferId>
Transfer Identifier. Recurring Transfer Model Identifier. This field is used as a selection criterion to select only transfer instances generated by a Recurring Transfer Model. Inclusion of <RecXferId> must not cause this message to include the recurring transfer model itself. The model may be retrieved using the Recurring Transfer Inquiry. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Loan Account Identification. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion and is subject to server support in the Service profile. Card Account Identification. This field is used as a selection criterion and is subject to server support in the Service profile
<CSPRefId>
Identifier
Optional Repeating Optional Repeating Optional XOR Optional XOR Optional XOR Optional XOR
<SPRefId>
Identifier
<DepAcctIdFrom>
<CardAcctIdFrom>
<LoanAcctIdFrom>
<DepAcctIdTo>
<CardAcctIdTo>
Aggregate
Optional XOR
128
April 2005
Version 1.7
Tag
<LoanAcctIdTo>
Type
Aggregate
Usage
Optional XOR
Description
Loan Account Identification. This field is used as a selection criterion and is subject to server support in the Service profile Transfer Status Code. Selection Range Due Date Aggregate.
<XferStatusCode> <SelRangeDueDt>
Closed Enum Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Boolean
<SelRangeCurAmt>
Optional
<IncToken>
Optional
Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<DeliveryMethod>
Open Enum
6.7.5.2 Response <XferInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Transfer Identifier.
<RecCtrlOut>
<XferId>
Version 1.7
April 2005
129
Tag
<RecXferId>
Type
Identifier
Usage
Description
Recurring Transfer Model Identifier. This field is used as a selection criterion to select only transfer instances generated by a Recurring Transfer Model. Inclusion of <RecXferId> must not cause this message to include the recurring transfer model itself. The model may be retrieved using the Recurring Transfer Inquiry. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Loan Account Identification. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion and is subject to server support in the Service profile. Card Account Identification. This field is used as a selection criterion and is subject to server support in the Service profile Loan Account Identification. This field is used as a selection criterion and is subject to server support in the Service profile Processing Status.
<CSPRefId>
Identifier
Optional Repeating Echoed Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional XOR Echoed Optional XOR Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
<SPRefId>
Identifier
<DepAcctIdFrom>
<CardAcctIdFrom>
<LoanAcctIdFrom>
<DepAcctIdTo>
<CardAcctIdTo>
Aggregate
<LoanAcctIdTo>
Aggregate
<XferStatusCode>
Closed Enum Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Open Enum Aggregate see section 6.3.19
<SelRangeDueDt>
Selection Range Due Date Aggregate.
<SelRangeCurAmt>
<DeliveryMethod> <XferRec>
Delivery Method. Transfer Record Aggregate. These records are generated by the server and reflect the current state of the customers Transfers. The records are filtered by the selection criteria specified in the request message. Also, note that transfers may have been generated by a client (using <XferAddRq>), or may have been generated by the server from one of the customers Recurring Transfer Models.
130
April 2005
Version 1.7
Tag
<Token>
Type
Identifier
Usage
Description
Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
6.7.6Funds Transfer Audit

6.7.6.1 Request <XferAudRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<XferId>
Identifier
Optional Repeating
Transfer Identifier. Assigned by the server at the time the Transfer is first added. Cannot be changed by the client. This field is used as a selection criterion.
<RecXferId>
Identifier
Optional Repeating
Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client. This field is used as a selection criterion.
Version 1.7
April 2005
131
6.7.6.2 Response <XferAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Transfer Identifier. Assigned by the server at the time the Transfer is first added. Cannot be changed by the client. This field is used as a selection criterion. Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client. This field is used as a selection criterion.
<XferId>
Identifier
<RecXferId>
Identifier
<XferMsgRec>
Optional Repeating
Transfer Message Record Aggregate.
6.7.6.2.1 Transfer Message Record Aggregate <XferMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP.
132
April 2005
Version 1.7
Tag
<MsgRecDt> <XferAddRs>
Type
Timestamp Aggregate see section 6.7.1.2 Aggregate see section 6.7.2.2 Aggregate see section 6.7.3.2 Aggregate see section 6.7.4.2 Aggregate see section 6.7.9.2
Usage
Optional Required XOR Required XOR Required XOR Required XOR Required XOR
Description
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Transfer Add Response Message Aggregate.
<XferModRs>
Transfer Modify Response Message Aggregate.
<XferStatusModRs>
Transfer Status Modify Response Message Aggregate.
<XferCanRs>
Transfer Cancel Response Message Aggregate.
<XferRevRs>
Transfer Reversal Response Message Aggregate.
6.7.7Funds Transfer Sync

6.7.7.1 Request <XferSyncRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<DepAcctIdFrom>
Required XOR
Version 1.7
April 2005
133
Tag
<CardAcctIdFrom>
Type
Usage
Description
<LoanAcctIdFrom>
6.7.7.2 Response <XferSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<RecCtrlOut>
<Token>
<DepAcctIdFrom>
Required XOR Echoed Required XOR Echoed Required XOR Echoed
<CardAcctIdFrom>
<LoanAcctIdFrom>
134
April 2005
Version 1.7
Tag
<NewToken>
Type
Identifier
Usage
Required
Description
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. If the client sent a token in the request, the server returns a new token based on this audit message.
<XferMsgRec>
Optional Repeating
Transfer Message Record Aggregate.
6.7.8Funds Transfer Advise

The Xfer Advise message is used to notify interested parties that an Xfer object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.7.8.1 Request <XferAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Xfer Record Aggregate
<XferRec>
Xfer Identifier.
6.7.8.2 Response <XferAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
Version 1.7
April 2005
135
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Xfer Record Aggregate.
<XferRec>
<XferId>
Xfer Identifier.
<XferStatus>
6.7.9Funds Transfer Reversal

6.7.9.1 Request <XferRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Transfer Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <XferMsgRqInfo>
Optional Required
136
April 2005
Version 1.7
6.7.9.1.1 Transfer Message Request Information Aggregate <XferMsgRqInfo>

Tag
<XferAddRq>
Type
Usage
Description
Transfer Add Request Message Aggregate.
<XferModRq>
Transfer Modify Request Message Aggregate.
<XferStatusModRq>
Transfer Status Modify Request Message Aggregate.
<XferCanRq>
Transfer Cancel Request Message Aggregate.
<XferInqRq>
Transfer Inquiry Request Message Aggregate.
<XferAudRq>
Transfer Audit Request Message Aggregate.
<XferSyncRq>
Transfer Synchronization Request Message Aggregate.
6.7.9.2 Response <XferRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Transfer Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<Desc> <XferMsgRqInfo>
Version 1.7
April 2005
137
Tag
Type
Usage
Optional Optional
Description
6.8Recurring Transfer Model

6.8.1Recurring Transfer Model Add
6.8.1.1 Request <RecXferAddRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Information Aggregate.
<XferInfo>
Required
<RecModelInfo>
Required Optional
<DupChkOverride>
6.8.1.2 Response <RecXferAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
138
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Transfer Information Aggregate.
<XferInfo>
Aggregate see section 6.3.19.2 Aggregate see section 3.2.11.1 Boolean Aggregate see section 6.3.19.1 Identifier Identifier
Required Echoed Required Echoed Optional Echoed Required
<RecModelInfo>
Recurring Model Information Aggregate. Duplicate Check Override Flag. Recurring Transfer Model Record Aggregate.
<DupChkOverride> <RecXferRec>
Optional Optional
6.8.2Recurring Transfer Model Modify

6.8.2.1 Request <RecXferModRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client.
<RecXferId>
Identifier
Required
Version 1.7
April 2005
139
Tag
<XferInfo>
Type
Usage
Required
Description
Transfer Information.
<RecModelInfo>
Required
Recurring Model Information.
<ModPending>
Modify Pending Flag. If allowed by profile and set by client, any changes to the recurring model must be propagated to pending transfers previously spawned from the model. Regardless of this field, any instances spawned in the future must be based on the changed model.
6.8.2.2 Response <RecXferModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Transfer Model Identifier. Transfer Information.
<RecXferId> <XferInfo>
Identifier Aggregate see section 6.3.19.2 Aggregate see section 3.2.11.1 Boolean
Required Echoed Required Echoed Required Echoed Optional Profiled support Echoed Required
<RecModelInfo>
Recurring Model Information.
<ModPending>
Modify Pending Flag.
<RecXferRec>
Recurring Transfer Model Record Aggregate.
Optional Optional
140
April 2005
Version 1.7
6.8.3Recurring Transfer Model Cancel

6.8.3.1 Request <RecXferCanRq>
Note:
Tag
<RqUID>
Cancel Recurring Transfer Model always cancels pending transfers based on the model.
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client. Cascade Delete. If True, server must delete all dependent objects when this object is deleted. If False or omitted, the recurring model must not be deleted if dependent transfers exist.
<RecXferId>
Identifier
Required
<CascadeDel>
Boolean
Optional
6.8.3.2 Response <RecXferCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
141
Tag
<RecXferId> <CascadeDel> <RecXferRec>
Type
Identifier Boolean Aggregate see section 6.3.19.1
Usage
Required Echoed Optional Echoed Optional XOR
Description
Recurring Transfer Model Identifier. Cascade Delete. Recurring Transfer Model Record Aggregate. This aggregate is provided in cases where the server keeps the recurring transfer models record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Cancelled. Open Enum containing a list of depending object types that exist for the recurring model. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<DependentType>
Open Enum
Optional XOR Repeating Optional Optional
6.8.4Recurring Transfer Model Inquiry

6.8.4.1 Request <RecXferInqRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<RecXferId>
Optional Repeating
<DepAcctIdFrom>
Deposit Account Identification Aggregate. This field is used as a selection criterion. Card Account Identification Aggregate. This field is used as a selection criterion.
<CardAcctIdFrom>
142
April 2005
Version 1.7
Tag
<LoanAcctIdFrom>
Type
Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.2 Identifier
Usage
Description
Loan Account Identification Aggregate. This field is used as a selection criterion. Selection Range Amount Aggregate.
<SelRangeCurAmt>
<CSPRefId>
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<SPRefId>
Identifier
<IncToken>
Boolean
<DeliveryMethod>
Open Enum
6.8.4.2 Response <RecXferInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Recurring Transfer Model Identifier.
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed Optional XOR Echoed
<RecXferId>
<DepAcctIdFrom>
Deposit Account Detail Aggregate.
Version 1.7
April 2005
143
Tag
<CardAcctIdFrom>
Type
Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.2 Identifier
Usage
Optional XOR Echoed Optional XOR Echoed Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Repeating
Description
Card Account Detail Aggregate.
<LoanAcctIdFrom>
Loan Account Detail Aggregate.
<SelRangeCurAmt>
<CSPRefId>
<SPRefId>
Identifier
<IncToken> <DeliveryMethod> <RecXferRec>
Boolean Open Enum Aggregate see section 6.3.19.1 Identifier
Include Token. Delivery Method. Recurring Transfer Model Record Aggregate. One record is returned for each of the customers Recurring Transfer Models that meet the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
6.8.5Recurring Transfer Model Audit

6.8.5.1 Request <RecXferAudRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
144
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Input Aggregate.
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Action. Used to identify actions associated with the object that is being audited (e.g. payment, transfer, etc.). Valid values: Add, Mod, Can This field is used as a selection criterion.
<RecXferId>
Identifier
Optional Repeating
6.8.5.2 Response <RecXferAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
<SelRangeDt>
Version 1.7
April 2005
145
Tag
<Method>
Type
Closed Enum
Usage
Description
Action. Used to identify actions associated with the object that is being audited (e.g. payment, transfer, etc.). This field is used as a selection criterion. Recurring Transfer Model Identifier. Assigned by the server at the time the Recurring Transfer Model is first added. Cannot be changed by the client. This field is used as a selection criterion.
<RecXferId>
Identifier
<RecXferMsgRec>
Optional Repeating
Recurring Transfer Message Record Aggregate.
6.8.5.2.1 Recurring Transfer Message Record Aggregate <RecXferMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Recurring Transfer Add Response Message Aggregate.
<MsgRecDt> <RecXferAddRs>
Timestamp Aggregate see section 6.8.1.2 Aggregate see section 6.8.2.2 Aggregate see section 6.8.3.2 Aggregate see section 6.8.7.2
<RecXferModRs>
Recurring Transfer Modify Response Message Aggregate.
<RecXferCanRs>
Recurring Transfer Cancel Response Message Aggregate.
<RecXferRevRs>
Recurring Transfer Reversal Response Message Aggregate.
6.8.6Recurring Transfer Model Sync

6.8.6.1 Request <RecXferSyncRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
146
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<Token>
Required
<DepAcctIdFrom>
<CardAcctIdFrom>
<LoanAcctIdFrom>
6.8.6.2 Response <RecXferSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Version 1.7
April 2005
147
Tag
<DepAcctIdFrom>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Identifier
Usage
Description
<CardAcctIdFrom>
<LoanAcctIdFrom>
<NewToken>
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Recurring Transfer Message Record Aggregate.
<RecXferMsgRec>
Optional Repeating
6.8.7Recurring Transfer Reversal

6.8.7.1 Request <RecXferRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Recurring Transfer Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <RecXferMsgRqInfo>
Optional Required
6.8.7.1.1 Recurring Transfer Message Request Information Aggregate <RecXferMsgRqInfo>
148
April 2005
Version 1.7
Tag
<RecXferAddRq>
Type
Aggregate see section 6.8.1.1 Aggregate see section 6.8.2.1 Aggregate see section 6.8.3.1 Aggregate see section 6.8.4.1 Aggregate see section 6.8.5.1 Aggregate see section 6.8.6.1
Usage
Description
Recurring Transfer Add Request Message Aggregate.
<RecXferModRq>
Recurring Transfer Modify Request Message Aggregate.
<RecXferCanRq>
Recurring Transfer Cancel Request Message Aggregate.
<RecXferInqRq>
Recurring Transfer Inquiry Request Message Aggregate.
<RecXferAudRq>
Recurring Transfer Audit Request Message Aggregate.
<RecXferSyncRq>
Recurring Transfer Synchronization Request Message Aggregate.
6.8.7.2 Response <RecXferRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Recurring Transfer Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <RecXferMsgRqInfo>
Optional Optional
Version 1.7
April 2005
149
6.9Customer Communications
6.9.1Check Order
6.9.1.1 Check Order Add
6.9.1.1.1 Request <ChkOrdAddRq>
The client sends a <ChkOrdAddRq> to place a new check order.. Note:
Tag
<RqUID>
The customer must determine the supported values for <Count> and <ChkBkStyleId> through an out-of-band process.
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Order Information Aggregate.
<ChkOrdInfo>
Required
6.9.1.1.2 Response <ChkOrdAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
150
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<ChkOrdInfo>
<ChkOrdRec>
Check Order Record Aggregate.
Optional Optional
6.9.1.2 Check Order Modification

6.9.1.2.1 Request <ChkOrdModRq>
Check Order Modification Request message modifies a previously added check order record.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client. Check Order Information Aggregate.
<ChkOrdId>
Identifier
Required
<ChkOrdInfo>
Required
6.9.1.2.2 Response <ChkOrdModRs>
Version 1.7
April 2005
151
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client. Check Order Information Aggregate.
<ChkOrdId>
Identifier
<ChkOrdInfo>
<ChkOrdRec>
Check Order Model Record Aggregate.
Optional Optional
6.9.1.3 Check Order Cancellation

6.9.1.3.1 Request <ChkOrdCanRq>
Check Order Cancellation Request message cancels a previously added check order record.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
152
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client.
<ChkOrdId>
Identifier
Required
6.9.1.3.2 Response <ChkOrdCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client. Check Order Model Record Aggregate.
<ChkOrdId>
Identifier
<ChkOrdRec>
Aggregate see section 6.3.20 Identifier Identifier
Optional Optional
6.9.1.4 Check Order Inquiry

6.9.1.4.1 Request <ChkOrdInqRq>
Check Order Inquiry Request message retrieves check order records based on selection criteria provided.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
Version 1.7
April 2005
153
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control In.
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Identifier Identifier
Optional
<DepAcctId>
Required XOR Required XOR Required XOR Optional Repeating Optional Repeating
<CardAcctId>
Credt Card Account Identifier Aggregate.
<LoanAcctId>
<ChkOrdId> <RecChkOrdId>
Check Order Identifier. Recurring Check Order Identifier. This field is used as a selection criterion to select only check order instances generated by Recurring Check Order Model. Inclusion of <RecChkOrdId> must not cause this message to include the recurring check order model itself. The model may be retrieved using the Recurring Check Order Inquiry. Selection Date Range.
<SelRangeDt>
Optional
6.9.1.4.2 Response <ChkOrdInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
154
April 2005
Version 1.7
Tag
Type
Usage
Description
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Record Control. Deposit Account Identifier Aggregate.
<RecCtrlOut>
Optional but see Description Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Repeating Echoed Optional Repeating Echoed
<DepAcctId>
<CardAcctId>
Credit Card Account Identifier Aggregate.
<LoanAcctId>
<ChkOrdId>
Check Order Identifier.
<RecChkOrdId>
Identifier
Recurring Check Order Identifier. This field is used as a selection criterion to select only check order instances generated by a Recurring Check Order Model. Inclusion of <RecChkOrdId> must not cause this message to include the recurring check order model itself. The model may be retrieved using the Recurring Check Order Inquiry. Selection Date Range.
<SelRangeDt>
Optional
<ChkOrdRec>
6.9.1.5 Check Order Audit

6.9.1.5.1 Request <ChkOrdAudRq>
Check Order Audit Request message audits a previously added check order record.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
155
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Record Control Input Aggregate.
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Action. Used to identify actions associated with the object that is being audited (e.g. payment, ChkOrd, etc.). Valid values: Add, Mod, Can This field is used as selection criterion.
<ChkOrdId>
Identifier
Optional Repeating
Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client. This field is used as selection criterion.
<RecChkOrdId>
Identifier
Optional Repeating
Recurring Check Order Identifier. Assigned by the server at the time the Recurring Check Order Model is first added. Cannot be changed by the client. This field is used as selection criterion.
6.9.1.5.2 Response <ChkOrdAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
156
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Record Control. Selection Range Date Aggregate.
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Required Echoed
<SelRangeDt>
<Method>
Action. Used to identify actions associated with the object that is being audited (e.g. payment, ChkOrd, etc.). This field is used as selection criterion. Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client. This field is used as a selection criterion.
<ChkOrdId>
Identifier
<RecChkOrdId>
Identifier
Optional Repeating
<ChkOrdMsgRec>
Optional Repeating
Check Order Message Record Aggregate.
6.9.1.5.2.1 Check Order Message Record Aggregate <ChkOrdMsgRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 6.9.1.1.2 Aggregate see section 6.9.1.2.2 Aggregate see section 6.9.1.3.2 Aggregate see section 6.9.1.8.2
Usage
Optional Repeating Optional Required XOR Required XOR Required XOR Required XOR
Description
<MsgRecDt> <ChkOrdAddRs>
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Check Order Add Response Message Aggregate.
<ChkOrdModRs>
Check Order Modify Response Message Aggregate.
<ChkOrdCanRs>
Check Order Cancel Response Message Aggregate.
<ChkOrdRevRs>
Check Order Reversal Response Message Aggregate.
Version 1.7
April 2005
157
6.9.1.6 Check Order Synchronization

6.9.1.6.1 Request <ChkOrdSyncRq>
Check Order Synchronization Request message synchronizes the client with the server.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
Token. Server assigned. Client should make no assumption about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server.
<ChkOrdId>
Identifier
Required
Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client.
6.9.1.6.2 Response <ChkOrdSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
158
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Record Control. Token. Server assigned. Client should make no assumption about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server.
<RecCtrlOut>
<Token>
<ChkOrdId>
Identifier
Check Order Model Identifier. Assigned by the server at the time the Check Order is first added. Cannot be changed by the client. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Check Order Message Record Aggregate.
<NewToken>
Identifier
<ChkOrdMsgRec>
Optional Repeating
6.9.1.7 Check Order Advise

The ChkOrd Advise message is used to notify interested parties that a ChkOrd object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.9.1.7.1 Request <ChkOrdAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. ChkOrd Record Aggregate
<ChkOrdRec>
<ChkOrdId>
ChkOrd Identifier.
Version 1.7
April 2005
159
Tag
<ChkOrdStatus>
Type
Usage
Required
Description
6.9.1.7.2 Response <ChkOrdAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. ChkOrd Record Aggregate.
<ChkOrdRec>
<ChkOrdId>
ChkOrd Identifier.
<ChkOrdStatus>
6.9.1.8 Check Order Reversal

6.9.1.8.1 Request <ChkOrdRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
160
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Check Order Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <ChkOrdMsgRqInfo>
C-80 Aggregate see section 6.9.1.8.1.1
Optional Required
6.9.1.8.1.1 Check Order Message Request Information Aggregate <ChkOrdMsgRqInfo>

Tag
<ChkOrdAddRq>
Type
Usage
Description
Check Order Add Request Message Aggregate
<ChkOrdModRq>
Check Order Modify Request Message Aggregate
<ChkOrdCanRq>
Check Order Cancel Request Message Aggregate
<ChkOrdInqRq>
Check Order Inquiry Request Message Aggregate.
<ChkOrdAudRq>
Check Order Audit Request Message Aggregate
<ChkOrdSyncRq>
Check Order Synchronization Request Message Aggregate
6.9.1.8.2 Response <ChkOrdRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
Version 1.7
April 2005
161
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum
Usage
Description
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Check Order Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <ChkOrdMsgRqInfo>
C-80 Aggregate see section 6.9.1.8.1.1 Identifier Identifier
Optional Optional
6.9.2Recurring Check Order

6.9.2.1 Recurring Check Order Add
6.9.2.1.1 Request <RecChkOrdAddRq>
The Recurring Check Order Model Add message allows a client to set-up a recurring or repeating check order.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<ChkOrdInfo>
Required
162
April 2005
Version 1.7
Tag
<RecModelInfo>
Type
Usage
Required
Description
<DupChkOverride>
Optional
Duplicate Check Override Flag. When set to True, request that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new Check Order being added.
6.9.2.1.2 Response <RecChkOrdAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Order Information Aggregate.
<ChkOrdInfo>
Required Echoed Required Echoed Optional Echoed
<RecModelInfo>
<DupChkOverride>
Duplicate Check Override Flag. When set to True, request that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new Check Order being added. Recurring Check Order Record Aggregate.
<RecChkOrdRec>
Required
Optional Optional
6.9.2.2 Recurring Check Order Modification

6.9.2.2.1 Request <RecChkOrdModRq>
Version 1.7
April 2005
163
Interactive Financial Exchange Business Message Specification The Recurring Check Order Model Modification message allows a client to modify a previously added recurring or repeating check order.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Check Order Model Identifier. Assigned by the server at the tgime the Recurring Check Order Model is first added. Cannot be changed by the client. Check Order Information Aggregate.
<RecChkOrdId>
Identifier
Required
<ChkOrdInfo>
Required
<RecModelInfo>
Required
<ModPending>
Modify Pending Flag. If allowed by profile and set by the client, any changes to the recurring model must be propagated to pending check orders previoiusly spawned from the model. Regardless of this field, any instances spawned in the future must be based on the changed model.
6.9.2.2.2 Response <RecChkOrdModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
164
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Check Order Model Identifier. Check Order Information Aggregate.
<RecChkOrdId> <ChkOrdInfo>
Identifier Aggregate see section 6.3.20.1 Aggregate see section 3.2.11.1 Boolean
Required Echoed Required Echoed Required Echoed Optional Profiled support Echoed Required
<RecModelInfo>
<ModPending>
Modify Pending Flag.
<RecChkOrdRec>
Recurring Check Order Record Aggregate.
Optional Optional
6.9.2.3 Recurring Check Order Cancellation

6.9.2.3.1 Request <RecChkOrdCanRq>
Recurring Check Order Cancellation Request message cancels a previously added recurring check order record.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Check Order Model Identifier. Assigned by the server at the thime the Recurring Check Order Model is first added. Cannot be changed by the client.l
<RecChkOrdId>
Identifier
Required
Version 1.7
April 2005
165
Tag
<CascadeDel>
Type
Boolean
Usage
Optional
Description
Cascade Delete. If True, the server must delete all dependent objects when this object is deleted. If False or omitted, the recurring model must not be deleted if dependent Check Orders exist.
6.9.2.3.2 Response <RecChkOrdCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Check Order Model Identifier. Cascade Delete Flag. Check Order Model Record Aggregate.
<RecChkOrdId> <CascadeDel> <RecChkOrdRec>
Identifier Boolean Aggregate see section 6.3.21 Open Enum
Required Echoed Optional Echoed Optional XOR Optional XOR Repeating Optional Optional
<DependentType>
Dependent object type that exists for the customer/service link. One element must be returned for each dependent. Defined values: ChkOrd Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
6.9.2.4 Recurring Check Order Inquiry

6.9.2.4.1 Request <RecChkOrdInqRq>
Recurring Check Order Inquiry Request message retrieves recurring check order records based on selection criteria provided.
166
April 2005
Version 1.7
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control In.
<RecCtrlIn>
Optional
<DepAcctId>
Required XOR Required XOR Required XOR Optional Repeating
<CardAcctId>
Credt Card Account Identifier Aggregate.
<LoanAcctId>
<RecChkOrdId>
Recurring Check Order Identifier. This field is used as a selection criterion to select only check order instances generated by Recurring Check Order Model. Inclusion of <RecChkOrdId> must not cause this message to include the recurring check order model itself. The model may be retrieved using the Recurring Check Order Inquiry. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Selection Date Range.
<CSPRefId>
Identifier
<SPRefId>
Identifier
<SelRangeDt>
<IncToken>
Optional
Include Token. If True, a <Token> should be included in the response to set a base for future Audit messages. If False or omitted, no <Token> is returned.
6.9.2.4.2 Response <RecChkOrdInqRs>
Version 1.7
April 2005
167
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Record Control. Deposit Account Identifier Aggregate.
<RecCtrlOut>
Optional but see Description Required XOR Echoed Required XOR Echoed Required XOR Echoed Optional Repeating Echoed
<DepAcctId>
<CardAcctId>
Credit Card Account Identifier Aggregate.
<LoanAcctId>
<RecChkOrdId>
Recurring Check Order Identifier. This field is used as a selection criterion to select only check order instances generated by a Recurring Check Order Model. Inclusion of <RecChkOrdId> must not cause this message to include the recurring check order model itself. The model may be retrieved using the Recurring Check Order Inquiry. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Selection Date Range.
<CSPRefId>
Identifier
Optional Repeating Echoed Optional Repeating Echoed Optional
<SPRefId>
Identifier
<SelRangeDt>
<RecChkOrdRec>
Optional Repeating
168
April 2005
Version 1.7
Tag
<Token>
Type
Identifier
Usage
Description
6.9.2.5 Recurring Check Order Audit

6.9.2.5.1 Request <RecChkOrdAudRq>
Recurring Check Order Audit Request message audits a previously added recurring check order record.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Action. Used to identify actions associated with the object that is being audited (e.g. payment, ChkOrd, etc.). Valid values: Add, Mod, Can This field is used as selection criterion.
<RecChkOrdId>
Identifier
Optional Repeating
6.9.2.5.2 Response <RecChkOrdAudRs>
Version 1.7
April 2005
169
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Record Control. Selection Range Date Aggregate.
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed
<SelRangeDt>
<Method>
Action. Used to identify actions associated with the object that is being audited (e.g. payment, ChkOrd, etc.). This field is used as selection criterion. Recurring Check Order Identifier. Assigned by the server at the time the Recurring Check Order Model is first added. Cannot be changed by the client. This field is used as selection criterion.
<RecChkOrdId>
Identifier
<RecChkOrdMsgRec>
Optional Repeating
Recurring Check Order Message Record Aggregate.
6.9.2.5.2.1 Recurring Check Order Message Record Aggregate <RecChkOrdMsgRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 6.9.2.1.2 Aggregate see section 6.9.2.2.2
Usage
Optional Repeating Optional Required XOR Required XOR
Description
<MsgRecDt> <RecChkOrdAddRs>
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Recurring Check Order Add Response Message Aggregate.
<RecChkOrdModRs>
Recurring Check Order Modify Response Message Aggregate.
170
April 2005
Version 1.7
Tag
<RecChkOrdCanRs>
Type
Usage
Required XOR
Description
Recurring Check Order Cancel Response Message Aggregate.
6.9.2.6 Recurring Check Order Synchronization

6.9.2.6.1 Request <RecChkOrdSyncRq>
Recurring Check Order Synchronization Request message synchronizes the client with the server.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
Token. Server assigned. Client should make no assumption about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server.
<DepAcctId>
<CardAcctId>
<LoanAcctId>
6.9.2.6.2 Response <RecChkOrdSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
Version 1.7
April 2005
171
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Record Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Record Control. Deposit Account Identification Aggregate.
<RecCtrlOut>
Optional but see Description Required XOR Echoed Required XOR Echoed Required XOR Echoed Required
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<NewToken>
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Recurring Check Order Message Record Aggregate.
<RecChkOrdMsgRec>
Optional Repeating
6.9.2.7 Recurring Check Order Instance Add

The Recurring Check Order Instance Add messages allow a client to manually trigger the spawning of a check order instance from a Recurring Check Order Model that has its frequency value defined as Manually. This message is particularly useful because check orders occur on an irregular frequency basis. Values provided within <ChkOrdInfo> override the values already specified within the recurring check order model specified by <RecChkOrdId>
6.9.2.7.1 Request <RecChkOrdInstAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
172
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Check Order Model Identifier. The identifier for the recurring check order model. Check Order Detail.
<RecChkOrdId> <ChkOrdDetail>
Required Optional
6.9.2.7.2 Response <RecChkOrdInstAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Check Order Model Identifier. The identifier for the recurring check order model. Check Order Detail.
<RecChkOrdId> <ChkOrdDetail>
6.9.3Deposit Book Order Add

The Deposit Book Order message allows a client to order a Deposit Book from a Financial Institution.
Version 1.7
April 2005
173
6.9.3.1 Request <DepBkOrdAddRq>

The client must specify a client identifier, account identifier, number of deposit slips, deposit book style, and delivery method when ordering a Deposit Book.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Book Order Info Aggregate.
<DepBkOrdInfo>
Required
6.9.3.2 Response <DepBkOrdAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Book Order Info Aggregate.
<DepBkOrdInfo>
Required Echoed
174
April 2005
Version 1.7
Tag
<DepBkOrdRec>
Type
Usage
Required
Description
Deposit Book Order Record Aggregate.
Optional Optional
6.9.4Deposit Book Order Add

The DepBkOrd Advise message is used to notify interested parties that a DepBkOrd object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.9.4.1 Request <DepBkOrdAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. DepBkOrd Record Aggregate
<DepBkOrdRec>
<DepBkOrdId> <DepBkOrdStatus>
DepBkOrd Identifier.
6.9.4.2 Request <DepBkOrdAdviseRq>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
175
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. DepBkOrd Record Aggregate.
<DepBkOrdRec>
<DepBkOrdId>
DepBkOrd Identifier.
<DepBkOrdStatus>
6.9.5Deposit Book Order Reversal

6.9.5.1 Request <DepBkOrdRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Deposit Book Order Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <DepBkOrdMsgRqInfo>
Optional Required
6.9.5.1.1 Deposit Book Order Message Request Information Aggregate <DepBkOrdMsgRqInfo>
176
April 2005
Version 1.7
Tag
<DepBkOrdAddRq>
Type
Usage
Optional
Description
Deposit Book Order Add Request Message Aggregate.
6.9.5.2 Response <DepBkOrdRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Deposit Book Order Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <DepBkOrdMsgRqInfo>
Optional Optional
6.10
6.10.1
Debit and Credit

Debit Messages
The debit messages are used to obtain authorization and perform a debit of money from an account for a cash (or other valuable media) withdrawal or the purchase of merchandise. In the POS environment, for some merchandise purchases it is common that an authorization is required before the purchase is completed. To perform this the DebitAuthAddRq message is used to get authorization for the amount to be debited from the specified account. At this stage the funds may be held, but not yet debited from the account. On receipt of a good response, the DebitAddRq message is used to fulfill the merchandise purchase. The actual amount dispensed may be less than that previously authorized, but in any case the DebitAdd message should initiate the actual debit and stop the hold on the funds. The link between the Debit Authorization and the actual Debit is by means of the DebitAuthId, which is supplied by the server in the DebitAuthAdd response.
Version 1.7
April 2005
177
Interactive Financial Exchange Business Message Specification When performing a cash (or other valuable media) withdrawal in an ATM environment, the DebitAddRq message is used to debit the specified amount from an account. On receipt of a good response, the cash (or other valuable media) is dispensed. To modify a previous debit the DebitModRq message can be used. The DebitModRq message is typically used in a situation when a dispense is attempted but no money or only a partial amount of money requested could be dispensed. If the client terminal did not receive a response to the DebitAddRq, the client terminal can use the DebitRevRq message to reverse the previous debit request. When performing a cash (or other valuable media) withdrawal in a Teller environment, the DebitAddRq message is used to debit the specified amount from an account. On receipt of a good response, the cash (or other valuable media) is dispensed. To modify a previous debit the DebitModRq message can be used. The DebitModRq message is typically when a Teller needs to correct an amount error. If the teller terminal did not receive a response to the DebitAddRq, the teller terminal can use the DebitRevRq message to reverse the previous debit request.
6.10.1.1 Debit Authorization Add

The Debit Authorization Add message is used to request authorization for a debit.
6.10.1.1.1 Request <DebitAuthAddRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Authorization Information Aggregate
<DebitAuthInfo>
Required
6.10.1.1.2 Response <DebitAuthAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
178
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 6.3.26.1 Aggregate see section 6.3.26 Identifier Identifier
Usage
Optional
Description
<DebitAuthInfo>
Debit Authorization Info Aggregate
<DebitAuthRec>
Debit Authorization Record Aggregate.
Optional Optional
6.10.1.2 Debit Authorization Modify

The Debit Authorization Modify message is used to modify the Information previously supplied in a Debit Authorization Add request.
6.10.1.2.1 Request <DebitAuthModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Authorization Identifier. Assigned by the server at the time the Debit Authorization is first added. Cannot be changed by the client. Debit Authorization Info Aggregate
<DebitAuthId>
Identifier
Required
<DebitAuthInfo>
Required
6.10.1.2.2 Response <DebitAuthModRs>
Version 1.7
April 2005
179
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Aggregate see section 6.3.26.1 Aggregate see section 6.3.26 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Required Echoed Required
<DebitAuthId> <DebitAuthInfo>
Debit Authorization Identifier Debit Authorization Info Aggregate
<DebitAuthRec>
Debit Authorization Record Aggregate
Optional Optional
6.10.1.3 Debit Authorization Cancel

The client uses this message to cancel a previously added debit authorization.
6.10.1.3.1 Request <DebitAuthCanRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
180
April 2005
Version 1.7
Tag
<DebitAuthId>
Type
Identifier
Usage
Required
Description
Debit Authorization Identifier. Assigned by the server at the time the Debit Authorization is first added. Cannot be changed by the client. Client Change Code. This indicates the reason why an Authorization was cancelled or modified by the client, or why the fulfillment amount differed from the authorized amount. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout This element will be removed from the DebitAuthCanRq message in IFX 2.0.
<ClientChgCode>
Open Enum
Required
6.10.1.3.2 Response <DebitAuthCanRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Aggregate see section 6.3.26 Open Enum
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Optional
<DebitAuthId> <DebitAuthRec>
Debit Authorization Identifier Debit Authorization Record Aggregate.
<ClientChgCode>
Required Echoed
Client Change Code. This element will be removed from the DebitAuthCanRs message in IFX 2.0. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
6.10.1.4 Debit Authorization Inquiry

6.10.1.4.1 Request <DebitAuthInqRq>
Version 1.7
April 2005
181
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<DebitAuthId> <CSPRefId>
Optional Repeating Optional Repeating Optional Repeating Optional XOR Optional XOR Optional Repeating
Debit Authorization Identifier. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Client Change Code. This field is used as a selection criterion. This element will be removed from the DebitAuthInqRq message in IFX 2.0.
<SPRefId>
Identifier
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Open Enum
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
Optional
<SelRangeCurAmt>
Optional
<IncToken>
Optional
Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned.
6.10.1.4.2 Response <DebitAuthInqRs>

Tag
<Status>
Type
Usage
Optional
Description
182
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Debit Authorization Identifier.
<DebitAuthId>
<CSPRefId>
Identifier
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Client Change Code. This field is used as a selection criterion. This element will be removed from the DebitAuthInqRs message in IFX 2.0.
<SPRefId>
Identifier
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Closed Enum
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 6.3.26 Identifier
Optional Echoed Optional Echoed Optional Repeating
<SelRangeCurAmt>
<DebitAuthRec>
Debit Authorization Record Aggregate. These records are generated by the server and reflect the current state of the customers Debit Authorizations. The records are filtered by the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
Version 1.7
April 2005
183
6.10.1.5 Debit Authorization Audit

6.10.1.5.1 Request <DebitAuthAudRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited. Valid values: Add, Mod, Can. This field is used as a selection criterion.
<DebitAuthId>
Identifier
Optional Repeating
Debit Authorization Identifier. Assigned by the server at the time the Debit Authorization is first added. Cannot be changed by the client. This field is used as a selection criterion.
6.10.1.5.2 Response <DebitAuthAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
184
April 2005
Version 1.7
Tag
Type
UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Identifier
Usage
Optional Echoed Optional Echoed Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed
Description
<RecCtrlOut>
Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<SelRangeDt>
<Method>
Audit Selection Action. This field is used as a selection criterion. Debit Authorization Identifier. Assigned by the server at the time the Debit Authorization is first added. Cannot be changed by the client. This field is used as a selection criterion.
<DebitAuthId>
<DebitAuthMsgRec>
Optional Repeating
Debit Authorization Message Record Aggregate.
6.10.1.5.2.1
Tag
<CustId>
Debit Authorization Message Record Aggregate <DebitAuthMsgRec>

Type
Usage
Optional
Description
<MsgRecDt>
Optional
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Debit Authorization Add Response Message Aggregate.
<DebitAuthAddRs>
Aggregate see section 6.10.1.1.2 Aggregate see section 6.10.1.2.2 Aggregate see section 6.10.1.8.2 Aggregate see section 6.10.1.7.2 Aggregate see section 6.10.1.3.2
<DebitAuthModRs>
Debit Authorization Modify Response Message Aggregate. Debit Authorization Reversal Response Message Aggregate. Debit Authorization Status Modify Response Message Aggregate. Debit Authorization Cancel Response Message Aggregate.
<DebitAuthRevRs>
<DebitAuthStatusModRs>
<DebitAuthCanRs>
6.10.1.6 Debit Authorization Synchronization

6.10.1.6.1 Request <DebitAuthSyncRq>
Version 1.7
April 2005
185
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<DepAcctId>
<CardAcctId>
6.10.1.6.2 Response <DebitAuthSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
186
April 2005
Version 1.7
Tag
<RecCtrlOut>
Type
Usage
Optional but see Description Required XOR Required XOR Required Echoed
Description
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Deposit Account Identification Aggregate.
<DepAcctId>
<CardAcctId>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Debit Message Record Aggregate.
<DebitAuthMsgRec>
Optional Repeating
6.10.1.7 Debit Authorization Status Modify

6.10.1.7.1 Request <DebitAuthStatusModRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Authorization Identifier. Debit Authorization Status Aggregate.
<DebitAuthId> <DebitAuthStatus>
Required Required
6.10.1.7.2 Response <DebitAuthStatusModRs>
Version 1.7
April 2005
187
Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Aggregate see section 3.2.3.1
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Authorization Identifier. Debit Authorization Status Aggregate.
UUID Aggregate see section 6.3.26.2 Identifier Identifier
6.10.1.8 Debit Authorization Reversal

6.10.1.8.1 Request <DebitAuthRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8
<RevReasonCode>
Open Enum
Required
188
April 2005
Version 1.7
Tag
<Desc> <DebitAuthMsgRqInfo>
Type
C-80 Aggregate
Usage
Optional Required
Description
Description, text describing the reason for the reversal. Debit Authorization Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
6.10.1.8.1.1 Debit Authorization Message Request Information Aggregate <DebitAuthMsgRqInfo>

Tag
<DebitAuthAddRq>
Type
Usage
Description
Debit Authorization Add Request Message Aggregate.
<DebitAuthModRq>
Debit Authorization Modify Request Message Aggregate
<DebitAuthCanRq>
Debit Authorization Cancel Request Message Aggregate
<DebitAuthInqRq>
Debit Authorization Inquiry Request Message Aggregate
<DebitAuthAudRq>
Debit Authorization Audit Request Message Aggregate
<DebitAuthSyncRq>
Debit Authorization Synchronization Message Aggregate
6.10.1.8.2 Response <DebitAuthRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8
Version 1.7
April 2005
189
Tag
<Desc> <DebitAuthMsgRqInfo>
Type
C-80 Aggregate
Usage
Description
Description, text describing the reason for the reversal. Debit Authorization Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
6.10.1.9 Debit Add

6.10.1.9.1 Request <DebitAddRq>
The Debit Add message is used for withdrawals at ATM and bank tellers. It is also used for purchases from a POS device.
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Information Aggregate
<DebitInfo>
Required
6.10.1.9.2 Response <DebitAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
190
April 2005
Version 1.7
Tag
Type
UUID Aggregate see section 3.2.3.1 Aggregate see section 6.3.27 Aggregate see section 6.3.25 Identifier Identifier
Usage
Optional Echoed Optional Echoed Required Echoed Optional but see Description Optional Optional
Description
<DebitInfo>
Debit Information Aggregate
<DebitRec>
Debit Record Aggregate. This aggregate will be required in IFX 2.0. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
6.10.1.10 Debit Modify

6.10.1.10.1 Request <DebitModRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Identifier. Assigned by the server at the time the Debit is first added. Cannot be changed by the client. Debit Info Aggregate
<DebitId> <DebitInfo>
Identifier Aggregate see section 6.3.27 Open Enum
Required Required
<ClientChgCode>
Optional
Version 1.7
April 2005
191
6.10.1.10.2 Response <DebitModRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Aggregate see section 6.3.27 Aggregate see section 6.3.25 Identifier Identifier Open Enum
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<DebitId> <DebitInfo>
Debit Identifier Debit Info Aggregate
<DebitRec>
Debit Record Aggregate
6.10.1.11 Debit Cancel

6.10.1.11.1 Request <DebitCanRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
192
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Identifier. Assigned by the server at the time the Debit is first added. Cannot be changed by the client. Client Change Code. This indicates the reason why an Authorization was cancelled or modified by the client, or why the fulfillment amount differed from the authorized amount. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout
<DebitId> <ClientChgCode>
Required Required
6.10.1.11.2 Response <DebitCanRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Aggregate see section 6.3.25 Open Enum Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Optional
<DebitId> <DebitRec>
Debit Identifier Debit Record Aggregate.
<ClientChgCode> <CSPRefId>
Client Change Code. Customer Service Provider Reference Identifier.
Version 1.7
April 2005
193
Tag
<SPRefId>
Type
Identifier
Usage
Optional
Description
6.10.1.12 Debit Inquiry

6.10.1.12.1 Request <DebitInqRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<DebitId> <CSPRefId>
Optional Repeating Optional Repeating Optional Repeating Optional XOR Optional XOR Optional Repeating Optional
Debit Identifier. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Client Change Code. This field is used as a selection criterion. Selection Range Date Aggregate.
<SPRefId>
Identifier
<DepAcctId>
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
<SelRangeCurAmt>
Optional
<IncToken>
Optional
194
April 2005
Version 1.7
6.10.1.12.2 Response <DebitInqRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Repeating
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Debit Identifier.
<DebitId>
<CSPRefId>
Identifier
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Client Change Code. This field is used as a selection criterion. Selection Range Date Aggregate.
<SPRefId>
Identifier
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Closed Enum Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 6.3.25
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
<SelRangeCurAmt>
<DebitRec>
Debit Record Aggregate. These records are generated by the server and reflect the current state of the customers Debit Authorizations. The records are filtered by the selection criteria specified in the request message.
Version 1.7
April 2005
195
Tag
<Token>
Type
Identifier
Usage
Description
6.10.1.13 Debit Audit

6.10.1.13.1 Request <DebitAudRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<DebitId>
Identifier
Optional Repeating
Debit Identifier. Assigned by the server at the time the Debit is first added. Cannot be changed by the client. This field is used as a selection criterion.
6.10.1.13.2 Response <DebitAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
196
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Identifier
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Action. This field is used as a selection criterion. Debit Identifier. Assigned by the server at the time the Debit is first added. Cannot be changed by the client. This field is used as a selection criterion. Debit Message Record Aggregate.
<DebitId>
<DebitMsgRec>
Aggregate see section 6.10.1.13.2 .1
6.10.1.13.2.1 Debit Message Record Aggregate <DebitMsgRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 6.10.1.9.2 Aggregate see section 6.10.1.10.2 Aggregate see section 6.10.1.18.2 Aggregate see section 6.10.1.17.2 Aggregate see section 6.10.1.11.2
Usage
Optional
Description
<MsgRecDt> <DebitAddRs>
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Debit Add Response Message Aggregate.
<DebitModRs>
Debit Modify Response Message Aggregate.
<DebitRevRs>
Debit Reversal Response Message Aggregate.
<DebitStatusModRs>
Debit Status Modify Response Message Aggregate.
<DebitCanRs>
Debit Cancel Response Message Aggregate.
Version 1.7
April 2005
197
6.10.1.14 Debit Synchronization

6.10.1.14.1 Request <DebitSyncRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<DepAcctId>
<CardAcctId>
6.10.1.14.2 Response <DebitSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
198
April 2005
Version 1.7
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Identifier
Usage
Optional Echoed Optional but see Description Required XOR Required XOR Required Echoed
Description
<RecCtrlOut>
<DepAcctId>
<CardAcctId>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Debit Message Record Aggregate.
<DebitMsgRec>
Optional Repeating
6.10.1.15 Debit Advise

The Debit Advise message is used to notify interested parties that a Debit object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.10.1.15.1 Request <DebitAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Record Aggregate
<DebitRec>
<DebitId>
Debit Identifier.
Version 1.7
April 2005
199
Tag
<DebitStatus>
Type
Usage
Required
Description
6.10.1.15.2 Response <DebitAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Record Aggregate.
<DebitRec>
<DebitId>
Debit Identifier.
<DebitStatus>
6.10.1.16 Debit Auth Advise

The DebitAuth Advise message is used to notify interested parties that a DebitAuth object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.10.1.16.1 Request <DebitAuthAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
200
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. DebitAuth Record Aggregate
<DebitAuthRec>
DebitAuth Identifier.
6.10.1.16.2 Response <DebitAuthAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. DebitAuth Record Aggregate.
<DebitAuthRec>
<DebitAuthId>
DebitAuth Identifier.
<DebitAuthStatus>
Version 1.7
April 2005
201
6.10.1.17 Debit Status Modify

6.10.1.17.1 Request <DebitStatusModRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Identifier. Debit Status Aggregate.
<DebitId> <DebitStatus>
Required Required
6.10.1.17.2 Response <DebitStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Debit Identifier. Debit Status Aggregate.
<DebitId> <DebitStatus>
Required Echoed Required Echoed
202
April 2005
Version 1.7
Tag
Type
Usage
Optional Optional
Description
6.10.1.18 Debit Reversal

6.10.1.18.1 Debit Reversal Request <DebitRevRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Debit Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <DebitMsgRqInfo>
C-80 Aggregate see section 6.10.1.18.1 .1
Optional Required
6.10.1.18.1.1 Debit Message Request Information Aggregate <DebitMsgRqInfo>

Tag
<DebitAddRq>
Type
Aggregate see section 6.10.1.9.1 Aggregate see section 6.10.1.10.1 Aggregate see section 6.10.1.17.1 Aggregate see section 6.10.1.11.1
Usage
Required XOR Required XOR Required XOR Required XOR
Description
Debit Add Request Message Aggregate.
<DebitModRq>
Debit Modify Request Message Aggregate.
<DebitStatusModRq>
Debit Status Modify Request Message Aggregate.
<DebitCanRq>
Debit Cancel Request Message Aggregate.
Version 1.7
April 2005
203
Tag
<DebitInqRq>
Type
Usage
Description
Debit Inquiry Request Message Aggregate.
<DebitAudRq>
Debit Audit Request Message Aggregate.
<DebitSyncRq>
Debit Sync Request Message Aggregate.
6.10.1.18.2 Debit Reversal Response <DebitRevRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate see section 6.10.1.18.1 .1 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <DebitMsgRqInfo>
Reversal reason code. Description, text describing the reason for the reversal. Debit Message Request Information Aggregate. This aggregate contains the message to reverse.
Optional Optional
6.10.2
Credit Messages
The credit messages are used to obtain authorization to perform a credit of money to an account for cash, check or envelope deposits, or merchandise returns or check payments. A credit can either be performed by itself or require a prior authorization. Typically, in an ATM environment a credit is performed with the use of a CreditAdd message. If a problem occurred during the credit fulfillment and either the full amount or only a partial amount of the credit was received then the CreditModRq message can be used to modify the previous CreditAdd. If the client terminal did not receive a response to the CreditAddRq message, the client terminal can use the CreditRevRq message to reverse the previous credit request.
204
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification Credits in the POS environment sometimes require a prior authorization. For these cases the CreditAuthAddRq message is used to get authorization for the amount to be credited to the specified account. At this stage the funds may be posted, but not yet credited to the account. On receipt of a good response, the credit is fulfilled and the client will send a CreditAddRq message. If a link is required between the Credit Authorization and the actual Credit, the CreditAuthId that is supplied by the server in the CreditAuthAdd response can be used. The CreditAuthModRq message can be used to modify a previously added Credit Authorization. If the Credit Authorization needs to be reversed, the CreditAuthRevRq message can be used.
6.10.2.1 Credit Authorization Add

6.10.2.1.1 Request <CreditAuthAddRq>
The Credit Authorization Add message is used to request authorization for a credit.
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Authorization Information Aggregate
<CreditAuthInfo>
Required
6.10.2.1.2 Response <CreditAuthAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
205
Tag
<CreditAuthInfo>
Type
Usage
Description
Credit Authorization Information Aggregate
<CreditAuthRec>
Credit Authorization Record Aggregate.
Optional Optional
6.10.2.2 Credit Authorization Modify

The Credit Authorization Modify message is used to modify the Information previously supplied in a Credit Authorization Add request.
6.10.2.2.1 Request <CreditAuthModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Authorization Identifier. Assigned by the server at the time the Credit Authorization is first added. Cannot be changed by the client. Credit Authorization Information Aggregate
<CreditAuthId>
Identifier
Required
<CreditAuthInfo>
Required
6.10.2.2.2 Response <CreditAuthModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
206
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Aggregate see section 6.3.28.1 Aggregate see section 6.3.28 Identifier Identifier
Usage
Optional
Description
<CreditAuthId> <CreditAuthInfo>
Credit Authorization Identifier Credit Authorization Information Aggregate
<CreditAuthRec>
Credit Authorization Record Aggregate
Optional Optional
6.10.2.3 Credit Authorization Cancel

The client uses this message to cancel a previously added credit authorization.
6.10.2.3.1 Request <CreditAuthCanRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Authorization Identifier. Assigned by the server at the time the Credit Authorization is first added. Cannot be changed by the client.
<CreditAuthId>
Identifier
Required
Version 1.7
April 2005
207
Tag
<ClientChgCode>
Type
Open Enum
Usage
Required
Description
Client Change Code. This indicates the reason why an Authorization was cancelled or modified by the client, or why the fulfillment amount differed from the authorized amount. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout This element will be removed from the CreditAuthCanRq message in IFX 2.0.
6.10.2.3.2 Response <CreditAuthCanRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Open Enum
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Required Echoed
<CreditAuthId> <ClientChgCode>
Credit Authorization Identifier Debit / Credit Client Change Code. This element will be removed from the CreditAuthCanRs message in IFX 2.0. Credit Authorization Record Aggregate.
<CreditAuthRec>
Optional
Optional Optional
6.10.2.4 Credit Authorization Inquiry

6.10.2.4.1 Request <CreditAuthInqRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier.
208
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<CreditAuthId> <CSPRefId>
Optional Repeating Optional Repeating Optional Repeating Optional XOR Optional XOR
Credit Authorization Identifier. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion.
<SPRefId>
Identifier
<DepAcctId>
<CardAcctId>
<ClientChgCode>
Optional Repeating
Client Change Code. This field is used as a selection criterion. This element will be removed from the CreditAuthInqRq message in IFX 2.0.
<SelRangeDt>
Optional
<SelRangeCurAmt>
Optional
<IncToken>
Optional
6.10.2.4.2 Response <CreditAuthInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Version 1.7
April 2005
209
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Credit Authorization Identifier.
<CreditAuthId>
<CSPRefId>
Identifier
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Client Change Code. This field is used as a selection criterion. This element will be removed from the CreditAuthInqRs message in IFX 2.0.
<SPRefId>
Identifier
<DepAcctId>
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
<SelRangeCurAmt>
<CreditAuthRec>
Credit Authorization Record Aggregate. These records are generated by the server and reflect the current state of the customers Credit Authorizations. The records are filtered by the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
210
April 2005
Version 1.7
6.10.2.5 Credit Authorization Audit

6.10.2.5.1 Request <CreditAuthAudRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<CreditAuthId>
Identifier
Optional Repeating
Credit Authorization Identifier. Assigned by the server at the time the Credit Authorization is first added. Cannot be changed by the client. This field is used as a selection criterion.
6.10.2.5.2 Response <CreditAuthAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
211
Tag
Type
UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Identifier
Usage
Optional Echoed Optional Echoed Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed
Description
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Action. This field is used as a selection criterion. Credit Authorization Identifier. Assigned by the server at the time the Credit Authorization is first added. Cannot be changed by the client. This field is used as a selection criterion.
<CreditAuthId>
<CreditAuthMsgRec>
Optional Repeating
Credit Authorization Message Record Aggregate.
6.10.2.5.2.1
Tag
<CustId>
Credit Authorization Message Record Aggregate <CreditAuthMsgRec>

Type
Usage
Optional
Description
<MsgRecDt>
Optional
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Credit Authorization Add Response Message Aggregate. Credit Authorization Modify Response Message Aggregate. Credit Authorization Reversal Response Message Aggregate. Credit Authorization Status Modify Response Message Aggregate. Credit Authorization Cancel Response Message Aggregate.
<CreditAuthAddRs>
<CreditAuthModRs>
<CreditAuthRevRs>
<CreditAuthStatusModRs>
<CreditAuthCanRs>
6.10.2.6 Credit Authorization Sync

6.10.2.6.1 Request <CreditAuthSyncRq>
212
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<DepAcctId>
<CardAcctId>
6.10.2.6.2 Response <CreditAuthSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
213
Tag
<RecCtrlOut>
Type
Usage
Optional but see Description Required XOR Required XOR Required Echoed
Description
<DepAcctId>
<CardAcctId>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Credit Authorization Message Record Aggregate.
<CreditAuthMsgRec>
Optional Repeating
6.10.2.7 Credit Advise

The Credit Advise message is used to notify interested parties that a Credit object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.10.2.7.1 Request <CreditAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Record Aggregate
<CreditRec>
<CreditId>
Credit Identifier.
214
April 2005
Version 1.7
Tag
<CreditStatus>
Type
Usage
Required
Description
6.10.2.7.2 Response <CreditAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Record Aggregate.
<CreditRec>
<CreditId>
Credit Identifier.
<CreditStatus>
6.10.2.8 Credit Authorization Advise

The CreditAuth Advise message is used to notify interested parties that a CreditAuth object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.10.2.8.1 Request <CreditAuthAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Version 1.7
April 2005
215
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. CreditAuth Record Aggregate
<CreditAuthRec>
<CreditAuthId> <DebitStatus>
CreditAuth Identifier.
6.10.2.8.2 Response <CreditAuthAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. CreditAuth Record Aggregate.
<CreditAuthRec>
<CreditAuthId>
CreditAuth Identifier.
<CreditAuthStatus>
216
April 2005
Version 1.7
6.10.2.9 Credit Authorization Reversal

6.10.2.9.1 Request <CreditAuthRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Authorization Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <CreditAuthMsgRqInfo>
C-80 Aggregate
Optional Required
6.10.2.9.1.1 Credit Authorization Message Request Information Aggregate <CreditAuthMsgRqInfo>

Tag
<CreditAuthAddRq>
Type
Usage
Description
Credit Authorization Add Request Aggregate
<CreditAuthModRq>
Credit Authorization Modify Request Aggregate
<CreditAuthCanRq>
Credit Authorization Cancel Request Aggregate
<CreditAuthInqRq>
Credit Authorization Inquiry Request Message Aggregate.
<CreditAuthAudRq>
Credit Authorization Audit Request Aggregate
<CreditAuthSyncRq>
Credit Authorization Synchronization Request Message Aggregate.
Version 1.7
April 2005
217
6.10.2.9.2 Response <CreditAuthRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode>
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Authorization Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<Desc> <CreditAuthMsgRqInfo>
C-80 Aggregate
Optional Optional
6.10.2.10 Credit Authorization Status Modify

6.10.2.10.1 Request <CreditAuthStatusModRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Authorization Identifier.
<CreditAuthId>
Identifier
Required
218
April 2005
Version 1.7
Tag
<CreditAuthStatus>
Type
Usage
Required
Description
Credit Authorization Status Aggregate.
6.10.2.10.2 Response <CreditAuthStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Authorization Identifier. Credit Authorization Status Aggregate.
<CreditAuthId> <CreditAuthStatus>
6.10.2.11 Credit Add

6.10.2.11.1 Request <CreditAddRq>
The Credit Add message is used to add a credit for immediate action or to confirm a previously added credit authorization.
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
Version 1.7
April 2005
219
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Information Aggregate
<CreditInfo>
Required
6.10.2.11.2 Response <CreditAddRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 6.3.29 Aggregate see section 6.3.2 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Message Respone Header aggregate.
Optional Echoed Optional Echoed Required Echoed Optional but see Description Optional Optional
<CreditInfo>
Credit Information Aggregate
<CreditRec>
Credit Record Aggregate. This aggregate will be required in IFX 2.0. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
6.10.2.12 Credit Modify

The Credit Modify message is used to modify the Information previously supplied in a Credit Add request.
6.10.2.12.1
Tag
<RqUID>
Request <CreditModRq>
Type
UUID
Usage
Required
Description
Request Identifier.
220
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Identifier. Assigned by the server at the time the Credit is first added. Cannot be changed by the client. Credit Information Aggregate
Identifier Aggregate see section 6.3.29 Open Enum
Required Required
<ClientChgCode>
Optional
6.10.2.12.2 Response <CreditModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
221
Tag
Type
Identifier Aggregate see section 6.3.29 Aggregate see section 6.3.2 Identifier Identifier Open Enum
Usage
Description
Credit Identifier Credit Information Aggregate
<CreditRec>
Credit Record Aggregate
6.10.2.13 Credit Cancel

The client uses this message to cancel a previously added credit.
6.10.2.13.1 Request <CreditCanRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Identifier. Assigned by the server at the time the Credit is first added. Cannot be changed by the client.
<CreditId>
Identifier
Required
222
April 2005
Version 1.7
Tag
<ClientChgCode>
Type
Open Enum
Usage
Required
Description
Client Change Code. This indicates the reason why a credit was cancelled or modified by the client. Defined Values: None, ConsumerCancelled, TerminalExceptionAmountKnown, TerminalExceptionAmountUnknown, ConsumerExceptionAmountKnown, ConsumerExceptionAmountUnknown, ConsumerDeclined, ConsumerTimeout
6.10.2.13.2 Response <CreditCanRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Open Enum
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Required Echoed Optional
<CreditId> <ClientChgCode>
Credit Identifier Client Change Code.
<CreditRec>
Credit Record Aggregate
Optional Optional
6.10.2.14 Credit Inquiry

6.10.2.14.1
Tag
<RqUID> <MsgRqHdr>
Request <CreditInqRq>
Type
Usage
Required Optional
Description
Version 1.7
April 2005
223
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<CreditId> <CSPRefId>
Optional Repeating Optional Repeating Optional Repeating Optional XOR Optional XOR Optional Repeating Optional
Credit Identifier. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Deposit Account Identification. This field is used as a selection criterion. Card Account Identification. This field is used as a selection criterion. Client Change Code. This field is used as a selection criterion. Selection Range Date Aggregate.
<SPRefId>
Identifier
<DepAcctId>
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
<SelRangeCurAmt>
Optional
<IncToken>
Optional
6.10.2.14.2 Response <CreditInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
224
April 2005
Version 1.7
Tag
<MsgRsHdr>
Type
Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier
Usage
Optional
Description
Optional Echoed Optional Echoed Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Repeating
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Credit Identifier.
<CreditId>
<CSPRefId>
Identifier
<SPRefId>
Identifier
<DepAcctId>
Deposit Account Identification.
<CardAcctId>
Card Account Identification.
<ClientChgCode>
Client Change Code. This field is used as a selection criterion. Selection Range Date Aggregate.
<SelRangeDt>
<SelRangeCurAmt>
<CreditRec>
Credit Record Aggregate. These records are generated by the server and reflect the current state of the customers Credits. The records are filtered by the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
6.10.2.15 Credit Audit

6.10.2.15.1 Request <CreditAudRq>
Version 1.7
April 2005
225
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<CreditId>
Identifier
Optional Repeating
Credit Identifier. Assigned by the server at the time the Credit is first added. Cannot be changed by the client. This field is used as a selection criterion.
6.10.2.15.2 Response <CreditAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
226
April 2005
Version 1.7
Tag
<RecCtrlOut>
Type
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Identifier
Usage
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
Description
<SelRangeDt>
<Method>
Audit Selection Action. This field is used as a selection criterion. Credit Identifier. Assigned by the server at the time the Credit is first added. Cannot be changed by the client. This field is used as a selection criterion. Credit Message Record Aggregate.
<CreditId>
<CreditMsgRec>
6.10.2.15.2.1 Credit Message Record <CreditMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
<MsgRecDt>
Optional
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Credit Add Response Message Aggregate.
<CreditAddRs>
<CreditModRs>
Credit Modify Response Message Aggregate.
<CreditRevRs>
Credit Reversal Response Message Aggregate.
<CreditStatusModRs>
Credit Status Modify Response Message Aggregate.
<CreditCanRs>
Credit Cancel Response Message Aggregate.
6.10.2.16 Credit Sync

6.10.2.16.1 Request <CreditSyncRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
Version 1.7
April 2005
227
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<DepAcctId>
<CardAcctId>
6.10.2.16.2 Response <CreditSyncRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control.
228
April 2005
Version 1.7
Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Identifier
Usage
Required XOR Required XOR Required Echoed
Description
<CardAcctId>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Credit Message Record Aggregate.
<CreditMsgRec>
Optional Repeating
6.10.2.17 Credit Status Modify

6.10.2.17.1 Request <CreditStatusModRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Identifier. Credit Status Aggregate.
<CreditId> <CreditStatus>
Required Required
6.10.2.17.2 Response <CreditStatusModRs>
Version 1.7
April 2005
229
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Credit Identifier. Credit Status Aggregate.
<CreditId> <CreditStatus>
6.10.2.18 Credit Reversal

6.10.2.18.1 Request <CreditRevRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
230
April 2005
Version 1.7
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required
Description
Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Credit Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<Desc> <CreditMsgRqInfo>
C-80 Aggregate see section 6.10.2.18.2 .1
Optional Required
6.10.2.18.2 6.10.2.18.2.1 Credit Message Request Information Aggregate <CreditMsgRqInfo>

Tag
<CreditAddRq>
Type
Aggregate see section 6.10.2.11.1 Aggregate see section 6.10.2.12.1 Aggregate see section 6.10.2.17.1 Aggregate see section 6.10.2.13.1 Aggregate see section 6.10.2.14.1 Aggregate see section 6.10.2.15.1 Aggregate see section 6.10.2.16.1
Usage
Description
Credit Add Request Message Aggregate.
<CreditModRq>
Credit Modify Request Message Aggregate.
<CreditStatusModRq>
Credit Status Modify Request Message Aggregate.
<CreditCanRq>
Credit Cancel Request Message Aggregate.
<CreditInqRq>
Credit Inquiry Request Message Aggregate.
<CreditAudRq>
Credit Audit Request Message Aggregate.
<CreditSyncRq>
Credit Sync Request Message Aggregate.
6.10.2.18.3 Response <CreditRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
231
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate see section 6.10.2.18.2 .1 Identifier Identifier
Usage
Description
<RevReasonCode> <Desc> <CreditMsgRqInfo>
Reversal reason code. Description, text describing the reason for the reversal. Credit Message Request Information Aggregate. This aggregate contains the message to reverse.
Optional Optional
6.11
Deposit Application
This transaction set allows a customer to submit a deposit account application to a financial institution. The decision to create an account on the financial institutions system of permanent record is left to the financial institution. The financial institution may or may not post the account before the account is fundend. The message set does not force a financial institution to create a customer record for the applicant. Typically upon receipt of the application, a financial instituion suspends the application until the funds for the account arrive. The message set replaces the paper form typically filled in by the customer at a branch.
6.11.1
Deposit Application Add
Allows a client to apply for a deposit account. The client sends a <DepAppAddRq> message to request an account be opened in the applicants name. The financial institution replies with a <DepAppAddRs> signifying that the application was received and is scheduled for processing.
6.11.1.1 Request <DepAppAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
232
April 2005
Version 1.7
Tag
<DepAppInfo>
Type
Usage
Required
Description
Deposit Application Information Aggregate.
6.11.1.2 Response <DepAppAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Information Aggregate.
<DepAppInfo>
<DepAppRec>
Deposit Application Record Aggregate.
Optional Optional
6.11.2
Deposit Application Modification
Allows a client to modify a previously added deposit application.
6.11.2.1 Request <DepAppModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Version 1.7
April 2005
233
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Identifier. Assigned by the server at the time the application is first added. Deposit Application Information Aggregate.
Required Required
6.11.2.2 Response <DepAppModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Message Respones Header aggregate.
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Identifier. Deposit Application Information Aggregate.
234
April 2005
Version 1.7
Tag
<DepAppRec>
Type
Usage
Required
Description
Deposit Application Record Aggregate.
Optional Optional
6.11.3
Deposit Application Cancel
Allows a client to cancel a previously added deposit account application.
6.11.3.1 Request <DepAppCanRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Identifier. Assigned by the server at the time the application is first added.
<DepAppId>
Identifier
Required
6.11.3.2 Response <DepAppCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
235
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional Echoed
Description
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Identifier. Assigned by the server at the time the application is first added. Deposit Application Record Aggregate.
<DepAppId> <DepAppRec>
Optional Optional
6.11.4
Deposit Application Inquiry
Allows a client to inquiry on a previously added deposit account application.
6.11.4.1 Request <DepAppInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Identifier. Assigned by the server at the time the application is first added. Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned.
<DepAppId> <IncToken>
Identifier Boolean
236
April 2005
Version 1.7
6.11.4.2 Response <DepAppInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Deposit Application Identifier. Assigned by the server at the time the application is first added. Deposit Application Record Aggregate.
<DepAppId>
Identifier
Required Repeating Echoed Optional Repeating Optional Optional Optional but see Description
<DepAppRec>
Aggregate see section 6.3.31 Identifier Identifier Identifier
<CSPRefId> <SPRefId> <Token>
Customer Service Provider Reference Identifier. Service Provider Reference Identifier. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
6.11.5
Deposit Application Audit
Allows a client to audit a previously added deposit account application.
6.11.5.1 Request <DepAppAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
237
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited. Valid values: Aud, Mod, Can. This field is used as a selection criterion.
<DepAppId>
Identifier
Optional Repeating
Deposit Application Identifier. Assigned by the server at the time the application is first added. This field is used as a selection criterion.
6.11.5.2 Response <DepAppAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
238
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited. Valid values: Aud, Mod, Can. This field is used as a selection criterion.
<DepAppId> <DepAppMsgRec>
Deposit Application Identifier. Assigned by the server at the time the application is first added. Deposit Application Message Record Aggregagte.
6.11.6
6.11.6.1.1 Deposit Application Message Record <DepAppMsgRec>
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 6.11.1.2 Aggregate see section 6.11.2.2 Aggregate see section 6.11.3.2
Usage
Optional
Description
<MsgRecDt> <DepAppAddRs>
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Deposit Application Add Response Message Aggregate.
<DepAppModRs>
Deposit Application Modify Response Message Aggregate.
<DepAppCanRs>
Deposit Application Cancel Response Message Aggregate.
6.11.7
Deposit Application Sync
Allows a client to synchronize with a previously added deposit account application.
Version 1.7
April 2005
239
6.11.7.1 Request <DepAppSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
6.11.7.2 Response <DepAppSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
240
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. If the client sent a token in the request, the server returns a new token based on this audit message.
<RecCtrlOut>
<NewToken>
<DepAppMsgRec>
Optional Repeating
Deposit Application Message Record Aggregagte.
6.12
Bank Account Statement Image Inquiry
A client may use the <BankAcctStmtImgInqRq> message to retrieve an image of a bank account statement for a single statement period or multiple statement periods. This message should be used when a client must receive pre-rendered statement images and can be useful for supporting legacy statement printing host systems. A client may optionally provide a date range to limit the number of bank account statement image records that are returned in the response. Note that the statement is based on the normal cutoff cycles and the date range must return statements that ended (cutoff or cycled) during the specified range. The client may specify a date range that results in no statement, because there were no statement end cutoffs within the range.
The client may specify a delivery method picked from those supported in the Service Profile.
Note:
6.12.1.1 Request <BankAcctStmtImgInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Version 1.7
April 2005
241
Tag
<RecCtrlIn>
Type
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.1 Boolean
Usage
Optional
Description
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<SelRangeDt>
<IncDetail>
Optional
Include Detail Indicator. If True, the response should include the detail statement information. If False or omitted, the detail information should not be included. Statement type Defined values: Partial, Legal
<StmtType>
Open Enum
Optional
<DeliveryMethod>
Open Enum
Delivery Method. Default is Channel. Value must be supported in Service Profile. Delivery Media Defined values: CD, Diskette, DVD, Paper. Default value is Paper.
<DeliveryMedia>
Open Enum
Note: <DeliveryMedia> is only valid if <DeliveryMethod> is a manual process. (i.e. Post, UPS)
<ContactInfo> Aggregate see section 3.2.3.9 Optional Contact Information Aggregate.
6.12.1.2 Response <BankAcctStmtImgInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
242
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Deposit Account Identification Aggregate.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 Aggregate see section 3.2.10.1 Boolean Open Enum Open Enum Open Enum
Optional but see Description Optional XOR Echoed Optional XOR Echoed Optional XOR Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating Optional Optional
<DepAcctId>
<CardAcctId>
<LoanAcctId>
<SelRangeDt>
<IncDetail> <StmtType> <DeliveryMethod> <DeliveryMedia>
Include Detail Indicator. Statement type Delivery Method. Delivery Media
<ContactInfo>
Aggregate see section 3.2.3.9 Aggregate see section 6.12.1.2.1 Identifier Identifier
<BankAcctStmtImgInqRec>
Bank Account Statement Image Record Aggregate.
6.12.1.2.1 Bank Account Statement Image Record Aggregate <BankAcctStmtImgInqRec>

Tag
<StartDt> <EndDt> <StmtImg> <ImageURL>
Type
DateTime DateTime Binary URL
Usage
Required Required Optional OR Optional OR
Description
Selection Start Date for this statement. End for this statement. Statement Image. URL for retrieving a bank-rendered statement copy.
Version 1.7
April 2005
243
6.12.2
Bank Account Statement Image Reversal
The Bank Account Statement Image Reversal Message allows a client to reverse a previous Bank Account Statement Image Inquiry request.
Note
In case subsequent messages have to be sent, see 3.2.11.2 Records Control, the first Bank Account Statement Image Inquiry Request Message Aggregate have to be included in the <BankAcctStmtImgInqRq> tag. All subsequent messages will be reversed automatically.
6.12.2.1 Bank Account Statement Image Reversal Request <BankAcctStmtImgRevRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Object Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode>
Open Enum
Required
<Desc> <BankAcctStmtImgMsgRqInfo>
C-80 Aggregate
Optional Required
6.12.2.1.1 Bank Account Statement Image Message Request Information Aggregate <BankAcctStmtImgMsgRqInfo>
Tag
<BankAcctStmtImgInqRq>
Type
Usage
Optional
Description
Bank Account Statement Image Inquiry Request Message Aggregate.
244
April 2005
Version 1.7
6.12.2.2 Bank Account Statement Image Reversal Response <BankAcctStmtImgRevRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Optional Echoed Required Echoed Optional Optional
<RevReasonCode> <Desc> <BankAcctStmtImgMsgRqInfo> <CSPRefId> <SPRefId>
Reversal reason code. Description, text describing the reason for the reversal. Object Message Request Information Aggregate. This aggregate contains the message to reverse. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
6.13
Payment Enclosed
Allows a client to make a payment towards outstanding debts, such as loans, made by deposit enclosed in an envelope (along with the payment coupon). The <PmtEnclAddRq> creates a new Payment Enclosed transaction. In case of a Payment Enclosed transaction, customers deposit or credit card accounts are NOT involved in the payment process (its an offline payment). The payment is simply made by enclosing the check/money order/cash with the payment invoice/statement in an envelope deposited in the ATMs deposit slot. However, the customer needs to enter the amount of the payment when asked by the ATM, which is logged at the ATM (journal) and with the transaction at the acquiring/issuing server/host. This payment is subject to verification by the bank, later (and in case of a dispute, a dispute resolution is performed). The client sends a <PmtEnclAddRq> message to request a Payment Enclosed. The server replies with a <PmtEnclAddRs> signifying that the Payment Enclosed request was received and is subject to verification by the financial institution.
6.13.1
Payment Enclosed Add
The Payment Enclosed Add message is used by a client to request a payment enclosed transaction.
Version 1.7
April 2005
245
6.13.1.1 Request <PmtEnclAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Information aggregate.
<CustId>
Optional
<PmtEnclInfo>
Required
6.13.1.2 Response <PmtEnclAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Information aggregate.
<CustId>
Optional Echoed
<PmtEnclInfo>
<PmtEnclRec>
Payment Enclosed Record Aggregate.
246
April 2005
Version 1.7
Tag
Type
Usage
Optional Optional
Description
6.13.2
Payment Enclosed Modify
The Payment Enclosed Modify message is used to modify the information previously supplied in a Payment Enclosed Add request.
6.13.2.1 Request <PmtEnclModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Identifier. Assigned by the server at the time the Payment Enclosed is first added. Cannot be changed by the client. Payment Enclosed Information aggregate.
<CustId>
Optional
<PmtEnclId>
Identifier
Required
<PmtEnclInfo>
Required
6.13.2.2 Response <PmtEnclModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
247
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional Echoed
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Identifier. Payment Enclosed Information aggregate.
<CustId>
Optional Echoed
<PmtEnclId> <PmtEnclInfo>
Identifier Aggregate see section 6.3.32 Aggregate see section 6.3.32.2 Identifier Identifier
<PmtEnclRec>
Payment Enclosed Record Aggregate.
Optional Optional
6.13.3
Payment Enclosed Inquiry
The Payment Enclosed Inquiry message allows a client to get a list of previous Payment Enclosed objects, optionally, based on specified selection criteria.
6.13.3.1 Request <PmtEnclInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<PmtEnclId>
Optional Repeating
Payment Enclosed Identifier(s).
248
April 2005
Version 1.7
Tag
<CSPRefId>
Type
Identifier
Usage
Optional Repeating Optional Repeating Optional XOR Optional XOR Optional
Description
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Selection Range Payment Processing Date Aggregate.
<SPRefId>
Identifier
<SelRangePrcDt>
<SelRangeDueDt>
Selection Range Payment Due Date Aggregate.
<SelRangeCurAmt>
6.13.3.2 Response <PmtEnclInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Payment Enclosed Identifier(s).
<CustId>
Optional Echoed
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed
<PmtEnclId>
<CSPRefId>
Identifier
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion.
<SPRefId>
Identifier
Version 1.7
April 2005
249
Tag
<SelRangePrcDt>
Type
Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 6.3.32.2
Usage
Optional XOR Echoed Optional XOR Echoed Optional Echoed Optional Repeating
Description
Selection Range Payment Processing Date Aggregate.
<SelRangeDueDt>
Selection Range Payment Due Date Aggregate.
<SelRangeCurAmt>
<PmtEnclRec>
Payment Enclosed Record Aggregate. These records are generated by the server and reflect the current state of the customers Payment Enclosed transactions. The records are filtered by the selection criteria specified in the request message.
6.13.4
Payment Enclosed Cancel
The Payment Enclosed Cancel message is used to cancel a previously added Payment Enclosed Add request.
6.13.4.1 Request <PmtEnclCanRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Identifier. Assigned by the server at the time the Payment Enclosed is first added. Cannot be changed by the client.
<CustId>
Optional
<PmtEnclId>
Identifier
Required
6.13.4.2 Response <PmtEnclCanRs>

Tag
<Status>
Type
Usage
Optional
Description
250
April 2005
Version 1.7
Tag
<RqUID>
Type
UUID
Usage
Description
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Identifier. Payment Enclosed Record Aggregate. This aggregate is provided in cases where the server keeps the Payment Enclosed records on the server even after receiving a cancellation request. This may occur if the cancellation is not immediate, or if the server maintains the record with a status of Cancelled. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<CustId>
Optional Echoed
<PmtEnclId> <PmtEnclRec>
Optional Optional
6.13.5
Payment Enclosed Audit
The Payment Enclosed Audit message allows to play back the Payment Enclosed messages associated with the current customer since some past point in time.
6.13.5.1 Request <PmtEnclAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
251
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited. Valid values: Add, Mod, Can, Rev. This field is used as a selection criterion.
<PmtEnclId>
Identifier
Optional Repeating
Payment Enclosed Identifier(s). This field is used as a selection criterion.
6.13.5.2 Response <PmtEnclAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<CustId>
Optional Echoed
<RecCtrlOut>
<SelRangeDt>
252
April 2005
Version 1.7
Tag
<Method>
Type
Closed Enum
Usage
Description
Audit Selection Action. Used to identify actions associated with the object that is being audited. Valid values: Add, Mod, Can, Rev. This field is used as a selection criterion.
<PmtEnclId>
Identifier
Optional Repeating Echoed Optional Repeating
Payment Enclosed Identifier(s). This field is used as a selection criterion. Payment Enclosed Message Record Aggregate.
<PmtEnclMsgRec>
6.13.5.2.1 Payment Enclosed Message Record Aggregate <PmtEnclMsgRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 6.13.1.2 Aggregate see section 6.13.2.2 Aggregate see section 6.13.4.2 Aggregate see section 6.13.8.2
Usage
Optional
Description
<MsgRecDt> <PmtEnclAddRs>
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Payment Enclosed Add Response Message Aggregate.
<PmtEnclModRs>
Payment Enclosed Modify Response Message Aggregate.
<PmtEnclCanRs>
Payment Enclosed Cancel Response Message Aggregate.
<PmtEnclRevRs>
Payment Enclosed Reversal Response Message Aggregate.
6.13.6
Tag
<RqUID>
Payment Enclosed Status Modify

Type
6.13.6.1 Request <PmtEnclStatusModRq>

Usage
Required Optional
Description
<MsgRqHdr>
<AsyncRqUID>
Optional
Version 1.7
April 2005
253
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Identifier. Payment Enclosed Status Aggregate.
<PmtEnclId> <PmtEnclStatus>
Required Required
254
April 2005
Version 1.7
6.13.6.2 Response <PmtEnclStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Enclosed Identifier. Payment Enclosed Status Aggregate.
6.13.7
Payment Enclosed Advise
The PmtEncl Advise message is used to notify interested parties that a PmtEncl object was created or modified. This message will be used to notify an account owning organization of transactions authorized on their behalf.
6.13.7.1 Request <PmtEnclAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Version 1.7
April 2005
255
Tag
<PmtEnclRec>
Type
Aggregate see section 6.3.32.2 Identifier Aggregate see section 6.3.32.3
Usage
Description
PmtEncl Record Aggregate
PmtEncl Identifier.
6.13.7.2 Response <PmtEnclAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtEncl Record Aggregate.
<PmtEnclRec>
<PmtEnclId>
PmtEncl Identifier.
<PmtEnclStatus>
6.13.8
Payment Enclosed Reversal
The Payment Enclosed Reversal message allows a client to reverse a previously authorized Payment Enclosed Add transaction request. The Payment Enclosed message is introduced to address issues related to delays in receiving Payment Enclosed Add transaction responses and also to help address situations where the Consumer either cancels or walks-away from the ATM/POS terminal before their transactions are complete. In general, the Payment Enclosed Reversal message provides the capability to undo a previous Payment Enclosed Add request in an online environment.
256
April 2005
Version 1.7
6.13.8.1 Request <PmtEnclRevRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Payment Enclosed Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<CustId>
Optional
<RevReasonCode>
Open Enum
Required
<Desc> <PmtEnclMsgRqInfo>
Optional Required
6.13.8.1.1 Payment Enclosed Message Request Information Aggregate <PmtEnclMsgRqInfo>

Tag
<PmtEnclAddRq>
Type
Usage
Required XOR
Description
Payment Enclosed Add Request Message Aggregate.
<PmtEnclModRq>
Required XOR
Payment Enclosed Modify Request Message Aggregate. Payment Enclosed Inquiry Request Message Aggregate. Payment Enclosed Cancel Request Message Aggregate. Payment Enclosed Status Modification Request Message Aggregate. Payment Enclosed Audit Request Message Aggregate.
<PmtEnclInqRq>
Required XOR
<PmtEnclCanRq>
Required XOR
<PmtEnclStatusModRq>
Required XOR
<PmtEnclAudRq>
Required XOR
Version 1.7
April 2005
257
6.13.8.2 Response <PmtEnclRevRs>

Tag
<RqUID>
Type
UUID
Usage
Description
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Please see the enumerated items in section 3.1.8 Description, text describing the reason for the reversal. Payment Enclosed Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<CustId>
Optional Echoed
<RevReasonCode>
Open Enum
Required Echoed Optional Echoed Required Echoed
<Desc> <PmtEnclMsgRqInfo>
Optional Optional
6.14
6.14.1
Check Issue
Check Issue Add
A commercial customer originates a check issue add message to provide Positive Pay information to a financial institution. This message is generated when a check is printed. The message instructs the financial institution to honor the check if the information on the presented check matches the information in the <ChkIssueInfo> aggregate. If the information does not match, the financial institution should generate a <ChkIssueModRq> to the commercial customer notifying them that the check was not honored. If the commercial customer wishes the financial institution to pay the check anyway, the commercial customer sends a <ChkIssueStatusModRq> with a <ChkIssueStatusCode> of Pay.
258
April 2005
Version 1.7
6.14.1.1 Request <ChkIssueAddRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional Echoed Optional
Description
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Information Aggregate
<ChkIssueInfo>
Required
6.14.1.2 Response <ChkIssueAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Information Aggregate
<ChkIssueInfo>
Required Echoed
Version 1.7
April 2005
259
Tag
<ChkIssueRec>
Type
Usage
Required
Description
Check Issue Record Aggregate
Optional Optional
6.14.2
Check Issue Modification
A financial institution originates a check issue modification message to provide to a commercial customer information as to a check that was presented and the information as provided in the <ChkIssueAddRq> did not match. This would be considered an exception item. This message, <ChkIssueModRq> is generated when a check is not honored. The commercial client responds with a <ChkIssueModRs> noting in the <ChkIssueStatusCode> of the <ChkIssueStatus> as to what action the FI should take on this exception item, i.e., Pay or Rejected. The <ChkIssueModRq> may also be sent by the commercial client to modify any information originally submitted in the <ChkIssueAddRq>. This would allow the FI to update the system of record.
6.14.2.1 Request <ChkIssueModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Identifier. If a Check Issue Id was not assigned due to a check not included in the <ChkIssueAddRq>, i.e., fraudulant check being presented, a Check Issue Id should be created upon the issuance of the <ChkIssueModRq> by the FI. Check Issue Information Aggregate
<ChkIssueId>
Required but see Description
<ChkIssueInfo>
Required
260
April 2005
Version 1.7
6.14.2.2 Response <ChkIssueModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Identifier.
<ChkIssueId>
Aggregate see section 6.3.34.4 Aggregate see section 6.3.34 Aggregate see section 6.3.34.3 Identifier Identifier
Optional Echoed Required Echoed Required
<ChkIssueInfo>
Check Issue Information Aggregate
<ChkIssueRec>
Optional Optional
6.14.3
Check Issue Status Modification
The check issue modification status message modifies the status of an issued check. A financial institution sets the status code to pending when it receives a check issue add message, and the check has not been presented. The financial institution can change the status to Paid when honoring a check, or Rejected if the presented check information does not match the check information on file. A commercial customer can override a rejected check by sending a status modification message with the status code set to Pay.
6.14.3.1 Request <ChkIssueStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier.
Version 1.7
April 2005
261
Tag
<MsgRqHdr>
Type
Usage
Description
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Identifier
<ChkIssueId>
Required
<ChkIssueStatus>
Required
6.14.3.2 Response <ChkIssueStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
<ChkIssueId>
<ChkIssueStatus>
262
April 2005
Version 1.7
Tag
<ChkIssueRec>
Type
Usage
Required
Description
6.14.4
Check Issue Delete
A commercial customer can request that a previously sent issued check be removed from the financial institutions system of record by sending a check issue deletion request.
6.14.4.1 Request <ChkIssueDelRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<AsyncRqUID>
<CustId>
Optional
<ChkIssueId>
Required Repeating
6.14.4.2 Response <ChkIssueDelRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
263
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<ChkIssueId>
Required Repeating Echoed Required
<ChkIssueRec>
Optional Optional
6.14.5
Check Issue Inquiry
A commercial customer initiates the Check Issue Inquiry message by sending a <ChkIssueInqRq> message.
6.14.5.1 Request <ChkIssueInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
<CustId>
Optional
<RecCtrlIn>
Optional
<ChkIssueId>
Optional Repeating
Check Issue Identifier. Assigned by the server at the time the Check Issue is first added. Cannot be modified by the client. This field is used as a selection criterion.
<DepAcctId>
Optional
Deposit Account Aggregate. Source account for check issue. This field is used as a selection criterion.
264
April 2005
Version 1.7
Tag
<ChkNum> <ChkIssueStatusCode>
Type
NC-12 Closed Enum
Usage
Description
Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. Check Issue Status Code. This identifies the check issue processing status. Valid values: Pending, Paid, Rejected, Pay, NoPay This field is used as a selection criterion.
<SelRangeDueDt>
Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Identifier
Optional
<SelRangePaidDt>
Optional
Selection Range PaidDate Aggregate.
<SelRangeCurAmt>
Optional
<CSPRefId>
Optional Repeating
Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a transaction corresponding to a confirmation number that was returned to the client when the transaction was added or modified. When a transaction has been modified, only the <CSPRefId> received in the most recent PMPMODRS is valid. The use of an <CSPRefId> from an earlier response is likely to result in a transaction not found response. Service Provider Reference Identifier. Same usage as <CSPRefId>. Include Token. If True, a <Token> must be included in the response, if the Service Profile indicates support for transaction synchronization, to set a base for future synchronization messages. If False or omitted, the <Token> may be omitted in the response. Include History. If True, the response should include issuances that have already occurred, as well as those scheduled to occur.
<SPRefId> <IncToken>
Identifier Boolean
<IncHistory>
Boolean
Optional
6.14.5.2 Response <ChkIssueInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
265
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Check Issue Identifier. Assigned by the server at the time the Check Issue is first added. Cannot be modified by the client. This field is used as a selection criterion.
<RecCtrlOut>
<ChkIssueId>
<DepAcctId>
Aggregate see section 3.2.7.2.2 NC-12
Optional Echoed
Deposit Account Aggregate. Source account for check issue. This field is used as a selection criterion. Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. Check Issue Status Code. This identifies the check issue processing status. Valid values: Pending, Paid, Rejected, Pay, NoPay This field is used as a selection criterion.
<ChkNum>
<ChkIssueStatusCode>
Closed Enum
<SelRangeDueDt>
Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Identifier
Optional Echoed Optional Echoed Optional Echoed Optional Repeating Echoed
<SelRangePaidDt>
Selection Range PaidDate Aggregate.
<SelRangeCurAmt>
<CSPRefId>
Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a transaction corresponding to a confirmation number that was returned to the client when the transaction was added or modified. When a transaction has been modified, only the <CSPRefId> received in the most recent PMPMODRS is valid. The use of an <CSPRefId> from an earlier response is likely to result in a transaction not found response. Service Provider Reference Identifier. Same usage as <CSPRefId>. Include Token. If True, a <Token> must be included in the response, if the Service Profile indicates support for transaction synchronization, to set a base for future synchronization messages. If False or omitted, the <Token> may be omitted in the response. Include History. If True, the response should include issuances that have already occurred, as well as those scheduled to occur.
<SPRefId>
Identifier
Optional Repeating Echoed Optional Echoed
<IncToken>
Boolean
<IncHistory>
Boolean
Optional Echoed
266
April 2005
Version 1.7
Tag
<ChkIssueRec>
Type
Usage
Optional Repeating Optional but see Description
Description
Check Issue Record Aggregate. One record is returned for each of the customers checks that meets the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
6.14.6
Check Issue Audit
A commercial customer originates a check issue audit request to obtain all changes related to a particular issued check.
6.14.6.1 Request <ChkIssueAudRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<AsyncRqUID>
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.10.1 Aggregate see section 6.3.16
Optional
<DepAcctId>
Required
<SelRangeDt>
Optional
Selection Range Date Aggregate. Date of the Check Issue request. Selection RangeCheck Number Aggregate.
<ChkRange>
Optional
Version 1.7
April 2005
267
6.14.6.2 Response <ChkIssueAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.10.1 Aggregate see section 6.3.16 Aggregate see section 6.14.7.2.1
Optional but see Description Required Echoed Optional Echoed Optional Echoed Optional Repeating
<DepAcctId>
<SelRangeDt>
Check Issue Audit Selection Criteria Aggregate.
<ChkRange>
<ChkIssueMsgRec>
Check Issue Message Record Aggregate.
6.14.7
Tag
<RqUID>
Check Issue Sync

Type
6.14.7.1 Request <ChkIssueSyncRq>

Usage
Description
<MsgRqHdr>
<AsyncRqUID>
268
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<DepAcctId>
Required
<Token>
Required
6.14.7.2 Response <ChkIssueSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Optional but see Description Required Echoed Required Echoed
<DepAcctId>
<Token>
Check Issue Synchronization Aggregate.
Version 1.7
April 2005
269
Tag
<NewToken>
Type
Identifier
Usage
Required
Description
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Check Issue Message Record Aggregate.
<ChkIssueMsgRec>
Optional Repeating
6.14.7.2.1 Check Issue Message Record Aggregate <ChkIssueMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date/time at which the audit record was stored/created by the service provider. Check Issue Add Response Message Aggregate.
<MsgRecDt>
Timestamp
Optional
<ChkIssueAddRs>
<ChkIssueModRs>
Check Issue Modify Response Message Aggregate.
<ChkIssueStatusModRs>
Check Issue Status Modify Response Message Aggregate. Check Issue Delete Response Message Aggregate.
<ChkIssueDelRs>
6.14.8
Check Issue Advise
6.14.8.1 Request <CheckIssueAdviseRq>

A commercial customer can request the status of checks provided in an issue file by a series of selection criteria including check number, date range, amount range or check status.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
270
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Record Aggregate
<ChkIssueRec>
Required
6.14.8.2 Response <CheckIssueAdviseRs>

The service provider provides the requested status of checks provided in an issue file by a series of selection criteria including check number, date range, amount range or check status.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<CustId>
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Issue Record Aggregate
<ChkIssueRec>
<CSPRefId>
Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a transaction corresponding to a confirmation number that was returned to the client when the transaction was added or modified. When a transaction has been modified, only the <CSPRefId> received in the most recent PMPMODRS is valid. The use of an <CSPRefId> from an earlier response is likely to result in a transaction not found response. Service Provider Reference Identifier. Same usage as <CSPRefId>.
<SPRefId>
Identifier
Optional Repeating
6.15
6.15.1
Bank Service Checksum

Bank Service Checksum Add
The Bank Service Checksum Add message allows a client to provide a Bank Service Checksum record against which the server can verify receipt of a batch of issued transactions, where the control data such as sum amount
Version 1.7
April 2005
271
Interactive Financial Exchange Business Message Specification and count are provided to the server. The Bank Service Checksum Add message can be sent together with or separate from the associated messages within a bank service to facilitate both cases where the control record is sent via the same or different routes due to authorization and segregation reasons.
6.15.1.1 Request <BankSvcChkSumAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Request Identifier. Identifier for the file generated by the client. This must be the same as the <RqUID> of <BankSvcRq>, so that the server can match it to the <BankSvcRq> containing the associated issuances. Bank Service Checksum Information Aggregate. Provides the BankSvcChkSum information used by the server to validate a bank service batch.
<SvcRqUID>
UUID
Optional
<BankSvcChkSumInfo>
Required
6.15.1.2 Response <BankSvcChkSumAddRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed
Asynchronous Request Identifier. Customer Identifier.
<SvcRqUID>
Service Request Identifier.
272
April 2005
Version 1.7
Tag
<BankSvcChkSumInfo>
Type
Usage
Description
Bank Service Checksum Information
<BankSvcChkSumRec>
Bank Service Checksum Record Aggregate.
Optional Optional
6.15.2
Bank Service Checksum Modify
6.15.2.1 Request <BankSvcChkSumModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Service Request Identifier. Identifier for the file generated by the client. This must be the same as the <RqUID> of <BankSvcRq>, so that the server can match it to the <BankSvcRq> containing the associated issuances. Bank Service Checksum Control Identifier. Assigned by the server at the time the Bank Service Checksum Control is first added. Cannot be modified by the client. Bank Service Checksum Information Aggregate. Provides the checksums used by the server to validate a bank service batch.
<SvcRqUID>
UUID
Optional
<BankSvcChkSumId>
Identifier
Required
<BankSvcChkSumInfo>
Required
6.15.2.2 Response <BankSvcChkSumModRs>

Tag
<Status>
Type
Usage
Optional
Description
Version 1.7
April 2005
273
Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Aggregate see section 6.3.1.1 Aggregate see section 6.3.1 Identifier Identifier
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed Required Echoed Required
Asynchronous Request Identifier. Customer Identifier Aggregate.
<SvcRqUID> <BankSvcChkSumId> <BankSvcChkSumInfo>
Service Request Identifier. Bank Service Checksum Control Identifier. Bank Service Checksum Information.
<BankSvcChkSumRec>
Optional Optional
6.15.3
Bank Service Checksum Status Modify
6.15.3.1 Request <BankSvcChkSumStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
<CustId>
Optional
274
April 2005
Version 1.7
Tag
<SvcRqUID>
Type
UUID
Usage
Optional
Description
Service Request Identifier. Identifier for the file generated by the client. This must be the same as the <RqUID> of <BankSvcRq>, so that the server can match it to the <BankSvcRq> containing the associated issuances. Bank Service Checksum Control Identifier. Assigned by the server at the time the BankSvcChkSum Control is first added. Cannot be modified by the client. Bank Service Checksum Status Aggregate.
<BankSvcChkSumId>
Identifier
Required
<BankSvcChkSumStatus>
Required
6.15.3.2 Response <BankSvcChkSumStatusModRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Aggregate see section 6.3.1.2 Aggregate see section 6.3.1 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<SvcRqUID> <BankSvcChkSumId> <BankSvcChkSumStatus>
Service Request Identifier. Bank Service Checksum Control Identifier. Bank Service Checksum Status Aggregate.
<BankSvcChkSumRec>
Optional Optional
6.15.4
Bank Service Checksum Delete
Version 1.7
April 2005
275
6.15.4.1 Request <BankSvcChkSumDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Request Identifier. Optionally sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header Aggregate.
<MsgRqHdr>
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Bank Service Request Identifier. Identifier for the file generated by the client. This must be the same as the <RqUID> of <BankSvcRq>, so that the server can match it to the <BankSvcRq> containing the associated issuances. Bank Service Checksum Control Identifier. Assigned by the server at the time the Bank Service Checksum Control is first added. Cannot be modified by the client.
<SvcRqUID>
UUID
Optional
<BankSvcChkSumId>
Identifier
Required
6.15.4.2 Response <BankSvcChkSumDelRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed
<SvcRqUID> <BankSvcChkSumId>
Bank Service Request Identifier. Bank Service Checksum Control Identifier.
276
April 2005
Version 1.7
Tag
<BankSvcChkSumRec>
Type
Usage
Required
Description
Optional Optional
6.15.5
Bank Service Checksum Inquiry
6.15.5.1 Request <BankSvcChkSumInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Bank Service Request Identifier. Identifier for the file generated by the client. This must be the same as the <RqUID> of <BankSvcRq>, so that the server can match it to the <BankSvcRq> containing the associated issuances. This is used as a selection criterion.
<SvcRqUID>
UUID
Optional
<BankSvcChkSumId>
Identifier
Required
Bank Service Checksum Identifier. Assigned by the server at the time the bank service check issue is first added. Cannot be modified by the client. This is used as a selection criterion.
<BankSvcChkSumStatusCode>
Open Enum
Required
Bank Service Checksum Status Code. Defined values: Pending, Posted, Refused, Rejected, Returned, DelPend, Deleted This is used as a selection criterion.
Version 1.7
April 2005
277
6.15.5.2 Response <BankSvcChkSumInqRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Open Enum Aggregate see section 6.3.1 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<SvcRqUID> <BankSvcChkSumId> <BankSvcChkSumStatusCode> <BankSvcChkSumRec>
Bank Service Request Identifier. Bank Service Checksum Identifier. Bank Service Checksum Status Code. Bank Service Checksum Record Aggregate.
Optional Optional
6.15.6
Bank Service Checksum Audit
6.15.6.1 Request <BankSvcChkSumAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
278
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
Selection Range Date Aggregate. This is used as a selection criterion.
<Method>
Optional Repeating
Method. Valid Values: Add, Mod, Can This is used as a selection criterion.
<BankSvcChkSumId>
Identifier
Optional Repeating
Bank Service Checksum Control Identifier. This is used as a selection criterion.
6.15.6.2 Response <BankSvcChkSumAudRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<SelRangeDt>
Aggregate see section 3.2.10.1 Closed Enum Identifier
Optional Echoed Optional Repeating Echoed Optional Echoed
<Method>
Method.
<BankSvcChkSumId>
Bank Service Checksum Identifier.
Version 1.7
April 2005
279
Tag
<BankSvcChkSumMsgRec>
Type
Usage
Description
Bank Service Checksum Message Record Aggregate. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
6.15.6.2.1 Bank Service Checksum Message Record <BankSvcChkSumMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created. Bank Service Checksum Add Response Message Aggregate. Bank Service Checksum Modify Response Message Aggregate. Bank Service Checksum Status Modify Response Message Aggregate. Bank Service Checksum Delete Response Message Aggregate.
<MsgRecDt> <BankSvcChkSumAddRs>
<BankSvcChkSumModRs>
<BankSvcChkSumStatusModRs>
<BankSvcChkSumDelRs>
6.15.7
Bank Service Checksum Synchronization
6.15.7.1 Request <BankSvcChkSumSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
<AsyncRqUID>
280
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<Token>
Required
6.15.7.2 Response <BankSvcChkSumSyncRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional
<RecCtrlOut>
Records Control Output Aggregate.
<Token> <NewToken>
Token. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Bank Service Checksum Message Record Aggregate. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<BankSvcChkSumMsgRec>
Version 1.7
April 2005
281
6.16
6.16.1
Check Accept
Check Accept Add
The client may send a check to a financial institution for collection using the check accept add message to verify the check is good. If check authorization is not going to be performed then check (s) can be sent on the other messages that support checks such as the Credit messages. Typically if the status code indicates an error then the check is returned to the customer otherwise the check is retained. These messages support either client or server determination of what level of truncation and guarantee the merchant or check acceptor requires.
6.16.1.1 Request <ChkAcceptAddRq>

The Check Accept Add message is used to request payment for a check.
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Information Aggregate
<ChkAcceptInfo>
Required
6.16.1.2 Response <ChkAcceptAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
282
April 2005
Version 1.7
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Aggregate see section 6.3.35.2 Aggregate see section 6.3.35 Identifier Identifier
Usage
Optional Echoed Required Echoed Required
Description
<ChkAcceptInfo>
Check Accept Information Aggregate
<ChkAcceptRec>
Check Accept Record Aggregate.
Optional Optional
6.16.2
Check Accept Modify
The Check Accept Modify message is used to modify the Information previously supplied in a Check Accept Add request.
6.16.2.1 Request <ChkAcceptModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Accept Identifier. Assigned by the server at the time the Check is first added. Cannot be changed by the client. Check Accept Information Aggregate
<ChkAcceptId> <ChkAcceptInfo>
Required Required
6.16.2.2 Response <ChkAcceptModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
Version 1.7
April 2005
283
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Identifier Aggregate see section 6.3.35.2 Aggregate see section 6.3.35 Identifier Identifier
Usage
Description
<MsgRsHdr>
<ChkAcceptId> <ChkAcceptInfo>
Check Accept Identifier Check Accept Information Aggregate
<ChkAcceptRec>
Check Accept Record Aggregate
Optional Optional
6.16.2.3
6.16.3
Check Accept Inquiry
This message allows a client to retrieve Check Accept Records.
6.16.3.1 Request <ChkAcceptInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<DebitId>
Optional Repeating
Debit Identifier.
284
April 2005
Version 1.7
Tag
<CSPRefId>
Type
Identifier
Usage
Optional Repeating Optional Repeating Optional XOR Optional XOR Optional Repeating Optional
Description
<SPRefId>
Identifier
<DepAcctId>
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 6.3.38 Boolean
<SelRangeCurAmt>
Optional
<SelRangeChkNum>
Optional
Selection Range Check Number. This field is used as a selection criterion. Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned.
<IncToken>
Optional
6.16.3.2 6.16.3.3 Response <ChkAcceptInqRs>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate.
<RecCtrlOut>
Optional
<DebitId>
Optional Repeating
Debit Identifier.
Version 1.7
April 2005
285
Tag
<CSPRefId>
Type
Identifier
Usage
Optional Repeating Optional Repeating Optional XOR Optional XOR Optional Repeating Optional
Description
<SPRefId>
Identifier
<DepAcctId>
<CardAcctId>
<ClientChgCode>
<SelRangeDt>
<SelRangeCurAmt>
Optional
<ChkAcceptRec>
Optional Repeating
Check Accept Record Aggregate. These records are generated by the server and reflect the current state of the customers Check Authorizations. The records are filtered by the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
6.16.3.4
6.16.4
Check Accept Cancel
This message allows a client to cancel a previous check accept.
6.16.4.1 Request <ChkAcceptCanRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
286
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Accept Identifier.
<ChkAcceptId>
Identifier
Required
6.16.4.2 Response <ChkAcceptCanRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Accept Identifier. Check Accept Record Aggregate.
<CustId>
Optional Echoed
<ChkAcceptId> <ChkAcceptRec>
Optional Optional
6.16.5
Check Accept Audit
Allows playing back the check accept messages associated with the customer since some past point in time.
6.16.5.1 Request <ChkAcceptAudRq>
Version 1.7
April 2005
287
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<ChkAcceptId>
Identifier
Required Repeating
Check Accept Identifier.
6.16.5.2 Response <ChkAcceptAudRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
288
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Check Accept Identifier.
<ChkAcceptId>
Identifier
<ChkAcceptMsgRec>
6.16.5.2.1 Check Accept Message Record Aggregate <ChkAcceptMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Message Record Creation Date. The timestamp at which the message record was stored/created by the service provider. Check Accept Add Response Message Aggregate.
<MsgRecDt> <ChkAcceptAddRs>
Timestamp Aggregate see section 6.16.1.2 Aggregate see section 6.16.2.2 Aggregate see section 6.16.4.2 Aggregate
<ChkAcceptModRs>
Check Accept Modify Response Message Aggregate.
<ChkAcceptCanRs>
Check Accept Cancel Response Message Aggregate.
<ChkAcceptDelRs>
Check Accept Delete Response Message Aggregate.
6.16.6
Check Accept Sync
Allows a client to synchronize the check accept messages associated with the current customer since some past point in time.
Version 1.7
April 2005
289
6.16.6.1 Request <ChkAcceptSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<ChkAcceptId>
Identifier
Required Repeating
Check Accept Identifier.
6.16.6.2 Response <ChkAcceptSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to buil and be able to be sent synchronously.
290
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issues. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<RecCtrlOut>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Check Accept Identifier.
<ChkAcceptId>
Identifier
<ChkAcceptMsgRec>
Check Accept Message Record Aggregate.
6.16.7
Check Accept Reversal
Allows a client to reverse a previous check accept message.
6.16.7.1 Request <ChkAcceptRevRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
291
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Defined values: CustomerCancellation, Unspecified-NoActionTaken, SuspectedMalfunction, FormatErrorNoActionTaken, CompletedPartially, OriginalAmountIncorrect, ResponseReceivedTooLate, CardAcceptorDeviceUnableToCompleteTransaction , DepositOutOfBalance, NoCheckInEnvelope, PaymentOutOfBalance, DepositOutOfBalanceAppliedContents, PaymentOutOfBalanceAppliedContents, UnableToDeliverMessageToPointOfService, SuspectedMalfunction-CardRetained, SuspectedMalfunction-CardReturned, SuspectedMalfunction-Track3NotUpdated, SuspectedMalfunction-NoCashDispensed, TimedOutAtTakingMoney-NoCashDispensed, TimedOutAtTakingCardCardRetainedAndNoCashDispensed, InvalidResponse-NoActionTaken, TimeoutWaitingForResponse (reference ISO 8583:1993 Annex A.11)
<RevReasonCode>
Open Enum
Required
<Desc> <ChkAcceptMsgRqInfo>
Optional Required
Description, text describing the reason for the reversal. Check Accept Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
6.16.7.1.1 Check Accept Message Request Information Aggregate <ChkAcceptMsgRqInfo>

Tag
<ChkAcceptAddRq> <ChkAcceptModRq> <ChkAcceptCanRq> <ChkAcceptInqRq> <ChkAcceptAudRq>
Type
Usage
Description
Check Accept Add Request Message Aggregate. Check Accept Modify Request Message Aggregate. Check Accept Cancel Request Message Aggregate. Check Accept Inquiry Request Message Aggregate. Check Accept Audit Request Message Aggregate.
292
April 2005
Version 1.7
Tag
<ChkAcceptSyncRq> <ChkAcceptStatusModRq>
Type
Usage
Description
Check Accept Sync Request Message Aggregate. Check Accept Status Modify Request Message Aggregate.
6.16.7.2 Response <ChkAcceptRevRs>

Tag
<Status> <RqUID>
Type
Usage
Optional Required Echoed Optional Echoed Optional Optional Echoed
Description
Status Aggregate Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header Aggregate. Message Request Header Aggregate. Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued.
<MsgRqHdr> <MsgRsHdr> <AsyncRqUID>
<CustId>
Optional Echoed
Version 1.7
April 2005
293
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required Echoed
Description
Reversal reason code. The reason why the client is requesting a reversal. Defined values: CustomerCancellation, Unspecified-NoActionTaken, SuspectedMalfunction, FormatErrorNoActionTaken, CompletedPartially, OriginalAmountIncorrect, ResponseReceivedTooLate, CardAcceptorDeviceUnableToCompleteTransacti on, DepositOutOfBalance, NoCheckInEnvelope, PaymentOutOfBalance, DepositOutOfBalanceAppliedContents, PaymentOutOfBalanceAppliedContents, UnableToDeliverMessageToPointOfService, SuspectedMalfunction-CardRetained, SuspectedMalfunction-CardReturned, SuspectedMalfunction-Track3NotUpdated, SuspectedMalfunction-NoCashDispensed, TimedOutAtTakingMoney-NoCashDispensed, TimedOutAtTakingCardCardRetainedAndNoCashDispensed, InvalidResponse-NoActionTaken, TimeoutWaitingForResponse (reference ISO 8583:1993 Annex A.11)
<Desc> <ChkAcceptMsgRqInfo>
Description, text describing the reason for the reversal. Check Accept Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
6.16.8
Check Accept Status Modify
Allows a client to change the status of a check accept message.
6.16.8.1 Request <ChkAcceptStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
294
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Accept Identifier. Check Accept Status aggregate.
<ChkAcceptId> <ChkAcceptStatus>
Required Required
6.16.8.2 Response <ChkAcceptStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Check Accept Identifier. Check Accept Status aggregate.
<CustId>
Optional Echoed
<ChkAcceptId> <ChkAcceptStatus>
6.17
Passbook
Version 1.7
April 2005
295
6.17.1
Passbook Add
Passbook Add is used to add a logical passbook to an account. This is not used if a passbook relationship has already been established for an account.
6.17.1.1 Request <PassbkAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Information Aggregate.
<CustId>
Optional
<PassbkInfo>
Required
6.17.1.2 Response <PassbkAddRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
296
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Information Aggregate.
<PassbkInfo>
<PassbkRec>
Passbook Record Aggregate.
Optional Optional
6.17.2
Passbook Modify
This message is used to modify the passbook object most likely to set the Id of the last printed Item, and the next line at which printing should begin. As a matter of processing this message, all Passbook Items with Item Ids before the Item Id specified in the <PassbkLastItemPrinted> field should be set to Printed by the server as this message is processed. Also, it is assumed that the server will also update the status of this Passbook object and recalculate the <PassbkStatusCode> and <PassbkNewItemsToPrint> fields based on what is currently outstanding.
6.17.2.1 Request <PassbkModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier. Passbook Information Aggregate.
<CustId>
Optional
Required Required
Version 1.7
April 2005
297
6.17.2.2 Response <PassbkModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier. Passbook Information Aggregate.
<CustId>
Optional Echoed
<PassbkRec>
Optional Optional
6.17.3
Passbook Inquiry
This message is used to inquire on a passbook object
6.17.3.1 Request <PassbkInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
298
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<PassbkId>
Optional Repeating Optional XOR Optional XOR Optional XOR Optional
Passbook Identifier. This field is used as a selection criterion. Deposit Account Identification Aggregate. This field is used as a selection criterion. Card Account Identification Aggregate. This field is used as a selection criterion. Loan Account Identifier Aggregate. This field is used as a selection criterion. A short identifier that differentiates one passbook from another. It would be assumed that this Identifier could be entered or selected by an account holder, and is used to identify which passbook is being updated. This would likely only be necessary in an environment where multiple passbooks could be attached to the same account. This field is used as a selection criterion.
<DepAcctId>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 Aggregate see section 3.2.7.2.5 C-40
<CardAcctId>
<LoanAcctId>
<Name>
<PassbkLastItemPrinted>
Identifier
Optional
The Id of the last successful PassbkItem that has been printed in the Passbook media. This field is used as a selection criterion.
<PassbkLastBalPrinted>
Currency Amount
Optional
The last balance printed in the passbook media. Typical usage would only consider the <Amt> field in the currency amount type. If this value is unknown, the field is omitted. This field is used as a selection criterion.
<PassbkNextLine>
Long
Optional
The line number on which to start printing. This should always be updated to the last line number printed+1 or reset to 1 if the next line to print is on a new page. This number is one-based, so a value of 1 means to print at the top of the page. A value of zero or negative values are reserved, and should not be used. If this value is unknown, the field is omitted. This field is used as a selection criterion.
Version 1.7
April 2005
299
Tag
<PassbkNextPage>
Type
Long
Usage
Optional
Description
The page number on which to start printing. This number is one-based, so a value of 1 means to print on the first page of the Passbook. A value of zero or negative values are reserved, and should not be used. If this value is unknown, the field is omitted. This field is used as a selection criterion.
6.17.3.2 Response <PassbkInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Passbook Identifier. This field is used as a selection criterion. Deposit Account Identification Aggregate. This field is used as a selection criterion. Card Account Identification Aggregate. This field is used as a selection criterion. Loan Account Identifier Aggregate. This field is used as a selection criterion.
<CustId>
Optional Echoed
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional XOR
<PassbkId>
<DepAcctId>
<CardAcctId>
<LoanAcctId>
300
April 2005
Version 1.7
Tag
<Name>
Type
C-40
Usage
Optional Echoed
Description
A short identifier that differentiates one passbook from another. It would be assumed that this Identifier could be entered or selected by an account holder, and is used to identify which passbook is being updated. This would likely only be necessary in an environment where multiple passbooks could be attached to the same account. This field is used as a selection criterion.
<PassbkLastItemPrinte d>
Identifier
Optional Echoed
The Id of the last successful PassbkItem that has been printed in the Passbook media. This field is used as a selection criterion.
<PassbkLastBalPrinted >
Currency Amount
Optional Echoed
The last balance printed in the passbook media. Typical usage would only consider the <Amt> field in the currency amount type. If this value is unknown, the field is omitted. This field is used as a selection criterion.
<PassbkNextLine>
Long
Optional Echoed
The line number on which to start printing. This should always be updated to the last line number printed+1 or reset to 1 if the next line to print is on a new page. This number is one-based, so a value of 1 means to print at the top of the page. A value of zero or negative values are reserved, and should not be used. If this value is unknown, the field is omitted. This field is used as a selection criterion.
<PassbkNextPage>
Long
Optional Echoed
The page number on which to start printing. This number is one-based, so a value of 1 means to print on the first page of the Passbook. A value of zero or negative values are reserved, and should not be used. If this value is unknown, the field is omitted. This field is used as a selection criterion.
<PassbkRec>
Optional Repeating
6.17.4
Passbook Delete
This message is used to delete a logical passbook from an account.
6.17.4.1 Request <PassbkDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
301
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier.
<PassbkId>
Identifier
Required
6.17.4.2 Response <PassbkDelRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier. Passbook Record Aggregate.
<CustId>
Optional Echoed
<PassbkId> <PassbkRec>
Optional Optional
6.17.5
Passbook Audit
These messages are used to audit changes made to a Passbook object.
6.17.5.1 Request <PassbkAudRq>
302
April 2005
Version 1.7
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<PassbkId>
Identifier
Required Repeating
Passbook Identifier.
6.17.5.2 Response <PassbkAudRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
303
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Passbook Identifier.
<PassbkId>
Identifier
<PassbkMsgRec>
6.17.5.3 Passbook Message Record Aggregate <PassbkMsgRec>

Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Timestamp Aggregate see section 6.17.1.2 Aggregate see section 6.17.2.2 Aggregate see section 6.17.4.2 Aggregate see section 6.17.7.2 Aggregate see section 6.17.8.2
Usage
Optional
Description
<MsgRecDt> <PassbkAddRs>
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Passbook Add Response Message Aggregate.
<PassbkModRs>
Passbook Modify Response Message Aggregate.
<PassbkDelRs>
Passbook Delete Response Message Aggregate.
<PassbkRevRs>
Passbook Reversal Response Message Aggregate.
<PassbkStatusModRs>
Passbook Status Modify Response Message Aggregate.
6.17.6
Passbook Sync
These messages are used to synchronize changes made to a Passbook object.
304
April 2005
Version 1.7
6.17.6.1 Request <PassbkSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<PassbkId>
Identifier
Required Repeating
Passbook Identifier.
6.17.6.2 Response <PassbkSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to buil and be able to be sent synchronously.
Version 1.7
April 2005
305
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issues. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<RecCtrlOut>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Passbook Identifier.
<PassbkId>
Identifier
<PassbkMsgRec>
6.17.7
Passbook Reversal
These messages are used to reverse on operation performed on the Passbook object.
6.17.7.1 Request <PassbkRevRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
306
April 2005
Version 1.7
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required
Description
<Desc> <PassbkMsgRqInfo>
Optional Required
6.17.7.2 Response <PassbkRevRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Version 1.7
April 2005
307
Tag
<RevReasonCode>
Type
Open Enum
Usage
Required Echoed
Description
<Desc> <PassbkMsgRqInfo>
C-80 Aggregate see section 6.17.7.3 Identifier Identifier
Optional Optional
6.17.7.3 Passbook Message Request Information Aggregate <PassbkMsgRqInfo>

Tag
<PassbkAddRq>
Type
Usage
Description
Passbook Add Request Message Aggregate.
<PassbkModRq>
Passbook Modify Request Message Aggregate.
<PassbkDelRq>
Passbook Delete Request Message Aggregate.
<PassbkInqRq>
Passbook Inquiry Request Message Aggregate.
<PassbkAudRq>
Passbook Audit Request Message Aggregate.
<PassbkSyncRq>
Passbook Sync Request Message Aggregate.
<PassbkStatusModRq>
Passbook Status Modify Request Message Aggregate.
308
April 2005
Version 1.7
6.17.8
Passbook Status Modify
These messages modify the status of the Passbook object. This would typically only be done to set <PassbkStatusCode> to MediaError if there is a problem with the passbook media. The server maintains <PassbkNewItemsToPrint>, and therefore may ignore changes (or reset this field to the correct value) during a Passbook Status Modify.
6.17.8.1 Request <PassbkStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier. Passbook Status aggregate.
<CustId>
Optional
Required Required
6.17.8.2 Response <PassbkStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
309
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional Echoed
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier. Passbook Status aggregate.
<CustId>
Optional Echoed
Identifier Aggregate see section 6.3.40.2 Aggregate see section 6.3.40.1 Identifier Identifier
<PassbkStatusRec>
Passbook Status Record aggregate.
Optional Optional
6.17.9
Passbook Status Inquiry
These messages request and return the status of a passbook.
6.17.9.1 Request <PassbkStatusInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier.
<CustId>
Optional
<PassbkId>
Identifier
Optional Repeating
6.17.9.2 Response <PassbkStatusInqRs>
310
April 2005
Version 1.7
Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Identifier.
<CustId>
Optional Echoed
<PassbkId>
Identifier
Optional Repeating Echoed Optional Repeating Optional Optional
<PassbkStatusRec>
Passbook Status aggregate.
6.17.10 Passbook Item Add

These messages are used to add a line into a passbook. Standard transactions are considered to be added automatically (through back-end processing), and would not require this to be called explicitly from a client.
6.17.10.1 Request <PassbkItemAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
311
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Information Aggregate.
<PassbkItemInfo>
Required
6.17.10.2 Response <PassbkItemAddRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Information Aggregate.
<CustId>
Optional Echoed
<PassbkItemInfo>
<PassbkItemRec>
Passbook Item Record Aggregate.
Optional Optional
6.17.11 Passbook Item Modify

These messages are used to modify an item in the passbook. Although this message may be defined, in all practical situations no passbook holder or bank staff would likely have permission to use this message.
312
April 2005
Version 1.7
6.17.11.1 Request <PassbkItemModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier. Passbook Item Information Aggregate.
<CustId>
Optional
<PassbkItemId> <PassbkItemInfo>
Required Required
6.17.11.2 Response <PassbkItemModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
Version 1.7
April 2005
313
Tag
<PassbkItemId> <PassbkItemInfo>
Type
Usage
Description
Passbook Item Identifier. Passbook Item Information Aggregate.
<PassbkItemRec>
Passbook Item Record Aggregate.
Optional Optional
6.17.12 Passbook Item Inquiry

These messages are used to inquire on Passbook Items for a specific passbook given the Passbook Id. This is the main message used when performing a Passbook update.
6.17.12.1 Request <PassbkItemInqRq>

This message requests a list of Passbook Items. The items are returned in the order they would appear in a Passbook typically sorted by Date. Although included in this message, the <SelRangeDate> selection criteria would typically not be used in a Passbook update operation.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 UUID
Optional
<RelatedItemInqRqUID>
Optional
The RqUID of a previous PassbkItemInqRq that is to be considered a part of the same Passbook update. This field is included so the server will not assess multiple fees for the same series of Passbook Item Inquiries.
314
April 2005
Version 1.7
Tag
<PassbkItemId>
Type
Identifier
Usage
Optional Repeating
Description
Passbook Item Identifier. This criterion would not be used during a typical Passbook update operation. This field is used as a selection criterion.
<PassbkId>
Identifier
Optional
Passbook Identifier. The Id of the passbook object of which lines are being queried. This field is used as a selection criterion.
<PassbkItemStatusCode>
Closed Enum
Optional
The current status of the Passbook Item object. Defined Values: NotPrinted The Item has not yet been printed. This is used in the Inquiry (without other selection criteria) to indicate that the next lines to print should be returned. Printed The Item has been printed Unknown It is not known whether or not the item has been printed This field is used as a selection criterion.
<SelRangeDt>
Optional
Selection Range Date Aggregate. This is advanced selection criteria, which would not be used during a typical Passbook update operation.
6.17.12.2 Response <PassbkItemInqRs>

The items are returned in the order they would appear in a Passbook typically sorted by Date.
Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control.
<CustId>
Optional Echoed
<RecCtrlOut>
Version 1.7
April 2005
315
Tag
<RelatedItemInqRqUID>
Type
UUID
Usage
Optional
Description
The RqUID of a previous PassbkItemInqRq that is to be considered a part of the same Passbook update. This field is included so the server will not assess multiple fees for the same series of Passbook Item Inquiries. Passbook Item Identifier. This criterion would not be used during a typical Passbook update operation. This field is used as a selection criterion. Passbook Identifier. The Id of the passbook object of which lines are being queried. This field is used as a selection criterion.
<PassbkItemId>
Identifier
Optional Repeating Echoed Optional Echoed
<PassbkId>
Identifier
<PassbkItemStatusCode>
Closed Enum
Optional Echoed
The current status of the Passbook Item object. Defined Values: NotPrinted The Item has not yet been printed. This is used in the Inquiry (without other selection criteria) to indicate that the next lines to print should be returned. Printed The Item has been printed Unknown It is not known whether or not the item has been printed This field is used as a selection criterion.
<SelRangeDt>
Selection Range Date Aggregate. This is advanced selection criteria, which would not be used during a typical Passbook update operation. Passbook Item Record Aggregate.
<PassbkItemRec>
6.17.13 Passbook Item Delete

These messages are used to delete a line from a passbook. Although this message may be defined, in all practical situations no passbook holder or bank staff would likely have permission to use this message.
6.17.13.1 Request <PassbkItemDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
316
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier.
<PassbkItemId>
Identifier
Required
6.17.13.2 Response <PassbkItemDelRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier. Passbook Item Record Aggregate.
<CustId>
Optional Echoed
<PassbkItemId> <PassbkItemRec>
Optional Optional
6.17.14 Passbook Item Audit

These messages are used to audit changes made to a passbook item object.
6.17.14.1 Request <PassbkItemAudRq>
Version 1.7
April 2005
317
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
<PassbkItemId>
Identifier
Required Repeating
Passbook Item Identifier.
6.17.14.2 Response <PassbkItemAudRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
318
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Passbook Item Identifier.
<PassbkItemId>
Identifier
<PassbkItemMsgRec>
6.17.14.3 Passbook Item Message Record Aggregate <PassbkItemMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
<MsgRecDt>
Optional
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Passbook Item Add Response Message Aggregate.
<PassbkItemAddRs>
<PassbkItemModRs>
Passbook Item Modify Response Message Aggregate.
<PassbkItemDelRs>
Passbook Item Delete Response Message Aggregate.
<PassbkItemRevRs>
Passbook Item Reversal Response Message Aggregate. Passbook Item Status Modify Response Message Aggregate.
<PassbkItemStatusModRs>
Version 1.7
April 2005
319
6.17.15 Passbook Item Sync

These messages are used to synchronize changes made to a passbook object.
6.17.15.1 Request <PassbkItemSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
<PassbkItemId>
Identifier
Required Repeating
Passbook Item Identifier.
6.17.15.2 Response <PassbkItemSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
320
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional Echoed
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to buil and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issues. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<CustId>
Optional Echoed
<RecCtrlOut>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Passbook Item Identifier.
<PassbkItemId>
Identifier
<PassbkItemMsgRec>
6.17.16 Passbook Item Reversal

These messages are used to reverse on operation performed on the Passbook item object. For example, this can be used to reverse an inquiry (in order to reverse any back-end fees associated with a passbook update).
6.17.16.1 Request <PassbkItemRevRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
321
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Defined values: CustomerCancellation, UnspecifiedNoActionTaken, SuspectedMalfunction, FormatErrorNoActionTaken, CompletedPartially, OriginalAmountIncorrect, ResponseReceivedTooLate, CardAcceptorDeviceUnableToCompleteTransaction, DepositOutOfBalance, NoCheckInEnvelope, PaymentOutOfBalance, DepositOutOfBalanceAppliedContents, PaymentOutOfBalanceAppliedContents, UnableToDeliverMessageToPointOfService, SuspectedMalfunction-CardRetained, SuspectedMalfunction-CardReturned, SuspectedMalfunction-Track3NotUpdated, SuspectedMalfunction-NoCashDispensed, TimedOutAtTakingMoney-NoCashDispensed, TimedOutAtTakingCardCardRetainedAndNoCashDispensed, InvalidResponseNoActionTaken, TimeoutWaitingForResponse (reference ISO 8583:1993 Annex A.11)
<RevReasonCode>
Open Enum
Required
<Desc> <PassbkItemMsgRqInfo>
Optional Required
6.17.16.2 Response <PassbkItemRevRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
322
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional Echoed
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Defined values: CustomerCancellation, UnspecifiedNoActionTaken, SuspectedMalfunction, FormatErrorNoActionTaken, CompletedPartially, OriginalAmountIncorrect, ResponseReceivedTooLate, CardAcceptorDeviceUnableToCompleteTransaction, DepositOutOfBalance, NoCheckInEnvelope, PaymentOutOfBalance, DepositOutOfBalanceAppliedContents, PaymentOutOfBalanceAppliedContents, UnableToDeliverMessageToPointOfService, SuspectedMalfunction-CardRetained, SuspectedMalfunction-CardReturned, SuspectedMalfunction-Track3NotUpdated, SuspectedMalfunction-NoCashDispensed, TimedOutAtTakingMoney-NoCashDispensed, TimedOutAtTakingCardCardRetainedAndNoCashDispensed, InvalidResponseNoActionTaken, TimeoutWaitingForResponse (reference ISO 8583:1993 Annex A.11)
<CustId>
Optional Echoed
<RevReasonCode>
Open Enum
Required Echoed
<Desc> <PassbkItemMsgRqInfo>
C-80 Aggregate see section 6.17.16.3 Identifier Identifier
Optional Optional
6.17.16.3 Passbook Item Message Request Information Aggregate <PassbkItemMsgRqInfo>

Tag
<PassbkItemAddRq>
Type
Usage
Description
Passbook Item Add Request Message Aggregate.
<PassbkItemModRq>
Passbook Item Modify Request Message Aggregate.
Version 1.7
April 2005
323
Tag
<PassbkItemDelRq>
Type
Usage
Description
Passbook Item Delete Request Message Aggregate.
<PassbkItemInqRq>
Passbook Item Inquiry Request Message Aggregate.
<PassbkItemAudRq>
Passbook Item Audit Request Message Aggregate.
<PassbkItemSyncRq>
Passbook Item Sync Request Message Aggregate.
<PassbkItemStatusMod Rq>
Passbook Item Status Modify Request Message Aggregate.
6.17.17 Passbook Item Status Modify

These messages are used to manually update the Status of the Passbook Item. These messages are not typically called by client applications. Note that the <PassbkItemStatusCode> should be updated to Printed automatically when the client sends a <PassbkModRq> indicating a new <PassbkLastItemPrinted> of an Item Id that is greater than this Passbook Item.
6.17.17.1 Request <PassbkItemStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier. Passbook Item Status aggregate.
<CustId>
Optional
Required Required
324
April 2005
Version 1.7
6.17.17.2 Response <PassbkItemStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier. Passbook Item Status aggregate.
<CustId>
Optional Echoed
Identifier Aggregate see section 6.3.41.3 Aggregate see section 6.3.41.1 Identifier Identifier
<PassbkItemStatusRec>
Passbook Item Status Record aggregate.
Optional Optional
6.17.18 Passbook Item Status Inquiry

These messages inquire on the status of a specific Passbook Item object.
6.17.18.1 Request <PassbkItemStatusInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
325
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier. This criteria would not be used during a typical Passbook update operation.
<CustId>
Optional
<PassbkItemId>
Identifier
Optional Repeating
6.17.18.2 Response <PassbkItemStatusInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Passbook Item Identifier.
<CustId>
Optional Echoed
<PassbkItemId>
Identifier
Optional Repeating Echoed Optional Repeating Optional Optional
<PassbkItemStatusRec>
Passbook Item Status Record aggregate.
326
April 2005
Version 1.7
6.18 Banking Service Profile <BankSvcProfInfo>

The Profile for the Banking Service <BankSvcProfInfo> is defined below. This profile is returned to the client in <SvcProfInqRq> and provides information on how the client should use the Banking Service.
Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service. Supported Messages. This is a list of messages that are supported for Banking. The convention is to use the name of the message without the Rq or Rs so that each message is only listed once. Defined values: BalInq, BalRev, AcctInq, AcctRev, DepAcctStmtInq, DepAcctStmtAdvise, DepAcctStmtRev, CCAcctStmtInq, CCAcctStmtRev, BankAcctStmtImgInq, BankAcctStmtImgRev, DepAcctTrnInq, DepAcctTrnRev, CCAcctTrnInq, CCAcctTrnRev, BankAcctTrnImgInq, BankAcctTrnImgRev, IntRateInq, IntRateRev, BankAcctTaxInq, BankAcctTaxRev, ForExRateInq, ForExRateRev, StpChkAdd, StpChkCan, StpChkInq, StpChkAud, StpChkSync, StpChkRev, XferAdd, XferMod, XferCan, XferStatusMod, XferInq, XferAud, XferSync, XferRev, RecXferAdd, RecXferMod, RecXferCan, RecXferInq, RecXferAud, RecXferSync, RecXferRev, ChkOrdAdd, ChkOrdRev, DepBkOrdAdd, DepBkOrdRev, DebitAuthAdd, DebitAuthMod, DebitAuthStatusMod, DebitAuthCan, DebitAuthInq, DebitAuthAud, DebitAuthSync, DebitAuthRev, DebitAdd, DebitMod, DebitStatusMod, DebitCan, DebitInq, DebitAud, DebitSync, DebitRev, CreditAuthAdd, CreditAuthMod, CreditAuthStatusMod, CreditAuthCan, CreditAuthInq, CreditAuthAud, CreditAuthSync, CreditAuthRev, CreditAdd, CreditMod, CreditStatusMod, CreditCan, CreditInq, CreditAud, CreditSync, CreditRev, DepAppAdd, DepAppInq, DepAppCan, DepAppMod, DepAppAud, DepAppSync, PmtEnclAdd, PmtEnclMod, PmtEnclCan, PmtEnclInq, PmtEnclAud, PmtEnclRev, PmtEnclStatusMod, BankSvcChkSumAdd, BankSvcChkSumMod, BankSvcChkSumStatusMod, BankSvcChkSumDel, BankSvcChkSumInq, BankSvcChkSumAud, BankSvcChkSumSync, DebitAdvise, DebitAuthAdvise, CreditAdvise, CreditAuthAdvise, XferAdvise, PmtEnclAdvise, ChkOrdAdvise, DepBkOrdAdvise, StopChkAdvise, ChkAcceptAdd, ChkAcceptMod, ChkAcceptStatusMod, ChkAcceptInq, ChkAcceptCan, ChkAcceptAud, ChkAcceptSync, ChkAcceptRev, PassbkAdd, PassbkMod, PassbkInq, PassbkDel, PassbkAud, PassbkSync, PassbkRev, PassbkStatusMod, PassbkStatusInq, PassbkItemAdd, PassbkItemMod, PassbkItemInq, PassbkItemDel, PassbkItemAud, PassbkItemSync, PassbkItemRev, PassbkItemStatusMod, PassbkItemStatusInq
<MsgSupt>
Required Repeating
Version 1.7
April 2005
327
Tag
<RevOptSupt>
Type
Open Enum
Usage
Optional Repeating
Description
Reversal Options Supported. This is a list of reversal messages supported for Banking. The convention is to use the name of the message without the Rq or Rs so that each message is only listed one. Defined values: BalInq, AcctInq, DepAcctStmtInq, CCAcctStmtInq, BankAcctStmtImgInq, DepAcctTrnInq, CCAcctTrnInq, BankAcctTrnImgInq, IntRateInq, ForExRateInq, StpChkAdd, StpChkCan, StpChkInq, StpChkAud, StpChkSync, XferAdd, XferMod, XferCan, XferStatusMod, XferInq, XferAud, XferSync, RecXferAdd, RecXferMod, RecXferCan, RecXferInq, RecXferAud, RecXferSync, ChkOrdAdd, DepBkOrdAdd, DebitAuthAdd, DebitAuthMod, DebitAuthCan, DebitAuthInq, DebitAuthAud, DebitAuthSync, DebitAdd, CreditAuthAdd, CreditAuthMod, CreditAuthCan, CreditAuthInq, CreditAuthAud, CreditAuthSync, CreditAdd, DebitAuthStatusMod, DebitMod, DebitCan, DebitInq, DebitAud, DebitSync, DebitStatusMod, CreditAuthStatusMod, CreditMod, CreditCan, CreditInq, CreditAud, CreditSync,CreditStatusMod, PmtEnclAdd, PmtEnclMod, PmtEnclCan, PmtEnclInq, PmtEnclAud, PmtEnclStatusMod, ChkAcceptMod, ChkAcceptCan, ChkAcceptInq,ChkAcceptAud, ChkAcceptSync, ChkAcceptStatusMod, , PassbkAdd, PassbkMod, PassbkInq, PassbkDel, PassbkAud, PassbkSync, PassbkRev, PassbkStatusMod, PassbkStatusInq, PassbkItemAdd, PassbkItemMod, PassbkItemInq, PassbkItemDel, PassbkItemAud, PassbkItemSync, PassbkItemRev, PassbkItemStatusMod, PassbkItemStatusInq.
<OptSupt>
Open Enum
Optional Repeating
Options Supported. Defined values: RecCtrl, SuppressEcho, AddReadOnlyAllowed Customer Bank Service Preferences Supported. Defined values: Language, MktgInfo, CustWithdrawalPref Delivery Method. Defined values: Channel, Courier, Email, Fax, HomeBank, Overnight, Post, LocalPrinter, TwoDay, UPS. Note that although these are valid values for this element, they may not be appropriate for a particular message and may result in rejection. In this case, a response must be sent to the customer with an appropriate Status Code.
<CustBankPrefSupt>
Open Enum
<DeliveryMethod>
Open Enum
<StopChkProf>
Aggregate see section 6.18.1 Aggregate see section 6.3.24 Aggregate
Optional
Stop Check Profile Aggregate. Included if supported.
<XferProf>
Optional but see Description Optional but see Description
Transfer Profile Aggregate. Must be included if funds transfers are supported. Interbank Transfer Profile Aggregate. Must be included if interbank transfers are supported
<InterXferProf>
6.18.1
Stop Check Profile Aggregate <StopChkProf>
328
April 2005
Version 1.7
Tag
<OptSupt>
Type
Open Enum
Usage
Description
Options Supported. Valid values: StopChkRangeSC. Processing Schedule Aggregate. If omitted, the default processing schedule is assumed. Default Check Stop Fee(s).
<PrcSched>
Aggregate see section 5.2.2.3 Currency Amount
<Fee>
Optional Repeating
6.18.2
Tag
Interbank Transfer Profile Aggregate <IntXferProf>

Type
Aggregate
Usage
Description
Interbank Transfer Profile Aggregate. Must be included if interbank transfers are supported Transfer Profile Aggregate.
<InterXferProf>
<XferProf>
Aggregate see section 6.3.24 Currency Amount Currency Amount Aggregate see section 6.18.3
<DomXferFeeCurAmt> <IntlXferFeeCurAmt> <USA.ACHProf>
Standard fee for a domestic interbank transfer. Standard fee for an international interbank transfer. ACH Profile Aggregate. This is for use in the United States.
6.18.3
Tag
ACH Profile Aggregate <USA.ACHProf>

Type
Long Long Long
Usage
Description
Number of Days Before Withdrawal. Number of days before processing date that funds are withdrawn. Default Days to Pay. Cancellation WindowRefers to number of days after a transfer is initiated using ACH during which the transfer may be cancelled.
<DaysWith> <DfltDaysToPay> <CanWind>
Version 1.7
April 2005
329
7 The Pay Service <PaySvc>

The IFX Specification defines all functionality related to consumer and business payment in the Pay Service <PaySvc>. Clients use the Pay Service to manage a list of payees, schedule individual payments, and define recurring payment models that automatically generate fixed-amount payments at regular intervals to a given payee. Payments may be made to organizations (Billers) with which the CPP (also described in this chapter as the customers Pay provider, and may be a Financial Institution or Service Provider) has contracts for payment consolidation (Standard Payee), or obtains equivalent information from the BSP (Biller Payee). Payments may also be made to individuals or organizations that have no such relationship with the customers Pay provider (Fully-Specified Payees) or to accounts at other Financial Institutions (Interbank Transfer Payees).
7.1Description
7.1.1Payees
7.1.1.1 Types of Payees
As mentioned previously, a payee may be one of four types: a Standard Payee, a Fully-Specified Payee, a Biller Payee, or a Transfer Payee.
7.1.1.1.1 Standard Payee

A Standard Payee is a merchant or payment recipient whose remittance attributes are well known to the CPP. Typically remittance attributes include remittance method (ACH-CIE, ACH-CTX, RPS, ePay, etc.,) concentrator, lockbox, posting exceptions contact, etc. A standard payee is uniquely identified within a CPP with a payee identifier <StdPayeeId>. The customer need only reference the Standard Payee. A customer should not be able to modify the <StdPayeeId> of a standard payee. Standard Payees are typically national, regional, or large local companies or organizations (such as billers) that have contracted with the CPP to consolidate payments from multiple consumers and small businesses. Because the CPP consolidates payments, it already has sufficient remittance information about the biller in its systems, and the customer does not need to enter all the information required for a Fully-Specified Payee. In some countries, Standard Payees are assigned unique identifiers on a national basis, while in others a biller identifier may only be significant to a single CPP. IFX allows for both cases by qualifying a biller number with the name of the organization that assigned it (e.g., the <StdPayeeId> is the Biller as known by the CPP, and the <BillerId> is the Biller as known by the Biller or BSP). Note that anytime a <StdPayeeId> exists outside of a payment message, it must include the CPP <SPName> to scope its value.
7.1.1.1.2 Fully-Specified Payee

A Fully-Specified Payee is a payee for which a customer must enter all information needed for his or her Pay provider to identify the payee and payment destination, such as the payees full name and address. Some Pay providers may also require that customers enter a telephone number for the payee. Most individuals and small businesses are likely to be Fully-Specified Payees.
7.1.1.1.3 Biller Payee

A Biller Payee is one where the details about that payee (name, address, acctid, remittance information, payment instruments) have been obtained from a BSP as a result of a Biller Inquiry <BillerInqRq> or Presentment Service/Account Link Add <SvcAcctAddRq>.
7.1.1.1.4 Transfer Payee

A Transfer Payee is a payee for which the customer knows the Financial Institution and Account information where a payment may be made using a funds transfer.
Version 1.7
April 2005
7.1.1.1.5 Changing Payee Information

Generally, the customer is permitted to change name/address or destination account information about the Fully-Specified Payee and Transfer Payee, but the customer cannot change Biller name and address information. Only Financial Institutions or Service Providers may change Biller information.
7.1.1.2 Common Payee Information

Although a customer must specify some different information for each type of payee, there are a number of attributes common to all types of payees. A Payee Name and, optionally, a Payee Nickname may be assigned to each payee. The name is typically the payees legal name and may be used by the Pay provider as well as the client. A payee nickname may be assigned by the customer and is only used as a user-friendly name for ease of recall for later use. All Pay providers should allow a Customer Payee Account number to be stored as part of each payee record. This number is then sent to the Payee with a payment to allow the payee to correlate the payment with one of their customer accounts. While this element is not required for all payments, it should be included if it is known. The Customer Payee Account within the Payee definition is used as a default for all payments to that payee. If a Customer Payee Account is specified as part of the payment, it must be used for that payment, but must not modify the Customer Payee Account within the payee definition. While not explicitly supported within the IFX specification, a customer may have multiple accounts with the payee. For example, a customer who purchases auto and homeowners insurance from the same insurance company may want to set up payments for both policies. The customer adds the insurance company to his payee list as two independent payees, each with its own customer account number, based on instructions from the insurance company (use account 11023732 for auto insurance payments, and account 97584324 for homeowners insurance payments.) The customer may use the <Nickname> field to differentiate between payees, e.g., ABC InsuranceHome and ABC InsuranceAuto. Default Payment Information may also be assigned to a payee so that when a customer is adding a payment or a recurring payment model for that payee, some fields may be pre-populated with default values for the customers convenience. The customer may always elect to change the values for a particular payment, but the defaults are useful to help a customer quickly enter payment information for common payments. Payment defaults, which may be assigned to a payee, are the funding account for payments, the category to which payments are assigned, and the memo that is associated with the payment.
7.1.1.3 Customer Payee ManagementCustomer Payee List and Customer Payee Identifier
Some Pay Service Providers require an individual list of Payees for each customer, while others do not. Pay Service Providers within the United States typically support this feature, while Canadian and European systems generally do not support it. A Service Profile option is provided to specify whether this feature is supported or not. Each customer maintains a list of payees on the Pay providers server. This list contains payees that the customer has added, either explicitly using the Customer Payee Add message <CustPayeeAddRq> or implicitly using the Payment Add <PmtAddRq> or Recurring Payment Model Add <RecPmtAddRq> messages (which allow a payee to be added along with a payment). In any case, the customers Payee list may contain any or all of the four types of payees and only contains payees that the customer has added. Each payee on the customers payee list is assigned a unique identifier <CustPayeeId> that is used for unambiguous communications between the client and server. The <CustPayeeId> is unique only for that particular customer; another customer may use the same <CustPayeeId> value to refer to a different payee. Once a payee appears on the customers payee list, the client may use the Customer Payee Modify <CustPayeeModRq> and Customer Payee Delete <CustPayeeDelRq> messages to keep the payee information up-to-date or to remove the payee from the customers payee list. A client may request a current view of the customers payee list at any time by using the Customer Payee Inquiry <CustPayeeInqRq> message. Clients that keep a local copy of a customers payee list may use this
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification message to refresh their copy of the list. They may also request a playback of the messages that affected the customers payee list since a given time by using the Customer Payee Audit <CustPayeeAudRq> and/or Customer Payee Synchronization <CustPayeeSyncRq> messages.
7.1.1.4 Pay Provider Payee ManagementDuplicate Checking and Payee Type Conversion
Pay providers also manage customer Payee Lists. Two common practices among Pay providers are duplicate checking and payee type conversion. Some Pay providers perform Duplicate checking when a Payee record is added to or modified on a customers Payee List. In this case, the Pay provider verifies that the Payee is not already on the customers payee list. Payee type conversion to Biller allows payments to Billers to be paid effectively. A customer may be unaware that a payee is actually considered a biller by his or her Pay provider and may enter a payment to a Fully Specified Payee by entering the payees complete name and address. The Pay provider may check additions or modifications to a customers Payee List against its biller database and convert the Fully Specified Payee to a biller payee if a match is detected. This checking may be performed when the Customer Payee is added or modified, or done in a background process, which converts the Fully-Specified payee to a Biller payee at some time after it is added to or modified on the payee list. The customer may obtain information about the payee conversion the next time a Customer Payee Inquiry message is sent, or when the client performs a Customer Payee Synchronization message to update its records. Payee type conversion to Fully Specified Payee may occur if a Biller terminates a relationship with the customers Pay provider. In this case, a Fully-Specified Payee aggregate may be substituted for the Biller ID in the Payee record on the customers Payee List.
7.1.1.5 Standard Payee Inquiry

Although the list of Standard Payees with contractual arrangements with a Pay provider may be very long, it is sometimes desirable for a client to search for a particular Standard Payee. A client may use the Standard Payee Inquiry <StdPayeeInqRq> message for this purpose. If the client finds a biller that the customer is interested in adding to the payee list, the client may add it simply by using the Customer Payee Add <CustPayeeAddRq> message with the Standard Payees Identifier <StdPayeeId>.
7.1.2Payments
7.1.2.1 Funding Accounts
The Pay Service uses the <DepAcctIdFrom> and <CardAcctIdFrom> aggregates to identify accounts as funding accounts for payment. When a customer schedules a Payment or creates a Recurring Payment Model, he or she specifies which account should be used as the funding account for that Payment, whether or not it is the default funding account. A user may activate multiple funding accounts for paying bills and making other payments. If a single funding account is specified during Service Activation, then the User Interface may use that funding account as a default account. The funding account must be specified in <PmtInfo> for each individual payment message .
7.1.2.2 Payment Processing Flow

When a customer decides to make a payment, several dates are important. The date he or she transmits the request to the server is the payment set-up date. The customer may, depending on the Pay Service Profile, either supply the payment processing date <PrcDt> or payment due date <DueDt> in the <PmtInfo> aggregate in the request. The processing date is the date by which the service must begin processing it for payment. In the case where a customers CPP actually provides payment support directly, the processing date is the date by which the CPP must retrieve the payment request from its warehouse, generate remittance data, and possibly initiate funds transfers. The processing date is not necessarily the same as the date the funds are withdrawn from the
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification customers funding account. The actual funds withdrawal date varies depending on who actually processes the funds transfer requests. The due date is the date the customers payment needs to be in the hands of the payee. The customer establishes the date when he or she scheduled the payment. If supported by the CSP model, the customer may enter the due date for a payment and the service must calculate the processing date. A customer processing date may be adjusted by a service for FI holidays and other non-processing days. A processing date may be adjusted either forward or backward depending on the Service Profile. Once the original processing date is adjusted, it is known as the adjusted processing date and must be the actual processing date. If a user interface or client wishes to allow a customer to enter a due date even though the CSP model is processing date, the client must calculate a processing date for the customer. To aid in that calculation, for each biller payee, <DaysToPay> is provided in <StdPayeeRec>. <DaysToPay> is the number of business days it takes for the CPP to deliver the payment to the payee. This data is provided by the CPP and is returned when the client uses a Standard Payee Inquiry to obtain the Standard Payees. For fully specified payees and transfer payees, the <DfltDaysToPay> (for Fully-Specified payees) and <DfltXferDaysToPay> (for Transfer Payees) are provided in the Service Profile. To be strictly accurate, a client would also need to know the SPs holidays, using <HolInqRs>, and nonprocessing day schedule, via Service Profile <PrcDaysOff>, as well. But in general, the client may subtract the number of business days it would take for payment to arrive (<DaysToPay>, <DfltDaysToPay> or <DfltXferDaysToPay> depending on payee type) from the entered due date, and use that as the processing date. Business day is another term for processing day (the inverse of the <PrcDaysOff> for an FI or its service provider). If the FI holidays were available, the client may also check for and adjust for holidays. Once a payment is processed, two deliveries take place: remittance data delivery and the funds delivery. Remittance data is information provided to payees about the payment, such as the customers name, address, the payment amount, and account number with the payee <BillingAcct>. The delivery mechanism for this data may be electronic, such as using the Remittance Add <RemitAddRq> message or another electronic delivery channel, or paper, and may be separate from the actual delivery of the funds. The funds delivery consists of a withdrawal from the customers funding account and a credit or deposit to the payees account or a designated account at a BPP for that payee. A payee may post a payment to the customers account <BillingAcct> either when they receive the remittance data or when they receive the funds, at the discretion of the payee. The date that posting occurs is called the Biller Posting Date and is reflected in IFX as the Effective Date <EffDt> associated with the Payment Status of Posted. The Biller Posting Date should ideally be earlier than or equal to the Due Date, although this is rarely guaranteed by a CPP due to variations in postal service and billers accounts receivables systems. Billers may consider the payment to be on-time if it is received by the Due Date, even if they require additional days to process and actually post the payment. If the billing cycle occurs prior to posting, such that the next bill is received without reflecting the prior payment, a customer care issue may arise. In order to facilitate customer care at the CSP/CPP, the biller may provide information to their BSP about the number of days they require to post an electronic payment after it is received <DaysToEPost>. The CSP may then retrieve this data from the BSP, using a Biller Inquiry. <DaysToEPost> is returned within <BillerRec>. If the payee was paid with a draft drawn on the customers actual funding account, then the funds withdrawal date mentioned above would be the date the debit cleared the customers account. However, if the drafts are drawn on an FI consolidation account or if the payee is being paid electronically, the funds may be withdrawn (to go into the consolidation account) at the banks discretion. This typically takes place once the CPP receives the funds transfer requests generated during payment processing. How a CPPs customers know when their funds are actually withdrawn is typically up to the CPP to disclose when the customer is signing up for the service.
April 2005
Version 1.7
P a y m e n t P r o c e s s in g F lo w
P a y m e n t S e tu p D a te
A d ju s te d /A c tu a l P r o c e s s in g D a t e
O r ig in a l P r o c e s s in g D a te
M o n e y D e liv e r y (F u n d s W ith d r a w a l D a te ) R e m it t a n c e D e liv e r y D a t e
M o n e y D e liv e r y ( D e p o s it D a t e )
B ille r P o s tin g D a te
D u e D a te
C h e c k C le a r e d D a t e
The diagram illustrates the flow of a payment using its significant event dates as briefly introduced in the earlier text. The dates on the right hand side represent floating events. For example, the Remittance Delivery may occur before Funds Withdrawal, before Deposit to the payee, or after the deposit to the payee. In the above diagram, the dates in bold are dates the customer usually cares about. In the service provider scenario, the customer cares about the Processing Date or Adjusted Processing Date because it may be the only date the service provider may supply about a processed/completed payment. Typically, service providers firmly know the Payment Setup Date, Processing Date, and Adjusted Processing Date. The other dates in the chart are usually only known by a service provider if the actual money or remittance delivery organization (such as the customers FI) notified the service provider of them. The same is also true for Biller Posting Date; i.e., a service provider would only know this date if it was supplied by the payees receiving payments and posting them to customer accounts <BillingAcct>. Due Date and Check Cleared Date are in italics to show they may or may not be of importance to the customer. Due Date may be of importance if the customer enters or is more comfortable with the Due Date model. Check Cleared Date is only of importance if the payment was made via paper check and if the customer is in dispute with their payee about proper credit being given them for a payment.
7.1.2.3 Payment Invoices for Businesses

The IFX Service allows a customer to indicate which invoices are included in a payment, including line item detail. A customer may create a payment that pays one or more invoices or may choose to pay specific line items from one or more invoices.
7.1.2.4 Recurring Payments

By specifying the normal parameters associated with a Payment (funding account, payee, amount, date, etc.) and adding a Recurring Message Detail aggregate, a client may define a Recurring Payment Model. The
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification Recurring Payment Model may be either closed-ended (with a specified total number of payments or last payment date) or open-ended (continue until canceled). Once a customer has defined Recurring Payment Models, the Pay provider must automatically generate payments based on those models at whatever frequency is specified in the Recurring Message Detail aggregate.
7.1.2.5 Payment Life Cycle and Payment Status

The IFX Specification contains a payment status reporting aggregate <PmtStatus> that is based on a typical payment life cycle. This life cycle may be described as follows: A payment is Scheduled, either by a customer using the Payment Add Request message or by the Pay provider using one of the customers Recurring Payment Models. Once scheduled, a customer may cancel a payment using the Payment Cancel Request message up until the time that payment is submitted for processing, resulting in a <PmtStatusCode> of Cancelled. A customer may request that a payment that has been generated from a recurring payment model be skipped (<PmtStatusCode> of Skip). Payment processing has a number of possible outcomes. A payment may be processed with a successful result. A Processed payment may be Returned. The payment may be posted, rejected or refused by the BPP or Biller, indicated by <PmtStatusCode> values of Posted, RemitRejected, or RemitRefused, respectively. Those Pay providers that request a Payment Authorization from the customers Financial Institution before payment may indicate additional payment states, such as PmtAuthRejected or PmtAuthHeld. Since a Pay provider may not have access to the customers bank account data, its records may show Processed as the final state for a successful payment. In the case where the Pay provider issues a paper check to a payee on behalf of the customer, the Pay provider may indicate to the customer the check has cleared (<PmtStatusCode> CheckCleared).
7.1.2.6 Additional Payment Information

Several elements are provided within the payment instruction to communicate other payment-related information back to the payee. These include the <BillRefInfo> and <Memo> elements, the <InvoiceInfo> aggregate, and the <PmtSummAmt> aggregate. The <BillRefInfo> element is biller-defined text from the bill summary that may be sent back with the payment to assist in the billers accounts receivable reconciliation. This may be equivalent to scanline information included with a billers paper remittance stub. Some payment processing systems currently handle a maximum of 22 characters for <BillRefInfo>, so an implementation must consider data truncation of larger inputs. The <Memo> element may be used by CPPs that convert electronic payment instructions into paper checks. The <InvoiceInfo> aggregate, like the <Memo> element, is information that may be delivered to the payee, either with the payment or through some other means, including email or as a separate paper item. This element may be used to allow a small business to identify, along with a payment, which invoices this payment pays and may include other characteristics such as discounts, credit adjustments, and/or free-form text. The <PmtSummAmt> aggregate is used to indicate additional information about the total payment amount, as specified by the <CurAmt> in <RemitInfo>. It is comprised of the <BillSummAmtId> and the associated currency amount <CurAmt>. The <BillSummAmtId> is obtained from the <BillInfo> on a presented bill and is a tag that identifies the payment category to the biller. This element is used to indicate which payment amount is being paid when multiple payable amounts were presented, or to allocate a supplemental payment to one or more categories, or to designate a breakdown of the total amount into sub-amount categories. Examples of how this data may be presented and used may be found in the text above the <BillInfo> aggregate (see Section Error: Reference source not found). Note:
April 2005
Version 1.7
7.2Pay Service Message Summary

Message / Message Name Service Profile Inquiry
Req.
Yes
Comments
Allows the client to retrieve a current view of the services supported by the SP, the Authentication Realms that must be used for authentication, and basic information about the SP. Allows a client to inquire about payees that are well known to the CPP, which may be used to assist customers in selecting payees to be added to the customers personal payee list <CustPayeeId>. Allows a client to reverse an action about payees.
Standard Payee Inquiry

<StdPayeeInqRq> <StdPayeeInqRs>
Standard Payee Reversal

<StdPayeeRevRq> <StdPayeeRevRs>
Customer Payee Add

<CustPayeeAddRq> <CustPayeeAddRs>
Allows a client to create a new Payee record on the customers Payee List. This Payee may be one of four types: a Biller Payee specified using <BillerPayee> aggregate, a standard payee specified using <StdPayeeId> aggregate, a Fully-Specified Payee using the <FSPayee> aggregate, or an Interbank Transfer Payee using the <XferPayee> aggregate. Allows a client to modify an existing Payee record on a customers Payee List.
Customer Payee Modify

<CustPayeeModRq> <CustPayeeModRs>
Customer Payee Type Modify

<CustPayeeTypeModRq> <CustPayeeTypeModRs>
Allows a CSP to request a change in a Customers Payee Type.
Customer Payee Delete

<CustPayeeDelRq> <CustPayeeDelRs>
Allows a client to delete an existing Payee record on a customers Payee List.
Customer Payee Inquiry

<CustPayeeInqRq> <CustPayeeInqRs>
Allows a client to view a summary of current Payee records associated with the current customer. (Payee List)
Customer Payee Audit

<CustPayeeAudRq> <CustPayeeAudRs>
Allows client to play back the Customer Payee messages associated with the current customer since some past point in time. Allows client to play back the Customer Payee messages associated with the current customer since some past point in time. Allows a client to create a new Payment associated with the current customer. The Payee is automatically added to the customers Payee List if it is not already there. Allows a client to modify pending Payment records.
Customer Payee Synchronization

<CustPayeeSyncRq> <CustPayeeSyncRs>
Payment Add
<PmtAddRq> <PmtAddRs>
Payment Modify
<PmtModRq> <PmtModRs>
Payment Status Modify

<PmtStatusModRq> <PmtStatusModRs>
Allows an SP to request a modification in the status of a Payment.
Version 1.7
April 2005
Message / Message Name Payment Cancel

<PmtCanRq> <PmtCanRs>
Req.
Comments
Allows a client to cancel pending Payment records.
Payment Status Advise

<PmtStatusAdviseRq> <PmtStatusAdviseRs>
Allows a client to advise an entity of a change in Payment Status
Payment Status Inquiry

<PmtStatusInqRq> <PmtStatusInqRs>
Allows a client to view Payment Status.
Payment Inquiry
<PmtInqRq> <PmtInqRs>
Allows a client to view pending Payment records.
Payment Reversal
<PmtRevRq> <PmtRevRs>
Allows a client to reverse the Payment messages associated with a current customer.
Payment Audit
<PmtAudRq> <PmtAudRs>
Allows a client to play back the Payment messages associated with the current customer since some past point in time. Note that an audit must return payment messages for both pending and completed payments. Allows a client to play back the Payment messages associated with the current customer since some past point in time. Note that a sync must return payment messages for both pending and completed payments. Allows a client to request a new Payment Authorization.
Payment Synchronization
<PmtSyncRq> <PmtSyncRs>
Payment Authorization Add

<PmtAuthAddRq> <PmtAuthAddRs>
Payment Authorization Modify

<PmtAuthModRq> <PmtAuthModRs>
Allows a client to modify existing Payment Authorization records.
Payment Authorization Cancel

<PmtAuthCanRq> <PmtAuthCanRs>
Allows a client to cancel existing Payment Authorization records.
Payment Authorization Inquiry

<PmtAuthInqRq> <PmtAuthInqRs>
Allows a client to view existing Payment Authorization records.
Payment Authorization Audit

<PmtAuthAudRq> <PmtAuthAudRs>
Allows a client to play back the Payment Authorization messages since some past point in time. Note that an audit must return payment messages for both pending and completed authorizations. Allows a client to play back the Payment Authorization messages since some past point in time. Note that a synchronization must return payment messages for both pending and completed authorizations. Allows a client to reverse the action on existing Payment Authorization records.
Payment Authorization Synchronization

<PmtAuthSyncRq> <PmtAuthSyncRs>
Payment Authorization Reversal

<PmtAuthRevRq> <PmtAuthRevRs>
April 2005
Version 1.7
Message / Message Name Remittance Add

<RemitAddRq> <RemitAddRs>
Req.
Comments
Allows a client to create a new Remittance object.
Remittance Modify
<RemitModRq> <RemitModRs>
Allows a client to modify existing Remittance records.
Remittance Status Modify

<RemitStatusModRq> <RemitStatusModRs>
Allows an SP to request a modification in the status of a Remittance Advice.
Remittance Delete
<RemitDelRq> <RemitDelRs>
Allows a client to delete existing Remittance records.
Remittance Inquiry
<RemitInqRq> <RemitInqRs>
Allows a client to view existing Remittance records.
Remittance Audit
<RemitAudRq> <RemitAudRs>
Allows a client to play back the Remittance messages since some past point in time. Note that an audit must return payment messages for both pending and completed remittances. Allows a client to play back the Payment messages since some past point in time. Note that a synchronization must return payment messages for both pending and completed remittances. Allows a client to reverse the action on Remittance records.
Remittance Synchronization
<RemitSyncRq> <RemitSyncRs>
Remittance Reversal
<RemitRevRq> <RemitRevRs>
Recurring Payment Model Add

<RecPmtAddRq> <RecPmtAddRs>
Allows a client to create a new Recurring Payment Model associated with the current customer. The first Payment may be generated when the Recurring Payment Model is added. The Payee is automatically added to the customers Payee List if it is not already there. Allows a client to generate a payment instance from a Manual frequency Recurring Payment Model.
Recurring Payment Instance Add

<RecPmtInstAddRq> <RecPmtInstAddRs>
Recurring Payment Model Modify

<RecPmtModRq> <RecPmtModRs>
Allows a client to modify a Recurring Payment Model associated with the current customer. Pending payments generated from the modified Recurring Payment Model may also be modified if supported by the Pay Provider. Allows a client to delete a Recurring Payment Model associated with the current customer. Pending payments generated from the deleted Recurring Payment Model may also be deleted. Allows a client to view a summary of Recurring Payment Models associated with the current customer.
Recurring Payment Model Cancel

<RecPmtCanRq> <RecPmtCanRs>
Recurring Payment Model Inquiry

<RecPmtInqRq> <RecPmtInqRs>
Recurring Payment Model Audit

<RecPmtAudRq> <RecPmtAudRs>
Allows a client to play back the Recurring Payment Model messages associated with the current customer since some past point in time.
Version 1.7
April 2005
Message / Message Name Recurring Payment Model Synchronization

<RecPmtSyncRq> <RecPmtSyncRs>
Req.
Comments
Allows a client to play back the Recurring Payment Model messages associated with the current customer since some past point in time. Allows a client to reverse the action on recurring payments.
Recurring Payment Model Reversal

<RecPmtRevRq> <RecPmtRevRs>
Payment Acknowledgement Inquiry

<PmtAckInqRq> <PmtAckInqRs>
Allows a client to retrieve acknowledgement of payments.
Payment Acknowledgement Reversal
Allows a client to reverse the action on acknowledgement of payments.
<PmtAckRevRq> <PmtAckRevRs>
Payment Acknowledgement Advise
Allows a client to advise on the acknowledgement of payments.
<PmtAckAdviseRq> <PmtAckAdviseRs>
Batch Checksum Add

<ChksumAddRq> <ChksumAddRs>
Used to provide information associated with the service and its summary control totals.
Batch Checksum Modify

<ChksumModRq> <ChksumModRs>
Used to modify information associated with the service and its summary control totals.
Batch Checksum Status Modify

<ChksumStatusModRq> <ChksumStatusModRs>
Used to modify the status related to information associated with the service and its summary control totals. Used to remove information associated with the service and its summary control totals.
Batch Checksum Delete

<ChksumDelRq> <ChksumDelRs>
Batch Checksum Inquiry

<ChksumInqRq> <ChksumInqRs>
Used to retrieve information associated with the service and its summary control totals.
Batch Checksum Audit

<ChksumAudRq> <ChksumAudRs>
Used to track the history of information associated with the service and its summary control totals.
Batch Checksum Synchronization

<ChksumSyncRq> <ChksumSyncRs>
Used to play back checksum messages associated with the service and its summary control totals.
Comprehensible Remittance Statement Add

<CompRemitStmtAddRq> <CompRemitStmtAddRs>
Allows a financial institution to transmit lockbox remittance information to a client for posting.
Comprehensible Remittance Statement Inquiry

<CompRemitStmtInqRq> <CompRemitStmtInqRs>
Allows a customer to inquiry about remittance information on a specific lockbox.
10
April 2005
Version 1.7
Message / Message Name Comprehensible Remittance Statement Audit

<CompRemitStmtAudRq> <CompRemitStmtAudRs>
Req.
Comments
Request to obtain all changes related to a particular comprehensible remittance.
Comprehensible Remittance Statement Synchronization

<CompRemitStmtSyncRq> <CompRemitStmtSyncRs>
Request to synchronize to a particular comprehensible remittance.
PmtBatch Add
<PmtBatchAddRq> <PmtBatchAddRs>
PmtBatch Modify
<PmtBatchModRq> <PmtBatchModRs>
PmtBatch Inquiry
<PmtBatchInqRq> <PmtBatchInqRs>
PmtBatch Cancel
<PmtBatchCanRq> <PmtBatchCanRs>
PmtBatch Delete
<PmtBatchDelRq> <PmtBatchDelRs>
PmtBatch Audit
<PmtBatchAudRq> <PmtBatchAudRs>
PmtBatch Sync
<PmtBatchSyncRq> <PmtBatchSyncRs>
PmtBatch Reversal
<PmtBatchRevRq> <PmtBatchRevRs>
PmtBatch Advise
<PmtBatchAdviseRq> <PmtBatchAdviseRs>
PmtBatch Status Modify

<PmtBatchStatusModRq> <PmtBatchStatusModRs>
PmtBatch Status Inquiry

<PmtBatchStatusInqRq> <PmtBatchStatusInqRs>
PmtBatch Status Advise

<PmtBatchStatusAdviseRq> <PmtBatchStatusAdviseRs>
Version 1.7
April 2005
11
7.3Pay Service Common Aggregates

7.3.1Standard Payee Record <StdPayeeRec>
Tag
<StdPayeeId>
Type
Usage
Required
Description
Customers Payee Identifier. The Standard Payee as known to the CPP. Standard Payee Information Aggregate
<StdPayeeInfo>
Required
7.3.1.1 Standard Payee ID <StdPayeeId>

The <StdPayeeId> aggregate is used to describe a Predefined Payee, such as a Biller. The <StdPayeeId> is the Biller as known by the CPP. <StdPayeeId> is a synonym of <BillerId>, which is the Biller identification as known by the Biller or BSP.
Tag
<SPName>
Type
Identifier
Usage
Required
Description
Service Provider Name. Used to qualify <BillerNum>. This is the name of the organization that assigned <BillerNum>, i.e., the CPP (or agent of the CPP). Biller Number. Assigned by the CPP.
<BillerNum>
Identifier
Required
7.3.1.2 Standard Payee Information <StdPayeeInfo>

Tag
<Name> <PostAddr>
Type
C-40 Aggregate see section 3.2.3.10.1 C-32 Aggregate see section 3.2.13 Long
Usage
Optional Optional
Description
Payee Name. Standard Payee Address Aggregate.
<AcctMask> <IndustId>
Account Mask. Zero or more edit masks to facilitate <BillingAcct> entry and editing. Industry Identifier
<DaysToPay>
Required
Days to Pay. Minimum number of business days needed to process. Assigned by the Pay provider. Cannot be changed by the client.
7.3.2Customer Payee Record Aggregate <CustPayeeRec>

Tag
<CustPayeeId>
Type
Identifier
Usage
Required
Description
Customers Payee Identifier. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. New Payee Information. This is an instance of <CustPayeeInfo> that provides information about the payee after any adjustment has been made
<CustPayeeInfo>
Required
12
April 2005
Version 1.7
Tag
<BillerContact>
Type
Aggregate see section 3.2.6.1 Long
Usage
Optional
Description
Biller Contact Information Aggregate.
<DaysToPay>
Required
Days to pay. Number of days required to complete the payment.
7.3.2.1 Customer Payee Information Aggregate <CustPayeeInfo>

The <CustPayeeInfo> aggregate is used in most messages related to Payees and is optionally used in <PmtAddRq> and <RecPmtAddRq> if a new Payment or Recurring Payment Model is being added for a new Customer Payee. Note: <Name> is optional in this aggregate. The following table provides guidelines for including <Name> within implementations.
Payee Type
Fully Specified Payee Transfer Payee Standard Payee Biller Payee
Usage
Required Recommended Recommended Required
Explanation
Required in order to issue the check. Recommended for problem resolution. Recommended for problem resolution. Required because it is always returned as part of <BillerRec>.
Tag
<Name>
Type
C-40
Usage
Description
Payee Name. Initially assigned by the customer when the Payee is added. May be modified by the client. Should contain Biller Name <BillerName> in the case of a Biller. For more information, see the above table. Does not affect the behavior of interbank transfer payments, but recommended usage is destination account name for interbank transfer payees.
<Nickname>
C-40
Optional
Payee Nickname. Optionally assigned by the customer. Server always echoes it in immediate response if received in a request. Pay provider may indicate support for longerterm storage of nicknames in the Service Profile. May be modified by the client. Standard Payee Identification Aggregate.
<StdPayeeId>
Aggregate see section 7.3.1.1 Aggregate see section 7.3.2.1.2 Aggregate see section 7.3.2.1.4 Aggregate see section 7.3.2.1.3 C-32
Required XOR Required XOR Required XOR Required XOR Optional
<FSPayee>
Fully-Specified Payee Aggregate.
<XferPayee>
Transfer Payee Aggregate.
<BillerPayee>
Biller Payee Aggregate.
<BillingAcct>
Customer Account Number with Payee. This is the customers identification with this Payee. For Transfer Payees, the account number for the target account is carried in the <XferPayee> aggegate, rather than in this element.
Version 1.7
April 2005
13
Tag
<AcctPayAcctId>
Type
Identifier
Usage
Optional
Description
Accounts Payable Account Identifier. Vendor Account Number with Customer (Payer). This is the payers Accounts Payable account number for reconciliation. Default Payment Information Aggregate. Used to add default payment information when adding a new payee. This would not be included when paying a bill unless the user was also adding a new payee at the same time.
<DfltPmtInfo>
Optional
7.3.2.1.1 Default Payment Information Aggregate <DfltPmtInfo>

Tag
<DepAcctIdFrom>
Type
Usage
Optional XOR Profiled support
Description
Deposit Account Aggregate. The default funding account must be used when the Payment definition does not specify the funding account. The client may modify the default funding account. Either <DepAcctIdFrom> or <CardAcctIdFrom> may be specified. A default funding account for bill presentment may be specified during service activation when used within <PmtInfo>. Card Account Identifier Aggregate. Used when the default funding account is a Card account.
<CardAcctIdFrom>
Aggregate see section 3.2.7.2.3 C-40 C-255
Optional XOR Profiled support Optional Optional
<Category> <Memo>
Default Category for Payments. May be modified by the client. Default Memo for Payments. May be modified by the client.
7.3.2.1.2 Fully-Specified Payee Aggregate <FSPayee>

The <FSPayee> aggregate is used to provide complete information about a Fully-Specified Payee.
Tag
<PostAddr>
Type
Aggregate see section 3.2.3.10.1 Aggregate see section 3.2.5.2 Aggregate see section 3.2.3.9 C-96 Aggregate see section 3.2.5.1.1
Usage
Required
Description
Payee Address Aggregate.
<OrgContact>
Required XOR Required XOR Optional Optional Repeating
Payee contact information.
<ContactInfo>
<LegalName> <OrgId>
Legal Name. The legal name of the Payee. Organization Identifier.
7.3.2.1.3 Biller Payee Aggregate <BillerPayee>

The <BillerPayee> aggregate is used to provide information for payment to a Biller.
14
April 2005
Version 1.7
Tag
<BillerId>
Type
Aggregate see section 8.3.1.2 Aggregate see section 3.2.6.1 Long
Usage
Required
Description
Biller Identification Aggregate.
<BillerContact>
Optional
Biller Contact Information.
<HistRetentionDays>
Optional
Number of days that Bill Summary and Bill Detail information is available for inquiries. The Bill Detail information may be available for a longer period of time. Biller Pay Information Aggregate.
<BillerPayInfo>
Optional
7.3.2.1.4 Transfer Payee Aggregate <XferPayee>

The <XferPayee> aggregate is used to provide complete information about a Transfer Payee.
Tag
<DepAcctIdTo>
Type
Aggregate
Usage
Required
Description
Deposit Account Aggregate. In this context, <DepAcctIdTo> specifies the target account for the transfer.
7.3.3Payment Record Aggregate <PmtRec>

Tag
<PmtId> <RecPmtId>
Type
Usage
Description
Payment Identifier. Assigned by the server at the time the Payment is first added. Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Returned if payment was generated from a Recurring Payment Model. Service Request Unique Identifier. The UUID of the service wrapper containing the payment. This is used to identify the batch in which the payment was sent. Payment Information Aggregate.
<SvcRqUID>
UUID
Optional
<PmtInfo>
Aggregate see section 7.3.3.1 Aggregate see section 7.3.4.1 Aggregate see section 7.3.4.2 Aggregate see section 7.3.4 Date Date
Required
<PmtStatus>
Required
Payment Status Aggregate.
<PmtRemitAck>
Optional
Payment Remittance (Credit) Acknowlegement Aggregate. Status record for the credit side of the payment transaction. Payment Remittance Information. The name and address to which a payment was actually remitted, if different than the name and address for the payee (typically, fully-specified payee). Message Date. Date payment was actually processed and entered history. Original Payment Processing Date.
<PmtRemitInfo>
Optional
<CreatedDt> <OrigPmtPrcDt>
Version 1.7
April 2005
15
Tag
<OrigPmtDueDt> <FIDebitTrcNum> <FICreditTrcNum> <CSPRefId>
Type
Date NC-7 NC-7 Identifier
Usage
Optional XOR Optional Optional Optional
Description
Original Payment Due Date. FI Debit Trace Number. FI Credit Trace Number. Customer Service Provider Reference Identifier. This is the <CSPRefId> of the message that created or last modified the payment. Service Provider Reference Identifier. This is the <SPRefId> of the message that created or last modified the payment.
<SPRefId>
Identifier
Optional
7.3.3.1 Payment Information Aggregate <PmtInfo>

The <PmtInfo> aggregate is used in most messages related to Payments and Recurring Payments.
Tag
<CurAmt> <LegalName> <PayerInfo>
Type
Currency Amount C-96 Aggregate see section 7.3.3.1.1
Usage
Optional Optional XOR Optional XOR
Description
Total Payment Amount. Total debit from funding account. Legal Name. The legal name of the account holder of the funding account. Payer Information. The information about the party that is the account holder of the funding account. Note: In IFX 1.3 or later, this aggregate takes precedence over <CustId> if both are present.
<RemitInfo>
Required Repeating but see Description Profiled support Required XOR Required XOR Optional Required XOR Profiled support Required XOR Profiled support Optional Profiled support Optional Optional
Remittance Information Aggregate.
Note: This aggregate may repeat only in IFX 1.1 or later when the server indicates support for it to repeat, via <OptSupt> = PmtMultiRemit.
Deposit Account Aggregate. The funding account for this payment. Card Account Identifier Aggregate. Used for card payments and transfers. Payment Category. The customer assigns categories. Payment Processing Date. The customer enters this date as the original requested processing date, not corrected for holidays and non-processing days. May be modified by the customer. Payment Due Date. The customer enters this date to represent the date the payment is due to arrive at the payee. May be modified by the customer. Immediate Payment Indicator. If set to True, the payment must be executed immediately, and not at end of day. Subject to support in Service Profile. Foreign Exchange Deal Identifier (Committed deals). Payment reference identifier. Identifier for the payment generated by the Payer, generally in the Accounts Payable system.
<DepAcctIdFrom>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 C-40 Date
<CardAcctIdFrom>
<Category> <PrcDt>
<DueDt>
Date
<ImmediatePmt>
Boolean
<ForExDealId> <PmtRefId>
16
April 2005
Version 1.7
7.3.3.1.1 Payer Information Aggregate <PayerInfo>

The <PayerInfo> aggregate provides complete information about a Payer.
Tag
<PersonInfo>
Type
Aggregate see section 3.2.4.1 Aggregate see section 3.2.5.1.2 Aggregate see section 3.2.5.1.1
Usage
Description
Person Information. Personal funding-account holder information. Organization Information. Organization funding-account holder information. Organization Identifier. Organizatization funding-account holder ID.
<OrgInfo>
<OrgId>
7.3.4Payment Remittance Information <PmtRemitInfo>

Tag
<Name> <PostAddr>
Type
Usage
Optional Optional
Description
Payment Remittance Name. The name of the organization to which the payment was remitted. Postal Address Aggregate.
7.3.4.1 Payment Status Aggregate <PmtStatus>

The <PmtStatus> is returned in responses to Add or Modify Payment and Add or Modify Recurring Payment Model.
Tag
<PmtStatusCode>
Type
Closed Enum
Usage
Required
Description
Payment Status Code. This identifies the payment processing status. Valid values: Scheduled, Processed, FundAcctDebited, Skipped, Cancelled, Failed, PmtAuthHeld, PmtAuthNoFunds, PmtAuthInactive, PmtAuthClosed, Posted, CheckCleared, Returned, RemitPending, RemitRefused, RemitRejected
Status Description. Explanatory text associated with this status. Payment Status Date. The date associated with the state change to the current state. Status Modified By. If present, indicates who modified the Payment Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<PmtAuthId>
Identifier
Optional
Payment Authorization Identifier. If present, payment authorization was obtained for the payment and the authorizing SP assigned this identifier. If omitted, no authorization was obtained.
Version 1.7
April 2005
17
Tag
<RemitId>
Type
Identifier
Usage
Optional
Description
Remittance Idenitifier. If present, indicates the identifier of the remittance advice associated with this payment. May apply for <PmtStatusCode> of Posted, RemitPending, RemitRejected, or RemitRefused Recurring Payment Modified Indicator. Required to be True if a <PmtModRq> has subsequently modified a payment generated from a Recurring Payment Model so that it no longer matches the Recurring Payment Model. This may only be supplied for recurring payment instances. Payment Authorization Count. For Pay providers that require an authorization from the customers CPP. This is the number of times that the payment has been submitted for authorization. Payment Method. Indicates how the payment was transmitted to the payee; e.g., via check or electronically. Defined values: Check, Electronic, ACH, FedNet, SWIFT, CHIPS, CHAPS, BookEntry, Draft
<RecPmtMod>
Boolean
Optional
<PmtAuthCount>
Long
Optional
<PmtMethod>
Open Enum
Optional
<ChkNum>
NC-12
Optional
Check Number. Assigned by the Pay provider or the CPP if payment is by paper check.
<Memo>
C-255
Optional
Memo. Intended to be optionally used by a CPP to store any necessary text associated with the payment.
7.3.4.2 Payment Remittance Acknowldegement Aggregate <PmtRemitAck>

Contains information about the credit side of the payment transaction status. Includes information such as the total transaction fee charged to the payer, Checksum control total of successful or failed credit transactions, and individual credit transaction status.
Tag
<TotalFeeCharge>
Type
Aggregate see section 7.3.4.2.1 Aggregate
Usage
Optional
Description
Total Fee Charge. Total fees charged to the Payer for successful credit transactions remitted to (multiple) payees. Payment Remittance Acknowledgement Information. Information about the status of payment credit transactions.
<CompositePmtRemitInfo>
Required Repeating
7.3.4.2.1 Total Fee Charge <TotalFeeCharge>

Tag
<Count>
Type
Long
Usage
Required
Description
Transaction Count. Indicates the number of successfully transacted credit transactions for which the Payee was charged. Currency Value Sum. Indicates the total fee charged for successfully transacted payment credit transactions.
<CompositeCurAmt>
Required
18
April 2005
Version 1.7
7.3.4.2.2 Composite Payment Remittance Acknowledgement Information <CompositePmtRemitInfo>

Tag
<PmtRemitChksum>
Type
Aggregate see section 7.3.4.2.2.1 Aggregate see section 7.3.4.2.2.3
Usage
Optional
Description
Payment Remittance (Credit) Checksum Control Record. Payment Remittance (Credit) Detail.
<PmtRemitDetail>
Optional Repeating
7.3.4.2.2.1 Payment Remittance Checksum Control Record <PmtRemitChksum>

Tag
<AckType>
Type
Open Enum
Usage
Required
Description
Acknowledgement Type. Sent by the CPP indicating the state of the transaction processing. Defined values: Accepted, Rejected, Pending
<Count>
Long
Required
Transaction Count. Indicates the number of transactions associated with the acknowledgement type. Currency Value Sum. References the accumulated amount associated with the acknowledgement type. Memo. Text associated with the acknowledgement type. CPP Contact Information. Information on how the customer can contact the CPP regarding the trancation set associated with the acknowledgement type.
<TotalCurAmt> <Memo> <CompositeContactInfo>
Currency Amount C-255 Aggregate see section 3.2.3.8
7.3.4.2.2.2 7.3.4.2.2.3 Payment Remittance Detail <PmtRemitDetail>

Tag
<PmtRemitRefId> <CurAmt>
Type
Identifier Currency Amount Aggregate see section 7.3.4.3
Usage
Required Required
Description
Payment Remittance (Credit) Reference Transaction Identifier. Assigned by the client application. Currency Amount. References the amount of the Payment Remit (credit) fo rthe acknowledgement type. Payment Remittance Status.
<PmtRemitStatus>
Optional
7.3.4.3 Payment Remittance Status Aggregate <PmtRemitStatus>

Tag
<PmtRemitStatusCode>
Type
Closed Enum
Usage
Required
Description
Payment Remittance Status Code. Identifies the Payment Remittance (Credit) status of a payment. Valid Values: Accepted, Rejected, Pending
Version 1.7
April 2005
19
Tag
Type
Usage
Description
Status Description. Explanatory text associated with the status. Processing Status Date. Date associated with the status change. Status Modified By. Indicates who modified the Payment Remittance Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<Memo>
C-255
Optional
Memo. Text associated with the Payment Remittance Status.
7.3.4.4 Recurring Payment Record <RecPmtRec>

Tag
<RecPmtId> <PmtInfo>
Type
Identifier Aggregate see section 7.3.3.1 Aggregate see section 3.2.11.1 Long
Usage
Required Required
Description
Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Payment Information Aggregate.
<RecModelInfo>
Required
<RemainingInsts>
Required
Remaining Instance Count. The server must calculate this number as the number of actual payments to be made plus the number of instances to skip. Server must calculate on <RecPmtAddRq> and return in response. Server must recalculate in case of an <RecPmtModRq> that changes <RecSeriesEnd> or when a payment is spawned. The server is not required to generate a <RecPmtModRs> on each change to <RemainingInsts>.
7.3.5Payment Authorization Record Aggregate <PmtAuthRec>

Tag
<PmtAuthId> <PmtAuthInfo>
Type
Usage
Required Required
Description
Payment Authorization Identifier Payment Authorization Information Aggregate.
<PmtAuthStatus>
Required
Payment Authorization Status Aggregate
7.3.5.1 Payment Authorization Information Aggregate <PmtAuthInfo>

Tag
<DepAcctIdFrom>
Type
Usage
Required XOR
Description
Deposit Account Aggregate. The funding account for this payment.
20
April 2005
Version 1.7
Tag
<CardAcctIdFrom>
Type
Aggregate see section 3.2.7.2.3 Currency Amount C-80
Usage
Required XOR Required Optional
Description
Card Account Identifier Aggregate. Used for card payments and transfers. A funding account must be specified. Currency Amount. The amount of funds being requested for a payment authorization. Payee name.
<CurAmt> <Name>
7.3.5.2 Payment Authorization Status Aggregate <PmtAuthStatus>

Tag
<PmtAuthStatusCode>
Type
Open Enum
Usage
Required
Description
Payment Authorization Status Code Valid Values are: Authorized, Cleared, Expired
<StatusDesc> <EffDt> <ExpDt>
C-255 DateTime DateTime
Status Description. Explanatory text associated with this status. Effective Date. Effective date of this status. Expiration Date. Expiration date of this status. For example, the value of Authorized for <PmtAuthStatusCode> may only be valid for a limited amount of time. Status Modified By. If present, indicates who modified the Status Code. Defined values: FI
<StatusModBy>
Open Enum
Optional
7.3.6Remittance Record Aggregate <RemitRec>

Tag
<RemitId> <RemitInfo>
Type
Usage
Required Required
Description
Remittance Identifier. Assigned by the server at the time the Remittance is first added. Remittance Record Aggregate.
<RemitStatus>
Required
Remittance Status Aggregate.
7.3.6.1 Remittance Information Aggregate <RemitInfo>

The <RemitInfo> aggregate is used in most messages related to Remittance of Payments and Recurring Payments. <RemitInfo> contains the elements that pertain to remittance.
Tag
<RemitInstruction>
Type
Usage
Optional
Description
Remit instruction. Specifies the remittance delivery instruction, delivery method and provide remit advice codes for reconciliation process to link the payments and remittance advice. Payment/Settlement information.
<SettlementInfo>
Optional
Version 1.7
April 2005
21
Tag
<CounterpartyInfo>
Type
Aggregate see section 7.3.9.1 Aggregate see section 6.3.34.1 URL Identifier
Usage
Optional
Description
Counterparty Information Aggregate.
<ChkInfo>
Optional
Check information.
<ChkURL> <CustPayeeId>
Optional Required XOR Required XOR
URL location to obtain an image of the check. Customer's Payee Identifier. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. Payee Information Aggregate. Must be used if <CustPayeeId> is unassigned.
<CustPayeeInfo>
The following structure is for use in IFX 1.0.1 or later. Either this structure, or the one following it, may be used, but not both. This structure will be deprecated in IFX 2.0.
<BillRefInfo> NC-80 Optional Biller Reference Information. Biller-defined text from <BillRec>, for the billers Accounts Receivable reconciliation. Depending on the Payment Provider and the payment network and message used to make the payment, <BillRefInfo> may be truncated to 22 characters. <BillId> UUID Optional Bill Identifier. Bill Service Provider defined universally-unique identifier, to be provided if the payment is related to an IFXpresented bill. Payment Identifier. The identifier of the payment associated with this remittance. This is included to enable the BPP to inform the CPP of payment posting against this remittance. Memo for Payment. From Customer to Payee. Depending on the Payment Provider and the payment network and message used to make the payment, <Memo> may be truncated or dropped. <BillingAcct> C-32 Optional but see Description Required Optional Repeating Optional Repeating Customer Account Number with Payee. Required if the Service Provider does not support <CustPayeeId>. Inclusion here must not modify the <BillingAcct> at the CPP. Currency Amount. The total amount being paid. Payment Summary Amount. Used to designate the identifier for the amount being paid, or to specify the allocation of the total amount being paid or a portion of the total amount. Invoice Information Aggregate. Provides information about which Invoices and optionally Line Items are paid by this payment. The amount of the payment is always <CurAmt> above, which may or may not match the total of invoices or line items listed here.
<PmtId>
Identifier
Optional
<Memo>
C-255
Optional
<CurAmt> <PmtSummAmt>
Currency Amount Aggregate see section 7.3.6.1.1 Aggregate see section 7.3.7
<InvoiceInfo>
The following structure is for use in IFX 1.1.0 or later. Either this structure, or the one preceding it, may be used, but not both. This structure will replace the above structure, which will be deprecated in IFX 2.0.
<RemitDetail> Aggregate see section 7.3.6.2.1 Identifier Required Repeating Optional Remittance detail information aggregate.
<PmtId>
Payment Identifier. The identifier of the payment associated with this remittance. This is included to enable the BPP to inform the CPP of payment posting against this remittance.
22
April 2005
Version 1.7
Tag
<RefInfo>
Type
Aggregate see section 3.2.17 Currency Amount Identifier Aggregate see section 7.3.6.2.6
Usage
Optional Repeating Required Optional Optional
Description
Reference information associated with a payment information generated by the payment application. Currency Amount. The total amount being credited to the payees account. Payment Remittance (Credit) Reference Transaction Identifier. Payment Legal Reporting. For cross border payments in some foreign countries, it is sometimes mandatory to provide legal reporting information to the foreign central bank. This aggregate contains the information to satisfy the legal reporting requirement for payments to foreign payees. It is the responsibility of the reporting party (payer or payee) to pass the payment legal reporting information to CPP for CPP to forward to Central Bank. This information may be pass from the payer to CPP. CPP may then pass it to the countrys central bank. CPPs should not modify the information in this aggregate. Following are some countries in which this aggregate is used: Austria, Belgium, Germany, Denmark, Finland, Japan, Netherlands, Norway, and Sweden.
<CurAmt> <PmtRemitRefId> <PmtLegalRpt>
7.3.6.1.1 Payment Summary Amount Aggregate <PmtSummAmt>

Tag
<BillSummAmtId>
Type
Identifier
Usage
Required
Description
Bill Summary Amount Identifier. Billers identifier for this currency amount, which is obtained in the <BillInfo> for a presented bill. The consumer can return this in the payment messages to identify to the biller the type of amount being paid or allocated by the consumer. Currency Amount. Used to specify the amount being associated with the identifier specified by <BillSummAmtId>. This may be the same as the total amount being paid or a portion of the total amount (such as a supplemental payment amount or sub-amount allocation).
<CurAmt>
Currency Amount
Required
7.3.6.2
7.3.6.2.1 Remittance Detail Information Aggregate <RemitDetail>
Tag
<InvoiceReceiver>
Type
Aggregate see section 7.3.6.2.5 Aggregate see section 7.3.6.2.4 Currency Amount
Usage
Optional
Description
Invoice/credit memo receiver
<InvoiceSender>
Optional
Invoice/credit memo sender
<CurAmt>
Payment Currency Amount. Total amount being paid on behalf of subsidiary account. This element must be present if <RemitDetail> is repeating.
Version 1.7
April 2005
23
Tag
<PmtSummAmt>
Type
Aggregate see section 7.3.6.1.1 Aggregate see section 3.2.17 NC-80
Usage
Description
Payment Summary Amount. Used to designate the identifier for the amount being paid, or to specify the allocation of the total amount being paid or a portion of the total amount. Reference Information Aggregate. Identification information, typically supplied by the customer, used to correlate the bank account transaction to an associated <XferInfo> or <RemitInfo> sent by the client. Biller Reference Information. Biller-defined text from <BillRec>, for the billers Accounts Receivable reconciliation. Depending on the Payment Provider and the payment network and message used to make the payment, <BillRefInfo> may be truncated to 22 characters. Invoice Sender Reference Information.
<RefInfo>
<BillRefInfo>
Optional
<BillId>
UUID
Optional
Bill Identifier. Bill Service Provider defined universally-unique identifier, to be provided if the payment is related to an IFXpresented bill. Memo for Payment. From Customer to Payee. Depending on the Payment Provider and the payment network and message used to make the payment, <Memo> may be truncated or dropped.
<Memo>
C-255
Optional
<BillingAcct>
C-32
Customer Account Number with Payee. Account Reference information supplied by the Payee to the Payer. Required if the Service Provider does not support <CustPayeeId>. Inclusion here must not modify the <BillingAcct> at the CPP. Invoice Information Aggregate. Provides information about which Invoices and optionally Line Items are paid by this payment. The amount of the payment is always <CurAmt> above, which may or may not match the total of invoices or line items listed here.
<InvoiceInfo>
Optional Repeating
7.3.6.2.2 7.3.6.2.3 Remittance Instruction <RemitInstruction>

The Remittance Instruction aggregate specifies the remittance delivery method, and remit advice codes for reconciliation process to link the payments and remittance advice.
Tag
<RemitRefId>
Type
Identifier
Usage
Optional
Description
Remittance reference identifier. Remittance reference identifier generated for the payment, generally in the Accounts Payable system. Remit reference identifier links a payment and a remittance, and is used to re-join the two information streams when remittance and payment travel separately. Payment reference identifier. The Payee payment reference number generated by the payer associated with the payment, generally in the Accounts Payable system. Remittance Delivery Instruction. Instruction specifies the responsible party to generate the remittance if the payment and the remittance are to be separated. Define Value: CPPDeliver, CSPDeliver, PayerDeliver.
<PmtRefId>
Identifier
Optional
<DeliveryInstruction>
Open Enum
Optional
<DeliveryMethod>
Open Enum
Optional
Remittance Delivery Method. Defined Values: Fax, Email, EDI, Post, URL
24
April 2005
Version 1.7
Tag
<ContactInfo>
Type
Usage
Optional
Description
Remittance contact information. In the case that contact info is needed, may be used in the case the remittance is sent separately from the payment.
7.3.6.2.4 Invoice Sender Aggregate <InvoiceSender>

The Invoice Sender Aggregate describes the Invoice or credit memo sender, which is the organization or person who receives the credit for the payment on the invoice.
Tag
<OrgId>
Type
Usage
Required
Description
Organization Identifier.
<OrgInfo>
Optional
Organization Identifier Information Aggregate.
<PostAddr>
Optional
Invoice Senders Postal Address.
<AcctPayAcct>
Optional
Accounts Payable Account identifier. Vendor Account Number assigned by Customer (Payer). This is the payers Accounts Payable account number for reconciliation.
7.3.6.2.5 Invoice Receiver Aggregate <InvoiceReceiver>

The Invoice Receiver Aggregate describes the invoice or credit memo receiver, which is the organization or person who owns the liability of the invoice.
Tag
<OrgId>
Type
Usage
Required
Description
Organization Identifier.
<OrgInfo>
Optional
Organization Identifier Information Aggregate.
<PostAddr>
Optional
Invoice Receivers Postal Address.
7.3.6.2.6 Payment Legal Reporting Aggregate <PmtLegalRpt>

For cross border payments in some foreign countries, it is sometimes mandatory to provide legal reporting information to the foreign central bank. This aggregate contains the information to satisfy the legal reporting requirement for payments to foreign payees. It is the responsibility of the reporting party (payer or payee) to pass the payment legal reporting information to CPP for CPP to forward to Central Bank. This information may be pass from the payer to CPP. CPP may then pass it to the countrys central bank. CPPs should not modify the information in this aggregate. Following are some countries in which this aggregate is used: Austria, Belgium, Germany, Denmark, Finland, Japan, Netherlands, Norway, and Sweden.
Version 1.7
April 2005
25
Tag
<OrgInfo>
Type
Usage
Required
Description
Legal reporting organization information. Information about the entity that is obligated to send the notification to central bank about a payment to a foreign payee. This entity could be the invoice receiving organization or the paying organization, depending on different foreign country regulation. Organization Identifier. This is the tax identifier as required in legal reporting. ISO code of the residual country of the payee. Payment Currency Amount. Total amount being paid to Payee. Payment Processing Date. The customer enters this date as the original requested processing date. Detail information for legal reporting.
<OrgId>
Aggregate see section 3.2.5.1.1 NC-3 Currency Amount Date Aggregate see section 7.3.6.2.6.1
Optional
<PayeeCountry> <CurAmt> <PrcDt> <PmtLegalRptData>
Required Optional Optional Required Repeating
7.3.6.2.6.1 Payment Legal Reporting DataAggregate <PmtLegalRptData>

Tag
<LegalRptCode> <SupplRptCode> <Desc> <Memo> <SupplyingCountry> <CurAmt>
Type
C-36 C-36 C-80 C-255 NC-3 Currency Amount Date
Usage
Required Optional Optional Optional Optional Required
Description
Country specific code given by the central bank. Example: T015L-LVAWU Supplemental country dependent code. Could be more detail or could be another code. Description for additional information to the legal reporting code. Memo for Legal Reporting. From Customer to Central Bank. ISO code of the country from which goods or services come. Currency Amount. Amount Paid to supplying country on invoice. The Payer provides this amount to the CPP. CPP will pass this to central bank. CPP do nothing with this amount. Date the goods or services are imported.
<ImportDt>
Optional
7.3.6.3 Remittance Status Aggregate <RemitStatus>

Tag
<RemitStatusCode>
Type
Closed Enum
Usage
Required
Description
Remit Status Code. This identifies the remittance status. Valid values: Pending, Posted, Refused, Rejected, Returned, DelPend, Deleted
<StatusDesc> <EffDt>
C-255 DateTime
Optional Required
Status Description. Explanatory text associated with this status. Processing Status Date. The date associated with the state change to the current state.
26
April 2005
Version 1.7
Tag
<StatusModBy>
Type
Open Enum
Usage
Optional
Description
Status Modified By. If present, indicates who modified the Remit Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<Memo>
C-255
Optional
Memo. Intended to be optionally used by a BPP to store any necessary text associated with the remittance status.
7.3.7Invoice Information Aggregate <InvoiceInfo>

Tag
<InvoiceType>
Type
Open Enum
Usage
Optional
Description
Invoice Type. Defined values:Invoice, CreditMemo
<InvoiceNum> <RefInfo>
C-32 Aggregate see section 3.2.17 Currency Amount Currency Amount DateTime C-80 C-80
Required Optional Repeating Required Optional Required Optional Optional
Invoice Number. The client enters this identifier since it does not serve as a database key on the server. Reference Information. Additional Invoice reference. Used to unique identify an invoice for either country-specific or company-specific system tracking and reconciliation. Invoice Due Currency Amount. Invoice Paid Currency Amount. Invoice Date. Invoice Description. Invoice Voucher Number. The invoice recipients internal voucher number confirming receipt of the goods listed on the invoice. Invoice Fee(s), such as late fees, etc.
<TotalCurAmt> <PaidCurAmt> <EffDt> <Desc> <InvoiceVouchNum>
<Fee>
Aggregate see section 3.2.16.2 Currency Amount Aggregate see section 7.3.7.2 Aggregate see section 3.2.16.3 Aggregate see section 7.3.8 Aggregate see section 7.3.9
<InvoicePremium> <Discount>
Invoice Premium. Discount Information Aggregate.
<TaxInfo>
Optional
Tax Aggregate.
<InvoiceAdj>
Optional
Adjustment Aggregate.
<InvoiceLineItem>
Optional Repeating
Invoice Line Item Aggregate.
7.3.7.1.1
Version 1.7
April 2005
27
7.3.7.2 Discount Aggregate <Discount>

Tag
<Rate> <CurAmt> <EffDt> <Desc>
Type
Decimal Currency Amount DateTime C-80
Usage
Required XOR Required XOR Optional Optional
Description
Discount Percentage. Discount Currency Amount. Discount Date. Discount Description.
7.3.8Invoice Adjustment Aggregate <InvoiceAdj>

Tag
<InvoiceAdjNum> <AdjType>
Type
C-32 Open Enum
Usage
Optional Optional
Description
Adjustment Number. Adjustment Type. This element describes the reason for the adjustment. Defined values: Return, Damage
<CurAmt> <EffDt> <Desc>
Currency Amount DateTime C-80
Adjustment Currency Amount. Adjustment Date. Adjustment Description. This is often a text representation of <AdjType>.
7.3.9Invoice Line Item Aggregate <InvoiceLineItem>

Tag
<InvoiceLineItemNum> <AdjType>
Type
C-12 Open Enum
Usage
Required Optional
Description
Line Item Number Adjustment Type. This element describes the reason for the adjustment. Defined values: Return, Damage
<CurAmt> <Desc>
Currency Amount C-80
Required Optional
Line Item Amount. Line Item Description.
7.3.9.1 Counterparty Information Aggregate <CounterpartyInfo>

The Counterparty Information aggregate <CounterpartyInfo> contains information regarding the source (originator) party of the transaction posted on the account.
Tag
<LegalName>
Type
C-96
Usage
Optional
Description
Legal Name. Used by entities like trusts, or businesses in the case where an individual is doing business as a company. Name of payor of funds. Reference Information Aggregate. References unique to the counterparty of the transaction.
<RefInfo>
Optional Repeating
28
April 2005
Version 1.7
Tag
<DepAcctId>
Type
Usage
Description
Deposit Account Identification Aggregate
<CardAcctId>
Card Account Identification Aggregate
<LoanAcctId>
Loan Account Identification Aggregate
7.3.10
Tag
Checksum Record Aggregate <ChksumRec>

Type
Usage
Required Required
Description
Checksum Identifier. Assigned by the server at the time the Payment is first added. Checksum Information Aggregate.
<ChksumId> <ChksumInfo>
<ChksumStatus>
Required
Checksum Status Aggregate.
7.3.10.1 Checksum Information Aggregate <ChksumInfo>

The Checksum Information <ChksumInfo> aggregate provides information about the payment file and its summary control totals. These control totals provide information necessary for the server to verify the data contained in a Pay Service Request <PaySvcRq>.
Tag
<RefInfo>
Type
Usage
Optional
Description
Payment transaction reference Identifier number. Identifier for the payment file generated by the client. Checksum Message Type. Message type of transaction being calculated for the checksum. Defined values: All IFX Add and Mod Messages. Example: PmtAddRq, RemitAddRq, etc.
<MsgType>
Required
<Count> <Chksum>
Long Aggregate see section 7.3.10.1.1
Required Optional Repeating
Transaction count. This count indicates how many request messages should be contained in the file or <PaySvcRq>. Checksum data. Define different types of Checksum and values for verification of control Checksum totals with file transactions. Example: transaction amount sum, account Id sum or bank Id sum (foreign payment transactions).
7.3.10.1.1 Checksum Aggregate <Chksum>

Tag
<ChksumType>
Type
Open Enum
Usage
Required
Description
Checksum type identifier. Defined values: Sum, Hash, Mod, etc.
Version 1.7
April 2005
29
Tag
<ChksumValue>
Type
Decimal
Usage
Required
Description
Value of checksum type <ChksumType>. Example, if used for the sum, <ChksumValue> contains the total amount of all payment transactions of the file, without currency implication. Thus it contains the total of all <CurAmt>s in all <RemitInfo>s of the associated <PaySvcRq>, reflecting all payment items in the file.
7.3.10.2 Checksum Status Aggregate <ChksumStatus>

The Checksum Status <ChksumStatus> is returned in responses to Add or Modify Checksum.
Tag
<ChksumStatusCode>
Type
Open Enum
Usage
Required
Description
Chksum Status Code. This identifies the checksum status. Defined values: Pending, Posted, Refused, Rejected, Returned, DelPend, Deleted
Status Description. Explanatory text associated with this status. Status Date. The date associated with the state change to the current state. Status Modified By. If present, indicates who modified the Remit Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<Memo>
C-255
Optional
Memo. Intended to be optionally used by a BPP to store any necessary text associated with the Checksum Control status.
7.3.11
Tag
Comprehensible Remittance Statement Record Aggregate <CompRemitStmtRec>

Type
Identifier
Usage
Required
Description
Comprehensible Remittance Statement Identifier Aggregate. Assigned by the server at the time the Comprehensible Remittance Statement is first added. Comprehensible Remittance Statement Information Aggregate. Comprehensible Remittance Statement Status.
<CompRemitStmtId>
<CompRemitStmtInfo>
Required
<CompRemitStmtStatus>
Required
7.3.11.1 Comprehensible Remittance Statement Information Aggregate <CompRemitStmtInfo>

Tag
<LockboxDepId>
Type
Usage
Optional XOR
Description
Lockbox Deposit Identifier. A unique identifier assigned to a specific lockbox where deposits are collected.
30
April 2005
Version 1.7
Tag
<DepAcctId>
Type
Aggregate see section 3.2.7.2.2 Currency Amount Long Aggregate see section 3.2.17 DateTime Aggregate see section 7.3.11.1.2 URL
Usage
Optional XOR Required Optional Optional
Description
Deposit Account Id Aggregate. Deposit account for remittanc etransactions. Currency Amount. Total amunt of the remittance deposit cycle. Count. Total number of batches processed in the remittance cycle. Reference information associated with remittance deposit information. Processing Date. The date the remittance payments were processed by the financial institution. Batch Information Aggregate. One or more batches may be processed within a remittance deposit. Lockbox URL. URL containing lockbox remittance information.
<CurAmt> <Count> <RefInfo>
<PrcDt> <BatchInfo>
Required Optional Repeating Optional
<LockboxURL>
7.3.11.1.1 Lockbox Deposit Identifier Aggregate <LockboxDepId>

Tag
<LockboxAcctId> <DepAcctId>
Type
Usage
Required Optional
Description
Lockbox Account Identifier. Assigned by FI to identify lockbox to customer, i.e., PO Box number at post office Deposit Account Id Aggregate. Deposit account for lockbox transactions.
7.3.11.1.2 Batch Information Aggregate <BatchInfo>

Tag
<RefInfo>
Type
Aggregate see section 3.2.17 Currency Amount Long Aggregate see section 7.3.6.1
Usage
Optional
Description
Reference Information Aggregate. Reference information associated with remittance information. Currency Amount. Total amount of the remittance deposit cycle. Transaction count. Indicates the number of request messages contained in the file or <PaySvcRq>. Remittance Record Aggregate.
<CurAmt> <Count> <RemitInfo>
Required Required Required Repeating
7.3.11.2 Comprehensible Remittance Statement Status Aggregate <CompRemitStmtStatus>

Tag
<CompRemitStmtStatusCode>
Type
Closed Enum
Usage
Required
Description
Comprehensible Remittance Status Code. Values: Pending, Deposited, Rejected
Version 1.7
April 2005
31
Tag
Type
Usage
Description
Status Description. Explanatory text associated with the comprehensible remittance status. Effective Date/Time. The date/time the status code took effect. Status Mod By. Indicates who modified the status. Defined Values: CSP, FI
7.3.12
Payment Status Record Aggregate <PmtStatusRec>
The <PmtStatusRec> contains information regarding the status of the payment at the CPP or the Payment Network.
Tag
<PmtId> <PmtStatus>
Type
Identifier
Usage
Required Required
Description
Payment Identifier. The identifier of the payment matching the selection criteria of the request. Payment Status Aggregate.
<PmtRefId>
Optional
Payment reference identifier. Identifier for the payment generated by the client. It can be the document generated by the Payers Accounts Payable system, or it can be the identifier generated in the payment request (same as the <RqUID> of the <PmtAddRq>).
Note: If CPP uses the AddRq or InqRq message to push acknowledgement to client, there is no place to echo back the <RqUID> from the <PmtAddRq>, so this <PmtRefId> is required for client to link the status back to the original payment request.
<SvcRqUID> UUID Optional Service Request Identifier. The payment service request identifier that was created and sent by the client to the CPP. Network Transaction Information Aggregate. Contains transaction identifiers for the network that processed the payment. CPP Remittance contact information. In the case that contact info is needed, may be used in the case the URL is needed to link the customer back to the CPP site for additional information about the service or transaction. Remittance is sent separately from the payment. Payment Remittance (Credit) Status Record Aggregate.
<NetworkTrnInfo>
Optional
<CompositeContactInfo>
Optional
<PmtRemitAck>
Optional Repeating
7.3.13
Payment Acknowledgement Record Aggregate <PmtAckRec>
The <PmtAckRec> contains acknowledgment records at a consolidated or summarized level applicable to a <SvcRqUID>, or batch of payments submitted by the customer.
32
April 2005
Version 1.7
Tag
<SvcRqUID>
Type
UUID
Usage
Required
Description
Service Request Identifier. The payment file identifier that was created by the payer in the Accounts Payable system when the file is created and sent. Payment Acknowledgement Information Aggregate.
<PmtAckInfo>
Required Repeating
7.3.13.1 Payment Acknowledgement Information Aggregate <PmtAckInfo>

Tag
<PmtStatusCode>
Type
Closed Enum
Usage
Required
Description
Payment Status Code. This identifies the payment processing status. Valid values: Scheduled, Processed, Failed
<Count>
Long
Required
Transaction counts. This count would indicate how many requested transactions were acknowledged for the type indicated. Amount. This amount references the accumulated amount for the <AckType> identified above. Memo for appropriate text concerning the acknowledgment. CPP contact information. In the case that contact info is needed, may be used in the case the URL is needed to link the customer back to the CPP site for additional information about the service or transaction.
<CurAmt> <Memo> <CompositeContactInfo>
Currency Amount C-255 Aggregate see section 3.2.3.8
7.3.14
pain.001.001.01 <pain.001.001.01>
The CoreCreditTransferInitiation message is sent by the initiating party to the forwarding agent or first agent. This message is used to request movement of cash from a debtor's account to a creditor.
The CoreCreditTransferInitiation message can contain : one or more instances of a credit transfer initiation, payment transactions that result in book transfers at the first agent or payments to another financial institution, payment transactions that result in an electronic cash transfer to the creditor's account or in the emission of a cheque. The message can be used in a direct or a relay scenario. In a direct scenario, the initiating party sends the CoreCreditTransferInitiation message directly to the first agent. The first agent is the account servicer of the debtor. In a relay scenario, the initiating party sends the CoreCreditTransferInitiation message to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CoreCreditTransferInitiation message to the first agent.
Version 1.7
April 2005
33
Interactive Financial Exchange Business Message Specification An initiating Party that has authority to send the message on behalf of the debtor can also use the message. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CoreCreditTransferInitiation message can be used in domestic and cross-border scenarios.
The message can be used to group payments (in this case, the Payment Information component is present once) or can be used as a collection of individual payments (in this case the Payment Information component is present once per occurrence of Payment Transaction component).
7.3.15
pain.002.001.01 <pain.002.001.01>
The PaymentInitiationStatus message is sent by the first agent or the forwarding agent to the initiating party. It is used to inform the initiating party about the status of a payment initiation that the initiating party has sent to the forwarding agent or first agent.
The usage of the PaymentInitiationStatus message will always be governed by a bilateral agreement between the agent and customer. The PaymentInitiationStatus message can be used to report on the initiation of a credit transfer, as well as on the initiation of other customer transactions. It can contain status information on the group of payments included in the initiation, as well as status information on any of the individual payment transactions included in the initiation.
In the case of a relay scenario, the first agent can either send the PaymentInitiationStatus message to the forwarding agent, who in its turn will forward the PaymentInitiationStatus message to the initiating party, or the first agent can send it directly to the initiating party.
7.3.16
pain.003.001.01 <pain.003.001.01>
The initiating party sends the PaymentInitiationCancellationRequest message to the forwarding agent or to the first agent. It is used to request the forwarding agent or first agent to consider cancellation of a payment initiation previously sent by the initiating party. The usage of the PaymentInitiationCancellationRequest message will always be governed by a bilateral agreement between the agent and customer.
The PaymentInitiationCancellationRequest message can be used to request the cancellation of an initiation of a credit transfer, as well as request the cancellation of the initiation of other customer transactions. The PaymentInitiationCancellationRequest message can be used to request the cancellation of a complete payment initiation, or of individual transactions included in the initiation.
The message requires a reply from the forwarding agent or first agent. This reply can be sent in the form of a PaymentInitiationCancellationRequestStatus message.
7.3.17
pain.004.001.01 <pain.004.001.01>
The forwarding agent or the first agent sends the PaymentInitiationCancellationStatus message to the initiating party. It is used to inform the initiating party of the status of a request for cancellation that the initiating party sent to the forwarding agent or first agent.
34
April 2005
Version 1.7
The usage of the PaymentInitiationCancellationStatus message will always be governed by a bilateral agreement between the agent and customer.
7.3.18
Tag
PmtBatch Record Aggregate <PmtBatchRec>

Type
Usage
Required Optional
Description
PmtBatch Identifier PmtBatch Information Aggregate
<PmtBatchId> <PmtBatchInfo>
<PmtBatchStatus>
Required
PmtBatch Status Aggregate
7.3.18.1 PmtBatch Status Record Aggregate <PmtBatchStatusRec>

Tag
<PmtBatchId> <PmtBatchStatus>
Type
Usage
Required Required
Description
PmtBatch Identifier PmtBatch Status Aggregate
7.3.18.2 PmtBatch Status Aggregate <PmtBatchStatus>

Tag
<pain.002.001.01> <pain.004.001.01>
Type
External Aggregate External Aggregate
Usage
Description
External status information as provided by the processing server. External status information as provided by the processing server. This aggregate will only be used to provide status information concerning cancelled batches.
7.3.18.3 PmtBatch Information Aggregate <PmtBatchInfo>

Tag
<pain.001.001.01>
Type
External Aggregate
Usage
Optional
Description
Payment kernel (IST). This aggregate is expected on Add requests. Trading partners should agree on whether it should be returned on response messages or included in other request messages (i.e., PmtBatchCanRq, PmtBatchAdviseRq).
7.4Standard Payee
7.4.1Standard Payee Inquiry
The Standard Payee Inquiry message may be used to assist customers in selecting payees to be added to the customers personal payee list <CustPayeeId>. The response returns one or more well-known payees that match the selection criteria of the request.
Version 1.7
April 2005
35
7.4.1.1 Request <StdPayeeInqRq>

If the client omits all search elements in the <StdPayeeInqRq>, the client is requesting a complete directory of payees. Otherwise, the client wants to filter results based on the included elements. For each payee that matches the elements in the request, the CPP returns the complete name and address of the payee, the payee ID, and the CPP name. This inquiry request is similar to the <BillerInqRq>, which returns billers serviced by a BSP. Note: billers known by a <BillerId> to a BSP may be well-known merchants to a CPP and therefore will have a corresponding <StdPayeeId>. In fact, an entity playing both BSP and CSP roles may use the same actual value, but implementers must never count on this.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 7.3.1.1 C-40
Optional
<StdPayeeId>
Optional Repeating Optional Repeating Optional Repeating Optional Repeating
Payee Identification. This field is used as a selection criterion. Payee Name. This field is used as a selection criterion. Customer (Billing) Account Number with the Payee. Useful for determining appropriate merchant instance via account scheme. Postal Code. This is the postal code of the billing account. This field is used as a selection criterion. (1) It may used to limit the search to billers doing business within a limited geography, or (2) It may be used to identify the correct legal/entity or remittance address such as the cable company for a specific city, e.g. TCISunnyvale CA. Industry Identifier
<Name>
<BillingAcct>
C-32
<PostalCode>
C-11
<IndustId>
Optional Repeating Optional Profiled values
<DeliveryMethod>
36
April 2005
Version 1.7
7.4.1.2 Response <StdPayeeInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Payee Identification.
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed
<StdPayeeId>
<Name>
Payee Name. This field is used as a selection criterion. Customer (Billing) Account Number with the Payee. Useful for determining appropriate merchant instance via account scheme. Postal Code. This is the postal code of the billing account. This field is used as a selection criterion. (1) It may used to limit the search to billers doing business within a limited geography, or (2) It may be used to identify the correct legal/entity or remittance address such as the cable company for a specific city, e.g. TCISunnyvale CA. Industry Identifier
<BillingAcct>
C-32
<PostalCode>
C-11
<IndustId>
Aggregate see section 3.2.13 Open Enum Aggregate see section 7.3.1
Optional Repeating Echoed Optional Echoed Optional Repeating
<DeliveryMethod> <StdPayeeRec>
Delivery Method. Standard Payee Record Aggregate. One record is returned for each Payee defined for this customer who meets the selection criteria in the request.
Version 1.7
April 2005
37
7.4.2Standard Payee Reversal

7.4.2.1 Request <StdPayeeRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Standard Payee Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <StdPayeeMsgRqInfo>
Open Enum C-80 Aggregate see section 7.4.2.1.1
Required Optional Required
7.4.2.1.1 Standard Payee Message Request Information Aggregate <StdPayeeMsgRqInfo>

Tag
<StdPayeeInqRq>
Type
Usage
Optional
Description
Standard Payee Inquiry Request Message Aggregate.
7.4.2.2 Response <StdPayeeRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
38
April 2005
Version 1.7
Tag
Type
UUID Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate see section 7.4.2.1.1 Identifier Identifier
Usage
Description
<RevReasonCode> <Desc> <StdPayeeMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Standard Payee Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
7.5Customer Payee
7.5.1Customer Payee Add
The client uses the Customer Payee Add message to add a Payee to a Customer Payee list on the Pay providers server.
7.5.1.1 Request <CustPayeeAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payee Record Aggregate.
<CustPayeeInfo>
Required
Version 1.7
April 2005
39
7.5.1.2 Response <CustPayeeAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payee Record Aggregate.
<CustPayeeInfo>
<CustPayeeRec>
Customer Payee Record.
Optional Optional
7.5.2Customer Payee Modify

The Modify Payee message allows a client to change information about a payee on a customers Payee list on the Pay providers server.
7.5.2.1 Request <CustPayeeModRq>

The <CustPayeeModRq> message is sent by a client to modify a Payee record on a customers Payee list on the server.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
40
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customers Payee Identifier. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. Payee Info Aggregate.
<CustPayeeId>
Identifier
Required
<CustPayeeInfo>
Required
<ModPending>
Modify Pending Payments indicates whether to propagate the payee change to pending single payments. Changes to payees are always propagated to payment models. If True, changes to payees are propagated to pending payments If False, or omitted, changes are not propagated. This option must be ignored when <ModPendingType> IfRequested in the Pay Service Profile.
7.5.2.2 Response <CustPayeeModRs>

The server sends the <CustPayeeModRs> message in response to a <CustPayeeModRq> message from a client.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customers Payee Identifier. Payee Record Aggregate.
<CustPayeeId> <CustPayeeInfo>
Version 1.7
April 2005
41
Tag
<ModPending>
Type
Boolean
Usage
Optional Profiled support Echoed Required
Description
Modify Pending Payments Flag.
<CustPayeeRec>
Customer Payee Record.
Optional Optional
7.5.3Customer Payee Type Modify

A user with special authorization, typically a CSR, may send a request to the Payment Service Provider to change the payee type.
7.5.3.1 Request <CustPayeeTypeModRq>

The user must specify security details, the payee identifier, the payee type, and the new payee type.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customer Payee Identifier. Assigned by the server at the time the Payee is first added. Cannot be modified by the client. Payee Type. May be Standard Payee, Biller, Fully-Specified Payee or Interbank Transfer. Valid values: Biller, FSPayee, Xfer, Std
<CustPayeeId>
Identifier
Required
<PayeeType>
Closed Enum
Required
7.5.3.2 Response <CustPayeeTypeModRs>

Tag
<Status>
Type
Usage
Optional
Description
42
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payee Identifier.
<CustPayeeId>
Aggregate see section 7.1.1.3 Closed Enum
<PayeeType>
Payee Type. May be Standard Payee, Biller, Fully-Specified Payee or Interbank Transfer. Valid values: Biller, FSPayee, Xfer, Std
Optional Optional
7.5.4Customer Payee Delete

A client uses the Customer Payee Delete message to delete a Payee from a Customer Payee list on the server. If the <CascadeDel> element is not set to True, an error must be returned if a payee delete is attempted when payments are still pending. If this error is returned, the types of dependent objects must be communicated to the client in the response message.
7.5.4.1 Request <CustPayeeDelRq>

A client initiates the Delete Payee message by sending a <CustPayeeDelRq> message to the server.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Version 1.7
April 2005
43
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customers Payee Identifier. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. Cascade Delete. If True, server must delete all dependent objects when this object is deleted. If False or omitted, the customer payee must not be deleted if dependent objects exist. For a customer payee, a dependant objects are recurring models or payments.
<CustPayeeId>
Identifier
Required
<CascadeDel>
Boolean
Optional
7.5.4.2 Response <CustPayeeDelRs>

The server responds to the clients <CustPayeeDelRq> message by sending a <CustPayeeDelRs> message.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Customers Payee Identifier. Cascade Delete. Customer Payee Record.
<CustPayeeId> <CascadeDel> <CustPayeeRec>
Identifier Boolean Aggregate see section 7.3.2 Open Enum
Required Echoed Optional Echoed Optional XOR Optional Repeating XOR Optional Optional
<DependentType>
Open Enum containing a list of dependent object types that exist for the customer payee. Defined values: RecPmt, Pmt Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
44
April 2005
Version 1.7
7.5.5Customer Payee Inquiry

A client uses the Payee Inquiry message to obtain records from the Customer Payee list on a server. Clients that store a local copy of a Customer Payee list may use this message to refresh the Payee list.
7.5.5.1 Request <CustPayeeInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<DeliveryMethod>
Delivery Method. Used to request the delivery channel for requested information. Included here primarily to allow customer using an IVR (interactive voice response) unit to request a delivery option for their Payee list. Defined values: Channel, HomeBank, Post, UPS, Courier. Default value is Channel Value must be supported in Service Profile.
<CustPayeeId>
Identifier
Customers Payee Identifier. This field is used as a selection criterion. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. Payee Type. May be Standard Payee, Biller, Fully-Specified Payee or Interbank Transfer. Valid values: Biller, FSPayee, Xfer, Std This field is used as a selection criterion.
<PayeeType>
Closed Enum
<Name>
C-40
Payee Name. This field is used as a selection criterion. Payee Nickname. Optionally assigned by the customer. Only stored by the Pay provider if indicated in the Service Profile. This field is used as a selection criterion.
<Nickname>
C-40
Version 1.7
April 2005
45
Tag
<IncToken>
Type
Boolean
Usage
Optional
Description
Include Token. If True, a <Token> must be included in the response, if the Service Profile indicates support for customer payee synchronization, to set a base for future synchronization messages. If False or omitted, the <Token> may be omitted in the response.
7.5.5.2 Response <CustPayeeInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Delivery Method.
<RecCtrlOut>
Optional but see Description Optional Profiled values Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed
<DeliveryMethod>
<CustPayeeId>
Identifier
Customers Payee Identifier.
<PayeeType>
Closed Enum C-40
Payee Type.
<Name>
Payee Name.
<Nickname>
C-40
Payee Nickname.
<IncToken>
Boolean
Include Token.
46
April 2005
Version 1.7
Tag
<CustPayeeRec>
Type
Usage
Optional Repeating
Description
Payee List Record Aggregate. One record is returned for each Payee defined for this customer who meets the selection criteria in the request. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token must be provided if <IncToken> = True in the request and the server supports synchronization. <Token> = 0 is returned if no records are returned within the response.
<Token>
7.5.6Customer Payee Audit

7.5.6.1 Request <CustPayeeAudRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Payee Method. Valid values are: Add, Mod, Del This field is used as a selection criterion.
<CustPayeeId>
Identifier
Optional Repeating
Customers Payee Identifier. This field is used as a selection criterion. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added.
Version 1.7
April 2005
47
7.5.6.2 Response <CustPayeeAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
<SelRangeDt>
<Method>
Payee Method.
<CustPayeeId>
Customers Payee Identifier. This field is used as a selection criterion. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. Payee Message Record Aggregate.
<CustPayeeMsgRec>
7.5.6.2.1 Customer Payee Message Record Aggregate <CustPayeeMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created.
<MsgRecDt>
Timestamp
Optional
48
April 2005
Version 1.7
Tag
<CustPayeeAddRs>
Type
Usage
Description
Customer Payee Add Response Message Aggregate.
<CustPayeeModRs>
Customer Payee Modify Response Message Aggregate.
<CustPayeeTypeModRs>
Customer Payee Type Modify Response Message Aggregate. Customer Payee Delete Response Message Aggregate.
<CustPayeeDelRs>
7.5.7Customer Payee Synchronization

The Customer Payee Synchronization message is used by a client for retrieving a list of changes to a customers Payee list. This message may be used by clients that keep local copies of a customers Payee messages to synchronize their local databases of Payee messages against the databases of Payee messages kept by Pay providers. Typically results of this message tells a client what the customer has done using other clients since they last used this one, but it may also inform a client about changes the Pay provider made (e.g., converted a Payee from a Fully-Specified Payee to a Biller).
7.5.7.1 Request <CustPayeeSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
Version 1.7
April 2005
49
7.5.7.2 Response <CustPayeeSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Message Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. If the client sent a token in the request, the server returns a new token based on this message.
<RecCtrlOut>
<Token> <NewToken>
<CustPayeeMsgRec>
Optional Repeating
Customer Payee Message Record Aggregate.
7.6Single Payment
7.6.1Payment Add
The Payment Add message allows a client to schedule a single payment, where the amount is input by the customer or from a presented bill. The Payment Add message may reference an existing payee or add a new one, by specifying the information within <RemitInfo> <PayeeInfo>. If the Payment service provider supports <CustPayeeId>, the client must specify an existing <CustPayeeId> or include the <CustPayeeInfo> aggregate, but not both. Whether or not the Payment service provider supports <CustPayeeId>, the <CustPayeeInfo> aggregate may specify an existing standard payee or create a new fully specified or transfer payee. It is not possible to modify an existing payee within an Add Payment message. The customer may modify a payee via <CustPayeeModRq>.
50
April 2005
Version 1.7
7.6.1.1 Request <PmtAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Information Aggregate. Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new payment being added.
<PmtInfo>
Required Optional
<DupChkOverride>
7.6.1.2 Response <PmtAddRs>

The <PmtAddRs> message is used to provide an acknowledgement to a customer-initiated <PmtAddRq>. It is also used in the Payment Audit Response <PmtAudRs> and Payment Synchronization Response <PmtSyncRs> to communicate to the client that payments have been added by the customer using <PmtAddRq> and by the Pay provider using the customers Recurring Payment Models.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Version 1.7
April 2005
51
Tag
<PmtInfo>
Type
Aggregate see section 7.3.3.1 Boolean Aggregate see section 7.3.3 Identifier Identifier
Usage
Description
Payment Information Aggregate. Duplicate Check Override Flag. Payment Record Aggregate.
<DupChkOverride> <PmtRec>
Optional Optional
7.6.2Payment Modify
The Payment Modify message allows a client to modify the current information about a Payment that was set up using the Payment Add message or a Payment that was generated from a Recurring Payment Model. For information on Conventions for Modification of Server-Based Data, see Chapter 2. The Payment Modify message may neither add a new payee nor modify the definition of an existing payee. The client may change the previously defined payee, to whom the payment is intended, by using either the <CustPayeeId>, if the Payment service provider supports its use, or the <StdPayeeId> within <CustPayeeInfo> within <PmtInfo>.
7.6.2.1 Request <PmtModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client. Payment Information Aggregate. If the server supports Customer Payee lists, the client must specify the Payee using <CustPayeeId> within <PmtInfo>. Adding new Payees using the <PmtModRq> message is not supported.
<PmtId> <PmtInfo>
Required Required
Note: Values of <InvoiceInfo>s included in this aggregate must be interpreted as replacing all existing <InvoiceInfo>s associated with this payment.
52
April 2005
Version 1.7
Tag
<UpPayee>
Type
Boolean
Usage
Optional
Description
Update PayeeUpdate Payee to current level. Used if a previous CustPayeeMod was done without propagating the changes to all pending payments, and the client would like the payee changes propagated to this particular payment. If True, the Payee information for this payment should be updated to match the current level of payee information known to the server. If False, or omitted, do not update the Payee information to the current level. Note that the rest of the <CustPayeeInfo> aggregate may still be used to update the Payee information for this payment, either within a <PmtModRq> or <CustPayeeModRq> as appropriate. Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a distinct payment, even if the modification creates a duplicate of another payment.
<DupChkOverride>
Boolean
Optional
7.6.2.2 Response <PmtModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Identifier. Payment Information Aggregate.
<PmtId> <PmtInfo>
Identifier Aggregate see section 7.3.3.1 Boolean Boolean Aggregate see section 7.3.3 Identifier
Required Echoed Required Echoed Optional Echoed Optional Echoed Required
<UpPayee> <DupChkOverride> <PmtRec>
Update Payee Flag. Duplicate Check Override Flag. Payment Record Aggregate.
<CSPRefId>
Optional
Version 1.7
April 2005
53
Tag
<SPRefId>
Type
Identifier
Usage
Optional
Description
7.6.3Payment Status Modify

A user with special authorization, typically a CSR, may send a request to the SP Server to modify the payment status of a specific payment instance. Customers may also send a request to the SP Server to modify the payment status in order to undo a Skip applied to one or more payments. The only fields that may be changed are within the payment status aggregate <PmtStatus>.
7.6.3.1 Request <PmtStatusModRq>

The user must specify the payment identifier along with the payment details to be changed.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client. Used to reference a specific payment.
<PmtId>
Identifier
Required
<PmtRefId>
Identifier
Optional
Note: If the CPP uses StatusModRq or InqRs to push acknowledgement to client, there is no place to echo back the <RqUID> from the <PmtAddRq>, so this <PmtRefId> is required for the customer to link the status back to the original payment request.
<SvcRqUID> <PmtStatus> UUID Aggregate see section 7.3.4.1 Optional Required Service Request Identifier. The payment service request identifier that was created and sent by the client to the CPP. Payment Status Aggregate.
54
April 2005
Version 1.7
7.6.3.2 Response <PmtStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Message Respoonse Header aggregate.
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Identifier. Payment reference identifier. Service Request Identifier. Payment Status Aggregate.
<PmtId> <PmtRefId> <SvcRqUID> <PmtStatus>
Identifier Identifier UUID Aggregate see section 7.3.4.1 Aggregate see section 3.2.18 Aggregate see section 3.2.3.8 Identifier Identifier
Required Echoed Optional Echoed Optional Echoed Required Echoed Optional
<NetworkTrnInfo>
Network Transaction Information Aggregate. Contains information regarding the network that processed the transaction. CPP contact information. In the case that contact info is needed, may be used in the case the URL is needed to link the customer back to the CPP site for additional information about the service or transaction. Financial Institution Reference Number. Service Provider Reference Number.
<CompositeContactInfo>
Optional
Optional Optional
7.6.4Payment Status Advise

PmtStatusAdvise message is used to advise an entity of a change in Payment Status. For every status change in the lifecycle of a payment, a PmtStatusAdvise messages may be sent.
7.6.4.1 Request <PmtStatusAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
Version 1.7
April 2005
55
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Status Record Aggregate. Contains information regarding the status of the payment at the CPP or the Payment Network.
<PmtStatusRec>
Required
7.6.4.2 Response <PmtStatusAdviseRs>

Tag
<Status>
Type
Usage
Required
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Status Record Aggregate. Contains information regarding the status of the payment at the CPP or the Payment Network. Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a payment corresponding to a confirmation number that was returned to the client when the payment was added or modified. When a payment has been modified, only the <CSPRefId> received in the most recent <PmtStatusAdviveRs> is valid. Service Provider Reference Identifier. Same usage as <CSPRefId>.
<PmtStatusRec>
<CSPRefId>
<SPRefId>
Identifier
Optional
7.6.5Payment Cancel
The Cancel Payment message allows a client to cancel a Payment that was set up using the Payment Add message or generated from a Recurring Payment Model.
56
April 2005
Version 1.7
7.6.5.1 Request <PmtCanRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client.
<PmtId>
Identifier
Required
7.6.5.2 Response <PmtCanRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Server must return <RqUID> if provided by client in a <PmtCanRq>.
<RqUID>
Required Echoed
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Identifier.
<PmtId>
Identifier
Required Echoed
Version 1.7
April 2005
57
Tag
<PmtRec>
Type
Usage
Optional
Description
Payment Record Aggregate. This aggregate is provided in cases where the server keeps the payments record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Cancelled. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
7.6.6Payment Inquiry
The Payment Inquiry message allows a client to get a list of the customers pending, completed, or failed payments on the CPPs server. The client may select on a number of criteria. Clients that keep local copies of a customers payments may use this message to refresh their payment list. This message must not return a customers recurring payment models but must return any pending, completed, or failed payments that were generated from recurring payment models. The <FIDebitTrcNum> and <FICreditTrcNum> elements exist to support the case where the CPP submits a payment request to the FI (or CSP) that actually sends the payment messages. For example, a CPP may send a file of ACH-style messages that the FI forwards as actual ACH messages. The FI/CSP may edit the file; e.g., process their in-house messages and forward the rest. As part of this process the FI/CSP may assign reference numbers that correlate the messages to their system of record. There are both credit and debit fields to handle cases like US on US where two messages are spawned by the same payment request. Note that the debit and credit trace numbers are received offline but are added to support message histories. Also note that in this scenario all 4 message IDs are used: <SPRefId> is the Pay engine (CPP) reference to the payment and <CSPRefId> is the FI/CSP reference to the payment. One or both were probably returned to the client as confirmation number(s) when the payment was added or modified. <FIDebitTrcNum> and <FICreditTrcNum> are references to the messages that actually move funds to and from accounts.
7.6.6.1 Request <PmtInqRq>

A client initiates the Payment Inquiry message by sending a <PmtInqRq> message.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
58
April 2005
Version 1.7
Tag
<PmtType>
Type
Closed Enum
Usage
Optional Repeating
Description
Payment Type. Valid values: Pmt, RecPmt This field is used as a selection criterion.
<PmtId>
Identifier
Optional Repeating
Payment Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client. This field is used as a selection criterion.
<RecPmtId>
Identifier
Optional Repeating
Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Cannot be modified by the client. This field is used as a selection criterion.
<DepAcctIdFrom>
Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 C-40
Optional XOR
Deposit Account Aggregate. Source account for payment. This field is used as a selection criterion. Card Account Identifier Aggregate. Source account for payment. This field is used as a selection criterion. Payment Category. The customer assigns categories. This field is used as a selection criterion. Memo for Payment. From Customer to Payee. This field is used as a selection criterion. Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. Check Cleared Date. The date when the check cleared the account on which it was drawn. FI Debit Trace Number. FI Credit Trace Number. Payment Method. Intended to provide the customer with information regarding the method of payment used by the service provider to transfer the funds to the payee. Defined values: Check, Electronic, ACH, FedNet, SWIFT, CHIPS, CHAPS, BookEntry, Draft
<CardAcctIdFrom>
Optional XOR
<Category>
Optional Repeating Optional Repeating Optional Repeating Optional Repeating Optional Repeating Optional Repeating Optional Repeating
<Memo>
C-255
<ChkNum> <ChkClrDt> <FIDebitTrcNum> <FICreditTrcNum> <PmtMethod>
NC-12 Date NC-7 NC-7 Open Enum
<CustPayeeId> <BillingAcct>
Identifier C-32
Optional Repeating Optional Repeating Optional Repeating Optional Repeating
Customers Payee Identifier. This field is used as a selection criterion. Customer Account Number with Payee. This field is used as a selection criterion. Payee Name. This field is used as a selection criterion. Customers Payee Identifier Aggregate. <StdPayeeId> is a synonym for <BillerId>. This field is used as a selection criterion.
<Name>
C-40
<StdPayeeId>
<Nickname>
Optional Repeating
Payee Nickname. This field is used as a selection criterion.
Version 1.7
April 2005
59
Tag
<PmtStatusCode>
Type
Closed Enum
Usage
Optional Repeating
Description
Payment Status Code. This identifies the payment processing status. Valid values: Scheduled, Processed, FundAcctDebited, Skip, Cancelled, Failed, PmtAuthHeld, PmtAuthNoFunds, PmtAuthInactive, PmtAuthClosed, Posted, CheckCleared, Returned, RemitPending, RemitRefused, RemitRejected This field is used as a selection criterion.
<SelRangeDueDt>
Optional
<SelRangePrcDt>
Optional
Selection Range Processing Date Aggregate. Usage is range for actual processing date, possibly adjusted for holidays and non-processing daysas opposed to original customer-entered processing date if using the processing date model.
<SelRangeCurAmt>
Optional
<DeliveryMethod>
Delivery Method. Used to request the delivery channel for requested information. Included here primarily to allow customer using an IVR (interactive voice response) unit to request a delivery option for their payment list. Valid values: Channel, HomeBank, Post, UPS, Courier. Default value is Channel Value must be supported in Service Profile.
<CSPRefId>
Identifier
Optional Repeating
Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a payment corresponding to a confirmation number that was returned to the client when the payment was added or modified. When a payment has been modified, only the <CSPRefId> received in the most recent PMPMODRS is valid. The use of an <CSPRefId> from an earlier response is likely to result in a payment not found response. Service Provider Reference Identifier. Same usage as <CSPRefId>. Include Token. If True, a <Token> must be included in the response, if the Service Profile indicates support for payment synchronization, to set a base for future synchronization messages. If False or omitted, the <Token> may be omitted in the response. Include History. If True, the response should include payments that have already occurred, as well as those scheduled to occur.
<SPRefId> <IncToken>
Identifier Boolean
<IncHistory>
Boolean
Optional
7.6.6.2 Response <PmtInqRs>

The server responds to a <PmtInqRq> message by returning a <PmtInqRs> message to the client.
Tag
<Status>
Type
Usage
Optional
Description
60
April 2005
Version 1.7
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Payment Type. This field is used as a selection criterion. Payment Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client. This field is used as a selection criterion. Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Cannot be modified by the client. This field is used as a selection criterion.
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Closed Enum Identifier
<PmtType>
<PmtId>
<RecPmtId>
Identifier
<DepAcctIdFrom>
Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed
Deposit Account Aggregate. Source account for payment. This field is used as a selection criterion. Card Account Identifier Aggregate. Source account for payment. This field is used as a selection criterion. Payment Category. The customer assigns categories. This field is used as a selection criterion. Memo for Payment. From Customer to Payee. This field is used as a selection criterion. Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. Check Cleared Date. The date when the check cleared the account on which it was drawn. FI Debit Trace Number.
<CardAcctIdFrom>
<Category>
<Memo>
C-255
<ChkNum>
NC-12
<ChkClrDt>
Date
<FIDebitTrcNum>
NC-7
Version 1.7
April 2005
61
Tag
<FICreditTrcNum>
Type
NC-7
Usage
Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Repeating
Description
FI Credit Trace Number.
<PmtMethod>
Open Enum
Payment Method. Intended to provide the customer with information regarding the method of payment used by the service provider to transfer the funds to the payee. Customers Payee Identifier. This field is used as a selection criterion. Customer Account Number with Payee. This field is used as a selection criterion. Payee Name.
<CustPayeeId>
Identifier
<BillingAcct>
C-32
<Name>
C-40
<StdPayeeId>
Customers Payee Identifier Aggregate. <StdPayeeId> is a synonym for <BillerId>. Payee Nickname.
<Nickname>
<PmtStatusCode>
Closed Enum Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Open Enum Identifier
Payment Status Code.
<SelRangeDueDt>
<SelRangePrcDt>
Selection Range Processing Date Aggregate.
<SelRangeCurAmt>
<DeliveryMethod> <CSPRefId>
Delivery Method. Customer Service Provider Reference Identifier.
<SPRefId>
Identifier
<IncToken> <IncHistory> <PmtRec>
Boolean Boolean Aggregate see section 7.3.3
Include Token. Include History. Payment Record Aggregate. One record is returned for each of the customers payments that meets the selection criteria specified in the request message. Note that payments may have been generated by a client (using <PmtAddRq> or may have been generated by the Pay provider from one of the customers Recurring Payment Models.
62
April 2005
Version 1.7
Tag
<Token>
Type
Identifier
Usage
Description
7.6.7Payment Reversal
7.6.7.1 Request <PmtRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Payment Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <PmtMsgRqInfo>
7.6.7.1.1 Payment Message Request Information <PmtMsgRqInfo>

Tag
<PmtAddRq>
Type
Usage
Description
Payment Add Request Message Aggregate.
<PmtModRq>
Payment Modify Request Message Aggregate.
<PmtInqRq>
Payment Inquiry Request Message Aggregate.
Version 1.7
April 2005
63
7.6.7.2 Response <PmtRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <PmtMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Payment Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
7.6.8Payment Status Inquiry

7.6.8.1 Request <PmtStatusInqRq>
A client initiates the Payment Status Inquiry message by sending a <PmtStatusInqRq> message.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
64
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<SettlementMethod>
Optional Repeating
Settlement Method. Either the method accepted by the Biller or BPP for settling payments, or the payment/settlement method, provided as the general method for settling payment. Defined values: RPS, EPay, ACH, Concentrator, FedNet, SWIFT, CHIPS, CHAPS, BookEntry, Draft, OutsourcedCheck This field is used as a selection criterion.
<PmtId>
Identifier
Optional Repeating
<PmtRefId>
Identifier
Optional Repeating
<SvcRqUID> <PmtRemitRefId> <DepAcctIdFrom> UUID Identifier Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 C-40 Optional Optional Optional XOR Service Request Identifier. The payment service request identifier that was created and sent by the client to the CPP. Payment Remittance (Credit) Reference Transaction Identifier. Deposit Account Aggregate. Source account for payment. This field is used as a selection criterion. Card Account Identifier Aggregate. Source account for payment. This field is used as a selection criterion. Payment Category. The customer assigns categories. This field is used as a selection criterion. Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. Customers Payee Identifier. This field is used as a selection criterion. Fully-Specified Payee Aggregate.
<CardAcctIdFrom>
Optional XOR
<Category>
Optional Repeating Optional Repeating Optional Repeating XOR Optional Repeating XOR
<ChkNum> <CustPayeeId>
NC-12 Identifier
<FSPayee>
Version 1.7
April 2005
65
Tag
<Name>
Type
C-40
Usage
Description
Payee Name. This field is used as a selection criterion. Payer information. This field is used as a selection criterion.
<PayerInfo>
Aggregate see section 7.3.3.1.1 Closed Enum
<PmtStatusCode>
<SelRangeDueDt>
Optional
7.6.8.2 Response <PmtStatusInqRs>

The server respondes to a Payment Status Inquiry Request <PmtStatusInqRq> message by sending a Payment Status Inquiry Response <PmtStatusInqRs> message with information aabout the <PmtAddRq>.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Optional Echoed
<RecCtrlIn>
Optional Echoed
66
April 2005
Version 1.7
Tag
<SettlementMethod>
Type
Open Enum
Usage
Description
Settlement Method. Either the method accepted by the Biller or BPP for settling payments, or the payment/settlement method, provided as the general method for settling payment. Defined values: RPS, EPay, ACH, Concentrator, FedNet, SWIFT, CHIPS, CHAPS, BookEntry, Draft, OutsourcedCheck
<PmtId>
Identifier
<PmtRefId>
Identifier
<SvcRqUID> UUID Optional Echoed Optional Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating XOR Echoed Optional Repeating XOR Echoed Optional Repeating Echoed Optional Repeating Echoed Service Request Identifier. The payment service request identifier that was created and sent by the client to the CPP. Payment Remittance (Credit) Reference Transaction Identifier. Deposit Account Aggregate. Source account for payment. This field is used as a selection criterion. Card Account Identifier Aggregate. Source account for payment. This field is used as a selection criterion. Payment Category. The customer assigns categories. This field is used as a selection criterion. Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. Customers Payee Identifier. This field is used as a selection criterion.
<PmtRemitRefId> <DepAcctIdFrom>
Identifier Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.7.2.3 C-40
<CardAcctIdFrom>
<Category>
<ChkNum>
NC-12
<CustPayeeId>
Identifier
<FSPayee>
Fully-Specified Payee Aggregate.
<Name>
Payee Name. This field is used as a selection criterion. Payer Information. This field is used as a selection criterion.
<PayerInfo>
Version 1.7
April 2005
67
Tag
<PmtStatusCode>
Type
Closed Enum
Usage
Description
<SelRangeDueDt>
Aggregate see section 3.2.10.1 Aggregate see section 7.3.12 Identifier
Optional Echoed Optional Repeating Optional Repeating
<PmtStatusRec>
Payment Status Record Aggregate. Contains information regarding the status of the payment at the CPP or the Payment Network. Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a payment corresponding to a confirmation number that was returned to the client when the payment was added or modified. When a payment has been modified, only the <CSPRefId> received in the most recent <PmtModRs> is valid. The use of an <CSPRefId> from an earlier response is likely to result in a payment not found response. Service Provider Reference Identifier. Same usage as <CSPRefId>.
<CSPRefId>
<SPRefId>
Identifier
Optional Repeating
7.6.9Payment Audit
7.6.9.1 Request <PmtAudRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
68
April 2005
Version 1.7
Tag
<Method>
Type
Closed Enum
Usage
Optional Repeating
Description
Payment Method. Valid Values: Add, Mod, Can This field is used as a selection criterion.
<PmtId>
Identifier
Optional Repeating
7.6.9.2 Response <PmtAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Echoed
<SelRangeDt>
<Method>
Payment Method.
<PmtId>
<PmtMsgRec>
Optional Repeating
Payment Message Record Aggregate.
7.6.9.2.1 Payment Message Record Aggregate <PmtMsgRec>
Version 1.7
April 2005
69
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created. Payment Add Response Message Aggregate.
<MsgRecDt> <PmtAddRs>
<PmtModRs>
Payment Modify Response Message Aggregate.
<PmtStatusModRs>
Payment Status Modify Response Message Aggregate.
<PmtCanRs>
Payment Cancel Response Message Aggregate.
<PmtRevRs>
Payment Reversal Response Message Aggregate.
7.6.10
Payment Synchronization
A client uses the Payment Sync message to retrieve a list of changes that have occurred to a customers payments. This message may be used to enable a client that keeps local copies of a customers payment messages to synchronize its local database with the Pay provider. The results of this message tell a client what the customer has done using other clients since they last used this one. It may also inform a client about changes the Pay provider made (i.e., generated another payment instance for a recurring payment model, completed a payment or rejected a payment). Some examples of changes the Pay provider would communicate to a customer include: New pending payment generated from a Recurring Payment Modelreturned with a <PmtAddRs>; Successful payment processingreturned with <PmtModRs> with new <PmtStatus> indicating success; Unsuccessful payment processingreturned with <PmtModRs> with new <PmtStatus> indicating status and reason for failure, if available; Payment assigned a check numberreturned with <PmtModRs> with new <PmtStatus> including <ChkNum>; and status. Payment check clearedreturned with <PmtModRs> with new <PmtStatus> indicating
7.6.10.1 Request <PmtSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
70
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
7.6.10.2 Response <PmtSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Message Rewsponse Header aggregate.
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate.
<RecCtrlOut>
Optional
Version 1.7
April 2005
71
Tag
<Token>
Type
Identifier
Usage
Required Echoed
Description
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Payment Message Record Aggregate.
<PmtMsgRec>
Optional Repeating
7.7Payment Authorization
The Payment Authorization transactions are used by a CPP to request authorization for payment from the holder of the funding account, which could be a different organization than the CPP or CSP. The <PmtAuthAdd> would generally be done at the time of payment processing for current day payments. This message asks the Financial Institution for a decision on whether or not the CPP is authorized to make a particular payment. The <PmtAuth> messages facilitate what is commonly called the Good Funds model.
7.7.1Payment Authorization Add

7.7.1.1 Request <PmtAuthAddRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Authorization Information Aggregate.
<PmtAuthInfo>
Required
72
April 2005
Version 1.7
7.7.1.2 Response <PmtAuthAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Authorization Information Aggregate.
<PmtAuthInfo>
<PmtAuthRec>
Payment Authorization Record Aggregate
7.7.2Payment Authorization Modify

7.7.2.1 Request <PmtAuthModRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Authorization Identifier.
<PmtAuthId>
Identifier
Required
Version 1.7
April 2005
73
Tag
<PmtAuthInfo>
Type
Usage
Required
Description
Payment Authorization Information Aggregate.
7.7.2.2 Response <PmtAuthModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Authorization Identifier Payment Authorization Information Aggregate.
<PmtAuthId> <PmtAuthInfo>
Identifier Aggregate see section 7.3.5.1 Aggregate see section 7.3.5
<PmtAuthRec>
Payment Authorization Record Aggregate
7.7.3Payment Authorization Cancel

7.7.3.1 Request <PmtAuthCanRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
74
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Authorization Identifier.
<PmtAuthId>
Identifier
Required
7.7.3.2 Response <PmtAuthCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Authorization Identifier. Payment Authorization Record. This aggregate is provided in cases where the server keeps the payment authorizations record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Cancelled.
<PmtAuthId> <PmtAuthRec>
Version 1.7
April 2005
75
7.7.4Payment Authorization Inquiry

7.7.4.1 Request <PmtAuthInqRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Input Aggregate
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Identifier Aggregate see section 3.2.10.2 Aggregate see section 3.2.10.1 Open Enum
Optional
<PmtAuthId> <SelRangeCurAmt>
Payment Authorization Identifier. Used as a selection criterion. Selection Range Currency Amount. Used as a selection criterion. Date Selection Range. Used as a selection criterion.
<SelRangeDt>
Optional
<DeliveryMethod>
7.7.4.2 Response <PmtAuthInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
76
April 2005
Version 1.7
Tag
Type
Usage
Description
<RecCtrlOut>
Optional
<PmtAuthId>
Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
Payment Authorization Identifier.
<SelRangeCurAmt>
Aggregate see section 3.2.10.2 Aggregate see section 3.2.10.1 Open Enum Aggregate see section 7.3.5
Selection Range Currency Amount. Used as a selection criterion. Date Selection Range. Used as a selection criterion.
<SelRangeDt>
<DeliveryMethod> <PmtAuthRec>
Delivery Method. Payment Authorization Record. One aggregate for each record matching the selection criteria in the request.
7.7.5Payment Authorization Audit

7.7.5.1 Request <PmtAuthAudRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
Version 1.7
April 2005
77
Tag
<SelRangeDt>
Type
Usage
Optional
Description
<Method>
Optional Repeating
Payment Action. Valid values: Add, Mod, Can This field is used as a selection criterion.
<PmtAuthId>
Identifier
Optional Repeating
Payment Authorization Identifier. Assigned by the server at the time the Payment Authorization is first added. Cannot be modified by the client. This field is used as a selection criterion.
7.7.5.2 Response <PmtAuthAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed
<SelRangeDt>
<Method>
Payment Method.
<PmtAuthId>
Payment Authorization Identifier. Assigned by the server at the time the Payment Authorization is first added. Cannot be modified by the client. This field is used as a selection criterion.
<PmtAuthMsgRec>
Optional Repeating
Payment Authorization Message Record Aggregate.
78
April 2005
Version 1.7
7.7.5.2.1 Payment Authorization Message Record Aggregate <PmtAuthMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created. Add Payment Authorization Response Message Aggregate.
<MsgRecDt> <PmtAuthAddRs>
<PmtAuthModRs>
Modify Payment Authorization Response Message Aggregate. Cancel Payment Authorization Response Message Aggregate. Reversal Payment Authorization Response Message Aggregate.
<PmtAuthCanRs>
<PmtAuthRevRs>
7.7.6Payment Authorization Synchronization

7.7.6.1 Request <PmtAuthSyncRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
Version 1.7
April 2005
79
Tag
<Token>
Type
Identifier
Usage
Required
Description
7.7.6.2 Response <PmtAuthSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Optional
<Token>
Required Echoed
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Payment Authorization Message Record Aggregate.
<PmtAuthMsgRec>
Optional Repeating
80
April 2005
Version 1.7
7.7.7Payment Authorization Reversal

7.7.7.1 Request <PmtAuthRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Payment Authorization Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <PmtAuthMsgRqInfo>
Open Enum C-80 Aggregate
7.7.7.1.1 Payment Authorization Message Request Information Aggregate <PmtAuthMsgRqInfo>

Tag
<PmtAuthAddRq>
Type
Usage
Description
Payment Authorization Add Request Message Aggregate.
<PmtAuthModRq>
Payment Authorization Modify Request Message Aggregate.
<PmtAuthCanRq>
Payment Authorization Cancel Request Message Aggregate.
<PmtAuthAudRq>
Payment Authorization Audit Request Message Aggregate.
<PmtAuthSyncRq>
Payment Authorization Synchronization Request Message Aggregate.
Version 1.7
April 2005
81
7.7.7.2 Response <PmtAuthRevRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <PmtAuthMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Payment Authorization Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
7.8Remittance
7.8.1Remittance Add
The Remittance Add message allows a client to transmit a remittance advice to a BPP or BSP for posting.
7.8.1.1 Request <RemitAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
82
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date the payment was processed by the CPP. It is used for remittance advice from CPP to BPP. The date can be used by the BPP to associate the date the payment was processed with the posting date. This date should match the date settlement to the BPP/Biller was initiated. Remittance Record Aggregate. Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new remittance being added.
<EffDt>
DateTime
Required
<RemitInfo>
Required Optional
<DupChkOverride>
7.8.1.2 Response <RemitAddRs>

The <RemitAddRs> message is used to provide an acknowledgement to a CPP-initiated <RemitAddRq>. It is also used in the Remittance Audit Response <RemitAudRs> to communicate to the client that remittances have been added by the CPP using <RemitAddRq>.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date the payment was processed by the CPP. It is used for remittance advice from CPP to BPP. The date can be used by the BPP to associate the date the payment was processed with the posting date. This date should match the date settlement to the BPP/Biller was initiated.
<EffDt>
DateTime
Required Echoed
Version 1.7
April 2005
83
Tag
<RemitInfo>
Type
Aggregate see section 7.3.6.1 Boolean Aggregate see section 7.3.6 Identifier
Usage
Description
Remittance Record Aggregate. Duplicate Check Override Flag. Remittance Record Aggregate.
<DupChkOverride> <RemitRec>
<SPRefId>
Optional
7.8.2Remittance Modify
The Remittance Modify message allows a client to modify the current information about a Remittance that was set up using the Remittance Add message.
7.8.2.1 Request <RemitModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier. Assigned by the server at the time the Remittance is first added. Cannot be modified by the client. Effective Date. The date the payment was processed by the CPP. It is used for remittance advice from CPP to BPP. The date can be used by the BPP to associate the date the payment was processed with the posting date. This date should match the date settlement to the BPP/Biller was initiated. Remittance Information Aggregate. Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new remittance being added.
<RemitId> <EffDt>
Identifier DateTime
Required Required
<RemitInfo>
Required
<DupChkOverride>
Optional
84
April 2005
Version 1.7
7.8.2.2 Response <RemitModRs>

The <RemitModRs> message is used to provide an acknowledgement to a CSP-initiated <RemitModRq>. It is also used in the Remittance Audit Response <RemitAudRs> to communicate to the client that the customer has modified remittances by using <RemitModRq>.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date the payment was processed by the CPP. It is used for remittance advice from CPP to BPP. The date can be used by the BPP to associate the date the payment was processed with the posting date. This date should match the date settlement to the BPP/Biller was initiated. Remittance Identifier. Remittance Record Aggregate.
<EffDt>
DateTime
Required Echoed
<RemitId> <RemitInfo>
Identifier Aggregate see section 7.3.6.1 Boolean Aggregate see section 7.3.6 Identifier
Required Echoed Required Echoed Optional Echoed Required
<DupChkOverride> <RemitRec>
Duplicate Check Override Flag. Remittance Record Aggregate.
<SPRefId>
Optional
7.8.3Remittance Status Modify

7.8.3.1 Request <RemitStatusModRq>
The client must specify the remittance identifier along with the status.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
Version 1.7
April 2005
85
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier Aggregate. Assigned by the server at the time the Remittance is first added. Cannot be modified by the client. Used to reference a specific remittance.
<RemitId>
Identifier
Required
<RemitStatus>
Required
Remittance Status Aggregate.
7.8.3.2 Response <RemitStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier. Remittance Status Aggregate.
<RemitId> <RemitStatus>
Identifier Aggregate see section 7.3.6.3 Identifier
Required Echoed Required Echoed Optional
<CSPRefId>
Financial Institution Reference Number.
86
April 2005
Version 1.7
Tag
<SPRefId>
Type
Identifier
Usage
Optional
Description
Service Provider Reference Number.
7.8.4Remittance Delete
The Delete Remittance message allows a client to delete a Remittance that was set up using the Remittance Add message.
7.8.4.1 Request <RemitDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier. Assigned by the server at the time the Remittance is first added. Cannot be modified by the client.
<RemitId>
Identifier
Required
7.8.4.2 Response <RemitDelRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by a client as a universally unique identifier for the message. Used to correlate responses with requests. Server must return <RqUID> if provided by client in a <PmtCanRq>.
<RqUID>
Required Echoed
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
87
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier Remittance Record Aggregate. This aggregate is provided in cases where the server keeps the remittance record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Deleted. Service Provider Reference Identifier.
<RemitId> <RemitRec>
<SPRefId>
Identifier
Optional
7.8.5Remittance Inquiry
7.8.5.1 Request <RemitInqRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier. Used as a selection criterion. Selection Range Currency Amount. Used as a selection criterion. Date Selection Range. Used as a selection criterion.
<RemitId> <SelRangeCurAmt>
Identifier Aggregate see section 3.2.10.2 Aggregate see section 3.2.10.1 Open Enum
<SelRangeDt>
Optional
<DeliveryMethod>
88
April 2005
Version 1.7
7.8.5.2 Response <RemitInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Remittance Identifier.
<RemitId>
Identifier
Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
<SelRangeCurAmt>
Aggregate see section 3.2.10.2 Aggregate see section 3.2.10.1 Open Enum Aggregate see section 7.3.6
Selection Range Currency Amount. Used as a selection criterion. Date Selection Range. Used as a selection criterion.
<SelRangeDt>
<DeliveryMethod> <RemitRec>
Delivery Method. Remittance Record Aggregate.
7.8.6Remittance Audit
Remittance Audit allows a client to audit Remittance Add/Modify/Delete messages associated with the current customer. When the <RemitStatus> changes, the server must generate an Rs message to the Rq that created the pending state. The <Status> <Severity> must always be Info.
7.8.6.1 Request <RemitAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
89
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Remittance Method. Valid Values: Add, Mod, Del This field is used as a selection criterion.
<RemitId>
Identifier
Optional Repeating
Remittance Identifier. Assigned by the server at the time the remittance is first added. Cannot be modified by the client. This field is used as a selection criterion.
7.8.6.2 Response <RemitAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
Optional
90
April 2005
Version 1.7
Tag
<SelRangeDt>
Type
Aggregate see section 3.2.10.1 Closed Enum Identifier
Usage
Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
Description
<Method>
Remittance Method.
<RemitId>
Remittance Identifier. Assigned by the server at the time the remittance is first added. Cannot be modified by the client. This field is used as a selection criterion. Remittance Message Record Aggregate.
<RemitMsgRec>
7.8.6.2.1 Remit Message Record Aggregate <RemitMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created. Remittance Add Response Message Aggregate.
<MsgRecDt> <RemitAddRs>
<RemitModRs>
Remittance Modify Response Message Aggregate.
<RemitStatusModRs>
Remittance Status Modify Response Message Aggregate.
<RemitDelRs>
Remittance Delete Response Message Aggregate.
<RemitRevRs>
Remittance Reversal Response Message Aggregate.
7.8.7Remittance Synchronization
A client uses the Remittance Synchronization message to retrieve a list of changes that have occurred to a clients remittance. This message will commonly be used to enable a client to synchronize with the server to get up-to-date status information about a remittance. The results of this message typically will status change of a remittance advice.
Version 1.7
April 2005
91
7.8.7.1 Request <RemitSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or 0 for first time requests.
7.8.7.2 Response <RemitSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Message Respoonse Header aggregate.
92
April 2005
Version 1.7
Tag
<RecCtrlOut>
Type
Usage
Optional
Description
<Token>
Required Echoed
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or 0 for first time requests.
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. Remittance Message Record Aggregate.
<RemitMsgRec>
Optional Repeating
7.8.8Remittance Reversal
7.8.8.1 Request <RemitRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Remit Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <RemitMsgRqInfo>
7.8.8.1.1 Remit Message Request Information Aggregate <RemitMsgRqInfo>

Tag
<RemitAddRq>
Type
Usage
Required XOR
Description
Remit Add Request Message Aggregate.
Version 1.7
April 2005
93
Tag
<RemitModRq>
Type
Usage
Description
Remit Modify Request Message Aggregate.
<RemitStatusModRq>
Remit Status Modify Request Message Aggregate.
<RemitDelRq>
Remit Delete Request Message Aggregate.
<RemitInqRq>
Remit Inquiry Request Message Aggregate.
<RemitAudRq>
Remit Audit Request Message Aggregate.
<RemitSyncRq>
Remit Synchronization Request Message Aggregate.
7.8.8.2 Response <RemitRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <RemitMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Remit Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
94
April 2005
Version 1.7
7.9Recurring Payment Model

7.9.1Recurring Payment Model Add
The Recurring Payment Model Add message allows a client to set up a recurring or repeating payment where the payment amount is the same. Examples of these types of payments are mortgages, car loans, equity loans, etc. The initial and/or final payment amount may be different from the normal recurring payment amount if supported by the Pay provider.
7.9.1.1 Request <RecPmtAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Information Aggregate.
<PmtInfo>
Required
<RecModelInfo>
Required Optional Profiled support
<DupChkOverride>
Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new recurring payment model being added.
7.9.1.2 Response <RecPmtAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
Version 1.7
April 2005
95
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Information Aggregate.
<PmtInfo>
Required Echoed Required Echoed Optional Profiled support Echoed Required
<RecModelInfo>
<DupChkOverride>
Duplicate Check Override Flag.
<RecPmtRec>
Recurring Payment Model Record Aggregate.
Optional Optional
7.9.2Recurring Payment Instance Add

The Recurring Payment Instance Add message allows a client to manually trigger the spawning of a payment instance from a Recurring Payment Model that has its frequency value defined as Manually. This message is particularly useful when payments to a specific payee need to occur on an irregular frequency basis or perhaps when a client desires direct control of the spawning to manually override certain elements of each payment instance. Values provided within <DueDt>, <CurAmt>, <RemitInstruction>, <RemitDetail>, and <PmtLegalRpt> override the values already specified within the recurring payment model specified by <RecPmtId>.
7.9.2.1 Request <RecPmtInstAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
96
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Payment Model Identifier. The identifier for the recurring payment model. Due Date. The date that the payment is due. Currency Amount. The total amount being debited from the funding account. If this element is not present, the amount specified in the recurring model referenced by <RecPmtId> is the intended amount. Remittance Instruction.
<RecPmtId> <DueDt> <CurAmt>
Identifier DateTime Currency Amount
Required Required Optional
<RemitInstruction>
Optional
<RemitDetail>
Remittance Detail.
<PmtLegalRpt>
Payment Legal Reporting Aggregate.
7.9.2.2 Response <RecPmtInstAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Payment Model Identifier. The identifier for the recurring payment model. Due Date. The date that the payment is due.
<RecPmtId> <DueDt>
Identifier DateTime
Version 1.7
April 2005
97
Tag
<CurAmt>
Type
Currency Amount
Usage
Optional Echoed
Description
Currency Amount. The total amount being debited from the funding account. If this element is not present, the amount specified in the recurring model referenced by <RecPmtId> is the intended amount. Remittance Detail.
<RemitDetail>
Aggregate see section 7.3.6.2.1 Aggregate see section 7.3.6.2.6 Aggregate see section 7.3.3
Optional Repeating Echoed Optional Echoed Required
<PmtLegalRpt>
Payment Legal Reporting Aggregate.
<PmtRec>
Payment Record.
7.9.3Recurring Payment Model Modify

The Modify Recurring Payment Model message allows a client to modify the current definition of a recurring or repeating payment. Whether a modification to the model affects any current pending payment instance(s) from the model depends on profile settings and the message contents.
7.9.3.1 Request <RecPmtModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Cannot be modified by the client. Payment Information Aggregate.
<RecPmtId>
Identifier
Required
<PmtInfo>
Required
Note: If the server supports Customer Payee lists, the Payee must be specified using <PmtInfo> <CustPayeeId>.
Required Recurring Model Information Aggregate.
<RecModelInfo>
98
April 2005
Version 1.7
Tag
<ModPending>
Type
Boolean
Usage
Description
Modify Pending Indicator. If set to True, all pending payment instances that were automatically generated from the recurring model that is being modified must also be modified. If absent or set to False, only the model is modified; any pending payments must remain unaffected by the modification of the model. This element must be ignored unless <ModPendingType> in the Pay Service Profile = IfRequested.
7.9.3.2 Response <RecPmtModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Information Aggregate.
<PmtInfo>
Required Echoed Required Echoed Optional Profiled support Echoed Required
<RecModelInfo>
Recurring Model Information Aggregate. Modify Pending Flag.
<ModPending>
<RecPmtRec>
Recurring Payment Model Record Aggregate.
Optional Optional
7.9.4Recurring Payment Model Cancel

The Recurring Payment Model Cancel message allows a client to cancel a customers Recurring Payment Model. Cancellation of a Recurring Payment Model always also cancels any pending Payments that were generated from that model.
Version 1.7
April 2005
99
7.9.4.1 Request <RecPmtCanRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Cannot be modified by the client. Cascade Delete. If True, server must delete all dependent payments when this model is deleted. If False or omitted, the model must not be deleted if dependent payments exist.
<RecPmtId>
Identifier
Required
<CascadeDel>
Boolean
Optional
7.9.4.2 Response <RecPmtCanRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Recurring Payment Model Identifier. Cascade Delete.
<RecPmtId> <CascadeDel>
Identifier Boolean
100
April 2005
Version 1.7
Tag
<RecPmtRec>
Type
Usage
Optional XOR
Description
Recurring Payment Record. This aggregate is provided in cases where the server keeps the recurring payment models record on the server even after receiving a deletion request. This may occur if the deletion is not immediate, or if the server maintains the record with a status of Cancelled. Open Enum containing a list of dependent object types that exist for the model. Valid values: Pmt Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
<DependentType>
Open Enum
Optional XOR Repeating Optional Optional
7.9.5Recurring Payment Model Inquiry

The Recurring Payment Inquiry message allows a client to get a list of the current Recurring Payment Models. Clients that keep local copies of a customers Recurring Payment Models may use this message to refresh their copies of the customers Recurring Payment Models.
7.9.5.1 Request <RecPmtInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<RecPmtId>
Optional Repeating
Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. Cannot be modified by the client. This field is used as a selection criterion.
<CustPayeeId>
Identifier
Optional Repeating Optional XOR
Customers Payee Identifier. This field is used as a selection criterion. If the server supports Payee Lists, the server assigns <CustPayeeId> at the time the Payee is first added. Deposit Account Aggregate. Source account for payment. This field is used as a selection criterion.
<DepAcctIdFrom>
Version 1.7
April 2005
101
Tag
<CardAcctIdFrom>
Type
Usage
Optional XOR
Description
Card Account Identifier Aggregate. Source account for payment. This field is used as a selection criterion. Payment Category. The customer assigns categories. This field is used as a selection criterion. Memo for Payment. From Customer to Payee. This field is used as a selection criterion. Customer Account Number with Payee. This field is used as a selection criterion. Selection Range Amount Aggregate.
<Category>
<Memo>
C-255
<BillingAcct>
C-32
<SelRangeCurAmt>
<CSPRefId>
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<SPRefId>
Identifier
<IncToken>
Boolean
<DeliveryMethod>
Open Enum
7.9.5.2 Response <RecPmtInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RecCtrlOut>
102
April 2005
Version 1.7
Tag
<RecPmtId>
Type
Identifier
Usage
Optional Repeating Echoed Optional Repeating Echoed Optional XOR Echoed Optional XOR Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Repeating
Description
Recurring Payment Model Identifier.
<CustPayeeId>
Identifier
Customers Payee Identifier.
<DepAcctIdFrom>
Deposit Account Aggregate.
<CardAcctIdFrom>
<Category>
Payment Category.
<Memo>
C-255
Memo for Payment.
<BillingAcct>
C-32
Customer Account Number with Payee.
<SelRangeCurAmt>
<CSPRefId>
<SPRefId>
Identifier
<IncToken> <DeliveryMethod> <RecPmtRec>
Boolean Open Enum Aggregate see section 7.3.4.4 Identifier
Include Token. Delivery Method. Recurring Payment Model Record Aggregate. One record is returned for each of the customers Recurring Payment Models that meets the selection criteria specified in the request message Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
<Token>
Version 1.7
April 2005
103
7.9.6Recurring Payment Model Audit

7.9.6.1 Request <RecPmtAudRq>
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Recurring Payment Model Method. Valid values: Add, Mod, Can This field is used as a selection criterion.
<RecPmtId>
Identifier
Optional Repeating
Recurring Payment Model Identifier. Assigned by the server at the time the Recurring Payment Model is first added. This field is used as a selection criterion.
7.9.6.2 Response <RecPmtAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
104
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Selection Range Date Aggregate.
<RecCtrlOut>
<SelRangeDt>
<Method>
Recurring Payment Model Method.
<RecPmtId>
Recurring Payment Model Identifier.
<RecPmtMsgRec>
Recurring Payment Message Record Aggregate.
7.9.6.2.1 Recurring Payment Message Record Aggregate <RecPmtMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created. Add Recurring Payment Model Response Message Aggregate. Modify Recurring Payment Model Response Message Aggregate. Cancel Recurring Payment Model Response Message Aggregate. Reversal Recurring Payment Model Response Message Aggregate.
<MsgRecDt> <RecPmtAddRs>
<RecPmtModRs>
<RecPmtCanRs>
<RecPmtRevRs>
7.9.7Recurring Payment Model Sync

The Recurring Payment Model Sync message allows clients to retrieve a list of changes that have occurred to a customers Recurring Payment Models. This message may be used to enable a client that keeps local copies of a
Version 1.7
April 2005
105
Interactive Financial Exchange Business Message Specification customers Recurring Payment messages to synchronize its database against the one kept by the Pay provider. The results of this message tell a client what the customer has done using other clients since they last used this one.
7.9.7.1 Request <RecPmtSyncRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first-time requests.
7.9.7.2 Response <RecPmtSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
106
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first-time requests.
<RecCtrlOut>
<Token>
<NewToken>
Identifier
Required
Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it. If the client sent a token in the request, the server returns a new token based on this audit message.
<RecPmtMsgRec>
Optional Repeating
Recurring Payment Message Record Aggregate.
7.9.8Recurring Payment Model Reversal

7.9.8.1 Request <RecPmtRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal.
<RevReasonCode> <Desc>
Open Enum C-80
Required Optional
Version 1.7
April 2005
107
Tag
<RecPmtMsgRqInfo>
Type
Aggregate
Usage
Required
Description
Recurring Payment Model Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
7.9.8.1.1 Recurring Payment Model Message Request Information Aggregate <RecPmtMsgRqInfo>

Tag
<RecPmtAddRq>
Type
Usage
Optional
Description
Recurring Payment Model Add Request Message Aggregate.
<RecPmtInstAddRq>
Optional
Recurring Payment Instance Add Request Message Aggregate. Recurring Payment Model Modify Request Message Aggregate. Recurring Payment Model Cancel Request Message Aggregate. Recurring Payment Model Inquiry Request Message Aggregate. Recurring Payment Model Audit Request Message Aggregate. Recurring Payment Model Synchronization Request Message Aggregate.
<RecPmtModRq>
Optional
<RecPmtCanRq>
Optional
<RecPmtInqRq>
Optional
<RecPmtAudRq>
Optional
<RecPmtSyncRq>
Optional
7.9.8.2 Response <RecPmtRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
108
April 2005
Version 1.7
Tag
<RevReasonCode> <Desc> <RecPmtMsgRqInfo>
Type
Usage
Description
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Recurring Payment Model Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
7.10
Payment Acknowledgement
Upon the receipt of a payment request <PmtAddRq>, it is the fiduciary responsibility of the banking partner (CPP) to supply to the client an acknowledgment of the various processing cycles in an event driven environment. The acknowledgments are both positive and negative, indicating successful and unsuccessful application processing, respectively, of the payment transaction sent. This is an event driven process. The client is obligated to build a business process to review these messages within a defined timeline for applicable handling of failed messages by the client. All successful notifications assume that the payment has been forwarded to the appropriate payment platform for settlement processing. The client has the responsibility to notify the banking partner of non-receipt of the acknowledgment. The acknowledgments contain both summary information (total number of payments and dollars accepted, rejected, and changed) along with detail information for each payment file or group of payments transmitted. There are payment systems which also generate acknowledgments when the file is received by that specific payment system along with another acknowledgment which carries a reference number assigned by that payment system. Example: A wire payment transaction has been acknowledged as successful by the banking application system and has been passed to the wire platform system. This platform acknowledges receipt of the transaction by creating an acknowledgment message. During the processing cycle, a unique fed reference number is assigned to the transaction and is communicated to the client via another acknowledgment. This fed reference number is then tied back to the original transaction for tracking and archiving purposes. Level 1, Acknowledgment Summary and Detail: Validation of application processing for all transactions requested; supplies counts and values at a summary level; positive or negative acceptance supplied at detail level. Level 2, Acknowledgment Detail: Validation of receipt of transaction at Payment Network; single transaction based process Level 3, Acknowledgment Detail: Validation of network processing and return of trace reference number; single transaction based process The payment document number and AP batch number is recorded in the customers general ledger for account reconciliation processing after the payment has been settled. These are two keys that are required to be carried throughout the payment cycle and acknowledgment process for final reconciliation by the customer. Depicted below is a sample of this flow:
Version 1.7
April 2005
109
Customer General Ledger
<PmtAddRq>
CPP
Payment Networks
Level 1 Acknowledgment Summary & Detail
Receipt & Processed by Application
CPP
Receipt of File from CPP
CPP
Processed by Network; Trace Number Assigned
7.10.1
Payment Acknowledgment Inquiry
A customer may send a request to the CPP inquiring about the consolidated summary of a single or group of payments submitted for processing.
7.10.1.1 Request <PmtAckInqRq>

The user must specify the payment reference identifier.
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Selection Range Due Date Aggregate. This is used as a selection criterion.
<SelRangeDueDt>
Optional
110
April 2005
Version 1.7
Tag
<SvcRqUID>
Type
UUID
Usage
Optional
Description
Service Request Identifier. The payment file identifier that was created by the payer in the Accounts Payable system when the file is created and sent. This is used as a selection criterion.
7.10.1.2 Response <PmtAckInqRs>

The CPP may respond to the <PmtAckInqRq> with the following <PmtAckInqRs>, acknowledging the receipt and application processing of the single or group of payments processed within the Pay Service.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
Message Rewsponse Header aggregate.
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Selection Range Due Date Aggregate.
<SelRangeDueDt>
Aggregate see section 3.2.10.1 UUID Aggregate see section 7.3.13 Identifier Identifier
<SvcRqUID> <PmtAckRec>
Service Request Identifier. Payment Acknowledgment Record Aggregate. Contains acknowledgment records at a consolidated or summarized level applicable to a <SvcRqUID>, or batch of payments submitted by the customer. Financial Institution Reference Number. Service Provider Reference Number.
Optional Optional
7.10.2
Tag
<RqUID>
Payment Acknowledgment Reversal

Type
UUID
7.10.2.1 Request <PmtAckRevRq>

Usage
Required
Description
Request Identifier.
Version 1.7
April 2005
111
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Payment Acknowledgement Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <PmtAckMsgRqInfo>
7.10.2.1.1 Payment Acknowledgement Message Request Information <PmtAckMsgRqInfo>

Tag
<PmtAckInqRq>
Type
Usage
Optional
Description
Payment Acknowledgement Inquiry Request Message Aggregate.
7.10.2.2 Response <PmtAckRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
112
April 2005
Version 1.7
Tag
<RevReasonCode> <Desc> <PmtAckMsgRqInfo>
Type
Open Enum C-80 Aggregate see section 7.10.2.1.1 Identifier Identifier
Usage
Required Echoed Optional Echoed Required Echoed
Description
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Payment Acknowledgement Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
7.10.3
Payment Acknowledgment Advise
PmtAckAdvise message is used to acknowledge the receipt and application processing of a single or group of payments processed within the Pay Service.
7.10.3.1 Request <PmtAckAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Acknowledgment Record Aggregate. Contains acknowledgment records at a consolidated or summarized level applicable to a <SvcRqUID>, or batch of payments submitted by the customer.
<PmtAckRec>
Required
7.10.3.2 Response <PmtAckAdviseRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID
Usage
Required
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Message Request Header Aggregate.
<MsgRqHdr>
Optional Echoed Optional Echoed Required Echoed
<MsgRsHdr>
<RqUID>
Version 1.7
April 2005
113
Tag
<CustId>
Type
Usage
Optional Echoed
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Payment Acknowledgment Record Aggregate. Contains acknowledgment records at a consolidated or summarized level applicable to a <SvcRqUID>, or batch of payments submitted by the customer. Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a payment corresponding to a confirmation number that was returned to the client when the payment was added or modified. When a payment has been modified, only the <CSPRefId> received in the most recent <ChksumAdviseRs> is valid. Service Provider Reference Identifier. Same usage as <CSPRefId>.
<PmtAckRec>
Required Echoed
<CSPRefId>
Optional Repeating
<SPRefId>
Identifier
Optional Repeating
7.11
7.11.1
Batch Checksum
Checksum Add
The Checksum Add message allows a client to provide a chechsum record against which the server can verify scheduled payments, where the control data such as sum amount and count are provided to the server. The Checksum Add message can be sent together with or separate from the payment messages within a pay service to facilitate both cases where the control record is sent via the same or different routes due to authorization and segregation reasons.
7.11.1.1 Request <ChksumAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
114
April 2005
Version 1.7
Tag
<SvcRqUID>
Type
UUID
Usage
Optional
Description
Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. Payment Control Information Aggregate. Provides the checksums used by the server to validate a payment batch.
<ChksumInfo>
Required
7.11.1.2 Response <ChksumAddRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Aggregate see section 7.3.10.1 Aggregate see section 7.3.10 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed Required
Asynchronous Request Identifier. Customer Identifier.
<SvcRqUID> <ChksumInfo>
Pay Service Request Identifier. Payment Control Info.
<ChksumRec>
Checksum Control Record Aggregate.
Optional Optional
Customer Service Reference Provider Identifier. Service Provider Reference Identifier.
7.11.2
Tag
<RqUID>
Checksum Modify
Type
UUID
7.11.2.1 Request <ChksumModRq>

Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
115
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional
Description
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. Checksum Control Identifier. Assigned by the server at the time the Checksum Control is first added. Cannot be modified by the client. Payment Control Information Aggregate. Provides the checksums used by the server to validate a payment batch.
<SvcRqUID>
UUID
Optional
<ChksumId>
Identifier
Required
<ChksumInfo>
Required
7.11.2.2 Response <ChksumModRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Aggregate see section 7.3.10.1
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed Required Echoed
<SvcRqUID> <ChksumId> <ChksumInfo>
Pay Service Request Identifier. Checksum Control Identifier. Payment Control Info.
116
April 2005
Version 1.7
Tag
<ChksumRec>
Type
Usage
Required
Description
Checksum Control Record Aggregate.
Optional Optional
7.11.3
Tag
<RqUID>
Checksum Status Modify

Type
UUID
7.11.3.1 Request <ChksumStatusModRq>

Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. Checksum Control Identifier. Assigned by the server at the time the Checksum Control is first added. Cannot be modified by the client. Checksum Control Status Aggregate.
<SvcRqUID>
UUID
Optional
<ChksumId>
Identifier
Required
<ChksumStatus>
Required
7.11.3.2 Response <ChksumStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
Version 1.7
April 2005
117
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Aggregate see section 7.3.10.2 Identifier Identifier
Usage
Description
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed Required Echoed Optional Optional
<SvcRqUID> <ChksumId> <ChksumStatus>
Pay Service Request Identifier. Checksum Control Identifier. Chechkum Control Status Aggregate.
7.11.4
Tag
<RqUID>
Checksum Delete
Type
UUID
7.11.4.1 Request <ChksumDelRq>

Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. Checksum Control Identifier. Assigned by the server at the time the Checksum Control is first added. Cannot be modified by the client.
<SvcRqUID>
UUID
Optional
<ChksumId>
Identifier
Required
118
April 2005
Version 1.7
7.11.4.2 Response <ChksumDelRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Aggregate see section 7.3.10 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed Optional
<SvcRqUID> <ChksumId> <ChksumRec>
Pay Service Request Identifier. Checksum Control Identifier. Checksum Control Record Aggregate.
Optional Optional
7.11.5
Tag
<RqUID>
Checksum Inquiry
Type
UUID
7.11.5.1 Request <ChksumInqRq>

Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Version 1.7
April 2005
119
Tag
<SvcRqUID>
Type
UUID
Usage
Optional
Description
Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. This is used as a selection criterion.
<ChksumId>
Identifier
Required
Checksum Identifier. Assigned by the server at the time the Payment is first added. Cannot be modified by the client. This is used as a selection criterion.
<ChksumStatusCode>
Open Enum
Required
Checksum Status Code. This identifies the remittance status. Defined values: Pending, Posted, Refused, Rejected, Returned, DelPend, Deleted This is used as a selection criterion.
7.11.5.2 Response <ChksumInqRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 UUID Identifier Open Enum Aggregate see section 7.3.10
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional Echoed Required Echoed Required Echoed Optional
<SvcRqUID> <ChksumId> <ChksumStatusCode> <ChksumRec>
Pay Service Request Identifier. Checksum Identifier. Checksum Status Code. Checksum Record Aggregate.
120
April 2005
Version 1.7
7.11.6
Tag
<RqUID>
Checksum Audit
Type
UUID
7.11.6.1 Request <ChksumAudRq>

Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
Selection Range Date Aggregate. This is used as a selection criterion.
<Method>
Optional Repeating
Method. Valid Values: Add, Mod, Can This is used as a selection criterion.
<ChksumId>
Identifier
Optional Repeating
Checksum Control Identifier. This is used as a selection criterion.
7.11.6.2 Response <ChksumAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
121
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Identifier Aggregate see section 7.11.6.2.1
Usage
Optional Echoed Optional but see Description Optional Echoed Optional Repeating Echoed Optional Echoed Optional Repeating
Description
<RecCtrlOut>
<SelRangeDt>
<Method>
Payment Method.
<ChksumId> <ChksumMsgRec>
Checksum Identifier. Checksum Message Record Aggregate.
7.11.6.2.1 Checksum Message Record Aggregate <ChksumMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date when this audit record is created. Checksum Add Response Message Aggregate.
<MsgRecDt> <ChksumAddRs>
<ChksumModRs>
Checksum Modify Response Message Aggregate.
<ChksumStatusModRs>
Checksum Status Modify Response Message Aggregate.
<ChksumDelRs>
Checksum Delete Response Message Aggregate.
7.11.7
Tag
<RqUID>
Checksum Synchronization
Type
UUID
7.11.7.1 Request <ChksumSyncRq>

Usage
Required
Description
122
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<Token>
Required
7.11.7.2 Response <ChksumSyncRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional
<RecCtrlOut>
<Token> <NewToken>
Token. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is only significant to the server that originally assigned it.
Version 1.7
April 2005
123
Tag
<ChksumMsgRec>
Type
Usage
Optional Repeating
Description
Checksum Message Record Aggregate.
7.11.8
Checksum Advise
ChksumAdvise message is used to advise an entity of the processing status of a batch of transactions. This message would subsequently be sent in response to the ChksumAdd message set.
7.11.8.1 Request <ChksumAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. Checksum Control Record Aggregate.
<SvcRqUID>
UUID
Optional
<ChksumRec>
<ChksumId> <ChksumStatus>
Checksum Identifier. Assigned by the server at the time the Payment is first added. Checksum Status Aggregate.
7.11.8.2 Response <ChksumAdviseRs>

Tag
<Status>
Type
Usage
Required
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Message Request Header Aggregate.
<MsgRqHdr>
<MsgRsHdr>
<RqUID>
Required Echoed
124
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Usage
Description
<CustId>
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Pay Service Request Identifier. Identifier for the payment file generated by the client. This must be the same as the <RqUID> of <PaySvcRq>, so that the server can match it to the <PaySvcRq> containing the associated payments. Checksum Control Record Aggregate.
<SvcRqUID>
UUID
Optional Echoed
<ChksumRec>
Required XOR Echoed Required XOR Echoed Required Echoed Optional Repeating
<ChksumId>
Checksum Identifier. Assigned by the server at the time the Payment is first added. Checksum Status Aggregate.
<ChksumStatus>
<CSPRefId>
Customer Service Provider Reference Identifier. <CSPRefId> is used to inquire about a payment corresponding to a confirmation number that was returned to the client when the payment was added or modified. When a payment has been modified, only the <CSPRefId> received in the most recent <ChksumAdviseRs> is valid. Service Provider Reference Identifier. Same usage as <CSPRefId>.
<SPRefId>
Identifier
Optional Repeating
7.12
Comprehensible Remittance
In order to facilitate collection of check payments made to the biller, lockbox relationships are established with a bank(s) throughout a regional location. The lockbox addresses are generally located in major cities in the region, i.e., San Francisco, Chicago, Dallas, Atlanta, etc. Boxes are at the post office site with direct delivery of items to the applicable bank lockbox processing site. Multiple deliveries can be made throughout the day. The lockbox sites take a delivery from the post office and process the data, identifying each delivery as a batch. There are multiple cutoff times during the day for this processing which can result in multiple deposits being posted to an account. A batch or multiple batches are processed and posted to the billers account as a lockbox deposit. The batch information includes a batch number, item count of checks, batch total amount, processing date and lockbox number. The lockbox site process includes the following: Opening envelopes containing check and one or more documents (invoice, correspondence, etc.) Data input or scanning of check information with verification of specific data either by data input or voice activation Data input or scanning of remittance detail associated with a check (based on instructions agreed out of band between biller and bank) Imaging of check and documents associated with check
Version 1.7
April 2005
125
Interactive Financial Exchange Business Message Specification Mailing of copy of image of check with documents to biller (ranges from overnight to a infinite number of days based on agreement) Providing biller with CD Rom with images of check and documents or URL to viewing and/or obtain images on-line The biller imports electronic data into their Accounts Receivable data base to perform cash posting processes. Utilizing identified data elements to successfully match payment with outstanding bills on the account, cash posting can result in a successful match and removal of the receivables item(s). Failures would result in exception processing requiring a copy of the check and/or documents sent with the check or obtaining the image of the check and associated documents. This process can also be facilitated via manual input by the Cash Application department. Processes also exist to post the payment on the AR account if the appropriate MICR information is matched. This includes the Payor Bank Id and the Payor Account Number. Individual items are still required to be reconciled, but the payment is posted on the account for credit facilitation and statistical calculations. The Treasury and/or Cash Application departments at the biller require the batch information to reconcile the number of items processed at the lockbox site vs. the number of items processed during the cash application (whether automated or manual). Dependent upon the posting process, the total amount of the batches are also reconciled to the posted deposit amount on the account. Services are provided by various FIs to send a message to a client containing all of the receipts information received from various sources: ACH, lockbox, and wires. Therefore, a comprehensible receipts message could be facilitated from a lockbox remittance message. Depicted below is the flow for the process:
Checks sent to PO Lockbox
Delivery of PO Lockbox to Lockbox Processing Site
Lockbox Item Processing
Manual Input of Remittance Info
Data Import into Accounts Receivable
Transmission of the Data
Storage of Images for online or transmission
Data Format for Lockbox Remittance Data
Matching of Remittance Info to Outstanding AR items
Exception processing from Image or paper
7.12.1
Comprehensible Remittance Statement Add
The Comprehensible Remittance Statement Add message allows a financial institution to transmit lockbox remittance information along with electronic payment remittance information (ACH, low value, wires, or high value) to a client for posting.
126
April 2005
Version 1.7
7.12.1.1 Request <CompRemitStmtAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Effective Date. The date the remittance information was processed by the FI or CPP. Comprehensible Remittance Statement Information Aggregate. Duplicate Check Override Flag. When set to True, requests that the server not perform duplicate checking if any is normally performed. The client is affirming that this is a new remittance being added.
<EffDt> <CompRemitStmtInfo>
DateTime Aggregate see section 7.3.11.1 Boolean
Required Required
<DupChkOverride>
Optional
7.12.1.2 Response<CompRemitStmtAddRs>
Customers provide an acknowledgement to an FI initiated <CompRemitStmtAddRq> by sending a <CompRemitStmtAddRs> message.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
127
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 DateTime Aggregate see section 7.3.11.1 Aggregate see section 7.3.11 Identifier Identifier
Usage
Optional Echoed Required Echoed Required Echoed Required
Description
<EffDt> <CompRemitStmtInfo>
Effective Date. The date the remittance information was processed by the FI or CPP. Comprehensible Remittance Statement Information Aggregate. Comprehensible Remittance Statement Record Aggregate.
<CompRemitStmtRec>
Optional Optional
7.12.2
Comprehensible Remittance Statement Inquiry
The Comprehensible Remittance Statement Inquiry message allows a customer to inquiry about remittance information on a specific lockbox or deposit account.
7.12.2.1 Request <CompRemitStmtInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Aggregate see section 3.2.12.4.1 Aggregate see section 7.3.11.1.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.10.2
Optional
<LockboxDepId>
Lockbox Deposit Identifier.
<DepAcctId>
Deposit Account Id Aggregate.
<SelRangeCurAmt>
Selection Range Currency Amount. Used as a selection criterion.
128
April 2005
Version 1.7
Tag
<SelRangeDt>
Type
Usage
Optional
Description
Date Selection Range. Used as a selection criterion.
<IncToken>
Optional
Include Token. If True, a <Token> should be included in the response to set a base for future Sync messages. If False or omitted, no <Token> is returned. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<DeliveryMethod>
Open Enum
7.12.2.2 Response<CompRemitStmtInqRs>
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 7.3.11.1.1 Aggregate see section 3.2.7.2.2 Aggregate see section 3.2.10.2 Aggregate see section 3.2.10.1 Open Enum
Optional Echoed Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Lockbox Deposit Identifier.
<LockboxDepId>
<DepAcctId>
<SelRangeCurAmt>
Selection Range Currency Amount.
<SelRangeDt>
Date Selection Range.
<DeliveryMethod>
Delivery Method.
Version 1.7
April 2005
129
Tag
<CompRemitStmtRec>
Type
Usage
Required
Description
Comprehensible Remittance Statement Record Aggregate.
<Token>
Optional
Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant onlyl to the server that originally assigned it. The token is only included if <IncToken>=True in the request. <Token>=0 is returned if no records are returned within the response.
7.12.3
Comprehensible Remittance Statement Audit
A customer originates a Comprehensible Remittance Statement audit request to obtain all changes related to a particular comprehensible remittance addition by the FI.
7.12.3.1 Request <CompRemitStmtAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
Date Selection Range. Used as a selection criterion.
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited Valid values: Add, Mod, Delete. This field is used as a selection criterion.
<LockboxDepId>
Lockbox Deposit Identifier. This field is used as a selection criterion. Deposit Account Id Aggregate. This field is used as a selection criterion.
<DepAcctId>
130
April 2005
Version 1.7
7.12.3.2 Response <CompRemitStmtAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
<CustId>
Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Aggregate see section 7.3.11.1.1 Aggregate see section 3.2.7.2.2 Aggregate
Optional Echoed Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Date Selection Range.
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited. Lockbox Deposit Identifier.
<LockboxDepId>
<DepAcctId>
<CompRemitStmtMsgRec>
Comprehensive Remittance Statement Message Record Aggregate
7.12.4
Comprehensible Remittance Statement Synchronization

Type
UUID
7.12.4.1 Request <CompRemitStmtSyncRq>

Tag
<RqUID>
Usage
Required
Description
Version 1.7
April 2005
131
Tag
<MsgRqHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
<RecCtrlIn>
Optional
<LockboxDepId>
Lockbox Deposit Identifier. This field is used as a selection criterion. Deposit Account Id Aggregate. This field is used as a selection criterion. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<DepAcctId>
<Token>
7.12.4.2 Response<CompRemitStmtSyncRs>
Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
132
April 2005
Version 1.7
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 7.3.11.1.1 Aggregate see section 3.2.7.2.2 Identifier
Usage
Optional Echoed Optional but see Description Required XOR Echoed Required XOR Echoed Required Echoed
Description
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Lockbox Deposit Identifier.
<LockboxDepId>
<DepAcctId>
<Token>
<NewToken>
Identifier
Required
New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Comprehensive Remittance Statement Message Record Aggregate
<CompRemitStmtMsgRec>
Aggregate
Optional Repeating
7.12.4.2.1 Comprehensive Remittance Statement Message Record Aggregate <CompRemitStmtMsgRec>

Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Date. Date/time at which the audit record was stored/created by the service provider. Comprehensible Remittance Statement Add Response Message Aggregate. One record is returned for each Comprehensible Remittance Statement message, which meets the selection criteria specified in the request.
<MsgRecDt>
Timestamp
Optional
<CompRemitStmtAddRs>
Required
7.13
Pay Service Profile <PaySvcProfInfo>
The profile for the Pay Service is defined below. This profile is returned to the client in the Service Profile Inquiry <SvcProfInqRs> response and provides information on how the client should use the Pay Service.
Version 1.7
April 2005
133
Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service and version.
<MsgSupt>
Required Repeating
Supported Messages. This is a list of messages that are supported for Pay. The convention is to use the name of the message without the Rq or Rs so that each message is only listed once. Defined values: StdPayeeInq, CustPayeeAdd, CustPayeeMod, CustPayeeTypeMod, CustPayeeDel, CustPayeeInq, CustPayeeAud, CustPayeeSync, PmtAdd, PmtMod, PmtStatusMod, PmtStatusAdvise, PmtCan, PmtInq, PmtAud, PmtSync, PmtAuthAdd, PmtAuthMod, PmtAuthCan, PmtAuthInq, PmtAuthAud, PmtAuthSync, RemitAdd, RemitMod, RemitStatusMod, RemitDel, RemitInq, RemitAud, RemitSync, RecPmtAdd, RecPmtInstAdd, RecPmtMod, RecPmtCan, RecPmtInq, RecPmtAud, RecPmtSync, PmtAckInq, PmtAckAdvise, ChksumAdd, ChksumMod, ChksumStatusMod, ChksumDel, ChksumInq, ChksumAud, ChksumSync, ChksumAdvise, CompRemitStmtAdd, CompRemitStmtInq, CompRemitStmtAud, CompRemitStmtSync, PmtBatchAdd, PmtBatchCan, PmtBatchStatusAdvise, PmtBatchStatusInq
<OptSupt>
Open Enum
Optional Repeating
Options Supported. Defined values: AcctNickname, BillerPayee, CustPayee, CustPayeeNickName, ForEx, FSPayee, ImmediatePmt, LineItem, PmtMultiRemit, RecCtrl, RecFinalCurAmt, RecInitialCurAmt, Skip, SuppressEcho, XferPayee, AddReadOnlyAllowed
<PrcSched>
Optional
Processing Schedule Aggregate. If omitted, the default processing schedule is assumed.
<PmtModel>
Required
Payment Model. Indicates whether the client must enter the date that the server should initiate processing of the payment <PrcDt> or the date that the payment is due <DueDt> within the Payment Record Aggregate <PmtInfo>. Valid values: DueDt, PrcDt.
<DfltDaysToPay> <DfltXferDaysToPay> <DaysWith>
Long Long Long
Default Days to Pay. The default number of days required to complete the payment by check. Does not include transfers. Default Transfer Days to Pay. The default number of days required to complete the payment by transfer. Withdrawal Date Offset. Used in determination of date to withdraw funds from customer account. Usage is <DueDt> <DaysToPay> + <DaysWith> provides withdrawal date. NOTEIf the value of <DaysWith> is 1 then the withdrawal date is the same as <DueDt>.
<HistRetentionDays>
Long
Required
History Retention Days. Number of days after a message is processed that it is available for inquiries.
134
April 2005
Version 1.7
Tag
<DeliveryMethod>
Type
Open Enum
Usage
Optional Repeating
Description
Delivery Method. Used to request the delivery channel for requested information. Defined values: Channel, HomeBank, Post, UPS, Courier.
Note: although these are valid values for this element, they may not be appropriate for a particular message and may result in rejection. In that case, a response must be sent to the customer with an appropriate Status Code.
<ModPendingType> Closed Enum Required Payee Modify Pending specifies the rules used by the server to propagate changes to payees to pending single payments. Changes to payees are always propagated to payment models. Valid values: Always, Never, IfRequested. <RecPmtProf> Aggregate see section 7.13.1 Optional Recurring Payment Profile Aggregate.
7.13.1
Tag
<Freq>
Recurring Payment Profile Aggregate <RecPmtProf>

Type
Open Enum
Usage
Required Repeating
Description
Recurring Model Frequency. Usage is a list of supported frequencies. Defined values: Daily, Weekly, BiWeekly, TwiceMonthly, Monthly, EndOfMonth, FourWeeks, BiMonthly, Quarterly, SemiAnnually, Anually
<ModPendingType>
Closed Enum
Required
Client Modify Pending Type. Specifies the rules used by the server to propagate changes to recurring models to pending payments. Valid values: Always, Never, IfRequested.
7.14
7.14.1
Payment Batch
PmtBatch Add
The Payment Batch Add request message allows a client to transmit a batch of ISO 20022 defined payments along with remittance information. The payment batch will typically include one of more individual payments that are requests to move funds from a debtor to a creditor. Payment Batch Add messages are sent from an initiating party or forwarding institution to another forwarding institution, a settlement organization, or final agent. The element content and definition is contained within the schema and handbook located at ISO 20022 website. The IFX defined remittance detail can reside as an optional complex type within the payment transaction.
7.14.1.1 Request <PmtBatchAddRq>
Version 1.7
April 2005
135
Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtBatch Information Aggregate.
<CustId>
Optional
<PmtBatchInfo>
Required
7.14.1.2 Response <PmtBatchAddRs>

The Payment Batch Add response message is used to provide an acknowledgement to the initiating organization of the receipt of a payment batch. Although the underlying payment batch is an ISO 20022 message this will usually not be returned on the response message.
Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Required Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtBatch Information Aggregate.
<CustId>
Required Echoed
<PmtBatchInfo>
Required Echoed
136
April 2005
Version 1.7
Tag
<PmtBatchRec>
Type
Usage
Required
Description
PmtBatch Record Aggregate.
Optional Optional
7.14.2
PmtBatch Cancel
Provide description of the functionality of this message (request and response). The Payment Batch Cancel message allows for the initiating organization to cancel an entire batch of payments with one message. It will contain a reference to the original PmtBatchAddRq previously submitted.
7.14.2.1 Request <PmtBatchCanRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtBatch Identifier.
<CustId>
Optional
<PmtBatchId>
Identifier
Required
7.14.2.2 Response <PmtBatchCanRs>

The Payment Batch Cancel response message is used to provide an acknowledgement to the initiating organization of the receipt of a payment batch cancellation.
Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
Version 1.7
April 2005
137
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
<AsyncRqUID>
Required Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtBatch Identifier. PmtBatch Record Aggregate.
<CustId>
Required Echoed
<PmtBatchId> <PmtBatchRec>
Optional Optional
7.14.3
PmtBatch Status Inquiry
Provide description of the functionality of this message (request and response). The Payment Batch Status message can request status to be reported on at the Group level only or for each individual payment within the Group(s). Selection of either <PmtBatchStatusCode> or <PmtStatusCode> will determine the level of status information that would be contained in the response message.
7.14.3.1 Request <PmtBatchStatusInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
138
April 2005
Version 1.7
Tag
<PayorAcctId>
Type
Identifier
Usage
Optional
Description
Account Identifier. Related to the source account for payment. This identifier would be equivalent to <DbtrAcct><Id> in <pain.001.001.01> This field is used as a selection criterion.
<PayorName>
C-40
Optional
Payor Name. This would be equivalent to <Dbtr><Nm> in <pain.001.001.01> This field is used as a selection criterion.
<PmtBatchId>
Identifier
Optional Repeating
Payment Batch Identifier. Assigned by the server at the time the batch is first added. Cannot be modified by the client. This identifier would be equivalent to <GrpId> in <pain.001.001.01>. This field is used as a selection criterion.
<PmtRefId>
Identifier
Optional Repeating
Payment reference identifier. Identifier for the payment generated by the client. It can be the document generated by the Payers Accounts Payable system, or it can be the identifier equivalent to <EndtoEndId> in <pain.001.001.01>. This field is used as a selection criterion.
<SvcRqUID>
UUID
Optional
Service Request Identifier. The payment service request identifier that was created and sent by the client to the CPP. This field is used as a selection criterion.
<PmtRemitRefId>
Identifier
Optional Repeating
Payment Remittance (Credit) Reference Transaction Identifier. This identifier would be equivalent to <PmtRmtId> in <pain.001.001.01> This field is used as a selection criterion.
<ChkNum>
NC-12
Optional Repeating
Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. This would be equivalent to <ChqInstr><ChqNb> in <pain.001.001.01> This field is used as a selection criterion.
<CustPayeeId>
Identifier
Optional Repeating
Customers Payee Identifier. This field is used as a selection criterion. This identifier would be equivalent to <Cdtr><Id><OrgId> selection in <pain.001.001.01> This field is used as a selection criterion.
<CustPayeeName>
C-40
Optional Repeating
Payee Name. This would be equivalent to <Cdtr><Nm> in <pain.001.001.01> This field is used as a selection criterion.
<PmtBatchStatusCode>
Closed Enum
Optional Repeating XOR
Payment Batch Status Code. This identifies the payment batch processing status. This would be equivalent to <GrpSts> in <pain.002.001.01> Valid values: ACTC, ACCP, ACSP, ACSC, RCVD, PART, RJCT, PDNG This field is used as a selection criterion.
<PmtTrnStatusCode>
Closed Enum
Optional Repeating XOR
Payment Status Code. This identifies the payment processing status. This would be equivalent to <TxSts> in <pain.002.001.01> Valid values: ACTC, ACCP, ACSP, ACSC, RJCT, PDNG This field is used as a selection criterion.
Version 1.7
April 2005
139
Tag
<SelRangeDueDt>
Type
Usage
Optional
Description
Selection Range Due Date Aggregate. This would be equivalent to <ReqdExctnDt> in <pain.001.001.01> This field is used as a selection criterion.
7.14.3.2 Response <PmtBatchStatusInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Required Echoed
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Account Identifier. Related to the source account for payment. This identifier would be equivalent to <DbtrAcct><Id> in <pain.001.001.01> This field is used as a selection criterion.
<CustId>
Required Echoed
<PayorAcctId>
Identifier
Optional Echoed
<PayorName>
C-40
Optional Echoed
Payor Name. This would be equivalent to <Dbtr><Nm> in <pain.001.001.01> This field is used as a selection criterion.
<PmtBatchId>
Identifier
Payment Batch Identifier. Assigned by the server at the time the batch is first added. Cannot be modified by the client. This identifier would be equivalent to <GrpId> in <pain.001.001.01>. This field is used as a selection criterion.
<PmtRefId>
Identifier
Payment reference identifier. Identifier for the payment generated by the client. It can be the document generated by the Payers Accounts Payable system, or it can be the identifier equivalent to <EndtoEndId> in <pain.001.001.01>. This field is used as a selection criterion.
140
April 2005
Version 1.7
Tag
<SvcRqUID>
Type
UUID
Usage
Optional Echoed
Description
Service Request Identifier. The payment service request identifier that was created and sent by the client to the CPP. This field is used as a selection criterion.
<PmtRemitRefId>
Identifier
Payment Remittance (Credit) Reference Transaction Identifier. This identifier would be equivalent to <PmtRmtId> in <pain.001.001.01> This field is used as a selection criterion.
<ChkNum>
NC-12
Check Number. Assigned by the Pay provider or the CPP if payment is by paper check. This would be equivalent to <ChqInstr><ChqNb> in <pain.001.001.01> This field is used as a selection criterion.
<CustPayeeId>
Identifier
Customers Payee Identifier. This field is used as a selection criterion. This identifier would be equivalent to <Cdtr><Id><OrgId> selection in <pain.001.001.01> This field is used as a selection criterion.
<CustPayeeName>
C-40
Optional Repeating Echoed Optional Repeating Echoed XOR
Payee Name. This would be equivalent to <Cdtr><Nm> in <pain.001.001.01> This field is used as a selection criterion. Payment Batch Status Code. This identifies the payment batch processing status. This would be equivalent to <GrpSts> in <pain.002.001.01> Valid values: ACTC, ACCP, ACSP, ACSC, RCVD, PART, RJCT, PDNG This field is used as a selection criterion.
<PmtBatchStatusCode>
Closed Enum
<PmtTrnStatusCode>
Closed Enum
Optional Repeating Echoed XOR
Payment Status Code. This identifies the payment processing status. This would be equivalent to <TxSts> in <pain.002.001.01> Valid values: ACTC, ACCP, ACSP, ACSC, RJCT, PDNG This field is used as a selection criterion.
<SelRangeDueDt>
Optional Echoed
Selection Range Due Date Aggregate. This would be equivalent to <ReqdExctnDt> in <pain.001.001.01> This field is used as a selection criterion.
<PmtBatchStatusRec>
PmtBatch Status aggregate.
7.14.4
PmtBatch Status Advise
Provide description of the functionality of this message (request and response). The Payment Batch Status Advise message allows for the service provider to push status information to the originator of the Payment Batch Add Request without any action necessary by the originator. Only a server response is necessary to confirm receipt of the advice message.
Version 1.7
April 2005
141
7.14.4.1 Request <PmtBatchStatusAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtBatch Record Aggregate
<PmtBatchStatusRec>
Required
7.14.4.2 Response <PmtBatchStatusAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Status Aggregate
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Required Echoed
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. PmtBatch Record Aggregate.
<PmtBatchStatusRec>
Required Echoed Optional Optional
142
April 2005
Version 1.7
8 The Bill Presentment Service <PresSvc>

Bill Presentment is the electronic delivery of a bill from a biller to a customer. While this chapter focuses on the presentation of bills, this service may be used for the presentation of other documents such as notices, statements, and invoices. A company that distributes bills often has a variety of information that is to be presented to a customer, including payment information, announcements of new services, and changes in the terms and conditions of service. A biller also needs to know that they and their service providers have been able to get the bills to the customers. They often need to know that the customer has seen the bill, statement, or notice, and having information about the customers actions returned to the biller and their service provider should facilitate business. To support the widest intersection of customers who want bills, and billers that want bill delivery, the concept of the biller directory has been developed. Basically, the flow is that a customers agent (the CSP) locates billers through the Biller Directory, uses the customer, customer/service link, and service/account link messages to enable presentment and payment; obtains the current list of bills available for the consumer; and allows the consumer to initiate payment. This chapter covers the methods for finding billers, obtaining bills, and updating bill statuses. Although some billers may provide Bill Presentment service themselves, many may choose to work with a BSP that provides Bill Presentment service on behalf of many billers. For this reason, Bill Presentment focuses on connecting customers to BSPs.
8.1Description
This section summarizes the process of receiving bills electronically, starting with the steps required to find a BSP and set up Bill Presentment service. To receive bills electronically, a CSP determines which BSPs provide Bill Presentment service for the billers. Subsequently, the customer: Finds one or more billers by searching a biller directory server. The location and access to such servers is not currently defined within IFX. Determines which BSPs provide Bill Presentment service for the billers. Enables the bill presentment service with a CSP, who forwards the message on to the BSP or Biller. Enrolls with a CPP for a Payment service (if not already enrolled). Activates bill presentment with the BSP or Biller for one or more accounts with one or more billers. Requests electronic bills from the BSP via the CSP. Optionally pays the bills.
8.1.1Biller Inquiry
To find billers, the client sends a <BillerInqRq> request. A <BillerInqRs> response is returned. Contained within the response is the <BillerInfo> aggregate. This aggregate provides information about a biller, including preferences, such as Disclosures (see Section 5.4.1.2 for additional information). In some situations, the biller or BSP may prefer to never receive the account activation request without prior acceptance of the Billers Bill Presentment disclosure by the customer. The <DiscReqd> tag allows the Biller to specify whether or not the customer must have accepted the Billers disclosure prior to delivery of the account activation to the BSP. In the case where the value of this tag is True, the biller should specify the <DiscId> and <DiscDt> information. In the event a Customer Service Provider (CSP) stores Biller Disclosures locally, the <DiscDt> will allow the CSP to determine if an update to a disclosure has occurred, when processing a <BillerInqRs>. If
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification the CSP found that an update to the disclosure had occurred, the new disclosure information can be obtained by sending a <DiscInqRq> to the BSP, using the <DiscId> found within the <BillerInfo>. If the CSP does not store Biller disclosures locally, the <DiscInqRq> could be done at the time the CSP receives a request from their customer to activate a particular Biller. If the value of the <DiscReqd> tag is False or the tag is not present, the Biller/BSP either does not require acceptance of a disclsoure or will specify the disclosure in response to an account activation <SvcAcctAddRq>. Note: Customer acceptance of a disclosure is associated with the Disclosure Identifier <DiscId> for that disclosure. If it is necessary to track the version of a disclosure that a customer has accepted, it is recommended that a Biller or BSP use a new <DiscId> any time that they modify their Bill Presentment disclosure. The <DiscId> itself is the versioning mechanism for disclosures within IFX.
8.1.1.1 Search Arguments

If the client omits all elements in the <BillerInqRq>, the client is requesting a complete directory of billers. Otherwise, the client wants to filter results based on the included elements.
8.1.2Activate Bill Delivery

Once the customer has located a biller, the customer enables the bill presentment service using the <CustSvcAddRq>. After enabling the service, the customer may activate presentment accounts for one or more billers at that BSP using the <SvcAcctAddRq> in order to receive bills. Account Activation may be an off-line process for many billers, and in such situations the <SvcAcctStatusCode> must return xxxPend with an optional estimated decision date in the message. <SvcAcctInqRq> is used to request the current account status.
8.1.3Account Inquiry
The <SvcAcctInqRs> response must return a <PresAcctId> aggregate and <SvcAcctStatus> <StatusDesc> for each of the customers accounts with the billers at that BSP. The response may list only those accounts that have been activated for Bill Presentment service; it is not required to list all available accounts. Unlike a financial institution, BSPs generally will not have information about all the accounts of its supported billers. Billers that also serve as their own BSPs may be able return available accounts as well as activated accounts.
8.1.4Bill Presentment
The customer obtains bills that are ready for presentment using the <BillInqRq>. The responding <BillInqRs> includes bill summaries. Bill Summary is information from a biller that is essential for a customer to understand what is owed, which may include, but is not limited to, Amount Owed, Date Due, Biller, and Customers Account Number with the Biller. A customer may also elect to view an electronic version of the detail of the bill. Bill Detail is information from a biller that provides invoice line level information to a customer, such as credit card charges, telephone calls, or kilowatts used. IFX provides an <ImageURL>, included in <StmtImage>, to indicate the location where bill detail information may be found and retrieved. The definition of structured data for communicating Bill Detail in email or other message formats is planned for future releases of the specification. The bill record aggregate <BillRec> provides the ability to deliver bill-related information, including bill summary information about a single bill, a billing statement, a notification (textual information sent from the biller to communicate information about the bill presentment service), or an invoice, depending on the value in the <BillType> element. The Bill Summary may include such information as amount due, date due, and pointers to more information; e.g., a set of URLs that may be used to access bill detail and other information. The actual elements used are likely to vary depending on the Bill Type. For example, with <BillType> Notice, the biller may send <Memo> data but none of the other optional elements.
April 2005
Version 1.7
Interactive Financial Exchange Business Message Specification A Biller may use the <Memo> element within the Bill Summary to send human-readable text to the customer, regardless of bill type. This may include, for example, special instructions for accessing information within the bill detail when sent with a bill, or regulatory or other announcements when sent as part of a bill or statement or alone as part of a notice. The bill date, <BillDt>, is the bills as of date. It is sometimes referred to as invoice date or statement date on a paper bill. It is often the date that the biller generated the bill. It is not the date on which the BSP received the bill for publication or the date that the payment is due. <DueDt> is the date used by the biller to indicate when payment is to be received according to the terms and conditions of the account.
8.1.4.1 Bill Summary Amount and Sub-Amount

8.1.4.1.1 Bill Summary Amount
The Bill Summary Amount <BillSummAmt> aggregate is used to specify any currency values for the bill, including amount due when applicable. If <BillType> = Bill, at least one occurrence of this aggregate must be present where the amount is a payable amount (i.e., <BillAmtType> is <Payable>).
8.1.4.1.1.1 Amount Type

The <BillSummAmt> aggregate is designed to allow maximum flexibility in specifying amounts on a bill summary. The requirements vary greatly by industry, to the extent that a single amount due is not sufficient. Some currency values on a bill represent options on an amount to pay (specified by the <BillSummAmtType> = Payable). Some values on the bill summary may be for information only and are not an amount to be paid (specified by the <BillSummAmtType> = InfoOnly). Other values may be presented to denote a category for a supplemental or overpayment by the consumer (specified by the <BillSummAmtType> = Supplemental). Examples for each type are: Payable Amount Due and Minimum Amount Due on a credit card One-month, Three-month, and Six-month premium on an insurance policy Amount Due and Late Amount Due on a utility bill. InfoOnly Discount amount for an early payment of a utility bill Current Charges, Current Credits, Statement Balance, and Finance Charges on a credit card. Supplemental Extra Principal and Extra Escrow on a mortgage Tip and Charitable Contribution on a newspaper bill. Note: When multiple Payable amounts are specified within a bill summary, they must be treated as mutually exclusive; i.e., only one Payable amount may be selected for payment. Supplemental amounts are not mutually exclusive; i.e., the consumer may select more than one Supplemental amount for allocating an overpayment.
8.1.4.1.2 Bill Summary Sub-Amount

Another type of amount that may be presented is a breakdown of a total amount, typically a payable amount. The <BillSummSubAmt> aggregate allows for this breakdown, and associates the breakdown with a specific amount within a <BillSummAmt> aggregate. The amounts within the sub-amount aggregate may be designated as a category that may be selected by the consumer for allocation of their total payment (<AllocateAllowed> = True), or the amounts within this breakdown may be information only (<AllocateAllowed> = False). Sub-Amount Example: A consolidated insurance bill may include Payable amounts of 3-month premium and 6-month premium, at the <BillSummAmt> level. Within the <BillSummAmt> aggregate for the 3-month premium, the biller may include two sub-amount aggregates, one for the life insurance 3-month premium and one for the health insurance 3-month premium. A similar breakdown may be included for the 6-month
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification premium. If the biller wants the consumer to be able to specify what portion of their total payment (perhaps if they were paying something other than the amount billed, for example) was for life and what portion was for health, he would designate these sub-amounts as <AllocateAllowed> = True. If the sub-amounts were included for information only, the biller would designate these amounts as <AllocateAllowed> = False. The table below demonstrates some possible industry examples for using the amount types and sub-amount aggregate.
8.1.4.1.3 Amount ID
The <BillSummAmt> aggregate also allows for the BSP or biller to specify an identifier, or tag, for each amount specified. This identifier may be included in a payment message to return not only the amount paid, but also the specific amount category being paid. Using this identifier allows the consumer to specify the total amount paid, as well as how the allocation of the payment is intended.
8.1.4.1.4 Description Data

Each amount within the <BillSummAmt> aggregate must carry with it a short description <ShortDesc>. This is the description that may be displayed to the consumer to correspond with the currency amount specified, where a shortened description is needed, such as in a grid box. A more detailed description <Desc> may be specified for clarity, when the <ShortDesc> is insufficient to properly define the amount. The <Memo> tag may be used to provide Help text or terms that pertain to an amount. In addition, the aggregate allows the Biller to categorize the amount into a type, specified by an open Enum list, when possible. This would allow the CSP to have a machine-readable understanding of the amount being specified.
8.1.4.1.5 Important Notes about Bill Summary Amounts

All values for <CurAmt> are valid, including 0 and negative amounts. A CSP is not obligated to display all amounts specified within the bill summary. The CSP should display the bill summary amounts, beginning with the first occurrence in the message, proceeding in order and giving priority to Payable amounts, versus InfoOnly or Supplemental amounts or amounts specified within the <BillSummSubAmt> aggregate. Therefore, each occurrence of the <BillSummAmt> aggregate should be included in the message in priority order, with the first being the most important amount to display to the consumer, the second being the next highest amount in importance, and so forth, with the last occurrence being the least important. Although it may vary by client, billers should consider that amounts specified as <BillSummAmtType> = Supplemental or specified within <BillSummSubAmt> might only be displayed when the bill is selected for payment. The CSP or CPP may choose not to perform any edit checks on the amount actually paid by the consumer.
8.1.4.1.6 Bill Summary Amount Examples

Industry Example
Utilities
Short Desc
Amount Due Gas Electric Charity Donation Late Charge Late Amount Due Early Discount Discount Amt Due Early Gas
Payable
InfoOnly
Supplemental
SubAmt
AllocateAllowed
False False
False
April 2005
Version 1.7
Early Electric Newspaper Monthly Amount 3 Month Saver 6 Month SuperSaver Tip Charity Donation Mortgage Principal Interest RE Taxes Insurance Escrow Total PMI Total Amnt Due Extra Principal Extra Escrow Credit Card Current Balance Minimum Amt Due Revolving Minimum Long Term Minimum New Charges New Credits Finance Charges Late Charges Insurance 3-month Premium 3-month Life 3-month Health 6-month Premium 6-month Life 6-month Health Non-Smoker Disc %
False
True True
True True
True True
8.1.5Bill Payment
The customer may pay the bill using the payment messages specified in Chapter 7. Note that the <BillerId> used to identify a biller may be different for presentment and payment, even if the CPP and BSP are the same organization. Note also that the <BillRec> aggregate contains both the biller presentment account number and a
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification <BillRefInfo> data element, which are returned with the payment to facilitate correct posting of the payment by the billers accounts receivable.
8.2Bill Presentment Service Message Summary

Req.
Yes
Comments
Allows the client to retrieve a current view of the services supported by the SP, the Authentication Realms that must be used for authentication, and basic information about the SP. Allows client to view a summary of current Biller records maintained by the Pay or Presentment service provider. Payment billers may or may not have been previously added to the customers Payee List. Allows a client to reverse an action of a Biller record.
Biller Inquiry
<BillerInqRq> <BillerInqRs>
Biller Reversal
<BillerRevRq> <BillerRevRs>
Bill Inquiry
<BillInqRq> <BillInqRs>
Allows client to retrieve bills from the biller.
Bill Reversal
<BillRevRq> <BillRevRs>
Allows a client to reverse an action to bills from the biller.
Bill Status Modification

<BillStatusModRq> <BillStatusModRs>
Allows a client (Customer/CSP/CPP) to notify the BSP/Biller that the status of a bill or payment for the bill has changed.
8.3Presentment Service Common Aggregates

8.3.1Biller Record Aggregate <BillerRec>
The <BillerRec> aggregate is widely used to provide summary-level information about a Biller. The elements, <BillerStatus>, <EffDt>, <BSPReferTo>, <SPName>, and <OrgContact> support the case where a Biller discontinues usage of a BSP and includes forwarding information if available.
Tag
<BillerId>
Type
Usage
Required Repeating Required
Description
Biller Identification Aggregate.
<BillerInfo>
Biller Information Aggregate
<BillerStatus>
Optional
Biller Status Aggregate. If absent, the meaning of <BillerStatus> <BillerStatusCode> is Active. BSP Refer to Aggregate. The new BSP for this Biller, if known.
<BSPReferTo>
Optional
April 2005
Version 1.7
8.3.1.1 BSP Refer-to Aggregate <BSPReferTo>

Tag
<SPName> <OrgContact>
Type
Usage
Optional Optional
Description
Service Provider Name. Name of replacement BSP. Contact information for replacement BSP.
8.3.1.2 Biller Identification <BillerId>

The <BillerId> aggregate is widely used to uniquely identify a Biller within a BSP (i.e., the <SPName> would be the BSP). The <StdPayeeId> is the Billers ID as known to the CPP; i.e., the <SPName> would be the CPP. Billers may be known differently by different organizations, so when both <BillerId> and <StdPayeeId> are used in a message (such as in those messages that use the <PresAcctId> aggregate) the <BillerId> is the Billers ID as known by the BSP and the <StdPayeeId> is the Billers ID as known by the CPP. The presence of these two IDs may help in resolving the identification of Billers known differently by other organizations.
Tag
<SPName> <BillerNum>
Type
Usage
Required Required
Description
Service Provider Name. Used to qualify <BillerNum>. This is the name of the BSP that assigned <BillerNum>. Biller Number. Assigned by the Pay/Presentment provider. Cannot be changed by the client.
8.3.1.3 Biller Information Aggregate <BillerInfo>

Tag
<Name> <BillerContact>
Type
C-40 Aggregate see section 3.2.6.1 Aggregate see section 3.2.13 Aggregate see section 3.2.14.1 Open Enum
Usage
Required Optional
Description
Biller Name. Assigned by the service provider. Cannot be changed by the client. Biller Contact Information.
<IndustId>
Optional
Industry Identifier.
<SecretPrompt>
Optional Repeating AND Optional Repeating AND
Secret Prompt Aggregate. If omitted, the biller does not require the customer to enter any secrets for client enrollment. Encryption type to indicate encryption used for transmitting authentication information. The Biller may specify one or more encryption types that it accepts. Defined values: None, PKCS#1, PKCS#7, PKCS#10, ECB, CBC, CFB, OFB, TECB, TCBC, TCBC-I, TCFB, TCFB-P, TOFB, TOFB-I, AECB, ACBC, ACFB, AOFB, ACM
<CryptType>
<HistRetentionDays>
Long
Optional
Number of days that Bill Summary and Bill Detail information is available for inquiries. The Bill Detail information may be available for a longer period of time.
Version 1.7
April 2005
Tag
<CSPCustInfoReq>
Type
Boolean
Usage
Optional
Description
CSP Customer name and address information Required. If True, the Biller requires that the Customer name and address be sent with an account activation. IF False or omitted, the customer name and address are not required in the account activation. Biller Pay Information Aggregate.
<BillerPayInfo>
Aggregate see section 3.2.6.2 URL
Optional
<LogoURL>
Optional
Logo URL. URL of the billers logo.
<Logo> <BillerEnrollURL>
Binary URL
Optional Optional
Biller Logo. If the client requested images, the logo should be included here in this response. Biller Information URL. URL of human-readable description of additional information the biller would like the customer to have with regard to signing up. The resource may also include an interactive session to verify a customers identity and eligiblity to receive bills for an account. If successful, the session results in a security token or password that the customer may use in response to a <SecretPrompt> when activating the account for bill presentment.
<BillerAcctIdInfo>
Aggregate see section 8.3.2 Boolean
Optional
Biller Account Information Aggregate. Provides additional information to the customer to assist in entry of the customers account numbers with the biller. Disclosure Required. If True, the biller requires that their disclosure be presented to the customer prior to account activation. If False, the presentment of the disclosure is not required prior to the account activation request. This may be False if no disclosure is required or when the biller wishes to return the disclosure in the account activation response. Disclosure Identifier. The identifier of the disclosure associated with this biller. The <DiscInfo> associated with this identifier can be obtained by performing a Disclosure Inquiry. Date Last Disclosure Change.
<DiscReqd>
Optional
<DiscId>
UUID
Optional
<DiscDt>
Date
Optional
8.3.1.4 Biller Status Aggregate <BillerStatus>

Tag
<BillerStatusCode>
Type
Closed Enum
Usage
Required
Description
Biller Status Code. Valid Values: Available, AvailPend, Deleted, DelPend, Suspended.
<StatusDesc> <EffDt>
C-255 DateTime
Optional Optional but see Description
Status Description. Explanatory text associated with this status. Date Time Effective. The Date the <BillerStatus> was changed or, in the case of DeletePending, the date the delete should take effect. Required if <BillerStatusCode> = xxxPend.
April 2005
Version 1.7
Tag
<StatusModBy>
Type
Open Enum
Usage
Optional
Description
Status Modified By. If present, indicates who modified the Biller Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<Memo>
C-255
Optional
Memo Information. To provide additional information about the status.
8.3.2Biller Account Identification Information Aggregate <BillerAcctIdInfo>

The <BillerAcctIdInfo> aggregate specifies the format of valid account numbers acceptable to the biller.
Tag
<AcctFormat>
Type
NC-1024
Usage
Optional
Description
Account Format. Regular expression describing the account number format. The definition and behavior of Regular Expression is per IEEE Std 1003.2-1992 (POSIX.2). General definition may be found at http://www.ciser.cornell.edu/info/regex.html
<AcctMask>
NC-32
Optional Repeating
Account Mask. String describing the edit mask to identify a valid billing account number <BillingAcct> for that biller. The client uses the account edit mask to assist the user in entering the account number. Account Help Message. Human-readable message that the client may display to assist the customer in entering his or her account number.
<AcctHelpMsg>
C-
Optional
<AcctRestrictMsg>
C-1024
Optional
Account Restriction Message. Human-readable description of any restrictions on who may sign up with this biller. Enforcement of any restrictions is by the biller or the billers agent during the <SvcAcctAddRq>. Other service providers are only responsible for communicating this information.
<AcctValidateURL>
URL
Optional
URL for Account Validation. URL for validation. The client application may use this to validate the customers account number.
8.3.2.1 Account Number Validation

Servers may implement a lightweight CGI (or equivalent) to validate account numbers. The URL provided in the <AcctValidateURL> may be accessed with an HTTP GET with three arguments: <BillerId>, <AcctId> and <PostalCode>. The URL should respond with a text file that includes the following values: Status: (Required) Error: An error condition (wrong number of parameters, Database error, etc.). Clarifying text may accompany the error status. Pass: The account number is in an acceptable form for this biller (this does not guarantee that the account will be accepted for the service). Fail: The account number does not correspond to an acceptable account number for this biller. Clarifying text may accompany the failed status.
Version 1.7
April 2005
Interactive Financial Exchange Business Message Specification Account: (Optional) The preferred format or version of the account number presented in the request. Heading: (Optional) Additional text to help explain problems to end-users.
8.3.2.1.1 Example
<AcctValidateURL> = http://testit.com/validate.cgi Client application uses HTTP GET with http://testit.com/validate.cgi? billerid=5454&accountnumber=123-456-7890&customerpostalcode=12345
The server would respond with one of these: Error:

Content-type: text/plain <Status>Error</Status> <Heading>The server is unable to process your request at this time. Please resubmit.</Heading>
Failure:
Content-type: text/plain <Status>FAIL</Status> <Heading>123-456-7890 does not appear to be a valid account number</Heading>
Passed:
Content-type: text/plain <Status>passed</Status> <AcctId>1234567890</AcctId>
8.3.3Bill Record <BillRec>

The bill record aggregate <BillRec> provides the ability to deliver bill-related information, including bill summary information about a single bill, a billing statement, a notification (textual information sent from the biller to communicate information about the bill presentment service), or an invoice, depending on the value in the <BillType> element. The Bill Summary may include such information as amount due, date due, and pointers to more information; e.g., a set of URLs that may used to access bill detail and other information. The actual elements used are likely to vary depending on the Bill Type. For example, with <BillType> Notice, the biller may send <Memo> data but none of the other optional elements.
Tag
<BillId> <BillInfo>
Type
UUID Aggregate see section 8.3.3.1 Aggregate see section 8.3.3.2 Aggregate see section 8.3.3.3
Usage
Required Required
Description
Identifier for this bill within the BSP. Bill Information Aggregate.
<BillStatus>
Optional
Bill Status Aggregate.
<BillPmtStatus>
Optional
Bill Payment Status Aggregate.
8.3.3.1 Bill Information Aggregate <BillInfo>

Tag
<BillType>
Type
Open Enum
Usage
Required
Description
Bill Type. Defined values: Bill, Statement, Notice, Invoice.
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the customer to whom the bill is issued. If absent, the bill is issued to the customer specified in the message response.
10
April 2005
Version 1.7
Tag
<PresAcctId>
Type
Aggregate see section 3.2.7.3.1 C-255 Aggregate see section 8.3.3.1.1
Usage
Required
Description
Bill Presentment Account Identification Aggregate.
<Memo> <BillSummAmt>
Biller-information displayed to user by the biller. This may be used for notice information when <BillType> = Notice. Bill Summary Amount Aggregate. Used for any currency amounts that are being presented in the Bill Summary.
Note: If <BillType> = Bill, at least one occurrence of this aggregate must be present where the amount is a payable amount (<BillAmtType> = Payable).
Optional Required Optional Optional Optional Repeating Payment due date. If absent and <BillType> is Bill, the meaning is that the bill is due upon receipt. Bill date. Opening statement date. Closing statement date. Payment Instrument Aggregate. Types of payment that the biller accepts via the Pay provider. This aggregate may be used to override types of payments options indicated previously in the <BillerRec>. Note that a restriction here may result in no valid payment type being available to the customer, which may result in the CSP sending a <BillStatusModRq> to the BSP indicating that the bill is Unpayable. If True, the server requires that the client send a <BillStatusModRq> for each change of status of either the bill or its payment. The server may not send True if the client did not set <NotifyWilling> to True in <BillInqRq>. Indicates biller preference that customer view the detail of the bill. Defined values: None, Preferred Bill detail is available through the <URL> specified within the <StmtImage> aggregate.
<DueDt> <BillDt> <OpenDt> <CloseDt> <PmtInst>
Date Date Date Date Aggregate see section 3.2.15
<NotifyReqd>
Boolean
Optional
<ViewDtlPref>
Open Enum
Optional
<StmtImage>
Aggregate see section 8.3.3.1.2 NC-80
Optional
Statement image aggregate.
<BillRefInfo>
Optional
Biller-defined text to include with the payment, for the billers Accounts Receivable reconciliation. It is sent with electronic payment requests.
8.3.3.1.1 Bill Summary Amount Aggregate <BillSummAmt>

Tag
<BillSummAmtId>
Type
Identifier
Usage
Optional
Description
Bill Summary Amount Identifier. Billers identifier for this currency amount. This may be returned in the payment message to identify the type of amount being paid by the consumer. This value needs to be provided by the Biller if the intent is to allow the consumer to designate the particular amount being paid (using <PaySummAmt> in <PmtInfo> aggregate).
Version 1.7
April 2005
11
Tag
<BillSummAmtCode>
Type
Open Enum
Usage
Optional
Description
Bill Summary Amount Code. Indicates the type of amount being specified in <CurAmt>, using a standard list of billing amounts that are machine-readable by the client and may be used for internal processing. The short description <ShortDesc> should be used to describe the amount in a display to the consumer. Defined values: TotalAmtDue, MinAmtDue, MaxAmtDue, LateAmtDue, DiscAmtDue, MonthlyAmt, QuarterlyAmt, SemiAnnualAmt, AnnualAmt, ExtdAmt, PrevBal, Charges, Credits, StmtBal, LateChg, FinanceChg, Tip, Principal, Interest, Escrow, PMI, Donation
<ShortDesc>
C-15
Required
Short Description. A short description of the amount specified in <CurAmt> within this aggregate. To be used for display to the consumer. Description. A longer description of the amount specified in <CurAmt>. To be used when the short description <ShortDesc> may be insufficient to clearly describe the amount. Memo. Additional information about the amount specified in <CurAmt>. This may be used to further describe terms or instructions that may apply to the amount specified. Currency Amount. The amount being specified as described by the short description. This amount may be a zero or negative value. Bill Summary Amount Type. Indicates the type of amount specified in <CurAmt>. Note that the client must treat amounts that are Payable as mutually exclusive (i.e., the consumer may select only one). Amounts that are Supplemental are not mutually exclusive (i.e., the consumer may select more than one for indicating breakdown of an additional payment). Valid values: Payable, Supplemental, InfoOnly.
<Desc>
C-80
Optional
<Memo>
C-255
Optional
<CurAmt>
Currency Amount Closed Enum
Required
<BillSummAmtType>
Required
<BillSummSubAmt>
Optional Repeating
Bill Summary Sub-Amount. Allows for the specification of a breakdown of an amount specified in <CurAmt> within the higher level aggregate <BillSummAmt>.
8.3.3.1.1.1 Bill Summary Sub-Amount Aggregate <BillSummSubAmt>

Tag
<BillSummAmtId>
Type
Identifier
Usage
Required
Description
Bill Summary Amount Identifier. Billers identifier for this currency sub-amount. Used in a payment message to allocate a portion of a total payment amount to this subamount. Short Description. A short description of the amount specified in <CurAmt> within this aggregate. To be used for display to the consumer. Description. A longer description of the amount specified in <CurAmt>. To be used when the short description <ShortDesc> may be insufficient to clearly describe the amount. Memo. Additional information about the amount specified in <CurAmt>. This may be used to further describe terms or instructions that may apply to the amount specified.
<ShortDesc>
C-15
Required
<Desc>
C-80
Optional
<Memo>
C-255
Optional
12
April 2005
Version 1.7
Tag
<CurAmt>
Type
Currency Amount Boolean
Usage
Required
Description
Currency Amount. The amount being specified as described by the short description. This amount may be a zero or negative value. Allocation Allowed Indicator. If True, the <BillSummAmtId> for the amount specified may be used to indicate the allocation breakdown of the total payment amount within the <PayInfo> aggregate in a payment message. If False or omitted, the amount specified is for information only.
<AllocateAllowed>
Optional
8.3.3.1.2 Statement Image <StmtImage>

The <StmtImage> aggregate provides one or more URLs that point to a fully rendered image of the bill, in HTML. The <URL> should include enough information for the HTTP server to authenticate the client requesting the statement image. For security reasons, the authentication information embedded within the URLs should expire after a period of time deemed prudent by the service provider. Information about the authentication information expiration date and time is included in <ExpDt>. <ImageURL> accesses the complete bill image. This URL may contain navigation to other sites or to other pages of bill images at the same site. To support off-line viewing of the bill, the server may provide one or more additional URLs. Each <PrefetchURL> points to a local Web page.
Tag
<ImageURL>
Type
URL
Usage
Required
Description
URL address for retrieving an image of the complete bill encoded as HTML. This may be cached by the client for later display, or it may be viewed live directly from the Web. List of URLs required in order to display an HTML image of the complete bill, to support off-line viewing. Date/Time after which embedded authentication token expires. If absent, the embedded token never expires.
<PrefetchURL> <ExpDt>
URL DateTime
8.3.3.2 Bill Status Aggregate <BillStatus>

Tag
<BillStatusCode> <StatusDesc> <EffDt> <StatusModBy>
Type
Open Enum C-255 DateTime Open Enum
Usage
Description
Bill Status Code. Defined values are: New, Delivered, Viewed, Retired, Withdrawn, and Undeliverable. Status Description. Explanatory text associated with this status. Effective Date Time. The date and time the Bill Status became effective. Status Modified By. If present, indicates who modified the Bill Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, and BPPSR.
<Memo>
C-255
Optional
Memo Information. To provide additional information about the status.
Version 1.7
April 2005
13
8.3.3.3 Bill Payment Status Aggregate <BillPmtStatus>

Tag
<PmtId> <BillPmtStatusCode>
Type
Usage
Optional Required
Description
Payment Identifier. The ID of the payment associated with the bill. Bill Payment Status Code. Valid values are: None, AutoPay, Scheduled, Processed, PaidOutOfBand, Cancelled, Unpayable, and Posted. Effective Date Time. The date and time the Bill Payment Status became effective. Status Modified By. If present, indicates who modified the Bill Payment Status Code. Defined values: Customer, CSP, CSPSR, BSP, BSPSR, CPP, CPPSR, BPP, BPPSR.
DateTime Open Enum
Optional Optional
<Memo>
C-255
Optional
Memo Information. To provide additional information, for example, if the payment was rejected, it may contain the reason for the rejection.
8.4Presentment Service Message Detail

The Presentment Service contains messages to search for billers and to obtain bills. Typically, the client periodically requests a list of bills from the BSP. The BSP responds with a list of bills; each bill contains summary data such as the due date and amount due. For each bill, the BSP might also return a <URL> to a Web site that contains an HTML-rendered version of the bill. The server must include the BSPs <SPName> in the <BillerRec> aggregate for each biller sent in the <BillerInqRs>. The client may then use this <SPName> to activate accounts <SvcAcctAddRq>, request bills <BillInqRq>, and change status of bills <BillStatusModRq>. Since the bills for a specific customer may originate from multiple BSPs, it is the client softwares responsibility to ensure that the correct <SPName> is used in each message that it originates.
8.4.1Biller Inquiry
The Biller Inquiry message enables a client to retrieve a list of all Billers known to the BSP that meets certain selection criteria. Note that the Biller directory timestamp <UpDt> selection criterion allows the CSP to request all directory entries that have been added or changed since a point in time.
8.4.1.1 Request <BillerInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
14
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
<RecCtrlIn>
Optional
<BillerId>
Biller Identification. This field is used as a selection criterion. Biller Name. Assigned by the server at the time the Biller is first added. Cannot be changed by the client. This field is used as a selection criterion.
<Name>
<PostAddr>
Biller Postal Address Aggregate.
<Phone>
Customer Service Telephone Number. This field is used as a selection criterion against all customer service phone numbers associated with billers. Postal Code. This is the postal code of the billing account. This field is used as a selection criterion: (1) It may be used to limit the search to billers doing business within a limited geography, or (2) It may be used to identify the correct legal/entity or remittance address such as the cable company for a specific city, e.g. TCI- Sunnyvale CA. Biller Directory update timestamp. This is the time supplied by the server. If present, <BillerInqRs> must include at least those Billers whose information has changed or been added since <UpDt>. Industry Identifier This field is used as a selection criterion. Include Biller Contact Information. If True, the <BillerContact> aggregate is returned for each biller; otherwise, it is not returned. Include Images. If True, the client requests that images <Logo>s be returned. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<PostalCode>
C-11
Optional Repeating
<UpDt>
Timestamp
Optional
<IndustId>
Aggregate see section 3.2.13 Boolean
<IncBillerContact>
<IncImages> <DeliveryMethod>
Boolean Open Enum
Optional Optional Profiled values
8.4.1.2 Response <BillerInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
Version 1.7
April 2005
15
Tag
<MsgRqHdr>
Type
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Biller Identification Aggregate.
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Optional Repeating
<BillerId>
<Name>
C-40
Biller Name.
<PostAddr>
Aggregate see section 3.2.3.10.1 Phone Number C-11
Biller Postal Address Aggregate.
<Phone>
Customer Service Telephone Number.
<PostalCode>
Postal Code. This is the postal code of the billing account.
<UpDt> <IndustId>
Timestamp Aggregate see section 3.2.13 Boolean Boolean Open Enum Timestamp Aggregate see section 8.3.1
Biller Directory timestamp. Industry Identifier
<IncBillerContact> <IncImages> <DeliveryMethod> <NewUpDt> <BillerRec>
Include Biller Contact Information. Include Images. Delivery Method. New Biller Directory Timestamp. This is the response timestamp generated by the server. Biller Information Aggregate.
16
April 2005
Version 1.7
8.4.2Biller Inquiry Reversal

8.4.2.1 Request <BillerRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Biller Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <BillerMsgRqInfo>
8.4.2.1.1 Biller Message Request Information <BillerMsgRqInfo>

Tag
<BillerInqRq>
Type
Usage
Optional
Description
Biller Inquiry Request Message Aggregate.
8.4.2.2 Response <BillerRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<AsyncRqUID>
Optional Echoed
Version 1.7
April 2005
17
Tag
<CustId>
Type
Aggregate see section 3.2.3.1 Open Enum C-80 Aggregate see section 8.4.2.1.1 Identifier Identifier
Usage
Description
<RevReasonCode> <Desc> <BillerMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Biller Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
8.4.3Bill Inquiry
<BillInqRq> retrieves bills or counts of bills from the BSP. The BSP returns a <BillInqRs> that contains a list of zero or more bills, or counts of bills that match specific selection criteria. The client requests bills from a BSP by using one or more selection criteria, including bill creation date range. To specify the date range, clients use <StartDt> and <EndDt>, which the server compares to <BillDt> within the <BillRec> aggregate. The BSP returns information sufficient to identify the biller and provide the amount due, due date, and remittance information so that a payment may be made to the biller. The BSP does not provide a viewable form of the bill but may return a URL to an HTML rendering of the bill.
8.4.3.1 Request <BillInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Records Control Input Aggregate. It is used in inquiry request messages to allow the client to specify a maximum number of records that the server may return. Service Provider Name.
<RecCtrlIn>
Optional
<SPName>
Required
18
April 2005
Version 1.7
Tag
<SelRangeDt>
Type
Usage
Optional
Description
<BillId>
Bill Identifier. This field is used as a selection criterion. Biller Identifier Aggregate. This field is used as a selection criterion. Bill Type. Defined values: Bill, Statement, Notice, Invoice This field is used as a selection criterion.
<BillerId>
<BillType>
<BillStatusCode>
Open Enum
Optional Repeating
Bill Status Code. Defined values: New, Delivered, Viewed, Retired, Withdrawn, Undeliverable. This field is used as a selection criterion.
<BillPmtStatusCode>
Open Enum
Optional Repeating
Bill Payment Status Code. Defined values: None, Scheduled, Processed, Posted, PaidOutOfBand, AutoPay, Cancelled, Unpayable. This field is used as a selection criterion.
<NotifyWilling>
Boolean
Optional
Client Willing to Notify. If True, the client is prepared to send notifications of changes to bill status, if desired. If False or absent, the client cannot send notifications of bill status changes. Include Counts of Bills. If True, the client is requesting that the number of bills in each status included in the selection criteria <BillStatusCode>, <BillPmtStatusCode> is returned in the <BillCounts> aggregate in the response. Include Bill Summaries. If True, the client is requesting that the bill summaries for each bill as specified in the request be returned in the response, utilizing the <BillRec> aggregate. Delivery Method. Default is Channel. Value must be supported in Service Profile.
<IncCounts>
Boolean
Optional
<IncSummary>
Boolean
Optional
<DeliveryMethod>
Open Enum
8.4.3.2 Response <BillInqRs>

The <BillInqRs> may contain zero or more bill summaries <BillRec>. Each bill summary corresponds to a (usually monthly) bill. The response may contain either counts of bills or the collection of the bill summaries.
Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
Version 1.7
April 2005
19
Tag
<MsgRsHdr>
Type
Usage
Optional
Description
<RecCtrlOut>
Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 UUID
Optional but see Description Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating Optional Repeating
<SelRangeDt>
<BillId>
Bill Identifier.
<BillerId>
Biller Identifier Aggregate.
<BillStatusCode>
Bill Status Code. Defined values: New, Delivered, Viewed, Retired, Withdrawn, Undeliverable Bill Payment Status Code. Defined values: None, Scheduled, Processed, Posted, PaidOutOfBand, AutoPay, Cancelled, Unpayable Client Willing to Notify. Include Counts of Bills. Include Bill Summaries. Delivery Method. Bill Record Aggregate. This is a list of bills that match the selection criteria. Bill Counts Aggregate.
<BillPmtStatusCode>
Open Enum
<NotifyWilling> <IncCounts> <IncSummary> <DeliveryMethod> <BillRec>
Boolean Boolean Boolean Open Enum Aggregate see section 8.3.3 Aggregate see section 8.4.3.2.1
<BillCounts>
8.4.3.2.1 Bill Counts Aggregate <BillCounts>
20
April 2005
Version 1.7
Tag
<BillStatusCounts>
Type
Usage
Optional Repeating
Description
Bill Status Counts. The count(s) of all the bills for that customer, which may be provided by a given status(s). Note, if no selection criteria <BillStatusCode>, <BillPmtStatusCode> are specified when <IncCounts>=True, counts are returned for every status with a non-zero count. Bill Payment Status Counts. The count(s) of all the bill payment statuses for that customer, which may be provided by a given status(s). Note selection criteria is ignored when <IncCounts>=True.
<BillPmtStatusCounts>
Optional Repeating
8.4.3.2.1.1 Bill Status Counts Aggregate <BillStatusCounts>

Tag
<BillStatusCode>
Type
Open Enum
Usage
Required
Description
Bill Status Code. Defined values: New, Delivered, Viewed, Retired, Withdrawn, Undeliverable
<Count>
Long
Required
Count of Bills with the given Bill Status Code.
8.4.3.2.1.2 Bill Payment Status Counts Aggregate <BillPmtStatusCounts>

Tag
<BillPmtStatusCode>
Type
Open Enum
Usage
Required
Description
Bill Payment Status Code. Defined values None, Scheduled, Processed, Posted, PaidOutOfBand, AutoPay, Cancelled, Unpayable
<Count>
Long
Required
Count of Bills with the given Bill Payment Status Code.
8.4.4Bill Reversal
8.4.4.1 Request <BillRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Version 1.7
April 2005
21
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Bill Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <BillMsgRqInfo>
8.4.4.1.1 Bill Message Request Information Aggregate <BillMsgRqInfo>

Tag
<BillInqRq>
Type
Usage
Optional
Description
Bill Inquiry Request Message Aggregate.
8.4.4.2 Response <BillRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Required Echoed Optional Echoed Required
<RevReasonCode> <Desc> <BillMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Bill Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
22
April 2005
Version 1.7
8.4.5Bill Status Modify

The BSP may request the client to send notifications of various state changes for the bill of the associated payment by setting <NotifyReqd> = True in the <BillRec> aggregate (see Section Error: Reference source not found), if the client has indicated that it is capable of sending notifications; i.e., <NotifyWilling> = True within <BillInqRq>. The following table indicates which entity(s) sets each bill and bill payment status.
Status Code
<BillStatusCode> (Status of bill): New Delivered Viewed Retired Withdrawn Undeliverable <BillPmtStatusCode> (Status of a bill payment) None AutoPay Scheduled Processed Posted PaidOutOfBand Cancelled Unpayable BSP/Biller BSP/Biller CSP/CPP CSP/CPP BSP/Biller Customer or CSP/CPP Customer or CSP/CPP CSP/CPP BSP/Biller (initially) BSP/Biller Customer or CSP by inference Customer BSP/Biller CSP
Recognized/Set by
Setting <BillStatusCode>=Viewed tells the BSP that the CSP has presented the specified bills to the customer. This is a stronger statement than acknowledging that the client has received the bills <BillStatusCode>=Delivered, specifically when the client software implements the pre-fetching (i.e. pull) model. However, IFX does not define the meaning of presenting to the customer. In particular, receipt of a <BillStatusCode>=Viewed by the BSP is not intended to have any legal significance. The specification also does not define the maximum elapsed time between the presentation of the bill and sending a notification.
8.4.5.1 Request <BillStatusModRq>

Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Version 1.7
April 2005
23
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Bill Identifier. Identifies the bill from the given biller. Bill Status Aggregate.
<BillId> <BillStatus>
UUID Aggregate see section 8.3.3.2 Aggregate see section 8.3.3.3
Required Required OR
<BillPmtStatus>
Required OR
8.4.5.2 Response <BillStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Bill Identifier. Bill Status Aggregate.
<BillId> <BillStatus>
UUID Aggregate see section 8.3.3.2 Aggregate see section 8.3.3.3 Identifier Identifier
Required Echoed Required OR Echoed Required OR Echoed Optional Optional
<BillPmtStatus>
Financial Institute Reference Identifier. Service Provider Reference Identifier.
24
April 2005
Version 1.7
8.5Bill Presentment Service Profile <PresSvcProfInfo>

This section defines the profile aggregate for the Bill Presentment Service. This profile aggregate should be included in the <SvcProfInqRs> response for those servers that support the Bill Presentment Service.
Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service. Supported Messages. This is a list of messages that may be supported for Presentment. The convention is to use the name of the message without the Rq or Rs so that each message is only listed once. Defined values: BillerInq, BillerRev, BillInq, BillRev, BillStatusMod.
<MsgSupt>
Required Repeating
<OptSupt>
Open Enum
Optional Repeating
Options Supported. Defined values: AcctNickname, RecCtrl, SuppressEcho, AddReadOnlyAllowed Processing Schedule Aggregate. If omitted, the default processing schedule is assumed.
<PrcSched>
Optional
Version 1.7
April 2005
25
9 The Valuable Media Service <MediaSvc>

The IFX Specification provides support for the tracking of valuable media at IFX client devices (e.g. ATMs, teller cash drawers) through the Valuable Media Service. The Valuable Media Service includes functions such as Media Account Adjustments (i.e. by a withdrawal, deposit or replenishment activity) and Media Account Inventory Inquiries for retrieving the balance of inventory in Media Accounts. These can be used for tracking a wide variety of valuable media such as cash, coins, postage stamps, coupons, checks, and envelopes located at IFX client devices. The message set provided by the Valuable Media Service can be used in conjunction with the Debit and Credit messages from the Banking Service.
9.1Description
The Valuable Media Service message set is used to support the tracking of valuable media at IFX client devices. To achieve this, the notion of a Media Account is used. A Media Account is an entity that allows a financial institution to manage the value of the media stored within a single IFX client device. The Media Account may refer to a physical container, a logical grouping of containers, or the complete set of valuable media in the IFX client device. Whenever the valuable media in a Media Account is adjusted (i.e. by a withdrawal, deposit or replenishment activity), this adjustment should be reported to the server. Depending on the environment, the adjustments may be collected by the client and sent to the server in batches at certain times or when the batch has reached a certain size, or each adjustment may be sent as it occurs. The Valuable Media Service allows clients to perform the following functions: Debit and credit media accounts with the use of Add Media Account Adjust messages. Inquiry of media account results (i.e. balances) with the use of Media Account Inventory Inquiry messages. A Media Account may refer to a physical container, a logical grouping of containers, or the complete set of valuable media in the IFX client device. An example from the Self-Service (i.e. ATM) environment may be useful. Assume an ATM with identifier 123 has five cassettes and the Financial Institution has decided that $5 notes are always stored in cassettes one and two and $20 notes are always stored in cassettes three, four, and five. If the Financial Institution is not interested in keeping track of which cassette is used for dispensing a note, the <MediaAcctAdjInfo> aggregate may be used by setting the <MediaAcctId> to 123 (the ATM identifier), and using one <MediaItem> aggregate for all $5 notes dispensed and another <MediaItem> aggregate for all $20 notes dispensed. If, however, the Financial Institution is interested in keeping track of which cassette is used for dispensing a note, the <MediaAcctAdjInfo> aggregate may be used by setting the <MediaAcctId> to 123 (the ATM identifier), and using a separate <MediaItem> aggregate for each cassette. The Financial Institution establishes the values used for the identifiers. One <MediaItem> aggregate would be used for the $5 notes in cassette one (with <MediaContainerId> set to cassette1), a second <MediaItem> aggregate for the $5 notes in cassette two (with <MediaContainerId> set to cassette2), a third <MediaItem> aggregate for the $20 notes in cassette three (with <MediaContainerId> set to cassette3), a fourth <MediaItem> aggregate for the $20 notes in cassette four (with <MediaContainerId> set to cassette4), and the fifth <MediaItem> would be used for the $20 notes in cassette five (with <MediaContainerId> set to cassette5). These are just two examples how a Media Account and the <MediaAcctAdjInfo> aggregate can be used.
Version 1.7
April 2005
9.2Valuable Media Service Message Summary

Required
Yes
Comments
Allows the client to retrieve a current view of the services supported by the SP, the Authentication Realms that must be used for authentication, and basic information about the SP. Allows a client to request a debit or credit of valuable media from a specified media account.
Media Account Adjust Add

<MediaAcctAdjAddRq> <MediaAcctAdjAddRs>
Media Account Adjust Inquiry

<MediaAcctAdjInqRq> <MediaAcctAdjInqRs>
Allows a client to view media account adjust records.
Media Account Adjust Audit

<MediaAcctAdjAudRq> <MediaAcctAdjAudRs>
Allows a client to play back the media account adjust messages associated with the client device since some past point in time. Allows a client to synchronize the media account adjust messages associated with the client device since some past point in time.
Media Account Adjust Synchronization

<MediaAcctAdjSyncRq> <MediaAcctAdjSyncRs>
Media Account Adjust Reversal

<MediaAcctAdjRevRq> <MediaAcctAdjRevRs>
Allows a client to reverse a previous media account adjust request message.
Media Account Inventory Inquiry

<MediaAcctInventoryInqRq> <MediaAcctInventoryInqRs>
Allows a client to retrieve the inventory of valuable media in a media account at the time the message is executed.
Media Account InventoryReversal

<MediaAcctInventoryRevRq> <MediaAcctInventoryRevRs>
Allows a client to reverse a previous media account inventory request message.
9.3Valuable Media Service Common Aggregates

9.3.1Media Item <MediaItem>
The <MediaItem> aggregate is used to describe the media in a media account transaction. This aggregate is used with the Media Account Adjust Add and Media Account Inventory Inquiry messages.
Tag
<MediaContainerId>
Type
Identifier
Usage
Optional
Description
Media Container identifier. This identifier can be used to identify the container of the media item.
April 2005
Version 1.7
Tag
<MediaType>
Type
Open Enum
Usage
Required
Description
Media Type. Defines the type of media being described by the <MediaItem> aggregate. Defined values: Cash UnverifiedCashDeposit VerifiedCashDeposit Coin Stamp Coupon Check UnverifiedCheckDeposit VerifiedCheckDeposit EnvelopeDeposit MultiDeposit Card
<MediaSubType>
Open Enum
Optional
Media Subtype. Used to further clarify a media type. When media type is Check, defined values are: Travelers, Managers, Bank, Cashiers When media type is EnvelopeDeposit, defined values are: Consumer, Commercial, PmtEnclosed, FIMsg, All When media type is Card, defined values are: Retained
<MediaCashInfo>
Aggregate see section 9.3.2.2 Aggregate see section 6.3.6 Long
Contains details about a cash media item being deposited.
<CreditMediaChkInfo>
Contains details about a check media item.
<Count>
Required OR
A count of the number of media items in this aggregate.
This element will be deprecated in IFX 2.0, to be replaced by <MediaBal>.

The currency value of an individual media item.
<CurAmt>
Currency Amount
Required OR

The sum of the currency value of all media items of this type.
<TotalCurAmt>
Currency Amount
Required OR
Version 1.7
April 2005
Tag
<MediaBal>
Type
Usage
Optional
Description
Media Balances. Contains the denomination and different balances/totals for this media container (hopper/cassette).
This aggregate should be used in IFX 1.7 and beyond for all Media Totals. This will become a Required aggregate in IFX 2.0. To maintain backwards compatibility with client versions prior to 1.7, current counts should be reflected in the previous three fields marked for deprecation as well as in <MediaBal> as a current total.
9.3.1.1 Media Balance (<MediaBal>) Aggregate

The newly proposed Media Balance <MediaBal> sub-aggregate, of the <MediaItem> aggregate, contains media denomination (as Currency Amount <CurAmt>) and a repeating sub-aggregate that contains different types of media totals (<MediaTotal>).
Tag
<CurAmt>
Type
Currency Amount
Usage
Optional
Description
Currency denomination/value of the media container (hopper/cassette) whose totals are defined in the following <MediaTotal> sub-aggregate. If this element is not present, then a denomination/value of zero amount (nonvalue media) is assumed. Media Totals. Contains different balances/totals for this media container (hopper/cassette).
<MediaTotal>
Required Repeating
9.3.1.1.1 Media Total (<MediaTotal>) Aggregate

The newly proposed Required Repeating <MediaTotal> sub-aggregate, of the <MediaBal> aggregate, contains different types (Original/Begin, Increased, Decreased, Out, Current/End, etc.) of ATM hopper/cassette totals. Each entry/occurrence of the <MediaTotal> defines a separate total type, its count and/or monetary total.
Tag
<MediaTotalType>
Type
Open Enum
Usage
Required
Description
Hopper/Cassette Total Type. Defined Values: Original, ReplenisherIncrease, ReplenisherDecrease, Dispensed, Current.
<Count> <TotalCurAmt>
Long Currency Amount
A count of the number of items of this type in this aggregate. The sum of the currency value of all items of this type within this aggregate.
9.3.2Media Account Record Aggregate <MediaAcctAdjRec>

The <MediaAcctAdjRec> aggregate is used in responses to both the Media Account Adjust Add Response <MediaAcctAdjAddRs> and Media Account Adjust Inquiry Response <MediaAcctAdjInqRs> messages.
Tag
<MediaAcctAdjId>
Type
Identifier
Usage
Required
Description
Media Account Adjust Identifier. Assigned by the server at the time the Media Account Adjust transaction is first added. Cannot be changed by the client. Media Account Adjust Information Aggregate.
<MediaAcctAdjInfo>
Required
April 2005
Version 1.7
9.3.2.1 Media Account Adjust Information Aggregate <MediaAcctAdjInfo>

The <MediaAcctAdjInfo> aggregate is used in adjusting the value of a media account with the use of a Media Account Adjust Add message.
Tag
<MediaAcctId>
Type
Identifier
Usage
Required
Description
Media Account Identifier. This identifier can refer to a physical container, a logical grouping of containers, or the complete set of valuable media at a client device. Media Transaction Type. The type of media account transaction associated with this request. Defined values are: Dispense Valuable media was dispensed. Deposit Valuable media was deposited. ReplenishSet Replenishment, the amounts reported are set absolutely. ReplenishAdd Replenishment, the amounts reported are added. ReplenishRemove Replenishment, the amounts reported are subtracted. BalanceSet Balancing, the amounts reported are set absolutely.
<MediaTrnType>
Open Enum
Optional
<CurAmt> <TrnAuthId>
Currency Amount Identifier
Optional Optional
Currency Amount. The total value of the media in this media account transaction. Transaction Authorization Identifier. The client may use this identifier in a Banking Service Debit/Credit message to associate a Media Account Adjust message with the original authorization identifier generated. For a Media Account Adjust message to debit, the <TrnAuthId> would be set to the <DebitId> value that was returned from a Banking Service Debit Authorization message. For a Media Account Adjust message to credit, the <TrnAuthId> would be set to the <CreditId> value that was returned from a Banking Service Credit Authorization message. Note: May be renamed to <TrnId> in IFX 2.0
<TrnRqUID> <RelatedCreditId>
Optional Optional
RqUID of the financial transaction request associated with this media adjustment. Related Credit Identifier. The identifier of the financial transaction request that ties all the related transactions together in a multiple part transaction such as depositing multiple checks and getting cash back. A server may use this to identify all the checks deposited by a customer in a deposit. Media Item aggregate. This aggregate is used to describe the details of the media in a media account transaction. Base Environment aggregate
<MediaItem>
<BaseEnvr>
9.3.2.2 Media Cash Information Aggregate <MediaCashInfo>

The <MediaCashInfo> aggregate contains details about a cash media item being deposited.
Version 1.7
April 2005
Tag
<CashValidity>
Type
Open Enum
Usage
Optional
Description
Cash Validity. The validity of the cash being deposited. Defined Values: Genuine, Counterfeit, Suspect
<CashQuality>
Open Enum
Optional
Cash Quality. The quality of the cash being deposited. Defined Values: Fit, Unfit
<CashSignature> <CashSerialNum>
Binary C-30
Optional Optional
Cash Signature. The signature of the cash being deposited. Cash Serial Number. The serial number of the cash being deposited.
9.4Media Account Adjust

A client uses the Media Account Adjust messages when media has been dispensed from the client device during a customer withdrawal transaction or when media has been deposited to the client device during a customer deposit transaction. For a dispense action, the Media Account Adjust message can be associated with the Banking Service Debit Message by setting the TrnAuthId to the DebitAuthId value that was received in the withdrawal. For a deposit action, the Media Account Adjust message can be associated with the Banking Service Credit Message by setting the TrnAuthId to the CreditAuthId used for the deposit. A client also uses the Media Account Adjust messages when media is added or removed from the client device during a replenishment function.
9.4.1Media Account Adjust Add

A client uses the Media Account Adjust Add message to inform the server of a media account adjustment, due to either a dispense, deposit, or a replenishment action.
9.4.1.1 Request <MediaAcctAdjAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Customer Identification aggregate. This is the identification of the client device for which the request is being issued. This element is required if the owner of the object(s) specified in this request is not the user specified in <SignonRq>. Media Account Adjust Information Aggregate. This aggregate is used to uniquely identify the media account used in this media account transaction.
<MediaAcctAdjInfo>
Required
April 2005
Version 1.7
9.4.1.2 Response <MediaAcctAdjAddRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 9.3.2.1 Aggregate see section 9.3.2 Identifier Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identifier aggregate.
<MediaAcctAdjInfo>
Media Account Adjust Information Aggregate.
<MediaAcctAdjRec>
Media Account Adjust Record Aggregate.
Optional Optional
9.4.2Media Account Adjust Inquiry

A client can use the Media Account Adjust Inquiry message to get a list of transactions that have occurred on Media Accounts.
9.4.2.1 Request <MediaAcctAdjInqRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 UUID Aggregate see section 3.2.3.1
Usage
Required Optional
Description
Optional Optional
Asynchronous Request Identifier. Customer Identification aggregate. This is the identification of the client device for which the request is being issued. This element is required if the owner of the object(s) specified in this request is not the user specified in <SignonRq>. This field is used as a selection criterion.
<RecCtrlIn>
Optional
Version 1.7
April 2005
Tag
<MediaAcctAdjId>
Type
Identifier
Usage
Optional Repeating
Description
Media Account Adjust Identifier. Assigned by the server at the time the Media Account Adjust transaction is first added. Cannot be changed by the client. This field is used as a selection criterion.
<CSPRefId>
Identifier
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion. Media Account Identifier. This is used to uniquely identify the media account used in a media account transaction. This field is used as a selection criterion.
<SPRefId>
Identifier
<MediaAcctId>
Identifier
<SelRangeDt>
Optional
Selection Range Date Aggregate. This field is used as a selection criterion.
<SelRangeCurAmt>
Optional
Selection Range Currency Amount Aggregate. The currency amount used in this selection criterion is the total value of the media in a media account transaction (the MediaTrnAmt). This field is used as a selection criterion.
<IncToken>
Boolean
Optional
9.4.2.2 Response <MediaAcctAdjInqRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description Optional Echoed
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Media Account Adjust Identifier.
<MediaAcctAdjId>
April 2005
Version 1.7
Tag
<CSPRefId>
Type
Identifier
Usage
Optional Repeating Echoed Optional Repeating Echoed Optional Echoed Optional Echoed Optional Echoed Optional Repeating
Description
<SPRefId>
Identifier
<MediaAcctId> <SelRangeDt>
Aggregate Aggregate see section 3.2.10.1 Aggregate see section 3.2.10.2 Aggregate see section 9.3.2
Media Account Identifier. Selection Range Date Aggregate.
<SelRangeCurAmt>
Selection Range Currency Amount Aggregate.
<MediaAcctAdjRec>
Media Account Adjust Record Aggregate. These records are generated by the server and reflect the current state of the Media Account Ids Media Account Adjust transactions. The records are filtered by the selection criteria specified in the request message. Token. Server Assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. The token is only included if <IncToken> = True in the request. <Token> = 0 is returned if no records are returned within the response.
<Token>
Identifier
9.4.3Media Account Adjust Audit

A client can use the Media Account Adjust Audit message to audit Media Account Adjust Add messages. When the Media Account object changes, the server must generate an Rs message corresponding to the Rq that created the pending state.
9.4.3.1 Request <MediaAcctAdjAudRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 UUID Aggregate see section 3.2.3.1
Usage
Required Optional
Description
Optional Optional
Asynchronous Request Identifier. Customer Identification aggregate. This is the identification of the client device for which the request is being issued. This element is required if the owner of the object(s) specified in this request is not the user specified in <SignonRq>. This field is used as a selection criterion.
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
Selection Range Date Aggregate. This field is used as a selection criterion.
Version 1.7
April 2005
Tag
<Method>
Type
Closed Enum
Usage
Optional Repeating
Description
Audit Selection Action. Used to identify actions associated with the object that is being audited. Valid values: Add. This field is used as a selection criterion.
<MediaAcctAdjId>
Identifier
Optional Repeating
Media Account Adjust Identifier. Assigned by the server at the time the Media Account Adjust transaction is first added. Cannot be changed by the client. This field is used as a selection criterion.
9.4.3.2 Response <MediaAcctAdjAudRs>

Tag
<Status>
Type
Aggregate see section 3.2.12.1 UUID Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum Identifier Aggregate see section 9.4.3.3.1
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
Optional Echoed Optional Echoed Optional but see Description Optional Echoed Optional Repeating Echoed Optional Echoed Optional Repeating
<RecCtrlOut>
<SelRangeDt>
<Method>
Audit Selection Criterion.
<MediaAcctAdjId> <MediaAcctAdjMsgRec>
Media Account Adjust Identifier. Media Account Adjust Message Record Aggregate.
9.4.3.3
9.4.3.3.1 Media Account Adjust Message Record Aggregate <MediaAcctAdjMsgRec>
10
April 2005
Version 1.7
Tag
<CustId>
Type
Usage
Optional
Description
Customer Identification Aggregate. This is the identifier of the entity who initiated the request (e.g., the one whose identifier appears in the <SignonRq> of the original issued request). For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the CSR or SP. Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Media Account Adjust Add Response Message Aggregate.
<MsgRecDt>
Timestamp
Optional
<MediaAcctAdjAddRs>
Required
<MediaAcctAdjRevRs>
Required
Media Account Adjust Reversal Response Message Aggregate.
9.4.4Media Account Adjust Synchronization

A client can use the Media Account Adjust Synchronization message to synchronize on Media Account Adjust Add messages. When the Media Account object changes, the server must generate a response message to the request that created the pending state.
9.4.4.1 Request <MediaAcctAdjSyncRq>

Tag
<RqUID> <MsgRqHdr>
Type
UUID Aggregate see section 3.2.1.1 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.1 Identifier
Usage
Required Optional
Description
Optional Required
Asynchronous Request Identifier. Customer Identifier aggregate. This is the identification of the client device for which the request is being issued. Records Control Input Aggregate.
<RecCtrlIn>
Optional
<Token>
Required
<MediaAcctId>
Identifier
Required
Media Account Identifier.
9.4.4.2 Response <MediaAcctAdjSyncRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
Required Echoed
Version 1.7
April 2005
11
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 UUID Aggregate see section 3.2.3.1 Aggregate see section 3.2.12.4.2 Identifier
Usage
Description
<MsgRsHdr>
Asynchronous Request Identifier. Customer Identification aggregate. This is the identification of the client device for which the request is being issued. Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. This is a token that has been previously sent by the server, or zero for first time requests.
<RecCtrlOut>
<Token>
<MediaAcctId> <NewToken>
Required Required
Media Account Information Aggregate. New Token. Server assigned. Client should make no assumptions about the value of this token relative to others that it may have received. The token is significant only to the server that originally assigned it. Media Account Adjust Message Record Aggregate.
<MediaAcctAdjMsgRec>
Optional Repeating
9.4.5Media Account Adjust Reversal

9.4.5.1 Request <MediaAcctAdjRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
Asynchronous Request Identifier. Sent by a client to retrieve a response that was asynchronously generated by a server, generally in the case where the response would have taken too long to build and be able to be sent synchronously. Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is
<CustId>
Optional
<RevReasonCode>
Open Enum
Required
12
April 2005
Version 1.7
Tag
Type
Usage
Description
requesting a reversal.
<Desc> <MediaAcctAdjMsgRqInfo>
C-80 Aggregate
Optional Required
Description, text describing the reason for the reversal. Media Account Adjustment Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
9.4.5.2 Media Account Adjustment Message Request Information Aggregate <MediaAcctAdjMsgRqInfo>

Tag
<MediaAcctAdjAddRq>
Type
Usage
Description
Media Account Adjustment Add Request Message Aggregate. Media Account Adjustment Inquiry Request Message Aggregate. Media Account Adjustment Audit Request Message Aggregate. Media Account Adjustment Synchronization Request Message Aggregate.
<MediaAcctAdjInqRq>
<MediaAcctAdjAudRq>
<MediaAcctAdjSyncRq>
9.4.5.3 Response <MediaAcctAdjRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <MediaAcctAdjMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Media Account Adjustment Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service
Version 1.7
April 2005
13
Tag
Type
Usage
Description
profile for specific reversal messages supported.
Optional Optional
9.5Media Account Inventory

A client may use the following messages to retrieve the inventory balance of media accounts. These may be used for consolidation and replenishment purposes.
9.5.1Media Account Inventory Inquiry

A client may use the Media Account Inventory Inquiry message to retrieve the inventory balance of a media account.
9.5.1.1 Request <MediaAcctInventoryInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<AsyncRqUID>
Optional
<CustId>
Customer Identification aggregate. This is the identification of the client device for which the request is being issued. This element is required if the owner of the object(s) specified in this request is not the user specified in <SignonRq>. Media Account Identifier. This is used to uniquely identify the media account used in this media account transaction.
<MediaAcctId>
Identifier
Required
9.5.1.2 Response <MediaAcctInventoryInqRs>

Tag
<Status>
Type
Usage
Optional
Description
Response Status Aggregate. If this aggregate is absent, <StatusCode> defaults to 0 (zero). Request Identifier. Sent by the client as a universally unique identifier for the message. Used to correlate responses with requests. Message Request Header aggregate.
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
14
April 2005
Version 1.7
Tag
<AsyncRqUID>
Type
UUID
Usage
Optional Echoed
Description
<CustId>
Aggregate see section 3.2.3.1 Identifier Currency Amount Aggregate see section 9.3.1
Optional Echoed Required Echoed Optional Required Repeating
Customer Identification aggregate.
<MediaAcctId> <CurAmt> <MediaItem>
Media Account Identifier. Currency Amount. The total value of the media in this media account. Media Item aggregate. This aggregate is used to describe the details of the media in inventory.
9.5.2Media Account Inventory Reversal

9.5.2.1 Request <MediaAcctInventoryRevRq>
Tag
<RqUID> <MsgRqHdr>
Type
Usage
Required Optional
Description
<AsyncRqUID>
Optional
<CustId>
Optional
Customer Identification Aggregate. This is the identifier of the user for whom the request is being issued. This element is required if the owner of the object(s) specified in the request is not the user specified in <SignonRq>. For example, if a CSR or SP issues the request on behalf of the user, then <CustId> is required, and must contain the value of the user whose request is being issued. Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Media Account Inventory Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported.
<RevReasonCode> <Desc> <MediaAcctInventoryMsgRqInfo>
Version 1.7
April 2005
15
9.5.2.1.1 Media Account Inventory Message Request Information Aggregate <MediaAcctInventoryMsgRqInfo>

Tag
<MediaAcctInventoryInqRq>
Type
Usage
Optional
Description
Media Account Inventory Inquiry Request Message Aggregate.
9.5.2.2 Response <MediaAcctInventoryRevRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID> <MsgRqHdr>
<MsgRsHdr>
<RevReasonCode> <Desc> <MediaAcctInventoryMsgRqInfo>
Reversal reason code. The reason why the client is requesting a reversal. Description, text describing the reason for the reversal. Media Account Inventory Message Request Information Aggregate. This aggregate contains the message to reverse. See RevOptSupt in the service profile for specific reversal messages supported. Customer Service Provider Reference Identifier. Service Provider Reference Identifier.
Optional Optional
9.6Valuable Media Service Profile <MediaSvcProfInfo>

The Profile for the Valuable Media Service <MediaSvcProfInfo> is defined below. This profile may be returned to the client in <SvcProfInqRq>, providing information on how the client should use the Valuable Media Service.
Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service.
16
April 2005
Version 1.7
Tag
<MsgSupt>
Type
Open Enum
Usage
Required Repeating
Description
Messages Supported. Defined values: MediaAcctInventoryInq, MediaAcctAdjAdd, MediaAcctAdjInq, MediaAcctAdjAud, MediaAcctAdjSync, MediaAcctInventoryRev, MediaAcctAdjRev
<OptSupt>
Open Enum
Optional Repeating
Version 1.7
April 2005
17
10
Root Service <RootSvc>
The IFX Specification provides device management and terminal management capabilities through the Root Service. The Root Service includes device management functions to allow an IFX client (e.g. ATM) to provide information about its devices and the status of those devices. The terminal management functions within the Root Service allows information (e.g. Reg E information, terminal identifier) pertaining to an IFX client (e.g. ATM) to be managed.
10.1
Description
The Device object and associated messages provide the following functionality: Allow an IFX client terminal (e.g. ATM or POS) to send device information and device status information to another IFX entity (e.g. Host, SP, CSP). The <DevAdvise> message provides this functionality. Allow an IFX client (e.g. Host, SP, CSP) to retrieve device information and device status information from an IFX terminal (e.g. ATM or POS). The <DevInq> message provides this functionality. The Terminal Object is used to logically represent an IFX client terminal (e.g. ATM or POS). The Terminal Object messages provide for the following functionality: Allow the postal address (e.g. street address) of the terminal to be set. Allow the postal address (e.g. street address) of the terminal to be retrieved. Allow the common location name of the terminal to be set. Allow the common location name of the terminal to be retrieved. Allow the owner name of the terminal to be set. Allow the owner name of the terminal to be retrieved. Allow the time zone (and implicitly the time) of the terminal to be set. Allow the time zone information of the terminal to be retrieved. To request the state/status of the terminal to be set to "Open" or "Closed" The Terminal Service Provider Object is used to logically represent the relationship an IFX client (e.g. ATM or POS terminal) has with a Service Provider. The Terminal Service Provider Object messages provide for the following functionality: Allow for one IFX client Terminal to be known as more than one TerminalId. This requirement is needed in some multiple Service Provider environments. The TerminalId used in this object is an identifier that uniquely identifies the Terminal within the context of the acquiring service provider. Allow a Service Provider to inform an IFX client Terminal that services are available/unavailable.
Version 1.7
April 2005
10.2
Root Service Message Summary

Required
Yes

Comments
Allows the client to retrieve a current view of the services supported by the SP, the Authentication Realms that must be used for authentication, and basic information about the SP. Allows a client to add a Terminal object. The client that uses this message is a host (e.g. CSP, SP).
Terminal Object Add

<TerminalObjAddRq> <TerminalObjAddRs>
Terminal Object Modify

<TerminalObjModRq> <TerminalObjModRs>
Allows a client to modify the information in a Terminal object record. The client that uses this message is a host (e.g. CSP, SP). Allows a client to retrieve Terminal object records. The client that uses this message is a host (e.g. CSP, SP).
Terminal Object Inquiry

<TerminalObjInqRq> <TerminalObjInqRs>
Terminal Object Status Modify

<TerminalObjStatusModRq> <TerminalObjStatusModRs>
Allows a client to request a change in the status of a Terminal object. The client that uses this message is a host (e.g. CSP, SP). Allows a client to play back Terminal object messages associated with a specific Terminal object. The client that uses this message is a host (e.g. CSP, SP). Allows a client to inform others of a change in a Terminal object record. The client that uses this message is a Terminal (e.g. ATM, POS). Allows a client to delete a Terminal object. The client that uses this message is a host (e.g. CSP, SP).
Terminal Object Audit

<TerminalObjAudRq> <TerminalObjAudRs>
Terminal Object Advise

<TerminalObjAdviseRq> <TerminalObjAdviseRs>
Terminal Object Delete

<TerminalObjDelRq> <TerminalObjDelRs>
Terminal Service Provider Object Add

<TerminalSPObjAddRq> <TerminalSPObjAddRs>
Allows a client to add a Terminal Service Provider object. The client that uses this message is a Terminal (e.g. ATM, POS). Allows a client to modify the information in a Terminal Service Provider object record. The client that uses this message is a Terminal (e.g. ATM, POS).
Terminal Service Provider Object Modify

<TerminalSPObjModRq> <TerminalSPObjModRs>
Terminal Service Provider Object Inquiry

<TerminalSPObjInqRq> <TerminalSPObjInqRs>
Allows a client to retrieve Terminal Service Provider object records. The client that uses this message is a Terminal (e.g. ATM, POS).
Terminal Service Provider Object Audit

<TerminalSPObjAudRq> <TerminalSPObjAudRs>
Allows a client to play back Terminal Service Provider object messages associated with a specific Terminal Service Provider object. The client that uses this message is a Terminal (e.g. ATM, POS).
April 2005
Version 1.7
Function / Message Name Terminal Service Provider Object Advise

<TerminalSPObjAdviseRq> <TerminalSPObjAdviseRs>
Required
Comments
Allows a client to inform others of a change in a Terminal Service Provider object record. The client that uses this message is a host (e.g. CSP, SP).
Terminal Service Provider Object Delete

<TerminalSPObjDelRq> <TerminalSPObjDelRs>
Allows a client to delete a Terminal Service Provider object. The client that uses this message is a Terminal (e.g. ATM, POS).
Device Inquiry
<DevInqRq> <DevInqRs>
Allows a client to retrieve device information and device status information for devices located at a Terminal. The client that uses this message is a host (e.g. CSP, SP). Allows a client to inform others that a change in a device status has occurred. The client that uses this message is a Terminal (e.g. ATM, POS).
Device Advise
<DevAdviseRq> <DevAdviseRs>
10.3
10.3.1
Tag
Root Service Common Aggregates

Terminal Object Record Aggregate <TerminalObjRec>
Type
Usage
Required Required
Description
Terminal Object Identifier. The identifier of the terminal object. Terminal Object Information Aggregate.
<TerminalObjId> <TerminalObjInfo>
<TerminalObjStatus>
Required
Terminal Object Status Aggregate.
10.3.1.1 Terminal Object Information Aggregate <TerminalObjInfo>

Tag
<PostAddr>
Type
Aggregate see section 3.2.3.10.1 C-80 C-40 Long
Usage
Optional
Description
Postal Address Aggregate. The physical address of the ATM/POS terminal. Description. The generally accepted name for the location of the ATM/POS terminal. Name. Name of the owner or operator of the ATM/POS terminal. Offset from UTC in minutes for the ATM/POS terminal.
<Desc> <Name> <UTCOffset>
Version 1.7
April 2005
10.3.1.2 Terminal Object Status Aggregate <TerminalObjStatus>

Tag
<TerminalObjStatusCode>
Type
Closed Enum
Usage
Required
Description
Terminal Object Status Code. Current operation mode of the terminal. Valid Values: Open The terminal accepts business transactions and administrative maintenance. Closed The terminal does not accept business transactions, but does accept administrative maintenance.
<RequestedOperationMode>
Closed Enum
Optional
Requested Operation Mode. The requested operation mode of the terminal. Valid Values: Open The terminal has been requested to accept business transactions and administrative maintenance. Closed The terminal has been requested to not accept business transactions, but will continue to accept administrative maintenance.
<ExpectedOpenDt>
DateTime
Optional
Expected Open DateTime. The terminal date/time that the terminal operation mode is expected to return to "Open" if the operation mode is being changed to something other than Open. There is no obligation inferred. A Terminal application could use this information to inform customers when the Terminal may again be available. Status Description. Explanatory text associated with this terminal object status. Effective Date. The date/time the <TerminalObjStatusCode> took effect. Status Modified By. If present, indicates who modified the <TerminalObjStatusCode>. Valid Values: FI, CSP, CSPSR, Terminal.
10.3.2
Tag
Terminal Service Provider Object Record Aggregate <TerminalSPObjRec>

Type
Usage
Required Required
Description
Terminal Service Provider Object Identifier. The identifier of the terminal service provider object. Terminal Service Provider Object Information Aggregate.
<TerminalSPObjId> <TerminalSPObjInfo>
<TerminalSPObjStatus>
Required
Terminal Service Provider Object Status Aggregate.
April 2005
Version 1.7
10.3.2.1 Terminal Service Provider Object Information Aggregate <TerminalSPObjInfo>

Tag
<SPName> <TerminalId>
Type
Usage
Required Required
Description
Service Provider Name. The name of the Service Provider associated with this Terminal Information aggregate. Terminal Identifier. Identification of terminal, such as ATM/POS terminal code or terminal number. This terminal identifier is used to uniquely identify the terminal within the context of the acquiring service provider.
10.3.2.2 Terminal Service Provider Object Status Aggregate <TerminalSPObjStatus>

Tag
<TerminalSPObjStatusCode>
Type
Closed Enum
Usage
Required
Description
Terminal Service Provider Object Status Code. Current state of the availability of services from this Service Provider to this terminal. Valid Values: ServiceAvailable One or more services are available from the Service Provider. A service is a collection of one or more messages. ServiceUnavailable No services are available from the Service Provider. A service is a collection of one or more messages.
<ExpectedAvailDt>
DateTime
Optional
Expected Availability DateTime. The date/time that service is expected to be available from this Service Provider. A service is a collection of one or more messages. There is no obligation inferred. Status Description. Explanatory text associated with this terminal service provider object status. Effective Date. The date/time the <TerminalSPObjStatusCode> took effect. Status Modified By. If present, indicates who modified the <TerminalSPObjStatusCode>. Valid Values: FI, CSP, CSPSR, Terminal.
10.3.3
Tag
<DevId> <DevInfo>
Device Record Aggregate <DevRec>

Type
The <DevRec> aggregate is used to provide information about a device and the status of device.
Usage
Required Required
Description
Device Identifier. Device Information Aggregate.
<DevStatus>
Required
Device Status Aggregate.
Version 1.7
April 2005
10.3.3.1 Device Information Aggregate <DevInfo>

Tag
<DevName>
Type
C-255
Usage
Optional
Description
Device Name. Human readable name of the device.
10.3.3.2 Device Status Aggregate <DevStatus>

Tag
<DevStatusCode>
Type
Closed Enum
Usage
Required
Description
Device Status Code. This is the State-of-Health (SOH) of the device. Valid Values: Healthy, Warning, Fatal, Suspend.
<DevDetail>
Aggregate see section 10.3.3.3 Aggregate see section 10.3.3.4 C-255 DateTime Open Enum
Required
Device Detail Aggregate.
<DevPlatformData>
Optional Repeating Optional Optional Optional
Device Platform Data Aggregate. Native platform specific information pertaining to the device. Status Description. Explanatory text associated with this device status. Effective Date. The date/time the <DevStatusCode> took effect. Status Modified By. If present, indicates who modified the <DevStatusCode>. Valid Values: Terminal, Maintenance
10.3.3.3 Device Detail Aggregate <DevDetail>

Note that the categorization of the following Device objects have been modeled after the XFS service class definitions. Although this will use the same classification as the XFS standard, this in no way ties an IFX client to use the XFS standard when using devices.
Tag
<DevDetailIdc> Type Aggregate see section 10.3.3.6 Aggregate see section 10.3.3.15 Aggregate see section 10.3.3.29 Aggregate see section 10.3.3.9 Aggregate see section 10.3.3.10 Aggregate see section 10.3.3.11 Usage Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR Description Device details specific to identification card devices (covered by the XFS IDC service class). Device details specific to printer devices (covered in the XFS PTR service class). Device details specific to cash dispenser modules (covered in the XFS IDC service class). Device details specific to the Personal Identification Number Keypads and other keyboard entry devices (covered in the XFS PIN service class). Device details specific to Check Readers and Scanners (covered in the XFS CHK service class). Device details specific to Depositories (covered in the XFS DEP service class).
<DevDetailPtr>
<DevDetailCdm>
<DevDetailPIN>
<DevDetailChk>
<DevDetailDep>
April 2005
Version 1.7
Tag
<DevDetailTtu>
Type Aggregate see section 10.3.3.8 Aggregate see section 10.3.3.18 Aggregate see section 10.3.3.17 Aggregate see section 10.3.3.32 Aggregate see section 10.3.3.7 Aggregate see section 10.3.3.26 Aggregate see section 10.3.3.13
Usage Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR Required XOR
Description Device details specific to Text Terminal Units (covered in the XFS TTU service class). Device details specific to Sensors and Indicators Units (covered in the XFS SIU service class). Device details specific to Vendor Dependent Mode (covered in the XFS VDM service class). Device details specific to cameras (covered in the XFS CAM service class). Device details specific to alarms (covered in the XFS ALM service class). Device details specific to Cash In Modules (covered in the XFS CIM service class). Device details specific to the Application.
<DevDetailSiu>
<DevDetailVdm>
<DevDetailCam>
<DevDetailAlm>
<DevDetailCim>
<DevDetailApp>
10.3.3.4 Device Platform Data Aggregate <DevPlatformData>

The Device Platform Data Aggregate returns information specific to certain device platforms. This is necessary for logging and troubleshooting purposes. The DevPlatformXfs Sub-Aggregates may be returned even if the client is not on that platform. For instance, a non-XFS client may return the DevPlatformXfs Aggregate.
Tag
<DevPlatformSource>
Type
Closed Enum
Usage
Optional
Description
Device Platform Source. Indicates whether the Device message is coming directly from the device platform layer, or the client has interpreted this data from another format. Valid Values: Native, Interpreted
<DevPlatformXfs>
Optional
Device Platform XFS Aggregate. Device details specific to the XFS Device message standards.
10.3.3.5 Device Platform XFS Aggregate <DevPlatformXfs>

This aggregate is used to return Platform Specific information, as defined by the XFS Device Platform standard. Note that non-XFS platforms may return this information as well.
Tag
<PlatformXfsRequestId>
Type
Decimal
Usage
Optional
Description
Platform XFS Request Id. The sequence number (in decimal form) assigned by the XFS Manager for the request that raised the alert. This value is expected as an integer value in the range 0- 4294967295.
Version 1.7
April 2005
Tag
<PlatformXfsTimestamp>
Type
DateTime
Usage
Optional
Description
Platform XFS Timestamp. The time that the alert was raised, based on the XFS Platform date/time. The client should include as much detail as is available (down to the fraction of a second). Platform XFS Event Id. The Id of the event that raised the alert (for unsolicited events). This value is expected as an integer value in the range 0- 4294967295. Platform XFS Logical Name. The high-level, pre-defined logical name of a service used by the XFS Manager as a key to obtain the specific configuration information needed. (e.g. SYSJOURNAL1, PASSBOOKPTR3, CASHDISP02) Here, it is used to identify the service that raised the alert. Platform XFS Physical Name. The physical service name of the service that raised the alert. Platform XFS Workstation Name. The name of the workstation in which the logical service name is defined (if any) Platform XFS State. The new state of the physical device managed by the service. Example states from the XFS Specifications include: WFS_STAT_DEVONLINE = 0, WFS_STAT_DEVFFLINE = 1, WFS_STAT_POWEROFF = 2, WFS_STAT_DEVNODEVICE = 3, WFS_STAT_DEVHWERROR = 4, WFS_STAT_DEVUSERERROR = 5, WFS_STAT_DEVBUSY = 6 This value is expected as an integer value, not outside the range 0- 4294967295, that is defined as a state by the XFS standard.
<PlatformXfsEventId>
Decimal
Optional
<PlatformXfsLogicalName>
C-255
Optional
<PlatformXfsPhysicalName> <PlatformXfsWkstName>
C-255 C-255
Optional Optional
<PlatformXfsState>
Decimal
Optional
<PlatformXfsAppId> <PlatformXfsAction>
C-255 Decimal
Optional Optional
Platform XFS Application Id. The application ID associated with the session that raised the alert (if any) Platform XFS Action. The actions required to manage the error as defined by the XFS specification. Example actions from the XFS specifications include: WFS_ERR_ACT_NOACTION = 0, WFS_ERR_ACT_RESET = 1, WFS_ERR_ACT_SWERROR = 2, WFS_ERR_ACT_CONFIG = 4, WFS_ERR_ACT_HWCLEAR = 8, WFS_ERR_ACT_HWMAINT = 16, WFS_ERR_ACT_SUSPEND = 32 This value is expected as an integer value, not outside the range 0- 4294967295, that is defined as an action by the XFS standard.
<PlatformXfsDesc> <PlatformXfsCmdCode>
C- Decimal
Optional Optional
Platform XFS Description. A vendor-specific description of the error. Platform XFS Command Code. The WFSExecute command code or the WFSGetInfo category code; not used for other command completions. This value is expected as an integer value in the range 04294967295. Platform XFS Command HResult. The Device Command Result code as specified by the XFS device standards.
<PlatformXfsCmdHResult>
Long
Optional
April 2005
Version 1.7
10.3.3.6 Device Detail Identification Card Aggregate <DevDetailIdc>

Device details specific to identification card devices (devices covered by the XFS IDC service class).
Tag
<DevIdcType>
Type
Open Enum
Usage
Required
Description
Type of Card Reader/IDC. Valid Values: Motor, Swipe, Contactless, Dip
<DevIdcOperation>
Open Enum
Optional
The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values are used rather than custom values in order to ensure maximum portability. Valid Values: Read, Write, EjectCard, RetainCard, ChipIo, Reset, ChipPower
<DevIdcMedia>
Closed Enum
Required
The state of the media in the IDC device. Valid Values: Present, NotPresent, Jammed, NotSupported, Unknown, Entering
<DevIdcRetainBin>
Closed Enum
Required
The state of the retain bin. Valid Values: OK, High, Full, NotSupported
<DevIdcCards> <DevIdcRetainedCard>
Long Aggregate see section 10.3.3.12 Closed Enum
Optional Optional
The number of cards retained since the count was last reset on the client. Details of the cards that have been retained as a part of this alert. The state of the security unit for this device. Valid Values: NotSupported, NotReady, Open
<DevIdcSecurity>
Optional
<DevIdcChipPower>
Closed Enum
Optional
The state of the chip on the currently inserted card in the device: Valid Values: Online, PoweredOff, Busy, NoDevice, HwError, NoCard, NotSupported, Unknown
10.3.3.7 Device Detail Alarm Aggregate <DevDetailAlm>

Device details specific to Alarm devices (devices covered by the XFS ALM service class).
Tag
<DevAlmType>
Type
Open Enum
Usage
Required
Description
Type of Alarm/Alm. Valid Values: Alarm
<DevAlmOperation>
Open Enum
Optional
The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values are used rather than custom values in order to ensure maximum portability. Valid Values: SetAlarm, Reset, NotSupported
<DevAlmAlarm>
Closed Enum
Required
The state of the Alarm at time of alert. Valid Values: Reset, Set, NotSupported
10.3.3.8 Device Detail Text Terminal Unit Aggregate <DevDetailTtu>

Device details specific to Text Terminal Unit devices (devices covered by the XFS TTU service class).
Version 1.7
April 2005
Tag
<DevTtuType>
Type
Open Enum
Usage
Required
Description
Type of Text Terminal Unit/Ttu. Valid Values: Fixed, Removable
<DevTtuOperation>
Open Enum
Optional
The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values are used rather than custom values in order to ensure maximum portability. Valid Values: Write, Read, Reset, NotSupported
<DevTtuKbd>
Closed Enum Closed Enum Closed Enum
Required
The state of the keyboard at time of alert. Valid Values: On, Off, NotAvailable
<DevTtuKbdLock>
Required
The state of the keyboard lock at time of alert. Valid Values: On, Off, NotAvailable
<DevTtuLed>
The state of the leds at time of alert. If an LED is present this element should be returned. The order of the LEDs listed is significant. Valid Values: Off, BlinkingSlowly, MediumFlash, QuickFlash, Continuous, NotAvailable
10.3.3.9 Device Detail PIN Keypad Aggregate <DevDetailPIN>

Device details specific to PIN Keypad and other encryption/decryption devices (devices covered by the XFS PIN service class).
Tag
<DevPINType>
Type
Open Enum
Usage
Required
Description
Type of PIN Keypad device. Valid Values: Keyboard, EncryptDecrypt, HwSecurityModule
<DevPINOperation>
Open Enum
Optional
The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: Encrypt, Decrypt, RandomNum, GetData, GetPIN, ImportKey, DeriveKey, PresentIdc, GetPINBlock, PINInitialization, Reset
<DevPINEncStat>
Closed Enum
Optional
The state of the Encryption Module. Valid Values: Ready, NotReady, NotInitialized, Busy, Undefined, Initialized
10.3.3.10 Device Detail Check Reader/Scanner Aggregate <DevDetailChk>

Device details specific to check reader and scanner devices (devices covered by the XFS CHK service class).
Tag
<DevChkType>
Type
Open Enum
Usage
Required
Description
Type of check reader/scanner device. Valid Values: Check
10
April 2005
Version 1.7
Tag
<DevChkOperation>
Type
Open Enum
Usage
Optional
Description
The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: Eject, Retain, Reset, Write, Read
<DevChkImageEnabled>
Boolean
Optional
Indicates a special case of check reader, i.e., imageenabled (or check scanner). If present, and the value is True, then the device is a check scanner. If omitted, or the value is False, then the device is a check reader. The state of the media in the check reader/scanner device. Valid Values: NotSupported, NotPresent, Required, Present, Jammed
<DevChkMedia>
Closed Enum
Required
<DevChkInk>
Closed Enum
Optional
The state of the ink in the check reader/scanner device. Valid Values: NotSupported, Full, Low, Out
10.3.3.11 Device Detail Depositories Aggregate <DevDetailDep>

Device details specific to Depositories (devices covered by the XFS DEP service class).
Tag
<DevDepType>
Type
Open Enum
Usage
Required
Description
Device Depository Type. Type of Depository. Valid Values: EnvelopeMotorized, EnvelopeManual, EnvelopeNone, BagDrop
<DevDepOperation>
Open Enum
Optional
Device Depository Operation. The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values are used rather than custom values in order to ensure maximum portability. Valid Values: Entry, Dispense, Retract, Reset, ResetCount
<DevDepTransport>
Closed Enum
Required
Device Depository Transport. The state of the deposit transport at time of alert. Valid Values: OK, Inoperable, Unknown, NotSupported
<DevDepContainer>
Closed Enum
Required
Device Depository Container. The state of the deposit container at time of the alert. Valid Values: OK, High, Full, Inoperable, Missing, Unknown, NotSupported
<DevDepEnvelopeSupply>
Closed Enum
Required
Device Depository Envelope Supply. The state of the deposit envelope supply at time of the alert. Valid Values: OK, Low, Empty, Inoperable, Unlocked, Missing, Unknown, NotSupported
Version 1.7
April 2005
11
Tag
<DevDepEnvelopeDispenser>
Type
Closed Enum
Usage
Required
Description
Device Depository Envelope Dispenser. The state of the deposit envelope dispenser at time of the alert. Valid Values: OK, Inoperable, Unknown, NotSupported
<DevDepPrinter>
Closed Enum
Required
Device Depository Printer. The state of the deposit printer at time of the alert. Valid Values: OK, Inoperable, Unknown, NotSupported
<DevDepToner>
Closed Enum
Required
Device Depository Toner. The state of the deposit printers toner at time of the alert. Valid Values: Full, Low, Out, Unknown, NotSupported
<DevDepShutter>
Closed Enum
Required
Device Depository Shutter. The state of the shutter at time of alert. Valid Values: Jam, Unknown, NotSupported, Open, Close
<DevDepNumOfDeposits>
Long
Optional
Total number of bags or envelopes in the deposit container
10.3.3.12 Device Identification Card Retained Card Aggregate <DevIdcRetainedCard>

Tag
<CardMagData>
Type
Usage
Required
Description
Card Magnetic Stripe Data. The data from the card that was retained.
10.3.3.13 Device Detail Application Aggregate <DevDetailApp>

Device details specific to the Application.
Tag
<DevAppOperation>
Type
Open Enum
Usage
Optional Repeating
Description
Device Application Operation. The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: BusinessTransaction, AdminMaintenance, AppMaintenance, SoftwareInstallation.
NOTE: If the application is idle then no <DevAppOperation> element would be included.

<DevAppNormalOperation> Boolean Required Device Application Normal Operation. An indication that the application is available for consumer transactions. Valid Values: True, False.
12
April 2005
Version 1.7
Tag
<DevAppComponent>
Type
Usage
Optional Repeating
Description
Device Application Component Aggregate. The state of individual components in the application.
10.3.3.14 Device Detail Application Component Aggregate <DevAppComponent>

Device details specific an Application component.
Tag
<Name> <Version> <DevHealthLevel>
Type
C-40 NC-12 Open Enum
Usage
Description
Name. Application/Component Name Version. Application/Component Version Device Health Level. The state of the application/component at time of alert. Valid Values: Healthy, Warning, Fatal, Suspend
10.3.3.15 Device Detail Printer Aggregate <DevDetailPtr>

Device details specific to printer devices (devices covered by the XFS PTR service class).
Tag
<DevPtrType>
Type
Open Enum
Usage
Required
Description
Device Printer Type. Type of the printer device. Valid Values: Receipt, Journal, Document, Passbook, Scanner
<DevPtrOperation>
Open Enum
Optional
Device Printer Operation. The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: ControlMedia, Print, Reset, RetractMedia, DispensePaper, Read
<DevPtrMedia>
Closed Enum
Required
Device Printer Media. The state of the print media at the time of the alert. Valid Values: Present, NotPresent, Jammed, NotSupported, Unknown, Entering, Retracted
<DevPtrRetractBin>
Closed Enum
Optional
Device Printer Retract Bin. The state of the printer retract bin. Valid Values: OK, High, Full, Unknown
<DevPtrSupply>
Optional Repeating
Device Printer Supply Aggregate. The state of the print supply at time of alert. The <DevPtrSupply> aggregate repeats for different possible locations of the supply. Device Printer Ink. The state of the ink at the time of the alert. Valid Values: Full, Low, Out, NotSupported, Unknown
<DevPtrInk>
Optional
<DevPtrToner>
Closed Enum
Optional
Device Printer Toner. The state of the printer toner or ink supply. Valid Values: Full, Low, Out, Unknown, NotSupported
Version 1.7
April 2005
13
Tag
<DevPtrLamp>
Type
Closed Enum
Usage
Optional
Description
Device Printer Lamp. The state of the lamp at time of alert. Valid Values: OK, Fading, Inoperative, NotSupported, Unknown
10.3.3.16 Device Printer Supply Aggregate <DevPtrSupply>

Printer supply details specific to printer devices.
Tag
<DevPtrSupplyLocation>
Type
Open Enum
Usage
Optional
Description
Device Printer Supply Location. The location of the printer supply. Valid Values: Upper, Lower, External, Auxiliary, Auxiliary2, Park
<DevPtrSupplyLevel>
Closed Enum
Required
Device Printer Supply Level. The actual supply level for the printer. Valid Values: Full, Low, Out, NotSupported, Unknown, Jammed
10.3.3.17 Device Detail Vendor Dependent Mode Aggregate <DevDetailVdm>

Device details specific to Vendor Dependent Mode (covered by the XFS VDM service class).
Tag
<DevVdmOperation>
Type
Open Enum
Usage
Optional
Description
Device VDM Operation. The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: Enter, Exit
<DevVdmServiceState>
Closed Enum
Optional
Device VDM Service State. The state of the VDM Service at time of alert. Valid Values: EnterPending, ExitPending, Active, Inactive
10.3.3.18 Device Detail Sensors and Indicators Aggregate <DevDetailSiu>

Device details specific to sensors and indicator devices (devices covered by the XFS and J/XFS SIU service class).
Tag
<DevSiuType>
Type
Usage
Required
Description
Device SIU Type Aggregate. Types of sensors and indictors available.
14
April 2005
Version 1.7
Tag
<DevSiuOperation>
Type
Open Enum
Usage
Optional
Description
Device SIU Operation. The operation being performed at the time the alert is raised. . It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: SetPorts, SetDoor, SetIndicator, SetGuidelight, SetAuxiliary, Reset, NotSupported
<DevSiuSensorStatus>
<DevSiuDoorStatus>
Optional
Device SIU Sensor Status Aggregate. The current state of any general sensors that are available.
Optional
Device SIU Door Status Aggregate. The current state of any door sensors that are available.
<DevSiuIndicatorStatus>
Optional
Device SIU Indicator Status Aggregate. The current state of any indicators that are available.
<DevSiuAuxiliaryStatus>
Optional
Device SIU Auxiliary Status Aggregate. The current state of any auxiliary sensors that are available.
<DevSiuGuidelightStatus>
Optional
Device SIU Guidelight Status Aggregate. The current state of any guidelights that are available.
10.3.3.19 Device Sensors and Indicators Type Aggregate <DevSiuType>

Tag
<DevSiuSensors>
Type
Closed Enum
Usage
Required
Description
Device SIU Sensors. Specifies whether general sensors are available. Valid Values: Yes, No, NotSupported
<DevSiuDoors>
Closed Enum
Required
Device SIU Doors. Specifies whether door sensors are available. Valid Values: Yes, No, NotSupported
<DevSiuIndicators>
Closed Enum
Required
Device SIU Indicators. Specifies whether indicators are available. Valid Values: Yes, No, NotSupported
<DevSiuGuidelights>
Closed Enum
Required
Device SIU Guidelights. Specifies whether guidelights are available. Valid Values: Yes, No, NotSupported
<DevSiuAuxiliary>
Closed Enum
Required
Device SIU Auxiliary. Specifies whether auxiliary sensors are available. Valid Values: Yes, No, NotSupported
Version 1.7
April 2005
15
10.3.3.20 Device Sensors and Indicators Sensor Status Aggregate <DevSiuSensorStatus>

Tag
<DevSiuOperatorSwitch>
Type
Open Enum
Usage
Optional
Description
Device SIU Operator Switch. The state of the operator switch sensor Valid Values: Run, Maintenance, Supervisor, NotAvailable
<DevSiuTamper>
Open Enum Open Enum Open Enum
Required
Device SIU Tamper. The state of the tamper sensor Valid Values: Off, On, NotAvailable
<DevSiuSeismic>
Required
Device SIU Seismic. The state of the seismic sensor Valid Values: Off, On, NotAvailable
<DevSiuHeat>
Required
Device SIU Heat. The state of the external heat (fire) sensor Valid Values: Off, On, NotAvailable
<DevSiuProximity>
Open Enum
Required
Device SIU Proximity. The state of the proximity detector Valid Values: NotPresent, Present, NotAvailable
<DevSiuAmbientLight>
Open Enum
Required
Device SIU Ambient Light. The state of the ambient light sensor Valid Values: VeryDark, Dark, MediumLight, Light, VeryLight, NotAvailable
<DevSiuEnhancedAudio>
Open Enum
Optional
Device SIU Enhanced Audio. The state of the enhanced (digital) audio headset sensor component. Valid Values: HeadsetPresent, HeadsetNotPresent, NotAvailable,
10.3.3.21 Device Sensors and Indicators Door Status Aggregate <DevSiuDoorStatus>

Tag
<DevSiuCabinet>
Type
Open Enum Open Enum Open Enum
Usage
Required
Description
Device SIU Cabinet. The state of the cabinet door(s). Valid Values: Closed, Open, Locked, Bolted, NotAvailable
<DevSiuSafe>
Required
Device SIU Safe. The state of the safe door(s). Valid Values: Closed, Open, Locked, Bolted, NotAvailable
<DevSiuVandalShield>
Required
Device SIU Vandal Shield. The state of the vandal shield. Valid Values: Closed, Open, Locked, Service, Keyboard, Ajar, Jammed, NotAvailable
10.3.3.22 Device Sensors and Indicators Status <DevSiuIndicatorStatus>

Tag
<DevSiuOpenClose>
Type
Open Enum
Usage
Required
Description
Device SIU Open Close. The state of the open / close indicator. Valid Values: Closed, Open, NotAvailable
16
April 2005
Version 1.7
Tag
<DevSiuFasciaLight>
Type
Open Enum Open Enum
Usage
Required
Description
Device SIU Fascia Light. The state of the fascia light. Valid Values: On, Off, NotAvailable
<DevSiuAudio>
Required
Device SIU Audio. The state of the audio indicator. Valid Values: Off, KeyClick, Exclamation, Warning, Error, Critical, Continuous, NotAvailable
<DevSiuHeating>
Open Enum
Required
Device SIU Heating. The state of the internal heating. Valid Values: Off, On, NotAvailable
10.3.3.23 Device Sensors and Indicators Auxiliary Status <DevSiuAuxiliaryStatus>

Tag
<DevSiuVolume>
Type
Long
Usage
Required
Description
Device SIU Volume. An integer (0-1000) indicating the audio volume level. 0 = Off, 1=Minimum volume, 1000=Maximum volume.
<DevSiuUps>
Open Enum
Required
Device SIU Uninterruptable Power Supply. The state of the uninterruptable power supply. Valid Values: Available, Low, Engaged, Powering, Recovered, NotAvailable
<DevSiuRemoteStatus>
Required
Device SIU Remote Status. The state of the remote status monitor indicators.
<DevSiuAudibleAlarm>
Required
Device SIU Audible Alarm. The state of the audible alarm. Valid Values: Off, On, NotAvailable
10.3.3.24 Device Sensors and Indicators Remote Status <DevSiuRemoteStatus>

Tag
<DevSiuGreenLed>
Type
Closed Enum Closed Enum Closed Enum
Usage
Required
Description
Device SIU Green LED. The state of the green LED. Valid Values: Off, On, NotAvailable
<DevSiuRedLed>
Required
Device SIU Red LED. The state of the red LED. Valid Values: Off, On, NotAvailable
<DevSiuAmberLed>
Required
Device SIU Amber LED. The state of the amber LED. Valid Values: Off, On, NotAvailable
10.3.3.25 Device SIU Guidelight Status <DevSiuGuidelightStatus>

Tag
<DevSiuIdcGuidelight>
Type
Open Enum
Usage
Required
Description
Device SIU IDC Guidelight. The state of the card reader guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
Version 1.7
April 2005
17
Tag
<DevSiuCdmGuidelight>
Type
Open Enum
Usage
Required
Description
Device SIU CDM Guidelight. The state of the note dispenser guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuCoinOutGuidelight>
Open Enum
Required
Device SIU Coin Out Guidelight. The state of the coin dispenser guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuReceiptGuidelight>
Open Enum
Required
Device SIU Receipt Guidelight. The state of the receipt printer guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuPassbookGuidelight>
Open Enum
Required
Device SIU Passbook Guidelight. The state of the passbook printer guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuDepGuidelight>
Open Enum
Required
Device SIU DEP Guidelight. The state of the envelope depository guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuChkGuidelight>
Open Enum
Required
Device SIU CHK Guidelight. The state of the check reader guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuCimGuidelight>
Open Enum
Required
Device SIU CIM Guidelight. The state of the note accept guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuDocumentGuidelight>
Open Enum
Required
Device SIU Document Guidelight. The state of the document printer guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuCoinInGuidelight>
Open Enum
Required
Device SIU Coin In Guidelight. The state of the coin acceptor guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
<DevSiuScannerGuidelight>
Open Enum
Required
Device SIU Scanner Guidelight. The state of the scanner guidelight. Valid Values: Off, SlowFlash, MediumFlash, QuickFlash, Continuous, NotAvailable
10.3.3.26 Device Detail Cash Acceptor Aggregate <DevDetailCim>

Device details specific to cash acceptance devices (devices covered by the XFS CIM service class).
Tag
<DevCimType>
Type
Open Enum
Usage
Required
Description
Device CIM Type. Type of cash accept device. Valid Values: TellerBill, SelfServiceBill, TellerCoin, SelfServiceCoin
18
April 2005
Version 1.7
Tag
<DevCimOperation>
Type
Open Enum
Usage
Optional
Description
Device CIM Operation. The operation being performed at the time the alert is raised. Valid Values: CashInStart, CashIn, CashInEnd, Rollback, Retract, OpenShutter, CloseShutter, StartExchange, EndExchange, OpenSafeDoor, Reset, NotSupported
<DevCimSafeDoor>
Open Enum
Required
Device CIM Safe Door. The status of the safe door. Valid Values: Open, Closed, Unknown, NotSupported
<DevCimCashUnits>
Open Enum
Required
Device CIM Cash Units. The status of the acceptor cash units. Valid Values: OK, Warning, Fatal, Unknown
<DevCimIntermediateStacker>
Open Enum
Required
Device CIM Intermediate Stacker. The status of the intermediate stacker. Valid Values: Empty, NotEmpty, Full, Unknown, NotSupported
<DevCimStackerItems>
Open Enum
Required
Device CIM Stacker Items. Describes whether the items on the intermediate stacker have been in customer access. Valid Values: CustomerAccess, NoCustomerAccess, AccessUnknown, NoItems
<DevCimNoteReader>
Open Enum
Required
Device CIM Note Reader. The status of the banknote reader. Valid Values: OK, Inoperable, Unknown, NotSupported
<DevCimDropBox>
Open Enum
Required
Device CIM Drop Box. The status of the drop box. The drop box is an area within the CIM where items which have caused a problem during an operation are stored. Valid Values: Empty, NotEmpty, NotSupported
<DevCimPosition>
Required
Device CIM Position Aggregate.
<DevCimBin>
Required Repeating
Device CIM Bin Aggregate. Aggregate for each supported acceptor bin.
10.3.3.27 Device Cash Acceptance Position Aggregate <DevCimPosition>

Tag
<DevCimPositionLocation>
Type
Open Enum
Usage
Required
Description
Device CIM Position Location. Specifies the location of this position for cash acceptance. Valid values: InLeft, InRight, InCenter, InTop, InBottom, InFront, InRear, OutLeft, OutRight, OutCenter, OutTop, OutBottom, OutFront, OutRear
Version 1.7
April 2005
19
Tag
<DevCimShutter>
Type
Open Enum
Usage
Required
Description
Device CIM Shutter. The state of the shutter for this position. Valid values: Closed, Open, Jammed, Unknown, NotSupported
<DevCimPositionStatus>
Open Enum Open Enum
Required
Device CIM Position Status. The state of this position. Valid values: Empty, NotEmpty, Unknown, NotSupported
<DevCimTransport>
Required
Device CIM Transport. The state of the transport for this position. Valid values: OK, Inoperable, Unknown, NotSupported
<DevCimTransportItems>
Open Enum
Required
Device CIM Transport Items. The state of the transport for this position. Valid values: Empty, NotEmpty, CustomerAccess, Unknown, NotSupported
10.3.3.28 Device Cash Acceptance Module Bin Aggregate <DevCimBin>

Accepter bin details specific to CIM devices.
Tag
<DevCimBinNum> <DevCimBinType>
Type
Long Open Enum
Usage
Required Required
Description
Device CIM Bin Number. Number of the cash unit bin. Device CIM Bin Type. Type of media accepted by this device. Valid Values: Recycling, CashIn, RepContainer, RetractCassette
<DevCimBinStatus>
Closed Enum
Required
Device CIM Bin Status. The operational status of the currently referenced CIM cash bin. Valid Values: OK, Full, High, Empty, Inoperable, Missing, NotAvailable, NoReference, Manipulated
<DevCimBinCurCode> <DevCimBinDenomination> <DevCimBinCount> <DevCimBinMaxCount>
NC-3 Decimal Long Long
Device CIM Bin Currency Code. Three-letter currency code as defined by ISO-4217 Device CIM Bin Denomination. Denomination of the acceptor bin. Device CIM Bin Count. The total number of notes of all types in the cash unit. Device CIM Bin Maximum Count. The maximum number of notes the cash unit can hold.
10.3.3.29 Device Detail Cash Dispenser Module <DevDetailCdm>

Device details specific to the cash dispenser device (devices covered by the XFS CDM service class).
Tag
<DevCdmType>
Type
Open Enum
Usage
Required
Description
Device CDM Type. Type of dispenser device. Valid Values: TellerBill, SelfServiceBill, TellerCoin, SelfServiceCoin
20
April 2005
Version 1.7
Tag
<DevCdmOperation>
Type
Open Enum
Usage
Optional
Description
Device CDM Operation. The operation being performed at the time the alert is raised. It is strongly recommended that the following defined values be used rather than custom values in order to ensure maximum portability. Valid Values: Dispense, Present, Retract, Reject, Count, CloseShutter, OpenShutter, StartExchange, EndExchange, OpenSafeDoor, Calibrate, Reset, Test
<DevCdmSafeDoor>
Closed Enum
Required
Device CDM Safe Door. The status of the safe door. Valid Values: Open, Closed, NotSupported, Unknown
<DevCdmCashUnits>
Open Enum
Required
Device CDM Cash Units. The status of the dispenser cash units. Valid Values: OK, Warning, Fatal, Unknown
<DevCdmIntermediateStacker>
Open Enum
Required
Device CDM Intermediate Stacker. The status of the intermediate stacker. Valid Values: Empty, NotEmpty, CustomerAccess, NotEmpty, Unknown, NotSupported
<DevCdmPosition>
Required
Device CDM Position Aggregate.
<DevCdmBin>
Required Repeating
Device CDM Bin Aggregate. Aggregate for each supported dispenser bin. Note: At least 1 bin is required by the dispenser device.
10.3.3.30 Device Cash Dispenser Position Aggregate <DevCdmPosition>

Tag
<DevCdmPositionLocation>
Type
Open Enum
Usage
Required
Description
Device CDM Position Location. Specifies the location of this position for cash dispense. Valid values: OutLeft, OutRight, OutCenter, OutTop, OutBottom, OutFront, OutRear
<DevCdmShutter>
Open Enum
Required
Device CDM Shutter. The state of the shutter for this position. Valid values: Closed, Open, Jammed, Unknown, NotSupported
<DevCdmPositionStatus>
Open Enum Open Enum
Required
Device CDM Position Status. The state of this position. Valid values: Empty, NotEmpty, Unknown, NotSupported
<DevCdmTransport>
Required
Device CDM Transport. The state of the transport for this position. Valid values: OK, Inoperable, Unknown, NotSupported
<DevCdmTransportItems>
Open Enum
Required
Device CDM Transport Items. The state of the transport for this position. Valid values: Empty, NotEmpty, CustomerAccess, Unknown, NotSupported
Version 1.7
April 2005
21
10.3.3.31 Device Cash Dispenser Module Bin Aggregate <DevCdmBin>

Dispenser bin details specific to CDM devices.
Tag
<DevCdmBinNum> <DevCdmBinType>
Type
Long Open Enum
Usage
Required Required
Description
Device CDM Bin Number. Number of the dispenser bin. Device CDM Bin Type. Type of dispenser media. Valid Values: RejectCassette, BillCassette, CoinCylinder, CoinDispenser, RetractCassette, Coupon, Document, RepContainer, Recycling, NotApplicable
<DevCdmBinStatus>
Closed Enum
Required
Device CDM Bin Status. The operational status of the currently referenced CDM cash bin. Valid Values: OK, Jammed, NotSupported, NotAvailable, Unknown
<DevCdmBinMedia>
Closed Enum
Required
Device CDM Bin Media. The state of the media in the currently referenced CDM cash bin. Valid Values: OK, High, Full, Low, Empty, NotSupported, Unknown
<DevCdmBinCurCode> <DevCdmBinDenomination> <DevCdmBinCount> <DevCdmBinMaxCount>
NC-3 Decimal Long Long
Device CDM Bin Currency Code. Three-letter currency code as defined by ISO-4217 Device CDM Bin Denomination. Denomination of the dispenser bin. Device CDM Bin Count. The total number of notes of all types in the cash unit. Device CDM Bin Maximum Count. The maximum number of notes the cash unit can hold.
10.3.3.32 Device Detail Camera Aggregate <DevDetailCam>

Device details specific to camera devices (devices covered by the XFS CAM service class).
Tag
<DevCamType>
Type
Open Enum
Usage
Required
Description
Device CAM Type. Type of Camera device. Only one type is currently defined. Valid Values: Camera
<DevCamOperation>
Open Enum
Optional
Device CAM Operation. The operation being performed at the time the alert is raised. Valid Values: TakePicture, Reset, NotSupported
<DevCamStatusArea>
Open Enum
Required
Device CAM Status Area. Area monitored by the camera. Valid Values: Room, Person, ExitSlot
<DevCamStatusMedia>
Closed Enum
Optional
Device CAM Status Media. The state of the recording media of the camera. Valid Values: OK, High, Full, NotSupported, Unknown
22
April 2005
Version 1.7
Tag
<DevCamStatusState>
Type
Closed Enum
Usage
Optional
Description
Device CAM Status State. State of the camera. Valid Values: NotSupported, OK, Inoperative, Unknown
<DevCamStatusPictures>
Long
Optional
Device CAM Status Pictures. Number of pictures stored on the recording media of the camera.
10.4
10.4.1
Terminal Object
Terminal Object Add Message
An IFX client uses the <TerminalObjAddRq> message to add a Terminal object. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Terminal object resides on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
10.4.1.1 Request <TerminalObjAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<TerminalObjInfo>
Required
Terminal Object Information aggregate.
10.4.1.2 Response <TerminalObjAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 10.3.1.1 Aggregate see section 10.3.1
<MsgRsHdr>
<TerminalObjInfo>
Terminal Object Information Aggregate.
<TerminalObjRec>
Terminal Object Record Aggregate.
Version 1.7
April 2005
23
Tag
Type
Usage
Optional Optional
Description
10.4.2
Terminal Object Modify
An IFX client uses the <TerminalObjModRq> message to modify a Terminal object. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Terminal object resides on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
10.4.2.1 Request <TerminalObjModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Required Required
Terminal Object Identifier. Terminal Object Information Aggregate.
10.4.2.2 Response <TerminalObjModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Aggregate see section 10.3.1.1 Aggregate see section 10.3.1 Identifier
<MsgRsHdr>
Terminal Object Identifier. Terminal Object Information Aggregate.
<TerminalObjRec>
<CSPRefId>
Optional
Customer Service Provider Reference Identifier of the object information is requested on
24
April 2005
Version 1.7
Tag
<SPRefId>
Type
Identifier
Usage
Optional
Description
Service Provider Reference Identifier of the object information is requested on.
10.4.3
Terminal Object Inquiry
An IFX client uses the <TerminalObjInqRq> message to retrieve Terminal objects. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Terminal object resides on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
10.4.3.1 Request <TerminalObjInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<TerminalObjId>
Optional
Terminal Object Identifier. This field is used as a selection criterion.
10.4.3.2 Response <TerminalObjInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier
<MsgRsHdr>
<TerminalObjId>
Terminal Object Identifier.
<TerminalObjRec>
10.4.4
Terminal Object Delete
An IFX client uses the <TerminalObjDelRq> message to delete a Terminal object. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Terminal object resides on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
Version 1.7
April 2005
25
10.4.4.1 Request <TerminalObjDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<TerminalObjId>
Required
10.4.4.2 Response <TerminalObjDelRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Aggregate see section 10.3.1 Identifier Identifier
<MsgRsHdr>
<TerminalObjId> <TerminalObjRec>
Terminal Object Identifier. Terminal Object Record Aggregate.
Optional Optional
10.4.5
Terminal Object Audit
An IFX client uses the <TerminalObjAudRq> message to audit messages associated with a particular Terminal object. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Terminal object resides on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
10.4.5.1 Request <TerminalObjAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
26
April 2005
Version 1.7
Tag
<RecCtrlIn>
Type
Usage
Optional
Description
<SelRangeDt>
Optional
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). Valid values: Add, Mod, Del This field is used as a selection criterion.
<TerminalObjId>
Identifier
Required Repeating
10.4.5.2 Response <TerminalObjAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum
<MsgRsHdr>
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed Required Repeating Echoed Optional Repeating Optional Optional
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion. Terminal Object Identifier.
<TerminalObjId>
Identifier
<TerminalObjMsgRec>
Terminal Object Message Record Aggregate.
10.4.5.2.1 Terminal Object Message Record Aggregate <TerminalObjMsgRec>
Version 1.7
April 2005
27
Tag
<MsgRecDt>
Type
Timestamp
Usage
Optional
Description
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Terminal Object Add Response Message Aggregate.
<TerminalObjAddRs>
<TerminalObjModRs>
Terminal Object Modify Response Message Aggregate.
<TerminalObjDelRs>
Terminal Object Delete Response Message Aggregate.
10.4.6
Terminal Object Status Modify
An IFX client uses the <TerminalObjStatusModRq> message to modify the status of a particular Terminal object. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Terminal object resides on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
10.4.6.1 Request <TerminalObjStatusModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 Identifier Open Enum
Optional
<TerminalObjId> <RestartType>
Required Optional
Terminal Object Identifier. Restart Type. Requests that the terminal perform a restart prior to changing the operation mode. Valid Values: Restart
<EffUrgency>
Closed Enum
Optional
Effective Urgency. This element indicates the urgency that a terminal operation mode should take effect. Valid Values: Immediate, CurrentTransactionEnd, SessionEnd
<ExpectedOpenDt>
DateTime
Optional
Expected Open DateTime. The terminal date/time that the terminal operation mode is expected to return to "Open" if the operation mode is being changed to something other than Open. There is no obligation inferred. A Terminal application could use this information to inform customers when the Terminal may again be available. Terminal Object Status Aggregate.
<TerminalObjStatus>
Required
28
April 2005
Version 1.7
10.4.6.2 Response <TerminalObjStatusModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Open Enum Closed Enum DateTime Aggregate see section 10.3.1.2 Aggregate see section 10.3.1 Identifier Identifier
<MsgRsHdr>
<TerminalObjId> <RestartType> <EffUrgency> <ExpectedOpenDt> <TerminalObjStatus>
Required Echoed Optional Echoed Optional Echoed Optional Echoed Required Echoed Required
Terminal Object Identifier. Restart Type. Effective Urgency. Expected Open DateTime. Terminal Object Status Aggregate.
<TerminalObjRec>
Optional Optional
10.4.7
Terminal Object Advise
Since the Terminal object resides on the Terminal, the Terminal will use the <TerminalObjAdviseRq> message to inform other IFX entities (e.g. Hosts, CSP, SP) of changes to the Terminal object. If it is not necessary to Advise of changes to the data elements in the <TerminalObjInfo> aggregate then the <TerminalObjId> and <TerminalObjStatus> would be sent in the request. Otherwise, the entire <TerminalObjRec> aggregate should be sent.
10.4.7.1 Request <TerminalObjAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Version 1.7
April 2005
29
Tag
<TerminalObjRec>
Type
Usage
Description
<TerminalObjId> <TerminalObjStatus>
Terminal Object Identifier. Terminal Object Status Aggregate.
10.4.7.2 Response <TerminalObjAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<TerminalObjRec>
Required XOR Echoed Required XOR Echoed Required Echoed
<TerminalObjId>
<TerminalObjStatus>
Terminal Object Status Aggregate.
10.5
10.5.1
Terminal Service Provider Object

Terminal Service Provider Object Add Message
An IFX client uses the <TerminalSPObjAddRq> message to add a Terminal Service Provider object.
10.5.1.1 Request <TerminalSPObjAddRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
30
April 2005
Version 1.7
Tag
<TerminalSPObjInfo>
Type
Usage
Required
Description
Terminal Object Information aggregate.
10.5.1.2 Response <TerminalSPObjAddRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 10.3.2.1 Aggregate see section 10.3.2 Identifier Identifier
<MsgRsHdr>
<TerminalSPObjInfo>
Terminal Service Provider Object Information Aggregate.
<TerminalSPObjRec>
Terminal Service Provider Object Record Aggregate.
Optional Optional
10.5.2
Terminal Service Provider Object Modify
An IFX client uses the <TerminalSPObjModRq> message to modify a Terminal Service Provider object.
10.5.2.1 Request <TerminalSPObjModRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
Required Required
Terminal Service Provider Object Identifier. Terminal Service Provider Object Information Aggregate.
Version 1.7
April 2005
31
10.5.2.2 Response <TerminalSPObjModRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Aggregate see section 10.3.2.1 Aggregate see section 10.3.2 Identifier Identifier
<MsgRsHdr>
Terminal Service Provider Object Identifier. Terminal Service Provider Object Information Aggregate.
<TerminalSPObjRec>
Optional Optional
10.5.3
Terminal Service Provider Object Inquiry
An IFX client uses the <TerminalSPObjInqRq> message to retrieve Terminal Service Provider objects.
10.5.3.1 Request <TerminalSPObjInqRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.12.4.1 Identifier
Optional
<RecCtrlIn>
Optional
<TerminalSPObjId>
Terminal Service Provider Object Identifier. This field is used as a selection criterion. Service Provider Name. This field is used as a selection criterion. Terminal Identifier. This field is used as a selection criterion.
<SPName>
Identifier
<TerminalId>
Identifier
32
April 2005
Version 1.7
Tag
Type
Closed Enum Identifier
Usage
Description
Terminal Service Provider Object Status Code. This field is used as a selection criterion. Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion.
<CSPRefId>
<SPRefId>
Identifier
10.5.3.2 Response <TerminalSPObjInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 3.2.12.4.2 Identifier
<MsgRsHdr>
<RecCtrlOut>
Optional but see Description Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Terminal Service Provider Object Identifier.
<TerminalSPObjId>
<SPName>
Identifier
Service Provider Name.
<TerminalId>
Identifier
Terminal Identifier.
Terminal Service Provider Object Status Code.
<CSPRefId>
<SPRefId>
Identifier
<TerminalSPObjRec>
Version 1.7
April 2005
33
10.5.4
Terminal Service Provider Object Delete
An IFX client uses the <TerminalSPObjDelRq> message to delete a Terminal Service Provider object.
10.5.4.1 Request <TerminalSPObjDelRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Optional
<TerminalSPObjId>
Required
Terminal Service Provider Object Identifier.
10.5.4.2 Response <TerminalSPObjDelRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Identifier Aggregate see section 10.3.2 Identifier Identifier
<MsgRsHdr>
<TerminalSPObjId> <TerminalSPObjRec>
Terminal Service Provider Object Identifier. Terminal Service Provider Object Record Aggregate.
Optional Optional
10.5.5
Terminal Service Provider Object Audit
An IFX client uses the <TerminalSPObjAudRq> message to audit messages associated with a particular Terminal Service Provider object.
10.5.5.1 Request <TerminalSPObjAudRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
34
April 2005
Version 1.7
Tag
<MsgRqHdr>
Type
Aggregate see section 3.2.1.1 Aggregate see section 3.2.12.4.1 Aggregate see section 3.2.10.1 Closed Enum
Usage
Optional
Description
<RecCtrlIn>
Optional
<SelRangeDt>
Optional
<Method>
Optional Repeating
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). Valid values: Add, Mod, Del This field is used as a selection criterion.
<TerminalSPObjId>
Identifier
Required Repeating
10.5.5.2 Response <TerminalSPObjAudRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 3.2.12.4.2 Aggregate see section 3.2.10.1 Closed Enum
<MsgRsHdr>
<RecCtrlOut>
Optional but see Description Optional Echoed Optional Repeating Echoed
<SelRangeDt>
<Method>
Audit Selection Action. Used to identify actions associated with the object that is being audited (e.g. transfer). This field is used as a selection criterion.
<TerminalSPObjId>
Identifier
Required Repeating Echoed Optional Repeating Optional Optional
<TerminalSPObjMsgRec> <CSPRefId> <SPRefId>
Aggregate Identifier Identifier
Terminal Service Provider Object Message Record Aggregate. Customer Service Provider Reference Identifier of the object information is requested on Service Provider Reference Identifier of the object information is requested on.
Version 1.7
April 2005
35
10.5.5.2.1 Terminal Service Provider Object Message Record Aggregate <TerminalSPObjMsgRec>

Tag
<MsgRecDt>
Type
Timestamp
Usage
Optional
Description
Audit Record Creation Timestamp. Timestamp at which the audit record was stored/created by the service provider. Terminal Service Provider Object Add Response Message Aggregate. Terminal Service Provider Object Modify Response Message Aggregate. Terminal Service Provider Object Delete Response Message Aggregate.
<TerminalSPObjAddRs>
<TerminalSPObjModRs>
<TerminalSPObjDelRs>
10.5.6
Terminal Service Provider Object Advise
The <TerminalSPObjAdvise> message is used by a Service Provider to inform a Terminal that a change has occurred in the Terminal Service Provider Object. The primary use of the message is to inform a Terminal that service is available/unavailable from the Service Provider. Service is defined as a collection of one or more messages. If it is not necessary to Advise of changes to the data elements in the <TerminalSPObjInfo> aggregate then the <TerminalSPObjId> and <TerminalSPObjStatus> would be sent in the request. Otherwise, the entire <TerminalSPObjRec> aggregate should be sent.
10.5.6.1 Request <TerminalSPObjAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 10.3.2 Identifier Aggregate see section 10.3.2.2
Optional
<TerminalSPObjRec>
<TerminalSPObjId> <TerminalSPObjStatus>
Terminal Service Provider Object Identifier. Terminal Service Provider Object Status Aggregate.
36
April 2005
Version 1.7
10.5.6.2 Response <TerminalSPObjAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
<MsgRsHdr>
<TerminalSPObjRec>
Required XOR Echoed Required XOR Echoed Required Echoed
<TerminalSPObjId>
<TerminalSPObjStatus>
Terminal Service Provider Object Status Aggregate.
10.6
Device Messages
An IFX client uses the <DevInqRq> message to retrieve Device records from an IFX Terminal that can have one or more Device records. Each Device record contains the information and status of a particular device at an IFX Terminal. Typically the term client is associated with a Terminal and server is associated with a Host (e.g. CSP, SP). However, since the Device records reside on the Terminal, the IFX client that will use this message will be a Host (e.g. CSP, SP).
10.6.1
Tag
<RqUID>
Device Inquiry
Type
UUID
10.6.1.1 Request <DevInqRq>

Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.12.4.1 Identifier
Optional
<RecCtrlIn>
Optional
<DevId>
Device Identifier. This field is used as a selection criterion. Device Name. Human readable name of the device. This field is used as a selection criterion.
<DevName>
C-255
Version 1.7
April 2005
37
Tag
<DevType>
Type
Closed Enum
Usage
Optional Repeating
Description
Device Type. Device Type to return (i.e. as defined by <DevDetailXxx> Aggregates). For example if two DevType values are included in this inquiry with values of Idc and Ptr, the devices are filtered to only return devices that contain <DevDetailIdc> and <DevDetailPtr> aggregates. Valid Values: Idc, Ptr, Cdm, PIN, Chk, Dep, Ttu, Siu, Vdm, Cam, Alm, Ceu, Cim, App. This field is used as a selection criterion.
<DevStatusCode>
Closed Enum
Optional Repeating
Device Status Code. State-of-Health (SOH) of the devices to return. Devices returned should contain one of DevStatusCode values included in this request. For example if two DevStatusCode values are included in this inquiry with values of Warning and Fatal, the devices are filtered to only return devices with a status of Warning and Fatal. Valid Values: Healthy, Warning, Fatal, Suspend This field is used as a selection criterion.
<CSPRefId>
Identifier
Customer Service Provider Reference Identifier. This field is used as a selection criterion. Service Provider Reference Identifier. This field is used as a selection criterion.
<SPRefId>
Identifier
10.6.1.2 Response <DevInqRs>

Tag
<Status>
Type
Usage
Optional
Description
<RqUID>
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.1.2 Aggregate see section 3.2.12.4.2 Identifier
<MsgRsHdr>
<RecCtrlOut>
Records Control Output Aggregate. Required if <RecCtrlIn> was provided in the request and the server supports Records Control. Device Identifier.
<DevId>
<DevName>
C-255
Device Name.
<DevType>
Closed Enum
Device Type.
38
April 2005
Version 1.7
Tag
<DevStatusCode>
Type
Usage
Optional Repeating Echoed Optional Repeating Echoed Optional Repeating Echoed Optional Repeating
Description
Device Status Code.
<CSPRefId>
<SPRefId>
Identifier
<DevRec>
Device Record Aggregate.
10.6.2
Device Advise
An IFX Terminal uses the <DevAdviseRq> message to inform other IFX entities (e.g. Hosts, CSP, SP) of a change in the status of a device at the Terminal. It is expected the <DevAdviseRq> message will be sent to indicate both device faults, and when device faults have been resolved. If one transaction causes multiple device faults, then one <DevAdviseRq> message will be transmitted for each device fault.
10.6.2.1 Request <DevAdviseRq>

Tag
<RqUID>
Type
UUID
Usage
Required
Description
<MsgRqHdr>
Aggregate see section 3.2.1.1 Aggregate see section 3.2.3.1 UUID UUID
Optional
<CustId>
Optional
Customer Identifier. The customer at the terminal at the time of the failure. Transaction RqUID. The <RqUID>(s) of requests attempted to complete when failure occurred. Reconciliation RqUID. RqUID(s) of requests issued to attempt to reconcile the <TrnRqUID>(s) to what actually happened at the device. Device Record Aggregate.
<TrnRqUID> <ReconRqUID>
Optional Repeating Optional Repeating Required XOR Required XOR Required
<DevRec>
<DevId> <DevStatus>
Device Identifier. Device Status Aggregate.
10.6.2.2 Response <DevAdviseRs>

Tag
<Status>
Type
Usage
Optional
Description
Version 1.7
April 2005
39
Tag
<RqUID>
Type
UUID
Usage
Description
<MsgRqHdr>
<MsgRsHdr>
<CustId>
Optional Echoed Optional Repeating Echoed Optional Repeating Echoed Required XOR Echoed Required XOR Echoed Required Echoed
Customer Identifier.
<TrnRqUID>
Transaction RqUID.
<ReconRqUID>
UUID
Reconciliation RqUID.
<DevRec>
Device Record Aggregate.
<DevId>
Device Identifier.
<DevStatus>
Device Status Aggregate.
10.7 Root Service Profile Information <RootSvcProfInfo>

Tag
<SvcCore>
Type
Usage
Required
Description
Service Core Aggregate. Information specified for every service. Messages Supported for the Root Service. Defined values: TerminalObjAdd, TerminalObjMod, TerminalObjInq, TerminalObjDel, TerminalObjAud, TerminalObjStatusMod, TerminalObjAdvise, TerminalSPObjAdd, TerminalSPObjMod, TerminalSPObjInq, TerminalSPObjDel, TerminalSPObjAud, TerminalSPObjAdvise, DevInq, DevAdvise
<MsgSupt>
Required Repeating
<OptSupt>
Open Enum
Optional Repeating
40
April 2005
Version 1.7
Response Status Codes
The following table provides the complete set of valid Response Status codes defined for the Response Status Aggregate <Status> in Section 3.2.12.1, along with conditions that may cause the Response Status to be sent. Default text is provided in the <Desc> field, which is intended to be human-readable. The service provider may return this default text to the client, or may replace it with custom text that is more specific or translated into the appropriate language. The client may display the text it receives from the service provider, or may replace it with custom text that is more specific or translated into the appropriate language. The <StatusCode> and <Severity> elements are used by the system and must be included as they appear in the table. Negative <StatusCode> values (values less than zero) may be used for custom conditions. Clients receiving negative values for <StatusCode> with <Severity> Warn or Info must treat the response as if it were <StatusCode> 0 (Success). Clients receiving negative values for <StatusCode> with <Severity> Error must treat the response as if it were <StatusCode> 100 (General Error).
<StatusCode >
0 1
<Severity> <Desc> (Default Text)

Info Info Success Client Up to Date
Condition
The service provider successfully processed the request. The clients indicator (i.e., date-time or token) of last update in the request is equal to the servers indicator of last update processed. The service provider has successfully processed the request; however, it is suggesting (warning) the acquirer to verify/validate the cardholder/customers identification. The service provider has successfully processed the request; however, it is informing the acquirer about the VIP status of the cardholder/customer. The service provider has successfully processed the request; however, it is suggesting (warning) the acquirer to update the Track 3 data on the card (if it can). The entire string of the updated Track 3 data is typically eturned by the Customer Service Provider (CSP) in <MagData3> element of <CardMagData> aggregate in the response messages that contain this aggregate. The service provider has successfully processed the request; however, it is warning the acquirer that the account type in the response was specified by the transaction authorizer/issuer because the original request didnt specify it (it might have been specified as Default or Unknown). The service provider has successfully processed the request; however, it is warning the acquirer that the request was approved for the lesser amount than it was originally specified, and also the account type in the response was specified by the transaction authorizer/issuer because the original request didnt specify it (it might have been specified as Default or Unknown). There was an error that prevented the service provider from processing the transaction. No additional information is provided. One or more of the elements in the request is either invalid or is inconsistent with other elements. No additional information is available. The service provider for this transaction is not available due to a technical problem. Try again later
Warn
Honor with identification
Info
Approved (VIP)
Warn
Approved, update track 3
Warn
Approved, account type specified by issuer
Warn
Approved for partial amount, account type specified by issuer
100
Error
General Error
200
Error
General Data Error
300
Error
System Not Available
Version 1.7
April 2005
A-1
<StatusCode >
400 500 600 700 800 810 900 910 1000 1010

Error Error Error Error Error Error Warn Error Error Error Function Not Available Unsupported Service Unsupported Message Unsupported Function Object Already Committed Message Cannot Be Reversed Message Accepted for Asynchronous Processing Asynchronous Request Does Not Match Original Request Duplicate <RqUID> The <Cursor> returned within <RecCtrlIn> is invalid or has expired Required Element Not Included Request Declined
Condition
The function selected is not available. Other functions may be available. The service provider does not support the specified service offering. The server does not support the message. The server does not support one or more functions within the request. The object cannot be modified or canceled because it has already been committed for processing. The server is unable to reverse the requested message. The message was accepted for future processing. The message does not match the message referenced by the <AsyncRqUID>. A request with this client message identifier <RqUID> has already been received and processed. The suggested action is to resend the original message, omitting the cursor, to restart the sequence of messages required to retrieve all of the records. The request message does not contain one or more required elements. The Service Provider has declined your request (e.g., a no pay was received for a payment or a credit limit change request was declined). Customer input of an Enum value is not valid. The condition may echo the element name in error or the value input by the Customer. The service provider does not allow modifications to one or more elements in a modification request. No changes have been made. The requested change in a <xxxModRq> matched the existing data on the server. The request has asked for more records than the service provider can satisfy. The quantity that the service provider can satisfy has been provided. Records control is being used in the response, and RecCtrlOut is present in the response. No records match the selection criteria of the request. The server does not support one or more of the selection criterion fields in the request. Records returned based on only those supported. The server supports none of the selection criterion fields specified in the request. No records returned. The client has sent a token that precedes the history currently available. The client must do an inquiry to resync. The token is not of the valid format. Used when the client may edit the token format. The reference identifier used is invalid. Detail for this item is not available at this time.
1020 1040
Error Warn
1050
Error
Invalid Enum Value
1060 1080 1100
Error Warn Warn
Cannot Modify Element No Changes Made Too Many Records Requested
1110 1120 1140
Info Info Warn
Records Control Active No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Token Invalid Identifier Detail Not Available
1160 1180 1200 1220 1240
Error Error Error Error Warn
A-2
April 2005
Version 1.7
<StatusCode >
1260 1280

Error Warn Unknown Object ID Object already exists.
Condition
The specified object ID does not exist. The object that the client requested to add already exists. (e.g., the specified service is already activated for the customer or customer account, or customer is already enrolled.)
1290
Error
A duplicate Card Preference Preference was invalid because a duplicate association association already exists between between CardLogicalData and CardPrefType already exists. the presented card and the The operation is not allowed. selected business function. Object not deleted; dependent objects exist Cascade Delete Failed The object was not deleted because dependent objects exist, and the client did not request a cascading delete. The object was not deleted because the dependent objects could not be deleted at this time.
1300 1310 1320 1360 1380 1400 1420 1480 1500 1520 1540 1560 1580 1600 1620 1640 1700 1720
Warn Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Info
Object exists, but does not match The object exists but does not match the <CustId>. <CustId>. Customer is not authorized to act. <SPName> Invalid <SPName> within <CustId> is invalid <SPName> within <BillerId> is invalid. <CustId> invalid Edit Mask Error Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code <CryptType> not valid No <SPName> No <SvcName> Security Violation Customer Login ID And Password Will Be Sent Out-Of-Band Authentication Failed Authorization Failure OBO is not active for this <CustId> Service not Enabled Customer Session Already In Progress The Service Provider name specified in a request was not found or invalid. The Service Provider Name specified within a customer identification aggregate is invalid. The Service Provider Name specified within a biller identification aggregate is invalid. The customer identifier <CustId> specified is invalid or not found. The value specified does not match the edit mask. The specified address is incorrect. The city specified was incorrect. The state or province specified was incorrect. The postal code specified was incorrect. The specified country code is not valid in ISO 3166. <CryptType> not valid or not supported. Ambiguous request, <SPName> required Ambiguous request, <SvcName> required A security violation has occurred. The service provider will send the customer Login ID and password through postal mail, e-mail, or some other means. The customer could not be authenticated due to an incorrect login ID or password. Customer is not eligible to perform this function The currently logged-in customer does not have the authority to act on behalf of another user. The customer has not enabled the service with the service provider. The service provider supports only one session at a time per customer and there is already an active session for this <CustId>. Please try again later.
1740 1760 1790 1800 1820
Error Error Error Error Error
Version 1.7
April 2005
A-3
<StatusCode >
1840 1860 1880

Error Error Error No Customer Session In Progress Immediate Customer Lock Out Customer Locked Out
Condition
The specified customer does not have a session in progress. The customer identity for the current session is suspect. End any active sessions. The service provider has received too many failed authentication attempts for this customer or has detected other suspicious activity. Please call the technical support telephone number. The Logon is successful but the customer must enter a new password before any other messages will be allowed. The customer must change his or her password before any other messages will be allowed. The new customer ID entered is not valid because it does not meet edit criteria. The customer chose a customer identifier that is already in use. The new password entered as part of a <CustPswdModRq> is invalid. The ID of the client application is unsupported. Non-numeric or missing data was encountered in a single or low amount field.
1900 1910 1920 1940 1970 1980 2000 2010 2020 2030 2040
Warn Error Error Error Error Error Error Error Error Error Error
Password Change Required Must Change Password Invalid New Customer Identifier New Customer Identifier in use Invalid New password Unsupported Application ID Invalid Data in Single or Low Amount Field
Invalid Data in High Amount Field Non-numeric or missing data was encountered in a high amount field. Amount Too Small Amount Too Large Amount Out of Range The amount entered is too small (e.g., less than the minimum required). Please enter a larger amount. The amount entered is too large (e.g., exceeds the limit for this transaction). Please enter a smaller amount. The amount entered is not within the valid range of acceptable values, i.e. it could be less than the minimum accepted or greater than the maximum accepted. This status should be returned in scenarios where the authorisation system does not report whether the amount was too high or too low. Low amount is greater than high amount in an amount range. The service provider has established a maximum value for the amount of the final transfer or payment, which has been exceeded. The specified single date/time or the low date/time in a range is not in a valid date/time format.
2060 2080
Error Error
Invalid High/Low Amount Final Amount Exceeds Limit
2100 2110 2120 2130 2140 2150
Error Error Error Error Error Error
Invalid DateTime - Single date or Low of Range
Invalid DateTime - High of Range The specified high date/time in a range is not in a valid date/time format. Invalid DateTime Range Date Passed DateTime Too Soon DateTime Too Far In Future The date range specified is invalid because the low date exceeds the high date. The date entered is in the past. Please enter a valid date. The specified date and time is too near; enter a later date and time. The specified date and time is too far in the future. Reenter an earlier date.
A-4
April 2005
Version 1.7
<StatusCode >
2160 2170 2180 2190 2200 2210 2220 2300

Error Warn Error Error Warn Warn Warn Error Processing Date Precedes Today Requested Date Adjusted Request Is Too Late For Todays Work Weekend Or Holiday
Condition
The processing date required to meet the due date <DueDt> entered would be earlier than today. The Service Provider successfully processed the request, but the date requested has been adjusted. The customer has asked to schedule a transfer or payment for today but the cutoff time for todays work has passed. The date entered is a weekend or holiday. The date cannot be adjusted.
History Not Available for Full Date History is not available for the full date range specified. All Range transactions that were available were returned. Account Balance Information Not Available Extended Account Balance Information Not Available Single or Source Account Invalid One or more account balances for the selected account is currently unavailable. One or more extended account balances for the selected account is currently unavailable. The Specified single account <xxxAcctId> or source account <xxxAccIdtFrom> identification aggregate contains invalid data or was not found. The specified destination account identification aggregate <xxxAcctIdTo> contains invalid data or was not found.
2310 2320
Error Error
Destination Account Invalid
Single Account or Source Account The specified single account <xxxAcctId> or source Not For Customer account <xxxAcctIdFrom> does not correspond to the customer. Destination Account Not For Customer Single or Source Account Closed Destination Account Closed Source And Destination Accounts Are Identical Single or Source Account Not Authorized Destination Account Not Authorized Single or Source Account Not Available The specified destination account <xxxAcctIdTo> does not correspond to the customer. The specified single account <xxxAcctId> or source account <xxxAcctIdFrom> has been closed. The specified destination account <xxxAcctIdTo> has been closed. A transfer that indicates that the source and destination accounts are the same is invalid. The customer is not authorized to perform the requested action on the specified single or source account. The customer is not authorized to perform the requested action on the specified destination account. The single or source account requested is not available for transaction processing at this time. The customer may continue to access other accounts.
2340 2350 2360 2370 2380 2390 2400
Error Error Error Error Error Error Error
2410
Error
Destination Account Not Available The destination account requested is not available for transaction processing at this time. The customer may continue to access other accounts. Single or Source Account Not Eligible For Transaction Destination Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Destination Account Type Single or Source Account <BankId> Error This single or source account is not authorized for this particular transaction. This destination account is not authorized for this particular transaction. The single or source account type specified is not permitted by the service provider. The service provider does not permit the destination account type specified. The Bank Identifier <BankId> in the source or single account identification aggregate is incorrect.
2420 2430 2440 2450 2460
Version 1.7
April 2005
A-5
<StatusCode >
2470 2480 2490

Error Error Error Destination Account <BankId> Error Branch ID Missing Invalid <BankInfo>
Condition
The Bank Identifier <BankId> in the destination account is incorrect. A branch ID value must be provided in the single or source bank account information aggregate, but is missing. The information contained within <BankInfo> is either invalid or insufficient to unambiguously identify the single or source bank. The specified industry number is not valid for the Organization identifier. The card magnetic strip data provided is either incorrect or incomplete.
2500 2510 2520
Error Error Error
Invalid Industry Id Invalid Card Magnetic Strip Data
Unrecognized / Invalid Card Issuer The card track data has been analyzed and found to be valid. The primary account number (PAN) has been extracted and the Issuer ID obtained from the PAN. The switch/server does not know how to route the transaction since it does not recognize the issuer ID (e.g. trying to use a Bank of Scotland debit card in the US). The most likely result would be for the ATM to return the card to the user after displaying a message such as "This ATM does not accept cards from your financial institution". Unrecognized Card Number The card track data has been analyzed and found to be valid. The PAN has been extracted from the card, the issuer is known and the transaction routed to the issuer. However the issuer cannot find this PAN on its database. This card is from an institution known to the ATM owner, but the card number is invalid. The most likely result would be for the ATM to capture this card (especially if the card was issued by the ATM owner). The card has been registered as stolen, and is therefore invalid as either an authentication mechanism for transactions or an identifier for one or more accounts. The specified check number range is invalid. The customer has requested a Stop Payment on a check that has already cleared the bank and settled. The specified check number could not be found. Stop Check is already in process. The check range specified in <StopChkAddRq> is too large for the service provider to handle. The specified checkbook style is not currently available. Please choose another style The number of checks specified is not valid for the specified checkbook style. The currency code on both accounts involved in a transfer must be the same as the currency code of the input amount, unless ForEx is specified in <OptSupt>. The specified currency code is not valid in ISO 4217. The specified language code is not valid in RFC-1766. The specified frequency is not supported for this message.
2530
Error
2540
Error
Stolen Card
2600 2610 2620 2640 2660 2680 2700 2720
Error Error Error Warn Error Error Error Error
Invalid Check Number Range Request Is Too Late - Check has been paid Check Number Not Found Stop Check In Process Too Many Checks To Process Check Book Style Not Available Invalid Number Of Checks Foreign Exchange not supported
2740 2760 2780
Error Error Error
Invalid Currency Code Invalid Language Code Unsupported Frequency
A-6
April 2005
Version 1.7
<StatusCode >
2900

Error
Condition
Duplicate Payment/Transfer Exists The customer has attempted to schedule a payment/transfer that matches a previously entered payment/transfer (I.e., the day, amount and merchant or to account are the same). The client may resubmit using <DupChkOverride> = True, if the payment or transfer is not a duplicate. Duplicate Recurring Model The customer has attempted to schedule a recurring model that matches a previously entered model. The client may resubmit using <DupChkOverride> = True, if the model is not a duplicate. The number of transfers or payments specified to skip exceeds the number of transfers or payments remaining for this recurring model. The service provider cannot process the transaction because the specified account does not have sufficient funds. The number of transfers allowed for a monthly or statement cycle has been exceeded. Total transfers for today exceed maximum allowable for one day. A transfer to a loan account (a payment) is declined because the loan payoff is less than the transfer amount. The amount authorized for the transaction is different from that originally requested Either the requested withdrawal or cash back (if present) amount in the transaction request exceeds the currently allowable limit. However, the transaction was approved with a reduced, but maximum allowed, amount. This reduced amount is present in the transaction response message.
2910
Error
2920
Error
Invalid skip count
2940
Error
Insufficient Funds
3000 3020 3040 3050 3052
Error Error Error Warn Warn
Number of Transfers Exceeds Limit Daily Transfer Limit Exceeded Transfer Payment Greater Than Loan Balance Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed
Upon receiving this warning response, the client could offer a choice to the consumer, informing him/her about the reduced amount from the response message, and giving a choice to either accept or deny/reject the transaction.
3060 3070 3080 3090 3100 3120 3140 3180 3200 Error Warn Error Error Error Error Error Error Error Usage Limit Exceeded Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Invalid <BillerId> Invalid <StdPayeeId> Invalid Customer Payee ID Invalid Payee Name Payee List Full The number of transactions of this type exceeds a predefined limit over a given time period. The Fees required are different from those send in the request The amount the customer wishes to withdraw exceeds the withdrawal limit Client is not authorized to override the fee. The biller identifier specified could not be found or is invalid. The standard payee identifier could not be found or was invalid. The specified Customer Payee ID <CustPayeeId> does not exist or no longer exists. The name specified for the payee was incorrect or incomplete. The payee list is currently full. To add a payee, first delete an existing payee.
Version 1.7
April 2005
A-7
<StatusCode >
3240 3260 3300 3320

Error Error Error Error Invalid Customer Account With Payee Payee Type Not Supported Number Of Payments Invalid Total Payment Amounts Scheduled For Today Exceeded Daily Limit Expired Card Recurring Model Open-Ended Data Changed or Truncated
Condition
The pay account <PayAcct> specified by the user is invalid. This service provider does not support the payee type requested. The number of payments entered is invalid. Please re-enter the number of payments. The sum of all payment amounts scheduled for today exceeds the daily limit (either at the SP or customer level). The card specified has expired. No final date or number of instances has been specified for the recurring model; it has been added as open-ended. The server is responding with a warning that the <xxxRec> in the response is not identical to the data provided in the request. Rather, the data has been changed en route to storage. The currencies of the amounts (e.g. in <SelRangeCurAmt>) are not the same.
3380 3400 3500
Error Warn Warn
3520 3560 3580 3600 3610
Error Error Error Info Error
Currencies dont match
Card Account ID Matches Multiple The account cannot be uniquely identified based on the Accounts information provided by the Card Account Identifier. Authorization is rejected Authorization held over Authorization is declined for insufficient funds. Authorization is declined for inactive account. The Pay Provider is indicating that the payment has been rejected by the Customer Payment Provider The Pay provider is indicating that a payment has held over (typically for next day payment) by the CPP The financial institution has declined the payment authorization because the specified account does not have sufficient funds. The financial institution has declined the payment authorization because the specified account is inactive.
3620 3630 3640
Error Error Error
Authorization is declined for closed The financial institution has declined the payment account. authorization because the specified account is closed. Authorization is declined for other The financial institution has declined the payment reason. authorization for another reason. Customer should contact the FI for specific reason. Cash deposit limit exceeded. Object Type Not Supported Purpose Not Supported Format Not Supported Key Storage Space not available Invalid Certificate Revoked Certificate Customer not related to account New Tax Responsible Party not Certified, Action Successful The amount the customer wishes to deposit exceeds the cash deposit limit. Client does not support indicated Security Object Type Client does not support indicated purpose of Security Object Client does not support indicated security Object Format Storage space not available for key Certificate failed validation Certificate on Certificate Authorities revocation Invalid Customer to Account Relationship combination. Non-Certified Warn Indicator is set for Product, therefore, New Tax Responsible Party not Certified, Action Successful warning message is returned.
3650 3700 3710 3720 3730 3740 3750 3760 3770
Error Error Error Error Error Error Error Error Warn
A-8
April 2005
Version 1.7
<StatusCode >
3780 3800 3810

Error Error Error Delete would result in an invalid customer to account relationship Message Authentication Error <SPRefId> not recognized
Condition
Delete would result in an invalid customer to account relationship The message authentication code (MAC) value is not correct. The <SPRefID> is not recognized so cannot be used to process the request (<ForExDealAddRq>) or interpret the response (<ForExDealAddRs>). The <ForExDealId> provided for action (Inquire, Modify, Cancel, Audit, etc.) is not recognized. The <CurAmt> reported in the <ForExDealAddRq> does not match the <CurAmt> of the prior rate inquiry response (<ForExRateInqRs>). The <CurCode> reported in the deal request (<ForExDealAddRq>) does not match the CurCode of the prior rate inquiry (<ForExRateInqRs>). The combination of <CurAmt> and <CurCode> reported in the deal request (<ForExDealAddRq>) does not match the combination of <CurAmt> and <CurCode> of the prior rate inquiry response (<ForExRateInqRs>). The offer for the deal add requested has expired. The <ForExRateDealType> has not been provided. Device is currently in a state that does not allow it to initiate the Remote Key Load process. Remote Key Load Process will be initiated at a future point in time. Device does not support Remote Key Load Signed message has an invalid signature. Server did not recognize the specific value of the ModuleID. Client sent a request message where the required request for Fee should have been included. This request failed because of the failure of an associated message. Please check the <StatusCode> in the associated message. Object ID indicating what <SecObjValue> is Signed with is invalid Signature calculated using <SecSignID> does not match signature in <SecObjValue> Stop payment match on serial number or amount. The check was already accepted and is a duplicate on account. The cash back amount is greater then the total amount of cash and checks deposited. The request message contained data deemed to be nonmodifiable (read only) by the server. Changes to the nonmodifiable fields were ignored. Server requested identification device capture. This request could be made for cause (i.e., lost or stolen card) or as part of normal operations (i.e., single use card, stored value card with no remaining value, etc.)
3820 3830
Error Error
<ForExDealId> not recognized <CurAmt> does not equal prior <CurAmt> <CurCode> does not equal prior <CurCode> Combination of CurAmt and CurCode do not match the <SPRefId> Deal expired No <ForExRateDealType> provided. Remote Key Load Pending
3840
Error
3850
Error
3860 3870 3880
Error Warn Information
3890 3900 3910 3920 3930
Remote Key Load not supported Invalid Signature Invalid ModuleID value Required request for Fee Missing Associated message failed
3940 3950 3960 3970 3980 3990
Error Error Error Error Error Warn
Unknown Object ID Signature Check Failed Stop payment match. Check already accepted. Cash back exceeds total amount deposited Read only data ignored
4000
Warn
Capture Card
Version 1.7
April 2005
A-9
<StatusCode >
4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010

Error Error Error Error Error Error Info Warn Error Warn Warn Incorrect Postal Code Incorrect Address
Condition
Customer Postal Code does not match expected value. Customer Address does not match expected value.
Incorrect Address and Postal Code Customer Address and Postal Code do not match expected values. Address Not Validated Address Verify Not Supported No Address Data Address Validated Successfully Card Verify Error Accepted Card Verify Error Denied Card Verify Failure Accepted Card Verify Failure Referred Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted. The Server is indicating to the client application that if supported, the client application should prompt if the customer would like to have the details of the current transaction saved as a Card Preference for this transaction type. Note that if the customer accepts, the IFX Client must send the appropriate CardPref messages in order to create/modify this preference. The server received a Terminal Id that it did not recognize. In other words, the server received a Terminal Id in the message that it does not have any knowledge of. Host is asking the terminal not to honor the consumers requested transaction. Card entered for the transaction request is recognized by the CSP or host as a restricted card, i.e., only a limited set of transactions are allowed with this card. E.g., Deposits and/or Balance Inquiry, but not Withdrawals and/or Transfers. Authorization system is suggesting the cardholder and/or card-acquirer to contact the acquirers security department. A card that has been reported lost was used in this transaction. The cardholder is advised to contact the card issuer financial institution. Authorization system is suggesting the cardholder and/or card-acquirer to refer to the card issuers special conditions. The merchant id is invalid.
5020 5030 5040
Error Warn Info
Card Verify Failure Denied Card Ineligible For Verify Prompt Customer to save current transaction information as a Card Preference for this transaction type
6000
Error
Terminal Not Configured
6010 6020
Error Error
Do Not Honor Restricted Card
6030 6040 6050 6060
Error Error Error Error
Call Acquirers Security Dept. Lost Card Refer To Card Issuer Refer To Card Issuers Special Conditions Invalid Merchant
6070
Error
A-10
April 2005
Version 1.7
<StatusCode >
6080 6090 6100 6110 6120 6130

Error Error Error Error Error Error PIN Data Required Unacceptable Fee Message Not Permitted From Terminal Violation of Law Card Not Effective/Activated Invalid PIN Block
Condition
The required PIN data is missing. The ATM and/or acquirer has imposed a fee that is not acceptable to the authorizer. The cardholder has requested a message (the entire message) that is not supported from this terminal. A violation of applicable law was detected. The card used is not effective or activated. The (encrypted) PIN block data is invalid. This response code is different from the Authentication Failed, where the cardholders PIN/User or Logon Id/Password is wrong. In this case (Invalid PIN Block), the response indicate some sort of mechanical failure in formatting the PIN block (e.g., Invalid PIN pad character, or hex vs. BASE64 encryption, etc.) PIN length used for this transaction is incorrect. A PIN Encryption Key synchronization error was detected. A server/authorizer might return this response status code when it detects a pre-established number of Invalid PIN errors, or any similar pre-established PIN-related error conditions. Third party customer/vendor for the transaction was not found. Third party customer/vendor account is invalid. Transaction acquirer (CSP) not found. Formatted date is invalid. This response status code is used for more general date format or validation errors, where the specific type of date errors (older or future date, etc.) are not provided, specifically, by the legacy host systems. Although the cardholder has requested the full statement, but the statement data doesnt warrant a full statement. Only limited data is available for mini statement, and the customer should be asked whether to continue (fee implications). A mini-statement could be provided, instead. The requested statement data is not available. The authorization system has detected an Administrative/Supervisory card in the transaction request. It is assumed that the ATM has requested to switch into Admin. or Supervisory mode. This status code will be returned by any IFX response messages where a server receives the card number from a client, and the server/authorizer detects the card to be an Administrative card type (mainly the Signon response message).
6140 6150
Error Error
PIN Length Error PIN Key Sync Error
6160 6170 6180 6200
Error Error Error Error
Third Party Vendor Not Found Third Party Vendor Account Invalid Customer Service Provider Not Supported Invalid Date
6210
Warn
Full Statement Requested, Mini Statement Could Be Provided
6220 6300
Error Info
No Statement Data Available Admin/Supervisory Card Entered
Version 1.7
April 2005
A-11
<StatusCode >
6310

Error Function Not Available To User
Condition
The service provider cannot provide the requested function to the user. This function may be available to other users. This will be typically used in ATM networks where the authorization system has detected the card used in the transaction request as a "foreign" card, not issued by the authorizer. The authorizer has recognized this card as one issued by a financial institution that the authorizer has a "switch" relationship (not-on-us card) and the interchange to the issuer does not support the function requested. An example could be the Service Account Inquiry Response (SvcAcctInq) message, where the authorizer has detected the card as a "not-on-us". So, based on this status code, the ATM client can issue the subsequent transaction (typically, a Withdrawal) knowing that the issuer cannot provide the "account list", but it can route the transaction to a switch for processing.
6320
Error
Invalid Cassette Id
An invalid cassette/hopper/container Id was detected in an Administration/Supervisory transaction request (that the server couldnt match with its existing cassette Id). The Admin. transaction with this invalid cassette Id was not processed by the server, and the administrator or supervisor must re-enter this transaction with the valid cassette Id in order to proceed with this transaction. The CashBack amount in the transaction could not be authorized, but the original credit or debit amount in the same transaction was successfully authorized. Therefore, the CashBack amount has been changes in the response record (XxxRec) to a zero value. The deposit transaction was authorized with a warning because the authorizing entity has withheld a portion of the originally requested deposit amount. The amount withheld is included in the response message, which will not be available until the time period also indicated in the response message.
6330
Warn
Cash Back Amt Not Approved, Original Credit or Debit Amt was Approved
6340
Warning
A Portion of the Requested Deposit Amount was Held by the Authorizer
6350 6360 6370
Error Error Error
Posting session cannot be back-dated. Posting session cannot be future-dated. Posting Session Location invalid Posting Session is not available. Posting Session totals do not meet Close Final criteria
The teller or operator is not authorized to perform backdated transactions. The teller or operator is not authorized to perform future-dated transactions. The Posting Session location is invalid or the teller does not have security to perform transactions on behalf of the session location The Posting Session is not available for the teller or operator to perform transactions against. The Posting Session totals do not meet the criteria of the server to allow the close final to proceed.
6380 6390 6400
Error Error Error
Posting Session Location error The Posting Session has already been opened at a different location.
A.1
All Messages
The following <StatusCode>s may be provided in any response and are not repeated in the following message tables:
A-12
April 2005
Version 1.7
<StatusCode>
0 5 6 7 8 9 100 200 300 400 500 600 700 900 910 1000 1360 1910 2040 3800 3920 3930 4000 6000 6010 6020 6030 6040 6050 6060 6070 6090 6100 6110 6120 6160 6170 6180 6190 6200
<Desc>
Success Honor with identification Approved (VIP) Approved, update track 3 Approved, account type specified by issuer Approved for partial amount, account type specified by issuer General Error General Data Error System Not Available Function Not Available Unsupported Service Unsupported Message Unsupported Function Message Accepted for Asynchronous Processing Asynchronous Request Does Not Match Original Request Duplicate <MsgUID> <SPName> Invalid Must Change Password Amount Out of Range Message Authentication Error Required request for Fee Missing Associated message failed Server requested identification device capture. Terminal Not Configurred Do Not Honor Restricted Card Call Acquirers Security Dept. Lost Card Refer To Card Issuer Refer To Card Issuers Special Conditions Invalid Merchant Unacceptable Fee Message Not Permitted From Terminal Violation of Law Card Not Effective/Activated Third Party Vendor Not Found Third Party Vendor Account Invalid Customer Service Provider Not Supported Invalid Acquirer Data Invalid Date
Version 1.7
April 2005
A-13
<StatusCode>
6310 6380
<Desc>
Function Not Available To User Posting Session is not available.
In addition the following <StatusCode>s may be received in most responses and are not included in the message tables:
<StatusCode>
1010 1020 1110 1380 1420 1790 1800
<Desc>
The <Cursor> submitted within <RecCtrlIn> is invalid or has expired Required Element Not Included Records Control Active <SPName> within <CustId> is invalid <CustId> invalid OBO is not active for this <CustId> Service Not Enabled
A.2
A.2.1
1580 1700 1740 1820 1880 1900 1980 2510 2520 2530 2540 2760 3380 6080 6130 6140 6150 6300
Security Messages
Signon (Signon)
<Desc>
Invalid Country Code Security Violation Authentication Failed Customer Session Already In Progress Customer Locked Out Password Change Required Unsupported Application ID Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Language Code Expired Card PIN Data Required Invalid PIN Block PIN Length Error PIN Key Sync Error Admin/Supervisory Card Entered
<StatusCode>
A-14
April 2005
Version 1.7
A.2.2
1840
Signoff (Signoff)
<Desc>
No Customer Session In Progress
<StatusCode>
A.3
A.3.1
1
Base Service
Service Profile Inquiry (SvcProfInq)
<Desc>
Client Up To Date
<StatusCode>
A.3.2
1620 1640
Holiday Inquiry (HolInq)

<Desc>
No <SPName> No <SvcName>
<StatusCode>
A.3.3
1700 1720 1740 1760 1970
Customer Password Modify (CustPswdMod)

<Desc>
Security Violation Customer Login ID and Password Will Be Sent Out-Of-Band Authentication Failed Authorization Failure Invalid New Password
<StatusCode>
A.3.4
1280 1500 1520 1540 1560 1580 1600 1720 1760 1920 1940 1970
Customer Add (CustAdd)

<Desc>
Object already exists. Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code <CryptType> not valid Customer Login ID and/or Password will be Sent Out-Of-Band Authorization Failure Invalid New Customer Identifier New Customer Identifier in use Invalid New Password
<StatusCode>
Version 1.7
April 2005
A-15
A.3.5
1060 1080 1260 1320 1500 1520 1540 1560 1580
Customer Modify (CustMod)

<Desc>
Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId> Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code
<StatusCode>
A.3.6
1060 1080 1260 1320
Customer Status Modify (CustStatusMod)

<Desc>
Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.3.7
1
Customer Inquiry (CustInq)

<Desc>
Client Up To Date
<StatusCode>
A.3.8
1 1100 1180 1200
Customer Synchronization (CustSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History Invalid Token
<StatusCode>
A.3.9
1280 2300 2320 2350 2380
Customer/Service Link Add (CustSvcAdd)

<Desc>
Object Already Exists Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized
<StatusCode>
A-16
April 2005
Version 1.7
<StatusCode>
2400 2420 2460 2480 3380
<Desc>
Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Expired Card
A.3.10
1050 1060 1080 1260 1320 1980 2300 2320 2350 2380 2400 2420 2440 2460 2480
Customer/Service Link Modify (CustSvcMod)

<Desc>
Invalid Enum Value Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId> Invalid Application ID Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> Error Branch ID Missing
<StatusCode>
A.3.11
Customer/Service Link Status Modify (CustSvcStatusMod)

<Desc>
Cannot Modify Element No Changes Made
<StatusCode>
1060 1080
A.3.12
1050 1300 1310
Customer/Service Link Delete (CustSvcDel)

<Desc>
Invalid Enum Value Object Not deleted; dependent objects exist Cascade Delete Failed
<StatusCode>
Version 1.7
April 2005
A-17
A.3.13
1050 1100 1360 2120 2140
Customer/Service Link Audit (CustSvcAud)

<Desc>
Invalid Enum Value Too Many Records Requested <SPName> Invalid Invalid DateTime Range DateTime Too Soon
<StatusCode>
A.3.14
1 1100 1180 1200
Customer/Service Link Synchronization (CustSvcSync)

<Desc>
Client Up To Date Too Many Records Requested Token Value Prior to Available History Invalid Token
<StatusCode>
A.3.15
1600 2300 2320 2350 2380 2400 2420 2460 2480
Service/Account Link Add (SvcAcctAdd)

<Desc>
<CryptType> not valid Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <Bankid> Error Branch ID Missing
<StatusCode>
A.3.16
1060 1600 2300 2320 2350 2380 2400 2420 2460
Service/Account Link Modify (SvcAcctMod)

<Desc>
Cannot Modify Element <CryptType> not valid Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error
<StatusCode>
A-18
April 2005
Version 1.7
<StatusCode>
2480
<Desc>
Branch ID Missing
A.3.17
Service/Account Link Status Modify (SvcAcctStatusMod)

<Desc>
<StatusCode>
1060 1080 1260 1320
A.3.18
Service/Account Link Identifier Modify (SvcAcctIdMod)

<Desc>
<StatusCode>
1060 1080 1260 1320
A.3.19
1300 1310 2300 2320 2460 2480
Service/Account Link Delete (SvcAcctDel)

<Desc>
Object not deleted; dependent objects exist Cascade Delete Failed Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account <BankId> Error Branch ID Missing
<StatusCode>
A.3.20
1050 1120 1140 1160 2100 2150
Service/Account Link Inquiry (SvcAcctInq)

<Desc>
Invalid Enum Value No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid DateTime Single date or Low of Range DateTime Too Far in Future
<StatusCode>
Version 1.7
April 2005
A-19
A.3.21
1050 1100 1120 1140 1160 2100 2110 2120 2150
Service/Account Link Audit (SvcAcctAud)

<Desc>
Invalid Enum Value Too Many Records Requested No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid DateTime Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range DateTime Too Far in Future
<StatusCode>
A.3.22
1 1100 1180 1200
Service/Account Link Synchronization (SvcAcctSync)

<Desc>
<StatusCode>
A.3.23
810
Service/Account Link Reversal (SvcAcctRev)

<Desc>
Message can not be reversed.
<StatusCode>
A.3.24
1050 1120 1140 1160 1260 1320
Disclosure Inquiry (DiscInq)

<Desc>
Invalid Enum Value No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.3.25
Customer/Disclosure Link Status Modify (CustDiscStatusMod)

<Desc>
Cannot Modify Element Invalid Enum Value
<StatusCode>
1060 1050
A-20
April 2005
Version 1.7
<StatusCode>
1260 1320
<Desc>
Unknown Object ID Object exists, but does not match <CustId>
A.3.26
1050 1120 1140 1160 1260 1320
Customer/Disclosure Link Inquiry (CustDiscInq)

<Desc>
Invalid Enum Value No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.3.27
1120
Customer Identifier Inquiry (CustIdInq)

<Desc>
No Data Matches Selection Criteria
<StatusCode>
A.3.28
1060 1720 1910
Customer Status Modify (CustStatusMod)

<Desc>
Cannot Modify Element Customer Login ID And Password Will Be Sent Out-Of-Band Must Change Password
<StatusCode>
A.3.29
1060 6130 6140
Customer Authorization Modify (CustAuthMod)

<Desc> (Default Text)
Cannot Modify Element Invalid PIN Block PIN Length Error
<StatusCode>
A.3.30
1260 3700 3710 3720 3730 3740
Security Object Add (SecObjAdd)

<Desc>
Unknown Object ID Object Type Not Supported Purpose Not Supported Format Not Supported Key Storage Space not available Invalid Certificate
<StatusCode>
Version 1.7
April 2005
A-21
3750 3900 3910 3940 3950
Revoked Certificate Invalid Signature Invalid ModuleID value Unknown Object ID Signature Check Failed
A.3.31
1060 1260 3740 3750 3900 3910 3940 3950
Security Object Modify (SecObjMod)

<Desc>
Cannot Modify Element Unknown Object ID Invalid Certificate Revoked Certificate Invalid Signature Invalid ModuleID value Unknown Object ID Signature Check Failed
<StatusCode>
A.3.32
1120 1260
Security Object Inquiry (SecObjInq)

<Desc>
No Records Match Selection Criteria Unknown Object ID
<StatusCode>
A.3.33
1260
Security Object Delete (SecObjDel)

<Desc>
Unknown Object ID
<StatusCode>
A.3.34
3880 3890
Security Object Advise (SecObjAdvise)

<Desc>
Remote Key Load Pending Remote Key Load not supported
<StatusCode>
A.3.35
1 200 1100 1180
Security Object Sync (SecObjSync)

<Desc>
Client Up To Date General Data Error Too Many Records Requested Token Value Prior to Available History
<StatusCode>
A-22
April 2005
Version 1.7
1200
Invalid Token
A.3.36
200 300 1020 2300 1280 3700 3760 3770
Party Account Relationship Add (PartyAcctRelAdd)

<Desc>
General Data Error System Not Available Required Element Not Included Single or Source Account Invalid Object already exists. Invalid Relationship Type for Product Customer not related to account New Tax Responsible Party not Certified, Action Successful
<StatusCode>
A.3.37
700 1020 1060 2300 3780
Party Account Relationship Modify (PartyAcctRelMod)

<Desc>
Unsupported Function Required Element Not Included Cannot Modify Element Single or Source Account Invalid New Tax Responsible Party not Certified, Action Successful
<StatusCode>
A.3.38
1020 2300 3780
Party Account Relationship Delete (PartyAcctRelDel)

<Desc>
Required Element Not Included Single or Source Account Invalid Delete would result in an invalid customer to account relationship
<StatusCode>
A.3.39
1020 1120
Party Account Relationship Inquiry (PartyAcctRelInq)

<Desc>
Required Element Not Included No record match selection criteria
<StatusCode>
A.3.40
1040 1050
Card Preferences Add (CardPrefAdd)

<Desc>
Request Declined Invalid Enum Value
<StatusCode>
Version 1.7
April 2005
A-23
<StatusCode>
1290 1760 2020 2030 2420 2510 2530 3380 3560 4080 4090 5000 5010
<Desc>
A duplicate Card Preference association already exists between the presented card and the selected business function. Authorization Failure Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Unrecognized Card Number Expired Card Card Acct Id Matches Multiple Accounts Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
5020 5030
A.3.41
1040 1050 1060 1080 1220 1290 2020 2030 2420 2510 2530 3380 3560 4080 4090 5000 5010
Card Preference Modify (CardPrefMod)

<Desc>
Request Declined Invalid Enum Value Cannot Modify Element No Changes Made Invalid Identifier A duplicate Card Preference association already exists between the presented card and the selected business function. Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Unrecognized Card Number Expired Card Card Account ID Matches Multiple Accounts Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.).
<StatusCode>
A-24
April 2005
Version 1.7
<StatusCode>
5020 5030
<Desc>
Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
A.3.42
1050 1100 1120 1140 1160 1220 2510 2520 2530 2540 3380
Card Preference Inquiry (CardPrefInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Identifier Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
<StatusCode>
A.3.43
1220 1300 1310
Card Preference Delete (CardPrefDel)

<Desc>
Invalid Identifier Object Not deleted; dependent objects exist Cascade Delete Failed
<StatusCode>
A.3.44
1 1050 1100 1120 1140 1160 1220 1320 2100 2110 2120 2150
Card Preference Audit (CardPrefAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Identifier Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range DateTime Too Far In Future
<StatusCode>
Version 1.7
April 2005
A-25
<StatusCode>
2200
<Desc>
History Not Available for Full Date Range
A.3.45
1 1100 1180 1200 1220
Card Preference Sync (CardPrefSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History Invalid Token Invalid Identifier
<StatusCode>
A.3.46
810
Card Preference Reversal (CardPrefRev)

<Desc>
Message cannot be reversed.
<StatusCode>
A.3.47
1040 1060 1080 1220 1320
Card Preference Status Modify (CardPrefStatusMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Invalid Identifier Object exists, but does not match <CustId>.
<StatusCode>
A.3.48
1040 1080 1260 1280 1320 2130 2140 2150 2180 2190 6350 6360
Posting Session Add (PostingSessionAdd)

<Desc>
Request Declined No Changes Made Unknown Object ID Object already exists. Object exists, but does not match <CustId>. Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work Weekend Or Holiday The teller or operator is not authorized to perform backdated transactions. The teller or operator is not authorized to perform future-dated transactions.
<StatusCode>
A-26
April 2005
Version 1.7
<StatusCode>
6370
<Desc>
The Posting Session location is invalid or the teller does not have security to perform transactions on behalf of the session location
A.3.49
1040 1060 1080 1260 1320 2130 2140 2150 2180 2190
Posting Session Modify (PostingSessionMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work Weekend Or Holiday
<StatusCode>
A.3.50
1120
Posting Session Inquiry (PostingSessionInq)

<Desc>
<StatusCode>
A.3.51
Posting Session Status Modify (PostingSessionStatusMod)

<Desc>
No Data Matches Selection Criteria The Posting Session is not available for the teller or operator to perform transactions against. The Posting Session totals do not meet the criteria of the server to allow the close final to proceed.
<StatusCode>
1120 6380 6390
A.3.52
1120
Session Totals Inquiry (SessionTotalsInq)

<Desc>
<StatusCode>
A.4
A.4.1
1520
Banking Service
Balance Inquiry (BalInq)
<Desc>
Invalid City
<StatusCode>
Version 1.7
April 2005
A-27
<StatusCode>
1540 1560 2210 2220 2300 2320 2350 2380 2400 2420 2440 2460 2480 2490 2510 2520 2530 2540 3380 3560
<Desc>
Invalid State or Province Invalid Postal Code Account Balance Information Not Available Extended Account Balance Information Not Available Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.2
810
Balance Reversal (BalRev)

<Desc>
<StatusCode>
A.4.3
1520 1540 1560 2300 2320 2350 2380 2400 2420 2440 2460
Account Inquiry (AcctInq)

<Desc>
Invalid City Invalid State or Province Invalid Postal Code Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> error
<StatusCode>
A-28
April 2005
Version 1.7
<StatusCode>
2480 2490 2510 2520 2530 2540 3380 3560
<Desc>
Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.4
810
Account Reversal (AcctRev)

<Desc>
<StatusCode>
A.4.5
1100 1120 1160 1240 1520 1540 1560 2100 2110 2120 2200 2300 2320 2350 2380 2400 2420 2440 2460 2480 2490 2510 2520
Deposit Account Statement Inquiry (DepAcctStmtInq)

<Desc>
Too Many Records Requested No Data Matches Se lection Criteria None of Selection Criteria Supported Detail Not Available Invalid City Invalid State or Province Invalid Postal Code Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range History Not Available for Full Date Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer
<StatusCode>
Version 1.7
April 2005
A-29
<StatusCode>
2530 2540 3380 3560 6210 6220
<Desc>
Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts Full Statement Requested, Mini Statement Could Be Provided No Statement Data Available
A.4.6
1100 1120 1160 1240 1520 1540 1560 2100 2110 2120 2200 2300 2320 2350 2380 2400 2420 2440 2460 2480 2520 2530 2540 3380
Credit Card Statement Inquiry (CCAcctStmtInq)

<Desc>
Too Many Records Requested No Data Matches Selection Criteria None of Selection Criteria Supported Detail Not Available Invalid City Invalid State or Province Invalid Postal Code Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range History Not Available for Full Date Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> Error Branch ID Missing Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
<StatusCode>
A.4.7
810
Credit Card Statement Reversal (CCAcctStmtRev)

<Desc>
<StatusCode>
A-30
April 2005
Version 1.7
A.4.8
1050 1120 1140 1160 1260 1320 2000 2010 2020 2030 2060 2100 2110 2120 2200 2300 2320 2350 2380 2400 2420 2440 2460 2480 2520 2530 2540 3380
Deposit Account Transaction Inquiry (DepAcctTrnInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId>. Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Amount Too Small Amount Too Large Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range History Not Available for Full Date Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> Error Branch ID Missing Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
<StatusCode>
A.4.9
Deposit Account Transaction Reversal (DepAcctTrnRev)

<Desc>
<StatusCode>
810
Version 1.7
April 2005
A-31
A.4.10
Credit Card Account Transaction Inquiry (CCAcctTrnInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId>. Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Amount Too Small Amount Too Large Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range History Not Available for Full Date Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> Error Branch ID Missing Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
<StatusCode>
1050 1120 1140 1160 1260 1320 2000 2010 2020 2030 2060 2100 2110 2120 2200 2300 2320 2350 2380 2400 2420 2440 2460 2480 2520 2530 2540 3380
A.4.11
Credit Card Account Transaction Reversal (CCAcctTrnRev)

<Desc>
<StatusCode>
810
A-32
April 2005
Version 1.7
A.4.12
1050 1100 1120 1140 1160 2000 2120 2130 2440
Interest Rate Inquiry (IntRateInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Data in Single or Low Amount Field Invalid DateTime Date Passed Invalid Single or Source Account Type
<StatusCode>
A.4.13
810
Interest Rate Rev (IntRateRev)

<Desc>
<StatusCode>
A.4.14
1050 1120 1140 1160 1520 1540 1560 2100 2300 2320 2400 2460 2480 2490 2510 2520 2530 2540 3380
Bank Account Taxation Inquiry (BankAcctTaxInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid City Invalid State or Province Invalid Postal Code Invalid DateTime - Single date or Low of Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Not Available Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
<StatusCode>
Version 1.7
April 2005
A-33
A.4.15
1050 1120 2020 2030 2080 2300 2320 2350 2380 2400 2420 2460 2480 2510 2520 2530 2540 2740 3380 3560
Foreign Exchange Rate Inquiry (ForExRateInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Amount Too Small Amount Too Large Final Amount Exceeds Limit Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Currency Code Expired Card Card Account ID Matches Multiple Accounts
<StatusCode>
A.4.16
810
Foreign Exchange Rate Reversal (ForExRateRev)

<Desc>
<StatusCode>
A.4.17
3810 3830 3840 3850 3860 3870
ForExDealAdd
<Desc>
<SPRefId> not recognized <CurAmt> does not equal <CurAmt> in prior <ForExRateInqRs> <CurCode> does not equal <CurCode> in prior< ForExRateInqRs> Combination of <CurAmt> and <CurCode> do not match the <SPRefId> from prior <ForExRateInqRs> Deal expired No <ForExRateDealType> provided.
<StatusCode>
A-34
April 2005
Version 1.7
A.4.18
1060 3820
ForExDealMod
<Desc>
Cannot Modify Element <ForExDealId> not recognized.
<StatusCode>
A.4.19
3820
ForExDealInq
<Desc>
<ForExDealId> not recognized.
<StatusCode>
A.4.20
3820
ForExDealCan
<Desc>
<StatusCode>
A.4.21
3820
ForExDealAud
<Desc>
<StatusCode>
A.4.22
3820
ForExDealSync
<Desc>
<StatusCode>
A.4.23
810 3820
ForExDealRev
<Desc>
Message cannot be reversed. <ForExDealId> not recognized.
<StatusCode>
A.4.24
1060 3820
ForExDealStatusMod
<Desc>
Cannot Modify Element <ForExDealId> not recognized.
<StatusCode>
A.4.25
3820
ForExDealStatusInq
<Desc>
<StatusCode>
Version 1.7
April 2005
A-35
A.4.26
3820
ForExDealAdvise
<Desc>
<StatusCode>
A.4.27
800 1520 1540 1560 2300 2320 2350 2380 2400 2420 2460 2480 2490 2510 2520 2530 2540 2600 2610 2620 2640 3380 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
Stop Check Add (StopChkAdd)

<Desc>
Object Already Committed Invalid City Invalid State or Province Invalid Postal Code Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Check Number Range Request Is Too Late - Check has been paid Check Number Not Found Stop Check In Process Expired Card Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.).
<StatusCode>
A-36
April 2005
Version 1.7
<StatusCode>
5020 5030
<Desc>
Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
A.4.28
800 1520 1540 1560 2300 2320 2350 2380 2400 2420 2460 2480 2490 2510 2520 2530 2540 2600 2620 3380
Stop Check Cancel (StopChkCan)

<Desc>
ObjectAlready Committed Invalid City Invalid State or Province Invalid Postal Code Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Check Number Range Check Number Not Found Expired Card
<StatusCode>
A.4.29
1120 1140 1160 1520 1540 1560 2300 2320 2350 2380
Stop Check Inquiry (StopChkInq)

<Desc>
No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid City Invalid State or Province Invalid Postal Code Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized
<StatusCode>
Version 1.7
April 2005
A-37
<StatusCode>
2400 2420 2460 2480 2490 2510 2520 2530 2540 2600 2620 3380
<Desc>
Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Check Number Range Check Number Not Found Expired Card
A.4.30
1 1120 1140 1160 1180 1520 1540 1560 2120 2300 2320 2350 2380 2400 2420 2460 2480 2490 2510 2520 2530 2540 2600 2620
Stop Check Audit (StopChkAud)

<Desc>
Client Up to Date No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid City Invalid State or Province Invalid Postal Code Invalid DateTime Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Check Number Range Check Number Not Found
<StatusCode>
A-38
April 2005
Version 1.7
<StatusCode>
3380
<Desc>
Expired Card
A.4.31
1 1100 1180 1200 2300 2320 2350 2380 2400 2420 2460 2480 2490 2510 2520 2530 2540 3380
Stop Check Synchronization (StopChkSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History Invalid Token Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
<StatusCode>
A.4.32
810
Stop Check Reversal (StopChkRev)

<Desc>
<StatusCode>
A.4.33
1040 2000 2020 2030 2130 2140 2150 2180
Funds Transfer Add (XferAdd)

<Desc>
Request Declined Invalid Data in Single or Low Amount Field Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work
<StatusCode>
Version 1.7
April 2005
A-39
<StatusCode>
2190 2300 2310 2320 2340 2350 2360 2370 2380 2390 2400 2410 2420 2430 2440 2450 2460 2470 2480 2740 2900 2940 3000 3020 3040 3560 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
<Desc>
Weekend Or Holiday Single or Source Account Invalid Destination Account Invalid Single Account or Source Account Not For Customer Destination Account Not For Customer Single or Source Account Closed Destination Account Closed Source And Destination Accounts Are Identical Single or Source Account Not Authorized Destination Account Not Authorized Single or Source Account Not Available Destination Account Not Available Single or Source Account Not Eligible For Transaction Destination Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Destination Account Type Single or Source Account <BankId> Error Destination Account <BankId> Error Branch ID Missing Invalid Currency Code Duplicate Payment/Transfer Exists Insufficient Funds Number of Transfers Exceeds Limit Daily Transfer Limit Exceeded Transfer Payment Greater Than Loan Balance Card Account ID Matches Multiple Accounts Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted.
5020
A-40
April 2005
Version 1.7
<StatusCode>
5030
<Desc>
Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
A.4.34
1040 1060 1080 1260 1320 2000 2020 2030 2130 2140 2150 2180 2190 2300 2310 2320 2340 2350 2360 2370 2380 2390 2400 2410 2420 2430 2440 2450 2460 2470 2740 2900 2940 3000
Funds Transfer Modify (XferMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid Data in Single or Low Amount Field Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work Weekend Or Holiday Single or Source Account Invalid Destination Account Invalid Single Account or Source Account Not For Customer Destination Account Not For Customer Single or Source Account Closed Destination Account Closed Source And Destination Accounts Are Identical Single or Source Account Not Authorized Destination Account Not Authorized Single or Source Account Not Available Destination Account Not Available Single or Source Account Not Eligible For Transaction Destination Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Destination Account Type Single or Source Account <BankId> Error Destination Account <BankId> Error Invalid Currency Code Duplicate Payment/Transfer Exists Insufficient Funds Number of Transfers Exceeds Limit
<StatusCode>
Version 1.7
April 2005
A-41
<StatusCode>
3020 3040 3560 3990
<Desc>
Daily Transfer Limit Exceeded Transfer Payment Greater Than Loan Balance Card Account ID Matches Multiple Accounts Read only data ignored
A.4.35
1040 1060 1080 1260 1320 2100 2300 2320 2350 2380 2400 2420 2460 2490
Funds Transfer Status Modify (XferStatusMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid DateTime in Single or Low of Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Bank Information Missing or Invalid
<StatusCode>
A.4.36
800 1260 1320 2130 2180
Funds Transfer Cancel (XferCan)

<Desc>
Object Already Committed Unknown Object ID Object exists, but does not match <CustId>. Date Passed Request Is Too Late For Todays Work
<StatusCode>
A.4.37
1 1050 1100 1120 1140
Funds Transfer Inquiry (XferInq)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported
<StatusCode>
A-42
April 2005
Version 1.7
<StatusCode>
1160 1180 1200 1260 1320 2000 2010 2060 2100 2120 2150 2300 2310 2440 2470 2510 2520 2530 2540 3380
<Desc>
None of Selection Criteria Supported Token Value Prior to Available History Invalid Token Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future Single or Source Account Invalid Destination Account Invalid Invalid Single or Source Account Type Destination Account <BankId>Error Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card
A.4.38
1 1050 1100 1120 1140 1160 1180 1200 1260 1320 2000 2010 2060 2100 2120 2150
Funds Transfer Audit (XferAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Token Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future
<StatusCode>
Version 1.7
April 2005
A-43
<StatusCode>
2300 2310 2440
<Desc>
Single or Source Account Invalid Destination Account Invalid Invalid Single or Source Account Type
A.4.39
1 1100 1180 1200 2510 2520 2530 2540 3380 3560
Funds Transfer Synchronization (XferSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History Invalid Token Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
<StatusCode>
A.4.40
810
Funds Transfer Reversal (XferRev)

<Desc>
<StatusCode>
A.4.41
1040 1060 2000 2020 2030 2080 2100 2110 2120 2130 2140 2150 2180 2190
Recurring Funds Transfer Model Add (RecXferAdd)

<Desc>
Request Declined Cannot Modify Element Invalid Data in Single or Low Amount Field Amount Too Small Amount Too Large Final Amount Exceeds Limit Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work Weekend Or Holiday
<StatusCode>
A-44
April 2005
Version 1.7
<StatusCode>
2300 2310 2320 2340 2350 2360 2370 2380 2390 2400 2410 2420 2430 2440 2450 2460 2470 2480 2720 2740 2780 2910 2920 2940 3000 3020 3040 3400 3560 3990
<Desc>
Single or Source Account Invalid Destination Account Invalid Single Account or Source Account Not For Customer Destination Account Not For Customer Single or Source Account Closed Destination Account Closed Source And Destination Accounts Are Identical Single or Source Account Not Authorized Destination Account Not Authorized Single or Source Account Not Available Destination Account Not Available Single or Source Account Not Eligible For Transaction Destination Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Destination Account Type Single or Source Account <BankId> Error Destination Account <BankId> Error Branch ID Missing Foreign Exchange not supported. Invalid Currency Code Unsupported Frequency Duplicate Recurring Model Invalid skip count Insufficient Funds Number of Transfers Exceeds Limit Daily Transfer Limit Exceeded Transfer Payment Greater Than Loan Balance Recurring Model Open-Ended Card Account ID Matches Multiple Accounts Read only data ignored
A.4.42
Recurring Funds Transfer Instance Add (RecXferInstAdd)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid Data in Single or Low Amount Field
<StatusCode>
1040 1060 1080 1260 1320 2000
Version 1.7
April 2005
A-45
<StatusCode>
2020 2030 2080 2100 2110 2120 2130 2140 2150 2180 2300 2310 2320 2340 2350 2360 2370 2380 2390 2400 2410 2420 2430 2440 2450 2460 2470 2720 2740 2780 2910 2920 2940 3000 3020 3040 3560
<Desc>
Amount Too Small Amount Too Large Final Amount Exceeds Limit Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work Single or Source Account Invalid Destination Account Invalid Single Account or Source Account Not For Customer Destination Account Not For Customer Single or Source Account Closed Destination Account Closed Source And Destination Accounts Are Identical Single or Source Account Not Authorized Destination Account Not Authorized Single or Source Account Not Available Destination Account Not Available Single or Source Account Not Eligible For Transaction Destination Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Destination Account Type Single or Source Account <BankId> Error Destination Account <BankId> Error Foreign Exchange not supported. Invalid Currency Code Unsupported Frequency Duplicate Recurring Model Invalid skip count Insufficient Funds Number of Transfers Exceeds Regulation D Limit Daily Transfer Limit Exceeded Transfer Payment Greater Than Loan Balance Card Account ID Matches Multiple Accounts
A-46
April 2005
Version 1.7
A.4.43
1040 1060 1080 1260 1320 2000 2020 2030 2080 2100 2110 2120 2130 2140 2150 2180 2300 2310 2320 2340 2350 2360 2370 2380 2390 2400 2410 2420 2430 2440 2450 2460 2470 2720 2740 2780 2910 2920 2940
Recurring Funds Transfer Model Modify (RecXferMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid Data in Single or Low Amount Field Amount Too Small Amount Too Large Final Amount Exceeds Limit Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range Date Passed DateTime Too Soon DateTime Too Far In Future Request Is Too Late For Todays Work Single or Source Account Invalid Destination Account Invalid Single Account or Source Account Not For Customer Destination Account Not For Customer Single or Source Account Closed Destination Account Closed Source And Destination Accounts Are Identical Single or Source Account Not Authorized Destination Account Not Authorized Single or Source Account Not Available Destination Account Not Available Single or Source Account Not Eligible For Transaction Destination Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Destination Account Type Single or Source Account <BankId> Error Destination Account <BankId> Error Foreign Exchange not supported. Invalid Currency Code Unsupported Frequency Duplicate Recurring Model Invalid skip count Insufficient Funds
<StatusCode>
Version 1.7
April 2005
A-47
<StatusCode>
3000 3020 3040 3560 3990
<Desc>
Number of Transfers Exceeds Regulation D Limit Daily Transfer Limit Exceeded Transfer Payment Greater Than Loan Balance Card Account ID Matches Multiple Accounts Read only data ignored
A.4.44
800 1040 1260 1320 2130 2180
Recurring Funds Transfer Model Cancel (RecXferCan)

<Desc>
Object Already Committed Request Declined Unknown Object ID Object exists, but does not match <CustId>. Date Passed Request Is Too Late For Todays Work
<StatusCode>
A.4.45
1050 1100 1120 1140 1160 1180 1200 1260 1320 2000 2010 2060 2100 2120 2150 2200 2310 2440 2480 2510 2520
Recurring Funds Transfer Model Inquiry (RecXferInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Token Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Destination Account Invalid Invalid Single or Source Account Type Branch ID Missing Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer
<StatusCode>
A-48
April 2005
Version 1.7
<StatusCode>
2530 2540 3380
<Desc>
Unrecognized Card Number Stolen Card Expired Card
A.4.46
1 1050 1100 1120 1140 1160 1180 1200 1260 1320 2000 2010 2060 2100 2120 2150 2200 2300 2310 2440 2480
Recurring Funds Transfer Model Audit (RecXferAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Token Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Destination Account Invalid Invalid Single or Source Account Type Branch ID Missing
<StatusCode>
A.4.47
Recurring Funds Transfer Synchronization (RecXferSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History Invalid Token Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number
<StatusCode>
1 1100 1180 1200 2510 2520 2530
Version 1.7
April 2005
A-49
<StatusCode>
2540 3380 3560
<Desc>
Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.48
810
Records Funds Transfer Model Reversal (RecXferRev)

<Desc>
<StatusCode>
A.4.49
Bank Account Transaction Image Inquiry (BankAcctTrnImgInq)

<Desc>
No Data Matches Selection Criteria Unknown Object ID Object exists, but does not match <CustId>. Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code Invalid Data in Single or Low Amount Field Invalid DateTime - Single date or Low of Range Single or Source Account Invalid Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Check Number Not Found Expired Card
<StatusCode>
1120 1260 1320 1500 1520 1540 1560 1580 2000 2100 2300 2350 2380 2400 2420 2460 2480 2490 2510 2520 2530 2540 2620 3380
A-50
April 2005
Version 1.7
A.4.50
Bank Account Transaction Image Inquiry Reversal (BankAcctTrnImgRev)

<Desc>
<StatusCode>
810
A.4.51
1500 1520 1540 1560 1580 2300 2320 2350 2400 2460 2480 2490 2510 2600 2680 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
Check Order (ChkOrdAdd)

<Desc>
Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Available Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Invalid Check Number Range Check Book Style Not Available Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
<StatusCode>
5020 5030
Version 1.7
April 2005
A-51
A.4.52
810
Check Order Reversal (ChkOrdRev)

<Desc>
<StatusCode>
A.4.53
3990
Recurring Check Order Add (RecChkOrdAdd)

<Desc>
Read only data ignored
<StatusCode>
A.4.54
1060 3990
Recurring Check Order Modify (RecChkOrdMod)

<Desc>
Cannot Modify Element Read only data ignored
<StatusCode>
A.4.55
1050 1500 1520 1540 1560 1580 2300 2320 2350 2380 2400 2420 2460 2480 2490 3990 4010 4020 4030 4040 4050 4060 4070 4080
Deposit Book Order (DepBkOrdAdd)

<Desc>
Invalid Enum Value Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Branch ID Missing Bank Information Missing or Invalid Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted.
<StatusCode>
A-52
April 2005
Version 1.7
<StatusCode>
4090 5000 5010
<Desc>
Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
5020 5030
A.4.56
810
Deposit Book Order Reversal (DepBkOrdRev)

<Desc>
<StatusCode>
A.4.57
1050 2020 2030 2420 2510 2740 2940 3050 3052 3060 3070 3080 3090 3380 3560 3990 4010 4020 4030 4040 4050 4060 4070 4080
Debit Authorization Add (DebitAuthAdd)

<Desc>
Invalid Enum Value Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Usage Limit Exceeded Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted.
<StatusCode>
Version 1.7
April 2005
A-53
<StatusCode>
4090 5000 5010
<Desc>
Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted. Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved
5020 5030 6330
A.4.58
800 1050 1060 1220 2020 2030 2510 2740 2940 3050 3052 3070 3080 3090 3380 3560 3990 6330
Debit Authorization Modify (DebitAuthMod)

<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Read only data ignored Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved
<StatusCode>
A.4.59
800 1050 1220 2510
Debit Authorization Cancel (DebitAuthCan)

<Desc>
Object Already Committed Invalid Enum Value Invalid Identifier Invalid Card Magnetic Strip Data
<StatusCode>
A-54
April 2005
Version 1.7
A.4.60
1050 1100 1120 1140 1160 1180 1220 1260 1320 2000 2010 2060 2100 2120 2150 2200 2510 2520 2530 2540 3380 3560
Debit Authorization Inquiry (DebitAuthInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
<StatusCode>
A.4.61
1 1050 1100 1120 1140 1160 1220 1260 1320 2100 2120 2150 2200
Debit Authorization Audit (DebitAuthAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
<StatusCode>
Version 1.7
April 2005
A-55
A.4.62
1 1100 1180 1200 2510 2520 2530 2540 3380 3560
Debit Authorization Sync (DebitAuthSync)

<Desc>
<StatusCode>
A.4.63
Debit Authorization Status Modify (DebitAuthStatusMod)

<Desc>
<StatusCode>
1040 1060 1080 1260 1320 2100 2300 2320 2350 2380 2400 2420 2460 2490
A.4.64
810
Debit Authorization Reversal (DebitAuthRev)

<Desc>
<StatusCode>
A-56
April 2005
Version 1.7
A.4.65
1050 1220 2020 2030 2420 2510 2740 2940 3050 3052 3060 3070 3080 3090 3380 3560 3980 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
Debit Add (DebitAdd)

<Desc>
Invalid Enum Value Invalid Identifier Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Usage Limit Exceeded Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Cash back exceeds total amount deposited. Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted. Prompt Customer to save current transaction information as a Card Preference for this transaction type Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved
<StatusCode>
5020 5030 5040 6330
Version 1.7
April 2005
A-57
A.4.66
800 1050 1060 1220 2020 2030 2510 2740 2940 3050 3052 3070 3080 3090 3380 3560 3980 3990 5040 6330
Debit Modify (DebitMod)

<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Cash back exceeds total amount deposited. Read only data ignored Prompt Customer to save current transaction information as a Card Preference for this transaction type Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved
<StatusCode>
A.4.67
800 1050 1220 2510
Debit Cancel (DebitCan)

<Desc>
<StatusCode>
A.4.68
1050 1100 1120 1140 1160 1180
Debit Inquiry (DebitInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History
<StatusCode>
A-58
April 2005
Version 1.7
<StatusCode>
1220 1260 1320 2000 2010 2060 2100 2120 2150 2200 2510 2520 2530 2540 3380 3560
<Desc>
Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.69
1 1050 1100 1120 1140 1160 1220 1260 1320 2100 2120 2150 2200
Debit Audit (DebitAud)

<Desc>
<StatusCode>
A.4.70
1 1100 1180
Debit Sync (DebitSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History
<StatusCode>
Version 1.7
April 2005
A-59
<StatusCode>
1200 2510 2520 2530 2540 3380 3560
<Desc>
Invalid Token Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.71
1040 1060 1080 1260 1320 2100 2300 2320 2350 2380 2400 2420 2460 2490 5040
Debit Status Modify (DebitStatusMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid DateTime in Single or Low of Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Bank Information Missing or Invalid Prompt Customer to save current transaction information as a Card Preference for this transaction type
<StatusCode>
A.4.72
810
Debit Reversal (DebitRev)

<Desc>
<StatusCode>
A.4.73
1050 2020 2030 2420 2510
Credit Authorization Add (CreditAuthAdd)

<Desc>
Invalid Enum Value Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data
<StatusCode>
A-60
April 2005
Version 1.7
<StatusCode>
2740 2940 3050 3052 3060 3070 3080 3090 3380 3560 3980 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
<Desc>
Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Usage Limit Exceeded Changed Fee Advice Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Cash Back Exceeds Total Amount Deposited Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted. Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved A Portion of the Requested Deposit Amount was Held by the Authorizer
5020 5030 6330 6340
A.4.74
800 1050 1060 1220 2020 2030 2510
Credit Authorization Modify (CreditAuthMod)

<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data
<StatusCode>
Version 1.7
April 2005
A-61
<StatusCode>
2740 2940 3050 3052 3070 3080 3090 3380 3560 3980 3990 6330 6340
<Desc>
Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Changed Fee Advice Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Cash Back Exceeds Total Amount Deposited Read only data ignored Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved A Portion of the Requested Deposit Amount was Held by the Authorizer
A.4.75
800 1050 1220 2510
Credit Authorization Cancel (CreditAuthCan)

<Desc>
<StatusCode>
A.4.76
1050 1100 1120 1140 1160 1180 1220 1260 1320 2000 2010 2060 2100 2120 2150
Credit Authorization Inquiry (CreditAuthInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future
<StatusCode>
A-62
April 2005
Version 1.7
<StatusCode>
2200 2510 2520 2530 2540 3380 3560
<Desc>
History Not Available for Full Date Range Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.77
1 1050 1100 1120 1140 1160 1220 1260 1320 2100 2120 2150 2200
Credit Authorization Audit (CreditAuthAud)

<Desc>
<StatusCode>
A.4.78
1 1100 1180 1200 2510 2520 2530 2540 3380 3560
Credit Authorization Sync (CreditAuthSync)

<Desc>
<StatusCode>
Version 1.7
April 2005
A-63
A.4.79
Credit Authorization Status Modify (CreditAuthStatusMod)

<Desc>
<StatusCode>
1040 1060 1080 1260 1320 2100 2300 2320 2350 2380 2400 2420 2460 2490
A.4.80
810
Credit Authorization Reversal (CreditAuthRev)

<Desc>
<StatusCode>
A.4.81
1050 1220 2020 2030 2420 2510 2740 2940 3050 3052 3060 3070 3090 3380 3560
Credit Add (CreditAdd)

<Desc>
Invalid Enum Value Invalid Identifier Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Usage Limit Exceeded Changed Fee Advice No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts
<StatusCode>
A-64
April 2005
Version 1.7
<StatusCode>
3650 3980 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
<Desc>
Cash deposit limit exceeded. Cash Back Exceeds Total Amount Deposited Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted. Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved A Portion of the Requested Deposit Amount was Held by the Authorizer
5020 5030 6330 6340
A.4.82
800 1050 1060 1220 2020 2030 2510 2740 2940 3050 3052 3070 3080 3090 3380 3560
Credit Modify (CreditMod)

<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Withdrawal or Cash Back Amount Reduced to Maximum Allowed Changed Fee Advice Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts
<StatusCode>
Version 1.7
April 2005
A-65
<StatusCode>
3650 3980 3990 6330 6340
<Desc>
Cash deposit limit exceeded. Cash Back Exceeds Total Amount Deposited Read only data ignored Cash Back Amount Not Approved, But the Original Credit or Debit Amount was Approved A Portion of the Requested Deposit Amount was Held by the Authorizer
A.4.83
800 1050 1220 2510
Credit Cancel (CreditCan)

<Desc>
<StatusCode>
A.4.84
1050 1100 1120 1140 1160 1180 1220 1260 1320 2000 2010 2060 2100 2120 2150 2200 2510 2520 2530 2540 3380 3560
Credit Inquiry (CreditInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
<StatusCode>
A-66
April 2005
Version 1.7
A.4.85
1 1050 1100 1120 1140 1160 1220 1260 1320 2100 2120 2150 2200
Credit Audit (CreditAud)

<Desc>
<StatusCode>
A.4.86
1 1100 1180 1200 2510 2520 2530 2540 3380 3560
Credit Sync (CreditSync)

<Desc>
<StatusCode>
A.4.87
1040 1060 1080 1260 1320 2100 2300 2320
Credit Status Modify (CreditStatusMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid DateTime in Single or Low of Range Single or Source Account Invalid Single Account or Source Account Not For Customer
<StatusCode>
Version 1.7
April 2005
A-67
<StatusCode>
2350 2380 2400 2420 2460 2490
<Desc>
Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Bank Information Missing or Invalid
A.4.88
810
Credit Reversal (CreditRev)

<Desc>
<StatusCode>
A.4.89
Bank Account Statement Image Inquiry (BankAcctStmtImgInq)

<Desc>
Too Many Records Requested Records Control Active No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Detail Not Available Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range History Not Available for Full Date Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Single or Source Account <BankId> Error Branch ID Missing
<StatusCode>
1100 1110 1120 1140 1160 1240 1500 1520 1540 1560 1580 2100 2110 2120 2200 2300 2320 2350 2380 2400 2420 2440 2460 2480
A-68
April 2005
Version 1.7
<StatusCode>
2490 2510 2520 2530 2540 3380 3560 6210 6220
<Desc>
Bank Information Missing or Invalid Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts Full Statement Requested, Mini Statement Could Be Provided No Statement Data Available
A.4.90
Bank Account Statement Image Reversal (BankAcctStmtImgRev)

<Desc>
<StatusCode>
810
A.4.91
810
Payment Enclosed Reversal (PmtEnclRev)

<Desc>
<StatusCode>
A.4.92
1050 1280 1480 1760 2300 2440 2900 3580 3600
Check Issue Add (ChkIssueAdd)

<Desc>
Invalid Enum Value Object already exists Edit Mask Error Authorization Failure Single or Source Account Invalid Invalid Single or Source Account Type Duplicate Payment/Transfer Exists Authorization is rejected Authorization held over
<StatusCode>
A.4.93
800 1050 1060
Check Issue Modify (ChkIssueMod)

<Desc>
Object Object Already Committed Invalid Enum Value Cannot Modify Element
<StatusCode>
Version 1.7
April 2005
A-69
<StatusCode>
1080 1260 1320 1760 2300 2440 3580 3600
<Desc>
No changes made Unknown Object ID Object exists, but does not match <CustId> Authorization Failure Single or Source Account Invalid Invalid Single or Source Account Type Authorization is rejected Authorization held over
A.4.94
1050 1060 1080 1260 1320 1760 3580 3600
Check Issue Status Modify (ChkIssueStatusMod)

<Desc>
Invalid Enum Value Cannot Modify Element No changes made Unknown Object ID Object Exists But Does Not Match <CustId> Authorization Failure Authorization is rejected Authorization held over
<StatusCode>
A.4.95
800 1260 1320 1760 3580 3600
Check Issue Delete (ChkIssueDel)

<Desc>
Object Object Already CCommitted Unknown Object ID Object exists, but does not match <CustId> Authorization Failure Authorization is rejected Authorization held over
<StatusCode>
A.4.96
1050 1100 1120 1140 1160 1260
Check Issue Inquiry (ChkIssueInq)

<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID
<StatusCode>
A-70
April 2005
Version 1.7
<StatusCode>
1320 2000 2010 2060 2100 2110 2120 2150 2200 2300 2440
<Desc>
Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type
A.4.97
1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200 2300 2440
Check Issue Status Inquiry (ChkIssueStatusInq)

<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type
<StatusCode>
A.4.98
1 1050 1100 1120 1140 1160 1260
Check Issue Audit (ChkIssueAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID
<StatusCode>
Version 1.7
April 2005
A-71
<StatusCode>
1320 2100 2110 2120 2150 2200 2300 2440
<Desc>
Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type
A.4.99
1 1100 1180 1200 2300 2440
Check Issue Synchronization (ChkIssueSync)

<Desc>
Client Up to Date Too Many Records Requested Token Value Prior to Available History Invalid Token Single or Source Account Invalid Invalid Single or Source Account Type
<StatusCode>
A.4.100 Bank Service Checksum Add (BankSvcChkSumAdd)

<StatusCode>
1280 1480 2020 2030 2130 2160 2180 2190 3140 3580 3600
<Desc>
Object already exists Edit Mask Error Amount Too Small Amount Too Large Date Passed Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Invalid Customer Payee ID <CustPayeeId> Authorization is rejected Authorization held over
A.4.101 Bank Service Checksum Modify (BankSvcChkSumMod)

<StatusCode>
800 1060 1080
<Desc>
Object Already Committed Cannot Modify Element No changes made
A-72
April 2005
Version 1.7
<StatusCode>
1260 1320 2020 2030 2130 2160 2180 2190 3140 3580 3600
<Desc>
Unknown Object ID Object exists, but does not match <CustId> Amount Too Small Amount Too Large Date Passed Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Invalid Customer Payee ID<CustPayeeId> Authorization is rejected Authorization held over
A.4.102 Bank Service Checksum Status Modify (BankSvcChkSumStatusMod)

<StatusCode>
1050 1060 1080 1260 1320 1760 3580 3600
<Desc>
A.4.103 Bank Service Checksum Delete (BankSvcChkSumDel)

<StatusCode>
800 1260 1320
<Desc>
Object Object Already Committed Unknown Object ID Object exists, but does not match <CustId>
A.4.104 Bank Service Checksum Inquiry (BankSvcChkSumInq)

<StatusCode>
1050 1100 1120 1140 1160
<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported
Version 1.7
April 2005
A-73
<StatusCode>
1260 1320
<Desc>
Unknown Object ID Object exists, but does not match <CustId>
A.4.105 Bank Service Checksum Audit (BankSvcChkSumAud)

<StatusCode>
1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
A.4.106 Bank Service Checksum Synchronization (BankSvcChkSumSync)

<StatusCode>
1100 1180 1200
<Desc>
Too Many Records Requested Token Value Prior to Available History Invalid Token
A.4.107 Check Accept Add (ChkAcceptAdd)

<StatusCode>
1050 1220 2020 2030 2420 2510 2740 2940 3050
<Desc>
Invalid Enum Value Invalid Identifier Amount Too Small Amount Too Large Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed
A-74
April 2005
Version 1.7
<StatusCode>
3060 3070 3080 3090 3380 3560 3960 3970
<Desc>
Usage Limit Exceeded Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Stop Payment Match Check Already Accepted
A.4.108 Check Accept Modify (ChkAcceptMod)

<StatusCode>
800 1050 1060 1220 2020 2030 2510 2740 2940 3050 3070 3080 3090 3380 3560 3960 3970
<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data Invalid Currency Code Insufficient Funds Authorized Amount Changed Changed Fee Withdrawal Limit Exceeded No Fee Override Authorization Expired Card Card Account ID Matches Multiple Accounts Stop Payment Match Check Already Accepted
A.4.109 Check Accept Inquiry (ChkAcceptInq)

<StatusCode>
1050 1100 1120 1140 1160
<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported
Version 1.7
April 2005
A-75
<StatusCode>
1180 1220 1260 1320 2000 2010 2060 2100 2120 2150 2200 2510 2520 2530 2540 3380 3560
<Desc>
Token Value Prior to Available History Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.110 Check Accept Cancel (ChkAcceptCan)

<StatusCode>
800 1050 1220 2510
<Desc>
A.4.111 Check Accept Audit (ChkAcceptAud)

<StatusCode>
1 1050 1100 1120 1140 1160 1220 1260 1320
<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Identifier Unknown Object ID Object exists, but does not match <CustId>
A-76
April 2005
Version 1.7
<StatusCode>
2100 2120 2150 2200
<Desc>
Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
A.4.112 Check Accept Syncronization (ChkAcceptSync)

<StatusCode>
1 1100 1180 1200 2510 2520 2530 2540 3380 3560
<Desc>
A.4.113 Check Accept Reversal (ChkAcceptRev)

<StatusCode>
810
<Desc>
Message cannot be reversed.
A.4.114 Check Accept Status Modify (ChkAcceptStatusMod)

<StatusCode>
1040 1060 1080 1260 1320 2100 2300 2320 2350 2380
<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid DateTime in Single or Low of Range Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Closed Single or Source Account Not Authorized
Version 1.7
April 2005
A-77
<StatusCode>
2400 2420 2460 2490
<Desc>
Single or Source Account Not Available Single or Source Account Not Eligible For Transaction Single or Source Account <BankId> Error Bank Information Missing or Invalid
A.4.115 Media Account Adjustment Add (MediaAcctAdjAdd)

<StatusCode>
3990 6320
<Desc>
Read only data ignored Invalid Cassette Id
A.4.116 Media Account Adjustment Modify (MediaAcctAdjMod)

<StatusCode>
1060 3990
<Desc>
Cannot Modify Element Read only data ignored
A.4.117 Media Account Adjust Inquiry (MediaAcctAdjInq)

<StatusCode>
6320
<Desc>
Invalid Cassette Id
A.4.118 Media Account Inventory Inquiry (MediaAcctInventoryInq)

<StatusCode>
6320
<Desc>
Invalid Cassette Id
A.4.119 Passbook Add (PassbkAdd)

<StatusCode>
1050 1220 1280 2300 2320 2420 2440 2510 2520 2530
<Desc>
Invalid Enum Value Invalid Identifier Object already exists. Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number
A-78
April 2005
Version 1.7
<StatusCode>
2540 3380 3560 3990
<Desc>
Stolen Card Expired Card Card Account ID Matches Multiple Accounts Read only data ignored
A.4.120 Passbook Mod (PassbkMod)

<StatusCode>
800 1050 1060 1080 1220 1260 1280 1320 2420 2510 3380 3560 3990
<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element No Changes Made Invalid Identifier Unknown Object ID Object already exists. Object exists, but does not match <CustId> Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Expired Card Card Account ID Matches Multiple Accounts Read only data ignored
A.4.121 Passbook Inquiry (PassbkInq)

<StatusCode>
1100 1120 1140 1160 1220 1240 1260 1320 2300 2320 2420 2440 2510 2520 2530
<Desc>
Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Identifier Detail Not Available Unknown Object ID Object exists, but does not match <CustId> Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number
Version 1.7
April 2005
A-79
<StatusCode>
2540 3380 3560
<Desc>
Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.4.122 Passbook Delete (PassbkDel)

<StatusCode>
1260 1310 1320 1760 3580
<Desc>
Unknown Object ID Cascade Delete Failed Object exists, but does not match <CustId> Authorization Failure Authorization is rejected
A.4.123 Passbook Audit (PassbkAud)

<StatusCode>
1 1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
A.4.124 Passbook Sync (PassbkSync)

<StatusCode>
1 1100 1180 1200
<Desc>
A-80
April 2005
Version 1.7
A.4.125 Passbook Reversal (PassbkRev)

<StatusCode>
810
<Desc>
A.4.126 Passbook Status Modify (PassbkStatusMod)

<StatusCode>
1060 1080 1260 1320
<Desc>
A.4.127 Passbook Status Inquiry (PassbkStatusInq)

<StatusCode>
1050 1100 1120 1140 1160 1260 1320
<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId>
A.4.128 Passbook Item Add (PassbkItemAdd)

<StatusCode>
1050 1220 1280 2300 2320 2420 2440 2510 2520 2530 2540 3380 3560 3990
<Desc>
Invalid Enum Value Invalid Identifier Object already exists. Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts Read only data ignored
Version 1.7
April 2005
A-81
A.4.129 Passbook Item Modify (PassbkItemMod)

<StatusCode>
800 1050 1060 1080 1220 1260 1280 1320 2420 2510 3380 3560 3990
<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element No Changes Made Invalid Identifier Unknown Object ID Object already exists. Object exists, but does not match <CustId> Single or Source Account Not Eligible For Transaction Invalid Card Magnetic Strip Data Expired Card Card Account ID Matches Multiple Accounts Read only data ignored
A.4.130 Passbook Item Inquiry (PassbkItemInq)

<StatusCode>
1100 1120 1140 1160 1220 1240 1260 1320 2300 2320 2420 2440 2510 2520 2530 2540 3380 3560
<Desc>
Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Identifier Detail Not Available Unknown Object ID Object exists, but does not match <CustId> Single or Source Account Invalid Single Account or Source Account Not For Customer Single or Source Account Not Eligible For Transaction Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A-82
April 2005
Version 1.7
A.4.131 Passbook Item Delete (PassbkItemDel)

<StatusCode>
1260 1310 1320 1760 3580
<Desc>
Unknown Object ID Cascade Delete Failed Object exists, but does not match <CustId> Authorization Failure Authorization is rejected
A.4.132 Passbook Item Audit (PassbkItemAud)

<StatusCode>
1 1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
<Desc>
A.4.133 Passbook Item Sync (PassbkItemSync)

<StatusCode>
1 1100 1180 1200
<Desc>
A.4.134 Passbook Item Reversal (PassbkItemRev)

<StatusCode>
810
<Desc>
Version 1.7
April 2005
A-83
A.4.135 Passbook Item Status Modify (PassbkItemStatusMod)

<StatusCode>
1060 1080 1260 1320
<Desc>
A.4.136 Passbook Item Status Inquiry (PassbkItemStatusInq)

<StatusCode>
1050 1100 1120 1140 1160 1260 1320
<Desc>
A-84
April 2005
Version 1.7
A.5
A.5.1
1050 1100 1120 1140 1160 3120 3260
Pay Service
Standard Payee Inquiry (StdPayeeInq)
<Desc>
Invalid Enum Value Too Many Records Requested No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid <StdPayeeId> Payee Type Not Supported
<StatusCode>
A.5.2
810
Standard Payee Reversal (StdPayeeRev)

<Desc>
<StatusCode>
A.5.3
1280 1480 1500 1520 1540 1560 1580 3120 3200 3240 3260
Customer Payee Add (CustPayeeAdd)

<Desc>
Object already exists Edit Mask Error Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Invalid <StdPayeeId> Payee List Full Invalid Customer Account with Payee Payee Type Not Supported
<StatusCode>
A.5.4
1080 1060 1260 1320 1480
Customer Payee Modify (CustPayeeMod)

<Desc>
No Changes Made Cannot Modify Element Unknown Object ID Object exists, but does not match <CustId> Edit Mask Error
<StatusCode>
Version 1.7
April 2005
A-85
<StatusCode>
1500 1520 1500 1520 1540 1560 1580 3140 3180 3240 3260
<Desc>
Invalid Address Invalid City Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Invalid Customer Payee ID <CustPayeeId> Invalid Payee Name Invalid Customer Account with Payee Payee Type Not Supported
A.5.5
1260 1300 1310 1320 3140
Customer Payee Delete (CustPayeeDel)

<Desc>
Unknown Object ID Object not deleted; dependent objects exist Cascade Delete Failed Object exists, but does not match <CustId> Invalid Customer PayeeID<CustPayeeId>
<StatusCode>
A.5.6
1050 1100 1120 1140 1160 3140 3260
Customer Payee Inquiry (CustPayeeInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Records Match Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Invalid Customer Payee ID<CustPayeeId> Payee Type Not Supported
<StatusCode>
A.5.7
1 1050 1100 1140 1160
Customer Payee Audit (CustPayeeAud)

<Desc>
Client Up to Date Invalid Enum Value Too Many Records Requested Some Selection Criteria Not Supported None of Selection Criteria Supported
<StatusCode>
A-86
April 2005
Version 1.7
<StatusCode>
2100 2110 2120 2150 2200 3140 3260
<Desc>
Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range DateTime Too Far in Future History Not Available for Full Date Range Invalid Customer Payee ID <CustPayeeId> Payee Type Not Supported
A.5.8
1 1100 1180 1200
Customer Payee Synchronization (CustPayeeSync)

<Desc>
<StatusCode>
A.5.9
1280 1480 1500 1520 1540 1560 1580 2020 2030 2130 2140 2150 2160 2180 2190 2310 2900 3100 3120 3140 3180
Payment Add (PmtAdd)

<Desc>
Object already exists Edit Mask Error Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far in Future Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Destination Account Invalid (for Transfer Payee Payments) Duplicate Payment/Transfer Exists Invalid <BillerId> Invalid <StdPayeeId> Invalid Customer Payee ID <CustPayeeId> Invalid Payee Name
<StatusCode>
Version 1.7
April 2005
A-87
<StatusCode>
3200 3240 3260 3320 3380 3580 3600
<Desc>
Payee List Full Invalid Customer Account with Payee Payee Type Not Supported Total Payment Amounts Scheduled for Today exceeded daily limit Expired Card Authorization is rejected Authorization held over
A.5.10
800 1060 1080 1260 1320 1500 1520 1540 1560 1580 2020 2030 2130 2140 2150 2160 2180 2190 2310 3100 3120 3140 3180 3200 3240 3260 3320 3380 3580
Payment Modify (PmtMod)

<Desc>
Object Object Already Committed Cannot Modify Element (some bill pay systems dont allow mod of Payee Name) No changes made Unknown Object ID Object exists, but does not match <CustId> Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far in Future Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Destination Account Invalid (for Transfer Payee Payments) Invalid <BillerId><BillerId> Invalid <StdPayeeId><StdPayeeId> Invalid Customer Payee ID<CustPayeeId> Invalid Payee Name Payee List Full Invalid Customer Account with Payee Payee Type Not Supported Total Payment Amounts Scheduled for Today exceeded daily limit Expired Card Authorization is rejected
<StatusCode>
A-88
April 2005
Version 1.7
<StatusCode>
3600
<Desc>
Authorization held over
A.5.11
1050 1060 1080 1260 1320 1760 2100 2150 3580 3600
Payment Status Modify (PmtStatusMod)

<Desc>
Invalid Enum Value Cannot Modify Element No changes made Unknown Object ID Object Exists But Does Not Match <CustId> Authorization Failure Invalid DateTime Single Date or Low of Range DateTime Too Far in Future Authorization is rejected Authorization held over
<StatusCode>
A.5.12
800 1260 1320
Payment Cancel (PmtCan)

<Desc>
Object Object Already CCommitted Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.5.13
1050 1100 1120 1140 1160 1260 1320 2000 2010 2060 2100 2110 2120 2150
Payment Inquiry (PmtInq)

<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future
<StatusCode>
Version 1.7
April 2005
A-89
<StatusCode>
2200 2300 2440 2510 2520 2530 2540 3140 3380
<Desc>
History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Customer Payee ID <CustPayeeId> Expired Card
A.5.14
Payment Enclosed Add (PmtEnclAdd)

<Desc>
Invalid Enum Value Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data Invalid Currency Code Usage Limit Exceeded Changed Fee Advice No Fee Override Authorization Expired Card Read only data ignored Customer Postal Code does not match expected value. Customer Address does not match expected value. Customer Address and Postal Code do not match expected values. Customer Address could not be validated, retry. Customer Address verification is not supported by server. Customer Address verification cannot be performed because customer data is not available. Customer Address and Postal Code match expected values. Card Verification Data not present or incorrect, card accepted. Card Verification Data not present or incorrect, card not accepted. Card Verification could not be completed because the track data is incomplete, card accepted. Card Verification could not be completed because the track data is incomplete, accept card with manual verification or identification. This code can only be returned if it originates at an acceptor operated device (i.e., POS, Teller, etc.). Card Verification could not be completed because the track data is incomplete, card not accepted. Card Verification could not be performed because the card is not encoded with verification data. Card accepted.
<StatusCode>
1050 1220 2020 2030 2510 2740 3060 3070 3090 3380 3990 4010 4020 4030 4040 4050 4060 4070 4080 4090 5000 5010
5020 5030
A-90
April 2005
Version 1.7
A.5.15
800 1050 1060 1220 2020 2030 2510 2740 3070 3090 3380 3990
Payment Enclosed Modify (PmtEnclMod)

<Desc>
Object Already Committed Invalid Enum Value Cannot Modify Element Invalid Identifier Amount Too Small Amount Too Large Invalid Card Magnetic Strip Data Invalid Currency Code Changed Fee Advice No Fee Override Authorization Expired Card Read only data ignored
<StatusCode>
A.5.16
800 1050 1220 2510
Payment Enclosed Cancel (PmtEnclCan)

<Desc>
<StatusCode>
A.5.17
1050 1100 1120 1140 1160 1180 1220 1260 1320 2000 2010 2060 2100 2120 2150 2200
Payment Enclosed Inquiry (PmtEnclInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Identifier Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
<StatusCode>
Version 1.7
April 2005
A-91
<StatusCode>
2510 2520 2530 2540 3380 3560
<Desc>
Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Expired Card Card Account ID Matches Multiple Accounts
A.5.18
1 1050 1100 1120 1140 1160 1220 1260 1320 2100 2120 2150 2200
Payment Enclosed Audit (PmtEnclAud)

<Desc>
<StatusCode>
A.5.19
1040 1060 1080 1260 1320 2100
Payment Enclosed Status Modify (PmtEnclStatusMod)

<Desc>
Request Declined Cannot Modify Element No Changes Made Unknown Object ID Object exists, but does not match <CustId>. Invalid DateTime in Single or Low of Range
<StatusCode>
A.5.20
1050 1100
Payment Status Inquiry (PmtStatusInq)

<Desc>
Invalid Enum Value Too Many Records Requested
<StatusCode>
A-92
April 2005
Version 1.7
<StatusCode>
1120 1140 1160 1260 1320 2100 2110 2120 2150 2200 2300 2440 2510 2520 2530 2540 3140 3380
<Desc>
Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Customer Payee ID <CustPayeeId> Expired Card
A.5.21
1 1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
Payment Audit (PmtAud)

<Desc>
<StatusCode>
A.5.22
1 1100
Payment Synchronization (PmtSync)

<Desc>
Client Up to Date Too Many Records Requested
<StatusCode>
Version 1.7
April 2005
A-93
<StatusCode>
1180 1200
<Desc>
Token Value Prior to Available History Invalid Token
A.5.23
810
Payment Reversal (PmtRev)

<Desc>
<StatusCode>
A.5.24
1280 2000 2020 2030 2180 2190 3320 3380 3610 3620 3630 3640
Payment Authorization Add (PmtAuthAdd)

<Desc>
Object already exists Invalid Data in Single or Low Amount Field Amount Too Small Amount Too Large Request is Too Late for Todays Work Weekend or Holiday Total Payment Amounts Scheduled for Today exceeded daily limit Expired Card Authorization is declined for insufficient funds. Authorization is declined for inactive account. Authorization is declined for closed account. Authorization is declined for other reason.
<StatusCode>
A.5.25
800 1060 1080 1260 1320 2000 2020 2030 2180 2190 3320 3380 3610
Payment Authorization Modify (PmtAuthMod)

<Desc>
Transaction already committed Cannot Modify Element No changes made Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Amount Too Small Amount Too Large Request is Too Late for Todays Work Weekend or Holiday Total Payment Amounts Scheduled for Today exceeded daily limit Expired Card Authorization is declined for insufficient funds.
<StatusCode>
A-94
April 2005
Version 1.7
<StatusCode>
3620 3630 3640
<Desc>
Authorization is declined for inactive account. Authorization is declined for closed account. Authorization is declined for other reason.
A.5.26
800 1260 1320
Payment Authorization Cancel (PmtAuthCan)

<Desc>
Transaction already committed Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.5.27
1050 1100 1120 1140 1160 1260 1320 2000 2100 2110 2120 2200
Payment Authorization Inquiry (PmtAuthInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Data Matches Search Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range History Not Available for Full Date Range
<StatusCode>
A.5.28
1 1050 1100 1120 1140 1160 1260 1320 2100 2110
Payment Authorization Audit (PmtAuthAud)

<Desc>
Client Up to Date Invalid Enum Value Too Many Records Requested No Data Matches Search Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range
<StatusCode>
Version 1.7
April 2005
A-95
<StatusCode>
2120 2200
<Desc>
Invalid DateTime Range History Not Available for Full Date Range
A.5.29
Payment Authorization Synchronization (PmtAuthSync)

<Desc>
<StatusCode>
1 1100 1180 1200
A.5.30
810
Payment Authorization Reversal (PmtAuthRev)

<Desc>
<StatusCode>
A.5.31
1280 1500 1520 1540 1560 1580 2000 2100 2150 3100 3180 3240
Remittance Add (RemitAdd)

<Desc>
Object already exists Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Invalid Data in Single or Low Amount Field Invalid DateTime Single date or Low of Range DateTime Too Far in Future Invalid <BillerId> Invalid Payee Name Invalid Customer Account with Payee
<StatusCode>
A.5.32
800 1060 1080 1260
Remittance Modify (RemitMod)

<Desc>
Object Already Committed Cannot Modify Element No changes made Unknown Object ID
<StatusCode>
A-96
April 2005
Version 1.7
<StatusCode>
1320 1500 1520 1540 1560 1580 2000 2100 2150 3100 3180 3240
<Desc>
Object exists, but does not match <CustId> Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Invalid Data in Single or Low Amount Field Invalid DateTime Single date or Low of Range DateTime Too Far in Future Invalid <BillerId> Invalid Payee Name Invalid Customer Account with Payee
A.5.33
1050 1060 1080 1260 1320 2100 2150
Remittance Status Modify (RemitStatusMod)

<Desc>
Invalid Enum Value Cannot Modify Element No Changes made Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime Single Date or Low of Range DateTime Too Far in Future
<StatusCode>
A.5.34
800 1260 1320
Remittance Delete (RemitDel)

<Desc>
Object Already Committed Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.5.35
1050 1120 1140 1160 1260 1320
Remittance Inquiry (RemitInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
Version 1.7
April 2005
A-97
<StatusCode>
2000 2100 2110 2120 2150 2200
<Desc>
Invalid Data in Single or Low Amount Field Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
A.5.36
1 1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
Remittance Audit (RemitAud)

<Desc>
Client Up to Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
<StatusCode>
A.5.37
1 1100 1180 1200
Remittance Synchronization (RemitSync)

<Desc>
<StatusCode>
A.5.38
810
Remit Reversal (RemitRev)

<Desc>
<StatusCode>
A.5.39
1060
Recurring Payment Model Add (RecPmtAdd)

<Desc>
Cannot Modify Element
<StatusCode>
A-98
April 2005
Version 1.7
<StatusCode>
1280 1480 1500 1520 1540 1560 1580 2020 2030 2130 2140 2150 2160 2180 2190 2310 2780 2910 3140 3180 3200 3240 3260 3380 3400
<Desc>
Object already exists Edit Mask Error Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far in Future Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Destination Account Invalid (for Transfer Payee Payments) UnsupportedUnsupported Frequency Duplicate Recurring Model Invalid Customer PayeeID<CustPayeeId> Invalid Payee Name Payee List Full Invalid Customer Account with Payee Payee Type Not Supported Expired Card Recurring Model Open-Ended
A.5.40
1060 1080 1260 1300 1310 1320 2020 2030 2130 2140 2150
Recurring Payment Instance Add (RecPmtInstAdd)

<Desc>
Cannot Modify Element No Changes Made Unknown Object ID Object not deleted; dependent objects exist Cascade Delete Failed Object exists, but does not match <CustId> Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far in Future
<StatusCode>
Version 1.7
April 2005
A-99
<StatusCode>
2160 2180 2190 2310 2780 2910 2920 3140 3180 3200 3240 3260 3380 3400
<Desc>
Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Destination Account Invalid (for Transfer Payee Payments) Unsupported Frequency Duplicate Recurring Model Invalid Skip Count Invalid Customer Payee ID<CustPayeeId> Invalid Payee Name Payee List Full Invalid Customer Account with Payee Payee Type Not Supported Expired Card Recurring Model Open-Ended
A.5.41
1060 1080 1260 1300 1310 1320 2020 2030 2130 2140 2150 2160 2180 2190 2310 2780 2910 2920 3140 3180 3200 3240
Recurring Payment Model Modify (RecPmtMod)

<Desc>
Cannot Modify Element No Changes Made Unknown Object ID Object not deleted; dependent objects exist Cascade Delete Failed Object exists, but does not match <CustId> Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far in Future Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Destination Account Invalid (for Transfer Payee Payments) Unsupported Frequency Duplicate Recurring Model Invalid Skip Count Invalid Customer Payee ID<CustPayeeId> Invalid Payee Name Payee List Full Invalid Customer Account with Payee
<StatusCode>
A-100
April 2005
Version 1.7
<StatusCode>
3260 3380 3400
<Desc>
Payee Type Not Supported Expired Card Recurring Model Open-Ended
A.5.42
800 1260 1300 1310 1320
Recurring Payment Model Cancel (RecPmtCan)

<Desc>
Object Object Already CommittedAC Unknown Object ID Object Not Deleted; dependent objects exist Cascade Delete Failed Object exists, but does not match <CustId>
<StatusCode>
A.5.43
1100 1120 1140 1160 1260 1320 2000 2010 2060 2100 2110 2120 2150 2200 2300 2440 2510 2520 2530 2540 3140 3380
Recurring Payment Model Inquiry (RecPmtInq)

<Desc>
Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid Data in High Amount Field Invalid High/Low Amount Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Customer Payee ID<CustPayeeId> Expired Card
<StatusCode>
Version 1.7
April 2005
A-101
A.5.44
1 1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
Recurring Payment Model Audit (RecPmtAud)

<Desc>
<StatusCode>
A.5.45
Recurring Payment Model Synchronization (RecPmtSync)

<Desc>
<StatusCode>
1 1100 1180 1200
A.5.46
1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200 2300
Payment Acknowledgment Inquiry (PmtAckInq)

<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid
<StatusCode>
A-102
April 2005
Version 1.7
<StatusCode>
2440 2510 2520 2530 2540 3140 3380
<Desc>
Invalid Single or Source Account Type Invalid Card Magnetic Strip Data Unrecognized / Invalid Card Issuer Unrecognized Card Number Stolen Card Invalid Customer Payee ID <CustPayeeId> Expired Card
A.5.47
810
Payment Acknowledgement Reversal (PmtAckRev)

<Desc>
<StatusCode>
A.5.48
1280 1480 2020 2030 2130 2160 2180 2190 3140 3580 3600
Checksum Add (ChksumAdd)

<Desc>
Object already exists Edit Mask Error Amount Too Small Amount Too Large Date Passed Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Invalid Customer Payee ID <CustPayeeId> Authorization is rejected Authorization held over
<StatusCode>
A.5.49
800 1060 1080 1260 1320 2020 2030 2130 2160
Checksum Modify (ChksumMod)

<Desc>
Object Already Committed Cannot Modify Element No changes made Unknown Object ID Object exists, but does not match <CustId> Amount Too Small Amount Too Large Date Passed Processing Date Precedes Today
<StatusCode>
Version 1.7
April 2005
A-103
<StatusCode>
2180 2190 3140 3580 3600
<Desc>
Request is Too Late for Todays Work Weekend or Holiday Invalid Customer Payee ID<CustPayeeId> Authorization is rejected Authorization held over
A.5.50
1050 1060 1080 1260 1320 1760 3580 3600
Checksum Status Modify (ChksumStatusMod)

<Desc>
<StatusCode>
A.5.51
800 1260 1320
Checksum Cancel (ChksumCan)

<Desc>
Object Object Already Committed Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
A.5.52
1050 1100 1120 1140 1160 1260 1320
Checksum Inquiry (ChksumInq)

<Desc>
<StatusCode>
A.5.53
1050 1100
Checksum Audit (ChksumAud)

<Desc>
Invalid Enum Value Too Many Records Requested
<StatusCode>
A-104
April 2005
Version 1.7
<StatusCode>
1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
<Desc>
Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime - Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range
A.5.54
1100 1180 1200
Checksum Synchronization (ChksumSync)

<Desc>
Too Many Records Requested Token Value Prior to Available History Invalid Token
<StatusCode>
A.5.55
Comprehensible Remittance Statement Add (CompRemitStmtAdd)

<Desc>
Object already exists Invalid Address Invalid City Invalid State or Province Invalid Country Code Invalid Data in Single or Low Amount Field DateTime Too Far in Future Single or Source Account Invalid Single or Source Account Closed Invalid <BillerId> Invalid Payee Name
<StatusCode>
1280 1500 1520 1560 1580 2000 2150 2300 2350 3100 3180
A.5.56
Comprehensible Remittance Statement Inq (CompRemitStmtInq)

<Desc>
Invalid Enum Value No Data matches Selection Criteria
<StatusCode>
1050 1120
Version 1.7
April 2005
A-105
<StatusCode>
1140 1160 1260 1320 2000 2100 2110 2120 2150 2200 2300 2350
<Desc>
Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid Data in Single or Low Amount Field Invalid DateTime Single date or Low of Range Invalid DateTime High of Range Invalid DateTime range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Single or Source Account Closed
A.5.57
Comprehensible Remittance Statement Audit (CompRemitStmtAud)

<Desc>
Client Up to Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selectino Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object Exists, but does not match <CustId> Invalid DateTime Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far in Future History Not Available for Full Date Range
<StatusCode>
1 1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200
A.5.58
Comprehenesible Remittance Statement Synchronization (ComprRemitStmtSync)

<Desc>
Client Up to Date Too many Records Requested Token Value Prior to Available History Invalid Token
<StatusCode>
1 1100 1180 1200
A-106
April 2005
Version 1.7
A.5.59
Payment Batch Add (PmtBatchAdd)

<Desc>
Object already exists Edit Mask Error Invalid Address Invalid City Invalid State or Province Invalid Postal Code Invalid Country Code Amount Too Small Amount Too Large Date Passed DateTime Too Soon DateTime Too Far in Future Processing Date Precedes Today Request is Too Late for Todays Work Weekend or Holiday Destination Account Invalid (for Transfer Payee Payments) Duplicate Payment/Transfer Exists Invalid Payee Name Payee List Full Invalid Customer Account with Payee Payee Type Not Supported Total Payment Amounts Scheduled for Today exceeded daily limit Authorization is rejected Authorization held over
<StatusCode>
1280 1480 1500 1520 1540 1560 1580 2020 2030 2130 2140 2150 2160 2180 2190 2310 2900 3180 3200 3240 3260 3320 3580 3600
A.5.60
Payment Batch Cancel (PmtBatchCan)

<Desc>
Object Already Committed Unknown Object ID Object exists, but does not match <CustId>
<StatusCode>
800 1260 1320
A.5.61
Payment Batch Status Inquiry (PmtBatchStatusInq)
Version 1.7
April 2005
A-107
<StatusCode>
1050 1100 1120 1140 1160 1260 1320 2100 2110 2120 2150 2200 2300 2440 3140
<Desc>
Invalid Enum Value Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object ID Object exists, but does not match <CustId> Invalid DateTime Single date or Low of Range Invalid DateTime High of Range Invalid DateTime Range DateTime Too Far In Future History Not Available for Full Date Range Single or Source Account Invalid Invalid Single or Source Account Type Invalid Customer Payee ID <CustPayeeId>
A.6
A.6.1
1 1100 1120 1140 1160 1400 1500 1520 1540 1560 1580 2100 2150 2500 3100
Bill Presentment Service

Biller Inquiry (BillerInq)
<Desc>
Client Up to Date Too Many Records Requested Selection No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported <SPName> within <BillerId> is invalid Invalid Address Invalid City Invalid State Or Province Invalid Postal Code Invalid Country Code Invalid DateTime - Single date or Low of Range DateTime Too Far in Future Invalid Industry Id Invalid <BillerId><BillerId>
<StatusCode>
A-108
April 2005
Version 1.7
A.6.2
810
Biller Reversal (BillerRev)

<Desc>
<StatusCode>
A.6.3
1050 1100 1120 1140 1160 1260 1320 1400 2100 2110 2120 2150 2200 3100
Bill Inquiry (BillInq)

<Desc>
Invalid Enum Value Too Many Records Requested No Records Match Selection Criteria Some Selection Criteria Not Supported None of selection criteria supported Unknown Object ID Object exists, but does not match <CustId> <SPName> within <BillerId> is invalid Invalid DateTime - Single date or Low of Range Invalid DateTime - High of Range Invalid DateTime Range DateTime Too Far in Future History Not Available for Full Date Range Invalid <BillerId>
<StatusCode>
A.6.4
1050 1060 1080 1260 1320 1060 2100 3140 3180 3240
Bill Status Modification (BillStatusMod)

<Desc>
Invalid Enum Value Cannot Modify Element No Changed made Unknown Object ID Object exists, but does not match <CustId> Cannot Modify Element Invalid DateTime - Single date or Low of Range Invalid Customer Payee ID Invalid Payee Name Invailid Customer Account With Payee
<StatusCode>
A.6.5
810
Bill Reversal (BillRev)

<Desc>
<StatusCode>
Version 1.7
April 2005
A-109
A.7
A.7.1
1040 1280
Root Services
Terminal Object Add (TerminalObjAdd)
<Desc>
Request Declined Object already exists.
<StatusCode>
A.7.2
1050 1060 1080 1260
Terminal Object Modify (TerminalObjMod)

<Desc>
Invalid Enum Value Cannot Modify Element No Changes Made Unknown Object ID
<StatusCode>
A.7.3
1050 1120 1140 1160 1260 1520 1540 1560
Terminal Object Inquiry (TerminalObjInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object Id Invalid City Invalid State or Province Invalid Postal Code
<StatusCode>
A.7.4
1260
Terminal Object Delete (TerminalObjDel)

<Desc>
Unknown Object ID
<StatusCode>
A.7.5
1 1050 1100 1120 1140 1160
Terminal Object Audit (TerminalObjAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported
<StatusCode>
A-110
April 2005
Version 1.7
<StatusCode>
1180 1200 1260
<Desc>
Token Value Prior to Available History Invalid Token Unknown Object ID
A.7.6
Terminal Object Status Modify (TerminalObjStatusMod)

<Desc>
Invalid Enum Value Cannot Modify Element No Changes Made Unknown Object ID Status Code did not change.
<StatusCode>
1050 1060 1080 1260 4010
A.7.7
Terminal Service Provider Object Add (TerminalSPObjAdd)

<Desc>
Request Declined Object already exists.
<StatusCode>
1040 1280
A.7.8
Terminal Service Provider Object Modify (TerminalSPObjMod)

<Desc>
Invalid Enum Value Cannot Modify Element No Changes Made Unknown Object ID
<StatusCode>
1050 1060 1080 1260
A.7.9
Terminal Service Provider Object Inquiry (TerminalSPObjInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object Id Invalid City
<StatusCode>
1050 1120 1140 1160 1260 1520
Version 1.7
April 2005
A-111
<StatusCode>
1540 1560
<Desc>
Invalid State or Province Invalid Postal Code
A.7.10
Terminal Service Provider Object Delete (TerminalSPObjDel)

<Desc>
Unknown Object ID
<StatusCode>
1260
A.7.11
Terminal Server Provider Object Audit (TerminalSPObjAud)

<Desc>
Client Up To Date Invalid Enum Value Too Many Records Requested No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Token Value Prior to Available History Invalid Token Unknown Object ID
<StatusCode>
1 1050 1100 1120 1140 1160 1180 1200 1260
A.7.12
1050 1120 1140 1160 1260 1520 1540 1560
Device Inquiry (DevInq)

<Desc>
Invalid Enum Value No Data Matches Selection Criteria Some Selection Criteria Not Supported None of Selection Criteria Supported Unknown Object Id Invalid City Invalid State or Province Invalid Postal Code
<StatusCode>
A-112
April 2005
Version 1.7
B
B.1
Compatibility Policy
Introduction
This appendix defines the compatibility policy for future editions of the IFX Specification. A number written as n1.n2.n3 identifies the specifications edition and represents three levels of change control where n1 is the version level, n2 is the release level and n3 is the maintenance level. The following sections provide the definitions and rules for changing editions to insure appropriate compatibility between the new and old levels.
B.2
B.2.1
Definitions
Compatibility
Before proceeding to the detailed change rules, it is important that the following key terms are defined.
Compatibility, as used in this policy, is dichotomized into two types. They are syntactic compatibility and semantic compatibility, and are defined as: Syntactic compatibility: is the consistent representation of message structure, i.e., formats, tag names, and element definitions, between old and new levels of the specification. Semantic compatibility: is the consistent representation of message function, i.e., capability, between old and new levels of the specification.
B.2.2
Change Levels
As mentioned above, the three control levels to identify change are version, release and maintenance. Starting with the lowest form of change, the definition of each change level is: Maintenance Level Change: used when correcting defects or providing clarification to the previous edition of the specification. Syntactic and semantic compatibility with previous edition must be maintained. Requires Steering Committee approval by majority vote. Release Level Change: used when adding new functionality to the specification. Same architecture must be followed. Syntactic and semantic compatibility with previous release level must be maintained from a standpoint that the new function does not impact usage of previous function. Requires Steering Committee approval by majority vote. Version Level Change: used when significantly modifying the architecture of the specification. Semantic compatibility with previous version must be maintained unless deviation is approved by the Steering Committee. However, syntactic compatibility with previous version is not guaranteed. As a result, version changes are not expected with any frequency. Architecture Committee must provide advanced warning of potential version level changes to Steering Committee. Requires Steering Committee approval by two-thirds majority vote.
B.3
Compatibility Rules
All specification changes that impact IFX messages must be fully compatible with the previous level of the specification. Specification changes must not require changes by an implementation, in order to continue processing at the same level of function. All new IFX fields and aggregates must be optional. However, a field (or aggregate) within a new aggregate may be required. An absent field (or aggregate) means value not specified. Any processes using the new field (or aggregate) must be constructed such that, when the field (or aggregate) is absent, processing results are the same as before the field (or aggregate)
Following are the rules for maintaining syntactic and semantic compatibility between new and old levels of the IFX Specification:
Version 1.7
April 2005
B-1
Interactive Financial Exchange Business Message Specification existed. No warnings or other non-zero completion codes should be returned if the field (or aggregate) is absent. Optional IFX fields and aggregates must not later become mandatory. An implementation must not be required to populate an IFX field or aggregate to support a function it does not use. o o Repeating IFX fields or aggregates must not later become atomic (or vice versa). IFX fields and aggregates must not be removed from IFX messages. Data types of IFX fields must not change except for length increases. Where the domain of a field, e.g., a closed or open Enum, is a set of discrete valid values: The semantic meaning of a valid value must not change. A valid value must not later become invalid. The semantic meaning of an IFX field may only be clarified, not changed. The IFX tags of existing fields, aggregates or messages must not change.
B.3.1
Policy Guidelines
This section defines compatibility policy guidelines for other key factors that need to be safeguarded when creating a new edition of the specification.
B.3.1.1
Performance
A new edition of the IFX specification should aim for equivalent performance with the previous edition for the same feature set using required elements. Obviously, new features and additional optional data elements would typically imply an associated performance cost (although not necessarily).
B.3.1.2
Security
Application level security of a new edition of the IFX specification should provide compatible application level security support for the previous edition. Any deviation of security compatibility must be approved by the Steering Committee. However, cases may arise that would justify circumventing the security guideline as related to syntactic and/or semantic compatibility. One such example is where a security exposure is discovered with the approach used in the previous edition and an incompatible change is required. Another example is where the industrys security expectation level has increased such that it obsolesces the acceptability of the previous editions security.
B.4
Effective Start Time
The IFX Forum has formally adopted this release-to-release compatibility policy starting with IFX Specification Version 1.0.1 as its baseline release. Therefore, the policy will be in effect for all subsequent releases of the specification until otherwise indicated by the IFX Forum.
B.5
Managing Change for Migrational Ease
As the IFX Specification continues to extend its features and services, it may be necessary to modify or add new building blocks (i.e., fields, aggregates, and/or messages) that obsolesces older constructs. For compliance with this Compatibility Policy, the obsolete constructs will only be removed from the specification during a version level change. Since version level changes are infrequent, this provides sufficient overlap time for migration from the old to new constructs.
B.5.1
Deprecation List
The following table outlines the IFX elements and aggregates that will be replaced in Version 2.0. Both the original and replacement elements and aggregates will be available until Version 2.0.
B-2
April 2005
Version 1.7
Original Tag
Customer Name Aggregate <CustName> Customer Contact Aggregate <CustContact> Organization Contact Aggregate <OrgContact> Customer Name/Address Aggregate <CustNameAddr> Transfer From Supported Aggregate <XferFromSupt> in Bank Account Record Aggregate <BankAcctRec> Transfer To Supported Aggregate <XferToSupt> in Bank Account Record Aggregate <BankAcctRec> Payment Supported Aggregate <PaySupt> in Bank Account Record Aggregate <BankAcctRec> ATM Message Information Aggregate <ATMTrnInfo> in Deposit Account Transaction Record Aggregate <DepAcctTrnRec> ACH Message Information Aggregate <USA.ACHTrnInfo> in Deposit Account Transaction Record Aggregate <DepAcctTrnRec> Settlement Information Aggregate <SettlementInfo> in Payment Instrument Aggregate <PmtInst> Stop Check Information Aggregate <StopChkInfo> in Bank Account Transaction Image Inquiry (see section6.4.15 ) only. Customer Password Modfy Message <Cust PswdModRq>,<CustPswdModRs> Credit Authorization Type element <CreditAuthType> in Credit Information Aggregate <CreditInfo> Network Transaction Information Aggregate <NetworkTrnInfo> in Credit Information Aggregate <CreditInfo> Client Change Code element <ClientChgCode> in Credit Authorization Cancel Message <CreditAuthCanRq> <CreditAuthCanRs> Client Change Code element <ClientChgCode> in Credit Authorization Inquiry Message <CreditAuthInqRq> <CreditAuthInqRs> Debit Authorization Type element <DebitAuthType> in Debit Information Aggregate <DebitInfo> Network Transaction Information Aggregate <NetworkTrnInfo> in Debit Information Aggregate <DebitInfo>
Replacement Tag
Person Name Aggregate <PersonName> Contact Information Aggregate <ContactInfo> Contact Information Aggregate <ContactInfo> Person Information Aggregate <PersonInfo> Bank Account Feature Support Aggregate <BankAcctFeatSupt> Bank Account Feature Support Aggregate <BankAcctFeatSupt> Bank Account Feature Support Aggregate <BankAcctFeatSupt> Network Transaction Information Aggregate <NetworkTrnInfoRec>
Replacement Introduced in Version

1.1.0 1.1.0 1.1.0 1.1.0 1.1.0
1.1.0
1.1.0
1.1.0
Network Transaction Information Aggregate <NetworkTrnInfoRec>
1.1.0
Settlement Information Aggregate <SettlementInfo> Check Number <ChkNum> and several other elements and aggregates
1.1.0
1.2.0
Customer Authentication Modify Message <CustAuthModRq>, <CustAuthModRs> Credit Type element <CreditType> in Credit Information Aggregate <CreditInfo> Network Transaction Information Aggregate <NetworkTrnInfo> in Message Request Header Aggregate <MsgRqHdr> None
1.2.0 1.4.0
1.4.0
1.4.0
None
1.4.0
Debit Type element <DebitType> in Debit Information Aggregate <DebitInfo> Network Transaction Information Aggregate <NetworkTrnInfo> in Message Request Header Aggregate <MsgRqHdr>
1.4.0
1.4.0
Version 1.7
April 2005
B-3
Original Tag
Client Change Code element <ClientChgCode> in Debit Authorization Cancel Message <DebitAuthCanRq> <DebitAuthCanRs> Client Change Code element <ClientChgCode> in Debit Authorization Inquiry Message <DebitAuthInqRq> <DebitAuthInqRs>
Replacement Tag
none
Replacement Introduced in Version

1.4.0
none
1.4.0
B-4
April 2005
Version 1.7
Index
<AppPanSeq>.....................................7, 13 <ApprovalId>.....17, 23, 29, 32, 33, 34, 37, 43, 50, 52 <AppTrnCounter>.....................................8 <AppVersionNum>.................................10 <ArtWorkId>....................................28, 31 <AsyncRqUID>. 2, 3, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 20, 21, 22, 23, 24, 25, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 158, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 240, 241, 242, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 255, 257, 258, 259, 260, 261, 262, 263, 264, 265, 267, 268, 269, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 290, 291, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 305, 306, 307, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 320, 321, 323, 324, 325, 326 <AsyncRsInfo>.................................37, 38 <ATMCityState>....................................22 <ATMLocation>.....................................22
C-1
<AcceptReqd>..........................................9 <AccountHolder>...................................53 <AcctBal>....15, 25, 32, 43, 54, 55, 57, 58, 63, 64, 67 <AcctCur>.........................................26, 39 <AcctFormat>...........................................9 <AcctHelpMsg>........................................9 <AcctId>.........9, 10, 26, 27, 28, 39, 46, 48 <AcctInqRq>.................................2, 57, 59 <AcctInqRs>.......................................2, 58 <AcctKey>........................................26, 39 <AcctMask>....................................1, 9, 12 <AcctMsgRqInfo>............................59, 60 <AcctPayAcct>.......................................25 <AcctPayAcctId>....................................14 <AcctRestrictMsg>...................................9 <AcctRevRq>.....................................3, 59 <AcctRevRs>......................................3, 60 <AcctTaxInfo>........................................88 <AcctTaxStatus>...............................84, 85 <AcctTaxType>......................................24 <AcctType>. .18, 26, 27, 28, 34, 39, 84, 85 <AcctValidateURL>...........................9, 10 <AckType>.......................................19, 33 <AdditionalStatus>.................................38 <Addr1>..................................................18 <Addr2>..................................................18 <Addr3>..................................................18 <Addr4>..................................................18 <AddrType>............................................19 <AdjType>..............................................28 <AgentId>...............................................51 <AgentType>..........................................51 <Aging>..................................................68 <AllocateAllowed>.........................3, 4, 13 <Amt>.........................11, 51, 89, 299, 301 <AmtX>..................................................13 <AmtY>..................................................13 <AppEffDt>............................................10 <AppExpDt>...........................................10 <AppICProf>............................................8 <AppId>..............................................6, 13 <AppPan>...........................................7, 13
Version 1.7
April 2005
<ATMOwner>........................................22 <ATMTrnInfo>.............................3, 22, 47 <AuthAmt>...............................................8 <AuthCode>............................................11 <AuthInfo>.............................................29 <AuthRqCrypto>......................................7 <AuthRsCode>.......................................11 <AuthSupt>...........................................111 <AvailDt>...................................21, 37, 38 <BackupWithholding>............................29 <BalAmt>...............................................53 <BalInqRq>...................................2, 54, 56 <BalInqRs>.........................................2, 54 <BalMsgRqInfo>....................................56 <BalRevRq>.................................2, 20, 55 <BalRevRs>........................................2, 56 <BalType>..............................................32 <BankAcctFeatLimit>......................29, 30 <BankAcctFeatLimitType>....................30 <BankAcctFeatSupt>..............3, 24, 25, 29 <BankAcctFeatType>.............................30 <BankAcctInfo>.........................24, 28, 39 <BankAcctRec>................3, 24, 26, 63, 64 <BankAcctStatus>......................15, 24, 29 <BankAcctStatusCode>....................29, 31 <BankAcctStmtImgInqRec>.................243 <BankAcctStmtImgInqRq>....10, 241, 244 <BankAcctStmtImginqRs>.....................10 <BankAcctStmtImgInqRs>...................242 <BankAcctStmtImgMsgRqInfo>..244, 245 <BankAcctStmtImgRevRq>...........10, 244 <BankAcctStmtImgRevRs>...........10, 245 <BankAcctTaxInqRq>....................3, 4, 86 <BankAcctTaxInqRs>........................4, 87 <BankAcctTrnImgIngRs>......................80 <BankAcctTrnImgInqRq>............3, 79, 83 <BankAcctTrnImgInqRs>..................3, 80 <BankAcctTrnImgMsgRqInfo>.......82, 83 <BankAcctTrnImgRec>....................81, 82 <BankAcctTrnImgRevRq>.................3, 82 <BankAcctTrnImgRevRs>.................3, 83 <BankAcctTrnRec>....................19, 21, 23 <Bankid>.................................................18 <BankId>.. .5, 6, 17, 18, 19, 25, 28, 29, 30, 31, 32, 33, 34, 36, 37, 38, 39, 40, 41, 42,
43, 45, 46, 47, 48, 50, 51, 52, 56, 60, 64, 68, 78 <BankIdType>..................................25, 48 <BankInfo>.......................6, 25, 26, 28, 39 <BankSvc>................................................1 <BankSvcChkSum>................................14 <BankSvcChkSumAddRq>............11, 272 <BankSvcChkSumAddRs>.....11, 272, 280 <BankSvcChkSumAudRq>............12, 278 <BankSvcChkSumAudRs>.............12, 279 <BankSvcChkSumDelRq>.............12, 276 <BankSvcChkSumDelRs>......12, 276, 280 <BankSvcChkSumId>.. .14, 273, 274, 275, 276, 277, 278, 279 <BankSvcChkSumInfo>. 14, 272, 273, 274 <BankSvcChkSumInqRq>..............12, 277 <BankSvcChkSumInqRs>..............12, 278 <BankSvcChkSumModRq>...........12, 273 <BankSvcChkSumModRs>....12, 273, 280 <BankSvcChkSumMsgRec>........280, 281 <BankSvcChkSumRec> 14, 273, 274, 275, 277, 278 <BankSvcChkSumStatus>........14, 15, 275 <BankSvcChkSumStatusCode>....15, 277, 278 <BankSvcChkSumStatusModRq>..12, 274 <BankSvcChkSumStatusModRs>. 12, 275, 280 <BankSvcChkSumSyncRq>...........12, 280 <BankSvcChkSumSyncRs>...........12, 281 <BankSvcChkSumType>.......................15 <BankSvcChkSumValue>......................15 <BankSvcProfInfo>..............................327 <BankSvcRq>. .14, 15, 272, 273, 275, 276, 277 <BaseEnvr>....5, 17, 21, 24, 26, 28, 32, 34, 36, 37, 39, 42, 49, 51, 52 <BaseSvc>................................................1 <BaseSvcProfInfo>...................25, 29, 110 <BatchInfo>............................................31 <BillAmtType>...................................3, 11 <BillCounts>.....................................19, 20 <BillDt>........................................3, 11, 18 <BillerAcctIdInfo>...........................1, 8, 9 <BillerContact>.......................7, 13, 15, 23 <BillerEnrollURL>...................................8
B-2
April 2005
Version 1.7
<BillerId>.....1, 3, 5, 6, 7, 9, 12, 15, 16, 19, 20, 31, 36, 59, 62, 87, 88, 96, 97, 105, 108, 109 <BillerInfo>..................................1, 2, 6, 7 <BillerInqRq>.................1, 2, 6, 14, 17, 36 <BillerInqRs>...........................1, 6, 14, 15 <BillerMsgRqInfo>...........................17, 18 <BillerName>.........................................13 <BillerNum>.............................1, 7, 12, 31 <BillerPayee>...............................7, 13, 14 <BillerPayInfo>......................8, 15, 23, 42 <BillerRec>.4, 6, 11, 13, 14, 16, 42, 54, 56 <BillerRevRq>....................................6, 17 <BillerRevRs>....................................6, 17 <BillerStatus>.......................................6, 8 <BillerStatusCode>...............................6, 8 <BillId>...........................10, 19, 20, 22, 24 <BillInfo>.....................................6, 10, 23 <BillingAcct> 1, 4, 5, 9, 12, 13, 22, 24, 31, 36, 37, 53, 59, 62, 102, 103 <BillingAddr>...................................14, 18 <BillingMethod>...............................28, 31 <BillInqRq>............2, 6, 11, 14, 18, 22, 23 <BillInqRs>.........................2, 6, 18, 19, 31 <BillMsgRqInfo>....................................22 <BillPmtStatus>....................10, 14, 18, 24 <BillPmtStatusCode>....14, 18, 19, 20, 21, 23 <BillPmtStatusCounts>...........................21 <BillRec>...2, 5, 10, 18, 19, 20, 22, 23, 24, 42 <BillRefInfo>....................6, 11, 20, 22, 24 <BillRetAddr>..................................18, 23 <BillRevRq>.......................................6, 21 <BillRevRs>.......................................6, 22 <BillStatus>................................10, 13, 24 <BillStatusCode>............13, 19, 20, 21, 23 <BillStatusCounts>.................................21 <BillStatusModRq>..........6, 11, 14, 18, 23 <BillStatusModRs>.............................6, 24 <BillSummAmt>.......................3, 4, 11, 12 <BillSummAmtCode>............................12 <BillSummAmtId>...........6, 11, 12, 13, 23 <BillSummAmtType>....................3, 4, 12 <BillSummSubAmt>......................3, 4, 12 <BillType>....................2, 3, 10, 11, 19, 27
<BinData>.................................................5 <BinLength>.............................................5 <BirthDt>................................................19 <BranchId>.............................................25 <BranchName>.......................................25 <Brand>......................................28, 43, 52 <BSPReferTo>......................................6, 7 <CanWind>...........................................329 <CardAcctId> 1, 11, 12, 14, 18, 24, 27, 29, 30, 32, 34, 35, 37, 38, 50, 54, 55, 57, 58, 59, 60, 61, 62, 66, 67, 70, 71, 73, 75, 76, 79, 81, 83, 84, 85, 87, 88, 89, 91, 111, 112, 113, 114, 115, 116, 117, 118, 119, 154, 155, 167, 168, 171, 172, 182, 183, 186, 187, 194, 195, 198, 199, 209, 210, 213, 214, 224, 225, 228, 229, 242, 243, 285, 286, 299, 300 <CardAcctIdFrom>....3, 14, 15, 16, 21, 26, 27, 59, 61, 65, 67, 102, 103, 128, 130, 134, 142, 144, 147, 148 <CardAcctIdTo>.........22, 26, 27, 128, 130 <CardEmbossNum>..........................51, 91 <CardLogicalData>.........14, 17, 51, 91, 92 <CardMagData>....1, 3, 12, 14, 27, 28, 38, 39, 62, 63 <CardPref>........................................17, 92 <CardPrefAddRq>........................4, 19, 88 <CardPrefAddRs>.........................4, 19, 89 <CardPrefAdviseRq>................................5 <CardPrefAdviseRs>................................5 <CardPrefAudRq>........................4, 19, 94 <CardPrefAudRs>...............................4, 95 <CardPrefCanRq>.....................................4 <CardPrefCanRs>.....................................4 <CardPrefDelRq>.........................4, 19, 93 <CardPrefDelRs>..........................4, 20, 93 <CardPrefDeposit>.....................17, 18, 92 <CardPrefId>.....16, 90, 91, 92, 93, 94, 95, 96, 97, 99, 100 <CardPrefInfo>...............16, 17, 89, 90, 91 <CardPrefInqRq>..........................4, 19, 91 <CardPrefInqRs>................................4, 92 <CardPrefMisc>......................................17 <CardPrefModRq>.......................4, 19, 90 <CardPrefModRs>........................4, 19, 90 <CardPrefMsgRec>....................19, 95, 97
Version 1.7
April 2005
C-3
<CardPrefMsgRqInfo>...............19, 98, 99 <CardPrefRec>...............16, 89, 91, 93, 94 <CardPrefRevRq>...............................4, 97 <CardPrefRevRs>.........................4, 20, 98 <CardPrefStatus>......................16, 17, 100 <CardPrefStatusCode>...........................17 <CardPrefStatusInqRq>............................5 <CardPrefStatusInqRs>............................5 <CardPrefStatusModRq>..............5, 19, 99 <CardPrefStatusModRs>............5, 20, 100 <CardPrefSyncRq>.......................4, 19, 95 <CardPrefSyncRs>.............................4, 96 <CardPrefType>.....................................92 <CardPrefWithdrawal>...............17, 18, 92 <CardPrefXxx>.......................................92 <CardSeqNum>................................52, 91 <CardType>............................................39 <CardVrfyData>...............................27, 52 <CascadeDel>. .17, 37, 43, 44, 49, 61, 100, 141, 142, 166 <CaseSen>............................................111 <CashAmt>.............................................16 <CashQuality>....................................6, 17 <CashSerialNum>.....................................6 <CashSignature>.......................................6 <CashValidity>...................................6, 17 <Category>. .14, 16, 26, 41, 59, 61, 65, 67, 102, 103 <CCAcctRec>...................................18, 58 <CCAcctStmtInqRq>....................3, 65, 68 <CCAcctStmtInqRs>..........................3, 66 <CCAcctStmtMsgRqInfo>...............68, 69 <CCAcctStmtRec>.................................67 <CCAcctStmtRevRq>.........................3, 68 <CCAcctStmtRevRs>.........................3, 69 <CCAcctTrnInqRq>.....................3, 75, 78 <CCAcctTrnInqRs>............................3, 76 <CCAcctTrnMsgRqInfo>.................77, 78 <CCAcctTrnRec>.................23, 66, 67, 77 <CCAcctTrnRevRq>..........................3, 77 <CCAcctTrnRevRs>...........................3, 78 <CCMotoAcct>.......................................27 <CDOL1>...............................................10 <CDOL2>...............................................10 <Cdtr>...........................................139, 141 <CertCode>.............................................21
<Certificate>.......................................2, 33 <ChargeRegulation>...............................44 <CharType>..........................................111 <CheckAcceptAuth>...............................47 <CheckIssueAdviseRq>........................270 <CheckIssueAdviseRs>........................271 <ChkAcceptAdd>...................................45 <ChkAcceptAddRq>...............12, 282, 292 <ChkAcceptAddRs>...............12, 282, 289 <ChkAcceptAudRq>...............12, 287, 292 <ChkAcceptAudRs>.......................12, 288 <ChkAcceptCanRq>...............12, 286, 292 <ChkAcceptCanRs>...............12, 287, 289 <ChkAcceptDelRs>..............................289 <ChkAcceptId>17, 46, 283, 284, 287, 288, 289, 290, 291, 295 <ChkAcceptInfo>...........46, 282, 283, 284 <ChkAcceptInqRq>................12, 284, 292 <ChkAcceptInqRs>.........................12, 285 <ChkAcceptModRq>..............12, 283, 292 <ChkAcceptModRs>..............12, 283, 289 <ChkAcceptMsgRec>...................289, 291 <ChkAcceptMsgRqInfo>..............292, 294 <ChkAcceptRec>....46, 283, 284, 286, 287 <ChkAcceptRevRq>.......................12, 291 <ChkAcceptRevRs>.......................12, 293 <ChkAcceptStatus>........................46, 295 <ChkAcceptStatusCode>........................46 <ChkAcceptStatusModRq>....12, 293, 294 <ChkAcceptStatusModRs>.............12, 295 <ChkAcceptSyncRq>.............12, 290, 293 <ChkAcceptSyncRs>......................12, 290 <ChkAcceptType>..................................47 <ChkBkStyleId>.................28, 30, 31, 150 <ChkClrDt>......................................59, 61 <ChkCourtesyAmt>................................17 <ChkDetail>......................................17, 48 <ChkEnteredAmt>..................................17 <ChkImg>...................................17, 47, 82 <ChkImgBack>.......................................47 <ChkImgFront>......................................47 <ChkInfo>...................................22, 44, 45 <ChkIssueAddRq>..................11, 259, 260 <ChkIssueAddRs>..................11, 259, 270 <ChkIssueAudRq>..........................11, 267 <ChkIssueAudRs>..........................11, 268
B-4
April 2005
Version 1.7
<ChkIssueDelRq>...........................11, 263 <ChkIssueDelRs>...................11, 263, 270 <ChkIssueId>...45, 46, 260, 261, 262, 263, 264, 266 <ChkIssueInfo>.44, 45, 258, 259, 260, 261 <ChkIssueInqRq>...........................11, 264 <ChkIssueInqRs>............................11, 265 <ChkIssueModR>...................................11 <ChkIssueModRq>.......................258, 260 <ChkIssueModRs>.........11, 260, 261, 270 <ChkIssueMsgRec>......................268, 270 <ChkIssueRec>......45, 260, 261, 263, 264, 267, 271 <ChkIssueStatus>.............45, 46, 260, 262 <ChkIssueStatusCode>. .45, 258, 260, 265, 266 <ChkIssueStatusModRq>.......11, 258, 261 <ChkIssueStatusModRs>........11, 262, 270 <ChkIssueSyncRq>.........................11, 268 <ChkIssueSyncRs>.........................11, 269 <ChkNum>....3, 14, 18, 21, 24, 45, 46, 48, 59, 61, 65, 67, 70, 79, 81, 82, 110, 139, 141, 265, 266 <ChkNumEnd>.......................................23 <ChkNumPrefix>..............................28, 30 <ChkNumStart>..........................23, 28, 30 <ChkNumSuffix>.............................28, 30 <ChkOrdAddRq>......................6, 150, 161 <ChkOrdAddRs>......................6, 150, 157 <ChkOrdAdviseRq>.........................6, 159 <ChkOrdAdviseRs>..........................6, 160 <ChkOrdAudRq>......................6, 155, 161 <ChkOrdAudRs>..............................6, 156 <ChkOrdCanRq>......................6, 152, 161 <ChkOrdCanRs>.......................6, 153, 157 <ChkOrdDetail>.............................30, 173 <ChkOrdId>...27, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160 <ChkOrdInfo>..27, 29, 150, 151, 152, 162, 163, 164, 165, 172 <ChkOrdInqRq>.......................6, 153, 161 <ChkOrdInqRs>................................6, 154 <ChkOrdModRq>.....................6, 151, 161 <ChkOrdModRs>...............6, 37, 151, 157 <ChkOrdMsgRec>........................157, 159 <ChkOrdMsgRqInfo>...................161, 162
<ChkOrdRec> 27, 151, 152, 153, 155, 159, 160 <ChkOrdRevRq>..............................6, 160 <ChkOrdRevRs>.......................6, 157, 161 <ChkOrdStatus>.......................27, 29, 160 <ChkOrdStatusCode>.............................29 <ChkOrdSyncRq>.....................6, 158, 161 <ChkOrdSyncRs>.............................6, 158 <ChkPrint>..................................27, 28, 30 <ChkRange>......23, 70, 71, 111, 112, 113, 114, 115, 116, 117, 267, 268 <Chksum>...............................................29 <ChksumAddRq>...........................10, 114 <ChksumAddRs>....................10, 115, 122 <ChksumAdviseRq>.............................124 <ChksumAdviseRs>.............114, 124, 125 <ChksumAudRq>...........................10, 121 <ChksumAudRs>............................10, 121 <ChksumDelRq>............................10, 118 <ChksumDelRs>.....................10, 119, 122 <ChksumId>. .29, 116, 117, 118, 119, 120, 121, 122, 124, 125 <ChksumInfo>........................29, 115, 116 <ChksumInqRq>.............................10, 119 <ChksumInqRs>.............................10, 120 <ChksumModRq>...........................10, 115 <ChksumModRs>...................10, 116, 122 <ChksumMsgRec>.......................122, 124 <ChksumRec>29, 115, 117, 119, 120, 124, 125 <ChksumStatus>......29, 30, 117, 118, 124, 125 <ChksumStatusCode>.....................30, 120 <ChksumStatusModRq>.................10, 117 <ChksumStatusModRs>.........10, 117, 122 <ChksumSyncRq>..........................10, 122 <ChksumSyncRs>...........................10, 123 <ChksumType>.................................29, 30 <ChksumValue>.....................................30 <ChkText>........................................27, 30 <ChkURL>.............................................22 <ChqInstr>....................................139, 141 <ChqNb>.......................................139, 141 <City>...............................................18, 26 <ClientApp>...................................5, 6, 40 <ClientBusinessDt>................................49
Version 1.7
April 2005
C-5
<ClientChgCode>......3, 4, 36, 38, 51, 124, 125, 181, 182, 183, 191, 192, 193, 194, 195, 208, 209, 210, 221, 222, 223, 224, 225, 285, 286 <ClientCreateDt>....................................49 <ClientDt>............................................5, 6 <ClientTerminalSeqId>......................5, 49 <ClosedDt>.............................................15 <CloseDt>...............................................11 <ClubAcctId>...................................28, 31 <CollateralDesc>....................................18 <CompletedPmtCount>..........................18 <CompositeContactInfo>.....17, 19, 22, 32, 33, 55 <CompositeCurAmt>.....18, 20, 21, 34, 35, 36, 38, 41, 45, 47, 53 <CompositeCurAmtId>..........................45 <CompositeCurAmtType>...............16, 45 <CompositePmtRemitInfo>..............18, 19 <CompRemitStmtAddRq>.............10, 127 <CompRemitStmtAddRs>......10, 127, 133 <CompRemitStmtAudRq>.............11, 130 <CompRemitStmtAudRs>..............11, 131 <CompRemitStmtId>..............................30 <CompRemitStmtInfo>..........30, 127, 128 <CompRemitStmtInqRq>...............10, 128 <CompRemitStmtInqRs>...............10, 129 <CompRemitStmtMsgRec>..........131, 133 <CompRemitStmtRec>...........30, 128, 130 <CompRemitStmtStatus>.................30, 31 <CompRemitStmtStatusCode>...............31 <CompRemitStmtSyncRq>............11, 131 <CompRemitStmtSyncRs>.............11, 132 <ContactInfo>....3, 7, 8, 14, 15, 16, 17, 19, 22, 23, 25, 29, 43, 80, 81, 242, 243 <ContactInfoType>.................................17 <ContactName>......................................18 <ContactPref>...................................17, 18 <ContactType>.......................................22 <ContentType>.........................................5 <CorrectAction>.....................................21 <Count>.....3, 4, 14, 18, 19, 21, 28, 29, 30, 31, 33, 34, 44, 53, 150 <CounterpartyInfo>....................20, 22, 28 <Country>.......................18, 21, 26, 43, 54 <CoverMngrm>................................28, 31
<CoverStyleId>.................................28, 31 <CreatedDt>................................15, 39, 49 <CreateRefId>.........................................49 <CreditAddRq>.........................9, 219, 231 <CreditAddRs>.........................9, 220, 227 <CreditAdviseRq>..........................10, 214 <CreditAdviseRs>...........................10, 215 <CreditAudRq>.........................9, 225, 231 <CreditAudRs>.................................9, 226 <CreditAuthAddRq>.................8, 205, 217 <CreditAuthAddRs>.................8, 205, 212 <CreditAuthAdviseRq>....................9, 215 <CreditAuthAdviseRs>.....................9, 216 <CreditAuthAudRq>.................9, 211, 217 <CreditAuthAudRs>.........................9, 211 <CreditAuthCanRq>.............3, 9, 207, 217 <CreditAuthCanRs>.............3, 9, 208, 212 <CreditAuthId>36, 38, 206, 207, 208, 209, 210, 211, 212, 216, 218, 219 <CreditAuthInfo>...........36, 205, 206, 207 <CreditAuthInqRq>..............3, 9, 208, 217 <CreditAuthInqRs>.......................3, 9, 209 <CreditAuthModRq>................8, 206, 217 <CreditAuthModRs>................8, 206, 212 <CreditAuthMsgRec>...................212, 214 <CreditAuthMsgRqInfo>..............217, 218 <CreditAuthRec>...36, 206, 207, 208, 210, 216 <CreditAuthRevRq>.........................9, 217 <CreditAuthRevRs>.................9, 212, 218 <CreditAuthStatus>..........36, 37, 216, 219 <CreditAuthStatusModRq>..............9, 218 <CreditAuthStatusModRs>.......9, 212, 219 <CreditAuthSyncRq>...............9, 212, 217 <CreditAuthSyncRs>........................9, 213 <CreditAuthType>........................3, 36, 37 <CreditCanRq>.........................9, 222, 231 <CreditCanRs>.........................9, 223, 227 <CreditHeldAmtExpDt>.........................16 <CreditId>......5, 15, 38, 47, 214, 215, 221, 222, 223, 224, 225, 226, 227, 229, 230 <CreditInfo>.........3, 15, 37, 220, 221, 222 <CreditInqRq>..........................9, 223, 231 <CreditInqRs>...................................9, 224 <CreditMediaCashInfo>.........................16 <CreditMediaChkAcceptInfo>...............47
B-6
April 2005
Version 1.7
<CreditMediaChkInfo>.................3, 16, 17 <CreditMediaItem>.....................16, 38, 41 <CreditMediaItemId>.............................16 <CreditModRq>........................9, 220, 231 <CreditModRs>........................9, 221, 227 <CreditMsgRec>...........................227, 229 <CreditMsgRqInfo>......................231, 232 <CreditRec>...15, 214, 215, 220, 222, 223, 225 <CreditRevRq>...............................10, 230 <CreditRevRs>.......................10, 227, 231 <CreditStatus>..........15, 16, 215, 229, 230 <CreditStatusCode>..........................16, 37 <CreditStatusModRq>............10, 229, 231 <CreditStatusModRs>.............10, 227, 229 <CreditSyncRq>.......................9, 227, 231 <CreditSyncRs>................................9, 228 <CreditType>......................................3, 38 <CryptoInfoData>.....................................7 <CryptPswd>........................................1, 2 <CryptSecret>.........................................42 <CryptType>..1, 2, 3, 7, 13, 14, 15, 18, 29, 33, 42, 47, 54, 56, 111 <CSPCustInfoReq>...................................8 <CSPhoneNum>.....................................52 <CSPRefId>.....2, 3, 7, 8, 9, 14, 16, 18, 21, 22, 24, 26, 27, 29, 31, 32, 33, 34, 35, 38, 39, 40, 42, 43, 44, 45, 47, 48, 49, 52, 53, 55, 56, 57, 58, 60, 62, 64, 65, 68, 69, 70, 72, 73, 75, 76, 77, 78, 81, 82, 83, 85, 86, 87, 89, 91, 93, 94, 96, 97, 99, 100, 101, 102, 103, 104, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 117, 118, 119, 120, 122, 123, 125, 126, 127, 128, 130, 136, 137, 138, 139, 140, 141, 142, 143, 144, 149, 151, 152, 153, 155, 160, 162, 163, 165, 166, 167, 168, 175, 176, 177, 179, 180, 181, 182, 183, 188, 190, 191, 192, 193, 194, 195, 200, 201, 203, 204, 206, 207, 208, 209, 210, 215, 216, 218, 219, 220, 222, 223, 224, 225, 230, 232, 233, 235, 236, 237, 243, 245, 247, 248, 249, 251, 255, 256, 258, 260, 261, 264, 265, 266, 271, 273, 274, 275, 277, 278, 280, 281, 283, 284, 285, 286, 287, 294,
295, 297, 298, 302, 308, 310, 311, 312, 314, 317, 323, 325, 326 <CurAmt>. .3, 4, 5, 6, 9, 12, 13, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 26, 28, 30, 31, 32, 33, 34, 44, 45, 46, 68, 82, 84, 85, 88, 89, 90, 91, 94, 96, 97, 98 <CurCode>......9, 11, 28, 34, 89, 90, 91, 94 <CurConvertRule>............................11, 24 <CurRate>.........................................11, 24 <Cursor>.................................2, 14, 39, 40 <Cust PswdModRq>.................................3 <CustAcctUse>.......................................29 <CustAddRq>.....................1, 28, 111, 112 <CustAddRs>................................1, 29, 42 <CustAudRq>.....................................2, 40 <CustAudRs>................................2, 29, 41 <CustAuthModRq>...................1, 3, 32, 35 <CustAuthModRs>.........................1, 3, 33 <CustAuthMsgRqInfo>....................34, 35 <CustAuthRev>........................................1 <CustAuthRevRq>..................................34 <CustAuthRevRs>..................................35 <CustBankPrefSupt>............................328 <CustBankSvcPref>..........................16, 17 <CustContact>........3, 8, 15, 16, 17, 80, 81 <CustContactPref>............................15, 16 <CustDelRq>......................................1, 36 <CustDelRs>.................................1, 37, 42 <CustDiscInqRq>...............................3, 72 <CustDiscInqRs>................................3, 73 <CustDiscRec>...........................10, 57, 74 <CustDiscStatus>....................................10 <CustDiscStatusCode>.........10, 72, 73, 74 <CustDiscStatusModRq>.......3, 27, 54, 71 <CustDiscStatusModRs>....................3, 72 <CustId>. .2, 3, 4, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117,
Version 1.7
April 2005
C-7
118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 287, 288, 289, 290, 291, 292, 293, 295, 296, 297, 298, 299, 300, 302, 303, 304, 305, 306, 307, 309, 310, 311, 312, 313, 314, 315, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326 <CustIdInqRq>...................................2, 39 <CustIdInqRs>....................................2, 40 <CustInfo>........................8, 28, 30, 31, 40 <CustInqRq>.......................................2, 38 <CustInqRs>.......................................2, 38 <CustLangPref>....................................5, 6 <CustLoginId>..............................2, 14, 40 <CustModRq>.....................................1, 30 <CustModRs>...............................1, 30, 42 <CustMsgRec>.................................42, 44 <CustName>...3, 8, 15, 16, 20, 28, 29, 111 <CustNameAddr> 3, 16, 19, 27, 30, 31, 54, 56 <CustNameReqd>.................................111 <CustPayeeAddRq>....................2, 3, 7, 39 <CustPayeeAddRs>......................7, 40, 49 <CustPayeeAudRq>........................3, 7, 47 <CustPayeeAudRs>............................7, 48 <CustPayeeDelRq>.............2, 7, 15, 43, 44 <CustPayeeDelRs>.......................7, 44, 49
<CustPayeeId>. 2, 7, 12, 22, 24, 31, 35, 41, 42, 43, 44, 45, 46, 47, 48, 50, 52, 59, 62, 65, 67, 72, 73, 86, 87, 88, 90, 93, 98, 99, 100, 101, 103, 104, 108, 139, 141 <CustPayeeInfo>12, 13, 21, 22, 39, 40, 41, 50, 52, 53 <CustPayeeInqRq>.........................2, 7, 45 <CustPayeeInqRs>..............................7, 46 <CustPayeeModRq>.....2, 7, 40, 41, 50, 53 <CustPayeeModRs>.....................7, 41, 49 <CustPayeeMsgRec>........................48, 50 <CustPayeeName>........................139, 141 <CustPayeeRec>.............12, 40, 42, 44, 47 <CustPayeeSyncRq>.......................3, 7, 49 <CustPayeeSyncRs>...........................7, 50 <CustPayeeTypeModRq>...................7, 42 <CustPayeeTypeModRs>.............7, 42, 49 <CustPermId>.........................2, 14, 31, 40 <CustPref>..........................................8, 16 <CustPswd>..........1, 2, 4, 6, 29, 30, 31, 33 <CustPswdModRq>........................1, 4, 31 <CustPswdModRs>..................1, 3, 31, 32 <CustRec>.............8, 30, 31, 36, 37, 38, 39 <CustStatus>.......................................8, 36 <CustStatusCode>.....................................9 <CustStatusModRq>...........................1, 35 <CustStatusModRs>.....................1, 36, 42 <CustSvcAddRq>...............................2, 44 <CustSvcAddRs>....................2, 27, 44, 51 <CustSvcAudRq>...............................2, 50 <CustSvcAudRs>................................2, 50 <CustSvcDelRq>................................2, 48 <CustSvcDelRs>...........................2, 49, 52 <CustSvcId>. 10, 12, 44, 45, 46, 47, 48, 49 <CustSvcInfo>......................10, 44, 45, 46 <CustSvcModRq>...............................2, 45 <CustSvcModRs>...................2, 27, 46, 51 <CustSvcMsgRec>...........................51, 53 <CustSvcRec>....10, 28, 45, 46, 48, 49, 63, 64 <CustSvcStatus>.......10, 11, 47, 48, 50, 52 <CustSvcStatusCode>.......................11, 44 <CustSvcStatusModRq>.....................2, 47 <CustSvcStatusModRs>...............2, 47, 52 <CustSvcSyncRq>..............................2, 52 <CustSvcSyncRs>...............................2, 52
B-8
April 2005
Version 1.7
<CustSyncRq>....................................2, 42 <CustSyncRs>...............................2, 29, 43 <CustType>...............................................8 <CustWithdrawalPref>...........................17 <CutoffTm>..............................................7 <CVMList>.......................................11, 13 <CVMRslts>...........................................10 <CVMRule>...........................................13 <Day>.......................................................8 <DayFax>...............................................16 <DayPhone>...........................................15 <DaysCall>.............................................35 <DaysToEPost>..................................4, 24 <DaysToPay>.......................4, 12, 13, 134 <DaysWith>..................................134, 329 <Dbtr>...........................................139, 140 <DbtrAcct>...................................139, 140 <DebitAdd>............................................45 <DebitAddRq>....................8, 20, 190, 203 <DebitAddRs>....................8, 20, 190, 197 <DebitAdviseRq>.............................8, 199 <DebitAdviseRs>..............................8, 200 <DebitAudRq>..........................8, 196, 204 <DebitAudRs>..................................8, 196 <DebitAuthAddRq>..................7, 178, 189 <DebitAuthAddRs>..................7, 178, 185 <DebitAuthAdviseRq>.....................7, 200 <DebitAuthAdviseRs>......................7, 201 <DebitAuthAudRq>..................7, 184, 189 <DebitAuthAudRs>..........................7, 184 <DebitAuthCanRq>..............4, 7, 180, 189 <DebitAuthCanRs>...............4, 7, 181, 185 <DebitAuthId>. 34, 35, 179, 180, 181, 182, 183, 184, 185, 187, 188, 201 <DebitAuthInfo>.............34, 178, 179, 180 <DebitAuthInqRq>...............4, 7, 181, 189 <DebitAuthInqRs>........................4, 7, 182 <DebitAuthModRq>.................7, 179, 189 <DebitAuthModRs>.................7, 179, 185 <DebitAuthMsgRec>....................185, 187 <DebitAuthMsgRqInfo>...............189, 190 <DebitAuthRec>....33, 179, 180, 181, 183, 201 <DebitAuthRevRq>..........................8, 188 <DebitAuthRevRs>...................8, 185, 189 <DebitAuthStatus>.........34, 187, 188, 201
<DebitAuthStatusModRevRq>.................7 <DebitAuthStatusModRevRs>.................7 <DebitAuthStatusModRq>...................187 <DebitAuthStatusModRs>............185, 187 <DebitAuthSyncRq>.................8, 185, 189 <DebitAuthSyncRs>.........................8, 186 <DebitAuthType>.........................3, 34, 35 <DebitCanRq>..........................8, 192, 203 <DebitCanRs>...........................8, 193, 197 <DebitId>...5, 33, 191, 192, 193, 194, 195, 196, 197, 199, 200, 202, 284, 285 <DebitInfo>...........3, 33, 35, 190, 191, 192 <DebitInqRq>...........................8, 194, 204 <DebitInqRs>....................................8, 195 <DebitModRq>.........................8, 191, 203 <DebitModRs>.........................8, 192, 197 <DebitMsgRec>............................197, 199 <DebitMsgRqInfo>.......................203, 204 <DebitRec>....33, 191, 192, 193, 195, 199, 200 <DebitRevRq>............................8, 20, 203 <DebitRevRs>...........................8, 197, 204 <DebitStatus>...........33, 34, 200, 202, 216 <DebitStatusCode>...........................33, 34 <DebitStatusModRq>...............8, 202, 203 <DebitStatusModRs>................8, 197, 202 <DebitSyncRq>.........................8, 198, 204 <DebitSyncRs>.................................8, 198 <DebitType>.......................................3, 35 <DelinqAging>.................................67, 68 <DeliveryDestination>......................28, 30 <DeliveryInstruction>.............................24 <DeliveryMedia>..............79, 81, 242, 243 <DeliveryMethod>...15, 16, 19, 20, 23, 24, 25, 28, 30, 32, 36, 37, 38, 39, 45, 46, 54, 55, 57, 58, 60, 61, 62, 63, 64, 66, 67, 70, 71, 72, 73, 74, 76, 77, 79, 81, 84, 85, 87, 88, 89, 90, 91, 102, 103, 114, 115, 129, 130, 135, 143, 144, 242, 243, 328 <DepAcctId>..1, 11, 12, 14, 17, 18, 24, 26, 27, 29, 30, 31, 32, 34, 35, 36, 38, 40, 43, 44, 50, 54, 55, 57, 58, 59, 60, 61, 62, 70, 71, 72, 73, 79, 81, 83, 84, 85, 87, 88, 89, 91, 111, 112, 113, 114, 115, 116, 117, 118, 119, 128, 129, 130, 131, 132, 133, 154, 155, 167, 168, 171, 172, 182, 183,
Version 1.7
April 2005
C-9
186, 187, 194, 195, 198, 199, 209, 210, 213, 214, 224, 225, 228, 229, 242, 243, 264, 266, 267, 268, 269, 285, 286, 299, 300 <DepAcctIdFrom>.....3, 14, 15, 16, 20, 26, 59, 61, 65, 67, 101, 103, 128, 130, 133, 134, 142, 143, 147, 148 <DepAcctIdTo>..........15, 22, 26, 128, 130 <DepAcctRec>..................................17, 58 <DepAcctStmtAdvise>...........................65 <DepAcctStmtAdviseRq>..................3, 64 <DepAcctStmtAdviseRs>...................3, 65 <DepAcctStmtId>...................................43 <DepAcctStmtInqRq>..................3, 60, 63 <DepAcctStmtInqRs>.........................3, 62 <DepAcctStmtMsgRqInfo>..............63, 64 <DepAcctStmtRec>. .43, 61, 62, 63, 64, 65 <DepAcctStmtRevRq>.......................3, 63 <DepAcctStmtRevRs>........................3, 63 <DepAcctTrnAdviseRq>........................72 <DepAcctTrnAdviseRs>.........................73 <DepAcctTrnInqRq>....................3, 69, 74 <DepAcctTrnInqRs>...........................3, 71 <DepAcctTrnMsgRqInfo>................74, 75 <DepAcctTrnRec>.....3, 21, 44, 47, 61, 62, 72, 73 <DepAcctTrnRevRq>.........................3, 73 <DepAcctTrnRevRs>.........................3, 74 <DepAppAcctId>....................................39 <DepAppAddRq>.....................10, 39, 232 <DepAppAddRs>.....10, 39, 232, 233, 239 <DepAppAudRq>...........................10, 237 <DepAppAudRs>...........................10, 238 <DepAppCanRq>...........................10, 235 <DepAppCanRs>....................10, 235, 239 <DepAppId>. .41, 234, 235, 236, 237, 238, 239 <DepAppInfo>..................39, 41, 233, 234 <DepAppInqRq>.............................10, 236 <DepAppInqRs>.............................10, 237 <DepApplicant>......................................39 <DepApplicantAcctRel>.........................40 <DepAppModRq>..........................10, 233 <DepAppModRs>...................10, 234, 239 <DepAppMsgRec>.......................239, 241 <DepAppRec>........40, 233, 235, 236, 237
<DepAppStatus>.....................................41 <DepAppStatusCode>............................41 <DepAppSyncRq>..........................10, 240 <DepAppSyncRs>..........................10, 240 <DepBkOrdAddRq>.................7, 174, 177 <DepBkOrdAddRs>.........................7, 174 <DepBkOrdAdviseRq>.....................7, 175 <DepBkOrdAdviseRs>.............................7 <DepBkOrdId>.......................31, 175, 176 <DepBkOrdInfo>............................31, 174 <DepBkOrdMsgRqInfo>..............176, 177 <DepBkOrdRec>....................31, 175, 176 <DepBkOrdRevRq>.........................7, 176 <DepBkOrdRevRs>..........................7, 177 <DepBkOrdStatus>...........31, 32, 175, 176 <DepBkOrdStatusCode>........................32 <DepBkStyleId>.....................................31 <Dependents>.........................................19 <DependentType>37, 44, 49, 62, 101, 142, 166 <DepMatureDt>......................................17 <Desc>...1, 3, 4, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 121, 122, 136, 137, 148, 149, 161, 162, 176, 177, 189, 190, 203, 204, 217, 218, 231, 232, 244, 245, 257, 258, 292, 294, 307, 308, 322, 323 <DevAdvise>............................................1 <DevAdviseRq>.................................3, 39 <DevAdviseRs>..................................3, 39 <DevAlmAlarm>......................................9 <DevAlmOperation>................................9 <DevAlmType>........................................9 <DevAppComponent>............................13 <DevAppNormalOperation>..................12 <DevAppOperation>...............................12 <DevCamOperation>..............................22 <DevCamStatusArea>............................22
B-10
April 2005
Version 1.7
<DevCamStatusMedia>..........................22 <DevCamStatusPictures>.......................23 <DevCamStatusState>............................23 <DevCamType>......................................22 <DevCdmBin>..................................21, 22 <DevCdmBinCount>..............................22 <DevCdmBinCurCode>.........................22 <DevCdmBinDenomination>.................22 <DevCdmBinMaxCount>.......................22 <DevCdmBinMedia>..............................22 <DevCdmBinNum>................................22 <DevCdmBinStatus>..............................22 <DevCdmBinType>................................22 <DevCdmCashUnits>.............................21 <DevCdmIntermediateStacker>.............21 <DevCdmOperation>..............................21 <DevCdmPosition>.................................21 <DevCdmPositionLocation>..................21 <DevCdmPositionStatus>.......................21 <DevCdmSafeDoor>..............................21 <DevCdmShutter>..................................21 <DevCdmTransport>..............................21 <DevCdmTransportItems>.....................21 <DevCdmType>.....................................20 <DevChkImageEnabled>........................11 <DevChkInk>.........................................11 <DevChkMedia>.....................................11 <DevChkOperation>...............................11 <DevChkType>.......................................10 <DevCimBin>...................................19, 20 <DevCimBinCount>...............................20 <DevCimBinCurCode>..........................20 <DevCimBinDenomination>..................20 <DevCimBinMaxCount>........................20 <DevCimBinNum>.................................20 <DevCimBinStatus>...............................20 <DevCimBinType>.................................20 <DevCimCashUnits>..............................19 <DevCimDropBox>................................19 <DevCimIntermediateStacker>..............19 <DevCimNoteReader>...........................19 <DevCimOperation>...............................19 <DevCimPosition>.................................19 <DevCimPositionLocation>...................19 <DevCimPositionStatus>........................20 <DevCimSafeDoor>...............................19
<DevCimShutter>...................................20 <DevCimStackerItems>..........................19 <DevCimTransport>...............................20 <DevCimTransportItems>......................20 <DevCimType>......................................18 <DevDepContainer>...............................11 <DevDepEnvelopeDispenser>................12 <DevDepEnvelopeSupply>....................11 <DevDepNumOfDeposits>.....................12 <DevDepOperation>...............................11 <DevDepPrinter>....................................12 <DevDepShutter>...................................12 <DevDepToner>.....................................12 <DevDepTransport>...............................11 <DevDepType>.......................................11 <DevDetail>..............................................6 <DevDetailAlm>...................................7, 9 <DevDetailApp>.................................7, 12 <DevDetailCam>................................7, 22 <DevDetailCdm>................................6, 20 <DevDetailChk>.................................6, 10 <DevDetailCim>.................................7, 18 <DevDetailDep>.................................6, 11 <DevDetailIdc>...............................6, 9, 38 <DevDetailPIN>.................................6, 10 <DevDetailPtr>.............................6, 13, 38 <DevDetailSiu>..................................7, 14 <DevDetailTtu>....................................7, 9 <DevDetailVdm>................................7, 14 <DevDetailXxx>.....................................38 <DevHealthLevel>..................................13 <DevId>............................5, 37, 38, 39, 40 <DevIdcCards>.........................................9 <DevIdcChipPower>................................9 <DevIdcMedia>........................................9 <DevIdcOperation>..................................9 <DevIdcRetainBin>..................................9 <DevIdcRetainedCard>......................9, 12 <DevIdcSecurity>.....................................9 <DevIdcType>..........................................9 <DevInfo>.............................................5, 6 <DevInq>..................................................1 <DevInqRq>.......................................3, 37 <DevInqRs>........................................3, 38 <DevName>..................................6, 37, 38 <DevPINEncStat>...................................10
Version 1.7
April 2005
C-11
<DevPINOperation>...............................10 <DevPINType>.......................................10 <DevPlatformData>..............................6, 7 <DevPlatformSource>..............................7 <DevPlatformXfs>....................................7 <DevPtrInk>...........................................13 <DevPtrLamp>.......................................14 <DevPtrMedia>.......................................13 <DevPtrOperation>.................................13 <DevPtrRetractBin>...............................13 <DevPtrSupply>...............................13, 14 <DevPtrSupplyLevel>............................14 <DevPtrSupplyLocation>.......................14 <DevPtrToner>.......................................13 <DevPtrType>.........................................13 <DevRec>.....................................5, 39, 40 <DevSiuAmberLed>...............................17 <DevSiuAmbientLight>.........................16 <DevSiuAudibleAlarm>.........................17 <DevSiuAudio>......................................17 <DevSiuAuxiliary>.................................15 <DevSiuAuxiliaryStatus>.................15, 17 <DevSiuCabinet>....................................16 <DevSiuCdmGuidelight>.......................18 <DevSiuChkGuidelight>........................18 <DevSiuCimGuidelight>........................18 <DevSiuCoinInGuidelight>....................18 <DevSiuCoinOutGuidelight>.................18 <DevSiuDepGuidelight>........................18 <DevSiuDocumentGuidelight>..............18 <DevSiuDoors>......................................15 <DevSiuDoorStatus>........................15, 16 <DevSiuEnhancedAudio>......................16 <DevSiuFasciaLight>.............................17 <DevSiuGreenLed>................................17 <DevSiuGuidelights>.............................15 <DevSiuGuidelightStatus>...............15, 17 <DevSiuHeat>.........................................16 <DevSiuHeating>...................................17 <DevSiuIdcGuidelight>..........................17 <DevSiuIndicators>................................15 <DevSiuIndicatorStatus>..................15, 16 <DevSiuOpenClose>..............................16 <DevSiuOperation>................................15 <DevSiuOperatorSwitch>.......................16 <DevSiuPassbookGuidelight>................18
<DevSiuProximity>................................16 <DevSiuReceiptGuidelight>...................18 <DevSiuRedLed>...................................17 <DevSiuRemoteStatus>..........................17 <DevSiuSafe>.........................................16 <DevSiuScannerGuidelight>..................18 <DevSiuSeismic>...................................16 <DevSiuSensors>....................................15 <DevSiuSensorStatus>.....................15, 16 <DevSiuTamper>....................................16 <DevSiuType>..................................14, 15 <DevSiuUps>..........................................17 <DevSiuVandalShield>..........................16 <DevSiuVolume>...................................17 <DevStatus>..............................5, 6, 39, 40 <DevStatusCode>.........................6, 38, 39 <DevTtuKbd>.........................................10 <DevTtuKbdLock>.................................10 <DevTtuLed>..........................................10 <DevTtuOperation>................................10 <DevTtuType>........................................10 <DevType>.............................................38 <DevVdmOperation>.............................14 <DevVdmServiceState>.........................14 <DfltDaysToPay>.....................4, 134, 329 <DfltPmtInfo>...................................14, 15 <DfltXferDaysToPay>......................4, 134 <DiscDt>...............................................1, 8 <DiscId>. .1, 2, 8, 9, 10, 27, 70, 71, 72, 73, 74 <DiscInfo>..........................8, 9, 10, 73, 74 <DiscInqRq>...................................2, 3, 70 <DiscInqRs>.................................3, 27, 70 <Discount>........................................27, 28 <DiscRec>.........................9, 45, 46, 55, 71 <DiscReqd>......................................1, 2, 8 <DiscURL>...............................................9 <DomXferFeeCurAmt>........................329 <DriversLicense>..............................19, 21 <DueDt>....3, 5, 11, 16, 18, 26, 42, 44, 67, 96, 97, 134 <DupChkOverride>.. .7, 51, 52, 53, 83, 84, 85, 95, 96, 123, 124, 125, 127, 138, 139, 163 <EffDt> 4, 5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 20, 21, 26, 27, 28, 29, 30, 31, 32,
B-12
April 2005
Version 1.7
33, 34, 37, 41, 43, 44, 45, 46, 50, 52, 55, 82, 83, 84, 85, 86, 94, 127, 128 <EffUrgency>...................................28, 29 <EmailAddr>..............................16, 18, 23 <EmployeeIdent>....................................54 <EmployeeIdentlNum>...........................55 <EmployerName>...................................55 <EmploymentData>................................19 <EmploymentHistory>...............19, 21, 54 <EmploymentStatus>..............................21 <EMVCardAdviseRq>.....................87, 88 <EMVCardAdviseRs>............................88 <EMVCardId>........................................87 <EMVCardInfo>.....................................87 <EMVCardRec>...............................87, 88 <EMVRqData>...................4, 6, 14, 87, 88 <EMVRsData>.............................5, 10, 11 <EMVTrnType>.......................................9 <EndDt>.18, 19, 21, 35, 44, 67, 90, 91, 94, 243 <EndtoEndId>...............................139, 140 <EnrollDesc>........................................111 <EnrollProf>.....................28, 29, 110, 111 <Environment>.......................................51 <EstablishDt>.........................................22 <EU.Cur>........................................5, 6, 24 <EveFax>................................................16 <EvePhone>............................................15 <ExpDt>...6, 13, 18, 19, 21, 24, 27, 30, 32, 33, 34, 37, 38, 48, 52, 54, 55, 94 <ExpectedAvailDt>..................................5 <ExpectedOpenDt>.......................4, 28, 29 <ExtAcctBal>...........33, 54, 55, 57, 58, 67 <ExtBalType>.........................................33 <Fax>......................................................23 <Fee>................24, 27, 44, 46, 63, 72, 329 <FeeChargeAlloc>..................................44 <FeeType>..............................................46 <FICreditTrcNum>...............16, 58, 59, 62 <FIDebitTrcNum>................16, 58, 59, 61 <FinalCurAmt>.......................................36 <FinalDueDt>.........................................36 <FinalPrcDt>...........................................36 <FirstName>.....................................15, 20 <FontId>...........................................28, 31 <ForExDealAddRq>.....9, 94, 95, 104, 105
<ForExDealAddrs>.................................94 <ForExDealAddRs>...................9, 95, 102 <ForExDealAdviseRq>.........................109 <ForExDealAdviseRs>.........................109 <ForExDealAudRq>.............................101 <ForExDealAudRs>.............................101 <ForExDealCanRq>...............................99 <ForExDealCanRs>......................100, 102 <ForExDealId>....9, 16, 26, 35, 36, 93, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 107, 108, 109, 110 <ForExDealInfo>............93, 94, 95, 96, 97 <ForExDealInqRq>.................................98 <ForExDealInqRs>.................................99 <ForExDealModRq>..............................96 <ForExDealModRs>.......................96, 102 <ForExDealMsgRec>...................102, 104 <ForExDealMsgRqInfo>..............105, 106 <ForExDealRec>. 93, 96, 97, 99, 100, 109, 110 <ForExDealRevRq>.............................104 <ForExDealRevRs>..............................105 <ForExDealStatus>..93, 94, 107, 108, 109, 110 <ForExDealStatusCode>........................94 <ForExDealStatusInqRq>.....................108 <ForExDealStatusInqRs>.....................108 <ForExDealStatusModRq>...................106 <ForExDealStatusModRs>...................107 <ForExDealSyncRq>............................103 <ForExDealSyncRs>............................103 <ForExInfo>...........................................26 <ForExRateDealType>....9, 34, 89, 90, 91, 94, 98, 99 <ForExRateId>.................................88, 91 <ForExRateInfo>........................24, 26, 91 <ForExRateInqRq>.......................4, 89, 92 <ForExRateInqRs>...................4, 9, 34, 90 <ForExRateMsgRqInfo>..................92, 93 <ForExRateRec>...............................88, 91 <ForExRateRevRq>............................4, 92 <ForExRateRevRs>............................4, 92 <ForExRateType>.............................90, 91 <ForExValDt>............................90, 91, 94 <ForExValDtType>....................90, 91, 94 <Fraction>.............................................8, 9
Version 1.7
April 2005
C-13
<Freq>.................................18, 33, 36, 135 <FSPayee>........................7, 13, 14, 65, 67 <FullName>................................15, 16, 19 <FundingPriority>...................................40 <Gender>................................................19 <GenSessKey>............................2, 3, 6, 14 <GovIssueIdent>.....................................20 <GovIssueIdentType>.............................54 <GovOrg>...............................................54 <GovOrgName>.....................................54 <GovRank>.............................................54 <GrpId>.........................................139, 140 <GrpSts>.......................................139, 141 <Heading>...............................................10 <HighChkNum>.....................................48 <HighCurAmt>...........................35, 36, 40 <HistRetentionDays>..................7, 15, 134 <HoldCoId>..............................................7 <HoldCount>..........................................17 <HolDt>..................................................25 <HolInfo>...............................................25 <HolInqRq>........................................1, 24 <HolInqRs>.....................................1, 4, 24 <Id>.......................................139, 140, 141 <IdentCharacterData>.................48, 51, 52 <IdentConditions>..................................49 <IdentPrevReadMethod>........................49 <IdentPrevServiceCode>........................49 <IdentProgramId>...................................48 <IdentReadMethod>...............................48 <IdentSerialNum>.............................54, 55 <IdentServiceCode>...............................49 <IdentType>............................................48 <IdentVerifyEntity>................................49 <IdentVerifyMethod>.............................49 <IdentVerifyResults>..............................49 <IFX>................................................22, 23 <ImageURL>..................2, 13, 45, 82, 243 <ImmediatePmt>.....................................16 <ImmediateXfer>....................................26 <ImportDt>.............................................26 <IncAllItems>...................................80, 81 <IncBal>...............................57, 58, 63, 64 <IncBillerContact>...........................15, 16 <IncCounts>................................19, 20, 21
<IncDetail>. .44, 60, 61, 62, 63, 64, 65, 66, 67, 242, 243 <IncDisc>..........................................73, 74 <IncEndrsmntStmp>.........................28, 31 <IncExtBal>..........................54, 55, 57, 58 <IncHistory>.....................60, 62, 265, 266 <IncImages>.....................................15, 16 <Income>................................................21 <IncRefInfo>...........................................80 <IncSecSigLine>...............................28, 31 <IncSummary>.................................19, 20 <IncToken>8, 9, 38, 39, 46, 47, 60, 62, 63, 64, 102, 103, 114, 115, 129, 130, 131, 143, 144, 167, 169, 182, 183, 194, 196, 209, 210, 224, 225, 236, 237, 265, 266, 267, 285, 286 <IndustId>7, 12, 15, 16, 20, 22, 36, 37, 41, 42 <IndustNum>..........................................41 <InitialCurAmt>.....................................36 <InitialDeposit>......................................29 <InsPaidCurAmt>...................................19 <InsPaidDt>............................................19 <IntAPY>................................................40 <IntermediaryDepAcct>...................26, 44 <InterXferProf>............................328, 329 <IntlXferFeeCurAmt>..........................329 <IntRateInfo>..............................29, 40, 85 <IntRateInqRq>............................4, 83, 86 <IntRateInqRs>...................................4, 84 <IntRateMsgRqInfo>..............................86 <IntRateRevRq>.................................4, 85 <IntRateRevRs>..................................4, 86 <IntXferProf>.......................................329 <InvoiceAdj>....................................27, 28 <InvoiceAdjNum>..................................28 <InvoiceInfo>.............6, 21, 22, 24, 27, 52 <InvoiceLineItem>...........................27, 28 <InvoiceLineItemNum>.........................28 <InvoiceNum>........................................27 <InvoicePremium>.................................27 <InvoiceReceiver>............................23, 25 <InvoiceSender>...............................23, 25 <InvoiceType>........................................27 <InvoiceVouchNum>.............................27 <IssActionCodeDefault>........................10
B-14
April 2005
Version 1.7
<IssActionCodeDenial>..........................10 <IssActionCodeOnline>.........................10 <IssAppData>...........................................8 <IssAuthData>........................................11 <IssCountryCode>..................................10 <IssDiscData>.........................................11 <IssDt>........................................52, 54, 55 <IssPostScriptData>................................12 <IssPreScriptData>.................................12 <IssScriptCmd>......................................12 <IssScriptData>...........................10, 11, 12 <IssScriptId>.....................................12, 13 <IssScriptResult>....................................12 <IssScriptResultData>......................10, 12 <IssueLoc>........................................52, 55 <Issuer>...................................................55 <IssuerName>.........................................52 <JobTitle>...............................................21 <Language>..................................7, 16, 17 <LastDepCurAmt>.................................17 <LastDepDt>...........................................17 <LastName>......................................15, 20 <LastPmtCurAmt>..................................18 <LastPmtDt>.....................................18, 19 <LastStmtDt>..........................................58 <LastTrnDt>...........................................58 <LastYrInsPaidCurAmt>........................19 <LastYrInsPaidDt>.................................19 <LastYrTaxPaidCurAmt>.......................19 <LastYrTaxPaidDt>................................19 <LegalName>. 6, 14, 15, 16, 21, 22, 23, 28 <LegalRptCode>.....................................26 <LicenseNum>........................................21 <LimitPosition>......................................53 <LoanAcctId> 1, 12, 15, 18, 19, 24, 27, 28, 29, 30, 32, 38, 40, 50, 54, 55, 57, 58, 59, 60, 79, 81, 82, 83, 84, 85, 87, 88, 111, 112, 113, 114, 115, 116, 117, 118, 119, 154, 155, 167, 168, 171, 172, 242, 243, 299, 300 <LoanAcctIdFrom>. 26, 28, 128, 130, 134, 143, 144, 147, 148 <LoanAcctIdTo>.........22, 26, 28, 129, 130 <LoanAcctRec>................................18, 59 <LoanInfo>.............................................18 <LoanInfoCommon>........................18, 19
<LOCAcctRec>................................19, 59 <LocInfo>...............................................18 <LockboxAcctId>...................................31 <LockboxDepId>.....30, 31, 128, 129, 130, 131, 132, 133 <LockboxURL>......................................31 <LOCLimit>...........................................19 <Logo>................................................8, 15 <LogoURL>..............................................8 <LongText>..............................................9 <LowChkNum>......................................48 <LowCurAmt>............................35, 36, 40 <MacValue>.............................................5 <MacVariant>...........................................5 <MagData1>...........................................28 <MagData2>...........................................28 <MagData3>.......................................1, 28 <ManualMicr>........................................48 <MaritalStatus>.......................................19 <MatchedRec>........................................40 <MatDt>..................................................18 <Max>...................................................111 <MaxCurAmt>............................25, 45, 46 <MaxRec>.........................................39, 40 <MediaAcctAdjAddRq>.................2, 6, 13 <MediaAcctAdjAddRs>.............2, 4, 7, 11 <MediaAcctAdjAudRq>.................2, 9, 13 <MediaAcctAdjAudRs>.....................2, 10 <MediaAcctAdjId>.........................4, 8, 10 <MediaAcctAdjInfo>................1, 4, 5, 6, 7 <MediaAcctAdjInqRq>..................2, 7, 13 <MediaAcctAdjInqRs>.....................2, 4, 8 <MediaAcctAdjMsgRec>.................10, 12 <MediaAcctAdjMsgRqInfo>..................13 <MediaAcctAdjRec>........................4, 7, 9 <MediaAcctAdjRevRq>.....................2, 12 <MediaAcctAdjRevRs>................2, 11, 13 <MediaAcctAdjSyncRq>..............2, 11, 13 <MediaAcctAdjSyncRs>....................2, 11 <MediaAcctId>.....1, 5, 8, 9, 11, 12, 14, 15 <MediaAcctInventoryInqRq>.......2, 14, 16 <MediaAcctInventoryInqRs>.............2, 14 <MediaAcctInventoryMsgRqInfo>. .15, 16 <MediaAcctInventoryRevRq>............2, 15 <MediaAcctInventoryRevRs>............2, 16 <MediaBal>..........................................3, 4
Version 1.7
April 2005
C-15
<MediaCashInfo>.................................3, 5 <MediaContainerId>.............................1, 2 <MediaItem>.......................1, 2, 3, 4, 5, 15 <MediaSubType>.....................................3 <MediaSvc>..............................................1 <MediaSvcProfInfo>..............................16 <MediaTotal>...........................................4 <MediaTotalType>...................................4 <MediaTrnType>......................................5 <MediaType>............................................3 <Memo>.....2, 3, 4, 6, 9, 10, 11, 12, 13, 14, 15, 18, 19, 20, 22, 23, 24, 26, 27, 30, 33, 41, 42, 43, 45, 46, 48, 53, 59, 61, 102, 103, 111 <Method>.....10, 27, 35, 41, 42, 47, 48, 50, 51, 65, 66, 69, 78, 90, 91, 94, 95, 101, 102, 104, 105, 106, 107, 121, 122, 130, 131, 132, 145, 146, 156, 157, 169, 170, 184, 185, 196, 197, 211, 212, 226, 227, 238, 239, 252, 253, 279, 288, 289, 303, 304, 318, 319 <MicrReadIntegrity>..............................17 <MicrUnformatted>................................17 <MiddleName>.................................15, 20 <Min>...................................................111 <MinAmtDue>........................................67 <MinCurAmt>............................25, 45, 46 <MinPmtCurAmt>..................................19 <Minute>...................................................9 <MiscGovIssueIdent>.............................19 <MktgInfo>...............16, 44, 55, 67, 72, 77 <ModPending>. . .41, 42, 99, 140, 164, 165 <ModPendingType>...........33, 41, 99, 135 <ModPswdFirst>...................................111 <MortAcctRec>................................19, 59 <MotherMaidenName>...........................19 <MsgAuthCode>.......................................5 <MsgRecDt>11, 19, 28, 36, 42, 48, 51, 66, 70, 79, 91, 101, 102, 105, 117, 122, 133, 146, 157, 170, 185, 197, 212, 227, 239, 253, 270, 280, 289, 304, 319 <MsgRqHdr>.....3, 4, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57,
58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 158, 159, 160, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 240, 241, 242, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 290, 291, 293, 294, 295, 296, 297, 298, 300, 301, 302, 303, 305, 306, 307, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 320, 321, 322, 324, 325, 326 <MsgRsHdr>5, 7, 8, 10, 12, 13, 14, 16, 17, 20, 22, 23, 24, 25, 26, 27, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 43, 44, 45, 46, 48, 49, 50, 51, 53, 55, 56, 57, 58, 60, 61, 62, 63, 64, 65, 66, 67, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 111, 112, 113, 115, 116, 118, 119, 120, 121, 122, 123, 124, 126, 127, 129, 131, 132, 134, 136, 137, 138, 139, 140, 141, 142, 143, 145, 147, 149, 150, 152, 153, 154, 156, 158, 160, 162, 163, 164, 166, 168, 170, 172, 173, 174, 175, 177, 179, 180, 181,
B-16
April 2005
Version 1.7
183, 184, 186, 188, 189, 190, 192, 193, 195, 197, 198, 200, 201, 202, 204, 205, 207, 208, 210, 211, 213, 215, 216, 218, 219, 220, 221, 223, 225, 226, 228, 230, 231, 233, 234, 235, 237, 238, 240, 242, 245, 246, 247, 249, 251, 252, 255, 256, 258, 259, 261, 262, 263, 265, 268, 269, 272, 274, 275, 276, 278, 279, 281, 282, 284, 287, 288, 290, 293, 295, 296, 298, 300, 302, 303, 305, 307, 309, 311, 312, 313, 315, 317, 318, 320, 322, 325, 326 <MsgSupt>5, 17, 25, 26, 40, 110, 134, 327 <MsgType>.......................................14, 29 <MsgUID>..............................................13 <Name>3, 7, 12, 13, 15, 16, 17, 20, 21, 22, 23, 24, 25, 27, 36, 37, 41, 42, 45, 46, 47, 48, 51, 52, 59, 62, 66, 67, 299, 301 <NameAddrType>................16, 19, 27, 30 <NameSuffix>...................................15, 20 <NetCurAmt>.................................21, 109 <NetSessionTotals>..............................109 <NetworkOwner>.............................47, 48 <NetworkRefId>.....................................48 <NetworkTrnInfo>.3, 4, 22, 32, 36, 38, 47, 49, 55 <NetworkTrnInfoRec>.............................3 <NewToken>. 4, 12, 19, 44, 50, 53, 68, 72, 80, 93, 97, 104, 107, 119, 123, 133, 135, 148, 159, 172, 187, 199, 214, 229, 241, 270, 281, 291, 306, 321 <NewUpDt>........16, 24, 35, 39, 62, 64, 71 <NextDt>..........................................43, 67 <NextPmtCurAmt>.................................18 <Nickname>.....2, 6, 12, 13, 15, 20, 36, 45, 46, 59, 62 <NickName>...........................................15 <Nm>....................................139, 140, 141 <NotifyReqd>...................................11, 23 <NotifyWilling>...................11, 19, 20, 23 <NumEmployees>..................................22 <NumInsts>.............................................36 <Occupation>..........................................21 <OEDCode>...........................................20 <OEDInstitution>...................................20 <OpenAcctInd>.................................84, 85 <OpenDt>.........................................11, 15
<OptSupt>....6, 16, 17, 25, 32, 39, 40, 110, 134, 328, 329 <Org>................................3, 31, 41, 46, 88 <OrgContact>....3, 6, 7, 14, 17, 22, 23, 28, 43 <OrgId>...........14, 17, 22, 25, 26, 139, 141 <OrgIdNum>...........................................22 <OrgIdType>..........................................22 <OrgInfo>...................8, 17, 21, 22, 25, 26 <OrgPhone>......................................45, 48 <OrgRec>................................................22 <OrigCurAmt>........................................20 <OrigDt>.............18, 19, 20, 24, 45, 46, 48 <OriginatorName>............................22, 47 <OriginatorType>...................................47 <OrigIssueDt>.........................................48 <OrigPmtDueDt>....................................16 <OrigPmtPrcDt>.....................................15 <OtherIdentDoc>....................................20 <OverdraftFunding>.........................39, 40 <OverrideType>........................................6 <OvrSigText>...................................28, 31 <OwnerInd>............................................15 <OwnerPercent>.....................................15 <Ownership>...........................................29 <PaidCurAmt>........................................27 <PaidDt>.................................................44 <PartyAcctRel>.................................15, 16 <PartyAcctRelAddRq>.......................4, 80 <PartyAcctRelAddRs>.......................4, 81 <PartyAcctRelDelRq>........................4, 82 <PartyAcctRelDelRs>.........................4, 83 <PartyAcctRelDesc>...............................16 <PartyAcctRelId>.................15, 82, 83, 86 <PartyAcctRelInfo>........14, 15, 81, 82, 86 <PartyAcctRelInqRq>.........................4, 83 <PartyAcctRelInqRs>.........................4, 84 <PartyAcctRelModRq>......................4, 85 <PartyAcctRelModRs>.......................4, 86 <PartyAcctRelRec>........15, 82, 83, 85, 87 <PartyAcctRelStatus>.............................15 <PartyAcctRelStatusCode>....................15 <PartyAcctRelType>..............................16 <PartyAcctStatusCode>..........................16 <PassbkAcceptData>........................15, 53 <PassbkAddRq>.....................13, 296, 308
Version 1.7
April 2005
C-17
<PassbkAddRs>......................13, 296, 304 <PassbkAudRq>.....................13, 302, 308 <PassbkAudRs>..............................13, 303 <PassbkDelRq>.......................13, 301, 308 <PassbkDelRs>.......................13, 302, 304 <PassbkFormat>.....................................51 <PassbkId>...49, 50, 52, 53, 297, 298, 299, 300, 302, 303, 304, 305, 306, 309, 310, 311, 315, 316 <PassbkInfo>......49, 50, 53, 296, 297, 298 <PassbkInqRq>.......................13, 298, 308 <PassbkInqRs>...............................13, 300 <PassbkItemAddRq>..............13, 311, 323 <PassbkItemAddRs>...............13, 312, 319 <PassbkItemAudRq>..............13, 317, 324 <PassbkItemAudRs>.......................13, 318 <PassbkItemDelRq>...............13, 316, 324 <PassbkItemDelRs>................13, 317, 319 <PassbkItemDetail>..........................52, 53 <PassbkItemId>.......51, 52, 313, 314, 315, 316, 317, 318, 319, 320, 321, 324, 325, 326 <PassbkItemInfo>...........52, 312, 313, 314 <PassbkItemInqRq>................13, 314, 324 <PassbkItemInqRs>........................13, 315 <PassbkItemModRq>.............13, 313, 323 <PassbkItemModRs>..............13, 313, 319 <PassbkItemMsgRec>..................319, 321 <PassbkItemMsgRqInfo>.............322, 323 <PassbkItemRec>. . .51, 312, 314, 316, 317 <PassbkItemRevRq>.......................13, 321 <PassbkItemRevRs>...............13, 319, 322 <PassbkItemStatus>................52, 324, 325 <PassbkItemStatusCode>......52, 315, 316, 324 <PassbkItemStatusInqRq>....................325 <PassbkItemStatusInqRs>....................326 <PassbkItemStatusModRq>............14, 324 <PassbkItemStatusModRs>....14, 319, 325 <PassbkItemStatusRec>..........52, 325, 326 <PassbkItemSyncRq>.............13, 320, 324 <PassbkItemSyncRs>.....................13, 320 <PassbkLastBalPrinted>.........51, 299, 301 <PassbkLastItemPrinted>......51, 297, 299, 301, 324 <PassbkLinesPerPage>...........................51
<PassbkModRq>.............13, 297, 308, 324 <PassbkModRs>.....................13, 298, 304 <PassbkMsgRec>..........................304, 306 <PassbkMsgRqInfo>.....................307, 308 <PassbkNew ItemsToPrint>...................50 <PassbkNewItemsToPrint>..........297, 309 <PassbkNextLine>..................51, 299, 301 <PassbkNextPage>.................51, 300, 301 <PassbkPagesPerBook>..........................51 <PassbkRec>...........49, 297, 298, 301, 302 <PassbkRevRq>..............................13, 306 <PassbkRevRs>......................13, 304, 307 <PassbkStatus>.................49, 50, 309, 310 <PassbkStatusCode>...............50, 297, 309 <PassbkStatusInqRq>...........................310 <PassbkStatusInqRs>............................310 <PassbkStatusModRq>...........13, 308, 309 <PassbkStatusModRs>...........13, 304, 309 <PassbkStatusRec>.................50, 310, 311 <PassbkSyncRq>....................13, 305, 308 <PassbkSyncRs>.............................13, 305 <Passport Country>................................52 <Passport Number>................................52 <Passport>...............................................20 <PassportCountry>.................................20 <PassportNumber>.................................20 <PastDuePmtCount>...............................18 <Payable>.................................................3 <PayAcct>.................................................8 <PayeeCountry>.....................................26 <PayeeInfo>............................................50 <PayeeType>........................42, 43, 45, 46 <PayerInfo>..........................16, 17, 66, 67 <PayInfo>...............................................13 <PayorAcctId>..............................139, 140 <PayorName>...............................139, 140 <PaySummAmt>.....................................11 <PaySupt>...............................3, 24, 25, 26 <PaySvc>..................................................1 <PaySvcProfInfo>.................................133 <PaySvcRq> 14, 29, 30, 31, 115, 116, 117, 118, 120, 124, 125 <PDOL>..................................................10 <PersonalIdent>................................15, 53 <PersonInfo>....3, 8, 16, 17, 19, 28, 30, 53, 55, 56
B-18
April 2005
Version 1.7
<PersonName>.....3, 15, 16, 19, 20, 28, 29, 111 <PersonVerifyType>...............................53 <Phone>....................15, 16, 18, 23, 27, 29 <PhoneNum>..........................................18 <PhoneType>..........................................18 <PhysicalLocId>.....................................21 <PhysicalLocName>...............................21 <PINBlock>..................................3, 14, 33 <PlatformXfsAction>...............................8 <PlatformXfsAppId>................................8 <PlatformXfsCmdCode>..........................8 <PlatformXfsCmdHResult>.....................8 <PlatformXfsDesc>..................................8 <PlatformXfsEventId>..............................8 <PlatformXfsLogicalName>.....................8 <PlatformXfsPhysicalName>...................8 <PlatformXfsRequestId>..........................7 <PlatformXfsState>..................................8 <PlatformXfsTimestamp>........................8 <PlatformXfsWkstName>........................8 <PmtAckAdviseRq>.......................10, 113 <PmtAckAdviseRs>.......................10, 113 <PmtAckInfo>........................................33 <PmtAckInqRq>.............10, 110, 111, 112 <PmtAckInqRs>.............................10, 111 <PmtAckMsgRqInfo>...................112, 113 <PmtAckRec>.................32, 111, 113, 114 <PmtAckRevRq>............................10, 111 <PmtAckRevRs>............................10, 112 <PmtAddRq>...2, 7, 13, 15, 24, 32, 51, 54, 62, 63, 65, 66, 67, 109 <PmtAddRs>.............................3, 7, 51, 70 <PmtAudRq>......................................8, 68 <PmtAudRs>.................................8, 51, 69 <PmtAuth>..............................................72 <PmtAuthAdd>.......................................72 <PmtAuthAddRq>........................8, 72, 81 <PmtAuthAddRs>.........................8, 73, 79 <PmtAuthAudRq>........................8, 77, 81 <PmtAuthAudRs>...............................8, 78 <PmtAuthCanRq>.........................8, 74, 81 <PmtAuthCanRs>.........................8, 75, 79 <PmtAuthCount>....................................18 <PmtAuthId> 17, 20, 73, 74, 75, 76, 77, 78 <PmtAuthInfo>.....................20, 72, 73, 74
<PmtAuthInqRq>................................8, 76 <PmtAuthInqRs>................................8, 76 <PmtAuthModRq>.......................8, 73, 81 <PmtAuthModRs>........................8, 74, 79 <PmtAuthMsgRec>....................78, 79, 80 <PmtAuthMsgRqInfo>.....................81, 82 <PmtAuthRec>...............20, 73, 74, 75, 77 <PmtAuthRevRq>...............................8, 81 <PmtAuthRevRs>.........................8, 79, 82 <PmtAuthStatus>..............................20, 21 <PmtAuthStatusCode>...........................21 <PmtAuthSyncRq>.......................8, 79, 81 <PmtAuthSyncRs>.............................8, 80 <PmtBatchAddRq>.........................11, 135 <PmtBatchAddRs>.........................11, 136 <PmtBatchAdviseRq>............................11 <PmtBatchAdviseRs>.............................11 <PmtBatchAudRq>.................................11 <PmtBatchAudRs>.................................11 <PmtBatchCanRq>.........................11, 137 <PmtBatchCanRs>..........................11, 137 <PmtBatchDelRq>..................................11 <PmtBatchDelRs>..................................11 <PmtBatchId>.........35, 137, 138, 139, 140 <PmtBatchInfo>..............................35, 136 <PmtBatchInqRq>..................................11 <PmtBatchInqRs>...................................11 <PmtBatchModRq>................................11 <PmtBatchModRs>.................................11 <PmtBatchRec>......................35, 137, 138 <PmtBatchRevRq>.................................11 <PmtBatchRevRs>..................................11 <PmtBatchStatus>...................................35 <PmtBatchStatusAdviseRq>...........11, 142 <PmtBatchStatusAdviseRs>...........11, 142 <PmtBatchStatusCode>........138, 139, 141 <PmtBatchStatusInqRq>.................11, 138 <PmtBatchStatusInqRs>.................11, 140 <PmtBatchStatusModRq>......................11 <PmtBatchStatusModRs>.......................11 <PmtBatchStatusRec>............35, 141, 142 <PmtBatchSyncRq>................................11 <PmtBatchSyncRs>................................11 <PmtCanRq>...........................8, 15, 57, 87 <PmtCanRs>.................................8, 57, 70 <PmtEnclAddRq>...........10, 245, 246, 257
Version 1.7
April 2005
C-19
<PmtEnclAddRs>...........10, 245, 246, 253 <PmtEnclAdviseRq>......................11, 255 <PmtEnclAdviseRs>.......................11, 256 <PmtEnclAudRq>.........................251, 257 <PmtEnclAudRs>.................................252 <PmtEnclCanRq>...................11, 250, 257 <PmtEnclCanRs>....................11, 250, 253 <PmtEnclId>. .42, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256 <PmtEnclInfo>..........41, 42, 246, 247, 248 <PmtEnclInqRq>....................11, 248, 257 <PmtEnclInqRs>.............................11, 249 <PmtEnclModRq>..................10, 247, 257 <PmtEnclModRs>...................10, 247, 253 <PmtEnclMsgRec>...............................253 <PmtEnclMsgRqInfo>..................257, 258 <PmtEnclPayee>.....................................42 <PmtEnclPayeeInfo>........................41, 42 <PmtEnclRec> 42, 246, 248, 250, 251, 256 <PmtEnclRevRq>...........................11, 257 <PmtEnclRevRs>....................11, 253, 258 <PmtEnclStatus>.......42, 43, 254, 255, 256 <PmtEnclStatusCode>............................43 <PmtEnclStatusModRq>........11, 253, 257 <PmtEnclStatusModRs>.................11, 255 <PmtEnclType>................................41, 42 <PmtFormat>..........................................44 <PmtId>...3, 14, 15, 22, 32, 52, 53, 54, 55, 57, 59, 61, 65, 67, 69 <PmtInfo> 3, 11, 14, 15, 16, 20, 51, 52, 53, 95, 96, 98, 99, 134 <PmtInqRq>......................8, 18, 58, 60, 63 <PmtInqRs>........................................8, 60 <PmtInst>................................3, 11, 24, 42 <PmtInstruction>....................................43 <PmtInstType>.................................42, 43 <PmtLegalRpt>...............23, 25, 96, 97, 98 <PmtLegalRptData>...............................26 <PmtMethod>.............................18, 59, 62 <PmtModel>.........................................134 <PmtModRq>.............7, 15, 18, 52, 53, 63 <PmtModRs>......................3, 7, 53, 68, 70 <PmtMsgRec>..................................69, 72 <PmtMsgRqInfo>.............................63, 64 <PmtRec>.................15, 52, 53, 58, 62, 98
<PmtRefId>16, 24, 32, 54, 55, 65, 67, 139, 140 <PmtRemitAck>.........................15, 18, 32 <PmtRemitChksum>...............................19 <PmtRemitDetail>..................................19 <PmtRemitInfo>...............................15, 17 <PmtRemitRefId>.19, 23, 65, 67, 139, 141 <PmtRemitStatus>..................................19 <PmtRemitStatusCode>..........................19 <PmtRevRq>.......................................8, 63 <PmtRevRs>.................................8, 64, 70 <PmtRmtId>.................................139, 141 <PmtStatus>..........6, 15, 17, 32, 54, 55, 70 <PmtStatusAdviseRq>..................8, 20, 55 <PmtStatusAdviseRs>........................8, 56 <PmtStatusAdviveRs>............................56 <PmtStatusCode> 6, 17, 18, 33, 60, 62, 66, 68, 138 <PmtStatusInqRq>........................8, 64, 66 <PmtStatusInqRs>..............................8, 66 <PmtStatusModRq>............................7, 54 <PmtStatusModRs>......................7, 55, 70 <PmtStatusRec>..........................32, 56, 68 <PmtSummAmt>....................6, 22, 23, 24 <PmtSyncRq>...............................8, 20, 70 <PmtSyncRs>...............................8, 51, 71 <PmtTrnStatusCode>....................139, 141 <PmtType>.......................................59, 61 <PointOfServiceData>..................5, 49, 51 <POSAgent>.....................................50, 51 <POSAttended>......................................50 <POSCapabilities>............................50, 51 <POSCaptureCapability>.......................50 <POSEntryCapability>...........................50 <POSLocation>.......................................51 <POSOperation>.....................................50 <POSOutCapabilities>............................50 <POSSecurity>.................................49, 51 <PostAddr> 3, 8, 12, 14, 15, 16, 17, 18, 23, 25, 26, 27, 29, 42, 45, 47, 48, 112 <PostAddrReqd>...................................112 <PostalCode>..9, 15, 16, 18, 26, 27, 36, 37 <PostedDt>.................................20, 23, 53 <PostingSessionAddRq>..................5, 101 <PostingSessionAddRs>...........5, 101, 102 <PostingSessionAudRq>..................5, 106
B-20
April 2005
Version 1.7
<PostingSessionAudRs>...................5, 106 <PostingSessionId>..20, 51, 103, 104, 105, 106, 107, 108 <PostingSessionInfo>.............20, 102, 103 <PostingSessionInqRq>....................5, 104 <PostingSessionInqRs>....................5, 104 <PostingSessionModRq>..................5, 102 <PostingSessionModRs>..........5, 101, 103 <PostingSessionMsgRec>.............101, 107 <PostingSessionRec>......20, 102, 103, 105 <PostingSessionStatus>..................20, 108 <PostingSessionStatusCode>..20, 104, 105 <PostingSessionStatusModRq>........5, 107 <PostingSessionStatusModRs> 5, 101, 108 <PostingTotalType>.........................21, 22 <POSVerifyCapability>..........................50 <PrcDaysOff>.......................................4, 7 <PrcDt>...............3, 16, 26, 31, 42, 82, 134 <PrcDtAdj>...............................................7 <PrcSched>...................7, 25, 32, 134, 329 <PrefetchURL>.......................................13 <PrefTimeEnd>.................................15, 17 <PrefTimeStart>...............................15, 17 <PrenoteReqd>.......................................24 <PrepayPenalty>.....................................18 <PresAcctId>.....1, 2, 7, 11, 12, 14, 30, 31, 38, 59, 60 <PresAcctInfo>...............12, 30, 31, 59, 60 <PresAcctRec>.................................30, 64 <PresAcctStatus>..............................30, 31 <PresAcctStatusCode>...........................31 <PresSvc>.................................................1 <PresSvcProfInfo>..................................25 <PrevYrCurAmt>...................................88 <PrimaryAcct>..................................15, 29 <PrintReceipt>..................................18, 19 <ProcessControl>....................................48 <ProductId>............................................29 <Prompt>..........................................41, 42 <ProxyClient>.................................5, 6, 40 <PSSCATSecLevel>...............................50 <PSSMsgEncryption>.............................50 <PSSMsgMAC>.....................................50 <PSSNetworkType>...............................50 <Pswd>.....................................................1 <PswdDelivery>...............................29, 30
<PurposeDesc>.......................................18 <Rate>.............................28, 40, 45, 46, 88 <RecChkOrdAddRq>.................6, 30, 162 <RecChkOrdAddRs>................6, 163, 170 <RecChkOrdAudRq>.......................7, 169 <RecChkOrdAudRs>........................7, 169 <RecChkOrdCanRq>........................6, 165 <RecChkOrdCanRs>................6, 166, 171 <RecChkOrdId>.....29, 154, 155, 156, 157, 164, 165, 166, 167, 168, 169, 170, 172, 173 <RecChkOrdInqRq>.........................7, 166 <RecChkOrdInqRs>.........................7, 167 <RecChkOrdInstAddRq>.................7, 172 <RecChkOrdInstAddRs>..................7, 173 <RecChkOrdModRq>.................6, 30, 163 <RecChkOrdModRs>.........6, 37, 164, 170 <RecChkOrdMsgRec>..................170, 172 <RecChkOrdRec>...29, 163, 165, 166, 168 <RecChkOrdSyncRq>......................7, 171 <RecChkOrdSyncRs>.......................7, 171 <RecCtrlIn>.. .2, 7, 8, 9, 10, 11, 12, 14, 15, 16, 18, 20, 27, 32, 33, 35, 36, 37, 38, 39, 41, 43, 45, 46, 47, 48, 49, 50, 51, 52, 53, 58, 61, 62, 64, 65, 66, 67, 68, 69, 70, 71, 75, 76, 77, 78, 79, 80, 84, 85, 90, 92, 94, 95, 96, 97, 101, 102, 103, 104, 105, 106, 107, 114, 115, 116, 117, 118, 119, 121, 122, 123, 128, 129, 130, 131, 132, 133, 134, 142, 143, 145, 147, 154, 155, 156, 157, 158, 159, 167, 168, 169, 170, 171, 172, 182, 183, 184, 185, 186, 187, 194, 195, 196, 197, 198, 199, 209, 210, 211, 212, 213, 214, 224, 225, 226, 227, 228, 238, 239, 240, 241, 242, 243, 248, 249, 252, 264, 266, 267, 268, 269, 279, 281, 284, 288, 289, 290, 291, 299, 300, 303, 304, 305, 306, 314, 315, 318, 319, 320, 321 <RecCtrlOut>.8, 10, 12, 16, 20, 27, 33, 35, 37, 38, 39, 41, 43, 46, 48, 50, 51, 53, 61, 62, 64, 65, 66, 68, 69, 71, 76, 77, 78, 80, 85, 90, 93, 95, 97, 102, 104, 105, 107, 115, 117, 119, 122, 123, 129, 131, 132, 133, 134, 143, 145, 147, 155, 157, 159, 168, 170, 172, 183, 185, 187, 195, 197,
Version 1.7
April 2005
C-21
199, 210, 212, 214, 225, 227, 228, 239, 241, 243, 249, 252, 266, 268, 269, 279, 281, 285, 289, 291, 300, 304, 306, 315, 319, 321 <RecModelInfo>20, 25, 29, 36, 95, 96, 98, 99, 138, 139, 140, 163, 164, 165 <ReconRqUID>................................39, 40 <RecPmtAddRq>........2, 9, 13, 20, 95, 108 <RecPmtAddRs>........................9, 95, 105 <RecPmtAudRq>......................9, 104, 108 <RecPmtAudRs>..............................9, 104 <RecPmtCanRq>......................9, 100, 108 <RecPmtCanRs>.......................9, 100, 105 <RecPmtId>.......15, 20, 59, 61, 96, 97, 98, 100, 101, 103, 104, 105 <RecPmtInqRq>.......................9, 101, 108 <RecPmtInqRs>................................9, 102 <RecPmtInstAddRq>..................9, 96, 108 <RecPmtInstAddRs>..........................9, 97 <RecPmtMod>........................................18 <RecPmtModRq>.................9, 20, 98, 108 <RecPmtModRs>..................9, 20, 99, 105 <RecPmtMsgRec>........................105, 107 <RecPmtMsgRqInfo>...................108, 109 <RecPmtProf>.......................................135 <RecPmtRec>.............20, 96, 99, 101, 103 <RecPmtRevRq>............................10, 107 <RecPmtRevRs>.....................10, 105, 108 <RecPmtSyncRq>...................10, 106, 108 <RecPmtSyncRs>...........................10, 106 <RecSeriesEnd>..........................20, 25, 30 <RecXferAddRq>...............5, 25, 138, 149 <RecXferAddRs>.....................5, 138, 146 <RecXferAudRq>.....................5, 144, 149 <RecXferAudRs>.............................5, 145 <RecXferCanRq>.....................5, 141, 149 <RecXferCanRs>......................5, 141, 146 <RecXferId>. .25, 128, 130, 131, 132, 139, 140, 141, 142, 143, 145, 146 <RecXferInqRq>.......................5, 142, 149 <RecXferInqRs>...............................5, 143 <RecXferMod>.......................................25 <RecXferModRq>..............5, 25, 139, 149 <RecXferModRs>...............5, 37, 140, 146 <RecXferMsgRec>.......................146, 148 <RecXferMsgRqInfo>..................148, 149
<RecXferProf>..................................32, 33 <RecXferRec>........25, 139, 140, 142, 144 <RecXferRevRq>.............................6, 148 <RecXferRevRs>......................6, 146, 149 <RecXferSyncRq>....................6, 146, 149 <RecXferSyncRs>............................6, 147 <RefId>...................................................47 <RefInfo>.....14, 20, 23, 24, 25, 26, 27, 28, 29, 31, 44, 47, 80, 82 <RefType>..................................25, 44, 47 <RegPmtCurAmt>..................................18 <RelatedCreditId>.....................................5 <RelatedItemInqRqUID>.............314, 316 <RemainingInsts>.......................20, 25, 30 <RemainingPmtCount>..........................18 <RemitAddr>....................................18, 23 <RemitAddRq>...................4, 9, 82, 83, 93 <RemitAddRs>.............................9, 83, 91 <RemitAdviceRefId>..............................20 <RemitAudRq>.............................9, 89, 94 <RemitAudRs>.......................9, 83, 85, 90 <RemitDelRq>..............................9, 87, 94 <RemitDelRs>..............................9, 87, 91 <RemitDetail>.................22, 23, 96, 97, 98 <RemitId>....18, 21, 84, 85, 86, 87, 88, 89, 90, 91 <RemitInfo>...6, 15, 16, 20, 21, 24, 30, 31, 50, 83, 84, 85 <RemitInqRq>..............................9, 88, 94 <RemitInqRs>.....................................9, 89 <RemitInstruction>...............21, 24, 96, 97 <RemitModRq>......................9, 84, 85, 94 <RemitModRs>.............................9, 85, 91 <RemitMsgRec>...............................91, 93 <RemitMsgRqInfo>..........................93, 94 <RemitName>.........................................23 <RemitRec>....................21, 84, 85, 88, 89 <RemitRefId>.........................................24 <RemitRevRq>...................................9, 93 <RemitRevRs>..............................9, 91, 94 <RemitStatus>.......................21, 26, 86, 89 <RemitStatusCode>................................26 <RemitStatusModRq>..................9, 85, 94 <RemitStatusModRs>...................9, 86, 91 <RemitSyncRq>............................9, 92, 94 <RemitSyncRs>..................................9, 92
B-22
April 2005
Version 1.7
<ReqdExctnDt>............................140, 141 <RequestedOperationMode>....................4 <ResolvePendingDt>..............9, 11, 12, 29 <RestartType>...................................28, 29 <RevOptSupt>..............................110, 328 <RevReasonCode>....4, 12, 13, 15, 16, 17, 18, 22, 34, 35, 38, 39, 56, 59, 60, 63, 64, 68, 69, 74, 75, 77, 78, 81, 82, 83, 85, 86, 92, 93, 94, 98, 99, 105, 106, 107, 109, 112, 113, 121, 122, 136, 137, 148, 149, 161, 162, 176, 177, 188, 189, 203, 204, 217, 218, 231, 232, 244, 245, 257, 258, 292, 294, 307, 308, 322, 323 <RootSvc>................................................1 <RootSvcProfInfo>.................................40 <RqUID>. 2, 3, 4, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 210, 211, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 240, 241, 242, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287,
288, 290, 291, 293, 294, 295, 296, 297, 298, 300, 301, 302, 303, 305, 306, 307, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 320, 321, 322, 324, 325, 326 <SalesSlipRefNum>...............................23 <SecAmt>.................................................8 <SecEncryptId>......................................14 <SecObjAddRq>.................................3, 74 <SecObjAddRs>.................................3, 75 <SecObjAdviseRq>............................3, 78 <SecObjAdviseRs>.............................3, 78 <SecObjDelRq>..................................3, 77 <SecObjDelRs>..................................3, 77 <SecObjId>. .1, 3, 5, 13, 29, 33, 42, 47, 54, 56, 75, 76, 77, 78, 79, 80 <SecObjInfo>........................13, 74, 75, 76 <SecObjInitRemKey>.......................78, 79 <SecObjInqRq>..................................3, 76 <SecObjInqRs>...................................3, 77 <SecObjKeyChkValue>.........................13 <SecObjModRq>................................3, 75 <SecObjModRs>.................................3, 75 <SecObjName>.................................13, 76 <SecObjPurpose>.......................13, 14, 76 <SecObjRec> 12, 13, 75, 76, 77, 78, 79, 80 <SecObjStatus>.................................13, 14 <SecObjStatusCode>........................14, 77 <SecObjSyncRq>................................4, 79 <SecObjSyncRs>................................4, 79 <SecObjType>..................................13, 76 <SecObjValue>.......................9, 12, 13, 14 <Second>..............................................8, 9 <Secret>..............................................1, 42 <SecretFormat>.......................................42 <SecretId>.........................................41, 42 <SecretList>..............28, 29, 41, 42, 54, 56 <SecretMask>.................................1, 2, 42 <SecretOptional>....................................41 <SecretPrompt>. 1, 7, 8, 28, 41, 42, 54, 56, 111 <SecSignId>............................................14 <SecSignID>.............................................9 <SelRangeChkNum>..........48, 80, 81, 285 <SelRangeCurAmt>.....8, 9, 35, 60, 62, 70, 71, 75, 76, 77, 79, 81, 88, 89, 102, 103, 128, 129, 130, 143, 144, 182, 183, 194,
Version 1.7
April 2005
C-23
195, 209, 210, 224, 225, 249, 250, 265, 266, 285, 286 <SelRangeDate>...................................314 <SelRangeDt>..8, 9, 10, 19, 20, 27, 35, 41, 42, 47, 48, 50, 51, 61, 62, 65, 66, 67, 68, 69, 70, 71, 75, 76, 77, 78, 80, 81, 84, 88, 89, 90, 91, 94, 95, 101, 102, 104, 105, 106, 107, 114, 115, 116, 117, 121, 122, 129, 130, 131, 132, 145, 154, 155, 156, 157, 167, 168, 169, 170, 182, 183, 184, 185, 194, 195, 196, 197, 209, 210, 211, 212, 224, 225, 226, 227, 238, 239, 242, 243, 252, 267, 268, 279, 285, 286, 288, 289, 303, 304, 315, 316, 318, 319 <SelRangeDueDt>. 35, 60, 62, 66, 68, 110, 111, 129, 130, 140, 141, 249, 250, 265, 266 <SelRangePaidDt>........................265, 266 <SelRangePrcDt>.......35, 60, 62, 249, 250 <SentRec>...............................................40 <SeqNum>..............................................27 <ServerDt>................................................6 <ServerStatusCode>...............................38 <ServerTerminalSeqId>......................5, 49 <SessionBal>..........................................21 <SessionDt>....................................21, 104 <SessionId>...........................................109 <SessionLocId>......................................21 <SessionLocName>................................21 <SessionLoginId>...................................21 <SessionPostingDt>................................21 <SessionTotalInqRq>...............................5 <SessionTotalInqRs>................................5 <SessionTotalsInqRq>..........................108 <SessionTotalsInqRs>..........................109 <SessionTotalsRec>................21, 109, 110 <SessionType>......................................109 <SessKey>....................................3, 4, 5, 6 <SettleInd>..............................................47 <SettlementId>........................................43 <SettlementInfo>..........................3, 21, 43 <SettlementMethod>...................43, 65, 67 <Severity>....1, 3, 6, 19, 20, 37, 38, 40, 50, 52, 64, 66, 89 <ShortDesc>.......................................4, 12 <SignoffRq>.......................................7, 23
<SignoffRs>........................................7, 23 <SignonCert>....................................2, 4, 6 <SignonICC>......................................5, 13 <SignonInfo>............1, 3, 31, 33, 110, 111 <SignonMagPIN>.........................3, 4, 5, 6 <SignonOverride>.............................4, 5, 6 <SignonPswd>..................................2, 4, 6 <SignonRole>...................................2, 3, 6 <SignonRq>. 3, 4, 6, 7, 8, 9, 11, 12, 14, 15, 16, 17, 18, 20, 22, 23, 24, 25, 33, 34, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 145, 146, 147, 148, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 178, 179, 180, 182, 184, 186, 187, 188, 190, 191, 193, 194, 196, 198, 199, 200, 201, 202, 203, 205, 206, 207, 209, 211, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 224, 226, 228, 229, 230, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 243, 244, 246, 247, 248, 249, 250, 251, 252, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 266, 267, 268, 269, 270, 271, 272, 273, 274, 276, 277, 279, 280, 281, 282, 283, 284, 285, 287, 288, 289, 290, 291, 292, 293, 295, 296, 297, 298, 299, 300, 302, 303, 304, 305, 306, 307, 309, 310, 311, 312, 313, 314, 315, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326 <SignonRs>.................................3, 4, 6, 23 <SignonTransport>...............................2, 4 <SkipNextN>..........................................37 <SpaceAlwd>........................................111 <SpecialHandling>.................................46
B-24
April 2005
Version 1.7
<SPName>. 1, 3, 5, 6, 7, 10, 12, 13, 14, 15, 18, 21, 22, 24, 25, 31, 32, 33, 41, 50, 51, 94, 106, 108, 109 <SpouseName>.......................................19 <SPRefId>..2, 3, 7, 8, 9, 14, 16, 18, 21, 22, 24, 25, 26, 27, 29, 30, 31, 32, 33, 34, 35, 37, 38, 39, 40, 42, 43, 44, 45, 47, 48, 49, 52, 54, 55, 56, 57, 58, 60, 62, 64, 65, 67, 68, 69, 70, 72, 73, 75, 76, 77, 78, 81, 82, 83, 84, 85, 86, 87, 88, 89, 91, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 117, 118, 119, 120, 122, 123, 125, 126, 127, 128, 130, 136, 137, 138, 139, 140, 141, 142, 143, 144, 149, 151, 152, 153, 155, 160, 162, 163, 165, 166, 167, 168, 175, 176, 177, 179, 180, 181, 182, 183, 188, 190, 191, 192, 194, 195, 200, 201, 203, 204, 206, 207, 208, 209, 210, 215, 216, 218, 219, 220, 222, 223, 224, 225, 230, 232, 233, 235, 236, 237, 243, 245, 247, 248, 249, 251, 255, 256, 258, 260, 261, 264, 265, 266, 271, 273, 274, 275, 277, 278, 280, 281, 283, 284, 285, 286, 287, 294, 295, 297, 298, 302, 308, 310, 311, 312, 314, 317, 323, 325, 326 <SPRefID>................................................9 <SPRefIdCorrect>...................................21 <StartDt>18, 19, 21, 35, 43, 48, 67, 90, 91, 94, 243 <StateProv>...........................18, 21, 26, 54 <Status>.....1, 3, 6, 7, 8, 10, 11, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 123, 124, 126, 127, 129, 131, 132, 134, 135, 136, 137, 138, 140, 141, 142, 143, 145, 147, 149, 150, 152, 153, 154, 156,
158, 160, 161, 163, 164, 166, 168, 170, 171, 173, 174, 175, 177, 178, 180, 181, 182, 184, 186, 188, 189, 190, 192, 193, 195, 196, 198, 200, 201, 202, 204, 205, 206, 208, 209, 211, 213, 215, 216, 218, 219, 220, 221, 223, 224, 226, 228, 230, 231, 233, 234, 235, 237, 238, 240, 242, 245, 246, 247, 249, 250, 252, 255, 256, 259, 261, 262, 263, 265, 268, 269, 271, 272, 273, 275, 276, 278, 279, 281, 282, 283, 287, 288, 290, 293, 295, 296, 298, 300, 302, 303, 305, 307, 309, 311, 312, 313, 315, 317, 318, 320, 322, 325, 326 <StatusCode>...1, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 123, 124, 126, 127, 129, 131, 132, 134, 137, 138, 140, 141, 143, 145, 147, 149, 150, 152, 153, 154, 156, 158, 161, 163, 164, 166, 168, 170, 171, 173, 174, 177, 178, 180, 181, 182, 184, 186, 188, 189, 190, 192, 193, 195, 196, 198, 202, 204, 205, 206, 208, 209, 211, 213, 218, 219, 220, 221, 223, 224, 226, 228, 230, 231, 233, 234, 235, 237, 238, 240, 242, 245, 246, 247, 249, 250, 252, 255, 259, 261, 262, 263, 265, 268, 269, 271, 272, 273, 275, 276, 278, 279, 281, 282, 283 <StatusDesc>.....2, 4, 5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 17, 20, 21, 23, 26, 27, 29, 30, 31, 32, 37, 38, 41, 43, 45, 50, 52, 64, 66, 94 <StatusModBy>...4, 5, 6, 9, 10, 11, 12, 13, 14, 15, 16, 17, 20, 21, 27, 29, 30, 31, 32, 33, 34, 37, 41, 43, 45, 50, 52, 94 <StdPayeeId>.....1, 3, 7, 12, 13, 31, 36, 37, 42, 52, 59, 62, 85, 87, 88
Version 1.7
April 2005
C-25
<StdPayeeInfo>.......................................12 <StdPayeeInqRq>.....................3, 7, 36, 38 <StdPayeeInqRs>................................7, 37 <StdPayeeMsgRqInfo>.....................38, 39 <StdPayeeRec>.............................4, 12, 37 <StdPayeeRevRq>..............................7, 38 <StdPayeeRevRs>...............................7, 38 <StmtImage>.................................2, 11, 13 <StmtImg>............................................243 <StmtRunningBal>.................................21 <StmtSummAmt>.......................43, 44, 67 <StmtSummType>..................................44 <StmtType>....43, 61, 62, 66, 67, 242, 243 <StopChkAddRq>.................4, 6, 110, 121 <StopChkAddRs>.....................4, 111, 117 <StopChkAdviseRq>........................4, 119 <StopChkAdviseRs>.........................4, 120 <StopChkAudRq>.....................4, 116, 121 <StopChkAudRs>.............................4, 116 <StopChkCanRq>.....................4, 112, 121 <StopChkCanRs>.....................4, 113, 117 <StopChkId>.........................................120 <StopChkInfo> 3, 23, 24, 79, 81, 110, 111, 112, 113, 114, 115 <StopChkInqRq>......................4, 114, 121 <StopChkInqRs>...............................4, 114 <StopChkMsgRec>.......................117, 119 <StopChkMsgRqInfo>..................121, 122 <StopChkProf>.....................................328 <StopChkRec>........23, 112, 113, 115, 120 <StopChkRevRq>.............................4, 120 <StopChkRevRs>.....................4, 117, 121 <StopChkStatus>..................................120 <StopChkStatusCode>............................23 <StopChkSyncRq>...................4, 118, 121 <StopChkSyncRs>............................4, 118 <StopCount>...........................................17 <SupplRptCode>.....................................26 <SupplyingCountry>...............................26 <SuppressEcho>...................................3, 5 <SvcAcctAddRq>...........1, 2, 9, 14, 54, 68 <SvcAcctAddRs>.............2, 27, 53, 55, 66 <SvcAcctAudRq>...................3, 55, 64, 69 <SvcAcctAudRs>...............................3, 65 <SvcAcctDelRq>..........................3, 60, 69 <SvcAcctDelRs>...........................3, 61, 66
<SvcAcctId> 11, 54, 55, 56, 57, 58, 59, 60, 61 <SvcAcctIdModRq>...........................3, 59 <SvcAcctIdModRs>.....................3, 59, 66 <SvcAcctInfo>..........11, 12, 54, 55, 56, 57 <SvcAcctInqRq>.......................2, 3, 62, 69 <SvcAcctInqRs>.............................2, 3, 63 <SvcAcctModRq>........................2, 56, 69 <SvcAcctModRs>...................2, 27, 56, 66 <SvcAcctMsgRec>...........................66, 68 <SvcAcctMsgRqInfo>......................68, 69 <SvcAcctRec>.. .11, 28, 55, 57, 58, 60, 62, 63, 64 <SvcAcctRev>..........................................2 <SvcAcctRevRq>...................................68 <SvcAcctRevRs>..............................66, 69 <SvcAcctStatus>.........2, 11, 12, 58, 64, 66 <SvcAcctStatusCode>..................2, 11, 12 <SvcAcctStatusModRq>...............2, 57, 69 <SvcAcctStatusModRs>...............2, 58, 66 <SvcAcctSyncRq>..................3, 55, 66, 69 <SvcAcctSyncRs>..............................3, 67 <SvcCore>.....6, 7, 16, 18, 23, 25, 40, 110, 134, 327 <SvcName>....3, 10, 15, 24, 25, 44, 50, 51, 63, 64, 70, 71, 73, 74 <SvcProfInqRq>......1, 2, 6, 7, 16, 22, 110, 327 <SvcProfInqRs>........1, 2, 6, 7, 23, 25, 133 <SvcRqUID>.....15, 32, 33, 54, 55, 65, 67, 111, 113, 114, 115, 116, 117, 118, 119, 120, 124, 125, 139, 141, 272, 273, 274, 275, 276, 277, 278 <TagName>..............................................6 <TaxCountry>.........................................29 <TaxId>.............................................21, 88 <TaxInfo>.........................................27, 46 <TaxPaidCurAmt>..................................19 <TaxPaidDt>...........................................19 <TaxProvince>........................................29 <TaxType>........................................46, 88 <TaxYear>........................................87, 88 <TCHash>...............................................10 <TDOL>.................................................10 <Technology>.........................................52 <Term>.....................18, 29, 34, 40, 84, 85
B-26
April 2005
Version 1.7
<TerminalCaps>.....................................10 <TerminalCountryCode>..........................8 <TerminalId>..........................5, 32, 33, 47 <TerminalObjAddRq>........................2, 23 <TerminalObjAddRs>..................2, 23, 28 <TerminalObjAdviseRq>...................2, 29 <TerminalObjAdviseRs>....................2, 30 <TerminalObjAudRq>........................2, 26 <TerminalObjAudRs>........................2, 27 <TerminalObjDelRq>...................2, 25, 26 <TerminalObjDelRs>...................2, 26, 28 <TerminalObjId>. 3, 24, 25, 26, 27, 28, 29, 30 <TerminalObjInfo>.................3, 23, 24, 29 <TerminalObjInqRq>.........................2, 25 <TerminalObjInqRs>..........................2, 25 <TerminalObjModRq>.......................2, 24 <TerminalObjModRs>..................2, 24, 28 <TerminalObjMsgRec>..........................27 <TerminalObjRec>....3, 23, 24, 25, 26, 29, 30 <TerminalObjStatus>..........3, 4, 28, 29, 30 <TerminalObjStatusCode>.......................4 <TerminalObjStatusModRq>.............2, 28 <TerminalObjStatusModRs>..............2, 29 <TerminalSPObjAddRq>...................2, 30 <TerminalSPObjAddRs>..............2, 31, 36 <TerminalSPObjAdvise>........................36 <TerminalSPObjAdviseRq>...............3, 36 <TerminalSPObjAdviseRs>...............3, 37 <TerminalSPObjAudRq>...................2, 34 <TerminalSPObjAudRs>....................2, 35 <TerminalSPObjDelRq>.....................3, 34 <TerminalSPObjDelRs>...............3, 34, 36 <TerminalSPObjId>...4, 31, 32, 33, 34, 35, 36, 37 <TerminalSPObjInfo>........4, 5, 31, 32, 36 <TerminalSPObjInqRq>.....................2, 32 <TerminalSPObjInqRs>.....................2, 33 <TerminalSPObjModRq>...................2, 31 <TerminalSPObjModRs>.............2, 32, 36 <TerminalSPObjMsgRec>................35, 36 <TerminalSPObjRec>4, 31, 32, 33, 34, 36, 37 <TerminalSPObjStatus>...........4, 5, 36, 37 <TerminalSPObjStatusCode>.............5, 33
<TerminalType>.....................................47 <TerminalVrfyRslt>.................................9 <TermUnits>.....................................34, 35 <TINInfo>.............................15, 19, 21, 22 <TINType>.............................................21 <TitlePrefix>.....................................15, 20 <Token>...3, 4, 8, 9, 11, 12, 19, 20, 38, 39, 43, 46, 47, 49, 50, 52, 53, 60, 63, 64, 67, 68, 71, 72, 79, 80, 92, 93, 96, 97, 102, 103, 104, 106, 107, 114, 115, 118, 119, 123, 129, 130, 131, 132, 133, 134, 143, 144, 147, 158, 159, 167, 169, 171, 182, 183, 186, 187, 194, 196, 198, 199, 209, 210, 213, 214, 224, 225, 228, 229, 236, 237, 240, 265, 266, 267, 269, 281, 285, 286, 290, 291, 305, 306, 320, 321 <TotalCurAmt>...................3, 4, 19, 22, 27 <TotalFeeCharge>..................................18 <Trk2EquivData>.....................................7 <TrnAuthId>.............................................5 <TrnCategory>........................................11 <TrnCountLimit>............53, 61, 62, 70, 72 <TrnDt>....................................................9 <TrnId>.....................................................5 <TrnImg>................................................82 <TrnRqUID>.....................5, 35, 39, 40, 87 <TrnSeqCntr>.........................................10 <TrnSrc>.............20, 29, 30, 70, 72, 76, 77 <TrnStatInfo>.........................................10 <TrnType>...20, 53, 70, 71, 76, 77, 80, 81, 82 <TruncatedInd>.......................................47 <TxSts>.........................................139, 141 <UnpredictNum>......................................9 <UpDt>....8, 14, 15, 16, 22, 23, 24, 35, 38, 39, 58, 62, 63, 64, 70, 71 <UpPayee>..............................................53 <URL>............7, 11, 13, 14, 18, 23, 44, 67 <USA.ACHProf>..................................329 <USA.ACHTrnInfo>....................3, 22, 47 <USA.MilitaryRank>..............................19 <USA.RTN>.......................................7, 22 <UTCOffset>............................................3 <UTCOffsetMinute>...........................9, 10 <Version>...............................6, 13, 18, 41 <ViewDtlPref>........................................11
Version 1.7
April 2005
C-27
<VoucherTypeId>.............................28, 31 <WebEnrollURL>.................................111 <XferAddRq>...................4, 122, 130, 137 <XferAddRs>............................4, 123, 133 <XferAdviseRq>...............................5, 135 <XferAdviseRs>...............................5, 135 <XferAudRq>...........................5, 131, 137 <XferAudRs>....................................5, 132 <XferCanRq>............................5, 126, 137 <XferCanRs>............................5, 127, 133 <XferFromSupt>.....................3, 24, 25, 26 <XferId>......3, 22, 25, 124, 125, 126, 127, 128, 129, 131, 132, 135, 136 <XferInfo>. 20, 24, 25, 122, 123, 124, 125, 138, 139, 140 <XferInqRq>.............................5, 128, 137 <XferInqRs>.....................................5, 129 <XferModRq>.....................5, 25, 123, 137 <XferModRs>.....................5, 37, 124, 133 <XferMsgRec>.............................132, 135 <XferMsgRqInfo>........................136, 137 <XferPayee>.................................7, 13, 15 <XferProf>........................25, 32, 328, 329 <XferRec>......25, 123, 125, 127, 130, 135, 136 <XferRevRq>....................................5, 136 <XferRevRs>............................5, 133, 137 <XferStatus>.............25, 26, 126, 135, 136 <XferStatusCode>...................27, 129, 130 <XferStatusModRq>.................5, 125, 137 <XferStatusModRs>.................5, 126, 133 <XferSyncRq>..........................5, 133, 137 <XferSyncRs>...................................5, 134 <XferToSupt>.........................3, 24, 25, 26
B-28
April 2005
Version 1.7

Ifx 1.7 - BMS

Uploaded by

Copyright:

Available Formats

Ifx 1.7 - BMS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ifx 1.7 - BMS

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What topics does this document cover?

What topics does this document cover?

Interactive Financial Exchange

Interactive Financial Exchange Business Message Specification

Interactive Financial Exchange Business Message Specification

3 COMMON ELEMENTS AND AGGREGATES.........................................................................................1

5 THE BASE SERVICE <BASESVC>.................................................................................................1

6 THE BANKING SERVICE <BANKSVC>...........................................................................................1

7 THE PAY SERVICE <PAYSVC>......................................................................................................1

8 THE BILL PRESENTMENT SERVICE <PRESSVC>..............................................................................1

9 THE VALUABLE MEDIA SERVICE <MEDIASVC>..............................................................................1

10 ROOT SERVICE <ROOTSVC>.....................................................................................................1

A RESPONSE STATUS CODES...........................................................................................................1

Interactive Financial Exchange Business Message Specification

1.1.1The IFX Business Message Specification

1.1.2IFX Implementation Specifications

1.3Benefits to Financial Institutions and Service Providers

1.4Benefits to Consumers and Businesses

Interactive Financial Exchange Business Message Specification

2.1.2Biller Payment Provider (BPP)

2.1.3Biller Service Provider (BSP)

2.1.6Customer Payment Provider (CPP)

2.1.7Customer Service Provider (CSP)

2.1.8Financial Institution (FI)

Service Provider (SP)

May, Should, and Must

Optional Element. Occurs zero or one times.

<Element1> <Element2> <Element1> <Element2> <Element1> <Element2>

Long Decimal Long Decimal Long Decimal

<Element1> <Element2> <Element1> <Element2>

Long Decimal Long Decimal

<Element3> <Element1> <Element2>

C-10 Long Decimal

Interactive Financial Exchange Business Message Specification

Interactive Financial Exchange Business Message Specification

2.3.4.1 Boolean Conventions and Selection Criteria

2.3.5YrMon, Date, Time, DateTime, and Timestamp

UTC offset Hours UTC offset Minutes (time zone indication)

Interactive Financial Exchange Business Message Specification

YrMon Data type

Time Data type

Optional but see Description

Interactive Financial Exchange Business Message Specification

Time Data type

Optional but see Description

Optional but see Description

Interactive Financial Exchange Business Message Specification

Interactive Financial Exchange Business Message Specification

The sign is always optional. If it is absent, the value is assumed to be positive.

<CurRate> and <CurConvertRule>

Interactive Financial Exchange Business Message Specification

2.3.10.1 Closed Enum

2.3.10.2 Open Enum

Universally Unique Identifier (UUID)

The following is an example of the string representation of a UUID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Interactive Financial Exchange Business Message Specification

2.4.2.1 External Aggregate