Bug with new Advanced card hosted fields + Feature request.

Hello @eazyproo

Thanks for reaching out to us, we’re here to help.

We are using CheckoutWc plugin for a custom checkout page, and when activate your plugin with the new Advanced card payments new hosted fields there is a bug that the full checkout page when click place order button it keeps loading and it show some error on the consol log and when we refresh the page it’s working that means it failed to work on the first checkout page open (which a normal customer paying will not understand that issue),

We were able to reproduce the problem on our end. The bug report has been sent to our developers for further investigation. In the meantime, we also recommend contacting the developers of the CheckoutWc plugin for additional support.

We are hopeful that this issue will be addressed in the upcoming release candidate update. Thank you for bringing this to our attention.

1) an ability to change the card logo icons on the card form when enter the card number (if there is a current way to change this please share the guide with us please),
https://ibb.co/pRc7KTW

Unfortunately, there is limited flexibility in this area. The logos displayed are managed on the PayPal backend, and currently, there is no capability to modify these logos through the plugin, especially with the new hosted fields. This customization was possible with the old hosted fields, but not with the new implementation.

2) Save the last 4 digits of the card that customer paying with on the order meta data as we want to show it on the order details for the customer information as we see a lot of payment gateways added this fucntion recently and it been used for long time,

I’ve discussed this matter with the product owner, and it looks like we might be able to introduce this feature. However, I can’t provide an estimated time for its release at the moment. Your feedback is greatly appreciated.

We truly appreciate your feedback and are here to assist you further should you have any more questions or concerns.

Kind Regards,

Krystian

Hello Krystian,

Thanks for letting us know that you will fix the bug and thanks also for letting us know about the card logo that it’s not possible.

And about the store last 4 digits of card feature can you maybe open a pull request on github for developers to work on that function? as it’s a good and advanced function that all payment gateways currently using, hope you open a pull request on github so we can also follow it, it will be apprectiated if you guys can release it on the new coming nearest updates.

Thanks.

• This reply was modified 9 months, 1 week ago by Mohamed.

Hello?@eazyproo

you maybe open a pull request on github for developers to work on that function? as it’s a good and advanced function that all payment gateways currently using

Once we begin working on it and develop a solid solution, we will have a Pull Request (PR) ready well before the release. We’ll attempt to update you in this thread when the PR is available, though I cannot guarantee a specific timeline at this moment.

Kind regards,
Krystian

Thanks a lot for letting me know this.

Also another question,
Why you always use iframe card form rather than use a built in on same website card form like stripe, etc… (the built in on the same website card form is really easier for customizations and do whatever we need)

Please let us know, thanks.

Hello?@eazyproo

Stripe also uses iframe for payment card forms from what I know. This approach is not only about ensuring a seamless and secure payment experience but also plays a crucial role in maintaining Payment Card Industry (PCI) compliance.

Please do not hesitate to reach out if you have any more questions or need further assistance.

Kind Regards,

Krystian

Hello, any updates about our function feature request and the bug we mentioned?

• This reply was modified 8 months, 2 weeks ago by Mohamed.

Hello, any updates about our function feature request and the bug we mentioned??

Hello, any updates about our function feature request and the bug we mentioned???

Hello, any updates about our function feature request and the bug we mentioned????

So nobody will update on this?

Hello @eazyproo

I apologize for the delay in responding. I was hoping to have some updates to share by now, but unfortunately, there isn’t much new information yet. This issue wasn’t on our roadmap due to the prevalence of other issues and new feature implementations. However, after receiving another report from the user, we’ve assigned it to one of our developers. I hope to provide you with an update soon.

It’s unlikely that this update will be included in the next version of the plugin, but it should be fixed in the following release. I’ll keep you informed about all updates. Please let us know if you have any more questions.

Kind regards,

Krystian

Hello @eazyproo

The issue with CheckoutWC will be addressed in the prerelease dropping today on GitHub here, and it will also be fixed in the upcoming version 2.8.2.

Kind regards,
Krystian