Skip to content

[Payment due @shubham1206agra] Restore last-four SSN for USD beneficial owners - #102019

Merged
aldo-expensify merged 4 commits into
mainfrom
maxence/fix-usd-ubo-ssn-contract
Sep 24, 2026
Merged

aldo-expensify merged 4 commits into
mainfrom
maxence/fix-usd-ubo-ssn-contract

Conversation

@madmax330

Copy link
Copy Markdown
Contributor

Explanation of Change

Restores the ssnLast4 contract for beneficial owners in the USD verified bank account flow. The full-SSN contract for US-national beneficial owners in the Non-USD/Corpay flow is unchanged.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/681996
PROPOSAL:

Tests

  1. Start a USD verified bank account setup and add a beneficial owner.
  2. Verify the SSN screen requests and validates only the last four digits.
  3. Continue to the confirmation screen and verify it displays Last 4 of SSN.
  4. Submit the beneficial-owner step and verify UpdateBeneficialOwnersForBankAccount sends ssnLast4, not ssn.
  5. Start a Non-USD bank account setup with a US-national beneficial owner.
  6. Verify the flow still requests and submits the full nine-digit SSN.
  7. Ran npm run lint-changed, npm run spell-changed, and npm run react-compiler-compliance-check check-changed successfully.
  8. npm test -- --runTestsByPath tests/unit/ReimbursementAccountBeneficialOwnerSSNTest.ts --silent could not execute because the local installation is missing declared dependency @legendapp/list/react-native.
  9. npm run typecheck has unrelated pre-existing chart, LegendList dependency, and Expensify Card errors; it reports no errors in changed files.
  • Verify that no errors appear in the JS console

Offline tests

  1. Disable the network before entering the USD beneficial owner's last four SSN digits.
  2. Verify the form accepts and preserves the draft value offline.
  3. Re-enable the network and submit the beneficial-owner step.
  4. Verify the request sends ssnLast4.

QA Steps

Same as tests.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms
  • I verified there are no console errors
  • I followed proper code patterns
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained why the code was doing something instead of only explaining what it was doing
  • I added unit tests for this bug fix

Screenshots/Videos

Not applicable. This restores the previous USD beneficial-owner SSN UI.

@madmax330
madmax330 requested review from a team as code owners September 23, 2026 09:42
@melvin-bot
melvin-bot Bot requested review from dylanexpensify and shubham1206agra and removed request for a team and dylanexpensify September 23, 2026 09:42
@melvin-bot

melvin-bot Bot commented Sep 23, 2026

Copy link
Copy Markdown

@shubham1206agra Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team September 23, 2026 09:42

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c8f1a2fd58

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/CONST/index.ts Outdated
LEGAL_NAME: 'legal-name',
DATE_OF_BIRTH: 'date-of-birth',
SSN: 'ssn',
SSN_LAST_4: 'ssnLast4',

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the existing SSN subpage route

For an open or bookmarked USD setup URL whose subpage is ssn, changing the route value to ssnLast4 makes it unknown to useSubPage; findPageIndex() then falls back to index 0, displaying the legal-name screen rather than the SSN screen. Keep the established 'ssn' route value independently of changing the form-data field to ssnLast4 so in-progress navigation survives deployment.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 0520ed4 - retained the existing ssn subpage route while keeping the data field named ssnLast4.

-- AI Maxence

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index fddce43e..5a6edc57 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -4282,7 +4282,7 @@ ${amount} für ${merchant} – ${date}`,
         legalFirstName: 'Rechtlicher Vorname',
         legalLastName: 'Rechtlicher Nachname',
         enterTheDateOfBirthOfTheOwner: 'Wie lautet das Geburtsdatum des Eigentümers?',
-        enterTheSSN: 'Wie lauten die letzten 4 Ziffern der Sozialversicherungsnummer des Inhabers?',
+        enterTheSSN: 'Wie lauten die letzten 4 Ziffern der Sozialversicherungsnummer der Inhaberin oder des Inhabers?',
         dontWorry: 'Keine Sorge, wir führen keine persönlichen Bonitätsprüfungen durch!',
         enterTheOwnersAddress: 'Wie lautet die Adresse des Eigentümers?',
         letsDoubleCheck: 'Lass uns noch einmal überprüfen, ob alles richtig aussieht.',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index eece61c9..12da94a1 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -4339,7 +4339,7 @@ ${amount} για ${merchant} - ${date}`,
         legalFirstName: 'Επίσημο μικρό όνομα',
         legalLastName: 'Επώνυμο (όπως αναγράφεται στα επίσημα έγγραφα)',
         enterTheDateOfBirthOfTheOwner: 'Ποια είναι η ημερομηνία γέννησης του κατόχου;',
-        enterTheSSN: 'Ποια είναι τα τελευταία 4 ψηφία του Αριθμού Κοινωνικής Ασφάλισης του ιδιοκτήτη;',
+        enterTheSSN: 'Ποια είναι τα τελευταία 4 ψηφία του αριθμού κοινωνικής ασφάλισης του κατόχου;',
         dontWorry: 'Μην ανησυχείτε, δεν κάνουμε κανέναν προσωπικό έλεγχο πιστοληπτικής ικανότητας!',
         enterTheOwnersAddress: 'Ποια είναι η διεύθυνση του ιδιοκτήτη;',
         letsDoubleCheck: 'Ας ελέγξουμε διπλά ότι όλα φαίνονται σωστά.',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index f0220880..0f9497db 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -4206,7 +4206,7 @@ ${amount} para ${merchant} - ${date}`,
         legalFirstName: 'Nombre legal',
         legalLastName: 'Apellidos legales',
         enterTheDateOfBirthOfTheOwner: '¿Cuál es la fecha de nacimiento del dueño?',
-        enterTheSSN: '¿Cuáles son los últimos 4 dígitos del número de la Seguridad Social del propietario?',
+        enterTheSSN: '¿Cuáles son los últimos 4 dígitos del número de Seguro Social del propietario?',
         dontWorry: 'No te preocupes, ¡no realizamos verificaciones de crédito personales!',
         enterTheOwnersAddress: '¿Cuál es la dirección del dueño?',
         letsDoubleCheck: 'Vamos a verificar que todo esté correcto.',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 0a0eba04..d3a04a9c 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -4291,7 +4291,7 @@ ${amount} pour ${merchant} - ${date}`,
         legalFirstName: 'Prénom légal',
         legalLastName: 'Nom de famille légal',
         enterTheDateOfBirthOfTheOwner: 'Quelle est la date de naissance du responsable ?',
-        enterTheSSN: 'Quels sont les 4 derniers chiffres du numéro de sécurité sociale du propriétaire ?',
+        enterTheSSN: 'Quels sont les 4 derniers chiffres du numéro de Sécurité sociale du responsable ?',
         dontWorry: 'Ne vous inquiétez pas, nous ne faisons aucun contrôle de crédit personnel !',
         enterTheOwnersAddress: 'Quelle est l’adresse du responsable ?',
         letsDoubleCheck: 'Vérifions une dernière fois que tout est correct.',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 008d3a36..6c3b45c7 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -4262,7 +4262,7 @@ ${amount} per ${merchant} - ${date}`,
         legalFirstName: 'Nome legale di battesimo',
         legalLastName: 'Cognome legale',
         enterTheDateOfBirthOfTheOwner: 'Qual è la data di nascita del titolare?',
-        enterTheSSN: 'Quali sono le ultime 4 cifre del codice di previdenza sociale del titolare?',
+        enterTheSSN: 'Quali sono le ultime 4 cifre del numero di previdenza sociale del titolare?',
         dontWorry: 'Non preoccuparti, non effettuiamo alcun controllo del credito personale!',
         enterTheOwnersAddress: "Qual è l'indirizzo del proprietario?",
         letsDoubleCheck: 'Controlliamo che sia tutto a posto.',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index af17267e..0635336a 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -4230,7 +4230,7 @@ ${integrationName === CONST.ONBOARDING_ACCOUNTING_MAPPING.other ? 'あなたの'
         legalFirstName: '法的な名',
         legalLastName: '法的な姓',
         enterTheDateOfBirthOfTheOwner: '所有者の生年月日はいつですか?',
-        enterTheSSN: '所有者の社会保障番号の下4桁は何ですか?',
+        enterTheSSN: '所有者の社会保障番号の下4桁を入力してください。',
         dontWorry: 'ご安心ください。個人信用情報の審査は一切行いません。',
         enterTheOwnersAddress: 'オーナーの住所は何ですか?',
         letsDoubleCheck: 'すべて正しく表示されているか、もう一度確認しましょう。',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index c80aa341..4325be43 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -4263,7 +4263,7 @@ ${amount} voor ${merchant} - ${date}`,
         legalFirstName: 'Juridische voornaam',
         legalLastName: 'Wettelijke achternaam',
         enterTheDateOfBirthOfTheOwner: 'Wat is de geboortedatum van de eigenaar?',
-        enterTheSSN: 'Wat zijn de laatste 4 cijfers van het Amerikaanse Social Security Number (SSN) van de eigenaar?',
+        enterTheSSN: 'Wat zijn de laatste 4 cijfers van het burgerservicenummer (BSN) van de eigenaar?',
         dontWorry: 'Geen zorgen, we voeren geen persoonlijke kredietcontroles uit!',
         enterTheOwnersAddress: 'Wat is het adres van de eigenaar?',
         letsDoubleCheck: 'Laten we voor de zekerheid controleren of alles er goed uitziet.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 21c14be0..6805a566 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -4251,7 +4251,7 @@ ${amount} para ${merchant} - ${date}`,
         legalFirstName: 'Primeiro nome legal',
         legalLastName: 'Sobrenome legal',
         enterTheDateOfBirthOfTheOwner: 'Qual é a data de nascimento do proprietário?',
-        enterTheSSN: 'Quais são os últimos 4 dígitos do número de Social Security do proprietário?',
+        enterTheSSN: 'Quais são os últimos 4 dígitos do Número de Seguridade Social do proprietário?',
         dontWorry: 'Não se preocupe, não fazemos nenhuma análise de crédito pessoal!',
         enterTheOwnersAddress: 'Qual é o endereço do proprietário?',
         letsDoubleCheck: 'Vamos conferir se está tudo certo.',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 99175651..02f3f78d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -4133,7 +4133,7 @@ ${amount},商户:${merchant} - 日期:${date}`,
         legalFirstName: '法定名(名)',
         legalLastName: '法定姓氏',
         enterTheDateOfBirthOfTheOwner: '所有者的出生日期是什么?',
-        enterTheSSN: '所有者的社会安全号码后4位数字是多少?',
+        enterTheSSN: '所有者社会安全号码的后四位是多少?',
         dontWorry: '别担心,我们不会进行任何个人信用检查!',
         enterTheOwnersAddress: '所有者的地址是什么?',
         letsDoubleCheck: '让我们再仔细检查一下,确保一切都正确。',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@codecov

codecov Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 94.06% <ø> (ø)
...icialOwnerInfo/BeneficialOwnerDetailsFormPages.tsx 13.63% <ø> (ø)
...ntAccount/USD/utils/getValuesForBeneficialOwner.ts 85.71% <ø> (+85.71%) ⬆️
...t/USD/BeneficialOwnerInfo/BeneficialOwnersStep.tsx 4.93% <0.00%> (ø)
...ficialOwnerDetailsFormSubSteps/ConfirmationUBO.tsx 3.84% <0.00%> (ø)
...nerDetailsFormSubSteps/SocialSecurityNumberUBO.tsx 11.11% <16.66%> (ø)
... and 68 files with indirect coverage changes

@shubham1206agra

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-09-24.at.1.47.34.PM.mov

@melvin-bot
melvin-bot Bot requested a review from aldo-expensify September 24, 2026 08:19
@melvin-bot

melvin-bot Bot commented Sep 24, 2026

Copy link
Copy Markdown

@aldo-expensify Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot changed the title Restore last-four SSN for USD beneficial owners [Payment due @shubham1206agra] Restore last-four SSN for USD beneficial owners Sep 24, 2026
@melvin-bot

melvin-bot Bot commented Sep 24, 2026

Copy link
Copy Markdown

🎯 @shubham1206agra, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/681996.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@aldo-expensify
aldo-expensify merged commit 277f30a into main Sep 24, 2026
45 of 50 checks passed
@aldo-expensify
aldo-expensify deleted the maxence/fix-usd-ubo-ssn-contract branch September 24, 2026 18:34
@github-actions

Copy link
Copy Markdown
Contributor

🚧 aldo-expensify has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 9.4.94-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

Yes, one help article needed an update. I opened a draft PR: Docs updates for E/A#102019 USD beneficial owners enter last four SSN digits.

What changed: Connect-a-Business-Bank-Account.md said USD beneficial owners must enter the Full 9 digits of SSN. It now says they enter the last four digits in the Last 4 of SSN field.

Details
  • Left unchanged: Global-Reimbursement-Canada.md and Global-Reimbursement-United-Kingdom.md still describe the full SSN for US-citizen owners. This PR did not change the Non-USD flow.
  • Label check: I took Last 4 of SSN from personalInfoStep.last4SSN in src/languages/en.ts. This PR uses that string for the input and the confirmation row. I tried to confirm it in the browser, but the Validate your account security-code screen blocked the flow after Connect manually.
  • The draft PR has the HelpDot label and is assigned to madmax330.

@madmax330, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@izarutskaya

Copy link
Copy Markdown

@madmax330 Can you please clarify few steps?

Submit the beneficial-owner step and verify UpdateBeneficialOwnersForBankAccount sends ssnLast4, not ssn.
Ran npm run lint-changed, npm run spell-changed, and npm run react-compiler-compliance-check check-changed successfully
npm test -- --runTestsByPath tests/unit/ReimbursementAccountBeneficialOwnerSSNTest.ts --silent could not execute because the local installation is missing declared dependency @legendapp/list/react-native
npm run typecheck has unrelated pre-existing chart, LegendList dependency, and Expensify Card errors; it reports no errors in changed files

@aldo-expensify

Copy link
Copy Markdown
Contributor

@izarutskaya I think the QA/Testing steps are until step 6 (including), the rest shouldn't be there.

@izarutskaya

Copy link
Copy Markdown

@madmax330 @aldo-expensify It's passed in Web. But we can't capture the UpdateBeneficialOwnersForBankAccount request from step 4 in the Android/iOS app. Could you please check video and let me know if I can check this off? Thank you

1790521939946.bandicam_2026-09-27_18-06-30-741.mp4
WhatsApp.Video.2026-09-27.at.21.47.44.mp4

@madmax330

Copy link
Copy Markdown
Contributor Author

@izarutskaya yeah it looks like it's a pass, thanks

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.94-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@melvin-bot

melvin-bot Bot commented Sep 28, 2026

Copy link
Copy Markdown

🤖 Payment issue created: #102454

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants