In ISO message, what's the use of stan and rrn fields ? Also who will generate the these values while sending ISO messages?
相关问题
- Packing SUBFIELDS using jpos api
- In ISO message, what's the use of stan and rrn
- How to configure jpos channel header with spaces
- Generating MAC by encrypting data
- ISO8583 for Amex
相关文章
- In ISO message, what's the use of stan and rrn
- 太多的文件使用外部packager.xml文件通用包装机打开时(Too many files ope
- How to configure jpos channel header with spaces
- Generating MAC by encrypting data
- ISO8583 for Amex
- Iso8583 message encoding and decoding [closed]
- How should jPOS be configured/used in a prod envir
- Understanding ISO 8583 messaging log
Another good answer here.
STAN - usually generated by your network interface to make it unique per online message request.
RRN - is the transaction related reference and can be generated by POS system, Integrator environment or the generation can be done behind the authorisation interface by the acquired/issuer systems. Depending of RRN generation side the responsibility to make it unique (or keep same for some cases) can be at the client side or at the authorisation institutions side.
Both values required to trace the transaction flows and used for chained transactions like Reversal, Top-Up, Completion, etc.
The difference is the layer of the transaction identifier. STAN is the network layer and message reference. RRN is the customer's integration layer and transaction reference.
They can be mixed in practice, depending of transaction processing requirements. For sample STAN can be a part of RRN.