The software your PSP runs on.
Integra is the platform a payment service provider uses to manage customers, accounts, operations and transactions, process files, reconcile and report. You connect your market’s rails. The core is already built.
For PSPs, fintechs, payment operators and financial platforms that want to operate without building their software from scratch.
One distinction shapes this whole site.
Integra is not a PSP and does not connect to the world’s rails. Integra is the software; local connectivity belongs to the PSP.
INTEGRA PROVIDES
Integra
- The platform core
- Operating and administration interfaces
- APIs and webhooks
- Customer, account, operation and transaction management
- Files, reconciliation, reporting and audit
- The integration points to connect rails
THE PSP DEVELOPS OR ADAPTS
PSP
- The connection to its country’s banks
- The payment systems and networks of its market
- Clearing houses and providers
- The formats and rules of each rail
- Its regulatory and commercial relationship with those entities
Everything a PSP needs to operate, in modules that share one model.
A single data model: the same customers, identifiers and states in every module.
| Operation | Customer | State |
|---|---|---|
| op_01J9K3 | Nómina Andina S.A.S. | Validated |
| op_01J9K1 | Mercado Central | Confirmed |
| op_01J9JX | Logística del Norte | Approval 1/2 |
| op_01J9JT | Fondo Verde | Processing |
| op_01J9JQ | Cooperativa Sur | Confirmed |
Operating interface: the same information the APIs expose, for the team that runs the PSP.
Customer Management
Customers, users, profiles and the configuration of every commercial relationship of the PSP.
View moduleOperations
Workflows, states, approvals and monitoring of everything the PSP executes.
View moduleTransactions
Creation, processing, states, traceability and history of every transaction.
View moduleAccounts
Administration of accounts, balances, movements and the relationships between them.
View moduleFile Management
Upload, validation and processing of batch files, with results per record.
View moduleReconciliation
Movement identification, differences and reconciliation states.
View moduleReporting
Queries, operational and financial reports, and export.
View moduleAPIs
Integration, automation and communication with the PSP’s and its customers’ systems.
View moduleWebhooks
Events, notifications and state changes delivered to the systems that need them.
View moduleAudit Trail
Traceability, history and control of every action on the platform.
View moduleThe integration framework: how the PSP connects its rails.
Integra delivers APIs, webhooks, interfaces, data structures, events and open integration points. With them, the PSP builds the layer that connects the platform to its market’s financial infrastructure.
One core. Local rails.
The same platform serves PSPs in different countries, not because Integra knows every rail, but because the core is common and the integration layer is adaptable.
ONE CORE
Integra
- Customers and users
- Operations and transactions
- Files and reconciliation
- APIs, webhooks, audit
LOCAL ADAPTATION
The PSP’s layer
- Adapters per rail
- Local formats and validations
- Its own credentials and contracts
LOCAL RAILS
The country’s infrastructure
- Banks
- Payment systems and networks
- Clearing houses and providers
Conceptual example
Colombia
A Colombian PSP adapts the platform to its banks and to the local rails it uses.
Argentina
An Argentine PSP uses the same core and connects its market’s financial infrastructure.
Another country
Same core, new local adaptation. The software does not change; connectivity does.
Build a PSP from scratch, or build only what differentiates you.
What a PSP would have to develop and maintain versus what it gets with Integra.
Build everything
Before processing its first payment, the PSP would have to build and maintain:
- Customer and user management
- Interfaces and dashboards
- Transaction and state management
- Operations and workflows
- File upload and processing
- APIs and webhooks
- Reporting
- Reconciliation
- Audit trail
- All the operating infrastructure
Plus the technical adaptation to its local rails.
With Integra
The PSP gets all of that as a platform, already built and maintained:
- Customer and user management
- Interfaces and dashboards
- Transaction and state management
- Operations and workflows
- File upload and processing
- APIs and webhooks
- Reporting
- Reconciliation
- Audit trail
- All the operating infrastructure
AND DEVELOPS OR ADAPTS ONLY
The connectivity specific to its marketThe PSP’s engineering concentrates on what differentiates it: its rails, its product and its customers.
Two readings of the same platform.
IF YOU RUN THE BUSINESS
Speed, focus and a platform that grows with you.
- Problem: building a PSP’s software takes years and does not differentiate.
- Solution: operate on a complete platform and build only the connectivity.
- Speed: time to launch is measured in adaptation, not construction.
- Scale: the same modules serve the first customer and the volume of a mature operation.
- Expansion: a new country is a new local adaptation, not a new platform.
IF YOU RUN THE TECHNOLOGY
A core with clear contracts and open integration points.
- Architecture: modules over a common data model; explicit states across the platform.
- APIs and webhooks: REST with JSON, idempotency, signed events with retries.
- Integration framework: adapter contracts to connect every rail in your market.
- Extensibility: configurable workflows, file layouts and reconciliation rules.
- Security and observability: role-based permissions, immutable audit, end-to-end traceability.
Built as critical-infrastructure software.
What the platform guarantees by design. No certifications, figures or customers we cannot stand behind.
Security
Encryption in transit and at rest, scoped credentials, role-based permissions and segregation of duties.
Traceability
Every transaction keeps its instruction, its validations, the rail result and its reconciliation.
Auditability
Immutable log of human and system actions, with before and after for every change.
Control
Approval workflows, limits per customer and per operation, explicit rules.
Scalability
Asynchronous processing per event and per batch; per-record validation so one error does not stop the rest.
Resilience
Idempotency on every write, controlled retries and states that can always be rebuilt.
Observability
Metrics, logs and states queryable via interface and API, to operate on information rather than assumptions.
For engineering teams that will integrate and adapt.
A consistent API for every module, signed events and documented integration contracts for the local layer.
- One model for everything. Customers, operations, transactions and accounts share identifiers, states and errors.
- Safe writes. Key-based idempotency: retrying never duplicates an operation.
- Events, not polling. Every state change arrives signed at your system or your local adapter.
- Separate environments. Test and production with the same routes and independent credentials.
POST /v1/operations
Authorization: Bearer sk_test_••••••••
Idempotency-Key: cust-7781-payroll-2026-09
{
"customer_id": "cus_01J9K2",
"type": "payout",
"currency": "COP",
"items": [
{ "beneficiary": { "id_type": "CC", "id": "1020304050" },
"destination": { "rail": "psp-local:bank-transfer", "account": "4581••••••" },
"amount": 1850000, "reference": "Servicios septiembre" }
],
"workflow": "two-step-approval"
} Who Integra is for.
Teams that operate payments as a business, or are about to.
PSPs
Run your PSP on a complete platform and dedicate your engineering to your market’s connectivity.
View solutionFintechs
Turn a payments operation into a payments business with the platform already solved.
View solutionPayment operators
Modernize an operating payments platform without stopping the business.
View solutionFinancial platforms
Embed a payment operations layer inside a broader financial platform.
View solutionBuild and operate your PSP on Integra.
Tell us what you operate today and which rails you need to connect. We will show you the platform on your case.