Commit ID:dde4d21be7155b3927e56395dbaae6058ba1979c

Ximedes exists to allow a group of smart, friendly and ambitious professionals to work together on relevant and challenging software projects, to the delight of our clients and ourselves

Rabobank's Omnikassa PSP

Gijs ter Horst
April 12, 2018

Rabobank offers omni-channel PSP services to about 10,000 merchants. Rabo Omnikassa (ROK) supports online payments as well as terminal payments and has been around for almost a decade. Rabobank asked Ximedes to help them build ROK 2.0, a new version of this platform which is now live. We discuss the main components of the PSP below.

Focus on frontend APIs

Rabobank and Ximedes both knew that the success of the new version of ROK would be very dependent on the ease with which merchants could connect to its payment APIs. Therefore, in early workshops the existence of e-Commerce plugins for small merchants, and SDKs and plain REST API for larger merchants, was considered crucial. This in turn lead to the development of a robust yet simple set of APIs and plugins that allow merchants to connect to ROK in minutes.

The APIs check each and every call, verifying that it originates from a legitimate merchant, using a payment method that she is contractually allowed to use. Payment requests are subsequently passed on to the right payment processor.

Onboarding

Rabobank made it very easy for existing Rabobank clients to onboard the ROK 2.0 PSP. Building on the fact that merchants are already onboarded at the bank, with the Know Your Customer (KYC) process already performed, the merchant basically only has to 'switch on' the PSP capabilities. This instantly provides them with the digital keys neccessary to access the API and/or e-Commerce plugins. During the onboarding process, merchants can choose which payment methods are available in their web shops, and terminals to be used in their brick & mortar shops.

alexandre godreau 510220 unsplash

Merchant Dashboard

Merchants want insight in all of the transactions that were performed on their web shops and terminals. ROK's Merchant Dashboard provides them with that insight. It tells them how much turnover they made in a period, provides them with data on the popularity of certain a payment method and is key to understanding their payouts. Also, the merchant dashboard of ROK makes it easy to initiate a refund, and supports them in the process of chargebacks.

Ximedes built the backend of the ROK Merchant Dashboard, providing high-level REST APIs to the frontend team that implemented the dashboard UI.

Reconciliation, billing and payout

Any collecting PSP needs a thorough automated reconciliation process, and ROK 2.0 is no exception. Ximedes build the reconciliation software for ROK 2.0 in close co-operation with business analysts of Rabobank. The reconciliation software tracks the status of every transaction in the system, a status that is of course reflected in the Merchant Dashboard. The reconciliation software feeds transactions and their status to the billing process, which calculates the fees due by the merchant, and to the payout module which calculates the (net) turnover made by a merchant so that it can be paid out the next day.

Running the PSP

ROK 2.0 is a comprehensive PSP that Ximedes is very proud to work on. Currently a Ximedes DevOps team helps Rabobank run the PSP. Of course, in this ever-changing world a piece of software is never 'ready', and so Ximedes is continuously developing ROK 2.0, helping Rabobank's product owners to improve the product on a sprint-by-sprint basis.