Custom ICEPAY integration development
ICEPAY is a Dutch payment service provider with a REST API, a hosted checkout, payment links and plugins for well-known web shop platforms. For a standard web shop, such a plugin is enough. But as soon as payments need to come from your own portal, an app, an invoicing flow or a booking system, custom work is needed. Appfront builds the integration between ICEPAY and your own software: the payment started from your system, the status straight back, and refunds and reconciliation without manual work.
What is an ICEPAY integration?
An ICEPAY integration lets your own software handle payments via ICEPAY. Your system creates the payment, the customer pays with iDEAL, a card or another method that ICEPAY offers, and the outcome comes straight back into your system: the order goes to dispatch, the invoice is marked as paid, the booking is confirmed. You start a refund from your own screen, and your accounting software receives ICEPAY's payouts matched to the underlying payments.
Without an integration, you rely on a plugin that only suits a standard webshop, or on payment links that someone sends by hand. The status has to be looked up in the ICEPAY portal, a refund goes through that same portal and is then retyped into the accounting system, and the payout to the bank account is an amount that nobody can match to individual payments any more. With a few payments a day that works; with dozens it doesn't.
We build custom because your system determines what the payment looks like. Whether it's a webshop, a subscription portal, an app or an invoice flow, which payment methods you offer, how you handle partial payments and refunds, and which accounting package you use all differ. ICEPAY offers a REST API and webhooks for this; the integration uses them from your system.
Your own system
Payment starts where you work.
Status sent back
Instantly, via webhook.
Reconciled
Payment on order and invoice.
How we build your ICEPAY integration
We start with your payment flow: where payments currently originate, which methods you offer, what has to happen after a payment and how your accounting currently processes it. Then we build the first integration, starting a payment and processing the status, because that is where the manual work is. You work with it in ICEPAY's test environment for a while and then go live. Refunds, reconciliation and the accounting integration follow once that runs well. After that, we maintain the integration whenever ICEPAY or your system changes.
Where, how, what next.
The first integration.
Expansion.
Go-live, monitoring, and maintenance when things change.
What an ICEPAY integration actually does
The components below appear in almost every payment integration. Which ones you need depends on your system and your payment flow.
Starting a payment
From an order, invoice or app.
Payment methods
What ICEPAY offers.
Status
Webhook to your system.
Refund
From your own screen.
Reconciliation
Payment on order and invoice.
Accounting
Payout matched.
Who we build an ICEPAY integration for
The integration is intended for organisations with their own system in which payments originate or need to land. The more payments per day and the more that has to happen after a payment, the more it delivers.
Webshops
Your own platform, no standard plugin.
Portals
Subscriptions and invoices.
Apps
Paying in the app.
Associations
Membership fees and registrations.
Technology and integrations
This page is about ICEPAY integrations. If you use a different payment provider, see our page on the Pay.nl integration or the Payt integration; if you want to build your own payment environment, see our page on a payment platform. You can read about our approach on building software.
Why Appfront for your ICEPAY integration?
An order that gets stuck because the payment status never came through, a refund that has to be entered in two systems, or a payout that nobody can reconcile any more costs an organisation time and customer trust. That is what we build around: paying from your own system, the status straight back, and every payment in the right place in your accounts.
No manual work
Status arrives automatically.
Balanced
Payment on order and invoice.
One screen
Refunds too.
Security and privacy in an ICEPAY integration
The integration processes payment data, but not card details: those stay with ICEPAY. Your system only sees the status and the amount. Access to refunds is set up per role, and every transaction is logged with time and result.
The integration runs in a European data centre, with encrypted connections. Keys for the ICEPAY API are kept secure and are not visible to staff or customers. Webhooks are verified for origin before they are processed.
Frequently asked questions about an ICEPAY integration
Questions that webshop owners and finance administrators ask before getting started.
A connection between your own software and ICEPAY, so that payments are started from your system and the outcome comes straight back. Orders, invoices and bookings are then updated automatically.
Yes. ICEPAY offers a REST API with webhooks, alongside a hosted checkout, payment links and plugins for webshop platforms. The integration uses the API and webhooks from your system.
When payments don't come from a standard webshop but from your own portal, an app or an invoicing flow, or when something has to happen in your own system after payment that a plugin doesn't know about.
The methods that ICEPAY makes available for your account, such as iDEAL, Bancontact, cards and PayPal. Which ones those are depends on your agreement with ICEPAY.
Yes. You start a refund, including a partial one, from the order or invoice in your system. The integration sends it to ICEPAY and processes the confirmation.
The ICEPAY payout is linked to the payments it contains, so that accounting can reconcile payment by payment rather than by lump sum.
For organisations with their own system and dozens of payments a day or more. For a standard webshop with few orders, the ICEPAY plugin is usually enough.
ICEPAY in your own system?
Tell us where payments originate for you and what needs to happen after a payment. We'll show you how an ICEPAY integration can handle that.