Support APIs After Sunsetting a Legacy


(Durai) #1

After contacting support team and they were redirected to me here to get more info on the below clarifications.
We had received an email from you about the Sunsetting a Legacy such as, “In December 2018,
Dwolla will no longer support the product, Transfer, that your business has been using to send or receive payments. Dwolla will be removing the ability to sign up new users with this product on October 1, 2018. After December 3, 2018, the ability to use the Transfer product to send or receive payments will be removed entirely”

As per our understanding, transfer product has been introduced in 2017 from dwolla.

However, we have integrated the below API’s in our system to add user funds and those APIs are introduced in our system on April 2014.

  1. https://www.dwolla.com/payment/request
  2. https://www.dwolla.com/payment/checkout/{{CheckoutprocessId}}

It would be greatly helpful for us if you answer for the below clarifications.

  1. What would be the impact on the above APIs?

  2. Is there any relationship between the transfer product (with in Dwolla) vs the above APIs which are used in our applications?

  3. Are above API’s no more valid after removing the transfer product from dwolla?

  4. If there is any relationship, do you have any alternative APIs or product support for the fund transactions?

Please let me know if you need any additional details.

I’m looking your response forward.


(Spencer Hunter) #2

Hi @durairaj, I provided some additional background and information relating to the sunset of our our legacy v1 API in this thread, however I can address your questions specifically and hopefully provide clarification.

It would be greatly helpful for us if you answer for the below clarifications.

  1. What would be the impact on the above APIs?
    The API endpoints you referenced are for our Off-site gateway and Money Requests which exist within our v1 API. Those endpoint will no longer work at the end of the year and are included as part of the sunset of the v1 API.
  2. Is there any relationship between the transfer product (with in Dwolla) vs the above APIs which are used in our applications?
    Yes, the existing Transfer product and those APIs go hand-in-hand.
  3. Are above API’s no more valid after removing the transfer product from dwolla?
    Correct, the wind down of the Transfer product includes the deprecation of our v1 API
  4. If there is any relationship, do you have any alternative APIs or product support for the fund transactions?
    I would take a look at our latest v2 API and relevant documentation if you’re interested in the features and functionality available through leveraging the white labeled Dwolla solution. Referenced in the thread above, an integration with the Dwolla Platform comes with different integration requirements and an overall different payments user experience, which means that the transition from our legacy Transfer solution to the Dwolla platform isn’t one-to-one.

Hope this helps, please let me know if I can provide any additional details or if I misinterpreted any of your questions!


(Durai) #3

Hi @spencer
Thanks for your clarification on this regard. We are keen interest to integrate the latest v2 API’s in our system. Hence, We would like to understand the New API’s and integration steps based on .NET framework.
Do you have any possibility to provide the new integration steps and equivalent v2 API’s for the below legacy calls.

  1. https://www.dwolla.com/payment/request
  2. [https://www.dwolla.com/payment/checkout/{{CheckoutprocessId}]
    Please help us to move forward as soon as possible.
    Thanks