Tweet
I’m integrating Authorize.Net Accept Hosted into EspoCRM using a custom public invoice payment entry point.
The payment itself works. I can complete a transaction, and I land on the Authorize.Net receipt page that says “Thank you for your payment.” The problem is that when I click "Continue", nothing happens. There’s no redirect, no error, and the page just stays there.
I’ve confirmed that the transaction is successful in Authorize.Net and the receipt page renders normally. The return URL points to a public EspoCRM entryPoint (?entryPoint=invoicePayment&token=...). When I manually test that return URL in the browser, nginx responds with a 401 because the site is behind basic auth. In EspoCRM logs, I don’t see the return URL being hit at all when Continue is clicked.
This setup is behind nginx, Accept Hosted is running in an iframe, CSP is enabled, and I don’t see any JavaScript errors on the receipt page.
I’m trying to figure out whether a 401 or nginx basic auth on the return/relay URL would cause the Continue button in Accept Hosted to silently fail, or if there’s something else I should be checking in the Accept Hosted or iframe configuration that would explain this behavior.
The payment itself works. I can complete a transaction, and I land on the Authorize.Net receipt page that says “Thank you for your payment.” The problem is that when I click "Continue", nothing happens. There’s no redirect, no error, and the page just stays there.
I’ve confirmed that the transaction is successful in Authorize.Net and the receipt page renders normally. The return URL points to a public EspoCRM entryPoint (?entryPoint=invoicePayment&token=...). When I manually test that return URL in the browser, nginx responds with a 401 because the site is behind basic auth. In EspoCRM logs, I don’t see the return URL being hit at all when Continue is clicked.
This setup is behind nginx, Accept Hosted is running in an iframe, CSP is enabled, and I don’t see any JavaScript errors on the receipt page.
I’m trying to figure out whether a 401 or nginx basic auth on the return/relay URL would cause the Continue button in Accept Hosted to silently fail, or if there’s something else I should be checking in the Accept Hosted or iframe configuration that would explain this behavior.