EasyCollect is a system provided by Worldline to manage SEPA mandates for direct debits and also to handle direct debit payments themself.
SEPA Mandates can be approved with an One-Time-password (OTP) which can be provideed to the consumer either via SMS/text message or via email.
Transaction procedure of a direct debit payment on the Internet
In order to pay with a direct debit, the customer first needs to approve a SEPA mandate. Therefore the customer needs to be in session and approve the mandate creation via OTP.
Using this SEPA mandate the merchant can create later SEPA direct debit payments.
Logo
Info
The Paygate enables you to handle the direct debit mandates and payments popular with customers – and is fully compatible with SEPA.
Chart of process flow: Mandate approval via form interface / Direct Debit via Server-2-Server connection
Process flow of Mandate approval via form interface / Direct Debit via Server-2-Server connection
Mandate creation with customer approval via OTP
The interface of the Paygate form to approve a SEPA mandate is MandateForm.aspx.
This section explains the parametersfor Mandate Approval.
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.
Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).
To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.
Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.
Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.
Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.
Common notes:
We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate
However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.
Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.
Common notes:
We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate
However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.
Complete URL which Paygatecalls up in order to notify the shop about the payment result. The URL may be called up only via port 443. It may not contain parameters: Use the UserData parameter instead.
Common notes:
Before follow-up actions (capture / credit / reversal) are carried out on an existing transaction, the first Notify must have been answered by the shop.
Fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.
Key
Format
CND
Description
Beschreibung
RefNr
Key
Format
CND
Description
Beschreibung
Consumer Data
EMail
ans..254
M
Email address of the customer
FirstName
ans..50
M
First name
LastName
ans..50
M
Last name
bdStreet
ans..50
M
Street
bdStreetNr
ans..50
M
Street number
bdZip
ans..50
M
Postcode
bdCity
ans..50
M
Town
bdCountryCode
an..2
M
Country-Code, ISO-3166
phone
ans..50
M
Mobile phone of the customer; an OTP value is sent to this mobile number in case agreementScheme=SMS is used
bdGender
a1
M
M=Male
F=Female
Mandate Data
creditorid
ans..50
M
SEPA Creditor Identifier (SCI).
contractId
ans..50
O
Underlying contract identifier
contractDescription
ans..50
O
Underlying contract description
agreementScheme
enum
O
Value
SMS (default)
EMAIL
DocumentSignature
enum
O
The stamp is added on the last page of the mandate document.
Value
true (default)
The last page of the document will contain the stamp in the middle of the last page.
false
No stamp is added
GoogleAnalyticsConsent
enum
O
Debtor consent to use google analytics
Value
true (default)
false
SignatureBySca
enum
O
Value
true (default)
false
Sps
enum
O
Allows to identify that WS call comes from SPS
Value
true (default)
WS call comes from SPS
false
WS call does not come from SPS
Validation
enum
O
If Validation = TRUE --> ORG If Validation = FALSE --> OTU
"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.
The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.
General parameters to create new SEPA Mandates approved with OTP
The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. mid, RefNr) should not be checked case-sentive
"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.
The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.
General results parameters for URLNotify, URLSuccess and URLFailure
pls. be prepared to receive additional parameters at any time and do not check the order of parameters