> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Riwayat KYB Bisnis: Sesi & Laporan

> Ambil semua sesi KYB yang terkait entitas bisnis Didit, periksa data registri perusahaan dan hasil AML, picu verifikasi ulang, dan buat laporan kepatuhan.



Prompt Riwayat KYB
        Salin prompt ke papan klip



      
      

\<pre>

\````# Goal — read a business's full KYB history and trigger re-verification

Every KYB session is linked to the Business entity via `vendor_data`. List sessions, retrieve each decision, and create new sessions for re-KYB.

\## List every KYB session for a business

\```bash
curl -G https://verification.didit.me/v3/sessions/ \
-H "x-api-key: $DIDIT_API_KEY" \
\--data-urlencode "vendor_data=biz-acme" \
\--data-urlencode "page_size=50"
\```

KYB session payloads carry `session_kind: "business"` and `business_session_id` to distinguish them from KYC sessions.

\## Inspect a single KYB decision

\```bash
curl https://verification.didit.me/v3/session/$SESSION_ID/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
\```

KYB decisions include:

\- Company registry data (legal name, registration, status, incorporation date, addresses)
\- `key_people_checks[]` — UBOs, shareholders, directors, officers (registry-sourced and user-submitted, with role tags)
\- `aml_screenings[]` — company AML and per-person AML
\- `document_verifications[]` — uploaded docs with OCR extracts and signed image URLs

See /business-verification/response-schema for the full payload.

\## Fast path — fully verified right now?

\```bash
curl https://verification.didit.me/v3/businesses/biz-acme/ \
-H "x-api-key: $DIDIT_API_KEY"
\# data.features = { KYB: "Approved" }
\```

The Business entity's `features` map holds the latest company verification status under the `KYB` key.

\## Trigger re-KYB

Annual re-KYB or trigger-based re-checks: create a new session against the same `vendor_data`. The new session attaches to the existing Business entity.

\```bash
curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workflow_id": "wf_kyb_annual", "vendor_data": "biz-acme"}'
\```

\## Generate a KYB PDF report

\```bash
curl https://verification.didit.me/v3/session/$SESSION_ID/generate-pdf/ \
-H "x-api-key: $DIDIT_API_KEY" \
-o kyb-report.pdf
\```

PDF covers registry data, ownership structure, AML hits, document images, per-officer KYC status, questionnaires, phone verification, email verification, and IP analysis when those features are part of the workflow.

\## Resubmit vs new session

\| Scenario | Use |
\|---|---|
\| Registry needs corrected company name | Resubmit — analyst edits data and re-runs registry |
\| Additional document requested | Resubmit — business uploads the missing document |
\| Annual / trigger-based re-KYB | Create a brand new session |

\`kyb_key_people` and `kyb_registry` cannot be resubmitted directly — to re-verify a person, resubmit their child KYC session; the parent Key People feature re-aggregates automatically.

\## Share a session

\```bash
curl -X POST https://verification.didit.me/v3/session/$SESSION_ID/share/ \
-H "x-api-key: $DIDIT_API_KEY"

curl -X POST https://verification.didit.me/v3/session/import-shared/ \
-H "x-api-key: $RECEIVER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"share_token": "..."}'
\```

\## Failure modes

\- `404` — wrong `vendor_data` casing or no KYB sessions yet.
\- Stale signed image URLs — re-fetch the decision.
\- `session_kind: "user"` events in the same list — filter on `session_kind === "business"` for KYB-only handling.

\## Sources of truth

\- /business-verification/response-schema — full KYB decision payload
\- /business-verification/statuses — feature state machine
\- /entities/businesses/data-model — features map computation
\- /core-technology/reusable-kyc/overview — share / import pattern
\- /integration/integration-prompt — canonical end-to-end prompt````

\</pre>



      
      

Tempel ke

Setiap sesi Verifikasi Bisnis (KYB) yang pernah dilakukan oleh Bisnis akan tetap terhubung secara permanen dengan entitas Bisnis. Anda dapat mengambil seluruh riwayat, memeriksa data registri dan temuan AML setiap sesi, memicu verifikasi ulang, dan membuat laporan PDF untuk audit.## Menampilkan semua sesi Verifikasi Bisnis (KYB) untuk sebuah bisnisFilter daftar Sesi menurut `vendor_data`:```bash theme={null}
curl -G https://verification.didit.me/v3/sessions/ \
  -H "x-api-key: YOUR_API_KEY" \
  --data-urlencode "vendor_data=biz-acme" \
  --data-urlencode "page_size=50"
```Respons menyertakan setiap sesi Verifikasi Bisnis (KYB), terlepas dari statusnya.## Memahami fitur KYBSesi KYB menjalankan fitur-fitur berikut, dan setiap fitur memiliki statusnya sendiri dalam keputusan sesi:| Fitur | Cakupan |
| - | - |
| `KYB_REGISTRY` | Pencarian registri perusahaan: keberadaan, status, dan pencocokan silang identitas |
| `AML` | Skrining AML tingkat perusahaan (sanksi, media negatif, daftar pantauan) |
| `KYB_DOCUMENTS` | Pengumpulan dokumen dan pencocokan silang OCR |
| `KYB_KEY_PEOPLE` | Pejabat, UBO, pemilik manfaat: identifikasi dan KYC opsional |Peta `features` pada entitas bisnis hanya menyimpan status verifikasi perusahaan terbaru:```json theme={null}
"features": {
  "KYB": "Approved"
}
```Lihat [status fitur KYB](https://docs.didit.me/id/business-verification/statuses.md) untuk referensi lengkapnya.## Memeriksa satu sesi Verifikasi Bisnis (KYB)```bash theme={null}
curl https://verification.didit.me/v3/session/{session_id}/decision/ \
  -H "x-api-key: YOUR_API_KEY"
```Keputusan KYB mencakup:- Data registri perusahaan (nama hukum, nomor registrasi, status, tanggal pendirian, alamat)
- Pejabat dan UBO yang diekstrak dari registri
- Struktur kepemilikan (tabel kepemilikan saham, persentase kepemilikan oleh pemilik manfaat)
- Hasil AML perusahaan (temuan, skor)
- AML untuk setiap UBO dan pejabat
- Hasil dokumen beserta hasil ekstraksi OCR
- Kode alasan keputusanLihat [skema respons KYB](https://docs.didit.me/id/business-verification/response-schema.md) untuk payload lengkapnya.## Memicu verifikasi ulangRe-KYB tahunan, pemeriksaan ulang berbasis pemicu, atau alur remediasi semuanya dimulai dengan sesi baru:```bash theme={null}
curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "wf_kyb_annual",
    "vendor_data": "biz-acme"
  }'
```Sesi baru akan terhubung ke entitas Bisnis yang sudah ada dan memperbarui peta `features` saat selesai.## Pengajuan ulang vs sesi Verifikasi Bisnis (KYB) baru| Skenario | Gunakan |
| - | - |
| Pencarian registri memerlukan nama perusahaan yang sudah dikoreksi | Ajukan ulang: analis mengedit data dan menjalankan ulang pencarian registri |
| Dokumen tambahan diminta dari bisnis | Ajukan ulang: bisnis mengunggah dokumen yang kurang |
| Re-KYB tahunan atau berbasis pemicu | Buat sesi baru |## Mengekspor laporan KYBBuat PDF lengkap untuk sesi Verifikasi Bisnis (KYB) mana pun:```bash theme={null}
curl https://verification.didit.me/v3/session/{session_id}/generate-pdf/ \
  -H "x-api-key: YOUR_API_KEY" \
  -o kyb-report.pdf
```PDF mencakup data registri, struktur kepemilikan, temuan AML, gambar dokumen, status KYC pejabat, serta halaman sampul dengan alasan keputusan.## Membagikan sesi Verifikasi Bisnis (KYB)Untuk alur kerja konsorsium atau mitra:- `POST /v3/session/{session_id}/share/`: membuat token yang dapat dibagikan.
- `POST /v3/session/import-shared/`: mengimpor di sisi penerima.## Pemantauan berkelanjutanEntitas bisnis dalam mode pemantauan berkelanjutan menerima pemindaian ulang AML secara berkala. Ketika temuan sanksi atau media negatif baru terdeteksi, skrining AML perusahaan akan diperbarui; baca hasilnya dari `aml_screenings[]` pada keputusan sesi.Atur pemantauan berkelanjutan di konsol pada *Workflows → \[KYB workflow] → AML → Ongoing monitoring*.## Langkah selanjutnya> [card] [Ikhtisar KYB](https://docs.didit.me/id/business-verification/overview.md)
>
> Cara kerja sesi Verifikasi Bisnis (KYB) dari awal hingga akhir.> [card] [Respons KYB](https://docs.didit.me/id/business-verification/response-schema.md)
>
> Referensi lengkap payload keputusan.> [card] [Pihak kunci](https://docs.didit.me/id/entities/businesses/key-people.md)
>
> Pejabat, UBO, dan Pengguna terkait.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.