CreditNow! AutoProcessor 96-Byte Field Reference
For Paymentech
Version 1.415
September 2003
Versions 3.1.3.4 and greater of CreditNow! CN-3000
| Field Name | Type | Length | Importable | Field Pattern | Description | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Account | AN | 19 | Yes |
|
Credit Card, Purchase Card, or Checking Account number.
Credit Card and Purchase Card numbers may contain dashes ('-') or spaces. Checking account numbers should not have spaces. Field also supports encrypted credit card and checking account numbers. |
||||||||||||||||||||||||||||||||||
| Action | AN | 2 | Yes |
|
Defines type of transaction.
Must be one of the following:
C1, C3, and C6 are provided for IC-Verify compatibility. The following standard actions for checks (ECP) tranlate into Paymentech ECP action codes as follows:
|
||||||||||||||||||||||||||||||||||
| Activity Date | D&T | 22 | No |
M/D/YYYY H:M:S AMPM
M/D/YY H:M:S AMPM |
Date and time at which the activity specified in the Action field took
place, i.e., when was it authorized, when was it refunded, when was it
deposited, etc. Date and time is keyed to the server on which CN-3000 is running and not the time at the processor's location. |
||||||||||||||||||||||||||||||||||
| Amex Transaction Advice1 | AN | 40 | Yes |
|
American Express Transaction Advice Addendum #1.
This record provides additional purchase information for American Express transactions. It is also used for Purchase Card transactions to provide specific details about the transaction to the cardholder for tracking purposes. Information entered in this field should be as specific as possible. MERCHANDISE, for example, is unacceptable. APPLE MACINTOSH is acceptable. The text should be in uppercase. TAA fields are not supported for International currency processing. Transaction Advice Addendum (TAA) fields must be presented in sequence for them to be transmitted to the processor. If two TAA fields are to be transmitted, they must be TAA#1 and TAA#2. If TAA#1 and TAA#3 are presented, only TAA#1 is transmitted to processor. |
||||||||||||||||||||||||||||||||||
| Amex Transaction Advice2 | AN | 40 | Yes |
|
American Express Transaction Advice Addendum #2. | ||||||||||||||||||||||||||||||||||
| Amex Transaction Advice3 | AN | 40 | Yes |
|
American Express Transaction Advice Addendum #3 | ||||||||||||||||||||||||||||||||||
| Amex Transaction Advice4 | AN | 40 | Yes |
|
American Express Transaction Advice Addendum #4. | ||||||||||||||||||||||||||||||||||
| Amount | No | 12 | Yes | #########.## |
Amount of this transaction.
The decimal point and the two digits to the right of the decimal place are required except when processing Yen. When processing Yen, the decimal place and digits to the right are not allowed. For MasterCard, Visa, and JVB transactions, the amount must be greater than or equal to $0.01USD. For American Express, Discover Card, and Diners/Carte Blanche transactions, the amount must be greater than or equal to $1.00 USD. |
||||||||||||||||||||||||||||||||||
| Auth Code | AN | 6 | Yes |
|
Authorization Approval code returned by processor. Field should be
blank for Auth, Refund, and Conditional Deposit transactions. Deposit
transactions should enter information returned by the initial Auth
transaction. ECP transactions will return 123456. |
||||||||||||||||||||||||||||||||||
| Authorized Amount | No | 12 | Yes | #########.## | Amount of this transaction for which an Authorization has already been obtained. Used for MasterCard. | ||||||||||||||||||||||||||||||||||
| Authorized Date | D&T | 22 | Yes |
M/D/YYYY H:M:S AMPM
M/D/YY H:M:S AMPM |
Date and time at which Authorization was received.
For Authorization transactions, filled in by Processor on Authorization transactions. Needs to be imported for Deposit transactions. |
||||||||||||||||||||||||||||||||||
| AVS | AN | 6 | Yes |
|
Address Verification Response code returned by processor, if AVS is used.
Otherwise blank. |
||||||||||||||||||||||||||||||||||
| AVS Message | AN | 80 | No |
|
Textual description of the AVS response code. String starts with the
AVS response code, followed by a space, two dashes, another space and
the message. Example: "I3 -- Match Except +4" |
||||||||||||||||||||||||||||||||||
| AVS Requested | AN | 1 | No |
|
"Y" if AVS service was requested and "N" if it was not. | ||||||||||||||||||||||||||||||||||
| Batch ID | AN | 10 | Yes |
|
An arbitrary batch identifier which may be imported for tracking purposes. If not imported, CN-3000 generates a Batch ID. This Batch ID is not transmitted to Paymentech and is not used for tracking transactions with Paymentech. | ||||||||||||||||||||||||||||||||||
| BillAddress:Address1 | AN | 30 | Yes |
|
First address line of customer billing address. | ||||||||||||||||||||||||||||||||||
| BillAddress:Address2 | AN | 30 | Yes |
|
Second address line of customer billing address. | ||||||||||||||||||||||||||||||||||
| BillAddress:Apt | AN | 6 | Yes |
|
Apartment portion of customer billing address. Should say 50, not Apt 50. | ||||||||||||||||||||||||||||||||||
| BillAddress:City | AN | 20 | Yes |
|
City portion of customer billing address. | ||||||||||||||||||||||||||||||||||
| BillAddress:Country | AN | 3 | Yes |
|
Country portion of customer billing address.
Note: AVS currently only available for USA.
|
||||||||||||||||||||||||||||||||||
| BillAddress:Email | AN | 50 | Yes |
|
Email portion of customer billing address.
Example: customer@site.com. |
||||||||||||||||||||||||||||||||||
| BillAddress:FirstName | AN | 20 | Yes |
|
Customer's first name on card or checking account. | ||||||||||||||||||||||||||||||||||
| BillAddress:HomePhone | AN | 20 | Yes | AAAEEENNNXXXX |
Home phone portion of customer billing address.
|
||||||||||||||||||||||||||||||||||
| BillAddress:LastName | AN | 20 | Yes |
|
Customer's last name on card or checking account. | ||||||||||||||||||||||||||||||||||
| BillAddress:MiddleInitial | AN | 6 | Yes |
|
Customer's middle initial, not a middle name. Six characters for people who use two initials: G. A. Not intended for use by van as in van Beethovan. | ||||||||||||||||||||||||||||||||||
| BillAddress:State/Prov | AN | 2 | Yes |
|
US State or Canadian Province Code portion of customer billing address. | ||||||||||||||||||||||||||||||||||
| BillAddress:WorkPhone | AN | 20 | Yes | AAAEEENNNNXXXX |
Work phone number of customer billing address.
|
||||||||||||||||||||||||||||||||||
| BillAddress:ZipCode/PC | AN | 10 | Yes |
03458
03458-0458 N1D 1E5 |
A five-digit US Zip Code, 10-character Zip+4, or seven-character Canadian Postal Code.
This field may only contain properly formatted US Zip or Canadian Postal codes. |
||||||||||||||||||||||||||||||||||
| Captured Date | D&T | 22 | No |
M/D/YYYY H:M:S AMPM
M/D/YY H:M:S AMPM |
Date and time at which the capture occured. Filled in for C and D transactions. | ||||||||||||||||||||||||||||||||||
| Card Type | AN | 20 | Yes |
|
Type of credit or purchase card. If imported, value is only used if
type cannot be determined from the account number. If not imported, the
two-character code is automatically generated by CN-3000.
Card Type is case insensitive.
|
||||||||||||||||||||||||||||||||||
| Check Acct Type | AN | 1 | Yes |
|
Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| Check Fraud | Yes/No | 1 | Yes |
|
'Y' to obtain a fraud score on this transaction. Otherwise 'N' or blank. Merchant must be participating in Paymentech fraud scoring program. | ||||||||||||||||||||||||||||||||||
| Class | AN | 1 | Yes |
|
Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| CNX Order ID | No | 10 | Yes |
|
Order identifier used internally by CN-3000. Typically neither imported nor exported. This is not the Paymentech Order ID (see Order ID field). | ||||||||||||||||||||||||||||||||||
| Comment1 | AN | 128 | Yes |
|
Free-form descriptive field. Information is not transmitted to processor. | ||||||||||||||||||||||||||||||||||
| Comment2 | AN | 128 | Yes |
|
Free-form descriptive field. Information is not transmitted to processor. | ||||||||||||||||||||||||||||||||||
| Comment3 | AN | 128 | Yes |
|
Free-form descriptive field. Information is not transmitted to processor. | ||||||||||||||||||||||||||||||||||
| Comment4 | AN | 128 | Yes |
|
Free-form descriptive field. Information is not transmitted to processor. | ||||||||||||||||||||||||||||||||||
| Commercial Card Type | AN | 1 | Yes |
|
Describes the specific type of Commercial Card (Purchase Card) used for this transaction. Must be one of the following:
Enter a blank if it is not a commercial card. |
||||||||||||||||||||||||||||||||||
| Created Date | D&T | 22 | No |
M/D/YYYY H:M:S AMPM
M/D/YY H:M:S AMPM |
Date and Time at which the transaction was created in CN-3000 database. Useful for debugging purposes or tracking flow of transactions. | ||||||||||||||||||||||||||||||||||
| Currency | AN | 3 | Yes |
|
Necessary to import only if you are set-up to process multiple
currencies per Division ID with Paymentech. Also note that
multi-currency may be limited to particular division ids. Please work
with your Paymentech representative on configuration details. An import value of blank defaults to whatever currency has been set-up for the specific division by Paymentech. Most merchants set up different divisions for different currencies so there is usually no need to import this field.
|
||||||||||||||||||||||||||||||||||
| Cust Ref | AN | 17 | Yes |
|
Customer reference number or customer code. Not transmitted to Paymentech. | ||||||||||||||||||||||||||||||||||
| CVV Message | AN | 80 | No |
|
Text description of CID/CVV2 result. | ||||||||||||||||||||||||||||||||||
| CVV Presence | AN | 2 | Yes |
|
Indicates whether a CVV/CID code (3-digit code from back of card) is present. Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| CVV Resp | AN | 1 | Yes |
|
CVV2/CID response code returned by processor if CVV2 or CID submitted. | ||||||||||||||||||||||||||||||||||
| CVV/CID | AN | 4 | Yes |
|
A four-digit value for American Express CID. A three-digit value for MasterCard CVC2, Visa CVV2, and Discover CID. Number is usually printed on the back of the customers card. Used for fraud deterrence. | ||||||||||||||||||||||||||||||||||
| Discount Amount | No | 12 | Yes | #########.## | Discount Amount | ||||||||||||||||||||||||||||||||||
| Division ID | AN | 6 | Yes |
|
Paymentech Division ID (sometimes called Merchant ID). | ||||||||||||||||||||||||||||||||||
| Duty | No | 12 | Yes | #########.## | Amount of duty included in the transaction. | ||||||||||||||||||||||||||||||||||
| ECommerce Type | AN | 1 | Yes |
|
Must be one of the following:
Typical Ecommerce setting will be E for Non-SET Channel Encrypted (i.e., HTTPS). SET is a specific security implementation that is rarely used. |
||||||||||||||||||||||||||||||||||
| ECP Authorization Method | AN | 1 | Yes |
|
Method by which merchant is authorized by customer to conduct this Electronic Check transaction.
Please contact your Paymentech representative to determine legal requirements for the various methods. Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| Exp | AN | 7 | Yes | MM/YY | Credit card expiration date. Leave blank if unknown. | ||||||||||||||||||||||||||||||||||
| Freight Amount | No | 12 | Yes | #########.## | Amount of freight included in the transaction. | ||||||||||||||||||||||||||||||||||
| ICV-Style Response | AN | 256 | No |
|
See appendix on IC-Verify compatibility features. | ||||||||||||||||||||||||||||||||||
| Invoice | AN | 10 | Yes |
|
Invoice number for this order. Not sent to Paymentech. | ||||||||||||||||||||||||||||||||||
| LastActionSucceeded | No | 1 | No |
|
Flag indicating whether the last requested transaction action succeeded. Field is 1 if successful and 0 if not. Use this field to check for success or failure when writing programs that read CN-3000 exported files. | ||||||||||||||||||||||||||||||||||
| MC Banknet Date | AN | 4 | Yes | MMDD |
Authorization date assigned by the MasterCard authorization system. Used with externally-obtained MasterCard authorizations.
NOTE: format is MMDD for Month and Day. Year is not passed. |
||||||||||||||||||||||||||||||||||
| MC Banknet Reference Number | AN | 9 | Yes |
|
Reference number assigned by the MasterCard authorization system. Used with externally-obtained MasterCard authorizations. | ||||||||||||||||||||||||||||||||||
| MC SecureCode AAV | AN | 32 | Yes |
|
MasterCard Secure Code Authentication Value. This is a unique transaction token generated by the issuer and presented to the merchant each time a cardholder conducts an electronic transaction using MasterCard SecureCode. AAV incorporates elements specific to the transaction and effectively binds the cardholder to a transaction at a particular merchant for a given sale amount. | ||||||||||||||||||||||||||||||||||
| MCC | AN | 4 | Yes |
|
MasterCard Merchant Category Code. Used to describe merchant's primary business. MCC code for authorization and deposit must match. | ||||||||||||||||||||||||||||||||||
| Merchant Action | AN | 10 | No |
|
Suggested merchant action for declined or rejected transaction. For
more details, refer to Appendix A of Paymentech's 96-byte batch
technical specification. These are suggested, probable courses of
action for commonly received response codes.
|
||||||||||||||||||||||||||||||||||
| Merchant City Descriptor | AN | 13 | Yes |
|
Also known as a Soft Descriptor.
Contains either the City in which your business is located or, more commonly, a Customer Service Phone Number. The Customer Service Phone Number is a requirement to qualify for Visa's reduced Direct Marketing interchange rate. This field must be formatted in one of the following formats, where N is Numeric, A is Alpha, C is Character (Alpha or Blank) and U is Alphanumeric:
Paymentech can set up standard Soft Descriptors for you which are atached to every transaction. Specific Soft Descriptors may be keyed from a particular Division ID.
This field is valid only for credit cards, not check (ECP) transactions. This field must be blank for ECP transactions.
|
||||||||||||||||||||||||||||||||||
| Merchant Name Descriptor | AN | 22 | Yes |
|
Also known as a Soft Descriptor
This field contains the Merchant Name and/or Item Description. The Merchant Name Descriptor field must not start with a space. Visa regulations require that the company name must appear first and be followed by an asterisk (*). The asterisk may only appear in positions 5, 9, or 14. An additional product description may following the asterisk. For ECP Transactions, the first 10 characters of this field should be used as the Doing Business As (DBA) description and the rest of the field be used for the item description. If the DBA description is shorter than 10 characters, use spaces to fill out to the eleventh space before entering the item description. See Merchant City Description. |
||||||||||||||||||||||||||||||||||
| Order Date | Date | 10 | Yes |
M/D/YYYY
M/D/YY |
Date that customer placed the order.
See Order Time field. |
||||||||||||||||||||||||||||||||||
| Order Number | AN | 16 | Yes |
|
Used to track unique transactions through the Paymentech system. If not
imported, CN-3000 generates a unique order number. If you are doing
two-pass Authorization and Deposits, the Deposit should have the same
Order Number as the original Authorization transaction. To help in
reconciliation and report reviews, all Order Numbers within a single
batch should be unique. This, however, is not a mandatory constraint.
CN-3000 is limited to importing 10,000 duplicate order number
transactions in the same batch. Having large numbers of duplicate order
numbers in a batch will slow down CN-3000 processing. Do not use pipe(|), caret (^), percent symbol (%) or backslash () in the Order Number. |
||||||||||||||||||||||||||||||||||
| Order Time | AN | 11 | Yes | H:M:S AMPM | Time that customer placed the order. | ||||||||||||||||||||||||||||||||||
| PO Number | AN | 17 | Yes |
|
Customer Purchase Order Number | ||||||||||||||||||||||||||||||||||
| Preferred Delivery Method | AN | 1 | Yes |
|
Preferred Delivery Method for checks. Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| Product Delivery Type | AN | 1 | Yes |
|
Describes how the product being purchased is to be delivered. Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| Recurring Payment Advice Code | AN | 80 | No |
|
Action to be taken when receiving decline on a transaction marked as recurring. Will be one of the following:
Code returned only for MasterCard account numbers. The Transaction Class must be set to Recurring (see Transaction Class field). |
||||||||||||||||||||||||||||||||||
| Response Date | D&T | 22 | Yes |
M/D/YYYY H:M:S AMPM
M/D/YY H:M:S AMPM |
Date and Time the Authorization Response was obtained. | ||||||||||||||||||||||||||||||||||
| Response Text | AN | 255 |
|
|
Text description of the transaction result. Importable, but ignored. Usually export only. | ||||||||||||||||||||||||||||||||||
| Response Code | AN | 6 | Yes |
|
Paymentech returns a three-digit response code. 100 means success. The Paymentech 96-byte specification recommends returning the response code received for an authorization with the deposit transaction. See Appendix A of Paymentech 96-byte specification for response code details. | ||||||||||||||||||||||||||||||||||
| Routing Number | AN | 9 | Yes |
|
Bank routing number for checks. Also called Receiving Depository Financial Institution (RDFI) number, the Bank ID, the ABA#, or the Transit Routing #. US bank values are 9 digits. Canadian bank values are 8 digits. | ||||||||||||||||||||||||||||||||||
| Ship From Zip | AN | 9 | Yes |
|
Zip code or Canadian postal code from which product was shipped. | ||||||||||||||||||||||||||||||||||
| Ship Method | AN | 1 | Yes |
|
Method by which purchase is shipped to customer. Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| ShipAddress:Address1 | AN | 30 | Yes |
|
First address line of customer shipping address. | ||||||||||||||||||||||||||||||||||
| ShipAddress:Address2 | AN | 30 | Yes |
|
Second address line of customer shipping address. | ||||||||||||||||||||||||||||||||||
| ShipAddress:Apt | AN | 6 | Yes |
|
Apartment portion of customer shipping address. Should say 50 and not Apt 50. | ||||||||||||||||||||||||||||||||||
| ShipAddress:City | AN | 20 | Yes |
|
City portion of customer shipping address. | ||||||||||||||||||||||||||||||||||
| ShipAddress:Country | AN | 2 | Yes |
|
Country portion of customer shipping address.
|
||||||||||||||||||||||||||||||||||
| ShipAddress:Email | AN | 50 | Yes |
|
Email portion of customer shipping address.
Example: customer@site.com. |
||||||||||||||||||||||||||||||||||
| ShipAddress:FirstName | AN | 20 | Yes |
|
Customer's first name on shipping address. | ||||||||||||||||||||||||||||||||||
| ShipAddress:HomePhone | AN | 20 | Yes | AAAEEENNNNXXXX |
Home phone portion of customer shipping address.
|
||||||||||||||||||||||||||||||||||
| ShipAddress:LastName | AN | 20 | Yes |
|
Customer's last name on shipping address. | ||||||||||||||||||||||||||||||||||
| ShipAddress:MiddleInitial | AN | 6 | Yes |
|
Customer's middle initial, not a middle name. Six characters for people who use two initials: G. A. Not intended for use by van as in van Beethovan. | ||||||||||||||||||||||||||||||||||
| ShipAddress:State/Prov | AN | 2 | Yes |
|
US State or Canadian Province Code portion of customer shipping address. | ||||||||||||||||||||||||||||||||||
| ShipAddress:WorkPhone | AN | 20 | Yes | AAAEEENNNNXXXX |
Work phone number of customer shipping address.
|
||||||||||||||||||||||||||||||||||
| ShipAddress:ZipCode/PC | AN | 10 | Yes |
03458
03458-0458 N1D 1E5 |
A five-digit US Zip Code, 10-character Zip+4, or seven-character Canadian Postal Code.
This field may only contain properly formatted US Zip or Canadian Postal codes. |
||||||||||||||||||||||||||||||||||
| Shipping Carrier | AN | 4 | Yes |
|
Carrier delivering the merchandise to customer. Must be one of the following:
|
||||||||||||||||||||||||||||||||||
| Status | AN | 20 | No |
|
Transaction Status
|
||||||||||||||||||||||||||||||||||
| Submitter ID | AN | 6 | Yes |
|
Paymentech Submitter ID. Usually not imported unless working in a multi-submitter environment. All transactions in a single import file must have the same Submitter ID on each transaction. | ||||||||||||||||||||||||||||||||||
| Tax | No | 12 | Yes | #########.## | Amount of sales tax included in the transaction. | ||||||||||||||||||||||||||||||||||
| Tax Exempt | Yes/No | 1 | Yes | Y or N | 'Y' if customer is tax exempt. Otherwise 'N'. | ||||||||||||||||||||||||||||||||||
| Tender Type | AN | 1 | Yes |
|
Tender Type. CN-3000 is able to automatically distinguish between
credit card and check (ECP) transactions based on the information
imported for the transaction. If a Bank Routing number is imported,
CN-3000 assumes the Tender Type is Check. CN-3000 cannot distinguish
between a credit card and a purchase card. If you are processing
purchase cards, you must import the Tender Type. If this field is
blank, CN-3000 will distinguish between checks and credit careds. Must
be one of the following:
|
||||||||||||||||||||||||||||||||||
| Total Authorized Amount | No | 12 | Yes | #########.## | Current authorized amount for transaction. Only used when capturing Visa cards for which authorization was obtained elsewhere. | ||||||||||||||||||||||||||||||||||
| Transaction Reference Key | AN | 100 | Yes |
|
A processor-neutral transaction reference. When doing two-pass
Authorize/Deposit transactions, this remembering and returning this
field is a convenient way to remember all the processor-specific
information needed to Deposit the transaction. The Transaction Reference Key contains:
|
||||||||||||||||||||||||||||||||||
| User | AN | 10 |
|
|
Name of user that imported the transaction. Currently only one user. In
future, different import channels will have different users.
|
||||||||||||||||||||||||||||||||||
| Visa Authentication CAVV | AN | 40 | Yes |
|
Cardholder Authentication Verification Value or "Verified by Visa." | ||||||||||||||||||||||||||||||||||
| Visa Authentication CAVV Response | AN | 1 | Yes |
|
Result of a Verified by Visa transaction sent to Paymentech. Listed as
importable, but not sent to Paymentech. Will be one of the following:CAVV passed validation
|
||||||||||||||||||||||||||||||||||
| Visa Authentication XID | AN | 40 | Yes |
|
Unique tracking number set by the Merchant and sent to the Issuer Authentication Server. Used for Verified by Visa. | ||||||||||||||||||||||||||||||||||
Key for Type field: AN: Alphanumeric, D&T: Date and Time, N: Numeric
The Field Reference table provides a quick reference to all the CreditNow! fields available for use with Paymentech. Import and Export fields have a maximum, but not fixed, length. Fields are delimited by either tabs or commas. Therefore, a text field with a maximum size of 80 characters could have one or in some cases no, characters in the field.
Field references are subject to change as processor specifications evolve. CN-3000 supports Paymentech MOTO, Ecommerce, and Recurring abilities at this time. CN-3000 does not currently support retail transactions.
It is not necessary for you to import each and every field in this field reference. In fact, you will probably only import a small subset. Different fields are used for different purposes based on what you are selling, how you are delivering it, what types of payments (credit card, purchase card, electronic check) you are processing and even what specific industry you are in.
Your best course is to spend time with your Paymentech representative to determine the precise information you should be importing for transmission to Paymentech.
Notes on AVS: When performing AVS you need to either send just the US Zip code or the US Zip code PLUS the BillAddress:LastName, BillAddress:City, and BillAddress:State.
The address line sent to Paymentech is: First 30 characters of (BillAddress:Address1, space, BillAddress:Address2, 'APT' + BillAddress:Apt). Address2 and Apt fields are optional. For best matching, the number in the street and street name must be sent in numeric form. Example: One First Street should be 1 1ST ST
Importing Times: Time is an optional import portion of all date fields. You do not need to import time. If you do not include AM or PM then 24-hour clock is assumed.
Portions of this document were abstracted, with permission, from Paymentech's 96-byte Technical Specification, Revision 1.7.1 dated 21 September 2001.
