Requirements for XML Files per Rail

this section describes the xml file requirements for the following payment methods (rails) book transfer docid 64d jmuzssorhycjjn53 ach ccd/ppd docid\ htbnipwi9pr0u5djwxr0z fedwire docid\ zjziz54nqtoifgkwjtmx direct debit docid 9do0r7gsk3c0jersf4evs rtp/fednow docid\ z03rqu0m gbschwbybcij for more information on the code structure for each payment method, see the corresponding topic in the xml input file examples docid\ tguu7g7b9mco2rbyohw m section see preparing your input xml file docid\ uijcdsocfdnah0jrtvq e for more details on the blocks and tags used in the xml examples below book transfers for book transfers (among 2 accounts within cr) both the dbtragt block and the cdtragt block must contain cr's routing number (021214891) in the mmbid element ach push ccd for ach push ccd transfers, the pmttpinf block must be according to the following example \<pmttpinf> \<instrprty>norm\</instrprty> \<svclvl> \<cd>nurg\</cd> \</svclvl> \<lclinstrm> \<prtry>ccd\</prtry> \</lclinstrm> \</pmttpinf> all the above fields are required we validate for these fields in order to know what type of transaction you are requesting if we can’t find any of these, it will cause an error ach push ppd for ach push ppd transfers, the pmttpinf block must be according to the following example \<pmttpinf> \<instrprty>norm\</instrprty> \<svclvl> \<cd>nurg\</cd> \</svclvl> \<lclinstrm> \<prtry>ppd\</prtry> \</lclinstrm> \</pmttpinf> all the above fields are required we validate for these fields in order to know what type of transaction you are requesting if we can’t find any of these, it will cause an error fedwire for fedwire payments the cdtragt 's mmbid value must be different than cr's routing number (021214891) \<cdtragt> \<fininstnid> \<clrsysmmbid> \<clrsysid> \<cd>usaba\</cd> \</clrsysid> \<mmbid>123456789\</mmbid> \</clrsysmmbid> \<nm>the bank of new york mellon\</nm> \<pstladr> \<ctry>us\</ctry> \</pstladr> \</fininstnid> \</cdtragt> the pmttpinf 's cd value must be "urgp" \<pmttpinf> \<instrprty>norm\</instrprty> \<svclvl> \<cd>urgp\</cd> \</svclvl> \</pmttpinf> ach direct debits (ach pull) for ach direct debits the file type must be xml pain 008 001 02 iso 20022 \<?xml version="1 0" encoding="utf 8" ?> \<document xmlns="urn\ iso\ std\ iso 20022\ tech\ xsd\ pain 008 001 02"> the payment method ( pmtmtd ) value must be “dd” \<pmtinf> \<pmtmtd>dd\</pmtmtd> \<pmtinf> the creditor agent ( cdtragt )'s member id ( mmbid ) value must always be cr's routing number (021214891) \<cdtragt> \<fininstnid> \<clrsysmmbid> \<mmbid>021214891\</mmbid> \</clrsysmmbid> \</fininstnid> \</cdtragt> the payment type information must include the service level code of “nurg” and the local instrument proprietary value, which is the ach pull type (“ccd” or “ppd”) \<pmttpinf> \<svclvl> \<cd>nurg\</cd> \</svclvl> \<lclinstrm> \<prtry>ccd\</prtry> \</lclinstrm> \</pmttpinf> for example \<pmtinf> \<pmtmtd>dd\</pmtmtd> \<pmttpinf> \<svclvl> \<cd>nurg\</cd> \</svclvl> \<lclinstrm> \<prtry>ccd\</prtry> \</lclinstrm> \</pmttpinf> \<cdtragt> \<mmbid>021214891\</mmbid> \</cdtragt> \</pmtinf> all the fields shown above for direct debit are required so that we can identify the payment type and details rtp send (push) funds this is how you should structure your xml for sending funds using rtp \<pmttpinf> \<instrprty>norm\</instrprty> \<svclvl> \<cd>urns\</cd> \</svclvl> \<lclinstrm> \<prtry>rtp\</prtry> \</lclinstrm> \</pmttpinf>