API Payments – Migration from Dutch Direct Debit and ELV to SEPA Direct Debit Version: 1.00 Contact details Simon Carmiggeltstraat 6-50 1011 DJ Amsterdam P.O. Box 10095 1001 EB Amsterdam The Netherlands T +31 20 240 1240 E support@adyen.
Table of Contents 1. Introduction...............................................................................................................................................................................................................................................................................................................................................4 2. Updates to One-Off Dutch Direct Debit Payments.............................................................................................
Changelog Version Date Changes 1.00 2013-12-21 • Manual created Audience This is a technical manual aimed at IT personnel involved in integrating merchants' systems with those at Adyen. General Tips/Warnings Defensive Programming Adyen strongly recommends the use of “defensive programming” when integrating with the Adyen Services. This implies that automated decisions programmed into your systems should be defaulted to non-delivery of products and services.
1. Introduction The European Payments Council (EPC) has mandated that as of 1st February 2014, all merchants that are currently processing ELV or Incasso (Dutch Direct Debit) payments, must have implemented SEPA Direct Debits (SDD). The purpose of this manual is to provide you with some guidance on updating your API payment integration to SEPA Direct Debit from: 1. Dutch Direct Debit (directdebit_NL) 2.
2. Updates to One-Off Dutch Direct Debit Payments If you are processing Incasso payments, the payment request has to be be updated to accommodate the new SDD requirements, the bankAccount container will no longer include bankAccountNumber, this has been replaced by: • iban The IBAN. • bic The unique identification code for both financial and non-financial institutions. • BankName (optional) The name of the bank.
2.2. Sample sepadirectdebit authorise Payment Request EUR PAGE 72.3. Sample Oneoff sepadirectdebit Authorise Response sepadirectdebit.
3. Updates to One-Off ELV Payments If you are processing ELV payments, the payment request has to be be updated to accommodate the new SDD requirements, the ELV container will be removed and replaced by the bankAccount container. • BankName (optional) The name of the bank. In addition to adding the bankaccount container, you must also include: • selectedBrand (mandatory) The value should be sepadirectdebit. There is also a change to the flow of SDD transactions: 1.
3.2. Sample sepadirectdebit authorise Payment Request EUR PAGE 104. Updates to Recurring API Payment Requests The only change for Recurring API payment requests is the addition of the following mandatory field: • 4.1. selectedBrand (mandatory) The value should be sepadirectdebit. Sample sepadirectdebit recurring Payment Request PAGE 115. API Payment Response and Notifications The synchronous API response will contain key/value pair responses containing pertinent information regarding the SDD payment. 5.1. Sample sepadirectdebit Authorise Response PAGE 125.2. Sample sepadirectdebit Pending Notification 9913856361050084 Test Payment Reference TestMerchant 2013-11-28 11:55:05.
5.3. Sample sepadirectdebit Standard Notification 9913856361050084 Test Payment Reference TestMerchant 2013-11-28 11:55:05.934 CET AUTHORISATION 1500 EUR true sepadirectdebit
5.4. Sample sepadirectdebit Extended Notification 9913856361050084 Test Payment Reference TestMerchant 2013-11-28 11:55:05.
6. SDD Settlement Timeline Prior to initiating the DD, you will need to inform the customer that the payment is due. 6.1. Core Event: SDD First SDD Recurring Pre-notification (T-14) T-5 (T-14) T-2 Submit SDD instructions (Moment of payment request) T-5 T-2 Latest moment to revoke (cancel) SDD T-1 T-1 SDD instruction processed by bank T T Reconciliation by Adyen PSP T+1 T+1 6.2. Core 1 Core 1 is automatically used in Germany, Spain and Austria.
7. SDD Chargebacks The chargeback process is standardised for all SEPA DD variants. The SDD schemes ensure more protection and refund rights for consumers: • The shopper can have the authorised SEPA DD payment returned within 8 weeks. • The shopper has 13 months to report incorrect unauthorised SEPA DD with their bank and request a reversal, as the debit was not authorised or the mandate was expired or had been cancelled. Both scenarios result in a payment status of Chargeback.
Appendix A: TEST and LIVE URLs TEST URLs SOAP REST Payment Service https://pal-test.adyen.com/pal/servlet/soap/Payment Payment Service WSDL https://pal-test.adyen.com/pal/Payment.wsdl HTTP Adapter (Browser) https://pal-test.adyen.com/pal/adapter/httppost?Payment Authorisation https://pal-test.adyen.com/pal/adapter/httppost?Payment.authorise Test Capture https://pal-test.adyen.com/pal/adapter/httppost?Payment.capture Test Refund https://pal-test.adyen.com/pal/adapter/httppost?Payment.
