[checkout] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the checkout 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 delivers a comprehensive update to the checkout service's code generation, incorporating new API capabilities and refining existing data models. The changes aim to expand the platform's functionality by introducing mechanisms for forwarding payment details, enabling advanced payment validations, and standardizing SDK-related data. These updates facilitate more flexible and robust payment processing, particularly for complex scenarios involving network tokens and enhanced scheme data, while also improving the clarity and accuracy of data model descriptions.

Highlights

• New API Endpoint for Forwarding Payment Details: A new forward method has been added to the RecurringApi service, enabling the forwarding of stored payment details to third-party APIs. This functionality is supported by new request and response models: CheckoutForwardRequest and CheckoutForwardResponse.
• Standardized SDK Data Field: A new optional sdkData field, containing Base64-encoded JSON for SDK-related parameters, has been introduced across a wide range of payment method detail models (e.g., AchDetails, CardDetails, GooglePayDetails, PayPalDetails, etc.) to standardize SDK integration.
• Enhanced Scheme Data (Level 2/3) Support: New models like Destination, ItemDetailLine, and LevelTwoThree have been added to support more detailed Level 2/3 enhanced scheme data, allowing for richer transaction information to be passed for certain card payments.
• Payment Validations Feature: A new set of models (PaymentValidations, PaymentValidationsNameRequest, PaymentValidationsNameResponse, etc.) has been introduced to support payment validations, specifically for cardholder name verification against issuing bank records.
• Expanded Funding Source Options: The FundingSourceEnum across several payment method models (e.g., ApplePayDetails, CardDetails, GooglePayDetails) now includes a Prepaid option, reflecting broader support for different card types.
• Updates to Existing Payment Method Types: The GenericIssuerPaymentMethodDetails now includes OnlinebankingIn as a supported type, while PaymentDetails has removed Neteller and Moneybookers from its TypeEnum.
• Token Mandate Details: A new TokenMandate model has been added, providing detailed information about payment mandates, including billing rules, frequency, and status, and is now referenced in StoredPaymentMethodResource.

🧠 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 introduces a significant number of changes, primarily auto-generated from an OpenAPI specification update for the checkout service to version v71. The changes include adding new services, models, and properties, as well as updating existing ones. My review focused on the correctness and maintainability of these generated changes. I've identified a few minor issues, mainly related to documentation comments and a potential typo in a property name originating from the spec. Overall, the generated code seems correct and follows existing patterns.

[gemini-code-assist]

The comment for sdkData is missing important information about not including sensitive data. This information was present on the sdkData property that was removed from PaymentRequest. It would be beneficial to include this warning for developers. This comment applies to all newly added sdkData properties across the different payment detail files in this PR.

Suggested change

	/**
	* Base64-encoded JSON object containing SDK related parameters required by the SDK
	*/
	"sdkData"?: string;
	/**
	* Base64-encoded JSON object containing SDK related parameters required by the SDK to function optimally. Clients must not add unrelated or sensitive personal information.
	*/
	"sdkData"?: string;

[gemini-code-assist]

The property name sepadirectdebit_sepadirectdebit_dueDate seems to have a duplicate sepadirectdebit. This is likely due to its baseName being sepadirectdebit.sepadirectdebit.dueDate in the attributeTypeMap, which also seems to contain a typo. This might be an issue in the underlying OpenAPI specification. If so, it should be corrected there to generate a cleaner property name like sepadirectdebit_dueDate.

[gemini-code-assist]

The comment for storedPaymentMethodId incorrectly refers to recurringDetailReference. This seems to be a copy-paste error and should be corrected to refer to storedPaymentMethodId. This issue is present in many other payment detail files in this PR where storedPaymentMethodId is defined.

Suggested change

	/**
	* This is the `recurringDetailReference` returned in the response when you created the token.
	*/
	"storedPaymentMethodId"?: string;
	/**
	* This is the `storedPaymentMethodId` returned in the response when you created the token.
	*/
	"storedPaymentMethodId"?: string;