How would you measure the success of Deutsche Bank's real-time payments API built with Serrala for corporate treasuries?

Introduction

Deutsche Bank and Serrala, a treasury and payments software provider, launched what they described as the first API solution for real-time payments built on the SEPA Instant scheme, connecting a treasury system directly to the bank. Instead of uploading payment files in batches and waiting for bank statements, a treasurer can send an instant payment from inside the treasury software and receive confirmation within seconds. The prompt asks how we would measure the success of this real-time payments API. I'll set the product context, define goals, propose a North Star metric and support it with supporting, guardrail, trade-off and counter metrics.

Step 1

Product Context

Corporate payments in Europe historically flow in batches: the ERP or treasury management system (TMS) creates a payment file, it is uploaded through a host-to-host channel or EBICS (common in Germany), the bank processes it in cycles, and status comes back hours later. SEPA Instant changed the rails: euro transfers settle in under ten seconds, 24/7. The EU Instant Payments Regulation now requires euro-area banks to offer instant payments at no more than the price of standard transfers.

The Deutsche Bank and Serrala API connects these rails to the treasury desk:

• The treasurer or an automated rule triggers a payment in Serrala's software.
• The API sends the instruction to Deutsche Bank in real time.
• Deutsche Bank validates, screens and executes via SEPA Instant.
• Status (accepted, rejected, settled) returns in seconds and updates the treasury position.

Key stakeholders:

• Corporate treasurers and payments teams: Want certainty and control.
• Serrala: Wants its software to offer differentiated bank connectivity.
• Deutsche Bank: Wants to win payment flows, operating balances and a modern "API-first" reputation.
• Beneficiaries (suppliers, employees): Receive money instantly.

Product lifecycle stage: Introduction. Early adopters are piloting; the product needs evidence that it delivers value before scaling to other TMS partners.

Software-specific context:

• Integration: REST APIs, OAuth-based security, ISO 20022 message structures.
• Use cases: Urgent supplier payments, payroll corrections, intraday liquidity transfers between group entities, refunds.