Cancelling transaction returning 400 status

API Support
1

We started noticing that your API is returning 400 bad requests when attempting to cancel a transaction.

We are calling api.dwolla.com/transfers/{transfer_id}

“errors”:[{“code”:“NotAllowed”,“message”:“Status not allowed.”,“path”:"/status","_links":{}}]}

This started happening on May 28th and was working before that date. We are cancelling transfers like described here: https://docs.dwolla.com/#cancel-a-transfer

1 Like
2

Hi @normrider, I wonder if this transaction has already exported. Transfers are only cancellable before they have been exported at the standard timing of 4pm CT every business day.

One way to determine if a transfer has been exported or not is to retrieve the transfer via the API, and look for a cancel link in the response body. The presence of the cancel link means that the transfer hasn’t exported, and thus can be cancelled. The absence of the cancel link denotes that the transfer has exported, and cannot be cancelled.

If the transfer has already been exported, the only way to nullify it would be to wait for the funds to clear, and then re-initiate the transfer back to the source. I hope that helps, let me know if you have any questions!

EDIT: Added timezone.

3

Hi @shreya, I understand the timing of 4pm but I would like to know the timezone as well to provide more context on this.

Thanks

4

Oops! I meant to write 4:00pm CT!

Thanks @brijeshbhakta30!

1 Like
5

Additionally, this is still an issue in the Dwolla Sandbox Dashboard. My use case is, I have created a mass payment for x2 customers in Dwolla. All aok. I cancel one of the pending payments from the Dwolla dashboard in order to trigger events and ensure that the payment is correctly handled back inside my application for future processing.

As a test I decided to cancel the 2 pending payment via the dashboard, but the modal dialogue seemed to just hang. Inspecting the console, I could see that the ajax request was returning a 400 Status not allowed in the response.

This has nothing to do with 4pm, as the pending payments were cancelled one after the other. Does this mean that the payments are being exported on the first cancel which forces the 2nd to fail? I figure I should be able to cancel a payment from the Dwolla dashboard. Any help appreciated - thanks

6

Hi @syngency team – this seems to be bug. Thanks for reporting! I am able to recreate this in the Sandbox Dashboard as well as via the API. The cancel link is present, but the transfer isn’t cancellable.

Thanks for reporting this! The expected behavior would be for a transfer to be cancellable if there is a cancel link present in the resources.

I’ll be creating a ticket for our dev team to take a look!

1 Like