On This Page
Known Issues
Custom Roles on VAP | 1641831
- Description
- When a reseller account uses the Visa Analytics Platform (VAP) to create a custom role for a merchant-level user, the role is not applied, and the user does not inherit the permissions for the custom role.
- Audience
- Users of VAP who use custom roles.
- Technical Details
- None.
- Workaround
- To add the custom role:
- Navigate to the newly created account's user profile.
- Select the User Role drop-down menu.
- Select CUSTOM.
- Create the custom role.
Reporting | 1542583
Reporting
| 1542583- Description
- When digital payment transactions use the Cybersource decryption method and fail with the error102 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.
- Audience
- Merchants and resellers using digital payment transactions that use the Cybersource decryption method.
- Technical Details
- None.
- Workaround
- None.
Decision Manager | 1621465
Decision Manager
| 1621465- Description
- Transactions processed through the Elavon Americas gateway that combine Decision Manager and payment authorization with CVV are being declined.
- Audience
- Merchants who process Decision Manager transactions and use Elavon Americas.
- Technical Details
- Error Message:Reason Code 102.
- Reply Message:The following request field(s) is either invalid or missing: card_suffix.
- Workaround
- None.
Apple Pay | 1619722
Apple Pay
| 1619722- Description
- 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.
- Audience
- Merchants who process Apple Pay refunds.
- Technical Details
- Error Message:The field is invalid: paymentInstrument.card.expirationYear.
- Workaround
- Send four-digit expiration date.
Payments | 1600780
Payments
| 1600780- Description
- 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.
- Audience
- Users that process transactions in the Business Center.
- Technical Details
- The user receives this response code:RC 102 There is a problem processing this request: Auth reversal amount does not match auth amount.
- Workaround
- None. The authorization, if not captured, will expire in the issuer's system.