Re: [WebDNA] PayPal Instant Payment Notification Guide
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 103405
interpreted = N
texte = --Boundary-00=_gevjKms7AcAzKcq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > In my experience with using WebDNA to talk to PayPal > (using a regular form, not a tcpsend as you guys have > been discussing), you can send it any of your own > variables, and it will simply echo it back to you. This is nice where it applies, but it may not apply to our use of tcpsend because the tcpsend is used to report back the same variables paypal sends us in an ipn post -- and most of those values are never sent in a regular form like the one you're talking about. If we choose to actually believe the paypal docs they actually say we are allowed only two fields for special values that will be returned in their ipn posts -- custom and invoice -- but it sure would be nice to have more than these two parameters. > Unless "template" conflicts with something on their end, it > shouldn't be an issue. It seems that Dan got away with sending paypal the template parameter and placing the cmd parameter in the wrong place -- two things the paypal docs say not to do. This suggests that they do not really care about the order in which they receive the name=value pairs AND they do not care how many extra name=value pairs we send either. I hope this is correct because it makes things easier. Then again, doing it precisely according to the paypal docs is not that hard either ... :) I've had so many problems with little mistakes when trying to follow the API's from other online services that I tend to make a habit of following the published guidelines as accurately as possible now. Saves a lot of hassle in some cases. Sincerely, Ken Grome > > Terry > > On Fri, 21 Aug 2009 14:52:02 -0400 > > Kenneth Grome
wrote: > > There's something else that should probably be > > corrected too. Remember that WebDNA appends a > > "template" formvariable > > which does not exist in the actual form variables sent > >to > > the server, and I think it may be wise to get rid of it > >so > > it does not create any problems. > > > > Here's the code I'm planning to test and use if it > >works. > > The showif removes the extraneous template parameter > > inserted by WebDNA, so the result is (theoretically) > > the exact same string paypal sent to the server: > > > > [text]content=[!] > > [/!]cmd=_notify-validate[!] > > [/!][formvariables][!] > > [/!][showif [name]!template][!] > > [/!]&[name]=[url][value][/url][!] > > [/!][/showif][!] > > [/!][/formvariables][!] > > [/!][/text] > > > > Sincerely, > > Ken Grome > > --Boundary-00=_gevjKms7AcAzKcq Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable p, li { white-space: pre-wrap; }> In my experience with using WebDNA to talk to PayPal
> (using a regular form, not a tcpsend as you guys have
> been discussing), you can send it any of your own
> variables, and it will simply echo it back to you.
This is nice where it applies, but it may not apply t= o our use of tcpsend because the tcpsend is used to report back the same va= riables paypal sends us in an ipn post -- and most of those values are neve= r sent in a regular form like the one you're talking about.
If we choose to actually believe the paypal docs they= actually say we are allowed only two fields for special values that will b= e returned in their ipn posts -- custom and invoice -- but it sure would be= nice to have more than these two parameters.
> Unless "template" conflict= s with something on their end, it
> shouldn't be an issue.
It seems that Dan got away with sending paypal the template parameter= and placing the cmd parameter in the wrong place -- two things the paypal = docs say not to do.
This suggests that they do not really care about the = order in which they receive the name=3Dvalue pairs AND they do not care how= many extra name=3Dvalue pairs we send either.
I hope this is correct because it makes things easier= =2E Then again, doing it precisely according to the paypal docs is not tha= t hard either ... :)
I've had so many problems with little mistakes when t= rying to follow the API's from other online services that I tend to make a = habit of following the published guidelines as accurately as possible now. = Saves a lot of hassle in some cases.
Sincerely,
Ken Grome
>
> Terry
>
> On Fri, 21 Aug 2009 14:52:02 -0400
>
> Kenneth Grome <kengrome@gmail.com> wrote:
> > There's something else that should probably be
> > corrected too. Remember that WebDNA appends a
> > "template" formvariable
> > which does not exist in the actual form variables sent
> >to
> > the server, and I think it may be wise to get rid of it
> >so
> > it does not create any problems.
> >
> > Here's the code I'm planning to test and use if it
> >works.
> > The showif removes the extraneous template parameter
> > inserted by WebDNA, so the result is (theoretically)
> > the exact same string paypal sent to the server:
> >
> > [text]content=3D[!]
> > [/!]cmd=3D_notify-validate[!]
> > [/!][formvariables][!]
> > [/!][showif [name]!template][!]
> > [/!]&[name]=3D[url][value][/url][!]
> > [/!][/showif][!]
> > [/!][/formvariables][!]
> > [/!][/text]
> >
> > Sincerely,
> > Ken Grome
>
> =A0
--Boundary-00=_gevjKms7AcAzKcq--
Associated Messages, from the most recent to the oldest:
--Boundary-00=_gevjKms7AcAzKcq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > In my experience with using WebDNA to talk to PayPal > (using a regular form, not a tcpsend as you guys have > been discussing), you can send it any of your own > variables, and it will simply echo it back to you. This is nice where it applies, but it may not apply to our use of tcpsend because the tcpsend is used to report back the same variables paypal sends us in an ipn post -- and most of those values are never sent in a regular form like the one you're talking about. If we choose to actually believe the paypal docs they actually say we are allowed only two fields for special values that will be returned in their ipn posts -- custom and invoice -- but it sure would be nice to have more than these two parameters. > Unless "template" conflicts with something on their end, it > shouldn't be an issue. It seems that Dan got away with sending paypal the template parameter and placing the cmd parameter in the wrong place -- two things the paypal docs say not to do. This suggests that they do not really care about the order in which they receive the name=value pairs AND they do not care how many extra name=value pairs we send either. I hope this is correct because it makes things easier. Then again, doing it precisely according to the paypal docs is not that hard either ... :) I've had so many problems with little mistakes when trying to follow the API's from other online services that I tend to make a habit of following the published guidelines as accurately as possible now. Saves a lot of hassle in some cases. Sincerely, Ken Grome > > Terry > > On Fri, 21 Aug 2009 14:52:02 -0400 > > Kenneth Grome wrote: > > There's something else that should probably be > > corrected too. Remember that WebDNA appends a > > "template" formvariable > > which does not exist in the actual form variables sent > >to > > the server, and I think it may be wise to get rid of it > >so > > it does not create any problems. > > > > Here's the code I'm planning to test and use if it > >works. > > The showif removes the extraneous template parameter > > inserted by WebDNA, so the result is (theoretically) > > the exact same string paypal sent to the server: > > > > [text]content=[!] > > [/!]cmd=_notify-validate[!] > > [/!][formvariables][!] > > [/!][showif [name]!template][!] > > [/!]&[name]=[url][value][/url][!] > > [/!][/showif][!] > > [/!][/formvariables][!] > > [/!][/text] > > > > Sincerely, > > Ken Grome > > --Boundary-00=_gevjKms7AcAzKcq Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable p, li { white-space: pre-wrap; }> In my experience with using WebDNA to talk to PayPal
> (using a regular form, not a tcpsend as you guys have
> been discussing), you can send it any of your own
> variables, and it will simply echo it back to you.
This is nice where it applies, but it may not apply t= o our use of tcpsend because the tcpsend is used to report back the same va= riables paypal sends us in an ipn post -- and most of those values are neve= r sent in a regular form like the one you're talking about.
If we choose to actually believe the paypal docs they= actually say we are allowed only two fields for special values that will b= e returned in their ipn posts -- custom and invoice -- but it sure would be= nice to have more than these two parameters.
> Unless "template" conflict= s with something on their end, it
> shouldn't be an issue.
It seems that Dan got away with sending paypal the template parameter= and placing the cmd parameter in the wrong place -- two things the paypal = docs say not to do.
This suggests that they do not really care about the = order in which they receive the name=3Dvalue pairs AND they do not care how= many extra name=3Dvalue pairs we send either.
I hope this is correct because it makes things easier= =2E Then again, doing it precisely according to the paypal docs is not tha= t hard either ... :)
I've had so many problems with little mistakes when t= rying to follow the API's from other online services that I tend to make a = habit of following the published guidelines as accurately as possible now. = Saves a lot of hassle in some cases.
Sincerely,
Ken Grome
>
> Terry
>
> On Fri, 21 Aug 2009 14:52:02 -0400
>
> Kenneth Grome <kengrome@gmail.com> wrote:
> > There's something else that should probably be
> > corrected too. Remember that WebDNA appends a
> > "template" formvariable
> > which does not exist in the actual form variables sent
> >to
> > the server, and I think it may be wise to get rid of it
> >so
> > it does not create any problems.
> >
> > Here's the code I'm planning to test and use if it
> >works.
> > The showif removes the extraneous template parameter
> > inserted by WebDNA, so the result is (theoretically)
> > the exact same string paypal sent to the server:
> >
> > [text]content=3D[!]
> > [/!]cmd=3D_notify-validate[!]
> > [/!][formvariables][!]
> > [/!][showif [name]!template][!]
> > [/!]&[name]=3D[url][value][/url][!]
> > [/!][/showif][!]
> > [/!][/formvariables][!]
> > [/!][/text]
> >
> > Sincerely,
> > Ken Grome
>
> =A0
--Boundary-00=_gevjKms7AcAzKcq--
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Country & Ship-to address & other fields ? (1997)
[Announce]: Web server security and password protection (1997)
WC TableGrinder (1997)
I think WebDNA-Talk died ... :( (1997)
Is there a max number of fields? (1998)
cybercash (1998)
SET (1998)
service stop and restart (1997)
dates and hex formatting (1997)
setitems, one more thing (1997)
Pgp&emailer (1997)
[protect admin] (1997)
Simple way to create unique SKU (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
Resume Catalog ? (1997)
AuthorizeNet Declines (2005)
[OT] (waaaay OT) (2004)
OT - good CC processor(s)? (1999)
still having shipCost.db Problem (1997)
Snake Bites (1997)