Known Issues {#rn-known-issues} =============================== **Security Keys** \| EPS-32983 ------------------------------ Description : When a merchant-level account with an underscore in the account name generates a P12 security keys in the Business Center's Key Management page, they receive the message *Error, an error occurred retrieving the keys*. Audience : Business Center users. Technical Details : None. Workaround : Use a transacting account instead of a merchant account. Or if you plan to use the P12 key for multiple merchant accounts, generate a meta key. **Payments** \| EPS-33062 ------------------------- Description : The merchant advice code is not always returned for the Simple Order or SOAP Toolkit API implementation for some rejected authorization responses. Audience : Users of the Simple Order API and the SOAP Toolkit API. Technical Details : ccAuthReply_merchantAdviceCode and ccAuthReply_merchantAdviceCodeRaw are not returned for some rejected authorization responses. Workaround : You can retrieve complete response information by using the transaction search in either the Business Center or the Transaction Search API. **Decision Manager**\| EPS-33117 -------------------------------- Description : Some users receive a red banner error in the Business Center when they attempt to edit a Decision Manager queue. Audience : Users of Decision Manager. Technical Details : None. Workaround : None. **Flex Microform Version 2** \| EPS-32476 ----------------------------------------- Description : Merchants might experience transaction failures due to invalid card type errors when sending token creation requests using Flex Microform v2. This issue occurs when a reseller has Partner Risk Controls services enabled. In these cases, Flex does not include the card type in the initial request payload; instead, the card type is added later during the PaRC request process. This can result in validation errors and failed transactions for affected merchants. Audience : Merchants integrating Flex Microform version 2, particularly those whose resellers have Partner Risk Controls services enabled. The issue does not impact all such merchants and might depend on account configuration. Technical Details : Merchants received the error *102 The field is invalid: card_type* . The issue arises when the `card_type` value is missing or does not meet the expected validation requirements in the transaction payload. Workaround : To avoid validation errors, merchants can ensure the `card_type` value is explicitly included in the transaction request payload. **Partner Risk Controls** \| EPS-32921 -------------------------------------- Description : Some transactions whose Electronic Commerce Indicator is set to `ECI=7` were not blocked by Partner Risk Controls. Audience : Users of Partner Risk Controls. Technical Details : None. Workaround : None. **Fraud Management Essentials** \| EPS-31123 -------------------------------------------- Description : Users of Fraud Management Essentials who have signed up to receive SMS messages when a transaction is processed are not receiving SMS messages. Audience : Users of Fraud Management Essentials. Technical Details : None. Workaround : Use email messsges instead of SMS until the problem is resolved. **Merchant Boarding Templates** \| EPS-32626 -------------------------------------------- Description : Users might experience a persistent error message when applying a card processing template while boarding merchants in the Business Center. Audience : This issue may impact merchants using the Boarding Template feature in the Business Center for card processing configuration. Technical Details : The error message incorrectly indicates missing information when the card processing template application is processed, even if incomplete information was provided. Workaround : If this error is encountered, users can switch to a different tab in the Business Center platform, then return to the original tab and click **Apply** again. The form should then submit as expected. **Merchant Management** \| EPS-32722 ------------------------------------ Description : An intermittent issue is affecting users who edit merchant accounts on the Manage Merchants page. When a user edits only attributes in the Common Settings section and submits the changes, they might see a red banner that says *Error: An unknown error occurred. Try again later.* However, the changes are successfully saved. Audience : Users of Merchant Boarding. Technical Details : None. Workaround : You can ignore the error message. **Paypal** \| EPS-32184 ----------------------- Description : When clients pass in the note_to_payer and/or note_to_payee fields for SOAP XML integrations, the values are not transmitted to the processor. Audience : Cybersource PayPal merchants using the Billing Agreement. Technical Details : No errors are received by the merchant. Workaround : None. **RTSS** \| EPS-32633 --------------------- Description : Some customers might receive duplicate messages at their endpoint URL. Audience : Users of RTSS. Technical Details : None. Workaround : None. **Business Center** \| EPS-32636 -------------------------------- Description : Some users of the Business Center with non-administrative roles cannot access the My Profile section. When they attempt to navigate to the My Profile section using the link at the top-right corner of the screen, the page is blank. Audience : Global. Technical Details : None. Workaround : None. **Transaction Search** \| EPS-32719 ----------------------------------- Description : Merchant reference numbers that contain the slash character (/) cannot be searched for using the default search filters. Audience : Global. Technical Details : None. Workaround : Filter your search by using the *+add filter* option at the top of the page. **Decision Manager** \| EPS-32768 --------------------------------- Description : An intermittent issue sometimes causes an error when a user runs a Case Management search. Audience : Users of Decision Manager. Technical Details : None. Workaround : Try the search again. Retries are usually successful. **Virtual Terminal** \| EPS-32807 --------------------------------- Description : Due to an intermittent issue, when a one-time payment is made in the Virtual Terminal, the receipt sent to the customer sometimes shows 0.00 instead of the transaction amount. Audience : Merchants who use Virtual Terminal to make one-time payments. Technical Details : None. Workaround : Merchants can manually resend the email receipt using the Transaction Summary page, which shows the correct amount.