Code generation: update services and models

[AdyenAutomationBot]

Add in Recurring new enums ONECLICK_RECURRING, EXTERNAL in BinLookup/Checkout/Payout, however those enums are not used by the API (skip from Release Notes).

OpenAPI spec files or templates have been modified on 26-09-2025 by commit.

[gemini-code-assist]

Summary of Changes

Hello @AdyenAutomationBot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request delivers an automated update to the Adyen services and models, ensuring that the codebase remains synchronized with the latest OpenAPI specification. The changes are primarily focused on maintaining code quality and consistency through reordering imports, refining Javadoc comments, and adjusting whitespace, reflecting an evolution in the underlying API definitions.

Highlights

• Automated Code Generation: This pull request is an automated update of services and models based on recent modifications to the OpenAPI specification files.
• Code Formatting and Structure: Numerous Java model files across acswebhooks, balancecontrol, and balanceplatform packages have undergone structural and cosmetic changes, including reordering of import statements, adjustments to whitespace, and reformatting of Javadoc comments.
• New Imports and Javadoc Updates: Many files now include new import statements for various utility classes and model components, alongside updates to Javadoc comments to reflect the latest API definitions and improve readability.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, generated by an OpenAPI tool, introduces widespread formatting changes across numerous model and service files. While many changes are stylistic (like indentation), some have introduced inconsistencies and reduced code readability. My review focuses on these recurring patterns, with specific examples provided in the comments. Key areas for improvement include:

• Refactoring verbose logic in AcsWebhooksHandler to use a more concise, functional style.
• Reformatting single-line method implementations for better readability.
• Correcting improperly formatted empty constructors and Javadoc comments.
  Addressing these patterns across the codebase will improve maintainability and adherence to standard Java conventions.