Integra provides the platform. The PSP adapts the local connectivity.

The integration framework is the set of APIs, webhooks, interfaces, data structures, events and open points the PSP uses to connect Integra to its country’s financial infrastructure. It is the part of the platform designed for the PSP to extend.

What the framework includes.

APIs

Programmatic access to every module, with the same model of identifiers, states and errors.

Webhooks

Signed events to the PSP’s and its customers’ systems, and to the local adaptation layer.

Integration points

Defined contracts where the platform hands over an approved operation and expects a result: where each rail adapter lives.

Interfaces

Operating screens that show the state reported by the adapters, with no extra development.

Data structures

Instruction, beneficiary, account, result, statement: common types the adapter translates into the rail’s format.

Events

Catalogue of lifecycle events the adapter consumes and produces.

Communication mechanisms

Synchronous calls for submission and query; asynchronous delivery of results; file and statement import.

Documentation

Contract reference, adaptation guides and a test environment for the PSP’s team.

The journey of an operation through the framework.

Instruction
A PSP customer creates an operation via interface, file or API. Integra validates it and takes it through the configured workflow.
Integration point
Once approved, Integra hands the operation to the adapter of the indicated rail using the common data structure.
Local adaptation
The adapter, built by the PSP, translates the instruction into the bank’s, network’s or provider’s format and sends it through the corresponding channel.
Result
The adapter reports the result (reference, confirmation, rejection, return). Integra updates the transaction and emits the event.
Reconciliation
The adapter imports statements or provider reports; Integra reconciles against what was executed and exposes differences.

An adapter’s contract.

An adapter implements a small, explicit contract. Everything rail-specific (authentication, formats, response codes, windows, files) lives inside the adapter and belongs to the PSP.

Submit an instruction and receive an acknowledgement.
Query the state of a reference.
Import a statement or report for reconciliation.
Declare capabilities: currencies, schedules, limits, account types.

Integration point: rail adapter contractIllustrative · conceptual

// Lo que el PSP implementa para conectar un riel de su mercado.
// Conceptual: nombres y firmas se entregan en la documentación.
interface RailAdapter {
  readonly id: "psp-local:bank-transfer";
  submit(tx: TransactionInstruction): Promise<Acknowledgement>;
  status(ref: RailReference): Promise<RailState>;
  importStatement(file: Statement): Promise<StatementLines>;
}

// Integra llama a submit() cuando la operación queda aprobada
// y actualiza la transacción con lo que el adaptador reporta.

Event: transaction confirmedIllustrative · event

POST https://psp.example/webhooks/integra
X-Integra-Signature: t=1758037331,v1=6d1f…

{
  "id": "evt_01J9K5",
  "type": "transaction.confirmed",
  "data": {
    "transaction_id": "txn_01J9K4",
    "operation_id": "op_01J9K3Q8X2",
    "rail": "psp-local:bank-transfer",
    "rail_reference": "…",
    "amount": 1850000, "currency": "COP"
  }
}

What "local adaptation" means.

Local adaptation is the PSP’s work: developing or adapting the connection to the entities in its market and maintaining it. Integra does not perform it and does not claim connectivity to any specific rail unless a developed, confirmed integration exists.

Banks

Networks and payment systems

Clearing houses

Financial providers

National systems

Local infrastructure

Extensibility beyond the rails.

Workflows

Validation and approval rules per operation type and per customer.

File layouts

Input and response formats defined per customer.

Reconciliation rules

Matching criteria and tolerances per account and per provider.

Event catalogue

Subscriptions and destinations per event type, customer and environment.

Fields and metadata

Additional attributes on customers, operations and transactions for the PSP’s business.

Build 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.

Request a demo See the architecture