# Certification

Complete certification with Tyro before enabling merchants to use your integration — this applies regardless of which integration path you use.

Certification checks that your integration is complete, reliable, provides a good user experience, and complies with card scheme requirements. It's also how Tyro's support team learns enough about your product to support your mutual merchants after go-live.

To start or progress a certification request, use our [Integration Support Portal](https://tyropayments.atlassian.net/servicedesk/customer/portal/149/group/163/create/410). Before submitting your application, please ensure you perform thorough regression testing against our test case suite. For the online PAY API and Tap to Pay, we require your application for testing.

## Certification phases

The Terminal integration for .NET and JS library will require the certification process to be completed within two phases:

**Phase one for core functionality** starts once development is complete. You'll complete a short questionnaire and submit an initial round of 5–10 test cases covering the core setup flow and initial payment scenarios. See [Testing](/docs/in-person-payments/pay-in-person/testing) for the full list of mandatory and optional test cases by feature.

**Phase two for optional features** covers the remaining test cases for whichever optional features you've implemented. Tyro confirms Phase one has passed before you move on to Phase two — the number of test cases here depends entirely on which features you've built.

## Providing evidence

Each test case needs a video recording and, where applicable, a receipt image, uploaded to the Test Case Folder your Partner Manager provisions for you. Evidence is how Tyro verifies a test case without needing to reproduce it independently, so getting the format right the first time avoids review round-trips.

**Organise videos by category.** Create one folder per transaction category (for example `Purchase`, `Refund`) rather than uploading everything into a single flat folder.

**Name each video after its test identifier**, in the form `{Vertical}.{Category}.{Outcome}.{Number}.mov` — for example:


```
Retail.Purchase.Approved.1.mov
Retail.Purchase.Declined.2.mov
Retail.Purchase.Cancelled.3.mov
Retail.Purchase.Cancelled.4.mov
```

**Name receipts after the same test identifier**, appending which copy it is — customer, merchant, or tax invoice:


```
Purchase.Approved.1-Customer+TaxInvoice.png
Purchase.Approved.1-Merchant.png
```

See [Integrated receipts](/docs/in-person-payments/pay-in-person/features/integrated-receipts) for which transactions need a merchant copy, a customer copy, or both.

## .NET library pre-certification checklist

The .NET library has one additional set of pre-certification requirements, on top of the test cases above:

* Configuration instructions Tyro's support team can use to check that a customer's POS is configured correctly.
* Your support phone number, for when a customer needs to be referred to your support line.