Declined Drop Ships | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 41: Defining Authorization Services (WASV) |
Purpose: Use this report to review the authorization status of pick slips for a particular billing batch number.
How to print: The report prints when credit card orders are authorized during pick slip generation (see Introducing Pick Slip Generation), or when you reprocess the authorizations at the Reprocess Authorizations Screen (RPAA). The system also generates this report as part of drop ship processing; see Selecting Vendors for Drop Ship Processing (MDSP).
CWDirect Rel 5.0 Pick/Authorization Listing KBOTTGER AAR0008 8/09/01 14:29:52 Page 1 KAB Co. Billing batch # . . . . . . : 1319 Picks ready to print . . . : 3 Picks awaiting authorization: 3 Picks with decline auth . . : 0 Total picks . . . . . . . . : 6 |
Contents:
• Billing batch number. This field is not included when you generate this report as part of drop ship processing.
• Picks ready to print
• Picks awaiting authorization
• Picks with decline authorization
• Total picks
Paymentech Batch Processing 96-Byte Revision 1.6.2 Layouts
Purpose: This table displays the file layout of data sent to Paymentech for batch authorizations and data received from Paymentech for batch authorizations. Refer to the Paymentech Specifications Guide for more information on Paymentech processing and additional files sent to Paymentech for authorization transactions. If you are using Paymentech Batch Processing 96-Byte Revision 1.7.1, see the CWIntegrate CWDirect/Paymentech Integration Reference for record layouts.
Position |
Length |
Data Type |
Field Name |
CWDirect Field |
Description |
Transaction File Header Record |
|||||
1-4 |
4 |
A |
Constant |
PID= |
|
5-10 |
6 |
N |
Presenter’s ID (PID) |
Presenter’s ID from the Authorization Service file. |
Assigned by Paymentech. |
11 |
1 |
A |
Filler |
|
Blank |
12-19 |
8 |
A |
PID password |
PID password from the Authorization Service file. |
Assigned by Paymentech. |
20 |
1 |
A |
Filler |
|
Blank |
21-24 |
4 |
A |
Constant |
|
SID= |
25-30 |
6 |
N |
Submitter’s ID (SID) |
Submitter’s ID from the Authorization Service file. |
Assigned by Paymentech. |
31 |
1 |
A |
Filler |
|
Blank |
32-39 |
8 |
A |
SID password |
SID password from the Authorization Service file. |
Assigned by Paymentech. |
40 |
1 |
A |
Filler |
|
Blank |
41-45 |
5 |
A |
Constant |
|
START |
46-47 |
2 |
A |
Filler |
|
Blank |
48-53 |
6 |
A |
Creation date |
System date when the transaction was created. |
YYMMDD format (optional). |
54 |
1 |
A |
Filler |
|
Blank |
55-58 |
4 |
A |
Revision number |
|
01.6, left-justified and zero-filled. |
59 |
1 |
A |
Filler |
|
Blank |
60-70 |
11 |
A |
Submission number |
|
Populated by Paymentech. |
71-88 |
18 |
A |
Filler |
|
Blank |
89-96 |
8 |
A |
Merchant space |
|
Unique file ID supplied by the merchant (optional). |
1 |
1 |
A |
Constant |
|
S |
2-7 |
6 |
N |
Division number |
Merchant ID number for the authorization service. The system uses the following hierarchy to determine the merchant ID number to send to Paymentech: • Merchant # from the CC Paytype Cross Ref file. • Merchant ID override from the Merchant ID Override file. • Merchant ID from the Authorization Service file. |
Assigned by Paymentech (required). |
8-23 |
16 |
A |
Merchant’s order number |
This field is concatenated as: company#/order#/order payment method sequence#/sequence# |
This field ties the request by CWDirect to the response Paymentech provides. This number should be unique to the transaction and stored in the Deposit file. This field is left justified/blank filled. |
24-25 |
2 |
A |
Action |
Deposit Processing The system sends an action code of B for: • all pay plan deposits, except for the first deposit of an installment plan. • regular (non-pay plan) deposits whose authorization has expired. You can review the authorization expiration date at the Authorization History Details Window. Additionally, the system updates the Authorization History record with the new authorization number. The system sends an action code of D for all regular (non-pay plan) deposits as long as there is an authorization code for the invoice pay method and the authorization has not expired. |
Action requested, right-justified and blank filled. Valid values: A = Authorize B = Conditional deposit D = Deposit G = Verify only (dollar amount should be $0.00) H = Validate and deposit I = Verify and deposit J = Pre-note only - credit N = Refund O = Forced validate P = Pre-note only - debit R = Refund V = Validate only (dollar amount should be $0.00) Y = Verify and pre-note |
26-27 |
2 |
A |
Method of payment |
Paytype code from the Authorization Service Paytype file. |
Methods of payment. AX = AmericanExpress/ Optima CB = CarteBlanche DC = Diners Club DI = Discover (Novus) EC = Electronic Check GC = GE TwinPay Credit GD = GE TwinPay Debit JC = JCB MC = MasterCard SW = Switch/Solo VI = VISA/Delta |
28-46 |
19 |
A |
Account number |
Credit card number from the Order Pay Method file. If you use credit card encryption, the system decrypts the credit card number before sending it to the service bureau. |
Left-justified and blank filled. |
47-50 |
4 |
A |
Expiration date |
Expiration date from the Order Pay Method file. |
MMYY format (optional). |
51-62 |
12 |
N |
Amount |
Amount authorized from the CC Authorization Trans file or the amount deposited from the CC Deposit Transaction file. If the Use Alternate Currency Pricing (H89) system control value is set to Y and the order is associated with an alternate currency (a currency code and conversion rate are defined in the Order Header Extended file), the system converts the local amount to the alternate (foreign) amount and sends the alternate amount to Paymentech. |
2 decimals implied; right-justified and zero-filled. |
63-65 |
3 |
N |
Currency code |
Currency code from the Order Header Extended file. If currency code is blank, use 840; otherwise match the authorization service currency in the Auth Service Currency file and populate this field with the appropriate code. |
Valid values: 036 = Australian dollars 040 = Austria (Austrian) Schilling 056 = Belgium Francs 826 = British Pounds Sterling 124 = Canadian Dollars 208 = Danish Krone (Krona) 978 = Euro 246 = Finland (Finnish) Marrkka 250 = French Francs 280 = German Deutsche Marks 300 = Greece Drachma 344 = Hong Kong (Dollars) |
|
|
|
|
|
380 = Italian Lira 372 = Irish Punt 392 = Japanese Yen 458 = Malaysia Ringitt 528 = Netherlands Dutch Guilders 554 = New Zealand Dollars 578 = Norwegian Krone (Krona) 620 = Portugal (Portuguese) Escudo 702 = Singapore Dollar 710 = South African Rand 724 = Spanish Peseta 752 = Sweden (Swedish) Krona 756 = Swiss (Switzerland) Franc 840 = U.S. Dollars |
66-68 |
3 |
N |
Response reason code |
|
Result of action requested. Note: If action code is Authorization (A) or Conditional Deposits (B), this field should be blank. It will be populated by Paymentech when returning the response. For Deposit (D) transactions, this field should be populated with the information provided from the authorization response. |
69 |
1 |
A |
Transaction type |
Indicates where the authorization transaction originated. • If the Internet order field in the Order Header file is set to I (internet order) or the order type matches the order type defined in the E-Commerce Order Type (G42) system control value, the transaction type is 7. The credit card must be VISA or MasterCard; otherwise the transaction type is 1. • If the Internet order field in the Order Header file is blank (regular order), the transaction type is 1. |
Valid values: R = Retail merchant 1 = Single transaction mail/telephone order 2 = Recurring transaction 3 = Installment payment 5 = Secure electronic commerce transaction 6 = Non-authenticated SET transaction 7 = Non-SET transaction channel encrypted 8 = Non-secure electronic commerce transaction |
70 |
1 |
A |
Reserved |
|
Reserved - do not use |
71-76 |
6 |
N |
Response date |
The date is stored in the Deposit file. |
YYMMDD format. Note: If action code is Authorization (A) or Conditional Deposits (B), this field should be blank. It will be populated by Paymentech when returning the response. For Deposit (D) transactions, this field should be populated with the information provided from the authorization response. |
77-82 |
6 |
A |
Authorization/ Verification Code |
Response code from the CC Vendor Response file for authorization. |
Left-justified. Note: If action code is Authorization (A) or Conditional Deposits (B), this field should be blank. It will be populated by Paymentech when returning the response. For Deposit (D) transactions, this field should be populated with the information provided from the authorization response. |
83-84 |
2 |
A |
AVS/AAV response code |
Response code from the CC Vendor Response file for address verification. |
AVS/AAV result (optional). Note: If action code is Authorization (A) or Conditional Deposits (B) this field should be blank. It will be populated by Paymentech when returning the response. |
85 |
1 |
A |
Reserved |
|
Reserved - do not use. |
86 |
1 |
A |
Fraud indicator |
|
Valid values: Y = Partial participants blank = Non-participants/full participants |
87-89 |
3 |
A |
Encryption flag |
|
Valid values: F = FUSA program C = Citibank program blank = no encryption |
90-91 |
2 |
A |
Reserved |
|
Blank |
92 |
1 |
A |
Filler |
|
Blank |
93-96 |
4 |
A |
Merchant space |
|
For merchant use (optional). |
Transaction File Product Record: Procurement Level 2 The system sends this record during deposit processing if the Send Data for Level II/III Discounting (I12) system control value is set to Y and: • the authorization service code is PMT (Paymentech). • the action code in the Transaction File Detail Record is: • B: conditional deposit • D: deposit • R: refund • the method of payment in the Transaction File Detail Record is: • MC: Mastercard • VI: Visa • AX: American Express • the credit card number falls within a range of credit card numbers in the Level II Bin Range file. The Level II Bin Range file identifies those credit cards that are eligible for level II discounting. It is your responsibility to populate this file with data from Paymentech. Note: To qualify, the number of positions in the level II bin range must match the number of positions in the credit card number. For example, if the credit card number is 4788250000121444, the level II bin range level must be 16 positions. |
|||||
1 |
1 |
A |
Product record identifier |
|
P |
2-3 |
2 |
A |
Product record type |
|
PC |
4-6 |
3 |
A |
Product record sequence number |
|
001 |
7-23 |
17 |
A |
Customer reference number |
The purchase order number from the Purchase order # field in the Order Ship To file. If a purchase order number is not defined, this is the order number from the Order # field in the Order Ship To file. Note: If the Consolidated Invoice (B49) system control value is set to Y and the Invoice Consolidation Method (E29) system control value is set to ORDER, the system uses the purchase order number from the first order ship to whose Purchase order # field is populated. |
Purchase order number or other number used by the Merchant’s customer to track the order. Left justified and blank filled. Note: For level II processing, this field is not required; however, it must be populated to qualify for a lower rate. For level III processing, this field is required. If this field is not populated, the system rejects the transaction. |
24-35 |
12 |
N |
Sales tax amount |
The sales tax amount from the Tax field in the Invoice Payment Method file. If more than one invoice exists, the system uses the tax amount from the first invoice. |
Amount of sales tax assessed to the transaction. 2 decimals implied, right justified and zero filled. Note: For level II processing, this field is not required; however, it must be populated to qualify for a lower rate. For level III processing, this field is required. If this field is not populated, the system rejects the transaction. |
36-96 |
61 |
A |
Filler |
|
Blank |
Transaction File Product Record: Fraud Fraud record is used for authorizations and conditional deposits only. |
|||||
1 |
1 |
A |
Product record identifier |
|
P |
2-3 |
2 |
A |
Product record type |
|
FR |
4-6 |
3 |
N |
Product record sequence |
|
001 |
7-10 |
4 |
A |
Card security value |
Card security value defined for the credit card payment method requiring authorization in the Order Payment Method file. |
Identifies the card security value provided by the cardholder. Note: The card identification number is only available for online authorizations; once an order is accepted, the system removes the card identification number from the order, even if the order has not received an approved online authorization. American Express: The card security value, or CID (card identification number), is a 4-digit number imprinted, not embossed, on an American Express credit card. The card security value displays above and to the right of the imprinted credit card number on the front of the card. The system passes all 4 positions of the card security value. Discover: The card security value, or CID (card identification number), is a 3-digit number in reverse indent printing located on the signature panel on the reverse side of the credit card following the account number. The system passes only the last 3 positions of the card security value. |
|
|
|
|
|
VISA: The card security value, or CVV2 (card verification value), is a 3-digit number in reverse indent printing located on the signature panel on the reverse side of the credit card following the account number. The system passes only the last 3 positions of the card security value. Master Card: The card security value, or CVC2 (card validation code), is a 3-digit number in reverse indent printing located on the signature panel on the reverse side of the credit card following the account number. See Credit Card Security Service (CID, CVV2, CVC2) for more information on card security processing. The system passes only the last 3 positions of the card security value. Left-justified and blank filled. |
11 |
1 |
A |
Card security presence |
Card security presence defined for the credit card payment method requiring authorization in the Order Payment Method file. |
Supported by VISA, Discover, MasterCard, and AmericanExpress only. Valid values: 1 = Card security value is present on card. 2 = Card security value is present on card, but is illegible. 9 = Card holder states that the card has no security value. See Credit Card Security Service (CID, CVV2, CVC2) for more information on card security processing. |
12-96 |
85 |
A |
Filler |
|
Blank. |
Transaction File Product Record: Retail Enable |
|||||
1 |
1 |
A |
Product record identifier |
|
P |
2-3 |
2 |
A |
Product record type |
|
RR |
4-6 |
3 |
N |
Product record sequence |
|
001 |
7-22 |
16 |
A |
Terminal identification |
|
Right-justified and blank filled. |
23-36 |
14 |
A |
Batch identification |
|
Right-justified and blank filled. |
37-96 |
60 |
A |
Filler |
|
Blank. |
1 |
1 |
A |
Product record identifier |
|
A |
2 |
1 |
A |
Address type |
|
For credit card transactions: B = Zip only or Consumer’s name (asterisk should precede last name). Note: Required for American Express procurement record and is not used for AVS or AAV verification. E = Consumer employer information. G = Person receiving gift. I = Consumer IP address. L = Consumer email address. S = Ship to address (asterisk should precede last name). Note: Required for American Express procurement record and is not used for AVS or AAV verification. |
|
|
|
|
|
For ECP transactions: M = Name (asterisk should proceed last name) as it appears on the check followed by any necessary extension records. Extension records indicators: 2 = 1st extension record 3 = 2nd extension record 4 = 3rd extension record 5 = 4th extension record |
3-32 |
30 |
A |
Address line |
|
Uppercase only. |
33 |
1 |
A |
Telephone type |
|
Valid values: D = Day phone number H = Home phone number N = Night phone number W = Work phone number |
34-47 |
14 |
A |
Telephone number |
|
AAAEEENNNXXXX format where: AAA = Area code EEE = Exchange NNNN = Number XXXX = Extension Blank if not used. |
48-49 |
2 |
A |
Country code |
|
Country code: US = United States CA = Canada GB = Great Britain |
50-96 |
47 |
A |
Filler |
|
Blank |
Transaction File Batch Totals Record |
|||||
1-7 |
7 |
A |
Constant |
|
B RECS= |
8-16 |
9 |
N |
Batch record count |
Total number of orders in this batch of authorizations. |
Total count of all records prior to the batch totals record. |
17 |
1 |
A |
Filler |
|
Blank. |
18-22 |
5 |
A |
Constant |
|
ORDS= |
23-31 |
9 |
N |
Batch order count |
Total number of orders in this batch of authorizations. |
All detail records. |
32 |
1 |
A |
Filler |
|
Blank. |
33-37 |
5 |
A |
Constant |
|
$TOT= |
38-51 |
14 |
N |
Batch amount total |
Total dollar amount of sales in this batch of authorizations. |
Gross amount total (absolute amount sales + absolute amount refunds + absolute amount authorizations) |
52 |
1 |
A |
Filler |
|
Blank. |
53-58 |
6 |
A |
Constant |
|
$SALE= |
59-72 |
14 |
N |
Batch amount sales |
Total dollar amount of sales in this batch of authorizations. |
All sales transactions. |
73 |
1 |
A |
Filler |
|
Blank. |
74-81 |
8 |
A |
Constant |
|
$REFUND= |
82-95 |
14 |
N |
Batch amount refunds |
|
All refund transactions. |
96 |
1 |
A |
Filler |
|
Blank. |
Transaction File Totals Record |
|||||
1-7 |
7 |
A |
Constant |
|
T RECS= |
8-16 |
9 |
N |
File record count |
|
Total of all records prior to the Totals record. |
17 |
1 |
A |
Filler |
|
Blank. |
18-22 |
5 |
A |
Constant |
|
ORDS= |
23-31 |
9 |
N |
File order count |
|
All detail records. |
32 |
1 |
A |
Filler |
|
Blank. |
33-37 |
5 |
A |
Constant |
|
$TOT= |
38-51 |
14 |
N |
File amount total |
|
Gross amount total (absolute amount sales + absolute amount refunds + absolute amount authorizations) |
52 |
1 |
A |
Filler |
|
Blank. |
53-58 |
6 |
A |
Constant |
|
$SALE= |
59-72 |
14 |
N |
File amount sales |
|
All sales transactions deposited. |
73 |
1 |
A |
Filler |
|
Blank. |
74-81 |
8 |
A |
Constant |
|
$REFUND= |
82-95 |
14 |
N |
File amount refunds |
|
All refund transactions deposited. |
96 |
1 |
A |
Filler |
|
Blank. |
Transaction File Trailer Record |
|||||
1-4 |
4 |
A |
Constant |
|
PID= |
5-10 |
6 |
N |
Presenter’s ID (PID) |
Presenter’s ID from the Authorization Service file. |
Assigned by Paymentech. |
11 |
1 |
A |
Filler |
|
Blank. |
12-19 |
8 |
A |
PID password |
PID password from the Authorization Service file. |
Assigned by Paymentech. |
20 |
1 |
A |
Filler |
|
Blank. |
21-24 |
4 |
A |
Constant |
|
SID= |
25-30 |
6 |
N |
Submitter’s ID (SID) |
Submitter’s ID from the Authorization Service file. |
Assigned by Paymentech. |
31 |
1 |
A |
Filler |
|
Blank. |
32-39 |
8 |
A |
SID password |
SID password from the Authorization Service file. |
Assigned by Paymentech. |
40 |
1 |
A |
Filler |
|
Blank. |
41-43 |
3 |
A |
Constant |
|
END |
44-45 |
2 |
A |
Filler |
|
Blank. |
46-51 |
6 |
A |
Creation date |
|
YYMMDD format (optional). |
52-96 |
45 |
A |
Filler |
|
Blank. |
Transaction File Request for Response (RFR) Record |
|||||
1-4 |
4 |
A |
Constant |
|
PID= |
5-10 |
6 |
N |
Presenter’s ID (PID) |
|
Assigned by Paymentech. |
11 |
1 |
A |
Filler |
|
Blank. |
12-19 |
8 |
A |
PID password |
|
Assigned by Paymentech. |
20 |
1 |
A |
Filler |
|
Blank. |
21-24 |
4 |
A |
Constant |
|
SID= |
25-30 |
6 |
N |
Submitter’s ID (SID) |
|
Assigned by Paymentech. |
31 |
1 |
A |
Filler |
|
Blank. |
32-39 |
8 |
A |
SID password |
|
Assigned by Paymentech. |
40 |
1 |
A |
Filler |
|
Blank. |
41-43 |
3 |
A |
Constant |
|
RFR |
44-45 |
2 |
A |
Filler |
|
Blank. |
46-51 |
6 |
A |
Creation date |
|
YYMMDD format (optional). |
52-96 |
45 |
A |
Filler |
|
Blank. |
Transaction File "S" Record Output |
|||||
1 |
1 |
A |
Constant |
|
S |
2-7 |
6 |
N |
Division number |
|
Assigned by Paymentech. Required. |
8-23 |
16 |
A |
Merchant’s order number |
|
Number composed of any alpha, blank, digit, or punctuation combination that will be returned when we respond. This field will tie the request on your end to the response we provide you. It should be unique to the transaction and should be stored and supplied in the deposit file. Required. |
24-25 |
2 |
A |
Action |
|
Action requested. A = Authorize B = Conditional deposit D = Deposit G = Verify only H = Validate and deposit I = Verify and deposit J = Pre-note only - debit N = Refund O = Forced validate P = Pre-note only - credit R = Refund V = Validate only (dollar amount should be $0.00) Y = Verify and Pre-note |
26-27 |
2 |
A |
Method of payment (MOP) |
|
Methods of payment: AX = AmericanExpress/ Optima CB = Carte Blanche DC = Diners Club DI = Discover (Novus) EC = Electronic check GC = GW Twinpay Credit GD = GW Twinpay Debit JC = JCB MC = MasterCard SW = Switch/Solo VI = Visa/Delta |
28-46 |
19 |
A |
Account number |
|
Left-justified and blank filled. |
47-50 |
4 |
A |
Expiration date |
|
MMYY format. Optional. |
51-62 |
12 |
N |
Amount |
|
2 decimals implied, right-justified and zero-filled. |
63-65 |
3 |
N |
Currency code |
|
Valid values: 036 = Australian Dollars 040 = Austria (Austrian) Schilling 056 = Belgium Francs 826 = British Pounds Sterling 124 = Canadian Dollars 208 = Danish Krone (Krona) 978 = Euro 246 = Finland (Finnish) Marrkka 250 = French Francs 280 = German Deutsche Marks 300 = Greece Drachma 345 = Hong Kong (Dollars) 380 = Italian Lira |
|
|
|
|
|
372 = Irish Punt 392 = Japanese Yen 458 = Malaysia Ringitt 528 = Netherlands Dutch Guilders 555 = New Zealand Dollars 579 = Norwegian Krone (Krona) 620 = Portugal (Portuguese) Escudo 702 = Singapore Dollar 710 = South African Rand 724 = Spanish Peseta 752 = Sweden (Swedish) Krona 756 = Swiss (Switzerland) Franc 840 = U.S. Dollars |
66-68 |
3 |
N |
Response reason code |
|
Result of action requested. |
69 |
1 |
A |
Transaction type used |
|
Valid values: R = Retail merchant 1 = Single transaction mail/telephone order 2 = Recurring transaction 3 = Installment payment 5 = Secure electronic commerce transaction 6 = Non-authenticated SET transaction 7 = Non-SET transaction channel encrypted 8 = Non-secure electronic commerce transaction |
70 |
1 |
A |
Card security value response |
The card security value response is stored in the Vendor response 2 field in the Authorization History file. |
Response to credit card identification request. Valid values: M (match) = The card security value indicated on the card matches the card security value in the secured database. N (no match) = The card security value indicated on the card does not match the card security value in the secured database. You should be cautious in processing credit cards with a card security response of N; the transaction is possibly a fraud. P (not processed) = The card security value was not processed due to communication errors. S (should be on card) = The card security value should be present on the card (this response applies to card security presence 9). |
|
|
|
|
|
U (Unsupported by issuer) = The issuer of the credit card does not support card security identification. I (invalid) = The card security value is invalid. Do not process credit cards with a card security response of I; the transaction is possibly a fraud. See Credit Card Security Service (CID, CVV2, CVC2) for more information on card security processing. |
71-76 |
6 |
N |
Response date |
|
YYMMDD format. Stored in the Deposit file. |
77-82 |
6 |
A |
Authorization/ verification code |
The authorization/verification code is stored in the Vendor response field in the Authorization History file. |
Issued by the bank or service establishment. Stored in the Deposit file. |
83-84 |
2 |
A |
AVS/AAV response code |
The AVS/AAV response code is stored in the AVS response field in the Authorization History file. |
Response to address verification request. |
85 |
1 |
A |
Deposit flag |
|
Payment deposited Y/N. |
86-87 |
2 |
A |
Reserved |
|
Reserved - do not use. |
88-92 |
5 |
A |
Filler |
|
Blank. |
93-96 |
4 |
A |
Merchant space |
|
For merchant use (optional). |
Declined Drop Ships | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 41: Defining Authorization Services (WASV) |
SO04_01r CWDirect 18.0 August 2015 OTN