Additional information
Mapping from other payment channels
Below you will find a mapping overview for the Sales API and the two payment channels TIM/SIXML and Datatrans:
| ReconHub Sales API | TimAPI / Sixml | DataTrans API |
|---|---|---|
| amount | sixml:Amount (Request) | amount |
| currency | sixml:Currency (Request) | currency |
| transactionDate | Transaction Date according to LSI | Transaction Date according to LSI |
| acquirerId | sixml:TransactionInformation/AcqId | n/a |
| applicationId | sixml:CardData/Aid | ep2/aid |
| authorisationCode | sixml:TransactionInformation/AuthCode | ep2/authCode |
| brandId | sixml:CardData/BrandName | paymentMethod |
| businessDate | booking date according to LSI | booking date according to LSI |
| cardNumberMasked | sixml:CardData/CardNumberPrintable | card/masked, REK/masked, TWI/alias, etc. |
| eftTransactionDate | sixml:TransactionInformation/TimeStamp | ep2/trxDate & trxTime |
| locationId | n/a | merchantId or shop identifier |
| orderId | n/a | refno |
| panEncrypted | sixml:CardData/CardNumberEnc | ep2/appPanEnc |
| terminalId | sixml:TerminalId (from Notification) | ep2/trmId |
| transactionReference | sixml:TransactionInformation/AcqTransRef | ep2/trxRefNum |
| transactionSequenceCounter | sixml:TransactionInformation/TransSeq | ep2/trxSeqCnt |
| transactionTypes | Financlial Transaction function | InitRequest / CreditRequest |
| additionalData | Merchant specific information if desired in ReconHub | Merchant specific information if desired in ReconHub |
Datatrans
Payment processing between Datatrans and payment processors (such as Wordline or Postfinance) can be connected via different protocols. This setting can be adjusted individually for each merchant.
Depending on the protocol and means of payment, different information is available in the Datatrans response (status). This is mapped via the various objects such as card or ep2.
Preventing duplicate transactions
The Sales API generates a unique hash for each transaction to prevent duplicate imports. By default, this hash is calculated using all transaction fields, sorted in alphabetical order, from the upload request. As a result, adding a new field or modifying the value of any field will produce a different hash, causing the transaction to be treated as new.
During import, the generated hash is mapped to the UID field of the ECR transaction. This UID is used to detect duplicates and ensure that the same transaction is not imported multiple times.