I am migrating a website that offers subscription services from Square Space to Woo Commerce. Both platforms were configured using our Stripe account.
I am trying to figure out if we can migrate our existing customers into the new Woo Commerce app, so that it will use the same payment information that is already stored in Stripe. Basically we do not want existing customers to have to re-enter their payment information as we know we will lose some customers during this process.
On the Square Space side of things: whenever a new customer is created they create a customer in Stripe, then make a request to the Payment Intent API, associate the intent token to the customer, and then use this to charge the customer every time a payment is due.
On the Woo Commerce side of things: we are using the official Woo Commerce membership and subscription plugins. Whenever a new customer is created, a customer is created in Stripe, a payment method is attached to that user, and then that payment is used to charge the customer.
So my question for anyone who has a deep understanding of WooCommerce, is there a way to update how Woocommerce is integrating with Stripe to try and use the payment intent API tokens that we already have for these existing customers?
As long as these Customers were created under your account, you should be able to leverage them.
As a small correction, you would not be referring to existing Payment Intents, but rather existing Payment Methods attached to the Customer. You could, for example, retrieve these for any customer from the API and then use one of them to create a new Payment Intent.
Whether WooCommerce needs to do anything to be aware of these existing Customers or Payment Methods I can't say, but you should contact them for support about that.
Related
I use “WooCommerce Stripe Payment Gateway” plugin. Now I decided to sell the website.
How can I connect the new owner’s Stripe account (instead of mine)?
The new owner must have the data of subscribers.
Thanks in advance.
I've seen Stripe doc but I'm not sure about the solution.
I found this solution on WooCommerce Subscriptions FAQ
Can I change the account used for a payment gateway?
Yes, if you want to keep the same payment gateway but you have changed
account, for example, due to a change of ownership, then it is
possible to still use the same payment gateway on your site but please
contact the gateway themselves and ask about transferring/migrating
the customer information to your new account, then update any API keys
or credentials in your WooCommerce payment gateway settings.
I'm currently migrating a website from WooCommerce to Shopware 6, which needs to support recurring payments for a membership subscription.
WooCommerce is still using PayPal Standard, which allows you to mix non-recurring line items with a recurring subscription, in a single checkout flow.
Shopware 6 uses the REST API, which doesn't appear to support this ability and the only solution appears to be using the Javascript SDK:
User clicks Pay with PayPal.
Subscription is created via actions.subscription.create
Dialog is displayed requesting approval.
Customer approves.
Submit original checkout.
Redirect to PayPal.
Complete payment.
Redirect back to website with confirmation.
A potential solution I'm looking into now is changing the return URL of the initial order creation to redirect to a billing agreement approval URL and have the return URL's of that redirect back to the original return url.
Overly complicated and the worse UX I've ever seen.
Before I tear what's left of my hair out, does anyone have any suggestions?
UPDATE
Although it isn't the solution I was hoping for, I ended up removing the Shopware 6 PayPal plugin and implementing my own payment method using the NVP API.
From the user perspective, there is only one approval process. In the backend, once the user has approved the transaction (that has been marked as needing a billing agreement) the transaction is verified and then a recurring profile is created.
There's no way to combine Subscriptions and one-time payments in a single checkout. Such items even require different parameters on the PayPal SDK line, if using the PayPal buttons to show an in-context experience.
The in-context experience is best, since it involves no redirects away from your site to PayPal and back. Here is the flow for one-time payments:
Make two routes on your server, one for 'Create Order' and one for 'Capture Order', documented here. These routes should return only JSON data (no HTML or text). The latter one should (on success) store the payment details in your database before it does the return (particularly purchase_units[0].payments.captures[0].id, the PayPal transaction ID)
Pair those two routes with the following approval flow: https://developer.paypal.com/demo/checkout/#/pattern/server
A similar (separate) flow can be used for PayPal Subscriptions. Only one subscription can be approved at a time.
I am working on integrating Recurring Payments functionality in Asp.Net based application where people can subscribe to a Service where they will be paying a monthly amount. I am trying to achieve the same using PayPal's Subscription APIs. One another aspect is where people will be making payments using their Credit Card instead of PayPal's account. I have tried to search for a sample code where I can see that Credit Card information is passed to the Subscription API but unable to find the same. Can anyone points me to a sample code where this is implemented or guide me on how I can do this?
PayPal does provide a Subscription only API for PayPal payments or Guest Checkout where buyer's prompt to create PayPal personal account. To achieve a Credit card subscription I'd reckon to refer to Braintree Vaulting functionality wherein you can have both Credit Card & PayPal.
Braintree Vault Overview:
Our Braintree Vault securely stores customer information – including payment method information – so you can safely keep customers on file.
The Vault is used to process payments with our recurring billing feature, and can also be used for non-recurring transactions so your customers don't need to re-enter their information each time they make a purchase from you.
https://articles.braintreepayments.com/control-panel/vault/overview
Thanks.
A client of mine wants to change payment service provider in his WooCommerce store. He has a few hundred existing subscriptions that need to be transferred to this new PSP. Basically, everything is done in order to do this, except for the configuration in WooCommerce. WooCommerce needs to know to use the new payment plugin's code to renew subscriptions. I know of the existence of this integration method but that's not the issue. That integration allows you to add the required metadata to orders (like credit card tokens) in the WooCommerce UI. That has already been done. I changed the _payment_method post meta of a test subscription to my payment method identifier and I set _requires_manual_renewal identifier to false however, for some reason in the UI it still says Manual Renewal under payment method.
What things do I have to change in the database in order to change the payment method?
I am working on this website: http://wolves.phiresky.com/
It is an ASP.NET webpage using entity framework.
How can I make this a shopping cart?
How can I make this a shopping cart which can integrate with PayFast.co.za Payment Gateway?
The way that most developers create a shopping cart, including myself, is to create a object, often called cart, and then place that cart object into the visitor's session. This way the cart is accessible via the session object each page request. Integrating with a payment gateway is a whole other matter. To do that you will need to review the api documentation from the payment gateway company and then call the payment api's as appropriate.
The easiest to get started with a payment gateway is to try out Paypal, they offer test accounts and there is plenty .Net documentation to get you started. So using that you can run a test and see how online payments can be integrated. Also i see your prices are in ZAR, there is a couple of SA based payment gateway companies that you can easily integrate with, just run a google on SA payment gateway companies.