On This Page
FILTER BY TAG

Required Fields for Authorizing a Visa Payment on Paze with Merchant Decryption

As a best practice, include these REST API fields in your request for an authorization with the merchant decryption implementation of Paze for Visa.
IMPORTANT
Depending on your processor, your geographic location, and whether the relaxed address verification system (RAVS) is enabled for your account, some of these fields might not be required. It is your responsibility to determine whether an API field can be omitted from the transaction you are requesting.
For information about the relaxed requirements for address data and expiration dates in payment transactions, see the .
Set this field to
vbv
.
Set this field to the network token cryptogram.
Set this field to the value from the payment network token expiration month.
Set this field to the value from the payment network token expiration year.
Set this field to the payment network token value.
Set this field to
1
.
Set this field to
001
 for Visa.
The mandate to use 3-D Secure for Paze transactions varies by geographic location.
 For Visa card transactions, 3-D Secure is called
Visa Secure
.
  • If the transaction does not use 3-D Secure, set this field to the ECI value contained in the Paze response payload.
  • If the transaction uses 3-D Secure, set this field to
    vbv
    .
Set this field to
029
 to specify the Paze payment solution.
RELATED TO THIS PAGE