|
nmaddock
|
April 25, 2017 at 6:05 am
Hi guys,
we are going live this Friday and have noticed in final (live) Stripe testing, that when a ticket is purchased, there is no customer record created (and linked to payment) and no payment receipt is sent out from Stripe.
We have turned on, ‘Collect the users billing details’ in EE Stripe settings, but this makes no difference.
I’ve noticed from some older topics that this may be down to ‘request-email’ not being sent to Stripe?
This is going to cause us two issues –
1. When looking in Stripe it’s not easy to see all payments made by one customer
2. Payment receipts are not sent by Stripe to the customer
Can you help please?
This is really urgent!
Thanks.
|
|
Tony
|
April 25, 2017 at 7:33 am
Hi there,
The Stripe add-on does not create customers within Stripe, it uses a charge call to charge the users card within creating an individual customer within Stripe.
I’ve noticed from some older topics that this may be down to ‘request-email’ not being sent to Stripe?
Do you mean receipt_email? If so we don’t send that when making the charge request because it will override any settings you have on your Stripe account:
https://stripe.com/docs/api#create_charge-receipt_email
If receipt_email is specified for a charge in live mode, a receipt will be sent regardless of your email settings.
So if a user didn’t want to send the email receipts from Stripe and had them disabled in their account the above would force them to send.
1. When looking in Stripe it’s not easy to see all payments made by one customer
You can search within your Stripe payments by email to view all payments made by a user using that email address.
2. Payment receipts are not sent by Stripe to the customer
The receipt should send regardless of creating a customer within Stripe, do you have email receipts setup within Stripe:
https://dashboard.stripe.com/account/emails
Do you have at least ‘Successful Payments’ checked? – http://take.ms/M5v8K
|
|
nmaddock
|
April 25, 2017 at 7:40 am
HI Tony,
thanks for the reply.
Yes, email receipts are enabled and Successful Payments checked.
In the Stripe payment record, in the Receipts History section, you see “No receipts sent — No email address for this payment”.
How can I force a receipt to be sent please?
Thanks
|
|
nmaddock
|
April 26, 2017 at 9:16 am
bump! 🙂
|
|
Josh
|
April 26, 2017 at 9:47 am
Hi there,
I can share this documentation with you:
https://stripe.com/docs/dashboard/receipts
and
https://support.stripe.com/questions/why-am-i-not-receiving-confirmation-receipt-notification-emails-from-stripe
If you were using your live API key when you made a live transaction, that should have triggered an email. Usually you get “No receipts sent — No email address for this payment” if the there are testing API keys involved.
If have further questions about Stripe and email receipts you can reach out to Stripe support.
|
|
nmaddock
|
April 27, 2017 at 2:51 am
Hi Josh,
yes, we’re using live keys for this final test and have the receipt settings enabled.
So there’s nothing else to be done or set at the EE end; it should work out of the box?
Receipts are being sent when memberships are being purchased via PMPro, but they create a customer record in Stripe.
We’ll get in touch with Stripe support.
Thanks
|
|
Josh
|
April 27, 2017 at 11:14 am
Not necessarily, and we’re looking into this and I figured you could also help look into this since you bumped the thread.
|
|
nmaddock
|
April 28, 2017 at 2:34 am
Ok Josh.
I have raised this with Stripe support and waiting for a reply.
If you think of anything else, that would be appreciated.
Thanks
|
|
nmaddock
|
April 28, 2017 at 8:21 am
Hi,
I understand why you’re not passing an email address in the receipt_email variable as that overrides the Stripe ‘send receipt’ setting, but it looks like Stripe is expecting an email address in a certain place to use anyway and it’s not there…
Hence In the Stripe payment record, in the Receipts History section, you see “No receipts sent — No email address for this payment” ?
|
|
Josh
|
April 28, 2017 at 8:33 am
We did some checking and had an idea for adding a filter hook to allow for sending additional params to Stripe. The filter hook is included in this branch that you can download here:
https://github.com/eventespresso/eea-stripe-gateway/archive/master.zip
Once you have the above branch installed, you can make use of the filter hook by adding the following code to a site specific plugin:
https://github.com/eventespresso/ee-code-snippet-library/blob/master/payment-methods/tw_ee_stripe_data_array.php
You can add the above to a functions plugin.
|
|
nmaddock
|
April 28, 2017 at 9:12 am
thanks Josh, we’ll take a look!
Out of interest, if we have a branch of core or an add-on installed, how do we know when the next release of core or an add-on includes that branch – so it’s safe to upgrade?
|
|
Josh
|
April 28, 2017 at 9:23 am
You can check the change log for that information.
|
|
nmaddock
|
April 28, 2017 at 9:50 am
Thanks Josh.
That change for getting email receipt in Stripe works a treat!
|
|
Josh
|
April 28, 2017 at 10:45 am
OK thanks for the update. We’ll be sure to include the new filter hook in EE4 Stripe Payment Gateway v1.0.15.p.
|
|
nmaddock
|
May 2, 2017 at 2:46 am
HI Josh,
FYI, I received this back from Stripe support –
I had to bring in a little help on this one, but we were able to get to the bottom of what was going on. After taking a look at the log for each charge, we found that in the API coding, you have the email being listed under name, rather then as their email. When the code gets to the point where it’s suppose to initiate and send out to the customer, it’s reading a name instead of an email. To help resolve this, I was able to pull a link that will assist in editing your API:
https://stripe.com/docs/dashboard/receipts#automatically-send-receipts-using-the-api
|
|
Tony
|
May 2, 2017 at 7:01 am
Thanks for posting the response.
The link they’ve given is for the receipt_email which is what the above function your using uses.
Regarding this:
After taking a look at the log for each charge, we found that in the API coding, you have the email being listed under name, rather then as their email. When the code gets to the point where it’s suppose to initiate and send out to the customer, it’s reading a name instead of an email.
I’m pretty sure that’s connected with not using Stripes ‘customers’, we actually do send the email address to Stripe (within the email field, not name) the charge returns from Stripe with the name field set to the email address we passed in earlier (again likely because there was no customer created).
|
