Known Issues

When digital payment transactions use the Cybersource decryption method and fail with the error

102 DINVALIDDATA Unable to Decrypt Payment Data

, the error is not displayed in reports. This might cause difficulties in identifying the root cause of those rejections during reconciliation.

Merchants and resellers using digital payment transactions that use the Cybersource decryption method.

None.

None.

Transactions processed through the Elavon Americas gateway that combine Decision Manager and payment authorization with CVV are being declined.

Merchants who process Decision Manager transactions and use Elavon Americas.

Error Message:

Reason Code 102

.

Reply Message:

The following request field(s) is either invalid or missing: card_suffix

.

None.

When an Apple Pay refund is submitted for an authorization that is more than 60 days old and the refund uses a two-digit expiration date, the refund is declined.

Merchants who process Apple Pay refunds.

Error Message:

The field is invalid: paymentInstrument.card.expirationYear

.

Send four-digit expiration date.

A defect is affecting authorization reversal responses in the Business Center. When a user in the Business Center initiates an authorization reversal for a transaction that was successfully authorized, the wrong authorization amount is returned in the response.

Users that process transactions in the Business Center.

The user receives this response code:

RC 102 There is a problem processing this request: Auth reversal amount does not match auth amount

.

None. The authorization, if not captured, will expire in the issuer's system.

Users who do not have administrator permissions in the Business Center may be unable to see some negative list hyperlinks under Decision Manager > Case Management > Model Results, and in Transaction Management > Transaction > Transaction Details.

Merchants using Decision Manager to review orders.

None.

None.

Some users of the VAP Portfolio might be able to set up new gateways for existing merchant accounts, which can cause transaction failure.

Merchants who use the Business Center's Merchant Management feature to configure Merchant accounts using the Card Processing template.

If a user who does not have

Template Edit

permission edits the card processing configuration of an existing Merchant ID by adding a new gateway, our internal gateway selector might not send transactions to the expected gateway.

Ensure that Template Edit permission is given to all users who configure merchant accounts in the Business Center.

A defect is causing transactions for pre-paid non-reloadable cards that are approved by Worldpay to be declined by our system due to invalid response code mapping.

Merchants who process transactions for pre-paid non-reloadable cards using Worldpay.

None.

None.

When a zero-amount authorization in included in a subscription creation request, the request results in failure for American Express, Discover, Diners, JCB, and China Union Pay transactions.

Merchants processing on FDC Nashville and performing Token Creation calls without a Full Auth Amount.

This defect results in reason code 102:

DINVALIDDATA

with description

$0 auth not supported for [Card Scheme] on this gateway

.

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.

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.

Users of Virtual Terminal who perform Level III transactions.

The user receives the error message:

Level2PurchaseOrderNumber is a required field

.

Use the API instead of Virtual Terminal.

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.

Global.

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

.

None.