How Automatic Billing Updater works *
**
Below is a high-level visual representation of how Automatic Billing Updater works:
1.Make a selection on what you want to purchase.
2. Select Add to Bag
3. Select Go to checkout
Here you can either select Checkout or select the Bag icon it is still the same.
4.Insert your email address and the select Checkout
This cardholder email is used to send the correspondent updates regarding the transaction and order status updates
5.Complete the Shipping & Delivery details for the delivery of the goods.
Select Continue
6.Complete the delivery date details
Select Continue
*/Please Note!/*
The Store owner needs to set the charges and shipping method under “Shipping and Pick Up” on their Back End IYS Profile.
7.Choose how you choose to pay for this order.
Which in this case it is iVeri
Scroll down
8. Select Go to Payment
*/Please Note!/*
Payment Instruction is set up by the merchant
How to measure the network performance *
**
The following commands should be executed on the Indigo server and the destination should be the connected Devices. If there is any variation from a network point of view between the location of the various devices connecting to an Indigo Server, then they should be tested separately.
Windows
PS C:\Users\roland> ping -n 1000 -l 512 192.168.128.14
Pinging 192.168.128.14 with 512 bytes of data:
Reply from 192.168.128.14: bytes=512 time=1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
.
.
.
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512 time<1ms TTL=63
Reply from 192.168.128.14: bytes=512
Prognosis ** Merchants using NewPOS 7210 devices are
experiencing an inability to trade* due to the “Wnet
Run Fail”* error. This error is caused by the expiry of the WNET
file*, which manages SIM-based wireless connectivity on the device.
Impact ** Devices relying on SIM connectivity are
unable to establish a network connection, preventing merchants from processing
transactions and trading.
Action Required ** To restore connectivity and resume trading, the following actions are a necessity:
Pre-Step* - Ensure device serial numbers impacted are loaded onto the terminal management software (TMS). This step is to ensure the newPOS application update is made available for download to the devices. This should be actioned by iVeri/TouchPoint, acquirers can provide a list of serial numbers a
Here are the sequential steps a merchant should follow on the device to designate MauCAS QR as the chosen payment method:
Below we will list the steps on how a merchant can view MauCas QR Transaction information:
Ingenico RA1 based devices ***
Index
Prompt
Description
01
Amount
02
Please enter new total
03
Total
04
amount again
05
Please enter
06
Add
07
Input
09
Balance
10
Tip
11
Gratuity
12
Service
13
Donation
20
Waiter ID
21
Waiter logon
22
Table number
23
Bill number
24
Location reference
25
Tab Number
26
Operator ID
37
Split by
38
number of parties
39
to pay
3A
Auth code
3B
Cashback
3C
Due
3D
Maximum
3E
Minimum
3F
Multiples of
40
Format
41
Date
42
Incorrect
43
ID incorrect
44
Number incorrect
45
Bill not found
46
Cash
47
Card
48
Cheque
49
Voucher
4A
Payment
4B
Refund
4C
Voucher number
4D
Identity code
4E
Kilometers
4F
Car number
50
Product code
51
Number of items
52
Room number
53
Plu number
Default
Input
Onboarding a merchant is a vital initial step when signing up a new merchant. This process involves gathering the necessary merchant information and tailoring enablement requirements to meet their specific needs. Acquirers must have a clear understanding of the correct procedures to ensure a smooth and successful onboarding experience.