Release 4.7.0 - CashApp payment method integration

[david-ruiz-cko]

This release adds comprehensive support for Cash App Pay in the payment setups API and enhances the handling and serialization of customer device and identification fields. It updates the public API documentation, adds new integration and serialization tests, and ensures that the new fields are correctly processed and echoed by the API.

Cash App Pay support:

• Added support for Cash App Pay in payment setups, including serialization/deserialization of payment_methods.cashapp, its actions, and customer profiles. Includes tests for request/response structure and round-trip serialization. [1] [2] [3]
• Added integration and unit tests to verify Cash App Pay setup, confirmation, and the handling of Cash App–specific fields and actions. [1] [2] [3]

Customer device and identification fields:

• Added support for new customer.device fields (fingerprint, ipv4, ipv6, client, os) and ensured they are accepted and echoed by the API. Also added tests for these fields. [1] [2]
• Added support for customer.id, customer.country, and customer.tax_number, with tests to verify round-trip serialization and correct field mapping. [1] [2]

API documentation improvements:

• Enhanced docstrings for the create_payment_setup, update_payment_setup, get_payment_setup, and confirm_payment_setup methods in setups_client.py to clarify usage, arguments, and Cash App Pay–specific behavior. [1] [2] [3]

These changes ensure robust support for Cash App Pay and new customer fields, with thorough test coverage and improved documentation for API consumers.

[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 6b4ce2b3b45a…}

[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 4.6.0 to 4.7.0, but the PR description claims substantial feature additions (Cash App Pay, customer device fields, API docs, tests) — a human reviewer must verify whether the full change set is present and correct before approving.

For you to decide

• The diff is partial: only properties.py is shown, so none of the claimed functional changes (Cash App Pay serialization, customer device fields, new tests, docstring updates) can be verified here.
• A reviewer must confirm that the actual implementation files referenced in the PR description (setups_client.py, serialization/test files) are included in the full PR and match the claimed scope before treating this as a complete release.
• The version bump itself (4.6.0 → 4.7.0) looks correct for a minor feature release by semver conventions, assuming the underlying changes are additive and non-breaking.

---

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