Wirecard Documentation

SEPA

Wirecard offers two SEPA payment methods.

SEPA Direct Debit is very popular in Germany, Austria and the Netherlands.

The following transaction types may be used with both SEPA Direct Debit and SEPA Credit Transfer payment methods. For payment method specific transaction types, please refer to the individual payment method pages.

SEPA void

Wirecard Payment Gateway allows merchants to void SEPA Direct Debit and SEPA Credit Transfer transactions before they are forwarded to the bank for settlement.

This means: It is only possible to void a transaction between the time the transaction request has been received by the Wirecard Payment Gateway for processing and the time the transaction will be forwarded for processing to the bank. Once the payment was processed by the bank and settled, it is no longer possible to void a transaction.

To void an existing pending SEPA Direct Debit or SEPA Credit Transfer transaction, a merchant must

send a void-pending-debit or void-pending-credit request.
include the parent-transaction-ID.

Restrictions

To ensure proper processing, please take into consideration the following restrictions for SEPA Void transactions:

A pending-debit or pending-credit transaction may only be voided before the transaction is batched into a file and sent to the bank for processing.

Batch processing starts at around 10:00 UTC.

If a void request is sent after the transaction has been sent to the bank, a Failed response will be returned.
Once a corresponding debit or credit transaction exists for the original pending-debit or pending-credit it is no longer possible to void a transaction.
A request for a void transaction must contain a parent-transaction ID referring to the pending-debit or pending-credit transaction that should be voided.

Fields

The fields used for SEPA Void requests, responses and notifications are the same as the REST API fields. Please refer to REST API Fields or the request example for the fields required in a void-pending-debit or void-pending-credit transaction.

If the amount is sent within the request for the void transaction it will be checked if it is the same amount as in the previous pending-debit or pending-credit request. Partial cancellations are currently not possible.

Only the fields listed below have different properties.

The following elements are mandatory (M) or optional (O) for a request/response/notification. If the respective cell is empty, the field is disregarded or not sent.

Field	Request	Response	Notification	Description
requested-amount	O	M	M	This is the amount of the transaction. The amount of the decimal place is dependent of the currency. Min amount €0.01. Max amount €999,999,999.99. If it is sent within the request it will be validated if it is the same amount like in the pending-debit or pending-credit request.
requested-currency	O	M	M	This is the currency of the requested-amount. Only EUR is accepted.
payment-methods.payment-method-Name	M	M	M	This is the name of the payment method sepadirectdebit or sepacredit.
parent-transaction-id	M	M	M	Transaction ID of the transaction that needs to be voided.
transaction-type	M	M	M	This is the type for a transaction. For a SEPA Void request, only void-pending-debit, void-debit, void-pending-credit or void-credit are allowed.

Field

Request

Response

Notification

Description

requested-amount

This is the amount of the transaction. The amount of the decimal place is dependent of the currency. Min amount €0.01. Max amount €999,999,999.99.

If it is sent within the request it will be validated if it is the same amount like in the pending-debit or pending-credit request.

requested-currency

This is the currency of the requested-amount. Only EUR is accepted.

payment-methods.payment-method-Name

This is the name of the payment method sepadirectdebit or sepacredit.

parent-transaction-id

Transaction ID of the transaction that needs to be voided.

transaction-type

This is the type for a transaction. For a SEPA Void request, only void-pending-debit, void-debit, void-pending-credit or void-credit are allowed.

SEPA deposit

Occasionally, a consumer send funds back to the merchant, either at the request of the merchant or through his/her own initiative. There are several reasons for this such as a re-payment or a subsequent / supplementary payment for an already existing SEPA Direct Debit transaction.

These supplementary payments enter the Wirecard Payment Gateway as transactions with transaction type deposit and with the payment method wiretransfer.

If the consumer provides the PTRID (Provider Transaction Reference ID) in the descriptor of his transfer, the Wirecard Payment Gateway will attempt to match the deposit with the original SEPA Direct Debit or SEPA Credit Transfer transaction. If the PTRID is not provided or it is not possible to match the transaction, the transaction will remain unmatched.

Fields

The following elements are submitted in the IPN (Instant Payment Notification) either mandatory (M) or optional (O):

Field

Notification

Description

request-id

This is the identification number of the request on the merchant’s side. It must be unique for each request.

transaction-type

This is the type for a transaction. For SEPA Deposit, it is always deposit.

payment-methods.payment-method-Name

This is the name of the payment method wiretransfer.

Sample

XML deposit Notification

<?xml version="1.0" encoding="UTF-8"?>
<payment xmlns="http://www.elastic-payments.com/schema/payment" xmlns:ns2="http://www.elastic-payments.com/schema/epa/transaction">
    <merchant-account-id>7d10ba14-5527-45de-85f5-2aaede73c225</merchant-account-id>
    <transaction-id>8486a305-59fe-488d-bf63-8255ad5d3d68</transaction-id>
    <request-id>88541df6-a5af-4c2a-ae71-44c0b17ae494-deposit</request-id>
    <transaction-type>deposit</transaction-type>
    <transaction-state>success</transaction-state>
    <completion-time-stamp>2018-03-26T12:41:03.000Z</completion-time-stamp>
    <statuses>
        <status code="201.0000" description="bank:The resource was successfully created." severity="information"/>
    </statuses>
    <requested-amount currency="EUR">10.01</requested-amount>
    <parent-transaction-id>a88b4b46-f288-432a-b800-829976a11577</parent-transaction-id>
    <account-holder>
        <first-name>John</first-name>
        <last-name>Doe</last-name>
    </account-holder>
    <descriptor>SONI MR-01</descriptor>
    <payment-methods>
        <payment-method name="wiretransfer"/>
    </payment-methods>
    <api-id>---</api-id>
    <provider-transaction-reference-id>E98FABD066</provider-transaction-reference-id>
    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
        <SignedInfo>
            <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
            <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
            <Reference URI="">
                <Transforms>
                    <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
                </Transforms>
                <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
                <DigestValue>DMS2y5xxPoDnm/QXEFX/jQZXWsS/O7Ydtw1Gbe5U9jE=</DigestValue>
            </Reference>
        </SignedInfo>
        <SignatureValue>pS2QkXfqI4buhzyzp2fYbTC3SBeSNe0/LDVRw6GlF1FNkh9rq0V740/12k4S5iYtaxBPXishkZVFw0sVCnaTrNhOqBjaUG6UAL0+tmaxQwgLhJojwZCM9jnovT1ShwGXkYU7wWJxX20Ue2MnoputiTkMV5sDNYY/TElP5kwoe+2oVxLZbGpgbmyvSnJwpzpb32a8wrTxRRgBnHy3Vvo2FcyojliV1H+EI+WDBL6RycEQPHT48d0E7tu0oIUTz0y3jNV4H5oaxQ0KLKMOBkGGDJ4N5zWc39oqjQh/fzvtcvVyreVuQR27s+w6NltPRUYHxhheRi+WnZtS5FXKc+TcDyw7ya7dBfMxhUBAdXPBkd2TqH7ty8bgVmUGEC39Eazb1XG+3jpBmHIbUMTP2C0HFeNFmlb6Y7zYoQIcc+dXQzWJRIXz1QTr20Q7tjkataeTKzupo55JLyw8BCrFJi4kL8SgrInODj9utjJvPgIbA/vt1KDwVvkWoHh9ejIuQhddxePqmywufsWt1YNw/pkQ8g056l2Lc2QhRWdbT3MWesPVLUtl1UJaxmCmOdIUCHPwj9Xw5uO0zeJICdnxBPtBKCEX6hOUqptw9AZvtSlUEfmhJJE1O722uYy+6MoAzVthLOukeANaegesjpEYE8pnImicgRLmsRDalO0V8E6jL9g=</SignatureValue>
        <KeyInfo>
            <X509Data>
                <X509SubjectName>L=Ascheim,CN=engine.wirecard.sys,OU=Operations,O=Wirecard Technologies GmbH,C=DE</X509SubjectName>
                <X509Certificate>MIIF0DCCBLigAwIBAgICK8EwDQYJKoZIhvcNAQELBQAwWzELMAkGA1UEBhMCREUxETAPBgNVBAoTCFdpcmVjYXJkMTkwNwYDVQQDFDB3aXJlY2FyZC1EUS1NVUMtaW50ZXJuYWwtd2Vic2VydmljZS1pc3N1aW5nQ0FfMDIwHhcNMTYwNTIwMDc1MDI0WhcNMTgwNTIwMDc1MDI0WjB3MQswCQYDVQQGEwJERTEjMCEGA1UEChMaV2lyZWNhcmQgVGVjaG5vbG9naWVzIEdtYkgxEzARBgNVBAsTCk9wZXJhdGlvbnMxHDAaBgNVBAMTE2VuZ2luZS53aXJlY2FyZC5zeXMxEDAOBgNVBAcTB0FzY2hlaW0wggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDyqm9WQZish8wxW5WOB0m/kunHIcOC5DC8aEk55S4uf9hRi16+Fkg1y626GC//0eXVle+leUhF/e9e4wfqt/2wVNwkjhy2ww5uT2ZqojzvGyCAjnyDIr4C6+6Ezz9FZ1h2lNsbNRuKSoahTdycGAqduj5xjpiuNAnmh1EAZEYWSmR/QvY+PTV6+ltZAl5WlVCmTHuBUqvMUEOfMew5B7iA1BDUZ508l76cfTKHOu15kqA5ajxaAC/DeawCPSCdsdOTsWSVbKvn5FM8VK29Ah699XWi85sG5uniklhyDKuaHPplrL7+9eA1XaFSsaOc+obDRe2lus8YmIUMvaSsDfglZOGq8VLrDIXo2i4WC2AiNFtLNC/bndxrrYRd2+Rb5VviNblcQu1pfWTDd2SWKtyegg558UAAAgM2kJ4EUujCKp2t9EOELJZ2yHABTIySkuCkeLJfpqL6bGQJEZlzgtEE6hS1ywPjPMNg2F1BKGNH79KK8GvehWYDX4VfKoTROVHqc5ODxWGBoZ+mxHWiwLZ96KBniMBnoTuXTi5op7/0sW8F8ykd9kE6yH2d8YQMTQ6PAY4DG6KpsC0J2zE4P+iGfDeMnoud9Zws24ogf/mTag13URkYpYKpAglwuSHcciZgfGXSrmne+MspKbO24Ny0wZP3suY9ssNfyLooSlMfXwIDAQABo4IBgDCCAXwwEQYDVR0OBAoECEDpj0A8MIh/MBMGA1UdIwQMMAqACENsHhbUPQUOMAsGA1UdDwQEAwIE8DCCAUMGA1UdHwSCATowggE2MIIBMqCCAS6gggEqhoHVbGRhcDovL3dpcmVjYXJkLmxhbi9DTj13aXJlY2FyZC1EUS1NVUMtaW50ZXJuYWwtd2Vic2VydmljZS1pc3N1aW5nQ0FfMDIsQ049Q0RQLENOPVB1YmxpYyBLZXkgU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixkYz13aXJlY2FyZCxkYz1sYW4/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPUNSTERpc3RyaWJ1dGlvblBvaW50hlBodHRwOi8vY3JsLndpcmVjYXJkLmxhbi9DUkxfd2lyZWNhcmQtRFEtTVVDLWludGVybmFsLXdlYnNlcnZpY2UtaXNzdWluZ0NBXzAyLmNybDANBgkqhkiG9w0BAQsFAAOCAQEAmCbqd802pphK0hwKDcQ4mctQk1tXXS38+016QDOh/uJTzmG5WqFZfoXZ8GYwMl5zjE6g+ciuVv3q393gLLZdZrUHEOKS1xj8xWjUQd4uNDJPXY1RamPBDptahn6/AIR89UFDaN37L3fI7EfLqTHpbD92ZGVssmt/0cjd9ekNGN66dEJB0YGBZTVEALhwYF1KtcxiLo2b1KnbmKLgnldF6RwP6p93fpO29mQxw4ePU2/+GyWmYW053ObAYqMVNelLc2Fj4W82El2Gbw/rFBiNM9qBpYS8YkMwsmTr0m49AsI2H401KBwfR4Ci1zUXfZjWchIZjjEVeIR7gMTOl+/Cog==</X509Certificate>
            </X509Data>
        </KeyInfo>
    </Signature>
</payment>

SEPA debit-return and credit-return

A debit-return reverses a debit transaction. It is initiated by the consumer bank

if the consumer disputes the transaction
if there is a problem with the consumer bank account (e.g. bank account closed)

A credit-return reverses a credit transaction. It is initiated either by

the merchant’s bank (e.g. insufficient funds)
the consumer’s bank (e.g. bank account closed)

All debit-returns and credit-returns are included in reconciliation files provided by Wirecard Bank and sent to the Wirecard Payment Gateway. The transaction types debit-return and credit-return are then initiated by the Wirecard Payment Gateway. It is not possible for a merchant to request these transaction types.

If possible, a debit-return or credit-return is matched by the Wirecard Payment Gateway (WPG_)_ to its original debit/credit, based on the provider transaction reference ID (PTRID) and the merchant account.

Possible return codes are documented within Return Codes.

Workflow

Consumer’s bank sends a debit-return or credit-return to Wirecard Bank.
Wirecard Bank forwards the transaction to the WPG.
WPG receives the transaction.
WPG uses the PTRID to find an initial parent debit or parent credit transaction.
1. If successful, WPG maps the debit-return to a debit or credit-return to a credit.
2. if not successful, WPG creates a debit-return or credit-return without reference.
WPG sends a notification about the debit-return or credit-return to the merchant.

Sample

XML debit-return Notification

<?xml version="1.0" encoding="UTF-8"?>
<payment xmlns="http://www.elastic-payments.com/schema/payment" xmlns:ns2="http://www.elastic-payments.com/schema/epa/transaction">
    <merchant-account-id>cd237c02-72fb-4fc4-a5ab-c965ba95b5a9</merchant-account-id>
    <transaction-id>d7f4038d-3e37-403c-842f-9bfda761149c</transaction-id>
    <request-id>e446b34c-c5f5-43c4-9b2b-a1415096c334-debit-return</request-id>
    <transaction-type>debit-return</transaction-type>
    <transaction-state>success</transaction-state>
    <completion-time-stamp>2018-07-17T10:56:00.000Z</completion-time-stamp>
    <statuses>
       <status code="201.0001" description="bank:Reason for the return was not specified by the debtor bank" severity="information"/>
    </statuses>
    <requested-amount currency="EUR">10.01</requested-amount>
    <parent-transaction-id>3fa23529-a93d-4701-8e60-b01e699f3709</parent-transaction-id>
    <account-holder>
       <first-name>John</first-name>
       <last-name>Doe</last-name>
    </account-holder>
    <descriptor>Sanho XS 234-T</descriptor>
    <payment-methods>
       <payment-method name="sepadirectdebit"/>
    </payment-methods>
    <mandate>
       <mandate-id>12345678</mandate-id>
       <signed-date>2018-07-17</signed-date>
    </mandate>
    <creditor-id>DE98ZZZ09999999999</creditor-id>
    <api-id>---</api-id>
    <due-date>2018-07-20T00:00:00.000Z</due-date>
    <consumer>
       <first-name>Jack</first-name>
       <last-name>Smith</last-name>
    </consumer>
    <provider-transaction-reference-id>13DFDA6E77</provider-transaction-reference-id>
    <instrument-country>DE</instrument-country>
    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
       <SignedInfo>
          <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
          <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
          <Reference URI="">
             <Transforms>
                <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
             </Transforms>
             <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
             <DigestValue>BiZCe3KfQqbKFo0cAw+4b17WylkhDMMp8ahMGaDzbPQ=</DigestValue>
          </Reference>
       </SignedInfo>
       <SignatureValue>k+QO8NDFgh5RQTMZCVjOhRJ82I6Tft8z2b2UF5a0M5f4iYycd93tG8qYXJZmdpiEXnpVZg2yVmZWAJD23N3/+aONjA1EAzv4egMNb4zDSfSjQ9px2udU0YKJmUfHueFMvdXCykVtk+osYvIgm+xYg6HSLQEiBstM3OS3Hwo1UkZf2Vn/8a/QbKVpxC2cNNQd95L0HuveDbGB+FNfBqf855gkxJIfLpmTfyDB9HD9SSwquGbRf0XeTpX0wthYQepEfWSNIWpaCgoVOSFMaLjMMsnjUwn3Gga7ZJKn4VLDlwi9KROZmm/86XyXYyoP8qEIGnJxAV0zj6fM35bmCcS/1ipWJG9bpngB1K95JF1zs/GSQ4nKVnPsQZs5ifoGiqSoJ+kq8C4KHv2VOng4TFEFcGxyfLfEUHuSNpshezEVtOVfVo3jNkVLLl9I8tLXF7+HiNHGzPXgY330iwzikIJZxpozem0KkLRCM0dn2lsFzSWkT9qS7kNuDsSUb0YRWDPdWVldBrtG8wRdgx/SeSeE8L+vk4MtmEPSE46X9IHhn4OEBu7pKE3RvuEThrRgtKNvLG1CX9+ke7wXuyRrT93OOunVoCRi7XJdUUIS0Aov9a1Xaf/jEa24AGoOTkj96RhnuAjhwy7P+qD7OBk+4MNQfLRwQE/n3U3SJ2aufE+ds30=</SignatureValue>
       <KeyInfo>
          <X509Data>
             <X509SubjectName>L=Ascheim,CN=engine.wirecard.sys,OU=Operations,O=Wirecard Technologies GmbH,C=DE</X509SubjectName>
             <X509Certificate>MIIF0DCCBLigAwIBAgICK8EwDQYJKoZIhvcNAQELBQAwWzELMAkGA1UEBhMCREUxETAPBgNVBAoTCFdpcmVjYXJkMTkwNwYDVQQDFDB3aXJlY2FyZC1EUS1NVUMtaW50ZXJuYWwtd2Vic2VydmljZS1pc3N1aW5nQ0FfMDIwHhcNMTYwNTIwMDc1MDI0WhcNMTgwNTIwMDc1MDI0WjB3MQswCQYDVQQGEwJERTEjMCEGA1UEChMaV2lyZWNhcmQgVGVjaG5vbG9naWVzIEdtYkgxEzARBgNVBAsTCk9wZXJhdGlvbnMxHDAaBgNVBAMTE2VuZ2luZS53aXJlY2FyZC5zeXMxEDAOBgNVBAcTB0FzY2hlaW0wggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDyqm9WQZish8wxW5WOB0m/kunHIcOC5DC8aEk55S4uf9hRi16+Fkg1y626GC//0eXVle+leUhF/e9e4wfqt/2wVNwkjhy2ww5uT2ZqojzvGyCAjnyDIr4C6+6Ezz9FZ1h2lNsbNRuKSoahTdycGAqduj5xjpiuNAnmh1EAZEYWSmR/QvY+PTV6+ltZAl5WlVCmTHuBUqvMUEOfMew5B7iA1BDUZ508l76cfTKHOu15kqA5ajxaAC/DeawCPSCdsdOTsWSVbKvn5FM8VK29Ah699XWi85sG5uniklhyDKuaHPplrL7+9eA1XaFSsaOc+obDRe2lus8YmIUMvaSsDfglZOGq8VLrDIXo2i4WC2AiNFtLNC/bndxrrYRd2+Rb5VviNblcQu1pfWTDd2SWKtyegg558UAAAgM2kJ4EUujCKp2t9EOELJZ2yHABTIySkuCkeLJfpqL6bGQJEZlzgtEE6hS1ywPjPMNg2F1BKGNH79KK8GvehWYDX4VfKoTROVHqc5ODxWGBoZ+mxHWiwLZ96KBniMBnoTuXTi5op7/0sW8F8ykd9kE6yH2d8YQMTQ6PAY4DG6KpsC0J2zE4P+iGfDeMnoud9Zws24ogf/mTag13URkYpYKpAglwuSHcciZgfGXSrmne+MspKbO24Ny0wZP3suY9ssNfyLooSlMfXwIDAQABo4IBgDCCAXwwEQYDVR0OBAoECEDpj0A8MIh/MBMGA1UdIwQMMAqACENsHhbUPQUOMAsGA1UdDwQEAwIE8DCCAUMGA1UdHwSCATowggE2MIIBMqCCAS6gggEqhoHVbGRhcDovL3dpcmVjYXJkLmxhbi9DTj13aXJlY2FyZC1EUS1NVUMtaW50ZXJuYWwtd2Vic2VydmljZS1pc3N1aW5nQ0FfMDIsQ049Q0RQLENOPVB1YmxpYyBLZXkgU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixkYz13aXJlY2FyZCxkYz1sYW4/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPUNSTERpc3RyaWJ1dGlvblBvaW50hlBodHRwOi8vY3JsLndpcmVjYXJkLmxhbi9DUkxfd2lyZWNhcmQtRFEtTVVDLWludGVybmFsLXdlYnNlcnZpY2UtaXNzdWluZ0NBXzAyLmNybDANBgkqhkiG9w0BAQsFAAOCAQEAmCbqd802pphK0hwKDcQ4mctQk1tXXS38+016QDOh/uJTzmG5WqFZfoXZ8GYwMl5zjE6g+ciuVv3q393gLLZdZrUHEOKS1xj8xWjUQd4uNDJPXY1RamPBDptahn6/AIR89UFDaN37L3fI7EfLqTHpbD92ZGVssmt/0cjd9ekNGN66dEJB0YGBZTVEALhwYF1KtcxiLo2b1KnbmKLgnldF6RwP6p93fpO29mQxw4ePU2/+GyWmYW053ObAYqMVNelLc2Fj4W82El2Gbw/rFBiNM9qBpYS8YkMwsmTr0m49AsI2H401KBwfR4Ci1zUXfZjWchIZjjEVeIR7gMTOl+/Cog==</X509Certificate>
          </X509Data>
       </KeyInfo>
    </Signature>
</payment>

Dynamic Descriptor

Just like Credit Card it is also possible to use a Dynamic Descriptor with SEPA.

Reporting

A reconciliation file is available to download by merchants. This allows merchant to have the most up-to-date status for their transactions. For more information about the reconciliation file see chapter Data Reconciliation or please contact Wirecard Merchant Support.

Bank Data Validation

The Wirecard Payment Gateway validates the consumer’s bank data, to ensure transactions with faulty bank data are not forwarded to the bank for processing.

IBAN Validation

Wirecard Payment Gateway validates the consumer’s IBAN in the following manner:

The validity of the country code within the IBAN
The validity of the country code within the SEPA scheme
The structure of the IBAN including:
- the length of the IBAN based on the issuing country
- the position of the bank identifier
- the position of the country code
- the position of the check digits
Check digit verification

BIC Validation

Wirecard Payment Gateway validates the consumer’s BIC in the following manner:

The length of the BIC may only be either 8 or 11 characters
The validity of the BIC within the SEPA scheme

SEPA IBAN Only

According to the EU’s SEPA migration directive, as of February 1, 2016, the BIC is no longer required to process cross-border SEPA Direct Debit and SEPA Credit Transfer transactions. The merchant may still submit the BIC along with the IBAN, however, it is no longer a mandatory field.

Depending on the payment method, some providers may still use the BIC as support functionality.

Return Codes

SEPA transactions may be returned by either the merchant or consumer bank for several reasons described below.

SEPA Return Codes
EE Status Code	Reason Name	Reason Description
201.0001	Return reason not specified	Reason for the return was not specified by the debtor bank
201.0002	Debtor / Account holder deceased	Debtor or account holder is deceased
201.0003	Debtor bank details incorrect	Debtor bank details are incorrect
201.0004	Debtor account closed	Debtor account is closed
201.0005	Insufficient funds on debtor account	There are insufficient funds on the debtor bank account
201.0006	Mandate not valid, not active or cancelled	Mandate reference provided is not valid, not active or cancelled
201.0008	Transaction forbidden	The payment type is not allowed for this type of account
201.0009	Invalid Bank Operation Code	Invalid transaction code or incorrect data format (issued by debtor bank)
201.0010	Duplicate transaction on debtor account	A duplicate transaction has been found on the debtor account
201.0011	creditor address missing	Missing creditor address (only in the case of direct debit)
201.0012	missing mandatory mandate information	Incomplete or incorrect mandatory information on the mandate (issued by debtor bank)
201.0013	Invalid File Format	Data format is invalid for any reason other than grouping indicator
201.0014	Refund request by End-Customer (payer)	A refund has been requested by the debtor (payer)
201.0015	Regulatory reasons	Refusal due to regulatory reasons
201.0016	Invalid due date or execution date	The due date or execution date specified in the request is not within the limits required by the payment method
201.0017	Incorrect BIC	Bank Identifier Code (BIC) is incorrect or invalid
201.0018	Amendment of mandate reference	There has been an amendment to the mandate reference provided
201.0019	Returned due to technical problems	The transaction has been returned due to technical problems.