[TEST] [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 integrates recent updates from the Adyen OpenAPI specification into the checkout service models. The changes primarily involve adding new fields to existing request and response objects, enhancing the data available for payment processing and stored payment methods. This ensures the API client remains synchronized with the latest API definitions, providing extended functionality and data points for checkout operations.

Highlights

• New fields added to CheckoutForwardRequest and CheckoutForwardResponse: The CheckoutForwardRequest and CheckoutForwardResponse models now include a merchantReference field, allowing for merchant-defined payment references in checkout operations.
• Expanded StoredPaymentMethodDetails TypeEnum: The StoredPaymentMethodDetails model's TypeEnum has been significantly expanded to include various Alipay+ related payment methods, such as Alipay+ Alipay CN, Dana, GCash, KakaoPay, and more.
• New cardBin field in StoredPaymentMethodResource: The StoredPaymentMethodResource model now includes a cardBin field, which represents the bank identification number (BIN) of a stored card.
• Automated Code Generation Update: This pull request contains automated changes generated from the adyen-openapi specification, ensuring the checkout service models are up-to-date.

🧠 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 changes from a code generation process, which updates several model classes in the checkout service. The changes primarily involve adding new fields, such as merchantReference to CheckoutForwardRequest and CheckoutForwardResponse, and cardBin to StoredPaymentMethodResource. Additionally, new ALIPAY_PLUS payment method types have been added to the StoredPaymentMethodDetails enum. The generated code is consistent with the existing structure and patterns within the project. My review includes a suggestion to enhance test coverage for the newly added merchantReference field to ensure its behavior is verified.

[gemini-code-assist]

The CheckoutForwardResponse object now includes the merchantReference field. To improve test coverage for new features, it's a good practice to add assertions for new fields. In this test, since merchantReference is not set in the CheckoutForwardRequest, we can assert that it's null in the response.

Suggested change

	assertNull(response.getStoredPaymentMethodId()); // card is not tokenized
	assertNull(response.getStoredPaymentMethodId()); // card is not tokenized
	assertNull(response.getMerchantReference());