Known Issues

Some clients that use a payment facilitator ID (aggregator ID) through Visa Platform Connect might notice a data integrity mismatch between the authorization and clearing messages. Cybersource does not populate the payment facilitator ID in the outgoing authorization request, though the field populates correctly in the clearing message.

Clients that use a payment facilitator ID (aggregator ID) through Visa Platform Connect.

The authorization request does not return an error; the payment facilitator ID field is left empty.

None.

When a client uses the Boarding API to enable Decision Manager and assign a Token Management Service ID for Decision Manager Hierarchy, the request might return an HTTP 422 error. The Decision Manager subscription succeeds, but the Decision Manager Hierarchy configuration fails hierarchy-group validation, leaving the boarding request in a partial state.

Portfolio merchant IDs that use the Boarding API to enable Decision Manager and Decision Manager Hierarchy.

The response returns the error message

configuration.request.invalid

.

Contact Cybersource to have the merchant manually assigned to Decision Manager Hierarchy in the Business Center.

When a merchant receives a declined payer authentication setup response, for example when the card is expired, the response returns an incorrect value in the

status

field. The field returns a numeric code instead of the expected text value, such as

COMPLETED

.

All merchants that use Payer Authentication.

The

status

field in the payer authentication setup response returns a numeric code instead of a text value. Cybersource has always returned this status as a numeric code, so changing the field to a text value might break existing merchant integrations that rely on the numeric format.

Use the

errorInformation.reason

and

errorInformation.message

fields for more detail instead of relying only on the status code.

When a suspended webhook subscription passes a health check, the platform is expected to automatically reactivate the webhook and update its status to active. In some cases, the status update does not save successfully, so the webhook might repeatedly appear suspended even though the health check succeeded. This issue occurs in backend processing and is not related to endpoint connectivity or certificate issues.

All merchants and portfolios that use webhook subscriptions.

None.

Keep the webhook endpoint available and responsive so that health checks continue to succeed.