How encoding/Decoding of Grpc proto parameters processed in ReadAPI during .proto file import

In our project we have requirement to test the grpc protocol using unary operation. Able to import .proto file successfully in readyapi, but when created the test case using the imported file, the original data of the unary request is mistmatched with the actual data of the proto file. 

For example:

Following is the request data we have got after importing the .proto file in readyapi. we are not sure how this encoding/decoding occurs in readyapi.

Request Data from readyapi:

{
"token1" : "c3RyaW5n",
"nonce" : "c3RyaW5n"
}

But in grpc server we have stored the same data as constants and comparing these constants with the readyapi request. Unfortunately the comparison is not matching with our implementation with the readyapi data received. Below is our two scenarios of comparision, but in none of the case its matching.

comparision 1: 

const test_token = "blablabla"

token := []byte(test_token)

"if bytes.Compare(token, in.GetToken1()) == 0"

comparision 2:

const test_token = "c3RyaW5n"

token := []byte(test_token)

"if bytes.Compare(token, in.GetToken1()) == 0"