|
Steve Huang
|
May 3, 2017 at 7:55 am
Hi,
I’m currently using EE3 (Event Espresso – 3.1.36.4.P Version 4.7.4).
My credit card payment transaction is handled via Beanstream. In the EE3 PlugIn, I have had the payment setting set up as Beanstream with the proper Beanstream Merchant ID.
Beanstream now has been bought by Bambora, and on May 10, they will rebrand Beanstream to Bambora.
My question is, does this affect my payment setting in the EE3? Will all those updates change automatically? or on May 10, those credit card transaction on my website will not go through any more, and I had to reset the payment setting to Bambora?
Your help is appreciated. Thanks.
Steve
|
|
Josh
|
May 3, 2017 at 11:31 am
Hi Steve,
We actually haven’t gotten any information from Beanstream about this. Has Beanstream sent you any notice about whether or not payment calls to
beanstream.com/scripts/process_transaction.asp
will continue to work after May 10?
|
|
Steve Huang
|
May 3, 2017 at 3:59 pm
Hi Josh,
Wow, this could be dangerous. I’m glad I asked here.
Beanstream was bought out by Bambora around half year ago, and now they are rebranding Beanstream to Bambora, and all logo and website links will change to Bambora. I have received few notices in recent one month or so.
This link is the page of the Rebrand Took Kit. http://grow.beanstream.com/merchant-rebrand-toolkit?mkt_tok=eyJpIjoiWTJZeVpHSXpORFF5TlRaayIsInQiOiJSXC94bXlBXC9CM2k2NXFnbjZJTFF5WGxuTVlzNUVvU0FqZU40eU5jVVd6NkNSSG5pbDczaFpObnJZTE5sQzU0dlwvRDRcLys5NzZkYktuZ1NPWGZXNnU4V0ZHbk5VQ2d5RG92czMrdmF6Y1F6RVBTU21HNEx2UVMzaTFyR29majNCQUoifQ%3D%3D
Apparentally, all website URL starts with beamstream.com/ will change to bambora.com/.
I have just called them few minutes ago, beanstream.com/scripts/process_transaction.asp would need to change to bambora.com/scripts/process_transaction.asp
You probably need to get in touch with Beanstream to get the technical specification to make this transition.
I hope this change will take place on your plugin automatically, so we as users do not need to change anything on our end.
Please let me know how it goes, and hope it transition smoothly. Thanks.
Steve
|
|
Josh
|
May 3, 2017 at 10:06 pm
Hi Steve,
You will likely need to make the code change on your end because of the way that Beanstream isn’t being given any transition time. (The change is happening on May 10 with no overlap to allow for a transition period it seems.) So, you can change the code in the Beanstream gateway of Event Espresso 3 to point to the new URL that they gave you, which according to the information from your link, on May 10.
Releases of Event Espresso 3 after May 10 will include the changes so your change will not be overwritten.
The code change can be made directly onto line 38 of event-espresso/gateways/beanstream/return.php on that date.
|
|
Steve Huang
|
May 8, 2017 at 2:11 pm
Hi Josh,
I have no idea on how to get to the coding interface page to change code on line 38.
How to get to event-espresso/gateways/beanstream/return.php?
Steve
|
|
Josh
|
May 8, 2017 at 2:20 pm
Hi Steve,
If you or someone that helped set up your website doesn’t have FTP set up, you can log into your hosting account and use the CPanel file manager to access the file and edit it.
|
|
Steve Huang
|
May 8, 2017 at 3:34 pm
Hi Josh,
Thanks. Now I found out where to go to change the code as you specified.
Cheers,
Steve
|
|
Josh
|
May 9, 2017 at 7:00 am
Great! It may also be beneficial to reach out to Bambora and find out exactly at what time they plan on doing their switch you’ll know when to make the code change.
|
|
Tony
|
June 2, 2017 at 1:48 pm
Hi Steve,
I’m curious if you applied the above change to the site and have it working?
I’ve been looking into pushing an update for EE3 with the abov change, however on investigating it appears:
https://bambora.com/scripts/process_transaction.asp
Is invalid and it would need to remain:
https://beanstream.com/scripts/process_transaction.asp
(Click on the links and you’ll note the difference)
It appears to work for me using the ‘old’ but not the new one. I’ve had some strange results when testing this and have contacted Beanstream/Bambora but I’m curious if you have this working with the above change?
|
|
Steve Huang
|
June 5, 2017 at 3:11 pm
Hi Tony,
Since Beanstream/Bambora indicated there is automatic link redirection besides urging us to change the actual web address, I tried not to change the code in the plug-in, which is a little bit scary to do for me.
I tested it after the go live hour of that day, and found the payment could still go through, so I ended up not changing anything.
In the recent two weeks actual customers payments went through successfully too.
I thought the link re-direction must be working beautifully.
Your test indicates that only the old link works. I’m glad I did not change the code behind, otherwise, I would have been in a lot of trouble.
Did you find out from Beanstream/Bambora what the correct procedure should be after the go live date?
Cheers,
Steve
|
|
Tony
|
June 6, 2017 at 4:44 am
Ok, thank you for letting me know.
I thought the link re-direction must be working beautifully.
I don’t think there is a redirect happening on that call, as the link above doesn’t redirect.
Did you find out from Beanstream/Bambora what the correct procedure should be after the go live date?
I haven’t heard from Bambora as yet but my test account was approved and once I had that I found the correct new URL is:
https://web.na.bambora.com/scripts/process_transaction.asp
Testing transactions with the above URL worked as expected.
|
|
Josh
|
July 17, 2017 at 1:11 pm
Update:
Event Espresso 3.1.37.12 was released today and it includes an update to the Beanstream gateway so it now points to Bambora’s new URL.
|
