CyberSource: Issuing Credits back to a Card


I’ve been working on a system to improve our returns process and ran across a problem using the CyberSource API. Now it may be my eyes missed it, but every credit I issued I was receiving a 102 response code. This normally means “missing required fields,” and the response object contains exactly which fields were missing.



Ah-ha! If I’d only signed in to my testing business center I could have seen what 102 means in this context:

There is a problem processing this request: Original transaction data could not be found in online system-it may have been archived.

102 is a legitimate message, and the accounting office will have to take appropriate action. I’ll put this on the exception report. Additionally, I noticed my testing box was issuing an auth-only – not a capture – so there really really wasn’t anything to credit!