- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Patment getting declined
I have set up integration from salesforce to authorize.net. All transactions go through as expected but Visa. All visa payments are getting declined. It says
Declined (Card declined by issuer - Contact card issuer to determine reason.) |
But the payment is processed when I start the transaction from auth.net portal, it works. Not sure why is this not working using api and why only visa cards. If this had been one customer, it might have been bank issue but all visa customers can not be bank issue. Any guidance is appreciated
โ12-10-2024 04:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue with Visa card payments sounds tricky, especially since the transactions work fine from the Authorize.net portal but not through your Salesforce API integration. Itโs worth checking if there are discrepancies between the API setup and how transactions are processed through the portal. For instance, make sure all required fields, like billing address, CVV, and Visa-specific security protocols, are correctly included in the API requests.
Also, review your fraud detection settings. Sometimes, transactions can be flagged as high risk due to AVS mismatches or other minor discrepancies, which could explain why Visa is being declined. It might also help to check the transaction type and verify that nothing in the API calls is triggering issues, like incorrect merchant codes or transaction flags.
Since this is affecting all Visa transactions, it seems like a configuration issue rather than individual banks rejecting payments. You might want to compare your live environment setup with the sandbox and reach out to Authorize.net support for detailed logs or guidance. They could help pinpoint whether additional settings or permissions for Visa are needed on the API level.
โ12-11-2024 02:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you @RobertJoseph00 @Sufyan7
This was an api issue, I was using subsequent payment even for the first time payments. Removing that part resolved it.
โ12-18-2024 11:04 AM