Payment integration developer or payments engineer: which one do you need?

Victor Birjukov · 16 Oct 2026 · 8 min read

An integration developer connects your platform to PSPs, banks and schemes; a payments engineer owns the ledger, payment states and retries inside it.
Hire for the problem in front of you: a new partner or rail needs integration skills; duplicate or stuck payments need a payments engineer.
The instant payments deadline of 9 April 2027 for euro-area EMIs and payment institutions creates work for both roles.

Payment integration developer vs payments engineer: the titles sound alike, and job ads often mix them up. One connects your product to banks, PSPs and schemes; the other builds and runs the system that records and moves money inside your company. This guide explains the difference, when you need each and what to check before you hire.

What does a payment integration developer do?

A payment integration developer connects your platform to systems you do not control: payment service providers (PSPs), card processors, banks, SEPA and Open Banking APIs. The rules of the work come from someone else's specification: the partner's API documentation, its message formats and its test or certification process.

Typical tasks:

Building and testing a connection to a new PSP, acquirer or bank.
Mapping your data to the partner's messages and handling their responses and webhooks.
Updating an integration when a partner changes its API or message format.
Reading logs to find out why a partner rejected a payment.

Integration roles at PSPs show the same picture. PayU's integration engineer ad, for example, asks for hands-on experience with SOAP and REST APIs, knowledge of different payment flows, log analysis and the ability to explain technical issues to non-technical people.

With a clear scope, an integration is often a project with an end date.

What does a payments engineer do?

A payments engineer owns what happens to the money once it is inside your system. They build and maintain the ledger, the payment states (created, authorised, settled, refunded and so on), retries and idempotency, so that a payment is recorded once and moves once.

Idempotency is a good test of the difference. Stripe's API documentation explains that an idempotency key lets you repeat a request after a connection error without creating a second object or performing the update twice. An integration developer uses that feature when calling a PSP. A payments engineer designs your own system so the same is true inside it: a retried payment never pays out twice.

Payments engineer ads describe ongoing ownership. Monizze's ad, for example, includes keeping the payment authorisation system available and fast, acting as the technical contact for the PSP and terminal vendors, supporting audits and knowing payment technologies such as EMV, 3DS and tokenisation.

Where do the two roles overlap?

Both work with APIs, webhooks and failures. In a small team, one person often does both, and that can work for a while.

A simple way to draw the line:

The integration developer makes an external connection work to the partner's specification.
The payments engineer makes sure your own records stay correct whatever the partner sends back.

If your problems start at the edge (a partner rejects messages, a new rail needs connecting), you need integration skills. If they start in the middle (duplicate payments, stuck states, ledger and bank balances that do not match), you need a payments engineer.

Which one do you need first?

Match the hire to the problem in front of you:

Adding a PSP, card processor, bank or SEPA Instant → payment integration developer.
A partner is changing its API or message format → payment integration developer.
Building your own ledger or payment core → payments engineer.
Duplicate or missing payments traced to your code → payments engineer.
Payments are your core product and volume is growing → payments engineer, with integration help for each new partner.

Not every business needs a dedicated payments engineer. A guide on hiring for Paystack integrations makes the point that a developer who has built a few integrations is enough for a standard checkout, and that a payments engineer is needed when payments are the core product, volumes are high or the logic is complex. For an EMI, PI or PSP that holds its own licence, payments usually are the core product. Our pillar guide to building a payments team shows where both roles sit at each stage.

What rule changes create integration work in 2026 and 2027?

Some deadlines turn into integration projects whether you plan them or not:

Instant payments. Under Regulation (EU) 2024/886, EMIs and payment institutions located in a euro-area Member State must offer sending and receiving instant credit transfers in euro by 9 April 2027. The payee's PSP must make the funds available within 10 seconds of the payer's PSP receiving the order. The regulation also adds verification of the payee; check which date applies to your licence type.
SEPA Instant message rules. The European Payments Council's 2025 implementation guidelines for SEPA Instant Credit Transfer are based on the 2019 version of the ISO 20022 standard and took effect on 5 October 2025. The EPC also notes that the unstructured address format can no longer be provided in EPC payment messages from 15 November 2026.
Open Banking access. Under the PSD2 technical standards (Delegated Regulation (EU) 2018/389, Article 30), a bank or other account provider that offers online payment accounts must have at least one interface that lets account information and payment initiation providers identify themselves and communicate securely. If you connect to these interfaces, someone has to build and maintain the connection.

Each is mostly integration work, but each also touches the ledger, payment states and reconciliation, where a payments engineer comes in. This article describes the rules; it is not legal advice, so confirm what applies to you with your regulator and advisers.

What to check before you hire

Which rails and partners have they connected? Ask for names (SEPA, SEPA Instant, a specific PSP or card processor), not "familiar with".
Can they walk you through a failure? Ask about a rejected, duplicated or stuck payment they fixed, and how they found the cause.
For an integration developer: have they worked through a partner's test or certification process, and can they read a message specification such as ISO 20022?
For a payments engineer: how did they design the ledger, payment states and retries so that money moves once? How did they work with operations on reconciliation?
Production support: who watched the logs, who was called at night, and what changed after an incident?
A short practical task. A small mapping exercise for an integration developer, or a retry-and-ledger problem for a payments engineer, tells you more than another interview.
Ownership after the project: if an integration developer builds a connection, who maintains it when the partner changes something?

For the wider role list, see how to hire a payments specialist.

Hire, contract or fixed-price task?

The two roles often suit different ways of working.

Payment integration developer: a new connection with a clear scope works well as a fixed-price task. On AfterWorc, fixed-price tasks carry a fee of 5–8%, and funds are held until you accept the work.
Payments engineer: ledger and core ownership is ongoing work, so it usually suits a hire. Through AfterWorc, the price is the specialist's salary plus employer taxes plus a 10% AfterWorc margin.

AfterWorc interviews every specialist by video and gives them a practical test before you see them. You can start hiring on AfterWorc with a short description of the role.

FAQ

Is a payment integration developer the same as a payments engineer? No. The integration developer connects your system to outside partners such as PSPs, banks and schemes. The payments engineer builds and owns the internal system that records and moves money, such as the ledger, payment states and retries.

Can one person do both jobs? In a small team, often yes, and that can work while volumes are low. When integrations multiply or ledger problems appear, split the work so each part has a clear owner.

Do I need a payments engineer if I only use one PSP? Not always. If you run a standard checkout through one provider, a developer with integration experience may be enough. If payments are your core product, or you build your own ledger, plan for a payments engineer.

Does SEPA Instant need an integration developer or a payments engineer? Usually both. Connecting to the rail and its ISO 20022 messages is integration work. Making sure your ledger, payment states and reconciliation cope with transfers that complete within seconds, at any hour, is payments engineering.

Sources

Not sure whether you need an integration developer or a payments engineer? Tell us the role and get three matching profiles. Start hiring on AfterWorc. The first 10 business clients get €190 off their first hire and a free technical assessment.