NCPDP Telecom TrxID determination

Transaction ID determination depends upon the message format. For NCPDP Telecom, the transaction ID consists of a transaction code and transmission type. For example, B1-REQUEST is generated for a billing request message and B1-RESPONSE is generated for the corresponding response.

Every NCPDP Telecom transaction has a REQUEST and RESPONSE form. Messages that are split from branches have additional fields from the batch header that are included in the transaction ID.

The included fields are Sender ID, File type (for example, text/production) and Receiver ID.

An underscore separates these fields in the transaction ID string.

The TrxID uses the form:

mm_tt_sender_ft_receiver
  • mm is the message type (for example, B1).
  • tt is the transmission type from the Transaction Header (T, R, or E).
  • sender is the sender ID from the Transaction Header.
  • ft is the file type from the Transaction Header (P or T).
  • receiver is the receiver ID from the Transaction Header.

For example:

B1-REQUEST_T_SENDERID_P_RECEIVERID
Note: For v1.0 batches, the receiver must be omitted from the TrxID.