ISO报文中，STAN和RRN有什么用？
In ISO message, what's the use of STAN and RRN?
在ISO报文中，STAN和RRN字段有什么用？此外，谁将在发送 ISO 消息时生成这些值？
STAN - 通常由您的网络接口生成，以使其在每个在线消息请求中都是唯一的。
RRN - 是与交易相关的参考，可以由 POS 系统、集成商环境生成，或者生成可以由 acquired/issuer 系统在授权界面后面完成。根据 RRN 生成方的不同，使其唯一（或在某些情况下保持相同）的责任可以在客户端或授权机构方。
这两个值都需要跟踪交易流并用于链式交易，如撤销、充值、完成等。
区别在于交易标识符的层次。
STAN 是网络层和消息引用。 RRN是客户的集成层和交易参考。
它们在实践中可以混合使用，具体取决于事务处理要求。例如 STAN 可以是 RRN 的一部分。
另一个好答案here。
STAN : System Trace Audit Number.
RRN : Retrieval reference number.
RRN is usually wider than the STAN thus giving the RRN more values
than the stan before it rolls over and restart the sequencing (asuming
the values are defined as numeric).
The usage of these varies from spec to spec. As an example one of the
may implementations possible, the stan could be a sequential per
transaction number. A transaction I would consider as a request
response pair (0100/0110 , 0200/0210, 0220/0230 etc).
The RRN can also be a sequential number but may remain constant across
the entire transaction associated with a card. So if you have a
0100/0110 followed by a completion 0220/0230, the rrn would remain the
same across these request response pairs. It helps you to link the
transactions, so when the 0220 comes in you can look up the original
0100 by using the rrn. A similar thing can be done for reversals too
0200/0210 followed by a 0420/0430).
在ISO报文中，STAN和RRN字段有什么用？此外，谁将在发送 ISO 消息时生成这些值？
STAN - 通常由您的网络接口生成，以使其在每个在线消息请求中都是唯一的。
RRN - 是与交易相关的参考，可以由 POS 系统、集成商环境生成，或者生成可以由 acquired/issuer 系统在授权界面后面完成。根据 RRN 生成方的不同，使其唯一（或在某些情况下保持相同）的责任可以在客户端或授权机构方。
这两个值都需要跟踪交易流并用于链式交易，如撤销、充值、完成等。
区别在于交易标识符的层次。 STAN 是网络层和消息引用。 RRN是客户的集成层和交易参考。
它们在实践中可以混合使用，具体取决于事务处理要求。例如 STAN 可以是 RRN 的一部分。
另一个好答案here。
STAN : System Trace Audit Number.
RRN : Retrieval reference number.
RRN is usually wider than the STAN thus giving the RRN more values than the stan before it rolls over and restart the sequencing (asuming the values are defined as numeric).
The usage of these varies from spec to spec. As an example one of the may implementations possible, the stan could be a sequential per transaction number. A transaction I would consider as a request response pair (0100/0110 , 0200/0210, 0220/0230 etc).
The RRN can also be a sequential number but may remain constant across the entire transaction associated with a card. So if you have a 0100/0110 followed by a completion 0220/0230, the rrn would remain the same across these request response pairs. It helps you to link the transactions, so when the 0220 comes in you can look up the original 0100 by using the rrn. A similar thing can be done for reversals too 0200/0210 followed by a 0420/0430).