Repository navigation
deprecate(issuing): deprecate the update-card headers and allow revoke and suspend without a body - #697
Conversation
🟢 Risk Classification: LOWApproval route: AI Auto-Approval Classification reasons
Operational gates
Files analysed: 5 wall-e 2026.06.19-02 · policy |
🔬 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.
Kinds:
See issue #3 for the proposal to formalise this map as Appendix A of the standards doc. wall-e 2026.06.19-02 · debug |
🟢 Risk Classification: LOWApproval route: AI Auto-Approval Classification reasons
Operational gates
Files analysed: 11 wall-e 2026.06.19-02 · policy |
🔬 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.
Kinds:
See issue #3 for the proposal to formalise this map as Appendix A of the standards doc. wall-e 2026.06.19-02 · debug |
🟢 Risk Classification: LOWApproval route: AI Auto-Approval Classification reasons
Operational gates
Files analysed: 11 wall-e 2026.06.19-02 · policy |
🔬 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.
Kinds:
See issue #3 for the proposal to formalise this map as Appendix A of the standards doc. wall-e 2026.06.19-02 · debug |
…e and suspend without a body The API no longer documents the return-encrypted-cvv and Encryption-Key headers on the card update operation, so CardUpdateHeaders and the update overloads that take it are deprecated. They keep sending the headers when set and will be removed in the next major version. The revoke and suspend request bodies are optional in the API, so both operations now accept a null request and gain overloads without one.
1510613 to
9ca7e0f
Compare
🟢 Risk Classification: LOWApproval route: AI Auto-Approval Classification reasons
Operational gates
Files analysed: 11 wall-e 2026.06.19-02 · policy |
🔬 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.
Kinds:
See issue #3 for the proposal to formalise this map as Appendix A of the standards doc. wall-e 2026.06.19-02 · debug |
|
There was a problem hiding this comment.
✅ Auto-approved — this PR meets all Low-risk criteria.
All checks passed, no unresolved comments, and the change classification is:
no_low_class_matchedprod_source_modified2.2.6_logical_extension:The PR only adds no-arg default interface method overloads delegating to existing implementations, marks existing code as deprecated without changing behavior, removes unnecessary parameter validation, and adds Javadoc—no new endpoints, external integrations, persisted data, auth changes, or background processes are introduced.
wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…
There was a problem hiding this comment.
✅ Auto-approved — this PR meets all Low-risk criteria.
All checks passed, no unresolved comments, and the change classification is:
no_low_class_matchedprod_source_modified2.2.6_logical_extension:The PR only adds no-body convenience overloads that delegate to existing methods with null, deprecates existing headers/methods without removing them, relaxes validation on existing endpoints, and adds Javadoc—no new endpoints, services, persisted data, auth changes, or external integrations are introduced.
wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…
There was a problem hiding this comment.
✅ Auto-approved — this PR meets all Low-risk criteria.
All checks passed, no unresolved comments, and the change classification is:
no_low_class_matchedprod_source_modified2.2.6_logical_extension:The PR only deprecates existing methods/classes, adds no-body convenience overloads that delegate to existing code paths with null, removes parameter validation for optional request bodies, and adds Javadoc — no new endpoints, persisted data, auth changes, external integrations, or background processes are introduced.
wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…



Summary
The API no longer documents the
return-encrypted-cvvandEncryption-Keyheaders on card update, and the revoke and suspend request bodies are optional. This PR deprecates the headers (they still work) and lets revoke and suspend be called without a body.Changes
CardUpdateHeaders: marked@Deprecated, behaviour unchanged.IssuingClient/IssuingClientImpl:updateCard(String, UpdateCardRequest, CardUpdateHeaders)andupdateCardSync(String, UpdateCardRequest, CardUpdateHeaders)marked@Deprecated, pointing to the overloads without headers.IssuingClient/IssuingClientImpl: newrevokeCard(String),revokeCardSync(String),suspendCard(String),suspendCardSync(String); the existing overloads accept anullrequest, in which case no body is sent. Javadoc added to all revoke and suspend methods.IssuingClientImplTestcovers revoke and suspend without a body (sync and async) and the deprecated header overloads;CardUpdateResponseSerializationTestkeeps the header tests.Verified against the sandbox: update with and without the deprecated headers (200), and revoke and suspend without a body and with
{}(200, status changes applied), sync and async.API Reference
Breaking changes
None: deprecations and new overloads only, and the headers are still sent when set.
README
No changes needed; the README does not document these methods.