Known Issues

An intermittent bug is affecting the legacy Recurring Billing service. When a merchant issues a follow-on credit for a settled transaction that was processed through recurring billing, they sometimes receive the error

Reason Code 102

(see technical details). This occurs even if the merchant's account is configured for 365 day credits.

Users of the legacy Recurring Billing service.

Reason Code 102:

There is a problem processing this request: The request id for the transaction is either invalid or missing.

Use a standalone credit instead of a follow-on credit.

A bug that affecting acquirers is preventing three tax fields from being populated in the TC33A file for authorizations and follow-on settlements. This is true even when the fileds were included in the payload. The fields are:

Local tax
Local Tax Included
Total Taxes Amount

Acquirers who settle transactions that were performed using the Tax Calculation Service.

Local Tax: CP04 TCR0 Pos: 36-47, CP12 TCR1 Pos: 26-37

None.

When a user of Virtual Terminal has automatic email receipts enabled and they process a transaction, the email receipt states that 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.