Paymentech Support

Session 4
Summary Report, fires at 3:15am
• 3:15am is the time a large, off-peak batch should reliably be
completed
• Review which transactions are failing to get the key information
• Merchant ID
• File type (96 vs 120)
• Presenter IDS 245217=96B 261879=120B
• Chase Operations
• 1.800.228.7782 Option 1 for operations, option 2 for missing response
Error Scenarios
• Problem type 1
• File held for duplicates – When released, this WILL BE charged
• File held for bad method-of-payment (MOP) – When released, this WILL NOT BE
charged
• File held because its out-of-balance – When released, the offending transactions WILL
NOT BE charged
• Trailer record doesn’t match the sum of the order/refunds
• Usually because of a bad card number (tokenization)
• Problem Type 2
• No Files held, but asynchronous file exists
• Problem Type 3
• Sending issue internally
Problem Type 1 resolution
• View file-level report to see which files are missing
• Contact Chase operations, or review the email
• Decide to RELEASE or CANCEL file. If cancelling, you are done at this step
• The file will be returned to the SERVICES process. You will need to contact the service desk to contact Jyothi 516.526.8083.
Alternatively you can text her directly
• File verification:
• 96byte
• path:/db3/oracle/utlfiles
• ls –ltr *.response
• 120byte
• path:/db3/oracle/utlfiles/response_120
• ls –ltr *.response
• You will need to run the import process when Jyothi tells you the file is present
• dzdo –u atssysprod /db3/oracle/eoday/eodlitupdsun for the 96 byte process
• dzdo –u atssysprod /db3/oracle/eoday/eodlitupdsun_120 for the 120 byte process
• Rerun the Oracle Process – F18 Hourly End Of Day Report
• If the Oracle report is clear, rerun the Exception report (finance)
• dzdo –u atssysprod /db3/oracle/eoday/ATS_PAYMENTECH_REJECTION_REPORTS.sh
Problem Type 2 resolution
• Run this query
select COUNT(*), SUM(ODRF_AMOUNT), MRCHNT_ID, EODSTATUS, CHASE_FILESPEC
From ats_litlesears_Batch
group by MRCHNT_ID, EODSTATUS, CHASE_FILESPEC
ORDER BY 3,4,5;

• Go to this UNIX path: /db3/oracle/eoday/resps

• For each response file for the batch (file extension is a date), do a head -10 [filename]
• Find out which file is NOT the correct response
• Via helpdesk or text, you will need to get in touch with Jyothi and tell her the file you are missing
• You will need to run the import process when Jyothi tells you the file is present
• dzdo –u atssysprod /db3/oracle/eoday/eodlitupdsun for the 96 byte process
• dzdo –u atssysprod /db3/oracle/eoday/eodlitupdsun for the 120 byte process
• Rerun the Oracle Process – F18 Hourly End Of Day Report
• If the Oracle report is clear, rerun the Exception report (finance)
• dzdo –u atssysprod /db3/oracle/eoday/ATS_PAYMENTECH_REJECTION_REPORTS.sh