[transferwebhooks] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the transferwebhooks service.

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

[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 contains automated updates to the transferwebhooks service, reflecting recent changes in the underlying OpenAPI specification. The modifications primarily involve enhancing data models with new fields, updating and deprecating enum values, and refining documentation for improved clarity and accuracy. These changes ensure the service's typings and definitions remain synchronized with the latest API specifications.

Highlights

• New Field Addition: The BankAccountV3 model now includes an optional storedPaymentMethodId field, which is a unique token for identifying stored bank account details for payouts.
• Enum Value Updates: The PlatformPaymentTypeEnum in PlatformPayment has been updated to include DCCMarkup and deprecate DCCPlatformCommission. Additionally, the TransferData.ResultEnum and TransferEvent.ResultEnum have been significantly expanded with numerous new possible transfer result values, providing more granular status reporting.
• Documentation Refinements: JSDoc comments for various properties and enum values across Amount, BankCategoryData, and TransferData have been clarified and made more consistent.
• Internal Model Adjustments: The TransferDataTrackingClass has seen internal adjustments to its discriminator and mapping properties, likely to align with updated schema definitions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 contains automated updates to the services and models for transferwebhooks. The changes primarily consist of documentation updates, the addition of new enum values, and the introduction of new properties to existing models. While most of these changes appear to be routine updates, I have identified a critical issue in transferDataTracking.ts where the removal of a mapping object for a discriminated union is likely to cause runtime errors during webhook deserialization. This issue may also be present in other auto-generated files not included in this pull request's diff, so a broader check might be warranted.

[gemini-code-assist]

Removing the mapping object will likely break the deserialization of the TransferDataTracking union type. The ObjectSerializer.deserialize method relies on this mapping to resolve the concrete type from the type discriminator field in the JSON payload. Without it, the serializer won't be able to map values like "confirmation" to the ConfirmationTrackingData class, leading to runtime errors. Please restore the mapping to ensure proper deserialization.

    static readonly mapping: {[index: string]: string} | undefined = {
        "confirmation": "ConfirmationTrackingData",
        "estimation": "EstimationTrackingData",
        "internalReview": "InternalReviewTrackingData"
    };