Payments In-store & online REST API & webhooks

Custom CCV integration development

Appfront builds custom CCV integrations that bring in-store and online payments together in a single payment flow, from your webshop, till, platform or own application. Through the CCV Payment API and webhooks, you process payments with iDEAL, credit card and more, connect CCV payment terminals to your till, and have transaction data flow automatically into your accounting. You keep an overview of every payment, online and at the counter.

What is a CCV integration?

CCV is a payment service provider (PSP) with a strong position in the Dutch and European market for both in-store and online payments. At the till, CCV processes payments via payment terminals; online, checkout runs through CCV Online Payments with payment methods such as iDEAL and credit card. CCV also supports unattended payment points, such as vending machines and self-service checkouts. What sets CCV apart is precisely that combination: one provider for the counter and the webshop.

Please note: this page is about CCV as a payment service provider, not about CCV Shop, which is a separate webshop platform. In practice, a custom integration means: creating payments programmatically via the Payment API, offering the right payment methods in your checkout, integrating payment terminals with your till or POS, generating payment links for invoices, handling refunds from your own system, and synchronising payment status with your accounting via webhooks.

Appfront builds in line with the official CCV Payment API documentation and the OWASP ASVS security standard. We align payment flows, status handling and error scenarios with your actual sales processes, so the integration keeps running reliably, even during peak moments in your shop or webshop.

€

In-store and online payments in one flow

Payments at the till via CCV payment terminals and online via CCV Online Payments, brought together in a single payment flow. One overview across physical and digital transactions makes reconciliation and reporting simpler.

iDEAL

Wide range of payment methods

iDEAL, credit card and other common payment methods give your customers the choice they expect. We set up the right methods in your checkout, so paying runs smoothly and you see fewer abandoned payments.

Real-time status updates

CCV reports every status change via webhooks; your system then retrieves the transaction status. Orders, receipts and accounting stay automatically in sync with the actual payment status, with no manual checking.

Our development process for CCV integrations

We follow a proven method that removes uncertainty early and delivers a stable payment integration. From an initial analysis of your sales channels, payment methods and till or webshop environment through to go-live and ongoing maintenance, every step is aimed at an integration your team can understand and trust.

1
Analysis & scope

We map out which channels you process payments through (webshop, till, platform), which payment methods you need, whether both online and in-person payments are involved, and how refunds and transaction data should land in your accounting.

2
Architecture

We design the integration architecture, choose the right authentication and draw up an error-handling strategy.

3
Development

Implementation with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.

What a CCV integration delivers in practice

Every CCV integration is set up specifically for your sales channels, payment methods and adjacent systems. Below are the features we deliver most often for organisations that use CCV as their payment service provider: online, at the till or both.

Online checkout and payment methods

A smooth online checkout in your webshop or application via CCV Online Payments. We offer the payment methods your customers expect, such as iDEAL, credit card and more, and reliably feed the payment status back into your order flow.

Till, POS and payment terminals

Integration of CCV payment terminals with your till or POS system, so the amount is sent to the terminal automatically and the receipt is correct. One streamlined checkout flow at the counter, linked to your inventory and accounting.

€

Payment links

Generate payment links for invoices, phone orders or remote payments. The customer pays securely via a CCV payment page; your system receives the confirmation via webhook and immediately links it to the correct order or invoice.

€

Refunds from your own system

Process refunds directly from your own till, webshop or back office. A refund action calls the Payment API, CCV processes the refund and the status comes back via webhook, neatly logged for your accounting.

Omnichannel: one payment flow

In-store and online payments brought together under one CCV account and one integration. Whether a customer pays by card in the shop or checks out in the webshop, the transactions come together in one overview, which makes reconciliation and reporting much simpler.

Transaction data to accounting and BI

Transaction and reconciliation data flows automatically into your accounting or BI environment. Payments, refunds and payouts are linked to the correct orders, so matching takes less manual work and your figures stay up to date.

Typical use cases in practice

A CCV integration turns out very differently for each organisation. We see a number of patterns come up again and again, and for each of them we have a working setup that pays attention to payment methods, till or webshop integration and the right status and refund handling.

€

Retail and omnichannel

Retail chains and retailers with physical stores and a webshop. CCV payment terminals at the till and CCV Online Payments in the webshop, brought together in a single payment flow, so sales add up across channels. See also our API integrations and the MultiSafepay integration.

Hospitality

Restaurants, cafés and hospitality concepts that want to take payments quickly and reliably at the table or the bar. Payment terminals linked to the till system, tip handling and, where needed, payment links for reservations or deposits, all within a single CCV flow.

€

Webshops & e-commerce

Online shops that want to use CCV Online Payments for iDEAL, credit card and more. A smooth checkout, reliable status updates via webhooks and refunds from the order system. Feel free to compare it with our Mollie integration.

Platforms & unattended payment points

Platforms, marketplaces and organisations with unattended payment points, such as vending machines and self-service checkouts. CCV processes the payment, and your platform links the transaction to the right account or product. Also take a look at our middleware.

Technology we use

We build CCV integrations with the CCV Payment API and webhooks, combined with the backend stack that suits you. The exact choice depends on your channels (online, in-store or both) and the payment methods you need, so that your own team can manage or further develop the implementation.

CCV Online Payments REST API CCV webhooks API key / credentials iDEAL / credit card Payment terminals / POS Payment links Refunds Unattended payments PCI-DSS Tokenisation Node.js / Python / PHP / .NET Webshop & till integrations Accounting & BI integrations HMAC webhook validation GitHub Actions

Why Appfront for your CCV integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes: a payment integration must not only be technically sound, but also add practical value to the way you run your till or webshop.

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.

Also take a look at our broader services around API integrations, middleware, custom software and web app development. Feel free to compare with other payment integrations such as Adyen and Pay.nl.

  • Experience with the CCV Payment API, payment methods and webhooks
  • Specialist in integrations between webshop, till, POS and payment terminals
  • Familiar with in-store and online payments in a single payment flow
  • Secure by default: card data stays with CCV, tokenisation, scoped permissions
  • 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 IT landscape

Security and privacy in CCV integrations

Payments always involve sensitive data. That is why, in a CCV integration, we never process card data ourselves: the card data stays within CCV's PCI-DSS environment, and we work exclusively with tokens and transaction references. Appfront builds in line with CCV security best practices and the OWASP ASVS. Among other things, that means: API keys and credentials in secure vaults, webhook signature and status validation, scoped permissions and regular audits of the payment and refund flows.

As a payment service provider, CCV is PCI-DSS compliant and processes payments within that secure environment. We document the data flows, payment methods and webhook configuration so that your processing register is complete and you can demonstrably comply with the GDPR. Transaction references and status logs serve as traceable evidence for every payment and refund.

More about our approach to security: information security policy and CVD policy.

  • Card data within CCV's PCI-DSS environment, never stored by us
  • Tokenisation and transaction references instead of card data
  • 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 payment flows
  • Automatic retry and dead-letter queues
  • Monitoring and alerting for unusual transactions
  • Documentation for your record of processing activities

Frequently asked questions about CCV integrations

Answers to the questions we get asked most often about CCV implementations.

A CCV integration is a technical connection between CCV and another system — such as your webshop, till, platform or custom application. CCV is a payment service provider (PSP) for both in-person payments via payment terminals and online payments via CCV Online Payments. The CCV Payment API lets you create payments programmatically, offer payment methods such as iDEAL and credit card, and generate payment links. Webhooks report status changes, after which your system retrieves the transaction status. An integration can be simple (an online checkout in your webshop) or extensive (a single payment flow across till and webshop, with refunds and transaction data passed to your accounting).

CCV is the payment service provider (PSP) that processes payments — both in person at the till with payment terminals and online via CCV Online Payments. CCV Shop is a separate webshop platform for building an online store. This page deals exclusively with the payment service: integrating CCV payments with your webshop, till, platform or application. If you instead want to integrate a webshop on the CCV Shop platform with other systems, we will look at which approach fits in an initial meeting.

CCV suits businesses that want to combine in-person and online payments in a single payment flow — think retail, hospitality and omnichannel organisations that take payments both at the till and in the webshop. CCV is strong in the Dutch and European market, with payment terminals, online payment methods such as iDEAL and credit card, and unattended payment solutions. For purely international card acquiring at large scale, a different PSP may be a better fit; we will discuss that openly with you.

We work with the CCV Payment API (REST) and webhooks, combined with the backend stack that suits you — Node.js, Python, PHP or .NET. Authentication runs via API key or credentials. For online payments, we set up the checkout, payment methods and payment links; for in-person payments, we integrate CCV payment terminals with your till or POS. Refunds, status handling via webhooks and transaction data passed to your accounting or BI are all part of the integration.

The cost is determined by the complexity of the payment flows, the number of channels to integrate (webshop, till, platform), whether both online and in-person payments are involved, and the amount of custom business logic. Ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation. CCV's own transaction fees are not included in our quote.

Yes. For payments, we never process card details ourselves: sensitive card data stays within CCV's PCI DSS environment, and we work with tokens and transaction references. Appfront builds in line with OWASP ASVS: API keys and credentials in secure vaults, webhook signature and status validation, scoped access and strictly separated permissions per integration. We document the data flows so that your record of processing activities stays complete and you can demonstrate GDPR compliance.

Yes. Appfront regularly takes over the maintenance of existing CCV integrations, even if they were originally set up by another party. We review the Payment API integration, payment methods, webhook configuration, refund handling and error handling, document the current setup and draft improvement proposals. From that point on, we can handle changes, extensions and monitoring — including timely rotation of API keys.

A CCV integration suits organisations that process payments across multiple channels: retailers with physical shops and a webshop, hospitality, e-commerce, omnichannel businesses and platforms with unattended payment points. Typical use cases: online checkout in the webshop, POS integration with payment terminals, payment links for invoices, refunds from your own system, and transaction data that flows automatically to your accounting or BI. A single payment flow across physical and online makes reconciliation easier.

Ready to build your CCV integration?

Tell us which channels you process payments through (webshop, till or both) and which payment methods CCV needs to support. We're happy to help with the online checkout, payment terminal integration, payment links, refunds and transaction data for your accounting. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.

Edit content