Card Verification with CVD & AVS
Verifies the validity of the credit card, expiry date and any additional details (such as the Card Verification Digits or Address Verification details). It does not verify the available amount or lock any funds on the credit card.
The Card Validation Digits (CVD) value refers to the numbers appearing on the back of the credit card rather than the numbers imprinted on the front. It is an optional fraud prevention tool that enables merchants to verify data provided by the cardholder at transaction time. This data is submitted along with the transaction to the issuing bank, which provides a response indicating whether the data is a match.
The response that is received from CVD verification is intended to provide added security and fraud prevention, but the response itself does not affect the completion of a transaction. Upon receiving a response, the choice whether to proceed with a transaction is left entirely to the merchant. The response is not a strict guideline of which transaction will approve or decline.
Address Verification Service (AVS) is an optional fraud-prevention tool offered by issuing banks whereby a cardholder's address is submitted as part of the transaction authorization. The AVS address is then compared to the address kept on file at the issuing bank. AVS checks whether the street number, street name and zip/postal code match. The issuing bank returns an AVS result code indicating whether the data was matched successfully. Regardless of the AVS result code returned, the credit card is authorized or declined by the issuing bank.
The response that is received from AVS verification is intended to provide added security and fraud prevention, but the response itself does not affect the completion of a transaction. Upon receiving a response, the choice to proceed with a transaction is left entirely to the merchant. The responses is not a strict guideline of whether a transaction will be approved or declined.
Things to consider:
Security:The CVD value must only be passed to the payment gateway. Under no circumstances may it be stored for subsequent uses or displayed as part of the receipt information.
namespace Moneris
{
using System;
public class TestCanadaCardVerficiation
{
public static void Main(string[] args)
{
string store_id = "store5";
string api_token = "yesguy";
string order_id = "Test" + DateTime.Now.ToString("yyyyMMddhhmmss");
string pan = "4242424242424242";
string expdate = "1901"; //YYMM format
string crypt = "7";
string processing_country_code = "CA";
bool status_check = false;
AvsInfo avsCheck = new AvsInfo();
avsCheck.SetAvsStreetNumber("212");
avsCheck.SetAvsStreetName("Payton Street");
avsCheck.SetAvsZipCode("M1M1M1");
CvdInfo cvdCheck = new CvdInfo();
cvdCheck.SetCvdIndicator("1");
cvdCheck.SetCvdValue("099");
CofInfo cof = new CofInfo();
cof.SetPaymentIndicator("U");
cof.SetPaymentInformation("2");
cof.SetIssuerId("168451306048014");
CardVerification cardVerification = new CardVerification();
cardVerification.SetOrderId(order_id);
cardVerification.SetPan(pan);
cardVerification.SetExpDate(expdate);
cardVerification.SetCryptType(crypt);
cardVerification.SetAvsInfo(avsCheck);
cardVerification.SetCvdInfo(cvdCheck);
cardVerification.SetCofInfo(cof);
HttpsPostRequest mpgReq = new HttpsPostRequest();
mpgReq.SetProcCountryCode(processing_country_code);
mpgReq.SetTestMode(true); //false or comment out this line for production transactions
mpgReq.SetStoreId(store_id);
mpgReq.SetApiToken(api_token);
mpgReq.SetTransaction(cardVerification);
mpgReq.SetStatusCheck(status_check);
mpgReq.Send();
try
{
Receipt receipt = mpgReq.GetReceipt();
Console.WriteLine("CardType = " + receipt.GetCardType());
Console.WriteLine("TransAmount = " + receipt.GetTransAmount());
Console.WriteLine("TxnNumber = " + receipt.GetTxnNumber());
Console.WriteLine("ReceiptId = " + receipt.GetReceiptId());
Console.WriteLine("TransType = " + receipt.GetTransType());
Console.WriteLine("ReferenceNum = " + receipt.GetReferenceNum());
Console.WriteLine("ResponseCode = " + receipt.GetResponseCode());
Console.WriteLine("ISO = " + receipt.GetISO());
Console.WriteLine("BankTotals = " + receipt.GetBankTotals());
Console.WriteLine("Message = " + receipt.GetMessage());
Console.WriteLine("AuthCode = " + receipt.GetAuthCode());
Console.WriteLine("Complete = " + receipt.GetComplete());
Console.WriteLine("TransDate = " + receipt.GetTransDate());
Console.WriteLine("TransTime = " + receipt.GetTransTime());
Console.WriteLine("Ticket = " + receipt.GetTicket());
Console.WriteLine("TimedOut = " + receipt.GetTimedOut());
Console.WriteLine("IsVisaDebit = " + receipt.GetIsVisaDebit());
Console.WriteLine("IssuerId = " + receipt.GetIssuerId());
Console.ReadLine();
}
catch (Exception e)
{
Console.WriteLine(e);
}
}
}
}
Card Verification transaction object definition
CardVerification cardVerification = new CardVerification();
HttpsPostRequest object for Card Verification transaction
HttpsPostRequest mpgReq = new HttpsPostRequest();
mpgReq.SetTransaction(cardVerification);
Card Verification transaction object mandatory values
Value |
Type |
Limits |
Set method |
Description |
Order ID |
String |
50-character alphanumeric |
cardVerification.SetOrderId(order_id); |
Merchant-defined transaction identifier that must be unique for every Purchase, Pre-Authorization and Independent Refund transaction. No two transactions of these types may have the same order ID. For Refund, Completion and Purchase Correction transactions, the order ID must be the same as that of the original transaction. The last 10 characters of the order ID are displayed in the “Invoice Number” field on the Merchant Direct Reports. However only letters, numbers and spaces are sent to Merchant Direct. A minimum of 3 and a maximum of 10 valid characters are sent to Merchant Direct. Only the last characters beginning after any invalid characters are sent. For example, if the order ID is 1234-567890, only 567890 is sent to Merchant Direct. If the order ID has fewer than 3 characters, it may display a blank or 0000000000 in the Invoice Number field. |
Credit card number |
String |
20-character alphanumeric |
cardVerification.SetPan(pan); |
Most credit card numbers today are 16 digits, but some 13-digit numbers are still accepted by some issuers. This field has been intentionally expanded to 20 digits in consideration for future expansion and potential support of private label card ranges. |
Expiry date |
String |
4-character alphanumeric (YYMM format) |
cardVerification.SetExpdate(expdate); |
Submit in YYMM format. Note: This is the reverse of the date displayed on the physical card, which is MMYY. |
E-commerce indicator |
String |
1-character alphanumeric |
cardVerification.SetCryptType(crypt); |
Describes the category of e-commerce transaction being processed. Allowable values are:
- 1 - Mail Order / Telephone Order—Single
- 2 - Mail Order / Telephone Order—Recurring
- 3 - Mail Order / Telephone Order—Instalment
- 4 - Mail Order / Telephone Order—Unknown classification
- 5 - Authenticated e-commerce transaction (VBV)
- 6 - Non-authenticated e-commerce transaction (VBV)
- 7 - SSL-enabled merchant
In Credential on File transactions where the request field e-commerce indicator is also being sent: the allowable values for e-commerce indicator are dependent on the value sent for payment indicator, as follows:
if payment indicator = R, then allowable values for e-commerce indicator: 2, 5 or 6
if payment indicator = C, then allowable values for e-commerce indicator: 1, 5, 6 or 7
if payment indicator = U, then allowable values for e-commerce indicator: 1 or 7
if payment indicator = Z, then allowable values for e-commerce indicator: 1, 5, 6 or 7
|
CVD |
Object |
Not applicable. |
cardVerification.SetCvdInfo(cvdCheck); |
Note:It is optional for Canada. Refer below for further breakdown and definition. |
Card Verification transaction object optional values
Value |
Type |
Limits |
Set method |
Description |
AVS |
Object |
Not applicable. |
cardVerification.SetAvsInfo(avsCheck); |
Note:It is optional for Canada. Refer below for further breakdown and definition. |
COF Info
|
Object
|
|
cardVerification.SetCofInfo(cof);
|
For more information, see Card Verification with Credential on File section.
|
CvdInfo object mandatory values
Value |
Type |
Limits |
Set method |
Description |
CVD indicator |
String |
1-character numeric |
cvdCheck.SetCvdIndicator("1"); |
CVD presence indicator: 0: CVD value is deliberately bypassed or is not provided by the merchant. 1: CVD value is present. 2: CVD value is on the card, but is illegible. 9: Cardholder states that the card has no CVD imprint. |
CVD Value |
String |
4-character numeric |
cvdCheck.SetCvdValue("099"); |
CVD value located on credit card. The CVD value (supplied by the cardholder) must only be passed to the payment gateway. Under no circumstances may it be stored for subsequent use or displayed as part of the receipt information. |
AvsInfo object mandatory values
Value |
Type |
Limits |
Set method |
Description |
AVS street number |
String |
19-character alphanumeric1 |
avsCheck.SetAvsStreetNumber("212"); |
Cardholder street number. |
AVS street name |
String |
See AVS street number |
avsCheck.SetAvsStreetName("Payton Street"); |
Cardholder street name. |
AVS zip/postal code |
String |
9-character alphanumeric |
avsCheck.SetAvsZipCode("M1M1M1"); . |
Cardholder zip/postal code |
CVD & AVS Response Fields
Value |
Limits |
Get Method |
Description |
CVD result code |
2-character alphanumeric |
receipt.GetCvdResultCode(); |
Indicates the CVD validation result. The first byte is the numeric CVD indicator sent in the request; the second byte is the response code. Possible response codes are shown in the CVD Result Code table. |
AVS result code |
1-character alphanumeric |
receipt.GetAvsResultCode(); |
Indicates the address verification result. For a full list of possible response codes refer to the AVS Result Code table. |
Card verification with Credential on File
Merchants can use Card Verification with COF AVS and CVD as the first transaction prior to storing the credentials instead of Purchase or Preauthorization.
Verifies the validity of the credit card, expiry date and any additional details (such as the Card Verification Digits or Address Verification details). It does not verify the available amount or lock any funds on the credit card.
The Card Validation Digits (CVD) value refers to the numbers appearing on the back of the credit card rather than the numbers imprinted on the front. It is an optional fraud prevention tool that enables merchants to verify data provided by the cardholder at transaction time. This data is submitted along with the transaction to the issuing bank, which provides a response indicating whether the data is a match.
The response that is received from CVD verification is intended to provide added security and fraud prevention, but the response itself does not affect the completion of a transaction. Upon receiving a response, the choice whether to proceed with a transaction is left entirely to the merchant. The response is not a strict guideline of which transaction will approve or decline.
Address Verification Service (AVS) is an optional fraud-prevention tool offered by issuing banks whereby a cardholder's address is submitted as part of the transaction authorization. The AVS address is then compared to the address kept on file at the issuing bank. AVS checks whether the street number, street name and zip/postal code match. The issuing bank returns an AVS result code indicating whether the data was matched successfully. Regardless of the AVS result code returned, the credit card is authorized or declined by the issuing bank.
The response that is received from AVS verification is intended to provide added security and fraud prevention, but the response itself does not affect the completion of a transaction. Upon receiving a response, the choice to proceed with a transaction is left entirely to the merchant. The responses is not a strict guideline of whether a transaction will be approved or declined.
Things to consider:
Security:The CVD value must only be passed to the payment gateway. Under no circumstances may it be stored for subsequent uses or displayed as part of the receipt information.
namespace Moneris
{
using System;
public class TestCanadaCardVerficiation
{
public static void Main(string[] args)
{
string store_id = "store5";
string api_token = "yesguy";
string order_id = "Test" + DateTime.Now.ToString("yyyyMMddhhmmss");
string pan = "4242424242424242";
string expdate = "1901"; //YYMM format
string crypt = "7";
string processing_country_code = "CA";
bool status_check = false;
AvsInfo avsCheck = new AvsInfo();
avsCheck.SetAvsStreetNumber("212");
avsCheck.SetAvsStreetName("Payton Street");
avsCheck.SetAvsZipCode("M1M1M1");
CvdInfo cvdCheck = new CvdInfo();
cvdCheck.SetCvdIndicator("1");
cvdCheck.SetCvdValue("099");
CofInfo cof = new CofInfo();
cof.SetPaymentIndicator("U");
cof.SetPaymentInformation("2");
cof.SetIssuerId("168451306048014");
CardVerification cardVerification = new CardVerification();
cardVerification.SetOrderId(order_id);
cardVerification.SetPan(pan);
cardVerification.SetExpDate(expdate);
cardVerification.SetCryptType(crypt);
cardVerification.SetAvsInfo(avsCheck);
cardVerification.SetCvdInfo(cvdCheck);
cardVerification.SetCofInfo(cof);
HttpsPostRequest mpgReq = new HttpsPostRequest();
mpgReq.SetProcCountryCode(processing_country_code);
mpgReq.SetTestMode(true); //false or comment out this line for production transactions
mpgReq.SetStoreId(store_id);
mpgReq.SetApiToken(api_token);
mpgReq.SetTransaction(cardVerification);
mpgReq.SetStatusCheck(status_check);
mpgReq.Send();
try
{
Receipt receipt = mpgReq.GetReceipt();
Console.WriteLine("CardType = " + receipt.GetCardType());
Console.WriteLine("TransAmount = " + receipt.GetTransAmount());
Console.WriteLine("TxnNumber = " + receipt.GetTxnNumber());
Console.WriteLine("ReceiptId = " + receipt.GetReceiptId());
Console.WriteLine("TransType = " + receipt.GetTransType());
Console.WriteLine("ReferenceNum = " + receipt.GetReferenceNum());
Console.WriteLine("ResponseCode = " + receipt.GetResponseCode());
Console.WriteLine("ISO = " + receipt.GetISO());
Console.WriteLine("BankTotals = " + receipt.GetBankTotals());
Console.WriteLine("Message = " + receipt.GetMessage());
Console.WriteLine("AuthCode = " + receipt.GetAuthCode());
Console.WriteLine("Complete = " + receipt.GetComplete());
Console.WriteLine("TransDate = " + receipt.GetTransDate());
Console.WriteLine("TransTime = " + receipt.GetTransTime());
Console.WriteLine("Ticket = " + receipt.GetTicket());
Console.WriteLine("TimedOut = " + receipt.GetTimedOut());
Console.WriteLine("IsVisaDebit = " + receipt.GetIsVisaDebit());
Console.WriteLine("IssuerId = " + receipt.GetIssuerId());
Console.ReadLine();
}
catch (Exception e)
{
Console.WriteLine(e);
}
}
}
}
Card Verification transaction object definition
CardVerification cardVerification = new CardVerification();
HttpsPostRequest object for Card Verification transaction
HttpsPostRequest mpgReq = new HttpsPostRequest();
mpgReq.SetTransaction(cardVerification);
Card Verification transaction object mandatory values
Value |
Type |
Limits |
Set method |
Description |
Order ID |
String |
50-character alphanumeric |
cardVerification.SetOrderId(order_id); |
Merchant-defined transaction identifier that must be unique for every Purchase, Pre-Authorization and Independent Refund transaction. No two transactions of these types may have the same order ID. For Refund, Completion and Purchase Correction transactions, the order ID must be the same as that of the original transaction. The last 10 characters of the order ID are displayed in the “Invoice Number” field on the Merchant Direct Reports. However only letters, numbers and spaces are sent to Merchant Direct. A minimum of 3 and a maximum of 10 valid characters are sent to Merchant Direct. Only the last characters beginning after any invalid characters are sent. For example, if the order ID is 1234-567890, only 567890 is sent to Merchant Direct. If the order ID has fewer than 3 characters, it may display a blank or 0000000000 in the Invoice Number field. |
Credit card number |
String |
20-character alphanumeric |
cardVerification.SetPan(pan); |
Most credit card numbers today are 16 digits, but some 13-digit numbers are still accepted by some issuers. This field has been intentionally expanded to 20 digits in consideration for future expansion and potential support of private label card ranges. |
Expiry date |
String |
4-character alphanumeric (YYMM format) |
cardVerification.SetExpdate(expdate); |
Submit in YYMM format. Note: This is the reverse of the date displayed on the physical card, which is MMYY. |
E-commerce indicator |
String |
1-character alphanumeric |
cardVerification.SetCryptType(crypt); |
Describes the category of e-commerce transaction being processed. Allowable values are:
- 1 - Mail Order / Telephone Order—Single
- 2 - Mail Order / Telephone Order—Recurring
- 3 - Mail Order / Telephone Order—Instalment
- 4 - Mail Order / Telephone Order—Unknown classification
- 5 - Authenticated e-commerce transaction (VBV)
- 6 - Non-authenticated e-commerce transaction (VBV)
- 7 - SSL-enabled merchant
In Credential on File transactions where the request field e-commerce indicator is also being sent: the allowable values for e-commerce indicator are dependent on the value sent for payment indicator, as follows:
if payment indicator = R, then allowable values for e-commerce indicator: 2, 5 or 6
if payment indicator = C, then allowable values for e-commerce indicator: 1, 5, 6 or 7
if payment indicator = U, then allowable values for e-commerce indicator: 1 or 7
if payment indicator = Z, then allowable values for e-commerce indicator: 1, 5, 6 or 7
|
Card Verification transaction object conditional values
Value |
Type |
Limits |
Set method |
Description |
AVS |
Object |
Not applicable. |
cardVerification.SetAvsInfo(avsCheck); |
Note: It is optional for Canada. Refer below for further breakdown and definition. |
CVD |
Object |
Not applicable. |
cardVerification.SetCvdInfo(cvdCheck); |
Note:It is optional for Canada. Refer below for further breakdown and definition. |
COF Info
|
Object
|
|
cardVerification.SetCofInfo(cof);
|
For more information, see Card Verification with Credential on File section.
|
CvdInfo object mandatory values
Value |
Type |
Limits |
Set method |
Description |
CVD indicator |
String |
1-character numeric |
cvdCheck.SetCvdIndicator("1"); |
CVD presence indicator: 0: CVD value is deliberately bypassed or is not provided by the merchant. 1: CVD value is present. 2: CVD value is on the card, but is illegible. 9: Cardholder states that the card has no CVD imprint. |
CVD Value |
String |
4-character numeric |
cvdCheck.SetCvdValue("099"); |
CVD value located on credit card. The CVD value (supplied by the cardholder) must only be passed to the payment gateway. Under no circumstances may it be stored for subsequent use or displayed as part of the receipt information. |
AvsInfo object mandatory values
Value |
Type |
Limits |
Set method |
Description |
AVS street number |
String |
19-character alphanumeric1 |
avsCheck.SetAvsStreetNumber("212"); |
Cardholder street number. |
AVS street name |
String |
See AVS street number |
avsCheck.SetAvsStreetName("Payton Street"); |
Cardholder street name. |
AVS zip/postal code |
String |
9-character alphanumeric |
avsCheck.SetAvsZipCode("M1M1M1"); . |
Cardholder zip/postal code |
CVD & AVS Response Fields
Value |
Limits |
Get Method |
Description |
CVD result code |
2-character alphanumeric |
receipt.GetCvdResultCode(); |
Indicates the CVD validation result. The first byte is the numeric CVD indicator sent in the request; the second byte is the response code. Possible response codes are shown in the CVD Result Code table. |
AVS result code |
1-character alphanumeric |
receipt.GetAvsResultCode(); |
Indicates the address verification result. For a full list of possible response codes refer to the AVS Result Code table. |
Credential on File Info Object and Variables
The Credential on File Info object is nested within the request for the applicable transaction types.
Object:
Variables in the cof object:
- PaymentIndicator
- PaymentInformation
- IssuerID
For more information, see Definitions of Request Fields – Credential on File below.
Definitions of Request Fields – Credential on File
COF Info Object mandatory values
Value |
Type |
Limits Set |
Method |
IssuerID
NOTE: This variable is
required for all merchant-
intiated transactions
following the
first one; upon sending
the first transaction,
the IssuerID value is
received in the transaction
response and
then used in subsequent
transaction
requests (IssuerID
does not apply for Discover
or Union Pay). |
String |
15-character alphanumeric
variable length |
cof.setIssuerId("VALUE_FOR_
ISSUER_ID");
NOTE: For a list and explanation of the
possible values to send for this variable,
see Definitions of Request Fields – Credential
on File |
PaymentIndicator |
String |
1-character alphabetic |
cof.setPaymentIndicator
("PAYMENT_INDICATOR_VALUE");
NOTE: For a list and explanation of the
possible values to send for this variable,
see Definitions of Request Fields – Credential
on File |
PaymentInformation |
String |
1-character numeric |
cof.setPaymentInformation
("PAYMENT_INFO_VALUE");
NOTE: For a list and explanation of the
possible values to send for this variable,
see Definitions of Request Fields – Credential
on File |
Card Verification with Vault and CVD & AVS
This transaction uses the data key to identify a previously registered credit card profile. The details saved within the profile are then submitted to perform a Card Verification transaction.
The data key may be a temporary one generated using Hosted Tokenization or it may be a permanent one from the Vault.
The Vault feature allows merchants to create long term customer profiles, edit those profiles, and use them to process transactions without having to enter financial information each time.
The only difference between processing a Card Verification using a temporary token versus a standard Vault token is whether the expiry date is sent. With the Vault token, the expiry date is stored along with the card number as part of the Vault profile. Therefore, there is no need to send the expiry date again with each normal Vault transaction. However, a temporary token transaction may have only stored the card number. Therefore, in this scenario the expiry date must be sent when you submit the Card Verification.
Things to consider:
Security:The CVD value must only be passed to the payment gateway. Under no circumstances may it be stored for subsequent uses or displayed as part of the receipt information.
namespace Moneris
{
using System;
public class TestResCardVerificationCC
{
public static void Main(string[] args)
{
string store_id = "store5";
string api_token = "yesguy";
string data_key = "V6F9PJKdXQj6vKiCMNrWbsyJ2";
string order_id = "Test_P_033333_6";
string cust_id = "Customer1";
string crypt = "7";
string processing_country_code = "CA";
bool status_check = false;
/*************** Address Verification Service **********************/
AvsInfo avsCheck = new AvsInfo();
avsCheck.SetAvsStreetNumber("212");
avsCheck.SetAvsStreetName("Payton Street");
avsCheck.SetAvsZipCode("M1M1M1");
/****************** Card Validation Digits *************************/
CvdInfo cvdCheck = new CvdInfo();
cvdCheck.SetCvdIndicator("1");
cvdCheck.SetCvdValue("099");
/*************** Credential on File *************************************/
CofInfo cof = new CofInfo();
cof.SetPaymentIndicator("U");
cof.SetPaymentInformation("2");
cof.SetIssuerId("168451306048014");
ResCardVerificationCC rescardverify = new ResCardVerificationCC();
rescardverify.SetDataKey(data_key);
rescardverify.SetOrderId(order_id);
rescardverify.SetCustId(cust_id);
//rescardverify.SetExpDate("1612"); //for use with Temp Tokens only
rescardverify.SetCryptType(crypt);
rescardverify.SetAvsInfo(avsCheck);
rescardverify.SetCvdInfo(cvdCheck);
rescardverify.SetCofInfo(cof);
HttpsPostRequest mpgReq = new HttpsPostRequest();
mpgReq.SetProcCountryCode(processing_country_code);
mpgReq.SetTestMode(true); //false or comment out this line for production transactions
mpgReq.SetStoreId(store_id);
mpgReq.SetApiToken(api_token);
mpgReq.SetTransaction(rescardverify);
mpgReq.SetStatusCheck(status_check);
mpgReq.Send();
try
{
Receipt receipt = mpgReq.GetReceipt();
Console.WriteLine("CardType = " + receipt.GetCardType());
Console.WriteLine("TransAmount = " + receipt.GetTransAmount());
Console.WriteLine("TxnNumber = " + receipt.GetTxnNumber());
Console.WriteLine("ReceiptId = " + receipt.GetReceiptId());
Console.WriteLine("TransType = " + receipt.GetTransType());
Console.WriteLine("ReferenceNum = " + receipt.GetReferenceNum());
Console.WriteLine("ResponseCode = " + receipt.GetResponseCode());
Console.WriteLine("ISO = " + receipt.GetISO());
Console.WriteLine("BankTotals = " + receipt.GetBankTotals());
Console.WriteLine("Message = " + receipt.GetMessage());
Console.WriteLine("AuthCode = " + receipt.GetAuthCode());
Console.WriteLine("Complete = " + receipt.GetComplete());
Console.WriteLine("TransDate = " + receipt.GetTransDate());
Console.WriteLine("TransTime = " + receipt.GetTransTime());
Console.WriteLine("Ticket = " + receipt.GetTicket());
Console.WriteLine("TimedOut = " + receipt.GetTimedOut());
Console.WriteLine("IsVisaDebit = " + receipt.GetIsVisaDebit());
Console.WriteLine("IssuerId = " + receipt.GetIssuerId());
Console.ReadLine();
}
catch (Exception e)
{
Console.WriteLine(e);
}
}
} // end TestResCardVerificationCC
}
Card Verification with Vault transaction object definition
ResCardVerificationCC resCardVerificationCC = new ResCardVerificationCC();
HttpsPostRequest mpgReq = new HttpsPostRequest();
mpgReq.SetTransaction(resCardVerificationCC);
Card Verification with Vault transaction object mandatory values
Value |
Type |
Limits |
Set method |
Description |
Order ID |
String |
50-character alphanumeric |
resCardVerification.SetOrderId(order_id); |
Merchant-defined transaction identifier that must be unique for every transaction. No two transactions may have the same order ID |
Data Key |
String |
25-character alphanumeric |
resCardVerificationCC.SetDataKey(data_key); |
The data key is the token that points to a previously stored profile. Profile identifier that all future financial Vault transactions (that is, they occur after the profile was registered by a Vault Add Credit Card or Vault Tokenize Credit Card transaction, for example) will use to associate with the saved information.
The data key is generated by Moneris, and is returned to the merchant (via the Receipt object) when the profile is first registered. |
E-commerce indicator |
String |
1-character alphanumeric |
resCardVerificationCC.SetCryptType(crypt); |
Describes the category of e-commerce transaction being processed. Allowable values are:
- 1 - Mail Order / Telephone Order—Single
- 2 - Mail Order / Telephone Order—Recurring
- 3 - Mail Order / Telephone Order—Instalment
- 4 - Mail Order / Telephone Order—Unknown classification
- 5 - Authenticated e-commerce transaction (VBV)
- 6 - Non-authenticated e-commerce transaction (VBV)
- 7 - SSL-enabled merchant
In Credential on File transactions where the request field e-commerce indicator is also being sent: the allowable values for e-commerce indicator are dependent on the value sent for payment indicator, as follows:
if payment indicator = R, then allowable values for e-commerce indicator: 2, 5 or 6
if payment indicator = C, then allowable values for e-commerce indicator: 1, 5, 6 or 7
if payment indicator = U, then allowable values for e-commerce indicator: 1 or 7
if payment indicator = Z, then allowable values for e-commerce indicator: 1, 5, 6 or 7
|
Card Verification with Vault transaction object conditional values
Value |
Type |
Limits |
Set method |
Description |
Expiry Date |
Sring |
4-character alphanumeric (YYMM format) |
resCardVerificationCC.SetExpdate(expdate); |
The optional Expiry Date applies to Hosted Tokenization transactions. If the expiry date was not collected by the Hosted Tokenization solution, then it must be set in the Vault transaction request – it is then a mandatory field. |
AVS |
Object |
Not applicable. |
resCardVerification.SetAvsInfo(avsCheck); |
Note: It is optional for Canada.
If the Vault profile already has AVS details stored on file, then AVS is optional and the AVS data stored in the profile will be used for the validation. |
CVD |
Object |
Not applicable. |
resCardVerification.SetCvdInfo(cvdCheck); |
Note: It is optional for Canada.
If the temporary token generated using Hosted Tokenization already has the CVD details, then CVD is optional and the CVD value collected in by Hosted Tokenization will be used for the validation.
|
COF Info
|
Object
|
|
rescardverify.SetCofInfo(cof);
|
For more information, see Card Verification with Credential on File section.
|
CvdInfo object mandatory values
Value |
Type |
Limits |
Set method |
Description |
CVD indicator |
String |
1-character numeric |
cvdCheck.SetCvdIndicator("1"); |
CVD presence indicator: 0: CVD value is deliberately bypassed or is not provided by the merchant. 1: CVD value is present. 2: CVD value is on the card, but is illegible. 9: Cardholder states that the card has no CVD imprint. |
CVD Value |
String |
4-character numeric |
cvdCheck.SetCvdValue("099"); |
CVD value located on credit card. The CVD value (supplied by the cardholder) must only be passed to the payment gateway. Under no circumstances may it be stored for subsequent use or displayed as part of the receipt information. |
AvsInfo object mandatory values
Value |
Type |
Limits |
Set method |
Description |
AVS street number |
String |
19-character alphanumeric1 |
avsCheck.SetAvsStreetNumber("212"); |
Cardholder street number. |
AVS street name |
String |
See AVS street number |
avsCheck.SetAvsStreetName("Payton Street"); |
Cardholder street name. |
AVS zip/postal code |
String |
9-character alphanumeric |
avsCheck.SetAvsZipCode("M1M1M1"); . |
Cardholder zip/postal code |
Vault Response Fields
Value |
Limits |
Get Method |
Description |
Data Key |
25-character alphanumeric |
receipt.GetDataKey(); |
This field is created when a profile is created and a token is returned. It is a unique profile identifier, and is a required value for all future Vault transactions. |
Vault Success |
true/false |
receipt.GetResSuccess(); |
Indicates whether Vault transaction was successful. |
Payment Type |
cc |
receipt.GetPaymentType(); |
Indicates the payment type associated with a Vault profile. |
Customer ID |
30-character alphanumeric |
receipt.GetResCustId(); |
Returns the customer ID saved in the profile. |
Phone Number |
30-character alphanumeric |
receipt.GetResPhone(); |
Returns the phone number saved in the profile. |
Email Address |
30-character alphanumeric |
receipt.GetResEmail(); |
Returns the email address saved in the profile. |
Note |
30-character alphanumeric |
receipt.GetResNote(); |
Returns the note saved in the profile. |
Credit Card Fields |
Masked PAN |
20-character numeric |
receipt.GetResMaskedPan(); |
Returns the first 4 last 4 of the card number saved in the profile. |
Expiry Date |
4-character numeric |
receipt.GetResExpdate(); |
Returns the expiry date of the card number saved in the profile. YYMM format. |
E-Commerce Indicator |
1-character numeric |
receipt.GetResCryptType(); |
Returns the e-commerce indicator saved in the profile. |
AVS Street Number |
19-character alphanumeric |
receipt.GetResAvsStreetNumber(); |
Returns the AVS street number saved in the profile. If no other AVS street number is passed in the transaction request, this value will be submitted along with the financial transaction to the issuer. |
AVS Street Name |
19-character alphanumeric |
receipt.GetResAvsStreetName(); |
Returns the AVS street name saved in the profile. If no other AVS street number is passed in the transaction request, this value will be submitted along with the financial transaction to the issuer. |
AVS Zip/Postal Code |
9-character alphanumeric |
receipt.GetResAvsZipcode(); |
Returns the AVS zip/postal code saved in the profile. If no other AVS street number is passed in the transaction request, this value will be submitted along with the financial transaction to the issuer. |