Now I am working for integrating PayPal.
For PayPal actions including subscription and so on, it needs client id and secret.
For obtaining client id and secret, is there any way to obtaining these from paypal email address?
or maybe is there any way to do subscription and so on without client id, and secret?
Please let me know. Thanks
Related
I am creating a PayPal gateway for a store/shopping cart created for a CMS. Once completed, the gateway will be made available to others.
Do the API credentials (Client ID and Secret) created in my Developer account stay with the app or will everyone who uses my app be required to have API credentials of their own?
Everyone will need to supply their own client ID and secret. The client ID and secret point to your PayPal account, so it's not a good idea to include those in your app.
We are developing a marketplace webapp which charges customers on behalf of sellers.
After reading through PayPal's API documentation, the only solution seems to be the Permissions service.
According to the documentation. After retrieving the access token and token secrete of a seller through the RequestPermissions call, we generated X-PAYPAL-AUTHORIZATION header to initiate an express checkout payment id. However, the payment id generated is associated with our PayPal account instead of the seller's, which is not the anticipated behavior.
Adding seller's email address in the SUBJECT field as noted in PayPal Name-Value Pair API Basics does work, but as we tested it, it has nothing to do with the access token and token secrete.
The problem with the SUBJECT field is that we cannot make sure the seller's email address with us is the one PayPal have on file.
The GetBasicPersonalData permission seems to be able to get a valid email address, but that needs to be pre-approved by PayPal. In fact, I have come across many websites that does not require this permission but able to initiate payment on behalf of other users. Is there a way to just get sellers' email or PayPal Id without GetBasicPersonalData permission? We don't actually need any other personal data except email or PayPal Id.
I have been trying to validate Paypal client id but I didn't landed to any solution from Paypal documentation and also from other sources.
Anyone please help me if there is any API to validate Paypal's Client id.
You may want to look at PayPal Adaptive Accounts API. You can use GetVerifiedStatus API Operation to determine whether the specified PayPal account's status is verified or unverified.
Since Paypal officially sends people here for support, I hope StackOverflow members will not burn me at the stake.
After the product is sold, I need in the paypal confirmation email
Temporary password sent so user can login to site with their Email and that password.
We will obviously need that email/password via api to authenticate user.
You cannot modify Paypal's confirmation email, given Paypal's API restrictions. However, you can send emails via your application, to your users upon successful payment.
PayPal will send you application a response code for each transaction (payment successful/unsuccessful), which you can use to handle your behavior.
The documentation for paypal adapative api requires the developer to send 6 headers amongst which there are:
X-PAYPAL-SECURITY-USERID : Sandbox-Caller-User-Id
X-PAYPAL-SECURITY-PASSWORD : Sandbox-Caller-Password
X-PAYPAL-SECURITY-SIGNATURE : Sandbox-Caller-Security-Signature
The trouble is I don't know where to find the USERID, PASSWORD and SIGNATURE
In the below screenshot that I took from the Paypal Sandbox Business Account, there is no such thing as USERID, PASSWORD and SIGNATURE. Instead I have Sandbox account, Endpoint, Client ID and Secret.
Screenshot: https://dl.dropboxusercontent.com/u/6599473/Capture.PNG
So which is which? What is the userid? What is the password? and what is the signature?
The screenshot you've provided is for the REST API. UN, PASS, and SIG are for the Classic API.
You can obtain those credentials logging in here with your PayPal account.
You can find more details here.