Post-Payment Redirection URLs

when a user interacts with the asperato payment page, you can control where they are redirected after the payment process how it works asperato supports redirection based on three distinct outcomes; success payment completed successfully failure payment was unsuccessful cancellation the customer exited the payment page without completing or attempting payment for each of these scenarios, you can configure a specific url to which the customer will be redirected configure redirection urls set the following fields on your payment object to define the redirection urls success endpoint success url users are redirected here after a successful payment fail endpoint failure url users are redirected here after a failed payment cancel endpoint cancellation url users are redirected here if they cancel the payment process these fields directly determine the destination url for each outcome important considerations for endpoints individual record configuration redirection urls are configured at the individual payment or authorisation record level best practice utilize salesforce process builder or workflow rules for automated endpoint configuration manual setting is also possible if needed ecommerce url trigger redirection to these configured urls only occurs when processing payments via the ecommerce url payments processed directly within the asperato application will not trigger these redirections optional direct redirection to bypass the standard asperato confirmation screens and redirect users directly to your specified endpoints, please contact the asperato support team iframe implementations standard url redirection is not supported when the asperato paypage is embedded in an iframe for iframes, use postmessages for communication and redirection handling update (asperato one v2 19+) asperato one v2 19 and later versions introduce the ability to configure default endpoints for authorisations and payments refer to the release notes for detailed information on setting up default endpoints after a user has loaded the paypage, they may exit the payment page in three different scenarios having successfully completed the transaction, having unsuccessfully completed the transaction, and having cancelled (not attempted) the transaction asperato can send the user to different urls for each of these three separate scenarios these urls can be set by changing the value of fields on the payment object these fields are success endpoint , fail endpoint , and cancel endpoint , and control the url where a user will be sent in these three scenarios update starting from asperato one v2 19 it is possible to set up default endpoints for authorisations & payments, as described in release notes here https //payonomy freshdesk com/support/solutions/articles/43000676902 asperato release notes 2 19 summer 2022 #default settings for payment page navigation endpoint considerations endpoints need to be set on individual payment/authorisation records this can be done manually, or more likely, in practice, via a salesforce process builder/workflow redirection to endpoints will apply when payment/authorisations are processed via the ecommerce url only, they do not apply when payments/authorisations are processed from within the asperato application it is possible to automatically advance straight to the endpoints without displaying the standard asperato screens please contact the asperato team to request this redirection to endpoints will not take effect when the asperato paypage is iframed postmessages should be used with iframes