Payment multiple statuses for transaction success

Payment actions in a business process can now treat several transaction statuses as success instead of a single value. Flows that authorize, capture, or settle over multiple steps no longer stall when the gateway passes through an intermediate status you did not list.

• Set transactionSuccessMode to an array such as CAPTURED, SETTLING, and APPROVED so the action completes when any listed status arrives.
• Keep a single string when one success status is enough; existing blueprints continue to work without changes.
• Set context mode to AUTHORIZE when the underlying transaction should authorize rather than charge; success still follows the statuses you define.