Release 6.7.0 - CashApp payment method integration

[david-ruiz-cko]

This release introduces support for the Cash App payment method in the payment setup flow, along with enhancements to customer and device information handling. It adds new model classes for Cash App-specific data, extends device and customer models with additional fields, and improves test coverage for these features. The main changes are grouped below.

Cash App Payment Method Integration:

• Added a new CashApp payment method model, including support for customer profile sharing, actions, and customer profile details, with associated classes such as CashAppCustomerProfile, CashAppAddress, CashAppAction, and CashAppActionType. (lib/Checkout/Payments/Setups/Common/PaymentMethods/CashApp/CashApp.php [1] CashAppCustomerProfile.php [2] CashAppAddress.php [3] CashAppAction.php [4] CashAppActionType.php [5]
• Registered the CashApp payment method in the PaymentMethods class, allowing it to be serialized and used like other payment methods. (PaymentMethods.php [1] [2]

Customer and Device Model Enhancements:

• Extended the Customer model with new optional fields: id, country, and tax_number, improving support for customer identification and compliance. (Customer.php lib/Checkout/Payments/Setups/Common/Customer/Customer.phpR10-R65)
• Enhanced the Device model with new fields: fingerprint, ipv4, ipv6, client (with enum via DeviceClient), and os (with enum via DeviceOs), supporting richer device context for risk and eligibility checks. (Device.php [1] DeviceClient.php [2] DeviceOs.php [3]

Payment Method Base Improvements:

• Documented and clarified the meaning of status, flags, and initialization fields in PaymentMethodBase, including their possible values and usage. (PaymentMethodBase.php lib/Checkout/Payments/Setups/Common/PaymentMethods/Common/PaymentMethodBase.phpR8-R29)

Test Coverage:

• Added new integration tests to verify the correct handling and echoing of device fields, customer identifiers, and the Cash App payment method in payment setup requests and responses. (PaymentSetupsIntegrationTest.php test/Checkout/Tests/Payments/Setups/PaymentSetupsIntegrationTest.phpR143-R219)
• Added a unit test for confirming a payment setup with Cash App. (PaymentSetupsClientTest.php test/Checkout/Tests/Payments/Setups/PaymentSetupsClientTest.phpR118-R139)

These changes collectively enable richer customer and device data handling and introduce full support for the Cash App payment method in the payment setup workflow.

[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 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: Looks good to me

This PR still needs a human approval — wall-e cannot auto-approve it. For what it's worth, I read the diff and found nothing I'd block on.

This diff only bumps the version string from 6.6.0 to 6.7.0 in two places (CheckoutUtils.php and version.json), which is consistent with a release PR. The version is updated in both required locations and they match each other.

What I checked

• Version is incremented consistently in both CheckoutUtils.php (PROJECT_VERSION constant) and version.json, with no mismatch between the two files.

---

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