STF-1906: Add phone verification inputs to minFraud

[oschwald]

Adds three optional inputs to the minFraud request billing and shipping objects: phone_verification_method (delivered_code, network, or other), phone_was_verification_successful (boolean), and phone_verification_time (RFC 3339 date-time). They describe the most recent verification of the phone number. Both objects extend the shared Address schema, so the inputs live there. Risk scoring uses the shipping phone when the billing phone is absent. The request example and the bundled spec include the new fields.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • MinFraud requests can now include optional phone-verification details: the verification method, time, and whether the latest verification succeeded. Verification methods are limited to delivered code, network, or other.
  • Verification times earlier than January 1, 1970, or more than two days in the future are ignored with a warning.
• Documentation
  • Updated billing and shipping request examples to show successful delivered-code verification.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: afa0f1fd-5767-4d89-abe7-224254323f79

📥 Commits

Reviewing files that changed from the base of the PR and between fc47b62 and 25b86c5.

📒 Files selected for processing: 3

• bundled/minfraud.yaml
• components/minfraud-request.yaml
• examples/minfraud/request.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The minFraud Address request schema now defines optional phone-verification method, timestamp, and success fields. The bundled schema and billing and shipping request examples include the corresponding fields.

Changes: MinFraud phone verification

Layer / File(s)	Summary
Phone-verification request fields components/minfraud-request.yaml, bundled/minfraud.yaml	The Address schema defines optional verification method, time, and success fields. It limits methods to three values and specifies when timestamps are ignored with a warning.
Billing and shipping examples bundled/minfraud.yaml, examples/minfraud/request.yaml	Billing and shipping examples include delivered-code verification methods, timestamps, and successful-verification values.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 25b86

The change adds optional phone-verification metadata. Different timestamps for the same number in billing and shipping are permitted as per-entry values, so no actionable merge risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: adding phone verification inputs to minFraud.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the fields with care,
Three methods hop into the schema there.
A timestamp joins the billing call,
Then shipping gets the same field set, all.
“Verified!” the bunny writes with glee,
And bounds away beneath the tree.}

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.