Added #

• Introduces the PortoneErrorHandler class to provide a flexible way to handle error callbacks.
• Added _redirectedUrls to track redirected URLs during WebView navigation. This list is used to generate a stack trace if an error occurs, providing a history of navigation events leading to the error.

Changed #

• Modified the onError parameter in the PortonePayment constructor to accept a PortoneErrorHandler instance.
• Ensured that errors originating from the PortOne SDK, WebView errors, and navigation errors include stack traces when invoking the error callback.
• Introduced the _handleError method to centralize error reporting, ensuring that both the error object and a stack trace (either the current stack trace or one generated from _redirectedUrls) are consistently passed to the widget.onError callback.
• Added null safety check for url in shouldOverrideUrlLoading to prevent errors when the URL is null.

Added #

• Added onReceivedError callback to capture and propagate WebResourceError objects via the widget.onError handler.
• Added onReceivedHttpError callback to capture and propagate WebResourceResponse objects via the widget.onError handler.

Changed #

• Modified payment data processing to directly include the appScheme in the payment data map.
• Removed the conditional logic for setting retAppScheme specifically for Toss Payments, as it's no longer required.
• Updated paymentData to be a mutable map to allow modification.

• Added portone_flutter_v2.podspec for CocoaPods integration.
• Created PrivacyInfo.xcprivacy to declare the app's privacy practices.
• Added ios/Runner.xcodeproj/project.pbxproj to unmanaged files in .metadata to prevent template overwrites.

Added #

• Updated the supported payment methods section in the README to reflect the new PG Company specific support.
• Enable the Android plugin so that the app has the schema without modifying the manifest separately, and declare the external app schema (including <queries> for package visibility) in the plugin manifest.

Added #

• Added pg field to the PaymentRequest model, accepting a PGCompany enum to specify the payment gateway.
• Updated the PaymentRequest.fromJson factory method to handle the new pg field.
• Added PGCompany enum to represent supported PG companies.
• Added conditional logic to include the retAppScheme parameter when using the Tosspayments PG for redirect handling.

Changed #

• Introduced validation in the PaymentRequest constructor to ensure the selected payMethod is supported by the specified PGCompany.
• Throws an ArgumentError when an unsupported payMethod is provided, with a clear error message listing the supported methods.
• Added unit tests verifying that an ArgumentError is thrown for unsupported payMethod cases and that object creation succeeds for supported cases.
• Removed includeToJson: false annotation from the pg field in the PaymentRequest model. (If still present, please remove.)

Added #

• Added unit tests for most of model classes

Changed #

• Exposes the PortonePaymentState class as public and adds comprehensive documentation to facilitate testing and improve understanding of the payment process.
• Sets a default redirectUrl in the paymentData if it is null.
• Adds retAppScheme to the paymentData for compatibility with Tosspayments' TossPay, as it requires this parameter.

Added #

• Added PaymentCurrency enum with support for a wide range of currencies based on ISO 4217.
• Added Missing documentation for all public members to improve code readability and maintainability.

Changed #

• Translated the CHANGELOG from Korean to English.
• Converted enum values in CashReceiptTradeOption to snake case for consistency.

Added #

• Initial integration of PortOne V2 payment service
• Implementation of payment process using the PortonePayment widget
• Support for multiple payment methods (credit card, virtual account, easy-pay, etc.)
• Implementation of payment request model (PaymentRequest) and payment response model (PaymentResponse)
• Added PGCompany enumeration to support various PG companies
• Added PaymentSupportedMethods extension for checking supported payment methods per PG company
• Functionality for handling payment callbacks via app schemes
• Option to configure payment window type (iframe, popup)
• Multilingual support (Korean, English)
• Localization support for PG company names
• Support for multiple currencies (according to the ISO 4217 standard)
• Support for country information (according to the ISO 3166-1 alpha-2 standard)
• Added bypass parameter support for each PG company:
  • e.g., KakaoPay, Toss Payments, Toss Pay V2, KSNET, Smartro V2, Naver Pay, etc.
• Support for transmitting additional information such as custom data, store information, and shipping address
• Error handling and logging functionality

Changed #

• Renamed class from PortOnePayment to PortonePayment for consistency

Fixed #

• Improved handling of intent URL processing
• Improved payment response processing via app scheme
• Modified field type in PaymentRequest model (changed isEscrow to nullable)
• Changed paypal to convenienceStore in the PaymentPayMethod enumeration