> For the complete documentation index, see [llms.txt](https://payana-saas.gitbook.io/payana-saas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://payana-saas.gitbook.io/payana-saas-docs/panduan-karyawan/verifikasi-publik.md).

# Verifikasi Publik

Halaman `/verify` bersifat publik — siapa pun bisa memakainya untuk memverifikasi status kerja seseorang, tanpa perlu login atau punya akun Payana sama sekali.

## Cara membagikan bukti kerjamu

1. Buka halaman pengaturan (`/employee/settings`) — kartu Employment SBT-mu ditampilkan di sana sebagai tampilan utama.
2. Salin tautan verifikasi (formatnya `payana.app/verify?address=<alamat Smart Account-mu>`) atau bagikan langsung alamatmu.
3. Pihak yang perlu memverifikasi tinggal membuka tautan itu, atau memasukkan alamatmu secara manual di halaman `/verify`.

## Apa yang terlihat oleh pemverifikasi

* Nama perusahaan tempatmu bekerja
* Tanggal mulai bekerja
* Status token (aktif/terkunci sebagai bukti masih berlaku)
* Alamat otoritas HR yang menerbitkan SBT

Data pribadi seperti NIK dan nomor telepon **tidak pernah terlihat** lewat halaman ini — hanya informasi ketenagakerjaan yang memang dirancang untuk publik.

## Kenapa ini lebih cepat dari surat keterangan kerja manual

Karena datanya diambil langsung dari blockchain, tidak ada proses menunggu HR merespons konfirmasi — verifikasi terjadi instan begitu halaman dibuka. Cocok dipakai untuk pengajuan kredit, proses rekrutmen di tempat lain, atau situasi apa pun yang butuh pembuktian status kerja cepat.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://payana-saas.gitbook.io/payana-saas-docs/panduan-karyawan/verifikasi-publik.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.