Jason Judge

I'm not quite sure they have the JSON API quite right yet. The documentation gives examples with fragments in similar to this: ```json "lineItems": { "lineItem": { "itemId": "1", "name":...

Yes, the (estimated) time line for the REST API would be great, with any thoughts on what the API will look like.

The majority of the options are just what Omnipay generically supports across its various drivers. This especially applies to the `card` parameter, or `creditCard` object, which is fixed across all...

I don't believe this driver supports VAT, unfortunately. Most drivers support the cart object that allows a breakdown of payments to be included (and even that does not support VAT...

Did you solve this problem? Is it an erroneous validation check that should perhaps be removed?

From what I remember, the GetTransactionDetails API was a completely different API system that would need some major writing, additional credentials etc. Since then, the Authorize.Net REST API has changed...

@Nks Two quick questions: * What is `$this->gateway_auth`? * Is it always necessary to provide a unique `refId` even for transaction queries?

This gets the last card digits, which is great, but I'm not sure where the expiry date is coming from. I get "199912" every time, regardless of what the actual...

The raw AJS (using opaque data) rtesponse body: ```xml 313826278 Ok I00001 Successful. 1 000000 P 0 1 XXXX0027 Visa 1 This transaction has been approved. 70BADC10C279FD5102EC17DDB18225E46CBD1381C3E06C85976A5727415DA9E6BFAA758ABF15D1B6745D41D18FD355E0AFED8E5E5E7FCD06D34B0216E108EE48 ``` No expiry...

Looking at this example here: https://developer.authorize.net/api/reference/features/acceptjs.html#Integrating_Accept.js_into_Your_Payment_Form the payment form has names for the expiry date fields. That means although the card number (and CVV) are *not* captured direct to the...