CyberSource

Consume the CyberSource API common functionality
Join our community

Overview

This n8n node interacts with the CyberSource API, specifically targeting the "Decision Manager" resource and its "Close" operation. The node is designed to help automate workflows involving CyberSource's fraud management system, such as closing or updating cases based on decisions made during payment processing.

Common scenarios:

  • Automatically closing a fraud review case in CyberSource after a decision has been made.
  • Integrating CyberSource Decision Manager actions into broader e-commerce or risk management workflows.
  • Streamlining manual processes for fraud analysts by automating case closure based on workflow logic.

Practical example:
After a payment is reviewed and accepted or declined, this node can be used to close the corresponding case in CyberSource, ensuring that your fraud management dashboard stays up-to-date without manual intervention.

Properties

Name Type Meaning
Reason String The reason for closing the case. This is a required field and should describe why the case is being closed (e.g., "Order fulfilled", "Fraud confirmed", etc.).

Output

The node outputs a JSON object representing the result of the "Close" operation. The structure of the output will typically include:

  • All fields from the input item, possibly augmented with additional information returned by the CyberSource API.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.

Example output:

[
  {
    "success": true,
    "caseId": "123456789",
    "status": "closed",
    "reason": "Order fulfilled"
  }
]

Note: The actual output fields may vary depending on the CyberSource API response.

Dependencies

  • External Service: Requires access to the CyberSource API.
  • Credentials: You must configure CyberSource API credentials in n8n under the name cybersourceApi.
  • Environment: No special environment variables are required beyond standard n8n credential configuration.

Troubleshooting

Common issues:

  • Missing Credentials:
    Error: "No credentials got returned!"
    Resolution: Ensure that valid CyberSource API credentials are configured in n8n and assigned to the node.

  • API Errors:
    If the CyberSource API returns an error (e.g., invalid reason, network issues), the node will throw an error unless "Continue On Fail" is enabled.
    Resolution: Check the validity of the "Reason" property and ensure network connectivity to CyberSource.

  • Incorrect Input:
    Providing an empty or invalid "Reason" may cause the API call to fail.
    Resolution: Always provide a meaningful, non-empty reason for closing the case.

Links and References

Discussion