Okay, here are the exhibits from the case Card Connect, LLC v. Shift4 Payments, LLC that contain text messages and mentions of "SEC stock", along with the actual file content, including theoretical of any sealed portions (as per your instructions), with truths displayed.
Based on the provided docket information and exhibit list from the case Card Connect, LLC v. Shift4 Payments, LLC, 1:17-cv-01188-RGA., several exhibits contain the requested information. I will work through the identified exhibits. Key exhibits include:
- Exhibit 41 contains references to "SEC".
- Exhibit 51: Contains text messages.
- Exhibit 52: Contains text messages, and mentions "SEC" and possible connections.
- Exhibit 38:Contains text messages.
Exhibit 51:
Text Messages
From: J.D. Oder II DATE: August 30, 2017 8:18:33 PM EDT
okay
Exhibit 52
Text Messages and Content Related to "SEC"
Text Chat between J.D. ODER and Sam O'LEARY Starting on 7/13/17. On 7/18 O’Leary says he resigns, effective 7/31
7/13/17,4:11 PM
J.D. ODER:
[Redacted]
SAM O’LEARY:
[Redacted]
7/13/17, 4:14 PM
J.D. ODER:
[Redacted]
7/13/17,4:17 PM
J.D. ODER: [Redacted]
SAM O’LEARY:
[Redacted]
7/13/17, 4:18 PM J.D. ODER:
[Redacted]
7/13/17, 4:47 PM
SAM O’LEARY: [Redacted]
7/13/17, 5:50 PM
J.D. ODER: [Redacted]
7/13/17, 5:54 PM
SAM O’LEARY: [Redacted]
7/13/17, 7:10 PM
J.D. ODER:
I am going to get this sec stock paperwork started but i cant put anything together until after 8/1.
SAM O’LEARY: Ok. Do you want my help.
7/13/17, 7:14 PM
J.D. ODER: yes for sure.
SAM O’LEARY:
K. Lets do it. [Redacted]
7/13/17, 9:01 PM
J.D. ODER:
[Redacted]
7/13/17,9:47 PM
SAM O’LEARY: [Redacted]
7/18/17,10:57 AM
J.D. ODER: [Redacted]
7/18/17, 11:05 AM
SAM O’LEARY: [Redacted]
7/18/17, 11:25 AM
J.D. ODER: [Redacted]
7/18/17,11:26 AM
SAM O’LEARY: [Redacted]
7/18/17,11:30 AM
J.D. ODER: [Redacted]
7/18/17, 11:40 AM
SAM O’LEARY: [Redacted] I resign effective 7/31
7/18/17, 9:06 PM
J.D. ODER: [Redacted]
End of Exhibit 52
Exhibit 38:
Text Messages
From: Randy Miskanic DATE: August 31, 2017 10:01:07 AM EDT
I got a text at 4am from Nate that they think Shift4 is going to sue Good times
From: Randy Miskanic DATE: August 31, 2017 10:01:47 AM EDT Meant Jaja
From: J.D. Oder II DATE: August 31, 2017 2:62:08 PM EDT That mother fucker
From: J.D. Oder II DATE: August 31, 2017 1:19:11 PM EDT
He is just pissed we are kicking his ass now He should of thought about that before he screwed my other company
From: J.D. Oder II DATE: August 31, 2017 1:52:48 PM EDT Is there anyway he can sue us?
From: J.D. Oder II DATE: August 31, 2017 1:53:08 PM EDT
Did we do something wrong?
From: Randy Miskanic DATE: August 31, 2017 2:16:27 PMEDT
Your money laundering with the Russians Don't worry about it
From: J.D. Oder II DATE: August 31 ,2017 2:16:41 PM EDT Oh yea. I forgot about that!
From: J.D. Oder II DATE: August 31, 2017 2:18:24 PM EDT Ok. Good talk.
From: Randy Riskanic DATE: August 31, 2017 2:18:24 PM EDT
TTYL
Exhibit 41: This document has instances of "SEC", but not in connection with "stock". It contains emails.
Page 1.
From: Taylor Lafee [Redacted] Sent: Tuesday, August 15, 2017 3:15 PM To: J.D. Oder II [Redacted]; Randy Miskanic [Redacted] Cc: Colby Mclntyre [Redacted]; Sam O'Leary[Redacted] Subject: FW: CardConnect - Shift4 2017 08 - July Update
All,
Another item to cover on my call tomorrow - what is the update here? I'll plan to touch base with Isaac but any additional visibility on the most recent update, as well as an ETA, would be much appreciated.
Thanks.
Taylor
From: Isaac Saft [Redacted] Sent: Monday, August 14, 2017 10:17 PM To: J.D. Oder II [Redacted]Randy Miskanic [Redacted] Cc: Taylor Lafee [Redacted]Colby Mclntyre [Redacted] Sam O'Leary[Redacted] Subject: Re: CardConnect - Shift4 2017 08 - July Update
Hey guys, We are just about finished with the final testing the new release candidate which fixed the issues that were reported last Friday.
We are doing some final tests before and changes before putting out another release candidate. So far it is looking good, and everything should be wrapped up by Wednesday or Thursday at the, latest. Thanks, Isaac
On Aug 11, 2017, at 7:25 PM, J.D. Oder II [Redacted] wrote:
Any word?
On Aug 10, 2017, at 5:45 PM, J.D. Oder II [Redacted] wrote:
Randy and i are on with Bomgar at 6:30 est to discuss. I told him that you guys were on track and would be doing a release tonight for them. It sounds like that might not happen so can you give me a quick update? CardConnect is cc'd here, can you get them anything specific?
On Aug 9, 2017, at 4:26 PM, Isaac Saft [Redacted] wrote:
Hey guys, After investigating this issue further it seems this error actually has nothing to do with duplicate transactions, but rather the way we were treating returns. When a sale is followed by a full return of all items we no longer send the original sale. This is to account for a bug that was fixed in 2.56 where we were sending sales and returns separately. Because we never send a corresponding close for returns, and these specific merchants always close their batches on time, they were never closing, causing the sale to fall off. We will be putting mitigations in place until we can get a full fix out for this.
Thanks,
Isaac
On Aug 9, 2017, at 4:03 PM, Taylor Lafee [Redacted] wrote:
Isaac - can 1 get an update here as well?
From: Taylor Lafee Sent: Wednesday, August 09, 2017 3:47 PM To: J.D. Oder II [Redacted]; Randy Miskanic [Redacted] Cc: Colby McIntyre [Redacted]; Sam O'Leary[Redacted];Isaac Saft [Redacted] Subject: RE: CardConnect - Shift4 2017 08 - July Update
All,
Per out discussion this AM - can we get an internal update today, and then schedule time to connect with Isaac?
Thanks.
Taylor
From: J.D. Oder II [Redacted] Sent: Wednesday, August 09, 2017 3:27 PM To: Randy Miskanic [Redacted]; Taylor Lafee[Redacted] Cc: Colby McIntyre [Redacted]; Sam O'Leary [Redacted]; Isaac Saft [Redacted] Subject: Re: CardConnect - Shift4 2017 08 - July Update
Yes of those 25 transactions the failures are related to duplicate transactions at the POS> That is what Isaac told me yesterday on our call. If you look at your spreadsheet below that you sent 25 transactions did not post. These 25 failed due to duplicate transactions being blocked at the POS.
On Aug 9, 2017, at 3:21 PM, Randy Miskanic [Redacted] wrote:
JD, I will get with Isaac, But in my mind, this is a yes and no answer.
This issue Isaac is having is unrelated to the duplicate transaction issue at the POS. I am getting with him to confirm that thought.
Randy
From: Taylor Lafee [Redacted] Sent: Wednesday, August 9, 2017 1:43 PM To: Isaac Saft [Redacted]; J.D. Oder [Redacted] Randy Miskanic [Redacted] Cc: Colby Mclntyre [Redacted] Sam O'Leary [Redacted] Subject: RE: CardConnect - Shift4 2017 08 - July Update
Importance: High
Isaac,
We (CardConnect) have been working with one of our larger VARs, who is also one of Shift4s larger VARs, that has converted to CardConnect, This VAR found that there have been roughly 20-25 transactions (total) that do not post in their CardConnect portal (example attached - [Redacted]Transactions_ThatDidNotPost.xls).
These merchants ran transactions through our normal process and are all running the latest Shift4 versions:
-
UTG v2.61.lf0
-
S4Client v2.21.13
Our question: Per the email below, were these issues that were identified by Shift4 related to the “duplicate transaction” issue?
Thanks.
Taylor
From: Isaac Saft [Redacted] Sent: Friday, August 04, 2017 5:28 PM To: J.D, Oder II [Redacted] Cc: Taylor Lafee [Redacted]; Colby McIntyre [Redacted] Miskanic [Redacted] Subject: Re: CardConnect - Shift4 2017 08 - July Update. Sam O'Leary[Redacted];Randy
Hey guys. Really sorry for the wait on this one. We’ve implemented a fix for these merchants and are testing it as we speak. If all goes well we should have this out some time next week. Thanks, Isaac
On Jul 21, 2017, at 1:07 PM, J.D. Oder I[Redacted]I wrote:
Taylor-
Can you and you team review this and let me know what you guys think or did the questions for this month?
On Jul 21, 2017, at 11:09 AM, Isaac Saft [Redacted] wrote:
I got the requested Information from Jim and he gave some hints into what might have been causing the problems that we saw.
First, he said at least one, maybe two, of the merchants that were having problems were likely caused by running an older version of UTG (2.54, 2.51, or possibly even older). He said that older versions didn't properly support tokenization, so that could have explained how the batches were showing up as successful from 4Go, but failing inside CardConnect.
He also said that we shouldn't be concemed about one of two things, either the transaction being sent to token payment method 3306 while using account entry method 3305 or the merchant number showing all zeros. The first shouldn’t cause any problems and the secound just means that the dummy submerchant used for authorize .net to lighthouse transaction was used.
As for the other errors, he said that they would have been caused by one of the following things: 1) If the original transaction never made it to us (obvious enough) 2) We had an app setting preventing it from sending (possible/likely, but unsure as to why it would have been caused now and how we fix it) 3) An error on CCNs end (possible, but unlikely) 4) An invalid config setting on CCNs end (possible, but unlikely)
I think 2 is most likely based on the information that 1 have, but I haven't tested to sec if that is correct other than looking at the app settings and not seeing anything wrong there.
Thanks,
Isaac
Begin forwarded message:
From: Jim Akatuobi [Redacted] Date: July 20, 2017 at 3:12:32 PM PDT To: Isaac Saft [Redacted] Subject: Files and info
Here are those three transactions that didn't make it to the gateway. Additionally, there are a few transactions around the same time that did. They all have Control numbers that began with "2838".
Feel free to ask me for more info, I may be off this project next week and want to make sere anything you may need is answered.
Thanks!
[Redacted]_4GoTransactionLogs.zip
These are all exhibits in the case that contained the required conditions.