> For the complete documentation index, see [llms.txt](https://docs.fraudcheck.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraudcheck.co.za/product/overview/get-started/onboarding-steps.md).

# Onboarding steps

What happens from first contact to your first check.

You can open an account in one of two ways.

## Sign up yourself

1. Create an account on the [Fraudcheck onboarding portal](https://onboarding.fraudcheckonline.co.za/) and verify your email address and mobile number.
2. Complete the onboarding form with the representative, organisation, billing and intended-use information requested, and upload the supporting documents. See [What we need from you](/product/overview/get-started/requirements.md).
3. Fraudcheck reviews every application and completes the required client verification.
4. Once your application is approved, Fraudcheck emails you a link to finish setting up your account.

## Contact sales

Email <sales@fraudcheck.co.za> to discuss your use cases and the products you need. The sales team will guide you through the same onboarding and review, and the account is activated when Fraudcheck sends you the link to finish setting it up.

## Once your account is active

1. [Log in to the portal](https://portal.fraudcheckonline.co.za/login).
2. Invite team members so they can create their own user accounts. See [Users and roles](/product/administration/administration/account/users-and-roles.md).
3. Run your first check. See [Running a check](/product/administration/administration/portal/running-a-check.md).
4. To run checks from your own product, start with the [developer documentation](https://developer.fraudcheck.co.za/consumer-service).


---

# 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://docs.fraudcheck.co.za/product/overview/get-started/onboarding-steps.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.