> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.aurasos.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.aurasos.com/_mcp/server.

# Customer signup

AURA can host the customer onboarding flow for you. You create a signup session,
redirect the customer to an AURA-hosted URL where they enter their details and
pay, and AURA returns them to you with the outcome — no onboarding UI to build
yourself.

## The signup journey

1. **Create a session** — call [Create a signup session](/api-reference/customer-sessions/create-customer-signup-session)
   with a `returnUrl` and a customer identifier (`email` or your
   `customerReferenceId`).
2. **AURA returns an onboarding URL** — a secure, session-specific link.
3. **Present the URL** — open it in the customer's browser, or embed it in your
   app with a WebView for a seamless in-app experience.
4. **The customer completes onboarding** — personal and contact details, payment
   to activate a subscription, and optionally adding Fixed Locations.
5. **AURA redirects to your `returnUrl`** with the outcome as query parameters.

## Confirming the outcome

Treat the redirect's query parameters as a **hint**, and confirm the actual
outcome from your backend with
[Retrieve a signup session](/api-reference/customer-sessions/get-customer-signup-session) —
it returns the session's `customerId`, your `customerReferenceId`, the
configured `flows` (e.g. `payment`, `auth`, `download`), and any `siteDetails`.
That call is the source of truth regardless of how the customer left the hosted
flow (completed, abandoned, or navigated away).

```
https://your-app.example.com/signup-complete?...   →   GET /panic-api/v2/customer-signup/sessions/{sessionId}
```

## Embedding

See [Embedded flows](/overview/embedded-flows/overview) for the shared
embedding pattern and sample starter project.

To manage a subscription afterwards, keep the `customerId` returned during
signup, then use the subscription endpoints or a
[subscription-management session](/overview/embedded-flows/subscription-management-flow).

## In the API Reference

* [Create a signup session](/api-reference/customer-sessions/create-customer-signup-session)
* [Retrieve a signup session](/api-reference/customer-sessions/get-customer-signup-session)