ClearSale
#
Required credentialsAs mentioned in "Overview - Required credentials", each institution has credentials that must be obtained for the integration. ClearSale's services demand credentials below:
- Login (Merchant ID) - Login of the ClearSale merchant registration.
- Password (Merchant Code) - Password of the store registration at ClearSale.
IMPORTANT: The credentials above should be obtained from ClearSale. It is recommended to contact ClearSale and receive guidance on how to obtain the credentials. Then, the merchant should contact Carat Portal support and send the credentials to register in Carat Portal.
#
Webhook URL ConfigurationIn order for us to receive status updates from the risk analysis transactions, it is necessary to configure the webhook URL on the Konduto configuration environment.
Production URL:
https://esitef-ec.softwareexpress.com.br/e-sitef/processarPost.se?src=clearsale_rest
URL de Homologação:
https://esitef-homologacao.softwareexpress.com.br/e-sitef/processarPost.se?src=clearsale_rest
This URL must be configured for any status changes. To perform this configuration, please contact ClearSale Support.
#
Starting a transaction with Anti-FraudAfter performing the registration alignment with Carat Portal support to enable integration with the anti-fraud service, at the start of a transaction REST Payment (Learn more) or REST Pre Authorization (Learn more) the merchant must configure the property anti_fraud
and send the appropriate anti-fraud parameters (depends on the institution that your merchant was set up), both properties must be within the scope of the additional_data
object.
The anti_fraud
field determines how anti-fraud is applied and can contain the following values:
enabled_before_auth
- Risk analysis will be performed BEFORE authorization of the payment. If the analysis is rejected, payment will not be started. In the case of pre-authorization with non-SiTef routings, if the risk analysis remains as a manual analysis, Carat leaves the transaction in the PPC (Payment Pending Confirmation) state and waits for a conclusion of the manual analysis.enabled_after_auth
- Risk analysis will be performed AFTER authorization of the payment. If the analysis is rejected, the payment that has already been authorized will be canceled. In the case of pre-authorization with non-SiTef routings, Carat leaves the transaction in the PPC (Payment Pending Confirmation) state and waits for a conclusion of the manual analysis.
NOTE: Transactions that are pending payment can be confirmed or undone by time limit. Learn more.
#
Realtime ClearSale ConfigurationAfter performing the registration adjustment with the carat support team to enable the integration with the clearSale service,
the store must initiate a REST or HTML payment transaction by sending the "anti_fraud" property and sending the parameters
additional data collected for risk analysis of the transaction being sent in the additional_data
object.
#
ClearSale service versions supported by payment interface:ClearSale - Total
ClearSale - RealTime
#
ClearSale REST Anti-Fraud ParametersBelow is a list of anti-fraud parameters processed by ClearSale.
Attention: The fields below are specific to the ClearSale integration and their mandatory criteria and format refer to the validations made by the fraud analysis institution. It is important that these criteria are respected for an effective and accurate analysis.
Parameter | Description | Mandatory | Format | |||
---|---|---|---|---|---|---|
additional_data | Additional transaction data | |||||
b2b_b2c | Ecommerce type. | NO | 3 A | |||
item_amount | Total Value of Items in cents | YES | <1024 N | |||
total_order_amount | Total Order Amount in cents. Composed of the Total Value of the Items + Shipping Value + Possible Interest Value of the Purchase | YES | <1024 N | |||
gift | Identifies if the order is a gift: 1 - is a gift0 - is not a giftIf absent, the value 0 is assumed. | NO | 1 N | |||
gift_message | Gift Message | NO | <1024 AN | |||
obs | Order Observation | NO | <1024 AN | |||
sla_custom | Maximum Order Review SLA Minutes Value, if any | NO | 4 N | |||
origin | Order Origin Channel (ex: TELE SALES, WEBSITE, APP, etc.) | YES | <150 A | |||
channel_id | Complementary Source Channel, if any. (ex: ANDROID, IOS, etc.) | NO | <1024 AN | |||
reservation_date | Date of First Flight of the Request (in case of airline tickets). | NO | yyyy-mm-ddThh:mm:ss | |||
nationality | Nationality | NO | <50 AN | |||
product | ClearSale product identifier: -1 (Others)1 (Application)3 (Total)4 (Total Garantido)9 (Score)10 (Realtime Decision)11 (Tickets) | NO | 2N | |||
bank_authentication | Bank authentication type | NO | <1024 AN | |||
sub_acquirer | Sub-acquirer name | NO | <1024 AN | |||
list_type_id | List Type: 1 - Unregistered List2 - Baby Shower List3 - Wedding List4 - Wish List 5 - Birthday List6 - Bridal Shower | NO | 1N | |||
list_id | List ID in Store | NO | <200 AN | |||
additional_data .payer | Buyer related information | |||||
email | Buyer's email | YES | <1024 AN | |||
name | Buyer name | YES | <150 A | |||
legal_document | Buyer's document number | YES | <100 A | |||
additional_data .browser | Information relating to the buyer's browser | |||||
ip_address | Order IP | NO | <1024 AN | |||
additional_data .purchase_information_data | Purchase related information | |||||
last_date_change_inserted_mail | Date of last email change | NO | yyyy-mm-ddThh:mm:ss | |||
last_date_change_password | Date of last password change | NO | yyyy-mm-ddThh:mm:ss | |||
last_date_change_phone | Date of last phone change | NO | yyyy-mm-ddThh:mm:ss | |||
last_date_change_mobile_phone | Mobile phone last change date | NO | yyyy-mm-ddThh:mm:ss | |||
last_date_inserted_address | Date of last address change | NO | yyyy-mm-ddThh:mm:ss | |||
purchase_logged | Flag that indicates purchase with logged in user:1 for YES0 for NOIf absent or invalid, value 0 is assumed | NO | 1N | |||
email | Registration Email | NO | <1024 AN | |||
login | Access Login | NO | <1024 AN | |||
additional_data .social_network | Information about linked social networks | |||||
social_network.opt_in_buy_and_trust | Flag indicating if the customer accepts to join the Buy and Trust movement:1 for YES0 for NOIf absent or invalid, value 0 is assumed | NO | 1N | |||
social_network.type_social_network | Linked Social Network Identifier:1 - Facebook2 - Twitter3 - Linkedin4 - Google5 - Others | NO | 1N | |||
social_network.authentication_token | Token returned by the Social Network | NO | <1024 AN | |||
additional_data .billing_data | Billing information | |||||
client_id | Customer code | NO | <1024 AN | |||
person | Type of Person:1 - Individual2 - Legal Entity | YES | 1N | |||
cnpj_cpf | CPF or CNPJ. If absent, ClearSale uses the value informed in the additional_data.billing_data.documents[] list using the keys CPF or CNPJ , whichever comes first. | COND | <1024 AN | |||
identification_number | RG or State Registration. If absent, ClearSale uses the first value informed in the additional_data.billing_data.documents[] list using the RG key. | COND | <1024 AN | |||
name | Client name | YES | <1024 A | |||
birth_date | Birth date | NO | yyyy-mm-ddThh:mm:ss | |||
email | NO | <1024 AN | ||||
gender | Buyer's Gender:M - MaleF - Female | NO | 1A | |||
billing_data .address | ||||||
street_name | Street name | YES | <1024 AN | |||
street_number | Address Number | YES | <1024 AN | |||
complement | Address complement | NO | <1024 AN | |||
county | Address county | YES | <1024 AN | |||
city | Address City | YES | <1024 AN | |||
state | Address State Abbreviation | YES | 2 A | |||
country | Address Country | NO | <1024 AN | |||
zip_code | Address zip code | YES | <1024 AN | |||
reference | Address Reference | NO | <1024 AN | |||
billing_data .phones[] | Information regarding billing phones (fields marked with YES are only mandatory if the phones object is created) | |||||
type | Phone type:0 - Not defined1 - Residential2 - Commercial3 - Messages4 - Billing 5 - Temporary6 - Mobile | YES | 1N | |||
ddi | Telephone DDI | NO | 3 N | |||
ddd | Telephone DDD | YES | 2 N | |||
number | Telephone number | YES | 9 N | |||
extension | Telephone extension | NO | 10 N | |||
billing_data .documents[] | Information regarding billing identification documents | |||||
type | Document Type: CPF CNPJ | NO | <1024 AN | |||
number | Document number | NO | <1024 AN | |||
additional_data .shipment | ||||||
client_id | customer code | NO | <1024 AN | |||
person | Type of Person:1 - Individual2 - Legal Entity | YES | 1N | |||
cnpj_cpf | CPF or CNPJ. If absent, ClearSale uses the value informed in the additional_data.shipment.documents[] list using the keys CPF or CNPJ , whichever comes first. | COND | <1024 AN | |||
identification_number | RG or State Registration. If absent, ClearSale uses the first value informed in the additional_data.shipment.documents[] list using the RG key. | COND | <1024 AN | |||
name | Recipient's name | YES | <1024 AN | |||
birth_date | Recipient's date of birth | NO | yyyy-mm-ddThh:mm:ss | |||
email | Recipient's Email | NO | <1024 AN | |||
gender | Recipient's Gender:M - MaleF - Female | NO | 1A | |||
delivery_type | Delivery type:0 - Other1 - Normal2 - Guaranteed3 - ExpressBR4 - ExpressSP5 - High6 - Economic7 - Scheduled8 - Extra Fast9 - Printed 10 - Application11 - Mail12 - Motoboy13 - Ticket office withdrawal14 - Partner Store withdrawal15 - Ticket Credit Card16 - Store Pickup17 - Withdrawal via Lockers (Partners)18 - Post Office Pickup19 - Guaranteed delivery on the same day of purchase20 - Guaranteed delivery on the next day of purchase21 - Pickup in store - Express | YES | < 2N | |||
delivery_time | Deadline | NO | <1024 AN | |||
cost | Shipping cost in cents | NO | <1024 N | |||
pickup_store_document | CPF for pick up in store (if the order is for some type of delivery "Withdrawal") | NO | <1024 N | |||
shipment .address | ||||||
street_name | Street name | YES | <1024 AN | |||
street_number | Address Number | YES | <1024 AN | |||
complement | Address complement | NO | <1024 A | |||
county | Address county | YES | <1024 AN | |||
city | Address City | YES | <1024 AN | |||
state | Address State Abbreviation | YES | 2 A | |||
country | Address Country | NO | <1024 AN | |||
zip_code | Address zip code | YES | <1024 AN | |||
reference | Address Reference | NO | <1024 AN | |||
shipment .phones[] | Information regarding delivery phones (fields marked with YES are only mandatory if the phones object is created) | |||||
type | Phone type:0 - Not defined1 - Residential2 - Commercial3 - Messages4 - Billing 5 - Temporary6 - Mobile | YES | 1N | |||
ddi | Telephone DDI | NO | 3 N | |||
ddd | Telephone DDD | YES | 2 N | |||
number | Telephone number | YES | 9N | |||
extension | Telephone extension | NO | 10 N | |||
billing_data .documents[] | Information regarding identification documents for delivery | |||||
type | Document Type: CPF CNPJ | NO | <1024 AN | |||
number | Document number | NO | <1024 AN | |||
additional_data .items[] | Information regarding purchased items | |||||
id | Product code | NO | <1024 AN | |||
title | Product's name | YES | <1024 AN | |||
ean | EAN (Barcode) of the product | NO | <1024 AN | |||
unit_price | Unit Value in cents | NO | <1024 N | |||
quantity | Quantity | NO | <1024 N | |||
category_id | Product Category Code | NO | <1024 N | |||
category_name | Product Category Name | NO | <1024 AN | |||
gift | Identifies if the order is a gift: 1 - it is a gift0 - not a giftIf absent, the 0 value is assumed | NO | 1N | |||
sellerName | Seller's/partner's trade name | NO | <1024 AN | |||
sellerDocument | Seller/partner CNPJ | NO | <1024 AN | |||
marketPlace | Flag indicating whether the establishment is a market place:true or false | NO | <5 A | |||
sellerSegment | Seller/Partner Segment. | NO | <1024 AN | |||
shippingCompany | Carrier name | NO | <1024 AN | |||
sequential | Sequence of making the payment | NO | <1024 N | |||
voucher_order_origin | Order ID that generated the exchange voucher (if the current payment method is Vale ) | NO | <1024 AN | |||
payer .receiver_address | Information regarding the payment address (fields marked with YES are only mandatory if the receiver_address object is created) | |||||
street_name | Street name | YES | <1024 AN | |||
street_number | Address Number | YES | <1024 AN | |||
complement | Address complement | NO | <1024 A | |||
county | Address county | YES | <1024 AN | |||
city | Address City | YES | <1024 AN | |||
state | Address State Abbreviation | YES | 2 A | |||
country | Address Country | NO | <1024 AN | |||
zip_code | Address zip code | YES | <1024 AN | |||
reference | Address Reference | NO | <1024 AN | |||
additional_data .passenger_data[] | Passenger information (fields marked with YES are only required if the passenger_data object is created) | |||||
name | Passenger name | YES | <1024 AN | |||
company_mile | Mileage Company (Loyalty) | NO | <1024 AN | |||
frequente_flyer_card | Mileage Card (Loyalty) | NO | <1024 AN | |||
legal_document_type | Type of identification document:1 - CPF2 - CNPJ3 - RG4 - IE5 - Passport6 - CTPS7 - Voter Title | NO | 1N | |||
legal_document | Document number | NO | <1024 N | |||
birth_date | Date of birth | NO | yyyy-mm-ddThh:mm:ss | |||
gender | Passenger's Gender:M - MaleF - Female | NO | 1A | |||
additional_data .flight_connection[] | Information regarding air connections (fields marked with YES are only mandatory if the flight_connection object is created) | |||||
company | Airline name | NO | <1024 AN | |||
flight_number | Flight number | NO | <1024 AN | |||
flight_date | Flight date | YES | yyyy-mm-ddThh:mm:ss | |||
class | Seat Class | NO | <1024 AN | |||
from | Origin | NO | <1024 AN | |||
to | Destiny | NO | <1024 AN | |||
departure_date | Boarding Date | YES | yyyy-mm-ddThh:mm:ss | |||
arrival_date | Landing date | YES | yyyy-mm-ddThh:mm:ss | |||
class_code | Tariff Class | NO | <1024 AN | |||
additional_data .reservation_hotel[] | Information regarding hotel reservations | |||||
hotel | Hotel name | NO | <1024 AN | |||
city | City | NO | <1024 AN | |||
state | State | NO | <1024 AN | |||
country | Country | NO | <1024 AN | |||
reservation_date | Booking Date | NO | yyyy-mm-ddThh:mm:ss | |||
reservation_expiration_date | Reservation Expiration Date | NO | yyyy-mm-ddThh:mm:ss | |||
checkin_date | Date of arrival | NO | yyyy-mm-ddThh:mm:ss | |||
checkout_date | Departure Date | NO | yyyy-mm-ddThh:mm:ss |
#
ExampleThe following is an example of a request with the minimum parameters to start a payment transaction with risk analysis. Learn more about payment parameters.
To use this example, don't forget to define the variable {{url}}
to the value
esitef-homologacao.softwareexpress.com.br
Response:
#
Example of a request with all parameters to begin a risk analysis payment transactionRequest:
To use this example, don't forget to define the variable {{url}}
to the value
esitef-homologacao.softwareexpress.com.br
Response:
#
Example of a request with the minimum parameters to begin a Pre-Authorization transaction with risk analysis.Request:
To use this example, don't forget to define the variable {{url}}
to the value
esitef-homologacao.softwareexpress.com.br
Response:
#
Example of a request with the other parameters to start a Pre-Authorization transaction with risk analysis.Request:
To use this example, don't forget to define the variable {{url}}
to the value
esitef-homologacao.softwareexpress.com.br
Response:
#
Example of request with the other parameters, to start a payment transaction rest with RealtimeRequest:
Response: