[payout] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the payout 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 payout service models, specifically refining the representation of fraud result types. The changes standardize fraud status indicators and enhance documentation, ensuring the API client accurately reflects the latest Adyen OpenAPI specification for fraud-related data.

Highlights

• Fraud Result Type Constants: The FRAUD_RESULT_TYPE_FRAUD constant has been replaced with FRAUD_RESULT_TYPE_RED, and a new FRAUD_RESULT_TYPE_AMBER constant has been introduced in ResponseAdditionalDataCommon.php.
• Allowable Values Update: The getFraudResultTypeAllowableValues method was updated to include the new AMBER and RED fraud result types, reflecting the constant changes.
• Docblock Clarifications: Docblock comments for fraudResultType and fraudRiskLevel properties were updated to explicitly list possible values, improving clarity for developers.

🧠 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.

Changelog

• src/Adyen/Model/Payout/ResponseAdditionalDataCommon.php
  • Replaced FRAUD_RESULT_TYPE_FRAUD with FRAUD_RESULT_TYPE_RED.
  • Added FRAUD_RESULT_TYPE_AMBER constant.
  • Updated getFraudResultTypeAllowableValues to include AMBER and RED.
  • Modified docblock for fraudResultType to list AMBER, GREEN, RED as possible values.
  • Modified docblock for fraudRiskLevel to explicitly list possible values.

Activity

• This pull request was automatically generated by AdyenAutomationBot to update services and models based on the latest OpenAPI specification.

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 appears to be an automated update to the payout service models, likely generated from a new OpenAPI specification. The main changes involve updating the fraudResultType to use AMBER, GREEN, and RED as possible values, which is a breaking change from the previous GREEN and FRAUD values. Assuming this is intentional to align with the API, my feedback is focused on improving the readability of the generated PHPDoc comments.

[gemini-code-assist]

For better readability, it's recommended to format the list of possible values as a comma-separated list. The current formatting with asterisks between values can be difficult to read.

     * @param string|null $fraudResultType The fraud result properties of the payment. Possible values: AMBER, GREEN, RED

[gemini-code-assist]

For better readability and consistency, it's recommended to format the list of possible values as a comma-separated list. The current formatting with asterisks between values can be difficult to read.

     * @param string|null $fraudRiskLevel The risk level of the transaction as classified by the [machine learning](https://docs.adyen.com/risk-management/configure-your-risk-profile/machine-learning-rules/) fraud risk rule. The risk level indicates the likelihood that a transaction will result in a fraudulent dispute. Possible values: veryLow, low, medium, high, veryHigh

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
100.0% Duplication on New Code

See analysis details on SonarQube Cloud