[rodrigojara-cko]

Summary

Documents and types the Tamara payment method of Payment Setups: initialization and
risk_assessment (premium_customer, risk_score, order_count_last24h, linked_device_count), sent on
create and update. The SDK already sent these fields as given; this adds the JSDoc, the TypeScript
declaration types and tests.

Changes

• src/api/payment-setups/payment-setups.js: JSDoc for payment_methods.tamara on create and update, with the readOnly status and flags it returns.
• types/dist/api/payment-setups/payment-setups.d.ts: new Tamara and TamaraRiskAssessment types, tamara?: Tamara on PaymentSetupPaymentMethods.
• test/payment-setups/payment-setups-unit.js: create and update send payment_methods.tamara unchanged, with the literal wire keys.

API Reference

• POST /payments/setups: https://api-reference.checkout.com/tag/payment-setups/POST/payments/setups.body.payment_methods.tamara.initialization
• POST /payments/setups: https://api-reference.checkout.com/tag/payment-setups/POST/payments/setups.body.payment_methods.tamara.risk_assessment
• PUT /payments/setups/{id}: https://api-reference.checkout.com/tag/payment-setups/PUT/payments/setups/%7Bid%7D.body.payment_methods.tamara.risk_assessment

Breaking changes

None. payment_methods.tamara was typed unknown; code that sends the fields of the specification compiles unchanged.

Tests

• Existing tests pass
• Serialization tests cover every new or changed property
• README updated if documented usage changed (not needed)

Related

None.

[agent-wall-e]

🟢 Risk Classification: LOW

Approval route: AI Auto-Approval
Rollback controls: Automated Instant Rollback + feature flags

Classification reasons

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:The change only adds JSDoc comments, TypeScript type declarations, and tests for fields already being sent through an existing code path, with no new endpoints, persistence, auth changes, or external integrations introduced.

Operational gates

• ✅ jira_ticket (INT-1712)
• ✅ independent_review

Files analysed: 3

---

_{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.
2.2.6_logical_extension — The change only adds JSDoc comments, TypeScript type declarations, and tests for fields already being sent through an existing code path, with no new endpoints, persistence, auth changes, or external integrations introduced.	classifying	§2.2.6	Sonnet 4.6 evaluator promoted minor → low: the change reuses existing code paths and does not cross a trust boundary.

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}

[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

[agent-wall-e]

✅ Auto-approved — this PR meets all Low-risk criteria.

All checks passed, no unresolved comments, and the change classification is:

• no_low_class_matched
• prod_source_modified
• 2.2.6_logical_extension:The change only adds JSDoc comments, TypeScript type declarations, and tests for fields the SDK already sent, without introducing new endpoints, persisted data, auth changes, or external integrations.

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}