Custom Pay.nl integration development
Appfront builds custom Pay.nl integrations that fully embed payments into your webshop, platform, marketplace or own application. Through 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 flows back into 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 cards, Bancontact, PayPal and buy-now-pay-later in a hosted checkout, payment links for individual payment requests, and physical terminals for the counter. For platforms and marketplaces, split payments and payouts are available.
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/direct debit, refunds, payment links, split payments and terminal integrations where your process requires them.
Appfront builds in line with the official Pay. developer documentation and the OWASP ASVS security standard. We align payment methods, status handling and reconciliation with your actual processes, so the integration grows alongside your product and payments remain reliable even at peak volumes.
Broad payment methods
iDEAL, credit card, Bancontact, PayPal and pay later in a single hosted checkout. Your customers choose their preferred method, and you manage the full range from one Pay. integration instead of separate integrations for each method.
Real-time payment status
The Pay. webhook (exchange) reports every status change directly to your system: paid, failed, cancelled or refunded. Orders, subscriptions and invoices stay reliably in sync, without 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 management, every step is designed to give you an integration your team can understand and trust.
We map out which payment methods you want to offer, which channels are involved (webshop, app, terminal), whether recurring, refunds, split payments or payouts are needed, and how the status should flow back into your accounting.
We design the integration architecture around the Pay. REST API, choose the right authentication with AT code and SL code, and set out an error handling and reconciliation strategy.
Implementation with automated tests, structured logging and monitoring. You will see working builds along the way, including test transactions.
Controlled go-live with data validation and a safety net, followed by ongoing management and further development.
What a Pay.nl integration delivers in practice
Every Pay.nl integration is tailored to your payment flows, channels and adjacent systems. Below are the capabilities we most often deliver for organisations using Pay. as their payment service provider.
Checkout & payment methods
A hosted checkout in your webshop or app with iDEAL, credit card, Bancontact, PayPal and pay later. Customers complete payment in a familiar flow, and you manage the full range of methods centrally through Pay., without building a separate integration for each method.
Recurring & direct debit
Subscriptions and periodic payments via recurring and SEPA direct debit. We link 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 & 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 within seconds by email, app or QR code.
Split payments & payouts
For platforms and marketplaces: automatically split a payment across multiple connected sellers and release payouts at the right moment. We build the splitting rules and payout cycles in line with your commission model and accounting.
Terminal & till integration
Pay. card terminals connected 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 appear together in one overview for balanced end-of-day reports.
Transaction data to accounting and BI
Transactions, refunds and payouts passed on in a structured way to your accounting or BI environment for clean reconciliation. No more manual exports; completed and paid-out payments appear automatically in the right place in your financial records.
Typical use cases in practice
A Pay.nl integration looks very different from one organisation to the next. There are a few patterns we see often, and for each we have a working setup with attention to payment methods, status handling and the right reconciliation.
Online shops
Online retailers who want a reliable checkout with iDEAL, credit card and pay later. The payment status updates the order automatically via the webhook. Working on Shopify, Lightspeed or Magento? See also our Shopify integration and Lightspeed eCom integration.
Platforms & 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 clean accounting per seller. See also our API integrations.
SaaS with recurring billing
SaaS companies and subscription services that bill periodically via recurring and direct debit. We neatly link payment mandates, instalments and failed direct debits to your subscription administration, so renewals run automatically and your MRR comes in predictably.
Omnichannel retail
Retailers who sell both online and in store want everything in one overview. Webshop checkout, payment links and Pay. terminals together provide a single source of transaction data, so end-of-day figures reconcile and reconciliation across all channels runs smoothly.
Technology we use
We build Pay.nl integrations with the official REST API and webhooks, combined with the backend stack that suits you. The precise choice depends on your channels, payment methods and administration, so that your own team can manage or further develop the implementation.
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. An integration should not only work technically, but also add practical value to the way you work.
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.
Using a different PSP, or want to compare? Also see 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
- Specialists in e-commerce and platform integrations
- Experienced with recurring payments, refunds, split payments and payouts
- Secure by default: tokenisation, webhook validation, rights scoped per service
- Structured error handling and retry mechanisms
- Comprehensive logging and monitoring from day one
- Watertight reconciliation to your accounting or BI
- 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 Pay.nl integrations
Payments always involve personal data and sensitive financial information. Thanks to Pay.'s hosted checkout and tokenisation, you never process or store card details yourself, which significantly reduces your PCI DSS scope and keeps the most high-risk data outside your own environment. On top of that, Appfront builds to 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 back afterwards and your financial administration remains watertight.
More on our security approach: information security policy and CVD policy.
- No card data held in-house thanks to tokenisation
- Reduced PCI DSS scope via hosted checkout
- GDPR-compliant data processing and data 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 receive most often about Pay. implementations.
A Pay.nl integration is a technical link between Pay. (the payment service provider) and another system, such as your webshop, platform, marketplace or own application. Through the Pay. REST API, transactions are created, payment methods such as iDEAL and credit cards are offered in a hosted checkout or payment link, and payment statuses are fed back in real time via webhooks (exchange). An integration can be simple (a single checkout on your webshop) or extensive (recurring payments, refunds, split payments and payouts for a platform or marketplace).
Pay. suits organisations focused on the Dutch and European market that 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 methods, another PSP may be a better fit; during the intake we will look together at which provider best suits your situation.
A simple integration, such as a hosted checkout or payment link with the most widely used payment methods and a webhook for payment status, can go live relatively quickly. More advanced scenarios involving recurring or direct debit, refunds, split payments and payouts for a marketplace, or a terminal/point-of-sale integration, usually take longer. After an intake conversation, we provide 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 payments, we set up hosted checkout, payment links, recurring payments, refunds and split payments; for in-store sales, we connect terminals. Where desired, transaction and reconciliation data flows through to your accounting or BI.
The cost is determined by the complexity of the data flows, the number of payment methods and channels, whether recurring payments, split payments and payouts are required, and the amount of custom work involved in the business logic and reconciliation. Ongoing management, monitoring and support also factor in. Pay.'s own transaction fees fall outside our services. We always provide a clear quote following a no-obligation analysis of your situation.
Yes. Thanks to Pay.'s hosted checkout and tokenisation, you never process or store card details yourself, which greatly reduces your PCI DSS scope. Appfront builds to OWASP ASVS: API tokens in secure vaults, webhook (exchange) validation, scoped permissions per service and encrypted connections. We document the data flows around transactions and payouts so your record of processing activities remains complete and you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over existing Pay. integrations, even if they were originally set up by another party. We review the API integration, webhook configuration, payment methods and error handling, document the current setup and propose improvements. From that point on, we handle adjustments, extensions and monitoring, including timely rotation of API tokens.
Pay. is a good fit for webshops, platforms and marketplaces, SaaS companies with subscriptions, and retailers selling both online and in-store. Typical use cases include a webshop checkout with iDEAL and credit card, subscriptions via recurring or direct debit, refunds and payment links, split payments and payouts for a marketplace, and a terminal or point-of-sale integration for omnichannel retail. For purely international card acquiring, we will look with you at whether another PSP would be a better match.
Ready to build your Pay.nl integration?
Tell us which payment methods and channels you want to offer, and which webshop, platform or application Pay. needs to connect with. We are 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.