Which Payment Methods for the webapi?

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_method
where
    coalesce(inactive, 'n') = 'n'
and
    pmt_method_group = 2
and
    pmt_type = 1
order 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.

HI David,

In the IT and DBA documentation folder for Tessitura there is a sub folder of Third Party Interfaces. There is a Transcend and Tessitura doc that I found helpful. I was a little confused at the beginning, but it all makes sense now.

But even better...did you catch the webinar on transcend migration? I found it really helpful. It can be found in the learning and resources section.

Jennifer,

Thanks, I will dig into both of those resources.  I'm not doing most of the Transcend work, just helping with the Tessitura end of it.

I was sent an email to look in the security app for payment method permissions, and that made it clear.  I don't know where those permissions are stored in the database though.  I don't need to know, I was just surprised I didn't see it with all of my rooting around.

I still have the odd issue that the web payment methods don't have a merchant_id set.  It's null.  I posted about that here:

http://www.tessituranetwork.com/COMMUNITY/forums/t/375.aspx

Does it just work because the correct merchant_id for those is '000'?