Known Issues

When a user of Virtual Terminal has automatic email receipts enabled and they process a transaction, the email receipt states the amount is 0.00 instead of the amount of the transaction.

Users of Virtual Terminal.

None.

Generate a receipt manually in the Business Center.

When a user of Decision Manager tries to edit a queue that has

Move

in the policy, the result is a white screen.

Users of Decision Manager.

None.

None.

An intermittent issue is affecting some portfolio users of TMS. Sometimes the TMS search filter is disabled for users of merchant-level organizations. They are unable to view the details of any tokens that are used by the transacting organizations beneath them in the organization hierarchy.

Users of merchant-level organizations.

None.

Use a transacting organization to use token search.

Payment facilitator IDs are not being automatically populated when transactions are sent to VisaNet.

Merchants in the Asia-Pacific region, primarily India.

None.

Include the payment facilitator ID in API requests by using the aggregator ID field.

Merchants who process payments through Prosa receive an error when they try to refund a captured transaction more than 60 days after the original authorization.

Merchants who process payments through Prosa.

The error is

Payment processor error (100004) General System Error

.

Perform a standalone credit instead of a linked refund.

The Merchant Boarding API sometimes responds with an error during account registration. The API status is

PARTIAL

and the message is

Unexpected error with Product Enablement and Config API

. If that happens, the merchant account can be found in Business Center with the warning,

This merchant account hasn't completed the boarding process

.

Users of the Merchant Boarding API.

None.

Find the merchant account in the Business Center and choose

Complete Boarding

.

Merchants cannot create tokens from the transaction details page. When they select

Actions > Create Token

, fill in all the required details, and click

Save

, they receive an error message.

Users of the Token Management Service.

None.

Create the token from the Token Management page or by using the API.

When merchants try to enable the Processor Events Detail Report from the Standard Report Subscriptions tab in the Business Center's Report Subscription Management page, they see a success message but the report remains in

Disabled

status.

Users of the Processor Events Detail Report.

None.

Merchants can copy the standard Processor Events Detail Report and save it as a custom report subscription instead. They must click the

Save

button twice, as the first time will trigger this error.

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

.

Business Center users.

None.

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.

The merchant advice code is not always returned for the Simple Order or SOAP Toolkit API implementation for some rejected authorization responses.

Users of the Simple Order API and the SOAP Toolkit API.

You can retrieve complete response information by using the transaction search in either the Business Center or the Transaction Search API.

Some users receive a red banner error in the Business Center when they attempt to edit a Decision Manager queue.

Users of Decision Manager.

None.

None.

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.

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.

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.

To avoid validation errors, merchants can ensure the

card_type

value is explicitly included in the transaction request payload.

Some transactions whose Electronic Commerce Indicator is set to

ECI=7

were not blocked by Partner Risk Controls.

Users of Partner Risk Controls.

None.

None.