Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
are You going to port ePay payment provider from TeaCommerce?
ePay is cheaper than DIBS and all our customers already have an agreement with ePay (Bambora).
We do have a Bambora payment provider created, however it hasn't been through a thorough test yet. You can find the source code for it here https://github.com/vendrhub/vendr-payment-provider-bambora should you wish to try it out.
We'll be looking to test it and release it as soon as we can, but if you do test it before this, do let us know how you get on.
Thank you for a quick response.
It's a very good news. We are about to start a new ecommerce project and ePay is one of the requirements.
I'll try to find time to try it out ASAP.
after some time strugling with testing I realised that there are two (!) Bambora payments: Bambora Classic (ePay, aka Bambora Online in Denmark) and Bambora Checkout, which is used here as a payment provider.
After I switched to the "other" Bambora (not ePay), it looks like all is working fine: payment authorization and payment capture from Vender's backend.
I had recompiled the sourcecode with the newest Vendr first.
That's fantastic news (not about the confusion).
I'm really glad you managed to get it all working though and I'll look to get an actual release out soon.
Thanks so much for testing this
I was about to ask when are you planning to release the "release" version of Bambora NuGet package, but I can see it's already available. YAY! :)
But after installing the relese version I can't open nor use the existing Bambora PM. In Umbraco backend I'm getting this looong error:
I had to delete the existing Bambora PM and create a new one. So no problem, fortunately.
I think it was beacuse I used a selv compiled version from git.
But I can confirm, that the new package works with test Bambora Checkout.
Ahh, that's strange, but glad you sorted it.
I think the problem would have been because we changed the payment provider alias (I forgot you were using an unreleased version so my apologies for not flagging that as breaking).
For anyone else with the same issue, you can either delete and recreate the payment method as Tomasz, or you could update the payment provider alias of the payment method in the database to point to the new alias bambora-checkout. You'll probably need an app pool recycle after this, but it would save you re-setting up the payment method.
Thanks for reporting this and apologies again.
Yes. That was exactly that. I can see in staging database, that now I have two bambora payment methods. One deleted with the old alias, and one new with the new alias.
It was enough to change alias in production database :)
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted