Re: [WebDNA] PayPal Integration
This WebDNA talk-list message is from 2017
It keeps the original formatting.
numero = 113923
interpreted = N
texte = 1523 --001a11455f18a9701c0560d1dd0e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable is the token invalid because JSON is grabbing it on another page..? just a guess On Wed, Dec 20, 2017 at 10:42 PM, Stuart Tremain
wrote= : > This keeps on failing however it is as per the PayPal docs: > https://developer.paypal.com/docs/api/payments/#payment_list > > > curl -v -X GET "https://api.sandbox.paypal.com/v1/payments/payment?count= =3D > 10&start_index=3D0&sort_by=3Dcreate_time&sort_order=3Ddesc" -H > "Content-Type:application/json" -H "Authorization: Bearer > EC-2PE89wuyuwytuwy704126=E2=80=9D > > I keep getting {"error":"invalid_token","error_description":"Token > signature verification failed=E2=80=9D} yet it IS a fresh token. > > > > Kind regards > > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@idfk.com.au > > > > > > > On 21 Dec 2017, at 14:37, Brian Harrington wrote= : > > maybe post the issues then... I might be looking for one in the near > future! Good Luck! > > On Wed, Dec 20, 2017 at 10:30 PM, Stuart Tremain > wrote: > >> Thanks Brian >> >> I have built a few that are getting old now. I wanted to build one on th= e >> newest platform. Am having a few issues with part of it. >> >> Kind regards >> >> Stuart Tremain >> Pharoah Lane Software >> AUSTRALIA >> webdna@idfk.com.au >> >> >> >> >> >> >> On 21 Dec 2017, at 14:28, Brian Harrington >> wrote: >> >> i built one with some help about 10 years ago... let me know... >> http://www.webdna.us/page.dna?numero=3D244 >> >> Brian >> >> On Wed, Dec 20, 2017 at 10:13 PM, Stuart Tremain >> wrote: >> >>> Has anyone done a PayPal integration using the latest server-side rest >>> API ? >>> >>> https://developer.paypal.com/demo/checkout/#/pattern/server >>> >>> >>> >>> Kind regards >>> >>> Stuart Tremain >>> Pharoah Lane Software >>> AUSTRALIA >>> webdna@idfk.com.au >>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------- This message >>> is sent to you because you are subscribed to the mailing list >>> talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us >>> archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: >>> support@webdna.us >> >> >> --------------------------------------------------------- This message >> is sent to you because you are subscribed to the mailing list >> talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: >> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.= us >> >> >> --------------------------------------------------------- This message >> is sent to you because you are subscribed to the mailing list >> talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: >> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.= us >> > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us archives: > http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.u= s > > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us archives: > http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.u= s > --001a11455f18a9701c0560d1dd0e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable is the token invalid because JSON is grabbing it on anothe= r page..? just a guess