CLOSE_TAB
Last updated: 09-Dec-2024
This command closes a customer tab by performing a completion to PWC using an existing CTROUTD. Close Tab message specification is identical to Capture.
Device UI Required: Yes
Request Packet
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| FUNCTION_TYPE | Required | Static value | N/A | N/A | PAYMENT | Type of function |
| COMMAND | Required | Static value | N/A | N/A | CLOSE_TAB | Command name |
| TRANS_AMOUNT | Required | Floating point number | 1(2) | 6(2) | Total transaction amount (including any TIP_AMOUNT). Example: 5.35 | |
| TIP_AMOUNT | Optional | Floating point number | 1(2) | 6(2) | This indicates to send the TIP amount. Example: 1.00 | |
| POS_RECON | Optional | Conditional | 1 | 30 | POS Reconciliation field to be echoed back in response to POS. Example: RetailPOS1 | |
| EBTCASH_ELIGIBLE | Optional | Floating point number | 1(2) | 6(2) | Amount eligible for Cash Benefits EBT. When this field is present, SCA displays EBT payment button. Example: 5.00 | |
| EBTSNAP_ELIGIBLE | Optional | Floating point number | 1(2) | 6(2) | Amount eligible for Food Stamp EBT. When this field is present, SCA displays EBT payment button. Example: 5.00 | |
| EBT_VOUCHER_NUM | Optional | Conditional | 0 | 15 | This field is used to send EBT voucher number. This is an optional field for EBT Post Auth/Force transaction. Example: 2222222 | |
| PAYMENT_TYPE | Conditional | List | N/A | N/A | CREDIT DEBIT GIFT EBT CHECK_SALE/ CHECK_VERIFY (For Check Processing) Alipay/Klarna/WeChat/PayPal/Venmo(for APM) |
This field is required when CTROUTD is sent. Else this is an OPTIONAL field. When this field is present, the application will bypass the consumer payment selection screen. PAYMENT_TYPE field is mandatory for card token based transactions. |
| PAYMENT_SUBTYPE | Optional | List | N/A | N/A | This indicates to send with payment types of GIFT and PRIV_LBL. Example: BLACKHAWK | |
| EBT_TYPE | Optional | List | N/A | N/A | FOOD_STAMP CASH_BENEFITS |
This is required for EBT transactions. |
| AUTH_CODE | Conditional | Character | 1 | 16 | When this field is present, the capture is performed offline as a POST_AUTH. Vantiv Direct allows maximum 6 bytes. This is not supported by FD RC in Point Classic implementation. Example: TA1260 | |
| MANUAL_ENTRY | Optional | Boolean | N/A | N/A | TRUE or FALSE | This instructs application to collect the account information through the keypad on the device. |
| CUSTOMER_STREET | Optional | Character | 1 | 20 | This is applicable when MANUAL_ENTRY = TRUE. Merchants should send this field only when required by the processor. Not required for customers using Point Gateway services. | |
| CUSTOMER_ZIP | Optional | Character | 9 | This is applicable when MANUAL_ENTRY = TRUE. Merchants should send this field only when required by the processor. Not required for customers using Point Gateway services. | ||
| MANUAL_PROMPT_OPTIONS | Optional | Character | 1 | 50 |
|
This is applicable when MANUAL_ENTRY = TRUE and payment type is Credit Card. When this is present, SCA will prompt for customer zip code and/or not prompt for CVV value. The zip code that is entered will be returned in the CUSTOMER_ZIP field in the response. |
| PAYMENT_TYPES | Optional | Character | 3 | CREDIT|DEBIT|GIFT|FSA | Pipe-delimited list of valid tender types (for capture/refund transactions) specified by POS. Only listed payment types will appear on consumer payment selection screen. All included tender types must be configuration enabled. | |
| POS_TENDER1 | Optional | Character | 8 | POS-defined tender for SCA dynamic display. This will be truncated on display if >8 char. For example: STORE CREDIT will display as STORE CR. As of this publication POS-defined tender only supported by Point Classic implementations. | ||
| TENDER1_ACTION | Optional | List | N/A | N/A | CARD DATA (Track II data) NOTIFICATION (NOTIFICATION only) |
POS-defined action |
| POS_TENDER2 | Optional | Character | See POS_TENDER1. Example: ACME GIFT CARD | |||
| TENDER2_ACTION | Optional | List | N/A | N/A | See TENDER1_ACTION. Example: NOTIFICATION | |
| POS_TENDER3 | Optional | Character | See POS_TENDER1. Example: CHECK | |||
| TENDER3_ACTION | Optional | List | N/A | N/A | See TENDER1_ACTION. Example: NOTIFICATION | |
| CTROUTD | Conditional | Numeric | 1 | 16 | When this field is present, Point will mark the referenced transaction as eligible for settlement (performed with the COMPLETION command). CTROUTD is a sequence number for PAYMENT transactions (always enabled) that is generated per Client ID. Each Client ID has its own CTROUTD sequence counter. This is applicable for Credit card only. This is not supported by FDRC in Point Classic RVE006 implementation. Example: 1234567 | |
| RECURRING | Optional | Boolean | N/A | N/A | Yes or No | This is used when Payment Type is Credit. This field denotes Recurring Billing Flag to indicate the transaction is recurring. This is applicable to UGP only. |
| BILLPAY | Optional | Boolean | N/A | N/A | TRUE or FALSE | This is used to indicate a bill payment. This is applicable to UGP and Vantiv Direct. |
| FORCE_FLAG | Conditional | Boolean | N/A | N/A | TRUE or FALSE | This field is used to override duplicate checking for the transaction. |
| CAPTURECARD_EARLYRETURN | Optional | Boolean | N/A | N/A | TRUE or FALSE | If the sending value is TRUE, then the application returns card data to POS before processing. PCI BIN checking in place to return full PAN or masked PAN BIN range level. SCA will cache data from the swipe, but will only use in immediately subsequent CAPTURE request containing explicit tender type – else, it will discard. |
| ENCRYPT | Conditional | Boolean | N/A | N/A | TRUE or FALSE | This field is required to encrypt the PAN details before passing it on to processor/gateway. In case of P2PE encryption, this field needs to be set to TRUE as value. If this field is not present, then the application will internally treat this field as a value TRUE when the device encryption is ADE/VSD. |
| SCMCI_INDICATOR | Optional | Numeric | 2 | This field denotes the Stored Credential Transaction Indicator. The acceptable value for this field as of this publication is 2 which signifies that it is a cardholder initiated transaction. | ||
| CDD_DATA | Optional | Character | 1 | 30 | Customer Defined Data. This field is optional and the datatype is String. It is a pass through field and it is passed in the host request if this field is present in the POS request and also returned in POS response. This field is applicable for all payment transactions. Example: <CDD_DATA>INV200471</CDD_DATA> |
|
| COL_3, COL_4, COL_5, COL_6, COL_7, COL_8, COL_9, COL_10 | Optional | Character | 1 | 255 | These fields represent Column 3 to Column 10. These fields are expected for the Merchants internal POS System, which will record any additional data and link those to the PWC CLIENT_ID and CTROUTD. When a value for COL_n is passed in, that same value will be returned in the response. These COL_n values are not indexed, or searchable in any command report. These fields are not sent to any payment processor. Example: Merchant defined data | |
| COUNTER | Required | Numeric | 1 | 10 | COUNTER is used for a given MAC label. Each COUNTER should be higher than the last one. Used to authenticate the POS. Example: 100 | |
| MAC | Required | Base64 Encoded Data | Message Authentication Code. Used to authenticate the POS | |||
| MAC_LABEL | Required | Character | 1 | 50 | Associated label that tells the device which MAC_KEY to use to decrypt the value of MAC. This is used to authenticate the POS. Example: REG1 |
Level II Transaction
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| TAX_AMOUNT | Conditional | Floating point number | 1(2) | 6(2) | Tax amount. Example: 5.00 | |
| TAX_IND | Conditional | List |
|
Tax indicator | ||
| CMRCL_FLAG | Conditional | List |
|
Commercial flag | ||
| CUSTOMER_CODE | Conditional | Character | 1 | 25 | Customer code | |
| RETAIL_ITEM_DESC_1 | Conditional | Character | 1 | 40 | Default is (empty) | Items description. |
| ALLOW_DUP_TRAN | Conditional | Character | 1 | 40 | ALLOW_DUP_TRAN field is required to send if the previous CAPTURE transaction in the same session was declined as “DUPLICATE TRANSACTION”. The user needs to add ALLOW_DUP_TRAN tag (with value same as the INVOICE of current transaction) with the current CAPTURE command in order to override the duplicate detection and process the transaction with the card details from previous transaction. |
Keyed Account Information for Gift Card and Credit Card Payment Types Only
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| ACCT_NUM | Optional | Numeric | 1 | 25 | Ex: 67823456781313 |
|
| CARD_EXP_MONTH | Optional | Numeric | 2 | 2 | Card expiry month. Example: 12 | |
| CARD_EXP_YEAR | Optional | Numeric | 2 | 2 | Card expiry year. Example: 49 | |
| BARCODE | Optional | Character | 1 | 100 | Barcode scanning option. | |
| PIN_CODE | Optional | Numeric | 1 | 10 | PIN code. | |
| CVV2 | Optional | Numeric | 1 | 10 | Card Verification Value 2. |
FSA/HSA (Payment type CREDIT only)
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| AMOUNT_HEALTHCARE | Conditional | Floating point number | 1(2) | 6(2) | Total FSA-eligible amount. This is required for FSA. Example: 5.00 | |
| AMOUNT_PRESCRIPTION | Optional | Floating point number | 1(2) | 6(2) | FSA-eligible prescription amount. Example: 2.00 | |
| AMOUNT_VISION | Optional | Floating point number | 1(2) | 6(2) | FSA-eligible vision amount. Example: 1.00 | |
| AMOUNT_CLINIC | Optional | Floating point number | 1(2) | 6(2) | FSA-eligible clinic amount. Example: 1.00 | |
| AMOUNT_DENTAL | Optional | Floating point number | 1(2) | 6(2) | FSA-eligible dental amount. Example: 1.00 |
Checks (Payment type CHECK_SALE or CHECK_VERIFY)
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| MICR | Conditional | Character | 128 | Check transactions with MICR. As of RCHI 1.00.10 B4, if this is sent, then the transaction will process as Telecheck ECA. For FDRC, the maximum length for MICR is 113. Example: T999999992T1234567890111O3241 | ||
| ABA_NUM | Conditional | Numeric | 10 | Required if MICR not sent. Example: 123456789 | ||
| ACCT_NUM | Conditional | Numeric | 6 | 10 | Required if MICR not sent. Example: 656565656565 | |
| CHECK_NUM | Conditional | Numeric | 10 | Required if MICR not sent. Example: 1234 | ||
| CHECK_TYPE | Optional | List | 0 - Personal (default) 1 - Business/Company 2 - Payroll 3 - Government |
Check type. Example: For FDRC, value 0 and 1 are applicable only. | ||
| DL_STATE | Optional | Character | 2 | 2 | Driver’s license state abbreviation. Example: CA | |
| DL_NUMBER | Optional | Character | 1 | 12 | Driver’s license number. For FDRC, the maximum length for DL_NUMBER is 37. Example: A1234567 | |
| CUSTOMER_DOB | Optional | Numeric | 8 | 8 | Date of Birth (MMDDYYYY). Example: 01281974 | |
| ECA_BILL_NUM | Optional | Numeric | 1 | 25 | ECA bill number. This is a Host specific field for FDRC. Example: ECABCN |
h6-start| Checks (Payment type CHECK_SALE or CHECK_VERIFY)
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| CREDIT_PLAN_NBR | Conditional | Numeric | 1 | 15 | Credit plan number, as required by processor. This is applicable for Completion transaction. Example: T999999992T1234567890111O3241 |
Processor-Based Token (Conditional)
Note
For use with host based processors supporting card based token implementations.
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| CARD_TOKEN | Conditional | Character | 1 | 40 | Card token is processor-based or gateway-based and can represent a unique card. Example: 7987654321098765 | |
| CARD_EXP_MONTH | Conditional | Numeric | 2 | 2 | Card expiry month details are required when sending AUTH_CODE and CARD_TOKEN. This is applicable to Point SCA First Data Rapid Connect and Direct to Vantiv implementations only. | |
| CARD_EXP_YEAR | Conditional | Numeric | 2 | 2 | Card expiry year details are required when sending AUTH_CODE and CARD_TOKEN. This is applicable to Point SCA First Data Rapid Connect and Direct to Vantiv implementations only. | |
| BANK_USERDATA | Conditional | Character | 1 | 50 | Returned with CARD_TOKEN. Whatever comes back with BANK_USERDATA in the response for the token should also be sent in the request. Example: 01/00/02/Visa/ | |
| OC_INDUSTRY_CODE | Conditional | Character | 1 | 1 | E - eCommerce M - Moto Default is empty. |
This is used to convert a transaction from the Merchants default industry of Retail or Restaurant to E-Commerce or MOTO. This is applicable in case of UGP host only. |
Preset Counter Tip
Note
This section is applicable for CAPTURE, COMPLETION, CLOSE_TAB, FORCE transactions.
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| PRESET_TIP_AMOUNT1 | Optional | Floating point number | 1(2) | 6(2) | Preset counter TIP amount 1. Maximum value possible would be 999999.99$. Example: 4.00 | |
| PRESET_TIP_AMOUNT2 | Optional | Floating point number | 1(2) | 6(2) | Preset counter TIP amount 2. Maximum value possible would be 999999.99$. Example: 2.00 | |
| PRESET_TIP_AMOUNT3 | Optional | Floating point number | 1(2) | 6(2) | Preset counter TIP amount 3. Maximum value possible would be 999999.99$. Example: 1.00 | |
| PRESET_TIP_AMOUNT4 | Optional | Floating point number | 1(2) | 6(2) | Preset counter TIP amount 4. Maximum value possible would be 999999.99$. Example: 0.20 | |
| PRESET_TIP_PCT1 | Conditional | Numeric | 1 | 3 | This field must be present if PRESET_TIP_AMOUNT1 is present. Maximum value is 100. Example: 20 | |
| PRESET_TIP_PCT2 | Conditional | Numeric | 1 | 3 | This field must be present if PRESET_TIP_AMOUNT2 is present. Maximum value is 100. Example: 10 | |
| PRESET_TIP_PCT3 | Conditional | Numeric | 1 | 3 | This field must be present if PRESET_TIP_AMOUNT3 is present. Maximum value is 100. Example: 5 | |
| PRESET_TIP_PCT4 | Conditional | Numeric | 1 | 3 | This field must be present if PRESET_TIP_AMOUNT4 is present. Maximum value is 100. Example: 1 |
Response Packet
| Field | Type | Value | Description |
|---|---|---|---|
| RESPONSE_TEXT | Character | SUCCESS/ APPROVAL(VHI)/ APPROVED(RCHI and CPHI) |
Processor response text. Example: TIP MODIFIED :A :AP |
| RESULT | Character | Commonly CAPTURED or DECLINED. Example: SUCCESS (CPHI) or CAPTURED (VHI) or APPROVED (RCHI) or DECLINED | |
| RESULT_CODE | Numeric | Expected result code: 4, 5, 6, 59074 | This indicates the result code. |
| RESPONSE_CODE | Character | A or E | Response code data will be returned to POS, same as received from the Host if this is present in Host response. Example: <RESPONSE_CODE>E</RESPONSE_CODE> |
| TERMINATION_STATUS | Character | SUCCESS or FAILURE | This indicates the transaction termination status. This is the overall status of the transaction irrespective of approved or declined. Like, if the output is generated then the status is SUCCESS and if no output is generated then the status will be FAILURE. |
| COUNTER | Numeric | Echoes counter sent in the request. Example: 100 | |
| TROUTD | Numeric | Transaction routing ID (not meaningful for direct host integrations). Example: 000042 | |
| CTROUTD | Numeric | CTROUTD is a sequence number for PAYMENT transactions (always enabled) that is generated per Client ID. Each Client ID has its own CTROUTD sequence counter. For private label transaction (ADS), PT_CTROUTD field will be mapped to CTROUTD field back to SCA. In case of APM transaction, if this field is present, then order ID will be received from alternate payment method. For example, Alipay, Klarna, WeChat, PayPal, Venmo. Example: 028660198 | |
| TRANS_SEQ_NUM | Numeric | Processor/Batch trans sequence number (not meaningful for direct host integrations). For private label transaction (ADS), PT_SEQ_NUM field will be mapped to TRANS_SEQ_NUM and TROUTD fields back to SCA. Example: 000042 | |
| INTRN_SEQ_NUM | Numeric | PWC transaction ID (not meaningful for direct host integrations). Example: 000042 | |
| LPTOKEN | Numeric | LP Token is a non-sensitive unique number assigned to each unique card number processed with the UGP gateway. This value will automatically increment by one for each unique card number. This is a conditional field. Example: 12357 | |
| PAYMENT_TYPE | Character | Ex: CREDIT | Type of payment. PAYMENT_TYPE field will return the value, if this is entered in capture request. Example: CREDIT, DEBIT, APM, CHECK |
| PAYMENT_MEDIA | Character | Commonly VISA/MC/DISC/AMEX/DEBIT | Mode of payment |
| MERCHID | Numeric | Merchant ID. Example: 900000000123 | |
| TERMID | Numeric | Terminal ID. Example: 001 | |
| SERVER_ID | Numeric | Echoes what is sent in START request. Example: 10 | |
| CASHIER_ID | Character | Echoes what is sent in START request. Example: 10 | |
| EBT_TYPE | Character | FOOD_STAMP or CASH_BENEFITS | Indicates processed EBT transaction. |
| ACCT_NUM | Numeric | Returned masked account number. Example: 400555******0019 | |
| ACCOUNT_TYPE | Character | CHECKING/SAVINGS | Indicates the type of debit account based on the selection on the customer. |
| AUTH_CODE | Character | Processor authorization number. Example: TA01561 | |
| AVAILABLE_BALANCE | Floating point number | Available balance on the card used for transaction. This field will be returned to POS, when the Host returns the Available Balance data. SCA application sends <BALANCE_ENQ> as Host request field and based on the processor, it returns the Available Balance, and SCA will send it back to POS. Example: 1.00 | |
| APPROVED_AMOUNT | Floating point number | Amount approved on authorization. Example: 5.00 | |
| DIFF_AMOUNT_DUE | Floating point number | For partial authorizations – remaining payment amount (TRANS_AMOUNT – APPROVED_AMOUNT). Applicable if PARTIALAUTH configuration parameter (Host Specific parameter) is enabled. Example: 2.00 | |
| ORIG_TRANS_AMOUNT | Floating point number | Conditionally returned when supplied in the host response. | |
| FSA_AMOUNT | Floating point number | Indicates processing with FSA items in transaction. FSA amount. Example: 5.00 | |
| CASHBACK_AMNT | Floating point number | Returned for Debit or EBT Cash Benefits transactions with cash back. Example: 10.00 | |
| TIP_AMOUNT | Floating point number | Returned if counter tip selected or if TIP_AMOUNT sent in request. Example: 2.00 | |
| FS_AVAIL_BALANCE | Floating point number | Available balance on EBT SNAP card. Example: 0.00 | |
| CB_AVAIL_BALANCE | Floating point number | Available balance on EBT Cash Benefits card. Example: 0.00 | |
| CARD_ENTRY_MODE | Character | Returns the card entry mode value. Example: Swiped | |
| CARDHOLDER | Character | Returned for swiped/insert transactions. Example: Doe/John | |
| CARD_EXP_MONTH | Numeric | Card expiry month. Example: 12 | |
| CARD_EXP_YEAR | Numeric | Card expiry year. Example: 20 | |
| AVS_CODE | Character | Result of AVS check. Example: Z | |
| CVV2_CODE | Character | Result of CVV2 check. Example: M | |
| SERVER_ID | Numeric | Echoes what is sent in START request. Example: 10 | |
| CASHIER_ID | Numeric | Echoes what is sent in START request. Example: 10 | |
| CUSTOMER_ZIP | Numeric | Returned when zip code is captured with MANUAL_PROMPT_OPTIONS in request. Example: 10 | |
| MERCH_DECL | Character | 100-AVS MISMATCH 200-CVV MISMATCH 300-AVS/CVV MISMATCH |
Merchant decline codes will return when this is configured. It returns when declined by Host due to AVS/CVV mismatch. |
| MERCH_REF | Character | AVS MISMATCH or CVV MISMATCH | Merchant reference will return when this is configured. It returns when declined by Host due to AVS/CVV mismatch. |
| AUTH_RESP_CODE | Character | Returned by some processors when the transaction is declined. Maximum 19 bytes. Example: 0131 | |
| BANK_USERDATA | Character | Bank User Data, normally returned with CARD_TOKEN. Maximum 50 alphanumeric. Example: /CustData`JANE`K`DOE`````00` | |
| EMBOSSED_ACCT_NUM | Numeric | Card number conditionally returned if present in the SSI response. Returned if payment type = GIFT and returnembossednumforgift is enabled. Example: 6499991111115789 | |
| SAF_NUM | Numeric | Returned instead of CTROUTD when transaction has been put in SAF. SAF number is per device. Example: 0008 | |
| RECEIPT_DATA | Character | Receipt Data | |
| TRANS_DATE | Character | Transaction date returned. Example: 2016.09.20 | |
| TRANS_TIME | Character | Transaction time returned. Example: 09:16:25 | |
| TRAINING_MODE | Character | ON or OFF | Conditionally returned when session is in Training Mode. |
| TRAN_LANG_CODE | Character | en – English fr – French es – Spanish |
This field contains the language code for the current transaction which is finalized based on the configured language on terminal and language preference from the card. This field will be returned only whenever the Card data is captured from cardholder during transaction flow. If Language code is not available from card, then terminal language will be returned. This field needs to be added for the below transaction flows. |
| VSP_CODE | Numeric | If present, returns the VSP code. Example: 100 | |
| VSP_RESULTDESC | Character | Success or Failure | If present, returns the VSP result description. |
| VSP_TRXID | Numeric | If present, returns the VSP transaction ID. Example: 987696060049091234 | |
| PPCV | Character | This field is sent from the Host Response to POS Response, without any change. Example: CBCC.WSI | |
| TRACE_NUM | Numeric | This field is sent from the Host Response. This field contains the Interac Sequence number from the host. Example: 1400040000000004001951 | |
| CDD_DATA | Character | Customer Defined Data field is returned in POS response when it is present in the POS request and passed in the host request. Example: <CDD_DATA>INV200471</CDD_DATA> |
|
| SIGNATUREDATA | Base64 encoded data | Signature data. | |
| AUTH_REF_NUMBER | Character | Example: 123456789012345, Or It can be empty | This tag returns in the host response with the value for the particular transaction. This is used by some merchants to refer to the transaction at the host side. Currently this is applicable only for Worldpay processor. |
| COL_3, COL_4, COL_5, COL_6, COL_7, COL_8, COL_9, COL_10 | Character | Column 3 to Column 10 fields value will be echoed in POS response. These fields are not sent to any payment processor. |
Checks
| Field | Type | Value | Description |
|---|---|---|---|
| DENIAL_REC_NUM | Numeric | Check response field conditionally returned for declined transactions. Example: 1234567 | |
| RETURN_CHECK_FEE | Floating point number | Check response field. Example: 25.00 | |
| RETURN_CHECK_NOTE | Character | This indicates the Check response field. Example: Above fee increases to “30.01 + 12% interest if …” |
APM Based Respose Fields - (Conditional)
| Field | Type | Value | Description |
|---|---|---|---|
| APM_TRAN | Numeric | 0 - Transaction did not perform with APM 1 - Transaction performed with APM. |
This field returns to indicate if the current transaction is performed with alternate payment method. |
| CP_MERCH_RECEIPT_DATA | Character | Additional field will be sent along with RECEIPT_DATA field. | |
| CP_CUST_RECEIPT_DATA | Character | Additional field will be sent along with RECEIPT_DATA field. |
POS-defined Tender Response Fields - (Conditional)
| Field | Type | Value | Description |
|---|---|---|---|
| POS_TENDER1_DATA | Character | Track II Data or NOTIFICATION (or not sent) dependent on TENDER1_ACTION in request. Example: 545454******1111 | |
| POS_TENDER2_DATA | Character | Dependent on TENDER2_ACTION in request. | |
| POS_TENDER3_DATA | Character | Dependent on TENDER3_ACTION in request. |
Processor-Based Token (Conditional)
Note
For use with host based processors supporting card based token implementations.
| Field | Type | Value | Description |
|---|---|---|---|
| CARD_TOKEN | Character | Card token. Example: 7987654321098765 | |
| TOKEN_SOURCE | Character | Source of token. Example: PWC |
Duplicate Detection Response Fields (Conditional)
Note
Refer to Duplicate Detection section in Point Integration Best Practices.
| Field | Type | Value | Description |
|---|---|---|---|
| DUP_ACCT_NUM | Numeric | Duplicate detection for account number. This is Conditional field. Example: 400555******0019 | |
| DUP_AUTH_CODE | Character | Duplicate detection for authorization code. This is Conditional field. Example: 123123 | |
| DUP_AVS_CODE | Character | Ex: Y | Duplicate detection for AVS code. This is Conditional field. Example: Y |
| DUP_CTROUTD | Numeric | Duplicate detection for CTROUTD. This is Conditional field. Example: 45 | |
| DUP_CVV2_CODE | Character | Duplicate detection for CVV2 code. This is Conditional field. Example: M | |
| DUP_INVOICE | Character | Duplicate detection for invoice. This is Conditional field. Example: IN045 | |
| DUP_PAYMENT_MEDIA | Character | Duplicate detection for mode of payment. This is Conditional field. Example: VISA | |
| DUP_TRANS_AMOUNT | Floating point number | Duplicate detection for transaction amount. This is Conditional field. Example: 5.00 | |
| DUP_TRANS_DATE | Date (YYYY.MM.DD) | Duplicate detection for transaction date. This is Conditional field. Example: 2016.09.26 | |
| DUP_TRANS_TIME | Time (00:00:00) | Duplicate detection for transaction time. This is Conditional field. Example: 13:05:22 |
Duplicate Transaction (Conditional)
| Field | Type | Value | Description |
|---|---|---|---|
| DUPLICATE_TRANSACTION | Character | 1 - Duplicate transaction detected | A duplicate transaction is detected if the same card is swiped in the context of two consecutive cash-less purchase transactions on the same PIN pad. The DUPLICATECHECK parameter must be enabled on Engage device. |
Rate this article:
