Make processing fit your payment business.
Choose the transaction route around your acquiring relationships. Connect the payment SDK directly to an existing bank processor, or define a switch-based route with an acquiring partner.
- Your customer experience
A purchase within your payment application.
- Connected processing
The transaction layer behind the experience.
- Your operating systems
Payment results available to your business.
A connected payment and operational flow.
More control over the transaction layer.
Connect your existing systems
Bring terminal payment flows and backend systems together through defined interfaces.
Shape transaction routing
Configure how payments reach the acquiring connections in your programme.
Use the data behind the payment
Bring transaction results and message data into your operational and reporting workflows.
Two payment routes. Shared terminal operations.
The bank-host route and the switch-based route are separate delivery models. Choose the integration that fits your existing environment.
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 integrationA component you can connect to your product.
Build a new offering
Combine processing with Acceptance and the device environment your customers need.
Develop existing infrastructure
Map the processing component to your current systems and identify the integrations needed for a staged change.
For your technical team.
The processing layer uses ISO 8583 message switching. Your technical team can review transaction interfaces, message handling, routing configuration and integration requirements with us.
Connect processing to your business.
Tell us what you are building and the integration you have in mind.