Renaming & Logic Adjustment for Payment Method Selection

We have updated the payment-method action to enhance clarity and functionality:

Key Changes

• Parameter Renaming: The parameter previously known as restrictDefault has been renamed to defaultSelectionAllowList to better reflect its purpose.
• Logic Adjustment: The functionality has shifted from an exclusion list to an inclusion list. Now, only the payment methods specified in the defaultSelectionAllowList will be considered for default selection in user settings.

Impact

• Default Payment Method Selection: When a business process includes a payment-method action with a defined defaultSelectionAllowList, only the specified payment methods will be eligible for default selection in user settings. If a user's default payment method does not match the allowed list, it will not be set as the default for payment.
• Optional Parameter: The defaultSelectionAllowList parameter is optional. If not provided, all available payment methods may be considered for default selection.
• Validation: When creating a payment-method action, ensure that the values specified in the defaultSelectionAllowList align with the supported payment method types. Invalid entries will result in an error.

For detailed implementation guidance and further information, please refer to our API Documentation.