1. Introduction

This guide must be read alongside our DirectLink guide.

Hereafter we guide you through the features of the online part of the Worldline Omni-channel offer.

The following key elements to benefit from the online Omni-channel offer are covered:

  • How to become an Omni-channel merchant?
  • How to benefit from Omni-channel features such as the single back office (e-Portal), online refunding of in-store transactions and the tokenization?
  • How to make transactions in an Omni-channel context?
  • What are the new fields to handle via the various integration modes?

2. Activation: how to be Omni-channel

Please contact your sales representative to request activation of your Omni-channel features.

During the activation phase, you will define and submit to Worldline a hierarchical list of users and entities by which the transactions will be generated. Hereunder we've summarized how you can describe the different webshops and users.

For more details, please contact your sales representative for guidance on the activation process.

3. Access to the back-office e-Portal

One of the key benefits of the Omni-channel offer is a common back office to review and manage your transactions and your configuration. This web-based portal is called e-Portal.

Using e-Portal, you can perform refunds on your transactions, whether they were done online or in-store.

The Ogone online payments section is directly available in e-Portal, using your e-Portal credentials.

You can access e-Portal here: https://eportal.services.ingenico.com

For more details on how to use e-Portal, please refer to relevant e-Portal User Guide.

4. Group of Groups

Prior to the Omni-channel offer, you were able to define users (lowest level PSPID) and to order them into groups, by placing common users under one Merchant Group or MGID.

A concept has been added, where several groups can be grouped under a top MGID. During the activation process, you will provide a list of users list representing your shop structure and their users. Here is an example:

The maximum number of layers (levels) is 3 (e.g., country - region - store).

For more details, please contact your sales representative or refer to the relevant e-Portal User Guide.

5. User management

In order to simplify the user management, its configuration has been centralized within e-Portal. Please refer to e-Portal User Guide - User Management module for more details.

Note that API users on the Ogone platform must still be managed via the user management section in the "Online" tab of e-Portal.

6. API General information

XDL is a new API that allows Omni-channel merchants to access all of the features of Ogone DirectLink (new orders, maintenance and query) with the same interface as DirectLink, but with Omni-channel features included.

This means that the merchant will be able to act on his transactions, whether they come from Card Present (CP) or Card Not Present (CNP) world. Payment terminals at POS are CP, and payment online at a web shop is CNP.

This includes use cases like refund CP and/or CNP payment, deferred payment, etc. Please refer to your sales representative for more information about our proposed Omni-channel use cases.

6.1 Concept

In the context of Omni-channel we have a few new concepts to introduce:

Concept Description Platform
Omni-channel Order



A set of transactions that belong together from the point of view of the merchant. All of the transactions in the Omni-channel order have the same ORDERID. The order is identified by the combination of merchant and his sales reference.



n/a
Payment



Treatment of a payment. Starts with the authorization or the direct sale. Consists of multiple transactions.



Ogone: Order, identified by PAYID

Axis: Payment

Transaction



Lowest level of interaction. There are several types of transactions like capture, refund, credit, cancellation etc.



Ogone: Payment History, identified by PAYID + PAYIDSUB



6.2 URLs



Test Production
New order https://ogone.test.v-psp.com/dl/neworder

https://secure.ogone.com/dl/neworder
Maintenance https://ogone.test.v-psp.com/dl/maintenance

https://secure.ogone.com/dl/maintenance

Query https://ogone.test.v-psp.com/dl/query

https://secure.ogone.com/dl/query

6.3 Integration with Omni-channel

6.3.1 Parameters

With the new Omni-channel features, additional items or artefacts have been made available. Here is a summary of each new item added for each solution.

Parameter Description
OPERATORID



While calling XDL, the merchant can, for the sake of reporting and auditing, indicate which human user of his enterprise requested the action.



It is up to the merchant to make up a code to identify the employee, for instance, the userid of the employee logged on to the cash register. When not used, the field defaults to the Ogone user account. For e-Portal, the portal user account will be used.

Format: AN, 100

Optional

ORDERID



The merchant’s reference to the sale between the merchant and the merchant’s customer in the context of Omni-channel. The merchant has to guarantee the uniqueness of this field within the merchant’s realm.



In the context of Omni-channel, the ORDERID is mandatory for all new orders.

Format: AN, 35

Mandatory

REQUESTID



In order to identify different requests / payments for the same ORDERID / SalesReference, the merchant must send a unique request identifier for each individual request. In case a first call fails, and there is no response from our server, all subsequent retries must use the same REQUESTID.



The caller is advised to generate a random number or string (like a new guid) to be used as REQUESTID.



e-Commerce: Not returned



DirectLink: Input only (optional)

Format: AN, 35

Mandatory

TRANSACTIONID



Transaction identifier. In order to transfer the Omni-channel transaction to act upon (for instance during maintenance).



Each operation on the Worldline platform by an Omni-channel merchant will return both the PAYID and the TRANSACTIONID. The Omni-channel merchant is advised to store the TRANSACTIONID in his records.



If the Omni-channel merchant sends TRANSACTIONID and PAYID (and/or PAYIDSUB) parameters together in one request, the consistency between both is verified, and if they do not refer to the same transaction, the request is rejected with an error.



Mandatory for maintenance on Card Present transactions. In all other cases it is advised to use TRANSACTIONID, but optional as the merchant can also use the PAYID + PAYIDSUB instead.

Mandatory
XCORDERAMOUNT



The Omni-channel Order has an order amount attribute that the merchant can use to report on the planned value of the order. This information will be used in KPI reports regarding upselling.



The parameter is expressed in the same currency as the first transaction in the order (x 100, so there are no decimals).



The amount of the order does not influence transaction handling in any way.

Optional
XCORDERSTATUS



Omni-channel orders can be marked as Open or Closed. The closed status indicates that the normal sales process has been executed. This information can be used in the click-and-collect case, whereas open orders will be available for collecting.



The only acceptable values are: "Open" and "Closed".



The status of the order does not block transaction handling in any way.



The status is not to be confused with the difference in operation between SAL and SAS, which closes the payment against further capturing.

Format: "Open"/"Closed"

Optional

CRMTOKEN and XCDIGEST (Tokenization fields)



6.3.2 Operation codes

A few new operations were added to the DirectLink specification, for the purpose of supporting the deferred use case.

Operation code* Parameters

PAL

Maintenance operation that requests the system to issue a second, third, etc. payment, starting from an original payment transaction identified by TRANSACTIONID, with the same payment method details. The amount to be paid is mandatory, as well as the ORDERID.
The system will make sure that CVC and 3-D Secure will not be required, as the customer is not physically available at the time of the request. This is an alternative to the SAL direct sale/payment request, and follows the same capture rules, defined by the merchant's configuration.

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxxx
OPERATION=PAL
AMOUNT=1000
CURRENCY=EUR
TRANSACTIONID=9000001001785380000

Recommended

REQUESTID=UMDoperation001

Optional

REFKIND=MGID
REFID=ECOMRDS.MGP00

URL

TEST: https://ogone.test.v-psp.com/dl/Maintenance
PROD: https://secure.ogone.com/dl/Maintenance

PES

Same as PAL, but only gets an authorisation. This operation does not capture the payment. This is an alternative to RES (request for authorisation).

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxxx
OPERATION=PES
AMOUNT=1000
CURRENCY=EUR
TRANSACTIONID=9000001001785380000

Recommended

REQUESTID=PESoperation001

Optional
REFKIND=MGID
REFID=ECOMRDS.MGP00

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

UMD

Maintenance operation that allows updating the metadata fields of an Omni-channel Order without a financial transaction.
The request must contain ORDERID and can have the following additional parameters: XCORDERAMOUNT, XCORDERSTATUS, ANNEXNAME*XX*, ANNEXVALUE*XX*, OPERATORID, REQUESTID, TRANSACTIONID.

Mandatory

PSPID=ECOMRDSPSPID11
CURRENCY=EUR
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxx
OPERATION=UMD
ORDERID=UMDOperation001

Recommended

REQUESTID=UMDoperation001

Optional

REFID=ECOMRDS.MGP00

REFKIND=MGID

XCORDERAMOUNT=200
XCORDERSTATUS=Open
ANNEXNAME1=ORDER-USERDATA1
ANNEXVALUE1=SalesPeriod
ANNEXNAME2=ORDER-USERDATA2
ANNEXVALUE2=53
ANNEXNAME3=ORDER-USERDATA3
ANNEXVALUE3=Something
ANNEXNAME4=ORDER-USERDATA4
ANNEXVALUE4=UMDoperation001
OPERATORID=testoperator
TRANSACTIONID=9000001001785380000

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

CRD

Pure credit operation that works the same as a refund (RFD) but without verification of the amount.
You can use CRD if you want to give/return money to the cardholder, with an amount of your choice and no previously paid amount.
To be able to use CRD you need to specify the TRANSACTIONID, so that card details can be retrieved.

Double credit check: If for the same order two concurrent credits are attempted, the second attempt will be blocked. In that way "double-credit fraud", which is a risk when working with multiple channels, is avoided. This system is supported for all ePayments API’s, with Axis terminals and with e-Terminal (MOTO).

Mandatory

PSPID=QAINTC01PSPID01
CURRENCY=EUR
USERID=QAINTC01PSPID01_API

PSWD=xxxxxxxxxxxxxx
amount=50000
OPERATION=CRD
TransactionId=1012732100000017628

Optional

REFID=QAINTC01PSPID01
REFKIND=PSPID

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

RES

Mandatory

PSPID=PSPIDRESTY02
USERID=RestyAPIUser01
PSWD=xxxxxxxxxxxxxxx
amount=1000
CURRENCY=EUR
ORDERID=RESOperation001
CARDNO=48xxxxxxxxxxxx67
ED=1216
CVC=123
OPERATION=RES

Optional

REFID=MG_RESTY_01
REFKIND=MGID

URL

TEST:
https://ogone.test.v-psp.com/dl/NewOrder
PROD:
https://secure.ogone.com/dl/NewOrder

REN

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER

PSWD=xxxxxxxxxxxxxxx
OPERATION=REN
PAYID=3002492108

Optional

REFID=ECOMRDS.MGP00

REFKIND=MGID

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

SAL

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxxxx
OPERATION=SAL
amount=1000
currency=EUR
ORDERID=MerchReffdhgf4hgf56
CARDNO=48XXXXXXXXXXXX67
ED=1216
CVC=123

Recommended

REQUESTID=SALOperation01

Optional

REFKIND=MGID
REFID=ECOMRDS.MGP00

URL

TEST:
https://ogone.test.v-psp.com/dl/NewOrder
PROD:
https://secure.ogone.com/dl/NewOrder

SAS

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxxx
OPERATION=SAS
amount=1000
currency=EUR
ORDERID=MerchReffdhgf4hgf55
CARDNO=48XXXXXXXXXXXX67
ED=1216
CVC=123

Recommended

REFKIND=MGID
REFID=ECOMRDS.MGP00

Optional

REQUESTID=SASOperation01

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

DEL

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER

PSWD=xxxxxxxxxxxxxxx
OPERATION=DEL
PAYID=3002492530

Recommended

REQUESTID=DELOperation001

Optional

REFKIND=MGID
REFID=ECOMRDS.MGP00

amount=1000
currency=EUR

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

DES

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER

PSWD=xxxxxxxxxxxxxxx
OPERATION=DES

PAYID=3002492530

Recommended

REQUESTID=DESOperation001

Optional

REFKIND=MGID
REFID=ECOMRDS.MGP00
amount=1000
currency=EUR

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

RFD

Mandatory

PSPID=ECOMRDSPSPID11
CURRENCY=EUR
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxxx
amount=1
OPERATION=RFD
TransactionId=9000003002450295000

Optional

REFID=ECOMRDS.MGP00
REFKIND=MGID

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

RFS

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxxx
amount=1
CURRENCY=EUR
OPERATION=RFS
TransactionId=9000003002450295000

Optional

REFID=ECOMRDS.MGP00
REFKIND=MGID

URL

TEST:
https://ogone.test.v-psp.com/dl/Maintenance
PROD:
https://secure.ogone.com/dl/Maintenance

QUERY

Mandatory

PSPID=ECOMRDSPSPID11
USERID=Cust_12240_API_USER
PSWD=xxxxxxxxxxxxxx
PAYID=3002492530

Optional

REFID=ECOMRDS.MGP00
REFKIND=MGID
PAYIDSUB=1

URL

TEST:
https://ogone.test.v-psp.com/dl/Query
PROD:
https://secure.ogone.com/dl/Query

6.3.3 Metadata

XDL features a generic metadata system for transaction and order metadata. This will allow the merchant to bring additional information elements about the transaction and the order. This information does not influence the transaction processing, but will be used in the Unified Journal reporting. The fields are ANNEXNAMEx and ANNEXVALUEx. X is the sequence number and the fields should always come in pairs having the same sequence number. After processing, the sequence number is not relevant anymore, and you should not expect the metadata to be returned in the same sequence order.

You can send metadata with any of the transactions. The metadata already in the system is updated with the new values. Metadata that is not updated in a subsequent request will remain in the system. In order to clear a value, the name and value pair have to be sent, with the value set to nothing, like in &ANNEXNAME2=ORDER-USERDATA1&ANNEXVALUE2=

Although the merchant can send any type of metadata, only some annex names are recognized by Omni-channel for the purpose of KPI reporting:

  • ORDER-USERDATA1
Example:

ANNEXNAME1=ORDER-USERDATA1

ANNEXVALUE1=DEFERRED

6.3.4 Output

The output returned to the merchant can always be tuned to the merchant's expectations by changing the options in the Ogone back office. This section explains the availability of new output parameters. Whether they are returned to you depends on your settings.





PAYID and TRANSACTIONID

Upon each request from the merchant, the platform will respond with the reference of the executed transaction, commonly known as PAYID and PAYIDSUB.

When the merchant has been configured for Omni-channel, the platform will return the TRANSACTIONID together with the PAYID (if configured accordingly in the list of dynamic parameters).

More details about the TRANSACTIONID can be found earlier in this document, under Parameters.





CRMTOKEN and XCDIGEST (Offline token)

For each transaction request by the merchant that involves card details, the platform will return the CRM tokens that are available for Omni-channel merchants. The returned tokens are specific to the merchant and can only be used to track the cardholder, both online and in-store.

These two card identifiers are:

  • CRM Token: a “mask” for the card number, keeping the format of a card number
  • Offline token: a non-format preserving identifier for the card used for the payment, at the merchant level.
Field Format
CRMTOKEN

Numeric – 16 digits

Example: 0246777044912837

XCDIGEST (=Offline token)



Hexa - 64 digits

Example: 05E9…

Which type of token to choose is entirely up to the merchant, based on the requirements and/or possibilities of his own system.

In case of the XCDIGEST/Offline token, the merchant's system must be able to process long digests.

Note: if the CRM token/Offline token couldn’t be generated, the transaction will still go through but no token will be returned. Contact our Support team.





Add Omni-channel fields to transaction feedback

Log on to e-Portal and go to the Online payments tab > Configuration > Technical information > Transaction feedback:

  • Under DirectLink: Dynamic parameters, select the relevant fields (CRMTOKEN, XCDIGEST, TRANSACTIONID, ORDERID, PAYID) in the "Available" dropdown list, and set as “Selected”.







  • Under e-Commerce: Dynamic e-Commerce parameters, select the relevant fields (CRMTOKEN, XCDIGEST, TRANSACTIONID, ORDERID, PAYID) in the "Available" dropdown list, and set as “Selected”.







Add Omni-channel fields to electronic reports

Log on to e-Portal and go to the Online payments tab: Operations > View Transactions (note: you need to select one of your PSPIDs to have the menu item displayed):

  • Click on “File format”
  • Under "Structure", select "Dynamic". Confirm this change directly by clicking "Submit" at the bottom of the page, to show the list of available fields.
  • Select "Available fields", add [CRMTOKEN], [XCDIGEST] and [TRANSACTIONID] and click "Submit" at the bottom
  • "Selected fields" should show [CRMTOKEN], [XCDIGEST] and [TRANSACTIONID]

When this is done, the transaction reports will show these two fields.





Download reports including Omni-channel fields

Log on to e-Portal and go to the Online payments tab: Operations > Financial history (note: you need to select one of your PSPIDs to have the menu item displayed):

  • Check the “detailed list” box
  • Select all type of transactions needed
  • Click “Download list”.

The list will contain in the header CRMTOKEN; XCDIGEST; TRANSACTIONID. The values will be shown with each transaction.

6.3.5 SHA signature

List of additional Omni-channel parameters to be included in SHA-IN and/or SHA-OUT calculation. *XX* is the placeholder for sequence numbers:

ANNEXNAME*XX*

ANNEXVALUE*XX*

CRMTOKEN

OPERATORID

REQUESTID

TRANSACTIONID

XCDIGEST

XCORDERAMOUNT

XCORDERSTATUS

Please refer to our documentation about SHA-OUT.

6.4 Refunds

6.4.1 Cross-payment refunds

You can refund up to the full amount that is calculated as the sum of all payments (Card Present and Card Not Present) done for the whole order.

Example: If within one and the same order there was a CNP payment of €10 and a CP payment of €890, after capturing only the €10 (CP) it is still possible to refund the full €900.

6.4.2 Double refunds check

If for the same order two concurrent refunds are attempted, the second attempt will receive an error “Cannot refund - Order is already locked”.

In that way "double-refund fraud", which is a risk when working with multiple channels, is avoided.

This system is supported for all ePayments API’s, with Axis terminals and with e-Terminal (MOTO).

The order is unlocked shortly after the refund action has been completed.

7. Tokenization

A key pillar of the Omni-channel offer is the tokenization service allowing you to replace sensitive data (e.g. a card number) with non-sensitive data (i.e. a token).

Go to the CRM Token and Offline token chapter for detailed integration info.

For more details about the tokenization service, please refer to the Tokenization Overview document.

8. Error codes

In case the requested refund amount is higher than what is available on the balance, the following error info is returned:

  • NCERROR="50001129"
  • NCERRORPLUS="Overflow in refunds requests/"MaxRefund amount"/"balance amount"

Questions fréquemment posées

Sur ce site d’assistance, vous trouverez tous les manuels présentant nos produits. N’hésitez pas à les consulter.








Notre outil de réconciliation vous est fourni automatiquement à l’activation de votre compte si vous optez pour un compte Full Service.  Cette option permet de rapprocher en toute facilité les paiements reçus sur votre compte en banque et les commandes/transactions effectuées sur votre compte Ingenico ePayments. Pour en savoir plus sur l’outil de réconciliation, cliquez ici.

Worldline propose des solutions de paiement adaptées, sécurisées, intelligentes et transparentes, quel que soit le canal (magasin, en ligne et mobile). Il fournit aux commerçants une gamme complète et innovante de services et de solutions qui facilitent les paiements et garantissent des achats rapides, transparents et sécurisés, quel que soit le canal de vente ou la méthode de paiement.

 

Worldline compte trois divisions : Worldline Smart Terminals, Worldline Payment Services et Worldline . Notre gamme complète de terminaux intelligents, de services de paiement et de solutions mobiles facilite l’acceptation des paiements en ligne et en magasin des commerçants.

Désormais connu sous le nom d’Ingenico ePayments, Ogone était un prestataire paneuropéen de services de paiement en ligne, qui a été racheté par le groupe Ingenico en 2013 et qui a fusionné avec GlobalCollect en 2015 pour devenir Ingenico ePayments.


Pour rendre hommage à l’héritage d’Ogone, nous avons donné son nom à la plate-forme Ingenico ePayments, qui inclut Ingenico Collect, une solution de paiement intégrée qui permet aux commerçants de proposer les moyens de paiement favoris des acheteurs dans plusieurs pays sans avoir à ouvrir plusieurs comptes bancaires ni à créer de nouvelles entités juridiques.


Avec sa plate-forme Ogone et ses autres offres, Ingenico ePayments va au-delà des paiements en proposant des services de conseil sur des thèmes tels que la réglementation locale, les habitudes et préférences de paiement régionales, la fraude et la conformité.

Avant de prendre le nom d’Ingenico ePayments, Ogone a été provisoirement baptisé Ingenico Payment Services. Ogone et GlobalCollect ont ensuite fusionné pour ne former qu’un : Ingenico ePayments.



Aujourd’hui, Ingenico Payment Services est une division autonome du groupe Ingenico qui fournit aux commerçants une gamme complète de services de gestion centralisée et sécurisée des transactions en magasin. Ingenico Payment Services assure la sécurité, le contrôle et le suivi de bout en bout des transactions des commerçants grâce à une solution de paiement centralisée réservée aux détaillants structurés.



De plus, Ingenico Payment Services propose une gamme complète de solutions de fidélisation de la clientèle destinées à augmenter les revenus des commerçants : gestion des programmes et cartes de fidélité, gestion des cartes prépayées et des cartes cadeau, analyse des données des clients et gestion des campagnes marketing.

Un mandat SEPA est plus facile à organiser et vous, en tant que commerçant, ne devrez pas vous soucier du paiement manuel de nos factures.

Dans le menu de votre compte Worldline, vous pouvez facilement rechercher vos transactions en cliquant sur « Opérations », puis sur « Afficher les transactions » ou « Historique financier », selon le type de résultat que vous recherchez.

Cliquez sur Consulter vos transactions pour obtenir plus d’informations.

Par défaut, vous pouvez envoyer des marchandises ou fournir un service lorsque la transaction a atteint le statut « 9 - Paiement demandé ». Même si le statut 5 est un statut positif, il s’agit d’une simple réserve d’argent temporaire sur la carte du client. Une transaction possédant le statut 5 doit être confirmée (manuellement ou automatiquement), pour passer au statut 9, qui est le dernier statut positif pour la plupart des méthodes de paiement.

Cliquez sur Statuts des transactions pour obtenir plus d’informations.

Vous pouvez facilement rembourser un paiement en cliquant sur le bouton « Rembourser » dans l’aperçu des commandes d’une transaction (dans « Afficher les transactions »). Si votre compte le permet, vous pouvez également effectuer des remboursements avec une demande DirectLink ou l’option de téléchargement de fichier Batch (en cas de transactions multiples).

Sachez que l’option « Remboursement » doit être activée sur votre compte.

Cliquez sur Gérer vos transactions pour obtenir plus d’informations.

 

L’icône verte en forme de pouce levé indique que la transaction a été réalisée avec une méthode d’authentification 3-D Secure, comme un Digipass ou un lecteur de cartes. Cela ne signifie pas nécessairement que le paiement a été traité avec succès. Vous devez donc toujours vérifier le statut de la transaction pour savoir si vous recevrez l’argent.

Cliquez sur Statuts d'une transaction pour obtenir plus d’informations.

Ingenico ePayments propose une suite complète de produits flexibles, des technologies sophistiquées et un savoir-faire dédié pour vous aider à gérer et optimiser vos pratiques de prévention de la fraude en ligne. Forts de nos outils de pointe de détection des fraudes et de nos experts qui vous apportent leurs 20 années d’expérience sectorielle et régionale, nous travaillerons en étroite collaboration avec vous au développement, à la mise en œuvre et à la gestion d’une solution globale de la prévention, la détection et la gestion de la fraude. Nous proposons également des solutions complètes de gestion des réimputations et des litiges.


En faisant appel à Ingenico ePayments, vous pouvez sélectionner les solutions les mieux adaptées à vos besoins et personnaliser nos services, soit en externalisant la gestion de la fraude soit en l’internalisant avec notre support.

Si vous souhaitez vérifier les détails d’une commande/transaction ou gérer certaines transactions, vous devez utiliser l’option « Gestion des transactions ». « Historique financier » est l’option la plus pratique pour consulter périodiquement les fonds entrants et sortants.

Pour plus d’informations, consultez Gestion des transactions vs Historique financier.

Vous ne pouvez effectuer des remboursements que sur les transactions qui ont obtenu u statut 9 sur les dernières 24 heures. L’annulation ou la suppression d’un paiement est possible dans un délai de 24 heures après que le statut final de la transaction soit reçu (Statut 9 ou 5).

Pour connaître l’heure limite de votre acquéreur, nous vous recommandons de contacter directement notre service clientèle.