ELV

De Documentation Mercanet
Aller à : navigation, rechercher

Introduction

Purpose of the document

The purpose of the present document is to help merchants implement the ELV payment method.
Info.png to know

All terms, acronyms, expressions specific to Mercanet Acceptance
Solution context are defined in the document : GLOSSAIRE.
Please refer to them as appropriate.

General principle

ELV makes it possible to pay for your purchases by electronic bank transfer. When the Internet user chooses to pay for their order using ELV, they must enter the credential of the bank account to debit.
Once the form is submitted, the credentials are validated and the direct debit order is sent.
To use ELV, the Internet user does not need to create a specific account; all that is required is that their bank allows ELV payments.

How it works

Interface availability

Interface (mode) Payment means

Mercanet Essentiel

Mercanet Gestion Plus

Mercanet Batch

Mercanet  walletpage

POST

JSON

SOAP

SOAP

JSON

BATCH

POST

JSON

SOAP

ELV

-

-

-

-

Payment procedures

User view

The following schema illustrates the steps that the internet users follow to make an ELV payment:
ELV1.PNG
Sequence of Mercanet payment screens

 Mercanet Payment

  The payment process for Mercanet is described below
Elv2.PNG
Mercanet Payment flow chart

Stage

Description

1

The Internet user confirms his basket. The merchant initializes a payment session and redirects the Internet user to the payment method selection page. The Internet user selects ELV as the payment method

2

The Internet user confirms their basket and is redirected towards the pages for the Mercanet Payment Web solution.

3

The Internet user complete the form with his information (bank code, account number, first name, name). After user validation, Mercanet make a coherence control of the data entered by the internet user and process the payment.

4

The authorisation request is sent to the Acquirer

5

The response to the authorisation request is sent between the Acquirer and the Issuer, Mercanet informs the Merchant and the Internet user (if necessary) of the result

6

The transfer of funds is completed between the Issuer and the Acquirer, the Merchant may be informed of this action by way of reporting tools

Payment pages

Elv3.PNG
Choice of payment method
Elv4.PNG
 Identification of the Internet user
Elv5.PNG
Payment ticket

Functionalities

Type of functionality 

Availability 

Note 

Payment channel

Internet

Mandatory payment channel

MOTO (VPC )

Payment methods

Immediate payment

Payment at the end of the day

Deferred payment

Payment on dispatch

Payment in instalments

N/A

Subscription payments (recurring)

N/A

Batch payment

N/A

"One-click" payment

N/A

Payment in different currencies

Multi-currency acceptance

N/A

EUR only

Multi-currency settlement

N/A

EUR only

Fraud management

  Please refer to the following documents : guide contrôles anti-fraude

Merchant reporting

Transaction log

Operations log

Transaction reconciliation log

-

Outstanding payment reconciliation log

-

Extranet

Checkout operation

Cancellation

Available for a total or partial amount

Validation

-

Refund

Available for a total or partial amount

Duplication

-

Capture mode

Cancellation mode

Default mode

Validation mode

-

Immediate mode

Life cycle


Elv6.PNG
Figure 1 Life cycle for ELV transactions

Transfer request

A transfer request performed during the online procedure cannot be revoked. However, the transfer may not take place under some rare circumstances described below.  

Reconciliation and outstanding payments

A transaction in the CAPTURED status is considered as reconciled. There are no reconciliation and outstanding payments for an ELV payment.

Integration with Mercanet Essentiel

Payment request

No specific information is necessary to submit an ELV payment request.

Field name 

Notes/rules

Setting example

paymentMeanBrandList

Optional field :  as on Payment pages accepted payment means for will be displayed

ELV

mandateId

Optional field : mandateId field can be filled out by the merchant, if merchant wants to give his Unique Mandate Reference

037145789646091

 

Response

The following fields have a specific behaviour:

Field name 

Notes/rules

Setting example

paymentMeanType

DIRECT_DEBIT

paymentMeanBrand

ELV

paymentPattern

ONE_SHOT

Integration with Mercanet Gestion Plus

Payment request

It is possible to create ELV payments using the DirectDebitOrder function on the Checkout service. For an ELV, the following fields must be filled out:

Field name 

Notes/rules

Setting example

customerBankAccountType

NATIONAL_DEU value means that only Bank code and account number information are managed.

NATIONAL_DEU

paymentMeanBrand

Identifies the payment means.

ELV

holderContact.firstname

First Name information is required.

Peter

holderContact.lastName

Last Name information is required.

Falk

mandateId

Optional field : mandateId field can be filled out by the merchant, if merchant wants to give his Unique Mandate Reference

037145789646091

customerBankCode

The customer bank code

50050000

customerAccount

The customer bank account number

0043028661

Response

No specific information is necessary to submit an ELV payment request

Appendices

Acquirer response codes

Response codes returned by the ELV server.

Code

Description

00

Transaction approved or processed successfully

03

Non-existent/invalid ELV contract

05

Transaction refused.

14

Invalid bank details

17

Transaction cancelled by the Internet user

25

Non-existent transaction

30

Format error

60

Transaction processing

63

Security error

90

Service temporarily unavailable

97

Transaction expired