Release 8.0.0

[armando-rodriguez-cko]

• The merchant-specific subdomain (environmentSubdomain) is now required. Set it, or call the deprecated useLegacyDomain() to keep using the shared checkout.com hosts (feat: require environmentSubdomain or an explicit useLegacyDomain opt-out #649)
• An invalid subdomain now throws instead of being silently ignored (feat: require environmentSubdomain or an explicit useLegacyDomain opt-out #649)
• Add optional amount to VoidRequest to support partial voids (feat(payments): add optional amount to VoidRequest for partial voids #658)
• Add the ISV (SaaS seller) payout schedule fields balanceMinimum, carryForwardEnabled and paymentInstrumentId (feat(accounts): add the ISV payout schedule fields and funds_transfer_type on payouts #653)

[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.

This diff only shows the version bump from 7.16.2 to 8.0.0 in gradle.properties; the actual feature changes and breaking changes described in the PR body are not visible in the provided diff.

For you to decide

• The diff is partial — only gradle.properties is shown, so none of the claimed changes (required environmentSubdomain, invalid subdomain throws, VoidRequest amount field, ISV payout schedule fields) can be verified against actual code.
• The version bump to 8.0.0 signals a breaking change (major semver), which matches the description of environmentSubdomain now being required and invalid subdomain throwing — a human reviewer needs to confirm these breaking changes are intentional and communicated to consumers.
• A human should verify that the actual implementation PRs (feat: require environmentSubdomain or an explicit useLegacyDomain opt-out #649, feat(payments): add optional amount to VoidRequest for partial voids #658, feat(accounts): add the ISV payout schedule fields and funds_transfer_type on payouts #653) are merged and included in this release before approving the version bump.

---

_{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