Hi people,
We're trying to integrate Authorize.net into our software (a Rails app) but are coming across so many issues. Our app already integrates with half a dozen other payment providers, so we're fairly familar with the basics of payment processing. We're just _really_ struggling with Authorize.net,mainly down to the documentation I think. I've spent hours already trawling through the docs for answers to all the questions below. Any answers to any of the following would be appreciated greatly:
1) Is there a specific tool for testing webhooks? Other payment providers we've used have tools to form and fire webhook calls.
2) Is there a log of webhook calls I can see from the sandbox interface?
3) I've seen people talking about calls to https://apitest.authorize.net/rest/v1/notifications and suchlike as a means of listing webhook calls that have been sent, but...
3.a) I can't find any documentation for that stuff.
3.b) When I tried the Postman pack on GitHub and made the call I got a bunch of records back that bore no resemblance to any test transactions I'd ever made.
4) Should transactions I trigger from our app via the getHostedPaymentPageRequest call and then a redirect, trigger webhook calls upon completion?
5) If I'm using the getHostedPaymentPageRequest and redirect method, am I right in thinking that it's then completely impossible to ever find out the transaction id without having code that downloads all transactions and looking for one that matches in some way?
6) How do eCheck's payments work with regards to getting back a transaction id?
7) Does the system send webhook notifications as eChecks progress through the system?
8) Am I right in that the sandbox still has no support for testing eChecks?
9) What kind of timescale are we generally talking about between a payment being made and a webhook hitting our servers? Seconds, hours, days?
10) I'm making test transactions from our app, getting to the success / thankyou page after entering card details, returning to our website, then checking in the sandbox for transactions and seeing nothing - is that right?
I could go on, but that's enough for now. :-)
09-17-2019 07:45 AM
This really captures the frustration that comes with integrating a payment provider when the documentation doesn’t quite line up with real-world use cases. When you’re already familiar with other gateways, hitting these kinds of gaps can slow everything down and make simple things feel unnecessarily complex. It’s similar to how users search for quick answers or alternatives online like https://lightroom-modapk.com/ but in technical integrations especially, clearer docs and better tooling can save hours of trial and error.
01-15-2026 11:38 AM - edited 01-15-2026 11:40 AM