Payments In-store & online REST API & webhooks

Custom CCV integration development

Appfront builds custom CCV integrations that bring physical and online payments together in one payment flow, from your webshop, till, platform or own application. Via the CCV Payment API and webhooks you process payments with iDEAL, credit card and more, connect CCV payment terminals to your till, and automatically feed transaction data into your accounting. You keep oversight of every payment, online and at the counter alike.

What is a CCV integration?

CCV is a payment service provider (PSP) with a strong position in the Dutch and European markets for both in-store and online payments. In store, CCV processes payments through 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 tills. What sets CCV apart is precisely that combination: one provider for both the counter and the webshop.

Please note: this page is about CCV as a payment service provider, not 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 bookkeeping via webhooks.

Appfront builds to 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, including during peak moments in the shop or webshop.

€

Chip and PIN and online 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 of physical and digital transactions makes reconciliation and reporting simpler.

iDEAL

Wide range of payment methods

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

Real-time status updates

CCV sends a webhook for every status change, and your system then retrieves the transaction status. Orders, receipts and accounts stay automatically in sync with the actual payment status, without manual checking.

Our development process for CCV integrations

We work to a proven methodology 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 management, every step is aimed at an integration your team can understand and trust.

1
Analysis & scope

We map out which channels you take payments through, whether webshop, till or 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 accounts.

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 & management

Controlled go-live with data validation and a safety net, followed by ongoing management and further development.

What a CCV integration concretely delivers

Every CCV integration is set up specifically for your sales channels, payment methods and adjacent systems. Below are the features we most often deliver 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, including iDEAL, credit cards and more, and reliably pass 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 automatically to the terminal and the receipt is correct. One streamlined checkout flow at the counter, linked to your stock and accounting.

€

Payment links

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

€

Refunds from your 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 accounts.

Omnichannel: one payment flow

Physical and online payments brought together under one CCV account and one integration. Whether a customer pays by card in store or checks out in your webshop, transactions come together in one overview, making 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 matched to the correct orders, so reconciling takes less manual work and your figures stay up to date.

Typical use cases in practice

A CCV integration looks very different from one organisation to the next. We often see a number of recurring patterns — and for each we have a proven setup, with attention to payment methods, till or webshop integration, and correct handling of statuses and refunds.

€

Retail & 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 one payment flow so that sales match across channels. See also our API integrations and the MultiSafepay integration.

Hospitality

Restaurants, cafés and hospitality concepts that want fast, reliable payments at the table or the bar. Payment terminals linked to the point-of-sale system, tip handling and, where desired, payment links for reservations or deposits, all within one CCV flow.

€

Webshops & e-commerce

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

Platforms & unattended payment points

Platforms, marketplaces and organisations with unattended payment points, such as vending machines and self-service tills. CCV processes the payment, and your platform links the transaction to the correct account or product. See also our middleware.

Technology we use

We build CCV integrations using the CCV Payment API and webhooks, combined with the backend stack that suits you. The exact choice depends on your channels — online, till 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 begin with a thorough analysis of your existing systems and processes. A payment integration needs to work technically, but it also has to add practical value to the way your till or webshop operates.

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. Feel free to compare with other payment integrations such as Adyen and Pay.nl.

  • Experience with the CCV Payment API, payment methods and webhooks
  • Specialists in integrations between webshops, tills, POS systems and payment terminals
  • Familiar with both in-store and online payments within a single payment flow
  • Secure by default: card data held by CCV, tokenisation, scoped permissions
  • 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 aligned with your existing IT landscape

Security and privacy in CCV integrations

Payments always involve sensitive data. That is why, in a CCV integration, we never handle card details ourselves: card data stays within CCV's PCI DSS environment, and we work exclusively with tokens and transaction references. Appfront builds in line with CCV's security best practices and the OWASP ASVS. This means, among other things: API keys and credentials kept 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 record of processing activities 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 on our security approach: information security policy and CVD policy.

  • Card data held within CCV's PCI DSS environment, never stored by us
  • Tokenisation and transaction references instead of card details
  • 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 payment flows
  • Automatic retries 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 are asked most often about CCV implementations.

A CCV integration is a technical link between CCV and another system, such as your webshop, till, platform or own application. CCV is a payment service provider (PSP) for both in-person payments via card 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 cards, 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 (one payment flow across till and webshop, with refunds and transaction data feeding into your accounting).

CCV is the payment service provider (PSP) that processes payments, both in-store at the till using card terminals and online via CCV Online Payments. CCV Shop is a separate webshop platform for building an online store. This page covers only the payment service: connecting CCV payments to your webshop, till, platform or application. If you want to connect a webshop on the CCV Shop platform to other systems, we will determine in an intake conversation which approach fits best.

CCV suits business owners who want to combine in-person and online payments in a single payment flow, such as 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 card terminals, online payment methods such as iDEAL and credit cards, and unattended payment solutions. For purely international card acquiring at large scale, another PSP may be more suitable; we will discuss this 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 card terminals with your till or POS. Refunds, status handling via webhooks and transaction data feeding into your accounting or BI are all part of the integration.

The cost depends on the complexity of the payment flows, the number of channels to connect (webshop, till, platform), whether online and in-person payments are both involved, and the amount of custom work in the business logic. Ongoing management, 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. 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 are kept in secure vaults, webhook signatures and status are validated, rights are scoped, and permissions are strictly separated per integration. We document the data flows so your record of processing activities stays complete and you can demonstrate GDPR compliance.

Yes. Appfront regularly takes over 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 propose improvements. From that point on, we can handle changes, extensions and monitoring, including timely rotation of API keys.

A CCV integration suits organisations that take payments through multiple channels: retailers with physical stores and a webshop, hospitality, e-commerce, omnichannel businesses and platforms with unattended payment points. Typical use cases include online checkout in the webshop, till and POS integration with card terminals, payment links for invoices, refunds initiated from your own system, and transaction data flowing automatically into your accounting or BI. A single payment flow across in-store and online makes reconciliation much simpler.

Ready to build your CCV integration?

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

Edit content