Skip to main content
POST
Create payment

Overview

This endpoint creates SEPA Direct Debit payments for collecting funds from customer accounts. The payment is validated and submitted to the clearing system for processing.

Settlement Date

The settlementDate is the exact day the debtor is charged - the collection settles on that day. You choose it when creating the payment. You choose settlement date when creating the payment, and collection cannot be the same day you submit the request. It must be at least the next business day (Submissions accepted up to 11:30AM EEST if settlement day is set for tomorrow) and no more than 14 calendar days ahead.

Mandate

mandateInformation carries the reference data for the direct-debit mandate agreed between the creditor and the debtor. Holding a valid mandate is the creditor’s responsibility - Inventi does not verify it.

Creditor Identifier

creditor.id carries the SEPA Creditor Identifier (CI) - the scheme-wide identifier of the party collecting the funds. Together with the mandate reference (mandateInformation.id) it uniquely identifies the mandate: the debtor’s bank uses this pair to match every collection against the signed mandate, so both values must match the mandate exactly. Collections with an incorrect CI are returned with reason code BE05 (originator not identified) or MD01 (no valid mandate). A creditor obtains the CI once, before signing the first mandate, and keeps it permanently - it stays the same even if the creditor later starts collecting through a different payment service provider. For creditors registered in Lithuania, the CI is issued by the creditor’s payment service provider and is constructed from the creditor’s existing registration data: Example: LT11ZZZ123456789 Creditors registered in other SEPA countries receive their CI under their own national rules - in some countries it is issued by the national bank or a business registry rather than the creditor’s payment service provider. See the EPC Creditor Identifier Overview for the country-by-country issuance process and format.

Headers

Idempotency-Key
string
required

Unique identifier in scope of payment creation endpoints required to prevent unintended duplicate direct debit payments

Body

application/json
amount
integer
required

Amount in minor currency units

creditor
object
required

Party on the credit side of the transaction to which the tax applies

currencyIsoCode
string
required

For SEPA Direct Debit payments, only allowed value is 'EUR'

debtor
object
required

Party that owes an amount of money to the (ultimate) creditor

mandateInformation
object
required

Provides further details of the direct debit mandate signed between the creditor and the debtor.

sequenceType
enum<string>
required

Identifies the direct debit sequence, such as first, recurrent, final or one-off.

Available options:
FRST,
RCUR,
FNAL,
OOFF
settlementDate
string<date>
required

Date on which the amount of money ceases to be available to the agent that owes it and when the amount of money
becomes available to the agent to which it is due.

endToEndId
string

Unique identification, as assigned by the initiating party, to unambiguously identify the transaction.
This identification is passed on, unchanged, throughout the entire end-to-end chain

Required string length: 1 - 35
purpose
object

Underlying reason for the payment transaction. Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

ultimateCreditor
object

Ultimate party to which an amount of money is due.

ultimateDebtor
object

Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to the taxing authority.

Response

A new SEPA direct debit payment has been created

result
object
required

Result of sepa direct debit payment request creation

Last modified on July 15, 2026