You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Payment request submitted twice to Authorize.net and money is also deducted twice from credit card
This issue was not happening very frequently, but it happens once last week on Production Environment
Expected Behavior
Payment request to authorize.net should be submitted once for one Order.
Only one record must be created in Spree::Payment with state: "completed" , cvv_response_code: "M" and avs_response: "Y"
Actual Behavior
Payment request to authorize.net is getting submitted twice and succeded as well.
Money is deducted from credit card twice with same amount
2 Invoices are created on Authorize.net with same Transaction Id prefix(i.e. Invoice no in Spree)
2 records are created in spree_payments table with different number
Time difference b/w 2 records and transaction is just 1 sec.
Possible Fix
We have faced the similar issue years back on lower version of spree and applied this patch which fixed it. But in the newer version this code is already there so there must be some different issue but just for the reference please check the patch details below, It might help because the issue is similar.
Patch:
Steps to Reproduce
Unable to reproduce on any Environment, Including Production
Context : -
Payment request submitted twice to Authorize.net and money is also deducted twice from credit card
This issue was not happening very frequently, but it happens once last week on Production Environment
Expected Behavior
state: "completed"
,cvv_response_code: "M"
andavs_response: "Y"
Actual Behavior
Possible Fix
We have faced the similar issue years back on lower version of spree and applied this patch which fixed it. But in the newer version this code is already there so there must be some different issue but just for the reference please check the patch details below, It might help because the issue is similar.
Patch:
Steps to Reproduce
Environment & Version
Environment: Production
Version used:
Gemfile:-
Gemfile.lock
Any relevant stack traces ("Full trace" preferred):
Did not found any traces becasue both the transaction are succedeed.
The text was updated successfully, but these errors were encountered: