WPIntell

Source evidence

Fatal error, please try again

YouCan Pay · support · 2022-09-12T19:03:00+00:00

complaintsentiment
highseverity
0.97relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

11 / 39 rows with source links

28.2% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
s1oufianebarakat12123 unresolved
Hello Team youcan Pay 4 days ago, I have been looking for a solution to this problem, but I did not find it. when I do transcation in my website always see this error : Fatal error, please try again. I have an online store on WordPress that I want to connect with YOUCAN PAY. I follow this steps : 1.Create youcanpay and connects API Keys (mode sandbox) inside WooCommerce 2. Add Webhooks https://mywebsite.com/?wc-api=wc_youcanpay 3.I put sandbox mode on Siteweb YoucanPay for testing and I test cards on( Developpeurs youcanPay) https://snipboard.io/YpckXB.jpg (about advanced I’m not sure if right or no about this parameter (Success.Error) 4. I do test in my products on my store by card in information in YOUCANPAY developpeur (No 3DS – Success) but same errorFatal error, please try again WooCommerce version: 6.8.2 YOUCANPAY PLUGIN VERSION : 2.0.12 I’m facing the same issue. I installed the latest version of the plugin, latest version of woocommerce and latest version of PHP. I have Youcan Pay api keys linked properly. can’t figure out what causes the problem. I opened a support ticket. Once I solve the problem, I will share it here

Comments

1 shown
aminchamov 2022-09-20T17:50:00+00:00

I’m facing the same issue. I installed the latest version of the plugin, latest version of woocommerce and latest version of PHP. I have Youcan Pay api keys linked properly. can’t figure out what causes the problem. I opened a support ticket. Once I solve the problem, I will share it here