In this article
EFT Device (EFT Extension for LS Pay)
How the two types of device cards stay in sync
LS Central now has two setup cards for an EFT connection: the EFT Device card and the POS EFT Device card. Which one you should configure depends on which Card Payment Engine your installation uses. This topic explains what each card is for, when it is used, and how the two are kept in sync while both exist side by side.
Which card do I use?
The Card Payment Engine field on the Retail Setup page decides which engine the POS uses to process card payments, and therefore which of the two cards is the one you should actually edit:
| Card Payment Engine | Card to configure | What happens to the other card |
|---|---|---|
| EFT Extension for LS Pay | EFT Device | POS EFT Device becomes read-only. A notification on that card points you back to the EFT Device card. |
| Legacy Card Payments (or Default) | POS EFT Device | EFT Device stays fully editable, but only the fields the legacy engine actually reads are enabled (see below). |
Note: Default currently behaves the same as Legacy Card Payments. This will change to EFT Extension for LS Pay in a future release.
Note: whichever engine is active, the EFT device you attach to a Hardware Profile is always the EFT Device record — there is no separate hardware-profile entry for the POS EFT Device.
EFT Device (EFT Extension for LS Pay)
The EFT Device card is provided by the EFT Extension for LS Pay app and is the current, actively maintained way to configure an EFT connection. When Card Payment Engine is set to EFT Extension for LS Pay, this card controls the connection completely, including the payment provider connection (through the Hardware Station or directly to the LS Pay service), the currency, error recovery, and request logging.
The card also has an LS Central group with fields that are specific to LS Central and are not part of the base EFT Extension app: Custom Properties Profile, Card Type Handling, Pan No. Digits Used, and Default Card Type.
Note: do not confuse the Card Payment Engine field on Retail Setup with the Payment engine field on the EFT Device card itself. The Retail Setup field chooses between the legacy and the new engine for the whole POS. The field on the EFT Device card only applies when the new engine is used, and chooses how that device talks to the payment provider — through the Hardware Station or directly through the LS Pay service.
Note: while Card Payment Engine is set to Legacy Card Payments, most fields on the EFT Device card are disabled, because the legacy engine does not read them. An EFT Dialog Configuration group (Signature Verification, Amount Breakdown on Dialog, Hold Dialog Open, Display Scrolling Messages, Manual Session Control) stays enabled on this card even then, so that you can still tune how the legacy EFT dialog behaves without switching to the POS EFT Device card for those specific settings.
POS EFT Device (Legacy card functionality)
The POS EFT Device card is the original configuration card used by the legacy card-payment functionality (POS EFT Utility through the Hardware Station). While Card Payment Engine is set to Legacy Card Payments, this is the card you configure.
Once Card Payment Engine is switched to EFT Extension for LS Pay, the POS EFT Device card becomes read-only and shows a notification explaining that the EFT Device card now controls the connection, with an action to open it directly.
Note: the POS EFT Device card and the legacy engine are kept for a coexistence period while partners migrate. They are expected to be removed in a future release, once the EFT Extension for LS Pay becomes the only supported engine.
How the two types of device cards stay in sync
To avoid asking you to configure a connection twice, LS Central automatically copies the overlapping configuration from the EFT Device card down to the matching POS EFT Device record every time you create or change an EFT Device — regardless of which Card Payment Engine is active. If no matching POS EFT Device exists yet, one is created automatically with the same ID.
- This keeps legacy functionality that still reads the POS EFT Device record (for example during a switch back to Legacy Card Payments, or partner customizations that have not moved to the EFT Extension yet) working correctly, without you having to maintain both cards by hand.
- Fields that are copied down include the connection host, currency, card type handling, session control, and the EFT dialog behavior settings described above.
Note: the sync only goes one way, from the EFT Device card to the POS EFT Device card. Changes you make directly on the POS EFT Device card (while Legacy Card Payments is active) are not copied back up to the EFT Device card.
Note: deleting an EFT Device does not delete its matching POS EFT Device record. If you see a POS EFT Device with no corresponding EFT Device, it is safe to delete it manually.
See also
How to: Use EFT Card Type Handling in LS Central