For Reference Only EMVCo Token Service Provider Code Registration Form

Complete and Submit Form Via EMVCo's Online Docusign Process

EMVCo Token Service Provider

Code Registration Request

New, Renewal, Contact Information Change

Introduction
A Token Service Provider Code (TSP Code) is a 3 digit code assigned to Token Service Provider
(TSP) and maintained by EMVCo.
The TSP Code is included in the Token Requester ID which uniquely identifies the pairing of Token
Requester with the Token Service Provider. This helps achieve transparency of the entity that provided
the Payment Token.
A TSP Code is unique to each Token Service Provider, even those that support multiple unaffiliated
Card Issuers.
Please refer to the document EMV Payment Tokenisation Specification Technical Framework
Version 1.0 (Tokenisation Specification) for further details and definitions of certain terms.

Submission Process
This form should be completed in full and submitted via EMVCos online Docusign process
(questions to tspcode@emvco.com).

Prerequisites
The request for obtaining a TSP Code allocated by EMVCo shall meet the following criteria:
TSP Code Registrant is a company, or a significant division of a parent company, which must be
engaged in, or demonstrating intent to be engaged in, EMV Token Services relating to the role a
TSP as detailed in the Tokenisation Specification and highlighted on the Registration Form. This
includes national or regional representative organisations for these entities. If the qualification
applies to a division of a larger organisation, then the TSP Code Registrant must be from the
qualifying division.
TSP Code Registrant must demonstrate that they have direct ownership of a Token BIN or Token
BIN Range for EMV Token Services or demonstrate they have or will have the consent of Card
Issuers or BIN Controller / Manager of a Token BIN or Token BIN Range.
The TSP Code Registrant must have a financial or contractual obligation related to support EMV
Payment Tokenisation as described in the Tokenisation Specification (EMV Payment
Tokenisation) and is currently providing a developed (or otherwise owns) and commercially
released service in which it provides EMV Payment Tokens to registered Token Requesters (TSP
Service).

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Publication
The TSP Codes will be publicly published and maintained by EMVCo and are accessible from the
EMVCo website. Information will be published in two separate ways: an HTML-based table and a
downloadable Letter of Registration. A sample table is below, and a sample Letter of Registration can
be found in Appendix A of this document. This sample table is for illustration only; the actual
publication may vary in content and/or format. The Letter of Registration will be publicly published,
but the published version will not include Attachment A.

Sample HTML based Table Publication Sample

TSP Provider Company A
TSP Company Address, City, Country

Contact: TSPCompany@TSPCompany.com, Telephone: +123 45 67856

TSP Registration Framework Version Renewal Date Letter of

Code Number Registration

NNN TSP NNNNN EMV Payment Tokenisation Specification Technical 22-Oct-2016

Framework 1.0

NNN TSP NNNNN EMV Payment Tokenisation Specification Technical 05-Jul-2017

Framework 1.0

Fee Structure
The Registration Fee charged by EMVCo is intended to cover the administrative expense incurred by
EMVCo in managing the TSP Code registration process. This process includes, but is not limited to:
Review of registration and applicant criteria.
Updates to the TSP Code registration process.
Maintenance of the TSP Code list.
Publication of the current TSP Code list.

The following registration fee shall be paid to EMVCo by the applicant:

$10,000 (Ten Thousand USD) for reviewing the initial application and issuing the TSP Code.
The fee is non-refundable except in limited circumstances.

An annual renewal fee will apply for each assigned TSP Code:
$2,500 (Two Thousand Five Hundred USD) for renewal per annum; effective one year from
the registration date or last renewal date.
Failure to pay the renewal fee will result in EMVCo revoking the assigned TSP Code.

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Note: Payers are responsible for any bank charges associated with remittance. Each Token Service
Provider must work with its bank to ensure that EMVCo receives the full amount of the fee. The
Request for Registration will not be reviewed until complete payment has been received.

Change in Contact Information

The applicant shall inform EMVCo if the company name, address or contact information
changes.
EMVCo may reissue an existing Letter of Registration on explicit request as a result of company name
change, address change or contact information change.

Disclaimer
Issuance of a TSP Code may not be sufficient for an applicant TSP to provide its TSP Service. The
applicant TSP needs to work with Card Issuers and potentially Payment Networks to ascertain
additional program and participation requirements.

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Registration Process

Complete TSP Code Submit Agreement and

Registration Form and Form via Docusign process. EMVCo invoices the
Agreement Process on (Questions to applicant
EMVCo website tspcode@emvco.com)

EMVCo reviews and Payment NO

performs the Registration remitted to
Request YES EMVCo
YES

Applicant
revises and NO EMVCo
resubmits the Assigns the
Registration TSP Code
Form

NO YES

EMVCo publishes LoR and

Registration Declined
Registration Number

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Renewal Process

EMVCo informs
Registrant of
impending
renewal

EMVCo invoices
Registrant

NO YES
Payment
remitted

EMVCo revokes EMVCo updates

the assigned TSP TSP Code list
Code
with renewal date

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

EMVCo Token Service Provider

Code Registration Request

New, Renewal, Contact Information Change

A.1 To be Completed by Applicant

Please return the completed and signed form via DocuSign. Submit questions to tspcode@emvco.com.

Date: XXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXX
We hereby request registration of ________________________________________________
("Organisation") with EMVCo, in order to obtain a Token Service Provider Code. For all
correspondence between EMVCo and our Organisation please utilise the contact name and
information below.

Sincerely,

Name: XXXXXXXXXXXXXXXXXX ____________

Title: ____________

Date: ____________

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

All yellow fields are mandatory and must be completed.

I. Contact Information

Organisation Information

Organisation Name1 XXXXXXXXXXXXXXXXX

Address1 XXXXXXXXXXXXXXXXXXXXXX

Postal Code1 XXXXXXXXXXXXX City1 XXXXXXXXX

Country1 XXXXXXXXXXXXX

Main Contact

First Name XXXXXXXXXXXXX Last Name XXXXXXXXX

Email1 2 XXXXXXXXXXXX

Phone1 Fax

Invoicing Details

Invoicing contact is the same as the main contact

All invoices shall be sent to the following contact:

First Name Last Name

Email

Phone Fax

Invoicing address is the same as above

All invoices shall be issued using the following details:

1 This information may be included in future EMVCo publications and on the EMVCo website.
2 Many important communications with EMVCo will be done by email. Please make sure that you provide correct

email addresses and that your firewall does not block emails coming from EMVCo. All email notifications sent from

EMVCo will be sent to the main contact email address, copying the concerned additional contact email addresses.

Invoices will be sent to the main contact email address.

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Organisation Name XXXXXXXXXXXXXXXX

Address

Postal Code City

Country

Additional Contact

First Name Last Name

Email

Phone Fax

Business Information

This form is for a:

New Registration Renewal

Contact Information Change

If a TSP Code is already assigned, please specify:

Is your organisation a 3:

- Financial Institution Yes No

- Payment System Yes No

- Other (please specify)

Provide authorising BIN

Controller / Manager
Date Signature

3 This information may be included in future EMVCo publications and on the EMVCo website.

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

II. TSP Self-Assessment

Attest that the TSP to be registered implements Token Service Provider services as defined in section 5,
6 and 7 of the EMV Payment Tokenisation Specification Technical Framework.

# Assessment Items Answer by Applicant

1 Operate a Token Vault Yes No
2 Manage 3rd party Token Requestor Registration? Yes No
3 Issue and provision Tokens from BIN(s)? Yes No
4 Manage ID&V and Token Assurance? Yes No
5 Manage Domain Control Validation? Yes No
6 Perform Token Lifecycle Management? Yes No
7 Support De-tokenisation Interface? Yes No
8 TSP acting on behalf of a 3rd Party Yes No

If the answer by the applicant TSP is no for any of the above assessment items please provide further
details below:

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

A.2 To be completed by EMVCo

Registration Number

Assigned TSP Code

Date Signature

(End of the form)

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Appendix A: Sample Letter of Registration

Date: 1 June 2016

TSP Contact Name

TSP Company Address
TSP City, TSP Postal Code, TSP Country

Re: EMVCo Letter of Registration Token Service Provider

Code
Registration Number: TSP NNNNN
Approval Date:
Registration Expiration Date:

Organisation Name: TSP Company A

TSP Code: NNN
Organisation Type Financial Institution

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code Registration Form

Dear TSP Registration Contact,

EMVCo, LLC ("EMVCo"), a Delaware limited liability company, has received your
request for TSP Code assignment for the above referenced service. In connection with your
EMVCo Token Service Provider Code Registration Request dated May 12, 2014 attached hereto
as Attachment A, we have reviewed the self attestation that your Organisation implements Token
Service Provider services as defined in section 5, 6 and 7 of the EMV Payment Tokenisation
Specification Technical Framework.
EMVCo hereby (a) grants your EMVCo Token Service Provider Code Registration
request approval, based on the self attestation that your Organisation implements Token Service
Provider services as defined in section 5, 6 and 7 of the EMV Payment Tokenisation Specification
Technical Framework, and (b) issues to your Organisation the TSP Code specified above.
This Letter of Registration is subject to the terms of the EMVCo Token Service Provider
Code Registration Agreement between EMVCo and your Organisation.

This Letter of Registration is valid while the registration number is posted on the EMVCo
website.

EMVCo Token Service Provider Code Registration Form, version 1.1, May 2016
 EMVCo Token Service Provider Code
Registration Agreement
(FOR REFERENCE ONLY; COMPLETE AND SUBMIT AGREEMENT
VIA EMVCOS ONLINE DOCUSIGN PROCESS)

This EMVCo Token Service Provider Code Registration Agreement (Agreement) is

made and entered into as of ___________________ (Effective Date), between EMVCo, LLC
(EMVCo), a Delaware limited liability company, and ________________________________
________________________________ (Service Provider), a company organised under the
laws of __________________________, with its principal place of business at _____________
_____________________________________________________________________________
(each, a Party, and collectively, the Parties).

RECITALS

A. The EMV Payment Tokenisation Specification Technical Framework defines a

framework for EMV Payment Tokenisation in which a Token Service Provider code is assigned
to a token service provider to facilitate its issuance of payment tokens to registered Token
Requestors.

B. EMVCo issues token service provider codes to token service providers whose
service complies with the EMV Payment Tokenisation Specification Technical Framework.
EMVCo also maintains a publicly accessible registry of such issued token service provider
codes.

C. Service Provider intends to support payment tokenisation by serving as a token

service provider as described in the EMV Payment Tokenisation Specification Technical
Framework 1.0. Service Provider seeks to have EMVCo issue a token service provider code to
Service Provider and maintain such token service provider code in EMVCos publicly accessible
registry.

AGREEMENT

Therefore, the Parties agree as follows:

1. Definitions

Listing has the meaning set forth in Section 3.

Tokenisation Specification means the EMV Payment Tokenisation Specification

Technical Framework 1.0.

Registration Form has the meaning set forth in Section 2.2.

Registry means a publicly accessible database published and maintained by EMVCo

on a website, or by other means, with information regarding TSP Codes issued by EMVCo to
entities that registered with EMVCo.

127376546.3
 TSP Code means a token service provider code issued to a token service provider by
EMVCo for use as described in the Tokenisation Specification.

TSP Service means a service provided by a token service provider involving the
issuance of payment tokens and other activities of a Token Service Provider as described in the
Tokenisation Specification.

2. Registration Process

2.1 Eligibility.

Service Provider represents and warrants to EMVCo that it meets all of the prerequisite
criteria set forth in the Registration Form, including without limitation that (a) Service Provider
intends to support payment tokenisation as described in the Tokenisation Specification by
providing a TSP Service and (b) Service Provider has commercially released a TSP Service.

2.2 Registration

Service Provider acknowledges that any information it provides to EMVCo in any

registration form or request or other materials submitted to obtain a TSP Code (Registration
Form) is non-confidential. Service Provider represents and warrants that all information it
provides to EMVCo during the registration process (including in any Registration Form) is
accurate, current and complete. Service Provider will promptly notify EMVCo in writing of any
changes to such information.

2.3 Review Processes

EMVCos review of Service Providers request for the issuance of a TSP Code is subject
to EMVCos receipt of a complete Registration Form and all applicable Registration Fees from
Service Provider. Subject to Service Providers compliance with this Agreement, EMVCo may,
in its sole discretion, either issue a unique TSP Code to Service Provider or reject Service
Providers request. If EMVCo rejects Service Providers request, EMVCo will either (a) notify
Service Provider of the reasons of the rejection and allow Service Provider to revise and
resubmit the Registration Forms, or (b) terminate this Agreement as provided in Section 5.2.1
and refund all Registration Fees paid by Service Provider to EMVCo.

3. TSP Code Issuance and Registry

If EMVCo issues a TSP Code to Service Provider, EMVCo will (a) notify Service
Provider of the TSP Code and (b) list the TSP Code, Service Providers name and contact
information, and, in EMVCos discretion, other Service Provider information that EMVCo
generally makes available for TSP Codes in the Registry (collectively, a Listing) in the
Registry throughout the Term (as defined below). As long as the TSP Code is issued by EMVCo
to Provider, Service Provider may state to third parties that the TSP Code is registered with
EMVCo for Service Providers TSP Service. Service Provider will not suggest or imply to any
third party that EMVCo has evaluated, approved, certified or otherwise endorsed Service

-2-
127376546.3
Provider or its TSP Service. EMVCo will use reasonable efforts to update Service Providers
name or contact information in the Listing within five (5) business days after receiving notice of
change requests. Service Provider acknowledges that EMVCo does not guarantee and cannot
ensure that the TSP Code issued by EMVCo will not be used by third parties for other TSP
Services. Upon termination of this Agreement, EMVCo may remove the Listing from the
Registry.

4. Fees

Service Provider agrees to pay EMVCo the fees described on the Registration Form or
otherwise communicated to Service Provider in writing from time to time (Registration Fees)
in accordance with the payment terms set forth in such Registration Form or other written
communication. Except as specifically provided in this Agreement, all Registration Fees are
nonrefundable. EMVCo reserves the right, in its sole discretion, to modify the Registration Fees
at any time by giving notice of such modifications to Service Provider. For purposes of this
Section 4, such notice to Service Provider may be in written or electronic form, including e-mail
or by posting of notice on the EMVCo website. Any change in the Registration Fees will apply
to each Renewal Term (as defined below) commencing after the effective date of such change.

5. Term; Termination; Survival

5.1 Term

The term of this Agreement will commence on the Effective Date and will continue for
an initial term ending one (1) year after the first date on which EMVCo issues a TSP Code to
Service Provider (Initial Term). Thereafter, the term of this Agreement will automatically
renew for one or more successive one (1) year periods (each, a Renewal Term, and the Initial
Term together with all Renewal Terms, the Term) unless (a) either Party gives written notice
of nonrenewal at least thirty (30) days before the commencement of a Renewal Term, or
(b) EMVCo increases the Registration Fees within thirty (30) days before the commencement of
a Renewal Term and Service Provider provides written notice of nonrenewal to EMVCo before
such Renewal Term.

5.2 Termination

5.2.1 Termination Before Issuance of Registry ID

EMVCo may terminate this Agreement at any time before the issuance of a Registry ID,
effective immediately upon written notice to Service Provider. Upon EMVCos termination of
this Agreement under this Section 5.2.1, EMVCo will refund to Service Provider all of the
Registration Fees paid by Service Provider.

5.2.2 Termination Without Cause

EMVCo may terminate this Agreement at any time during the Initial Term or any
Renewal Term without cause by providing written notice to Service Provider at least thirty (30)

-3-
127376546.3
days before the effective date of such termination. Upon EMVCos termination of this
agreement under this Section 5.2.2, EMVCo will refund to Service Provider a portion of the
Registration Fees paid by Service Provider proportional to the remaining number of days in the
then-current Initial Term or Renewal Term, as applicable.

5.2.3 Termination With Cause

Either Party may terminate this Agreement upon fifteen (15) days written notice of a
material breach of this Agreement to the other Party, if such breach is not reasonably cured
within such fifteen (15) day period. Notwithstanding the foregoing, EMVCo may terminate this
Agreement immediately, upon written notice, for breach of Section 4 or 6.

5.3 Survival

The rights and obligations contained in Sections6, 7, 8, 9 and 10 of this Agreement will
survive termination of this Agreement.

6. Representations and Warranties

Service Provider represents and warrants that (a) it possesses full power and authority to
enter into this Agreement and to perform its obligations hereunder, (b) its performance of the
terms of this Agreement will not breach any separate agreement by which it is bound, and
(c) upon execution, this Agreement will be a legal, valid and binding obligation of Service
Provider.

7. Disclaimer of Warranties

EMVCO MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE TSP

CODES, LISTINGS, REGISTRY, OR THE REGISTRATION AND REVIEW PROCESSES
UNDER WHICH SUCH TSP CODES ARE ISSUED. IN PARTICULAR, EMVCO
EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES OF MERCHANTABILITY,
SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND
NONINFRINGEMENT.

UNDER NO CIRCUMSTANCES SHOULD EMVCOS ISSUANCE OF A TSP CODE,

PUBLICATION OF LISTINGS OR MAINTENANCE OF THE REGISTRY BE CONSTRUED
TO IMPLY ANY ENDORSEMENT OR WARRANTY REGARDING THE
FUNCTIONALITY, QUALITY OR PERFORMANCE OF ANY PARTICULAR PRODUCT
OR SERVICE OF SERVICE PROVIDER, AND SERVICE PROVIDER WILL NOT STATE
OR IMPLY ANYTHING TO THE CONTRARY. EMVCO SPECIFICALLY DISCLAIMS
ANY AND ALL REPRESENTATIONS AND WARRANTIES WITH RESPECT TO SERVICE
PROVIDERS PRODUCTS AND SERVICES, INCLUDING, WITHOUT LIMITATION, ANY
IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NONINFRINGEMENT.

-4-
127376546.3
 In addition, Service Provider acknowledges that it has no expectation and has received no
assurances that any investment by Service Provider in a TSP Code will be recovered or
recouped, or that Service Provider will obtain any anticipated amount of revenue or profits by
virtue of this Agreement.

8. Limitation of Liability

8.1 Generally

IN NO EVENT WILL EMVCO BE LIABLE TO SERVICE PROVIDER FOR ANY

INCIDENTAL, SPECIAL, INDIRECT, CONSEQUENTIAL, OR PUNITIVE DAMAGES
(INCLUDING WITHOUT LIMITATION DAMAGES ARISING FROM LOSS OF
GOODWILL, PROSPECTIVE PROFITS OR ANTICIPATED INCOME, OR LOSSES ON
ACCOUNT OF ANY EXPENDITURES, INVESTMENTS, LEASES, OR COMMITMENTS
MADE BY SERVICE PROVIDER) ARISING OUT OF OR RELATING TO THIS
AGREEMENT, INCLUDING WITHOUT LIMITATION EMVCOS REGISTRATION OR
REVIEW PROCESSES, THE REGISTRY AND ANY LISTINGS, EMVCOS DECISION TO
ISSUE, OR NOT ISSUE, A TSP CODE, AND THE TERMINATION OF THIS AGREEMENT
FOR ANY REASON. FURTHER, IN NO EVENT WILL EMVCOS AGGREGATE
LIABILITY TO SERVICE PROVIDER UNDER THIS AGREEMENT EXCEED THE
AMOUNTS PAID BY SERVICE PROVIDER TO EMVCO IN THE TWELVE (12) MONTH
PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM. THE
FOREGOING LIMITATIONS APPLY TO CAUSES OF ACTION OF ANY KIND,
WHETHER ARISING IN TORT (INCLUDING NEGLIGENCE), CONTRACT OR
OTHERWISE, EVEN IF EMVCO HAS BEEN INFORMED IN ADVANCE OF THE
POSSIBILITY OF SUCH DAMAGES OR LOSSES.

8.2 Material Inducement

Service Provider understands and acknowledges that Section 8.1 has been included as a
material inducement for EMVCo to enter into this Agreement, and that EMVCo would not have
entered into this Agreement but for the limitations of liability as set forth in Section 8.1.

9. Indemnification

Service Provider agrees to defend, indemnify and hold harmless EMVCo and its
members and their affiliates against any and all damages, costs, liabilities, expenses and
settlement amounts (including reasonable attorneys fees) incurred in connection with any suit,
claim or action by any third party, except to the extent arising from EMVCos willful
misconduct, arising out of or relating to (a) Service Providers TSP Service; (b) Service
Providers use, distribution or marketing of the TSP Code or a TSP Service; or (c) any claims of
EMVCos implied endorsement or negligent selection or approval of Registrant resulting from
EMVCos issuance of the TSP Code or EMVCos operation of the Registry.

-5-
127376546.3
10. General Provisions

10.1 Entire Agreement

This Agreement, and all documentation incorporated by reference, completely and

exclusively states the Agreement of the Parties regarding its subject matter. It supersedes, and its
terms govern, all prior or contemporaneous proposals, agreements or other communications
between the Parties, oral or written, regarding such subject matter.

10.2 Amendments

Except as otherwise stated in this Agreement, this Agreement may be amended only in a
writing manually signed by all the Parties.

10.3 Relationship of Parties

Nothing in this Agreement will be deemed to create a joint venture, partnership, or

agency relationship between the Parties. Neither Party has the right or authority to assume or
create any obligation or responsibility on behalf of the other.

10.4 Assignment

This Agreement may not be assigned by Service Provider without the prior written
approval of EMVCo, which approval may be withheld by EMVCo for any reason; provided that
no consent is required in the case of Service Providers merger, consolidation, reorganisation,
reincorporation, dissolution or sale of all or substantially all of its assets so long as the surviving
or successor entity specifically assumes all of Service Providers obligations under this
Agreement. EMVCo may freely assign this Agreement without the prior written consent of
Service Provider.

10.5 Successors and Assigns

This Agreement will be binding on and inure to the benefit of the Parties and their
respective successors and permitted assigns.

10.6 Notices

Except as otherwise stated in this Agreement, any notices required or permitted by this
Agreement will be in writing and sent by electronic mail to the email address specified below the
receiving Partys signature to this Agreement, or to such other email address as a Party may
specify by sending notice to the other Party in accordance with this sentence.

-6-
127376546.3
 10.7 Severability

If any provision of this Agreement or portion thereof should be declared invalid for any
reason, the invalid provision or portion thereof will be deemed omitted and the remaining terms
will nevertheless be carried into effect.

10.8 Waivers

The waiver by either Party of a breach of any provisions contained herein will be in
writing and will in no way be construed as a waiver of any succeeding breach of such provision
or the waiver of the provision itself.

10.9 Attorneys Fees

In the event of a dispute between the Parties regarding the enforcement or interpretation
of any terms of this Agreement, the non-prevailing Party will pay the reasonable costs and
attorneys fees of the prevailing Party, including the reasonable costs and attorneys fees incurred
in the appeal of any final or interlocutory judgment.

10.10 Rights and Remedies

The rights and remedies provided by this Agreement are cumulative and the use of any
one right or remedy will not preclude or waive the right to use any or all other remedies. These
rights and remedies are given in addition to any other rights the Parties may have by law, statute,
ordinance or otherwise.

10.11 Governing Law; Jurisdiction

This Agreement will be governed by and construed in accordance with the laws of the
state of Delaware, without regard to the choice of law provisions of the state of Delaware or any
other jurisdiction. Each Party to this Agreement consents to the exclusive jurisdiction and venue
of the state and federal courts within the state of Delaware.

-7-
127376546.3
 The Parties have executed this EMVCo Token Service Provider Code Registration
Agreement as of the Effective Date.

EMVCO: EMVCO, LLC

By:
Name:
Title:
Email for notices: emvcolegal@emvco.com

SERVICE PROVIDER:

By:
Name:
Title:
Email for notices:

-8-
127376546.3