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.
Related
I'm using MassPay Paypal API to make payments.
I was able to test it and is working pretty well using sandbox accounts.
The problem is I couldn't find a way to identify if the email that is going to receive money is a valid paypal email.
I tested it using a fake email and money was taken from the payer sandbox account even though the email (the one that should receive the money) doesn't have a paypal account associated, and the API response was as if it was a successful request.
I found this method to get the verification status of an account, but there is no much info in the documentation or any other info that helps me understand if this is what I'm looking for or how to apply it.
You will need an API operation called GetVerifiedStatus API Operation under PayPal adaptive accounts. Refer the below:
https://developer.paypal.com/docs/classic/api/adaptive-accounts/GetVerifiedStatus_API_Operation/
https://developer.paypal.com/docs/classic/adaptive-accounts/gs_AdaptiveAccounts/
Sample API request:
API end point: https://svcs.sandbox.paypal.com/AdaptiveAccounts/GetVerifiedStatus
requestEnvelope.errorLanguage = en_US&emailAddress = email#test.com&firstName = Firstname&lastName = Lastname&matchCriteria = NAME
Currently, payments processed through certain credit card processors (example: Authorize.net) can be set to first authorize the fund, then later capture them when prompted in the UI via the admin interface.
I am hoping to capture funds of authorized orders (Big Commerce status 'awaiting payment') via the API rather than through the UI. I have not been able to find anything but a post from 3 years ago saying it was not yet possible. Is there now a way, or is this still something that cannot be done?
old thread: Is it possible to "capture funds" for authorized credit card transactions via the API?
It isn't possible to capture funds via the API today. The API is meant to Create, Read, Update, or Destroy entries and nothing is exposed to the API that would allow you to execute an action between BigCommerce's core application and the payment gateway .
We are using Woocommerce along with PayPal Pro on our website.
We are using the CloudIQ basket abandonment system and need to add a PayPal API request call to be made after the customer completes the checkout process.
Does anybody know if this is possible in PayPal and how I do this?
Thanks
Not quite sure about your exact request. But if you are referring to the data collection API call in PayPal, you can refer to the link below about PayPal Instant Payment Notification (IPN).
https://developer.paypal.com/webapps/developer/docs/classic/ipn/integration-guide/IPNIntro/
In addition, PayPal have Classic API and REST API for your reference in the link below.
https://developer.paypal.com/docs/classic/api/
https://developer.paypal.com/docs/api/
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.
Can someone explain the difference between the two? From what I have read, subscription is the one where you grab the HTML button from PayPal, whereas recurring is done via the API.
Is that it or is there more to it?
If so, how do subscription customers cancel their subscription?
(And, why does PayPal make it so developers have to trawl forums for answers?!)
PayPal's different type of recurring transactions:
Subscription
A subscription is created via a Website Payments Standard Subscribe button.
Before 2009, the subscription profile ID started with S-XXXXXXXX. You are not able to manage these subscriptions via any API calls.
After 2009 the subscription profile ID starts with I-XXXXXX. You are able to cancel these subscriptions via the ManageRecurringPaymentsProfileStatus API call.
Recurring Payments Profile
A recurring payments profile is created through the CreateRecurringPaymentsProfile API, and is accessible for both Express Checkout users, as well as those using Direct Recurring Payments as part of their Website Payments Pro Product.
If you use CreateRecurringPaymentsProfile via Express Checkout, you'll need prior authorization from the buyer, typically obtained by passing BILLINGTYPE=RecurringPayments in your initial SetExpressCheckout API call.
If you're using Direct Recurring Payments, you'll be able to directly pass in the credit card details into the CreateRecurringPaymentsProfile API call.
Recurring Billing
Available for Payflow Pro / Website Payments Pro Payflow Edition customers. This works similar to Direct Recurring Payments, except it's done through the Payflow API.
--
In all cases, a 'profile' is created, and PayPal is the one doing the actual billing on the schedule that you provided. You don't need to make any further API calls for the subscription / recurring payments profile / recurring billing profile to be processed.
And one more thing that I noticed.
When we make an API call to get the Transaction-details for a recurring/subscription transaction, the subscriptions which have their Profile-ID's starting with 'S-' have their TRANSACTIONTYPE as 'subscr_payment' and the subscriptions with Profile-ID's starting with 'I-' have their TRANSACTIONTYPE as 'recurring_payment'
Don't know if I am completely right.