Callback and webhook notification sent wrong transaction Id, off by one

  • Problem
  • Updated 2 years ago
I sent money from my personal account (P) to my organization account (O) via the offsite gateway.

Something that surprised me is that apparently two transaction IDs represent every transaction. If I login to the dwolla interface, the organization shows that transaction id is 1346647. If I login with my personal account, the transaction id is 1346648. This seems funky, but I could live with it.
Let me restate who got which id:
O (organization) - 1346647
P (personal) - 1346648

The problem is that the callback and webhook notifications sent to O reference the Id as 1346648. If O's web application uses OAuth to get details of transaction with Id 1346648, it gets an error "Transaction not found for account." Now if I manually tell OAuth to use 1346647 instead (which I only know by logging into O's account via web browser) it works as expected.

Here's O's callback data:
array (
'Amount' => 1,
'OrderId' => '11902',
'Status' => 'Completed',
'Error' => NULL,
'TransactionId' => 1346648,
'CheckoutId' => redacted
'Signature' => redacted
'TestMode' => 'false',
'ClearingDate' => '9/13/2012 6:29:19 AM',
)

O's view from the web browser:


P's view from the web browser:
Photo of Chris Hiestand

Chris Hiestand

  • 36 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Chris Hiestand

Chris Hiestand

  • 36 Posts
  • 0 Reply Likes
Photo of Denver Dash

Denver Dash

  • 1 Post
  • 0 Reply Likes
Yes we have this exact same problem. Has there been no response to this issue? Obviously we can just decrement the order id by 1, but the we are making assumptions about what is happening on Dwolla's end and we may be wrong in some cases. For example, if 2 transactions occur at the same time from different clients, is it possible that the 2 transaction ids will differ by more than 1? It would be very useful if Dwolla could explicate the situation for us.
Photo of Chris Hiestand

Chris Hiestand

  • 36 Posts
  • 0 Reply Likes
The bug has not been fixed or even acknowledged by Dwolla. And please note that the latest link for this issue is: http://stackoverflow.com/questions/13...