Releases: checkout/checkout-sdk-python
3.7.0
Release 3.7.0 (#209)
This release introduces several major enhancements and new features to the issuing and disputes modules, as well as expands the API client surface for cards, controls, and simulated transactions. The changes include the addition of new request and response models, new client methods for dispute and card management, and extended support for control groups and profiles.
Issuing Cards and Card Management Enhancements:
- Added new request models for updating, renewing, and scheduling revocation of cards, including support for card metadata, and introduced corresponding client methods for these operations in
IssuingClient. [1] [2] [3] [4] [5] [6] [7] [8]
Disputes and Evidence Handling:
- Introduced new request and data models for creating and escalating disputes, including evidence and reason change structures, and added new methods to
IssuingClientfor dispute lifecycle management. [1] [2] - Enhanced the disputes client with arbitration evidence submission and retrieval methods. [1] [2]
Controls, Control Groups, and Profiles:
- Expanded the controls module with new types and enums (e.g.,
MID_LIMIT,FailIfType), added support for MID-based limits, and introduced models and client methods for control groups and control profiles, enabling more granular and grouped control management. [1] [2] [3] [4] [5] [6]
Testing and Simulation Improvements:
- Added simulation request/response models for refund authorizations and out-of-band (OOB) authentication, and extended
IssuingClientwith methods to simulate these scenarios. [1] [2] [3]
API Client Surface Expansion:
- Registered new API clients for network tokens and payment methods in the main API client initialization. [1] [2]
API Schemas review:
- All the requests schemas have been reviewed to detect missing or changed fields with the latest swagger specifications, several updates have been done including: new fields, renames, typo fixes, etc.
These changes significantly enhance the flexibility and capability of the SDK for managing cards, disputes, and controls, and provide improved support for testing and simulation scenarios.
3.6.1
Release 3.6.1 (#206)
This release makes a small update to the project's dependencies by adding the Deprecated package to the install_requires list in setup.py. This ensures that the package is installed alongside the other dependencies.
- Added
Deprecated >= 1.2.14to theinstall_requiressection insetup.pyto manage deprecated functionality.
3.6.0
Release - 3.6.0 (#204)
This release introduces several new features and enhancements across the SDK, including support for agentic commerce, compliance requests, expanded account management, and improved HTTP header handling. The most significant changes are the addition of new client modules, new data models, and enhancements to the API client to support custom headers.
New SDK Modules and Features:
- Added support for Agentic Commerce, including new models in
agentic_commerce.pyand a corresponding client inagentic_commerce_client.pyfor delegated payment flows. [1] [2] - Introduced Compliance Requests functionality with new models (
compliance_requests.py) and a client (compliance_requests_client.py) to retrieve and respond to compliance requests. [1] [2] - Updated
checkout_api.pyto expose new clients for agentic commerce, compliance requests, Apple Pay, Google Pay, standalone account updater, AML screening, face authentication, ID document verification, applicants, and identity verification, making these services available via the main API entry point. [1] [2] [3] [4]
Enhancements to Account Management:
- Added models and client methods for reserve rules, entity file uploads, and sub-entity member management in the accounts module. This includes new classes such as
ReserveRuleRequest,FilePurpose, and related API client methods for CRUD operations on reserve rules and entity files. [1] [2] [3] [4] [5]
API Client Improvements:
- Enhanced
ApiClientto support passing custom headers for POST, PUT, and PATCH requests, including logic to map model properties to HTTP headers (e.g., for ETag or API versioning). This allows for more flexible and standards-compliant API interactions. [1] [2] [3] [4]
Additional Data Models:
- Added new data models for forward requests and secret requests, expanding the flexibility of the SDK in handling various request types.
These changes collectively expand the SDK's capabilities, improve extensibility, and enhance support for new Checkout.com platform features.