Showing results for 
Search instead for 
Did you mean: 

"networkTransId" is coming with multiple 0's only(0000000000...) in transaction resp.



I have integrated and made changes for COF mandate. It was running fine when it's implemented(24 September 2021). But on Friday(24 December 2021) when I ran it , I am getting multiple 0 only in the response (see response below) I am using charge a customer profile<> for transactions. Following is the payload of my request:


<?xml version="1.0" encoding="utf-8"?>

<createTransactionRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">























I got the following response from Authorize.Net:


<?xml version="1.0" encoding="UTF-8"?>

<createTransactionResponse xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd" xmlns:xsd="" xmlns:xsi="">















      <refTransID />

      <transHash />







            <description>This transaction has been approved.</description>



      <transHashSha2 />









The networkTransId is coming as multiple 0's. It is coming same for all the transactions every time.

When I performed same request Earlier(24 September 2021), then the networkTransId was a unique string for all the transactions. E.g. - GATHLJF840VEO8RNMBNTDHU.

I didn't find any change in the request fields of above-mentioned API. Do I need to make any changes in the mentioned request to get unique networkTransId?


Can you please guide me to get the unique networkTransId?


Sandbox details:

username: n*******1


Hi @navigasandbox2 ,

Please try again, this should now be resolved.


Moderator Moderator

Hi Mansour,

I am also encountering this same issue with all 0's in the networkTransId for COF transactions.  It was working correctly last week but yesterday (1/17/22) is when I noticed the 0's being returned in that field.  This happens through our code calls as well as through the Authorize a Credit Card AP Live Console ( when I post my own JSON:



    "createTransactionRequest": {

        "merchantAuthentication": {

            "name": "5KP3u95bQpv",

            "transactionKey": "346HZ32z3fP4hTG2"


        "refId": "123456",

        "transactionRequest": {

            "transactionType": "authOnlyTransaction",

            "amount": "5",

            "profile": {

                  "customerProfileId": "903512139",

                  "paymentProfile": {

                        "paymentProfileId": "903251223"





            "customerIP": "",

            "processingOptions": {

            "isFirstRecurringPayment": false,

            "isFirstSubsequentAuth": false,

            "isSubsequentAuth": false,

            "isStoredCredentials": true


            "authorizationIndicatorType": {

           "authorizationIndicator": "pre"






Do I have something wrong or is there an issue with the API?

Thank you,

Bob P