Stored Payment API?

  • Resolved ariom

    (@ariom)


    11 years, 10 months ago

    I’ve used this plugin a few times before and I must it’s pretty AWESOME. However I’ve now been challenged to use this plugin with the eWay Stored Payment API.

    Basically it’s the same as the Direct Payment API except the merchant has to log into eWay to manually approve the transaction. From what I understand the details sent to eWay are the same, with the exception of the eWay URL and the ewayCVN field (eWay doesn’t need it for Stored Transactions).

    Without modifying the plugin directly, is there a way we can hook into the plugin to change the payment URL? If we have to, we can modify it.

    https://www.ads-software.com/extend/plugins/gravityforms-eway/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author webaware

    (@webaware)

    I can’t see anything called Stored Payments. Are you talking about Token Payments? That really isn’t the same as Direct Payments, as it has quite different data packets (and more of them – it splits the Customer from the Payment) to send to eWAY. Basically, it’s a whole new module added to what’s already there.

    Feel free to fork this plugin and add to it, it’s GPL code so no worries there. If you need, I can write the new modules under contract (I did that for recurring payments).

    At some point in the future, probably this year, I’ll be further developing this plugin (or writing a new one) to support eWAY’s Rapid API, which incorporates Token Payments, Beagle alerts and 3D Secure. But not this month ??

    Thread Starter ariom

    (@ariom)

    Thanks for the fast response. This is the API I’m talking about: https://www.eway.com.au/developers/api/stored-(xml)

    As I mentioned I don’t see any major difference between this API and the Direct Payment API. I know that might be a question for eWay itself (thats fine, I’ve already been in contact with them).

    I’m hoping the only change is what is sent to eWay and the URL it’s sent to, therefore I can continue to use this awesomesauce plugin for this particular project.

    Any ideas?

    Plugin Author webaware

    (@webaware)

    Interesting, that one isn’t listed on the Partner Portal with the other APIs, but there is sample code there for it. I’ll have to look at it and get back to you, it might be as simple as adding a new option to the plugin (which means maybe this week!)

    cheers,
    Ross

    Thread Starter ariom

    (@ariom)

    That would be great. I’ll keep an eye out for an update on this. Thanks Ross.

    Plugin Author webaware

    (@webaware)

    @ariom: please download and test this alpha release. I’ve added support for Stored Payments, but please note that eWAY do not have sandbox support for Stored Payments so you can only test this against a live account! Given that the payments don’t go through until the merchant says so, that’s probably OK, but still not brilliant.

    Let me know if this meets requirements, and I’ll release it.

    cheers,
    Ross

    Thread Starter ariom

    (@ariom)

    I can confirm that worked brilliantly. We tested with a couple of $1 transactions. The payment went through without issue and in eWay is stored within its own separate Stored Payments page accessed through the Payments menu. Thank you so much.

    Plugin Author webaware

    (@webaware)

    No worries, I’ll release it this afternoon. Thanks for bringing it to my attention, I didn’t know it existed let alone how easy it would be to add it in!

    cheers,
    Ross

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Stored Payment API?’ is closed to new replies.

Tags