Functionality set-up - Sogenactif
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Functionality set-up
The PDFs available on the documentation website are generated using the information posted on the following documentation website: https://documentation.sogenactif.com. The information contained in these PDFs is basically identical to the one published on the above-mentioned documentation website. In the event of any inconsistency, the information on the said site will prevail over the information contained in the PDFs. These are joint documents from Société Générale and Worldline. Consequently, any reproduction (in whole or in part) and any use of the document, any circulation, distribution or quotation (for the sole purpose of fulfilling the electronic payment contract signed with Société Générale), without the prior written consent of Société Générale and Worldline are strictly forbidden.
Contents
1 Preamble......................................................................................................................................................................... 5
2 Introduction....................................................................................................................................................................5
3 Availability of means of payment by interface.......................................................................................................... 5
4 Features setup................................................................................................................................................................ 6
4.1 Transaction identification mode...............................................................................................................................6
4.1.1 Identification at creation................................................................................................................................... 7
4.1.2 Cash management identification....................................................................................................................... 8
4.1.3 Identification in reporting................................................................................................................................. 9
4.2 Paypages management..............................................................................................................................................9
4.2.1 Customisation of pages..................................................................................................................................... 9
4.2.2 Displaying the means of payment..................................................................................................................... 9
4.2.3 Displaying the ticket by Sogenactif.................................................................................................................10
4.2.4 New payment attempt...................................................................................................................................... 10
4.2.5 Duration of time on payment pages................................................................................................................11
4.2.6 Displaying the webshop name.........................................................................................................................12
4.2.7 Entry of card number in seperate blocks........................................................................................................12
4.2.8 Displaying the error page during initialisation..............................................................................................13
4.2.9 iFrame tag....................................................................................................................................................... 14
4.3 Payment channel.....................................................................................................................................................14
4.3.1 Internet............................................................................................................................................................. 14
4.3.2 MOTO.............................................................................................................................................................. 15
4.3.3 IVR................................................................................................................................................................... 15
4.3.4 Mobile application...........................................................................................................................................15
4.4 Payment collecting methods...................................................................................................................................16
4.4.1 End of day payment.........................................................................................................................................16
4.4.2 Deferred payment............................................................................................................................................ 16
4.4.3 Payment upon shipping................................................................................................................................... 17
4.4.4 Payment in instalments....................................................................................................................................17
4.4.5 Immediate payment..........................................................................................................................................17
4.4.6 Batch payment................................................................................................................................................. 18
4.4.7 Validity period of authorisation......................................................................................................................19
4.5 Payment in currencies............................................................................................................................................ 19
4.5.1 Multi currency acceptance.............................................................................................................................. 19
4.5.2 Currency settlement......................................................................................................................................... 20
4.5.3 Dynamic Currency Conversion (DCC)........................................................................................................... 21
4.6 3-D Secure.............................................................................................................................................................. 21
4.7 Recurring payment................................................................................................................................................. 21
4.7.1 Recurring payment via duplication.................................................................................................................22
4.7.2 Recurring payment via wallet......................................................................................................................... 22
4.8 One Clic Payment.................................................................................................................................................. 24
4.9 Cash management...................................................................................................................................................24
4.9.1 Cancellation..................................................................................................................................................... 24
4.9.2 Validation.........................................................................................................................................................25
4.9.3 Refund.............................................................................................................................................................. 27
4.9.4 Duplication...................................................................................................................................................... 28
4.9.5 Recycling..........................................................................................................................................................28
4.10 Online reporting....................................................................................................................................................29
4.10.1 Diagnostic...................................................................................................................................................... 29
4.10.2 Manual response............................................................................................................................................29
|
4.10.3 Automatic response........................................................................................................................................30
4.10.4 End of transaction confirmation sent to customer........................................................................................30
4.11 Reporting file........................................................................................................................................................31
4.12 Fraud..................................................................................................................................................................... 31
4.12.1 Fraud detection before collecting................................................................................................................. 31
4.12.2 Scoring result management........................................................................................................................... 32
4.12.3 Fraud diagnostic............................................................................................................................................33
4.12.4 Online fraud checks.......................................................................................................................................33
4.13 Honor All Cards................................................................................................................................................... 33
4.14 Country specific aspects.......................................................................................................................................34
4.14.1 France............................................................................................................................................................ 34
4.14.2 United Kingdom.............................................................................................................................................34
4.14.3 Belgium.......................................................................................................................................................... 35
5 Appendix....................................................................................................................................................................... 36
5.1 Appendix 1 : Summary chart of the features available by interface..................................................................... 36
5.2 Appendix 2 : Summary chart of the authorisation request validity and the cash management authorised
features by payment mean...................................................................................................................................... 38
5.3 Appendix 3 : Summary of the remittance hours per acquirer / private................................................................. 40
Functionality set-up - 04/11/2021
1 Preamble
The features listed below, integrated in the Sogenactif offer, are subject to the acceptance of Société Générale. They are therefore not
available for all merchants:
• payment in instalments
• selective 3-D Secure
• recurring payment
• duplication
2 Introduction
Sogenactif is a secure multi-channel e-commerce payment solution that complies with the PCI DSS standard. It allows you to accept and
manage payment transactions by taking into account business rules related to your activity (payment upon shipping, deferred payment,
recurring payment, payment in instalments, etc.).
This document is a Sogenactif feature setup guide. It explains how to use the available features in the various payment interfaces
(Sogenactif Paypage, Sogenactif Office Serveur). It also summarises feature availability in each of the interfaces and provides detailed
information on the potential impact on your Sogenactif and/or acquirer configuration (requiring verification with the latter).
Specific guides look at the setup of particular features:
• fraud fighting management: GoNoGo, Scoring
• means of payment implementation
• payment pages customisation
• One Clic
• recurring
3 Availability of means of payment by interface
Means of payment \ Sogenactif Sogenactif Office Sogenactif Office Sogenactif In- Sogenactif
Interfaces Paypage Serveur Batch App Walletpage
CB yes yes yes yes yes
Visa yes yes yes yes yes
MasterCard yes yes yes yes yes
American Express yes yes yes yes yes
VPay yes yes yes yes yes
Maestro yes yes yes yes yes
Visa Electron yes yes yes yes yes
Bancontact yes yes no yes yes
Bancontact mobile yes yes no yes no
Cadhoc yes yes no no no
(for future usage)
Carte Oney yes yes yes no yes
Carte Cadeau Oney yes yes no no no
Cetelem CPay (formerly yes no no no no
Cetelem Aurore)
Page 5 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS Paris
Functionality set-up - 04/11/2021
Means of payment \ Sogenactif Sogenactif Office Sogenactif Office Sogenactif In- Sogenactif
Interfaces Paypage Serveur Batch App Walletpage
Cetelem 3X 4X CB yes no no no yes
Cetelem Presto yes no no no no
Cofidis Pay 5x10x20x yes no no no no
Cofidis 3xCB yes no no no no
e-Chèques Vacances yes yes no no no
Facily Pay yes no no no no
Franfinance 3XWEB yes no no no no
(for future usage)
Franfinance 4XWEB yes no no no no
(for future usage)
iDEAL (old contracts) yes yes no no no
iDEAL (new contracts) yes no no no no
Masterpass yes yes no no no
(for future usage)
Oney 3x 4x yes no no no no
Paylib yes yes no no no
PayPal yes yes no no yes
SEPA Direct Debit (SDD) yes yes yes no no
Sofortüberweisung yes yes no no no
Means of payment available (yes) / Means of payment unavailable (no)
4 Features setup
Features activation may require configuration on the Sogenactif and/or acquirer side.
• Sogenactif configuration: activation or deactivation of the feature requires a change of configuration on the Sogenactif platform
and may involve, eventually, an amendment of the acceptance contract.
• Acquirer verification: activation or deactivation of the feature may involve an amendment of the acquisition contract.You need to
check with your acquirer.
Use of a feature may also involve the addition of certain parameters in the payment request and a possible change of connectors.
4.1 Transaction identification mode
Two transaction identification modes are available on Sogenactif 2.0 : the TransactionReference mode and the TransactionId mode.
The difference between the two modes is the scope of the identification: the TransactionReference must be unique throughout the life
of the store, whereas the TransactionId must be unique for the day.
An option also lets you choose the generation mode:
• you supply the transaction ID in the payment request or
• you let Sogenactif generate it automatically and you retrieve it in the response.
Note: the TransactionReference is the default identification mode, the transactionId 1.0 has been continued in
2.0 to facilitate the migration of 1.0 merchants to 2.0.
Page 6 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS Paris
Functionality set-up - 04/11/2021
4.1.1 Identification at creation
During the creation of a transaction and depending on the selected mode, Sogenactif accepts or rejects the creation and generates
complementary IDs.
There are various possible cases:
Table 1: Shop in TransactionReference mode - The merchant logs
into Sogenactif with a transactionReference that they generated
Data Transaction creation via:
Sogenactif Paypage Sogenactif Office Serveur Sogenactif Gestion
transactionReference supplied Standard use case Standard use case proposed by Sogenactif, can be
by the merchant amended and is displayed in red
transactionId supplied by the Rejection Code = 12 Rejection Code = 12 N/A
merchant
transactionId absent OK OK N/A
transactionReference absent Rejection Code = 12 Rejection Code = 12 Rejection Code = 12
Complementary reference s10TransactionId s10TransactionId s10TransactionId
generated by Sogenactif s10TransactionIdDate s10TransactionIdDate s10TransactionIdDate
Response content s10TransactionId s10TransactionId
s10TransactionIdDate s10TransactionIdDate
transactionReference transactionReference
Table 2: Shop in TransactionReference mode - The merchant
logs into Sogenactif without a TransactionReference (Tref auto)
Data Transaction creation via:
Sogenactif Paypage Sogenactif Office Serveur Sogenactif Gestion
transactionReference Standard use case N/A generated by Sogenactif and
generated by Sogenactif displayed in red
transactionId supplied by the Rejection Code = 12 N/A
merchant
transactionId absent OK N/A
transactionReference supplied Rejet Code = 12 Rejection Code = 12
by the merchant
Complementary reference transactionReference transactionReference
generated by Sogenactif s10TransactionId s10TransactionId
s10TransactionIdDate s10TransactionIdDate
Response content s10TransactionId
s10TransactionIdDate
transactionReference
Table 3: Shop in TransactionId mode - The merchant logs
into Sogenactif with a transactionId that they generated
Data Transaction creation via:
Sogenactif Paypage Sogenactif Office Serveur Sogenactif Gestion
transactionId supplied by the Standard use case Standard use case proposed by Sogenactif, can be
merchant amended and is displayed in
red
Page 7 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Data Transaction creation via:
Sogenactif Paypage Sogenactif Office Serveur Sogenactif Gestion
transactionId absent Rejection Code = 12 Rejection Code = 12 Rejection Code = 12
transactionReference supplied Rejection Code = 12 Rejection Code = 12 N/A
by the merchant
transactionReference absent OK OK N/A
Complementary reference transactionReference transactionReference transactionReference
generated by Sogenactif
Response content s10TransactionId s10TransactionId
s10TransactionIdDate s10TransactionIdDate
transactionReference transactionReference
Table 4: Shop in TransactionId mode- The merchant
logs into Sogenactif without a TransactionId (Tid auto)
Données Transaction creation via:
Sogenactif Paypage Sogenactif Office Serveur Sogenactif Gestion
transactionId generated by Standard use case N/A generated by Sogenactif and
Sogenactif displayed in red
transactionId supplied by the Rejection Code = 12 N/A
merchant
transactionReference supplied Rejection Code = 12 N/A
by the merchant
transactionReference absent OK N/A
Complementary reference s10TransactionId s10TransactionId
generated by Sogenactif s10TransactionIdDate s10TransactionIdDate
TransactionReference TransactionReference
Response content s10TransactionId
s10TransactionIdDate
transactionReference
4.1.2 Cash management identification
For cash management operations, the identification method of a transaction is not limited to the mode selected at creation.
The tables below outline the various possibilities.
Table 5: Shop in transactionReference mode - Original
transaction generated with a transactionReference
Data Cash management
transactionId supplied by the merchant OK
transactionReference supplied by the merchant OK
Consistent transactionReference and transactionId supplied by OK
the merchant
transactionReference and transactionId not referencing the same Rejection Code = 12
transaction supplied by the merchant
New transaction (duplication, recycling) See transaction creation table above
Page 8 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Table 6: Shop in transactionId mode - Original transaction generated with a transactionId
Data Cash management
transactionId supplied by the merchant OK
transactionReference supplied by the merchant OK
Consistent transactionReference and transactionId supplied by OK
the merchant
transactionReference and transactionId not referencing the same Rejection Code = 12
transaction supplied by the merchant
New transaction (duplication, recycling) See transaction creation table above
4.1.3 Identification in reporting
The s10TransactionId, s10TransactionIdDate and transactionReference fields appear in the transactions, operations, reconciliations
and chargebacks reports, whatever the transaction identification mode.
For duplication and recycling operations, the original transaction is identifiable via the s10FromTransactionId,
s10FromTransactionIdDate and fromTransactionReference fields of the transactions report.
4.2 Paypages management
4.2.1 Customisation of pages
For further details, please read the Sogenactif Paypage customisation guides.
4.2.2 Displaying the means of payment
The Sogenactif means of payment selection page is not displayed automatically. It can be managed either on your merchant website or
by Sogenactif. An option lets you automatically display this page by Sogenactif.
Attention: the display of the Sogenactif means of payment selection page is useless if the brand selection
option (MIF) is activated on your webshop and if you only offer the CB, VISA and Mastercard means of
payment.
However, in cases where the means of payment are not of the same type (card and Paypal for example), the selection page is displayed
automatically. When several means of payment are configured in your contract, you can filter those that will be displayed in the means
of payment selection page via the paymentMeanBrandList field:
• a single means of payment: the means of payment selection page is not displayed
• a list of means of payment: the means of payment are displayed in the feed order of the field
• blank field: all configured means of payment are displayed.
Sogenactif displays the means of payment matching simultaneously with
• the list of means of payment provided in your configuration
and
• the transaction data (checking the transaction currency, for example).
If no compatible means of payment is found, Sogenactif refuses the transaction.
Sample means of payment selection page:
Page 9 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Table 7: Summary
Available connectors Sogenactif Paypage
Sogenactif configuration YES Means of payment selection page not
displayed by default.
Acquirer checking NO
Parameter in the payment request YES paymentMeanBrandList: optional, choice
of means of payment to be displayed.
Possible values are listed in the data
dictionary.
4.2.3 Displaying the ticket by Sogenactif
The payment confirmation page or "payment ticket" is displayed by default by Sogenactif. However, you can choose to display it
yourself on your website by using the elements provided in the response message sent to the response URL (normalReturnUrl). You
can also decide dynamically, depending on the context of the transaction, not to display the ticket produced by Sogenactif.
Table 8: Summary
Available connectors Sogenactif Paypage
Sogenactif configuration YES Sogenactif ticket displayed by default
Acquirer checking NO
Parameter in the payment request YES paypageData.bypassReceiptPage:
indicator that lets you hide the ticket page
during payment.
4.2.4 New payment attempt
Usually, a new payment attempt is proposed to the customer in case of an invalid PAN. This additional option allows to extend the
new payment attempts on other cases of refusal :
• acquirer rejection (except fraud)
Page 10 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
• 3-D Secure authentication failure
• fraud engine rejection (except fraud)
The following message is displayed to your client:
Attention: if the payment returns an acquirer code 03 (invalid acceptor) then all the means of payment
attached to this same acquirer contract will not be offered during the new payment attempt.
Example of means of payment linked to a same acquiring contract: CB, Visa, Mastercard,
Paylib, Masterpass.
If no other means of payment can be offered, the payment will be definitely refused
witthout possible retry.
Table 9: Summary
Available connectors Sogenactif Paypage
Sogenactif configuration YES
Acquirer checking NO
Parameter in the payment request NO
4.2.5 Duration of time on payment pages
The customer has a 15-minute period of inactivity to carry out the payment. Beyond this allotted time, the user session expires and the
customer is not able to complete their purchase. This period is set to 15 minutes in accordance with the PCI DSS regulation (condition
8.1.7).
In addition to this regulatory limit, you have the option (business session timeout) of proposing a maximum period of time spent on the
Sogenactif payment pages. This period begins when the customer arrives on the Sogenactif payment pages.
Table 10: Summary
Available connectors Sogenactif Paypage
Page 11 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Sogenactif configuration YES
Acquirer checking NO
Parameter in the payment request NO
4.2.6 Displaying the webshop name
The name of the webshop configured in Sogenactif can be displayed in the banner on the payment page.
Table 11: Summary
Available connectors Sogenactif Paypage, Sogenactif
Walletpage
Sogenactif configuration YES Display of webshop name not activated by
default
Acquirer checking NO
Parameter in the payment request NO
4.2.7 Entry of card number in seperate blocks
Card number entry can be divided into blocks of four numbers. In the case of Amex and BCMC, this option is adapted to the length
of the card number.
Page 12 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Table 12: Summary
Available connectors Sogenactif Paypage, Sogenactif
Walletpage
Sogenactif configuration YES Card number entry in separate blocks
activated by default
Acquirer checking NO
Parameter in the payment request NO
4.2.8 Displaying the error page during initialisation
This page is displayed in the event of a payment initialisation error only via the POST connector (incorrectly formatted query for
example).
The redirection button redirects the user to the merchant’s website (with the manual response). The display of the redirection button
is configurable:
Table 13: Summary
Available connectors Sogenactif Paypage (POST)
Sogenactif configuration YES Parameter “Display the error page”
Page 13 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Acquirer checking NO
Parameter in the payment request YES manualErrorResponseInitPOST: merchant's URL to return to
the website in case of payment initialisation error.
At the same time, an automatic response can be sent. The sending of this automatic response is configurable:
Table 14: Summary
Available connectors Sogenactif Paypage (POST)
Sogenactif configuration YES Parameter “Display the error page”
Acquirer checking NO
Parameter in the payment request YES automaticErrorResponseInitPOST: merchant's URL to receive
the automatic response in case of payment initialisation error.
4.2.9 iFrame tag
Sogenactif payment pages can be integrated into a webshop page. This has no impact on your pages and you can use this feature without
any Sogenactif configuration.
For more information, please read the Sogenactif Paypage iFrame user guide.
Table 15: Summary
Available connectors Sogenactif Paypage, Sogenactif
Walletpage
Sogenactif configuration NO
Acquirer checking NO
Parameter in the payment request NO
4.3 Payment channel
To select your payment channel, you must fill in the orderChannel field in the payment request. This information is important because
it determines the rules of acceptance and acquisition for transaction processing.
4.3.1 Internet
To use the internet channel, you must subscribe to a VADS (secure distance selling) contract with the acquirer.
Table 16: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur Sogenactif Office Batch
Sogenactif configuration YES
Acquirer checking YES mandatory VADS contract
Parameter in the payment request YES orderChannel: INTERNET
Page 14 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
4.3.2 MOTO
When using the MOTO (Mail Order Telephone Order), MAIL_ORDER or TELEPHONE_ORDER channels, the transaction is
processed in distance selling acceptance. You have to subscribe to a VAD contract (distance selling) with the acquirer.
Tip: on connectors side, it is adviced using MAIL_ORDER or TELEPHONE_ORDER instead of MOTO.
Table 17: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch
Sogenactif configuration YES
Acquirer checking YES mandatory VAD contract supporting
MOTO
Parameter in the payment request YES orderChannel:
MOTO
TELEPHONE_ORDER
MAIL_ORDER
FAX
4.3.3 IVR
The IVR (Interactive Voice Response) channel is assimilated to the MOTO channel. The transaction is processed in distance selling
acceptance. You have to subscribe to a VAD contract (distance selling) with the acquirer, supporting MOTO channel.
Table 18: Summary
Available connectors Sogenactif Office Serveur, Sogenactif
Office Batch
Sogenactif configuration YES (MOTO channel configured)
Acquirer checking YES mandatory VAD contract supporting
MOTO
Parameter in the payment request YES orderChannel: IVR
4.3.4 Mobile application
Use of the mobile application does not require any acquirer configuration. To find out more about this connector, please read the
Sogenactif In-App JSON documentation.
Table 19: Summary
Available connectors Sogenactif In-App
Sogenactif configuration YES
Acquirer checking NO Assimilated to the internet channel
Parameter in the payment request YES orderChannel: INAPP
Page 15 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
4.4 Payment collecting methods
The paymentPattern, captureMode and captureDay fields let you set the payment collecting methods.
To find out more about the availability of these methods for each means of payment, please refer to their integration guides.
4.4.1 End of day payment
In the case of end-of-day payment, all transactions accepted during the day are sent for payment collection in the evening. This method
applies to the means of payment functioning on dual-message mode (a message for authorisation and a message for collection).
If this method is not supported by a specific means of payment,Sogenactif overrides the captureMode parameter with the default value
of the means of payment in question (for more information, please read the integration guides of the means of payment).
Table 20: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration NO
Acquirer checking NO
Parameter in the payment request YES • captureMode: AUTHOR_CAPTURE
• captureDay: 0 (0 deferred day,
evening collecting)
4.4.2 Deferred payment
In the case of deferred payment, payment collection of the transaction is done N days after online acceptance.
The validity period of the authorisations of the means of payment is set out in the contract between you and the acquirer (six days by
default for CB, VISA and Mastercard).
Depending on the validity period of the authorisation, the number of days of deferred collecting that is communicated in the payment
request can have an impact on the transaction life cycle:
• 1st case: the deferred payment is lower or equal to the validity period of the authorisation. The authorisation given by the acquirer is
always valid for the total amount of the initial transaction. If the transaction is not cancelled, it is paid on the date of the transaction
+N days.
• 3-D Secure specific case: in order to benefit from the liability shift during a 3-D Secure transaction, the deferred payment cannot
be greater than the maximum validity period of the authorisation given by the acquirer. If needed, Sogenactif overrides the payment
deferral if the value you enter is greater.
• 2nd case: the deferred payment is greater than the validity period of the authorisation. The authorisation given during the online
purchase by the acquirer is no longer valid during the payment. Depending on the acquirer, Sogenactif chooses one of the following
scenarios:
• Acquirer is compliant with the "Account verification" feature: an account verification is sent to the acquirer with the objective
to check the transaction card number before performing an authorisation. If the response is positive, Sogenactif sends the
authorisation request with the real amount of the transaction at D+N. In the case of acceptance, the transaction is sent for
collecting.
• Acquirer is not compliant with the "Account verification" feature: the procedure is the same, but the information request made
online is replaced by an imprint (an authorisation request of a small amount).
As a result,Sogenactif makes two authorisation requests:
• The first authorisation request (of a small amount), called the imprint, to check the card during online acceptance.
• The second authorisation request for the real amount before payment collecting.
If the means of payment is not compatible with the deferral you have requested, Sogenactif overrides the captureDay field.
Page 16 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Table 21: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration NO
Acquirer checking NO
Parameter in the payment request YES • captureMode: AUTHOR_CAPTURE
• captureDay: N (Number of days of
deferred payment)
Note: the account checking is a regulatory development of CB, VISA, MASTERCARD and AMEX and
replaces the imprint. This feature is subject to the acquirer compliance.
4.4.3 Payment upon shipping
In the case of payment upon shipping, the transaction is sent for payment collecting following your validation. You indicate the validity
period for your transaction in the captureDay field. If you do not validate a given transaction before this period ends, this transaction
expires. If you forget to validate within the periods, you can submit the transaction again via the duplication operation. You can validate
all or part of the transaction amount, but it is not possible to validate an amount greater than the initial transaction amount.
If the VALIDATION method is not supported by the means of payment, Sogenactif overrides it with the default payment modality.
Table 22: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration YES VALIDATION option to activate
Acquirer checking NO
Parameter in the payment request YES • captureMode: VALIDATION
• captureDay: N (validity period before
the validation)
4.4.4 Payment in instalments
The payment in instalments is addressed to the merchant who want to offer payment facilities to their customers.
To get a functional description and implementation instructions for the payment in instalments, please refer to the payment in instalments
guide.
4.4.5 Immediate payment
In the case of immediate payment, the transaction is captured during online authorisation. This payment method is not used very
frequently and only for means of payment supporting single-message mode (a single message for authorisation and payment).
If this method is not supported by the means of payment, Sogenactif overrides the captureMode parameter with the default value
corresponding to the means of payment in question (for more information, see the means of payment integration guides).
The means of payment supporting this mode are the following:
• Bancontact
Page 17 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
• Bancontact mobile
• Cetelem 3X 4X CB
• Cetelem Presto
• Chèque-Vacances Connect
• e-Chèque Vacances
• iDEAL
• Sofortüberweisung
Table 23: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration NO
Acquirer checking NO
Parameter in the payment request YES • captureMode: IMMEDIATE
• captureDay: 0
4.4.6 Batch payment
Batch payment is a deferred exchange of information (in file mode) between you and Sogenactif. It allows you to create transaction
and/or operation files and then upload them to a secure Sogenactif FTP Account.
It is therefore different from a number N of information communicated in real time (transaction mode).
File mode:
1. You have a number N of individual payment transactions and/or operations (N1, N2, N3, N4, etc.).
2. Based on the Sogenactif Office Batch specifications, you create a 'request' file containing these transactions and/or operations, and
upload this file to a secure Sogenactif FTP account.
3. Sogenactif performs rights and file consistency checks (format, size), then processes the information contained in this file and sends
authorisation requests to the acquirers.
4. The acquirers process the authorisation requests received and send the responses to Sogenactif.
Page 18 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
5. Sogenactif creates the 'response' file containing the responses to payments and/or transactions and uploads this file to your secure
Sogenactif FTP account.
6. You download the 'response' file via your secure Sogenactif FTP account and then integrate this file into your own information
system.
Batch payment proves particularly useful if you have to process a very large number of flows since it saves you from having to provide
a real-time response to your customers.
Table 24: Summary
Available connectors Sogenactif Office Batch
Sogenactif configuration NO
Acquirer checking NO
Parameter in the payment request N/A
4.4.7 Validity period of authorisation
The acquirer's authorisation remains valid for a certain time (six days by default for CB, VISA and Mastercard):
• during this period, the transaction is sent for collecting with the authorisation carried out online
• beyond this period, a new authorisation request is sent to the acquirer prior to payment collecting
The validity period may depend on the acquisition contract concluded between you and the acquirer, this is why an option lets you
fix the authorisation period associated with your acquisition contract. This feature is available only for certain means of payment. For
more information, see the implementation guides.
Table 25: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration YES By default six days for CB / Visa /
Mastercard cards
Acquirer checking YES
Parameter in the payment request NO
4.5 Payment in currencies
4.5.1 Multi currency acceptance
In the case of multi-currency transactions, acceptance relates to the customer's currency, but payment is settled in your currency.
You must subscribe to this option with the acquirer.
The acceptance stages for multi-currency transactions are as following:
1. You must manage the price of your online sales in several currencies.
2. When you submit the transaction to the Sogenactifserver, you fill in the currency you want in the currencyCode field.
3. The transaction is sent for authorisation and for payment collecting with the same currency code.
4. During payment acquisition, the acquirer converts the transaction into your settlement currency.
Page 19 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Table 26: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration YES The accepted currencies must be defined
in the Sogenactif configuration.
Acquirer checking YES
Parameter in the payment request YES currencyCode: Transaction currency
code. The possible values are listed in
document Data dictionary.
4.5.2 Currency settlement
In the case of settlement in various currencies, acceptance and settlement are done in the same currency.
You specify the code for the currency used by the customer in the payment request. You must have an acquisition contract and a bank
account in the concerned currencies.
Tip: to implement this advanced feature, please contact the technical support.
Table 27: Summary
Available connectors Sogenactif Paypage, Sogenactif Office
Serveur, Sogenactif Office Batch,
Sogenactif In-App
Sogenactif configuration YES The accepted currencies must be defined
in the Sogenactif configuration.
Acquirer checking YES Acquisition contract with settlement in
various currencies.
Parameter in the payment request YES currencyCode: transaction currency code.
The possible values are listed in the data
dictionary.
Page 20 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
4.5.3 Dynamic Currency Conversion (DCC)
Dynamic currency conversion (DCC) is a financial service for Visa and Mastercard cardholders. It lets the customer pay in their currency
and the merchant to be paid in theirs.
DCC enables you and the local bank, which is the acquirer (handles payment in your name), to take advantage of the exchange fees
normally added to such transactions by VISA and Mastercard and the international issuing banks. You always receive the settlement
in your basic currency.
To use the Dynamic Currency Conversion (DCC), you must:
• subscribe to an acquisition contract with the DCC option.
• subscribe to an exchange rate service.
• request the DCC option when enroling in the Sogenactif service.
Tip: to implement this advanced feature, please contact the technical support.
Table 28: Summary
Available connectors Sogenactif Paypage
Sogenactif configuration YES The accepted currencies must be defined
in the Sogenactif configuration and agreed
with the acquirer and the exchanger.
Acquirer checking YES
Exchange contract YES
Parameter in the payment request YES currencyCode: indicate in this field the
code of your basic currency. Possible
values are listed in the data dictionary.
4.6 3-D Secure
3-D Secure is a mandatory authentication protocol designed to reduce the risk of payment fraud on the Internet. Its purpose is to ensure
that the card is used by its true owner. In addition to this security aspect, 3-D Secure allows you to benefit from the liability shift to the
bank issuing the card, according to rules issued by the CB, VISA, MASTERCARD, AMEX and Bancontact networks.
4.7 Recurring payment
Recurring payment defines the rules and conditions for the payment of a service over a given period, validated between the merchant
and their client. Using recurring payment is a good way for paying services linked to subscriptions.
In its use case, there are two phases in recurring payment:
• 1st phase: the collection of card details is done with the customer being present and is associated or not with a payment. This card
information will be used for the following payments under the agreement between you and the customer.
• 2nd phase: the Nth payments are sent without customer action, using card information stored during the 1st phase.
Supported means of payment: CB, Visa, Mastercard, American Express, Bancontact and SDD.
3-D Secure for card recurring payments
To secure recurring payments, it is mandatory to do the initial transaction (first payment) in 3-D Secure mode in order to authenticate
the card holder. The Nth following payments are not in 3-D Secure mode because the card holder is not present.
Processing recurring payments according to PCI requirements
Page 21 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Sogenactif allows you to use card information in a secure way, avoiding PCI constraints linked to card data storage. It is possible to
send the Nth payments using several ways:
• duplicate the initial transaction
• payment via a Wallet (card stored in the wallet)
Attention: you have to inform your customers that you store their information and you have to inform them
about the terms of recurring payments (duration, amount, periodicity…)
4.7.1 Recurring payment via duplication
Details on how to handle subscription payments using duplication method is fully described on subcription payment using duplication
guide.
4.7.2 Recurring payment via wallet
Please refer to the document recurring to have a functional description and to get the recurring payment implementation methods.
Here are the main use cases:
Saving a payment mean in the wallet during a payment via Sogenactif Paypage
Via Sogenactif Paypage, you can ask for the automatic enrollment of the payment mean in the wallet when the payment is accepted.
Attention: If the payment mean used is a card, you must keep track of the
schemeTransactionIdentifier returned in response. You will have to transmit this value in the field
InitialSchemeTransactionIdentifier for the recurring payments to chain them with the initial
transaction (PSD2).
Table 29: Summary
Available connectors Sogenactif Paypage
Sogenactif configuration YES Automatic enrolment option in the wallet
when a Sogenactif Paypage payment is
accepted.
Acquirer checking NO
Parameter in the request YES • merchantWalletID: Wallet Id
• paymentPattern: RECURRING_1
• challengeMode3DS : value forced to
CHALLENGE_MANDATE
Reporting • Transactions report: YES
• Operations report: NO
• Sogenactif Gestion: YES
Saving the payment mean in the wallet via Sogenactif Walletpage without any payment
Via the Sogenactif Walletpage interface you may can your customer to create a wallet by adding a payment mean.
IMPORTANT: this interface can no longer be used to set up a subscription with a card because as there is no
payment involved, you will not receive any chaining identifier on response. Therefore, you will not be able to
provide it on the recurring payments.
Page 22 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Table 30: Summary
Available connectors Sogenactif Walletpage
Sogenactif configuration YES Sogenactif Walletpage option
Acquirer checking YES Recurring option
Parameter in the request YES • merchantWalletID: Id in which the
PAN or the mandate will be stored
• walletActionNameList: ADDPM to
add a payment mean
• PaymentMeanBrandList:
SEPA_DIRECT_DEBIT
Reporting • Transactions report: NO
• Operations report: NO
• Sogenactif Gestion: NO
Saving a mandate in the wallet via the addDirectDebit method of Sogenactif Office Serveur without any payment
Via the Sogenactif Office Serveur or Sogenactif Office Batch interfaces, you may create a wallet for your customer with their mandate Id.
Table 31: Summary
Available connectors Sogenactif Office Serveur,
Sogenactif configuration YES Wallet option
Acquirer checking YES Recurring option
Parameter in the request YES • merchantWalletID: wallet Id
• mandateId: mandate Id
• paymentMeanBrand:
SEPA_DIRECT_DEBIT
Reporting • Transactions report: NO
• Operations report: NO
• Sogenactif Gestion: NO
For the Nth payments, use the walletOrder method entering the wallet id in the merchantWalletID field.
Attention: If the payment mean associated to the wallet is a card, you have to set
the field initialSchemeTransactionIdentifier with the value of the
schemeTransactionIdentifier you received when the subscription was set up.
Table 32: Summary
Available connectors Sogenactif Office Serveur, Sogenactif
Office Batch
Sogenactif configuration YES Not activated by default
Acquirer checking YES Recurring option
Page 23 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
Parameter in the request YES • paymentPattern: RECURRING_N
• merchantWalletID: Id of the wallet in
which the payment mean is stored
• initialSchemeTransactionIdentifier
: chaining identifier received when
the subscription was set up (only
applicable if the payment mean is a
card)
Reporting • Transactions report: YES
• Operations report: NO
• Sogenactif Gestion: YES
Note: the wallet is limited to one means of payment to ease the recurring payment. (1 wallet = 1 means of
payment).
You only have to manage the wallet Id and not the Id of the means of payment stored in the wallet.
4.8 One Clic Payment
One Clic payment is for merchants who want to ease the payment for their customers.
This service allows customers to register their payment details in a secure area called Wallet and thus avoid having to re-enter this
information for future payments.
One Clic payment simplifies the payment act, improves the user experience particularly for mobile purchases, and thus increases the
conversion rate.
For a functional description and the implementation methods of the One Clic payment, please read the One Clic document.
4.9 Cash management
Transaction life cycles differ depending on the means of payment, so the new status of the transaction can differ as well. The detailed
life cycles are available in the means of payment integration guides.
Tip: if you receive a response due to a technical error (responseCode 90 or 99) or a transaction status refusal
(responseCode 24) in response to your cash management operation, we advise you to try again.
4.9.1 Cancellation
You may cancel non captured transaction either partially or totally by using the Cancel function available in the Sogenactif Office
Serveur, Sogenactif Office Batch and Sogenactif Gestion interfaces.
For CB, Visa and Mastercard means of payment, the cancellation operation is no longer possible on a transaction as soon as its bank
remittance processing is carried out.
Example: if a transaction (CB, Visa or Mastercard) is carried out on day 1 (D), with captureDay set with 2 and captureMode set with
AUTHOR_CAPTURE, it will not be possible to cancel the transaction from day 3 (D+2) 10:00 p.m. CET onwards.
Page 24 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisFunctionality set-up - 04/11/2021
For most other means of payment, the cancellation operations are unavailable every day during the transaction remittance process to
the bank (please read appendix 3 ), even on transactions not included in the remittance file.
The process duration may vary depending on the number of transactions to sent for remittance.
It is possible to know a transaction settlement date via Sogenactif Gestion, via the reports or via the Sogenactif Office Serveur
getTransactionData function (captureLimitDate field).
In the case of a complete cancellation, the transaction status is set with "cancelled" (transactionStatus CANCELLED), but for a partial
cancellation, the status remains unchanged.
The below checks are carried out:
• You have the right of cancellation. If you do not, a responseCode 40 is returned.
• The transaction exists in our database. If it does not, a responseCode 25 is returned.
• The transaction status is "TO_CAPTURE" or "TO_VALIDATE" or "TO_AUTHORIZE" or "TO_CHALLENGE". If not, a
responseCode 24 is returned. You may consult the remittance hours per acquirer / private in Appendix 3.
• The amount to cancel is equal or lower than the transaction amount. If it is not, a responseCode 51 is returned.
• No cash management operation is already in progress on the transaction. Otherwise, a responseCode 24 is returned.
Note: you may find all the response codes in the Data Dictionary here.
Table 33: Summary
Available connectors Sogenactif Office Serveur, Sogenactif
Office Batch, Sogenactif Gestion
Sogenactif configuration YES Not activated by default
Acquirer checking NO
Reporting • Transactions report: NO
• Operations report: YES, CANCEL
• Sogenactif Gestion: YES
4.9.2 Validation
Transactions created in validation mode (captureMode = VALIDATION), must be validated fully or partially in order to trigger the
payment, by using the Validate function available in the Sogenactif Office Serveur, Sogenactif Office Batch and Sogenactif Gestion
interfaces.
The transaction is then set to the "to validate" status (transactionStatus = TO_VALIDATE) or to the "waiting for a validation with
authorisation request" status (transactionStatus = TO_REPLAY), then to the "to capture" status (transactionStatus = TO_CAPTURE)
or directly to the "captured" status (transactionStatus = CAPTURED) depending on the means of payment rules.
You can validate a transaction only once. In the case of a partial payment, the complement can be carried out via the duplication
operation.
The below checks are carried out:
• You have the right of validation. Otherwise, a responseCode 40 is returned.
• The transaction exists in our database. Otherwise, a responseCode 25 is returned.
Page 25 / 40
Confidentialité : C1
Société Générale, S.A. au capital de 1 066 714 367,50 € - Siège social : 29 bd Haussmann 75009 Paris - 552 120 222 RCS ParisYou can also read
