Momentus Enterprise includes built-in support* for the following payment gateways:
- Authorize.NET
- PayPal Express Checkout
- PayPal Payflow Pro
- TrustCommerce TC Link
- CyberSource2 Simple Order API
Momentus Enterprise is Touchnet Ready for Registration and Service Order Processing. If you use a payment gateway not included above, Momentus can provide assistance in developing a custom gateway connection. Contact your Account Manager or Customer Success Manager for more information.
You can also have more than one gateway provider per organization in the system.
*Momentus Enterprise does not support the Strong Customer Authentication (SCA) or 3DSecure (3DS) functionality out-of-the-box for these gateways. If you require this functionality, Momentus can provide assistance in developing a custom gateway connection. Contact your Account Manager or Customer Success Manager for more information.
Create a Payment Gateway Configuration
- Click Payment Gateway Configurations from the Main Menu. The Payment Gateway Configuration screen opens.
- Click the drop-down arrow next to the Add Configuration button.
- Select your payment gateway. The Add Integration Configuration screen opens.
- Enter the required information for:
- All payment gateways:
- Description - Name for the gateway. For example, if you have multiple merchant accounts, description could be Merchant A or Merchant Account B.
- Environment - Select if the payment configuration is for your Production (live) or Sandbox (test) environment.
- Authorize.Net:
- API Login ID
- Transaction Key
- Market Type (Retail, E-Commerce, MOTO)
- PayPal Express Checkout (only supported for Registration):
- API Login ID
- Password (sometimes referred to as Secret)
- PayPal PayPro Flow:
- Partner
- Merchant ID
- User
- Password
- TrustCommerce TC Link:
- Merchant ID
- User
- Password
- CyberSource 2 Simple Order API:
- Merchant ID
- User
- Transaction Key: See Generate Keys for CyberSource 2 (Cloud Only)
- Country Code Format
- All payment gateways:
- Click OK. You return to the Payment Gateway Configuration screen.
- Repeat steps 1 - 5 for additional merchant accounts or credit card processors.
Configure the Organization Parameters
- Click the Accounts Receivable Configuration link from the Main Menu. The Accounts Receivable Configuration screen opens.
- Select the Credit Card Processing tab.
- Select Basic from the Component drop-down.
- Click OK.
Configure the Receivable Transaction Types
Create a receivable transaction type for each payment option. Make sure to check the Authorize check box on the CC Authorization tab for each receivable transaction type. See Receivable Transaction Types for more information on setting up receivable transaction types.
Assign the Payment Gateway Configuration
You can assign payment gateways to the following:
- Organization Default - Determines the default gateway to use for credit card processing. If your organization has only one gateway, then you need to assign the gateway here. If your organization has multiple gateways, then the gateway assigned here is used as the default if the system cannot find the other gateways via the event or receivable transaction type.
- Receivable Transaction Type - Payment gateway configuration used depends on the receivable transaction type selected for the payment.
- Payment Configuration - Payment gateway is designated via the Payment Configuration for a public-facing application.
- Event - Payment gateway configuration used depends on the payment configuration assigned to the event.
If there are multiple payment gateways assigned, the hierarchy for determining which gateway to utilize is as follows:
1. Event
2. Payment Configuration
3. Receivable Transaction Type
4. Organization Integration Defaults
Organization Default Payment Gateway
If your organization uses one credit card gateway/merchant account, make the payment gateway configuration an organization-level default.
- Click the Organization Integration Defaults link from the Main Menu. The Organization Integration Defaults screen opens.
- Select the configuration created above from the Payment Gateway Configuration drop-down.
- Click OK.
Receivable Transaction Type Payment Gateway Configuration
For organizations using multiple payment gateway providers and/or merchant accounts, you can configure which payment gateway is used based on the receivable transaction type selected for the payment. For example, if multiple venues share the same organization but have different merchant accounts for payments, you can create separate sets of receivable transactions types for each venue’s credit card transactions. You can then assign the appropriate payment gateway to each receivable transaction type.
- Click the Receivable Transaction Types link from the Main Menu. The Receivable Transaction Types screen opens.
- Right-click on a receivable transaction type and select Edit. The Edit Receivable Transaction Types screen opens.
- Select the payment gateway configuration to use with the receivable transaction type from the Payment Gateway Configuration drop-down.
- Click OK.
- Repeat steps 2 - 4 to assign payment gateways to other credit card transaction types.
Payment Configuration - Payment Gateway Configuration
For organizations using multiple payment gateway providers and/or merchant accounts, you can configure which payment gateway is used based on the payment configuration assigned to a public-facing application. For example, if multiple venues share the same organization but have different merchant accounts for payments, you can designate for public-facing applications to look towards the Payment Configuration to determine which merchant account to use for processing.
- Click the Payment Configuration link from the Main Menu. The Payment Configuration screen opens.
- Right-click on a Payment Configuration and select Edit. The Edit Payment Configuration screen opens.
- Select the payment gateway configuration to use with the Payment Configuration from the Payment Gateway Configuration drop-down.
- Click OK.
- Repeat as needed to assign the gateway to other Payment Configurations.
Event Payment Gateway Configuration
For organizations using separate merchant accounts for event-specific transactions, you assign the payment gateway to the event. This ensures all credit card payments accepted for the event go to through the correct gateway/merchant account.
- Click the Events button from the Global Navigation Bar. The Events screen opens.
- Select the event for the payment gateway.
- Right click and select Tools -> Financials -> Events Payment Gateway Configuration. The Add Events Payment Configuration screen opens.
- Select the payment gateway configuration for the event from the Payment Gateway Configuration drop-down.
- Click OK.
Comments
7 comments
Hello, we are looking for the " generic payment url". In the v19 it could be found under "accounts recievable configuration" - tab "credit card processing".
Many thanks for your help
Verena Zublasing
0 upvotes
Hi Verena -
The Generic Payment URL can be found in the Organization Parameters window - It is AR198. The information would go into the Value field.
We will look into adding it to the main receivables configuration window for easier access.
Thanks!
Lauren
0 upvotes
hi Lauren,
thank you so much for your help and the prompt reply!!
Verena
0 upvotes
Where in the system can I find our merchant number? I need to delete a merchant account.
Thanks
Robert
0 upvotes
Hi Robert -
If you are using the original v19 credit card processing configuration, then the merchant id can be found by going to Organization parameters > Parm = AR140: Credit Card Auth Merchant ID.
If you are using a version prior to .96, organization parameters can be found by going to Organization master > then selecting Parameters. If you are using .96, organization parameters is located off the main menu.
Thanks!
Lauren
0 upvotes
Hi Laura,
We are using Version 20.94. I looked but couldn't find our merchant ID.
Thanks for your assistance.
Robert
0 upvotes
Hi Robert -
I will send you a followup email that contains this information for you.
Thanks!
Lauren
0 upvotes
Please sign in to leave a comment.