The document discusses various settings and features for a TIM API including:
1. The Integrator ID uniquely identifies the integrator and enables problem verification. OnFixIP is recommended for faster connectivity over Broadcast. DCC allows foreign transactions in the card's currency through acquirer currency conversions.
2. Receipt copies are required for verification, not just TIM logs. Terminals support inserted, contactless, and swiped cards, requiring rollbacks if methods like signatures are unavailable. Full connect/disconnect is recommended over pre/post-automatisms for easier troubleshooting.
3. Result codes should be "0" for OK. A card type of "unknown" means it's not in the terminal
The document discusses various settings and features for a TIM API including:
1. The Integrator ID uniquely identifies the integrator and enables problem verification. OnFixIP is recommended for faster connectivity over Broadcast. DCC allows foreign transactions in the card's currency through acquirer currency conversions.
2. Receipt copies are required for verification, not just TIM logs. Terminals support inserted, contactless, and swiped cards, requiring rollbacks if methods like signatures are unavailable. Full connect/disconnect is recommended over pre/post-automatisms for easier troubleshooting.
3. Result codes should be "0" for OK. A card type of "unknown" means it's not in the terminal
The document discusses various settings and features for a TIM API including:
1. The Integrator ID uniquely identifies the integrator and enables problem verification. OnFixIP is recommended for faster connectivity over Broadcast. DCC allows foreign transactions in the card's currency through acquirer currency conversions.
2. Receipt copies are required for verification, not just TIM logs. Terminals support inserted, contactless, and swiped cards, requiring rollbacks if methods like signatures are unavailable. Full connect/disconnect is recommended over pre/post-automatisms for easier troubleshooting.
3. Result codes should be "0" for OK. A card type of "unknown" means it's not in the terminal
The document discusses various settings and features for a TIM API including:
1. The Integrator ID uniquely identifies the integrator and enables problem verification. OnFixIP is recommended for faster connectivity over Broadcast. DCC allows foreign transactions in the card's currency through acquirer currency conversions.
2. Receipt copies are required for verification, not just TIM logs. Terminals support inserted, contactless, and swiped cards, requiring rollbacks if methods like signatures are unavailable. Full connect/disconnect is recommended over pre/post-automatisms for easier troubleshooting.
3. Result codes should be "0" for OK. A card type of "unknown" means it's not in the terminal
- The Integrator ID is a unique code assigned by Worldline to each Integrator. Implementation is
necessary because it enables quick verification of the Integrator when problems with the operation of terminals occur - We recommend using OnFixIP instead of Broadcast (OnFixIp is faster). Broadcast should be used in case a router is not owned by the Merchant: IP addresses of connected devices could be changed often etc. - DCC (Dynamic Currency Conversion) is a card feature that allows Cardholders to perform transactions in a foreign country using the currency of his home-country (card base currency). The legal DCC information should always be present on the customer receipt and may not be changed. Implementation of DCC is easy, just set DCC=True in TerminalSettings and properly handle the printouts. All currencies calculations are made by Acquirer’s authorisation Host. - Error messages in TIM log files can only be captured in English. Setting getErrorMessage as DE or FR will not work - The POS-ID (POS Identifier) has no impact to bank settlements. Is a value that can be set in the Terminal Settings, in order to identify the name of the ECR transmitting data to the Terminal. Can be useful if you have for example 5 ECR Stations in a restaurant. Each of them can have a separate POS-ID in order to identify each of them in your reporting
2 Features & Functions
- A copy/image of real receipts/invoices is required. The view of receipts in TIM log files is not enough - 3 card possibilities on Terminals: inserted, presented (contactless) or swiped. If one of them may not be accepted (e.g. signature on Unattended), the ECR Software should send a rollback instead of commit, meaning the transaction will be refused. This can be triggered by the Cardholder Verification Method (CVM). CVM can be Pin (inserted / contactless), Signature (swiped), ... - Pre and Post-automatisms are convenient, but in case of problems it gives less possibilities to quickly diagnose and fix the problem. A full Connect/Disconnect flow implementation is strongly recommended - The Terminal Status should be Idle before starting a new transaction - Keep Alive starts after Login if feature is activated. It checks if the connection between ECR and EFT is active - Balance = Day or Shift Closure - COMMIT is typically used when payments (PURCHASE) are followed by the release of a product or a service that needs to be delivered. If the product is not released or the service is not performed correctly, such payment can be corrected (cancelled) by performing ROLLBACK. If the transaction goes correctly, a COMMIT is performed. If there is no need for additional checking of product / service delivery - you can use AutoCommit = True (set in TerminalSettings)
3 Behaviours and results
- Result Codes in TIM log files should be "0", meaning result OK - Card Unknown (e.g. Result Code "800") means the card type is not present in the SCS Configuration of the Terminal - Stop Cardholder means the Cardholder (Merchant’s customer) pressed the Stop Button on the Terminal - Terminals in the test environment (ETU) requires TEST CARDS - production cards will not work. If you did not receive the test cards with your test terminal - please contact Worldline Business Owner / Key Account person responsible