feat: new endpoint payment setups support

[david-ruiz-cko]

This pull request introduces significant new functionality to support payment setups in the Checkout API, including the addition of new client classes, data models, and enhancements to existing payment and industry data structures. The main focus is on expanding the API's support for more complex payment setup scenarios, such as customer details, industry-specific data, and a variety of payment methods.

Key changes include:

Payment Setups Client Integration

• Added the PaymentSetupsClient to the CheckoutApi, including initialization, property, and a public getter method to provide access to payment setup operations. (lib/Checkout/CheckoutApi.php) [1] [2] [3] [4]

New Data Models for Payment Setups

• Introduced comprehensive new classes under lib/Checkout/Payments/Setups/Common/, including models for customer details (Customer, Device, Email, MerchantAccount), order information (Order, OrderSubMerchant), industry-specific data (Industry, AirlineData), and payment methods (PaymentMethods, Klarna, Stcpay, Tabby, Bizum, and related option/action classes). These models support richer data capture for payment setups. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]

Enhancements to Existing Payment and Industry Data

• Modified the FlightLegDetails class to use a DateTime object for the departure_date property, improving type safety and consistency for date handling. [1] [2]
• Updated imports in payment destination classes to support new account holder details.

These changes collectively enhance the flexibility and capability of the Checkout API for handling advanced payment setup scenarios, industry-specific requirements, and a broader range of payment methods.

[sonarqubecloud]

Quality Gate passed

Issues
32 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud