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.).
The purpose of this document is to explain the Visa mean of payment integration into Sogenactif.
Who does this document target?
This document is intended to help you implement the Visa mean of payment on your e-commerce site.
It includes:
- functional information for you
- implementation instructions for your technical team
To get an overview of the Sogenactif solution, we advise you to consult the following documents:
- Functional presentation
- Functionality set-up
Contacting the support
For any question or request for technical assistance, you can contact the usual Sogenactif support on 0 825 090 095 (0.15€/min + call charge - rate as of 02/11/2022) from Monday to Friday, from 9am to 7pm, excluding public holidays, or write to supportsogenactif@worldline.com specifying your VAD or MID contract number for a more efficient handling of your request.
Understanding Visa and Mastercard payments with Sogenactif
General principles
Cards in the Visa network is one of the most widespread payment cards in the world, used and issued by banks in more than 200 countries.
Visa offers a range of following cards: Visa, VPay, Visa Electron
Furthermore, the Visa network has established the 3-D Secure programme, to reduce the risk of fraud on customers online purchases. This program ensures, at the time of each online payment, that the card is used by the true cardholder.
To pay with a Visa or MasterCard network card, cardholders have to provide their card details, namely:
- Card number
- Expiry date
- Visual security code called CVV
- If the cardholder's card and your merchant ID are enrolled in 3-D Secure, the customer will be required to enter a dynamic one-time use code, usually received on their mobile phone.
Acceptance rules
Available functionalities
Payment channels | ||
---|---|---|
Internet | V | Default payment channel |
MAIL_ORDER, TELEPHONE_ORDER | V | |
Fax | V | |
IVS | V |
Means of payment | ||
---|---|---|
Immediate payment | X | |
End-of-day payment | V | Default method |
Deferred payment | V | Limited to 99 days, except for 3-D Secure which is limited to 6 days because of the liability shift rules. |
Payment upon shipping | V | Limited to 99 days, except for 3-D Secure which is limited to 6 days because of the liability shift rules. |
Payment in instalments | V | |
Subscription payment | V | |
Batch payment | V | |
OneClick payment | V |
Currency management | ||
---|---|---|
Multicurrency acceptance | V | |
Currency settlement | V | |
Dynamic currency conversion | V |
Payment remittance in the bank
Payments are remitted to a bank according to the payment terms you set. As standard, the remittance in bank is triggered at night as from 10 pm CET (Central European Time) via a file exchange with the acquirer.
Account verification on your initiative
For INTERNET and MOTO channels, you are allowed to perform an account verification on your own initiative (not conditioned by the deferred payment delay). To do this, you have to set the transaction amount to “0”. Therefore, Sogenactif will perform an account verification from the acquirer, and the transaction will be stored in the Sogenactif information system, but won’t be remitted in bank.
Cap adjustment in case of an error
During a payment, sometimes the current transaction cannot be finalised. This is the case, for instance, when one of the actors in the banking network encounters a failure when processing an authorisation request. The Sogenactif server will send a message to cancel the transaction, this is the famous cap adjustment. This message allows the issuing bank to update, if necessary, the cardholder's card outstandings.
Lost and stolen cards checking
If you have the required option, a card checking is done using a lost and stolen list provided by the acquirer. This checking will be carried out during the transaction validation or the remittance steps.
If the provided card is in the lost and stolen cards list during the validation, the operation is rejected.
If the provided card is in the lost and stolen cards list during the remittance, the transaction will not be remitted.
Reversal request
A reversal request aims to cancel the modification of the issuer authorisation cap.
This reversal request is always linked to an authorisation request.
The reversal request is sent to the acquirer in the following case:
- the merchant fully cancels the transaction. The cancellation is prioritized: it is completed even if the reversal fails;
- the authorisation server doesn't respond positively to an authorisation request for the following reasons: "approved after identification" or "approved for partial amount";
- no response has been received after an authorisation request (timeout);
Signing your Visa acceptance contract
The Sogenactif distance selling contract that you have signed with SG includes, by default, Visa cards acceptance and acquisition.
Making a Visa payment
Sogenactif offers you three solutions to integrate the Visa means of payment:
- Sogenactif Paypage which directly acts as the payment interface with customers via their web browser.
- Sogenactif Office Serveur which gives you the opportunity to display your payment pages and works through a server-to-server dialog.
- Sogenactif Office Batch which allows you to process batch payments.
The remittance modes available for a Visa transaction are:
- Cancellation mode: default mode allowing transaction remittance on a predefined date, called capture delay. When this capture delay is reached, the remittance is sent automatically. This delay is set via the captureDay field with its 0 default value (end-of-day payment).
- Validation mode: you must validate the transaction to trigger the remittance. A capture delay must also be defined. When this capture delay is reached or exceeded, you will not be able to validate the transaction, which will therefore expire automatically.
The diagram below explains the different transaction statuses according to the chosen capture mode:
Making a Visa payment with Sogenactif Paypage
The payment process for Sogenactif Paypage is described below:
Setting the payment request
The following fields have a particular behaviour:
Field name | Remarks/rules |
---|---|
statementReference | The value sent to this field will appear on your account statement (Available only for some acquirers). |
Analysing the response
The following table summarises the different response cases to be processed:
Status | Response fields | Action to take |
---|---|---|
Payment accepted | acquirerResponseCode = 00
authorisationId = (cf. the
Data Dictionary).cardProductCode = (cf. the
Data Dictionary).cardProductName = (cf. the
Data Dictionary).cardProductProfile = (cf. the
Data Dictionary).cardProductUsageLabel = (cf.
the Data Dictionary).virtualCardIndicator = (cf.
the Data Dictionary).issuerCode = (cf. the Data
Dictionary).issuerCountryCode = (cf. the
Data Dictionary).paymentMeanBrand = VISA
paymentMeanType =
CARDresponseCode =
00 |
You can deliver the order. |
Acquirer refusal | acquirerResponseCode = (cf.
the Data Dictionary).responseCode =
05 |
The authorisation is refused for a reason unrelated to
fraud. If you have not opted for the "new payment attempt"
option (please read the Functionality
set-up Guide for more details), you can suggest that your
customer pay with another means of payment by generating a new
request. |
Soft decline | acquirerResponseCode = A1
responseCode =
05 |
The acquirer has refused the payment because there was no
3-D Secure authentication. Please try the payment again by
activating the 3-D Secure authentication. |
Refusal due to the number of attempts reached | responseCode = 75 |
The customer has made several attempts that have all failed. |
Refusal due to a technical issue | acquirerResponseCode = 90-98
responseCode = 90,
99 |
Temporary technical issue when processing the transaction. Suggest that your customer redo a payment later. |
For the complete response codes (responseCode
) and acquirer response
codes (acquirerResponseCode
), please refer
to the Data dictionary.
Making a Visa payment with Sogenactif Office Serveur
The payment process for Sogenactif Office Serveur is described below:
Setting the payment request
American Express payments can be initiated using the cardCheckEnrollment
function of the
CheckOut service. The following fields are used to send information
specific to this means of payment:
Field name | Remarks/rules |
---|---|
cardNumber |
Mandatory |
cardExpiryDate |
Mandatory, if specified on the card. |
cardCSCValue |
Mandatory in some countries (3 digits). The CVV is
optional for transactions using the MOTO payment
channel. |
paymentMeanBrand |
The paymeantMeanBrand field can be populated with VISA. |
For more information, please refer to the 3-D Secure guide on Sogenactif Office Serveur connector to implement the other steps of a 3-D Secure payment.
Analysing the response
The following table summarises the different response cases to be processed:
Status | Response fields | Action to take |
---|---|---|
Payment accepted | acquirerResponseCode = 00
authorisationId = (cf. the
Data Dictionary).cardData.cardProductCode =
(cf. the Data Dictionary).cardData.cardProductName =
(cf. the Data Dictionary).cardData.cardProductProfile =
(cf. the Data Dictionary).cardData.cardProductUsageLabel
= (cf. the Data Dictionary).cardData.virtualCardIndicator
= (cf. the Data Dictionary).cardData.issuerCode = (cf.
the Data Dictionary).cardData.issuerCountryCode =
(cf. the Data Dictionary).cardData.issuerName = (cf.
the Data Dictionary).paymentMeanBrand = VISAresponseCode =
00 |
You can deliver the order. |
Acquirer refusal | acquirerResponseCode = (cf.
the Data Dictionary).responseCode =
05 |
The authorisation is refused for a reason unrelated to fraud, you can suggest that your customer pay with another means of payment by generating a new request. |
Soft decline | acquirerResponseCode = A1
responseCode =
05 |
The acquirer has refused the payment because there was no
3-D Secure authentication. Please try the payment again by
activating the 3-D Secure authentication. |
Refusal due to a technical issue | acquirerResponseCode = 90-98
responseCode = 90,
99 |
Temporary technical issue when processing the transaction. Suggest that your customer redo a payment later. |
For the complete response codes (responseCode
) and acquirer response
codes (acquirerResponseCode
), please refer
to the Data dictionary.
Please refer to 3-D Secure guide to analyse the authentication information.
Managing your Visa transactions
Available cash operations
The following operations are available on Visa transactions:
Cash management | ||
---|---|---|
Cancellation | V | Cancellation available on the
total or partial amount of the transaction. Depending on
your acquirer, a total cancellation can cause a reversal
request sending. |
Validation | V | Validation available on the partial amount of the transaction. |
Refund | V | Refund available on the partial amount of the transaction and for amounts greater than the initial amount (unlimited refund). |
Duplication | V |
The diagram below informs you which cash management operation is available when a transaction is in a given state:
Viewing your Visa transactions
Reports
The reports provided by Sogenactif allow you to have a comprehensive and consolidated view of your transactions, cash operations, accounts and chargebacks. You can use this information to improve your information system.
The availability of Visa transactions for each type of report is summarised in the table below:
Reports availability | |
---|---|
Transactions report | V |
Operations report | V |
Reconciliations report | V |
Chargebacks report | V |
Sogenactif Gestion
You can view your Visa transactions and perform various cash management operations with Sogenactif Gestion.