Known Issues {#rn-known-issues} =============================== **.NET REST Client SDK Methods Might Not Return Unified Checkout Transient Token Data** \| EPS-42309 ---------------------------------------------------------------------------------------------------- Description : Developers using the .NET REST Client SDK might find that payment details are not returned when calling methods that retrieve Unified Checkout transient token transaction data. Although the API request completes successfully, the calling application does not receive the requested billing, shipping, or masked card information. Audience : Developers using the CyberSource .NET REST Client SDK to retrieve payment details associated with Unified Checkout transient tokens. Technical Details : The `TransientTokenDataV2Api.GetTransactionForTransientTokenJTI()` and `TransientTokenDataV2Api.GetTransactionForTransientToken()` methods might not return payment data to the calling application. Workaround : No known workaround. **Authorization Decline Webhooks Might Omit the `submitTimeUtc` Field** \| EPS-42702 ------------------------------------------------------------------------------------ Description : Some merchants might find that authorization decline webhook events do not include the `submitTimeUtc` field. This issue can occur when an authorization request is declined, resulting in webhook payloads that omit the field entirely rather than returning it with a null value. Audience : Merchants that consume authorization decline webhooks through an affected gateway integration. Technical Details : For some declined authorization transactions, the `payload.submitTimeUtc` field might be omitted from the webhook payload. This issue affects `payments.authorization.rejected` and `payments.authorization.status.rejected` events and can occur for declined transactions such as those returned with response code `51` and reason `INSUFFICIENT_FUND`. Workaround : No known workaround. **Apple Pay Transactions Might Fail Due to Payment Data Decryption Errors** \| EPS-42773 ---------------------------------------------------------------------------------------- Description : Some Apple Pay transactions might fail during processing and return a decline response instead of being authorized successfully. This issue occurs during the decryption of Apple Pay payment data, preventing the transaction from being completed. Audience : Merchants that accept Apple Pay payments through affected integrations. Technical Details : Some Apple Pay transactions might fail with reason code `102` and the error message `Unable to decrypt encrypted_payment_data`. In affected transactions, the `publicKeyHash` cannot be validated, resulting in the error `Invalid public key hash` and preventing the Apple Pay payload from being decrypted. Workaround : No known workaround. **American Express Transactions Might Be Declined for Non-US and Non-Canadian Billing Addresses** \| EPS-42788 -------------------------------------------------------------------------------------------------------------- Description : Some merchants might experience declined American Express transactions when customers use billing addresses outside the United States or Canada. Although the billing address contains a valid postal code, the transaction might still be declined during authorization, preventing the customer from completing the purchase. Audience : Merchants processing American Express transactions through an affected processing connection when customer billing addresses are outside the United States or Canada. Technical Details : Some American Express transactions with non-US and non-Canadian billing addresses might be declined with Cybersource reason code `236` and processor response code `19`. Although the billing postal code is present in the transaction data, it might not be included in the required authorization field used during transaction processing. Workaround : No known workaround. **Comment Field in Virtual Terminal Might Still Appear When Disabled** \| EPS-42796 ----------------------------------------------------------------------------------- Description : Some merchants might see the comment field displayed on Virtual Terminal receipts even when the Comment Display feature is disabled. Audience : Merchants using Virtual Terminal that have disabled the Comment Display feature. Workaround : No known workaround. **Unsupported Processor Configuration Might Appear in Business Center Portfolio Management** \| EPS-42942 --------------------------------------------------------------------------------------------------------- Description : Some merchants might see an unsupported processor configuration associated with their Business Center portfolio. This issue can occur when processor settings are updated through internal management processes, resulting in a processor being associated with a portfolio that does not support it. Audience : Some merchants using affected portfolio configurations in Business Center. Workaround : No known workaround. **Editing a Subscription Plan May Trigger Immediate Billing and Reset the Billing Schedule** \| EPS-43012 --------------------------------------------------------------------------------------------------------- Description : When merchants edit an existing subscription and change it to a different plan or tier, the subscription might immediately charge the customer and reset the recurring billing date. As a result, the billing cycle may change unexpectedly, and the customer can be charged sooner than intended. Audience : Merchants using Subscription Management or Recurring Billing that modify an existing subscription by changing its plan or tier. Technical Details : When a subscription is updated with a different plan or tier, the subscription start date may be reset, causing the billing cycle to restart. As a result, an immediate charge might be processed and the recurring billing date recalculated based on the date of the change. Workaround : To adjust pricing without changing the billing schedule, merchants can update only the subscription amount rather than changing the plan or tier. If a plan or tier change is required, merchants can cancel the subscription and create a new one with the billing date. **Payment Requests Using Flex and Unified Checkout Transient Tokens Might Return HTTP 400 Errors** \| EPS-43048 --------------------------------------------------------------------------------------------------------------- Description : Some merchants might receive an HTTP `400` response when submitting `POST /pts/v2/payments` requests using Flex or Unified Checkout transient tokens, even when capture context generation and transient token creation complete successfully. Audience : Merchants without a TMS profile that submit REST API payment requests using Flex or Unified Checkout transient tokens. Technical Details : For some merchants without a TMS profile, payment requests might return HTTP `400` because TMS configuration validation is performed even when no TMS profile is present. As a result, the required profile ID information cannot be populated for the request. Workaround : Contact your account representative to discuss temporary TMS enablement. **Confirmation Step Might Appear When Disabled in Unified Checkout** \| EPS-43205 --------------------------------------------------------------------------------- Description : Some merchants might see the confirmation step briefly appear during checkout even when `showConfirmationStep=false` is configured to skip it. Although the checkout flow continues as expected, the confirmation step might momentarily render before being bypassed. Audience : Merchants using Unified Checkout that have configured checkout to skip the confirmation step. Technical Details : When `showConfirmationStep=false` is configured, the confirmation step might still briefly render before the checkout flow continues. Workaround : No known workaround. **Unified Checkout Webhooks Might Not Be Delivered Due to Documentation Configuration Issues** \| EPS-43340 ----------------------------------------------------------------------------------------------------------- Description : Some merchants might not receive Unified Checkout webhooks after completing webhook configuration. This issue can occur when merchants follow webhook configuration guidance that results in an incorrect Message-Level Encryption (MLE) key configuration, preventing webhook delivery. Audience : Merchants in the European Union that use Unified Checkout webhooks. Technical Details : Some Unified Checkout webhooks might not be delivered when the configured MLE key does not match the values used during webhook delivery. A documentation discrepancy can result in merchants configuring a key with `provider=nrtd` and `tenant=yellhsbc`, while webhook delivery attempts to perform the key lookup using `provider=yellhsbc` and `tenant=nrtd`. Workaround : No known workaround. **Debt Repayment Transactions Might Be Processed as Standard Debit Transactions** \| EPS-43598 ---------------------------------------------------------------------------------------------- Description : Some merchants might find that debt repayment transactions are processed as standard debit transactions even when debt repayment indicators are included in the transaction request. Transactions complete successfully, but the debt repayment designation might not be recognized during transaction processing. Audience : Merchants that process debt repayment transactions through an affected processing connection. Technical Details : Transactions submitted with `merchant_category_code: 6051`, `bill_payment=y`, and `debt_indicator=y` might be processed as standard debit transactions rather than debt repayment transactions. Workaround : No known workaround. **Google Pay Transactions Using Payer Authentication Might Fail with an Invalid XID Error** \| EPS-43618 -------------------------------------------------------------------------------------------------------- Description : Some merchants might be unable to complete Google Pay transactions when using Payer Authentication (3-D Secure). Transactions might fail with an invalid XID error even when a valid XID value is provided. Audience : Merchants that use Google Pay with Payer Authentication (3-D Secure). Technical Details : Some transactions might fail with the error message `The field is invalid: xid` even when the `xid` field contains a populated, correctly formatted value. Workaround : No known workaround.