So the XML-based API is supposed to be ready for prime time and that's
what we should be using for new development? I could be up for that and
for retrofitting it, BUT... I was more than a little surprised when
installing per instructions put almost ...
One other correction to what I wrote about mutual exclusions: I dug into
the schema and found there are no mutual exclusions, only a required
order of elements, most of which are optional. Those can look like
mutual exclusions if you don't know the o...
Also, although the schema requires an expiration date with the credit
card, it appears the processing logic for refunds accepts any future
date, i.e. does not validate the expiration against the card. I don't
know if that's universally true, but it w...
OK, the bottom line is that refunds were failing in the live environment
(after succeeding in the sandbox) based non-intuitively on account
settings under: Account | Settings | Payment Form | Form Fields and the
"Required" column ...even though we do...
PS In any case, I can't store the full card number or the card code
(storing expiration is permitted without full card number), so I'll
either need a solution where I can initiate a refund using last4 (or
none), or I'll have to tell the client they c...
Thanks for getting back so quickly, Richard. Removing the payment
element results in: E00027...Credit card number
is required. Providing full payment information and removing
refTransId results in: E00027...A valid
referenced transaction ID is requir...