This solution details SWP-Checkout customer experiences when the following SWP-Checkout request parameters are used:
- pg_return_url -------------> we will refer to this as the receiving endpoint for the postback
Case I. ( if pg_return_method="Post" ):
Upon approval, the postback will be sent and the customer will be redirected to the receiving endpoint. Upon decline, no postback will be sent. The customer will be redirected to the endpoint specified in the 'pg_cancel_url' request parameter upon click of the 'Abort' button (shown on the Transaction Decline dialog).
Case II, ( if pg_return_method='AsyncPost' ):
Upon approval or decline, the customer will either be first displayed the receipt (upon an approval) or be displayed the Transaction Decline dialog (upon decline). Next, the postback will be sent asynchronously. Lastly, the customer be redirected to the respective endpoints specified in 'pg_continue_url' or 'pg_cancel_url' request parameters upon click of continue (shown on the receipt) or abort (shown on the Transaction Decline dialog) buttons, as appropriate.
More information on the 'pg_return_url', 'pg_return_method', 'pg_continue_url', and 'pg_cancel_url' is available in the SWP-Checkout developer documentation available here: https://www.forte.net/devdocs/pdf/SWP_Integration.pdf. We strongly encourage testing this in the sandbox test environment.