Release/7.9.2

[david-ruiz-cko]

This release introduces support for the scheme_transaction_link_id field across several payment processing classes. This field, primarily relevant for Mastercard transactions, is now included in the models, and comprehensive test coverage ensures correct serialization and deserialization. The main focus is to enable the SDK to expose and handle this identifier, which links related transactions on the Mastercard network.

Support for Mastercard Transaction Link Identifier:

• Added the scheme_transaction_link_id field (with documentation) to the following classes: Processing, ProcessingData, and PaymentProcessing, ensuring the field is serialized/deserialized as scheme_transaction_link_id in JSON. [1] [2] [3]
• Updated integration and unit tests to verify correct handling of the new field, including deserialization, serialization, and null handling when the field is absent. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Added necessary imports and assertions in test files to support the new field and its test cases. [1] [2]

These changes ensure that the SDK is ready to handle Mastercard's transaction link identifiers, providing better traceability for related transactions.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[david-ruiz-cko]

Abandoned, wrong merge