From: J.D. Oder [mailto:joder@shift4.com]
Sent: Monday, March 27, 2017 4:31 PM
To: Nate Hirsh <nhirsh@cardconnect.com>
Cc: Randy, Jr. Oder <roder@shift4.com>; Dan Carr <dcarr@cardconnect.com>
Subject: RE: Kick off call for First Data Rapid Connect Certification

Hey Nate,

Before we schedule resources can we all agree on a mutual drop-dead date?
I'm willing to spend the time to do this, but it has to result in going after
First Data together.

Thanks,
J.D.

From: Nate Hirsh [mailto:nhirsh@cardconnect.com]
Sent: Monday, March 27, 2017 1:26 PM
To: J.D. Oder <joder@shift4.com>
Cc: Randy, Jr. Oder <roder@shift4.com>; Dan Carr <dcarr@cardconnect.com>
Subject: RE: Kick off call for First Data Rapid Connect Certification

Sounds good look forward to next steps.

Thanks
Nate

From: J.D. Oder [mailto:joder@shift4.com]
Sent: Monday, March 27, 2017 4:20 PM
To: Nate Hirsh <nhirsh@cardconnect.com>
Cc: Randy, Jr. Oder <roder@shift4.com>; Dan Carr <dcarr@cardconnect.com>
Subject: RE: Kick off call for First Data Rapid Connect Certification

We're good with two weeks.  Let me know how I can help.

Thanks,
J.D.

From: Nate Hirsh [mailto:nhirsh@cardconnect.com]
Sent: Monday, March 27, 2017 12:54 PM
To: J.D. Oder <joder@shift4.com>
Cc: Randy, Jr. Oder <roder@shift4.com>; Dan Carr <dcarr@cardconnect.com>
Subject: RE: Kick off call for First Data Rapid Connect Certification

JD-

We are going to need two weeks, please advise if this works?

Thanks
Nate Hirsh

From: r\J,D. Oder [mailto:joder@shift4.com]
Sent: Wednesday, April 05, 2017 7:39 AM
To: Nate Hirsh <nhirsh@cardconnect.com>
Cc: Randy, Jr. Oder <roder@shift4.com>; Dan Carr <dcarr@cardconnect.com>
Subject: RE: Kick off call for First Data Rapid Connect Certification

It's no secret that the relationship between First Data and CardConnect is
tense, especially at the executive level.

We're willing to do the work, but we need to be absolutely sure of
CardConnect's commitment prior to starting.

Thanks,
j.D.

From:   J.D. Oder [mailto:joder@shift4.com]
Sent:   Thursday, April 20, 2017 9:56 AM
To: 'Angelo Grecco'
Cc: 'Randy, Jr. Oder'; 'Daniel Turner'; 'Ryan McIsaac'; 'Nate Hirsh'; 'Dan Carr'
Subject:    RE: Go-Live

Hey Angelo,

Our disappointment with CardConnect has grown since you and I last spoke. Their
refusal to show any commitment toward a joint First Data/Shift4 go-to-market strategy
was incredibly shocking and telling.

We were blindsided by the news that they were acquired.  When First Data
acquires them, there is no doubt in my mind that they'll be forced off supporting
Shift4, which would include the 8,000+ merchants we have on their platform now.

Thanks,
j.D.

Case 2:17-cv-03988-MAK Document 20-7 Filed 10/06/17 Page 1 of 2

Messages                 JD Oder                      Details

Apr 19,2017 11:59 AM

JD Oder
We should talk about CardConnect

Me
Now?

JD Oder
Yup
Shit show
11:59 AM

Me
I hate them
12:01 PM

JD Oder
I'm so pissed
You have no idea
12:01 PM

Me
What do you need from us?
12:02PM

JD Oder

Need proof of concept by next
Wednesday

Can you do it?
12:03 PM

Me
I need 2 weeks.
12:09 PM

JD Oder
I don't think we have it.
12:10 PM

Case 2:17-cv-03988-MAK Document 20-7 Filed 10/06/17 Page 2 of 2

Messaqes                 JD Oder                      Details

Apr 19, 2017

Me
What happened.
12:20 PM

JD Oder
They don't want to do fdms with us
They want ts.
12:21 PM

Me
That's fine. Do both.
12:21 PM

From:   J.D. Oder [mailto:joder@shift4.com]
Sent:   Wednesday, April 26, 2017 2:49 PM
To: 'Nate Hirsh'
Cc: 'Randy, Jr. Oder'; 'Dan Carr'
Subject:    RE: timing

I can be ready by tomorrow EOD. Can you get yours over to us by then?

Thanks, J.D.

From:J.D. Oder [mailto:joder@sllift4.com]
Sent: Thursday, May 04, 2017 2:21 PM
To: 'Nate Hirsh'
Cc: 'Randy, Jr. Oder'; 'Dan Carr'
Subj~ct: RE: timing

I hear you - and maybe you're right... But that doesn't change my opinion that
CardConnect is holding the Rapid Connect/4Go solution hostage because they
have continued to prioritize TSYS over FDMS in their development queue despite
agreeing to work on the joint solution.

We're not opposed to developing the integration, but we're not comfortable building
this without confirmation, in writing, that CardConnect is willing to process First
Data merchants should Shift4 build and support the integration per the
agreement All of the merchants that were seeking this
solution would have to be boarded 100% on CardConnect.

Thanks,
J.D.

Case 2:17-cv-03988-MAK Document 20-10 Filed 10/06/17 Page 1 of 4
Messages                 JD Oder                      Details

May 23, 2017

JD Oder
Hey, give me a call when you can

Me
k
4:36 PM

JD Oder
We have a certified solution w/ Rapid
Connect to First Data. We have a
selling agreement w/ CardConnect.

We *thought* we had an agreement to
process FD merchants w/
CardConnect, using 4Go.

CardConnect is now saying they are
going to continue letting us take TSYS
but not First Data.

I need to know if you think we have an
agreement or not.

I'm pretty frustrated at this point,
getting ready to call Chuck and tell
him his team ran us around for 3
months knowing the plan was to sell
to First Data.
4:36 PM

Case 2:17-cv-03988-MAK Document 20-10 Filed 10/06/17 Page 2 of 4

Messaqes                 JD Oder                      Details

May 23, 2017, 4:36 PM
Me
I do not.

JD Oder
Ok. Thanks for confirming.

Sorry to waste your time with this.
4:37 PM

Me

JD Oder
I may have to adjust my testimony
then.
4:42 PM

Me
Did you have a drop dead date for me
to start first data with Rapid Connect
certification?
4:47 PM

JD Oder
Yes - the date that we tested the
application with you.

I told you if you didn't hit that date
we'd move on without your approval
process.

I believe it was May 1st, per my
email.

But I'll need to get that for you.
4:48 PM

Case 2:17-cv-03988-MAK Document 20-10 Filed 10/06/17 Page 3 of 4
Messages                 JD Oder                      Details

                                          May 23, 2017

Me
                                  I will get you the lanuage I sent over
                                 4:53 PM

JD Oder
                                  Thanks.
                                 4:53 PM
                                                         Write a message

Case 2:17-cv-03988-MAK Document 20-10 Filed 10/06/17 Page 4 of 4

MessaQes                 JD Oder                      Details

May 24, 2017

Me

We never agreed nor would have agreed

to the following, which you sent:

"We're not opposed to developing the
Integration, but we're not comfortable
building thls without confirmation, In
writing. that CardConnect is willing to
process Flrst Data merchants should
Shift4 build and support the Integration
per the agreement. All of the merchants

that were seeking this solution would
have to be boarded 100% on

CardConnect"

May 24, 2017, 6:48 PM

JD Oder
Ok.

I'll add this to my testimony.
6:55 PM

From: J.D. Oder [mailto:joder@shift4.com]
Sent: Wednesday, May 24, 2017 10:23 AM
To: 'Nate Hirsh' <nhirsh@cardconnect.com>
Cc: 'Randy, Jr. Oder' <roder@shift4.com>; 'Dan Carr' <dcarr@cardconnect.com>
Subject: RE: timing

Nate,
Our understanding was that the agreement was for all merchants using this
solution - meaning both First Data and TSYS.
Is your understanding different?
Thanks, j.D.

From: Nate Hirsh [mailto:nhirsh@cardconnect.com]
Sent: Wednesday, May 24, 2017 6:48 PM
To: J.D. Oder <joder@shift4.com>
Cc: Randy, Jr. Oder <roder@shift4.com>; Dan Carr <dcarr@cardconnect.com>
Subject: RE: timing

JD-

We never agreed nor would have agreed to the following, which you sent:
"We're not opposed to developing the integration, but we're not comfortable building this without confirmation, in writing,
that CardConnect is willing to process First Data merchants should Shift4 build and support the integration per the agreement.
All of the merchants that were seeking this solution would have to be boarded 100% on CardConnect."

Thanks,

Nate

From: J.D. Oder [mailto:joder@shift4.com]
Sent: Thursday, June 01, 2017 7:41 AM
To: 'Patrick Ward'
Cc: 'Randy, Jr. Oder'
Subject: FW: CardConnect

We did build this integration. They refused to support it.

From: Patrick Ward [mailto:pward@cardconnect.com]
Sent: Wednesday, May 31, 2017 4:36 PM
To: J.D. Oder <joder@shift4.com>
Cc: Randy, Jr. Oder <roder@shift4.com>
Subject: CardConnect

JD,

After speaking with the team here, given where we are at with the pending First Data
acquisition, we are not going to move forward with a Rapid Connect integration at this time.

We appreciate your understanding.

Pat Ward

Case 2:17-cv-03988-MAK Document 20-18 Filed 10/06/17 Page 1 of 5
Shift4 Payments, LLC Confidential Information

UTPG_SOURCE

1. Label
Auth Request
2. Label
Auth Response
3. Label
Capture
4. Label
Capture Response
5. Label
Refund
6. Label
Refund Response
7. Label
Void
8. Label
Void Response
9. Label
Tip Adjust
10. Label
Tip Adjust Response
11. Label
Close Batch

Case 2:17-cv-03988-MAK Document 20-18 Filed 10/06/17 Page 2 of 5
Shift4 Payments, LLC Confidential Information

12. Label
Close Batch
Response
13. Label
Force Auth/Post
14.
Force Auth/Post
Response
15. Label
AVS Only
16.
AVS Only
Response
17.
Tokenize
18.
Tokenize Response

Transaction Routing

Field Name, Required, Format, Max Length, Notes
ACCOUNT, Yes N, 19, Primary Account Number
EXP, Yes, N , 4, Expiration Date (MMYY
AMOUNT, Yes, N, 12, Auth + Tip Amount.

Case 2:17-cv-03988-MAK Document 20-18 Filed 10/06/17 Page 3 of 5
Shift4 Payments, LLC Confidential Information
Field Name, Required, Format, Max Length, Notes

INVOICE, Cond, AN, 9

PONUMBER, No, AN, 17

ADDRESS, No, ANS, 30
ZIP, NO, ANS, 9

Case 2:17-cv-03988-MAK Document 20-18 Filed 10/06/17 Page 4 of 5
Shift4 Payments, LLC Confidential Information

Case 2:17-cv-03988-MAK Document 20-18 Filed 10/06/17 Page 5 of 5
Shift4 Payments, LLC Confidential Information

3. Response Fields
Field Name, Required, Format, Max Length, Notes
UTPG_TRAN_ID, YES, N, 15
ERROR_NUMBER, YES, N, 5
ERROR_MESSAGE, YES, ANS, 50

Case 2:17-cv-03988-MAK Document 20-22 Filed 10/06/17 Page 1 of 1
Shift4 Payments, LLC Confidential Information

1. i4Go Certification Guidelines

1.1 Overview

i4Go is designed to minimize the impact of a single point of failure on the
merchant. A gateway failure or a failure at one of the processors should not affect
the merchant. If a gateway is down, the customer's location remains
operational. If there is a processor failure, the merchant still will still have the
ability to authorize credit cards at all remaining processors.

1.2 Key Features

2. Certification Setup pre-requisites.

2. Certification checklist

2.1 Gateway Test Environment and Setup Pre-Requisltea

2.1.1. CardConnect credentials provided.
2.1.2. Shift4 Account created (includes creating an Account, Division, and
Location).
2.1.3. i4Go is enabled on the Location account.
2.1.4. All supported processors are configured on the Location account.
2.1.5. At least one non-supported processor must be entered to complete
gateway substitution testing.

2.2 Required Testing

Transaction Type, Required, Auth, Capture, Refund, Void

/opt/local/apache2/conf/original/extra/httpd-ssl.conf
/opt/local/apache2/conf/extra/httpd-ssl.conf.
/opt/local/www/apache22/data/i4go"_new/ne1N/config/auth.php-cardconnect

<?PHP
//
/ / auth . php--CardConnect
$i4go[ 'auth ' ] [ 'ccrdconnect' ] [ 'url' ]=
  getenv('I4GO_CARD_CONNECT_URL');
$i4go[ 'auth' ] [ 'cardconnect' ] ['method']="POST";
$i4go[ 'auth' ] ['cardconnect' ] [ 'timeout'] = 12;
$i4go[ 'auth ' ] ['cardconnect' ] [ 'proxy'] = false;
$i4go[ 'auth ' ] ['cardconnect' ] [ 'response_codes' ] =
  array ( "A"=>"APPROVED", "B"=>"TRY_AGAIN",
  "C"=>"HOST_DOWN",""=>"UNKNOWN");
$i4go[ 'auth' ]['cardconnect' ]['credential_on_file'] =false;
?>

<?PHP
//
//auth.php--Dummy
$i4go[ 'auth ' ] [ 'dummy' ] [ 'url' ]- getenv('I4GO_DUMMY_URL');
$i4go[ 'auth' ][' dummy' ] ['method'] = "POST";
$i4go[ 'auth' ] [ 'dummy' ] [ 'timeout'] = 12;
$i4go[ 'auth' ] ( 'dummy' ] [ 'proxy' ] = false;
$i4go[ 'auth' ]['dummy' ]['credential_on_file' ] = false;
$i4go[ 'auth' ] [ 'dummy' ] [ 'response_codes']
array("A"=>"APPROVED", ''=>"UNKNOWN");
?>

//auth.php--FDMS_Nashville_i4Go.
S14go['auth']['fdms_nashville_14go')('url' l=
  getenv('I4GO_FDMS_NASHVILLE_I4GO_URL' ll i
$i4go['auth' J[ 'fdms_nashville_i4go' J[ 'method' l = "POST";
$i4go[ 'auth' ]('fdms_nashville_i4go' ]( 'timeout' ] - 12;
$i4go( 'auth' ][ 'fdms_nashville_i4go' ]( 'proxy' ] = false;

$i4go['auth' ]['fdms_nashville_i4go' ]['credential_on_file'] = false;

7/
// REQUIRED for FDMS Nashville i4go
//$i4go['auth')('fdms_nashville_i4go'[ 'headers'] -
// array('Content-Type: text/plain');
//
//$i4go('auth'[ 'fdms_nashville_i4go' J[ 'processors' J =
// Sprocessors;
//
//$i4go('auth' ]['fdms_nashville_i4go' J( 'response_codes' J =
// array ( "A"=>"APPROVED", "0"=>"UNKNOWN") ;
?>

<?PHP
//
// auth.php--FirstData_RapidConnect
$i4go( 'auth' ]( 'fd_rapidconnect' ][ 'url' ]-
getenv('I4GO_FD_RAPIDCONNECT_URL' );
$i4go[ 'auth' ] [ 'fd_rapidconnect' ] [ 'method'] = "POST";
$i4go( 'auth' ] [ 'fd_rapidconnect' ] [ 'timeout'] = 12;
$i4go( 'auth' ] [ 'fd_rapidconnect' J( 'proxy'] = false;
$i4go[ 'auth' ]['fd_rapidconnect' ]['credential_on_file' ] = false;

// REQUIRED for FDMS Nashville i4go
//$i4go('auth J( 'fd_rapidconnect' ]( ' headers']
-
// array('Content-Type: application/xm1');
//
// $i4go [ 'auth' ] [ 'fd_rapidconnect' ] [ 'processors' ]
$processors;
$i4go['auth' J[ 'fd_rapidconnect' ]( 'response_codes' ] =
array ( "A"=>"APPROVED ", ,, 0 ,,=>,, UNKNOWN");
?>

<?PHP
/ /
// auth . php--Heartland
$i4go( 'auth' ] [ 'heartland' ] [ 'url' ]-
getenv('I4G0_HEARTLAND_URL');
$i4go( 'auth' ] [ 'heartland' ] [ 'method' ] = "POST";
$i4go{ 'auth' ] [ 'heartland' ][ 'timeout'] = 12;
$i4go[ 'auth' ]( 'heartland' ]( 'proxy'] = false;
$i4go[ 'auth' ] [ 'heartland' ] [ 'response_codes' ] =
array ( "85"=>"APPROVED", ""=>"UNKNOWN");
$i4go[ 'auth' ] ['heartland' ]['credential_on_file'] false;
?>

< ?PHP / /
// auth.php--TSYS_i4Go

$i4go[ 'auth' ] [ 'tsys_i4go' ] [ 'url' ]=
getenv('I4GO_TSYS_I4GO_URL');
$i4go[ 'auth' ] [ 'tsys_i4go' ] [ 'method'] = "POST";
$i4go[ 'auth' ] [ 'tsys_i4go' ] [ 'timeout'] = lZ;
$i4go[ 'auth' ] [ 'tsys_i4go' ] ['proxy' J = false;
$i4go[ 'auth' ]['tsys_i4go' J['credential_on_file'] = false;

// REQUIRED for TSYS i4go
//$i4go['auth' ]['tsys_i4go' ]['headers' ] -
// array('Content-Type: application/xml');
//
//$i4go['auth' ]( 'tsys_i4go' ]['processors'] =
// $processors;
//
$i4go['auth' ] [ 'tsys_i4go' ] [ 'response_codes' ] =
array ( "A"=>"APPROVED", , , () , ,=> , , UNKNOWN, , ) ;
?>

<?PHP
//
// auth. php--Vantiv_Litle
$i4go( 'auth' ] [ 'vantiv_litle' ] [ 'url' ]-
getenv('I4GO_VANTIV LITLE_URL');
$i4go [ 'auth' ] [ 'vantiv_litle' ] [ 'method' ] "POST";
$i4go('auth' ]( 'vantiv_litle' ] [ 'timeout'] - 12;
$i4go( 'auth' ] [ 'vantiv_litle' ] [ 'proxy'] - true;

// REQUIRED for Vantiv
// $i4go[ 'auth' ] [ 'vantiv_litle' ] ( 'headers' ] -
// array('Content-Type: application/xml');
//
// $i4go [ 'auth' ] [ 'vantiv_litle' ] ( 'processors' ]
$processors;
//
$i4go[ 'auth' ]['vantiv_litle' ][ 'response_codes' ] =
array ( "A"=>"APPROVED", ''=>"UNKNOWN");
$i4go('auth' ] [ 'vantiv_litle' ] ['credential_on_file']
false;
?>

/opt/local/www/apache22/data/i4go_new/new/auth.php.

<?PHP
//
// auth.php--CardConnect

$i4go[ 'auth' ]['cardconnect' ]['url'] -
getenv( ' I4GO_CARD_CONNECT_URL' ) ;
$i4go[ 'auth' ]['cardconnect' ] ['method' ] = "POST";
$14go[ 'auth' ] [ 'cardconnect' ] [ 'timeout'] = 12;
$i4go['auth' ]['cardconnect' ]( 'proxy'] = false;
$i4go[ 'auth' ]['cardconnect' ] [ 'response_codes' ] =
array ( "A"=>"APPROVED", "B"=>"TRY _AGAIN",
"C"=>"HOST _ DOWN", ""=>"UNKNOWN");
$i4go['auth' ] [ 'cardconnect' ] ['credential_on_file']
false;
?>

<?PHP
//
// auth. php--Heartland
$i4go[ 'auth' ] [ 'heartland' ] [ 'url' ]
getenv ( ' I4GO_HEARTLAND_URL' ) ;
$i4go[ 'auth' ] [ 'heartland' ] [ 'method' ] = "POST";
$14go[ 'auth' ] [ 'heartland' ] [ 'timeout' ] - 12;
$i4go('auth' ] [ 'heartland' ] [ 'proxy'] = false;
$i4go[ 'auth' ] [ 'heartland' ] [ 'response_codes' ] =
array ( " 85 "=>"APPROVED", ••=>"UNKNOWN");
$i4go[ 'auth' ] [ 'heartland' ] [ 'credential_on_file' ]
false;
?>

20.     Exhibit 20         Email Chain between A.      UNDER SEAL
                          Shotwell and M. Mauer re:
                          Merchant Pricing (Sept. 23,
                          2016)

                          Bates Nos.:
                          CC-SHFT4-00032241 –
                          CC-SHFT4-00032242

47. Exhibit 47 Email Chain between A. UNDER SEAL
Shotwell and R. Sanford re:
“Shift4 API” (May 31, 2017 –
June 6, 2017)

               Bates Nos.:
               CC-SHFT4-00029366 –
               CC-SHFT4-00029367

58.  Exhibit 56    Email from Ryan Smith to Chris           REDACTED
                   Doyle, Drew Soffera, and Others,
                   Subject: “Fwd: CardConnect” (Sept.
                   24, 2015 10:25 PM)

                   Bates No.:
                   SHIFT4-CC_0019704

19 Exhibit 17 Excerpted Source Code for routes/api.php

<?php

use Illuminate\Http\Request;
use Illuminate\Support\Facades\Route;

/*
|--------------------------------------------------------------------------
| API Routes
|--------------------------------------------------------------------------
|
| Here is where you can register API routes for your application. These
| routes are loaded by the RouteServiceProvider within a group which
| is assigned the "api" middleware group. Enjoy building your API!
|
*/

Route::middleware('auth:api')->get('/user', function (Request $request) {
    return $request->user();
});

Route::post('register', 'API\RegisterController@register');
Route::post('login', 'API\RegisterController@login');

Route::group(['middleware' => 'auth:api'], function(){
    Route::post('details', 'API\RegisterController@details');
    Route::get('logout', 'API\RegisterController@logout');
});

Route::resource('products','API\ProductController');

Route::group(['middleware' => 'auth:api'], function(){
Route::resource('posts','API\PostController');
});

From:
Sent:
To:
Cc:
Subject:

Attachments:

Importance:

All:

Shotwell, Angelo
Friday, September 23, 2016 2:46 PM
Mauer, Michael
Sanford, Ryan; McWeeney, Pat; Thompson, Jeffrey; Rebraca, Dejan
RE: Merchant Pricing

High

Please see the chart below that shows all Durbin regulated debit interchange rates (and I added the base credit
interchange as well). The goal here being to show Shift4 that CardConnect's actual cost is per item +

05% for
ALL Durbin Regulated Debit transactions. For traditional interchange plus pricing, CardConnect charges some
merchants, for example + 15 bps and 5 cents per item; therefore, on all Durbin regulated debit CardConnect
would only make approximately 10 bps.

Visa

Durbin Regulated Debit

.05%+220

MasterCard

.05%+220

.05% +21¢

Discover
Base Credit
1.51% + 100

Per Item Fee
$0.22
$0.22
$0.22
$0.10 Inter./
Assessments
.05%
.05%
.05%
1. 51%

From what Rob and Mike are telling me, they are not concemed with the details in the chart as this would all be
considered proprietary info to CardConnect and First Data. I believe the main concem that they have right now is
understanding how the draft agreement can be worded as to protect them from the following scenario:

•
•
.

CardConnect adds a new feature to the gateway that has costs associated (for example, 3D Secure which
they are currently working and would cost them 5 cent per auth).
Shift4 passes these costs on to the merchants (in this case, the extra 5 cents per auth).
The merchant complains and CardConnect instructs Shift4 to turn off the feature for that merchant to

•

•

•

prevent that specific cost and Shift4 does so
Months later, Shift4 notifies CardConnect that they had not been paying that extra fee for the period. of
time that the feature was on (in this case, the additional 5 cents for 3D Secure authentication).
They feel that specific language needs to be added that can resolve that type of a scenario of us having
to credit a merchant for erroneous billing and then having to go back to CardConnect to be made whole
from the time the feature was turned on to when it was turned off.

Let me if you would like to jump on a call to review this in more detail.

Thanks,

Angelo

From:
Sent:
To:
Subject:

Mauer, Michaal
Friday, September 23, 2016 3:12 PM
Shotwel, Angelo
RE: Merchant Pricing

Angelo - yes, please give me a call to discuss.

Mike Mauer | Chief Information Officer
SHIFT4 PAYMENTS | 2100 West Liberty Road | Allentown, PA 18104
P: 702.597.2480 (ext. 43106) | F: 702.597.2489

This email and any files transmitted with it are confidential and intended solely for the use of the indirvidual or entity to whom
they are addressed. If you are not the named addressee you should not disseminate, distribute. copy or alter this email. Any
views or opinions presented in this email are solely those of the author and might not represent those of Shift4 Corporation,
Inc. and/or Its subsidlarles ("Shift47'). Warning: Although Shift4 has taken reasonable precautions to ensure no viruses are
present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or
attachments.

From:
Sent:
To:
Subject:

Shotwell, Angelo
Wednesday, May 31, 2017 8:36 AM
Sanford, Ryan
Shift4 API

Are you available to jump on a call to review the questions that I have regarding the DO integration?

Thanks,

Angelo

From: Sanford, Ryan
Sent: Wednesday, May 31, 2017 9:37 AM
To: Shotwell, Angelo
Cc: Thompson, Jeffrey; McWeeney, Pat; Rebraca, Dejan
Subject: RE: Shift4 API
Sure. Can you send the questions over and loop in whomever else is working this integration, that way we’ll have a
written record of everything.
Thanks.

CONFIDENTIALITY NOTICE
This message (including any attachments) contains information that may be confidential and/or legally privileged. If
you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this
message, of the use of any information contained herein, is strictly prohibited. If you have received this message in
error, please notify the sender and immediately delete this message and all copies from your computer.

From:
Sent:
To:
Cc:
Subject:

Shotwell, Angelo
Wednesday, May 31, 2017 1:26 PM
Sanford, Ryan
Thompson, Jeffrey; McWeeney, Pat; Rebraca, Dejan
RE: Shift4 API

Sure thing.

When performing a sale transaction, the currency code that is being sent with each request is "USD". Is there a way
to change this to a different currency code such as "CAD"? I am unable to locate it in the 4Go.DO documentation.
2. How do we add the PO Number field to the i4Go virtual terminal?
3. For EMV transactions, what are the specific parameters that DO needs to populate and retum to Shift4? In
addition, if the customer already has a device definition created with CardConnect for UTG, how can we get
the keys added to the device definition if the device is not going to be on-site for a live injection?
4. Is there any specific P2PE information that Shift4 can provide (such as a P2PE Implementation Manual)?
5. What web service does Shift4 utilize to send merchant boarding information from DO to Shift4?
6. Are there any other integration documents available that we do not have yet?
7. I know that we first discussed utilizing the hosted payment page that Shift4 has; however, is there an option to
send raw card data (PAN, Exp, CVV) to i4Go without having to utilize an iframe?
8. I know that we do not handle AMEX transactions at this time; therefore, will the system automatically reject all
AMEX transaction or is there a way to specify which card types are allowed (just Visa/MC/Discover)?
9. Is there any way to get reporting details (transactions, batches, chargebacks, etc.)?

Thanks,

Angelo

From: Sanford, Ryan
Sent: Friday, June 02, 2017 11:34 AM
To: Shotwell, Angelo
Cc: Thompson, Jeffrey; McWeeney, Pat; Rebraca, Dejan; Doyle, Chris; Mauer, Michael
Subject: RE: Shift4 API
Angelo,
Here are some answers, see below in-line.

CONFIDENTIALITY NOTICE
This message (Including any attachments) contains information that may be confidential and/or legally privileged. If
you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this
message, or the use of any information contained herein, is strictly prohibited. If you have received this message in
error, please notify the sender and immediately delete this message and all copies from your computer.

From: Shotwell, Angelo
Sent: Wednesday, May 31, 2017 1:26 PM
To: Sanford, Ryan
Cc: Thompson, Jeffrey; McWeeney, Pat; Rebraca, Dejan
Subject: RE: Shift4 API

Sure thing.

1. When performing a sale transaction, the currency code that is being sent with each request is "USD". Is
there a way
to change this to a different currency code such as "CAD"? I am unable to locate it in the 4Go.DO
documentation.
[RS] I have to contirm with our development team if this can be specified at the transaction level, versus what is set
on the account itself. I'll let you know once I have the answer.
2. How do we add the PO Number field to the i4Go virtual terminal?
[RS] It needs to be enabled under the account settings. I would enable this for you, but | am not sure which account
you are using to test.
3. For EMV transactions, what are the specific parameters that DO needs to populate and return to Shift4? In
addition, if the customer already has a device definition created with CardConnect for UTG, how can we get
the keys added to the device definition if the device is not going to be on-site for a live injection?
[RS] This is all handled through the UTG, so as long as the device is communicating with UTG, Shift4 will be able to
retrieve these values. The UTG will respond to the /f4go/call with the appropriate values to send Shift4, and store
the KSN for subsequent transactions (we also get this from our device record as well). As for changing the keys, as
long as you have a method of loading the new keys into UTG, you should be fine.
4. Is there any specific P2PE information that Shift4 can provide (such as a P2PE Implementation Manual)?
[RS] Since CardConnect is already P2PE validated, there should already be a PIM in your possession.
5. What web service does Shift4 utilize to send merchant boarding information from DO to Shift4?
[RS] We receive it via a proprietary method.
6. Are there any other integration documents available that we do not have yet?
[RS] I believe we have sent you everything that is needed. Do you have any specific questions or concerns that we
can address?
7. Iknow that we first discussed utilizing the hosted payment page that Shift4 has; however, is there an option to
send raw card data (PAN, Exp, CVV) to i4Go without having to utilize an iframe?

8.

9.

[RS] Yes, you can send the data via a server-side call, but as you know this introduces additional PCI concerns that
you will have to account for.
I know that we do not handle AMEX transactions at this time; therefore, will the system automatically reject all
AMEX transaction or is there a way to specify which card types are allowed (just Visa/MC/Discover)?
[RS] We can disable those card types at the account level for you, if needed.
Is there any way to get reporting details (transactions, batches, chargebacks, etc.)?
[RS] All transactional data would need to come directly through 41-ink, or via our Lighthouse Transaction Manager
website.

I will let you know once I have an answer on #1.

Thanks.
Ryan Sanford | Project Manager
SHIFT IZ | 2100 West Liberty Road | Allentown, PA 18104
(: 702.5972480 (ext 43070) | F: 702.597.2489

From: Shotwell, Angelo
Sent: Tuesday, June 06, 2017 10:08 AM
To: Sanford, Ryan
Cc: Thompson, Jeffrey; McWeeney, Pat; Rebraca, Dejan; Doyle, Chris; Mauer, Michael
Subject: RE: Shift4 API

Thanks for providing these answers. Just waiting on confirmation if a currency code other than "USD" is able to be
passed per transaction.

In addition, is there a different web services URL that we should be using to test the merchant boarding process?
The current URL we have been trying produces and error:
https://api.4go.com/14go/deal

From:
Sent:
Subject:

Ryan Smith
Thursday, September 24, 2015 10:25 PM
Fwd: CardConnect

Begin forwarded message:

From: Jared Isaacman <jisaacman@shift4.com>
Date: September 24, 2015 at 9:51:25 PM EDT
To: Taylor Vaughan <tvaughan@first-american.net>
Cc: "J.D. Oder" <jisaacman@shift4.com>,"Sam M. Boyer"
<SMBoyer@first-american.net>, Ryan Smith <rsmith@shift4.com>
Subject: Re: CardConnect.

Taylor

Understand

It would add 8 cents to our cost. It would also add 12 cents to

revenue.
Sent from my iPhone
On Sep 24, 2015, at 9:50 PM, Taylor Vaughan <tvaughan@first-american.net> wrote:

Jared

Card connect just came in.
$1.9M in Amex.
They want 5¢ and 30 bps over.
My thoughts are to tell them, yes but
need to mark up all transactions 4¢.

What are your thoughts?

.

Sent from my iPhone

Route::get('/reports/batch-detail/{id}', 'ReportsController@batchDetail');

Route::get('/', function () {
    return view('welcome');
});

Auth::routes(['verify' => true]);
Route::get('/home', 'HomeController@index')->middleware('verified');
Route::get('/get/download-file/{file_name}', 'FilesController@getFIle')->name('get.file.name');
Route::get('/reports/agent-activity-report',
'ReportsController@agentActivityReportView')->name('agent_activity_report_view');
Route::post('/reports/agent-activity-report',
'ReportsController@agentActivityReport')->name('agent_activity_report');

```

From: J. David Oder [mailto:jdo@shift4.com]
Sent: Friday, June 30, 2017 4:54 PM
To: Randy Oder <rkoder@yahoo.com>
Cc: Taylor Oder <taylor.oder@gmail.com>
Subject: Re:

Yea. Fuck em.

J. David Oder
Chief Executive Officer
SHIFT4 PAYMENTS

On Jun 30, 2017, at 4:50 PM, Randy Oder <rkoder@yahoo.com> wrote:

They called again today and said they were turning lawyers loose on you.

Sent from my iPhone