Response schema changed for DELETE /v1/accounts/{account}/bank_accounts/{id} (payments_primitives_payment_records_resource_payment_method_card_details_resource_…
Response schema changed for DELETE /v1/accounts/{account}/bank_accounts/{id} (payments_primitives_payment_records_resource_payment_method_card_details_resource_three_d_secure)
- Affected surface
- DELETE /v1/accounts/{account}/bank_accounts/{id}
- Affected field
- payments_primitives_payment_records_resource_payment_method_card_details_resource_three_d_secure
What changed
Response schema changed for DELETE /v1/accounts/{account}/bank_accounts/{id} (payments_primitives_payment_records_resource_payment_method_card_details_resource_three_d_secure) Affected surface: DELETE /v1/accounts/{account}/bank_accounts/{id}. Root cause: schema `payments_primitives_payment_records_resource_payment_method_card_details_resource_three_d_secure`. Detected at Wed, 26 Aug 2026 18:51:05 UTC UTC.
Diff
{
"path": "DELETE /v1/accounts/{account}/bank_accounts/{id}",
"removed_fields": [
"cryptogram"
],
"schema_path": "schema payments_primitives_payment_records_resource_payment_method_card_details_resource_three_d_secure"
}Likely impact
The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.
Recommended action
Diff your serializers against the new schema. The diff above shows what moved.
Related changes
Other endpoints affected by the same root cause.
Catch changes like this on every API you depend on.
Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.