ISO 8583 defines the Card originated messages.
In FCR, cod_msg_tye in td_nobook, ch_nobook stores the transaction message's type.
ISO defines message types as below:
A. 200: Normal
B. 220: advice (also called force post)
C. 400: reversal
D. 420: advice reversal (also called force post reversal)
FCR has one more:
E. 401: auto-reversal.
Seems there are other types of message in the ISO 8583, please ｒｅｆｅｒｅｎｃｅ:
http://en.wikipedia.org/wiki/ISO_8583#Message_class.
When two systems communicate with messages, they can use the common request-response protocol. System 1 sent a message to System 2 (called a request), and System 2 replies back to System 1 (response). System 1 need not wait for any response and can keep sending requests, and Sytsems will keep replying as and when it's able to reply.
Requests are indicated with message type and every message has an id, call it REF_STAN.
There are cases where you would want to reverse a request. This is message with type 400, also you have to indicate which is the message that you are requesting for reversing, which is indicated by REF_ORG_STAN.
There are also time out problems to handler.
For example, three messages as below:
MSG_TYPE = 200, REF_STAN =1
MSG_TYPE = 400, REF_STAN=2, REF_ORG_STAN = 1
MSG_TYPE = 401, REF_STAN=3, REF_ORG_STAN = 2
If the MSG_TYPE is 420/220, it means it can't be rejected. ..
In FCR, there is another concept as same-day reverse transaction. Currently, I take it as the same as reversal transaction.
In FCR, cod_msg_tye in td_nobook, ch_nobook stores the transaction message's type.
ISO defines message types as below:
A. 200: Normal
B. 220: advice (also called force post)
C. 400: reversal
D. 420: advice reversal (also called force post reversal)
FCR has one more:
E. 401: auto-reversal.
Seems there are other types of message in the ISO 8583, please ｒｅｆｅｒｅｎｃｅ:
http://en.wikipedia.org/wiki/ISO_8583#Message_class.
When two systems communicate with messages, they can use the common request-response protocol. System 1 sent a message to System 2 (called a request), and System 2 replies back to System 1 (response). System 1 need not wait for any response and can keep sending requests, and Sytsems will keep replying as and when it's able to reply.
Requests are indicated with message type and every message has an id, call it REF_STAN.
There are cases where you would want to reverse a request. This is message with type 400, also you have to indicate which is the message that you are requesting for reversing, which is indicated by REF_ORG_STAN.
There are also time out problems to handler.
For example, three messages as below:
MSG_TYPE = 200, REF_STAN =1
MSG_TYPE = 400, REF_STAN=2, REF_ORG_STAN = 1
MSG_TYPE = 401, REF_STAN=3, REF_ORG_STAN = 2
If the MSG_TYPE is 420/220, it means it can't be rejected. ..
In FCR, there is another concept as same-day reverse transaction. Currently, I take it as the same as reversal transaction.