cancel
Showing results for 
Search instead for 
Did you mean: 

AIM: auth_only - ok >> prio_auth_capture - declined >> void - transaction not found -- !?

My current setup goes like this:

 

AIM:

 - always try to authorize first

 -- if transaction gets declined: void it ..

 -- else capture it

 

And sometimes I have that issue, that I

 - get an authorization

 - BUT the capture gets declined

 - AND then the whole transaction can't not even be voided anymore

 

Here are the logs of such a misserable request-response-orgy:

 


----Request -- first auth_only ----

x_version=3.1&

x_delim_char=%2C&

x_delim_data=TRUE&

x_relay_response=FALSE&

x_encap_char=%7C&

x_amount=238&

x_address=14+Dojostr&

x_zip=65444&

x_first_name=John&

x_last_name=Doe&

x_invoice_num=508245&

x_cust_id=8549&

x_method=echeck&

x_bank_aba_code=121000248&

x_bank_acct_num=12345678&

x_bank_acct_type=checking&

x_bank_name=Bank+of+Earth&

x_bank_acct_name=Hans+ertg+rvf+rfrrf+rw&

x_echeck_type=web&

x_type=AUTH_ONLY&

x_login=**&x_tran_key=**

 

----Response----|1|,|1|,|1|,|This transaction has been approved.|,||,|P|,|2165268608|,|508245|,||,|238.00|,|ECHECK|,|auth_only|,|8549|,|John|,|Doe|,||,|14 Dojostr|,||,||,|65444|,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,|5274CA1D43C1D96E25D286E1FEB0C626|,||,||,||,||,||,||,||,||,||,||,||,||,|XXXX5678|,|Bank Account|,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||

 

----Request -- auth_only approved -- now capture ----

x_version=3.1&

x_delim_char=%2C&

x_delim_data=TRUE&

x_relay_response=FALSE&

x_encap_char=%7C&

x_first_name=John&

x_last_name=Doe&

x_invoice_num=508245&

x_cust_id=8549&

x_trans_id=2165268608&

x_type=PRIOR_AUTH_CAPTURE&

x_login=**&

x_tran_key=**

----Response----|2|,|1|,|2|,|This transaction has been declined.|,||,|P|,|2165268608|,|508245|,||,|238.00|,|ECHECK|,|prior_auth_capture|,|8549|,|John|,|Doe|,||,|14 Dojostr|,||,||,|65444|,||,||,||,||,||,||,||,||,||,||,||,||,|0.00|,|0.00|,|0.00|,|FALSE|,||,|5274CA1D43C1D96E25D286E1FEB0C626|,||,||,||,||,||,||,||,||,||,||,||,||,||,|Bank Account|,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||


----Request -- try to void ----

x_version=3.1&

x_delim_char=%2C&

x_delim_data=TRUE&

x_relay_response=FALSE&

x_encap_char=%7C&

x_method=echeck&

x_trans_id=2165268608&

x_type=VOID&

x_login=**&

x_tran_key=**

 

----Response----|3|,|2|,|16|,|The transaction cannot be found.|,||,|P|,|0|,||,||,|0.00|,|ECHECK|,|void|,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,|1041533EDE3B1D2EFB0755A6AAE45587|,||,||,||,||,||,||,||,||,||,||,||,||,||,|Bank Account|,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||,||

 

What am I missing ?

Why is the capture declined when the authorization was already approved ?

And why can't the declined transaction be found to be voided ?

 

 

abernh
Contributor
3 REPLIES 3

Is there any pattern to this? Does it always happen on certain types of transactions, such a e-check?

TJPride
Expert

I wasn't able to figure one out.

Currently I experience this more with echecks, as the cc transactions get never declined on the test server. But in the live env we have also some cc cases where this happens - not seldom.

 

But even if we'd leave the auth&capture problem aside - why is the transaction not found anymore to be voided ? did I sent wrong values for the void-request?

 

 

If you go into your account, does a transaction with that transaction ID exist? I'm not too familiar with working directly with the XML - seems like there's a lot more scope for something going wrong. I use the PHP API that sits on top of the XML.