Here's a quote from the Server Integration Protocol Documents:
Sage Pay’s Server integration provides a secure, simple means of authorising credit and debit card transactions from your website. In addition, you can accept payments via PayPal...
There is nothing in any public SagePay documentation that says clearly that you can't use PayPal with the Server iFrame integration.
One of the main selling points of the Server integration is that it can be used in an iframe on the customer's site, and if PayPal cannot be integrated via SagePay server in an iFrame then this should be made clear at the point where the docs say that the Server Integration allows PayPal integration.
I just checked today and in the actual documentation Sage Pay Server Integration and Protocol Guidelines 3.00 on Page 23 (5.0 Low Profile Payment Pages) there is a note confirming that PayPal is not supported for low profile payments (the one that use iframe).
Please note that you will NOT be able to accept PayPal transactions or
Local European Payments with the Low Profile templates enabled.
Although it's not stated anywhere in SagePay's public documentation The Server iframe integration doesn't support Pay Pal.
Related
I am using PayPal standard to make transactions in a WordPress website. I've set the API credentials and works perfectly means the transactions are done perfectly. But when I open the SandBox buyer account, I can see the following with pending status and the payments don't appear in the seller's account:
I've seen the PayPal official site to check this out and they say, sometimes they put on hold for verification. I would like to know if anyone has faced it before and how will this be available or completed later?
I've one another thing to know - I've used the PayPal Express Checkout plugin for transactions. But in the dashboard, it says WooCommerce Gateway PayPal Express Checkout requires OpenSSL >= 1.0.1 to be installed on your server and doesn't show the feature in the WooCommerce checkout settings. So do I have to set SSL for that?
Note: I am doing the above in localhost using WAMP.
You can't use localhost it's not a valid URL, PayPal can't access your local enviornment.Local host cannot be resolved on distant machines in case Paypal server.
Best way upload to the web, there's a number of free PHP web hosts out there if you don't have one.
I've recently tested sandbox on paypal. But I have to have Paypal Pro enabled to complete my transaction. According to information provided to paypal, the standard account should accept credit card.
(https://www.paypal.com/ca/webapps/mpp/compare-business-products)
So do I need to purchase Paypal pro to accept credit card or was this only required in sandbox?
Thanks
No, you do not. The basic, free account is enough. The Pro accounts simply come with premium features, like being able to process transactions without your customers needing to leave your website. The basic account redirects them to Paypal long enough to complete the checkout before redirecting back to your site.
Our .NET website uses Google Checkout to handle credit card processing and we need to migrate to another credit card service because Google Checkout is going away. Google Checkout used a .NET webcontrol that was easy to use and did not require that our site actually capture the credit card on a SSL site.
Does anyone recommend a replacement for this type of service that is easy to integrate using ASP.NET and leaves the security to them? Google provided a link to Braintree in their announcement but when I looked at that, it looked like we have to capture the credit card info. I'd prefer not to have the risk.
As #Aristos has mentioned, you can look into PayPal and/or Amazon Checkout.
Both of them provide alternative/3rd party checkout services - which is what Google Checkout is (was after November 2013).
Braintree is a payment processor and is very different from Google Checkout and any other checkout services - they offer credit card processing services (just like Authorize.net, Paypal Payflow, etc.). You will need to have/apply for a merchant account and comply with PCI DSS requirements when using such services (although they have services that minimize your PCI DSS work).
Google Wallet for Online Commerce (aka "Instant Buy") is a "layer" on top of such - which is the Google product/service that will "assume" the role of the "payment flow" (I hesitate to call it a "payment service" as it's really not) for merchants selling physical goods. It will work with (in fact require) your existing payment processor.
Wallet for Digital (aka "In-App Payment"), as the name implies, is the digital (product/service) counterpart of "Instant Buy". This is still a 3rd party checkout service - meaning it's still Google that handles the credit card processing (just like Checkout does/did). But it's primarily for digital merchants (selling digital products).
I have a requirement of integrating paypal in one of my asp.net website.
But I need to have a facility that One could pay through Paypal by using a credit card even if they don't have a paypal account. For credit cards, I don't have any idea of how can it be done through paypal development portal.
So can anybody let me know how to go about this and any reference link where I can find some details for this.?
I think one of the option I should go with is: PayPal Website Payments Pro but I have no idea about that and Is it a free service or a paid one.?
Thanks in advance.
PayPal Payments Pro does allow you to process credit card transactions using the Direct Payment API's. That product is currently available to US, UK, and Canadian merchants. The REST credit card process mentioned is only for US merchants at the moment.
Payments Pro isn't free. There a $30 a month fee.
Payments Standard and Express Checkout are both free and don't require that your buyers have a PayPal account but they are required to redirect to the PayPal site to log into their account or enter their credit card information.
If you have a more specific question I can help you further.
You can make credit card payments via the new PayPal REST API. Depending on your use case check the documentation for sale (directly charging a card), or authorize and capture. You also have the option of storing cards in the vault for later use.
I do not know whether you have gone through the Paypal developer's FAQ. Please go through this link once-
https://developer.paypal.com/webapps/developer/support/faq
Ideally to integrate paypal to a development site, A business account needs to be created.So when the user clicks on the pay now button on your site you send that userId and password to Paypal webservice and authenticate yourself as business user. it redirects to teh paypal site after authentication. So even if the user does not have an account with paypal they can pay using paypal(Which authenticates your site).
All the paypal integration is paid service.
Im looking for a Drupal6/ubercart2 payment module for any UK payment gateway which does'nt require PCI DSS compliance. My website is a relatively low transaction shoppingcart and acquiring compliance is over the budget.
For example, there is a module for 'Sage pay go direct' which requires the compliance. Sagepay also offers another solution called 'Sage Pay Go with Form' in which a customer is redirected to their site to store card details and make payments but as far as I know, there are no modules available.
Worldpay has a module but requires compliance.
We have the paypal module which I'm leaving as a last option as it requires users to create an account which is a bit off putting.
Any other gateway modules or cheap PCI-DSS compliant hosting providers anyone can recommend?
If your payment is processed by a third party (ie. Paypal, Sage) then you don't need to worry about PCI compliance for the most part, as it deals with the storage of payment information.
Also, Paypal Website Payments Standard has no monthly costs and does not require a Paypal account, users can pay using a credit card without signing up.
For smaller eCommerce clients (under around $2,000 per month) then it makes sense to use Paypal's free option (3% transaction fee). For higher volumes it starts to make sense to pay for a merchant account.