Is that possible to charge paypal customer manually. I can do it like user get redirected to paypal to confirm all the details but i do need that user allow my system to charge him every month without any confirmations from his side.
Currently i'm using the same approach as listed Paypal .Net Sdk example
But it doesn't have such a func to manually charge a user. If someone could chare links it'd be grateful.
Thanks in advance.
without any confirmations from his side.
That would require having a billing agreement on file. There are some reference transactions or "future payments" API solutions that use this, but the feature requires business approval from PayPal.
An alternative that does require confirmation from the buyer would be to send them a PayPal invoice, manually via https://www.paypal.com/invoice/create or programmatically via the Invoices API
Related
We are developing seller based system. In which seller can add there PayPal business email for getting payment in directly into there account.
Is there any way we can check seller added business email is correct or not using PayPal API? So we can reduce errors when customer placing order.
I have to validate from asp.net application. not in PayPal site.
Well, if you're verifying vendors, as per my point of view, you need to check account type as well, otherwise normal account will create an issue on placing an order..isn't it?
It's bit tricky, but you can use Log In with PayPal functionality in this case.
Create a button for your vendors to verify PayPal account, and call to the PayPal API. Once it redirect to your application you'll get response from PayPal with all the information including email, email_verified, verified_account and account_type. Then you can handle it as you want.
Doc: Integrate Log In with PayPal
Hope this helps!
This is more advice on how to go about upgrading to the PayPal .NET SDK. I've been playing with the SDK using the Nuget package and I'm able to stumble through most of the examples I can find. The issue is that some of the stuff we are already doing uses features from the other apis like merchant sdk dotnet
which is about to be deprecated. We are doing everything using the legacy stuff and i'm just not sure what the equivalent of those things are in the new API.
Here's what we are currently doing:
Accept PayPal Payment using Set/Get/Do Express Checkout
Accept credit cards using pay flow pro:
We get an authorized payment and then store the transaction id. This allows for saved payments without saving credit card numbers.
We do a sale payment by passing in a reference transaction id.
As an overview what we are trying to support is the ability to use paypal to checkout without a credit card, or allow the customer to pay with credit cards that can be saved and used again later. It would also be nice to add the lightbox or mini browser feature so the customer doesn't have to leave our site.
From what i understand so far, and please correct me if i'm wrong, is that to do the express checkout features we should start using the REST create payment function and pass paypal as the payment method. This returns a paymentId and a payerId that i can use later to execute a payment. I think i'm ok with all of that, but i am confused as to why the token that is returned doesnt work for getting the payment, i have to get a fresh token. I'm also not sure how to accomplish this inside a lightbox or mini browser.
I have also figured out how to do a REST payment with credit_card as the payment method, and i see that there is a way to save a payment to their vault. Am i correct in assuming that the REST api will not support payflow pro and that to accomplish what we were doing before with reference transactions and saved payments we need to move to the vault methods?
I can certainly help you with your Express Checkout requirement.
You can leverage PaySharp.NET in order to provide Express Checkout functionality. This SDK encapsulates the REST and HTML-parsing boilerplates necessary to fulfil an Express Checkout transaction. It also exposes async functionality.
This library removes the complexities of interfacing with PayPal, and provides PayPal metadata in comprehensible POCOs.
I'm currently implementing an Automation system for software selling through Paypal API. I have got the IPN portal working so it recieves IPN Messages from Paypal and is passed to a back-end service which files it in a SQL DB, Generates a license yadda yadda yadda. It also checks against an internal entry to confirm the payment recieved matches the actual price of the product purchased (Stopping them sneaky hackers). I have now got to a stumbling block where i would like to reject payments that are the incorrect price and i've trawled the Paypal API Developer documentation and can't seem to find what i'm after. My guess is making a call to the Adaptive or merchant API URLs but I cant find what info past auth credentials i'd need to send. Can anyone point me to the right page or 3rd party website with the information I can use to get this setup? an NVP solution would be preferred.
You can't really reject a payment at that point because the transaction has already been completed. All you can do is refund it, which you can do via the RefundTransaction API within your IPN script. This way you'll also get your PayPal fee refunded.
You've already got your logic in place to check if the prices match, so just add a call to RefundTransaction if the price does not match. You may also want to send an email notification to the buyer in such cases letting them know something was wrong with the pricing on their order so it's been refunded, and maybe even provide a checkout button for them to re-buy at the correct price if you want to.
I want to adding recurring payments to my application.
The requirement is as follows:
1.) User should be able to enter his/her credit card number, cvc and expirary in my application.
2.) I will submit the details along with his/her recurring payment option eg: 3 months, 6months etc
3.) Should receive response stating the recurring payments successful.
I went through the API but it didn't help.
I basically want to create a paypal direct recurring payment application (using C#). Any link or sample code to begin with is appreciated.
The API documentation you require is here
Most Paypal recurring transactions users implement a hosted page checkout, and i have not witnessed a single api checkout implementation. Do get in touch with Paypal as your page need to match up to certain requirements before you can collect credit card information on your webpage
I have some questions about Paypal adaptive payments as guest:
Do the users that want to do a purchase using their credit card information require a PayPal acount?, Is there any way to avoid this?. I'm considering to have many clients on my site thay may not have PayPal account.
Does guest payment supports the Parallel payment Schema or the Chained payment Schema?
If I'm using the guest payment default interface (the one provided by PayPal), should I still worry about having my site to be PCI compliant?. I'm not storing any credit card information about the users.
I've tried to find examples about how to invoke the adaptive payment api to get the Guest payment working without any success. Does anyone know where can I find an example for this?
Is Adaptive payment a feature of Paypal Standard?, or do I need to get the PayPal Pro subscription in order to get the Adaptive Payment Api working on my site.
Can anyone give me some assistance with all these?. Thanks a lot.
Well, here's what i found so far:
Do the users that want to do a purchase using their credit card information require a PayPal acount?, Is there any way to avoid this?. I'm considering to have many clients on my site thay may not have PayPal account.
Not required. You can use adaptive payments and pay as guest. Both Rest API and classic API support this payment schema. The Rest API relies on your site to handle security and PCI complience, on the second one is handled by paypal.
Does guest payment supports the Parallel payment Schema or the Chained
payment Schema?
Clasic API adaptive payments support to add multiple receivers and amounts when sendin payments, so yes, it is supported with this schema. Not sure about Rest API. The examples that I've found use just the Paypal to Paypal schema.
If I'm using the guest payment default interface (the one provided by
PayPal), should I still worry about having my site to be PCI
compliant?. I'm not storing any credit card information about the
users.
If you're using native Embedded payment flow with the dialogs and the javascript functions that paypal provides, no, it is not required. Paypal takes care of this for you. If you're using the Rest API, you have to use the payment with creditcard stored on paypal vault (however this force the buyer to have a paypal account). If you're using the Rest API to get credit card data, you have to design your site to be PCI Compliant.
I've tried to find examples about how to invoke the adaptive payment api to get the Guest payment working without any success. Does anyone know where can I find an example for this?
https://developer.paypal.com/webapps/developer/docs/classic/adaptive-payments/integration-guide/APIntro/ has Embedded flow example (however its really vague), http://paypal.github.io/ has examples for classic api implementation
Is Adaptive payment a feature of Paypal Standard?, or do I need to get the PayPal Pro subscription in order to get the Adaptive Payment Api working on my site.
Paypal pro is an account feature, not really related with the API for adaptive payments, or at least that is what I've found so far.