Recently we had an issue where a merchant (we act as a service provider)
had already refunded a transaction via the merchant portal then when
attempting to refund it through our service we encountered error code
55.We had no other way to determine if...
Hello all, We operate as a service provider, rather than a single
merchant. A lot of our merchants are not too tech savvy so asking them
to generate a public key (we're switching almost all merchants to
Accept.JS from AIM) is like pulling teeth most ...
@andreerThen you probably were compromised as well, as there is no way
this is a legitimate domain owned by Authorize.net. Are both of you
possibly running JQuery File Upload (or one of it's derivatives) as
every Tom, Dick and Harriet is targeting si...
Hey RichardH, thanks for accepting my response as the solution. First
and foremost I really like A.net's Accept.js integration method, as well
as the API (only gateway that allows easy validation of merchant
credentials). However maybe on A.net's end...
The reason this occurs is that the `Accept.dispatchData` function
triggers a pre-flight OPTIONS request (we're dealing with CORS here).
This request, on A.net's end, triggers the error response you are
seeing. Why this triggers the pre-flight request...