Skip to content

fix(DF-832): source GOV.UK Pay email from CYA confirmation field#376

Merged
mokhld merged 1 commit intomainfrom
feat/df-832-pay-v2-2
Apr 28, 2026
Merged

fix(DF-832): source GOV.UK Pay email from CYA confirmation field#376
mokhld merged 1 commit intomainfrom
feat/df-832-pay-v2-2

Conversation

@mokhld
Copy link
Copy Markdown
Contributor

@mokhld mokhld commented Apr 28, 2026

Proposed change

DF-832 requires the email pre-populated on GOV.UK Pay to come from the CYA confirmation email field, not a designer-configured form question. This change reads state.userConfirmationEmailAddress instead of state[options.emailField].

Jira ticket:

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Misc. (documentation, build updates, etc)

Checklist

  • You have executed this code locally and it performs as expected.
  • You have added tests to verify your code works.
  • You have added code comments and JSDoc, where appropriate.
  • There is no commented-out code.
  • You have added developer docs in `README.md` and `docs/*` (where appropriate, e.g. new features).
  • The tests are passing (`npm run test`).
  • The linting checks are passing (`npm run lint`).
  • The code has been formatted (`npm run format`).

…-832)

DF-832 requires the email pre-populated on GOV.UK Pay to be the
confirmation email the user provides on the CYA page, not a
designer-configured form question. Drop the options.emailField
lookup and read state.userConfirmationEmailAddress instead.
@mokhld mokhld changed the title fix(payment): source GOV.UK Pay email from CYA confirmation field (DF-832) fix(DF-832): source GOV.UK Pay email from CYA confirmation field Apr 28, 2026
@sonarqubecloud
Copy link
Copy Markdown

@mokhld mokhld merged commit 0d7e455 into main Apr 28, 2026
47 of 48 checks passed
@mokhld mokhld deleted the feat/df-832-pay-v2-2 branch April 28, 2026 15:37
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.

3 participants