API documentation
User
Tenant
Feature
Entitlement
User & permissions
Settings
- Settings
- Media
- Webhook
- Notification
Payment
- Payment Method
- Transaction
- SEPA XML
- Open Banking
- Bank Account Transaction
Customer
- Customer
- Customer Address
- Customer Email
- Customer Settings
- Customer Otp
Billing
- Invoice
- Invoice Position Item
- Billing Run
Dunning
- Dunning Document
- Dunning Rule
Subscription
- Subscription
- Subscription Item
- Subscription Measurement
- Billing Group
Offers
- Offer
- Offer Recipient
- Offer Template
Catalogue
- Unit
- Measurement
- Product
- Product Family
- Price Plan
- Coupon
Checkout
- Checkout Link
- Cart
Accounting
Get a SEPA XML file
Returns a generated SEPA XML file.
Required permissions:sepa-xml:read
Authorizations
Value for the Authorization header parameter.
Path Parameters
SepaXmlStatement identifier
Response
Indicates if the SEPA XML file was uploaded to the bank already. If not, the file can be deleted. If yes, all transactions will be marked as waiting, until the grace period of the bank is over.
The unique message ID of the SEPA XML file
The date and time when the SEPA XML file was generated
The SEPA XML payments included in this SEPA XML file
Possible values:
credit
: Creditdebit
: Debit
credit
, debit
The status of the mandate
Possible values:
active
: The mandate is active and can be used for paymentsrevoked
: The customer has revoked the mandate or a payment was rejected by the bank. The mandate can not be used for payments anymore
active
, revoked
The reference of the mandate
The bank account of the mandate
The sequence type of the mandate
Possible values:
FRST
: The sepa mandate is used for the first time for a recurring paymentRCUR
: The sepa mandate was already used the first time and is now used for recurring paymentsFNAL
: The sepa mandate is used for the last time for a recurring paymentOOFF
: The sepa mandate is only allowed to be used for one payment
FRST
, RCUR
, FNAL
, OOFF
The type of the mandate
Possible values:
CORE
: The core scheme is used for payments between consumers and companiesB2B
: The B2B scheme is used for payments between companies. No refund is possibleCOR1
: The COR1 scheme is used for payments between consumers and companies. The payment is processed faster than with the core scheme
CORE
, B2B
, COR1
The invoice of the payment. In case of a cart payment or manual payment intent, the invoice is null.
The unique identifier of the invoice.
The customer of the invoice.
2 - 255
Can be empty if the customer is a company.
2 - 255
Can be empty if the customer is a company.
2 - 255
Can be empty. In this case the default currency of the tenant is used.
2 - 255
The ID of the customer in DATEV
2 - 255
STATUS_ACTIVE
, STATUS_ARCHIVED
, STATUS_SUSPENDED
The payment method which should be used to fullfill the payment of the invoice.
wallet
, sepa_debit
, stripe
, fake_provider
, paypal
, bank_transfer
, go_cardless
, testing
sepa_debit
, card
, paypal
, bank_transfer
, wallet
, fake_provider
active
, action_required
, expired
, revoked
, gateway_unconfigured
The type of the invoice.
TYPE_INVOICE
, TYPE_CREDIT
, TYPE_REFUND
, TYPE_REMINDER
, TYPE_CANCEL
, TYPE_DUNNING
The currency code of the invoice. If multiple currency codes will be used in the positions, they will be converted to that base currency.
The document id of the invoice. This will be generated, when the invoice will be finalized.
STATUS_DRAFT
, STATUS_PAID
, STATUS_CANCELLED
, STATUS_CLOSED
, STATUS_REFUNDED
, STATUS_REMINDED
, STATUS_UNPAID
, STATUS_NEW
, STATUS_FINALIZING
reminder
, dunning
, none
The invoice address of the invoice.
The notice of the invoice.
The net amount of the invoice.
Custom fields for the entity. The keys are the field names and the values are the field values. They need to be configured under "/custom-fields" in the API documentation. The input is validated against the configuration. For more details see Custom Fields Guide
The transaction of the payment.
The media file containing the SEPA XML statement(s) as zip. See <a href ="#tag/Media/operation/getDownloadToken">Download media</a> for more information.
Was this page helpful?