Worldline is a payment solution that can be integrated into your PrestaShop store.
Production environment
If you are using the production environment for the first time, please note that you must first send a validation report to your payment platform which will confirm the successful production of the monetary flows on the new 2,0 connectors.
When switching to the production environment, you must ensure that the module configuration complies with the instructions of your payment platform:
- In the Identifiers section, please verify the values of the fields Merchant Identifier, Secret Key and Secret Key Version.
- In the Transaction Identification section, please verify the values of the fields Transaction Identification Method and Generate Transaction Identifier.
Please also verify that the payment methods you have activated in the module configuration are consistent with those made available by your payment platform.
Transaction Identification
Two transaction identification methods are available:
- the transactionReference mode
- the transactionId mode
The difference between the 2 modes is the scope of the identifier: the transactionReference must be unique throughout the life of the store, whereas the transactionId must be unique for the day.
There is also an option to generate the transaction identifier:
- If activated, the module generates the transaction identifier in the payment request sent to the payment platform
- If disabled, the module lets the payment platform generate the transaction identifier automatically, then retrieves it in the payment platform's response
Note: transactionReference is the default identification mode, transactionId 1,0 has been reverted to 2,0 to facilitate the migration of 1,0 merchants to 2,0 as part of the simplified migration procedure.
When creating a transaction, and depending on the chosen mode, the payment platform accepts or rejects the creation and generates additional identifiers.
1. Store in TransactionReference mode
Creating a transaction with a transactionReference generated by the module
This is the default mode if you have a new merchant_id
transactionReference generated by the module | Standard processing |
transactionId generated by the module | Rejection Code = 12 |
transactionId absent | OK |
transactionReference absent | Rejection Code = 12 |
Additional reference generated by the payment platform | s10TransactionId and s10TransactionIdDate |
Response content | s10TransactionId, s10TransactionIdDate and transactionReference |
Creation of a transaction without transactionReference (auto Tref)
The module retrieves and stores the additional references generated by the payment platform.
transactionReference generated by the payment platform | Standard processing |
transactionId generated by the module | |
transactionId missing | OK |
transactionReference generated by the module | Rejection Code = 12 |
Additional reference generated by the payment platform | transactionReference, s10TransactionId and s10TransactionIdDate |
Response content | s10TransactionId, s10TransactionIdDate and transactionReference |
2. Store in TransactionId mode
Creation of a transaction with transactionId generated by the module
This is the mode to configure as part of a simplified migration procedure from the 1,0 connector to 2,0
transactionId generated by the module | Standard processing |
transactionId absent | Rejection Code = 12 |
transactionReference generated by the module | Rejection Code = 12 |
transactionReference missing | OK |
Additional reference generated by the payment platform | transactionReference |
Response content | s10TransactionId, s10TransactionIdDate, and transactionReference |
Creating a transaction without a transactionId (automatic Tid)
The module retrieves and stores the additional references generated by the payment platform.
transactionId absent | Standard processing |
transactionId generated by the module | Rejection Code = 12 |
transactionReference generated by the module | Rejection Code = 12 |
transactionReference absent | OK |
Additional reference generated by the payment platform | s10TransactionId, s10TransactionIdDate and TransactionReference |
Response content | s10TransactionId, s10TransactionIdDate and transactionReference |
Sogenactif 1,0 migration to Sogenactif 2,0
To consult the documentation on the Sogenactif 1,0 to Sogenactif 2,0 migration, go to the Sogenactif help center.
Migration LCL Sherlock's 1,0 to LCL Sherlock's 2,0
To view documentation on migrating LCL Sherlock's 1,0 to LCL Sherlock's 2,0 visit the dedicated help center.
Comments
0 comments
Please sign in to leave a comment.