My purpose is to automate (as buyer) login into PayPal Sandbox(1) and confirm payment(2) using REST requests (with Postman) after being redirected from third-party payment service.
From there a got a link like: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_express-checkout&token=EC-5AU897953H105581R
I have login and password for buyer account.
I was able to import request from devtools network and it leads me to confirm form, but I cannot make it generic. I found out that the minimum body values are (on screen), but there are some changes in cookies at headers. I am not sure if my approach is even correct. Do you have any ideas?
If you find out the first very easily, maybe you will also have some tips for confirming payment.
I already searched a lot for answers. There are some instructions for sandbox API, but it looks like it needs clientId and secret(?). See those on the PayPal Sandbox development page, but I do not have credentials for dev dashboard, only for my test customer.
Please Help!
I am unable to login into my heroku account even I know my correct login id and password due to the 2FA which was enabled mistakenly with me because I needed to deploy my app quickly.
I used Google Authenticator for generating the authentication code and logged in but next day my mobile got damaged in a way which couldn't be repaired. Due to which when again I tried to login it still asks for google generated verification code which I don't have, I contacted heroku support several times but it's been a month but still I couldn't get any satisfactory response.
They have opened some Temporary code login and provided a recovery code but still I am unable to login.
Anyone Please help me get my account
Page where I am stuck
Last year Facebook rolled out setting that allowed community to entrypt traffic using user installed certificates. I've successfully enabled whitehat settings for instagram account associated to my facebook account, and set them as seen on image.
I'm using Charles Proxy to monitor HTTPS traffic, however after applying these Instagram settings and enabling SSL proxying in Charles I can't read any requests and every action on Instagram app results in error like can't update feed. Disablind SSL proxying let's me use the app without errors, but all requests seen in Charles from Instagram are encrypted.
I'm able to read requests from sites that doesn't use pinned
certificates like stackoverflow.com.
On my mobile phone I
downloaded Charles certificate from chls.pro/ssl.
tutorial I've followed, however I didn't understand and did not do part past How to Find Version, VersionCode and Signature Key
Is there something I forgot to do or have done wrong way? Thanks in advance for any advises.
Hye,
I'm not sure what is the problem is, but whenever I want to submit my app, this will occur,
afterthat i've tried to revoke my certificate and quest it back, the status were "issued" . How can i solve this problem ? tq.
Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)
Are you sure that you are using the distribution profile to sign your app for submission, and not the developer profile?
It's a common cause of this failure.
It could also be that you are using Xcode 4.5 or iOS6 (which are pre-release) and that is preventing submission.
In general - I find the Apple Technical Note on Code Signing Issues to be a great reference for solving such problems.
I'm getting some rather conflicting information from PayPal. I've spent 2 hours on the phone with them today, and posted my questions on their forums, and I have not received one single solution. So I am turning to SO since people here actually know what they're doing.
I am trying to add the AddressVerify and MassPay APIs to our website. We are currently using the Payflow Pro (DirectPayment, etc) calls with no problems. This uses our PayPal Manager login, password and vendor credentials for authentication via the HTTPS interface. This is all written in PHP using NVP.
However, when I try to add the AddressVerify and/or the MassPay APIs using the HTTPS interface, all I get back is a PNREF and an error saying, "Invalid Tender."
On the forums, I see everyone using email addresses as logins, and a certificate key of some sort. I called PayPal today to figure out how the heck to get that information, and the developer there said I don't use the login with the key and that I'm using the wrong SDK. He told me where to get the Dev Guide and that I should use that instead.
However, the dev guide only outlines what we're already using, and I wasn't about to sit on the phone for another hour and 40 minutes.
So my question is this:
Am I just missing something, or did I just get some bad information? I'm guessing it's the latter, because nobody there seemed to know squat about jack diddly.
Am I correct in assuming that the code ( as outlined here ) is what I should be using? If so, how do I obtain a signature key and presumably a new login & password?
If the dev guy from PayPal is correct and I should be using the HTTPS Interface, then how do I get that to work? Because like I said above, all I'm getting from that is a PNREF and an error message saying, "Invalid Tender."
If anyone has any experience with this and/or some suggestions on how to get this stupid thing to work, I'd be forever greatful!
Thanks in advance!
Brian
In case anybody is interested in knowing, I received a response from the devs at PayPal:
If you are using Payflow then you should be using the Payflow Pro SDK, it would require a User, Vendor, Partner, and Password in the credentials that get passed over. It would also return a PNREF number. If you are wanting to use Website Payments Pro, then your SDK would have either a API Username, API Password, API Signature, or an API Username, API Password,and API Certificate. The AddressVerfiy API is an API that is available for Website Payments Pro/PayPal accounts not Payflow. You can find all of the SDK's for both services here. The Payflow SDK's are the ones at the bottom of the page.
So apparently MassPay and AddressVerify is part of the Web Payments Pro, which uses a different SDK than the Payflow Pro stuff. And for this, you need to obtain a separate username, password, and certificate or key. The Payflow Pro credentials will not work with this.
Hope someone else can benefit from my hours of wasted time!