Ben Meredith

Hey @erichmond

That is controlled completely from Stripe’s end: GiveWP loads the Stripe fields directly from Stripe, and they control what displays there. In the Stripe Docs you can see the sample payment flow: https://stripe.com/docs/payments/sepa-debit#payment-flow

There’s not a way (I don’t even think from Stripe’s side) to modify the payment flow that I know of.

For Sort Code as an option, they’d need to use the GoCardless gateway, which is a premium add-on. We’re not allowed by forum rules to really talk about those here, but if you have followup questions, reach out via our contact form: https://givewp.com/contact-us

Thanks!

Hi @dzimnikov!

Glad you reached out, here.

Usually when the form displays on one page but not another, you’re right to assume some kind of conflict going on, so let’s rule out some things and see if we can isolate the issue!

I see in the source code there that you are using a plugin to lazy-load images (smush) and that’s likely the culprit here. That plugin attempts to help the page load faster by adding all the JavaScript files into one large file and then serve them together, and also attempts to speed up page load by loading images after the page has loaded. That doesn’t work for GiveWP forms, since GiveWP requires that the JavaScript files to all be loaded in a specific order, and for images to not be lazy-loaded.

SO I’d start there, by changing the settings for that plugin to not lazy-load, and not plop all the JS files into one. That process is called “concatenation” so you’ll want to disable JavaScript concatenation.

If that doesn’t resolve it, definitely reach back out here.

Also, please send along your System Info.

Navigate to Donations –> Tools –> System Info (tab) and click the button to “Get System Report” and copy/paste that in your reply here.

That will give me some more context to be able to help.

Hi @eac2015

I really appreciate you reaching out here. I was aware of the issue you’re referencing which you can see here but honestly I thought that it had a simple workaround, explaining why it sat there since May with no action. I’ve looked more deeply into it today, and it’s actually not as simple as I thought, but there is a workaround.

You’ll see a comment there now from me including a video that lines out step-by-step how to temporarily resolve the issue while our team looks into it.

Note also that I think we’ve conflated two issues, one producing a fatal error and one that is as described in the linked feedback above. That’s our mistake for sure. Accountant roles not having access to a page or functionality should not result in fatal errors, and we’ll fix that as soon as we are able to replicate the problem.

I’m still looking into the fatal error issue and working with you in the ticket you opened.

Your success with online donations is our number one priority, and I want to make sure that we get you back to full speed very soon.

Hi @vermaakpetrus

Glad to hear that you found a solution that fits your needs. Your success with online donations is our number one priority.

As you know, the legalities, complications, and red tape around international currency support are numerous for Payment Gateways, and some countries like South Africa are especially difficult to integrate with. It’s an odd twist that PayPal (founded by Elon Musk) has no real option for accepting South African currency at all.

You’re right that Payfast recurring support is a relatively popular request, currently with 31 votes on our feedback site here: https://feedback.givewp.com/feature-requests/p/recurring-donations-in-the-payfast-gateway

Given unlimited time and resources, we’d develop *all the things* and have *all the features* but it’s just not a reality at this time. With the resources that we have now, it’s not made the top of the priority list, and if it were as simple as flipping a switch to turn on that support, we’d do it.

You mention “bugs, shortcomings, and limitations” and I’m curious what exactly you mean. It sounds like Payfast recurring support is a dealbreaker, and that’s understandable. If you’re aware of bugs, we’re definitely keen to know about them.

I searched your history of communication with us, and you’ve reached out twice, once back in 2020 for Zapper Payment Gateway support, and once recently about Payfast recurring support. Perhaps I’m missing the ticket or email where you found a bug, but I will personally look into any problems you have. We take bug reports very seriously.

Have a great day!

Wow! GiveWP version 1.8.13! That’s suuuuuper old, and there’s no way we’ll be able to track down what’s going on there. We try very hard to support older versions in some cases, but in this case, that’s just too old to be able to help.

Your best bet is to wait on that import until you can update your GiveWP plugin to the latest version.

Heads up, though: I would strongly recommend using a staging site to test those updates, because updating directly from 1.8.13 to the latest will almost certainly come with some nuances.

There have been many MANY improvements to GiveWP in the nearly 5 years since 1.8.13 that you need to be taking advantage of.

Hi there! That error is from Authorize.Net, and that’s a premium add-on that (by forum rules) we are not allowed to support here.

Please open a ticket with our priority support team, and we’ll have a look. You can do that from within your Givewp.com account at https://givewp.com/priority-support/

Thanks!

Hi @debedete

All Venmo donations will still go through (and be processed in) the PayPal account, so the reporting should remain exactly the same. I am not super-familiar with it from their side, but in my tests it shows up right there alongside other PayPal donations.

PayPal support may be able to clarify.

Glad you reached out!