Skip to content

[checkout] Code generation: update services and models#860

Merged
gcatanese merged 3 commits intomainfrom
sdk-automation/checkout
Jan 26, 2026
Merged

[checkout] Code generation: update services and models#860
gcatanese merged 3 commits intomainfrom
sdk-automation/checkout

Conversation

@AdyenAutomationBot
Copy link
Copy Markdown
Collaborator

@AdyenAutomationBot AdyenAutomationBot commented Jan 13, 2026

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.

Checkout API

Breaking Changes 🛠

A new ShopperName class has been introduced to define the name of the shopper. This change affects the shopperName property in the following classes: CreateCheckoutSessionRequest, CreateCheckoutSessionResponse, DonationPaymentRequest, PaymentRequest.

The property type has been updated from Name to ShopperName.

Migration Steps for PHP

If you were manually creating the Name object for your requests, you must now instantiate the ShopperName model instead:

Before:

$name = new \Adyen\Model\Checkout\Name();
$name->setFirstName("John");
$request->setShopperName($name);

After:

$shopperName = new \Adyen\Model\Checkout\ShopperName();
$shopperName->setFirstName("John");
$request->setShopperName($shopperName);

Enum FRAUD_RESULT_TYPE_FRAUD has been removed from ResponseAdditionalDataCommon

New Features 💎

  • Added support for Checkout Forward stored payment details
  • Added support for UpiQrDetails payment method
  • Added the SdkData property to all payment methods (i.e. AchDetails, etc..)
  • Added attributes billingSequenceNumber and encryptedPassword in CardDetails, CardDonations, CheckoutPaymentMethod
  • Added attributes bankCode and branchCode in CheckoutBankTransferAction, CheckoutBankTransferAction, PaymentResponseAction
  • Added attribute levelTwoThree to EnhancedSchemeData
  • Added enum prepaid In ApplePayDonations, CardDetails, CardDonations, PaymentMethod, VisaCheckoutDetails
  • Added attributes paymentValidations and shopperTaxInfo in PaymentRequest
  • Added attribute paymentValidations in PaymentResponse
  • Added new contract types (EXTERNAL and ONECLICK,RECURRING) to the ContractEnum in Recurring
  • Added attribute sepadirectdebitSepadirectdebitDueDate in ResponseAdditionalDataSepa
  • Added ResponseAdditionalDataSwish class
  • Added attribute dueDate to SepaDirectDebitDetails
  • Added attribute mandate to StoredPaymentMethodResource
  • Added attribute billingSequenceNumber to UpiIntentDetails
  • Added attributes recurringDetailReference, storedPaymentMethodId in WeChatPayMiniProgramDetails

@AdyenAutomationBot AdyenAutomationBot requested review from a team as code owners January 13, 2026 14:59
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @AdyenAutomationBot, I'm Gemini Code Assist1! 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 updates the checkout service by integrating new models and services generated from an updated OpenAPI specification. The changes primarily focus on enhancing payment method details, introducing new functionalities for forwarding payment requests, and improving data structures for enhanced scheme data and payment validations. These automated updates ensure the API client remains synchronized with the latest platform capabilities.

Highlights

  • New SDK Data Field: A new 'sdkData' field has been introduced across numerous payment method detail models (e.g., AchDetails, AffirmDetails, AfterpayDetails, AmazonPayDetails, AncvDetails, AndroidPayDetails, BacsDirectDebitDetails, BillDeskDetails, BlikDetails, CellulantDetails, DokuDetails, EBankingFinlandDetails, EcontextVoucherDetails, EftDetails, FastlaneDetails, GenericIssuerPaymentMethodDetails, GooglePayDetails, GooglePayDonations, IdealDetails, IdealDonations, KlarnaDetails, MasterpassDetails, MbwayDetails, MobilePayDetails, MolPayDetails, OpenInvoiceDetails, PayByBankAISDirectDebitDetails, PayByBankDetails, PayPalDetails, PayPayDetails, PayToDetails, PayUUpiDetails, PixDetails, PseDetails, RakutenPayDetails, RatepayDetails, SamsungPayDetails, SepaDirectDebitDetails, StoredPaymentMethodDetails, TwintDetails, UpiCollectDetails, UpiIntentDetails, VippsDetails, VisaCheckoutDetails, WeChatPayDetails, WeChatPayMiniProgramDetails, ZipDetails) to accommodate Base64-encoded JSON objects containing SDK-related parameters.
  • Enhanced Card Details: The 'CardDetails' and 'CardDonations' models now include 'billingSequenceNumber' and 'encryptedPassword' fields, expanding the data captured for card transactions.
  • New Payment Validations Feature: New models and fields have been added to support payment validations, including 'PaymentValidations', 'PaymentValidationsNameRequest', 'PaymentValidationsNameResultRawResponse', and 'PaymentValidationsNameResultResponse', enabling name validation checks against cardholder data.
  • New Forwarding API: A new 'forward' method has been added to the RecurringApi, along with supporting models like 'CheckoutForwardRequest', 'CheckoutForwardRequestCard', 'CheckoutForwardRequestOptions', 'CheckoutForwardResponse', 'CheckoutForwardResponseFromUrl', and 'CheckoutOutgoingForwardRequest', to facilitate forwarding stored payment details to third parties.
  • Expanded Enhanced Scheme Data: The 'EnhancedSchemeData' model now includes a 'levelTwoThree' field, which further details item-level data, including 'ItemDetailLine' and 'Destination' models, for improved Level 2/3 data reporting.
  • Updated Payment Method Types: Several payment method types have been added or removed in 'PaymentDetails.php', such as the addition of 'bankTransfer', 'iris', 'onlinebanking_IN', and the removal of 'upi_qr', 'neteller', and 'moneybookers'.
  • Recurring Contract Types: New contract types 'ONECLICK,RECURRING' and 'EXTERNAL' have been added to the 'Recurring' model, providing more flexibility for recurring payment setups.

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

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a number of automated changes from the OpenAPI specification, including adding new models and updating existing ones. The changes primarily involve adding sdkData to various payment detail models, introducing new payment method details, and updating documentation. I've noticed a potential naming issue in ResponseAdditionalDataSepa.php which could be a typo in the OpenAPI specification or the generator. Please see the specific comment for details.

Comment thread src/Adyen/Model/Checkout/ResponseAdditionalDataSepa.php
@AdyenAutomationBot AdyenAutomationBot force-pushed the sdk-automation/checkout branch 4 times, most recently from 4f130d2 to db095aa Compare January 16, 2026 12:55
@AdyenAutomationBot AdyenAutomationBot force-pushed the sdk-automation/checkout branch 2 times, most recently from 6cf9754 to b985dd1 Compare January 26, 2026 09:45
@gcatanese gcatanese added the breaking change Introduces a breaking API change (correlating with MAJOR in Semantic Versioning) label Jan 26, 2026
@gcatanese gcatanese enabled auto-merge January 26, 2026 20:05
@gcatanese gcatanese added this pull request to the merge queue Jan 26, 2026
@sonarqubecloud
Copy link
Copy Markdown

Merged via the queue into main with commit 580fb4d Jan 26, 2026
9 checks passed
@gcatanese gcatanese deleted the sdk-automation/checkout branch January 26, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking change Introduces a breaking API change (correlating with MAJOR in Semantic Versioning)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants