- Help Center
- Essential modules
- Worldline
- Transaction identification
Transaction identification
Matthias Raigne
-Updated on Wednesday, August 23, 2023
Two transaction identification modes are available:
- transactionReference mode
- transactionId mode
The difference between the 2 modes is the scope of the identifier: the transactionReference must be unique over the entire life of the store, whereas the transactionId must be unique over the day.
There is also an option to generate the transaction identifier:
- if enabled, the module generates the transaction identifier in the payment request sent to the payment platform
- if deactivated, the module lets the payment platform generate the transaction identifier automatically, then retrieves it from the payment platform's response.
Note: transactionReference is the default identification mode; the transactionId 1.0 has been renewed in 2.0 to facilitate the migration of 1.0 merchants to 2.0 as part of the simplified migration procedure.
When a transaction is created, the payment platform accepts or rejects the creation and generates additional identifiers, depending on the chosen method.
Different cases are possible:
Store in TransactionReference mode
Creation of a transaction with transactionReference generated by the module
This is the default mode if you have a new merchant_id
transactionReference generated by the | Standard treatment |
transactionId generated by the | Reject Code = 12 |
transactionId absent | OK |
transactionReference absent | Reject Code = 12 |
Additional reference generated by the payment platform | s10TransactionId and s10TransactionIdDate |
Response content | s10TransactionId s10TransactionIdDate and transactionReference |
Create a transaction without transactionReference (Tref auto)
The module retrieves and stores additional references generated by the payment platform.
transactionReference generated by the payment platform | Standard treatment |
transactionId generated by the | |
transactionId absent | OK |
transactionReference generated by the | Reject Code = 12 |
Additional reference generated by the payment platform | transactionReference, s10TransactionId and s10TransactionIdDate |
Response content | s10TransactionId s10TransactionIdDate and transactionReference |
Store in TransactionId mode
Creation of a transaction with transactionId generated by the module
This is the mode to be configured as part of a simplified migration procedure from 1.0 connector to 2.0
transactionId generated by the | Standard treatment |
transactionId absent | Reject Code = 12 |
transactionReference generated by the | Reject Code = 12 |
transactionReference absent | OK |
Additional reference generated by the payment platform | transactionReference |
Response content | s10TransactionId s10TransactionIdDate, and transactionReference |
Create a transaction without transactionId (Tid auto)
The module retrieves and stores additional references generated by the payment platform.
transactionId absent | Standard treatment |
transactionId generated by the | Reject Code = 12 |
transactionReference generated by the | Reject Code = 12 |
transactionReference absent | OK |
Additional reference generated by the payment platform | s10TransactionId s10TransactionIdDate and TransactionReference |
Response content | s10TransactionId s10TransactionIdDate and transactionReference |
Share