thanks for writing this app... saved me a bunch of time

75 views
Skip to first unread message

Roman Onosovski

unread,
Nov 5, 2014, 7:55:59 PM11/5/14
to django-...@googlegroups.com
I wanted to find out why the recurred billing seems to have been written in the XML implementation where are purchase/void/etc are using a different method? was this just halfway into being updated?

Roman Onosovski

unread,
Nov 5, 2014, 7:59:32 PM11/5/14
to django-...@googlegroups.com
nevermind.. i found that it was implemented using the now legacy API for AIM

Thejaswi Puthraya

unread,
Nov 6, 2014, 5:58:54 AM11/6/14
to django-...@googlegroups.com
Hi Roman,
We try our best to keep up with updates but sometimes things slip past
especially when tracking so many gateways. So can I request you to
excuse us on this front? :)

On Thu, Nov 6, 2014 at 6:29 AM, Roman Onosovski <r.ono...@gmail.com> wrote:
> nevermind.. i found that it was implemented using the now legacy API for AIM

What would be the successor to the legacy API for AIM?

>
>
> On Wednesday, November 5, 2014 7:55:59 PM UTC-5, Roman Onosovski wrote:
>>
>> I wanted to find out why the recurred billing seems to have been written
>> in the XML implementation where are purchase/void/etc are using a different
>> method? was this just halfway into being updated?
>
> --
> You received this message because you are subscribed to the Google Groups
> "django-merchant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-mercha...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Cheers
Thejaswi Puthraya
http://thejaswi.info/

Roman Onosovski

unread,
Dec 19, 2014, 10:55:24 AM12/19/14
to django-...@googlegroups.com
Absolutely! I got the API working and doing what I need it to do! Thanks again!
Reply all
Reply to author
Forward
0 new messages