• Paymentech Online Heartbeat Request File
• Paymentech Online Heartbeat Response File
• Paymentech Online Authorization Request File
• Paymentech Online Authorization Response File
• Paymentech Batch Authorization Request File
• Paymentech Batch Authorization Response File
• Paymentech Batch Deposit Request File
• Paymentech Batch Deposit Response File
• Paymentech Request for Response (RFR)
Paymentech Online Heartbeat Request File
CWSerenade receives the Online Heartbeat Request file from Paymentech during the Paymentech Point-to-Point Online Heartbeat Process.
Sample transaction: See Sample Paymentech Online Transactions.
Name |
Position |
Length |
Type |
Comments |
Record Type |
1-2 |
2 |
alpha |
HO defaults. |
Format Constant |
3 |
1 |
alpha |
1 defaults. |
Sequence Number |
4-11 |
8 |
numeric |
Assigned by Paymentech. |
Current GMT Time |
12-19 |
8 |
numeric |
Current time in DDHHMMSS format. |
Each heartbeat request ends with a carriage return.
Paymentech Online Heartbeat Response File
CWSerenade generates an Online Heartbeat Response when it receives an Online Heartbeat Request from Paymentech if the PMD_ONLINE integration layer job is active; see Paymentech Point-to-Point Online Heartbeat Process.
Sample transaction: See Sample Paymentech Online Transactions.
Name |
Position |
Length |
Type |
Comments |
Record Type |
1-2 |
2 |
alpha |
HI defaults. |
Format Constant |
3 |
1 |
alpha |
1 defaults. |
Sequence Number |
4-11 |
8 |
numeric |
Assigned by Paymentech. |
Current GMT Time |
12-19 |
8 |
numeric |
Current time in DDHHMMSS format. |
Each heartbeat response ends with a carriage return.
Paymentech Online Authorization Request File
CWSerenade creates a Paymentech Online Authorization Request file during the Paymentech Point-to-Point Online Authorization Process and Paymentech Point-to-Point Online Balance Inquiry Process.
The Paymentech Online Authorization Request file is a fixed record length flat file that contains the following record types.
Sample transaction: See Sample Paymentech Online Transactions.
Record |
Begins With |
When Included |
P6 |
Always included. |
|
AB |
Included if the AVS flag for the country cross reference record on the Work with Authorization Service Country Screen is Y, the vendor paytype code on the Work with Paytype Cross Reference Screen is not SW (Switch Card) or SV (Stored Value Card), and a last name is defined for the bill to customer (or sold to customer if a bill to customer is not defined). |
|
FR |
Included if a security presence or value is defined for the payment. |
|
VA |
Included if the vendor payment method is VI (Visa) and an authentication value exists for the payment in the Order Payment Method table. |
|
MA |
Included if the vendor payment method is MC (MasterCard) and an authentication value exists for the payment in the Order Payment Method table. |
|
SW |
Included if the vendor paytype code is SW (Switch card) and a start date or issue number is defined for the debit card payment. |
Name |
Position |
Length |
Type |
Comments |
Detail Record for Online Request This record contains the details of the authorization transaction, such as the card number and the amount to authorize. Example: P6 0070000368500000VI***** REMOVED *****12120205940000000010878401 A where: • P is the Record Type • 6 is the Format Constant • 0070000368500000 is the Merchant Order Number • VI is the Method of Payment • ****REMOVED***** is the Account Number (masked in the log for data security) • 1212 is the Expiration Date • 020594 is the Division Number • 1087 is the Amount • 840 is the Currency Code • 1 is the Transaction Type • A is the Action Code |
||||
1 |
1 |
alpha |
P defaults. |
|
2 |
1 |
numeric |
6 defaults. |
|
Filler |
3 |
1 |
alpha |
Blank filled. |
4-19 |
16 |
alpha |
A unique number made up of the CWSerenade company code + order number. For balance inquiry transactions, this is the CWSerenade company code only. From the Company and Order # in the Order Payment Method table. |
|
20-21 |
2 |
alpha |
The vendor paytype code associated with the authorization request; this is the code the authorization service uses to identify a method of payment. From the CPC vendor paytype/code in the CC Paytype Cross Ref table. |
|
22-40 |
19 |
alpha |
The card number for the payment method requesting authorization. Left-justified and blank filled. From the Credit card number in the Order Payment Method table. If you use encryption, the system decrypts the card number before sending it to the service bureau. |
|
41-44 |
4 |
alpha |
The date the card requesting deposit expires in MMYY format. From the OPM expiration date in the Order Payment Method table. 1249 defaults if the Method of Payment is stored value card. |
|
45-50 |
6 |
numeric |
The account number assigned by the service bureau to identify transmissions. CWSerenade uses the following hierarchy to determine the merchant ID number to send: • Merchant # from the CC Paytype Cross Ref table. • Merchant ID override from the Merchant ID Override table. • Merchant ID from the Authorization Service table. |
|
51-62 |
12 |
numeric |
The amount on the card requesting authorization, with 2 implied decimals. Right-justified and zero filled. Zero-filled for balance inquiry transactions. If the Use Alternate Currency Pricing (H89) system control value is selected and a currency code and conversion rate are defined in the Order Header Extended table, the alternate currency displays; otherwise, the local currency displays. From the Auth Amount in the Online Authorization table. Example: 0000000002078 represents $20.78. |
|
63-65 |
3 |
numeric |
The currency code used by the authorization service to define a currency. From the ASC currency code in the Auth Service Currency table. |
|
66 |
1 |
alpha |
Represents either: • An electronic commerce indicator code, received from an authentication service such as Visa's Verified by Visa program or MasterCard's SecureCode program, indicating the level of security provided for a credit card transaction placed over the internet. • A value indicating if the order was placed on a web storefront. • 7 defaults if the Ecomm Indic in the Order Payment Method table is YES. • 1 defaults if the Ecomm Indic in the Order Payment Method table is NO. From the Ecommerce Indicator field in the Order Payment Method table. If the Ecommerce Indicator in the Order Payment Method table is blank, from the E-commerce indicator (Future use sts 1 field) in the Order Header table. |
|
Encryption Flag |
67-69 |
3 |
alpha |
Blank filled. |
Fraud Indicator |
70 |
1 |
alpha |
Blank filled. |
71 |
1 |
alpha |
A defaults for authorizations. K defaults for stored value card activations. E defaults for authorization reversals. Q defaults for balance inquiry. |
|
Reserved |
72 |
1 |
alpha |
Blank filled. |
Bill To Address Record for Online Request This record contains bill to address information and is used for AVS processing. Example: AB BARBARA *WILLIAMS 109 RIVER LN USTEMPLETON MA01468-1566 where: • AB is the Format Indicator • BERNADETTE *MIRANDA is the Name Text • 109 RIVER LN is Address Line 1 • US is the Country Code • TEMPLETON is the City • MA is the State • 01468-1566 is the Zip Code |
||||
1-2 |
2 |
alpha |
AB defaults. |
|
Telephone Type |
3 |
1 |
alpha |
D = Day time phone number. N = Night time phone number. |
Telephone Number |
4-17 |
14 |
alpha |
The bill to customer’s day time phone number; if a day time phone number is not defined, this is the bill to customer’s evening phone number. If a bill to customer is not defined, this is the sold to customer’s day time phone number; if a day time phone number is not defined, this is the sold to customer’s evening phone number. From the Phone # field in the Customer Bill To Phone # or Customer Sold To Phone # table. |
5-47 |
30 |
alpha |
The first name + last name of the bill to customer on the order, each value separated by an asterisk (*). If a bill to customer is not defined, this is the first name + last name of the sold to customer on the order. Example: BERNADETTE *MIRANDA From the First name and Last name in the Customer Bill To or Customer Sold To table. |
|
48-77 |
30 |
alpha |
The first address line of the bill to customer on the order. If a bill to customer is not defined, this is the first address line of the sold to customer on the order. From the Street Address in the Customer Bill To or Customer Sold To table. |
|
Address Line 2 |
78-105 |
28 |
alpha |
The apartment number defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the apartment number defined for the sold to customer on the order. From the Apartment in the Customer Bill To or Customer Sold To table. |
106-107 |
2 |
alpha |
The authorization service country code defined for the country cross reference record on the Work with Authorization Service Country Screen. From the Auth Service Country in the Auth Service Country table. |
|
108-127 |
20 |
alpha |
The city defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the city defined for the sold to customer on the order. From the City in the Customer Bill To or Customer Sold To table. |
|
128-129 |
2 |
alpha |
The state defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the state defined for the sold to customer on the order. From the State in the Customer Bill To or Customer Sold To table. |
|
130-139 |
10 |
alpha |
The zip defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the zip defined for the sold to customer on the order. Note: If the zip code is 9 positions, the system inserts a hyphen before the last 4 positions; for example 01468-1566. From the Zip in the Customer Bill To or Customer Sold To table. |
|
Fraud Record for Online Request Included if a security value or presence is defined for the payment. Example: FR1234 where: • FR is the Format Indicator • 1234 is the Card Security Value |
||||
1-2 |
2 |
alpha |
FR defaults. |
|
Card Security Presence |
3 |
1 |
alpha |
Indicates whether a card security value is defined for the credit card. 1 = CID number present on card. 2 = CID number present on card, but not legible. 9 = CID number not present on card. From the OPM card security presence field in the Order Payment Method table. Included only if a card security value is not defined. |
4-7 |
4 |
alpha |
The card security number defined for the credit card payment. From the OPM card security value field in the Order Payment Method table. |
|
Visa Authentication Record for Online Request Included only if the vendor payment method is VI (Visa) and an authentication value exists for the payment in the Order Payment Method table. Example: VA JHYN+7YFI1EUAREAAAAV6YF8F6S= where: • VA is the Format Indicator • JHYN+7YFI1EUAREAAAAV6YF8F6S= is the Cardholder Verification Value |
||||
1-2 |
2 |
alpha |
VA defaults. |
|
Transaction ID |
3-42 |
40 |
alpha |
Blank filled. |
43-82 |
40 |
alpha |
A code received from an authentication service, such as Visa’s Verified by Visa program, indicating whether the card authentication password the cardholder entered on the web storefront was approved for the credit card. From the Authentication value in the Order Payment Method table. |
|
MasterCard Authentication Record for Online Request Included only if the vendor payment method is MC (MasterCard) and an authentication value exists for the payment in the Order Payment Method table. Example: MAJHYN+7YFI1EUAREAAAAV6YF8F6S= where: • MA is the Format Indicator • JHYN+7YFI1EUAREAAAAV6YF8F6S= is the Authentication Value |
||||
1-2 |
2 |
alpha |
MA defaults. |
|
3-34 |
32 |
alpha |
A code received from an authentication service, such as MasterCard’s Secure Code program, indicating whether the card authentication password the cardholder entered on the web storefront was approved for the credit card. From the Authentication value in the Order Payment Method table. |
|
Switch Record for Online Request Included if the vendor paytype code is SW (Switch card) and a start date or issue number is defined for the debit card payment. Example: SW1203 where: • SW is the Format Indicator • 1203 is the Card Start Date |
||||
1-2 |
2 |
alpha |
SW defaults. |
|
3-6 |
4 |
alpha |
The start date for the switch card, in MMYY format. From the Card start date field in the Order Payment Method table. Included only if a card issue number is not passed. |
|
Card Issue Number |
7-8 |
2 |
alpha |
The card issue number for the switch card. From the Card issue # field in the Order Payment Method table. |
Paymentech Online Authorization Response File
When a Paymentech Online Authorization Response file is ready, CWSerenade retrieves the file from Paymentech; see Paymentech Point-to-Point Online Authorization Process and Paymentech Point-to-Point Online Balance Inquiry Process.
CWSerenade directly maps the information in the response to a record in the OnLine Authorization table.
Once the OnLine Authorization record is updated, CWSerenade continues with regular online authorization processing; see Performing Online Credit Card Authorizations.
Sample transaction: See Sample Paymentech Online Transactions.
Name |
Position |
Length |
Type |
Comments |
Detail Record for Online Response This record contains the details of the authorization response, such as whether the authorization was confirmed or declined. Example: T60070000368500000100110727tst301I3 ***** REMOVED *****1212VI where: • T is the Record Type • 6 is the Format Constant • 0070000368500000 is the Merchant Order # • 100 is the Response Reason Code • 110727 is the Response Date • tst301 is the Authorization Verification Code • I3 is the AVS/AVV Response Code • ***** REMOVED ***** is the Account Number • 1212 is the Expiration Date • VI is the Method of Payment |
||||
1 |
1 |
alpha |
T defaults. |
|
2 |
1 |
numeric |
6 defaults. |
|
3-18 |
16 |
alpha |
A unique number made up of the CWSerenade company code + order number. For balance inquiry transactions, this is the CWSerenade company code only. Corresponds to the Company and Order # in the Authorization History table. |
|
19-21 |
3 |
numeric |
The authorization response for the card. Updates Authorization Vendor Response in the CC Authorization History table. |
|
22-27 |
6 |
numeric |
The date in YYMMDD format the response was processed by Paymentech. Corresponds to the Authorization date in the CC Authorization History table. |
|
28-33 |
6 |
alpha |
The authorization code for the deposit. Updates Authorization code in the CC Authorization Transaction and CC Authorization History table. Also creates an Authorization History record when authorizations are processed. |
|
34-35 |
2 |
alpha |
The address verification response for the card. Updates AVS Response in the CC Authorization History table. |
|
Card Security Value Response |
36 |
1 |
alpha |
Response returned for card security. Updates the Vendor Response 2 field in the Authorization History table. Not included for stored value card transactions. Values returned: M = Value Matched. N = Value Not Matched. P = Not Processed. S = Should Be On Card. U = Unsupported By Issuer. I = Invalid. |
37-55 |
19 |
alpha |
The card number for the payment method receiving the authorization response. Left-justified and blank filled. Corresponds to the Credit card # in the CC Authorization Transaction table. For data security, CWSerenade masks the card number in the Trace log. |
|
56-59 |
4 |
alpha |
The date the card expires in MMYY format. Corresponds to the OPM expiration date in the Order Payment Method table. 1249 defaults if the Method of Payment is stored value card. |
|
60-61 |
2 |
alpha |
The vendor paytype code associated with the authorization request; this is the code the authorization service uses to identify a method of payment. Corresponds to the CPC vendor paytype/code in the CC Paytype Cross Ref table. Note: For Diner’s Club, Paymentech sends back DD. |
|
Recurring Payment Advice |
62-63 |
2 |
numeric |
Blank filled. |
Stored Value Current Balance |
64-75 |
12 |
numeric |
The current balance on the stored value card. Included for balance inquiry transactions only. |
Stored Value Previous Balance |
76-87 |
12 |
numeric |
The previous balance on the stored value card. Included for balance inquiry transactions only. |
CAVV Response Code |
88 |
1 |
alpha |
Blank filled. |
Paymentech Batch Authorization Request File
During the Paymentech Point-to-Point Batch Authorization Process, Paymentech Point-to-Point Activation Process, and Paymentech Point-to-Point Authorization Reversal Process, CWSerenade creates a fixed record length flat file containing the following record types.
Record |
Begins With |
When Included |
PID= |
Always included |
|
S |
Always included |
|
E |
Included only if the vendor payment method is VI (Visa) and an authentication value exists for the payment in the Order Payment Method table. |
|
E |
Included only if the vendor payment method is MC (MasterCard) and an authentication value exists for the payment in the Order Payment Method table. |
|
Transaction File Extension Record: Switch Card (UK Debit) for Batch Request |
SW |
Included only if the vendor paytype code is SW (Switch card) and a start date or issue number is defined for the debit card payment. |
FR |
Included if a security presence or value is defined for the payment. |
|
A |
Included only if the AVS flag for the country cross reference record on the Work with Authorization Service Country Screen is Y, the vendor paytype code on the Work with Paytype Cross Reference Screen is not SW (Switch Card) or SV (Stored Value Card), and a last name is defined for the bill to customer (or sold to customer if a bill to customer is not defined). |
|
A2 |
Included only if a street address (address line 1) is defined for the bill to customer (or sold to customer if a bill to is not defined) on the order. |
|
A3 |
Included only if a second address line is defined for the bill to address (or sold to address if a bill to is not defined) on the order. |
|
A4 |
Included only if a city is defined for the bill to address (or sold to address if a bill to is not defined) on the order. |
|
B |
Always included after all detail and supplemental records. |
|
T |
Always included |
|
PID= |
Always included |
Sample transaction: See Sample Paymentech Batch Transactions.
Name |
Position |
Length |
Type |
Comments |
Authorization Header Record for Batch Request This record identifies the source of the submitted file and contains the presenter and submitter information used to match a request to a response. Example: PID=192864 COMMERCI SID=192864 COMMERCI START 110216 01.7 A304 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • START is the third Constant • 110216 is the Create Date • 01.7 is the Revision Number • A304 is the Merchant Space |
||||
Constant |
1-4 |
4 |
alpha |
PID= defaults. |
Presenter’s ID |
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. From the Presenter’s ID in the Authorization Service table. |
Filler |
11 |
1 |
alpha |
Blank filled. |
PID Password |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. From the PID Password in the Authorization Service table. |
Filler |
20 |
1 |
alpha |
Blank filled. |
Constant |
21-24 |
4 |
alpha |
SID= defaults. |
Submitter’s ID |
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. From the Submitter’s ID in the Authorization Service table. |
Filler |
31 |
1 |
alpha |
Blank filled. |
SID Password |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. From the SID Password in the Authorization Service table. |
Filler |
40 |
1 |
alpha |
Blank filled. |
Constant |
41-45 |
5 |
alpha |
START defaults. |
Filler |
46-47 |
2 |
alpha |
Blank filled. |
Create Date |
48-53 |
6 |
alpha |
The date when the request was sent to the service bureau in YYMMDD format. |
Filler |
54 |
1 |
alpha |
Blank filled. |
Revision Number |
55-58 |
4 |
alpha |
01.7 defaults. Left-justified and zero filled. |
Filler |
59 |
1 |
alpha |
Blank filled. |
Submission Number |
60-70 |
11 |
alpha |
Blank filled; populated by Paymentech. |
Filler |
71-88 |
18 |
alpha |
Blank filled. |
Merchant Space |
89-96 |
8 |
alpha |
A + the next available number from the Batch Auth File Trace Number number assignment value. Example: A999 |
Detail Record for Batch Request This record contains the details of the authorization transaction, such as the card number and the amount to authorize. Example: S0205940070000370401001 AVI***** REMOVED *****1212000000001087840 7 where: • S is the Constant • 020594 is the Division Number • 00700003370401001 is the Merchant Order Number • A is the Action Code • VI is the Method of Payment • ***** REMOVED ***** is the Account Number (masked in the log for data security) • 1212 is the Expiration Date • 000000001087 is the Amount • 840 is the Currency Code • 7 is the Transaction Type |
||||
Constant |
1 |
1 |
alpha |
S defaults. |
Division Number |
2-7 |
6 |
numeric |
The account number assigned by the service bureau to identify transmissions. CWSerenade uses the following hierarchy to determine the merchant ID number to send: • Merchant # from the CC Paytype Cross Ref table. • Merchant ID override from the Merchant ID Override table. • Merchant ID from the Authorization Service table. |
Merchant Order Number |
8-23 |
16 |
alpha |
A unique number made up of the CWSerenade company code + order number + order payment method sequence number + authorization sequence number. For stored value card transactions, this is the company code + order number only. From the Company, Order #, OPM Seq # in the CC Authorization Transaction table and AUH Seq # in the Authorization History table. |
Action Code |
24-25 |
2 |
alpha |
A defaults for authorizations. K defaults for stored value card activations. E defaults for authorization reversals. Q defaults for balance inquiry. |
Method of Payment |
26-27 |
2 |
alpha |
The vendor paytype code associated with the authorization request; this is the code the authorization service uses to identify a method of payment. From the CPC vendor paytype/code in the CC Paytype Cross Ref table. |
Account Number |
28-46 |
19 |
alpha |
The card number for the payment method requesting authorization. Left-justified and blank filled. From the Credit card number in the Order Payment Method table. If you use encryption, the system decrypts the card number before sending it to the service bureau. |
Expiration Date |
47-50 |
4 |
alpha |
The date the card expires in MMYY format. From the OPM expiration date in the Order Payment Method table. 1249 defaults if the Method of Payment is stored value card. |
Amount |
51-62 |
12 |
numeric |
The amount on the card requesting authorization, with 2 implied decimals. Right-justified and zero filled. For activation transactions, this is the amount that requires activation. For authorization reversal transactions, this is the amount to reimburse. If the Use Alternate Currency Pricing (H89) system control value is selected and a currency code and conversion rate are defined in the Order Header Extended table, the alternate currency displays; otherwise, the local currency displays. From the Dollar amt for auth in the CC Authorization Transaction table. Example: 0000000002078 represents $20.78. |
Currency Code |
63-65 |
3 |
numeric |
The currency code used by the authorization service to define a currency. From the CUR currency code in the CC Authorization Transaction table. |
Response Reason Code |
66-68 |
3 |
numeric |
Blank filled. |
Transaction Type |
69 |
1 |
alpha |
Represents either: • An electronic commerce indicator code, received from an authentication service such as Visa's Verified by Visa program or MasterCard's SecureCode program, indicating the level of security provided for a credit card transaction placed over the internet. • A value indicating if the order was placed on a web storefront. • 7 defaults if the Ecomm Indic in the Order Payment Method table is YES. • 1 defaults if the Ecomm Indic in the Order Payment Method table is NO. From the Indic in the Order Payment Method table. If the Ecomm Indic in the Order Payment Method table is blank, from the E-commerce indicator (Future use sts 1 field) in the Order Header table. |
Reserved |
70 |
1 |
alpha |
Blank filled. |
Response Date |
71-76 |
6 |
numeric |
Blank filled. |
Authorization Verification Code |
77-82 |
6 |
numeric |
Blank filled. |
AVS Response Code |
83-84 |
2 |
alpha |
Blank filled. |
Reserved |
85 |
1 |
alpha |
Blank filled. |
Fraud Indicator |
86 |
1 |
alpha |
Blank filled. |
Encryption Flag |
87-89 |
3 |
alpha |
Blank filled. |
Reserved |
90-91 |
2 |
alpha |
Blank filled. |
Filler |
92 |
1 |
alpha |
Blank filled. |
Merchant Space |
93-96 |
4 |
alpha |
Blank filled. |
Visa Authentication Record for Batch Request Included only if the vendor payment method is VI (Visa) and an authentication value exists for the payment in the Order Payment Method table. Example: EVI002 JHYN+7YFI1EUAREAAAAV6YF8F6S= where: • E is the Extension Record ID • VI is the Extension Record MOP Type • 002 is the Extension Record • JHYN+7YFI1EUAREAAAAV6YF8F6S= is the CAVV Response Code |
||||
Extension Record ID |
1 |
1 |
alpha |
E defaults. |
Extension Record MOP Type |
2-3 |
2 |
alpha |
VI defaults. |
Extension Record |
4-6 |
3 |
numeric |
002 defaults. |
Transaction ID |
7-46 |
40 |
alpha |
Blank filled. |
Cardholder Authentication Verification Value |
47-86 |
40 |
alpha |
A code received from an authentication service, such as Visa’s Verified by Visa program, indicating whether the card authentication password the cardholder entered on the web storefront was approved for the credit card. From the Authentication value in the Order Payment Method table. |
CAVV Response Code |
87 |
1 |
alpha |
Blank filled. |
Filler |
88-96 |
9 |
alpha |
Blank filled. |
MasterCard Authentication Record for Batch Request Included only if the vendor payment method is MC (MasterCard) and an authentication value exists for the payment in the Order Payment Method table. Example: EMC002JHYN+7YFI1EUAREAAAAV6YF8F6S= where: • E is the Extension Record ID • MC is the Extension Record MOP Type • 202 is the Extension Record • JHYN+7YFI1EUAREAAAAV6YF8F6S= is the Authentication Value |
||||
Extension Record ID |
1 |
1 |
alpha |
E defaults. |
Extension Record MOP Type |
2-3 |
2 |
alpha |
MC defaults. |
Extension Record |
4-6 |
3 |
numeric |
002 defaults. |
Authentication Value |
7-38 |
32 |
alpha |
A code received from an authentication service, such as MasterCard’s Secure Code program, indicating whether the card authentication password the cardholder entered on the web storefront was approved for the credit card. From the Authentication value in the Order Payment Method table. |
Filler |
39-96 |
58 |
alpha |
Blank filled. |
Transaction File Extension Record: Switch Card (UK Debit) for Batch Request Included only if the vendor paytype code is SW (Switch card) and a start date or issue number is defined for the payment. Example: ESW0011203 where: • E is the Extension Record ID • SW is the Product Record Type • 001 is the Product Record Seq # • 1203 is the Card Start Date |
||||
Extension Record ID |
1 |
1 |
alpha |
E defaults. |
Extension Record MOP |
2-3 |
2 |
alpha |
SW defaults. |
Extension Record Sequence # |
4-6 |
3 |
alpha |
001 defaults. |
Card Start Date |
7-10 |
4 |
numeric |
The start date of the debit card being processed, in MMYY format. Blank filled if a start date is not present. From the Card Start date in the Order Payment Method table. |
Card Issue Number |
11-12 |
2 |
numeric |
The card issue number of the debit card being processed. Right-justified and blank filled. From the OPM card issue # in the Order Payment Method table. |
Filler |
13-96 |
84 |
alpha |
Blank filled. |
Fraud Record for Batch Request Included if a security value or presence is defined for the payment. Example: PFR00112341 where: • P is the Record Identifier • FR is the Record Type • 001 is the Record Sequence • 1234 is the Card Security Value • 1 is the Card Security Presence |
||||
1 |
1 |
alpha |
P defaults. |
|
2-3 |
2 |
alpha |
FR defaults. |
|
4-6 |
3 |
numeric |
001 defaults. |
|
7-10 |
4 |
alpha |
The card security number defined for the credit card payment. From the OPM card security value field in the Order Payment Method table. |
|
11 |
1 |
alpha |
Indicates whether a card security value is defined for the credit card. 1 = CID number present on card. 2 = CID number present on card, but not legible. 9 = CID number not present on card. From the OPM card security presence field in the Order Payment Method table. Included only if a card security value is not defined. |
|
Filler |
12-96 |
85 |
alpha |
Blank filled. |
Address Record for Batch Request Included only if the AVS flag for the country cross reference record on the Work with Authorization Service Country Screen is Y, the vendor paytype code on the Work with Paytype Cross Reference Screen is not SW (Switch Card) or SV (Stored Value Card), and a last name is defined for the bill to customer (or sold to customer if a bill to customer is not defined). Example: ABBARBARA*WILLIAMS US where: • A is the Product Record ID • B is the Address Type • BERNADETTE*MIRANDA is the Address Line • US is the Country Code |
||||
Product Record ID |
1 |
1 |
alpha |
A defaults. |
Address Type |
2 |
1 |
alpha |
S defaults if the vendor paytype code on the Work with Paytype Cross Reference Screen is AX (American Express); otherwise, B defaults. |
Address Line |
3-32 |
30 |
alpha |
The first name + last name of the bill to customer on the order, each value separated by an asterisk (*). If a bill to customer is not defined, this is the first name + last name of the sold to customer on the order. Example: BERNADETTE *MIRANDA From the First name and Last name in the Customer Bill To or Customer Sold To table. |
Telephone Type |
33 |
1 |
alpha |
D = Day time phone number. N = Night time phone number. |
Telephone # |
34-47 |
14 |
alpha |
The bill to customer’s day time phone number; if a day time phone number is not defined, this is the bill to customer’s evening phone number. If a bill to customer is not defined, this is the sold to customer’s day time phone number; if a day time phone number is not defined, this is the sold to customer’s evening phone number. From the Phone # field in the Customer Bill To Phone # or Customer Sold To Phone # table. |
Country Code |
48-49 |
2 |
alpha |
The authorization service country code defined for the country cross reference record on the Work with Authorization Service Country Screen. From the Auth Service Country in the Auth Service Country table. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Address Record Extension 2 for Batch Request Included only if a street address (address line 1) is defined for the bill to customer (or sold to customer if a bill to is not defined) on the order. Example: A2109 RIVER LN where: • A is the Product Record ID • 2 is the Address Type • 109 RIVER LN is the Address Line |
||||
Product Record ID |
1 |
1 |
alpha |
A defaults. |
Address Type |
2 |
1 |
alpha |
2 defaults. |
Address Line |
3-32 |
30 |
alpha |
The first address line of the bill to customer on the order. If a bill to customer is not defined, this is the first address line of the sold to customer on the order. From the Street Address in the Customer Bill To or Customer Sold To table. |
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
Country Code |
48-49 |
2 |
alpha |
Blank filled. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Address Record Extension 3 for Batch Request Included only if a second address line is defined for the bill to address (or sold to address if a bill to is not defined) on the order. Example: A3STE 202 where: • A is the Product Record ID • 3 is the Address Type • STE 202 is the Address Line |
||||
Product Record ID |
1 |
1 |
alpha |
A defaults. |
Address Type |
2 |
1 |
alpha |
3 defaults. |
Address Line |
3-32 |
30 |
alpha |
The second address line defined for the customer’s address. From the Address line 2 in the Customer Bill To or Customer Sold To table. |
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
Country Code |
48-49 |
2 |
alpha |
Blank filled. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Address Record Extension 4 for Batch Request Included only if a city is defined for the bill to address (or sold to address if a bill to is not defined) on the order. Example: A4TEMPLETON, MA 01468-1566 where: • A is the Product Record ID • 4 is the Address Type • TEMPLETON, MA 014681566 is the Address Line |
||||
Product Record ID |
1 |
1 |
alpha |
A defaults. |
Address Type |
2 |
1 |
alpha |
4 defaults. |
Address Line |
3-32 |
30 |
alpha |
The city + state + zip defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the city + state + zip defined for the sold to customer on the order. Note: If the zip code is 9 positions, the system inserts a hyphen before the last 4 positions; for example 01468-1566. From the City, State and Zip in the Customer Bill To or Customer Sold To table. |
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
Country Code |
48-49 |
2 |
alpha |
Blank filled. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Batch File Totals Record for Batch Request Included for every batch request after all detail and supplemental records. Paymentech uses this record to balance the number of records, authorizations and refunds before processing. If the batch request is out of balance, Paymentech will not process the batch file. Example: B RECS=000000005 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • B RECS= is the first Constant • 000000005 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000000000 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000000000 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
Constant |
1-7 |
7 |
alpha |
B RECS= defaults. |
Batch Record Count |
8-16 |
9 |
numeric |
The total count of all records prior to this record type in the batch request. |
Filler |
17 |
1 |
alpha |
Blank filled. |
Constant |
18-22 |
5 |
alpha |
ORDS= defaults. |
Batch Order Count |
23-31 |
9 |
numeric |
The total count of Detail Record for Batch Requests in the batch request. |
Filler |
32 |
1 |
alpha |
Blank filled. |
Constant |
33-37 |
5 |
alpha |
$TOT= defaults. |
Batch Amount Total |
38-51 |
14 |
numeric |
Example: 00000000000000 defaults. |
Filler |
52 |
1 |
alpha |
Blank filled. |
Constant |
53-58 |
6 |
alpha |
$SALE= defaults. |
Batch Amount Sales |
59-72 |
14 |
numeric |
00000000000000 defaults. |
Filler |
73 |
1 |
alpha |
Blank filled. |
Constant |
74-81 |
8 |
alpha |
$REFUND defaults. |
Batch Amount Refunds |
82-95 |
14 |
numeric |
00000000000000 defaults. |
Filler |
96 |
1 |
alpha |
Blank filled. |
Transaction File Totals Record for Batch Request Included for every batch request. The totals in this record should match the totals in the Batch File Totals Record for Batch Request. Example: T RECS=000000006 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • T RECS= is the first Constant • 000000006 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000000000 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000000000 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
Constant |
1-7 |
7 |
alpha |
T RECS= defaults. |
File Record Count |
8-16 |
9 |
numeric |
The total count of all records prior to the Batch File Totals Record for Batch Request in the batch request. |
Filler |
17 |
1 |
alpha |
Blank filled. |
Constant |
18-22 |
5 |
alpha |
ORDS= defaults. |
File Order Count |
23-31 |
9 |
numeric |
The total count of Detail Record for Batch Requests in the batch request. |
Filler |
32 |
1 |
alpha |
Blank filled. |
Constant |
33-37 |
5 |
alpha |
$TOT= defaults. |
File Total Amounts |
38-51 |
14 |
numeric |
00000000000000 defaults. |
Filler |
52 |
1 |
alpha |
Blank filled. |
Constant |
53-58 |
6 |
alpha |
$SALE= defaults. |
File Amount Sales |
59-72 |
14 |
numeric |
00000000000000 defaults. |
Filler |
73 |
1 |
alpha |
Blank filled. |
Constant |
74-81 |
8 |
alpha |
$REFUND defaults. |
File Amount Refunds |
82-95 |
14 |
numeric |
00000000000000 defaults. |
Filler |
96 |
1 |
alpha |
Blank filled. |
Trailer Record for Batch Request Included for every batch request, indicating the batch request has been successfully sent and is ready for processing by Paymentech. Example: PID=192864 COMMERCI SID=192864 COMMERCI END 110216 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • END is the third Constant • 110216 is the Create Date |
||||
Constant |
1-4 |
4 |
alpha |
PID= defaults. |
Presenter’s ID |
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. From the Presenter’s ID in the Authorization Service table. |
Filler |
11 |
1 |
alpha |
Blank filled. |
PID Password |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. From the PID Password in the Authorization Service table. |
Filler |
20 |
1 |
alpha |
Blank filled. |
Constant |
21-24 |
4 |
alpha |
SID= defaults. |
Submitter’s ID |
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. From the Submitter’s ID in the Authorization Service table. |
Filler |
31 |
1 |
alpha |
Blank filled. |
SID Password |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. From the SID Password in the Authorization Service table. |
Filler |
40 |
1 |
alpha |
Blank filled. |
Constant |
41-43 |
3 |
alpha |
END defaults. |
Filler |
44-45 |
2 |
alpha |
Blank filled. |
Create Date |
46-51 |
6 |
alpha |
The date when the request was sent to the service bureau in YYMMDD format. |
Filler |
52-96 |
45 |
alpha |
Blank filled. |
Paymentech Batch Authorization Response File
When a Paymentech Batch Authorization Response file is ready, CWSerenade retrieves the file from Paymentech.
CWSerenade directly maps the information in the Detail Record to a record in the CC Authorization Transaction table and discards the Header, Batch Totals, Totals, and Trailer records.
Once the CC Authorization Transaction record is updated, CWSerenade continues with regular batch authorization processing; see Using Batch Authorization.
Sample transaction: See Sample Paymentech Batch Transactions.
Name |
Position |
Length |
Type |
Comments |
Authorization Header Record for Batch Response This record identifies the source of the submitted file and contains the presenter and submitter information used to match a request to a response. CWSerenade discards this record during processing. Example: PID=192864 COMMERCI SID=192864 COMMERCI START 110801 01.7 10801.059Ey A357 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • START is the third Constant • 110801 is the Create Date • 01.7 is the Revision Number • 10801.059Ey is the Submission Number • A357 is the Merchant Space |
||||
Constant |
1-4 |
4 |
alpha |
PID= defaults. |
Presenter’s ID |
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. Corresponds to the Presenter’s ID in the Authorization Service table. |
Filler |
11 |
1 |
alpha |
Blank filled. |
PID Password |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. Corresponds to the PID Password in the Authorization Service table. |
Filler |
20 |
1 |
alpha |
Blank filled. |
Constant |
21-24 |
4 |
alpha |
SID= defaults. |
Submitter’s ID |
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. Corresponds to the Submitter’s ID in the Authorization Service table. |
Filler |
31 |
1 |
alpha |
Blank filled. |
SID Password |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. Corresponds to the SID Password in the Authorization Service table. |
Filler |
40 |
1 |
alpha |
Blank filled. |
Constant |
41-43 |
5 |
alpha |
RFR defaults. |
Filler |
44-45 |
2 |
alpha |
Blank filled. |
Create Date |
46-51 |
6 |
alpha |
The date when the request was sent to the service bureau in YYMMDD format. |
Filler |
52-96 |
45 |
alpha |
Blank filled. |
Revision Number |
55-58 |
4 |
alpha |
01.7 defaults. Left-justified and zero filled. |
Filler |
59 |
1 |
alpha |
Blank filled. |
Submission Number |
60-70 |
11 |
alpha |
Populated by Paymentech. |
Filler |
71-88 |
18 |
alpha |
Blank filled. |
Merchant Space |
89-96 |
8 |
alpha |
A + the number from the Batch Auth File Trace Number number assignment value. Corresponds to the Merchant Space value sent in the deposit request. Example: A999 |
Detail Record for Batch Response This record contains the details of the authorization response, such as whether the authorization was confirmed or declined. Example: S0205940070000370401001 AVI***** REMOVED *****12120000000010878401007 110801tst488I3N where: • S is the Constant • 020594 is the Division Number • 0070000370401001 is the Merchant Order # • A is the Action Code • VI is the Method of Payment • ***** REMOVED ***** is the Account Number • 1212 is the Expiration Date • 000000001087 is the Amount • 840 is the Currency Code • 100 is the Response Reason Code • 7 is the Transaction Type Used • 110801 is the Response Date • tst488 is the Authorization Verification Code • N is the Deposit Flag |
||||
Constant |
1 |
1 |
alpha |
S defaults. |
Division Number |
2-7 |
6 |
numeric |
The account number assigned by the service bureau to identify transmissions. Corresponds to the: • Merchant # in the CC Paytype Cross Ref table. • Merchant ID override in the Merchant ID Override table. • Merchant ID in the Authorization Service table. |
Merchant Order # |
8-23 |
16 |
alpha |
A unique number made up of the CWSerenade company code + order number + order payment method sequence number + authorization sequence number. Corresponds to the Company, Order #, OPM Seq # and AUH Seq # in the Authorization History table. |
Action Code |
24-25 |
2 |
alpha |
A defaults for authorizations. K defaults for stored value card activations. E defaults for authorization reversals. Q defaults for balance inquiry. |
Method of Payment |
26-27 |
2 |
alpha |
The vendor paytype code associated with the authorization request; this is the code the authorization service uses to identify a method of payment. Corresponds to the CPC vendor paytype/code in the CC Paytype Cross Ref table. Note: For Diner’s Club, Paymentech sends back DD. |
Account Number |
28-46 |
19 |
alpha |
The card number for the payment method receiving the authorization response. Left-justified and blank filled. Corresponds to the Credit card # in the CC Authorization Transaction table. For data security, CWSerenade masks the card number in the Trace log. |
Expiration Date |
47-50 |
4 |
alpha |
The date the card expires in MMYY format. Corresponds to the OPM expiration date in the Order Payment Method table. 1249 defaults if the Method of Payment is stored value card. |
Amount |
51-62 |
12 |
numeric |
The amount on the card receiving the authorization response, with 2 implied decimals. Right-justified and zero filled. Corresponds to the Authorization amount in the Authorization History table. Example: 0000000002078 represents $20.78. |
Currency Code |
63-65 |
3 |
numeric |
The currency code used by the authorization service to define a currency. Corresponds to the CUR currency code in the CC Authorization Transaction table. |
Response Reason Code |
66-68 |
3 |
numeric |
The authorization response for the card. Updates Authorization Vendor Response in the CC Authorization History table. |
Transaction Type Used |
69 |
1 |
alpha |
A code provided by Paymentech indicating the circumstances under which the transaction takes place. Not mapped. |
Card Security Value Response |
70 |
1 |
alpha |
Response returned for card security. Updates the Vendor Response 2 field in the Authorization History table. Not included for stored value card transactions. Values returned: M = Value Matched. N = Value Not Matched. P = Not Processed. S = Should Be On Card. U = Unsupported By Issuer. I = Invalid. |
Response Date |
71-76 |
6 |
numeric |
The date in YYMMDD format the response was processed by Paymentech. Corresponds to the Authorization date in the CC Authorization History table. |
Authorization Verification Code |
77-82 |
6 |
alpha |
The authorization code for the authorization. Updates Authorization code in the CC Authorization Transaction and CC Authorization History table. Also creates an Authorization History record when authorizations are processed. |
AVS/AVV Response Code |
83-84 |
2 |
alpha |
The address verification response for the card. Updates AVS Response in the CC Authorization History table. |
Deposit Flag |
85 |
1 |
alpha |
Not mapped. |
Fraud Indicator |
86 |
1 |
alpha |
Defines scoring for Paymentech Fraud Detection. Not mapped. |
Encryption Flag |
87-89 |
3 |
alpha |
Not mapped. |
Recurring Payment Advice |
90-91 |
2 |
numeric |
Not mapped. |
Filler |
92 |
1 |
alpha |
Blank filled. |
Merchant Space |
93-96 |
4 |
alpha |
Not mapped. |
Batch File Totals Record for Batch Response Included for every batch response after all detail records. CWSerenade discards this record during processing. Example: B RECS=000000007 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • B RECS= is the first Constant • 000000007 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000001207 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000001207 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
Constant |
1-7 |
7 |
alpha |
B RECS= defaults. |
Batch Record Count |
8-16 |
9 |
numeric |
The total count of all records prior to this record type in the batch response. |
Filler |
17 |
1 |
alpha |
Blank filled. |
Constant |
18-22 |
5 |
alpha |
ORDS= defaults. |
Batch Order Count |
23-31 |
9 |
numeric |
The total count of Detail Record for Batch Responses in the batch response. |
Filler |
33 |
1 |
alpha |
Blank filled. |
Constant |
33-37 |
5 |
alpha |
$TOT= defaults. |
Batch Total Amounts |
35-51 |
14 |
numeric |
The sum total of all deposit and refund Detail Record for Batch Responses in the batch response. This is the absolute total, not the net total. Example: If the authorization amount is 100.00 and the refund amount is 25.00, the batch total amount is 125.00. |
Filler |
52 |
1 |
alpha |
Blank filled. |
Constant |
53-58 |
6 |
alpha |
$SALE= defaults. |
Batch Amount Sales |
59-72 |
14 |
numeric |
The sum total of the deposit amounts in the Detail Record for Batch Responses in the batch response. |
Filler |
73 |
1 |
alpha |
Blank filled. |
Constant |
74-81 |
8 |
alpha |
$REFUND defaults. |
Batch Amount Refunds |
82-95 |
14 |
numeric |
The sum total of the refund amounts in the Detail Record for Batch Responses in the batch response. |
Filler |
96 |
1 |
alpha |
Blank filled. |
Transaction File Totals Record for Batch Response Included for every batch response. The totals in this record should match the totals in the Batch File Totals Record for Batch Response. CWSerenade discards this record during processing. Example: T RECS=000000008 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • T RECS= is the first Constant • 000000008 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000001207 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000001207 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
Constant |
1-7 |
7 |
alpha |
T RECS= defaults. |
Batch Record Count |
8-16 |
9 |
numeric |
The total count of all records prior to the Batch File Totals Record for Batch Response in the batch response. |
Filler |
17 |
1 |
alpha |
Blank filled. |
Constant |
18-22 |
5 |
alpha |
ORDS= defaults. |
Batch Order Count |
23-31 |
9 |
numeric |
The total count of Detail Record for Batch Responses in the batch response. |
Filler |
33 |
1 |
alpha |
Blank filled. |
Constant |
33-37 |
5 |
alpha |
$TOT= defaults. |
Batch Total Amounts |
35-51 |
14 |
numeric |
The sum total of all deposit and refund Detail Record for Batch Responses in the batch response. This is the absolute total, not the net total. Example: If the authorization amount is 100.00 and the refund amount is 25.00, the batch total amount is 125.00. |
Filler |
52 |
1 |
alpha |
Blank filled. |
Constant |
53-58 |
6 |
alpha |
$SALE= defaults. |
Batch Amount Sales |
59-72 |
14 |
numeric |
The sum total of the authorization amounts in the Detail Record for Batch Responses in the batch response. |
Filler |
73 |
1 |
alpha |
Blank filled. |
Constant |
74-81 |
8 |
alpha |
$REFUND defaults. |
Batch Amount Refunds |
82-95 |
14 |
numeric |
The sum total of the refund amounts in the Detail Record for Batch Responses in the batch response. |
Filler |
96 |
1 |
alpha |
Blank filled. |
Trailer Record for Batch Response Included for every batch response, indicating the batch response has been successfully sent and is ready for processing by CWSerenade. CWSerenade discards this record during processing. Example: PID=192864 COMMERCI SID=192864 COMMERCI END 110307 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • START is the third Constant • 110307 is the Create Date |
||||
Constant |
1-4 |
4 |
alpha |
PID= defaults. |
Presenter’s ID |
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. Corresponds to the Presenter’s ID in the Authorization Service table. |
Filler |
11 |
1 |
alpha |
Blank filled. |
PID Password |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. Corresponds to the PID Password in the Authorization Service table. |
Filler |
20 |
1 |
alpha |
Blank filled. |
Constant |
21-24 |
4 |
alpha |
SID= defaults. |
Submitter’s ID |
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. Corresponds to the Submitter’s ID in the Authorization Service table. |
Filler |
31 |
1 |
alpha |
Blank filled. |
SID Password |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. Corresponds to the SID Password in the Authorization Service table. |
Filler |
40 |
1 |
alpha |
Blank filled. |
Constant |
41-43 |
3 |
alpha |
END defaults. |
Filler |
44-45 |
2 |
alpha |
Blank filled. |
Create Date |
46-51 |
6 |
alpha |
The date when the request was sent to the service bureau in YYMMDD format. |
Filler |
52-96 |
45 |
alpha |
Blank filled. |
Paymentech Batch Deposit Request File
During the Paymentech Point-to-Point Deposit Process, CWSerenade creates a fixed record length flat file containing the following record types.
Record |
Begins With |
When Included |
PID= |
Always included |
|
M |
Included only when the deposit record is for a credit card payment that is assigned to an installment flexible payment plan, an Industry format code is defined for the service bureau, and a Merchant ID Message is defined for the flexible payment option. |
|
S |
Always included |
|
E |
Included only if the vendor payment method is VI (Visa) and an authentication value exists for the payment in the Order Payment Method table. |
|
E |
Included only if the vendor payment method is MC (MasterCard) and an authentication value exists for the payment in the Order Payment Method table. |
|
Transaction File Product Record: Procurement Level 2 for Deposit Request |
P |
Included only if the deposit transaction is eligible for level II discounting. See Level II and III Discounting. |
Transaction File Switch Card (UK Debit) Record for Deposit Request |
SW |
Included only if the vendor paytype code is SW (Switch card) and a start date or issue number is defined for the debit card payment. |
A |
Included only if the AVS flag for the country cross reference record on the Work with Authorization Service Country Screen is Y, the vendor paytype code on the Work with Paytype Cross Reference Screen is not SW (Switch Card) or SV (Stored Value Card), and a last name is defined for the bill to customer (or sold to customer if a bill to customer is not defined). |
|
A2 |
Included only if a street address (address line 1) is defined for the bill to customer (or sold to customer if a bill to is not defined) on the order. |
|
A3 |
Included only if the system creates an Address Record Extension 2 for Deposit Request for the deposit request and an apartment or city is defined for the bill to address (or sold to address if a bill to is not defined) on the order. Note: The information in this record is based on whether an apartment number is defined for the customer’s address: • If an apartment number is not defined for the customer’s address, this record contains the customer’s city, state and zip. • If an apartment number is defined for the customer’s address, this record contains the apartment number and Address Record Extension 4 for Deposit Request contains the customer’s city, state and zip. |
|
A4 |
Included only if the system creates an Address Record Extension 2 for Deposit Request for the deposit request and an apartment/suite number and city are defined for the bill to address (or sold to address if a bill to is not defined) on the order. |
|
B |
Always included after all detail and supplemental records. |
|
T |
Always included |
|
PID= |
Always included |
Sample transaction: See Sample Paymentech Deposit Transactions.
Name |
Position |
Length |
Type |
Comments |
Deposit Header Record for Deposit Request This record identifies the source of the submitted file and contains the presenter and submitter information used to match a request to a response. Example: PID=192864 COMMERCI SID=192864 COMMERCI START 110216 01.7 D304 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • START is the third Constant • 110216 is the Create Date • 01.7 is the Revision Number • D304 is the Merchant Space |
||||
1-4 |
4 |
alpha |
PID= defaults. |
|
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the Presenter’s ID for Deposit in the Authorization Service table; if this property setting is blank, from the Presenter’s ID in the Authorization Service table. |
|
Filler |
11 |
1 |
alpha |
Blank filled. |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the PID Password for Deposit in the Authorization Service table; if this property setting is blank, from the PID Password in the Authorization Service table. |
|
Filler |
20 |
1 |
alpha |
Blank filled. |
21-24 |
4 |
alpha |
SID= defaults. |
|
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the Submitter’s ID for Deposit in the Authorization Service table; if this property setting is blank, from the Submitter’s ID in the Authorization Service table. |
|
Filler |
31 |
1 |
alpha |
Blank filled. |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the SID Password for Deposit in the Authorization Service table; if this property setting is blank, from the SID Password in the Authorization Service table. |
|
Filler |
40 |
1 |
alpha |
Blank filled. |
41-45 |
5 |
alpha |
START defaults. |
|
Filler |
46-47 |
2 |
alpha |
Blank filled. |
48-53 |
6 |
alpha |
The date when the deposit request was sent to the service bureau in YYMMDD format. |
|
Filler |
54 |
1 |
alpha |
Blank filled. |
55-58 |
4 |
alpha |
01.7 defaults. Left-justified and zero filled. |
|
Filler |
59 |
1 |
alpha |
Blank filled. |
60-70 |
11 |
alpha |
Blank filled; populated by Paymentech. |
|
Filler |
71-88 |
18 |
alpha |
Blank filled. |
89-96 |
8 |
alpha |
D + the next available number from the Batch Auth File Trace Number number assignment value. Example: D999 |
|
Merchant Descriptor Record for Deposit Request This record is used during installment billing and is included only when the deposit record is for a credit card payment that is assigned to an installment flexible payment plan, an Industry format code is defined for the service bureau, and a Merchant ID Message is defined for the flexible payment option. Example: MIND*INSTALLMENT1OF2 where: • M is the Constant • IND*INSTALLMENT1OF2 is the Soft Merchant Name |
||||
1 |
1 |
alpha |
M defaults. |
|
2-23 |
22 |
alpha |
The merchant description that displays on the customer’s statement. The soft merchant name contains the following: • DBA industry code (3 positions): the first 3 positions of the Industry format code for the service bureau. From the Industry format code in the Authorization Service table. • * defaults after the DBA industry code • Merchant ID message (11 positions): the Merchant ID message for the pay plan. From the Merchant ID Message in the Flexible Payment Option table. • Installment description (4 positions): for installment pay plans, this is a description of which installment was deposited; for example 1of4. Example: IND*INSTALLMENT1OF2 where: • IND is the DBA industry code • INSTALLMENT is the merchant ID message • 1OF2 is the installment description |
|
Filler |
24-27 |
4 |
alpha |
Blank filled. |
Soft Merchant City / Customer Service # |
28-40 |
13 |
alpha |
Blank filled. |
Filler |
41-96 |
56 |
alpha |
Blank filled. |
Detail Record for Deposit Request This record contains the details of the deposit transaction, such as the card number and the amount to charge or refund. Example: S0205940070000337201001 DVI***** REMOVED *****12120000000025608401001 110301tst643 where: • S is the Constant • 020594 is the Division Number • 0070000337201001 is the Merchant Order Number • D is the Action Code • VI is the Method of Payment • ***** REMOVED ***** is the Account Number (masked in the log for data security) • 1212 is the Expiration Date • 000000002560 is the Amount • 840 is the Currency Code • 100 is the Response Reason Code • 1 is the Transaction Type • 110301 is the Response Date • tst643 is the Authorization Code |
||||
1 |
1 |
alpha |
S defaults. |
|
2-7 |
6 |
numeric |
The account number assigned by the service bureau to identify transmissions. CWSerenade uses the following hierarchy to determine the merchant ID number to send: • Merchant # from the CC Paytype Cross Ref table. • Merchant ID override from the Merchant ID Override table. • Merchant ID from the Authorization Service table. |
|
8-23 |
16 |
alpha |
A unique number made up of the CWSerenade company code + order number + order payment method sequence number + authorization sequence number. From the Company, Order #, OPM Seq # in the CC Deposit Transaction table and AUH Seq # in the Authorization History table. |
|
24-25 |
2 |
alpha |
D defaults for regular deposits, the first deposit for an installment, or deposits for stored value cards. B defaults for regular deposits with an expired or missing authorization, subsequent deposits for installments, or deposits for deferred billing. R defaults for credit deposits. |
|
26-27 |
2 |
alpha |
The vendor paytype code associated with the deposit request; this is the code the deposit service uses to identify a method of payment. From the CPC vendor paytype/code in the CC Paytype Cross Ref table. |
|
28-46 |
19 |
alpha |
The card number for the payment method requesting deposit. Left-justified and blank filled. From the Credit card # in the CC Deposit Transaction table. If you use encryption, the system decrypts the card number before sending it to the service bureau. |
|
47-50 |
4 |
alpha |
The date the card requesting deposit expires in MMYY format. From the OPM expiration date in the Order Payment Method table. 1249 defaults if the Method of Payment is stored value card. |
|
51-62 |
12 |
numeric |
The amount on the card requesting deposit, with 2 implied decimals. Right-justified and zero filled. If the Use Alternate Currency Pricing (H89) system control value is selected and a currency code and conversion rate are defined in the Order Header Extended table, the alternate currency displays; otherwise, the local currency displays. From the Total $ amt in the CC Deposit Transaction table. Example: 0000000002078 represents $20.78. |
|
63-65 |
3 |
numeric |
The currency code used by the deposit service to define a currency. From the CUR currency code in the CC Deposit Transaction table. |
|
66-68 |
3 |
numeric |
100 defaults if the Action Code is D; otherwise, blank filled. |
|
69 |
1 |
alpha |
Represents either: • An electronic commerce indicator code, received from an authentication service such as Visa's Verified by Visa program or MasterCard's SecureCode program, indicating the level of security provided for a credit card transaction placed over the internet. • A value indicating if the order was placed on a web storefront. • 7 defaults if the Ecomm Indic in the Order Payment Method table is YES. • 1 defaults if the Ecomm Indic in the Order Payment Method table is NO. From the Indic in the Order Payment Method table. If the Ecomm Indic in the Order Payment Method table is blank, from the E-commerce indicator (Future use sts 1 field) in the Order Header table. |
|
Reserved |
70 |
1 |
alpha |
Blank filled. |
71-76 |
6 |
numeric |
The date the card was authorized, in YYMMDD format. Included only if the Action Code is D and the authorization has not yet expired; otherwise, blank filled. From the Auth date in the CC Deposit Transaction table. |
|
77-82 |
6 |
numeric |
The authorization code defined for the associated authorization. From the Auth code in the CC Deposit Transaction table. Included only if the Action Code is D and the authorization has not yet expired; otherwise, blank filled. |
|
83-84 |
2 |
alpha |
Blank filled. |
|
Reserved |
85 |
1 |
alpha |
Blank filled. |
Fraud Indicator |
86 |
1 |
alpha |
Blank filled. |
Encryption Flag |
87-89 |
3 |
alpha |
Blank filled. |
Reserved |
90-91 |
2 |
alpha |
Blank filled. |
Filler |
92 |
1 |
alpha |
Blank filled. |
Merchant Space |
93-96 |
4 |
alpha |
Blank filled. |
Visa Authentication Record for Deposit Request Included only if the vendor payment method is VI (Visa) and an authentication value exists for the payment in the Order Payment Method table. Example: EVI002 JHYN+7YFI1EUAREAAAAV6YF8F6S= where: • E is the Extension Record ID • VI is the Extension Record MOP Type • 002 is the Extension Record • JHYN+7YFI1EUAREAAAAV6YF8F6S= is the CAVV Response Code |
||||
1 |
1 |
alpha |
E defaults. |
|
2-3 |
2 |
alpha |
VI defaults. |
|
4-6 |
3 |
numeric |
002 defaults. |
|
Transaction ID |
7-46 |
40 |
alpha |
Blank filled. |
47-86 |
40 |
alpha |
A code received from an authentication service, such as Visa’s Verified by Visa program, indicating whether the card authentication password the cardholder entered on the web storefront was approved for the credit card. From the Authentication value in the Order Payment Method table. |
|
87 |
1 |
alpha |
Blank filled. |
|
Filler |
88-96 |
9 |
alpha |
Blank filled. |
MasterCard Authentication Record for Deposit Request Included only if the vendor payment method is MC (MasterCard) and an authentication value exists for the payment in the Order Payment Method table. Example: EMC002JHYN+7YFI1EUAREAAAAV6YF8F6S= where: • E is the Extension Record ID • MC is the Extension Record MOP Type • 202 is the Extension Record • JHYN+7YFI1EUAREAAAAV6YF8F6S= is the Authentication Value |
||||
1 |
1 |
alpha |
E defaults. |
|
2-3 |
2 |
alpha |
MC defaults. |
|
4-6 |
3 |
numeric |
002 defaults. |
|
7-38 |
32 |
alpha |
A code received from an authentication service, such as MasterCard’s Secure Code program, indicating whether the card authentication password the cardholder entered on the web storefront was approved for the credit card. From the Authentication value in the Order Payment Method table. |
|
Filler |
39-96 |
58 |
alpha |
Blank filled. |
Transaction File Product Record: Procurement Level 2 for Deposit Request Included only if the deposit transaction is eligible for level II discounting. A deposit transaction is eligible for level II discounting if the Send Data for Level II Discounting (I12) system control value is selected and: • The service bureau is Paymentech, • The transaction is a conditional deposit (B), regular deposit (D), or refund deposit (R), • The method of payment is MasterCard, Visa, or American Express, • The credit card number falls within a range of numbers in the Level II Bin Range table. 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 must be 16 positions. See Level II and III Discounting. Example: PPC0013385 000000000052 where: • P is the Extension Record ID • PC is the Product Record Type • 001 is the Product Record Sequence # • 3385 is the Customer Reference # • 000000000052 is the Sales Tax |
||||
1 |
1 |
alpha |
P defaults. |
|
2-3 |
2 |
alpha |
PC defaults. |
|
4-6 |
3 |
alpha |
001 defaults. |
|
7-23 |
17 |
alpha |
The purchase order number associated with the deposit request. From the Purchase order # in the Order Ship To table. If a purchase order is not defined for the order, the order number defaults. From the Order number in the CC Deposit Transaction table. |
|
24-35 |
12 |
numeric |
The total tax dollar amount requiring deposit with 2 implied decimals. From the Total tax $ amt in the CC Deposit Transaction table. Right justified and zero filled. |
|
Filler |
36-96 |
61 |
alpha |
Blank filled. |
Transaction File Switch Card (UK Debit) Record for Deposit Request Included only if the vendor paytype code is SW (Switch card) and a start date or issue number is defined for the debit card payment. Example: ESW0011203 where: • E is the Extension Record ID • SW is the Product Record Type • 001 is the Product Record Seq # • 1203 is the Card Start Date |
||||
1 |
1 |
alpha |
E defaults. |
|
2-3 |
2 |
alpha |
SW defaults. |
|
4-6 |
3 |
alpha |
001 defaults. |
|
7-10 |
4 |
numeric |
The start date of the debit card being processed, in MMYY format. Blank filled if a start date is not present. From the Card Start date in the Order Payment Method table. |
|
Card Issue Number |
11-12 |
2 |
numeric |
The card issue number of the debit card being processed. Right-justified and blank filled. From the OPM card issue # in the Order Payment Method table. |
Filler |
13-96 |
84 |
alpha |
Blank filled. |
Address Record for Deposit Request Included only if the AVS flag for the country cross reference record on the Work with Authorization Service Country Screen is Y, the vendor paytype code on the Work with Paytype Cross Reference Screen is not SW (Switch Card) or SV (Stored Value Card), and a last name is defined for the bill to customer (or sold to customer if a bill to customer is not defined). Example: ABBARBARA*WILLIAMS US where: • A is the Product Record ID • B is the Address Type • BERNADETTE*MIRANDA is the Address Line • US is the Country Code |
||||
1 |
1 |
alpha |
A defaults. |
|
2 |
1 |
alpha |
S defaults if the vendor paytype code on the Work with Paytype Cross Reference Screen is AX (American Express); otherwise, B defaults. |
|
3-32 |
30 |
alpha |
The first name + last name of the bill to customer on the order, each value separated by an asterisk (*). If a bill to customer is not defined, this is the first name + last name of the sold to customer on the order. To keep within 30 characters, the system truncates the first name if necessary. Example: BERNADETTE *MIRANDA From the First name and Last name in the Customer Bill To or Customer Sold To table. |
|
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
48-49 |
2 |
alpha |
The authorization service country code defined for the country cross reference record on the Work with Authorization Service Country Screen. From the Auth Service Country in the Auth Service Country table. |
|
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Address Record Extension 2 for Deposit Request Included only if a street address (address line 1) is defined for the bill to customer (or sold to customer if a bill to is not defined) on the order. Example: A2109 RIVER LN where: • A is the Product Record ID • 2 is the Address Type • 109 RIVER LN is the Address Line |
||||
1 |
1 |
alpha |
A defaults. |
|
2 |
1 |
alpha |
2 defaults. |
|
3-32 |
30 |
alpha |
The first address line of the bill to customer on the order. If a bill to customer is not defined, this is the first address line of the sold to customer on the order. From the Street Address in the Customer Bill To or Customer Sold To table. |
|
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
Country Code |
48-49 |
2 |
alpha |
Blank filled. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Address Record Extension 3 for Deposit Request Included only if the system creates an Address Record Extension 2 for Deposit Request for the authorization request and an apartment or city is defined for the bill to address (or sold to address if a bill to is not defined) on the order. Note: The information in this record is based on whether an apartment number is defined for the customer’s address: • If an apartment number is not defined for the customer’s address, this record contains the customer’s city, state and zip. • If an apartment number is defined for the customer’s address, this record contains the apartment number and Address Record Extension 4 for Deposit Request contains the customer’s city, state and zip. Example: A3TEMPLETON, MA 01468-1566 (no apartment number defined for cusotmer’s address) A3STE 202 (apartment number defined for customer’s address) where: • A is the Product Record ID • 3 is the Address Type • STE 202 is the Address Line |
||||
1 |
1 |
alpha |
A defaults. |
|
2 |
1 |
alpha |
3 defaults. |
|
3-32 |
30 |
alpha |
The information in this field is based on whether an apartment number is defined for the customer’s address: • If an apartment number is not defined for the customer’s address, this field contains the city + state + zip defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the city + state + zip defined for the sold to customer on the order. From the City, State and Zip in the Customer Bill To or Customer Sold To table. Note: If the zip code is 9 positions, the system inserts a hyphen before the last 4 positions; for example 01468-1566. • If an apartment number is defined for the customer’s address, this field contains the apartment number defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the apartment number defined for the sold to customer on the order. From the Apartment in the Customer Bill To or Customer Sold To table. |
|
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
Country Code |
48-49 |
2 |
alpha |
Blank filled. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Address Record Extension 4 for Deposit Request Included only if the system creates an Address Record Extension 2 for Deposit Request for the authorization request and an apartment/suite number and city are defined for the bill to address (or sold to address if a bill to is not defined) on the order. Example: A4TEMPLETON, MA 01468-1566 where: • A is the Product Record ID • 4 is the Address Type • TEMPLETON, MA 014681566 is the Address Line |
||||
Product Record ID |
1 |
1 |
alpha |
A defaults. |
Address Type |
2 |
1 |
alpha |
4 defaults. |
Address Line |
3-32 |
30 |
alpha |
The city + state + zip defined for the bill to customer on the order. If a bill to customer is not defined for the order, this is the city + state + zip defined for the sold to customer on the order. Note: If the zip code is 9 positions, the system inserts a hyphen before the last 4 positions; for example 01468-1566. From the City, State and Zip in the Customer Bill To or Customer Sold To table. |
Telephone Type |
33 |
1 |
alpha |
Blank filled. |
Telephone # |
34-47 |
14 |
alpha |
Blank filled. |
Country Code |
48-49 |
2 |
alpha |
Blank filled. |
Filler |
50-96 |
47 |
alpha |
Blank filled. |
Batch File Totals Record for Deposit Request Included for every batch authorization request after all detail and supplemental records. Paymentech uses this record to balance the number of records and authorizations before processing. If the batch authorization request is out of balance, Paymentech will not process the batch file. Example: B RECS=000000005 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • B RECS= is the first Constant • 000000005 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000001207 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000001207 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
1-7 |
7 |
alpha |
B RECS= defaults. |
|
8-16 |
9 |
numeric |
The total count of all records prior to this record type in the batch deposit request. |
|
Filler |
17 |
1 |
alpha |
Blank filled. |
18-22 |
5 |
alpha |
ORDS= defaults. |
|
23-31 |
9 |
numeric |
The total count of Detail Record for Deposit Requests in the batch deposit request. |
|
Filler |
33 |
1 |
alpha |
Blank filled. |
33-37 |
5 |
alpha |
$TOT= defaults. |
|
35-51 |
14 |
numeric |
The sum total of all deposit and refund Detail Record for Deposit Requests in the batch deposit request. This is the absolute total, not the net total. Example: If the deposit amount is 100.00 and the refund amount is 25.00, the batch total amount is 125.00. |
|
Filler |
52 |
1 |
alpha |
Blank filled. |
53-58 |
6 |
alpha |
$SALE= defaults. |
|
59-72 |
14 |
numeric |
The sum total of the deposit amounts in the Detail Record for Deposit Requests in the batch deposit request. |
|
Filler |
73 |
1 |
alpha |
Blank filled. |
74-81 |
8 |
alpha |
$REFUND defaults. |
|
82-95 |
14 |
numeric |
The sum total of the refund amounts in the Detail Record for Deposit Requests in the batch deposit request. This is an absolute value without a positive or negative sign. |
|
Filler |
96 |
1 |
alpha |
Blank filled. |
Transaction File Totals Record for Deposit Request Included for every batch deposit request. The totals in this record should match the totals in the Batch File Totals Record for Deposit Request. Example: T RECS=000000006 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • T RECS= is the first Constant • 000000006 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000001207 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000001207 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
1-7 |
7 |
alpha |
T RECS= defaults. |
|
8-16 |
9 |
numeric |
The total count of all records prior to the Batch File Totals Record for Deposit Request in the batch deposit request. |
|
Filler |
17 |
1 |
alpha |
Blank filled. |
18-22 |
5 |
alpha |
ORDS= defaults. |
|
23-31 |
9 |
numeric |
The total count of Detail Record for Deposit Requests in the batch deposit request. |
|
Filler |
33 |
1 |
alpha |
Blank filled. |
33-37 |
5 |
alpha |
$TOT= defaults. |
|
35-51 |
14 |
numeric |
The sum total of all deposit and refund Detail Record for Deposit Requests in the batch deposit request. This is the absolute total, not the net total. Example: If the deposit amount is 100.00 and the refund amount is 25.00, the batch total amount is 125.00. |
|
Filler |
52 |
1 |
alpha |
Blank filled. |
53-58 |
6 |
alpha |
$SALE= defaults. |
|
59-72 |
14 |
numeric |
The sum total of the deposit amounts in the Detail Record for Deposit Requests in the batch deposit request. |
|
Filler |
73 |
1 |
alpha |
Blank filled. |
74-81 |
8 |
alpha |
$REFUND defaults. |
|
82-95 |
14 |
numeric |
The sum total of the refund amounts in the Detail Record for Deposit Requests in the batch deposit request. |
|
Filler |
96 |
1 |
alpha |
Blank filled. |
Trailer Record for Deposit Request Included for every batch deposit request, indicating the batch deposit request has been successfully sent and is ready for processing by Paymentech. Example: PID=192864 COMMERCI SID=192864 COMMERCI END 110216 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • END is the third Constant • 110216 is the Create Date |
||||
1-4 |
4 |
alpha |
PID= defaults. |
|
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the Presenter’s ID for Deposit in the Authorization Service table; if this property setting is blank, from the Presenter’s ID in the Authorization Service table. |
|
Filler |
11 |
1 |
alpha |
Blank filled. |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the PID Password for Deposit in the Authorization Service table; if this property setting is blank, from the PID Password in the Authorization Service table. |
|
Filler |
20 |
1 |
alpha |
Blank filled. |
21-24 |
4 |
alpha |
SID= defaults. |
|
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the Submitter’s ID for Deposit in the Authorization Service table; if this property setting is blank, from the Submitter’s ID in the Authorization Service table. |
|
Filler |
31 |
1 |
alpha |
Blank filled. |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the SID Password for Deposit in the Authorization Service table; if this property setting is blank, from the SID Password in the Authorization Service table. |
|
Filler |
40 |
1 |
alpha |
Blank filled. |
41-43 |
3 |
alpha |
END defaults. |
|
Filler |
44-45 |
2 |
alpha |
Blank filled. |
46-51 |
6 |
alpha |
The date when the deposit request was sent to the service bureau in YYMMDD format. |
|
Filler |
52-96 |
45 |
alpha |
Blank filled. |
Paymentech Batch Deposit Response File
When a Paymentech Batch Deposit Response file is ready, CWSerenade retrieves the file from Paymentech.
CWSerenade directly maps the information in the Detail Record for Deposit Response to a record in the CC Deposit Transaction table and discards the Header, Batch Totals, Totals, and Trailer records.
Once the CC Deposit Transaction record is updated, CWSerenade continues with regular deposit processing; see Processing Auto Deposits (SDEP).
Sample transaction: See Sample Paymentech Deposit Transactions.
Name |
Position |
Length |
Type |
Comments |
Deposit Header Record for Deposit Response This record identifies the source of the submitted file and contains the presenter and submitter information used to match a request to a response. CWSerenade discards this record during processing. Example: PID=192864 COMMERCI SID=192864 COMMERCI START 110307 01.7 10307.046Ay D327 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • START is the third Constant • 110307 is the Create Date • 01.7 is the Revision Number • 10307.046Ay is the Submission Number • D304 is the Merchant Space |
||||
1-4 |
4 |
alpha |
PID= defaults. |
|
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the Presenter’s ID for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the Presenter’s ID in the Authorization Service table. |
|
Filler |
11 |
1 |
alpha |
Blank filled. |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the PID Password for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the PID Password in the Authorization Service table. |
|
Filler |
20 |
1 |
alpha |
Blank filled. |
21-24 |
4 |
alpha |
SID= defaults. |
|
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the Submitter’s ID for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the Submitter’s ID in the Authorization Service table. |
|
Filler |
31 |
1 |
alpha |
Blank filled. |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the SID Password for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the SID Password in the Authorization Service table. |
|
Filler |
40 |
1 |
alpha |
Blank filled. |
41-45 |
5 |
alpha |
START defaults. |
|
Filler |
46-47 |
2 |
alpha |
Blank filled. |
48-53 |
6 |
alpha |
The date when the deposit request was sent to the service bureau in YYMMDD format. |
|
Filler |
54 |
1 |
alpha |
Blank filled. |
55-58 |
4 |
alpha |
01.7 defaults. Left-justified and zero filled. |
|
Filler |
59 |
1 |
alpha |
Blank filled. |
60-70 |
11 |
alpha |
Populated by Paymentech. |
|
Filler |
71-88 |
18 |
alpha |
Blank filled. |
89-96 |
8 |
alpha |
D + the number from the Batch Auth File Trace Number number assignment value. Corresponds to the Merchant Space value sent in the deposit request. Example: D999 |
|
Detail Record for Deposit Response This record contains the details of the deposit response, such as whether the deposit was confirmed or declined. Example: S0205940070000339501001 DVI***** REMOVED *****12120000000012078401001 110307tst982 Y where: • S is the Constant • 020594 is the Division Number • 0070000339501001 is the Merchant Order # • D is the Action Code • VI is the Method of Payment • ***** REMOVED ***** is the Account Number • 1212 is the Expiration Date • 000000001207 is the Amount • 840 is the Currency Code • 100 is the Response Reason Code • 1 is the Transaction Type Used • 110307 is the Response Date • tst982 is the Authorization Verification Code • Y is the Deposit Flag |
||||
1 |
1 |
alpha |
S defaults. |
|
2-7 |
6 |
numeric |
The account number assigned by the service bureau to identify transmissions. Corresponds to the: • Merchant # in the CC Paytype Cross Ref table. • Merchant ID override in the Merchant ID Override table. • Merchant ID in the Authorization Service table. |
|
8-23 |
16 |
alpha |
A unique number made up of the CWSerenade company code + order number + order payment method sequence number + authorization sequence number. Corresponds to the Company, Order #, OPM Seq # in the CC Deposit Transaction table and AUH Seq # in the Authorization History table. |
|
24-25 |
2 |
alpha |
D defaults for regular deposits, the first deposit for an installment, or deposits for stored value cards. B defaults for regular deposits with an expired or missing authorization, subsequent deposits for installments, or deposits for deferred billing. R defaults for credit deposits. |
|
26-27 |
2 |
alpha |
The vendor paytype code associated with the deposit request; this is the code the deposit service uses to identify a method of payment. Corresponds to the CPC vendor paytype/code in the CC Paytype Cross Ref table. Note: For Diner’s Club, Paymentech sends back DD. |
|
28-46 |
19 |
alpha |
The card number for the payment method receiving the deposit response. Left-justified and blank filled. Corresponds to the Credit card # in the CC Deposit Transaction table. For data security, CWSerenade masks the card number in the Trace log. |
|
47-50 |
4 |
alpha |
The date the card expires in MMYY format. Corresponds to the OPM expiration date in the Order Payment Method table. 1249 defaults if the Method of Payment is stored value card. |
|
51-62 |
12 |
numeric |
The amount on the card receiving the deposit response, with 2 implied decimals. Right-justified and zero filled. Corresponds to the Total $ amt in the CC Deposit Transaction table. Example: 0000000002078 represents $20.78. |
|
63-65 |
3 |
numeric |
The currency code used by the deposit service to define a currency. Corresponds to the CUR currency code in the CC Deposit Transaction table. |
|
66-68 |
3 |
numeric |
The deposit response for the card. Updates Vendor response 1 in the CC Deposit Transaction table and Response code in the CC Deposit History table. |
|
69 |
1 |
alpha |
A code provided by Paymentech indicating the circumstances under which the transaction takes place. Not mapped. |
|
Card Security Value Response |
70 |
1 |
alpha |
Response returned for card security. Not mapped. Values returned: M = Value Matched. N = Value Not Matched. P = Not Processed. S = Should Be On Card. U = Unsupported By Issuer. I = Invalid. |
71-76 |
6 |
numeric |
The date in YYMMDD format the response was processed by Paymentech. Corresponds to the Transaction date in the CC Deposit History table. |
|
77-82 |
6 |
alpha |
The authorization code for the deposit. Updates Authorization code in the CC Deposit Transaction and CC Deposit History table. Also creates an Authorization History record when deposits are processed. |
|
AVS/AVV Response Code |
83-84 |
2 |
alpha |
The address verification response for the card. Updates AVS Response in the CC Deposit Transaction table. |
85 |
1 |
alpha |
Indicates if the deposit was successful, based on the response code received back from the service bureau and an authorization number of NOTDEP. YES = The deposit was approved by the service bureau (the deposit response is 100 approved). NO = The deposit was rejected by the service bureau. If YES, updates Status in the CC Deposit Transaction table to *RCVD; otherwise, the system does not update the status and the deposit is rejected and unconfirmed. |
|
Fraud Indicator |
86 |
1 |
alpha |
Defines scoring for Paymentech Fraud Detection. Not mapped. |
Encryption Flag |
87-89 |
3 |
alpha |
Not mapped. |
Recurring Payment Advice |
90-91 |
2 |
numeric |
Not mapped. |
Filler |
92 |
1 |
alpha |
Blank filled. |
Merchant Space |
93-96 |
4 |
alpha |
Not mapped. |
Batch File Totals Record for Deposit Response Included for every batch deposit response after all detail records. CWSerenade discards this record during processing. Example: B RECS=000000007 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • B RECS= is the first Constant • 000000007 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000001207 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000001207 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
1-7 |
7 |
alpha |
B RECS= defaults. |
|
8-16 |
9 |
numeric |
The total count of all records prior to this record type in the batch deposit response. |
|
Filler |
17 |
1 |
alpha |
Blank filled. |
18-22 |
5 |
alpha |
ORDS= defaults. |
|
23-31 |
9 |
numeric |
The total count of Detail Record for Deposit Responses in the batch deposit response. |
|
Filler |
33 |
1 |
alpha |
Blank filled. |
33-37 |
5 |
alpha |
$TOT= defaults. |
|
35-51 |
14 |
numeric |
The sum total of all deposit and refund Detail Record for Deposit Responses in the batch deposit response. This is the absolute total, not the net total. Example: If the deposit amount is 100.00 and the refund amount is 25.00, the batch total amount is 125.00. |
|
Filler |
52 |
1 |
alpha |
Blank filled. |
53-58 |
6 |
alpha |
$SALE= defaults. |
|
59-72 |
14 |
numeric |
The sum total of the deposit amounts in the Detail Record for Deposit Responses in the batch deposit response. |
|
Filler |
73 |
1 |
alpha |
Blank filled. |
74-81 |
8 |
alpha |
$REFUND defaults. |
|
82-95 |
14 |
numeric |
The sum total of the refund amounts in the Detail Record for Deposit Responses in the batch deposit response. |
|
Filler |
96 |
1 |
alpha |
Blank filled. |
Transaction File Totals Record for Deposit Response Included for every batch deposit response. The totals in this record should match the totals in the Batch File Totals Record for Deposit Response. CWSerenade discards this record during processing. Example: T RECS=000000008 ORDS=000000001 $TOT=00000000001207 $SALE=00000000001207 $REFUND=00000000000000 where: • T RECS= is the first Constant • 000000008 is the Batch Record Count • ORDS= is the second Constant • 000000001 is the Batch Order Count • $TOT= is the third Constant • 00000000001207 is the Batch Total Amounts • $SALE= is the fourth Constant • 00000000001207 is the Batch Amount Sales • $REFUND= is the fifth Constant • 00000000000000 is the Batch Amount Refunds |
||||
1-7 |
7 |
alpha |
T RECS= defaults. |
|
8-16 |
9 |
numeric |
The total count of all records prior to the Batch File Totals Record for Deposit Response in the batch deposit response. |
|
Filler |
17 |
1 |
alpha |
Blank filled. |
18-22 |
5 |
alpha |
ORDS= defaults. |
|
23-31 |
9 |
numeric |
The total count of Detail Record for Deposit Responses in the batch deposit response. |
|
Filler |
33 |
1 |
alpha |
Blank filled. |
33-37 |
5 |
alpha |
$TOT= defaults. |
|
35-51 |
14 |
numeric |
The sum total of all deposit and refund Detail Record for Deposit Responses in the batch deposit response. This is the absolute total, not the net total. Example: If the deposit amount is 100.00 and the refund amount is 25.00, the batch total amount is 125.00. |
|
Filler |
52 |
1 |
alpha |
Blank filled. |
53-58 |
6 |
alpha |
$SALE= defaults. |
|
59-72 |
14 |
numeric |
The sum total of the deposit amounts in the Detail Record for Deposit Responses in the batch deposit response. |
|
Filler |
73 |
1 |
alpha |
Blank filled. |
74-81 |
8 |
alpha |
$REFUND defaults. |
|
82-95 |
14 |
numeric |
The sum total of the refund amounts in the Detail Record for Deposit Responses in the batch deposit response. |
|
Filler |
96 |
1 |
alpha |
Blank filled. |
Trailer Record for Deposit Response Included for every batch deposit response, indicating the batch deposit response has been successfully sent and is ready for processing by CWSerenade. CWSerenade discards this record during processing. Example: PID=192864 COMMERCI SID=192864 COMMERCI END 110307 where: • PID= is the first Constant • 192864 is the Presenter’s ID • COMMERCI is the PID Password • SID= is the second Constant • 192864 is the Submitter’s ID • COMMERCI is the SID Password • START is the third Constant • 110307 is the Create Date |
||||
1-4 |
4 |
alpha |
PID= defaults. |
|
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the Presenter’s ID for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the Presenter’s ID in the Authorization Service table. |
|
Filler |
11 |
1 |
alpha |
Blank filled. |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the PID Password for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the PID Password in the Authorization Service table. |
|
Filler |
20 |
1 |
alpha |
Blank filled. |
21-24 |
4 |
alpha |
SID= defaults. |
|
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the Submitter’s ID for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the Submitter’s ID in the Authorization Service table. |
|
Filler |
31 |
1 |
alpha |
Blank filled. |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, corresponds to the SID Password for Deposit in the Authorization Service table; if this property setting is blank, corresponds to the SID Password in the Authorization Service table. |
|
Filler |
40 |
1 |
alpha |
Blank filled. |
41-43 |
3 |
alpha |
END defaults. |
|
Filler |
44-45 |
2 |
alpha |
Blank filled. |
46-51 |
6 |
alpha |
The date when the deposit request was sent to the service bureau in YYMMDD format. |
|
Filler |
52-96 |
45 |
alpha |
Blank filled. |
Paymentech Request for Response (RFR)
If a Paymentech Batch Deposit Response File was not received within the maximum wait time, or if a communication failure occurred during transaction processing, you can use the receive deposits option on the Auto Deposit Screen (Send or Receive Deposits) to send a Paymentech Request for Response (RFR) transaction to Paymentech, requesting Paymentech to queue the Paymentech Batch Deposit Response File so that CWSerenade can retrieve it.
Example:
PID=192864 COMMERCI SID=192864 COMMERCI RFR 110308
where:
• PID= is the first Constant
• 192864 is the Presenter’s ID
• COMMERCI is the PID Password
• SID= is the second Constant
• 192864 is the Submitter’s ID
• COMMERCI is the SID Password
• RFR is the third Constant
• 110308 is the Create Date
If a response is not ready: The system sends the RFR request one time to Paymentech. If a Paymentech Batch Deposit Response File is not available, the system writes a message similar to the following to the CWSerenade Trace Log if its Logging Level is set to DEBUG:
YY-MM-DD HH:MM:SS No data to send back at this time.
Request for Response record:
Name |
Position |
Length |
Type |
Comments |
1-4 |
4 |
alpha |
PID= defaults. |
|
5-10 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the Presenter’s ID for Deposit in the Authorization Service table; if this property setting is blank, from the Presenter’s ID in the Authorization Service table. |
|
Filler |
11 |
1 |
alpha |
Blank filled. |
12-19 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the PID Password for Deposit in the Authorization Service table; if this property setting is blank, from the PID Password in the Authorization Service table. |
|
Filler |
20 |
1 |
alpha |
Blank filled. |
21-24 |
4 |
alpha |
SID= defaults. |
|
25-30 |
6 |
numeric |
A code required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the Submitter’s ID for Deposit in the Authorization Service table; if this property setting is blank, from the Submitter’s ID in the Authorization Service table. |
|
Filler |
31 |
1 |
alpha |
Blank filled. |
32-39 |
8 |
alpha |
A password required to sign on to the service bureau. If a port number is defined in the PMD_PAY_LINK_SERVICE_BATCH_DEPOSIT_PORT property setting, from the SID Password for Deposit in the Authorization Service table; if this property setting is blank, from the SID Password in the Authorization Service table. |
|
Filler |
40 |
1 |
alpha |
Blank filled. |
41-43 |
3 |
alpha |
RFR defaults. |
|
44-49 |
6 |
alpha |
The date when the deposit request was sent to the service bureau in YYMMDD format. |
|
Filler |
50-94 |
45 |
alpha |
Blank filled. |
