Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


(lightbulb) This information is written in English only

System requirements

Smartcards

We 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-PC

Operating System - OS

  • Win7 64-bits 
  • Win10 64-bits - recommended


System programs

  • Microsoft .NET Framework 4.6.2 (from BAM v3.7.5)
  • 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 ²
  • Scanner
  • SignaturPad
  • Cardreaders for User card and Operator card

 


WebLTS

The .net version uses a new web service interface connecting to Buypass - WebLTS. This is made specially for communication between a LRA 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.



ACR88/89 in combination with a card reader for user cards can and must still be used until the organization has all cards with applications supporting Secure PinPad (see next section below). The shift between ACR88/89 and Secure PinPad can easily be reconfigured by running Setup Wizard where this is selected.

The .net version has 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). 


³) Secure PinPad



System requirements

Local  Mode

Mixed Mode

Buypass Mode

Microsoft .NET Framework (4.6.2) Download

(tick)

 (tick)

(tick)

Remote Server Administration Tools for Windows

Windows 7 Download

Windows 8.0 Download

Windows 8.1 Download

Windows 10 Download

 (tick)

(tick)

(error)

Merchant Certificate

(error)

(tick)

(tick)

Device drivers (PinPad, SignPad, Scanner, Card   Readers)

(tick)

(tick)

(tick)

You will find descriptions of the different Modes of BAM-client later in this document.

New requirements due to new version

No 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.




Related contents

Unable to render {include} The included page could not be found.


Unable to render {include} The included page could not be found.

 

Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.
 
Unable to render {include} The included page could not be found.
 


  • No labels