> For the complete documentation index, see [llms.txt](https://api-docs.visadoc.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.visadoc.co/use-cases/basics.md).

# Basics

These patterns show how the v3 endpoints combine into a working integration. Pick one by answering two questions: **how much of the traveller journey do you want to own** vs. hand to VisaDoc, and **whose assessment decides the visa**: VisaDoc's or your own.

```mermaid
flowchart TD
  Q1{Fulfil visas, or just check eligibility?}
  Q1 -->|Check only| P1[Embedded eligibility check]
  Q1 -->|Fulfil| Q2{Keep travellers in your own UI?}
  Q2 -->|No, hand to VisaDoc| P2[Assessment-driven handoff]
  Q2 -->|Yes| Q3{Whose assessment decides?}
  Q3 -->|VisaDoc's| P3[Full white-label flow]
  Q3 -->|Your own engine| P4[Bring-your-own engine]
```

| Pattern                                                                      | Best for                     | You own                   | VisaDoc handles                        | PII through you           |
| ---------------------------------------------------------------------------- | ---------------------------- | ------------------------- | -------------------------------------- | ------------------------- |
| [Embedded eligibility check](/use-cases/embedded-eligibility-check.md)       | Booking / policy gating      | The check UI              | Visa rules                             | Trip data only            |
| [Assessment-driven handoff](/use-cases/assessment-driven-handoff.md)         | Fastest end-to-end visas     | The entry point           | Everything after handoff               | Name + email only         |
| [Full white-label flow](/use-cases/white-label-flow.md)                      | Total brand control          | The whole journey         | Verification, submission               | All, incl. documents      |
| [Bring-your-own engine](/use-cases/bring-your-own-engine.md)                 | You already have visa logic  | Routing / policy          | Execution                              | Depends on how you fulfil |
| [Background operational sync](/use-cases/background-operational-sync.md)     | Ops dashboards & closure     | Your back-office          | The case of record                     | None (read-only)          |
| [Returning-traveller fast path](/use-cases/returning-traveller-fast-path.md) | Frequent business travellers | Recognising the traveller | The traveller record and saved profile | Reused, not re-collected  |
| [Document verification service](/use-cases/document-verification-service.md) | Adding AI document checks    | Collection UI             | AI checks + cross-check                | Documents                 |

**Rule of thumb:** the more of the journey you own, the more sensitive data flows through your side, so default to **handoff** unless brand control is a hard requirement.

The last three patterns (background sync, returning-traveller fast path, and document verification) are complementary: they layer onto any of the primary patterns rather than replacing them.

Whichever pattern you pick, two pages apply to all of them: [Statuses](/statuses.md), including how to read the outcome after `Decision Made`, and [Trip changes and erasure](/trip-changes-and-erasure.md).