SEPA Direct Debit

Countries & currencies

Supported countries

• Åland Islands
• Andorra
• Austria
• Belgium
• Cyprus
• Estonia
• Finland
• France
• French Guiana
• Germany
• Greenland
• Guadeloupe
• Ireland
• Italy
• Latvia
• Lithuania
• Luxembourg
• Malta
• Martinique
• Mayotte
• Monaco
• Netherlands
• Portugal
• Réunion
• Saint Barthélemy
• Saint Martin
• Saint Pierre and Miquelon
• San Marino
• Slovakia
• Slovenia
• Spain
• Vatican City

Supported currencies

• Euro (EUR)

Integration

We offer this payment methods for the following integration modes. Learn in our dedicated guides about their individual differences:

• Hosted Checkout Page
• Server-to-server

Find a high level overview in the "Process flows" chapter.

This payment method allows you to address various business cases. Depending on the integration mode and the business case, differences apply. Have a look at this matrix to know exactly what is most suitable for you:

Hosted Checkout Page with mandate creation

Add the following properties to a standard CreateHostedCheckout request:

{
   "hostedCheckoutSpecificInput":{
      "returnUrl":"https://yourReturnUrl.com",
      "locale":"en_GB",
      "paymentProductFilters":{
         "restrictTo":{
            "products":[
               771
            ]
         }
      }
   },
   "order":{
      "amountOfMoney":{
         "amount":1000,
         "currencyCode":"EUR"
      }
   },
   "sepaDirectDebitPaymentMethodSpecificInput":{
      "paymentProduct771SpecificInput":{
         "mandate":{
            "customerReference":"CustomerRef_{{TIMESTAMP}}",
            "recurrenceType":"RECURRING",
            "signatureType":"SMS"
         }
      }
   }
}

Server-to-server with mandate creation

Add the following properties to a standard CreatePayment request:

{
	"order": {
		"amountOfMoney": {
			"amount": 123,
			"currencyCode": "EUR"
		}
	},
	"sepaDirectDebitPaymentMethodSpecificInput": {
		"paymentProduct771SpecificInput": {
			"mandate": {
                        "returnUrl": "https://yourReturnUrl.com",
			"customer": {
					"bankAccountIban": {
						"iban": "BE45000253450589"
					},
					"companyName": "yourCompanyName",
					"contactDetails": {
						"emailAddress": "customer@domain.com"
					},
					"mandateAddress": {
						"city": "Paris",
						"countryCode": "FR",
						"street": "27 rue des fleurs",
						"zip": "75008"
					},
					"personalInformation": {
						"name": {
							"firstName": "john",
							"surname": "doe"
						},
						
					}
				},
			"customerReference": "0efaa98944324234b9ad27f9355a1093",
			"language": "en",
			"recurrenceType": "RECURRING",
			"signatureType": "SMS"
			}
		},
	"paymentProductId": 771
	}
}

Server-to-server with existing mandate

Add the following properties to a standard CreatePayment request:

{
	"order": {
		"amountOfMoney": {
			"amount": 200,
			"currencyCode": "EUR"
		}
	},
	"sepaDirectDebitPaymentMethodSpecificInput": {
		"paymentProduct771SpecificInput": {
			"existingUniqueMandateReference": "mandateRef_existingReference"
		},
		"paymentProductId": 771
		}
}

Create mandate

Our CreateMandateAPI allows you to create a mandate for later use, thus separating it from the transaction request linked to this mandate. Consequentially, you can use this mandate in subsequent Server-to-server with existing mandate requests.

Add the following properties to a standard CreateMandate request:

{
   "customer":{
      "bankAccountIban":{
         "iban":"BE45000253450589"
      },
      "mandateAddress":{
         "city":"Monument Valley",
         "countryCode":"US",
         "houseNumber":"13",
         "street":"Desertroad",
         "zip":"84536"
      },
      "personalInformation":{
         "name":{
            "firstName":"Jane",
            "surname":"Doe"
         },
      }
   },
   "customerReference":"uniqueCustomerReference123456789012",
   "language":"en",
   "recurrenceType":"UNIQUE",
   "returnUrl":"https://yourReturnUrl.com",
   "signatureType":"SMS"
}

Process flows

As there are some differences in the flow depending on the integration mode/mandate management, we describe them separately. Read our dedicated paragraphs in the "Integration" chapter to get a JSON example for each flow.

With mandate creation via CreateHostedCheckout

This flow applies to the creation of a transaction and a mandate in one go.
It covers the following use cases:

• One-off transactions
• The first transaction of a series linked to a mandate

1. Your customers finalise an order in your shop and select this payment method.
2. You send a CreateHostedCheckout request to our platform to create a mandate and the payment.
3. Our platform sends you a response containing a redirectUrl
4. If you have sent the signatureType as SMS, our platform sends a SMS with an one -time password to your customers for verification (step 5). If you have sent signatureType as UNSIGNED, the flow continues at step 6.
5. Your customers enter their bank credentials, including the one-time password, on the redirectUrl to sign the mandate and to confirm the payment.
6. We redirect your customer to your returnUrl
7. We send the transaction for processing and receive the result from the issuer (within 1-2 days).
8. As soon as the issuer has confirmed processing the transaction, our platform updates the transaction to statusOutput.statusCode=9
9. You request the transaction result from our platform via GetHostedCheckout or receive the result via webhooks.
10. If the transaction was successful(statusOutput.statusCode=9), you can deliver the goods / service.
11. The issuer transfers the funds to us.
12. We transfer the funds to you.

With mandate creation via CreatePayment

1. Your customers finalise an order in your shop and select this payment method.
2. You send a CreatePayment request to our platform to create a mandate. Our platform sends you a response containing a merchantAction.redirectData.redirectURL (you will need for step 4) and sepaDirectDebitPaymentMethodSpecificOutput.paymentProduct771SpecificOutput.mandateReference (you will need for step 8).
3. You redirect your customers to the merchantAction.redirectData.redirectURL. Your customers enter their phone number on this page.
4. If you have sent the signatureType as SMS, our platform sends a SMS with an one -time password to your customers for verification (step 5). If you have sent signatureType as UNSIGNED, the flow continues at step 6.
5. Your customers enter the one-time password on the redirectUrl to sign the mandate.
6. We redirect your customer to your returnUrl
7. We process the transaction immediately after the mandate creation. We receive the result from the issuer within 1-2 days.
8. As soon as the issuer has confirmed processing the transaction, our platform updates the transaction to statusOutput.statusCode=9
9. You request the transaction result from our platform via GetPaymentDetails or receive the result via webhooks.
10. If the transaction was successful(statusOutput.statusCode=9), you can deliver the goods / service.
11. The issuer transfers the funds to us.
12. We transfer the funds to you.

With existing mandate via CreatePayment

This flow applies to:

• One-off transactions
• The first or follow-up transactions of a series of related payments

for which you already have a mandate.

1. Your customers finalise an order in your shop and select this payment method.
2. You send this CreatePayment request to our platform, including the existing mandate reference in property sepaDirectDebitPaymentMethodSpecificInput.paymentProduct771SpecificInput.existingUniqueMandateReference
3. We process the transaction. We receive the result from the issuer within 1-2 days.
4. As soon as the issuer has confirmed processing the transaction, our platform updates the transaction to statusOutput.statusCode=9
5. You request the transaction result from our platform via GetPaymentDetails or receive the result via webhooks.
6. If the transaction was successful(statusOutput.statusCode=9), you can deliver the goods / service.
7. The issuer transfers the funds to us.
8. We transfer the funds to you.

Mandate creation for later use via CreateMandate

This flow applies if you want to create a mandate and charge your customer at a later stage (i.e. when your customers create an account with you and you charge them at a fixed date at a later stage):

1. You send a CreateMandate request to our platform.
2. Our platform sends you a response containing a redirectUrl
3. You redirect your customers to the redirectUrl to fill in the SEPA mandate.
4. If you have sent the signatureType as SMS, our platform sends a SMS with an one-time password to your customers for verification (step 4). If you have sent signatureType as UNSIGNED, the flow continues at step 5.
5. Your customers enter the one-time password on the redirectUrl to confirm the mandate creation.
6. We redirect your customer to your returnUrl

Testing

Refer to our Test cases for test data and detailed instructions.