Custom Rabo Smart Pay integration development
Appfront builds custom integrations with Rabo Smart Pay (formerly Rabo OmniKassa), Rabobank's payment service provider. Using the OmniKassa 2.0 REST API, we connect your webshop, point of sale or custom application to payment methods such as iDEAL, credit card, Bancontact and PayPal. You receive every payment status in real time via webhooks, process refunds programmatically and keep your order administration in sync automatically.
What is a Rabo Smart Pay integration?
Rabo Smart Pay is Rabobank's payment service provider and the current name of what used to be called Rabo OmniKassa. It is a payment solution for webshops and SMEs that lets your customers pay online with methods such as iDEAL, credit card, Bancontact, Maestro, V PAY and PayPal. The payment itself takes place in Rabobank's secure environment, so your webshop never has to process or store card details.
In practice, a custom integration means that your system announces an order via the OmniKassa 2.0 REST API, receives a omnikassaOrderId and a redirect URL in return, and sends the customer to the payment page. Once the payment is complete, your webshop receives the payment status via the return URL and via webhook notifications that update the order status in real time. Refunds, payment requests and retrieving refundable amounts are also handled programmatically via the API.
Appfront builds in line with the official Rabo OmniKassa developer documentation and the OWASP ASVS security standard. We tailor the payment flow, signature validation and error handling to your actual ordering process, so the integration grows with your webshop and payments keep running reliably even at peak volumes.
All common payment methods
One integration for iDEAL, credit card (Mastercard and Visa), Bancontact, Maestro, V PAY and PayPal. Your customers pay with the method they are used to, and you manage everything from a single Rabo Smart Pay dashboard.
Real-time status updates
Webhook notifications from Rabo Smart Pay update your order status immediately when a payment succeeds, fails or is cancelled. No manual reconciliation: your webshop and administration stay in sync automatically.
Refunds via the API
You process refunds programmatically: initiate a refund with the amount and VAT category, retrieve the refundable amount and track the status. Full or partial refunds are handled directly from your own system.
Our development process for Rabo Smart Pay integrations
We follow a proven methodology that removes uncertainty early and delivers a stable payment integration. From an initial analysis of your ordering process, payment methods and webshop platform through to go-live and ongoing maintenance, every step is aimed at an integration your team can understand and trust.
We map out which payment methods you need, how your ordering process works, which webshop or POS system Rabo Smart Pay needs to connect to, and whether refunds and payment requests are involved.
We design the payment flow on the OmniKassa 2.0 API, set up token and signature validation, and define an error handling and webhook strategy.
We implement and test the payment flow in the sandbox environment, with automated tests, structured logging and monitoring. You get to see working builds along the way.
A controlled transition to the production environment with payment validation and a safety net, followed by ongoing maintenance and further development.
What a Rabo Smart Pay integration delivers in practice
Every Rabo Smart Pay integration is set up specifically for your ordering process, payment methods and adjacent systems. Below are the features we deliver most often for webshops and SMEs that use Rabo Smart Pay as part of their payment process.
OmniKassa 2.0 REST API
Your webshop announces an order via the OmniKassa 2.0 REST API and receives an omnikassaOrderId plus a redirect URL in return. The customer completes the payment steps in the Rabobank environment and returns with a signed payment status, which your system verifies and processes.
iDEAL, credit card, Bancontact & PayPal
A single integration unlocks all Rabo Smart Pay payment methods: iDEAL including bank selection, credit card (Mastercard, Visa), Bancontact, Maestro, V PAY and PayPal. We set up the checkout so that new payment methods can easily be added later.
Webhook notifications
Rabo Smart Pay sends a notification to your webhook URL on every status change. Your system retrieves the corresponding order results (with pagination for larger volumes) and updates the order status automatically. Essential for reliable order administration.
Refunds
You process full or partial refunds programmatically via the API: initiate a refund with an amount, description and VAT category, retrieve the refundable amount and track the status. No more manual reversals.
Payment requests & payment links
With Rabo Betaalverzoek, you send customers a payment link they can pay using iDEAL, credit card or PayPal, which is ideal for invoices, telephone orders or orders placed outside the webshop. We link the creation and follow-up of payment requests to your own administration.
Signing & security
Rabo Smart Pay cryptographically signs every return URL and webhook payload with a signing key. Our integration validates that signature on every status update, so any tampering is rejected. We store tokens and keys in secure vaults and rotate them in good time.
Typical use cases in practice
A Rabo Smart Pay integration turns out differently for each organisation. We see a number of patterns come up often, and for each of them we have a working set-up that pays attention to the right payment methods, webhook handling and integration with your existing systems.
Webshops & e-commerce
Online shops that want customers to pay at checkout with iDEAL, credit card, Bancontact or PayPal. The order is announced via the OmniKassa 2.0 API and the payment status flows back to your order administration via webhook. See also our e-commerce development and API integrations.
Retail & POS
Shops and hospitality businesses that want to process in-store and online payments under a single Rabo Smart Pay account. We connect your POS or order system to the payment service, so payments, status updates and refunds come in centrally and your end-of-day reconciliation simply adds up.
Subscriptions & SaaS
SaaS platforms, membership and subscription services that want to support recurring payments. With card-on-file, a payment method can be stored securely at Rabobank for repeat payments, while your own application handles invoicing and access based on the payment status.
Services & invoicing
Service providers and SMEs that have invoices or orders paid outside a webshop. With payment requests and payment links, the customer receives a direct payment option via iDEAL, credit card or PayPal, and the payment status is linked back to your accounting or CRM.
Technology we use
We build Rabo Smart Pay integrations with the official OmniKassa 2.0 REST API and the accompanying SDKs, in combination with the backend stack that suits you. The exact choice depends on your webshop platform and environment, so that your own team can manage or further develop the implementation.
If you work with ICEPAY instead of Rabo Smart Pay, read more about our ICEPAY integration.
Why Appfront for your Rabo Smart Pay integration?
Appfront has extensive experience building API integrations and payment integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your ordering process and existing systems. A payment integration has to be technically correct, but it also has to process every transaction and status update reliably.
For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.
Take a look at our broader services around API integrations, middleware, custom software and web app development. Working with a different payment service provider? Then see our CCV integration or the overview of all integrations.
- Experience with the OmniKassa 2.0 REST API and the official SDKs
- Familiar with iDEAL, credit cards, Bancontact, PayPal and payment requests
- Webhook handling, refunds and signature validation in line with the documentation
- Secure by default: signing keys in vaults, token rotation, separate environments
- Structured error handling and retry mechanisms
- Extensive logging and monitoring from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach tailored to your existing webshop and IT landscape
Security and privacy in Rabo Smart Pay integrations
Payments always involve personal data and sensitive payment data. With Rabo Smart Pay, Rabobank acts as the payment service provider and processes the card and payment details: the actual payment takes place in the bank's PCI-compliant environment, so your webshop never processes or stores card numbers itself. Appfront builds the integration in line with the OWASP ASVS: signing keys and tokens in secure vaults, mandatory signature validation on every webhook and return URL, and strictly separated permissions between sandbox and production.
Because your system processes customers' personal data around every transaction, we document the data flows, integration points and retention periods so that your record of processing activities is complete and you can demonstrably comply with the GDPR. Rabo Smart Pay's signed status messages serve as verifiable proof of every payment status change.
More about our approach to security: information security policy and CVD policy.
- GDPR-compliant data processing and minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Automatic retry and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management following best practices
- Documentation for your record of processing activities
Frequently asked questions about Rabo Smart Pay integrations
Answers to the questions we are asked most often about Rabo Smart Pay implementations.
A Rabo Smart Pay integration is a technical integration between Rabo Smart Pay (formerly Rabo OmniKassa) and your webshop, point of sale or custom application. Via the OmniKassa 2.0 REST API, your system announces an order, sends the customer to the payment page and receives the final payment status back. Webhook notifications keep your order status in sync in real time, refunds are handled programmatically, and payment methods such as iDEAL, credit card, Bancontact and PayPal are available in a single checkout.
Rabo Smart Pay is the current name of the payment service that was formerly called Rabo OmniKassa. The underlying OmniKassa 2.0 REST API is the same technical foundation: the developer SDKs and documentation still refer to OmniKassa. An existing Rabo OmniKassa integration therefore continues to work under the name Rabo Smart Pay; we build new integrations on that same OmniKassa 2.0 API.
Rabo Smart Pay supports iDEAL, credit cards (Mastercard and Visa), Bancontact, Maestro, V PAY and PayPal, among others. Payment requests (Rabo Betaalverzoek) and buy now, pay later via partners are also available. The documentation states that new payment brands may be added, so we set up the integration in such a way that additional methods are easy to enable later.
With the OmniKassa 2.0 REST API, the webshop first announces an order; Rabo Smart Pay returns an omnikassaOrderId and a redirect URL that the customer uses to go through the payment steps. Authentication works via a refresh token, which is used to retrieve temporary access tokens. All messages, including the merchantReturnUrl and the webhook payload, are cryptographically signed with a signing key, so your system can verify the authenticity of every status update.
A simple integration (announcing the order, redirecting the customer, processing the payment status and handling webhook notifications) can go live within a few weeks. More complex scenarios involving refunds, payment requests, multiple webshops under one account or a deep integration with your ERP or order administration usually take more time. After an intake conversation, we will give you a realistic estimate.
We work with the official OmniKassa 2.0 REST API and the accompanying SDKs for PHP, Java and .NET, combined with the backend stack that suits you: Node.js, Python, PHP or .NET. We use the sandbox environment to test payment flows, and set up signature validation, token management and webhook handling in line with Rabobank's documentation.
Yes. With Rabo Smart Pay, Rabobank acts as the PSP and processes the sensitive payment and card data; the actual payment takes place in Rabobank's environment, so your webshop never has to store card numbers. Appfront builds according to the OWASP ASVS: signing keys and tokens in secure vaults, mandatory signature validation on every webhook and return URL, and separate permissions per environment. We document the data flows so your record of processing activities stays complete and you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over the management of existing Rabo OmniKassa or Rabo Smart Pay integrations, even when they were originally set up by another party. We review the API integration, signature validation, webhook configuration and error handling, document the current setup and draw up improvement proposals. From that point on, we handle changes, extensions and monitoring, including timely rotation of signing keys and tokens.
Ready to build your Rabo Smart Pay integration?
Tell us which payment methods you need and which webshop, point-of-sale or order system Rabo Smart Pay needs to connect to. We're happy to help think through the payment flow, webhooks, refunds and payment requests. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.