Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

For any of the following errors we have been advised to use this error message:
Os dados do seu cartão estão incorretos. Por favor verifique as informações e tente novamente 
- Incorrect customer data;
- Invalid card number;
- Invalid card type;
- Security code mismatch.
We need to add validation for CPF and Phone number fields as well. Refer to below tickets.
CPF validation: 
Jira Legacy
serverSystem JIRA
serverIdb5f78b4b-8603-3879-a97e-a16b5dacbf76
keyDFSB-1193
Phone validation: 
Jira Legacy
serverSystem JIRA
serverIdb5f78b4b-8603-3879-a97e-a16b5dacbf76
keyDFSB-1270

============================================================================================================

We need to collect address details in local format. It helps us ensure correct addresses are recorded.

...

  • On mobile version - show numpad for postcode and phone number. Example:



Development ticket: 

Jira Legacy
serverSystem JIRA
serverIdb5f78b4b-8603-3879-a97e-a16b5dacbf76
keyDFSB-198


============================================================================================================

Submitting to CRM

One example: 
Av. Pedroso de Morais, 457
Sala 410
São Paulo, SP
05419-000
-

...

Address1 -> Street name, number
Address2 -> complement
Image RemovedImage Added
============================================================================================================

Suggestion for API integration

Even better, is to have a simple integration with an API that simply finds the address through the zip code. That is how our major websites work in Brazil.
The first step is to collect the zip code (CEP):
Image Removed
After inputting the information, call the CEP API (details at the end of the email), and auto-fill the address found, making sure that the customer fills the house number (has to be mandatory), and complement as optional.
Image Removed
In case that there is no address found, we can use the Google API to help the customer with the address, but as an exception. The CEP API should be very reliable.

...

Simple GET call and you will have a Json as response.

...

Using Find CEP API

Development ticket: 

Jira Legacy
serverSystem JIRA
serverIdb5f78b4b-8603-3879-a97e-a16b5dacbf76
keyDFSB-956


Please use the example below as reference on how exactly it should be. You may use the postal code 13087-430, which will return valid data, and 13087-400 will be invalid.
In the file that I am sending you, you may see some changes in the following functions (Please make sure to use the ones that I updated): 
  • getAddressFormBR: function(data){...} 
  • submitAddressFormBR: function(){...}
And a new function called: $("#cep").blur(function(){...}
Once someone types their CEP (ZipCode), you will call the following API:
GET https://api.findcep.com/v1/cep/{postalCode}.json 
Please use the postal code without any special characters, only numbers.
In case that there is no match for the postal code, it will return a 404 (Not Found), and you may give an alert to the customer: "CEP não encontrado!", but we should still allow the customer to confirm that this CEP is valid and input the address manually. Sometimes the database might not have the postal code for new neighborhoods.
When there is a match for the postal code, the return will be as following:
{
    "logradouro": "Rua das Orquídeas",
    "status": "completo",
    "bairro": "Chácara Primavera",
    "codigo_ibge": "3509502",
    "nome": "",
    "tipo": "cep_logradouro",
    "complemento": "",
    "cep": "13087430",
    "uf": "SP",
    "cidade": "Campinas"
}
You should use the response as follows:
address1 =  logradouro
address2 =  bairro
state = uf
city = cidade
If there is a response from the API, the fields Rua/Avenida, Bairro, Cidade, Estado, Pais should be as read-only
Image Added
For the fields "Numero" and "Complemtento", you should do as following:
  • Numero -> That is the house number. This field should be mandatory, and we expect the customer to input that data. You will concatenate this field in the "address1" with a comma. example: Rua das Orquideas, 587
  • Complemtento -> Not mandatory. Only when someone leaves in apartments or any kind of complex with unit number.  You will concatenate this field in the "address2" with a dash.example: Chacara Primavera - unidade 22

============================================================================================================

Submitting CPF field

We need to send the CPF value in the place order call for Brazil. Currently it's not sending it, so we are getting a decline from EBANX.

Current JSON:
"customer":

{ "email":"andre.thivierge@emanagecrm.com", "phoneNumber":"60455555555", "firstName":"Andre", "lastName":"Thivierge" }

,

Please add the following values in Customer:
"customerIdentificationValue":"698.868.809-96", //CPF value taken from CPF field
"customerIdentificationTypeId":1 //always 1


Updated JSON sample:

"customer":

{ "email":"andre.thivierge34324@emanagecrm.com", "phoneNumber":"6045555555", "firstName":"Andre", "lastName":"Thivierge", "customerIdentificationValue":"957.734.334-19", "customerIdentificationTypeId":1 }