Open Banking TTPs
Add Xace. Gain Serious Customers.
If you're an Open Banking provider or third-party app, Xace gives you instant credibility with high-value, hard-to-reach operators. Connect via Salt Edge, appear in more bank pickers, and power richer finance experiences—fast.
TTP capabilities
Everything an authorised provider needs
Xace handles the regulated plumbing — APIs, consent, SCA, and bank connectivity — so your team can focus on the product built on top.
AISP account data access
Read balances, transactions, and account metadata from 1,500+ banks with scoped, auditable consent tokens.
PISP payment initiation
Initiate bank-to-bank payments directly from customer accounts — no card rails, no chargebacks, instant settlement.
PSD2 & SCA compliance
Redirect, decoupled, and embedded SCA flows that meet RTS requirements across EU and UK jurisdictions.
Consent lifecycle management
Grant, renew, and revoke consent tokens per PSD2 requirements with full audit trail and per-purpose scoping.
Standardised API access
A single API surface for all connected banks — OBIE, Berlin Group, and national variants normalised to one schema.
Sandbox and certification
Full sandbox environment with simulated bank responses for development, QA, and pre-production certification.
Operating model
Four layers that power a regulated TTP
From data access to payment initiation — the full TTP operating surface, built on Xace infrastructure.
Read account data with consent and certainty
AISP access gives your service a real-time view of balances, transactions, and account ownership — scoped per customer, per consent grant, and per regulatory purpose.
Consent-scoped data reads
Every data pull is tied to a specific consent token — account ID, purpose, and expiry captured at grant time and enforced at the API layer.
Transaction history
Access 12+ months of transaction data from connected bank accounts with normalised categorisation across all connected banks.
Real-time balances
Current and available balances returned per-account at request time, with currency, timestamp, and freshness indicator.
Consent verification
Confirmation of Payee and consent checks at every step
Before any payment is initiated or account data is accessed, Xace verifies the payee account name against bank records and confirms the customer's consent token is valid, in-scope, and unexpired. No silent data access. No unverified payment initiation.
API surface
A single normalised API across 1,500+ banks
The Xace API abstracts OBIE, Berlin Group, and national PSD2 variants into a single, documented surface. Your integration handles one schema — we handle the bank-by-bank differences, error codes, and edge cases underneath.
Real-time events
Webhook streams for every TTP event in your flow
Consent grants, SCA completions, payment state changes, and bank-side errors — all streamed to your endpoints in real time. Build reactive, event-driven TTP services without polling or stale state.
Regulatory positioning
Infrastructure for TTPs at every stage of authorisation
Whether you are in sandbox development, pre-licensing testing, or live in production under a full AISP/PISP authorisation, Xace provides the bank connectivity layer that underpins your regulated service. We work with teams operating under their own licence, agents acting under an authorised TTP's umbrella, and white-label provider models.
For operators new to the TTP model, our team can advise on the operating structure that fits your jurisdiction, your use case, and your regulatory timeline — before a single line of code is written. For established TTPs, the integration is API-first and moves at your pace.
Infrastructure at scale
The numbers that matter to regulated providers
1,500+
Banks connected
99.9%
API uptime SLA
EU & UK
PSD2 jurisdictions
AISP + PISP
Dual authorisation support
TTP questions answered