This information is written in English only System requirementsSmartcardsWe support smartcards with Multos operating system. The applications BID and BEID from Buypass must be loaded on the cards. In BAM we support the versions BEID5 and BEID6. We do not support version BEID3 any more.
BAM-PCOperating System - OS - Win7 64-bits (32-bits will still do, but not recommendend)
- Win10 64-bits - recommended
System programs - Microsoft .NET Framework 4.6.2 or later version
- Remote Server Administration Tools for Windows - see RSAT - Remote Server Administration Tools for Windows
- Merchant certificate from Buypass
We are using a Merchant Certificate for signing the communication between the BAM client and Buypass web service reception. The certificate must be ordered specially from Buypass entering a Subscription Agreement for Merchant Certificate. The Merchant Certificate is associated with the organization, and the organization will use the same certificate on each BAM PC installed through the Microsoft Management Console - see Installation - Merchant Certificate.
Devices with drivers - SecurePinPad
BAM has support for Secure PinPad, which is an alternative to PinPad (ACR88/89) and user card reader. Prerequisite to adopt Secure PinPad is that the smart card contains BID application version BIDA5V3S or later - recommended
- PinPad ACR88/89
ACR88/89 in combination with a card reader for user cards can and must still be used if smartcards with BID-version older than BIDA5V3S is used.
The shift between ACR88/89 and Secure PinPad is reconfigured by running Setup Wizard where wanted device is selected.
There is implemented a server interfaces towards ACR88/89 which uniquely handles the communication with the card and card reader regardless of 32- / 64-bit platform. This server implementation also make it unnecessary to run the BAM client or Configuration Application client as Administrator (Run as Administrator).
- Scanner
- SignaturPad
- Cardreader for Operator card
- Cardreader for User card if PinPad ACR is used
Local CA
Access requirementsThe .net version uses a new web service interface Interface Buypass You will need an opening in local infrastructure for connecting to Buypass - WebLTS. This This is made specially for communication between a LRA the BAM client and Buypass backend for exchanging secure data over the Internet. We use https as before, but in addition, the Merchant Certificate is used for signing all exchange of data between the LRA and Buypass.(TLS1.2 or later), the api and in addition all requests and exchange of data is signed with the Merchant Certificate. https://api.buypass.no/access-registration-api
Local CA/AD Document file area Report file area Remote file area
You will find descriptions of the different Modes of BAM-client later in this document. New requirements due to new versionNo version of Buypass Access Manager has other requirements other than those mentioned above.
Buypass Access Manager (BAM) – are released on regular basis. See releasenotes for each version with new features and fixes - see Releaser. This document will give you the overall description of requirements, installation and configuration of the client. In addition, there are links to other necessary documents and user guides. For first time installation of .net version of BAM - read all chapters. For upgrade to new version of BAM – read chapter New requirements (below on this page) and then jump directly to chapter Installation - first time and update.
|