* *Visa Check-Out is a digital representation of a cardholders Visa Card. Cardholders can register their debit or credit cards by downloading the Visa Check-Out app. Once cardholders have their profiles and card details loaded in Visa Check-out, they are able to make purchases at merchants who are accepting with Visa Check-Out payments.
The Visa Check Out process flow explained below showcases the different parties involved.
/ Transaction Notification /*
**
/ Email to Merchant */
This is an order confirmation from the Payment Gateway to Lite Application.
We have received the following Sale from your customer:
Customer Details:
Name : Mr. John Doe
Email : John
Payment Details:
Transaction Type : Sale
Transaction Index : A0394EB4-BBC1-4567-BBCB-A56B702050DD
Merchant Reference : LITE0000028
Card Number : 4242........4242
Expiry Date : 092025
Acquirer Reference : 80903:09089990
Electronic Commerce Indicator : SecureChannel
Order Details:
Purchase DateTime : 2022-09-03 09:08:32
Total Order Amount : R 100.00
Line Item Details:
Item Description Quantity Unit Cost Line Total
-----------------------------------------------------
Donation product#1 1 100.00 100.00
Additional Info:
Please contact <Distributor> should yo
Release Notes *
**
Release Notes for every iVeri product.
Introduction: *** Google Pay™* is a digital wallet service from Google
that is expanding into e‑commerce to streamline online and in-app transactions.
That allows customers to use payment cards saved to their Google Account to pay
online without re-entering card details*. In essence, Google Pay functions
as a secure intermediary: when a customer checks out with Google Pay, the
system provides the merchant with a tokenised version of the customer’s card
data instead of the actual card number.
What is
Google Pay in E‑Commerce? *** In the context
of e-commerce, Google Pay* serves as a digital wallet checkout option*
that lets customers pay on websites or mobile apps using payment cards saved to
their Google account. When a customer uses Google Pay on an e-commerce site,
Google Pay provides th
Downloads ***
Download for products
*
*
* Parameter description ***
Command *
Authorisation *
Debit *
Credit *
AutohorisationReversal *
Void*
GetData*
Cancel*
GetHMAC*
GetSystemInfo*
Parameter*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
Description*
AcquirerCode
O
O
O
O
O
The Acquirer ISO code returned for this transaction. Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription. This is only made available as extra information and may not exist in all response.
AcquirerDescription
O
O
O
O
O
The Acquirer ISO description returned for this transaction. Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription
Automatic Billing Updater* **
Introduction **
The documentation, titled Merchant Onboarding Guide, is intended to provide a comprehensive and methodical explanation of the merchant onboarding process within the Standard Bank Administration Website. The Merchant Onboarding Guide provides the onboarding process for Card Not Present iVeri solutions.
Objectives **
The purpose of this user guide is to assist users in navigating the merchant take-on process by providing step-by-step visual representations on the screen.
Accompanied by detailed explanations, these screen representations aim to enhance the user's understanding of the iVeri administration website interface.
The guide contains all the essential information for users to successfully onboard a merchant. It also covers typical scenarios that may arise based on the
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