no data in x_SHA2_Hash when using Silent Post

[desiminr61]

I've created a Signature Key but there is no data in x_SHA2_Hash when using Silent Post.

What is required to get the x_SHA2_Hash field to be populated?

[MinneSnowtain]

Try it again!  I just returned to look at this again and without changing my code my hashed result is matching sandbox's hashed return..I must have had a gremlin last night.

[ilyas]

No such luck for me

[Renaissance]

@MinneSnowtain

Good deal! It seemed funny. Apologies for underestimating you if I came across that way. I help all kinds of people on here and a lot, maybe even a majority, are at a lesser skill level. Quite often it is someone who specializes more in operations of their store than they do in writing code. So I never know what to expect. If you see me on the AWS forum you can probably help me! I am doing great so far, but am new to them. Moving all my clients from a rather terrible hosting company whose name I will not mention. AWS is everything I cracked it out to be and I wish I would have switched sooner. I’m preaching their gospel to everyone I meet in the development space (also trash talking the old provider)

[Renaissance]

@ilyas

I’ll look at your hash at some point. Quite possibly can help you. You are using what programming language?

[ilyas]

@Renaissance , thank you so much. I am using C#.

[kabutotx]

@ilyas 

Your hash is the correct hash for that string.  So your return string is not what Auth is seeing to get a different hash.

[ilyas]

@Renaissance  and @kabutotx , 

I modified my sandbox so it is in live mode so it can generate non-zero transaction id. 

So my new text before hash is 

^40026012469^false^1^NC786I^P^2^Y^CC^XXXX1111^200.00^^^^^^^^^^^^^^^^^^^^^

My signature key

66AEDE64761DE2ED2843C0CB6C5D9736C277B58E5F6556F05615175CC17EF6D51B8B9E447BF590CCF0CDAAD69EDB4BA0E59BF24E7461BC0563B7E408BC57BF44

My generated hash

8C5895709E2014BD8BC6854CB045C3336C101FC90451ACE41DFD5D0EF048C359AB9E7DD231AC9E6555EC26CD9835F0C7A28E3FA779F4AFACA1ECABB2E4AB2D18

x_SHA2_Hash

87C6B757903FE517CCEDAC32395348E86D4CEBE14B2916DB4BF565435046489A1DD7F6503630E112D998937BA531A9B756DD5B675E6D47785485B618DDF36C60

Post parameters from Auth (I removed some custom parameters with sensitive data)

x_response_code=1&x_response_reason_code=1&x_response_reason_text=This+transaction+has+been+approved%2E&x_avs_code=Y&x_auth_code=NC786I&x_trans_id=40026012469&x_method=CC&x_card_type=Visa&x_account_number=XXXX1111&x_first_name=&x_last_name=&x_company=&x_address=&x_city=&x_state=&x_zip=&x_country=&x_phone=&x_fax=&x_email=&x_invoice_num=&x_description=A+Payment+Form&x_type=auth%5Fcapture&x_cust_id=&x_ship_to_first_name=&x_ship_to_last_name=&x_ship_to_company=&x_ship_to_address=&x_ship_to_city=&x_ship_to_state=&x_ship_to_zip=&x_ship_to_country=&x_amount=200%2E00&x_tax=0%2E00&x_duty=0%2E00&x_freight=0%2E00&x_tax_exempt=FALSE&x_po_num=HNM%2DXXC5%2DJ33S7&x_MD5_Hash=503C6FF615B1CB9B56BD62B3881C52CA&x_SHA2_Hash=87C6B757903FE517CCEDAC32395348E86D4CEBE14B2916DB4BF565435046489A1DD7F6503630E112D998937BA531A9B756DD5B675E6D47785485B618DDF36C60&x_cvv2_resp_code=P&x_cavv_response=2&x_test_request=false&currentQueryString=&order_id=b1d87fc8%2Dd22f%2D4cbb%2Da05f%2D82cfa5f67204&x_method_available=true

[Renaissance]

@ilyas 

I think you need to get a new signature key. I think you are using the wrong one. I just ran this and I get your exact same string and your exact same hash. Try generating a new signature key and using it in a new transaction.  The only way you are doing anything wrong here is if the data you removed belongs to one of the 30 fields used in the hash. All the fields are there, so unlesss you removed the value for one of those everything here is exactly right. 

[kabutotx]

I have to agree with @Renaissance 

Do note the amount.  You post 200%2E00 in the dump which is different than 200.00 and gives a different hash.  Watch for any special characters.

[ilyas]

@Renaissance  and @kabutotx , thank you for trying to help me out. This is the second signature key I generated. I will try to generate a new one tomorrow. Personally I don't think that signature key is the issue since I am successfully able to generate fingerprint using very same key. Maybe there is something about my sandbox. As far as amount in the dump (200%2E00) being different from one in prehashed text (200.00). I also don't think this is an issue as one (200%2E00) is simply url encoded representation of the other (200.00). Or are you saying that auth hashing url encoded (rather than actual) values? Thanks again.