|
Eric Amundson
|
December 26, 2024 at 9:01 am
Hi! We have used Event Espresso with PayPal Standard for years to sell our classes in the US and Canada on our WordPress site.
We used a piece of custom code that depending on our client location changed our receiving PayPal email address from our US account to our Canadian account respectively, but now Event Espresso is requiring its users to transition to Paypal Commerce and we won’t be able to use our method with it because it links just one account to the site using OAuth.
What options do we have to receive our Canadian client’s payments to our Canadian PayPal account and our US client’s payments to our US PayPal account?
|
|
Tony
|
December 30, 2024 at 8:57 am
Hi there,
Hmm, good question!
Which specific version number of Event Espresso are you using?
Do you use the Multi Event Registration add-on?
|
|
Eric Amundson
|
December 30, 2024 at 2:09 pm
Hi Tony!
We are currently using version 5.0.21.p and we are not using the Multi Event Registration add-on?
|
|
Eric Amundson
|
December 30, 2024 at 2:10 pm
Hi Tony!
We are currently using version 5.0.21.p and we are not using the Multi Event Registration add-on
|
|
Eric Amundson
|
January 6, 2025 at 1:55 pm
This is an urgent matter, We need to find a solution before EE stops working with Paypal Standard on January 15th.
|
|
Tony
|
January 7, 2025 at 4:54 pm
Hi Eric,
So, as it stands, I don’t have a solution for your customization that will work with PayPal Commerce.
The reason I asked if you were using Multi Event Registration (MER for short) was to look into possibly using the Payment Methods Pro add-on (PMP) for what you are trying to do. That add-on allows you to have multiple instances of a payment method and assign each specific instance to an event so it’s used for its payments (it’s not compatible with Multi Event Registration).
However, the PayPal Commerce payment method is not currently compatible with the PMP add-on in that it won’t allow you to connect individual accounts to each instance. Moving forward, that would be the method I would recommend looking into here, as it will allow for support across any payment method.
I assume you’re using the address values from the registration form to work out which account to charge.
—
Now the ‘good’ news.
We’ve extended the deadline for the deprecated payment methods to April 15th 2025 as some users weren’t ready for the switch, so this gives some extra time for the above.
|
|
Eric Amundson
|
January 24, 2025 at 5:42 am
Thank you Tony! Is it possible to assign two or more instances of payment methods to the same event using the Payment Methods Pro add-on? For example 2 different instances of Paypal each one with a different receiving account.
|
|
Tony
|
January 24, 2025 at 8:57 am
Yes, but the intention is to allow you to assign specific payment methods to specific events. It wouldn’t be expected (by the payment method itself) that 2 instances of the same payment method would be enabled on a single event. Yes they’ll have different accounts connected to them, but the payment method itself wont know that.
However, you can use a filter to filter out the payment methods based on a response from the registration form (likely in the way you are already doing with your custom code) OR assign neither of them directly to the event and pull either of the 2 PayPal Commerce payment methods in based on the above response.
Take a look at the FHEE__EEM_Payment_Method__get_all_for_transaction__payment_methods filter for that.
Note – you’ll still need the Payment Methods Pro add-on to enable that second PayPal Commerce payment method instance.
|
