We've found that using Accept.js (JSON flavor) works just fine for
single transactions. Reccing transactions, however, present a problem.
We initially had our recurring transaction "start date" set to the same
day as the initial transaction, hoping t...
Hello, I'm updating an old piece of code that used to post form values
directly to the authorize.net API using curl. It still works perfectly
in the original form! I would like to update this old form to use
accept.js, and so far I've gotten to the p...
Back to the point: I've reset `trialOccurrences` back to zero, and am
trying to test. It works great on my local site, while connecting to the
sandbox server. On the production server, with a live account, I'm
getting the same E00114: Invalid OTS Tok...
I'm having the same issue: only on our production site (not on the
sandbox server) and only in live mode. I've implemented the recommended
delay of up to 20 seconds, but still the E00114: Invalid OTS Token error
persists. Is there still an bug that n...
I've looked into the recommended approach, and it seems unnecessarily
complex. If setting up a single transaction is three steps, why can't a
recurring transaction also be three steps? This is especailly
frustrating because it's the EXACT same custom...
> If this is for your production account It is. > please open a support
case and ask for escalation. Where do I do that? (I do not have access
to the AuthNet account as I am only the developer - not the account
owner. Do I need that?) > ARB does not ...
Yes, that's correct. The creation of the customer profile succeeds
immediately, but the first attempt at recurring charge fails. That first
failure happens whether the charge is scheduled for the same day, the
next day (tommorrow) and also 2 days lat...