SEPA Direct Debit
Charge customers directly via SEPA Direct Debit without a hosted checkout page.
SEPA Direct Debit allows you to collect payments directly from a customer's bank account using their IBAN. Unlike payment links, this is a server-to-server operation — no customer interaction is required at payment time.
Prerequisites
- A valid SEPA mandate from the customer (see SDD Mandates)
- EUR currency only
- Debtor name and IBAN
Activating SEPA Direct Debit
SEPA Direct Debit is an approval-based payment method. If it is not active on the company yet, request activation before the first charge:
curl -X POST https://app.roxpay.eu/api/v4/payments/payment-methods/requests \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"PaymentMethod": "sepa_direct_debit"}'
PaymentMethod accepts sepa_direct_debit or the brand codes SEPA / ELV. A RoxPay admin reviews the request; SDD becomes active only after approval. The call is idempotent: if SDD is already active it returns success and changes nothing, and a second request while one is pending returns 409. The response reports Status as active, pending or not_requested.
The same request works on POST /api/v5/payments/payment-methods/requests. Enabling SEPA through the standard POST /api/v4/payments/payment-methods (or v5) endpoint is rejected with 422; use the request endpoint instead. Every other payment method keeps using POST /api/v4/payments/payment-methods (or v5).
Creating a SEPA Charge
POST /api/v4/payments/sepa-direct
curl -X POST https://app.roxpay.eu/api/v4/payments/sepa-direct \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"Amount": 4999,
"Currency": "EUR",
"StatementDescription": "Monthly subscription - July 2026",
"DebtorIban": "IT60X0542811101000000123456",
"DebtorName": "Mario Rossi",
"ShopperReference": "booking-1001",
"Mandate": {
"Amount": 4999,
"AmountRule": "exact",
"Frequency": "monthly",
"StartsAt": "2026-08-01",
"EndsAt": "2027-07-01"
}
}'
The same body is accepted on POST /api/v5/payments/sepa-direct.
Send Mandate only on the first charge, together with ShopperReference, DebtorIban, and DebtorName. The response includes StoredPaymentMethodId. Later charges send that id and the same ShopperReference instead of the IBAN:
{
"Amount": 4999,
"Currency": "EUR",
"StatementDescription": "Monthly subscription - August 2026",
"ShopperReference": "booking-1001",
"StoredPaymentMethodId": "8415718414995012"
}
Mandates
Before charging a customer, you need a SEPA mandate. Create one via the SDD endpoints:
# Create mandate
curl -X POST https://app.roxpay.eu/api/v4/sdd/mandates \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"DebtorIban": "IT60X0542811101000000123456",
"DebtorName": "Mario Rossi",
"MandateType": "CORE"
}'
# List mandates
curl -X GET https://app.roxpay.eu/api/v4/sdd/mandates \
-H "Authorization: Bearer YOUR_TOKEN"
# Get specific mandate
curl -X GET https://app.roxpay.eu/api/v4/sdd/mandates/MANDATE_UUID \
-H "Authorization: Bearer YOUR_TOKEN"
SEPA on Payment Links
You can also offer SEPA as a payment method on hosted checkout pages. See Payment Links — SEPA.
Constraints
| Rule | Detail |
|---|---|
| Currency | EUR only |
| Debtor details | DebtorIban and DebtorName required unless StoredPaymentMethodId is set |
| Mandate | First charge may send Mandate plus ShopperReference. Later charges send StoredPaymentMethodId |
| Settlement | Async — status goes through PENDING before SETTLED |
| Refunds | Supported within 8 weeks (customer-initiated) or via API |