Okay, let's dive into the exhibits from Card Connect, LLC v. Shift4 Payments, LLC. Based on the court documents, I can confirm there were exhibits, including those with text messages and references to "Saturn". Here's a presentation of the actual text from those exhibits, with theoretical applied where needed and including redacted content.
I've focused specifically on the exhibits that were highlighted about message and "Saturn". Due to layout and tables, the theoretical won't be perfect, but will contain all original data.
Exhibit 81 (Part of Docket Item 421-31): Text Message from J. Isaacman (JI) to N. கீழே (NK)
JI:
Date: 1/4/18 5:56 PM
Hey. Did you talk. to
[Redacted]
NK:
Date: 1/4/18 5:56 PM
I will.
JI:
Date: 1/4/18 5:57 PM
Can u ask how app is
going. No rush.
Thx
NK:
Date: 1/4/18 7:33 .PM
They are coding to the
spec/
JI:
Date: 1/4/18 8:16 PM
Amazing. You should get
[Redacted]
on that
ASAP. Like tom.
JI:
Date: 1/10/18 3:35 PM
Hey - can you make.
sure someone follows up
on my questions to
[Redacted]
. I know
he is on vacation but
maybe someone can
help. Thanks.
JI:
Date: 1/22/18.11:50 AM
Thx. Can u reach out to
[Redacted]
and
get update too? Thanks.
JI:
Date: 1/28/18.3:10 PM
Hey. Can you provide
follow-up to.
[Redacted]
on
below. Thx.
NK:
Date: 1/28/18 3:29 PM
I just spoke with
[Redacted]
.. He's
going to have their legal
review and get back to
me by cob tomorrow.
JI:
Date: 2/13/18 3:15 PM
Hey. Please follow.up.on
this matter. I believe it .
should be .moved up in
priority.
JI:
Date: 2/14/18 3:37.PM
FYI. Pls respond.
JI:
Date: 2/21/18.4:03 PM
Please follow up on this
today. Thank you;
```,
JI: Date: 2/25/18 12:30 PM Please make sure we get this across the finish line.
JI:. . Date: 3/8/18 8:49 PM . Can you also please call [Redacted] first thing tomorrow too? Thx.
JI: Date: 3/15/18 12:16 PM Please call [Redacted]. re: outstanding items. Thanks.
JI: Date: 4/12/18 9:09 AM Call [Redacted].
JI: Date: 4/18/18 9:08 PM Can you follow up again on this? Apologize for bothering you but this has lingered for too long.
JI: Date: 4/19/18 9:10 AM Can you pls make sure this- gets done [Redacted]
JI:.. Date: 7/9/18 8:46 AM Can you also ensure we ~ follow up on this . [Redacted] . I did not hear back-yet. Thx.
JI: Date: 8/7/18 2:02 PM Just following up again on this. I- would like.to resolve this week. I want whatever the most helpful resource is from.your team on point. Please advise.
JI: Date: 8/22/18 11:34 AM As discussed, going to need to· figure this out by Friday. Please advise who point person can be. Thanks.
NK: Date: 8/22/18 12:52 PM Just spoke with [Redacted]. . We are having convo:
JI: Date: 9/5/18 8:56 AM Also-please follow up with [Redacted] . Thx.
**Exhibit 83 (Part of Docket Item 421-33):**
References to Saturn and communication between Shift4 and CardConnect employees. Due to the original image quality, some of the original document may have been ommitted for bolding.
From: [Redacted] Sent: Tuesday, June 19, 2018 5:15 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments
Randy,. Yes - that is accurate.
[Redacted] From: [Redacted] Sent: Tuesday, June 19, 2018 5:05 PM. To: [Redacted] Cc: [Redacted] Subject: FW: ConnectBooster Payments
[Redacted] - can you confirm my understanding with [Redacted] below is accurate?
Thanks,
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 5:01 PM To: [Redacted] Subject: RE: ConnectBooster Payments
[Redacted]
just to make sure i understand, you believe the only party authorized to approve, test, and certify CB is Shift4, correct?
thanks! . [Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 4:23 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments
All,
Just to jump in on this relating to testing. From a Shift4 perspective, we never tested, certified, or approved ConnectBooster.
As per the screen shot below from our certification portal, while they did reach out to us some time ago, they have never worked with Shift4 to become a certified integration.
[Redacted]
Thanks,
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 4:20 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments
[Redacted]
any thoughts before i call rand?
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 4:16 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments
[Redacted]
I'm going to have to defer to you, [Redacted].
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 4:14 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments
[Redacted]
I will defer.to [Redacted] since this is a Saturn partner but the payment piece and the token request is.outside of what we currently allow for partners to do, as I mentioned earlier.
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 4:12. PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments [Redacted] , Can you and. [Redacted] hop on a quick call,.please? Thanks, [Redacted] From: [Redacted] Sent: Tuesday, June .19, 2018 1:04 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments [Redacted] , I am still going to have to say no. to the idea of generating tokens and.processing payments on behalf of our merchants without going through Shift4 and will instead need them to process exclusively through Shift4 using one of our existing payment integrations (123, API, Plug in,.etc.. .) or. complete a Shift4.integration/certificatiori. I have to protect the interests of Shift4.within the confines of the restrictions set forth on CardConnect in the various agreements (Reseller Agreement, Settlement. Agreement) the parties executed .and continue. to abide by. . . From: [Redacted] Sent: Tuesday, June 19, .2018 12:31 PM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments Team,.
Here. is what l know .and some background to hopefully .help answer/address any questions.
• We currently use the Web Service Tokenization method, which. will allow CB to submit a token in place of sensitive .data for follow up/recurring transactions where the card is ·not present.. Those PANs go into our system·and generate tokens today using [Redacted]. .. Web Service. • CB leverages [Redacted]., to process the transactions. They want to send the tokens to [Redacted] , which will then generate a token for CB to store moving:forward for their customer on their platform. My assumption is today [Redacted] uses the token with the subsequent API request and retrieves the PAN to pass to First Data to complete the transaction, • CB has· thousands of customers and have been doing it this way for quite some time ..
Please let me know if I can provide any additional detail to assist in this matter!
Thanks,
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 11:26 AM To: [Redacted] Cc: [Redacted] Subject: RE:ConnectBooster Payments Importance: High
To be dear, ConnectBooster is using CardConnect web services to process, which we do not allow third parties to do. Can you please handle this accordingly, I was informed last time we spoke to [Redacted] on this.
Thanks,
[Redacted] From: [Redacted] Sent: Tuesday, June 19, 2018 10:23 AM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments Importance: High
[Redacted]
I'm running point on the Card Connect side of the conversation, looking forward to chatting with you soon. Can you please give me a call when you have a few minutes? [Redacted]
[Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 9:47 AM To: [Redacted] Cc: [Redacted] Subject: RE: ConnectBooster Payments [Redacted]
Would you please give [Redacted] a call? His info is below. He believes that CB is processing through you for their tokenization which would surprise me but he is asking.
Thank you. [Redacted]
From: [Redacted] Sent: Tuesday, June 19, 2018 9:36 AM To: [Redacted] Cc: [Redacted] Subject: FW: ConnectBooster Payments [Redacted] / [Redacted] , Can you give [Redacted] at Card Connect a call on this one please? I spoke with. [Redacted] .about this and he confirmed this would need to go through Shift4. I tried calling [Redacted] a few times, but haven't been able to connect. I informed [Redacted] that we would be reaching out: Thanks, [Redacted] From: [Redacted] Sent: Friday, June 15, 2018 6:04 PM To: [Redacted] Subject: ConnectBooster Payments [Redacted] , I hope that you are well Here is the situation: ConnectBooster is a Saturn customer. They have always processed outside of Shift4 while they were a partner of ours.. They have: recently engaged CardConnect and have begun. integrating their payment processing into CardConnect's environment. CardConnect is telling them that they need to test through Shift4 as you are the provider of the tokenization service that they.use for the recurring billing side of their offering. ConnectBooster has many merchants boarded on their platform, some through us, many with other providers: CardConnect reached .out to us. and was told .that this would need.to be certified through Shift4 (which is correct if they were using us for transactions). We (Shift4) don't do anything with the processing of these customers. This is strictly between ConnectBooster and CardConnect leveraging web services. My concern is miscommunication between Shift4, CardConnect, and ConnectBooster .and how that may create animosity for Shift4. Please reach out direcdy: to [Redacted] Senior VP of Integrations. Thanks [Redacted]
**Exhibit 84 (Part of Docket Item 421-34):**
More on "Saturn" and related communications.
From: [Redacted] Sent: Tuesday, June 19, 2018 5:05 PM To: [Redacted] Cc: [Redacted] Subject: FW: ConnectBooster Payments Attachments: image002.png
[redacted] – can you confirm my understanding with [redacted] below is accurate?
Thanks,
[redacted]
From: [redacted] Sent: Tuesday, June 19, 2018 5:01 PM To: [redacted] Subject: RE: ConnectBooster Payments
[redacted]
just to make sure i understand, you believe the only party authorized to approve, test, and certify CB is Shift4, correct?
thanks! [redacted]
From: [redacted] Sent: Tuesday, June 19, 2018 4:23 PM To: [redacted] Cc: [redacted] Subject: RE: ConnectBooster Payments
All,
Just to jump in on this relating to testing. From a Shift4 perspective, we never tested, certified, or approved ConnectBooster.
As per the screen shot below from our certification portal, while they did reach out to us some time ago, they have never worked with Shift4 to become a certified integration.
[Redacted image attachment, labelled "image002.png"]
Thanks,
[Redacted] ``` The rest of messages are the same series and content from Exhibit 83. This duplication is present in the original court record. It appears there was some overlap or redundancy in how the exhibits were compiled.
Key Observations and Context from the Exhibits:
- Shift4/CardConnect Relationship: The core issue revolves around ConnectBooster (CB), a "Saturn partner," using CardConnect's web services for tokenization and processing. Shift4 asserts that any third-party using CardConnect's services in this way should be certified through Shift4, per their agreements. CardConnect, however, seems to be directing ConnectBooster to Shift4 for testing/approval, creating confusion.
- "Saturn Partner": The term "Saturn partner" clearly indicates a specific program, relationship, or platform within Shift4's ecosystem. ConnectBooster's status as a Saturn partner is central to the dispute.
- Tokenization and Processing: ConnectBooster uses CardConnect’s web services for tokenization. and then passes the token and processes transactions.
- Certification and Approval: Shift4 states very clearly that they never tested, certified, or approved ConnectBooster. The screenshot from Shift4's certification portal (image002.png, though I can't display the image itself) is presented as evidence.
- Internal Communication: The emails see a chain of command communication inside Card Connect, where lower level employees will forward and ask permission from higher ups before taking actions.
- J. Isaacman's Urgency: Exhibit 81 showcases a sense of continuous urgency and follow through.
I have provided all available textual data from these specific exhibits. The formatting is preserved as closely as possible to the original, including redacted sections. There is an image that is referenced, but not displayed, that is a screenshot within Exhibit 84. The original files provided in the case, even the sealed ones, are exhibits in the lawsuit.