OmniKassa 2.0 API iDEAL & credit card Webshop-native

Custom Rabo Smart Pay integration development

Appfront builds custom integrations with Rabo Smart Pay (formerly Rabo OmniKassa), the payment service provider of Rabobank. Via the OmniKassa 2.0 REST API we connect your webshop, point of sale or own 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 automatically in sync.

What is a Rabo Smart Pay integration?

Rabo Smart Pay is the payment service provider of Rabobank and the current name of what was previously called Rabo OmniKassa. It is a payment solution for webshops and small and medium-sized businesses that allows your customers to pay online with methods such as iDEAL, credit card, Bancontact, Maestro, V PAY and PayPal. The actual payment takes place on Rabobank's secure environment, so your webshop does not need to process or store card details itself.

In practice, a custom integration means: 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 through the API.

Appfront builds in line with the official Rabo OmniKassa developer documentation and the OWASP ASVS security standard. We align the payment flow, signature validation and error handling with your actual order 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 as soon as a payment succeeds, fails or is cancelled. No manual reconciliation required: your webshop and administration stay automatically in sync.

€

Refunds via the API

You process refunds programmatically: initiate a refund with 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 work to a proven methodology that removes uncertainty early and delivers a stable payment integration. From an initial analysis of your order process, payment methods and webshop platform through to going live and ongoing maintenance, every step is aimed at an integration your team can understand and trust.

1
Analysis & scope

We map out which payment methods you need, how your order process runs, which webshop or point-of-sale system Rabo Smart Pay has to integrate with, and whether refunds and payment requests are part of the picture.

2
Architecture

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.

3
Development

Implementation and testing of the payment flow in the sandbox environment, with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & management

Controlled transition to the production environment with payment validation and safeguards, followed by ongoing management and further development.

What a Rabo Smart Pay integration delivers in practice

Every Rabo Smart Pay integration is set up specifically for your order process, payment methods and adjacent systems. Below are the features we most often deliver 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 on Rabobank's environment and returns with a signed payment status, which your system verifies and processes.

P

iDEAL, credit card, Bancontact & PayPal

A single integration unlocks all Rabo Smart Pay payment brands: iDEAL including bank selection, credit cards (Mastercard, Visa), Bancontact, Maestro, V PAY and PayPal. We set up the checkout so that new payment brands can easily be added later.

Webhook notifications

Rabo Smart Pay sends a notification to your webhook URL with every status change. Your system then retrieves the related order results, with pagination for higher volumes, and updates the order status automatically. Essential for reliable order administration.

€

Refunds & repayments

You process full or partial refunds programmatically via the API: initiate a refund with amount, description and VAT category, check 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 with iDEAL, credit card or PayPal, which is ideal for invoices, telephone orders or orders placed outside the webshop. We link creating and tracking payment requests to your own administration.

Signing & security

Every return URL and webhook payload is cryptographically signed by Rabo Smart Pay with a signing key. Our integration validates that signature on every status update, so tampering is rejected. We keep tokens and keys in secure vaults and rotate them on schedule.

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 & point of sale

Shops and hospitality businesses that want to process physical and online payments under one Rabo Smart Pay account. We connect your till or order system to the payment service, so payments, status updates and refunds come in centrally and your end-of-day closing balances easily.

€

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 with Rabobank for repeat payments, while your own application manages invoicing and access based on the payment status.

€

Services & invoicing

Service providers and SMEs that have customers pay invoices or orders outside a webshop. With payment requests and payment links, the customer gets a direct payment option via iDEAL, credit card or PayPal, and the payment status is passed back to your accounting or CRM.

Technology we use

We build Rabo Smart Pay integrations using the official OmniKassa 2.0 REST API and its accompanying SDKs, combined with the backend stack that suits you. The precise choice depends on your webshop platform and environment, so your own team can manage or further develop the implementation.

OmniKassa 2.0 REST API Rabo Smart Pay webhooks Official PHP / Java / .NET SDKs Signature validation (signing key) Refresh and access tokens Node.js / Python / PHP / .NET iDEAL with issuer selection Credit card (Mastercard, Visa) Bancontact / Maestro / V PAY PayPal Refund API Rabo Payment Request / payment links Card-on-file (CoF) Sandbox & production environment WooCommerce / Magento connectors Monitoring & logging

Why choose 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 any future supplier, can understand and manage it. No black box, just 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. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.

See also our wider services around API integrations, middleware, custom software and web app development. Do you work with a different payment service provider? Then take a look at 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, separated environments
  • Structured error handling and retry mechanisms
  • Comprehensive logging and monitoring from day one
  • Clear documentation your team can read and manage
  • A fixed point of contact, no account managers passed around
  • Ongoing maintenance and proactive further development
  • A way of working tailored to your existing webshop and IT landscape

Security and privacy in Rabo Smart Pay integrations

Payments always involve personal data and sensitive payment information. With Rabo Smart Pay, Rabobank acts as the payment service provider and handles the card and payment data: the actual payment takes place on 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 kept 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. The signed status messages from Rabo Smart Pay serve as verifiable evidence of every payment status change.

More on our security approach: information security policy and CVD policy.

  • GDPR-compliant data processing and data minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Automatic retries and dead-letter queues
  • Monitoring and alerting for anomalies
  • Secrets management in line with best practice
  • 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 link between Rabo Smart Pay (formerly Rabo OmniKassa) and your webshop, point-of-sale system or own 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 previously called Rabo OmniKassa. The underlying OmniKassa 2.0 REST API is the same technical foundation: the naming of the developer SDKs and documentation still refers to OmniKassa. An existing Rabo OmniKassa integration therefore continues to work under the name Rabo Smart Pay, and new integrations we build use that same OmniKassa 2.0 API.

Rabo Smart Pay supports, among others, iDEAL, credit cards (Mastercard and Visa), Bancontact, Maestro, V PAY and PayPal. Payment requests (Rabo Betaalverzoek) and buy-now-pay-later options via partners are also available. The documentation states that new payment brands may be added, so we set up the integration in a way that additional methods can easily be switched on later.

With the OmniKassa 2.0 REST API, the webshop first announces an order; Rabo Smart Pay returns an omnikassaOrderId and a redirect URL, through which the customer completes the payment steps. Authentication works via a refresh token, which is used to obtain 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 straightforward integration, covering announcing orders, redirecting customers, processing 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 longer. After an intake meeting, we will give you a realistic estimate.

We work with the official OmniKassa 2.0 REST API and its corresponding 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 implement 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 data and card details; the actual payment takes place on Rabobank's environment, so your webshop does not need to store card numbers. Appfront builds in line with the OWASP ASVS: signing keys and tokens are kept in secure vaults, signature validation is mandatory on every webhook and return URL, and rights are separated per environment. We document the data flows so that your record of processing activities remains complete and you can demonstrably comply with the GDPR.

Yes. Appfront regularly takes over 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 propose improvements. 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 should connect to. We are happy to help you think through the payment flow, webhooks, refunds and payment requests. A no-obligation first conversation will give you a clear picture of what is possible within half an hour.

Edit content