But are you understanding the API correctly? I would expect the
"VERIFIED" to either be in their POST to your listener (to indicate
that the payor's payment method is valid), or that it would be in your
response to that POST to tell paypal that this looks like a valid
payment (the payment amount or item quantities haven't been hacked,
etc.).
But you could be right.
Bill
On 3/12/12, hack <scott...@gmail.com> wrote:
> I read the paypal ipn docs, and think I understand the procedure for
> processing payments.
> The only issue I have is that I am not 100% certain how to do this via
> django.
>
> Basically you setup a listener http://mysite.com/mylistener/, and when
> someone makes a payment paypal responds by notifying your litener. (ie
> - http://mysite.com/mylistener/?paypalparms=somepaypalstuff&blah=blah
>
> So I then access all the parms and verify them. However, the place where
> I'm stuck is how exactly do I programmatically execute a post back to
> paypal to confirm my receipt and how do I obtain their response object to
> view response.content? Basically I need to view the content of the body to
> see if it contains VERIFIED, etc. Django seems a little different than
> java servlets, which is what I am used to using. Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/wCjYi1UxT50J.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
Yeah the docs may say it's in the body of the response, but is that
your response to them, or the response to some request you have to
further make to them.
This sounds familiar. It may or may not have been Paypal, but I've
done something like this in the past, and there was no extra request.
Yes, you have to have a remembered cart, or something, to coordinate
with what they're sending you, unless you're getting everything you
need for fulfillment in the post from them.
Anyway, good luck. In my experience, webservice documentation has
spotty quality.
>> > django-users...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/django-users?hl=en.
>> >
>> >
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/UHrly8fABmMJ.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/django-users?hl=en.
>> >
>> >
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/UHrly8fABmMJ.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
>> > django-users...@googlegroups.com.
>> > django-users...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/django-users?hl=en.
>> >
>> >
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/sSWTr8YpGuQJ.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.