Rabo Smart Pay for WooCommerce

For any technical questions you can get in contact with PayoCity via phone or email. You can find our contact information via the following link: https://payocity.nl/en/contact If you have any questions about Rabo Smart Pay you can contact Smart Pay via phone or email. You can find their contact information via the following link: https://www.rabobank.nl/smartpay

In update 2.3.2.5 we introduced support to select the desired Merchant Order ID which is send to Rabo Smart Pay. By default this was the order ID of the order. There are plugins that allow for custom/sequential order numbers, which could be used when selecting the Order Number reference. The plugins that are supported are the following; Sequential Order Numbers Pro for WooCommerce ( Skyverge ) Sequential Order Number for WooCommerce ( WebToffee )

There can be several reasons why the transactions aren't updating, all of them are related to the webhook. From the 1st of december there will be an update to the webhook security that could prevent transactions from updating as well. The list below will be issues from common to least common. The webhook is not configured on the Rabo Smart Pay dashboard Handshake fails or firewall blocks the request. The accesslogs/usagelogs of the server will also indicate if the previous mentioned could be an issue. iThemes Security plugin is active. The iThemes plugin has an option to enable HackRepair.com’s ban list feature (WordPress admin » Security » Banned Users » Configure setting button), which blocks user agents that contain “Java” and Smart Pay includes “Java” in their user agent identification for webhook requests. Disabling this feature resolved webhook requests being processed. (Thank you Reüel of Pronamic for this information). Something is going wrong in the plug-in, please contact us. Update from 1st of december 2020: A cipher suite is removed from the allowed list, that is: - TLS_RSA_WITH_AES_256_CBC_SHA256 The ciphers that are supported are the following: - TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, - TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384. Update as of the 1st of july 2021 The following ciphers are also added to the webhook: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 You can check the supported ciphers on your website by going to: https://www.ssllabs.com/ssltest/ Update on the ciphers The Rabobank will be changing the accepted ciphers for outgoing calls on your webserver. This included transaction announcements and gatekeeper calls. Provide the list below to your server manager, they need to check the openSSL library and configuration; Current accepted ciphers: TLS-AES-256-GCM-SHA384 TLS-CHACHA20-POLY1305-SHA256 TLS-AES-128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-CHACHA20-POLY1305 TLS_AES_128_CCM_8_SHA256 TLS_AES_128_CCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Updated list of accepted ciphers: TLS-AES-256-GCM-SHA384 TLS-CHACHA20-POLY1305-SHA256 TLS-AES-128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-CHACHA20-POLY1305