Find more answers in the frequently asked questions for Spice but note that some are not relevant to SPI.
npm install @mx51/spi-client-js
Yes, you can download the sample application’s code at the link below.
Listen for the ‘StatusChanged’ event as it contains this information.
This is possible when using Pay at table.
This error is caused when
spi.SetTenantCode(...) is used to set a tenant code that is not in the list of available tenant codes. To get this list, call
SpiClient.GetAvailableTenants(...). Learn more
In case of POS App crash/closer and relaunch, to reconnect with the already paired EFTPOS terminal POS need to pass in the stored secret and other info when initiating a new Spi object before calling the .start() ,
it would be something like below
const spi = new Spi('posId', 'serialNumber', 'eftposAddress', storeSecret)
You will need to set
true. Learn more
If there is a network outage or internet disconnection during a transaction, SPI can recover the transaction and return the result.
Whether a transaction requires a signature is determined by the customer's card or bank account. It is not determined by the merchant or SPI. For instance, international cards often require a signature when used overseas.
No additional logic is needed for your SPI integration to handle the
spi.Config.SignatureFlowOnEftpos setting. This is because when this setting is enabled, the EFTPOS terminal handles the signature workflow, allowing your POS to handle it as a normal transaction.
When this setting is enabled and a signature is required for a transaction, a 'signature required' message will not be returned. Instead, a standard 'TxFlowStateChanged' event will be returned (but only after the EFTPOS terminal completes the signature workflow).
Updated 14 days ago