[configurationwebhooks] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the configurationwebhooks service.

The commit history of this PR reflects the adyen-openapi commits that have been applied.

Breaking Changes 🛠

Mandate

• The createdAt field type changed from Object to OffsetDateTime (getter/setter/builder signatures updated).
• The updatedAt field type changed from Object to OffsetDateTime (getter/setter/builder signatures updated).

New Features 💎

Configuration Webhooks

• MandateBankAccountAccountIdentification — Added discriminator (type) mappings for the account-identification subtypes (ukLocal → UKLocalMandateAccountIdentification).
• PaymentInstrumentAdditionalBankAccountIdentificationsInner — Added discriminator (type) mappings for the additional bank account identification subtypes (iban → IbanAccountIdentification).
• Mandate.createdAt / Mandate.updatedAt — documentation expanded ("The date when the mandate was created/updated").
• Added BalancePlatformWebhooksTest cases covering the OffsetDateTime mandate dates and the account-identification discriminator (happy path plus invalid-date and unknown-type failure paths).

[gemini-code-assist]

Code Review

This pull request updates the SDK generation metadata and registers discriminator mappings for MandateBankAccountAccountIdentification and PaymentInstrumentAdditionalBankAccountIdentificationsInner. The review feedback points out redundant self-mappings in the discriminator maps that should be removed to keep the code clean. Additionally, it highlights a potential concurrency vulnerability in the underlying JSON registration utility, recommending the use of ConcurrentHashMap to ensure thread safety during class loading.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

1. Redundant Self-Mapping in Discriminator (Medium)

The mapping mappings.put("MandateBankAccount_accountIdentification", MandateBankAccountAccountIdentification.class); maps the parent/composed class to itself. A discriminator should only map to concrete subtype classes (like UKLocalMandateAccountIdentification). If this mapping is ever matched, the custom deserializer MandateBankAccountAccountIdentificationDeserializer will fail anyway because "MandateBankAccount_accountIdentification" is not a valid enum value for any of the subtypes. Removing this self-mapping keeps the code clean and avoids confusion.

2. Concurrency Vulnerability in JSON.registerDiscriminator (High)

The static block calls JSON.registerDiscriminator(...). Under the hood, JSON.java stores these mappings in a plain HashMap (modelDiscriminators). Since different model classes can be loaded concurrently on different threads (especially in a multi-threaded webhook processing environment), concurrent writes to this HashMap can cause race conditions, data corruption, or infinite loops.

Recommendation:
Although JSON.java is not modified in this PR, it should be updated to use ConcurrentHashMap for both modelDiscriminators and modelDescendants to ensure thread safety during class loading:

private static final Map<Class<?>, ClassDiscriminatorMapping> modelDiscriminators =
    new ConcurrentHashMap<>();
private static final Map<Class<?>, Map<String, GenericType>> modelDescendants =
    new ConcurrentHashMap<>();

    // Initialize and register the discriminator mappings.
    Map<String, Class<?>> mappings = new HashMap<>();
    mappings.put("ukLocal", UKLocalMandateAccountIdentification.class);
    mappings.put("UKLocalMandateAccountIdentification", UKLocalMandateAccountIdentification.class);
    JSON.registerDiscriminator(MandateBankAccountAccountIdentification.class, "type", mappings);

[jeandersonbc]

Needs to be checked closely (cc @poojah-adyen)

[poojah-adyen]

1. Low impact fix as it would never match
2. Will be fixed in follow-up PR

[gemini-code-assist]

1. Redundant Self-Mapping in Discriminator (Medium)

The mapping mappings.put("PaymentInstrument_additionalBankAccountIdentifications_inner", PaymentInstrumentAdditionalBankAccountIdentificationsInner.class); maps the parent/composed class to itself. A discriminator should only map to concrete subtype classes (like IbanAccountIdentification). If this mapping is ever matched, the custom deserializer PaymentInstrumentAdditionalBankAccountIdentificationsInnerDeserializer will fail anyway because "PaymentInstrument_additionalBankAccountIdentifications_inner" is not a valid enum value for any of the subtypes. Removing this self-mapping keeps the code clean and avoids confusion.

2. Concurrency Vulnerability in JSON.registerDiscriminator (High)

The static block calls JSON.registerDiscriminator(...). Under the hood, JSON.java stores these mappings in a plain HashMap (modelDiscriminators). Since different model classes can be loaded concurrently on different threads (especially in a multi-threaded webhook processing environment), concurrent writes to this HashMap can cause race conditions, data corruption, or infinite loops.

Recommendation:
Although JSON.java is not modified in this PR, it should be updated to use ConcurrentHashMap for both modelDiscriminators and modelDescendants to ensure thread safety during class loading:

private static final Map<Class<?>, ClassDiscriminatorMapping> modelDiscriminators =
    new ConcurrentHashMap<>();
private static final Map<Class<?>, Map<String, GenericType>> modelDescendants =
    new ConcurrentHashMap<>();

    // Initialize and register the discriminator mappings.
    Map<String, Class<?>> mappings = new HashMap<>();
    mappings.put("iban", IbanAccountIdentification.class);
    mappings.put("IbanAccountIdentification", IbanAccountIdentification.class);
    JSON.registerDiscriminator(
        PaymentInstrumentAdditionalBankAccountIdentificationsInner.class, "type", mappings);

[jeandersonbc]

breaking change

[sonarqubecloud]

Quality Gate passed

Issues
16 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

[poojah-adyen]

LGTM

[poojah-adyen]

1. Low impact fix as it would never match
2. Will be fixed in follow-up PR