Hi,
I have integrated Authorize.net 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<https://developer.authorize.net/api/reference/index.html#payment-transactions-charge-a-customer-prof...> for transactions. Following is the payload of my request:
<?xml version="1.0" encoding="utf-8"?>
<createTransactionRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<merchantAuthentication>
<name>8*****2K</name>
<transactionKey>69c**********8Bv</transactionKey>
</merchantAuthentication>
<transactionRequest>
<transactionType>authOnlyTransaction</transactionType>
<amount>8</amount>
<profile>
<customerProfileId>903260949</customerProfileId>
<paymentProfile>
<paymentProfileId>902980356</paymentProfileId>
</paymentProfile>
</profile>
<processingOptions>
<isFirstRecurringPayment>false</isFirstRecurringPayment>
<isFirstSubsequentAuth>true</isFirstSubsequentAuth>
<isSubsequentAuth>false</isSubsequentAuth>
<isStoredCredentials>true</isStoredCredentials>
</processingOptions>
</transactionRequest>
</createTransactionRequest>
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="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<messages>
<resultCode>Ok</resultCode>
<message>
<code>I00001</code>
<text>Successful.</text>
</message>
</messages>
<transactionResponse>
<responseCode>1</responseCode>
<authCode>000000</authCode>
<avsResultCode>Y</avsResultCode>
<cvvResultCode>P</cvvResultCode>
<cavvResultCode>2</cavvResultCode>
<transId>60182826364</transId>
<refTransID />
<transHash />
<testRequest>0</testRequest>
<accountNumber>XXXX1111</accountNumber>
<accountType>Visa</accountType>
<messages>
<message>
<code>1</code>
<description>This transaction has been approved.</description>
</message>
</messages>
<transHashSha2 />
<profile>
<customerProfileId>903260949</customerProfileId>
<customerPaymentProfileId>902980356</customerPaymentProfileId>
</profile>
<networkTransId>00000000000000000000000</networkTransId>
</transactionResponse>
</createTransactionResponse>
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
12-29-2021 03:51 AM - last edited on 12-29-2021 09:18 AM by MansourH
Hi @navigasandbox2 ,
Please try again, this should now be resolved.
Mansour
12-29-2021 09:49 AM - edited 12-29-2021 09:50 AM
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 (https://developer.authorize.net/api/reference/index.html#payment-transactions-authorize-a-credit-car...) 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": "192.168.1.1",
"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
01-18-2022 05:42 AM