Lemonway changelog
Lemonway changelog
www.lemonway.com

NEW : Processing of incoming transactions on Saturdays

 

New Feature

  

As of 26/11/2022, Lemonway will start processing incoming & unpaid transactions received on Fridays every Saturday morning. This processing concerns only transactions that do not require manual intervention.

It concerns all incoming flows: transfers, direct debits and checks as well as the associated unpaid transactions.

It depends on the availability of the bank statements (some bank communicates the statements on Monday morning: out of scope of this improvement).

Transactions received on Friday and that requires manual intervention will be processed by Lemonway' Payments teams on Monday morning.

The services associated with the processing of transfers (pending list) are out of the scope of this improvement.

Identified impact: if you have subscribed to receive notifications, you will receive them on Saturday. We advise you to check that this does not impact your processing.

Discover our Buy Now Pay Later solution designed for B2C Marketplaces

 

New Feature

  

Your customers can now initiate Buy Now Pay Later payments on your platform and pay in several instalments or deferred.

What are the benefits for you:

  • Improved conversion rates
  • Average basket increase
  • Customer loyalty
  • Business expansion
  • Easy & fast integration

➡️ Watch the demo for a full view of the customer journey

Important notification for your Tech/IT department

 

Critical

  

As part of our continued commitment to protect our environment and your data, and to remain compliant in the continually evolving world of security it is necessary for us to make modifications to the security of our API and dashboards.

As the security standards have evolved, we are required to remove two outdated ciphers from our API

TLSECDHERSAWITHAES256CBCSHA384 TLSECDHERSAWITHAES128CBCSHA256

This will mean we will only accept connections from clients using the following

PCI DSS changelog.PNG

For compliance reasons this change will take effect as from 8th August 2022. Please make sure your systems can use the supported protocols and ciphers, especially when using older libraries.

Our teams remain at your disposal to answer your questions via our dedicated contact form.

Discover your new dashboard design

 

Dashboard

  

We are happy to present you the new dashboard design revamped. Dashboard has been given a fresh new look to make monitoring, reporting and navigation easier!

Dashboard-Rebranding-2.jpg

Health Insurance Cards no longer accepted for KYC

 

Critical

  

Today we're talking KYC!

In accordance with applicable laws and regulation, we hereby inform you that Lemonway will no longer accept Health Insurance Cards for KYC purposes from June 1st 2022.

As we understand that this might impact your current process and that time is needed to make the relevant changes, Health Insurance Cards will continue to be accepted until the due date.

The complete list of required documents is available in our Support Center for France and other EU countries.

Updates on SDD process

 

API Method Update

 

Fix

  

We are happy to announce 2 improvements regarding our SEPA Direct Debit process:

  • For all SEPA Direct Debits: we fixed a small issue in the REST API. The field scheduledDatewill now correctly be filled in by Lemonway in the answer of the API call Request a SEPA Direct Debit (SDD)

  • For B2B mandates on Italian bank accounts - first debit only: There is now an irreducible 2-week delay between first debit request & its execution date. Therefore, in case of asked collection date too early, Lemonway is updating the field scheduledDate in answer of the API call Request a SEPA Direct Debit (SDD)

Dashboard is now available in German

 

Dashboard

  

Dear German speaking partners, we are happy to announce that the dashboard has been translated in your language. In addition to English, Spanish, French and Italian, it is now available in image.png German!

image.png

Spanish Virtual IBAN now available

 

New Feature

 

API Method Update

 

Dashboard

  

Virtual IBANs can now be generated for Spainimage.png along with Belgium image.png,

France image.png, Italy image.png and Germany image.png

How to generate one ?

Via the Dashboard

  • Accounts > Account details > Payment methods > Virtual IBAN > + GENERATE A VIRTUAL IBAN

Via the API

  • API v2: Create Dedicated Virtual IBANs
  • API v1: CreateIBAN: Create a Dedicated Virtual IBAN

Get a better view on your activity with the Reports section

 

Dashboard

  

To help you get a better idea of your payment activity, you will now find in the Reports section some insightful information about Money-In, Money-Out, payment methods, commissions and chargebacks.

Charts will show you the overall trend and you will get more details on hover of each element. You will also be able to select your preferred time period and granularity (daily, weekly, monthly or yearly) for tailored analysis.

Please note that for performance matters, data cannot be streamed and will only be updated once a day (current day will not be displayed).

Please note that if you created specific roles for your users, you will have to add the Reports permission to their role.

Reports page screen.png

New information required for Recurring Card Payments

 

API Method Update

  

In order to always better protect your end-users against fraud, Le Groupement des cartes bancaires CB, also named 'GIE CB' which includes all French Issuing Banks, shared some new guidelines regarding recurring card payments.

First, how do recurring payments work?

In order to set up Card Recurring Payments, you necessarily take a first standard payment from your customer. It allows you to capture their card information and verify that the payer is indeed the cardholder (3-D Secure authentication). Once the first transaction is successfully completed, you are free to initiate the following recurring payments.

What changes?

  1. For the first Client Initiated Transaction of Recurring Payments, you will now be required to send the following additional information:

a. You will need to indicate that this first transaction is the one to initialize Recurring Payments

b. You will also need to communicate the average amount of the Ne Recurring Transactions if the amount of the Recurring Payments is higher than the one of the first transaction

  1. Considering the sensitivity of these transactions, 3-D Secure authentication will now be mandatory for the first client transaction (we will need to force 'CHALLENGE' and there will be no FRICTIONLESS).

How can you implement these changes?

To complete this information, 2 new parameters were integrated in API calls for Client Initiated Transactions – see API documentation links below

  • paymentPattern > Possibles values: Recurring or One_shot
  • recurringAvgAmount > to be completed if higher than totalAmount

API documentation:

SOAP: MoneyInWebInit - MoneyIn3DInit

REST: POST/v2/moneyins/card/webinit - POST/v2/moneyins/card/direct/3dinit