Skip to main content
POST
/
api
/
pay
/
{projectId}
/
transactions
/
cybinfo
Get CyberSource Transaction Details
curl --request POST \
  --url https://localhost:44371/api/pay/{projectId}/transactions/cybinfo \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "transactions": [
    {
      "companyProjectId": "<string>",
      "transactionId": "<string>"
    }
  ]
}
'
{
  "success": true,
  "code": 200,
  "errorMessage": null,
  "entries": []
}

​
Description

Fetches detailed CyberSource transaction information including advanced fraud detection results, AVS/CVV responses, decision manager scores, and CyberSource-specific transaction fields. This endpoint is only applicable for transactions processed through CyberSource payment gateway.

​
Input

  • Path Parameter: projectId (guid, required) — Project identifier matching authenticated API key.
  • Body: model (TransactionCybQueryRequest, required) — Query request with transactionId and optional flags.

​
Output

Returns a TransactionCybQueryResponse containing CyberSource-specific transaction details including fraud scores, AVS/CVV results, and decision manager data.

​
Example Request

POST /api/payment/projects/{projectId}/transactions/cyb-info
Content-Type: application/json

{
  "transactionId": "7b8c9d0e-1234-5678-9abc-def012345678",
  "includeDecisionManagerDetails": true
}

​
Example Response

{
  "success": true,
  "data": {
    "avsCode": "Y",
    "cvCode": "M",
    "decisionManagerScore": 45,
    "fraudScore": 12
  }
}

​
Errors

  • 400 Bad Request — Missing transactionId or not a CyberSource transaction.
  • 404 Not Found — Transaction or CyberSource data not found.
  • 401 Unauthorized — Invalid API key.

​
Notes

  • This endpoint only works for transactions processed through CyberSource payment gateway.
  • Decision Manager data is only available if enabled in CyberSource configuration.
  • Fraud scores depend on CyberSource subscription level and enabled features.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

​
projectId
string<guid>
required

The unique identifier of the project containing the CyberSource transaction (must match authenticated API key).

Body

application/json

The CyberSource query request specifying transaction ID and optional flags for including detailed fraud and decision manager data.

Represents the request payload used to query CyberSource transactions.

​
transactions
object[] | null

Collection of project and transaction pairs to retrieve.

Response

Always returned. Check the success property in the response body to determine if the query succeeded.

Standard response structure containing operation status and error information. Standard query response containing a collection of matching entities. Wraps CyberSource transaction query results for API responses.

​
success
boolean

True if the operation completed successfully; false if an error occurred.

Example:

true

​
code
enum<string>

Result code indicating the outcome of the operation.

Available options:
Unknown,
Success,
BadRequest,
Unauthorized,
NotFound,
Error
Example:

200

​
errorMessage
string | null

Human-readable error message when an error occurs.

Example:

null

​
entries
object[] | null

Collection of entities matching the query criteria.

Example:
[]