6.1.1 PTI XML (NRT) Template 1
Source: TI_Host_to_Host_Client_User_Manual_v52.pdf
Document pages: 84-86
PDF pages: 84-86
Appendix A
Herewith the layout for the standard XML transaction feeds for near real time:
TI PTI XML (NRT) field lengths are variable and indicated below are maximum lengths XML Tag name Data type Expected Maximum size Description Sample value
| <CISNumber> Numeric 12 Unique client number
issued by Nedbank 1234
<ProfileNumber> Numeric 10 Profile number on which
the PTI product is setup 30000000014
<Product> Alpha Numeric 10
|
Will contain the value PTI to indicate it is a provisional transaction file
PTI
| <InstanceNumber> Numeric 4
|
You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination
1234
| <InstanceName> Alpha Numeric 30 Instance name as
specified by the client ADMIN
<Date> Numeric 8
|
Displays the date on which the file is being sent. CCYYMMDD 20140916
HEADER (Example)
| <Header><CISNumber>1234</CISNumber><ProfileNumber>30000000014</ProfileNumber><Product>Product</Pro
duct><InstanceNumber>1234</InstanceNumber><InstanceName>ADMIN</InstanceName><Date>20130130</Date>
</Header>
|
TI PTI XML (NRT) field lengths are variable and indicated below are maximum lengths XML Tag name Data Type Expected Maximum size Description Sample value
Alpha N/A Start of XML body N/A
| <TransactionKey> Numeric 16
Each PTI transaction is allocated a unique key. If you receive the same transaction key on another PTI message then it will be for the same transaction ie the key is not unique across TI products 1
<ProcessKey> Alpha Numeric 9
|
Uniquely identifies the current client preferences for this transaction. This value is for internal purposes and does not have to be interpreted by you in processing this 0001
transaction.
| <ResendKey> Numeric 9
Any value greater than zero means that the transaction was resent. It will have the same transaction key as the initial transaction. 1
<DestinationKey> Numeric 9
If a single instance has more than one destination address it will have different destination keys. In the case of using Web Service only one destination address is allowed per instance 0012
<Account> Numeric 23
The account number on which the transaction was processed. 1009000951
<TranType> Alpha Numeric 30
This field indicates the type of transaction eg Cash or Cheque. Refer to no 3.8 for a list of Channel and Transaction type combinations C Deposit
<Channel> Alpha Numeric 30
Indicates the channel through which the transaction was processed eg Teller. Refer to no 3.8 for a list of Channel and Transaction type combinations INTERNET BANKING
<Amount> Numeric 16.2 The amount of the
transaction -141.11
<DebitCredit> Alpha 2
Is the transaction a debit (Money out) or credit (Money in) to the account which is being reported on? Values are indicated by; D=Debit, C=Credit, RD=Reversal of Debit, RC=Reversal of Credit RD
<Date> Numeric 8
The date on which the transaction was processed to the account. Format - 20140916
<Time> Alpha Numeric 11
Time at which the provisional transaction was processed to the account. Format - 12:34:28:33
<AccountBookBalance> Numeric 16.2
|
Actual account balance including any uncleared funds (eg cheque deposits -7 days clearance).
622000.54 Numeric 16.2 Actual account balance plus account overdraft limit less any uncleared funds
635406.46
| <UserRef> Alpha Numeric 30 Statement description /
|
narrative NarrText 0899
Alpha End of XML body
BODY (Example)
| <TIRecord><TransactionKey>1</TransactionKey><ProcessKey>0001</ProcessKey><ResendKey>1200</ResendKe
y><DestinationKey>0012</DestinationKey><Account>1009000951</Account><TranType>C
Deposit</TranType><Channel>INTERNET BANKING</Channel><Amount>-
|
| 141.11</Amount><DebitCredit>RD</DebitCredit><Date>20130916</Date><Time>12:34:28:33</Time><AccountBook
Balance>622000.54</AccountBookBalance><AccountAvailableBalance>635406.46</AccountAvailableBalance><Use
rRef>NarrText 0899</UserRef></TIRecord>
|
TI PTI XML (NRT) field lengths are variable and indicated below are maximum lengths XML Tag name Data type Expected Maximum size Description Sample value
| <RecordCount> Numeric 18
Number of <TI records>
|
in the file ie excluding header and footer 3
FOOTER (Example)
| <RecordCount>3</RecordCount>
|
PTI XML layout - near real time.txt
Sample file layout
| <?xml version="1.0"?>
<TIRequest>
<Header><CISNumber>1234</CISNumber><ProfileNumber>30000000014</ProfileNumber><Product>Product</Pr
oduct><InstanceNumber>1234</InstanceNumber><InstanceName>ADMIN</InstanceName><Date>20130130</Da
te></Header>
<TIRecord><TransactionKey>1</TransactionKey><ProcessKey>0001</ProcessKey><ResendKey>1200</Resend
Key><DestinationKey>0012</DestinationKey><Account>1009000951</Account><TranType>C
Deposit</TranType><Channel>INTERNET BANKING</Channel><Amount>-
141.11</Amount><DebitCredit>RD</DebitCredit><Date>20130916</Date><Time>12:34:28:33</Time><AccountBo
okBalance>622000.54</AccountBookBalance><AccountAvailableBalance>635406.46</AccountAvailableBalance>
<UserRef>NarrText 0899</UserRef></TIRecord>
<TIRecord><TransactionKey>2</TransactionKey><ProcessKey>0001</ProcessKey><ResendKey>1200</Resend
Key><DestinationKey>0012</DestinationKey><Account>1009000951</Account><TranType>C
Deposit</TranType><Channel>INTERNET
BANKING</Channel><Amount>141.11</Amount><DebitCredit>D</DebitCredit><Date>20130916</Date><Time>1
2:37:28:33</Time><AccountBookBalance>622000.54</AccountBookBalance><AccountAvailableBalance>635406.
46</AccountAvailableBalance><UserRef>NarrText 0899</UserRef></TIRecord>
<TIRecord><TransactionKey>1234565781</TransactionKey><ProcessKey>0001</ProcessKey><ResendKey>120
0</ResendKey><DestinationKey>0012</DestinationKey><Account>1234567890</Account><TranType>Cash
</TranType><Channel>N/A</Channel><Amount>1000.00</Amount><DebitCredit>D</DebitCredit><Date>2013013
0</Date><Time>00:00:00:00</Time><AccountBookBalance>1002.00</AccountBookBalance><AccountAvailableBa
lance>1001.00</AccountAvailableBalance><UserRef>Deposit/EFT narrative</UserRef></TIRecord>
<RecordCount>3</RecordCount>
</TIRequest>
|