Skip to main content
Object implements VerifyAccountResponse

​
Fields

​
message
required
A detailed description of the response code. e.g., Insufficient funds.
​
processorAdvice
required
When an authorization is declined, Tesouro will provide advice on what can be done to remedy, and/or prevent this type of response from occurring in the future.
​
declineType
required
Specifies the type of response, e.g. SOFT_DECLINE, HARD_DECLINE, REFERRAL.
​
avsResponseDetails
required
Address Verification Service (AVS) is a service provided by the payment brands that determines the match or partial match of the consumer’s address information.
​
cardSecurityCodeResponseDetails
required
The security code response from the network.
​
nameVerificationResponseDetails
required
Name verification service result provided by the payment brand.
​
systemTraceAuditNumber
The system trace audit number sent to the network.
​
networkTransactionId
The transaction ID forwarded from the network response.
​
advice
required
Advice regarding follow up action for this transaction.
​
businessApplicationId
The business application identifier (BAI) is a value provided by Visa to identify the type of transfer that is being performed.
​
cardDetails
Details related to the card used on the transaction
​
networkResponseDetails
required
The response code from the network.
​
timestampUtc
required
The UTC date and time the transaction was received by Tesouro.
​
transactionId
required
A unique identifier created by Tesouro and assigned to the transaction.
​
paymentId
required
A unique 36 character identifier created by Tesouro and assigned to a group of transactions in the same payment request cohort. e.g., An authorization request, incremental authorization request, and the final capture would have the same paymentID.
​
duration
required
Difference between request receipt and response in milliseconds.
​
activityDate
required
The date Tesouro received the transaction based on acceptor cutoff time
​
isDuplicateRequest
required
Result of Tesouro’s idempotency check. If the transaction reference matches that of another transaction from that presenter it will be treated as a duplicate.
​
tokenDetails
Details associated with the token generated on a tokenization request.
{
  "message": "abc123",
  "processorAdvice": "abc123",
  "declineType": "REFERRAL",
  "avsResponseDetails": AddressVerificationResponse,
  "cardSecurityCodeResponseDetails": CardSecurityCodeResponseDetails,
  "nameVerificationResponseDetails": NameVerificationResponseDetails,
  "systemTraceAuditNumber": "xyz789",
  "networkTransactionId": "xyz789",
  "advice": Advice,
  "businessApplicationId": "CB",
  "cardDetails": CardInformation,
  "networkResponseDetails": NetworkResponseDetails,
  "timestampUtc": "2007-12-03T10:15:30Z",
  "transactionId": "72ef289d-77d4-4696-8a08-da83ed15b751",
  "paymentId": "72ef289d-77d4-4696-8a08-da83ed15b751",
  "duration": 987,
  "activityDate": "2007-12-03",
  "isDuplicateRequest": false,
  "tokenDetails": TokenDetails
}