---
feature: Driver account completion (profile)
slug: profile
surface: delivery
consumer: flutter
version: 1.0.3
status: ready (scoped delivery)
brd_version: "1.3"
brd_ids: [DRIV-006, DRIV-002]
business_rules: [BR-03, BR-04, BR-08]
decisions: [DEC-25, TD-01, TD-14, TD-19, TD-44, TD-45, TD-56, TD-57, TD-62, TD-63, TD-65, TD-66, TD-67, TD-69, TD-72, TD-76, TD-77]
schema_tables: [drivers, driver_districts, payout_accounts, governorates, regions, users, media]
screens: []   # DRIV-006 profile screens are not captured (PROJECT_BRAIN "— (not captured)")
related_docs: [onboarding.md, auth.md, ../provider/profile.md, ../admin/drivers.md]
last_updated: 2026-11-10
---

# Driver account completion — Flutter Integration Guide (delivery)

> **Base URL:** `{HOST}/api/v1/delivery` · Shared rules (headers, envelope,
> errors, pagination, Dio setup): [API_CONVENTIONS.md](../API_CONVENTIONS.md) · **Scoped delivery:** city, districts, photo, birth date, nationality and payout account completed from the account (SCR-19). Vehicle, identity and document changes are pending (§11); DEC-25 remains open.

## Version history

Newest first. Never edit an old row.

| Version | Date | Type | Summary | App action required |
|---------|------|------|---------|---------------------|
| 1.0.3 | 2026-11-10 | PATCH | Docs only: changing a saved restricted value after approval now has its own flow, the reviewed change request ([profile-change-requests.md](profile-change-requests.md), TD-184, DEC-25 resolved). The direct edits in this guide are unchanged: they still answer 409 `PROFILE_CHANGE_REVIEW_REQUIRED`. | When a restricted field is locked, open the change-request form instead of showing "change through support" (once the change-request endpoints are announced as deployed). |
| 1.0.2 | 2026-11-02 | PATCH | A payout account an admin `rejected` while refusing a transfer request (DEC-11, TD-158) can be replaced by `POST /profile/payout-account` in any account status, including approved. | None: the old 409 does not apply to a rejected account; its `status` reads `rejected`. |
| 1.0.1 | 2026-10-26 | PATCH | Documentation only: validation 422 examples and rows now show `data.errors` (`{field: [messages]}`, TD-02, API_CONVENTIONS 2.7.0) instead of `data: null`; examples are the captured Postman responses. | None. |
| 1.0.0 | 2026-10-22 | Initial scoped release | Work area, photo, personal details and payout account: first set is direct in any status; changing a saved value after approval is 409 (TD-76/77). | Integrate as described below. |

## Changelog

### 1.0.2 — 2026-11-02

- **Changed:** `POST /profile/payout-account` treats a `rejected` primary account as not effective: replacing it is direct in every account status. Any other saved account follows the rules below. Postman: `delivery.payout-account.store` › "201 Rejected payout account replaced after approval".
- **Breaking:** No. **App action required:** None.

### 1.0.1 — 2026-10-26

- **Added:** N/A.
- **Changed:** Validation 422 examples and error-table rows show `data.errors`, not `data: null` (TD-02).
- **Fixed:** Documentation only; the server already returned `data.errors`.
- **Removed / Deprecated:** N/A.
- **Breaking:** No.
- **Endpoints affected:** None (documentation).
- **App action required:** None; map `data.errors` onto form fields, fall back to `message`.
- **BRD / decisions:** TD-02.

### 1.0.0 — 2026-10-22
- **Added:** `GET`/`PUT /profile/work-area`, `PUT /profile/photo`, `GET`/`PUT /profile/personal`, `GET`/`POST /profile/payout-account`; error code `PROFILE_CHANGE_REVIEW_REQUIRED` (409).
- **Changed:** —
- **Fixed:** —
- **Removed / Deprecated:** —
- **Breaking:** No
- **Endpoints affected:** the seven routes in §3.
- **App action required:** build the completion forms; prefill from the GETs; disable fields in `locked_fields`; hide the bank form when `can_edit` is false; refresh `GET /onboarding` after each save.
- **BRD / decisions:** DRIV-006, DRIV-002, AC-DRIV-006, SCR-19/26, BR-04/08, TD-45, TD-62, TD-65, TD-76, TD-77; DEC-25 resolved (TD-184).

---

## 1. Business summary

At registration the driver sends only her name, national ID, vehicle and three documents (SCR-19). Before she can go online she completes her city, work districts, photo, birth date, nationality and bank account from the account; each item leaves `missing_for_activation` in `GET /onboarding` once saved. Setting a value for the first time saves directly in any account status. Changing a saved value after approval needs a reviewed change request ([profile-change-requests.md](profile-change-requests.md), TD-184): the direct edit here still answers 409 and the approved data stays in force until an admin approves the request (BR-04, TD-76). The photo is always a direct edit (DRIV-006).

## 2. User flow and screens

DRIV-006 profile screens are not captured yet; the steps below follow the SCR-19 activation checklist.

| Step | Screen / widget | Endpoint | Notes (states, empty, loading, errors) |
|------|-----------------|----------|-----------------------------------------|
| 1 | Activation checklist | `GET /onboarding` | `missing_for_activation` lists `city`, `districts`, `photo`, `birth_date`, `nationality`, `payout_account`, `account_status`. Each item opens its form. |
| 2 | Work area form | `GET` / `PUT /profile/work-area` | Prefill city and districts. Disable inputs in `locked_fields`. Use the shared geo lists for choices. |
| 3 | Photo picker | Shared `POST /api/v1/media` (collection=image), then `PUT /profile/photo` | Send the returned hash; null removes. |
| 4 | Personal details form | `GET` / `PUT /profile/personal` | Date picker (before today) and nationality text. Disable inputs in `locked_fields`. |
| 5 | Bank account | `GET` / `POST /profile/payout-account` | No account → form. Saved → masked IBAN + status; when `can_edit` is false open the change-request form ([profile-change-requests.md](profile-change-requests.md)). |

Show a loading state for the GETs and explicit save success/error. After a 409, reload the GET so the form shows the saved (approved) values.

## 3. Endpoints

All ids are UUID strings. Send `Accept: application/json`, `Authorization: Bearer …` (driver-app token) and `Accept-Language: ar|en`. No `X-City` or `Idempotency-Key`. Every route works in any account status (approval not required) while the user is active; customer- or provider-app tokens get 403. Responses are private/no-store.

### 3.1 Read work area

`GET /api/v1/delivery/profile/work-area`

No query or body fields. Returns the saved city, districts (sorted by name) and `locked_fields` (§4).

Success — **200** ([captured](../postman-collection.json) (Postman: `delivery.work-area.show` › "200 Saved city and districts")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "city": {
      "id": "01a1631f-d9ad-7005-aba0-595497709473",
      "name": "Sample-utai10063746"
    },
    "districts": [
      {
        "id": "01a1631f-d9b2-71c7-a5ff-999b57000ffd",
        "name": "Sample-vghe71883581"
      }
    ],
    "locked_fields": [
      "city_id",
      "district_ids"
    ]
  }
}
```

### 3.2 Save work area

`PUT /api/v1/delivery/profile/work-area`

All keys optional; omitted keys keep their saved value. Response = §3.1.

| Field | Validation | Behavior |
|-------|------------|----------|
| city_id | uuid of `governorates` (BRD city); not null when sent | Must be enabled. Changing it leaves saved districts in place, so send the new `district_ids` too or you get 422. |
| district_ids | array (list), may be empty | Replaces the whole saved list; `[]` clears it. |
| district_ids.* | uuid of `regions` (BRD district), distinct | Each enabled and belonging to the resulting city (BR-08). |

First set vs change (TD-76):

| Account status | City change | Districts change |
|----------------|-------------|------------------|
| incomplete / needs_changes / rejected | direct | direct |
| pending_review | 409 `INVALID_STATE_TRANSITION` (TD-62) | direct |
| approved / suspended | 409 `PROFILE_CHANGE_REVIEW_REQUIRED` | 409 `PROFILE_CHANGE_REVIEW_REQUIRED` |

Re-sending the saved value is not a change. A refused change writes nothing.

Success — **200**, approved driver, first-time set ([captured](../postman-collection.json) (Postman: `delivery.work-area.update` › "200 Approved driver sets city and districts for the first time")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "city": {
      "id": "01a1631f-d9ad-7005-aba0-595497709473",
      "name": "Sample-utai10063746"
    },
    "districts": [
      {
        "id": "01a1631f-d9b2-71c7-a5ff-999b57000ffd",
        "name": "Sample-vghe71883581"
      }
    ],
    "locked_fields": [
      "city_id",
      "district_ids"
    ]
  }
}
```

Error — **409**, changing saved districts after approval ([captured](../postman-collection.json) (Postman: `delivery.work-area.update` › "409 Changing approved districts needs review")):

```json
{
  "status": "fail",
  "message": "Changing Districts after approval needs an admin-reviewed change request. Please send a change request from your account.",
  "data": {
    "error_code": "PROFILE_CHANGE_REVIEW_REQUIRED",
    "correlation_id": "83d78ba4-3c4f-49e5-9c8c-f36a78d0bd91"
  }
}
```

Error — **409**, city change during review ([captured](../postman-collection.json) (Postman: `delivery.work-area.update` › "409 Driver city cannot change during review")):

```json
{
  "status": "fail",
  "message": "City cannot be changed while your account is under review.",
  "data": {
    "error_code": "INVALID_STATE_TRANSITION",
    "correlation_id": "c334c22f-20df-4fcb-bd2a-d7461a3b7de9"
  }
}
```

Error — **422**, district of another city ([captured](../postman-collection.json) (Postman: `delivery.work-area.update` › "422 Driver district belongs to another city")); `data.context` appears only in debug environments:

```json
{
  "status": "fail",
  "message": "The selected district does not belong to this city.",
  "data": {
    "error_code": "BUSINESS_RULE_VIOLATED",
    "context": {
      "violations": [
        "The selected district does not belong to this city."
      ]
    },
    "correlation_id": "b39899be-5d3a-40cd-8711-e1c82ef9c9e3"
  }
}
```

Error — **422**, inactive district ([captured](../postman-collection.json) (Postman: `delivery.work-area.update` › "422 Driver district is inactive")); an inactive city gives the same code:

```json
{
  "status": "fail",
  "message": "Service is unavailable in this city or district. Please choose another service area.",
  "data": {
    "error_code": "SERVICE_AREA_UNAVAILABLE",
    "correlation_id": "3061cb18-9556-4acf-9583-4fee76a8d109"
  }
}
```

Other captured errors: [city change after approval](../postman-collection.json) (Postman: `delivery.work-area.update` › "409 Changing the approved driver city needs review") (409), [city sent as an integer id](../postman-collection.json) (Postman: `delivery.work-area.update` › "422 City sent as an integer id") (422 validation). Districts without a city also return 422 `BUSINESS_RULE_VIOLATED` ("Choose a city before selecting districts.").

### 3.3 Save profile photo

`PUT /api/v1/delivery/profile/photo`

| Field | Validation | Behavior |
|-------|------------|----------|
| photo | required key; null or string max 255 | Hash of a fresh image you uploaded with `POST /api/v1/media` (jpg/jpeg/png/webp, max 2048 KiB, users.image). `null` removes the photo. Always direct. |

`has_photo` tells whether a real photo is saved (`photo` is a placeholder URL otherwise).

Success — **200** ([captured](../postman-collection.json) (Postman: `delivery.photo.update` › "200 Driver sets her profile photo")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "photo": "http://localhost/storage/images/77f71d52-513b-4ee1-a50b-4ef8c2c4efcd.png",
    "has_photo": true
  }
}
```

Errors: [hash uploaded by someone else](../postman-collection.json) (Postman: `delivery.photo.update` › "422 Driver photo hash uploaded by someone else") (422 `BUSINESS_RULE_VIOLATED`; also attached, missing, non-image or oversized files), [photo key missing](../postman-collection.json) (Postman: `delivery.photo.update` › "422 Driver photo key missing") (422 validation).

### 3.4 Read personal details

`GET /api/v1/delivery/profile/personal`

No query or body fields. Success — **200** ([captured](../postman-collection.json) (Postman: `delivery.personal.show` › "200 Personal details not set yet")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "birth_date": null,
    "nationality": null,
    "locked_fields": []
  }
}
```

### 3.5 Save personal details

`PUT /api/v1/delivery/profile/personal`

All keys optional; omitted keys keep their value, explicit null clears (a change).

| Field | Validation | Behavior |
|-------|------------|----------|
| birth_date | null or `Y-m-d`, before today | Date of birth. |
| nationality | null or string max 60 | Free text; blank counts as empty. |

First set is direct in any status. Changing a saved value while approved or suspended → 409 `PROFILE_CHANGE_REVIEW_REQUIRED`; other statuses (including pending_review) change directly.

Success — **200**, approved driver, first-time set ([captured](../postman-collection.json) (Postman: `delivery.personal.update` › "200 Approved driver sets birth date and nationality for the first time")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "birth_date": "1995-04-12",
    "nationality": "Saudi",
    "locked_fields": [
      "birth_date",
      "nationality"
    ]
  }
}
```

Error — **409**, changing approved nationality ([captured](../postman-collection.json) (Postman: `delivery.personal.update` › "409 Changing approved nationality needs review")):

```json
{
  "status": "fail",
  "message": "Changing Nationality after approval needs an admin-reviewed change request. Please send a change request from your account.",
  "data": {
    "error_code": "PROFILE_CHANGE_REVIEW_REQUIRED",
    "correlation_id": "507e93d8-6b41-4826-92e7-757188145209"
  }
}
```

Other captured errors: [clearing approved birth date](../postman-collection.json) (Postman: `delivery.personal.update` › "409 Clearing approved birth date needs review") (409), [future birth date and too-long nationality](../postman-collection.json) (Postman: `delivery.personal.update` › "422 Future birth date and too-long nationality") (422 validation).

### 3.6 Read payout account

`GET /api/v1/delivery/profile/payout-account`

Returns the primary account that is not inactive, or `payout_account: null`. The IBAN is always masked to the last four (TD-45). `can_edit` is false when a saved account cannot be replaced now (approved, suspended or pending_review).

Success — **200** ([captured](../postman-collection.json) (Postman: `delivery.payout-account.show` › "200 Saved driver payout account with masked IBAN")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "payout_account": {
      "id": "01a1631f-d9fa-71c1-a9f7-b4bd7c54370f",
      "holder_name": "Sara",
      "bank_name": "Al Rajhi Bank",
      "iban": "****7519",
      "status": {
        "value": "pending",
        "label": "Pending"
      },
      "created_at": "2026-10-22T10:19:54+00:00"
    },
    "can_edit": false
  }
}
```

### 3.7 Add payout account

`POST /api/v1/delivery/profile/payout-account`

| Field | Validation | Behavior |
|-------|------------|----------|
| holder_name | required string max 150 | Account holder name. |
| bank_name | required string max 100 | Bank name. |
| iban | required, regex `^SA[0-9A-Z]{22}$` | Capital letters, no spaces (schema ck_pa_iban). No checksum check; the admin verifies. |

Creates a primary account with status `pending`. The first account is always direct. A `rejected` account (an admin refused it with a transfer request, DEC-11) is always replaceable. Replacing another one is direct only in incomplete / needs_changes / rejected (the old row becomes `inactive`, kept as history); pending_review → 409 `INVALID_STATE_TRANSITION`; approved / suspended → 409 `PROFILE_CHANGE_REVIEW_REQUIRED`.

Success — **201**, approved driver, first account ([captured](../postman-collection.json) (Postman: `delivery.payout-account.store` › "201 Approved driver adds her first payout account")):

```json
{
  "status": "success",
  "message": "",
  "data": {
    "payout_account": {
      "id": "01a1631f-d9fa-71c1-a9f7-b4bd7c54370f",
      "holder_name": "Sara",
      "bank_name": "Al Rajhi Bank",
      "iban": "****7519",
      "status": {
        "value": "pending",
        "label": "Pending"
      },
      "created_at": "2026-10-22T10:19:54+00:00"
    },
    "can_edit": false
  }
}
```

Error — **409**, replacing after approval ([captured](../postman-collection.json) (Postman: `delivery.payout-account.store` › "409 Replacing the approved driver payout account needs review")):

```json
{
  "status": "fail",
  "message": "Changing Payout account after approval needs an admin-reviewed change request. Please send a change request from your account.",
  "data": {
    "error_code": "PROFILE_CHANGE_REVIEW_REQUIRED",
    "correlation_id": "2c186417-0058-45b6-b9f9-4d9c53fb331f"
  }
}
```

Error — **422**, bad IBAN ([captured](../postman-collection.json) (Postman: `delivery.payout-account.store` › "422 Driver IBAN is not SA plus 22 characters")):

```json
{
  "status": "fail",
  "message": "The IBAN field format is invalid.",
  "data": {
    "errors": {
      "iban": [
        "The IBAN field format is invalid."
      ]
    }
  }
}
```

Other captured errors: [change during review](../postman-collection.json) (Postman: `delivery.payout-account.store` › "409 Driver payout account cannot change during review") (409 `INVALID_STATE_TRANSITION`).

### 3.8 Errors and app behavior

| HTTP | error_code | Cause / action |
|------|------------|----------------|
| 401 | UNAUTHENTICATED | Refresh/sign in under shared auth behavior. |
| 403 | PERMISSION_DENIED / ACCOUNT_INACTIVE | Wrong app token (customer/provider) or inactive user. |
| 409 | INVALID_STATE_TRANSITION | Changing a saved city or payout account during pending_review (TD-62). Wait for the review result. |
| 409 | PROFILE_CHANGE_REVIEW_REQUIRED | Changing saved approved data (approved or suspended, BR-04/TD-76). Nothing saved; direct the driver to support and reload the form. |
| 422 | absent (`data.errors`) | Validation: bad IBAN, unpaired/invalid fields, future birth date, integer ids, missing photo key. Show each message under its field from `data.errors`. |
| 422 | BUSINESS_RULE_VIOLATED | District of another city, districts without a city, or an invalid photo upload. |
| 422 | SERVICE_AREA_UNAVAILABLE | City or district disabled. Ask for another area. |

## 4. Statuses and enums

| Enum / flag | Value | Meaning / allowed action |
|-------------|-------|--------------------------|
| locked_fields (work area) | `city_id`, `district_ids` | Saved keys whose change returns 409 now. |
| locked_fields (personal) | `birth_date`, `nationality` | Saved keys whose change returns 409 now (approved / suspended only). |
| payout_account.status | pending | Saved, waiting for admin verification. New accounts always start here. |
| payout_account.status | verified | Verified by an admin (payouts feature). |
| payout_account.status | rejected | Refused by an admin (payouts feature). |
| payout_account.status | inactive | Replaced; never returned by GET. |
| can_edit | true / false | Whether `POST /profile/payout-account` is accepted now. |
| has_photo | true / false | Whether a real photo is saved. |

Account statuses (`incomplete`, `pending_review`, `needs_changes`, `approved`, `rejected`, `suspended`) are documented in [onboarding.md](onboarding.md); they decide which changes are direct (§3.2, §3.5, §3.7).

## Data model

| Table | Read / write | Notes |
|-------|--------------|-------|
| drivers | read/write + lock | city_id, birth_date, nationality. |
| driver_districts | read/replace | Work districts; replaced as a set when it changes. |
| governorates / regions | read (shared lock) | BRD city / district; is_active and membership checked. |
| payout_accounts | read/write | owner_role=driver; primary non-inactive row; replacement marks the old row inactive. IBAN stored in full, returned masked. |
| users / media | read/write + lock | users.image collection for the photo; soft delete on replace. |

No `profile_change_requests` row is written (TD-44).

## 5. Dart models

```dart
typedef Json = Map<String, dynamic>;
class AreaRef {
  final String id;
  final String? name;
  AreaRef.fromJson(Json j) : id = j['id'] as String, name = j['name'] as String?;
}
class DriverWorkArea {
  final AreaRef? city;
  final List<AreaRef> districts;
  final List<String> lockedFields;
  DriverWorkArea.fromJson(Json j)
      : city = j['city'] == null ? null : AreaRef.fromJson(j['city'] as Json),
        districts = (j['districts'] as List).map((e) => AreaRef.fromJson(e as Json)).toList(),
        lockedFields = (j['locked_fields'] as List).cast<String>();
}
class DriverPersonal {
  final String? birthDate, nationality; // birthDate: YYYY-MM-DD
  final List<String> lockedFields;
  DriverPersonal.fromJson(Json j)
      : birthDate = j['birth_date'] as String?, nationality = j['nationality'] as String?,
        lockedFields = (j['locked_fields'] as List).cast<String>();
}
class AccountPhoto {
  final String photo;
  final bool hasPhoto;
  AccountPhoto.fromJson(Json j) : photo = j['photo'] as String, hasPhoto = j['has_photo'] as bool;
}
class PayoutAccount {
  final String id, holderName, bankName, iban; // iban is masked, e.g. ****7519
  final Json status;
  final String createdAt;
  PayoutAccount.fromJson(Json j)
      : id = j['id'] as String, holderName = j['holder_name'] as String, bankName = j['bank_name'] as String,
        iban = j['iban'] as String, status = j['status'] as Json, createdAt = j['created_at'] as String;
}
class PayoutAccountState {
  final PayoutAccount? account;
  final bool canEdit;
  PayoutAccountState.fromJson(Json j)
      : account = j['payout_account'] == null ? null : PayoutAccount.fromJson(j['payout_account'] as Json),
        canEdit = j['can_edit'] as bool;
}
```

## 6. Business rules enforced by the backend

| Rule | Backend behavior | What the app sees |
|------|------------------|-------------------|
| SCR-19 / TD-65 | Activation items are completed from the account, never at registration. | `missing_for_activation` items clear after each save. |
| TD-76 | First set is direct in any status; changing saved city/districts/personal/payout while approved or suspended is refused. | 409 `PROFILE_CHANGE_REVIEW_REQUIRED`; approved data unchanged. |
| TD-62 / TD-76 | pending_review refuses city and payout changes; districts and personal details stay direct. | 409 `INVALID_STATE_TRANSITION`. |
| BR-08 / TD-69 / TD-77 | Districts belong to the resulting city; city and districts enabled. | 422 `BUSINESS_RULE_VIOLATED` / `SERVICE_AREA_UNAVAILABLE`. |
| TD-63 / TD-72 | Photo must be your own fresh image upload within the users.image limits. | 422 `BUSINESS_RULE_VIOLATED`. |
| TD-45 | IBAN masked to the last four in every response. | `****1234`. |

## 7. Notifications and real-time events

N/A. No push, inbox or review event is sent for these edits.

## 8. Localization and UI notes

Messages and status labels follow `Accept-Language` (Arabic default). City/district names fall back to Arabic when no English name exists. The 409 message names the refused fields (e.g. "Changing Districts after approval …"); show it as-is. Nationality is free text, not translated.

## 9. Integration checklist

- [ ] Drive the completion screens from `GET /onboarding` → `missing_for_activation`; refresh it after each save.
- [ ] Prefill every form from its GET after an app restart.
- [ ] Send `district_ids` with any city change.
- [ ] Upload the photo first; send the hash, never a URL.
- [ ] Disable inputs listed in `locked_fields`; hide the bank form when `can_edit` is false.
- [ ] Handle 409 `PROFILE_CHANGE_REVIEW_REQUIRED` (support) and 409 `INVALID_STATE_TRANSITION` (under review); reload after either.
- [ ] Show only the masked IBAN after saving.
- [ ] Use the driver-app token; other app tokens get 403.

## 10. Acceptance scenarios

| AC ID | Scenario | Expected |
|-------|----------|----------|
| AC-DRIV-006 | Approved driver sets city, districts, photo, birth date, nationality and payout for the first time. | 200/201; `missing_for_activation` becomes empty. |
| AC-DRIV-006 | Approved driver changes saved city, districts, nationality, clears birth date, replaces payout. | 409 `PROFILE_CHANGE_REVIEW_REQUIRED`; data unchanged, no change-request row; re-sending saved values is 200. |
| AC-DRIV-006 | pending_review: city/payout change vs districts/personal change. | 409 `INVALID_STATE_TRANSITION` / 200. |
| AC-DRIV-006 | District of another city; inactive district. | 422 `BUSINESS_RULE_VIOLATED` / `SERVICE_AREA_UNAVAILABLE`; nothing saved. |
| AC-DRIV-006 | Bad IBAN; masking; future birth date; foreign photo hash. | 422; `****` + last four only; 422; 422. |
| AC-DRIV-006 | Customer- or provider-app token of the same person. | 403 on every route; 401 without a token. |

Tests: `tests/Feature/Api/V1/Delivery/ProfileTest.php` (MySQL `joshen_testing`); real responses in `docs/postman-collection.json` (saved responses of `delivery.{work-area,photo,personal,payout-account}.*`).

## 11. Open decisions and known limitations

- **DEC-25 (resolved, TD-184):** a restricted value changes through the reviewed change request ([profile-change-requests.md](profile-change-requests.md)); the direct edits in this guide still return 409 after approval.
- **Pending DRIV-006 scope:** vehicle changes, ID/residency and driving-licence details, document replacement after approval, and the reviewed change-request flow. Vehicle and documents are edited only through onboarding before approval ([onboarding.md](onboarding.md)).
- Payout verification, payout cycle and history belong to the payouts feature.
- DRIV-006 screens are not captured; the flow in §2 follows SCR-19. No password flow exists (TD-01).
