After getting the token or signature in the previous step, the virtual store must send the data of the merchant to be created on e-SiTef and SiTef (if necessary).
Call details
Resource:/v1/merchants
HTTP Method:POST
Request format:JSON
Response format:JSON
Header parameters:
Parameter
Description
Format
Mandatory
merchant_id
Merchant code on e-SiTef. The production and certification codes will be different.
< 15 AN
YES
merchant_key
Merchant authentication key on e-SiTef. The production and certification keys will be different.
Terminal number that will be defined by Global Payments.
Stone WS
Parameter
Description
authorizers[].parameters
Specific routing parameters.
salesAffiliationKey
Merchant identification key on Stone.
subAdquirenciaHabilitada
Send true to enable sub-acquiring or false otherwise.
BIN via SiTef
Parameter
Description
Format
authorizers[].parameters
Specific routing parameters.
subacquirerMerchantId
Submerchant code.
establishments
Data of the establishments to be created on SiTef.
establishments.extra_data
Terminal code. Mandatory field for integration with the Bin acquirer.
= 8 AN
e-Rede
Parameter
Description
authorizers[].parameters
Specific routing parameters.
filiacao
Merchant filiation code on e-Rede.
senha
Merchant public key on e-Rede.
Registering merchants with anti-fraud
It's possible to automatically register new merchants with the following anti-fraud solutions: Fraud Detect, ClearSale, CyberSource and Konduto. To do it, the merchant must contact the risk analysis institution and request the necessary credentials. Then, the merchant must pass a set of MCC's (Merchant Category Code) for each registered credential to the e-SiTef Production team, which will register this data. These MCC's will be mapped for each credential and these values will be used on the registration of each merchant. Once this pre-registration is done, it will be possible to perform the anti-fraud registration automatically using the merchant creation API.
Attention:
It's required to activate the anti-fraud permission (risk_analysis) on the merchant creation call.
Only the merchant creation service performs the automatic anti-fraud registration.
Response parameters
If successful, the HTTP response code will be 201. Any other code must be interpreted as an error. The table below describes the response parameters of the merchant creation service:
Parameter
Description
Format
response_code
e-SiTef response code. Any code different from 0 means failure.
< 4 N
response_message
e-SiTef response message.
< 500 AN
authorizer_response_code
Authorizer response code.
< 4 N
authorizer_response_message
Authorizer response message.
< 500 AN
id
Code of the created merchant. Automatically generated (note: uppercase and lowercase characters are differentiated in the system).