Date: 23-04-21

Document of Test Administration report EML

Scope of this document:

- The scope of this document provide the information about the certification program,
and what will going to happen during the test execution.
- It clarifies what type of card needed and what is expected from the representative.
- Provides the contact details (UL)

UL’s Transaction security division:

UL’s transaction security division guides companies in different ways to safeguard the
security, compliance, and interoperability.

Transaction security division offers:

- Advice
- Test
- Certification services
- Security evaluation
- Test tools

For implementing the new technologies and full life cycle of our product development.

Certification process:

1. High level overview.

- Spot testing by apple

- Apple pay certification by UL.

- Testing.

- Implementation.

-Implementation options.
 - Contact with.

2. Certification process Steps:

- Project Engagement

- Preparation

- Certification

- Project closure

Project Engagement:

- Document is shared
- Provides the scope and the basic configuration of the issuer certification
- The document returned within minimum of 2 weeks prior to agreed start of
certification.

Preparation:

- It requires some preparation from the issuer for the smooth process.

1) Required preparation:

- Metadata

- Production cards

- SMS OTP and E-mail OTP

- In-App Activation and In-App provisioning.

- Readiness call

- Checklist
Certification.

1. Customer sample handling and intake

Intake test execution is the process of executing the tests step by step to obtain the actual
result that can be compared with expected result to check whether the tests passed or
failed.

-In test case which scenario going to be tested.

-Test name includes the feature to be tested.

-Objective summary determines what the expected result was.

-Verdict determines the opinion which may be pass, fail, and pass with issue, N/A.

Example,

Test case Test name Objective summary Verdict

Humm_UK_openhum Splash Activity Verify that the Pass
m humm opens with
the Splash Activity
2.Test scope and planning

-The scenarios will cover all the user interaction:

-Basic intake testing.

-initial focus on the cases that require direct require input.

-Test cases that impact the feature permanently.

-Regression testing

3. Test Administration and report

- All the progress of tests is tracked in the test administration and report.

- End of the progress the test administration report is converted into final report

4. Issue resolution

Any issues found during test case execution.

5. Failure of certification

- Change of project scope

Once the progress is completed and approved by no changes made to the issuer. Any
changes that result in different test case outcome will require a new certification (for
example)

- Major connectivity and technical issues

If during the entire progress, the system issues prevent test cases from being completed and
cannot resolved within 2 to 3 days, the progress will be cancelled.

Project closure.

Final test report:

The final stage is the final test report that will sent for the final approval, in case of
successful approval the final decision will be taken

Refunding policy:

In this refunding policy, to ensure a zero balance needed to be refunded on the used cards.

Location and timelines of the certification:

1. Needed to be agreed upon the location and timelines.

2. Alignments between issuer and the UL on the timelines and the location will be discussed
in initial meeting.

Certification information:

Prior to engaging with UL and starting the certification, the issuer will need to complete the
the following information and confirm that all necessary requirements have been met.

- Stakeholder Information

- Portfolio Information

- Functional Checklist

- Resolution Timelines

- Fraud Rules

The Mobile Pay Team:

The mobile pay team is giving solutions regarding apple pay payments. This could be
centrally organized.

Summary:

The summary determines,

-Total number of test cases passed in percentage for different types of devices.

-Percentage of executed test cases.

-Percentage of remaining test cases.

-Total number of issues.

-Comments.