SEPA Direct Debit Model A
With SEPA Direct Debit Model A you allow PPRO to collect and store the mandates. The consumer can consent/reject a mandate on a mandate page. PPRO also generates and sends out pre-notification emails.
Session Timeout
A SEPA Direct Debit Model A will timeout after 1 day.
Integration
Specific input parameters for the TRANSACTION call
One-off payments or first payment in recurring series
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.sequencetype | M | string | 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 |
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 |
Follow-up payment in recurring series (Model A)
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.sequencetype | O | ascii | Sequence type of the direct debit. Defaults to oneOff . Valid values:- recurring : A direct debit in a series of recurring ones- f inal : The last direct debit in a series of recurring ones |
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
accountholdername
parameter.
Specific output parameters for the TRANSACTION call
This payment method will emit the SPECOUT.PAYMENTPURPOSE output parameter.
Field Name | Type | Description |
---|---|---|
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) |
SPECOUT.MANDATESIGNATUREDATE | date | A UTC date (YYYY-MM-DD ) on which the SEPA mandate was signed |
For standard output parameters, see Output parameters for the TRANSACTION call.
TRANSACTION call input
tag=sepaddmodela
&txtype=TRANSACTION
&countrycode=DE
¤cy=EUR
&amount=1055
&merchanttxid=TuAgXJ65r4mf
&login=johndoe
&password=wXBrpVporFVjGO4R
&contractid=JOHNDOECONTRACT
&channel=testchannel
&merchantredirecturl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Flanding.php
¬ificationurl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Fnotification.php
&specin.dynamicdescriptor=DynDescriptor
&accountholdername=John+Doe
&specin.iban=DE12500105170648489890
&specin.email=test%40gmx.de
&specin.sequencetype=oneOff
&preferredlanguage=en
&specin.mandatereference=
&specin.mandatesignaturedate=
&returnmode=urlencodeext
TRANSACTION call output
REQUESTSTATUS=SUCCEEDED
&STATUS=SUCCEEDED
&TXID=638853265
&ERRMSG=
&CHANNEL=testchannel
&TAG=sepaddmodela
&PAYMENTGUARANTEE=NONE
&REDIRECTSECRET=TIO7yxwkZuWc1gQ6sCoiuiqwsOiQS8JW
&SPECOUT.MANDATEREFERENCE=3AOUAA9
&SPECOUT.PAYMENTPURPOSE=DynDescriptor
&SPECOUT.PLANNEDDUEDATE=2020-04-16
&SPECOUT.MANDATESIGNATUREDATE=2020-04-10
&SPECOUT.SRCCOUNTRY=DE
&SPECOUT.SRCIBAN=DE12500105170648489890
Additional Information
- Model A supports ready for settlement in general. Be aware that there is always a risk of chargeback, even when funds have been received for a transaction. We communicate these chargebacks to you via the SFTP reporting interface. See SFTP access to reconciliation files. Besides this inherent risk, ready for settlement works exactly as it does for other payment methods.
- Model A supports various sequence types to allow recurring direct debit. This decision defines whether the transaction is synchronous or not.
- For sequence types
oneOff
and first: like in most payment methods, you must redirect the consumer to the redirect URL received in the response. In case the consumer accepts the SEPA direct debit mandate, send a copy of the mandate to the address provided inspecin.email
. This changes the state of the transaction to SUCCEEDED. For sequence typefirst
, store the outputSPECOUT.MANDATEREFERENCE
to send the same reference on recurring payments. - For sequence types
recurring
andfinal
: the previously-stored mandate reference must be passed as specin.mandatereference. The parameterspecin.mandatesignaturedate
must be the date of the initial transaction (sequence typefirst
), i.e. the day on which the mandate was signed. Both are mandatory input and serve as proof that the consumer signed the recurring payment mandate. If all input is valid, a copy of the mandate will be sent to the address provided inspecin.email
and the transaction call returns the state SUCCEEDED immediately. - Transactions may change from any state, especially from FAILED to a SUCCEEDED state at any time. SUCCEEDED itself is considered a stable state (see also Important note about transaction states).
- You are informed through PPRO’s processing files when the funds are received or a chargeback occurred.
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
Can I customize the PPRO mandate page?
No. PPRO does not offer any customization options for the mandate page. If you need to use a custom mandate page, we recommend you use SEPA Direct Debit Model C.
Updated about 1 year ago