Hi, Isaac

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

That was good thinking, I can see you have found a great example of this point covered by my senior colleague, Aleksandar.

Basically, Amelia itself doesn't handle the payments but we have integration with several payment systems just to process the payment.

What you can do to, is to use this metaData description for Stripe, in Amelia Payments settings,

you can set various placeholders, same as it goes with the notifications in Amelia;

I just gave a brief example on that screenshot, for example you can set appointment price, customer's full name, and so on.

This should work, please try and let me know how it goes.

Hi, Isaac

Now i can see what you mean, thank you for these details.

I will have to check if we have a workaround for this.

As soon as i can confirm this with our senior Team, i will come back to you. Thank you for your patience.

Hi, Isaac

Sorry that it took me so long. 

We have found a workaround for this. Please try these steps:

Find and edit this PHP file with any text/code editor, located at:

 ../wp-content/plugins/ameliabooking/src/Infrastructure/Services/Payment/

StripeService.php

There, around line 52 add this code:

if (isset($data['metaData']['email'])) {   
 $stripeData['receipt_email'] = $data['metaData']['email'];
}

Like this:

I don't know if it's going to work, though, if there already isn't a customer with this email registered in Stripe.

-

Let me know how it goes, and if you need further assistance. Thank you

Hi, DesignBurst

This is a bit of an improvised workaround that we came up with some time ago.

We have not tested it yet to the full extent, it is still in a testing phase, but it should work.

We are not sure about situations if there already isn't a customer with this email registered in Stripe.

If you try, please let us know how it goes on your installation.

Our developers are doing their best to improve this and come up with a better solution, as soon as possible.

Hi, richard_oven

My sincere apologies for replying so late to this.

1. Thank you for the confirmation and for the added note about making sure to set the correct "email" field in the MetaData, we will note that for other users. 

2. About adding these lines as part of the plugin,

we will pass this as an improvement suggestion for our management and developers,

it has to go through testing to make sure that it does not affect anything else in the plugin for other users that use other payment methods,

but we will do our best to implement the solution in one of the future updates.

We can't guarantee an exact ETA, though.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Hi, Carrie

Did you try the modification that richard_oven suggested on the comment?

If you already tried that, and our workaround suggestion,

i can ask our 2nd level Team to check if we have any updated workaround that you could try.

Thank you

Hi, Carrie and Isaac.

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

@Carrie :

- Thank you for pointing that out. We will make note of this, and we will do our best to modify the workaround,

and to make improvements as soon as possible.  We can't promise an ETA , though.

2. In regards to taxes in Amelia,

our developers will start working to add a "taxes" feature in Amelia soon,

but i can't confirm exactly what this functionality will be and if it will be perfectly compatible with the payment integrations, such as Stripe.

I think it should be, but i have to wait for their development progress and we will see how it turns out.

If you wish to affect the development speed, you can search and upvote this feature for taxes.

Please feel free to search through our feature suggestion page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

I will elaborate a bit more in general on how payment integrations currently work with Amelia.

Amelia itself doesn't handle the payments, but we have integration with several payment systems such as: PayPal, Mollie, Stripe and WooCommerce.

 
Adding taxes at the moment is only possible to do with WooCommerce products for different services.

 By default, all services are connected to one WooCommerce product, but if you create multiple products you will be able to choose a product that will be connected to each service.
If you wish to try adding taxes with WooComerce,

once you enable WooCommerce as a payment method, go to the Services page, 

open one of the services and you will see a Settings tab. 

When you choose this tab you will see the option “Select WooCommerce product” where you can choose a product that will be connected to this service.
This way, you will be able to set different taxes and other WooCommerce options for each product and each service in Amelia.

Or you can just write the price with tax included and insert (Tax incl.) On behalf of the service.

-

@Isaac :

This PHP file can not be opened through your browser like that.

In order to get to the location of the PHP file,  

you will have to either get to the file via an FTP client and ask your hosting for FTP credentials( Such as FileZilla or any other FTP client),

or you can access it through your Hosting Panel, then find their "File Manager" tool, in order to see the plugin files.

This PHP file is located in your WordPress folder on the hosting server, then in this path:

 ../wp-content/plugins/ameliabooking/src/Infrastructure/Services/Payment/StripeService.php

There, around line 52 add this code:

if (isset($data['metaData']['email'])) {  
  $stripeData['receipt_email'] = $data['metaData']['email'];
}

Like this:

Just please make note of what Carrie pointed out, the meta tag needs to be "email" not "Email" or it will not work.

Let us know how it goes.

Hi DantianHealth,

Amelia itself does not handle any online payments and thus is not able to send a payment receipt from Stripe.

The only payment method that Amelia is handling is the "ON-SITE" method, where the user needs to go in and edit the Payment to set it as paid.

-

For any online payments,

Amelia has the integration to just send the booking data to a payment processor,

then your chosen payment gateway takes over the payment process,

and then, in this case, Stripe, is the one that sends a receipt since it is doing the payment process.

I can see what you mean, though, we will pass this feedback to our management,

and they will do their best to make a task for our developers to make improvements for our Stripe integration as soon as possible.

I can't say an ETA on it, though.

If you have an idea what kind of improvements you would like to see,

Please feel free to search through our feature suggestion page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Hi DantianHealth,

firstly my apology for the delayed response time.

-

I understand that implementing an improvement like this might seem easy from your end,

but in practice, our developers will first need to change the logic behind our Stripe Integration,

then our QA Team also needs to conduct a lot of testing to ensure that adding this metaData improvement will not have a negative impact/ or a bug to any other Amelia functionalities,

before it gets added to the Plugin's Core.

We are not able to comment about any competitor Plugins, as they have a completely different code, etc.

I passed this feedback and an improvement suggestion to our management;

they will coordinate with the developers to create a task for this improvement, as you described;

but i can't promise a realistic ETA when it will be added.

Our Planning Team is doing their best to manage task priorities, we take into consideration all our user requests.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Thank you again for this suggestion and feedback.

Hello NLP from scratch,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

We have this planned, but at this moment we can't say an exact ETA when our developers will start working on it,

our Planning Team is doing their best to manage priorities of each user request according to how many users request it , and how difficult it is to implement,

we will certainly do our best to add this as soon as possible.

If you wish to affect the development speed, you can upvote this feature suggestion on this page :

https://features.wpamelia.com/1129

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Thank you.

Hi Barbara,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

If i understood, you have succeeded in this workaround in the end?

If that is the case, that is great to hear.

Could you share what you did with us - if it is any different step or detail from the previous workarounds we had?

Thank you.

Hi Barbara,

Thank you very much for sharing these details and pointers for us.

We passed all of it to our developers, and we will do our best to make built-in improvements;

or at least to try to create a workaround that could be as easy as possible for our users.

Thanks again.