WL SIPS DOCS

In 1.0 checks are made on the 1.0 fraud check tool.

In 2.0, you use the new 2.0 fraud engine manageable from the MEX.

On Worldline Sips 1.0, in order to bypass one or more additional checks, you need to notify the keyword corresponding to the checking in the DATA field of the API. On Worldline Sips 2.0, you need to enter the values of the bypassCtrlList and bypassInfoList fields.

The bypass keywords correlation is described in the 1.0 / 2.0 Data correlation guide.

The checkings not linked to the means of payment (ex. customer outstanding payments, gray list, etc.) are not shared between 1.0 and 2.0.

• The migration of gray lists from 1.0 to 2.0 is supported by the migration process.

The main features of 2.0 fraud management are:

• Go-No-Go mode
• Go-No-Go+ mode (optional in the Sogenactif 2.0 offer)

• RMS (Risk Management system) GUI: viewing / updating of the configuration

You have a shop in 1.0, so you have a merchantId which allows to log in. All your transactions are made with this merchantId and you enjoy consolidated reports and a visualisation of all your transactions on Sips Office Extranet with all means of payment combined.

You pilot the migration. After issuing your migration report, the decision of the date and time of migration is taken jointly between you and Worldline. A close monitoring of the first flows is done by you and Worldline to ensure the smooth running of the 2.0 migration.

In case you detect an anomaly (unidentified issue during the test phase of your internal developments), flows can be migrated back to Worldline Sips 1.0 via the APIs.

This solution remains possible as long as you and Worldline Sips keep valid 1.0 login credentials. The 1.0 accesses removing is done during the last step. The removal of the 1.0 accesses is performed during the last step. Your access to the Worldline Sips 1.0 tools will be maintained to allow you to access to the transaction history and to manage transactions until you express your wish to close your shop permanently. closing your shop permanently Worldline Sips 1.0.

Worldline has developed a new Worldline Sips platform, allowing you to:

• simplify Worldline Sips integration and standardise connection methods thank to new state of the art Worldline Sips connectors.
• optimise the customer experience thanks to new features and new ergonomics of the customer interfaces (InApp application, webresponsive, etc.).
• have greater autonomy in the management of transactions and settings thanks to a new Extranet interface.
• facilitate the deployment on the international market thanks to new means of payment.
• enjoy advanced features such as an effective anti-fraud tool, dashboard, etc.

If you have created a new shop in 2.0 you will have two separate merchantId.

From the 2.0 interfaces you cannot access and manage transactions created in Worldline Sips 1.0 (validation, cancellation, refund, duplication) since you keep your existing identifier for your 1.0 shop, and use a new identifier for your new 2.0 shop.

From the 2.0 interfaces you cannot access and manage transactions created in Worldline Sips 1.0 (validation, cancellation, refund, duplication) since you keep your existing identifier for your 1.0 shop, and use a new identifier for your new 2.0 shop.

From the 2.0 interfaces you cannot access and manage transactions created in Worldline Sips 1.0 (validation, cancellation, refund, duplication) since you keep your existing identifier for your 1.0 shop, and use a new identifier for your new 2.0 shop.

From the 2.0 interfaces you cannot access and manage transactions created in Worldline Sips 1.0 (validation, cancellation, refund, duplication) since you keep your existing identifier for your 1.0 shop, and use a new identifier for your new 2.0 shop.

From the 2.0 interfaces you cannot access and manage transactions created in Worldline Sips 1.0 (validation, cancellation, refund, duplication) since you keep your existing identifier for your 1.0 shop, and use a new identifier for your new 2.0 shop.

However, you can can use the extended duplication feature that allows from a 2.0 shop to duplicate a transaction from another shop, even if the transaction is in 1.0.

In the case where you keep the identification by TransactionId, you have the option to keep your reports in the old 1.0 format or to enjoy the new 2.0 reports format at your convenience.

However, only 2.0 reports evolve and enjoy new added fields. If you keep the 1.0 format, you will not enjoy the updates (ex. adding a means of payment related additional data in the reports).

The s10TransactionId and s10TransactionIdDate fields have been added to the Transactions, Operations, Reconciliations and Chargebacks 2.0 reports.

This new identifier has the advantage of being in ANS35 format which allows:

• to keep this unique identifier unlimited (over the period of transaction existence in Worldline Sips: 15 months) instead of one day for transactionId.
• to use alphanumeric characters in the reference, an open format facilitating the way you generate the latter.
• to be independent of time zones (internationalisation).

You can opt for transactionReference mode at any time. For example, you have the opportunity to migrate to Worldline Sips 2.0 by keeping the transactionId mode to facilitate the migration and then opt for the transactionReference in order enjoy the advantages of this new format.

If you have opted for the transactionReference mode you can no longer switch to the transactionId mode, because if you are in transactionId mode, the extranet display is not changed, and the transactionReference is not visible. This would prevent manipulating transactions generated with the transactionReference mode.

Customising payment pages is an optional step to start in 2.0. Worldline Sips offers customisation by default.

There is no migration tool that reproduces the customisation of 1.0 payment pages. We do not recommend attempts to reproduce exactly the visuals of the 1.0 payment pages on the 2.0 payment pages. Indeed, it would be a shame to be deprived of the new opportunities offered by the 2.0 payment pages, especially from the responsiveness point of view.

It is recommended to change the payment pages customisation in order to enjoy the advantages of the 2.0 payment pages.

A page customisation guide is available.

The wallet database is shared between Worldline Sips 1.0 and 2.0.

The SUBSCRIPTION subscribers data base is already migrated to the wallet database.

The list of means of payment available in 2.0 is provided in § 3.1.2 of this guide.

Fraud checks available in 2.0 are detailed in the "Anti-fraud management" guide.

Accepted currencies depend on the acquirer’s contract. The currencies available for the Visa/MC, Amex scheme are as follows:

EUR,USD,CHF,GBP,CAD,JPY,MXN,TRY,AUD,NZD,NOK,BRL,ARS,KHR,TWD,SEK,DKK,KRW,SGD,XPF,XOF.

• La Banque Postale
• Banque Populaire
• BNP Paribas
• Caisse d’Epargne
• Crédit Agricole
• Crédit Du Nord
• Crédit Mutuel Centre Est Europe
• CIC
• Crédit Mutuel of Brittany
• HSBC
• Crédit Lyonnais
• Société Générale

Worldline provides you with a test shop that allows you to validate your internal developments.

When you have finished your test phase, you provide a migration report and determine jointly with Worldline the date and time of your migration.

Following this migration, a careful monitoring of the first flows is performed.

The standard procedure for registering a new 2.0 shop should be used.

You access and manage the transactions in the 1.0 or 2.0 environments/interfaces in which you created those transactions.

The extended duplication allows you to create a transaction from an existing transaction initiated by another shop. You can use this feature to duplicate a transaction of your 1.0 shop from your new 2.0 shop.

To do this, both shops must share the same clientId.

You need to include in your payment request the identifiers of the original shop and of the original transaction:

• fromMerchantId
• fromMerchantId
• s10FromTransactionIdDate

The details of the means of payment are retrieved by Worldline Sips from the initial transaction. However, you can modify the business data (order number, remittance method, etc.).

The duplicated transactions are processed as a new transaction in recurring mode (the paymentPattern field is set to RECURRING_N).

The performed checks are as follows:

• You do not have the extended duplication right (refusal code 03).
• The original shop is not attached to you (refusal code 40).
• The transaction to be duplicated does not exist (refusal code 25).
• The initial transaction cannot be duplicated because the means of payment does not allow this (refusal code 24).
• The means of payment expiry date has been exceeded (refusal code 24).
• Authorisation request refused by the acquirer.

The transaction created by duplication is included in the Transactions report and displayed in the Extranet.

Reports: you receive your reports by shop, 1.0 and 2.0 reports are not consolidated. The 2.0 reports isolate flows related to Worldline Sips 2.0 transactions.

This scenario allows you to benefit from the new 2.0 report format for your second shop. However, this option is not mandatory, you can keep the 1.0 format if you want to keep the existing reporting processing in your Back Office. This is valid for Transactions report, Operations report, Reconciliation report and Chargebacks reports types.

Extranet: you can keep the same URL and your existing login/password by using the super-user feature.

However, you do not have access to a consolidated history of your 1.0 and 2.0 transactions since you keep your existing login for your 1.0 shop and use a new login for your new 2.0 shop.

In 1.0 checks are made on the 1.0 fraud check tool.

In 2.0, you use the 2.0 fraud engine accessible from MEX.

Checks not related to the means of payment (ex. customer outstanding payments, gray list, etc.) are not shared between 1.0 and 2.0.

The creation of lists in 2.0 is handled via a specific request. Please contact your Worldline privileged interlocutor.

There is a coexistence of 1.0 and 2.0 billing items.

Both shops are linked to the same charged customer with the same billing model.

• Compartmentatlisation of fraud 1.0 and fraud 2.0.
• Do not use the same means of payment in 1.0 AND in 2.0 with a single distance selling contract because the reconciliation does not work properly when several shops of the same merchant have the same acquisition contract.