Skip to main content
Sign in RESOURCES

Cybersource Processor Error: Invalid Field subsequentAuthReason (No Processor Selected)

Recurly
  • Updated

In this scenario, Cybersource may return an invalid field error for subsequentAuthReason, which is a common signal that the credentials are not associated with the expected processor configuration for CoF (Card on File)/ subsequent transactions.

Symptoms and Error Messages

You may see one or both of the following:

Recurly Message

  • The payment gateway declined the transaction due to invalid data. Please check the response details for more information.

Gateway Response Detail

  • <c:invalidField>c:subsequentAuthReason</c:invalidField>
Note: The subsequentAuthReason field is typically associated with subsequent / CoF transaction handling. If Cybersource flags this field as invalid, it often indicates the request is being evaluated under an unexpected processor configuration for the provided credentials.

 

Most Common Cause

After CoF settings are changed in Cybersource, the processor is not selected (or the wrong processor is selected) for the configured credentials. As a result, Cybersource rejects the request as invalid data and may flag subsequentAuthReason as an invalid field.

Important: This issue is commonly configuration-related. Even if Recurly is sending a properly structured request, Cybersource can still decline it if the credential-to-processor mapping does not match your CoF setup.

How to Fix

  1. Confirm which processor your Cybersource credentials should use
    In Cybersource, identify the processor you intend to use for the merchant account / profile tied to the credentials configured in Recurly.
  2. Update your Cybersource configuration to select the correct processor
    Ensure the processor selection aligns with your CoF/subsequent transaction setup.
  3. Verify Recurly is using the correct Cybersource gateway configuration
    If you have multiple Cybersource gateway configurations in Recurly, confirm the one in use is mapped to the correct Cybersource credentials (and that those credentials are mapped to the correct processor).
  4. Retry the affected transaction
    Once the processor selection is corrected, retry a representative transaction to confirm the error is resolved.

Verification Steps

After applying the fix, validate with the following checks:

  • Re-run a test transaction that previously failed with the invalid data message.
  • Confirm the gateway response no longer includes invalidField for subsequentAuthReason.
  • If you have CoF/subsequent use cases (e.g., renewals), validate both:
    • an initial authorization/purchase flow (if applicable), and
    • a subsequent/recurring authorization flow.
Tip: If you maintain multiple Cybersource profiles (e.g., separate credentials for different business units or environments), ensure each profile has an explicit processor selection that matches its intended CoF behavior.

Additional Notes

  • This error can appear immediately after CoF configuration changes in Cybersource, especially when credentials are rotated, profiles are duplicated, or processor defaults are altered.

  • If the processor selection appears correct but the error persists, capture:

    • the full gateway response (including any field-level errors), and
    • the gateway configuration name/code used in Recurly for the attempt.

    Then escalate to Recurly Global Support with your examples.

Related articles

Comments

0 comments

Please sign in to leave a comment.