Release - 4.7.0 (#330)

This release adds support for new sdk clients: Agentic Commerce, Compliance Requests and GooglePay. It introduces new API clients, request/response entity classes, and updates the main CheckoutApi class to expose these clients. Additionally, it updates the API client to allow passing custom headers for POST requests. These changes enable delegated payment token creation, compliance request retrieval, and response submission.

Agentic Commerce API integration:

• Added AgenticCommerceClient for creating delegated payment tokens, including support for custom integrity headers and idempotency keys.
• Introduced related entity classes: DelegatedPaymentRequest, DelegatedPaymentAllowance, DelegatedPaymentBillingAddress, DelegatedPaymentMethodCard, DelegatedPaymentRiskSignal, and supporting enums/types for card and funding types. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Compliance Requests API integration:

• Added ComplianceRequestsClient to retrieve and respond to compliance requests by payment ID.
• Added entity classes for compliance response fields and grouping by party: ComplianceRespondedField, ComplianceRespondedFields. [1] [2]

Google Pay API integration:

• Added GooglePayClient to manage all google pay enrollments and domains

Core API enhancements:

• Updated ApiClient::post to accept optional custom headers, supporting new API requirements for integrity and versioning.

Main API surface changes:

• Updated CheckoutApi to instantiate and expose AgenticCommerceClient, ComplianceRequestsClient, and GooglePayClient via new getter methods. [1] [2] [3] [4] [5]

Release - 4.6.1 (#328)

Added account_name_inquiry field to AccountHolder class (#327)

This release introduces a small update to the AccountHolder class by adding a new property to support account name inquiry functionality.

lib/Checkout/Common/AccountHolder.php: Added a new public boolean property account_name_inquiry to the AccountHolder class to indicate whether an account name inquiry has been performed.

Release - 4.6.0 (#311)

This release introduces several enhancements and new features to the SDK, focusing on expanding API coverage, improving file handling. The changes include new client methods for file upload and retrieval, support for additional API clients, improvements to request serialization, and the addition of several new data classes.

Major SDK Feature Additions and Improvements:

• Added new methods to AccountsClient for uploading and retrieving files for sub-entities, supporting due diligence documentation.
• Introduced new endpoints in DisputesClient to support arbitration evidence submission and retrieval for disputes.
• Added new data classes: FilePurpose (for file upload purposes), UploadFileRequest (file upload request model), CardholderAccessTokenRequest, UpdateCardholderRequest, and CardMetadata. [1] [2] [3] [4] [5]
• Updated ShippingInstructions in the issuing cards module to clarify and swap the meaning of shipping_address and recipient_address.

API Client and Serialization Enhancements:

• Improved request body handling in ApiClient to correctly set content types for JSON, multipart, and form-urlencoded requests, ensuring more robust API interactions.
• Added utility methods in Client to serialize request objects as form-urlencoded data, converting camelCase properties to snake_case as required by some endpoints.

Expanded API Client Access:

• Registered and exposed new clients in CheckoutApi: PaymentMethodsClient, StandaloneAccountUpdaterClient, and ApplePayClient, with corresponding getter methods for easier access. [1] [2] [3] [4]

Other Minor Improvements:

• Added a missing import for UploadFileRequest in AccountsClient to support the new file upload feature.
• Added a constant for the arbitration path in DisputesClient.

Release - 4.5.0 (#309)

This release introduces new features and enhancements to the Checkout API client, focusing on expanding support for identities management, sub-entity member management, reserve rules, and additional API clients. It also improves the flexibility of the API client for handling custom headers and request body formats. Below are the most important changes:

API Client Enhancements

• Refactored ApiClient to support custom headers via reflection, improved handling of different request body formats (JSON, multipart form data, form URL encoded), and updated method signatures for greater flexibility. [1] [2] [3] [4] [5]

• Refactored ApiClient methods to accept a more generic $requestBody and optional custom headers, improving support for different content types (JSON, multipart, form URL encoded) and making header injection more flexible via reflection. Utility methods were added for header conversion and content-type detection. [1] [2] [3] [4] [5]

• New if-match header support in the put requests through Accounts Headers class.

New API Client Integrations

• Added new client properties and getter methods to CheckoutApi for NetworkTokensClient, FaceAuthenticationClient, IdDocumentVerificationClient, IdentityVerificationClient, AmlScreeningClient, and ApplicantsClient, enabling access to additional Checkout.com API features. [1] [2] [3] [4] [5] [6]

New Features: Sub-Entity Members & Reserve Rules

• Added methods to AccountsClient for managing sub-entity members (retrieving and reinviting) and reserve rules (creating, retrieving, updating, and fetching details). New request and entity classes for reserve rules (CreateReserveRuleRequest, UpdateReserveRuleRequest, Rolling, HoldingDuration) were introduced. [1] [2] [3] [4] [5]

Enhancements to Accounts and Reserve Rules

• Added new methods in AccountsClient to manage sub-entity members (retrieving and re-inviting members) and reserve rules (creating, querying, retrieving details, and updating reserve rules), along with the necessary request and entity classes (CreateReserveRuleRequest, UpdateReserveRuleRequest, Rolling, HoldingDuration). [1] [2] [3] [4] [5] [6] [7]

Identity Verification Client Integrations

• Added new clients for identity verification, AML screening, face authentication, ID document verification, and applicant management to the CheckoutApi, making these services directly accessible via the main API class, integrated new identity-related clients (FaceAuthenticationClient, IdDocumentVerificationClient, IdentityVerificationClient, AmlScreeningClient, ApplicantsClient) into CheckoutApi, with corresponding getter methods for each. [1] [2] [3] [4]

Forward API Secret Management

• Added secret management functionality to the ForwardClient, including methods to create, list, update, and delete secrets. New request classes for creating and updating secrets, and a metadata entity for secret information, were also introduced.

Codebase Organization

• Moved and renamed files in the Forward module from the Requests namespace to the Entities namespace for improved clarity and consistency. (Headers.php, MethodType.php, NetworkToken.php) [1] [2] [3]This pull request introduces several new features and improvements to the Checkout SDK, focusing on enhanced support for sub-entity management, reserve rules, and identity verification, as well as improvements to the API client for more flexible request handling. It also includes some refactoring and namespace changes for better organization.

• Refactored several ForwardClient request-related classes to reside under the Entities namespace instead of Requests, improving code organization and clarity. [1] [2] [3] [4] [5] [6]

These changes collectively add significant new functionality for managing sub-entity users and reserve rules, improve the flexibility of API requests, and enhance the SDK's support for identity verification workflows.

Release 4.4.1 (#306)

• feat: update Hosted Payments Request with missing fields

Release 4.4.0 (#304)

• Enhance JsonSerializer to prevent escaping forward slashes in Google Pay signedMessage

Release 4.3.0 (#302)

• Fix file upload Content-Length for Dispute API

Release 4.2.0 - Merchant-specific DNS names support for access (#300)

Release 4.1.0 - New endpoint payments setups support (#298)

This release introduces significant new functionality to support payment setups in the Checkout API, including the addition of new client classes, data models, and enhancements to existing payment and industry data structures. The main focus is on expanding the API's support for more complex payment setup scenarios, such as customer details, industry-specific data, and a variety of payment methods.

Release 4.0.3 (#295)

• feat: add affiliate_id and affiliate_url to ProcessingSettings, type and sub_type to Product, and create ProductSubType class (#294)