Release 6.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 #359)
• An invalid subdomain now throws instead of being silently ignored (feat: require environmentSubdomain or an explicit useLegacyDomain opt-out #359)
• Add optional amount to VoidRequest to support partial voids (feat(payments): add optional amount to VoidRequest for partial voids #366)
• Add the ISV (SaaS seller) payout schedule fields balance_minimum, carry_forward_enabled and payment_instrument_id (feat(accounts): add ISV payout schedule fields and payment_instrument_id #367)

[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: 2

---

_{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 bumps the version string from 5.4.0 to 6.0.0 in two places, but the PR description claims four substantive feature/breaking changes are included; none of those changes are visible in this diff.

For you to decide

• The diff contains only version string changes in CheckoutUtils.php and version.json — the four claimed changes (required environmentSubdomain, invalid subdomain throws, partial void amount, ISV payout schedule fields) are not present in this diff, so they must be in prior commits or the diff is incomplete.
• If this is a squash/tag-only PR on top of already-merged feature branches, a human reviewer needs to confirm all four described changes are actually present in the codebase at this commit before approving the version bump.
• The jump from 5.4.0 to 6.0.0 signals a breaking change (required environmentSubdomain); a reviewer should verify that changelog, migration guide, or README updates accompany this release and are not silently missing.

---

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