Banner Logo

Be a part of the family: Connect, Receive Support,
Contribute, and Reap Abundant Rewards

error with stripe

MultivendorX Pro

Tagged: 

Resolved
Viewing 47 reply threads
  • Author
    Posts
    • #192456
      vincent joubert
      Participant

      Hello,
      I have a problem when creating a seller account, in the billing section.
      When I connect the seller account to stripe, I generate a token which is validated.
      After filling in all the fields correctly, I register the account and then get this error message (even though the seller account connection seems validated with the message : You have a connected Bank Account, etc…):
      Error with Stripe: Connect platforms based in FR must create Custom accounts via account tokens. For documentation on account tokens, see https://stripe.com/docs/connect/account-tokens.

      What’s wrong ?
      Thank you.

    • #192474

      @vincent joubert, sorry to hear that you have faced this issue.

      Can you please help us with small information, do share the scrrenshot of the Stripe payment settings page from the admin end. We will proceed with testing accordingly.

    • #192493
      vincent joubert
      Participant

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

    • #192608

      Thanks for sharing the screenshot . As we do not have custom account hence we are not able to generate the token . It would be great if you can share the site url and temporary site access with us so that we can check the issue on your end .

    • #192697
      vincent joubert
      Participant
      This reply has been marked as private.
    • #192724

      @vincent joubert, we have faced the same issue on our end.
      Our team is looking into this issue.

    • #192868

      @vincent, we checked this error, it seems like stripe is sending this error code.

      I am in touch with the stripe team. to locate the reason behind this error. They are basically checking why does stripe give this error?

      We will keep you posted.

    • #192884
      vincent joubert
      Participant

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

    • #192921

      Once we hear back from the Stripe team we will surely keep you posted.

    • #193009
      vincent joubert
      Participant

      @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

    • #193027

      @vincent joubert, we have heard back from the stripe team. They have updated their API hence this issue.
      It would take us quite some time to add this support.

      We have a question, why are you not using Express or Standard accounts?

    • #193030
      vincent joubert
      Participant

      @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

    • #193035

      @vincent joubert, yes custom account does help you here.

      But, it might take some time, they have added huge modifications in their API.

    • #193039
      vincent joubert
      Participant

      @moumita How many days do you think?

    • #193062

      It might take us 2-3 weeks, depending on the kind of support stripe will provide us. But please understand sharing an exact time is quite difficult.

    • #193552
      vincent joubert
      Participant

      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

    • #193607

      @vincent joubert Sorry for the delayed response.
      Our team is working to add the support for the new api modification of Stripe. So we need some time.
      As the modification is huge hence giving an exact ETA is not possible.Also after we add the fix testing needs to be done so it is a time taking procedure.
      But We will surely keep you posted as soon as we add the fix for this.

    • #193638
      vincent joubert
      Participant
      This reply has been marked as private.
    • #193660

      Kindly understand that the stripe team has added huge modifications in their API integration recently.
      As they have added new modifications we will also have to add support for that to our plugin. It will take some time.

    • #193817
      vincent joubert
      Participant

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

    • #193822

      @vincent joubert extremely sorry for the delay.
      Currently our team is working on some huge enhancements that is why the work with support for stripe modification got delayed.
      Our team will start working on the modification from this week only.

    • #194032
      vincent joubert
      Participant

      @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.

    • #194042

      Extremely sorry for the inconvenience. It is taking more than expected time to add the fix. But not to worry we will share the fix with you even if your subscription gets over as you faced the issue within your subscription period.

    • #194047
      vincent joubert
      Participant

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

    • #194058

      @vincent joubert We are very sorry for the delay. Our team is working on this. We will provide you with the fix as soon as possible.
      But as we have to remove our previous code in order to add support for newer version of stripe API. That’s why sharing an exact ETA is difficult. It’s just not a flow we have to add, we have to make sure money is also getting transferred properly.
      We are trying our best to complete this ASAP. Kindly bear with us.

    • #194446
      vincent joubert
      Participant
      This reply has been marked as private.
    • #194471

      We are extremely sorry for the delay. Our team is still working on the integration and we have also added support for the company profile.
      We are just having issues with saving 2 fields, because the stripe API doc is much more outdated than their coding.
      We are in touch with Stripe, so they can assist us here better.
      For refund kindly send a mail to refund@multivendorx.com. The refund team will help you further regarding this.

    • #194493
      vincent joubert
      Participant

      thank you Sangita, I wrote to the refund team.

    • #194523

      @vincent joubert The refund team will help you accordingly.
      But just to keep you informed our team has already added support for custom accounts in the UK. Do let us know which country do you belong to, so we can add that and share the plugin file.

    • #194527
      vincent joubert
      Participant

      @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.

    • #194599

      @vincent joubert We are glad to inform you we have successfully added support for individual accounts for France. Today we are working to add support for the company profile.
      Also the refund team will check your refund request and get back to you as soon as possible.

    • #194611
      This reply has been marked as private.
    • #194644
      vincent joubert
      Participant

      @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.

    • #194656

      @vincent joubert the plugin file we have shared is fully tested on our end. Only then we have shared the file.
      Vendor connection : https://tinyurl.com/28j4amay
      Commission paid : https://prnt.sc/K8gd0dQL_KiF
      By testing, we just asked you to check the same on your end.
      Regarding the bug, we were not aware of this issue. The last time we checked the flow, it used to work without any error.
      However, despite our best efforts, it’s possible that you might encounter a few bugs while using it.
      We believe in transparency and that’s why the moment you reported this issue, we started to do further research and kept you in the loop. We checked the api and found out that they have updated their api recently. But without proper documentation on their end, it took us more time than expected.
      We understand that encountering a bug can be frustrating, but our team is always there to help out users the best way possible.
      I hope you can understand our end too.

    • #194658
      vincent joubert
      Participant

      @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.

    • #194699

      @vincent joubert, I am afraid you have the wrong information.
      Stripe has updated the custom account API on 31st March, 2023. Here is the chat transcript of the same https://prnt.sc/Z1Oj1DY88tD4
      Please understand we try our best to assist you with everything. But when we face huge modification especially which is dependent on third party API’s, then it might take some time. What exactly happened for this.
      We are not making any excuses, but staging the fact.
      For refund, contact the refund team. They handle these queries.

    • #194713
      vincent joubert
      Participant
      This reply has been marked as private.
    • #194715

      @vincent joubert We are from the support team hence we can not accept or reject refund or help you with the refund. Kindly reach out to the refund team for this. You may send them a mail on refund@multivendorx.com.

    • #194801
      vincent joubert
      Participant

      @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.

    • #194803

      Extremely sorry to hear that. But as we are from the support team hence we really can not help you with anything related to refund.
      However I have informed the refund team they will look into it and get back to you as soon as possible.

    • #194804
      vincent joubert
      Participant

      yes sure.

    • #194805

      They will surely get back to you soon.

    • #194971
      vincent joubert
      Participant

      @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.

    • #194027
      vincent joubert
      Participant

      @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,

    • #194030
      vincent joubert
      Participant

      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,

    • #194029
      vincent joubert
      Participant

      @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,

    • #194712
      vincent joubert
      Participant
      This reply has been marked as private.
    • #194031
      vincent joubert
      Participant
      This reply has been marked as private.
Viewing 47 reply threads

The topic ‘error with stripe’ is closed to new replies.