I am going to build an eCommerce website that supports PayPal.
Buyers connect their PayPal account to the website before they get products.
The website should collect funds without a normal checkout flow whenever buyers buy products.
For this, I've researched the Permissions Service API on PayPal.
But, I can't find enough descriptions to build such a website.
I would like to know how to integrate PayPal for this.
What you are looking for is a "Reference Transactions" solution. It can be tested in sandbox, but to use it in live, the business account would need to be approved for this feature by PayPal. To do this the account owner would need to contact their PayPal account manager or PayPal's general customer support (not MTS), and explain the business need for this feature.
As far as implementing the solution, the only public documentation I'm aware of is for classic APIs: https://developer.paypal.com/docs/classic/express-checkout/ec-set-up-reference-transactions/ . Any newer API or vault solution does not appear to be publicly available at this time, but you could always contact PayPal's support and ask if there's something they'd rather you implement than those classic APIs. The more significant hurdle is the business approval for the feature mentioned earlier.
Related
I have an app with Free, Premium and Gold subscription plan. Based on the plan user can access features like filters, messages, likes.
Now, I'm planning to have an web app only for payments using stripe. So, users will directed to web app to pay payments.
Will apple allow this approach or will they insist to use in-app purchase?
I'm little confused here. Need your suggestion here?
This is a question for Apple Review team, you should reach out to them directly and clarify. Stripe doesn't replace in-app purchases and you need to use Apple's API to perform in-app purchases. See here for details
A few weeks ago I implemented my first REST integration with the DocuSign API. Things over all went smoothly and with very little complaints. One particular hang up I experienced though was some confusion in regards to the Developer account and how it relates to the General account. I started with a developer account and used the test credentials to build my integration. Once my integration passed inspection it required me to choose another paid docusign account that the integration key would "go live" on. This is all pretty straight forward.
The curve ball came when I actually went to purchase the API account and it said, "you aren't eligible to purchase this". There isn't clear instruction on the site, so my questions are:
1.) In what order does the account creation need to go? Developer > General (Paid) > API Plan (Paid)?
2.) Does DocuSign expect the user, as the customer, to purchase the plan or should that plan be purchased through my developer account?
I tried to reach out to customer service directly, but it was pretty much a, "give us all of your money, then we'll help" situation. I have several customers who are interested in this integration, but I'm not comfortable presenting this as an option until I get a better understanding of the process. Any advice is greatly appreciated.
In general, DocuSign does require a paid account to complete the Go Live process. If you - the integration owner - will not be using DocuSign yourself, you would want to reach out to the [DocuSign Partners program][1] to receive a free Partner account that can hold your integration key instead of having to purchase one.
From there, the end users of your integration can purchase their own DocuSign accounts. You could potentially act as a reseller of DocuSign if you were so inclined.
https://www.docusign.com/partners/become-partner
If you still need assistance, please email apihelp#docusign.com with this information. Someone will help you right away.
I want to include debit/credit card payments powered by papal for my website, I am following the guide as per
https://developer.paypal.com/docs/business/checkout/advanced-card-payments/
but for the code
paypal.HostedFields.isEligible()
I always get the false or undefined as error, may be I skipped something, please help.
I found this answer on the Paypal community.
"In my case, I was using a personal account as a developer account. When I created sandbox credentials from the Business account it started to work. So make sure,
Developer account is linked/created with the business account
Sandbox account is created from that.
Sandbox account should also be a business account and it should be enabled for advanced payments ( Using this link: https://developer.paypal.com/docs/business/checkout/advanced-card-payments/#enable-your-account )"
Here the keypoints:
You need a business account to use advanced payments.
You don't need to have a real business account when working in the sandbox environment: you can create a fake business account in the sandbox and use it.
You need to ask for approval to use the advanced payments. This request must be done separately for sandbox and production accounts.
When loading the Javascript SDK be sure to not pass the disable-funding=card parameter, otherwise isEligible() will return false even if your account has been approved!
I see paypal is upgrading their APIs. I want to collect recurring payments and provide a feature to upgrade / downgrade the plans.
In the samples, paypal is using billing agreements and when I see the docs, it says the API is deprecated please use subscriptions API. I am confused which one to use.
Please help me in this.
PS: Also my product includes one time payments
The PayPal Subscriptions API uses billing agreements and plans, and there are multiple versions. Everything linked from https://developer.paypal.com/docs/subscriptions/integrate/ will be the most recent version.
For one-time (non-subscription) payments, the most robust integration is to have two routes on your server that implement v2/checkout/orders API calls to "create order" and "capture order", combined with this front end: https://developer.paypal.com/demo/checkout/#/pattern/server
For a subscription integration to be similarly robust (in that your server gets an immediate API response of profile activation), you can have those buttons call your server as well: PayPal Smart Subscribe server side
Can I get users to enter credit card details on the PayPal site, rather than my own when setting up a recurring payments profile for direct credit card payments?
When setting up a recurring payments profile for a user who wishes to subscribe to my service, I currently follow the standard recurring payment flow (as shown in the PayPal API examples):
Use the REST API to create a billing plan and agreement.
Redirect the user to the PayPal site.
User logs in/registers on PayPal site and confirms their acceptance there.
PayPal redirects them back to my site for final confirmation of the billing agreement.
Once they have confirmed on my site, billing commences and we start listening for IPN's.
However, it seems that if you want to use direct credit card payments (i.e. the customer does not have/want a PayPal profile), you have to capture the credit card details on your own site and pass them through to PayPal on the API call. Is there a way to move the credit card detail capturing to the PayPal site itself?
Yes, PayPal supports this arrangement; they call it hosted pro or hosted sole solution. However, it's classic, not the new REST.
PayPal's newer direct credit card APIs use vaulting, but I don't believe they come with a fully PayPal-hosted page that would avoid all PCI complications for you.
You might also want to look at Braintree's solution, which integrates into your page but handles encrypting & tokenizing the card details so you don't have to worry about PCI.