Trying to implement automatic payments via the Paypal Reference Transaction API.
Manage to make it work on sandbox but I noticed on the customer summary page, it refers to the payments as "preapproved payments".
Comparing it to services I used where automatic payments are enabled, the customer summary page shows them as "automatic payments".
Now I'm wondering if these are two different things. Or maybe the sandbox site has outdated/updated naming.
Are they the same?
Well, there are lots of different terms for these you might be seeing, but they are different things.
If you see preapproved payments, preapproval, billing agreement, reference transaction, then that's referring to having an agreement on file that allows your application to process payments on behalf of the user. This could be for any amount at any time, so you can build much more flexible apps with this sort of thing. It's also harder to get approved because it gives you, the app owner, a lot of power. Your app would be in charge of triggering payments when necessary.
Subscriptions, recurring payments, recurring billing would be referring to where you create a profile on the PayPal system, and their system takes care of triggering payments for you. These are more limited because it's a fixed amount that gets processed at a fixed interval.
Related
I want to implement a pay as you go with Paypal, as I read the subscriptions API we need to create a plan and product, and as I understand it, it works based on the regular payments which obviously we don't want that we want if the user's budget is below a certain amount we recharge the user by a fixed amount again, can anybody guide me how to approach and implement pay as go using Paypal?
You are correct, subscriptions bill on a regular schedule whereas what you are describing is the ability to bill an arbitrary amount at any time.
That feature is called "reference transactions", or sometimes "billing agreements". It is not enabled for PayPal business accounts by default. To request the feature, the owner of the PayPal account should contact PayPal's general business support (note: not technical support) and explain the business need for this reference transactions feature.
If it's approved for the account, PayPal can then guide you on which API integration to use; potentially something like the newest v2/vault.
I need to create a subscriptions system in my app, where users can subscribe to a certain package and they must be billed monthly.
Moreover, I need to charge their credit card automatically, and without requiring them to have a PayPal account.
I read about https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=merchant/erp_overview, but is seems it's not available anymore as I click on sign up and it gives me an error ("Sorry, this feature is not available at this time.").
Then I've read about PayPal Standard Payments, which have a subscription method (https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/subscribe_buttons/)
From what I can read there is that this is what is suitable for my use case, and it says that I need to enable the above mentioned service, which it doesn't work.
Can someone point me in the right direction on what service should I use from PayPal in order to implement recurring payments (basically my users will subscribe themselves to a service on my website, and I need to charge them monthly).
Thank you.
If you're wanting to handle credit cards directly I would highly recommend going with Payments Pro w/ Recurring Payments APIs.
You'll have to pay a monthly fee to get it all activated, and it's a little bit more expensive than what you were looking at, but it will give you much greater flexibility building your application(s) into various experiences for your buyers.
I need someone to point me in the right direction of what is the best Paypal product to use and the associated functions I need to accomplish my project.
I have a site where a user can signup for a internet phone service with a set monthly fee, lets say $200 for 1000 minutes.
The problem I have is that:
1. The first month is pro-rated so the amount may change.
2. If a user of my site goes over their allotted minutes I will charge them an overage fee in their next billing cycle, so the recurring payment may be different also.
From what I read I need to use adaptive payments is this correct, what functions should I use for creating, capturing and receiving payments.
Please help, I'm really in a bind.
There are many products that will do this. Avoid searching for "Recurring Payments" as that is generally used to refer to specific, relatively fixed payment schedules (like subscriptions) that you set up once with the payment partner (PayPal) and they execute the payments on that schedule for you. These schedules can be configured somewhat flexibly (e.g. free or reduced initial payment) but require that you can state the schedule & amounts in advance.
If you have more variable needs to collect payments from your users then you generally manage the timing and amount of the payments yourself; then you just need a mechanism for billing the user, ie a billing agreement.
PayPal products that support some form of billing agreements include PayPal Reference Transactions, PayPal Adaptive Payments, and the PayPal RESTful Payments suite.
Getting into opinion territory here, but of these three I would recommend either Reference Transaction (as the longest-standing, most mature and widely used solution) or the RESTful payments suite (as the latest and greatest solution) over Adaptive.
I'm going to offer my customers a selection of subscriptions to digital content. I want the customer to be able to add or delete subscriptions later, with as little hassle as possible.
It seems that if I use Paypal vault, I can collect the card information on the same subscriptions screen without multiple redirects and later change the monthly total without another checkout process or even customer sending approval to Paypal!
Does Paypal allow this? It seems too easy and also too permissive. Also, do I need to worry about PCI compliance?
Does anyone know a better way to do this (with or without Paypal)? I don't know how to use paypal recurring payments without a lengthy checkout if they ever change their subscriptions. Google wallet does not have subscription cancellation in their API! Several other alternatives only allow preset subscription amounts.
The CSC/CVV is missing from the examples here: https://developer.paypal.com/docs/integration/direct/store-a-credit-card/ which makes me think you cannot use the card at will. The customer is probably going to be asked for authorisation.
Normally your online payment provider needs to support recurring payments (installments, subscriptions). PayPal does, there's a specific API:
https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/installment_buttons/
For the customer it's one-off, then the card is billed, say, monthly.
I am using PayPal PreApproved payments for my crowd funding website, where project backers are only charged if the project is successfully backed.
I am worried that high rate of payments will fail when the PayPal API tries to collect the funds when a project is successful:
a backer might not have any funds in their PayPal account
a backer might close their account once the project is successful (to intentionally stop payment)
a backer might remove/cancel their preapproved payment
etc...
There are a number of ways that the payment could fail which would mean that the project owner would not get their funds.
Can anyone suggest a way of tightening or securing payments. Please note, that PayPal will only allow you to use PreApproved payments for crowdfunding. Please also note that project owners need to be able to receive the funds from my site. Sometimes, these funds can be as small as $10 or up to $10,000 so we need to use PayPal to pay them as there is not other method of getting the funds to the project owner
I've implemented Paypal Adaptive payments and used them for payments at http://www.wethetrees.com and we had the exact problems you are describing. The capture rate is almost random, we were down to 35% with one campaign and had to manually send all backers invoices.
When capturing we had backers with closed/unauthorized accounts, insufficient funds, unavailable payment methods etc. We switched to just doing direct capture for a while, which is great since we get 100% of all pledges, but Paypal closed our account without notice when one of our campaigns mentioned the word "Cuba".
The solution in the end was to scrap Paypal so now we're using Wepay and Dwolla, and we're considering Bitpay (Bitcoin) as well. Seems to like Paypal wants to kill crowdfunding or doesn't understand it. Anything less than a 90% capture rate is totally unacceptable and will cause projects to fail.
Preapproval isn't the only thing they'll allow you to use. That's just one part of the Adaptive Payments API, but you could go with a delayed chained payment, too.
This way your account can be treated sort of like an Escrow. You can use the Pay API to create payments in the system that are split between receivers accordingly. Only the primary receiver would get paid at first, though, and then you can call ExecutePayment to submit the secondary payments from the primary account within 90 days.
This way the primary account holds all of the funds so they're available to pay out when the goal is reached. If the goal is not reached the payments could be refunded.