wix pay API confirmation user email header faulty

Ask the community
,
1

To Whom It May Concern,

I am having an issue with the confirmation email that users receive when they have made a custom payment on the website using the Wix Pay API.


It should state ‘Bedankt voor je betaling aan VOCAP VZW.’ English translation: ‘Thanks for your payment to VOCAP VZW’.

The payment processed correctly, all other information in the confirmation email was correct also.

Is there something in particular I can do to solve this issue? Or is it a minor bug?

Best regards,

Chiel Buseyne
On behalf of the Flemish Society for Industrial and Organizational Psychologists (VOCAP VZW)

2

Having similar issues with payments that are being processed:

984×515 17.1 KB

3

Hope you work it out quickly, it looks like a glitch. BTW: it should be “bevestigt”, not “bevestigd”.

4

Further issue: the Wix Pay API thinks manually closing the box of a Sofort payment by the user is a “pending” payment. This is ofcourse very wrong… I would kindly ask for an answer on this and the abovementioned questions as there really seem to be issues with this Pay API… As a paying customer, I am entitled to that. One should keep in mind that this is about payments, there is no room for error, it should be correct from the start.

5

Info, I have been looking for a day now where you setup the confirmation screen and confirmation email with Wix Pay. Looked thru Triggered Emails, Automations, everywhere. So, can you tell me, where is it hidden?

6

Hi!
Will be fixed today.
Sorry for the inconvenience!

7

Hi,
Thanks. We are on it. Will update you.

8

Well, thanks for your question!
Basically, when User closes manually tab - it is still Pending anyway because it was not finished. For instance, tab can be restored. This flow implies Pending status.

9

Hi!
Answering to your question - no, there is no ability to customize Emails. Regarding Thank You Page - it can be disabled or customized by code.

Thanks for your question!

10

@irakliyt Thank you. But in the above screen shot posted by Info, you can clearly see he can customize the email and there are vars in in that cannot be found elsewhere : $(data.paymentmethod). So where is this done?

11

Fixed.
Thanks!

12

@giri-zano Thing with $(data.paymentmethod) and $ {data.businessName} were bugs and it has been fixed.
However I am not clearly understand about what parts customize you are mentioning. Please, clarify and point items you want to ask.
Thanks!

13

@irakliyt OK, we are getting somewhere now. I will try to make it as clear as possible. I would like to know:
a) how I can translate the fields (name, email, etc) in the pop up window into another language (Spanish, Dutch)
b) how I can edit the confirmation email. Info, in the above screenshot, made a syntactical error spelling a verb, I pointed that out and he corrected it. So obviously he has access to the confirmation email, otherwise he would not have been able to. I have looked all over, but I cannot find this possibility. It´s not a triggered email, because those are agnostic about things like $(data.paymentmethod), I checked.
Thanks for your help, I appreciate it.

14

@giri-zano
а) You can choose site language you want to. Using Dashboard Settings. Go to My Dashboard (Editor-Settings) - Settings - General info - Regional Settings - Language.
b) I see posted screenshot from user “Info” 6 days ago and your’s pointing out the syntactical error. However I didn’t see screenshot he actually corrected it.

Anyway - checking.

15

@irakliyt Grudgingly, my humble apologies to b): I was sure I saw a corrected screen shot with “bevestigt” instead of the erroneous “bevestigd”, but, alas, I cannot find it, so I was probably wrong.
Which leads me to a more serious matter, concerning a): am I correct in stating that we have no control over the email that is being sent to the customer? That the language he/she receives is dependent upon the settings in My Dashboard (Editor-Settings) - Settings - General info - Regional Settings - Language. ?
Because if so, this is not going to lead to satisfactory results. The problems are twofold:
a) there are many countries in the world where the relation country-language > 1. In Belgium, they speak 3 languages (but nobody speaks all three), in Switserland 4, in Spain 3 (where, currently, addressing someone from Barcelona in Castillano instead of Catalan could lead to a cancellation of the order altogether) , in the US at least 2 and in the Netherlands 154.
We must have multi-lingual control over the confirmation text, this may never be an ukase from a software developer, never.
The second part of the problem is the chosen style and syntax used in a pre-cooked message. I can only assume that the above Dutch message is a standard one, non-editable. Not only did it have a spelling error, but, more seriously, it uses the second person singular instead of the third. In current Dutch, this is, unfortunately, rather common. But in Castillano (which you would call Spanish), if you really want to abuse someone, you switch to second person (singular or plural).
And what about variants in languages: there is, for instance, a huge difference in Spanish- Spanish and Argentine-Spanish, where the same words have a completely different meaning (coger-tomar).

In short, I am still not sure if we can or cannot edit the confirmation email (but I fear we cannot), but if so, I can tell you right now that this is going to be a huge problem. Simply give people the freedom to send the message they see fit to send to their customers: they now them best.

And I haven´t even addressed the language in the `pop-up window when you are dealing with International markets.

This is one of the few times in my life that I hope I am wrong, that Wix has NOT chosen to make the pop-up dependent upon some language setting and that the email is NOT pre-cooked, rigidly based upon the same language setting and, possibly, full of silly errors.

Repeating my appreciation for your time spent,
Giri

16

@irakliyt Please let me rephrase my question so that you can thoroughly grasp my issue.

The problem lies within the client-side code and more specifically in the result.status === “Successful” option for Sofort payments.

The status “successfull” does not recognize a ‘successfull’ Sofort payment as such. So if I specify in the code that on the result.status === “Successfull” I want the code to go to a page (which I did NOT do below), this works perfectly fine for credit card payments and PayPal payments, but not for Sofort payments as it does not recognize a ‘successfull’ Sofort payment as === “succesfull”…

I tried to ‘solve’ this by letting the “pending” option do the same thing as the “successfull” option. However this tweak had unintended consequences. Once the Sofort payment was made, the code did continue. But it also had the unintended side effect of continuing with the user closing the box without a succesfull payment. So this second appraoch does not work. :frowning:

Additionally it should be noted that the payments with sofort DO work: they are visible in STRIPE and the user receives an email about his/her payment. Just the “successfull” option in the user end code seems to fail for Sofort payments.

In my opinion this bug is more serious than the one adressed above with the faulty email fields. If I was not so sure about my case, I would not have adressed it. But I am convinced you will find a solution for this as well :slight_smile:

Also you need to better explain in your API manual what the different result.status options mean.

Best regards,

Chiel Buseyne

import {createMyPayment} from 'backend/pay';
import wixPay from 'wix-pay';

export function myButton_click(event, $w) {
  createMyPayment()
    .then( (payment) => {
      wixPay.startPayment(payment.id)
        .then( (result) => {
          if (result.status === "Successful") {
            // handle payment success
          } else if (result.status === "Failed") {
            // handle payment failure
          } else if (result.status === "Pending") {
            // handle payment pending
          } else if (result.status === "Cancelled") {
            // handle user closing payment panel
          }
        } );
    } );
}
17

@info85223 Thanks for clarifying.
We will look into this deeper and find better solution. Appreciate for your feedback and efforts on it.
That means for us. Once will be ready - we will update you.

18

@info85223
Hi!
Fixed.
Thanks!