> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/loyalty-card/introduction/registration-flow.md).

# Registration Flow

**Standard Registration (with SMS verification):**

1. User submits registration data (POST without `code`)
2. System sends SMS verification code
3. Code stored in session as `confirmation_data`
4. User resubmits with `code` parameter
5. System validates phone and code match
6. Creates loyalty account in external system
7. Creates local LoyaltyCard record
8. Sets user attributes: `has_loyalty=true`, `verified_user=true`
9. Optionally syncs user data if `is_sync=true`

**OTP Registration (without SMS verification):**

1. User already verified via other means
2. Direct submission to `/add_loyalty_card_otp/`
3. Skips SMS verification entirely
4. Creates loyalty account and local record
5. Sets `has_loyalty=true` attribute

**Search and Link:**

1. User submits phone/email to `/search_exists_create/`
2. System queries external loyalty system
3. If account exists, creates local LoyaltyCard link
4. If not found, returns message (no account creation)


---

# 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://apidocs.akinon.com/commerce-openapis/loyalty-card/introduction/registration-flow.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.