You need to put your sandbox in live mode so that you get a transaction id. The other half of your solution is accomplished using webhooks. You get the results pinged to your server with a webhook, and when the webhook hits your server you pull out the transaction Id from the json payload. The run the method call.
These things are extremely reliable. My clients production account has never had an issue. I have a remote server I test things on, and it has puny resources. I would hate to fathom how many Iโve tested at this point. Way up in the 100s. The only โfailuresโ Iโve had, are when I have a large list of test orders populated on my orders page and am refreshing the screen trying to catch them when they come in. What happens there is this test account has a limited amount of entry processes, and due to customer data encryption/decryption functions every time I refresh the page when Iโve got a list like that, 100s of Php scripts are ran.
So to make it short, authorize never fails, ever. As long as your server has reasonable uptime you will never miss one. The first one will come in a few seconds. If your server doesnโt respond then there will be more attempts on 3 second intervals, then 3 minutes, and there is a redelivery schedule that goes on for 3 or more days.
I read others comments where they are skeptical or report problems, but thatโs not my experience at all and I highly recommend them. I have a 99%+ success rate with the 1% due to my own actions overwhelming my server because I refresh my orders page too many times too rapidly.
