9.5.0

Changes

Added

• New TransactionService.getSuccessfulChargeAttempt method — returns the successful charge attempt that authorized a given transaction.
• New PaymentTerminalTillService methods to trigger terminal configuration: triggerConfiguration (by terminal ID) and triggerConfigurationByIdentifier (by terminal identifier/TID).

Changed

• Added transactionLinkIdentifier field to the AuthenticatedCardDataCreate and TokenizedCardDataCreate entities, used to link card transaction lifecycle events within the payment scheme.
• Added activatedOn, deactivatedOn, and decommissionedOn timestamp fields to the PaymentTerminal entity.
• Added numberOfFreeTrialPeriods field to the ProductMeteredFee and ProductMeteredFeeUpdate entities, to define the number of trial billing cycles before fees are charged.
• Added description field to the Role entity for custom key/value metadata.
• Added trustedExternalOrigins field to the Scope entity for CORS/redirect trust configuration.
• Added requiredFeatures field to the WalletType entity, listing required wallet Features.
• Updated the label of the productionMerchantId field on the PaymentTerminalLocation entity from "Production Merchant Id" to "Merchant Id" (cosmetic only, no type/behavior change).

9.4.0

Changes:

• Introduced a new ExpressCheckoutService
• Added a new metaData field in several entities
• Changes in SubscriptionUpdateRequest entity

9.3.0

Changes:

• Added ApiExceptionErrorCodes and SdkExceptionErrorCodes classes for more convenient error handling.
• New PaymentTerminalTransactionSummariesService for operations related to transaction summaries.

9.2.0

Feature

• PaymentTerminalLocation now has new filed: productionMerchantId

Python

• Fixed __init__ files for correct module recognition

Minor changes

• Small technical adjustments in SDK internal components

9.1.0

Feature

• Analytics queries now require ExternalId to be submitted
• Existing operations in AnalyticsQueriesService can now be performed with either QueryToken or ExternalId

9.0.0

Introducing API v2 Support (Breaking Changes)

This is a major milestone release for the SDK! New version has been completely rewritten to support our new, more powerful REST API v2.

This update brings significant improvements in performance, security, and features. Due to the foundational changes in the API, this version is not backward-compatible with previous versions of the SDK.

BREAKING CHANGES

Before upgrading, please be aware of the following:

• REST API v1 Is No Longer Supported: This SDK version works only with REST API v2. To continue using API v1, you must remain on the previous versions of this package.

• Complete Method Rewrite: All client methods have been renamed and restructured to align with the new API v2 endpoints.

• New Authentication: The client initialization and authentication process has been updated to match API v2 requirements.

• Updated Error Handling: Error responses now follow the new API v2 error schema.

• Model/Type Changes: All request and response models have been replaced with new ones based on the API v2 specification.

What's New

• Full REST API v2 Support: All new endpoints are now available.

• Improved Performance: Optimized request handling for faster and more reliable communication.

• Enhanced Security: Implements the latest authentication and signing mechanisms required by API v2.

Authentication Guide

We strongly recommend reading the Authentication Guide before upgrading.

Documentation

For full details on the new API, please see the official API v2 documentation:
https://checkout.postfinance.ch/en-us/doc/api/web-service

8.8.3

SDK alignment with latest REST API v1 changes

8.8.1

SDK alignment with latest REST API v1 changes

8.8.0

SDK alignment with latest REST API v1 changes

8.7.0

Feature

• Artifacts are now published directly to Maven Central instead of the legacy OSSRH.