# Go-live checklist (/global/en/docs/Terminal/TestYourIntegration/Go-live-checklist)

## Test Your Integration

Validate the selected capabilities on a prepared terminal. For payment and refund, perform end-to-end testing using a real payment card.

### Startup and Terminal Configuration

| Scenario                           | Expected result                                                                                                        |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Build and deploy                   | The correct SDK and required runtime files are included for the selected platform and architecture.                    |
| Cold start                         | Platform startup completes before discovery or business entry points are used. Required host objects remain available. |
| Required permission is unavailable | The application explains the unavailable capability and allows authorization or a supported configuration change.      |
| Discover and select a terminal     | The intended terminal is selected from the available results; the request reaches that terminal.                       |
| Restart the application            | The selected strategy is restored, or the application offers the intended selection flow.                              |
| Switch or clear a terminal         | Subsequent requests follow the new selection; obsolete remembered choices do not silently route them elsewhere.        |
| Leave and reopen a screen          | SDK startup is not repeated by each screen, and callbacks reach the active consumer without updating a closed screen.  |

### Basic Test Flow

For integrations that include payment and refund, start with the following basic scenarios:

1. **Make a low-value payment** using a real card.
2. **Refund the payment** to verify your refund flow.

### Transaction Verification

If possible, verify the transaction details on the payment terminal (e.g., in the acquiring application).

Make sure that key information—such as the **transaction amount** and **reference data**—matches the response received by your integrated application.

### Additional Scenarios to Validate

To ensure the robustness of your integration, you should also verify that the following scenarios are properly handled:

- Transaction failure
- Transaction cancellation
- Network timeout
- Duplicate transaction handling
- Invalid amount / edge values

For each selected capability, verify its expected response and observable terminal behavior using the corresponding business guide and API reference. Record build checks separately from results observed on a real terminal. Use [Error Codes](doc-id:27dda32e), [FAQ](doc-id:350ba5c5), and [Developer Resources](doc-id:d38c2ed5) for diagnosis and supporting resources.