本文介绍了STAN编号可以重复且随机吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在开发具有某些存储库的连接器,并且我们正在使用ISO8583协议,现在,我将STAN(field 11)设置为使用随机数发生器生成的随机数,但有时我会有一些数问题是,我是否可以安全地使用此生成器,或者需要使STAN成为序列号?

I'm developing a Connector with some bank, and we're using the ISO8583 protocol, right now, i'm setting the STAN(field 11) with some random number generated with a random generator but sometimes I have some number collisions, the question is, could I safely use this generator or do I need to make the STAN a sequential number?

谢谢.

推荐答案

系统跟踪审核号(STAN)ISO-8583号具有不同的值,并且基本上在事务之间的关系之间维护.也就是说,它可以保持不变,或者同一笔交易在其交易路径上将有许多STAN,但在两个端点之间应该相同,并且通常由STAN使用谁来控制.

The System Trace Audit Number (STAN) ISO-8583 number has different values and is maintained basically between relationships within the transaction. That is it can stay the same or the same transaction will have many STANs over its transaction path but it SHOULD be the same between two end point and it is usually controlled in settings whos STAN to use.

例如:

终端->终端驱动程序->开关1->开关2->发卡器

Terminal -> Terminal Driver -> Switch 1->Switch 2->Issuer

STAN是由终端驱动程序分配的,然后对于以下关系至少保持不变...尽管对于每种关系可能会发生变化.

The STAN is say assign by the terminal driver and then remains constant at minimum for the following relationships... though may change for each relationship.

  • 终端驱动器-开关1
  • 开关1->开关2
  • 开关2->颁发者

请注意,STAN的每个系统内部也可能是唯一的,但它需要为每个关系保留唯一的STAN ..并且不应在请求和响应之间进行更改,因为多部分事务需要它(单项PA,多次完成和多项PA,单项完成),以及数据元素90中的冲销等.

Note that internally within each system to the STAN may be unique as well but it needs to keep a unique STAN for each relationship.. and it shouldn't change between the request and response as it is needed for multi-part transactions (Single PA, Multiple Completions & Multi-PA, Single Completion) as well as for reversals and such in Data Element 90.

这篇关于STAN编号可以重复且随机吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-13 21:09