Collect Payments Automatically

SEPA Direct Debit lets you pull funds directly from customer accounts - ideal for subscriptions, recurring billing, and scheduled collections. Inventi routes your direct debits through CSM to reach accounts across Europe.

What happens when you collect a payment:

You submit a direct debit request via API with a valid mandate
Inventi validates and forwards to CSM
The debtor’s bank processes the collection
You receive status updates via webhooks

Supported Schemes

SDD Core

Consumer direct debits with extended refund rights (8 weeks unconditional, 13 months for unauthorized)

API Reference

Create SDD Payment

Initiate a direct debit collection

Cancel SDD Payment

Recall an accepted collection before settlement

Return SDD Payment

Return a settled collection that debited your account

Reverse SDD Payment

Reverse after settlement

Business Requirements

Valid mandate is required

Every direct debit must reference a valid SEPA mandate signed by the debtor. Store mandate details including:

Mandate reference (unique identifier)
Signing date
Debtor name and IBAN
Sequence type (FRST, RCUR, OOFF, FNAL)

Collections without valid mandates will be rejected or returned by the debtor’s bank.

Respect collection timing

You choose the settlement date when creating the collection:

Settlement date must be at least the next business day (submit by 11:30 EEST for next-day settlement) and at most 14 calendar days ahead

Submissions past the cutoff for the chosen settlement date are rejected - resubmit with a later settlement date.

Handle refunds and returns

Debtors can dispute direct debits:

Core scheme: 8 weeks unconditional refund right, 13 months for unauthorized debits

Build automated handling for returns and refunds to update your billing system promptly.

Use idempotency for collections

Always send an Idempotency-Key header when creating direct debits. If your request times out, retry with the same key to prevent duplicate collections.

Duplicate direct debits can result in customer complaints and chargebacks.

Transaction Lifecycle

Transaction Statuses

Collection Flow
Error States

Status	Description	Timing
`Created`	Direct debit initiated	Immediate
`To sign`	Awaiting approval (if configured)	Until signed
`Signed`	Approved, queued for clearing	Until sent to clearing
`Sent to clear`	Delivered to CSM for processing	Same business day as submission
`Accepted`	Accepted by the CSM	From acceptance until settlement date
`Completed`	Funds collected	On settlement date

Status	Description
`Cancelled`	Cancelled before sending, or recalled while Accepted - possible until 11:30 EEST on settlement day
`Rejected`	Rejected by the CSM or the debtor’s bank - possible from submission until the settlement-day cutoff

Create a Direct Debit

curl -X POST https://api.pgw-sandbox.finventi.com/v1/createSepaDDPayment \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: {uuid}" \
  -d '{
    "amount": 4999,
    "currencyIsoCode": "EUR",
    "settlementDate": "2024-01-22",
    "sequenceType": "RCUR",
    "creditor": {
      "id": "LT11ZZZ123456789",
      "iban": "LT543210010000000003",
      "name": "Your Company"
    },
    "debtor": {
      "iban": "DE89370400440532013000",
      "name": "Customer Name"
    },
    "mandateInformation": {
      "id": "MNDT-2024-001",
      "dateOfSignature": "2024-01-15"
    },
    "purpose": {
      "unstructured": "Monthly subscription - January 2024"
    }
  }'

{
  "result": {
    "id": 12345,
    "amount": 4999,
    "currencyIsoCode": "EUR",
    "settlementDate": "2024-01-22",
    "sequenceType": "RCUR",
    "endToEndId": "...",
    "creditor": { "..." : "..." },
    "debtor": { "..." : "..." },
    "mandateInformation": { "..." : "..." }
  }
}

Request Fields

integer

required

Amount in minor currency units (cents)

string

required

Currency code - must be EUR

string

required

Collection date (YYYY-MM-DD) - at least the next business day (11:30 EEST cutoff), at most 14 calendar days ahead

string

required

FRST (first), RCUR (recurring), OOFF (one-off), FNAL (final)

string

required

Your SEPA Creditor Identifier (CI) - must match the mandate. See Create SDD payment for details

string

Collection account IBAN that receives the funds

string

Creditor name (max 70 characters)

string

required

Debtor’s IBAN to debit

string

required

Debtor’s name as on the mandate (max 70 characters)

string

Optional - the debtor’s bank is derived from the IBAN

string

required

Mandate reference (max 35 characters) - must match the signed mandate

string

required

Mandate signing date (YYYY-MM-DD)

string

Payment description shown to debtor (max 140 characters)

string

Name of the party the collection is ultimately for, when you collect on behalf of another party (max 70 characters)

string

Your transaction identifier (max 35 characters)

Handle Returns and Reversals

Return / Refund (Post-Settlement)
Reversal (Post-Settlement)

Return a settled direct debit that debited your account - operational returns within 5 business days after settlement, customer refunds via MD06 (8 weeks) or MD01 (13 months).

curl -X POST https://api.pgw-sandbox.finventi.com/v1/transactions/{id}:return \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "AM04",
    "additionalInfo": "Insufficient funds"
  }'

Common return reasons:

Code	Description
`AM04`	Insufficient funds
`AC04`	Closed account
`MD01`	Unauthorized transaction / no valid mandate - refund right up to 13 months
`MS02`	Not specified reason (customer generated)

Reverse a completed direct debit when funds need to be returned after settlement.

curl -X POST https://api.pgw-sandbox.finventi.com/v1/transactions/sdd/{id}:reverse \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "Customer dispute",
    "amount": 4999
  }'

A reversal creates a new linked transaction returning the funds to the debtor - the original collection stays Completed. Ensure sufficient balance in your account.

Collection Flow

Webhook Integration

Each status transition triggers a webhook notification:

string

required

Transaction identifier

string

required

INBOUND for collections you initiated (direction follows the funds); OUTBOUND when your account is being debited

string

required

Current transaction status

integer

required

Amount in cents

Data Model

Store these fields for complete tracking:

string

required

Platform transaction ID (primary key)

string

required

Reference to customer mandate

string

required

FRST, RCUR, OOFF, or FNAL

string

required

Your generated key for retry safety

string

required

Latest transaction status

string

Reason code if returned

Integration Checklist

Implement mandate management

Store valid mandates with references, dates, and sequence tracking

Use idempotency

Generate and persist an Idempotency-Key for each collection

Submit with correct timing

Choose a settlement date from next business day (11:30 EEST cutoff) up to 14 calendar days ahead

Handle returns and reversals

Build automated processing for failed collections and customer disputes

Track sequence types

Update sequence type from FRST to RCUR after first successful collection

Implement webhook receiver

Process status updates to keep your billing system synchronized

What’s Next?

Send SEPA Payments

Send outbound credit transfers

Track and Reconcile

Monitor transactions and reconcile with statements

Getting Started

Integration Guide

Account Management

SEPA Instant/SCT

SEPA Direct Debit

SWIFT Payments

Payment Information

Investigations (Preview)

Nostro Accounts

Bank Information

Webhooks

Collect with Direct Debit

Collect Payments Automatically

Supported Schemes

SDD Core

API Reference

Create SDD Payment

Cancel SDD Payment

Return SDD Payment

Reverse SDD Payment

Business Requirements

Transaction Lifecycle

Transaction Statuses

Create a Direct Debit

Request Fields

Handle Returns and Reversals

Collection Flow

Webhook Integration

Data Model

Integration Checklist

What’s Next?

Send SEPA Payments

Track and Reconcile

​Collect Payments Automatically

​Supported Schemes

SDD Core

​API Reference

Create SDD Payment

Cancel SDD Payment

Return SDD Payment

Reverse SDD Payment

​Business Requirements

​Transaction Lifecycle

​Transaction Statuses

​Create a Direct Debit

​Request Fields

​Handle Returns and Reversals

​Collection Flow

​Webhook Integration

​Data Model

​Integration Checklist

​What’s Next?

Send SEPA Payments

Track and Reconcile

Collect Payments Automatically

Supported Schemes

API Reference

Business Requirements

Transaction Lifecycle

Transaction Statuses

Create a Direct Debit

Request Fields

Handle Returns and Reversals

Collection Flow

Webhook Integration

Data Model

Integration Checklist

What’s Next?