Page last modified 16:08, 8 Mar 2013 by Antero

EndToEndId

    Table of contents
    No headers

     

    ISO20022 describes EndToEndId as follows:

    Presence:  [1..1]
    Definition:  Unique identification assigned by the initiating party to unumbiguously identify the transaction. This 
    identification is passed on, unchanged, throughout the entire end-to-end chain.
    Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. 
    It can be included in several messages related to the transaction.
    Data Type:  Max35Text, Format:  maxLength: 35, minLength: 1
     
    It's worth noting that the uniqueness combined with element being mandatory can bring certain problems. A common workaround is to allow element to be filled with value NOTPROVIDED. Stuzza allows the usage of value NOTPROVIDED.
     

    Example:

    <PmtInf>
    <CdtTrfTxInf> 
       <EndToEndId>1</EndToEndId>
    </CdtTrfTxInf>
    </PmtInf>
    <PmtInf>
    <CdtTrfTxInf> 
       <EndToEndId>2</EndToEndId>
    </CdtTrfTxInf>
    <CdtTrfTxInf> 
       <EndToEndId>NOTPROVIDED</EndToEndId>
    </CdtTrfTxInf>
    <CdtTrfTxInf> 
       <EndToEndId>NOTPROVIDED</EndToEndId>
    </CdtTrfTxInf>
    <PmtInf>

    (Various elements have been removed for the sake of the example)

    The example is in valid format.

    Menu