Payments and POS integration

Yes, where the acquirer or processor offers it. ISO 8583 is a framework rather than one format: each acquirer publishes its own specification of fields, message types and network management. We build from that specification, handle authorisations, reversals and advice messages, and test every response code. Where a gateway offers a modern API in front of the acquirer, we often recommend that instead.

We cannot remove PCI DSS, but we can reduce how much of your estate it applies to. We use hosted payment pages, point-to-point encryption at the terminal and tokens from the gateway, so card numbers never reach your POS, ERP or data warehouse. We document the data flows so your assessor can see which systems handle card data and which do not.

We integrate EMV chip and contactless terminals through the protocol their provider supplies, usually a local or cloud API between the POS and the terminal. The terminal and its payment application are certified by the provider, so we integrate with them rather than change them. We confirm the exact models and protocols with you and the provider at the start.

The store keeps selling. Sales are stored locally on the POS or store server and sent to the ERP when the connection returns, each with a unique identifier so nothing is posted twice. Whether card payments can continue offline depends on your acquirer’s rules and your risk appetite, and we design that with you.

It is set largely by the gateway or acquirer: their test windows, the number of test cases and how many rounds it takes. We prepare the test scripts and evidence before the window opens, which shortens the rounds, and we plan the rest of the work around the provider’s calendar. We share that plan once the provider confirms its process.

The number of providers, terminal types and sales channels, whether the acquirer uses ISO 8583 or an API, the certification steps each provider requires, and the number of stores to roll out. Settlement and reconciliation rules add effort when fees and payouts are complex. We estimate per provider and per flow after the mapping step.

Yes. Refunds and reversals are part of the payment flows we build. For chargebacks, we import the acquirer’s dispute reports, link each one to the original sale and settlement, and give your team a list to work through with the evidence attached. How each dispute is answered stays your decision.

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom code, documentation and other deliverables made for you. Anything we bring that existed before, such as internal tools or libraries, stays ours, and you receive a licence to use it in your systems. Open-source components keep their own licences, and we list them for you.