This is what happens: When a user in our client's platform purchases a course and uses authorize.net as a payment method, they get kicked out of the platform, and when they log in, the platform shows them that they have purchased the course successfully.
This is what we discovered:
We are sending the proper relay url, and authorize keeps returning the to the default one set on their side. That is why it appears that the user is not logged in, because the user is redirected to the original domain instead (the client uses a custom domain) of the custom one and he is not logged in the original one . This is a known issue I have tested by changing the Default Relay Response URL to the desired one and it works, but it will only redirect to it, and not to the one we send.
