Jason Judge

Some details here: http://developer.authorize.net/api/reference/features/acceptjs.html If I understand it correctly, the AcceptJS interface sits in the web client only and just tokenises card details using AJAX. Those tokens can then be...

Hi @Mark-H we'll get some example code together and get you working. I use the DPM API mostly, which POSTs direct to the gateway, and has a "nofify" redirect to...

I'm hoping that once we work out the front end, you can then just use AIM for the back end, but using the tokenised card rather than the original card...

Looks great :-) This is where I wish we had different payment types - card, tokenisedCard, PayPal, blank account, ApplePay, saved card etc. that could handle all these things invisibly....

Okay, agreed `setDataDescriptor` and `setDataValue` as *gateway-specific* setters. That would be a starting point and offer flexibility for other payment sources that we don't cater for now. There is a...

I've been trying similar front end code to yours, but always get error: > E_WC_15:An error occurred during processing. Please try again. The docs say that means: > Please provide...

Silly me - I was using my account login ID instead of the API login ID. Works fine now after swapping that over. The error message was a little misleading....

Something has always bothered me about these submit handlers. Here, the submit is caught, the card is tokenised, and the handler getting the token response puts the result into the...

Just a thought: the tokenised card consists of two strings, e.g.: ```php array(3) { ["dataDescriptor"]=> string(27) "COMMON.ACCEPT.INAPP.PAYMENT" ["dataValue"]=> string(22) "9487554895312816104603" } ``` As well as accepting them as two separate...

@Mark-H If you would like to submit a PR for the set/get methods, preferably with a test, that would be very useful. If not, I'll do one, since it's a...