Payment Modifications
Original transaction id to cancel / void.
76944d4b-89e6-48d2-ac04-675383c3eedfEcommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfToken used for authorizing a payment transaction.
The reason a transaction has been refused within the payment ecosystem by the client/Verifone/acquirer. This needs to be set by the component that is refusing this transaction request.
A reference specified by the merchant to identify the transaction.
7a1db7a8-6f24-4bc5-a51b-cef33fc05140The Klarna Complete Payment Response.
Bad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
Original transaction id to adjust.
76944d4b-89e6-48d2-ac04-675383c3eedfAmount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, refer to the Currencies documentation for more details. The amount provided determines the type of adjustment. If it is greater than the original pre-authorization amount, it is treated as an increment. If it is less than the original pre-authorization amount, it is treated as a decrement. To fully void a transaction after an increment, set the amount to 0.
150The reason of the adjust.
Ecommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Original transaction id to capture.
76944d4b-89e6-48d2-ac04-675383c3eedfAmount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
150The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
This field indicates the taxable status of the transaction (if any of the purchased items are taxable). This field is part of so-called Level 2 data. If the value TAX_PROVIDED is sent, tax_amount should also be provided
TAX_NOT_PROVIDEDPossible values: Defines the type of receipt to be generated
Ecommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Original transaction id to refund.
76944d4b-89e6-48d2-ac04-675383c3eedfNote: This value is required to process a refund for an Affirm payment.
63bbc548-d2de-4546-b106-880a5018461cAmount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
150The reason of the refund.
This field indicates the taxable status of the transaction (if any of the purchased items are taxable). This field is part of so-called Level 2 data. If the value TAX_PROVIDED is sent, tax_amount should also be provided
TAX_NOT_PROVIDEDPossible values: A code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Defines the type of receipt to be generated
Ecommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Ecommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Original transaction id to cancel / void the capture.
76944d4b-89e6-48d2-ac04-675383c3eedfEcommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
string(uuid)
Technical Reversal Result
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Original preauthorized transaction id to release
76944d4b-89e6-48d2-ac04-675383c3eedfstring(uuid)
Example: 63bbc548-d2de-4546-b106-880a5018461c A value you specify that uniquely identifies this transaction. If you're unsure whether a particular transaction succeeded, you can reattempt it with the same idempotency key without worrying about duplicating the transaction.
Amount is charged without a decimal place e.g. $1.5 = 150. The required number of decimal places for a currency code is according to ISO For Account Verification transaction, provide 0 as value for this field.
Ecommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Original preauthorized transaction id to release
76944d4b-89e6-48d2-ac04-675383c3eedfstring(uuid)
Example: 63bbc548-d2de-4546-b106-880a5018461c A value you specify that uniquely identifies this transaction. If you're unsure whether a particular transaction succeeded, you can reattempt it with the same idempotency key without worrying about duplicating the transaction.
Ecommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
Original transaction id to apply instalment selection to.
76944d4b-89e6-48d2-ac04-675383c3eedfEcommerce Payment Result
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
Optional. The invoice number to track this payment.
A reference specified by the merchant to identify the transaction
The payment product corresponding to this transaction
The name of the processor used for this transaction
Reference identifying the transaction, as provided by the processor.
Stores all details specific for the processor of the transaction.
The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
Acquirer reference number. Generated by the Acquirer at the time of clearing for card transactions.
-
When the payment is authorized successfully, this field holds the authorization code for the payment.
-
When the payment is not authorized, this field is not returned.
5B1D4CAddress verification services result, which provides information about the outcome of the AVS check. The full list of codes and descriptions can be found here
APossible values: The token representing the payment card
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
True if the card was used with a cvv
The CVC verification result, which provides information about the outcome of the CVC check.
CVC-CVV result codes:
0Unknown1Matches.2Doesn't match.3Not checked.4No CVC/CVV provided, but was required.5Issuer not certified for CVC/CVV.6No CVC/CVV provided.
The following are included only for backwards compatibility. They are deprecated and will be removed in the next major release. The client must take action now to ensure ongoing support.
MMatchYMatchNNo MatchPNot ProcessedSCVV Should be present, but Merchant indicates not present.UIssuer not certified or registered to process card verification.
1Possible values: This field will be populated for any Verified by Visa transaction and AVV Authorisation message sent by MasterCard SecureCode: This includes CAVV and AEVV from American Express SafeKey.
CAVV Transaction Response Code Values:
-
0CAVV or AEVV Not Validated due to erroneous data submitted. -
1CAVV or AEVV Failed Validation - Authentication Transaction. This is an indication of potential bad or fraudulent data submitted. -
2CAVV or AEVV Passed Validation – Authentication Transaction. -
3CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (Determined that the Issuer ACS generated this value from the use of the Issuer’s CAVV/AEVV key[s]). -
4CAVV or AEVV Failed Validation – Attempted Authentication Transaction. Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (Determined that Visa generated this value from the use of CAVV/AEVV key[s]). -
5Reserved. -
6CAVV or AEVV Not Validated – Issuer not participated. This value is generated when an Issuer requests thedo not verifyflag to be established for its BINs. This parameter enables an Issuer to temporarily stop CAVV/AEVV verification while resolving CAVV/AEVV key issues. VisaNet processes this value as a valid CAVV/AEVV. -
7CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
8CAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key). -
9CAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
99An unknown value was returned from the processor. -
ACAVV or AEVV Passed Validation – Attempted Authentication Transaction. (CAVV/AEVV generated with Visa Key – Issuer ACS unavailable). -
BCAVV or AEVV Failed Validation – Attempted Authentication Transaction. This is an indication of potential bad or fraudulent data submitted as the CAVV/AEVV. (CAVV/AEVV generated with Visa Key). -
CCAVV or AEVV Not Validated – Attempted Authentication Transaction. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
DCAVV or AEVV Not Validated – Authentication. Issuer did not return a CAVV/AEVV results code in the authorisation response. VisaNet will treat this as valid CAVV/AEVV if the Issuer approves the authorisation. -
IInvalid Security Data. -
UIssuer does not participate or 3-D Secure data not utilised. -
NABlank CAVV or AEVV Not Present.
99Possible values: A reason code assigned by the acquiring platform; '0000' in case of success
A client (user friendly) identifier for the transaction generated at the outset of a business event. The format will be dependent on the calling system.
A reference supplied by the system retaining the original source information and used to assist in locating that transaction or a copy of the transaction. This value is critical in matching values that are sent to other Payment processors or Acquirers. This value would correspond to the ISO8583 specification as RRN in attribute DE 37, which limits the value to being an alphanumeric value 12 characters.
For the GSC client android application the format will correspond to YYMMdd<stan 6 digits>.
200211654321Determines the point of sale of a customer. Possible values: pos, moto, mail_order, telephone_order, ecommerce and cont_auth
System Trace Audit Number.
Indicates to the API client if a technical reversal has been completed by Verifone.
NONEPossible values: The latitude / longitude resolved from the customer's ip address.
["52.370216","4.895168"]The city resolved from the customer's ip address.
West RoxburyThe country code resolved from the customer's ip address.
USA code defined by the merchant that affects the calculation of the total amount.
The purchase order number. It can be provided in transactions with purchase or procurement cards for the cardholder to get better interchange rates (note that this functionality needs alignment with the acquirer and the scheme). This field is part of so-called Level 2 data.
Balance amount is the amount remaining on a card or account of cardholder without a decimal place e.g. $1.5 = 150.
The required number of decimal places for a currency code is according to ISO 4217. However the following table takes precedence over ISO 4217:
Bad Request
Unauthorised
Forbidden
Not Found
Internal Server Error
A value you specify that uniquely identifies this transaction. This must be used to trigger a reversal if there is a timeout.
63bbc548-d2de-4546-b106-880a5018461cA reference specified by the merchant to identify the transaction
The reason a transaction has been refused within the payment ecosystem by the client/Verifone/acquirer. This needs to be set by the component that is refusing this transaction request.
The Affirm Initiation Response.
The ID of the transaction.
76944d4b-89e6-48d2-ac04-675383c3eedfThe time when the auth transaction will expire (i.e. before which capture must be made). The value is formatted in RFC 3339.
Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
150Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to ISO 4217.
Deprecated: BYR (replaced by BYN), FRF (replaced by EUR), LTL (replaced by EUR), LVL (replaced by EUR), MRO (replaced by MRU), STD (replaced by STN), USS (no replacement), VEF (replaced by VES), ZMK (replaced by ZMV) and BTC (Bitcoin only supported as Crypto Amount).
The time at which the transaction was created.
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
The ID of a customer
A reference specified by the merchant to identify the transaction
The name of the processor used for this transaction
KLARNAThe payment product corresponding to this transaction
KLARNAThe payment product type corresponding to this transaction. Fees applied to the transaction, is based on the payment product
UnknownPossible values: The outcome of the payment request.
AUTHORIZEDPossible values: Message provided by the 3rd party service as additional information, when the transaction does not succeed.
The latitude / longitude resolved from the customer's ip address.
[52.370216,4.895168]The ISO 3166-1 alpha-2 country code.
Note: The country code for Great Britain is.GBand notUKas is used in that country's top-level domain names.
EUBad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
Last updated
Was this helpful?