I am working on an eCommerce platform that will allow a buyer to buy products from multiple stores and checkout with one payment using Paypal (unified checkout). My scenario is exactly like this:
https://www.paypalobjects.com/webstatic/en_US/developer/docs/ap/AdapPymntRolesApp_B.gif
The flow of the app would be starting the checkout on our website, then redirecting to Paypal for user to pay, then be redirected back to our website. Like this:
https://www.paypalobjects.com/webstatic/en_US/developer/docs/ap/AdapPymntSrvcFlow_A.gif
My confusion is with the credentials passed to the API.
Dictionary<string, string> configMap = new Dictionary<string, string>();
configMap = GetConfig();
// Signature Credential
configMap.Add("account1.apiUsername", "jb-us-seller_api1.paypal.com");
configMap.Add("account1.apiPassword", "WX4WTU3S8MY44S7F");
configMap.Add("account1.apiSignature", "AFcWxV21C7fd0v3bYYYRCpSSRl31A7yDhhsPUU2XhtMoZXsWHFxu-RWy");
Who's API credentials are these? Surely we won't make the buyer generate an API key in their PayPal account. If it's the merchant (receiver), what if we have 2 receiver's? Do I do this:
Dictionary<string, string> configMap = new Dictionary<string, string>();
configMap = GetConfig();
// Signature Credential
configMap.Add("account1.apiUsername", "jb-us-seller_api1.paypal.com");
configMap.Add("account1.apiPassword", "WX4WTU3S8MY44S7F");
configMap.Add("account1.apiSignature", "AFcWxV21C7fd0v3bYYYRCpSSRl31A7yDhhsPUU2XhtMoZXsWHFxu-RWy");
configMap.Add("account2.apiUsername", "jb-us-seller_api1.paypal2.com");
configMap.Add("account2.apiPassword", "WX4WTU3S8MY44S7F2");
configMap.Add("account2.apiSignature", "AFcWxV21C7fd0v3bYYYRCpSSRl31A7yDhhsPUU2XhtMoZXsWHFxu-RWy2");
Or do we need to generate an apiUsername, apiPassword and apiSignature from our PayPal Business account and use that?
We are not taking any money from the buyer, we are purely a middle man, connecting buyers and sellers, at this point. All fee's will be passed on to the receivers.
I hope those aren't your actual live API credentials. If they, get them out of this thread immediately!
As for setting up Adaptive Payments apps, your app will use your API credentials. You will then user the Permissions API (or have people do it manually from their PayPal account profile) to have users grant permissions for your App to make calls on their behalf. That way you can send money from 3rd party accounts using your own credentials.
Related
I would like to make my program compatible with the new LinkedIn V2 api. The user migration is my question. In my database, I store the LinkedIn V1 api generated user id-s and e-mail addresses and access tokens.
In the LinkedIn Marketing Developer Program at the top of the page, I read this:
I understand by applying for Marketing API my app will lose access to V1 APIs. Since these APIs are deprecated for LMS partners, the app cannot make API request to any of the V1 endpoints. Note: If you do not want to lose access to V1 APIs for the app you are applying for, create a new app to request access for LMS program using this form. We recommend migrating your apps from using V1 APIs as they are planned to be deprecated.
So I created new LinkedIn applications with new ClientId, and ClientSecret.
In the LinkedIn new developer documentation LinkedIn new developer documentation I read this:
id: A unique identifying value for the member. Referenced as personId in other API documentation pages. Can also be referenced as an URN such as urn:li:person:{personId}. This value is linked to your specific application. Any attempts to use it with a different application will result in a 404 error.
So if I make a new app in the LinkedIn developer console, the old app's user ids will be gone.
If I would like to find my "old" user with the e-mail address, the new LinkedIn V2 api doesn't provide this primary-contact-api, because it will provide primary contact, which can be the telephone number, not the e-mail address.
My question is, how can I migrate my "old" users?
I want to create a subscription using Paypal. I created the API call but I want my BlueSnap console to manage it. Is there a way? I don't want to use the retrieve call all the time...
Bluesnap has two ways of managing the PayPal subscription: one using PayPal's system, and one using BlueSnap's subscription manager . In both cases, you do not need to retrieve the subscription constantly to charge it, if you're using a standard subscription.
In order to know which subscription management you will use, you can contact BlueSnap and ask about your account configuration.
In order to use the API to create a subscription in PayPal, you can use the extended API or the payment API.
Extended API:
1) create a subscription SKU to use: https://developers.bluesnap.com/v8976-Extended/docs/create-product, https://developers.bluesnap.com/v8976-Extended/docs/create-sku.
2) Create shopping context with the SKU: https://developers.bluesnap.com/v8976-Extended/docs/create-shopping-context. Make sure you use the PayPal examples.
3) Use the created Token URL to send to the shopper to approve the purchase in PayPal.
Payment API:
1) Create the PayPal transaction: https://developers.bluesnap.com/v8976-XML/docs/create-paypal-transaction.
2) Use the created Token URL to send to the shopper to approve the purchase in PayPal.
I am having difficulty figuring out how to set up the API for the Paypal pro accounts. They list it as the NVP/SOAP account. https://developer.paypal.com/docs/classic/lifecycle/apps101/
I have researched this and created a sandbox test API app for the sandbox credentials. I am just unsure of where the API doc is that I need to include and then what else I need for it. I found this, but it confuses me even more. https://developer.paypal.com/docs/classic/api/gs_PayPalAPIs/ ...
I am unsure of what I need to put where and how to even process this. I have integrated the authorize.net API and there was a base template for it that required only modification and it was very straight forward.
Could anyone provide me with some insight to how I can do this?
Refer this link
https://developer.paypal.com/docs/classic/paypal-payments-pro/gs_PayPalPaymentsPro/?mark=paypal%20pro
You need to first setup the authentication parameters
PWD : // password
SIGNATURE : // signature
USER : // user id
VERSION
and then calls the different paypal methods like DoDirectPayment etc with their list of parameters..
Refer the documentation for the individual paypal methods and their list of parameters.
Also first create a paypal sandbox account to get the API credentials
I'm trying to find out how to get a ClientID and clientSecret to use with the Bigcommerce API.
Our website has to redirect an owner of a bigcommerce store to bigcommerce itself, so that they can grant us permission to query their sales data.
My understanding is that before doing this, we need credentials for OAuth, i.e. ClientID and ClientSecret, and that when our user grants us permission, we get back a token.
The only problem is, I can't see where to get our credentials in the first place. Bigcommerce seems to want you to create an 'App', which it then suggests you place on their store. We already have a website, which is going to call the API behind the scenes.
How do I go about getting ClientID, ClientSecret?
thanks in advance.
You want to create a developer account and then register a draft app which will provide a Client ID and Client Secret for you.
You can find the details in the Getting Started section here:
https://developer.bigcommerce.com/apps/
If an existing PayPal user has one or more credit cards saved in their PayPal account, and that user is new to my application, are those card details accessible via the Rest API Vault endpoint?
No. When you make a REST call, the end user will be providing you their card data directly. The credit cards in their PayPal account are backup funding sources. While it's possible you could get paid through them, there's no way for you to know because the payment will be shown as their PayPal account only.