thank you for your reply, here is the screenshot.
thank you

@moumita , OK, thank you. We look forward to your feedback.

@sangita , Is it absolutely compulsory to generate a stripe token to validate the use of stripe for our vendor customers? Can we do without it?
thank you

@sangita The aim is to be able to access the entire account management interface and bank details from the site. We don’t want sellers to be redirected to stripe. We thought that only custom mode would allow this

@moumita How many days do you think?

the problem is that we have up to 1 month to test and cancel the purchase of the multivendor x extension if necessary.
But the month will be up in … 2 days!
Your extension meets our needs, but if it’s technically impossible for us to be sure that it’s implemented and functions correctly, we’ll have to cancel the purchase within 2 days.
What do you suggest?
Thank you

Hello, is the stripe custom mode integration still on schedule for this week? thank you very much.

@sangita , Hello, you were supposed to get back to us three weeks after taking care of our issue, but we still haven’t received any updates regarding a fix or any other progress. Where do things stand now? Thank you.

Are you serious ?
We have an annual subscription and you aren’t able to give a date ?

thank you Sangita, I wrote to the refund team.

@sangita I have already given you that information,we’re in france, but we chose another solution following your lack of responsiveness.

Please tell to the refund team to contact us (we wrote to them yesterday), to respond to our request of refund. thank you.

@sangita @moumita
The refund team told me that they refused to issue a refund.
I would like to remind you once again that your development team had not integrated a feature for our country at the time of purchase, even though it was mentioned in the description (Stripe).
The contract is therefore implicitly null and void.
This does not apply to the month in which payment was due.
You are now in the process of integrating the Stripe solution for our country, very good.
You’re asking us to test it!
We did not pay $300 to be your beta tester and there’s no guarantee that a bug won’t appear in a few days, weeks,… of use.
As I told you, after several months of waiting, given your delay we decided to take another solution.
Please ask the refund team to proceed with the refund.
thank you.

@sangita
It’s been 2 months to the day since we pointed out to you that stripe was not working. 2 months that we had to wait for you to correct the problem.
As I’ve already told you, we contacted stripe who confirmed that there had been no update on these tokens for France since 2018.
We’ve had to push back our timetable and put ourselves in a complicated situation.
We are tired of this waste of time.
Thank you for accepting a refund for a feature that was not implemented at the time of purchase.
Please take this last message seriously.

@sangita,
Well, no response from the refund team.
We are disappointed and angry.
2 months wasted, 2 months late because contrary to what you said, and as confirmed by Stripe, you didn’t implement the feature for our country when we bought your extension.
Your late response to the problem forced us to change our solution.
But you refuse to refund us. This is unacceptable and unprofessional.

yes sure.

@sangita It’s now been over two weeks since I first contacted the refund service, despite your agreement.
Of course, there’s still no refund.
To tell the truth, I was expecting one.
Right from the start you’ve been constantly putting things off, drowning out the issue…
It’s infuriating.
I’m not going to waste any more time trying to argue with you, there’s no point.
This experience will teach me a lesson.

@sangita, Hello
I’m coming back to give you an update.
It’s been over 3 weeks since you were supposed to fix the custom stripe mode problem.
Now, almost 2 months after purchasing your extension, we’re unable to go any further.
This has disrupted our entire development schedule.
We’ve had a look around. When you look at the stripe updates page, you can see that the updates are minimal and regular: https://stripe.com/docs/changelog
From this page, we can see that there are no particular difficulties in relation to the problem we are experiencing:
https://stripe.com/docs/connect/account-tokens
Could this be a bug on your part?
What do you intend to do?
Thank you for your understanding,

@sangita,
Hello, we bought your extension 2 months ago.
Your team has been talking about fixing the problem for almost 1 month now, but it still hasn’t happened.
We have conducted some research on our end. As we can see on this page, updates are regular and minimal: https://stripe.com/docs/changelog.
On this page, the usage of tokens does not seem to pose any particular difficulties: https://stripe.com/docs/connect/account-tokens

How is it possible that the issue has still not been resolved?
We find it unacceptable and unprofessional to offer an extension for sale that is not functional and for which the description of the specifications is false.
Our entire development schedule needs to be reviewed, as does our roadmap, putting us in a difficult situation.
What do you plan to do?
We’re going to think about what to do next.
regards,

Hello, we bought your extension 2 months ago.
Your team has been talking about fixing the problem for almost 1 month now, but it still hasn’t happened.
We have conducted some research on our end. As we can see on this page, updates are regular and minimal: https://stripe.com/docs/changelog.
On this page, the usage of tokens does not seem to pose any particular difficulties: https://stripe.com/docs/connect/account-tokens

How is it possible that the issue has still not been resolved?
We find it unacceptable and unprofessional to offer an extension for sale that is not functional and for which the description of the specifications is false.
Our entire development schedule needs to be reviewed, as does our roadmap, putting us in a difficult situation.
What do you plan to do?
We’re going to think about what to do next.
regards,