• Resolved Ali

    (@lindenhoff)


    Hi,

    We have recently noticed a strange problem, the cause of which is unknown! When one of our teammates tries to pay for a product that has a shipping class, she encounters the following errors!

    https://ibb.co/hDn8Ftm

    This is while there is no problem for other users!

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Reüel

    (@pronamic_reuel)

    I’m unable to reproduce the issue in our test environment. Have you compared the payment in question with an other payment in WordPress admin ? Pay ? Payments which does not result in the error message? Did you notice any differences? Any error messages in the MultiSafepay dashboard, as the error message is coming from the payment provider?

    Thread Starter Ali

    (@lindenhoff)

    Hey @pronamic_reuel
    Finally i found that this issue only happens when there is plus symbol (+) in user email address! Is that related to woocommerce or your plugin?!

    Plugin Author Remco Tolsma

    (@remcotolsma)

    This may also be a limitation of the payment provider used. Which payment provider (Mollie, Buckaroo, Pay.nl, MultiSafepay, OmniKassa, etc.) do you use? Then we can investigate this problem further and at least clarify the error message.

    Thread Starter Ali

    (@lindenhoff)

    We use MultiSafepay

    Plugin Author Reüel

    (@pronamic_reuel)

    I was able to reproduce this issue specifically with MultiSafepay. I’ve asked MultiSafepay support if they can confirm the issue.

    Watch or subscribe to https://github.com/pronamic/wp-pronamic-pay-multisafepay/issues/4 for details.

    Plugin Author Reüel

    (@pronamic_reuel)

    MultiSafepay has confirmed that the plus sign is not supported in email addresses with the API currently being used in Pronamic Pay.

    Alimir

    (@alimir)

    Hey @pronamic_reuel
    Thanks, Do you have any plan to replace XML with JSON?

    Plugin Author Reüel

    (@pronamic_reuel)

    At the moment, we haven’t planned on updating to the JSON API yet but we’re always improving our plugin, so it could change anytime.

    I’ve added this use case to our existing issue about updating to the JSON API: https://github.com/pronamic/wp-pronamic-pay-multisafepay/issues/1

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Something went wrong with the payment!’ is closed to new replies.