SEPA

SEPA (Single Euro Payments Area) is an area comprised of 34 European countries in which payment transactions denominated in euro are being standardized. Starting on the 1^st of February 2014, the old national bank transfer and direct debit systems are replaced by the standardized SEPA Credit Transfer and SEPA Direct Debit.

SEPA provides

• SEPA direct debit (collect money from customer)
• SEPA credit transfer (refund money to customer)
• in 34 countries
• in EUR currency.

IBAN/BIC

For you as an online trader this transition will not only affect direct debit payments but any bank account-based payment method. From now on, bank account details must be provided in IBAN/BIC format. This is true for both your customers' and your own accounts. All German bank account details of our merchants will be converted automatically by us. However, if you are using a foreign bank account, we will have to ask you to take care of that transition yourself.

For payments via online transfer, on invoice or by prepayment, it is sufficient to indicate the IBAN/BIC of your merchant account to receive the payments. In case of refunds or repayments, the respective IBAN/BIC will also be required.

PAYONE has adapted the processing of bank statements for IBAN/BIC in such a way, that the automatic assignment of transactions and return debit notes will still be possible.

All account details for accounts with German financial institutions will automatically be converted to the IBAN/BIC format during a transaction. This means that the account details of existing customers will remain unchanged in our system until a transaction is performed. Details for bank accounts with foreign institutions cannot be converted automatically (see below).

Converting account number/sort code into IBAN/BIC

We will generate the IBAN and BIC from the provided account number and sort code wherever this is necessary for a transaction for both existing customers' and newly submitted account details for German accounts. We will also complement the BIC, if only an IBAN was submitted. This allows you to use the "IBAN only" procedure, which was officially introduced in Germany on 1^st February 2014. We do not offer this service for accounts at foreign institutions. For German accounts, PAYONE has a conversion rate of over 99% of all valid bank details (excluding deprecated or deleted bank codes).

We will break down the IBAN/BIC into the country-specific account details (BBAN, in Germany: account number/sort code) for both German and foreign bank accounts ensuring that the dataset in our system always contains IBAN/BIC and BBAN. Any payment information provided in IBAN/BIC format before the official SEPA migration is therefore processed correctly without any risk of rejected payments due to missing account information.

Bank account check

The so-called Bankaccount Check (request "bankaccountcheck") is extended by the above conversion. You will receive the converted account data with the response. The same applies to the new "managemandate" request (see below).

SEPA Direct Debit

SEPA requires a number of changes for processing direct debit payments. With the extension of our interfaces and enhanced features on the PAYONE Platform, we offer you to retrieve individual customised SEPA direct debits. The spectrum ranges from the simple processing of SEPA direct debits without the need to adapt the interfaces at your end up to a complete SEPA service which includes obtaining mandates as well as generating and managing mandate PDFs.

Creditor ID

The creditor ID identifies your company to the end customer and is issued on the account statement of the end customer. The creditor ID is also required for obtaining a mandate, since mandates are always created for a particular beneficiary or creditor.

If you use the PAYONE Collection Service, you are automatically assigned a business identifier of PAYONE's own creditor IDs – so everything is taken care of.

If you process direct debits via your own accounts, please send your creditor ID to PAYONE; we need this information in combination with the mandate reference for processing your direct debits.

SEPA mandate retrieval

You are generally free to adapt the retrieval process for your SEPA mandates according to your own requirements. However, there are certain rules for retrieving mandates. Please consult your principal bank to find out the exact form for obtaining your mandates.

PAYONE offers a mandate retrieval procedure that meets the requirements of the German banking industry for SEPA mandates (telecommunications-based transmission complying with the requirement for written documentation according to article 127 paragraph 2, 126 b – German Civil Code). This procedure has passed the corresponding legal examination. In addition, PAYONE has aligned this procedure with its own principal banks.

Please note that the legal situation with regard to obtaining mandates in online trading will remain uncertain in the coming years. Therefore, you will have to check with your principal bank whether it accepts the procedure described here or whether it insists on using a paper-based mandate. Please note that, in any event, the burden of proof and evidence for the existence of a mandate that was authorised by the payer is with you as the payee. Therefore, no guarantee can be given that the electronic mandate issued will be recognised by the debtor's bank in case of dispute. In this case, the deadline for returning goods is extended from 8 weeks to 13 months. (This is essentially the current practice in electronic direct debit)

PAYONE provides the following functions for processing SEPA direct debits:

Mandate reference generation

If the mandate references are not transmitted by the merchant's API, PAYONE automatically generates these references. PAYONE exclusively uses recurring mandates. If you use your own mandate references, please note that PAYONE only stores one mandate reference for each individual account (IBAN). If you submit the same account with a different mandate reference, our system will reject this and issue an error message. If you leave the generation of mandate references to PAYONE, our system will automatically check for each IBAN whether a valid mandate is already available or whether a new mandate needs to be created.

Determination of SEPA lead times

The SEPA regulations provide two different lead times of five and two days for an initial or for subsequent direct debits respectively. Direct debits between two German credit institutions will use the "COR1 procedure" reducing the lead time to only one day. Please consult your principal bank to find out whether and when it will support the COR1 procedure. The stipulated lead times are expressed in international banking days, so-called TARGET2 days. An additional regional banking day must be added for the submitting bank. PAYONE will determine whether the mandate is an initial or subsequent direct debit and will calculate the corresponding lead time.

Mandate text generation in HTML

PAYONE uses the request "managemandate" to generate mandate texts in the language of the consumer (currently German or English) that will be displayed to the consumer during the ordering process prompting him or her to confirm the mandate. The texts comply with the requirements of the European Payment Council EPC. Please refer to the Appendix for PAYONE's default mandate text.

Mandate text generation in PDF format

If you commission the product "SEPA mandates as PDF", a PDF containing the mandate content in the language of the consumer (currently German or English) will be created for each newly generated mandate. The texts comply with the requirements of the European Payment Council EPC. Please refer to the Appendix for PAYONE's default mandate text.

The mandate is stored on the PAYONE Platform from where you can retrieve it any time using the request "getfile".

There is a charge for generating mandates as a PDF files. Please note that PAYONE will only store one mandate for each of account (IBAN). If you order another mandate for the same account, the system will not generate a new mandate and there will not be any additional cost for you.

Using the Invoicing module for creating pre-notifications

If you have commissioned our Invoicing module for your billing processes, you can use these invoices for dispatching pre-notifications. If you use PAYONE's default invoice template, all the required SEPA data such as the creditor ID, the mandate reference and the posting date will be added automatically. If you use a custom template, please provide us with a sample when ordering the service so that we can make the necessary adjustments.

Mandate administration options

There are different options for handling mandates. The options outlined here describe a typical process in the area of retail with shipment of goods. A content provider's process may vary slightly, the SEPA functions remain the same, however. For detailed representations of the different processes and requests, please refer to the sequence diagrams in the Appendix.

SEPA direct debit with the PAYONE procedure for mandate retrieval

If you are using the full functionality of the PAYONE mandate administration, you can retrieve SEPA compliant direct debits (see above). PAYONE covers all specific SEPA requirements.

The sequence is as follows:

1. The consumer selects a product in the merchant's online shop.
2. The consumer enters his or her personal address and payment information.
   1. The merchant system will transfer the customer data with the request "managemandate" to PAYONE. No SEPA-relevant data have to be provided. If the merchant submits a mandate reference, PAYONE will use this information. Otherwise PAYONE will generate a new mandate reference automatically.
   2. PAYONE checks the payment data. If there is no mandate text associated to this account, the system will generate a "floating" mandate with a mandate reference and a mandate text in the consumer's language in HTML format.
   3. If there already is a mandate, the status "active" is transmitted. The mandate retrieval and storage steps described below (items 3 and 4) will not be required then meaning that the consumer will not have to acknowledge the mandate.
3. The SEPA-compatible mandate text is shown to the consumer for him or her to confirm.
4. The consumer acknowledges the mandate retrieval and completes the ordering process.
   
   1. The merchant system transmits the above-mentioned mandate reference to PAYONE with the next request (e.g. "preauthorization") which constitutes the consumer's authorisation of the mandate.
   2. If the merchant has commissioned the product "SEPA mandates as PDF", PAYONE will also create a mandate-PDF and save this on the PAYONE Platform.
5. The consumer will receive the mandate as a PDF file.
   1. If PAYONE has generated a mandate (see above), the merchant system can use the "getfile" request to retrieve this mandate and use it for further processes (e.g. provide it for download to the consumer).
6. The merchant dispatches the product and initiates the payment.
   1. The merchant initiates the payment (e.g. using the "capture" request). No SEPA-relevant data have to be provided.
   2. PAYONE will calculate the posting date and collect the direct debit.
   3. PAYONE transmits all data required by the merchant for a pre-notification via the server API.
   4. If the dealer has commissioned the Invoicing module, PAYONE will send the invoice with the pre-notification to the customer.

SEPA direct debit with own mandate retrieval

You can use the server API as described below, if you prefer to retrieve the mandates yourself:

1. The consumer selects a product in the merchant's online shop.
2. The consumer enters his or her personal address and payment information.
   1. The merchant retrieves the SEPA mandate from the end customer using his or her own system and requirements. This includes defining his or her own mandate reference.
3. The consumer completes the order.
   1. The order is transferred to PAYONE using an API request (e.g. "preauthorization"). The merchant includes the above-mentioned mandate reference in the request.
   2. If no mandate information has been stored at PAYONE for the transferred account details, the mandate is saved with the provided mandate reference on the PAYONE Platform.  If the merchant has commissioned the product "SEPA mandates as PDF", PAYONE will also create a mandate-PDF and save this on the PAYONE Platform.
   3. No new mandate will be generated if there already is one available.
4. The merchant dispatches the product and initiates the payment.
   1. The merchant initiates the payment (e.g. using the "capture" request). No SEPA-relevant data have to be provided.
   2. PAYONE will calculate the posting date and collect the direct debit.
   3. PAYONE transmits all data required by the merchant for a pre-notification via the server API.
   4. If the dealer has commissioned the Invoicing module, PAYONE will send the invoice with the pre-notification to the customer.

SEPA direct debit with automatically generated mandates

If PAYONE handles the generation of the mandate reference, the process is similar to the one described above under "SEPA direct debit with own mandate retrieval". The merchant is provided all relevant data for ensuring a SEPA-compliant direct debit process via the server API. PAYONE meets all technical requirements for SEPA direct debit submission and mandate referencing using this procedure. Please note, however, that you must ensure a SEPA-compliant retrieval of the mandates from your consumers yourself when using this procedure.

1. The consumer selects a product in the merchant's online shop.
2. The consumer enters his or her personal address and payment information.
3. The consumer completes the order.
   1. The order is transferred to PAYONE using an API request (e.g. "preauthorization"). The merchant does not transmit any SEPA-relevant data.
   2. If there is no mandate for the transferred account details on the PAYONE Platform, the system will generate a new one. If the merchant has commissioned the product "SEPA mandates as PDF", PAYONE will also create a mandate-PDF and save this on the PAYONE Platform. 
   3. No new mandate will be generated if there already is one available.
4. The merchant dispatches the product and initiates the payment.
   1. The merchant initiates the payment (e.g. using the "capture" request). The merchant does not transmit any SEPA-relevant data.
   2. PAYONE will calculate the posting date and collect the direct debit.
   3. PAYONE transmits all data required by the merchant for the mandate and the pre-notification via the server API.
   4. If the dealer has commissioned the Invoicing module, PAYONE will send the invoice with the pre-notification to the customer.

More options

Of course, you can also use the different options and requests separately. For example, you can decide to use the request "managemandate" without subsequently generating and saving the mandate as a PDF file. Or you can use the product "SEPA mandates as PDF" without previously having generated a "floating" mandate using the request "managemandate".

Request "managemandate"

The "managemandate" request provides the following functionality:

1. Bankaccount check: The transmitted account details are validated.
2. IBAN converter:
   1. German bank account details with account number/sort code are automatically converted into the IBAN/BIC format. The converted account data is transmitted via the API. This allows you to display them to the end customers for verification and information.
   2. Account details provided in the IBAN/BIC format will be complemented with the country-specific account details (BBAN, in Germany: account number/sort code).
3. Verification whether a mandate has been stored for these account details in the past.
4. Generation of a new "floating" mandate with a mandate text in the consumer's language in case no mandate is found.

If the mandate reference of the "floating" mandate is re-transmitted for the following request, this mandate will be stored permanently. If no subsequent request is sent, (e.g. because the consumer cancels the purchasing process), the "floating" mandate will be deleted after two hours.

Subsequent requests may be one of the following:

• preauthorization
• authorization
• createaccess
• vauthorization
• updateuser

Since a "bankaccount check" is performed during this request it will incur the same cost per call as the request "bankaccount check" itself. You will find a description of the API parameters in the API documentation.

Please refer to the Appendix for a sequence diagram with the mandate.

The request "getfile"

You can use the "getfile" request to download the mandate as a PDF from the PAYONE Platform. For this, the PDFs must have been generated previously, of course. This is done during the generation of a new mandate, if you have commissioned the product "SEPA mandates as PDF".

This request does not incur any charges. You will find a description of the API parameters in the API documentation.

Please refer to the Appendix for a sequence diagram with the mandate.

Check list: What do I have to do?

• If you are using the PAYONE Payment Service (PPS), you do not need your own creditor ID for processing direct debits via PAYONE. You are automatically assigned a business identifier of PAYONE's creditor IDs.
• If you are not using the PPS, you will have to provide your own creditor ID for using the direct debit procedure. You can request your own creditor ID at the German Central Bank at https://extranet.bundesbank.de/scp/.
  This is also required for working with the new requests for mandate administration in test mode.
  • If you want to use the direct debit procedure, please contact your principal bank with regard to a debt collection agreement.
  • Please clarify with your bank if direct debits are executed automatically or whether the execution requires the prior authorisation via an accompanying note to the transferred media.

• Provide us with the IBAN/BIC information for your accounts.
  PAYONE has automatically converted your bank accounts held at German financial institutions to the IBAN/BIC format and sent you a corresponding overview. 

• Decide on the nature and the scope of the SEPA implementation.
• Plan the adaptation of your interfaces.
• Enable the extended SEPA response data in the PMI under Configuration, Payment Portals. You can choose separate configurations for this data for test mode and for live mode to adjust your test systems accordingly.

FAQ – Frequently asked questions and answers

Appendix: Default mandate texts

Mandate text German

Mandate text English