Build the integration around your product.
Work with the Payment SDK, terminal application and processing interfaces to connect your software to in-person payments.
- Your software
POS application or partner system.
- Integration boundary
Payment SDK and agreed processing interfaces.
- ESCUDIX platform
Terminal experience and connected operations.
Schematic platform view.
Choose your starting point.
Payment SDK
Work with payments, refunds, cancellations, progress and results inside your own application.
Terminal application
Connect the payment interface to receipts, device capabilities and commerce extensions.
Processing integration
Exchange transaction messages and map response data into your systems.
Terminal operations
Manage configuration profiles, software delivery, device status and diagnostics through TMS.
API / MCP
Platform access for onboarding and product configuration.
API
Integrate onboarding and product configuration into your own systems.
MCP
Connect AI assistants to onboarding and configuration workflows.
Understand the integration boundaries.
Payment exchange and terminal operations connect to different parts of your product.
Direct to your bank processor
For banks retaining their processing host, the payment SDK connects directly to that environment.
- Your branded application
The merchant-facing payment experience.
- Payment SDK
Connects the terminal payment flow to the agreed bank host.
- Existing bank processor
Handles authorisations within the bank’s processing environment.
A direct deployment does not require an ESCUDIX switch in the authorisation path.
Through the payment switch
An alternative delivery model connects the payment application to an agreed acquiring partner through the switch.
- Payment app / SDK
Starts the payment and presents its progress and result.
- Payment switch
Exchanges transaction messages with the acquiring connection.
- Acquiring connection
The endpoint configured for your payment programme.
Connector availability, security requirements and production approvals are defined for the deployment.
The operations path
Device configuration, software and keys support the terminal throughout its lifecycle.
- Operations team
Controls the setup and software for the terminal fleet.
- TMS / RKL
Distributes configurations, applications and payment keys.
- Terminal estate
Receives the configuration and software needed to run.
Interfaces for partner and client onboarding and product configuration from your own backend or AI tools.
Explore developer integrationBring your integration context.
Your application
The customer workflow, interface and backend systems.
Your environment
Target devices and the acquiring connection for the deployment.
Your operating model
Who manages onboarding, configuration, updates and support.
Let’s map the technical fit.
Tell us what you are building and the integration you have in mind.