Date: Thu, 28 Mar 2024 19:28:44 +0100 (CET) Message-ID: <214737388.33512.1711650524333@atlf1p2.dc1lan.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_33511_2016024230.1711650524332" ------=_Part_33511_2016024230.1711650524332 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
More information
The plugin configuration is divided into several sections, accessible vi=
a the menu : Stores> Configuration> SALES&g=
t; Payment Methods
The Access key must be retrieved directly from=
your Payline administration center, if you need help, see this link &=
nbsp;What is=
the access key and where to find it?
Enter your merchant ID and your access key in the two corresponding fiel= ds. The plugin automatically detects for which environmen= t (certification or production) the parameters are intended, and offers add= itional fields for entering the parameters of the other environment.
When the parameters of the two environments are filled in, a button allo= ws you to indicate which environment to use.
When saving the authentication parameters, the plugin detects whether a = proxy is preventing connection to Payline (the library returns an error cod= e XXXXX, "could not connect to host"). If necessary, 4 fi= elds are displayed for entering the host and port of your internet proxy, a= s well as the authentication parameters with the latter.
The proxy is detected via the response of the getMerchantSettings web se=
rvice.
An XXXXX return code indicates a connection error to Payline, the additiona=
l message "could not connect to host" indicates the presence of a proxy.
The getMerchantSettings web service is called during the validation of t=
he form to check that the identifiers have been entered correctly and to de=
termine the environment.
Its response must be stored for the configuration of the means of payment.<=
/p>
The list of payment methods configured on your Payline account is automa=
tically imported when you save your authentication settings.
In this list:
Technical appendixThese contracts are entered in the<= span> selectedContractList <= /strong>list of the doWebPayment web service.
Increase your conversion rate by immediately allowing your buyers to ret=
ry payment after a failure.
Select from the displayed list the means of payment that will be offered fo=
r this retry.
Technical appendixThese contracts are entered in the<= span> secondSelectedContractList list of the doWebPayment<= /em> web service.
You can adjust the configurations= :
You find a detail of the parameters below.
The Payline plugin can be integrated into the Magento 2 checkout in 3 wa= ys:
When do you want your buyers to be debited?
Technical appendixPayment on order corresponds to
Activate this option to offer payment data recording to your buyers.
Technical appendixThe activation of One Click corresp= onds to the valuation of the buyer.walletId= em> parameter of = span>doWebPayment , a&nbs= p;unique identifier gene= rated by the plugin and associated with the buyer account.
This payment method allows merchan= ts to offer buyers payment for purchases in several installments in redirec= t mode only.
The default setting is proposed as shown below:
Define here the correspondence between the result of the payment returne=
d by Payline, and the status of the order.
The proces=
s can suggest various results: