APPENDIX A: GATEWAY RESPONSE. SECURENET Gateway API

PDF

Document

Advertentie

SecureNet Gateway Implementation Guide 4.1.5

APPENDIX A: GATEWAY RESPONSE

A. Account Duplicate Check Indicator (ADCI)

Account Duplicate Check Indicator—Indicates whether duplicate account exists.

0 - Does not check for Duplicate Card Number for specified Customer ID

1 - Checks for Duplicate Card Number for specified Customer ID

2 - Checks for Duplicate Card Number for All Customer IDs for specified SecureNet ID

3 - Checks for Duplicate Card Number for All Customer IDs for specified Group ID

NOTE: For ACCOUNT_VAULT only. Set to 0 by default. a. AVS_RESULT_CODE

Indicates the result of Address Verification System (AVS) checks.

The Address Verification System (AVS) helps merchants detect suspicious transaction activity. To use this system, the merchant must submit the customer’s credit card billing address (numeric value only) to the Gateway for validation. This information is submitted by the Gateway to the financial institutions. The financial institutions compare the submitted address with the billing address on file for that particular credit card and return an AVS response code to the Gateway. The Gateway includes this code in the response back to the merchant.

AVS Code

Description

AVS data not provided

Street address matches, Zip Code does not

Postal code not verified due to incompatible formats

Street address and postal code not verified due to incompatible formats

Street address and postal code match

AVS data is invalid

Non-U.S. issuing bank does not support AVS

Address information not verified by international issuer

Customer Name, Billing Address and Zip match

Neither street address nor Zip code match

Street address not verified due to incompatible format

Retry: issuer's system unavailable or timed-out

U.S. issuing bank does not support AVS

Street address does not match, but 9-digit Zip code matches

Address information is unavailable

9-digit Zip matches, street address does not

Street address and 9-digit Zip match

Street address and 5-digit Zip match

5-digit Zip matches, street address does not

NOTE: It is recommended that merchants enable some level of Address Verification to avoid non-qualified transaction surcharges that can be levied by merchant banks and merchant service providers.

SecureNet Gateway Implementation Guide 4.1.5

b. CARD_CODE_RESPONSE_CODE

(CVV2/CVC2/CID) The Credit Card Identification Code, or “Card Code,” is a three- or four-digit security code that is printed on the back of credit cards in reverse italics in the card’s signature panel (or on the front for American

Express cards). The merchant can collect this information from the customer and submit the data to the Gateway.

The Gateway will pass this information to the financial institution along with the credit card number. The financial institution will determine if the value matches the value on file for that credit card and return a code indicating whether the comparison failed or succeeded. The Gateway passes back this response code to the merchant.

Code Description

0 CVV/CID not provided

M Match

Data not present

Issuer unable to process request

Card Code Matches (Amex Only) c. CARDLEVEL_RESULTS

This table provides additional information on card type:

NOTE: MasterCard results are available only for SecureNet Frontend, First Data

Nashville and TSYS processor.

Code Description

AX1

American Express

Visa Traditional Rewards

DI1

E –F

Visa Signature Preferred

Discover

Reserved

Visa Signature Business

Visa Business Check Card

Visa Business Enhanced

Visa Debit

Visa Check Card

Visa Debit

I Reserved

J Reserved

J1 Visa General Prepaid

J2 Visa Prepaid Gift

Visa Prepaid Healthcare

Visa Prepaid Commercial

SecureNet Gateway Implementation Guide 4.1.5

Code Description

Visa GSA Corporate T&E

L Reserved

M MasterCard/EuroCard

N –P Reserved

Q1 Private Label Prepaid

R Proprietary

Visa Purchasing with Fleet

Visa GSA Purchasing

S3 Visa GSA Purchasing with Fleet

T Reserved

W –Z

O –9

Reserved

Provides additional information on MasterCard type:

DLG

DLH

DLI

DLS

MAB

MAC

Code Description

Debit MasterCard Gold—Delayed Debit

Debit MasterCard World Embossed—Delayed Debit

Debit MasterCard Standard ISIC Student Card—Delayed Debit

Debit MasterCard Card—Delayed Debit

World Elite MasterCard Business

MasterCard Corporate World Elite

MBE

MCA

MCB

MCE

MCF

MCG

MCH

MCM

MCP

MCS

MasterCard Electronic Business Card

MasterCard Electronic Basic Card

MasterCard BusinessCard Card MasterCard Corporate Card

MasterCard Electronic Card

MasterCard Corporate Fleet Card

Gold MasterCard Card

MasterCard Premium Charge

MasterCard Corporate Meeting Card

MasterCard Corporate Purchasing Card

MasterCard Standard Card

SecureNet Gateway Implementation Guide 4.1.5

MDM

MDN

MDO

MDP

MDQ

MDT

MDU

MEB

MEC

MED

MEF

MEO

MEP

MFB

MFE

MIB

MIC

MID

MIG

MIH

MIJ

MIK

MFL

MFW

MGF

MHA

MHB

NHC

MHH

MIL

MIP

MIS

MIU

MCW

MDB

MDG

MDH

MDJ

Code Description

World MasterCard Card

Debit MasterCard BusinessCard Card

Debit Gold MasterCard

World Debit Embossed

Debit- Debit Other 2 Embossed

Middle Market Fleet Card

Middle Market Purchasing Card

Debit MasterCard Other

Debit MasterCard Platinum

Middle Market Corporate Card

MasterCard Business Debit

Debit MasterCard Unembossed

MasterCard Executive BusinessCard Card

MasterCard Electronic Commercial

Debit MasterCard Electronic

MasterCard Electronic Payment Account

MasterCard Corporate Executive Card

Premium Debit MasterCard

Flex World Elite

Flex charge World Elite

Flex Charge Platinum

Flex Charge World

MasterCard Government Commercial Card

MasterCard Healthcare Prepaid Non-tax

MasterCard HAS Substantiated

MasterCard Healthcare Credit Non-substantiated

MasterCard Unembossed Prepaid Student card

MasterCard Credit Electronic Student Card

MasterCard Credit Standard Student Card

MasterCard Debit Unembossed Student Card

MasterCard Credit Umembossed Student Card

MasterCard Electronic Consumer Non U.S. Student Card

MasterCard Debit Unembossed Non U.S. Student Card

MasterCard Electronic Consumer Prepaid Non U.S Student Card

MasterCard Unembossed Prepaid Non U.S Student Card

MasterCard Debit Prepaid Student Card

MasterCard Debit Standard Student Card

Debit MasterCard Unembossed Outside US

SecureNet Gateway Implementation Guide 4.1.5

MLA

MLC

MLD

MLL

Code

MNW

MPA

MPB

MPC

MPF

MPG

MPJ

MPK

MPL

MPM

MPN

MPO

MPR

MPT

MPV

MPW

MPY

MPZ

MRB

MRC

Description

MasterCard Central Travel Solutions Air

MasterCard Micro-Business Card

MasterCard Distribution Card

MasterCard Central Travel Solutions Land

World MasterCard Card (Europe)

Prepaid MasterCard Payroll Card

MasterCard Preferred BusinessCard

MasterCard Professional Card

Prepaid MasterCard Gift Card

Prepaid MasterCard Consumer Reloadable Card

Prepaid Debit MasterCard Card Gold

Prepaid MasterCard Government Commercial Card

Platinum Mastercard Card

Prepaid MasterCard Consumer Promotion Card

Prepaid MasterCard Insurance Card

Prepaid MasterCard Other Card

Prepaid MasterCard Travel Card

Prepaid MasterCard Teen Card

Prepaid MasterCard Government Benefit Card

Prepaid MasterCard Corporate Card

Prepaid MasterCard Employee Incentive Card

Prepaid MasterCard Emergency Assistance Card

Prepaid MasterCard Electronic BusinessCard

Prepaid MasterCard Electronic Card

MRH

MRJ

MRK

MRO

MRP

MRS

MRW

MSD

MUP

MUS

MUW

MasterCard Platinum Prepaid Travel Card

Prepaid MasterCard Gold Card

Prepaid MasterCard Public Sector Commercial Card

MasterCard Rewards Only

Standard Retailer Centric Payments

Prepaid MasterCard ISIC Student Card

Prepaid MasterCard BusinessCard Credit Outside US

Deferred Debit MasterCard

Premium Debit MasterCard Unembossed

Prepaid MasterCard Unembossed US

MasterCard World Domestic Affluent

SecureNet Gateway Implementation Guide 4.1.5

PVD

PVE

PVF

PVG

PVH

PVI

PVJ

SUR

MWE

MWO

MWR

PVA

PVB

PVC

Code

TCB

TCC

TCE

TCF

TCG

TCP

TCW

TDN

TEB

TEC

TEO

TIB

TIC

TIU

TLA

TNF

TNW

TPB

TPC

TPL

Description

MasterCard World Elite

MasterCard Corporate World

World Retailer Centric Payment

Private Label 1

Private Label 2

Private Label 3

Private Label 4

Private Label 5

Private Label 6

Private Label 7

Private Label 8

Private Label 9

Private Label 10

Prepaid MasterCard Unembossed Outside US

MasterCard Business Card—Immediate Debit

MasterCard (Mixed BIN) —Immediate Debit

MasterCard Electronic —Immediate Debit

MasterCard Fleet Card —Immediate Debit

Gold MasterCard Card —Immediate Debit

MasterCard Purchasing Card—Immediate Debit

World Signia MasterCard Card —Immediate Debit

Middle Market MasterCard Purchasing Card —Immediate Debit

MasterCard Executive BusinessCard Card —Immediate Debit

MasterCard Electronic Commercial —Immediate Debit

MasterCard Corporate Executive Card —Immediate Debit

ISIC MasterCard Electronic Student Card —Immediate Debit

ISIC MasterCard Standard Student Card —Immediate Debit

MasterCard Unembossed —Immediate Debit

MasterCard Central Travel Solutions Air—Immediate Debit

MasterCard Public Sector Commercial Card —Immediate Debit

MasterCard New World —Immediate Debit

MasterCard Preferred Business Card —Immediate Debit

MasterCard Professional Card —Immediate Debit

Platinum MasterCard —Immediate Debit

SecureNet Gateway Implementation Guide 4.1.5

d. CAVV_RESPONSE_CODE

Indicates the results of Cardholder Authentication Verification Value (CAVV) verification.

Code

Blank

Description

CAVV not validated

CAVV not validated because erroneous data was submitted

CAVV failed validation

CAVV passed validation

CAVV validation could not be performed; issuer attempt incomplete

CAVV validation could not be performed; issuer system error

Reserved for future use

CAVV attempt—failed validation—issuer available (U.S.-issued card/non-U.S acquirer)

CAVV attempt—passed validation—issuer available (U.S.-issued card/non-U.S. acquirer)

CAVV attempt—failed validation—issuer unavailable (U.S.-issued card/non-U.S. acquirer)

CAVV attempt—passed validation—issuer unavailable (U.S.-issued card/non-U.S. acquirer)

CAVV passed validation, information only, no liability shift

The CARDTPYE Code is a system-specific code for different types of cards as identified by the Gateway.

Reference CARDTYPE Code Response Description

ACH e-Check

DS Discover

EBT Electronic

GC Gas Card (Fuelman)

JC JCB

MC MasterCard

SV Stored Value Card

VI Visa

VY Voyager

WX Wright Express (WEX) Card

SecureNet Gateway Implementation Guide 4.1.5

f . DCI

Duplicate Transaction Indicator must be activated in Tools tab of the Virtual Terminal: "Duplicate Transaction Lockout

Settings". Duplicates are evaluated against AMOUNT, CARDNUMBER, and, optionally, a user defined field (like

Customer ID, Invoice Number or one of the UDFs), and within a specified time frame of only APPROVED transactions, unless otherwise noted. If a duplicate transaction is found the new transaction is not reprocessed.

0 No duplicate checking will be done.

1 If evaluation of the above conditions results in a duplicate transaction an exception code will be returned.

2 If evaluation of the above conditions results in a duplicate transaction the original transaction response is returned with RESPONSE_REASON_TEXT = “Approved”.

3 Identical to 1 however OrderID is not evaluated.

NOTE: After the above duplicate check is evaluated and no duplicate is found, then

OrderID will be evaluated and responses sent accordingly.

For eCommerce transactions:

P - Physical goods

D - Digital goods

For MO/TO transactions:

1 - Single purchase transaction (AVS is required)

2 - Recurring billing transaction (do not submit AVS)

3 - Installment transaction

For Retail transactions—leave blank.

NOTE: If TRANSACTION_SERVICE = 1 (Process using Customer ID) or 2 (Process using Secondary Merchant ID), INDUSTRYSPECIFICDATA will be set to 1 by default, unless transaction request specifies otherwise.

C. METHOD

Method indicates the method of payment for the transaction being sent to the system and can be one of the following

(The following values are case sensitive):

Reference Code Description

DB Debit

SecureNet Gateway Implementation Guide 4.1.5

a. OrderID

A client generated unique ID for each transaction submitted to the Gateway. OrderID must be unique to the

SecureNet ID; however the uniqueness is only evaluated for APPROVED transactions and only for the last

30 days. If a transaction results in a decline that OrderID may be used again. The OrderID is used as a default method to avoid processing duplicate transactions. The OrderID is not verified for transaction types such as VOID and 0200-PRIOR_AUTH_CAPTURE . OrderID is limited to 25 characters; for example

“CUSTOMERID MMddyyyyHHmmss”.

Format—Alphanumeric values only, No spaces and no special characters b. REF_TRANSID

Transaction ID is a unique value provided by SecureNets Gateway in response for all transactions (approved and declined). This value can be used to reference a previously processed transaction for further processing like to void an approved transaction, capture a 0000—AUTH_ONLY transaction etc.

REF_TRANSID is required information for 0200—PRIOR_AUTH_CAPTURE, 0400 — VOID Transaction and

0500-CREDIT.

It is possible to “re-use” account information (Credit Card, Bank account information, etc.) from an authorized transaction to [process a new transaction i.e. retrieve credit card information from a previously approved transaction and use this information to submit a new transaction. If the REF_TRANSID value is set in the

TRANSACTION object using a previously approved transaction’s Transaction ID, a credit card number is not required to be sent, the credit card number from the transaction referenced by REF_TRANSID will be used.

In order to re-use account information to process a new transaction, please follow the instructions below:

1. REF_TRANSID should be present. CARDNUMBER, ACCOUNTNUM, TRACKDATA, or MICRDATA should not be present.

2. Last 4 digit of card number or account number should be available

3. REF_TRANSID can be from a previously approved transaction.

4. REF_TRANSID should not be older than 180 days for the SecureNet ID.

5. Re-using account information from an approved transaction is available for the following transaction codes: a. 0100—AUTH_CAPTURE,0000—AUTH_ONLY,0300—CAPTURE_ONLY, b. Re-using account information cannot be done for a Card-Present transaction, i.e.

INDUSTRYSPECIFICDATA in the TRANSACTION object should not be empty or null, it should be set to 1, 2, 3, P, or D. c. RESPONSE_CODE

Indicates the result of the transaction:

1 —Approved

2 —Declined

3 —Error / Invalid Data d. SECCODE

The Standard Entry Class (SEC) code is a three letter code that identifies the nature of the ACH entry. Here are some common SEC codes:

Code Description

ARC Accounts Receivable Entries A check received by a merchant through mail or drop box and presented as an ACH entry. Business Checking account, Personal Savings and Personal

Checking accounts are only allowed

SecureNet Gateway Implementation Guide 4.1.5

Code Description

BOC Back Office Conversion A check that is converted from paper to an electronic debit at a centralized location and presented as an ACH entry. Business Checking account, Personal

Savings and Personal Checking accounts are only allowed

CCD Corporate Cash Disbursement Primarily used for business to business transactions. Business

Checking account is only allowed. Credits can only be processed using CCD for Business Accounts

POS Point-of-Sale A debit at electronic terminal initiated by use of a plastic card. An example is using a

Debit card to purchase gas. Personal Savings and Personal Checking accounts are only allowed

PPD Prearranged Payment and Deposits Used to credit or debit a consumer account. Popularly used for payroll direct deposits and preauthorized bill payments. Personal Savings and Personal Checking accounts are only allowed. Credits can only be processed using PPD for Personal Accounts.

TEL Telephone Initiated-Entry Verbal authorization by telephone to issue an ACH entry such as checks by phone. (TEL code allowed for inbound telephone orders only. NACHA disallows the use of this code for outbound telephone solicitations calls). Personal Savings and Personal

Checking accounts are only allowed

WEB Web Initiated-Entry Electronic authorization through the Internet to create an ACH entry. Bank

Account Holder First and Last Name are required. Personal Savings and Personal Checking accounts are only allowed

POP Business Checking account, Personal Savings and Personal Checking accounts are only allowed

Please note that “Linked Credit transactions can be processed only if the original transaction used the following

SEC codes; PPD, POS, WEB, TEL and CCD”.

CODE : Transaction Type Code The following table describes the Codes of transactions that can be submitted to the Gateway and how the Gateway will process them.

CODE Transaction Type

0000 AUTH_ONLY

0001 PARTIAL_AUTH_ONLY

Description

Used to validate a credit card for the amount of goods sold. The

Gateway will send this type of transaction to the financial institution for approval. However this transaction will not be sent for settlement. If the merchant does not act on the transaction within 30 days, the transaction will no longer be available for capture.

Available for:

 Credit

 Prepaid

 StoredValueCard for Ceridian

Used ONLY to validate a prepaid card for the amount of goods sold and may return an amount less than the requested amount if the total amount cannot be fully authorized. The Gateway will send this type of transaction to the financial institution for approval. However this transaction will not be sent for settlement. If the merchant does not act on the transaction within 30 days, the transaction will no longer be available for capture.

Available for:

 Prepaid

 Nashville platform only

Reference

SecureNet Gateway Implementation Guide 4.1.5

CODE Transaction Type

0100 AUTH_CAPTURE

0101 PARTIAL_AUTH_CAPTURE

0200 PRIOR_AUTH_CAPTURE

0201 UPDATE_TRANS_INFO

Description

Identical to AUTH_ONLY(0000); however on approval the transaction will be picked up for settlement.

Available for:

 E-checks

 Credit

 PIN

 PIN-less

 Prepaid

 StoredValueCard for Ceridian

 EBT

Identical to PARTIAL_AUTH_ONLY(0101); however on approval the transaction will be picked up for settlement.

Available for:

 Prepaid

 Credit Cards on TSYS and SecureNet FrontEnd platforms

This transaction is used to request settlement for a transaction that was previously submitted as an AUTH_ONLY( 0000). The Gateway will accept this transaction and initiate settlement if the following conditions are met:

The transaction is submitted with the ID of the original authorizationonly transaction to be settled.

The transaction ID is valid and the system has a record of the original authorization-only transaction.

The original transaction referred to is not already settled, expired, or voided.

The amount being requested for settlement is less than or equal to the original authorized amount.

If no amount is submitted in this transaction, the Gateway will initiate settlement for the amount originally authorized. Merchant account set up as Retail cannot capture an amount greater than the authorized amount (AUTH_ONLY(0000) to PRIOR_AUTH_CAPTURE(0200)).

NOTE:

If extended line item, tax, freight, and/or duty information was submitted with the original transaction, adjusted information may be submitted in the event that the transaction amount changed. If no adjusted line item, tax, freight, and/or duty information is submitted, the information submitted with the original transaction will apply.

Available for:

 E-checks*

 Credit

 Check

 Prepaid

 StoredValueCard for Ceridian

To update Level II and Level III information for qualified transaction before settlement and for updating the image for Check 21 and image for ACH signature.

Reference

SecureNet Gateway Implementation Guide 4.1.5

CODE Transaction Type

0300 CAPTURE_ONLY

0400 VOID

0401 PARTIAL_VOID

Description

This is a request to settle a transaction that was not submitted for authorization through the payment Gateway. The Gateway will accept this transaction if an authorization code is submitted.

AUTHCODE is a required field for CAPTURE_ONLY(0000) transactions.

Available for:

 Credit

 Check

 Prepaid

 EBT

This action cancels a previous transaction such that it is not sent for settlement. It can be performed on the following transaction types:

 CREDIT(

 AUTH_CAPTURE(0100)

 CAPTURE_ONLY(0300)

 AUTH_ONLY

The transaction will be accepted by the Gateway if the following conditions are met:

The transaction is submitted with the ID of the original transaction to be voided (REF_TRANSID).

The card number (or the last four digits thereof) submitted with the credit transaction matches the card number of the original transaction.

The Gateway has a record of the transaction referenced by the ID.

The transaction has not been sent for settlement.

Available for:

 E-checks

 Credit

 Check

 Prepaid

 All

This action will reduce the amount of a previous unsettled transaction.

The transaction is submitted with the ID of the original transaction to be voided (in REF_TRANSID field).

The Gateway has a record of the transaction referenced by

REF_TRANSID.

The card number (or the last four digits thereof) submitted with the credit transaction matches the card number of the original transaction.

The transaction has not been sent for settlement.

Available for:

 E-checks

 Credit

 Check

 Prepaid

MOTO and E-Commerce merchants only

Nashville platform only, TSYS in pipeline

Reference

SecureNet Gateway Implementation Guide 4.1.5

CODE Transaction Type

0402 VOID_BY_OrderID

0500 CREDIT

Description

This action cancels a previous transaction such that it is not sent for settlement. It can be performed on unsettled transactions of the following types:

 AUTH_ONLY(0000)

 AUTH_CAPTURE(0100)

 PRIOR_AUTH_CAPTURE(0101)

 CREDIT_AUTHONLY(0501)

 FORCE_CREDIT(0600)

The transaction will be accepted by the Gateway if the following conditions are met:

The transaction is submitted with the OrderID of the original transaction to be voided (in OrderID field).

The card number (or the last four digits thereof) submitted with the credit transaction matches the card number of the original transaction.

The Gateway has a record of the transaction referenced by the

OrderID.

The transaction has not been sent for settlement.

Available for:

 E-checks

 Credit

 Check

 Prepaid

 All

This transaction is also referred to as a “Refund” and indicates to the

Gateway that money should flow from the merchant to the customer.

The Gateway will accept a credit (refund) request if the transaction submitted meets the following conditions:

The transaction is submitted with the ID of the original transaction against which the credit is being issued (REF_TRANSID).

The transaction ID is valid and the system has a record of the original transaction.

The original transaction has been settled.

The sum submitted in the credit transaction and all credits submitted against the original transaction is less than or equal to the original transaction amount.

The card number (or the last four digits thereof) submitted with the credit transaction matches the card number of the original transaction.

The credit transaction is submitted within 180 days of the settlement date and time of the original transaction.

**Transactions are captured if approved

Available for:

 E-checks

 Credit

 Check

 Prepaid

 Debit cards for SecureNet Front End with Pin Data

 StoredValueCard for Ceridian

 EBT

Reference

SecureNet Gateway Implementation Guide 4.1.5

CODE Transaction Type

0501 CREDIT_AUTHONLY*

Description

0600 FORCE_CREDIT Similar to CREDIT(0500) used for Unlinked credits when previous

Authorized Transaction is not Available. This feature has to be enabled by Merchant Service Provider on the Gateway. Full Account

Number should be provided

**Transactions are captured if approved

Available for:

 E-checks

 Credit

 Prepaid

 StoredValueCard for Ceridian

 EBT

0602 FORCE_CREDIT_PRIORAUTHCAP

TURE*

0700 VERIFICATION

Future use

0800 AUTH_INCREMENT

0900 ISSUE

Run Transaction Verification on Credit Card or Bank Account with zero dollar amount.

For Certegy ECHECK verification can be done for non-zero amount also.

Available for:

 Nashville

 TSYS

 SecureNet FrontEnd platforms

 Credit

 E-checks

This action performs an incremental authorization on a previously authorized transaction (i.e., AUTH_ONLY). Only applicable to Visa transactions and only if the terminal has been set up as LODGING or

AUTO RENTAL industry type. The transaction will be accepted by the

Gateway if the following conditions are met:

 The transaction is submitted with the ID of the transaction.

 The Gateway has a record of the transaction referenced by the ID.

 The transaction has not been sent for settlement.

 AUTH_INCREMENT(0800) can be submitted multiple times before submitting PRIOR_AUTH_CAPTURE(0101).

This action issues a new card or adds funds to an already activated stored value card for paymentech platform and issues a card for

Ceridian platform; also used for refunds to a stored value card for paymentech platform. Will be treated as credit to the card holder.

Available for:

 Pre-paid Cards/Stored Value Cards only

 Ceredian and Paymentech platform

Reference

SecureNet Gateway Implementation Guide 4.1.5

CODE Transaction Type

0901 ACTIVATE

0902 REDEEM

0903 REDEEM_PARTIAL

0904 DEACTIVATE

0905 REACTIVATE

0906 INQUIRY_BALANCE

0907 RELOAD/ RECHARGE

0908

0909

0201

ISSUE_VIRTUAL

CASH_OUT

UPDATE TRANSACTION

INFORMATION

Description

This action activates a new card; only necessary if the stored value card is set to require activation.

Available for:

 Pre-paid

 Paymentech

 Ceridian

This action charges a card; the amount has to be within the available balance.

Available for:

 Pre-paid

 Paymentech

 Ceridian

This action charges a card; the card will be approved only for the available balance on the card if the transaction is approved.

Available for:

 Pre-paid only

 Paymentech platform only

This action de-activates an activated card; amount should be specified as zero.

Available for:

 Pre-paid only

 Paymentech platform only

This action re-activates a de-activated card.

Available for:

 Pre-paid only

 Paymentech platform only

This action checks the available balance on the stored value card; amount should be specified as zero. The available balance on the gift card will be returned in the TRANSACTIONAMOUNT field in the

TRANSACTIONRESPONSE object.

Available for:

 Pre-paid only

 Paymentech platform only

 Ceridian

Adds value to a card

Available for Ceridian

 Pre-paid Cards/Stored Value Cards only

Ceredian platform

This will issue a Virtual Card number and PIN. No plastic exists.

Available for Ceridian

This will withdraw all the available balance from the card.

Available for Ceridian

This code enables updating Level2/Level3 transaction information of an approved transaction before it gets settled.

Also this is used for CHECK21 image update and SIGNATURE image update.

Both Image and Level2/Level3 information cannot be updated simultaneously.

Reference

SecureNet Gateway Implementation Guide 4.1.5

Displays a description in addition to the merchants DBA. This is currently restricted to credit card transactions only.

Contact Support to use this field. Maximum length is 25 characters.

The SOFTDESCRIPTOR field should contain the “Doing Business As” (DBA) name of the merchant and be the name most recognizable to the cardholder. The SOFTDESCRIPTOR field must not be used as a description field in lieu of the required, recognizable name. In addition, the SOFTDESCRIPTOR field may contain a merchandise description, order number, reference number, or other information that will further identify the transaction and assist cardholder recognition.

If additional information is used, the SOFTDESCRIPTOR field must conform to one of the following formats:

Option 1:

Option 2:

Option 3:

Field Position

Pos. 1–3:

Pos. 4:

Pos. 5–25:

Pos. 1–7:

Pos. 8:

Pos. 9–25:

Pos. 1–12:

Pos. 13:

Pos. 14–25:

Data

Merchant name or abbreviation

Asterisk (*)

Descriptive Information

Merchant name or abbreviation

Asterisk (*)

Descriptive Information

Merchant name or abbreviation

Asterisk (*)

Descriptive Information

F. TRACKDATA

This field contains information encoded from a valid magnetic stripe and includes data such as Primary Account

Number and Expiration Date. Unaltered Track Data must be forwarded intact. On Debit Card and EBT (Not Voucher

Clear) transactions, this field is mandatory (with the exception of Debit Card PIN-Less transactions, which are entered manually). Track Data may contain Track 1 and/or Track 2 data. Track 2 data is required for Pin Debit and

Stored Value transactions. Track 1 and Track2 data should not be submitted together. Gateway will also accept trackdata with beginning and end sentinel removed.

It is not acceptable to:

1. Use a manually entered account number and attempt to create a pseudo magnetic stripe.

2. Alter a Track 1 magnetic stripe and remove the cardholder name to make it look like a Track 2.

3. Flip the expiration date digits to MMYY order.

4. Truncate trailing spaces or zeroes.

5. Add, delete, or move characters in any way, including trailing spaces.

Accurate Track 1 or Track 2 data is required to receive Card Present rates. Authorization requests containing altered Track 1 or Track 2 data will be flagged as NOT COMPLIANT by Visa and MasterCard, resulting in the merchant paying the highest transaction rate and forfeiture of chargeback protection. Both associations monitor non-compliant transactions and will assess fines and penalties to merchants that are not in compliance.

The POS device or software must perform the following operations on Track read data before it can be used in an authorization request message:

 The longitudinal redundancy checks (LRC) must be calculated for the data read from the Track and compared to the LRC read from the Track. The Track data is assumed to be read without errors when no character parity errors are detected and the calculated and read LRCs match.

 The starting sentinel, ending sentinel, and LRC are discarded.

SecureNet Gateway Implementation Guide 4.1.5

 The character codes read from the magnetic stripe must be converted from the encoded character set to the set used for the authorization request message. The characters encoded on Track 1 are six bit plus parity codes and the characters encoded on Track 2 are four bit plus parity codes, with the character set used for the request message defined as seven bit plus parity code. All characters read from a Track must be converted to the request message character set and transmitted as part of the request. The converted

Track data cannot be modified by adding or deleting non-framing characters and must be a one for one representation of the characters read from the Track.

NOTE: You only need to submit Track 1 or Track 2 data. If both tracks are sent by the

POS application, the Gateway will use the Track 1 information. If neither Track 1 nor

Track 2 data is submitted, but x_card_num and x_exp_date are submitted, the Card

Present transaction rate might be downgraded.

This is a variable length field with a maximum data length of 76 characters. The Track 1 data read from the cardholder’s card is checked for parity and LRC errors and then converted from the six-bit characters encoded on the card to seven bit characters as defined in ANSI X3.4.

As part of the conversion, the terminal must remove the framing characters (start sentinel, end sentinel, and

LRC characters). The separators must be converted to either an ASCII “^” (HEX 5E) or ASCII <US> (HEX 1F) characters. The entire unaltered Track, excluding framing characters, must be provided in the authorization request message or an error condition will result.

Track 1 can be encoded with up to 79 characters as shown below:

SVC

NAME FS DATE CD

DISCRETIONARY

LEGEND:

Field Description Length Format

PAN

NAME

(“B” for credit cards)

Primary Account Number

Card Holder Name

DATE

SVC CD

Expiration Date (YYMM)

Service Code

DISCRETIONARY DATA Optional Issuer Data

1 Alphanumeric

19 max Numeric

2 - 25 max

Variable

Alphanumeric

Numeric

Alphanumeric

LRC Longitudinal Redundancy Check

Total cannot exceed 79 bytes

79 b. Track 2 Data

This is a variable length field with a maximum data length of 37 characters. The Track 2 data read from the cardholder’s card is checked for parity and LRC errors and then converted from the four-bit characters encoded on the card to seven bit characters as defined in ANSI X3.4. As part of the conversion, the terminal must remove the start sentinel, end sentinel, and LRC characters. The separators must be converted to either an

SecureNet Gateway Implementation Guide 4.1.5

ASCII “=” (HEX 3D) or ASCII “D” (HEX 44) characters. The entire UNALTERED Track (excluding framing characters) must be provided in the authorization request message or an error message will be generated.

Track 2 Data can be encoded with up to 40 characters as shown below:

CD ES LRC

LEGEND:

Field Description

PAN Primary Account Number

DATE Expiration Date (YYMM)

SVC CD Service Code

DISCRETIONARY DATA Optional Issuer Data

ES End Sentinel

LRC Longitudinal Redundancy Check

Total cannot exceed 40 bytes

Length

19 max

Variable

Format

Numeric

Alphanumeric

0F Hex

Field Name

ADDITIONALDATA1

ADDITIONALDATA2

ADDITIONALDATA3

ADDITIONALDATA4

Debit Cards EBT

Stored Value

Cards Fleet Cards

Paymentech specific data—For Debit

Transactions it will contain the Trace Number for the transaction. For PD transaction, settlement date is returned.

For EBT transactions it will contain the FNS

# echoed from the

ADDITIONALINFO field of the

MERCHANT_KEY object.

For EBT transactions it will contain the

Voucher # echoed from the

ADDITIONALINFO field of the CARD object.

Previous Balance (15 characters long zero filled decimal number with explicit decimal point) followed by

Cash Out Amount (15 characters long zero filled decimal number with explicit decimal point)

for ISSUE_VIRTUAL:

Virtual issued card number

Paymentech only—

Optional data returned by the Host for Fleet Cards. (If data exists, it must be printed on the customer receipt as reference data).

for ISSUE_VIRTUAL:

Virtual issued card

EXP date for ISSUE_VIRTUAL:

Virtual issued card

Pin Number

SecureNet Gateway Implementation Guide 4.1.5

Field Name

ADDITIONALDATA5

Debit Cards

P2P Encryption

Transaction Response—

String (22 Characters): 7digit Key ID + {1,2} +

MMddyyyyHHmmss

EBT

Stored Value

Cards Fleet Cards

P2P Encryption

Transaction

Response—String (22

Characters): 7-digit

Key ID + {1,2} +

MMddyyyyHHmmss

P2P Encryption

Transaction

Response—String (22

Characters): 7-digit

Key ID + {1,2} +

MMddyyyyHHmmss

P2P Encryption

Transaction

Response—String

(22 Characters): 7digit Key ID + {1,2} +

MMddyyyyHHmmss

Current Balance Current Balance ADDITIONALAMOUNT For Debit Transactions it will contain the surcharge for the transaction, if one has been setup on the

Host. (If surcharge applies, it must be printed on the customer receipt).

Applicable to Paymentech only.

CASHBACK_AMOUNT Cash Back Amount

ADDITIONALAMOUNT For Debit Transactions it will contain the surcharge for the transaction, if one has been setup on the

Host. (If surcharge applies, it must be printed on the customer receipt).

Applicable to Paymentech only.

Current Balance Current Balance

CHECK

Object CARD Object

ADDITIONAL

INFO

ACH

No Check

Verification—

(default value)

Credit Card

No credit card account verification, default value.

Applicable only when adding a new Account to the

SecureNet Vault.

EBT

MERCHANT_KEY

Object Reference

 Gateway

 Extended

Services

Supported Platform:

 Paymentech

 Ceridian

 ACH

 Refer:

Check verification through

Certegy

Pre-Note with

ACH Provider

Credit card account verification. Applicable only when adding a new Account to the SecureNet Vault.

Update EXPDATE of credit card during Process

Transaction by Customer ID.

SecureNet Gateway Implementation Guide 4.1.5

Variable Text

CHECK

Object CARD Object

11 (EBT indicator) + 15character long leftjustified space-filled

EBT Voucher number.

For EBT Voucher Clear transactions only.

MERCHANT_KEY

Object

For EBT transactions only. 11 (EBT indicator) + 7-digit FNS number (left-justified, space-filled, if FNS is less than 7 digits).

Reference d. TRANSACTION_SERVICE

[Regular Transactions]

0 —Regular Transaction (Default)

[SecureNet Vault Transactions]

1 - Process Transaction using Customer ID

2 - Process Transaction using SECONDARY_MERCHANT_KEY

3 - Process Transaction Add Customer and Account

G. Commodity Code for Level III items

Summary and Item Commodity code and Description fields should be populated with Standard United Nations Standard

Products and Services Code(UNSPC) from unspsc.org

Standard codes can be found at http://www.unspsc.org/Search.asp

a. Unit of Measurement for Level III items

2 characters UOM should be submitted for Item Unit type for Level III transactions. Refer ANSI X-12 Allowable

Units of Measure and Codes

Standard codes can be found at http://das.ct.gov/Purchase/Info/ANSI_UNITS_OF_MEASURE.pdf

2 characters HealthCare Code is required for HealthCare Transactions.

Refer United States Health Information Knowledgebase(USHIK) Metadata Registry for Accredited Standards

Committee X12 Service Type Code.

Standard Service Type code can be found at http://ushik.ahrq.gov/ViewItemDetails?system=mdr&itemKey=27573000 c. Product Codes for Petroleum Industry Transactions

Paymentech Petroleum Product Codes/Paymentech ‘Generic’ Codes

Ethan1 (Regular) 001 Wipers 023

Super Unleaded

Other Fuel

Unleaded Plus

Gas/Alcohol 2

004

005

006

008

Tires

Hoses

Filters

Oil Change

026

027

028

030

031

SecureNet Gateway Implementation Guide 4.1.5

Diesel 2 009 Tune Up 032

Unleaded 10% blend

Unleaded Plus 10% blend

Super Unleaded 10%

Unleaded 7% blend

Unleaded Plus 7%

Super Unleaded 7% blend

Refer Fuel

Farm Fuel

012

013

014

015

016

017

018

019

Tires/Batteries/Access

Other

Accessories

Food

Service

Parts

Labor

Reserved

035

040

041

042

043

044

045

046

Motor Oil 021 Sales Tax**

Lamps 022

056

*Product Code 051: Discount is a negative amount

**If tax is submitted as a Product Code, it must ALSO be submitted in the purchasing card data fields.

Product Amounts can be treated as negative values if they have been setup as such with the host. When submitted, the total of the positive product amounts minus the negative product amounts must equal the transaction amount. Transaction amounts must cross foot:

 Sum of all Product Amounts must equal Transaction Amount.

 If provided: Unit Price * Quantity = Product Amount (Quantity multiplied by Unit Price is rounded using 4/5 rounding to derive the extended amount.)