CodeBrain BV

Hello @crool ,

The update has been pushed out, this should resolve the warning!

Thank you for your patience!

This is part of the webhook processing, where we grab the transaction ID of the payment and its brand (method).
The transaction is found, however it seems that the brand is empty.

We’ll change the code that it doesnt cause errors if the brand is empty/null.
Expect an update on Monday!

Hello Auke,

I’m sorry to hear you had issues with the webhook of the Smart Pay.
We could have assisted with solving any issues that you had, but unfortunally we have no ticket from you. Still this is valuable feedback, which we’ll take on looking forward.

Thank you!

Thank you for the response Igor.

I have tried the steps but that didnt solve the issue.

So i have tried a new installation with WordPress 6.0 and Woocommerce 6.6.0, however it doesnt show the settings either. Is the filter woocommerce_payment_gateways_settings still used?
I searched the changelogs, but cannot find any reference to it. So it doesnt seem removed or deprecated. I see a call of the filter in woocommerce as well.

I dont see anything in the logs, even with debugging in wordpress on. No errors in the console either.
So far i havent been able to solve the issue, nor am i sure what the next step should be.

Thanks in advance!

Hello Nico,

To give you an update, the Rabobank has an API which you can use for the refunds.
We could integrate that, however they are going to move the functionality to the OmniKassa itself.
Therefor the integration changes and how we integrate it in the plug-in.
Once the changes have been made, we will update the plug-in with the functionality.

The error shouldnt occur on versions before 5.0 either, we shall look into it just to make sure. The check is made to prevent already paid orders or completed orders to revert back.

The problem was that the order object couldnt be loaded with ID 1154, and the function returned a false most likely.

However the second error was generated because the getStatus() doesnt exist.

• This reply was modified 3 years, 9 months ago by CodeBrain BV. Reason: Fixed a typo

Hello Nico,

Thank you for clearing it up.

At the moment the Rabo OmniKassa doesnt support automatic refunds, however they are working on an option to make it possible.
We are closely working with them, in order to make it possible in the plug-in as well.

The way it is at the moment, it requires an additional service on the OmniKassa called the Merchant Services.
These merchant services make it able to perform refunds and download/view transactions.
The integration however is entirely different, so thats what we are currently working on.

So it will come in an update in the near future.

Hello,

Do you mean recurring payment, or what do you mean?
We recently added the return status change as well, but im sure this is not what you are referring to.

If you could give us a bit more information, we can look into this and possibly support this with an update.

Thank you in advance,

Martijn Bakker

Since this topic has been open for well over 3 weeks without response, we will close this.
If this issue still persists and you need further assistance, do not hesitate to contact us.

@pronamic_reuel Thank you for additional information.

@bwijbenga , has this issue been resolved, or do you need additional support?

Sorry for the late response.

The webhook URL is the only way transactions are updated in WooCommerce, because on the Return not all data is given. However there can be several reasons why the webhook URL is not working on the website.

A number of these issues are related to the server the webshop is running on.
Before the webhook is actually called, the firewall or handshake could block the call.
You can check this for yourself in the accesslogs of the server, check if the webhook URL is listed in the calls and gives the correct 200 HTTP response code in return.

If it is in the list, you know that the server doesnt block the webhook calls of the Rabo OmniKassa. Then we can look into the plug-in, where it could be a configuration issue.
Check the signing key listed in the configuration, this could prevent the webhook from working. Because the Rabo OmniKassa uses signature hashes which are calculated with the signing key, if these don’t match the call is rejected. However due to working returns, I don’t expect this to be an issue because the same hashing applies.

Perhaps you can give us a call on: +31 522 746060 we can help you with this issue. If the above listed doesn’t solve it.

Hello @supportwi ,

The payment status is not going to be updated on the payment return, this is done by the webhook.
The webhook is found in the configuration of the plug-in in the backend, which can be found in the backend of WordPress.

– WooCommerce
– Settings
– Payment/Betalingen
– The webhook is noted above the refresh token field.

this needs to be configured on the dashboard of the Rabo OmniKassa 2.0.

The reason why is because the webhook contains all the neccesary information regarding the transaction. This is also the most secure.

I suspect that the webhook hasnt been configured on the Rabo OmniKassa 2.0 Dashboard.
This can be done by clicking on:

– Beheer
– Webwinkels & Verkooppunten
– Details

• This reply was modified 4 years, 6 months ago by CodeBrain BV. Reason: Added steps for the Wordpress backend