How does the website/webapi determine which payment method to use with a credit card purchase?
We're working on our Transcend migration, and want to be sure the correct merchant id is used.
It is based on MOS -
In the API you can determine what the available payment methods are by using the GetPaymentMethod function. The function returns the available payment methods based on the MOS rules for that session.Here is an example of the GetPaymentMethod dataset:
<PaymentMethod diffgr:id="PaymentMethod1" msdata:rowOrder="0"> <id>90</id> <description>Amex - WEB</description> <auth_ind>Y</auth_ind> <pmt_type>1</pmt_type> <pmt_type_desc>Credit Card</pmt_type_desc> <account_type>American Express</account_type> <card_prefix>37</card_prefix> <address_verification>Y</address_verification> <merchant_id>[snip]</merchant_id> <use_cv2>N</use_cv2> </PaymentMethod>
Just a small correction here. The payment methods returned are based on the security rights over payment methods for the web user. So the code first figures out the web user for the current session (based on organization if necessary), then figures out that users' default user group and returns the payment methods to which that user group has rights.
Chuck,
Our payment methods for our box office and internet sales have the same control group. I ran this query:
select *from tr_payment_methodwhere coalesce(inactive, 'n') = 'n'and pmt_method_group = 2and pmt_type = 1order by pmt_method_group
I can see two payment methods for each credit card type, one for the box office and one for the web. I'm still trying to determine how the API picks the correct one.