Custom card issuing software development
Appfront builds the software around card issuing: applying for cards, activating them, setting budget and spending rules, blocking cards and making transactions visible. The issuing itself stays with a licensed party; we build the layer in which your organisation and your cardholders work. Get in touch to discuss what your situation needs.
What is card issuing software?
Card issuing software is the layer between your organisation and a card issuer. The issuer is a licensed party that actually issues the cards and processes the transactions; your software handles everything around that: who gets a card, with what spending allowance, which rules apply, how cards are activated or blocked, and how transactions end up in your own accounting.
That distinction matters. Issuing payment cards yourself requires licences and a connection to card schemes — that is not a software question but a licensing question. What does belong with a custom software developer is the programme logic: budgets, approvals, category rules, receipt handling and the integration with your accounting.
Appfront builds that layer as custom software on top of the API of an issuer you choose. For broader fintech challenges, see custom fintech development.
Rules before the spend
Who gets a card, with what limit, for which categories and with what approval, all recorded as policy rather than as ad hoc agreements.
Cardholders do it themselves
Activating, setting a PIN, temporarily blocking a lost card and adding a receipt to a transaction, without the finance team having to step in.
Transactions in your own accounting
Transactions come in, are enriched with cost centre and receipt, and flow through to your accounting instead of sitting in a separate file.
What we do and don't do
With card issuing, the division of roles is essential, and it is more honest to state it upfront than afterwards.
The programme layer
Application and approval, budget and category rules, activation and blocking, receipt handling, transaction insight, reporting and the integration with your accounting or ERP system, all on top of your issuer's API.
The issuing itself
The card issuing, the connection to the card schemes, transaction processing and the supervision that comes with it. That requires licences a software builder does not provide. We do help with the choice and the technical connection.
Our development process for your card programme
The choice of issuer determines what is technically possible. That is why we put it first rather than running into it halfway through.
We map out who the cardholders are, which rules must apply, which approvals are needed and how transactions should end up in your accounting. We also assess which issuers support the features you need, which varies considerably.
We design the rules model, the application and approval flow, the cardholder environment and the integrations with the issuer and your accounting.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.
A controlled go-live with validation and a safety net, followed by ongoing management, monitoring and further development as your card programme or choice of issuer changes.
What custom card software delivers in practice
What you need varies per programme. These are the components that come up most often.
Application and approval
An application flow with the approvals that fit your organisation, and issuing of physical or virtual cards via the issuer as soon as approval is given.
Budget and spending rules
Limits per period, permitted categories, geographic restrictions and time windows, configurable per card or per group of cardholders.
Cardholder environment
Activating, viewing balance and transactions, temporarily blocking a lost card and adding a receipt, in an app or web environment in your own branding.
Receipts and accountability
Linking a receipt to the transaction, with a reminder for missing receipts and a review and approval step for the budget holder.
Accounting integration
Passing transactions with cost centre, general ledger and VAT treatment to your accounting, for example via an Exact Online integration.
Monitoring and alerts
Alerts for unusual spending, cards that haven't been used for a long time and overspending, with an audit trail of every change to limits and rules.
Typical use cases in practice
We mainly see card programmes where money has to reach other people in a controlled way.
Business expenses
Organisations that give employees a payment card instead of reimbursing expense claims afterwards, with rules per role and instant accountability.
Mobility and fuel
Vehicle fleets and mobility schemes where spending is tied to a vehicle, a category and sometimes a location.
Social services and allowances
Organisations that provide targeted spending allowances where spending is restricted to certain categories and accountability is required.
Platforms with payouts
Marketplaces and platforms that want to give participants spending power without first transferring money and accounting for it afterwards.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology we use
Working with a card issuer means working within their API and their security and logging requirements. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, with no dependence on per-user licences.
Why Appfront for your card programme?
Appfront builds custom software for a wide range of organisations in the Netherlands. With card programmes, we are clear up front about the division of roles: issuing belongs with a licensed party, the programme layer with us. That avoids a conversation halfway through in which it turns out something is not allowed.
We start by comparing issuers, because their API determines what can be built. Designing a programme and only then discovering that your issuer doesn't support category rules is an expensive way round.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.
Also see our broader services around custom software, fintech development and KYC/AML compliance software. Unsure about the approach? Get in touch.
Security for your card programme
Payment cards are subject to strict requirements for handling card data. Appfront designs so that sensitive card data does not flow through your own systems: the cardholder environment displays it directly via the issuer. That significantly limits your own obligations. We build in line with OWASP ASVS.
Transaction data is personal data and reveals a lot about a person's activities. We restrict access to those who functionally need it, record every change to limits and rules in an audit trail, and document the data flows for your record of processing activities.
More about our approach to security: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail of views and changes
- Secrets in a secure vault, not in code
- Documented data flows for your processing register
- Card data stays with the licensed issuer
Frequently asked questions about building card issuing software
Answers to the questions we get asked most often.
No, and no software developer can. Issuing cards and processing transactions requires licences and a connection to the card schemes. That is done by a licensed issuer. We build the software around it — application, rules, cardholder environment, reporting and integrations — on top of that issuer's API, and help you choose.
Based on what your programme needs: which rules can be set per card, whether transactions arrive in real time, whether virtual cards are possible, which countries are covered and what costs are involved. These differences are significant, and the choice determines what can be built in your software at all. We do this comparison before the design.
A virtual card exists only as a number and is available immediately, suitable for online spending and for one-off use with a fixed amount. A physical card is needed for in-person payments and at vending machines. Many programmes combine both, with the same rules underneath.
Up front with rules rather than afterwards with checks: limits per period, permitted categories, geographic and time-based restrictions. On top of that, alerts for unusual patterns and an audit trail of every change to a limit. Who is allowed to raise a limit matters at least as much as the limit itself.
Yes, and that is usually the biggest saving. Transactions arrive via webhooks, are enriched with cost centre and receipt, go through the approval you set up and then pass to your accounting system or ERP. That largely eliminates the after-the-fact expense claim process.
Cardholders can block their card instantly in the app, and the block takes effect with the issuer straight away. A replacement card can then be requested under the same rules. We build in temporary blocking and unblocking as standard, because it prevents a lot of unnecessary replacements for cards that were simply misplaced.
Your issuer sets strict requirements for how you handle card data. In practice, we design the system so that sensitive card data never passes through your own systems: the cardholder environment displays it via the issuer itself. This keeps the scope of your own security obligations limited.
Many issuers provide their own portal, and for a simple programme that works perfectly well. Custom software pays off when the rules or approvals are specific to your organisation, when you want an integration with your own accounting or HR systems, or when cardholders should see an environment in your own branding rather than the issuer's.
Ready to build your card programme?
Tell us who the cardholders are, which rules need to apply and how transactions should end up in your accounting. We are happy to help you think through scope, integrations and the first version. A no-obligation initial conversation gives you a clear picture of the possibilities and whether custom software makes sense in your situation.