Known Issues

The Payment REST API is sending HTTP response code 202 instead of 201 when the error reason is

contact_processor

.

Users of the Payment REST API.

The affected endpoint is

pts/v2/payments

.

None.

Virtual Terminal is visible in the Business Center to merchant accounts onboarded to the VAP portfolio that are not enabled for Virtual Terminal.

Resellers on the VAP portfolio.

None.

None.

A defect is affecting the Transaction Request Report. For some requests that resulted in 102 errors, the Rmsg column is not populated.

Users of the Transaction Request Report.

None.

None.

A defect is preventing enhanced data from being passed in API responses for authorizations and refunds on Visa Platform Connect gateways for airline and hospitality merchants.

Users of enhanced data.

When the merchant has configured the

<gateway>_enhanced_data_enabled

field and they send airline or hospital data request fields in the API for authorizations and refunds, the

<auth or credit>_enhanced_data_enabled

field is not sent in the response.

None.

The Transaction Reference Number is not being included in the batching file for merchants that use Streamline for payment processing. This defect can affect reconciliation.

Merchants that use Streamline for payment processing.

The Merchant Reference Number is being passed during authorization instead of the Transaction Reference Number.

For reconciliation purposes, use the Merchant Reference Number in the Clearing File.

Some merchants might experience issues downloading reports if the report subscription time zone is set to Africa/Cairo. Despite the reports being generated successfully, they might receive an error message.

Merchants who subscribed to reports in the Africa/Cairo Time Zone.

Error Message when using the Business Center: "Error: File is not available. Try again later."

Error Message when using the REST API: "Requested Resource Not Found"

Reports after September 21 are working properly. The affected reports must be recreated as a one-time report.

Merchants on Elevon Americas that enable the new Dynamic Data feature might experience transaction failures due to a defect in data validation.

Merchants on Elevon Americas.

The API field

merchant_country

is not being validated correctly.

If you would like to use the Dynamic Data feature, contact Customer Support to have your account configured and monitored.

A defect is causing a false success message during batch upload in the Business Center. If a batch upload file contains a

batchID

field with a value longer than the maximum supported length of 8 characters, the batch fails, as it was designed to do. However, the response message says

file successfully uploaded

.

Users of Batch Upload.

None.

Manually verify that the value of any

batchID

field is within the 8 character maximum before uploading.

Merchants using

auth_type

=autocapture

when performing a sale transaction might experience data issues in the Business Center, Decision Manager, and Reporting.

Users of the Payments 2.0 platform.

The current implementation of the Payments 2.0 platform does not support

auth_type

=autocapture

.

Refrain from using

auth_type

=autocapture

in sale transactions until this issue is fixed. Instead, use

auth_type

=standardcapture

or

auth_type

=verbal

.

Boarding new transacting merchant IDs using the Merchant Boarding API might require assistance by Visa Acceptance Solutions Customer Support to adjust the hierarchy.

Users of the Merchant Boarding API.

None.