After his payment, the customer will be redirected to the url you submitted in the redirect_url variable defined at payment initialization. The return link/url (redirect_url) is called by TransFluo to send the customer back to your site. This url must be available to receive HTTP requests of type GET and POST.
TransFluo adds in parameter the order_id which allows you to identify for which customer the return is done, you can then display a message to your users after their payment to inform them if their payment is successful or not, this is possible since you have the status of the transaction via your webhook url (see previous chapter)
{danger.fa-close} No processing in your database should be done on the redirect url, it should only be used for redirections.
After a payment, your customer is invited to return to your site regardless of the outcome of the transaction. After th customer is automatically redirected back to your site, TransFluo executes a POST type request on your notification url containing:
After obtaining it, you should check your database or contact Checking a transaction to TransFluo to know the status of the payment.
Write the client to the desired pagenote
Some technologies require the user to log in again when they return to your platform.
To avoid this, use themetadata variable at initialization to pass session information.
If your return page displays this page. It is possible that you are facing a 307 redirect which implies that there is a restriction on your server regarding access to the development file, you should lift this restriction on your server. Please contact your web host for more details.
This is the default operation of o2switch hosting. To remove this restriction:
In your O2switch admin panel, find the menu named Generic , then disable the Default Security option.