Do changes need to be made to the Moto Sagepay backoffice integration to support 3D Secure V2? - opayo

We currently utilise MOTO and Sagepay within our ERP software to process credit/debit card payments in the back office. Looking on the sagepay system, these come through as using the 'Direct' system, which the 3D Secure V2 details page suggests will have to change to support 3DSV2. However, 3DS isn't currently used at all in the back office. Will this change, i.e. will 3DSV2 be mandated for transactions for this, or can we continue as is and not worry?

Strong Customer Authentication is a requirement for all ecommerce transactions. It is AccountType=E in Sage Pay Direct. All MOTO transactions are AccountType=M and don't have 3DS by default. Make sure that your customer is off-session and payment is made by your employee in the back office system, not by the customer.
Check also https://www.sagepay.co.uk/support/12/36/3d-secure-explained

Related

Is a marketplace of Square Online Stores possible?

I want to develop a market place store front for farmers, but use Square as my payment gateway. I have achieved this using Stripe, but they do not have the in-person payment option and that is crucial for the business model we want.
I would like to know do you allow application fees that go to the marketplace owner on transactions? If not, how do you propose that a user of the payment gateway that is building a marketplace get paid. I need to pay the vendor AND the marketplace owner. I saw that with OAuth, you can connect to up to 10 merchants from your merchant account. How am I supposed to use this information to get paid?
Can I create a separate fee transaction/transfer on a merchant account that goes into the marketplace account? If so, I would incur the 2.9% +30 cent fee for a small transaction of maybe 40 cents. Is there a way to avoid that?
The Square Connect API does not currently support additional application fees on top of API charges (aka "multi-party payments").
While the API can be integrated into your platform as an e-commerce payment gateway, it is not currently recommended for platforms that require multi-party payments.

Automating payments through paypal

I am new to e-commerce development. In my marketplace application, I have three parties involved: Me, customer(end user) and vendor. The customer pays to me for a service to be done by vendor and when the vendor completes the service, I have to transfer the payment to them. So essentially the business logic is:
Customer pays to me through paypal/credit card/apple pay etc.
I ask the vendor to serve the customer.
When customer confirms the service, I pay the vendor's share.
Customer may also ask for a cancellation.
So, I thought to use braintree to collect the payment from customer, but I am not sure how to transfer the vendor's share automatically on a certain day of week? So for example, suppose on every Monday, I want my system to go through the completed services and transfer the vendor's share. Assuming each vendor has got a paypal account, can I do it through paypal? Is there a way to transfer the vendor's share from backend without asking me for the credentials or any conformation?
Thanks in advance.
Yes you can do this programmatically through REST APIs. You can do this by using PayPal's Mass Payment system. It's called Payouts when you are using REST APIs. I'm not sure if there is a Magento extension for it. You do have to be approved for it. Just go to your REST Applications and enable Payouts.

Delay Paypal payment - Braintree APIs

I am developing a website that offers car-washings in all places publicly available through geolocation. However, due to weather instability, bookings can be cancelled at any time; instead of issuing expensive refunds, I would like to charge customers only once the washing has been performed.
I would like to accept Paypal payments and was suggested to use Braintree. Do you know if it is possible to delay charges with Braintree APIs on Paypal accounts?
I use Laravel 5.1.
Thank you
I would recommend using PayPal Preapproval profiles, specifically the Preapproval API to setup the profile, and then you would use the Pay API to process payments using the preapproval key for a given customer.
This PayPal PHP SDK makes all of those API calls very quick and easy, and it's available on Packagist so you can load it up in your composer.json for Laravel and be running in no time.
It has samples and empty templates for you to work with to make the Preapproval and Pay calls.

What are CreateToken and StoreToken in SagePay Server V3.0?

We are upgrading our SagePay protocol from v2.23 to 3.0 to support surcharge fees. In v3.0 transaction registration post there are CreateToken and StoreToken which was not in the earlier version. What is the reason for create and store tokens? I went through the document but couldn't find a clue.
The link provided in the above post links to advice by one of our Sage Pay Partners so take a look at it.
Token allows shoppers the option of storing their card details (as a token) to their account on the payment page during their first purchase instead of having to set it up manually afterwards. Single click purchases for repeat customers will become much simpler and quicker to set up.
To view the Token Guide go to here, scroll to the bottom of the screen and select the Download the Documents option within your preferred method of integration (server, server inframe, direct). Within the guide it explains creating and storing a token.
If this is a service you would like enabled on your Sage Pay account our New Business team are available 0900-1800 on 0845 111 4466. Prices for Token are available via here. If you have any other questions, our 24/7 Support team can assist to on 0845 111 4455.
Sage Pay Support.
I believe this is related to their token system, allowing you to store and send card details as a token.
If you don't use their token system you don't need to worry about it.
Sage Pay have destroyed their content recently so it's hard to find anything, here's a quick article on their token system - http://www.metakinetic.com/blog/2013/09/sage-pays-token-system-and-advancements-in-payment-gateways/

Does Paypal Payments Pro work directly with magento community to accept credit cards for recurring billing?

I have an online subscription store in magento and I was looking at using Paypal payments pro to accept credit cards/debit cards (UK based) to accept payments on recurring basis.
Can I can directly enable Paypal payment pro in magento to accept credit cards for recurring payments or does it require an external plugins (such as aheadworks etc.) for it? There seems to be very little information about recurring payments online and the support staff at most of these companies speak extremely cryptic language.
I tried the integration steps that I found in a Paypal guide online that enables Payment Pro in magento. But when I do that I only get an option to pay through a paypal account. What am I missing here? Do I need an external plugin to accept credit cards?
First, disclaimer, I am working on an US PayPal integration, not a UK PayPal integration, so there may be differences based on that.
Your question is a scenario that I am presently working on. That is, having BOTH direct credit card payment AND PayPal Express Checkout for purchase of subscription-based products (e.g., creating recurring payment profiles) with PayPal being the provider for the direct payment method (via either Payments Pro or Payflow).
There are limitations with Magento as far as recurring profiles are concerned. PayPal Payments Pro does integrate with Magento, however it is not a supported method for setting up recurring profiles in PayPal. You need to utilize Express Checkout.
There is a third-party extension -- "Subscriptions and Recurring Payments" -- available from AheadWorks that provides expanded functionality for recurring payments. The older version (1.9) does support the use of PayPal Payments Pro or Payflow Pro, but NOT Express Checkout. The newer version (2.0) supports the use of ONLY Express Checkout. So you get one or the other. Technically, it is feasible to run BOTH versions of SARP, but it is a hackneyed, server-intensive approach and not one that I would recommend.
If you want to do both Express Checkout -AND- direct credit card pay (via a PayPal product), you have to dive into the deep end of the pool and extend the existing PayPal module in Magento. (I know this, as I am currently in that deep end of the pool!)
Sorry this does not "solve" your problem. I've spent several months doing discovery work on this specific situation and the result was that I either:
a) Hack Magento's PayPal module to do what I want.
b) Create a custom module that extends Magento's PayPal module.
c) Create a standalone transaction API with a separate Magento module to interface to the API.
Payments Pro is for direct credit card processing, so if you have it enabled you would get that option.
I'm pretty sure in Magento when you enable Pro it requires Express Checkout to be enabled as well, so you'll see the Checkout with PayPal button and that would have them just sign in. If somebody clicks the regular checkout button, though, and goes through the remaining steps it'll allow them to enter credit card details directly.
Payments Pro (recurring payments) do not integrate directly with Magento. You can however create recurring profiles by creating billing agreements with PayPal
A billing agreement is a purchase/sales agreement between the store and the customer that is signed/authorized on the side of a payment service. With the Billing Agreements functionality introduced in Magento Enterprise Edition 1.9 and Magento Community Edition 1.4.1, individual customers purchasing products from a web store on regular basis can place sales orders without entering payment information again and again; they can simply grant the authorization to the payment system once.
In other words, a billing agreement is a payment method that allows customers to place orders without providing payment details to the store. After the customer signs a billing agreement with the store on the side of the payment service, the latter provides the store and the customer with the reference ID for the signed billing agreement. The reference ID is a unique number assigned to a billing agreement by the payment system. During further purchases, the customer selects the billing agreement as the payment method and uses the billing agreement reference ID. No other payment information is required for placing an order. The payment system verifies billing agreement information and whether the payment can be fulfilled by the reference ID specified by the customer. After the payment system performs the payment transaction, the reference ID is returned to the Magento system and an order is placed. After a billing agreement is signed with PayPal, the store owner can charge the customer’s PayPal account directly.
Currently Magento supports using only the PayPal payment system for the Billing Agreement functionality. Prior to using the Billing Agreements functionality, the store administrator must contact the PayPal Merchant Technical Services to enabling the billing agreements (reference transactions) for their PayPal merchant account.
More information listed here: http://www.magentocommerce.com/knowledge-base/entry/setting-up-billing-agreements-through-paypal//

Resources