Skip to main content

Receive Payments from Across Europe

When a payment arrives via CSM, Inventi notifies you in real-time through webhooks so you can credit your customer’s balance immediately.
What happens when a payment arrives:
  1. Payment comes through CSM to your customer’s IBAN
  2. Inventi validates and processes the incoming transfer
  3. Your webhook receiver gets notified instantly
  4. You credit your customer’s balance in your system

Supported Payment Types

SEPA Credit Transfer

Standard transfers with next business day settlement

SEPA Instant

Real-time payments settled in under 10 seconds

API Reference

Transaction Status Webhook

Receive notifications for incoming payments

Confirm Transaction

Accept or reject pending instant payments

Get Transaction

Retrieve full transaction details

Transaction Status History

View complete status timeline

Business Requirements

Use the Transaction Status Change webhook to create and update incoming transaction records in your system. This is the primary signal for all inbound payments.
Webhooks provide near real-time notifications. Use polling only as a fallback for reconciliation.
If your webhook endpoint fails, the platform retries until success and holds all subsequent notifications until the blocked one is delivered.
Your webhook receiver must respond with 2xx quickly. Process heavy work asynchronously using a queue.
When Instant Confirmation is enabled, incoming SEPA Instant transactions arrive as Pending confirmation. You must respond within 5 seconds after receiving the webhook.
Build an automated decision service. Manual review is not viable with a 5-second deadline.

How It Works

The platform sends webhook notifications as transactions progress through the payment lifecycle.

Webhook Payload

Each status change notification includes these fields:
integer
required
Unique transaction identifier
string
End-to-end reference from the originator
string
required
INBOUND for incoming payments
string
required
Current transaction status
integer
required
Amount in cents
string
required
Currency code (EUR)
string
Sender’s IBAN
string
Recipient’s IBAN
datetime
required
Status change timestamp

Transaction Statuses

Handle SEPA Instant Confirmation

When instant confirmation is enabled for your account, incoming SEPA Instant payments require your approval.

Confirmation Endpoint

You must respond within 5 seconds. The transaction must be in Pending confirmation status.

Decision Patterns

Auto-accept

Accept all payments automatically. Best for low-risk scenarios with trusted counterparties.

Rules-based

Apply amount limits, counterparty checks, and AML screening. Recommended for most use cases.

Manual review

Human approval required. Not viable due to 5-second time limit.

Integration Checklist

1

Implement webhook endpoint

Create an endpoint that responds with 2xx immediately and processes asynchronously
2

Handle idempotency

Upsert transactions by trx_id to safely handle duplicate deliveries
3

Process inbound direction

Filter for direction=INBOUND and update your ledger accordingly
4

Implement confirmation flow

If using instant confirmation, build a fast decision service that responds within 5 seconds
5

Maintain status history

Store all status transitions for audit and investigation purposes

What’s Next?

Your integration now handles both sending and receiving payments. Complete it with exception handling and reconciliation:

Return Payments

Return funds when you can’t credit the beneficiary

Handle Cancellations

Respond when originators request cancellation

Track and Reconcile

Monitor transactions and verify with Nostro statements
Last modified on July 10, 2026