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
Related
Our client has asked us to build a Shopify site that ties into their in-house customer db (with or without using Salesforce). Is this even possible? Does Shopify support any method of cross-site database querying?
The only thing I can think of to accomplish this is to write a webhook on their in-house server with a simple read-only mini DB query API. However, as that I'm not super familiar with Shopify's more obscure capabilities (and having already spent quite some time sifting through their docs and running google searches on the matter with absolutely zero results), I'm not even sure if this is possible.
Are we barking up an impossible tree, or is this something that can actually be accomplished?
Thank you in advance for any help you can give.
What I have understood from your description is you already have an external database with user login details and you want to use the same for authentication in Shopify. If yes, then it is possible with Shopify Multipass feature. This feature is only available for Shopify Plus plans. From the Shopify Multipass docs
Multipass login is for store owners who have a separate website and a
Shopify store. It redirects users from the website to the Shopify
store and seamlessly logs them in with the same email address they
used to sign up for the original website. If no account with that
email address exists yet, one is created. There is no need to
synchronize any customer databases.
For your particular scenario, you would have to validate user credentials with your external database, generate multipass url and redirect.
Yes your requirement is quite possible. But the method i am going to mention is a hack basically. Below are the steps:
Create Login page/Account creation page in Shopify
When the user does a login/create account you send the information to your server via below methods
JSONP request
Creating a iframe of your domain and passing the information in the iframe
Now, you validate the user credentials at your server
After validating you check if the user is present in Shopify. If not you create the user with a password. API Link
Make sure you save the user password you push into Shopify at your end also.
Now when you have completed authentication of the user, return back Shopify username and password
Create a hidden form in Shopify liquid file and pass the credentials in the respective fields and submit the form and user should be able to log in with the existing password they have!
How can I get my PayPal balance via .NET PayPal API and my API credentials?
I have already added the API to Visual Studio 2017.
I think the answer as of now is that there isn't an answer.
Here is what I do know though.
In a discussion here, someone claims that there is a whole separate API called Balance Accounts API, but the link is broken or the API is deprecated.
On the GitHub link I linked in this solution you'll see the following dialog between two users:
#AMRITPK Correct me if I am wrong, but as I see it, this API is only for PayPal partners, for retrieving balances of your internal customers. Or am I mistaken?
yes #andrey-zav , it works only if the caller is a third party... But work around is you can give permissions to your own account to call this api .. not sure if this is right approach.
So, I'm not really sure what to take out of that.
In addition, you can stay tuned to me fighting the PayPal automated bot-responsive "human" moderators on the PayPal tech support forum here.
As far as I know though, you have to be a PayPal Partner and then use some convoluted way to incorrectly ping your own account via the API to get your PayPal balance account.
I hope this helped.
UPDATE: Through exhaustive searching I found a C# .NET implementation of how to get the PayPal Account Balance using their NVP API here. You'll have to install the PayPal Merchant Nuget Package. In addition, you will have to set up your web config file using the information found here. I'm assuming this works on live as well. I have only tested it in sandbox mode, and it did indeed work.
How can I recognize when user has added account in Yodlee Fast Link (for example an investment account) by going to the link.
What I want:
I am creating a link to "Fast Link";
User are following by this link;
He is adding a their account;
And in this point I wanna know that he has added something (for example by callback url). How?
Thanks!
Yes, this can be done. You can have a page hosted that can count the hits and use that page as callback URL in extra params for FastLink.
You can get more information on this at
https://developer.yodlee.com/Fastlink_2.0/FastLink_Integration_Guide_for_Web
The extra parameters that needs to be passed for achieving this is as below
callback=http://google.co.in where here google.co.in is your callback page
Regards,
Vijay
Yodlee have introduced a new event subscription service using webhooks. It is part of their YSL (Yodlee Service Language) product.
It can trigger events for following –
the MFA information is requested by the provider site to log in for
aggregating data
the Yodlee system has performed the login on the provider site
successfully
the Yodlee system has retrieved the account summary information from
the provider site successfully
the final status of account addition or update account APIs
Details -
https://developer.yodlee.com/apidocs/index.php#!/cobrand/eventSubscription
Please NOTE that Webhook event notifications will work only when you try to add the account using YSL APIs (manually).It doesn't work with FastLink. I have been informed by Yodlee Support. They also informed me that till date they don't have any client using webhook service, which was bit scary to know.
Does anyone know how / if it is possible to use token billing? The 2Checkout API supports it and OmniPay supports token billing, but I've not had much luck and a quick look at the Official Gateway code doesn't seem to show support for it?
Anyone doing this / have any idea?
I can categorically state that it's possible to use token billing, I do so regularly. I'm not that familiar with 2Checkout but I have used token billing on stripe, paypal, PaymentWall, MultiCards, Fat Zebra and other gateways.
Is there a specific problem you're having that you can illustrate with some example code?
Does 2Checkout support token billing? Yes, and it works. However, there are some quirks with it:
You have to turn Demo Mode off on the dashboard or the 2Checkout and OmniPay API doesn't seem to work properly.
You have to send a Billing Address in order for the transactions to go through. If that doesn't work for you, such as for digital downloads, then you'll want to consider another payment gateway.
The billing address must contain a customer email and cannot be empty. Again, if that doesn't work well in your sales workflow, then you'll want to consider another payment gateway.
The billing address must contain a phone number, but CAN be empty.
I discuss this here as well as provide an OmniPay sample code snippet: https://stackoverflow.com/a/36807292/105539
Take a look at my project, TokenPay. I've weeded through the confusing docs and got it working on 2CO.
P.S. Don't ever forget your sandbox password -- they don't tell you this in the docs, but found out via tech support that their password reset on the sandbox login doesn't look disabled, but is disabled. (It would have been nice if they made that quite clear.) Instead, you'll have to create another sandbox account entirely when you forget a password there.
I can not praise with my contribution here, because I am new user,
but would help if I can.
I have a big problem and I do not know how to solve it, please help.
In the same Paypal account with the default email address: email1#somedomain.com, there is 7 more emails:
email2#somedomain.com
email3#somedomain.com
email4#somedomain.com
email5#somedomain.com
email6#somedomain.com
email7#somedomain.com
that's the maximum allowed number of emails under one PayPal account (8).
So we are using API on several pages, and only one API signature can be done in the paypal
interface, so same API signature is used for each web page.
We would like to define where will money go - to which email address inside the same PayPal account.
We use Premium PayPal account, and we know that for logo change, email remove and so on, we would need Business account,
but for defining money receiver email address inside the same PayPal account
we suppose that it can be defined, otherwise we do not se a point of having several email addresses inside one same PayPal account.
The problem is that always is shown default email when making a purchase :S
We tried to define SUBJECT:
SUBJECT=merchantEmailAddress
N O T E: Typically, a merchant grants third-party permissions to a shopping cart...
And set merchantEmailAddress email2#somedomain.com.
In sandbox it works like a charm as soon as we put it on production, default mail is shown again.
Please if anyone had the same issue help.
Thank you very much, this forum is great and I realise that without nice people and contribution as well there would be no answers.
regards
You would not be using SUBJECT unless dealing with Permissions and making calls on behalf of 3rd party PayPal accounts.
You're working with a single PayPal account, so you won't be using SUBJECT at all. You'll use the credentials like you are already.
That said, I'm not sure I'm following you entirely what trying to send to different emails. I don't understand the end goal with that..?? The API credentials are what are going to tell the system where to drop the money, or pull data from, or whatever.
If you're just trying to get different logos to show up during checkout you can do that with parameters in your standard button code or API requests.
Let me know if that helps or not. Again, I'm not sure I'm understanding what you're after here.