![]() |
A merchant provider may charge service fees or fixed costs for using this service to offset associated costs with maintaining customer and credit card information on their servers. Moneris charges money; and is not recommended for this feature. |
![]() |
If you only need to save credit cards for post dated or recurring payments, PCI Schedule D - post dated may suffice for your needs.
Contact your merchant provider customer support representative to determine if there will be any additional fees to your organization. |
Merchant Profiles are for organizations who are concerned with PCI compliance and wish (or are required to) maintain a PCI Schedule-C compliance within Theatre Manager.
Using Merchant Profiles reduces the exposure risk by maintaining full credit card information directly on the merchant provider's secure PCI-certified servers without having the requirement to store and maintain credit card numbers within Theatre Manager's database. Using Merchant Profiles in a PCI Schedule-C setup, allow full access to Theatre Manager's features such as Post-Dated Payments, Recurring Donations, and the Auto-Renew Season Subscriptions which would typically require a credit card number to be kept on file for each subsequent payment.
Enable Profiles |
|
||||
Profiles API Login Key | The secure API Key used to access credit card profiles on the merchant provider's server.
|
||||
Profiles API URL | The IP Address to use to access the Credit Card Profiles on the merchant provider's server.
|
||||
![]() |
If necessary, you can manage the Customer Credit Card profiles for this merchant. This will not alter the 'credit card' information that has been saved in Theatre Manager It is used to maintain the 'credit card profile' for each of your customers that has been saved to your merchant's PCI-certified secure servers from Theatre Manager. This can be used to cross reference and match the information between the two systems. | ||||
![]() |
As part of a conversoin or initialization process, you can Create Customer Credit Card Profiles for this merchant from existing credit card information saved in Theatre Manager. It is used to create the initial 'customer credit card profile' and save it to your merchant's PCI-certified secure servers. |
Merchant Profiles allows you to store credit card numbers directly with your merchant provider, on their servers, and then access those saved credit card numbers at any time for subsequent processing without the cardholder being present.
A masked card means that it will be displayed in the payment window as '#### **** **** ####'. This renders the PAN useless for all purposes. However, given the first 4 and last 4 digits of any card, you can still validate you're using the correct merchant profile for authorizing the card. |
If your PCI Settings are set to Schedule C to shred cards immediately after use:
If your PCI Settings are set to Schedule D to retain encrypted credit card data in Theatre Manager:
Each merchant provider has its own unique name for the setup and maintaining of "Customer Payment Profiles." When talking with your merchant provider, use the following name to describe the feature you'll be activating:
|
![]() |
If your PCI Settings are set to Schedule D to retain encrypted credit card data in Theatre Manager, and if you process any new credit cards while the Enable Profiles is inactive, a merchant profile will not be created. If you choose to Enable Profiles later on, it is suggested using the function to build merchant profiles for known credit cards, to make the transition back to using merchant profiles more seamless. |
![]() |
If your PCI Settings are set to Schedule C to shred cards immediately after use, and if you process any new credit cards while the Enable Profiles is inactive, a merchant profile will not be created. If you choose to Enable Profiles later on, you will require the full credit card number again before processing another new payment for that patron's credit card. |
No. The Customer Payment Profile's created by the merchant provider are uniquely linked to that merchant provider and your merchant account number. Customer Payment Profiles cannot be shared between different providers or accounts.
Merchant Profiles can be created and saved on your merchant provider's secure PCI-certified servers using the existing credit card information in Theatre Manager.
This window is used as an analysis tool to determine the critical and primary credit card profiles that should have a Merchant Profile created.
Post Dated Payments | Select to include credit cards from non-deposited (future dated) post dated payments. | ||
Recurring Donations (Active) | Select to include credit cards from active and ongoing recurring donations. | ||
Season Auto-Renewal (Active) | Select to include credit cards from active Season Subscriptions that are setup with Auto-Renewals. An active season is defined as the current and previous seasons. | ||
Cards Aged 0 - 6 Months | Select to include credit cards that have been used or updated within the previous 6 months. | ||
Cards Aged 6 - 12 Months | Select to include credit cards that have been used or updated within the previous 6 to 12 months. | ||
Cards Aged 12 - 18 Months | Select to include credit cards that have been used or updated within the previous 12 to 18 months. | ||
Cards Aged 18+ Months | Select to include credit cards that have been used or updated over 18 months ago. | ||
Recurring Donations (inactive) | Select to include credit cards from inactive or completed recurring donations | ||
Season Auto-Renew (Inactive) | Select to include credit cards from inactive Season Subscriptions that are setup with Auto-Renewals. An inactive season has the season pages flagged as inactive or is 2+ seasons ago. | ||
Total Profiles Selected | The total number of credit cards selected to create merchant profiles. | ||
Maximum Profiles to Create | The maximum number of merchant profiles to create during this process. | ||
![]() |
Query Theatre Manager's database to determine the possible number of merchant profiles that can be created; the number of existing merchant profiles; and the number of known credit cards that are unable to be used for creating a merchant profile.
|
||
![]() |
Start the process for creating merchant profiles for the selected credit card numbers.
|
![]() |
Before proceeding, verify that this merchant account has credit card payment types(i.e. VISA, MC, DISC, AMEX, etc.) created and assigned in code tables. If a payment method does not exist as a credit card type for this merchant, a merchant profile will not be created. |
Click here to learn how to access this window.
A confirmation window will open prior to proceeding.
![]() |
Depending on the number of existing credit cards in Theatre Manager, the credit card analysis tool determining the number merchant profiles to create may take a while to complete. |
A progress checklist window will open.
![]() |
If the Maximum Number of Profiles to Create is less than the Total Profiles Selected, the credit card list will be sorted in the following sequential order in attempts to create the most important credit card profiles first:
|
A confirmation window will open prior to proceeding.
![]() |
Depending on the number of merchant profiles requested to create, the process may take a while to complete. |
A progress window will open.
![]() |
Clicking cancel on the progress window will stop the process. All merchant profiles that have been created up to the time the cancel button was clicked, will remain. |
A status window will open.
![]() |
If a message that 0 merchant profiles were created after running the Building Merchant Profiles for Existing Cards function:
|
Merchant Profiles are created automatically when the Merchant Profile option is enabled for a merchant provider. When a credit card number is provided as a form of payment and a merchant profile does not already exist for this specific patron/payment combination, Theatre Manager will communicate with the merchant provider directly to get a Client Token and Payment Token assigned for the patron's payment information.
Patrons will have a separate Client Token/Payment Token combination for each credit card number used for payment.
Merchant Profiles are not shared between merchant providers, even if the merchant account is with the same merchant provider. If you have multiple merchant accounts setup for different operational unit within your organization (i.e. box office sales, internet/web sales and/or development) and each merchant account is enabled to maintain profiles, then a patron could have multiple Client Token/Payment Tokens for the same credit card if the patron provides payment with those different operational units. In most cases the organization only has a single merchant account, thus there would only be a single Client Token/Payment Token for each patron credit card. |
For patron credit card security reasons, functionality to manually enter the Client Tokens/Payment Tokens generated by a merchant provider into Theatre Manager is not allowed. |
Click here to learn how to access the Merchant Profiles List window.
Single click on a Merchant Profile to select it.
The Delete Record confirmation opens.
A second Delete Record confirmation opens.
The Merchant Profile from Theatre Manager is now deleted.
Theatre Manager does a best attempt to delete the customer profile from the merchant provider's servers. There could be a circumstance where the customer profile cannot be deleted using the API calls from Theatre Manager. If this occurs, login into your merchant provider's web portal and delete the customer profile manually. |
If the Merchant Profile is referenced by other files in the system, you will be unable to delete it and Theatre Manager will not delete the customer profile from the merchant provider's servers.
The Merchant Profiles List can be used to review the customer profiles created and located on your merchant provider's secure PCI servers. This list can also be narrowed to only patrons on a specific grouping by using select criteria. This window is only visible to an employee if they have been granted access under Employee Setup.
![]() |
Opens the Merchant Profile Detail window for the selected profile. Click here for more information about the profile detail window. |
![]() |
Deletes the merchant profile. Click here for more information on deleting profiles. |
![]() |
Prints a report the of the profiles in the merchant profile list to screen or default print location. |
![]() |
Exports the data from the merchant profiles list into a tab delimited format and saves it to a selected location. |
![]() |
Opens the Patron record for the selected patron. |
Patron # | The unique identifier for this patron account. |
Type | Type of Patron account. |
First Name | The first name of the patron. |
Last Name | The last name of the patron. |
Company | The company that the patron works for. |
Profile # | The company that the patron works for. |
Credit Card | The credit card number. |
Expiry Date | Date the card will expire. |
Name on Card | Name printed on the credit card used for added security when processing the card. |
Active | The state of the card and if it can be selected to process credit card transactions. Expired, lost or stolen cards can be set to an inactive state. |
Blacklisted | Indicates if this credit card is blacklisted for this patron. If blacklisted, the patron cannot use the card again unless this card is reset. |
Merchant # | The unique identifier for this merchant account. |
Merchant Description | The internal description to identify the merchant account. |
To view all merchant profiles created for a specific merchant:
To view all merchant profiles for a specific patron:
To view merchant profiles for a specific patron while making a payment:
![]() |
Deletes the merchant profile. Click here for more information on deleting profiles. |
Merchant | The unique identifier and internal description for this merchant account. | ||
Card Number | The credit card number. | ||
Expiry Date | Date the card will expire. | ||
Name on Card | Name printed on the credit card used for added security when processing the card. | ||
Client Token | The unique identifier assigned by the merchant provider for this patron's customer information. | ||
Payment Token | The unique identifier assigned by the merchant provider for this patron's payment information.
|