Feature/add support to all flow endpoints #291
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced AccommodationAddress, AccommodationData, AccommodationGuest, AccommodationRoom, and CustomerSummary classes to manage accommodation-related data. - Enhanced FlightLegDetails class with additional properties for flight information. - Added PartnerCustomerRiskData class for partner-specific risk data. - Updated Passenger and PassengerAddress classes to include more detailed passenger information. - Implemented PaymentCustomerRequest class with tax number and customer summary. - Created PaymentInstruction and PaymentPurpose classes for payment processing. - Revamped ProcessingSettings class to include new fields for payment processing. - Developed PaymentSessionCompleteRequest and PaymentSessionSubmitRequest classes for handling payment session completion and submission. - Added PaymentSessionsClient methods for completing and submitting payment sessions. - Implemented tests for new payment session functionalities, including completion and submission. - Introduced new session classes for ApplePay, GooglePay, and Billing with relevant properties.
armando-rodriguez-cko
approved these changes
Nov 17, 2025
Contributor
armando-rodriguez-cko
left a comment
armando-rodriguez-cko
left a comment
There was a problem hiding this comment.
🥇 Good job
robert-goheen-cko
approved these changes
Nov 17, 2025
Contributor
Author
|
Closed to revisit the files for a best organization |
|
armando-rodriguez-cko
deleted the
feature/add-support-to-all-flow-endpoints
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several new data models and expands existing classes to support enhanced payment processing features, particularly for accommodations, customer summaries, and payment instructions. It also adds detailed configuration options for payment sessions, including Apple Pay and Google Pay, and refines the airline and passenger data structures.
New Data Models and Expanded Payment Data:
AccommodationData,AccommodationAddress,AccommodationGuest, andAccommodationRoom, enabling detailed hotel and guest information to be captured in payments. [1] [2] [3] [4]CustomerSummaryto store customer registration, transaction history, and value metrics, and integrated it intoPaymentCustomerRequest. [1] [2]PartnerCustomerRiskDatafor handling partner-specific risk information, referenced inProcessingSettings. [1] [2]PaymentInstructionandPaymentPurposeclasses to specify and enumerate payment purposes for account funding transactions. [1] [2]Enhancements to Payment Session Configuration:
PaymentMethodConfigurationto include new configuration options for Apple Pay, Google Pay, and stored cards, with corresponding new classes (ApplePay,GooglePay). [1] [2] [3]Cardsession configuration to support storing payment details and account holder data.Billingsession configuration.Refinements to Airline and Passenger Data:
FlightLegDetailswith additional fields (e.g.,class_of_travelling,departure_time,arrival_airport) and improved documentation.Passengerto use separatefirst_name,last_name,date_of_birth, and an address object, with a newPassengerAddressclass for country codes. [1] [2]Major Extension of Processing Settings:
ProcessingSettingswith new fields for discounts, shipping, taxes, invoice and receipt IDs, campaign and order information, airline and accommodation data, risk data, and more, with improved documentation for each property.New data models and payment data:
AccommodationData,AccommodationAddress,AccommodationGuest, andAccommodationRoomclasses to support detailed accommodation payment information. [1] [2] [3] [4]CustomerSummaryand integrated it intoPaymentCustomerRequestfor richer customer profiling. [1] [2]PartnerCustomerRiskDataclass and its usage inProcessingSettingsfor enhanced fraud detection. [1] [2]PaymentInstructionandPaymentPurposeclasses to capture and enumerate payment purposes. [1] [2]Payment session configuration:
PaymentMethodConfigurationto support Apple Pay, Google Pay, and stored card configurations, with new classes for each. [1] [2] [3]CardandBillingsession classes to include account holder and phone information. [1] [2]Airline and passenger data enhancements:
FlightLegDetailsfor more granular flight data.Passengerto use individual name fields and a newPassengerAddressclass. [1] [2]Processing settings extension:
ProcessingSettingsto add support for discounts, taxes, shipping, campaign and order IDs, accommodation and airline data, risk data, and more, with comprehensive property documentation.