tuum.
Newsroom · April 2026
Prisma Goes Live on Tuum's Modular Core, Establishing a New Standard for European Payment Institutions
Prisma (PRISMA PAYMENTS EP, S.A.), a regulated payment institution licensed by the Bank of Spain, has successfully gone live on Tuum's next-generation core banking platform. This strategic implementation represents Prisma's move towards a modern, full SaaS stack, designed to enhance scalability and support its continued global expansion as the business grows.
Prisma specializes in providing robust payment and account services to companies worldwide that rely on complex payment flows and strict regulatory compliance. By migrating to Tuum, Prisma has deployed a comprehensive end-to-end capability specifically tailored for EMIs and PSPs.
The successful go-live delivers several key strategic advantages:
- Direct Connectivity & Efficiency: Tuum provides direct integrations with SWIFT, SEPA, and CentroLINK, completely removing the need for third-party middleware.
- Regulatory Confidence: Tuum's resilient architecture combined with a pre-built integration to Hawk for AML compliance strengthens Prisma's ability to operate in a heavily regulated EU landscape, supporting readiness for DORA and ISO standards.
- A Shift to Intentional Expansion: By offloading the burden of maintaining legacy infrastructure, Prisma has improved its unit economics and can now shift its focus from defensive maintenance to intentional, sustainable expansion.
"To support our global growth ambitions, we identified the need to evolve our core capabilities. Tuum's modular platform represents a natural next step, enhancing our architecture with the agility required to handle complex payment flows and adapt quickly to regulatory change."
Jose Carbajosa, CEO at Prisma
⚠ Title announces Tuum's achievement, not Prisma's problem solved — "Establishing a New Standard for European Payment Institutions" is Tuum's claim. The reader's question is: what did Prisma actually escape from, and what does that mean for institutions like mine?
⚠ The most operationally valuable sentence is the third bullet — "shift from defensive maintenance to intentional, sustainable expansion" is the entire business case for core migration. It appears after two bullets of technical feature listing, not in the hook.
⚠ No numbers in the hook — SWIFT, SEPA, and CentroLINK direct (zero middleware) is a concrete operational advantage. It appears as a bullet point, not as a headline stat. "Zero middleware" is a number worth surfacing.
⚠ DORA and ISO compliance mentioned as a parenthetical — for European payment institutions, DORA compliance is a regulatory deadline, not a feature. It appears inside a bullet point as context rather than as urgency.
⚠ CEO quote buried mid-post — Jose Carbajosa's quote contains the most human signal in the piece ("handle complex payment flows and adapt quickly to regulatory change") but appears after the technical bullets, not before them.
⚠ CTA "Get in touch" is completely disconnected — there is no bridge between reading about Prisma's migration and being asked to contact Tuum. The CTA does not name what Tuum solves for the EMI or PSP reading this.
tuum.
Customer Story · April 2026
Customer Story · Fintech · EU Payments · April 2026
Prisma was maintaining legacy infrastructure. Now they're expanding intentionally.
Prisma is a Bank of Spain-regulated payment institution serving complex global payment flows. After migrating to Tuum's modular core, they eliminated third-party middleware entirely, gained pre-built DORA and AML compliance, and shifted engineering focus from keeping legacy alive to building what's next. This is what that migration delivered — and what it means for European EMIs still on legacy stacks.
0
third-party middleware — SWIFT, SEPA, CentroLINK all direct
Hawk
AML compliance pre-built, not bolted on post-migration
DORA
and ISO readiness built into the architecture from day one
0
failed implementations across all Tuum go-lives to date
The problem Prisma solved
Defensive maintenance was absorbing the engineering capacity that should be building growth.
Prisma's legacy infrastructure required constant maintenance to stay operational — not to improve. Every engineering hour spent keeping legacy alive was an hour not spent on new payment products, new markets, or new customer value. The migration to Tuum was not a technology upgrade. It was a reallocation of the entire organization's capacity from maintenance to expansion. That shift in unit economics is the real business case — not the feature list.
"We're now operating on a core that supports intentional, sustainable expansion."
Jose Carbajosa, CEO at Prisma
What the architecture change actually means
Zero middleware. Direct rails. Compliance built in, not integrated after.
The operational difference between third-party middleware and direct SWIFT, SEPA, and CentroLINK connectivity is not marginal — it removes an entire layer of failure surface, latency, and vendor dependency from every payment processed. Hawk AML is pre-built into the Tuum architecture, not a post-migration integration. DORA and ISO readiness are structural, not a compliance layer added on top. For European payment institutions, these are not feature additions — they are the difference between a stack that grows with regulatory change and one that fights it.
What this means if you're still on legacy
The question is not whether to migrate. It is how much defensive maintenance you can still afford.
Every quarter on a legacy core is another quarter of engineering capacity allocated to maintenance instead of growth. Tuum's progressive modernization model means you do not switch off legacy until the new core is proven — Prisma went live in weeks, not years. If your institution is processing complex payment flows across multiple currencies and jurisdictions, the architecture Prisma now runs on is available today.
❌ Before
Title: Prisma Goes Live on Tuum's Modular Core, Establishing a New Standard for European Payment Institutions
Announces Tuum's milestone. An EMI reading this has one question: what did Prisma actually escape from, and is my situation the same?
✅ After
Title: Prisma stopped maintaining legacy infrastructure and started expanding. Here is what the migration to Tuum actually changed.
Names the before state ("maintaining legacy") and the after state ("expanding") in one sentence. Any EMI on a legacy stack recognises their situation immediately.
The 6 upgrades — and why they work
1 · Title rebuilt from vendor achievement to customer transformation
The original title announces what Tuum did. The rebuild announces what Prisma changed — and frames it in the language every EMI on a legacy stack uses internally: "we're spending too much time maintaining what we have." The reader recognises their own situation before they have read a single technical detail.
2 · "Shift from defensive maintenance to intentional expansion" moved from bullet 3 to hook
The original buries the business case in the third bullet. The rebuild opens with it. "Defensive maintenance was absorbing the engineering capacity that should be building growth" is the operational consequence that makes the migration decision legible to any CTO or CPO reading this announcement. It belongs in the first paragraph, not the third point in a list.
3 · Zero middleware surfaced as a stat card, not a feature bullet
Direct SWIFT, SEPA, and CentroLINK connectivity without third-party middleware is the single most concrete operational advantage in the announcement. In the original it appears as a bullet point. The rebuild makes it the first stat card above the fold — "0 third-party middleware" is a number that immediately communicates the architecture shift without requiring the reader to process a paragraph of explanation.
4 · DORA compliance reframed from parenthetical to urgency signal
The original mentions DORA inside a bullet point as a capability. For European payment institutions, DORA is a regulatory obligation with enforcement consequences — not a feature. The rebuild surfaces it as a dedicated stat card and names it directly: "DORA and ISO readiness built into the architecture from day one." An EMI reading this understands immediately that DORA readiness is structural, not a separate project.
5 · CEO quote moved to the front of the business case section
Jose Carbajosa's quote — "we're now operating on a core that supports intentional, sustainable expansion" — is the most human signal in the announcement. It confirms the transformation in the voice of the person who lived it. In the original it appears at the bottom of the post. The rebuild places it immediately after the explanation of what the migration achieved, where it functions as proof rather than decoration.
6 · CTA rebuilt around the reader's migration decision
"Get in touch" in the original has no logical link to what was just read. The rebuild closes with "See how Tuum handles your migration" — a direct consequence of reading about an institution that successfully migrated off legacy in weeks. The reader who finished this announcement and is still on a legacy core knows exactly what the CTA is offering and why now is the relevant moment to click it.
This is the Strategic Flow method
Customer's transformation before vendor's achievement. The business consequence leads, not the feature list. Compliance deadlines as urgency anchors, not capabilities. Every section answers the reader's silent question — "is my situation the same, and what would change if I made this move?" — before asking them to act. Visit strategicflow.carrd.co to get started.
Failure patterns identified in this teardown
Filing Label Subject · Feature-First Bias · Missing Hierarchy · Consequence-After-Caveat · Zero Social Proof · Generic Urgency Theatre
Filing Label Subject · Feature-First Bias · Missing Hierarchy · Consequence-After-Caveat · Zero Social Proof · Generic Urgency Theatre