Hello,
I am currently implementing the createTransactionRequest resource to charge a tokenized card and create the Customer and Payment Profiles using a single request as described in the official documentation. However, the API behavior varies depending on the authentication method I'm using.
For instance, when executing the request using the API Login ID and Transaction Key, it works as expected: the transaction is captured, customer and payment profiles are created and returned.
{
"createTransactionRequest": {
"merchantAuthentication": {
"name": "8F4s7aVD",
"transactionKey": "<OMMITED_FOR_SECURITY>"
},
"transactionRequest": {
"transactionType": "authCaptureTransaction",
"amount": 1,
"payment": {
"opaqueData": {
"dataDescriptor": "COMMON.ACCEPT.INAPP.PAYMENT",
"dataValue": "<OMMITED_FOR_SECURITY>"
}
},
"profile": {
"createProfile": "true"
},
"solution": {
"id": "AAA100302"
},
"customer": {
"id": "adan@example.io",
"email": "adan@example.io"
},
"billTo": {
"firstName": "Adan R D",
"lastName": " Santos",
"address": "1st Avenue",
"city": "New York",
"state": "AL",
"zip": "46205",
"country": "US"
},
"transactionSettings": {
"setting": {
"settingName": "duplicateWindow",
"settingValue": "70"
}
}
}
}
}
On the other hand, when executing the request using the OAuth 2.0 access token, the API throws a generic exception that doesn't help me understand what is wrong.
Request
{
"createTransactionRequest": {
"merchantAuthentication": {
"accessToken": "<OMMITED_FOR_SECURITY>"
},
"transactionRequest": {
"transactionType": "authCaptureTransaction",
"amount": 1,
"payment": {
"opaqueData": {
"dataDescriptor": "COMMON.ACCEPT.INAPP.PAYMENT",
"dataValue": "<OMMITED_FOR_SECURITY>"
}
},
"profile": {
"createProfile": "true"
},
"solution": {
"id": "AAA100302"
},
"customer": {
"id": "adan@example.io",
"email": "adan@example.io"
},
"billTo": {
"firstName": "Adan R D",
"lastName": " Santos",
"address": "1st Avenue",
"city": "New York",
"state": "AL",
"zip": "46205",
"country": "US"
},
"transactionSettings": {
"setting": {
"settingName": "duplicateWindow",
"settingValue": "70"
}
}
}
}
}
Response
{
"transactionResponse": { "SupplementalDataQualificationIndicator": 0 },
"messages": {
"resultCode": "Error",
"message": [
{
"code": "E00001",
"text": "An error occurred during processing. Please try again."
}
]
}
}
I would like to understand why the request fails for the OAuth 2.0 authentication, because that is the authentication method the company has been using since the implementation of Authorize.Net integration within our app.
Also, does anyone know how to troubleshoot the infamous E00001 generic error?
