We are looking at a partnership with AMEX and of course they want only AMEX as a possible payment method so we need to limit our Internet-AMEX mode of sale to only allow AMEX cards. Is there a way to do this, while still allowing our regular Internet MOS to accept all other cards?
Michele
Hi Michele,
We have run into the same challenge. Unfortunately, I do not know of any native way to do this. We implemented a custom table and procedure that we exposed via the REST API to handle this sort of thing.
Here is an overview of what we did:
(1) I built a custom table that ties specific payment methods to MOS. I create a row in this table for the MOS we're using for AMEX-only promotions to only have an AMEX payment method.
(2) We define all other rules in the table, including default handling so that we don't have to literally define rules for every MOS.
(3) When we have an AMEX promo code that changes the user's session to the special MOS.
(4) During checkout, we call our custom procedure that incorporates the custom table to identify payment methods instead of the standard SOAP API call.
That solution has worked well for us. I'd be happy to share the table and procedure code if that would be helpful.
Thanks,David