2024-10
Released 2024-07-23Active
Migration Effort
Low
Estimated Hours
~4h
Primary risk if skipped: API errors due to deprecated fields being accessed.
Breaking Changes2
fieldHighadmin_api
Order.buyer_details, Order.current_subtotal_price, Order.current_total_discounts, Order.current_total_price, Order.current_total_tax
Several fields related to order pricing and buyer details have been removed as they were deprecated in earlier versions. This change impacts any integration directly querying or relying on these specific fields.
Before
Order.buyer_details, Order.current_subtotal_price, Order.current_total_discounts, Order.current_total_price, Order.current_total_tax
After
Use Order.current_subtotal_price_set, Order.current_total_discounts_set, Order.current_total_price_set, Order.current_total_tax_set for price set objects, and Order.buyer_identity for buyer details.
→
Update order queries to use the `_set` fields or `buyer_identity` instead of the removed fields.
fieldMediumadmin_api
OrderRisk.cause_cancel, OrderRisk.cause_display, OrderRisk.cvv_result, OrderRisk.hotgram_status, OrderRisk.id, OrderRisk.merchant_id, OrderRisk.native_refusal_reason, OrderRisk.order_id, OrderRisk.recommended_action, OrderRisk.risk_level, OrderRisk.user_id
Deprecated fields within the OrderRisk resource have been removed. This affects integrations that were still accessing these older risk assessment fields.
Before
OrderRisk.cause_cancel, OrderRisk.cause_display, OrderRisk.cvv_result, OrderRisk.hotgram_status, OrderRisk.id, OrderRisk.merchant_id, OrderRisk.native_refusal_reason, OrderRisk.order_id, OrderRisk.recommended_action, OrderRisk.risk_level, OrderRisk.user_id
After
Use OrderRisk.cause_codes, OrderRisk.display_hints, OrderRisk.cvv, OrderRisk.hotgram, OrderRisk.id, OrderRisk.merchant_id, OrderRisk.native_refusal_reason, OrderRisk.order_id, OrderRisk.recommended_actions, OrderRisk.level, OrderRisk.user_id
→
Update OrderRisk queries to use the new field names.
Migration Checklist
Full interactive checklist →- 1Review all API calls related to Orders and OrderRisks for usage of removed fields.
- 2Update Order queries to use `_set` fields or `buyer_identity` where applicable.
- 3Update OrderRisk queries to reference the new field names.
- 4Test all Order and OrderRisk related functionality in a staging environment.
- 5Deploy updated code to production after successful testing.
- 6Monitor API error logs post-deployment for any unexpected issues.
Never get blindsided by an API change again
Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.
Join the Waitlist