[payment] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the payment 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, automatically generated by AdyenAutomationBot, updates the payment service models and typings. The changes introduce new functionalities such as a 'Prepaid' funding source and a SEPA Direct Debit due date field, alongside an expanded 'Surcharge' split type. Additionally, descriptions for localized shopper statements and amount properties have been refined for improved clarity and accuracy.

Highlights

• New Funding Source: The FundingSourceEnum in PaymentRequest now includes a Prepaid option, expanding the types of funding sources that can be specified.
• SEPA Direct Debit Due Date: A new field, sepadirectdebit_sepadirectdebit_dueDate, has been added to ResponseAdditionalDataSepa to provide information about the date a shopper's bank account is charged.
• Enhanced Shopper Statement Details: The description for localizedShopperStatement across PaymentRequest, PaymentRequest3d, and PaymentRequest3ds2 has been updated to clarify supported card types (Visa, Mastercard, JCB, Diners, Discover) and character sets (Hiragana, Katakana, Kanji, alphanumeric).
• New Split Type: The Split model now includes Surcharge as a possible type for Balance Platform integrations, along with an updated and clarified description for various split types.
• Documentation Improvements: Minor clarifications were made to the descriptions for currency and value in the Amount model, and a link for UNSPSC commodity codes was updated in additionalDataLevel23.ts.

🧠 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 PR appears to be an automated code generation task to update services and models based on OpenAPI specifications. The changes mostly involve documentation updates, adding new enum values, and introducing new properties, which is consistent with an API update. My review focuses on the correctness and consistency of these generated changes. I've found a potential naming issue and a typo in src/typings/payment/responseAdditionalDataSepa.ts which I've detailed in the comments.

[gemini-code-assist]

The property name sepadirectdebit_sepadirectdebit_dueDate seems to have a redundant sepadirectdebit_ prefix. To maintain consistency with other properties in this class, it should probably be sepadirectdebit_dueDate.

Additionally, there is a typo in the comment on line 21 ('the the').

Suggested change

	* The date that the the shopper\'s bank account is charged.
	*/
	"sepadirectdebit_sepadirectdebit_dueDate"?: string;
	* The date that the shopper's bank account is charged.
	*/
	"sepadirectdebit_dueDate"?: string;

[gemini-code-assist]

To align with the suggested fix for the property name, the name and baseName here should also be corrected to remove the duplicated sepadirectdebit part.

Suggested change

	"name": "sepadirectdebit_sepadirectdebit_dueDate",
	"baseName": "sepadirectdebit.sepadirectdebit.dueDate",
	"name": "sepadirectdebit_dueDate",
	"baseName": "sepadirectdebit.dueDate",