On This Page

Known Issues

Subscription Payments
 | 1573208

Description
When a zero-amount authorization in included in a subscription creation request, the request results in failure for American Express, Discover, Diners, JCB, and CUP transactions.
Audience
Merchants processing on FDC Nashville and performing Token Creation calls without a Full Auth Amount.
Technical Details
This defect results in reason code 102:
DINVALIDDATA
 with description
$0 auth not supported for [Card Scheme] on this gateway
.
Workaround
  • If you are tokenizing your customers before they place an order, create a token in conjunction with a $1 Authorization then perform a full authorization reversal to remove the temporary funding block on your customer account.
  • If you are tokenizing your customers at time of checkout, create a token in conjunction with the full amount of the customer's order.

Virtual Terminal
 | 1588256

Description
A defect is preventing Level III transactions in Virtual Terminal when Level II fields are set as required fields, even when all required fields are included.
Audience
Users of Virtual Terminal who perform Level III transactions.
Technical Details
The user receives the error message:
Level2PurchaseOrderNumber is a required field
.
Workaround
Use the API instead of Virtual Terminal.

Payments
 | 1560940

Description
A defect is causing payment transactions with an incorrect Card Verification Value (CVV) to receive a response code that claims the transaction can still be captured. However, capture fails.
Audience
Global.
Technical Details
The response code to the authorization says:
RC 230: Soft decline. The authorization request was approved by the issuing bank but was flagged because it did not pass the Card Verification Number (CVN) check. You can capture the authorization, but consider reviewing the order for the possibility of fraud
.
The error message during capture failure says:
Auth code is missing or invalid
.
Workaround
None.

Payments
 | 1576231

Description
A defect is allowing authorizations to succeed when the purchase order number is sent in an incorrect format. These transactions fail during settlement.
Audience
Merchants in the US.
Technical Details
The API field names for the purchase order number field are:
REST API
:
orderInformation.invoiceDetails.purchaseOrderNumber
Simple Order API
:
invoiceHeader_userPO
Workaround
Be sure to send API values using the correct format.

Fraud Management Essentials
 | 1525926

Description
Due to a defect, when an order that is pending review is viewed in the Transaction Details page in the Business Center, the Marking Tool feature is not available.
Audience
Users of Fraud Management Essentials.
Technical Details
None.
Workaround
Use the Fraud Management Essentials page to review orders until this defect is resolved.

Token Management System (TMS)
 | 1045848

Description
A defect is affecting TMS in the following scenario:
  1. An existing customer token contains an existing payment insturment token that uses
    either
     credit card or bank account.
  2. An additional payment instrument token is created for that customer token. The first payment instrument token was credit card and the new payment instrument token is bank account, or the old payment instrument token was bank account and the new payment instrument token is credit card.
  3. The orginial payment instrument token is used in an existing autopay.
  4. The new payment instrument token is set to default.
The result is that the payment request fails.
Audience
Users of TMS.
Technical Details
None.
Workaround
None.

Decision Manager
 | 1589720

Description
Merchants that review transactions in Decision Manager are experiencing intermittent timeout failures while searching for customer information in the Negative List.
Audience
Decision Manager users that review customer infromation in the Negative List.
Technical Details
None.
Workaround
Try selecting a date range to limit the number of results until the defect is fixed.

Payment REST API
 | 1561824

Description
The Payment REST API is sending HTTP response code 202 instead of 201 when the error reason is
contact_processor
.
Audience
Users of the Payment REST API.
Technical Details
The affected endpoint is
pts/v2/payments
.
Workaround
None.

Boarding and Virtual Terminal
 | 001548638

Description
Virtual Terminal is visible in the Business Center to merchant accounts onboarded to the VAP portfolio that are not enabled for Virtual Terminal.
Audience
Resellers on the VAP portfolio.
Technical Details
None.
Workaround
None.

Reporting
 | 1542583

Description
A defect is affecting the Transaction Request Report. For some requests that resulted in 102 errors, the Rmsg column is not populated.
Audience
Users of the Transaction Request Report.
Technical Details
None.
Workaround
None.

Payments
 | 1484767

Description
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.
Audience
Users of enhanced data.
Technical Details
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.
Workaround
None.

Payments

Description
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.
Audience
Merchants that use Streamline for payment processing.
Technical Details
The Merchant Reference Number is being passed during authorization instead of the Transaction Reference Number.
Workaround
For reconciliation purposes, use the Merchant Reference Number in the Clearing File.

Reports
 | 1549972

Description
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.
Audience
Merchants who subscribed to reports in the Africa/Cairo Time Zone.
Technical Details
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"
Workaround
Reports after September 21 are working properly. The affected reports must be recreated as a one-time report.

Dynamic Data
 | 1209374

Description
Merchants on Elevon Americas that enable the new Dynamic Data feature might experience transaction failures due to a defect in data validation.
Audience
Merchants on Elevon Americas.
Technical Details
The API field
merchant_country
 is not being validated correctly.
Workaround
If you would like to use the Dynamic Data feature, contact Customer Support to have your account configured and monitored.

Batch Upload
 | 1528573

Description
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
.
Audience
Users of Batch Upload.
Technical Details
None.
Workaround
Manually verify that the value of any
batchID
 field is within the 8 character maximum before uploading.