Katie - does FX give you any reaqson as to WHY your application is being denied?? (pretty hard to correct something if you don't know what's wrong, isn't it... (and I know FX can be this way sometimes!))
I think assigning some resources to the unsupported connector is a good move. In actuality, it gets the job done just fine (my experience overall so far), but it is definitely long in the tooth. When I had the issue a few months ago of the FX mothership only returning LIST rates rather than my discounts, I spoke with FX tech support multiple times, got them to look at the xml rate requests my site was sending, they noted that the requests were structured according to pretty old versions of the FX Web Services Developers Guide, they strongly suggested the code be updated if we want the confidence that it will continue to work going forward. (So, YES - please do that!)
And while your guys are in there, might I suggest that you modify the code so that we could select either Use List Rates, or Use Contract Rates. And also make it so it will accept a NEGATIVE handling charge for each service (so if we choose Use List Rates we can apply a discount off list (rather than having to ADD a handling charge to our negotiated rates). I had my site developer modify my copy to accept negative handling charge, and it worked great. (He did NOT modify so we could CHOOSE list or contract rates, so as it is, if the FX mothership hiccups on me again, I would have to catch it and change to negative hdl fee, and then watch it to see when the mothership corrects and go back in & change back to positive hdl fee (royal PITA but at least a workaround). If you like, I'd be happy to share the negative hdl fee code he did do with you, at least that's half of the mod that's needed?
THANKS for your willingness to pursue this!
(And I'm still willing to hep in any way I can if you want to continue to press for the full supported integration.)
AbleCommerce for ASP.NET
Release Label: GoldR10