SEPA Direct Debit Model C
With SEPA Direct Debit Model C you collect and store the mandates yourself. You also generate and send out pre-notification emails
Session Timeout
A SEPA Direct Debit Model C transaction has no timeout, the technical success or failure of the transaction is known immediately.
SEPA Direct Debit Model C Integration
Specific input parameters for the TRANSACTION call
| Field Name | M/O/C | Type | Description |
|---|---|---|---|
specin.email | M | string | Consumer’s email address. It is required to send the direct debit mandate. |
specin.iban | M | ascii | Valid IBAN |
specin.mandatereference | M | ascii | Mandate reference as returned on the first transaction in the sequence (in SPECOUT.MANDATEREFERENCE) |
specin.mandatesignaturedate | M | date | The date of the initial transaction. Format: YYYY-MM-DD. The date can be taken from the finaltimestamp of the SUCCEEDED notification for the first transaction in the sequence |
specin.mandateurl | M | ascii | A valid URL pointing to the SEPA mandate. PPRO's risk and compliance department needs to be able o access it. |
specin.sequencetype | O | ascii | Sequence type of the direct debit. Defaults to oneOff. Valid values:- oneOff: The direct debit is executed once- first: The first direct debit in a series of recurring ones- recurring: Direct debit in a series of recurring ones- final: Last direct debit in a series of recurring direct debits. |
specin.debtoraddress | C | string | The full address of the party to be debited (eg: shopper). Up to two lines are supported, each separated by a #. Ex: Street 123#43212 City This parameter is only required for the following countries; the parameter is not required for other countries. Andorra, French Polynesia, French Southern Territories, Gibraltar, Great Britain, Guernsey, Holy See (Vatican City State), Isle of Man, Jersey, Monaco, New Caledonia, Saint Barthélemy, Saint Pierre and Miquelon, San Marino, Switzerland, Wallis and Futuna |
For standard input parameters, see Input parameters for the TRANSACTION call.
This payment method supports the dynamic descriptor field (see The dynamic descriptor).
Important
This payment method requires the real account holder value for the
accountholdernameparameter.
Specific output parameters for the TRANSACTION call
This payment method will emit the SPECOUT.PAYMENTPURPOSE output parameter.
| Field Name | Type | Description |
|---|---|---|
SPECOUT.MANDATEREFERENCE | ascii | The reference provided in specin.mandatereference |
SPECOUT.PLANNEDDUEDATE | date | A UTC date (YYYY-MM-DD) with the planned due date (the earliest day that the funds will be debited from the consumer’s account) |
For standard output parameters, see Output parameters for the TRANSACTION call.
TRANSACTION call input
tag=sepaddmodelc
&txtype=TRANSACTION
&countrycode=DE
¤cy=EUR
&amount=1055
&merchanttxid=U9Mu5YzHHHGn
&login=johndoe
&password=wXBrpVporFVjGO4R
&contractid=JOHNDOECONTRACT
&channel=testchannel
&merchantredirecturl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Flanding.php
¬ificationurl=https%3A%2F%2Fseewhatididhere.com%2Fwork%2Fppro2%2Fnotification.php
&specin.dynamicdescriptor=DynDescriptor
&accountholdername=Tester+Williams
&specin.iban=DE12500105170648489890
&specin.mandateurl=https%3A%2F%2Fseewhatididhere.com%2Fwork%2Fppro2%2Fnotifications.php
&specin.mandatereference=1245&specin.mandatesignaturedate=2020-04-14
&specin.sequencetype=oneOff
&specin.email=test%40gmx.de
&specin.consumerid=XYZ321
&returnmode=urlencodeext
TRANSACTION call output
STATUS=SUCCEEDED
&TXID=639445669
&MERCHANTTXID=U9Mu5YzHHHGn
&RAND2510950350=554f8c05ffea71e6ce547255f06c1fad1fa213f2
&FUNDSSTATUS=NOT_EXPECTED
&FLAGS=
&ERRMSG=
&CHANNEL=testchannel
&TAG=sepaddmodelc
&REDIRECTSECRET=vwah6euxmkKEi4Q5zC4D5P1TC8J1LO2e
&SPECOUT.MANDATEREFERENCE=1245
&SPECOUT.PAYMENTPURPOSE=DynDescriptor
&SPECOUT.PLANNEDDUEDATE=2020-04-17
&SPECOUT.SRCCOUNTRY=DE
&SPECOUT.SRCIBAN=DE12500105170648489890
Additional Information
- SEPA Direct Debit Model C is synchronous in nature, transactions fail or succeed immediately.
- SEPA Direct Debit Model C supports various sequence types to allow recurring direct debits.
Warning
We don't advise using test data to test SEPA Direct Debit transactions in PPRO’s live environment. Any technically succeeded SEPA Direct Debit transaction(s) with this data will lead to chargebacks that cannot be prevented, refunded, or reversed.
To avoid unnecessary chargebacks, we highly recommend using real consumer data with a real bank account for live testing SEPA Direct Debit.
FAQ
What needs to be shown on a mandate?
See the guidelines as defined by the European Payments Council. Not meeting the basic mandate design requirements will lead to a chargeback if the mandate is at all created.
How long do I need to store a mandate?
A chargeback is permissible for up to 13 months after the mandate is signed. It needs to be available for recall on request during at least the13 month period. If possible, five years is recommended.
Which format must the stored mandate be?
An HTML page showing evidence of a consumer’s e-signature, date, mandate reference, etc. is sufficient (see requirements above). For paper mandates, a PDF copy is sufficient.
Can I put the mandate behind a protected URL?
Yes, but make sure you have credentials ready for PPRO on short notice to access the mandate in case of a request from one of our partner banks for proof of a mandate’s existence.
Updated 9 months ago