iVeri Payment Technologies

Mode: Test Vs Live

The iVeri Gateway provides a mechanism where a merchant can perform test transactions that are routed to an iVeri Gateway issuer simulator. This enables a merchant to complete testing within a test environment. When the merchant is ready s/he can perform live transactions, which are routed to the genuine card issuer. merchant specifies the mode of a transaction by setting Mode as “Test” or “Live” and sends their corresponding Test or Live ApplicationID.

Sending the following card numbers to the Test environment has the following results:

PAN	Result
4242424242424242	returns "Authorised"
2121212121212121	randomly returns "Hot Card", "Please Call" or "Denied"
5454545454545454	randomly returns "Unable to process" or times out
All other card numbers (eg "1111222233334444")	returns "Invalid card number"

For information on testing PIN based accounts, see “PIN based transactions”.
Merchants are requested not to abuse the test environment more than their realistic requirements.
A merchant abusing the Test environment may have their use of it suspended

Budget Period

The Budget Period facility is only available within certain localities (eg South Africa), and therefore only currently available with distributor Nedbank. Since a transaction sequence may entail the Budget Period being sent to the acquirer multiple times, the merchants should ensure that this value is consistent. If an authorisation was obtained outside the iVeri Gateway, and then the AuthorisationCode is sent within “Debit with PAN” or “Debit with Track2”, then the BudgetPeriod should be set to the same value as when authorised. If the BudgetPeriod is not sent to the iVeri Gateway, then iVeri assumes to be “straight” (0 months). However, if the external authorisation was “over budget”, then it would then be up to the acquirer/issuer to decide between the conflicting budget values.

Field	Description	Length (bytes)	Format
SS	Start Sentinel	1	;
PAN	Primary Account Number	19 max	Digits
FS	Field Separator	1	=
DATE	Expiration Date (YYMM)	4	Digits
SVC CD	Service Code	3	Digits
Discretionary Data	Optional Issuer Data	variable	Digits
ES	End Sentinel	1	?
	Total cannot exceed 39 bytes	39

Track2
The Track2 is used for card present transactions and is sent to the iVeri Gateway after it is read by the swipe device from the magnetic stripe on the card. It is inclusive of the beginning and end markers being ; and ? respectively.
The Track2 sent to the iVeri Gateway must be in the following format:

The Track2 read from by the card reader typically contains the following fields (at most 40 bytes):

PAN

DATE

SVC CD

Descretionary Data

LRC

The e 1-byte Longitudinal Redundancy Check (LRC) should not be sent to the iVeriGateway.
The End Sentinel (ES) may need to be converted to? (0x3F)

Track2 Service Code values
The following tables can be used to determine the meaning of the 3-digit service code.
See section 17.6.4 for algorithm to determine if a card is PIN based or not.
Note that a transaction may not decline or rejected solely because of the value of the service code.

Value Position#1	Description	MasterCard	Visa
1	International Card	Yes	Yes
2	International Card – Integrated Circuit Card	Yes	Yes
5	National Use Only	Yes	Yes
6	National Use Only – Integrated Circuit Card	Yes	Yes
7	Private Label or Proprietary Card	Yes	No

Value Position#2	Description	MasterCard	Visa
0	Normal Authorisation	Yes	Yes
2	Positive Online Authorisation Required	Yes	Yes

Value Position#3	Description	MasterCard	Visa
0	PIN Required	Yes	Yes
1	Normal Cardholder Verification, No Restrictions	Yes	Yes
2	Normal Cardholder Verification – Goods and services only at point of interaction (no cash back)	Yes	No
3	ATM Only, PIN Required	Yes	Yes
5	PIN Required – Goods and services only at point of interaction (no cash back)	Yes	No
6	Prompt for PIN if PIN Pad Present	Yes	Yes
7	Prompt for PIN if PIN Pad Present – Goods and services only at point of service (no cash back)	Yes	No