It would make sense that ACL would not have any future updates for a
card, however I am wondering if a card can move from a bad state
(CCH/ACL) to a good state (NAN/NED) over the course of two or more
I am running a request to getAUJobDetailsRequest. The documentation
shows that deletes and updates should be seggregated into arrays
(auDelete and auUpdate) that are held within the auDetails object as
seen below. My actual response does not have the...
Reading through your documentation on the 'Get Account Updater Job
Details' section, in the "Try It" tab with JSON selected, when I look at
the 'Response' section I see that the 'auDelete' key has an object as
the value while the 'auUpdate' has an ar...
From the testing guide I see the following: "The Account Updater process
in the developer sandbox runs at the same frequency as in production
(once per month). Results are available the following month. There is no
function to manually trigger an upd...
Ok, so how do we proceed? Will you be changing the documentation to
reflect the differences in json, or bringing the json response inline
with the XML? My concern here is regression for anyone who has coded to
the current json implementation.
Lets ignore the refId, we are not passing one so we will not get one
back. The "ListOfAUDetailsType" definition shows auUpdate and auDelete
withing the XSD file. What I am saying is our response does not have
these. This XSD seems to be inline with t...
Can we expand on the expected behavior for the provided card numbers?