# SDK installation

> The V2 SDK script tag, which versions exist, and which versioning guarantees do not exist.

- kind: guide
- status: stable
- sdk_version: v2
- last_verified: 2026-08-28
- url: https://www.tilopay.com/en/developers/sdk/instalacion

## The script [#script]

```html
<script src="https://app.tilopay.com/sdk/v2/sdk_tpay.min.js"></script>
```

Load it before your own checkout code. The SDK exposes the global `Tilopay` object.

## jQuery is not required [#jquery]

<Callout type="info">
**jQuery is NOT required.** It was a leftover from SDK V1. The article published so far
said otherwise and it is wrong: you can install SDK V2 without jQuery on the page.
</Callout>

## Versions [#versiones]

There are only two versions:

| Version | Status |
|---|---|
| `v1` | Unsupported |
| `v2` | Current |

## What does not exist [#garantias]

<Callout type="warn">
**There is no immutable versioning, no SRI hash and no changelog.** The
`/sdk/v2/sdk_tpay.min.js` URL is not pinned to a specific version: its contents can change
without prior notice and without public release notes.

Practical consequences:

- You cannot set `integrity="sha384-..."` on the `script` tag, because the file changes.
- You cannot rely on a build number to reproduce a bug.
- Keep smoke tests for your checkout running periodically, not only on deploy.
</Callout>

## What is next [#que-sigue]

- [Form fields](/developers/sdk/campos-del-formulario) — the ids the SDK looks for.
- [`Tilopay.Init()`](/developers/sdk/reference/init) — start the purchase.