About EasyCollect

General information about EasyCollect

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 enables you to handle the direct debit mandates and payments popular with customers – and is fully compatible with SEPA.

TypePayments by Direct Debit




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


interface


Mandate creation with customer approval via OTP

The interface of the form to approve a SEPA mandate is MandateForm.aspx.

MandateForm.aspx

This section explains the parameters for Mandate Approval.


Key

Format

CND

Description

TransID

ans..35

M

TransactionID which should be unique for each payment.

When using auto-mandate (filling-in of MandateID with TransID or RefNr) the permitted character set is that of the MandateID parameter.

Account

ans..12

O

Within several EasyCollect accounts can be stored on one MerchantID and controlled by the parameter Account. Each account relates to a specific creditor configuration. By default, first entry will be used. The setup must be agreed with .

Key

Format

CND

Description




Consumer Data
EMailans..254OEmail address of the customer
FirstNameans..50OFirst name
LastNameans..50OLast name
companyNameans..50OName of the company
bdStreetans..50MStreet
bdStreetNrans..50MStreet number
bdZipans..50MPostcode
bdCityans..50MTown
bdCountryCodea..3MCountry code 2 or 3 characters according to ISO 3166
phoneans..50OMobile phone of the customer; an OTP value is sent to this mobile number in case agreementScheme=SMS is used
bdGendera1O
  • M=Male
  • F=Female



Mandate Data
contractIdans..50O

Underlying contract identifier

contractDescriptionans..50OUnderlying contract description
businessIdentifierans..50OUnique SIREN Id of the merchant
agreementSchemeenumO

The way how the OneTimePassword (OTP) will be forwarded to the customer.

Value
SMS (default)Given phone number (phone)
EMAILGiven email address (EMail)
DocumentSignatureenumO

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.
falseNo stamp is added
GoogleAnalyticsConsentenumO

Debtor consent to use google analytics

Value
true (default)
false
SignatureByScaenumO

If "true" customer will be authenticated by AccountIdentificationService.

Value
true
false (default)
SpsenumO

Allows to identify that WS call comes from SPS

Value
true (default)WS call comes from SPS
falseWS call does not come from SPS
ValidationenumO

If Validation = TRUE --> ORG / If Validation = FALSE --> OTU

Value
true (default)
false
customerTypeenumO

Type of customer

Value
KNOWNKnown customer
PROSPECTUnknown customer
MandateIDans..35O

Predefined mandate id. The mandate itself will use this mandate id.

Pattern: ^[a-zA-Z\+\?\(\)\-\s:/.,_'0-9] {1,35}$

MdtSeqTypeenumO

Indicates whether the mandate is a one-off mandate or a mandate for recurring direct debits.

There is no default. The default value depends on merchant configuration.

Value
OOFFone-off mandate
RCURrecurring mandate
MdtTypeenumO

Indicates whether the mandate is a business-to-business mandate or a customer-to-business mandate.

There is no default. The default value depends on merchant configuration.

Value
B2BBusiness-to-business mandate
COREBase mandate (customer-to-business)
EventTokenenumO

Creates a new mandate and first direct debit transaction simultaneously.

Value
MandateCreates only a mandate, no payment
PaymentCreates mandate and payment simultaneously
DueDateans10O

DueDate of this transaction. If missing the current day will be used.

Pattern: YYYY-MM-DD

CustomerIdan1..64O

Customer identifier submitted by the merchant during a payment

RemittanceInfoans..50O

The RemittanceInfo parameter is required for reconciliation purposes, providing essential customer-visible information on customer bank statements for better tracking and reporting.

  • Allowed characters: A..Za..z0..9 / - ? : ( ) . , +
  • Diactrics like äöüÄÖÜ, áéíóú, àèìòù, âêîôû, ... are not allowed
signerPositionOccupiedans..70O

Title of the signatory's position in the company

templateans..20O

Name of a XSLT template to get an individual layout for your EasyCollect form which matches with your shop layout. Details are available here: Corporate PayPage and templates.

General parameters to create new SEPA Mandates approved with OTP


Key

Format

CND

Description

MandateIDans..35O

Predefined mandate id. The mandate itself will use this mandate id.

Pattern: ^[a-zA-Z\+\?\(\)\-\s:/.,_'0-9] {1,35}$

General result parameters for URLNotify, URLSuccess and URLFailure