How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tietoevry SEPA Direct Debits

A SEPA Direct Debit gateway for Creditor and Debtor roles, allowing creditors to initiate payments, cancel (reverse) them and issue refunds, and debtors to reject payments and raise chargebacks, with an event-notification webhook mechanism that pushes state changes for payments, refunds and incoming collections to Creditor-Notification-URI and Debtor-Notification-URI endpoints.

This API exposes 15 operations across 15 paths, organized into 2 resource areas, and defines 14 schemas. It is described by OpenAPI 3.0.1, at version 1.

Requests are made against 2 base URLs: https://payments.api.tieto.com/sandbox/v1/sepadd, https://payments.api.tieto.com/live/v1/sepadd.

15 operations 15 paths 14 schemas 3 GET12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1
Base URL
https://payments.api.tieto.com/live/v1/sepadd
Authentication
OpenID Connect
Resource Areas
2

Authentication & Security 1

Tietoevry SEPA Direct Debits declares 1 security scheme for authenticating requests. It supports OpenID Connect (bearerToken) discovered at http://example/openid-connect. By default, every request must be authenticated.

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 3 GET, 12 POST. They span 2 resource areas: Debtor, Creditor. Each is listed below with its method, path, parameters, and response codes.

Debtor 7

Operation for debtors

POST
/{receiveRefund}
(Webhook) Receive a Refund
receiveRefund body → 2044XX5XX
POST
/{receivePaymentCharge}
(Webhook) Receive Payment Charge
receivePaymentCharge body → 2044XX5XX
POST
/{confirmAvailabilityOfFunds}
(Webhook) Confirm availability of funds
confirmAvailabilityOfFunds body → 2044XX5XX
POST
/v1/debtor/payments/{payment-id}/actions/reject
Reject payment
rejectPayment 5 params body → 2044XX5XX
POST
/v1/debtor/payments/{payment-id}/chargebacks
Create a chargeback
chargebackPayment 6 params body → 2014XX5XX
POST
/{receiveChargebackStatus}
(Callback) Receive Chargeback Status
receiveChargebackStatus body → 2044XX5XX
GET
/v1/debtor/payments/{payment-id}/chargebacks/{chargeback-id}
Get chargeback
getChargeback 6 params → 2004XX5XX
Creditor 8

Operation for creditors

POST
/{verifyCreditorAndAccounts}
(Webhook) Verify creditor and accounts
verifyCreditorAndAccounts body → 2044XX5XX
POST
/v1/creditor/payments
Create payment
createPayment 5 params body → 2014XX5XX
POST
/{receivePaymentStatus}
(Callback) Receive Payment Status
receivePaymentStatus body → 2044XX5XX
GET
/v1/creditor/payments/{payment-id}
Get payment
getPayment 5 params → 2004XX5XX
POST
/v1/creditor/payments/{payment-id}/actions/cancel
Cancel payment
cancelPayment 5 params body → 2044XX5XX
POST
/v1/creditor/payments/{payment-id}/refunds
Create a refund
createRefund 6 params body → 2014XX5XX
POST
/{receiveRefundStatus}
(Callback) Receive Refund Status
receiveRefundStatus body → 2044XX5XX
GET
/v1/creditor/payments/{payment-id}/refunds/{refund-id}
Get refund
getRefund 6 params → 2004XX5XX

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are PaymentRequest (12 properties), Address (5 properties), MandateInformation (4 properties), RefundStatus (3 properties). Each schema is shown below with its type and property counts.

TransactionStatus
string
The transaction status is filled with codes of the ISO 20022 data table: - 'ACCP': 'AcceptedCustomerProfile' - Preceding check of technical validation was succ…
ErrorResponse
object
2 properties 1 required
Amount
object
2 properties 2 required
AccountReference
object
1 property 1 required
RemittanceInformationStructured
object
Structured remittance information
1 property
MandateInformation
object
4 properties
Address
object
5 properties
ReasonCode
string
"MD05" - "Collection not due" "MD06" - "Refund Request By End Customer"
EventName
string
Event name
PaymentRequest
object
Data that describes the payment
12 properties
Event
object
1 property
PaymentStatus
object
3 properties
RefundStatus
object
3 properties
ChargebackStatus
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tietoevry-sepa-direct-debit-api-gateway.yaml Raw ↑
Where this information came from

This is an independent, third-party profile of Tietoevry SEPA Direct Debits, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.