Custom Pay.nl integration development
Appfront builds custom Pay.nl integrations that fully integrate payments into your webshop, platform, marketplace or own application. Via the Pay. REST API and webhooks, we offer iDEAL, credit card and dozens of other payment methods in a hosted checkout or payment link, with recurring payments, refunds, split payments and terminals wherever you need them. Every payment status comes back to your system in real time.
What is a Pay.nl integration?
Pay. is a Dutch payment service provider (PSP) for online and in-store payments. Where many payment solutions are limited to a single channel, Pay. offers a broad package: iDEAL, credit card, Bancontact, PayPal and buy now, pay later in a hosted checkout, payment links for one-off payment requests, and physical terminals for the counter. Split payments and payouts are available for platforms and marketplaces.
In practice, a custom integration means: creating transactions programmatically from your webshop or application, offering the payment methods you want, receiving the payment status in real time via the webhook (exchange) and synchronising that status with your order or subscription administration. On top of that, we set up recurring payments/direct debit, refunds, payment links, split payments and terminal integrations wherever your process requires them.
Appfront builds according to the official Pay. developer documentation and the OWASP ASVS security standard. We tailor payment methods, status handling and reconciliation to your actual processes, so the integration grows with your product and payments keep running reliably even at peak volumes.
Broad range of payment methods
iDEAL, credit card, Bancontact, PayPal and buy now, pay later in a single hosted checkout. Your customers choose the method they trust, and you manage the full range from one Pay. integration instead of separate integrations per method.
Real-time payment status
The Pay. webhook (exchange) reports every status change to your system immediately: paid, failed, cancelled or refunded. Orders, subscriptions and invoices stay reliably in sync, with no manual polling or rework.
Online & in-store
One PSP for your webshop checkout, payment links and physical terminals at the counter. For retailers with omnichannel sales, that means a single source of transaction data and consistent reconciliation across all channels.
Our development process for Pay.nl integrations
We follow a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your payment flows, channels and payment methods through to go-live and ongoing maintenance, every step is aimed at an integration your own team can understand and trust.
We map out which payment methods you want to offer, which channels are involved (webshop, app, terminal), whether you need recurring payments, refunds, split payments or payouts, and how the status should flow back into your accounting.
We design the integration architecture around the Pay. REST API, choose the right authentication using the AT code and SL code, and draw up an error-handling and reconciliation strategy.
Implementation with automated tests, structured logging and monitoring. You see working builds along the way, including test transactions.
A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.
What a Pay.nl integration delivers in practice
Every Pay.nl integration is set up specifically for your payment flows, channels and adjacent systems. Below are the features we deliver most often for organisations that use Pay. as their payment service provider.
Checkout and payment methods
A hosted checkout in your webshop or app with iDEAL, credit card, Bancontact, PayPal and buy now, pay later. Customers complete their purchase in a familiar flow, and you manage the full range of methods centrally from Pay. without building a separate integration for each one.
Recurring payments and direct debit
Subscriptions and periodic payments via recurring payments and SEPA direct debit. We link the payment mandates and instalments to your subscription administration, with automatic reminders and clean handling of failed direct debits, so your MRR comes in reliably.
Refunds and payment links
Full and partial refunds from your own back office, without having to switch to the Pay. portal. Plus standalone payment links for quotes, telephone orders or invoices — a payment request you can share in seconds via email, app or QR code.
Split payments and payouts
For platforms and marketplaces: automatically divide a payment across multiple connected sellers and pay out at the right moment. We build the split rules and payout cycles in line with your commission model and administration.
Terminal and POS integration
Pay. card terminals linked to your till or POS software, so the amount due is sent to the terminal automatically and the result comes back. Online and in-store transactions come together in a single overview for balanced daily totals.
Transaction data to accounting and BI
Pass transactions, refunds and payouts to your accounting or BI environment in a structured way for accurate reconciliation. No more manual exports; completed and paid-out payments end up in the right place in your financial administration automatically.
Typical use cases in practice
A Pay.nl integration looks very different from one organisation to the next. We see a few patterns come up again and again — and for each of them we have a working setup that takes care of payment methods, status handling and proper reconciliation.
Webshops
Online retailers who want a reliable checkout with iDEAL, credit card and buy now, pay later. The payment status updates the order automatically via the webhook. Do you work on Shopify, Lightspeed or Magento? Also see our Shopify integration and Lightspeed eCom integration.
Platforms and marketplaces
Marketplaces and platforms that collect payments on behalf of connected sellers. Split payments divide each transaction automatically and payouts release commissions and revenue at the right moment — with balanced books per seller. See also our API integrations.
SaaS with recurring payments
SaaS companies and subscription services that invoice periodically via recurring payments and direct debit. We link payment mandates, instalments and failed direct debits neatly to your subscription administration, so renewals run automatically and your MRR comes in predictably.
Omnichannel retail
Retailers who sell both online and in store and want everything in one overview. Web shop checkout, payment links and Pay. terminals deliver a single source of transaction data, so daily reports add up and reconciliation across all channels runs smoothly.
Technology we use
We build Pay.nl integrations using the official REST API and webhooks, combined with the backend stack that suits you. The exact choice depends on your channels, payment methods and accounting set-up, so that your own team can manage or further develop the implementation.
If you use ICEPAY as your payment service provider, take a look at our ICEPAY integration.
Why Appfront for your Pay.nl 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, because an integration must not only be technically sound but also add practical value to the way you work.
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.
Working with a different PSP or want to compare? Also take a look at our Mollie integration, Adyen integration and Stripe integration, or our broader services around API integrations, middleware, custom software and web app development.
- Experience with the Pay. REST API, webhooks (exchange) and payment methods
- Specialist in e-commerce and platform integrations
- Familiar with recurring payments, refunds, split payments and payouts
- Secure by default: tokenisation, webhook validation, scoped permissions per service
- Structured error handling and retry mechanisms
- Extensive logging and monitoring from day one
- Watertight reconciliation with your accounting or BI
- 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 Pay.nl integrations
Payments always involve personal data and sensitive financial information. Thanks to Pay.'s hosted checkout and tokenisation, you neither process nor store card details yourself. This significantly reduces your PCI DSS scope and keeps the highest-risk data out of your own environment. Appfront builds on top of this following the OWASP ASVS: API tokens in secure vaults, webhook (exchange) validation, scoped permissions per service and encrypted connections.
We document the data flows around transactions, refunds and payouts so that your record of processing activities is complete and you demonstrably comply with the GDPR. We record payment statuses, mandates and payouts in a traceable way, so every transaction can be traced afterwards and your financial records stay watertight.
More about our approach to security: information security policy and CVD policy.
- No card data held in-house thanks to tokenisation
- Reduced PCI DSS scope through hosted checkout
- GDPR-compliant data processing and minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Validation and verification of the webhook (exchange)
- Role-based access and least-privilege principles
- Audit logs with traceable payment flows
- Monitoring and alerting for anomalies
- Documentation for your record of processing activities
Frequently asked questions about Pay.nl integrations
Answers to the questions we get asked most often about Pay. implementations.
A Pay.nl integration is a technical integration between Pay. (the payment service provider) and another system, such as your web shop, platform, marketplace or your own application. Via the Pay. REST API, transactions are created, payment methods such as iDEAL and credit card are offered in a hosted checkout or payment link, and payment statuses are reported back in real time via webhooks (exchange). An integration can range from simple (a single checkout on your web shop) to extensive (recurring payments, refunds, split payments and payouts for a platform or marketplace).
Pay. is a good fit for organisations that focus on the Dutch and European market and want to offer a broad range of payment methods, such as iDEAL, credit card, Bancontact, PayPal, buy now, pay later and more, often combined with physical terminals and split payments for platforms. For purely international card acquiring or a different set of payment methods, another PSP may be a better fit; during the intake we will work out together which provider best suits your situation.
A simple integration — a hosted checkout or payment link with the most common payment methods and a webhook for the payment status — can go live relatively quickly. More extensive scenarios, such as recurring payments or direct debit, refunds, split payments and payouts for a marketplace, or a terminal/POS integration, usually take more time. After an intake conversation, we'll give you a realistic estimate based on your situation.
We work with the official Pay. REST API and webhooks (exchange), combined with the backend stack that suits you — Node.js, Python, PHP or .NET. Authentication runs via an API token (AT code) and a service ID (SL code). For online payments, we set up hosted checkout, payment links, recurring payments, refunds and split payments; for in-store sales, we integrate terminals. Transaction and reconciliation data can flow through to your accounting or BI tools where required.
The cost depends on the complexity of the data flows, the number of payment methods and channels, whether recurring payments, split payments and payouts are needed, and the amount of custom business logic and reconciliation. Ongoing maintenance, monitoring and support also play a part. Pay.'s own transaction fees fall outside our services. We always provide a clear quote after a no-obligation analysis of your situation.
Yes. Thanks to Pay.'s hosted checkout and tokenisation, you don't process or store card details yourself, which greatly reduces your PCI DSS scope. Appfront builds in line with OWASP ASVS: API tokens in secure vaults, validation of the webhook (exchange), scoped permissions per service and encrypted connections. We document the data flows around transactions and payouts so that your record of processing activities stays complete and you can demonstrate GDPR compliance.
Yes. Appfront regularly takes over the maintenance of existing Pay. integrations, including those originally set up by another party. We review the API integration, the webhook configuration, the payment methods and the error handling, document the current setup and draft improvement proposals. From that point on, we handle changes, extensions and monitoring — including timely rotation of API tokens.
Pay. is a good fit for web shops, platforms and marketplaces, SaaS companies with subscriptions, and retailers that sell both online and in store. Typical use cases include a web shop checkout with iDEAL and credit card, subscriptions via recurring payments or direct debit, refunds and payment links, split payments and payouts for a marketplace, and a terminal or POS integration for omnichannel retail. For purely international card acquiring, we'll look with you at whether another PSP is a better fit.
Ready to build your Pay.nl integration?
Tell us which payment methods and channels you want to offer and which web shop, platform or application Pay. needs to integrate with — we're happy to advise on checkout, recurring payments, refunds, split payments, terminals and reconciliation. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.