Does anybody know of a way to charge a customer 30 days later on WooCommerce? We use Stripe as our payment method.
We want to allow customers to "Buy now and pay later"
I thought WooCommerce Deposits would be perfect but unfortunately, they do not offer an automatic charge, you have to have the customer pay through a link later.
You may try to use Stripe's Charge API with the auth and capture flow. This way first you authorize the transaction - i.e. reserve the money on the account. To do this, you need to send a capture: false parameter when making the charge request.
Later you need to issue a capture charge call, otherwise the auth will be released, meaning you won't get the money at all.
Read the docs on Stripe how long do they hold the auth part for, usually it's 7 or 14 days on other providers.
Related
I'm looking for a way to charge users to post to a directory site.
I've tried using the WPMU Dev directory plugin, but it didn't have this feature.
You could either charge a one time fee per post, or you could charge a monthly rate.
Oh, and for now the gateway would be PayPal.
Cheers.
There are a number of ways you could do that on the PayPal platform, but with the limited info I have here I would probably recommend the Adaptive Payments API, specifically Preapproval and Pay.
Using Preapproval, you would have users create a preapproval profile which gives you authentication to make payments on their behalf without further approval. This way you could take payments based on any trigger you want, be it a post, a specific date coming up, or whatever.
The gateway I am using is Cardsave (http://www.cardsave.net). I obviously can't store credit cards on my servers, but to store credit cards on their servers, there needs to be an initial transaction. I am writing a billing management website that customers are going to be migrating to from other systems. There wouldn't be a reason to have their clients pay in between billing cycles.
The only solution I can think of is making a small payment to the credit card (like $1, PayPal style) and then either crediting this amount back to the customer on the next billing cycle, or issuing a refund. Is this the correct approach?
Is this the common way of handling recurring monthly 'subscriptions' where the amount is variable every month and don't start right away. For instance, is this how trial periods that require your credit card information to start is handled?
$1 charges are no longer allowed by Visa and MasterCard. You can do $0 authorizations so if your processor allows that you'll probably be able to do your original plan.
Some payment gateway providers, like Authorize.Net, offer services that allow you to create payment profiles and charge against them at any time for any amount. Their service is called Customer Information Manager. You should see if your provider offers a similar service.
For Cardsave Payment gateway you have Automated Subscriptions and Cross Reference Transaction Code Examples
For the reference check out this link: Click Here
My client has a drupal + ubercart site. now he wants to setup a product for preorder. Meaning, take the credit card info now, but charge only after 5 months. Is there any way this can be achieved?
originally I thought about using authorization (the site is using paypal as gateway). But, the authorizations lasts only 29 days.
I understand that storing all the credit card info is a big no-no. but maybe there is some solution to this?
This would need PayPal Preapproved Payments, available via the PayPal Adaptive Payments API.
Buyers would authorize (preapprove) you to charge them at a later date for up to a certain amount. When that time comes, you would simply call the PayPal Adaptive Pay API and charge them.
For an example checkout flow, see the Adaptive Payments Developer Guide (page 25)
See also page 171 onwards for an integration example with the Preapproval API.
I am developing a website with online payment.
Payment is done using Paypal NVP Api.
There is need of a facility to store customers credit card details(not in database) once they register to Website.There onwards whenever they order these details will be fetched, Customer need not enter their card details for every order.
So is there any facility to create a profile n store credit card details of customer, as it is there for recurring payments?
This is not the idea of paypal, you are not allowed to store the customer credit cart and use them later by your self - if you do that, paypal see its and block your account in no time.
The paypal offer recurring payments, so you only need to initialize correct the paypal options and you have your solution.
Or get permission from visa, or master-cart to have the ability to keep local the credit cart informations. I must say that is very dangerous and if your system is not well protected you put your clients and your business in a big risk to lose the credit cart data and have real problems.
to store customers credit card details(not in database)
Where to you wish to store it ? in the paper :)?
Customer need not enter their card details for every order.
This is something that paypal take care of. You do not have to do something about.
You may want to check Recurly.com
they are providing support for Paypal and other gateways too. Plus great API documentation.
using it and definitely recommend it. 10 out of 10
I am willing to know how the process of sending the user account information, payment amount information as well as product/service id information to the payment gateway is conducted.
Where does the data from my last jsp page goes out there in the payment gateway?
How the transmitted information is synchronized and understood when they don't know my thing about the product/service m offering,prices and other flexibilities associated
or whether they expect me to be preparing a fully accomplished shopping cart and the finally tell them the final amount the buyer has to pay. what actually happens out there?
Most inline payment processors are willing to just take an amount. If you're sending the user to an external payment site, you'll normally have to send a cart. Each different payment processor will most likely give you a schema or webservice to use to send them a cart. The cart won't stay synchronized, just updated whenever you send that user to the payment processor.