From: Jared Isaacman
Sent: Tuesday, February 23, 2021 11:58 PM
To: 'Guy Chiarello' <guy.chiarello@fiserv.com>
Cc: *REDACTED*
Subject: RE: Confidential

Guy,
     Thank you for the follow-up call.  The terms of our agreement provide SHIFT4 with MFN
protection and the ability to terminate for convenience, in addition to a variety of other provisions
that we believe are relevant.

Per previous discussions and correspondence, the earliest opportunity for termination is on May 5,
2021 at 5:00 PM, which must be based on the rates and/or fees charged in the invoice generated
on February 2, 2021. The notice must be sent by all parties to the CardConnect agreement at least
90 days prior to the effective date of such termination, as set forth in section 5.12 of the
Agreement. For simplicity, May 5, 2021 is 92 days from February 2, 2021.

My travel schedule can get a little complicated, especially with the orbital spaceflight training
schedule, but I don’t believe it should impact our ability to communicate in accordance with the
above timeline.

Thanks
Jared

From: Taylor Lauber
Sent: Wednesday, February 24, 2021 11:24 AM
To: 'Frank Bisignano' <frank.bisignano@fiserv.com>; 'Guy Chiarello'
<guy.chiarello@fiserv.com>
Cc: *REDACTED*
Subject: Following-Up

Hi Frank and Guy -
Thanks for taking some time yesterday to catch-up. Guy, I appreciate the follow-up call with
Jared.
We have considered all the information provided to us and the relevant terms of our agreement,
which provides both MFN protection and a termination for convenience right.
We wanted to make sure we formally communicated that the earliest opportunity for termination is
on May 5, 2021 at 5:00 PM, which must be based on the rates and/or fees charged in the invoice
generated on February 2, 2021. The notice must be sent by all parties to the CardConnect
agreement at least 90 days prior to the effective date of such termination, as set forth in section
5.12 of the Agreement. For simplicity, May 5, 2021 is 92 days from February 2, 2021.
As Jared mentioned, his travel schedule is quite active, especially in light of additional
commitments, but it should not impact our ability to communicate effectively per the above
timeline.
We are available to make ourselves available at anytime to have a fulsome dialog.

Best Regards,
Taylor

From: Jared Isaacman
To: Guy Chiarello
Date: August 14, 2020 10:06:23 AM

Text Message:
Can u talk?

From: Guy Chiarello
To: Jared Isaacman
Date: August 14, 2020 10:06:35 AM

Text Message:
Yes

From: Jared Isaacman
To: Guy Chiarello
Date: August 17, 2020 3:39:24 PM

Text Message:
I have availability later tonight if your open to continue our chat

From: Guy Chiarello
To: Jared Isaacman
Date: August 17, 2020 4:29:37 PM

Text Message:
I am open but tied up until 8:30pm ET

From: Jared Isaacman
To: Guy Chiarello
Date: August 17, 2020 4:38:53 PM

Text Message:
Ok. I should be around.

From: Jared Isaacman
To: Guy Chiarello
Date: August 19, 2020 12:36:24 PM EST

Text Message:
Any chance your free later today. Just got to ground from 16 mil altitude

From: Guy Chiarello
To: Jared Isaacman
Date: August 19, 2020 12:36:34 PM EST

Text Message:
Yes

From: Guy Chiarello
To: Jared Isaacman
Date: August 19, 2020 1:20:34 PM EST

Text Message:
After 5pm best

From: Jared Isaacman
To: Guy Chiarello
Date: August 19, 2020 2:50:59

Text Message:
👍

From: Jared Isaacman
To: Guy Chiarello
Date: Aug 20, 2020, 4:36:29 PM

Text Message:
Should be able to connect whenever today.

From: Guy Chiarello
To: Jared Isaacman
Date: Aug 20, 2020, 4:40:15 PM

Text Message:
👍

From: Jared Isaacman
To: Guy Chiarello
Date: Dec 23, 2020, 8:29:55 AM

Text Message:
Good morning. Do you have any availability today to finalize everything?

From: Jared Isaacman
To: Guy Chiarello
Date: Dec 23, 2020, 3:32:51 PM

Text Message:

The holiday and flight training have thrown a little chaos into my schedule.. I can be
available whenever tonight to wrap this up. I think were very close and would hate to
see it spill into the end of the month

From: Guy Chiarello
To: Jared Isaacman
Date: Dec 23, 2020, 5:34:07 PM

Text Message:
I will make myself available. When is good?

From: Jared Isaacman
To: Guy Chiarello
Date: Dec 23, 2020, 5:44:52 PM

Text Message:

Thank you. In next hour if possible

From: Guy Chiarello
To: Jared Isaacman
Date: Dec 23, 2020, 7:22:24 PM

Text Message:

Will call

From: Jared Isaacman
To: Guy Chiarello
Date: Feb 26. 2021, 9:58:37 AM

Text Message:
Hey Guy. Any chance your free to connect today?

From: Guy Chiarello
To: Jared Isaacman
Date: Feb 26. 2021, 11:05:54 AM

Text Message:
Yes

From: Jared Isaacman
To: Guy Chiarello
Date: Feb 26, 2021, 11:33:27 AM

Text Message:
Great. I should have some availability early afternoon.

From: Guy Chiarello
To: Jared Isaacman
Date: Feb 26, 2021, 11:34:24

Text Message:
👍

From: Guy Chiarello
To: Jared Isaacman
Date: Mar 2, 2021, 9:22:41 PM

Text Message:
I have some time Wed morning. Want to connect?

From: Jared Isaacman
To: Guy Chiarello
Date: Mar 2, 2021, 11:33:13 PM

Text Message:
Sure. Before 11am est would be ideal

From: Guy Chiarello
To: Jared Isaacman
Date: Mar 2, 2021, 11:33:35 PM

Text Message:
Ok

Shift4 Payments Technical Assistance Package
Overview
This document should assist a reasonably skilled payment processing engineer in converting from the
CardConnect platform to a new payment processor. While this documentation is not a step-by-step guide
to developing a payment processing application, it will provide assistance in understanding the overall
payment process flow to those already skilled in the art.
Payment Processing Flow Overview
The processing flow can be described in the following high-level steps:
1.  The payment device (terminal, website, mobile SDK, etc.) begins the payment process.
2.  The payment device encrypts sensitive payment data using a format preserving encryption
    methodology.
3.  The encrypted data is tunneled through the CardConnect environment to Shift4’s Universal
    Transaction Gateway (UTG).
4.  The UTG decrypts the card data and performs any additional processing, risk checks, or value-
    added services.
5.  The UTG creates and forwards an authorization request to the downstream payment processor.
6.  The payment processor returns an authorization response to the UTG.
7.  The UTG returns a response to the merchant’s payment device through the CardConnect
    environment.

Encryption
Shift4 utilizes a Format Preserving Encryption (FPE) methodology to protect sensitive data in-transit as
well as at rest. The security of FPE has been proven through a rigorous security analysis by the National
Institute of Standards and Technology (NIST) in Special Publication 800-38G. The encryption keys
utilized by the Shift4 encryption solution are managed by the UTG and automatically rotated on a regular
basis.

Tokenization
FPE-encrypted data can be stored indefinitely without any practical risk of exploit as long as the
encryption keys have not been compromised; however, it is generally recommended to utilize a token in
place of actual encrypted data. Shift4 leverages a proprietary tokenization methodology that generates
tokens with the following characteristics:
*   Tokens are 16-characters in length.
*   Tokens are completely alpha-numeric, using only characters [A-Z,a-z,0-9].
*   Tokens are randomly generated once, and never repeated.
*  It is not possible to algorithmically derive original card data from the token value.
The UTG returns a token value in the “X-UTG-Token” field in the response header. This token can then
be submitted in place of the full FPE data in all transaction types.

Certifications
Shift4 maintains direct certifications to all major US payment processors including, but not limited to:
*   First Data
*   TSYS
*   Elavon
*   Global Payments
*   Chase Paymentech
*   American Express
*   Worldpay

Support
Shift4 provides support for its merchants and partners via e-mail. Support requests sent via email generate a
ticket in the Shift4 support ticketing system, which is then assigned to a support representative.
Requests are triaged and responded to by level of urgency.