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 payment
Get a Sepa XML payment
Authorizations
Value for the Authorization header parameter.
Path Parameters
SepaXmlPayment identifier
Response
The invoice of the payment. In case of a cart payment or manual payment intent, the invoice is null.
The bank account of the mandate
The source of the bank account. Can be any string.
The date of the creation
The reference of the mandate
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 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 date of the mandate signature
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 bank account of the mandate
The source of the bank account. Can be any string.
The date of the creation
The reference of the mandate
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 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 date of the mandate signature
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 transaction of the payment.
Possible values:
credit
: Creditdebit
: Debit
credit
, debit
Was this page helpful?