Vero
To make transactions with the Vero acquirer on Carat Portal, besides the basic parameters of each service, some additional data is necessary.
Supported Carat Portal interfaces#
It's possible to use the following interfaces for integration with the Vero routing:
- REST Payment
- HTML Payment
- REST Pre-Authorization
- HTML Pre-Authorization
- REST Cancel
- Cancel via Merchant's Portal
REST Payment#
Payment Effectuation#
Below are the parameters with specific data for Vero transactions which the merchant's application can send on the payment effectuation service:
| Parameter | Description | Format | Mandatory |
|---|---|---|---|
card | |||
holder_present | Indicates whether the card holder is present or not. Send true if positive, or false otherwise. Default value: true | < 5 AN | NO |
external_authentication | |||
eci | Eletronic Commerce Indicator – indicates the security level of the transaction with card holder authentication. | < 3 N | NO |
reference_id | Identifier of the transaction with card holder authentication on 3DS 1.0 transactions. | < 40 AN | NO |
cavv | Cardholder Authentication Verification Value - code that indicates the authentication result. | < 40 AN | NO |
ucaf_sli | Contains the UCAF (Universal Cardholder Authentication Field), which corresponds to SLI's last digit (Security Level Indicator) from Mastercard Secure Code. | = 1 N | NO |
version | 3DS version (1 or 2). | = 1 N | NO |
reference_id | Directory Server identifier for 3DS 2.0 transactions. | < 36 AN | NO |
tavv | DSRP-UCAF tokenized transaction cryptogram. | < 40 AN | NO |
cavv | Cardholder Authentication Verification Value - Codes that refers to card holder authentication result data. | < 40 N | NO |
acquirer | |||
ecommerce_device_type | Device type. | < 2 AN | NO |
token_req_id | Token requestor ID. | < 11 N | NO |
pan_token_relation_level | PAN & Token relation level. | < 2 AN | NO |
ecommerce_input_type | 1: E-commerce2: Server3: MasterCard DSRP Full EMV.Default value: 1 | = 1 N | YES |
Sending authentication data for debit transactions is mandatory.
REST Pre-Authorization#
Pre-Authorization Creation#
The specific parameters for the pre-authorization creation service are the same from the payment service, along with the following field:
| Parameter | Description | Format | Mandatory |
|---|---|---|---|
additional_data | |||
pre_auth_lifecycle | Represents the number of days in which the pre-authorization is considered valid. | < 2 N | YES |
Pre-Authorization Capture#
The specific parameters for the pre-authorization capture service are the same from the payment service cited above.