• Toll-free  888-665-8637
  • International  +1 717-220-0012
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

RhinoGroup
#1 Posted : Thursday, February 22, 2018 12:43:18 PM(UTC)
RhinoGroup

Rank: Member

Joined: 7/31/2013(UTC)
Posts: 11

I've been trying to run payment tests against a BVC 2015 cart using the Authorize.net sandbox. I get the same error every time:

[Charge] Warning for order number 1837: Authorize.Net Processing Error: This transaction cannot be processed. [AVS - AVS not applicable for this transaction]

So I upgraded the software to version 2017 because we had an unused 2017 license for this particular domain.

I get the same error message.

I looked into the Authorize.net response message provided by enabling Debug on the payment method and found this response reason code: 265. I looked it up and it means: The transaction was submitted with an invalid Solution ID. So I researched the Solution IDs and found that the sandbox only supports these 3:
AAA100302, AAA100303, and AAA100304

BV is sending this Solution ID in the API request: AAA101341. Obviously, that ID is not in the list.

We need to hit the sandbox site to confirm our TLS 1.2 is working correctly.

Can you help?

Aaron
#2 Posted : Thursday, February 22, 2018 1:12:58 PM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,220
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 138 time(s) in 133 post(s)
This is a bug in BVC 2017 that was resolved in 2018. You would need to alter the code. Also note that test mode/sandbox will only work with a sandbox account; you cannot use a production account in test mode/sandbox.
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
RhinoGroup
#3 Posted : Friday, February 23, 2018 11:17:33 AM(UTC)
RhinoGroup

Rank: Member

Joined: 7/31/2013(UTC)
Posts: 11

I altered and rebuilt the Authorize.Net assembly, using one of the supported sandbox Solution IDs. Processing against the sandbox now works correctly. Thanks!

I think that bug goes all the way back to BV 2015 or earlier.
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

©2018 Develisys. All rights reserved.
  • Toll-free  888-665-8637
  • International  +1 717-220-0012