On This Page
Known Issues
Payer Authentication | 1401886
Payer Authentication
| 1401886- Description
- A defect was discovered that happens when a Payer Authentication Enroll request is sent by a merchant whose account configuration contains an incorrect country code value. The resulting error code is a genericESYSTEMcode instead of a more meaningful code that indicates the problem.
- Audience
- Users of Payer Authentication.
- Technical Details
- None.
- Workaround
- Call Customer Support to have your configuration updated to include the correct merchant country code.
Reporting | 1391959
Reporting
| 1391959- Description
- A defect was discovered that causes custom reports in the Business Center to fail when the time zone is set toAsia/Rangoon.
- Audience
- Merchants who create custom reports in the Business Center.
- Technical Details
- None.
- Workaround
- Choose a different time zone.
Payments Using AmexDirect | 1320151
Payments Using AmexDirect
| 1320151- Description
- A defect was discovered that affects merchants who are payment aggregators and use Amex Direct as their payment processor. When these merchants submit the Merchant Category Code (MCC) through the API, the code does not take precedent over the code that is already stored in their merchant configuration, which could lead to transaction failures.
- Audience
- Merchants processing aggregator transactions on Amex Direct and send the MCC in API requests.
- Technical Details
- None.
- Workaround
- None.
Payer Authentication using Electronic Check Debit | 1288928
Payer Authentication using Electronic Check Debit
| 1288928- Description
- Users who submit Electronic Check Debit requests through Payer Authentication may encounter an error message statingThe following request fields is either invalid or missing: IPAddress. This issue arises when an IPV6 address, which is a 39-character string, is passed into thedeviceInformationfield using the REST API.
- Audience
- Users of Payer Authentication and Electronic Check Debit.
- Technical Details
- The Cardinal gateway is designed to accept an IP address with a maximum length of 20 characters.
- Workaround
- Use an IPV4 address.
Pay by Link
Pay by Link
- Description
- Clicking the Pay button multiple times when using Pay By Link can result in multiple charges.
- Audience
- Users of Pay By Link.
- Technical Details
- None.
- Workaround
- None.
Payments | 1349008
Payments
| 1349008- Description
- The REST API FieldmerchantInformation.merchantDescriptor.alternateNameis inconsistently validated for some payment services by our servers. This can lead to incorrect information being accepted as successful.
- Audience
- Users of the REST API.
- Technical Details
- None.
- Workaround
- To prevent this defect, follow the documented field lengths for all services. Failure to do so might cause declines.
Simple Order API and SOAP Toolkit API | 1356890
- Description
- The reconciliation ID is not being returned in credit transaction responses.
- Audience
- All Simple Order API and SOAP Toolkit API users who perform credit transactions and want to capture the reconciliation ID.
- Technical Details
- TheccCreditReply_reconciliationReferenceNumberfield was not mapped correctly.
- Workaround
- None.
Linked Credit Transactions | 1394514
- Description
- There is an intermittent issue that sometimes causes the Credit option to become unavailable for transactions in the Transaction Details page of the Business Center.
- Audience
- Users of the Business Center.
- Technical Details
- None.
- Workaround
- Use a stand-alone credit instead of a linked credit.
Recurring Billing | 001354539
Recurring Billing
| 001354539- Description
- Merchants using the Edge browser who use the Business Center’s Merchant Switch feature to switch to a subordinate merchant account and then attempt to create a new subscription in Recurring Billing might receive an error message sayingTry Again Later.
- Audience
- Users of Edge, Merchant Switch, and Recurring Billing.
- Technical Details
- None.
- Workaround
- Using Google Chrome does not trigger this error.
Payer Authentication with Network Tokens | 1332105
Payer Authentication with Network Tokens
| 1332105- Description
- There is a flaw in processing some Mastercard transactions when using Chase Paymentech as a processor. If a Mastercard payment transaction uses a network token containing card credentials and received a successful Payer Authentication response, the transaction fails when it is received by Chase Paymentech.
- Audience
- Merchants who process Mastercard transactions through Chase Paymentech and use Payer Authentication and network tokens.
- Technical Details
- The transaction request fails because unnecessary data is added to it by our system.
- Workaround
- Do not migrate Mastercard tokens to network token until the defect is resolved.
TMS and Transaction Details | 1367414
TMS and Transaction Details
| 1367414- Description
- An intermittent issue sometimes causes the Transaction Details page to wrongly identify the token type of a transaction and generate a hyperlink which fails to return results.
- Audience
- TMS users relying on Transaction Details pages.
- Technical Details
- None.
- Workaround
- Navigate to theToken Management > Customerspage and filter the results using the token displayed in the Transaction Details page.
API Testing—Partial Authorization
API Testing—Partial Authorization
- Description
- Attempts to use our testing environment to test FDI Global API processor test triggers for Partial Authorization are not returning an expected value in the fieldauth_account_balanceif the merchant category code (MCC) is not set correctly.
- Audience
- Merchants for FDI Global who test Partial Authorization API transactions in our testing environment.
- Technical Details
- If Merchant Category Code (MCC) is set to 1111 in the request, theauth_account_balanceresponse field contains 9999999999.99 instead of 100.00.
- Workaround
- Configure merchants in the testing environment with a valid MCC when using FDI Global as a processor.
Merchant Boarding with Meta Key | 1375954
Merchant Boarding with Meta Key
| 1375954 - Description
- Some portfolio merchants are unable to assign Meta Keys to subordinate accounts.
- Audience
- Users of merchant boarding and meta keys.
- Technical Details
- None.
- Workaround
- None.