PONativeAlternativePaymentMethodEvent
Defines native alternative payment lifecycle events.
Inheritors
Types
Event is sent after payment was confirmed to be captured. This is a final event.
Event is sent during the capture stage when the user confirms that they have completed required external action. Implementation proceeds with the actual capture process.
Event is sent when unretryable error occurs. This is a final event.
Event is sent when parameters submission failed and the error is retriable, otherwise expect DidFail event.
Event is sent when user asked to confirm cancellation, e.g. via dialog.
Event indicates that initial data has been loaded successfully. Currently waiting for user input.
Event is sent when parameters were submitted successfully. Inspect the associated value additionalParametersExpected to check whether additional user input is required.
Event is sent when user changes any editable value.
Initial event that is sent prior any other event.
Event is sent just before submitting user input. This is usually a result of a user action, e.g. button press.
Event is sent after all information is collected and implementation is waiting for a PSP to confirm capture. Inspect the associated value additionalActionExpected to check whether user needs to do an additional action(s) outside the application, for example to confirm the operation in their banking app to make capture happen.