Open the Portico Developer Guide site
PosGateway Schema
Details Element
PosGateway Schema > PosReportActivityRspType Complex Type : Details Element
Description

Report details sorted by DeviceId, TxnUtcDT

Note: If the data was defined in the request or response, a description has not been added here; only fields that are being introduced in this response have additional detail added. Typically, these will be fields that drive business logic that can be assumed at the time of the transaction or they are calculated at the time of the report.

Namespace http://Hps.Exchange.PosGateway
Diagram
x_global_transaction_id Element HasEMVTag Element EMVChipCondition Element UniqueDeviceId Element CredentialData Element ClerkID Element SettlementAmt Element AuthAmt Element TxnDT Element TzConversion Element Amt Element MaskedCardNbr Element IssuerRspText Element IssuerRspCode Element Status Element GatewayRspMsg Element GatewayRspCode Element SiteTrace Element OriginalGatewayTxnId Element TxnUtcDT Element GatewayTxnId Element ServiceName Element UserName Element DeviceId Element All Details Element
Overview
Details 0..∞

Report details sorted by DeviceId, TxnUtcDT

Note: If the data was defined in the request or response, a description has not been added here; only fields that are being introduced in this response have additional detail added. Typically, these will be fields that drive business logic that can be assumed at the time of the transaction or they are calculated at the time of the report.

All
DeviceId xs:int
UserName xs:string
ServiceName xs:string

This is the original request type (i.e. CreditSale)

TxnUtcDT xs:dateTime

Transaction response date time in UTC (Coordinated Universal Time)

OriginalGatewayTxnId txnIdType Simple Type

If the transaction performed an action on a previous transaction, this field records the transaction that was acted upon.

SiteTrace xs:string
GatewayRspCode xs:int

Gateway response code (issuer is separate)

GatewayRspMsg xs:string

Gateway response message

Status xs:string

The current transaction status at the time of the search.

These can vary, but some of the key status values include:

  • Active - 'A'
  • Closed - 'C'
  • Voided - 'V'
  • Inactive - 'I'
  • Reversed - 'R'

IssuerRspCode xs:string

Issuer response code

IssuerRspText xs:string

Issuer response text

MaskedCardNbr xs:string

This is the original transaction's card number, if any. It will contain the first six and last four digits with '*' filling in the middle. This value is safe for receipts and displays.

Amt amtTypeGlobal Simple Type

The original requested amount

TzConversion tzoneConversionType Simple Type

Time zone conversion applied to report results

TxnDT xs:dateTime

Transaction response date time in the time zone conversion requested

AuthAmt amtTypeGlobal Simple Type

The actual authorized amount

Note: This can be different from the original requested amount for partial authorizations.

SettlementAmt amtTypeGlobal Simple Type

The amount the transaction would settle for if it were closed as part of a batch

Note: This does not mean that it has or will close for this amount. The client controls this by adding it to the batch and closing the batch.

Note: This can be different from the original requested amount or the authorized amount for many reasons including: transaction edits (tip), reversals, additional authorizations, etc.

ClerkID optional xs:string
CredentialData optional CredentialDataType Complex Type

Credential details tied to a user session

Note: This is for internal use only.

All
DisplayName optional descriptionType Simple Type

User display name

ImpersonatedDisplayName optional xs:string

Impersonated user display name

UniqueDeviceId optional xs:string
EMVChipCondition optional xs:string
HasEMVTag optional xs:string

Indicates whether or not EMVTags were sent on this transaction; 'Y' indicates that it did and 'N' that it did not.

Source
<xs:element name="Details" minOccurs="0" maxOccurs="unbounded" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:annotation>
    <xs:documentation>
      <p xmlns="http://Hps.Exchange.PosGateway">Report details sorted by DeviceId, TxnUtcDT</p>
      <p xmlns="http://Hps.Exchange.PosGateway" />
      <p xmlns="http://Hps.Exchange.PosGateway">
        <strong>Note:</strong> If the data was defined in the request or response, a description has not been added here; only fields that are being introduced in this response have additional detail added. Typically, these will be fields that drive business logic that can be assumed at the time of the transaction or they are calculated at the time of the report.
            </p>
    </xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:all>
      <xs:element name="DeviceId" type="xs:int" />
      <xs:element name="UserName" type="xs:string" />
      <xs:element name="ServiceName" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">This is the original request type (i.e. CreditSale)</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="GatewayTxnId" type="txnIdType" />
      <xs:element name="TxnUtcDT" type="xs:dateTime">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Transaction response date time in UTC (Coordinated Universal Time)</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="OriginalGatewayTxnId" type="txnIdType">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">If the transaction performed an action on a previous transaction, this field records the transaction that was acted upon.</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="SiteTrace" type="xs:string" />
      <xs:element name="GatewayRspCode" type="xs:int">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Gateway response code (issuer is separate)</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="GatewayRspMsg" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Gateway response message</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Status" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">The current transaction status at the time of the search.</p>
            <p xmlns="http://Hps.Exchange.PosGateway">
                    These can vary, but some of the key status values include:
                    <ul><li>Active - 'A'</li><li>Closed - 'C'</li><li>Voided - 'V'</li><li>Inactive - 'I'</li><li>Reversed - 'R'</li></ul></p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="IssuerRspCode" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Issuer response code</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="IssuerRspText" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Issuer response text</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="MaskedCardNbr" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">This is the original transaction's card number, if any. It will contain the first six and last four digits with '*' filling in the middle. This value is safe for receipts and displays.</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Amt" type="amtTypeGlobal">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">The original requested amount</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="TzConversion" type="tzoneConversionType" default="UTC">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Time zone conversion applied to report results</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="TxnDT" type="xs:dateTime">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Transaction response date time in the time zone conversion requested</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="AuthAmt" type="amtTypeGlobal">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">The actual authorized amount</p>
            <p xmlns="http://Hps.Exchange.PosGateway" />
            <p xmlns="http://Hps.Exchange.PosGateway">
              <strong>Note:</strong> This can be different from the original requested amount for partial authorizations.
                  </p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="SettlementAmt" type="amtTypeGlobal">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">The amount the transaction would settle for if it were closed as part of a batch</p>
            <p xmlns="http://Hps.Exchange.PosGateway" />
            <p xmlns="http://Hps.Exchange.PosGateway">
              <strong>Note:</strong> This does not mean that it has or will close for this amount. The client controls this by adding it to the batch and closing the batch.
                  </p>
            <p xmlns="http://Hps.Exchange.PosGateway" />
            <p xmlns="http://Hps.Exchange.PosGateway">
              <strong>Note:</strong> This can be different from the original requested amount or the authorized amount for many reasons including: transaction edits (tip), reversals, additional authorizations, etc.
                  </p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ClerkID" type="xs:string" minOccurs="0" />
      <xs:element name="CredentialData" type="CredentialDataType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Credential details tied to a user session</p>
            <p xmlns="http://Hps.Exchange.PosGateway" />
            <p xmlns="http://Hps.Exchange.PosGateway">
              <strong>Note:</strong> This is for internal use only.
                  </p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="UniqueDeviceId" type="xs:string" minOccurs="0" />
      <xs:element name="EMVChipCondition" type="xs:string" minOccurs="0" />
      <xs:element name="HasEMVTag" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://Hps.Exchange.PosGateway">Indicates whether or not EMVTags were sent on this transaction; 'Y' indicates that it did and 'N' that it did not.</p>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="x_global_transaction_id" type="x_global_transaction_idType" minOccurs="0" />
    </xs:all>
  </xs:complexType>
</xs:element>
See Also
PosReportActivityRspType Complex TypePosGateway Schema