Release 7.16.0

[armando-rodriguez-cko]

• Add merchant_id to the Google Pay enrollment response (fix: add merchant_id to the Google Pay enrollment response #651)
• Send articles_of_association as an object with type and front, instead of a bare string the API rejected, so the document can be sent at all (fix: send articles_of_association as an object, not a bare string #650)
• Add fallback_source_used to PaymentProcessing and document ProcessingData (feat(payments): add fallback_source_used to PaymentProcessing and complete ProcessingData JavaDoc #646)

Note for the release notes: #650 changes the type of OnboardSubEntityDocuments.articlesOfAssociation from the ArticlesOfAssociationType enum to the new ArticlesOfAssociation object. That is source-breaking for anyone assigning the enum directly, but the old shape was rejected by the API, so nothing that worked stops working. Minor, per the rule that an API-forced break is not a major.

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket
• ✅ independent_review

Files analysed: 1

---

_{wall-e 2026.06.19-02 · policy 376219bc71e6…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[agent-wall-e]

🔵 Advisory review: Sound, but needs your judgement

This PR needs a human approval. The code itself reads as correct; whether it should land depends on context I don't have.

The diff only shows a version bump from 7.15.0 to 7.16.0, but the PR description claims three substantive code changes (merchant_id in Google Pay response, articles_of_association object refactor, fallback_source_used addition). The actual code changes are not present in this diff, so correctness of the release cannot be verified here.

For you to decide

• The diff is partial — only gradle.properties is shown, so the three claimed feature changes (fix: add merchant_id to the Google Pay enrollment response #651, fix: send articles_of_association as an object, not a bare string #650, feat(payments): add fallback_source_used to PaymentProcessing and complete ProcessingData JavaDoc #646) cannot be verified against this diff.
• A human reviewer must confirm that the accompanying code changes for merchant_id, ArticlesOfAssociation object type change, and fallback_source_used are actually included in this release branch/commit range.
• The breaking change noted for OnboardSubEntityDocuments.articlesOfAssociation (enum → object) needs human confirmation that it is intentionally included and release notes/changelog have been updated accordingly.
• Version 7.16.0 follows 7.15.0 semantically — a human should confirm this is the correct version increment given the described changes (minor version bump appears consistent with the described additions and the one source-breaking-but-API-forced change).

---

_{This is not an approval. wall-e cannot auto-approve this PR — it is an opinion to help whoever does. Advisory review · us.anthropic.claude-sonnet-4-6 · wall-e 2026.06.19-02}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud